02-20-2014
When you "run it as a job [manually]", how is it getting the password? In our Autosys environment, we give the jobs the password automatically and it reads and goes on its' merry way.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
My project uses Autosys.
I am new to this product and I don't know where to start from.
Q1. Please provide me the link where I can get Autosys documentation
Q2. Please refer a good book on Autosys. (Beginner/Intermediate Level) (0 Replies)
Discussion started by: gram77
0 Replies
2. Shell Programming and Scripting
Hi,
i have an autosys job 'AUTJOBA' that calls a script script1.sh
Now, inside the script i would like to know the autosys job that kicked off this script.
When AUTJOBA runs script1.sh, will it set an environmental variable for this shell session that can be accessed within this script?
... (1 Reply)
Discussion started by: ysrinu
1 Replies
3. Shell Programming and Scripting
Hi All
Something really weird happened, I have an autosys job:
insert_job: CAT_LDN_BaseCorrs job_type: c
command: $$(LDNFIRC)\CAT_LDN_BaseCorrs.bat -modeldate $$MODEL_DATE -cutdate $$CUT_DATE
permission: gx, mx, wx
description: "Rerun=0;625;#CAT_Autosys"
std_out_file:... (0 Replies)
Discussion started by: evilsmile2004
0 Replies
4. Shell Programming and Scripting
Hi
I am new to this Scripting process and would like to know How can i write a ksh script that will call other ksh scripts and write the output to a file and/or email.
For example
-------
Script ABC
-------
a.ksh
b.ksh
c.ksh
I need to call all three scripts execute them and... (2 Replies)
Discussion started by: pacifican
2 Replies
5. Shell Programming and Scripting
Hi,
A ------> B ------> C
I have a scenario where each day, my server B would ftp to server A and pull (A,B,C,D,E) from a specific directory.
Server C would need files (B,D) only when server B finished receiving from server A. These files change everyday, so sometimes it takes longer... (3 Replies)
Discussion started by: arex876
3 Replies
6. UNIX for Advanced & Expert Users
Hi,
I need to create a autosys job which will run on every sunday at 7:30 AM NY time for each 10 min interval of time.
days_of_week: su
start_mins: 0,10,20,30,40,50
run_window:"07:30"
Is it fine? Please help
Thanks,
Anup (2 Replies)
Discussion started by: anupdas
2 Replies
7. UNIX for Dummies Questions & Answers
Hi,
There are 2000 jobs in the list and i need to draw their status. I put all the jobs in the list and trying to read one by one from the list and to find out the status.
Help me out in correcting the script.
#!/bin/csh
for a in $(cat Jobs_List.txt);
do
source <<path>>
autorep -j $a... (1 Reply)
Discussion started by: venkatesht
1 Replies
8. Shell Programming and Scripting
:wall:Hi All,
I want to build script to force start the list of child jobs under a box. I prepared this below script, but this script need to some bug fix at run time. Please help me to to develop this script. Please let me know if any thing require for this script. Advance thank for all..
... (3 Replies)
Discussion started by: pradipta_pks
3 Replies
9. Windows & DOS: Issues & Discussions
I'm not sure if this is the right place to post this issue...but here goes...
I am converting a set of windows jobs from Control-M to AutoSys r11.3. The same command line is being executed in both systems. The Control-M job runs to compltion in about 1.5 hours, waiting for the entire batch... (3 Replies)
Discussion started by: ajomarquez
3 Replies
10. Solaris
Hi All,
We run Many jobs evryday using Autosys. Sometimes due to various reason we got to run the job from terminal as well (using nohup).
We observed that the job running through terminal(nohup) takes much less time then the autosys (for same job).
What can be the possible reason for such... (1 Reply)
Discussion started by: kg_gaurav
1 Replies
PSERVER(1) pserver PSERVER(1)
NAME
pserver - NetWare print server
SYNOPSIS
pserver [ -S server ] [ -h ] [ -U user name ] [ -P password | -n ] [ -C ] [ -q queue name ] [ -c command ] [ -j job type ] [ -t timeout ] [
-d ]
DESCRIPTION
pserver is a program that connects to print queues on NetWare servers and feeds incoming print jobs to the Linux printing system.
OPTIONS
-h
-h is used to print out a short help text.
-S server
server is the name of the server you want to use.
-U user
user is the print server name at the server.
-P password
password is the password to use for the print server at the server. If neither -n nor -P are given, and the user has no open connection
to the server, pserver prompts for a password.
-n
-n should be given if the print server does not require a password.
-C
By default, passwords are converted to uppercase before they are sent to the server, because most servers require this. You can turn off
this conversion by -C.
-q queue name
queue name is the name of the print queue you want to service.
-c command
When a job is received from the print queue, pserver forks off a new process, and feeds the job file to stdin. command is the printing
command that is executed for each job. The default command is 'lpr'.
You can insert several flags into the command, preceded by %. These are replaced with values retrieved from the queue structure for the
print job.
%u: This field will be replaced by the name of the user who posted this print job.
%d: This field will be replaced by the job description field of this print job.
-j job type
Each job in a NetWare print queue has a job type. For print jobs, this corresponds to the number of the form the job should be printed
on. You can tell pserver that it should only receive jobs for one specific form from the queue. The default is -1, which means that
everything is received.
-t timeout
Pserver is not informed by NetWare servers when new jobs arrive. So a polling scheme has to be used. When there are no jobs to service,
timeout tells pserver how long to wait between two requests. The default is 30 seconds. When a job is finished, pserver asks the NetWare
server immediately for a new job, and does not wait timeout seconds.
-d
Normally, pserver daemonizes itself. -d tells it not to do so. This is useful if you want to see the diagnostic messages that are
printed when a error occurs.
SEE ALSO
nwclient(5), slist(1), pqlist(1), ncpmount(8), ncpumount(8)
CREDITS
pserver was written by Volker Lendecke (lendecke@math.uni-goettingen.de)
pserver 10/22/1996 PSERVER(1)