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.
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)
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)
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)
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)
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)
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... (1 Reply)
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)
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)
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
LEARN ABOUT SUNOS
queuedefs
queuedefs(4) File Formats queuedefs(4)NAME
queuedefs - queue description file for at, batch, and cron
SYNOPSIS
/etc/cron.d/queuedefs
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
q.[njobj][nicen][nwaitw]
The fields in this line are:
q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see
at(1)); c is the default queue for jobs run from a crontab(1) file.
njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100.
nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2.
nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's
queue, or because the system-wide limit of jobs executing has been reached. The default value is 60.
Lines beginning with # are comments, and are ignored.
EXAMPLES
Example 1: A sample file.
#
#
a.4j1n
b.2j2n90w
This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying
again to run it.
The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job
cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All other queues can
have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs
are running cron will wait 60 seconds before trying again to run it.
FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron.
SEE ALSO at(1), crontab(1), nice(1), cron(1M)SunOS 5.10 1 Mar 1994 queuedefs(4)