10 More Discussions You Might Find Interesting
1. 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
2. Shell Programming and Scripting
I need to know the list of autosys job that run between given time.
I have the following command.
job_depends -t -J abc% -F "12/25/2010 03:00" -T "12/26/2010 05:00"
Above command will give the list of job that run between time 3 AM and 5 AM.
But the it gives me in random order how to... (1 Reply)
Discussion started by: diehard
3. UNIX for Dummies Questions & Answers
Hi Can any one tell me free online good book for autosys job.
Also whats the basic difference between Autosys job and cron job.
Thanks in advance. (2 Replies)
Discussion started by: diehard
4. 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
5. Shell Programming and Scripting
I am trying to schedule an autosys job for weblogic server reboot. When i run the job it is failing with the following error:
/bin/sh: /path/stop_wls instancename: not found
The following is my jil and i dont refer to /bin/sh at all
update_job: mgd_shutdown_cmd.jil job_type: c ... (3 Replies)
Discussion started by: userscript
6. UNIX and Linux Applications
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
7. UNIX for Advanced & Expert Users
I want to schedule a job through Autosys (in Linux server) to run on 1st day of every 3rd month(gap of 90 days). Please someone help me to achive my above requirement
Run the sample.sh on 01-Jan-2009, 01-Apr-2009, 01-Jul-2009, 01-Oct-2009.
Thanks in advance (4 Replies)
Discussion started by: apsprabhu
Hello - We have setup printers to startup in the /etc/rc.d/8 directory and when the SCO system is booted this script should kick them off or start them up but it doesn't. So I have to start it from root and leave the window open. I know this isn't right and trying to figure out what's missing. ... (13 Replies)
Discussion started by: dbm7230
9. 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
10. UNIX for Advanced & Expert Users
could someone tell me how do I update an autosys job?
i was trying something like:
$ jil < solarCleaning.jil -V none
Insert/Updating Job: solarCleaning
*** CANNOT INSERT Job: solarCleaning, because... (3 Replies)
Discussion started by: nosnam
stopped(7) Miscellaneous Information Manual stopped(7)
stopped - event signalling that a job has stopped
stopped JOB=JOB INSTANCE=INSTANCE RESULT=RESULT [PROCESS=PROCESS] [EXIT_STATUS=STATUS] [EXIT_SIGNAL=SIGNAL] [ENV]...
The stopped event is generated by the Upstart init(8) daemon when an instance of a job has stopped. The JOB environment variable contains
the job name, and the INSTANCE environment variable contains the instance name which will be empty for single-instance jobs.
If the job was stopped normally, the RESULT environment variable will be ok, otherwise if the job was stopped because it has failed it will
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 was stopped because it hit the respawn
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) emits this event as an informational signal, services and tasks started or stopped by this event will do so in parallel with other
activity. It is typically combined with the starting(7) event by services when inserting themselves as a dependency.
Job configuration files may use the export stanza to export environment variables from their own environment into the stopped event. See
init(5) for more details.
A service that wishes to be running whenever another service would be running, started before and stopped after it, might use:
start on starting apache
stop on stopped apache
A task that must be run after another task or service has been stopped might use:
start on stopped postgresql
starting(7) started(7) stopping(7) init(5)
Upstart 2009-07-09 stopped(7)