04-22-2009
Hey gil bates..
This is Mahesh..
Actually can u tell me the step-by-step procedure for installing Autosys in a Linux Environment. And do u have any Reference Manual for Autosys for Unix Users...
Ur help will be really appreciated..
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello,
I want to know about job scheduling utilities available in unix. It should not be responsible just for starting the job like in case of cron but should also be able to handle the execution of jobs.
Regards,
Ritesh (1 Reply)
Discussion started by: turlapaty
1 Replies
2. 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
3. UNIX and Linux Applications
I am working on UNIX AIX system, with Oracle OS.
We are not supposed to use any tools to schedule our unix shell scripts.
Basically we have to make use of Oracle tables and Shell scripts to manage dependencies, restartability, scheduling, parallelizing,etc.
If anyone has worked/ is working... (1 Reply)
Discussion started by: singhabhijit
1 Replies
4. Shell Programming and Scripting
I am working on UNIX AIX system, with Oracle OS.
We are not supposed to use any tools to schedule our unix shell scripts.
Basically we have to make use of Oracle tables and Shell scripts to manage dependencies, restartability, scheduling, parallelizing,etc.
If anyone has worked/ is working... (4 Replies)
Discussion started by: singhabhijit
4 Replies
5. UNIX and Linux Applications
Hello!
I will be working with Autosys and I am looking for individuals that have knowledge of this UNIX application.
Thank-you! (3 Replies)
Discussion started by: preshe79
3 Replies
6. Shell Programming and Scripting
We need to configure autosys that when a job fails continously for 3 times, we need to call another job.
Is this possible in Autosys, or can anyone advice on the alternative. (2 Replies)
Discussion started by: sangea
2 Replies
7. Shell Programming and Scripting
Below is the requirement i am trying to do using auto sysjob.
I need to create a JOB or script which will do the below things for me
I have a box and there corresponding jobs as below
BOX_1
JOB_1
JOB_2
BOX_2--- SU(JOB_2), this will run only on completion (Success) of JOB_2
... (2 Replies)
Discussion started by: j_panky
2 Replies
8. Shell Programming and Scripting
Hi All,
I am new to unix and i have a task in front of me.
The code part is "android update sdk" . I need to crontab this process.
Hence i have written a script that runs the above command and sends a mail once the update is done. The problem with the automation is the installer asks for a... (5 Replies)
Discussion started by: Kashyap
5 Replies
9. UNIX for Advanced & Expert Users
I have submitted an autosys job and force start it. Autosys hit the job 4 times to restart but it did not start and finally I terminate the job. Any idea why the job did not start. Below is the code I executed.
1214 missun0ap /export/home/bzn97r/develop/dswi/jil$ sendevent -E FORCE_STARTJOB... (0 Replies)
Discussion started by: jnrohit2k
0 Replies
10. Shell Programming and Scripting
Hi Friends,
There is an Autosys scheduled job that runs on the second day of the month, and it is using the Business day calendar.
So when the month starts on a weekend or there is a holiday at the beginning of the month the second business day and second day of the month obviously do not... (1 Reply)
Discussion started by: Aditya_001
1 Replies
AT(1) General Commands Manual AT(1)
NAME
at - execute commands at a later time
SYNOPSIS
at [ -c ] [ -s ] [ -m ] time [ day ] [ file ]
DESCRIPTION
At spools away a copy of the named file to be used as input to sh(1) or csh(1). If the -c flag (for (csh(1))) or the -s flag (for (sh(1)))
is specified, then that shell will be used to execute the job; if no shell is specified, the current environment shell is used. If no file
name is specified, at prompts for commands from standard input until a ^D is typed.
If the -m flag is specified, mail will be sent to the user after the job has been run. If errors occur during execution of the job, then a
copy of the error diagnostics will be sent to the user. If no errors occur, then a short message is sent informing the user that no errors
occurred.
The format of the spool file is as follows: A four line header that includes the owner of the job, the name of the job, the shell used to
run the job, and whether mail will be set after the job is executed. The header is followed by a cd command to the current directory and a
umask command to set the modes on any files created by the job. Then at copies all relevant environment variables to the spool file. When
the script is run, it uses the user and group ID of the creator of the spool file.
The time is 1 to 4 digits, with an optional following `A', `P', `N' or `M' for AM, PM, noon or midnight. One and two digit numbers are
taken to be hours, three and four digits to be hours and minutes. If no letters follow the digits, a 24 hour clock time is understood.
The optional day is either (1) a month name followed by a day number, or (2) a day of the week; if the word `week' follows, invocation is
moved seven days further off. Names of months and days may be recognizably truncated. Examples of legitimate commands are
at 8am jan 24
at -c -m 1530 fr week
at -s -m 1200n week
At programs are executed by periodic execution of the command /usr/libexec/atrun from cron(8). The granularity of at depends upon the how
often atrun is executed.
Error output is lost unless redirected or the -m flag is requested, in which case a copy of the errors is sent to the user via mail(1).
FILES
/usr/spool/at spooling area
/usr/spool/at/yy.ddd.hhhh.* job file
/usr/spool/at/past directory where jobs are executed from
/usr/spool/at/lasttimedone last time atrun was run
/usr/libexec/atrun executor (run by cron(8))
SEE ALSO
atq(1), atrm(1), calendar(1), sleep(1), cron(8)
DIAGNOSTICS
Complains about various syntax errors and times out of range.
BUGS
Due to the granularity of the execution of /usr/libexec/atrun, there may be bugs in scheduling things almost exactly 24 hours into the
future.
If the system crashes, mail is not sent to the user informing them that the job was not completed.
Sometimes old spool files are not removed from the directory /usr/spool/at/past. This is usually due to a system crash, and requires that
they be removed by hand.
4th Berkeley Distribution October 21, 1996 AT(1)