report of autosys job in RUNNING state


 
Thread Tools Search this Thread
Top Forums Shell Programming and Scripting report of autosys job in RUNNING state
# 1  
Old 09-12-2008
Question report of autosys job in RUNNING state

I am looking to get a report on autosys jobs in RUNNING state b/w certain time frame (timeA and timeB).

What I am after is the list of all the jobs that ran between AND during timeA and timeB.
Jobs within the timeframe could either:

A: STARTING --> RUNNING --> SUCCESS/FAILURE etc..
B: .....RUNNING......(No status changed if the job was already running b/f timeA and continut to run after timeB.
C: .....RUNNING --> SUCCESS/FAILURE etc (already running b/f timeA and finished before timeB)


Simply put, any job that had a RUNNING state during timeA and timeB.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

Job Run Slower using Autosys than running through terminal

Hi All, We run Many jobs evryday using Autosys. Sometimes due to various reason we got to run the job from terminal as well (using nohup). We observed that the job running through terminal(nohup) takes much less time then the autosys (for same job). What can be the possible reason for such... (1 Reply)
Discussion started by: kg_gaurav
1 Replies

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

3. AIX

Open firmware state to running state

Hi Admins, I am having a whole system lpar in open firmware state on HMC. How can I bring it to running state ? Let me know. Thanks. (2 Replies)
Discussion started by: snchaudhari2
2 Replies

4. UNIX for Advanced & Expert Users

Autosys Job Running every 5th Day of Month

Hi, Is there a way to schedule a job in Autosys to run every 5th Day of Month without using custom calendar? Thanks. (1 Reply)
Discussion started by: vbhatnag
1 Replies

5. Shell Programming and Scripting

autosys job configuration for job failure.

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
2 Replies

6. Windows & DOS: Issues & Discussions

Requirements for running an autosys job on Windows server

Hi, I have created an autosys job which calls an exe and updates its output files. The job is failing without updating the output and error files. I if restart the usvmapgrnd01.pc.ml.com machine, the job runs successful for first time and fails rest of the time. Please let me know what might be... (0 Replies)
Discussion started by: sonaldewle
0 Replies

7. UNIX for Advanced & Expert Users

report of autosys job in RUNNING state

I am looking to get a report on autosys jobs in RUNNING state b/w certain time frame (timeA and timeB). What I am after is the list of all the jobs that ran between AND during timeA and timeB. Jobs within the timeframe could either: A: STARTING --> RUNNING --> SUCCESS/FAILURE etc.. B: ... (1 Reply)
Discussion started by: rgilan01
1 Replies

8. Solaris

report of autosys job in RUNNING state

I am looking to get a report on autosys jobs in RUNNING state b/w certain time frame (timeA and timeB). What I am after is the list of all the jobs that ran between AND during timeA and timeB. Jobs within the timeframe could either: A: STARTING --> RUNNING --> SUCCESS/FAILURE etc.. B: ... (2 Replies)
Discussion started by: rgilan01
2 Replies

9. Programming

report of autosys job in RUNNING state

I am looking to get a report on autosys jobs in RUNNING state b/w certain time frame (timeA and timeB). What I am after is the list of all the jobs that ran between AND during timeA and timeB. Jobs within the timeframe could either: A: STARTING --> RUNNING --> SUCCESS/FAILURE etc.. B: ... (0 Replies)
Discussion started by: rgilan01
0 Replies

10. 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
Login or Register to Ask a Question
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)