Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Refresh the jobs in Autosys Scheduler Post 302908074 by Lakme Pemmaiah on Thursday 3rd of July 2014 10:31:30 AM
Old 07-03-2014
Hi Robin,

The Application Server through which we run Autosys Scheduler was down on 21st and the daily jobs were halted from 22nd of June. Hence , we had to run it manually.

once the server was upend running,i found the force start job and send event options in autosys GUI were not working fine .And i was not able to get the details of the failed or running jobs. It would show only the jobs which ran successfully until 21st June.Even the commands like "autorep -J ALL|grep RU" or "autorep -J ALL|grep FA" were not giving me any result.So I thought if I try to refresh the Scheduler and try, I may get the result(Details of the failed jobs from 22nd) properly.
Then I ran this command "chk_auto_up" to check if there was no connection to the database, but the output showed that the Database was up but the event processor was not running for the server. So i Ran the "eventor" command to start the event processor for the server.
And now im able to run all the halted jobs manually in the CA Workload Automation AE(CA Autosys).


Lakme Pemmaiah.

Last edited by Lakme Pemmaiah; 07-04-2014 at 12:40 PM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

creating and modifying jobs in autosys

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

Searching Status for 2 Autosys jobs

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

Repeated execution of Autosys Jobs

post deleted ... (2 Replies)
Discussion started by: Data469
2 Replies

4. 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

5. Shell Programming and Scripting

How to find out which jobs are referencing my AutoSys variable?

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

6. UNIX for Advanced & Expert Users

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... (1 Reply)
Discussion started by: SPJ47
1 Replies

7. UNIX for Dummies Questions & Answers

Autosys jobs

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 Advanced & Expert Users

Autosys Scheduler- Running job at particular time

Hi Experts, I am new to Autosys. I created a Autosys box job to run at 10 AM daily. As scheduled, the job starts on time. There is another box job inside the box. I have scheduled it to run at 11 AM but it kicks off automatically with the main job at 10 AM. insert_job: Main-job ... (2 Replies)
Discussion started by: pk_bohra
2 Replies

9. Shell Programming and Scripting

Help required in Identifying child jobs in autosys recursively.

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

How to list autosys detail jobs?

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
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)
All times are GMT -4. The time now is 08:01 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy