Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Shell script - Finding Autosys job status Post 302588831 by Rksiva on Tuesday 10th of January 2012 04:28:08 AM
Old 01-10-2012
Try this,

Code:
#!/bin/ksh
 
while read line
do
    . <<Path>>
    autorep -j $line
done<Jobs_List.txt

 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Documentation and books on Autosys Job Control Tool from Autosys

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

autosys job name in the called script

Hi, i have an autosys job 'AUTJOBA' that calls a script script1.sh Now, inside the script i would like to know the autosys job that kicked off this script. When AUTJOBA runs script1.sh, will it set an environmental variable for this shell session that can be accessed within this script? ... (1 Reply)
Discussion started by: ysrinu
1 Replies

3. Shell Programming and Scripting

How to list the Autosys jobs thats in failure status using Shell Script

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

4. UNIX for Dummies Questions & Answers

How to list the Autosys jobs thats in failure status using Shell Script

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

5. Windows & DOS: Issues & Discussions

Autosys unable to set the job to the status of FAILED

Hi The Autosys job that call DOS batch file which in turn calls java and this java program has successful completion though there are series of exception occurred in the data it handles and want the job to be set to Fail in its autosys, how could it be done? a.bat { java sample.class ... (1 Reply)
Discussion started by: muthupus
1 Replies

6. UNIX for Dummies Questions & Answers

Job Status for running shell script

Hello, I am running a shell script whose execution often takes several hours to complete. Is there way I can get some kind of status update as the job is running? Something as simple as the start and the current time stamp. Thanks, Gussi (2 Replies)
Discussion started by: Gussifinknottle
2 Replies

7. Shell Programming and Scripting

Script to Start a Job after finding the Old job completed

Hi Experts, I need a script advice to schedule 12 jobs ( SAS Codes execute back ground ). Algorithem: 1. Script checks first job. 2. Finds first job is done; invoke second job. 3. finds second job is done; invoke third job. .. Request you to please assist. (3 Replies)
Discussion started by: Jerald Nathan
3 Replies

8. UNIX for Dummies Questions & Answers

How to findsuccessful job status completion in Autosys, programatically

We are using autosys for job scheduling. How to find successful job status completion in Autosys, programatically. Based on the successful job completion , mail has to be trigeered to Business users. Please help Thanks (0 Replies)
Discussion started by: vkalya
0 Replies

9. Shell Programming and Scripting

Please help me to develop this script for autosys job

:wall:Hi All, I want to build script to force start the list of child jobs under a box. I prepared this below script, but this script need to some bug fix at run time. Please help me to to develop this script. Please let me know if any thing require for this script. Advance thank for all.. ... (3 Replies)
Discussion started by: pradipta_pks
3 Replies

10. Shell Programming and Scripting

Shell script to set trap for finding cron job failures

Unix box: solaris 5.8 Server: IP Need to to set trap for cron job failures by writing a shell script (5 Replies)
Discussion started by: ChandruBala73
5 Replies
queuedefs(4)						     Kernel Interfaces Manual						      queuedefs(4)

NAME
queuedefs - queue description file for at, batch, and crontab SYNOPSIS
DESCRIPTION
The file describes the characteristics of the queues managed by (see cron(1M)). Each non-comment line in this file describes one queue. The format of the lines are as follows: [njob[nice[nwait The fields in this line are: q The name of the queue, such that is the default queue for jobs started by (see at(1)), is the queue for jobs started by (see at(1)), and is the queue for jobs run from a file (see crontab(1)). Queue names through designate user-defined queues. njob The maximum number of jobs that can be run simultaneously in that queue. Although any number can be specified here, (see cron(1M)) by default limits the number of jobs that can be run on all the queues to 100. This limitation can be removed by setting the variable to 1 in the file. nice The value to give to all jobs in that queue that are not run with a user ID of super-user (see nice(1)). 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 more than 100 jobs were running in all the queues (see njob above). EXAMPLES
Consider the following file: The file is interpreted as follows: The queue, for jobs (see at(1)), can have up to 4 jobs running simultaneously, and those jobs will be run with a value of 1. Since no nwait value is given, if a job cannot be run because too many other jobs are running, will wait 60 seconds before trying again to run it (see cron(1M)). The queue, for jobs (see at(1)), can have up to 2 jobs running simultaneously. Those jobs will be run with a value of 2. If a job cannot be run because too many other jobs are running, 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 value of 2, and if a job cannot be run because too many other jobs are running, will wait 60 seconds before trying again to run it. SEE ALSO
at(1), nice(1), crontab(1), cron(1M), proto(4). STANDARDS CONFORMANCE
queuedefs(4)
All times are GMT -4. The time now is 02:04 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy