06-30-2010
Autosys help on Unix server
Hi,
I've few simple questions related to Autosys 4.5. Thought you may be knowing about this. Can you pl. help me in this regard?
Questions:
If I stop Autosys instance systematically thru' the necessary autosys command,
1) What will happen to the autosys job(assume this job runs for 5mins only) which are scheduled to run during that point of time, when instance were down.
2) Once instance is down for 4 hours, what will happen to the job which are scheduled to run after 30 mins or 3 hours? Will that autosys job will run once the instance is restarted and is up & running after 4 hours.
Will I need to forcestart job in that case or autosys will automatically start the job?
3) What will happen to these jobs, if the instance is down suddenly( due to power outage), will I need to restart these autosys jobs manually or this will be taken care of autosys instance automatically.
Thanks for your help in advance.
Mike
8 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 am having a problem running multiple commands in a autosys command line. For example I would like to run a perl script first and then add sleep command after that in the same autosys job like below
insert_job: xxxxxxxxx
command: `perlscript.pl ; sleep 180`
Perlscript.pl... (0 Replies)
Discussion started by: waavman
0 Replies
3. Windows & DOS: Issues & Discussions
Hi, I have created an autosys job which calls an exe and updates its output files. The job is failing without updating the output and error files.
I if restart the usvmapgrnd01.pc.ml.com machine, the job runs successful for first time and fails rest of the time. Please let me know what might be... (0 Replies)
Discussion started by: sonaldewle
0 Replies
4. Shell Programming and Scripting
Hi,
I have the UNIX OS and i want to use autosys job.
What is basic requirement i mean infra needed to create autosys job.
Thanks!!!!!! (0 Replies)
Discussion started by: diehard
0 Replies
5. UNIX for Dummies Questions & Answers
All the autosys jobs are on server-1 and server-1 has been crashed due to some reason, Now I have to run 5 autosys jobs on server-2 (failover server) which are on server 1.
How to do with Autosys command (which command needs to fired on JIL) (0 Replies)
Discussion started by: tp2115
0 Replies
6. UNIX and Linux Applications
Good afternoon:
I need your help plase
IN Prudcution system Autosys 4.5 was used and the was a migration to release Autosys 11. but AFTER THE RELASE TO THE NEW VERSUON r11 i cann not longer connect to the event server, so when i connected to the previous SERVER in A 4.5 i was able to use... (5 Replies)
Discussion started by: alexcol
5 Replies
7. Shell Programming and Scripting
Hi all,
Here is my scenario..
i need to get dates from an existing autosys calendar and compare it with current date with in a unix shell script.
Please help me out and give me an approach to handle this.......
the general autosys calendar command used is autocal_asc ,but this is... (1 Reply)
Discussion started by: shrik12345
1 Replies
8. Programming
Hi all,
I am new to Unix.
I would like to create a Autosys job in Unix. Can you please suggest.
below is the requirement.
1. Need t Send in email every 30 minutes from 11 am to 3:00 PM. E-mail should only be sent ONLY when below Query have data return.
select * from emp where... (1 Reply)
Discussion started by: vasuvv
1 Replies
LEARN ABOUT HPUX
stopping
stopping(7) Miscellaneous Information Manual stopping(7)
NAME
stopping - event signalling that a job is stopping
SYNOPSIS
stopping JOB=JOB INSTANCE=INSTANCE RESULT=RESULT [PROCESS=PROCESS] [EXIT_STATUS=STATUS] [EXIT_SIGNAL=SIGNAL] [ENV]...
DESCRIPTION
The stopping event is generated by the Upstart init(8) daemon when an instance of a job begins stopping. The JOB environment variable con-
tains the job name, and the INSTANCE environment variable contains the instance name which will be empty for single-instance jobs.
If the job is stopping normally, the RESULT environment variable will be ok, otherwise if the job is stopping because it has failed it will
be failed.
When the job has failed, the process that failed will be given in the PROCESS environment variable. This may be pre-start, post-start,
main, pre-stop or post-stop; it may also be the special value respawn to indicate that the job is stopping because it hit the respawn
limit.
Finally in the case of a failed job, one of either EXIT_STATUS or EXIT_SIGNAL may be given to indicate the cause of the stop. Either
EXIT_STATUS will contain the exit status code of the process, or EXIT_SIGNAL will contain the name of the signal that the process received.
The normal exit job configuration stanza can be used to prevent particular exit status values or signals resulting in a failed job, see
init(5) for more information.
If neither EXIT_STATUS or EXIT_SIGNAL is given for a failed process, it is because the process failed to spawn (for example, file not
found). See the system logs for the error.
init(8) will wait for all services started by this event to be running, all tasks started by this event to have finished and all jobs
stopped by this event to be stopped before allowing the job to continue stopping.
This allows jobs to depend on other jobs, safely stopping themselves before their dependency goes away. This event is typically combined
with the started(7) event by services.
Job configuration files may use the export stanza to export environment variables from their own environment into the stopping event. See
init(5) for more details.
EXAMPLE
A service that wishes to depend on another service might use:
start on started apache
stop on stopping apache
A task that must be run before another task or service is stopped might use:
start on stopping postgresql RESULT=ok
SEE ALSO
starting(7) started(7) stopped(7) init(5)
Upstart 2009-07-09 stopping(7)