08-20-2010
Mutually Exclusive Autosys jobs
Hi
I have 2 autosys jobs (JobA and JobB) both are in different boxes but part of one big box. I want to make them mutually exclusive so that when JobA is running then JobB should not run and wait for jobA to finish/fail/terminate and vice versa.
Both jobs have their own starting conditions and they depend on their predecesors but then should not run at the same time. Is there any such setting in autosys?
SPJ.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
now, I tried looking at the User manuals I can find on the internet concerning autosys but these manuals seem to be quite confusing to me.
My question is, does anyone have a straight forward explanation on how to modify and/or create jobs in autosys??? (3 Replies)
Discussion started by: TRUEST
3 Replies
2. UNIX for Dummies Questions & Answers
I need to search for a failed status of 2 autosys jobs which write to the same logfile. Is there any way to do that on one line? I already know the following doesn't work, but is there a way to get it to work, or will I have to do a loop?
RUN_STATUS=autorep -J jobname jobname
if
then
... (1 Reply)
Discussion started by: tekster757
1 Replies
3. Shell Programming and Scripting
post deleted ... (2 Replies)
Discussion started by: Data469
2 Replies
4. Shell Programming and Scripting
hello There,
I am pretty much new to Shell Scripting and also to AutoSys. I would like to know how to list the Autosys jobs in FA status using shell scripting. I would like to get an email alert as and when any Autosys job fails. Also, it should give the path of the Log file.
Could you please... (0 Replies)
Discussion started by: supragna
0 Replies
5. UNIX for Dummies Questions & Answers
Hello There,
I am pretty much new to Shell Scripting and also to AutoSys. I would like to know how to list the Autosys jobs in FA status using shell scripting. I would like to get an email alert as and when any Autosys job fails. Also, it should give the path of the Log file.
Could you please... (5 Replies)
Discussion started by: supragna
5 Replies
6. Shell Programming and Scripting
I need to list out all the AutoSys jobs that are referencing a particular AutoSys global variable.
I know the autorep command will definitely need to be used here, and maybe grep as well, but I can't figure out exactly how it's to be done. For example, "autorep -q -J %jobnamewildcard% | grep... (1 Reply)
Discussion started by: dazzwater
1 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I have a script that take one parameter as an input.
for example:
./clean.sh <foldername>
There are 7 different folder names that we can provide to my script and my script would delete the contents of that folder that was passed as an argument.
Inorder to have this script... (3 Replies)
Discussion started by: shifahim
3 Replies
8. UNIX for Dummies Questions & Answers
Can anyone please tell me how to refresh the jobs in Autosys Scheduler?
---------- Post updated at 03:19 PM ---------- Previous update was at 03:18 PM ----------
I need a command to refresh it. (2 Replies)
Discussion started by: Lakme Pemmaiah
2 Replies
9. Shell Programming and Scripting
I have been working on to neatly present the job dependency lineage in autosys through ksh/perl and I am having trouble in recursively finding the dependency.
it will be great if anyone could share their thoughts on this.?
I know that job_depends in autosys will help me give first level of... (0 Replies)
Discussion started by: Vhunt
0 Replies
10. Shell Programming and Scripting
Hi Gurus,
below list is autosys job output stats, it includes boxes, sub-boxes and detail jobs. detail jobs are most right indented ones in each box. the requests is to get all these detail jobs list.
the only way to identify the "detail job", is intend.
auto_job ... (2 Replies)
Discussion started by: green_k
2 Replies
LEARN ABOUT LINUX
starting
starting(7) Miscellaneous Information Manual starting(7)
NAME
starting - event signalling that a job is starting
SYNOPSIS
starting JOB=JOB INSTANCE=INSTANCE [ENV]...
DESCRIPTION
The starting event is generated by the Upstart init(8) daemon when a new instance of a job begins starting. 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.
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 starting.
This allows jobs to effectively insert themselves as dependencies of other jobs. The event is typically combined with the stopped(7) event
by services.
Job configuration files may use the export stanza to export environment variables from their own environment into the starting event. See
init(5) for more details.
EXAMPLE
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 before another task or service is started might use:
start on starting postgresql
SEE ALSO
started(7) stopping(7) stopped(7) init(5)
Upstart 2009-07-09 starting(7)