Job and Data Set requirements - initial satisfaction

Products

• CA 7 Workload Automation

Issue/Introduction

Why did a job not have its requirement posted? 

Resolution

When jobs are scheduled into the queue for execution, CA 7 attaches requirements for this execution of the job (by SCHID) and then checks to see if the requirement can be immediately satisfied.

For job requirements:

1. If a non-zero lead time (LEADTM) was specified on the DB.3.2 or DB.1 screen, has the job that is a requirement run in the specified time frame?
   
   AND
   
   
2. Has the job that is a requirement run since the dependent job ran? (If the requirement uses a zero LEADTM, then only the second test is made)

For data set requirements:

1. If a non-zero LEADTM was specified on the DB.3.1 screen, then has the data set been created within the specified time frame?
   
   OR
   
   
2. If LEADTM is zero on the DB.3.1 screen, has the data set been created since the last run of the dependent job?

Note: The times used in lead time checking are obtained from the CA 7 data base. For a job, examine the LAST-RUN DATE/TIME from the LJOB display. For a data set, use the LCTLG,DSN=data.set.name command to examine the last creation date and time CA 7 recorded for the data set.

 

Satisfaction Lead Time is also known as LEADTM and can be 0, 1-98, and 99. A 0 LEADTM signifies that the requirement must have been met since the last good run of the job that has the requirement. 1-98 is a number of hours that cannot be exceeded since the requirement was met and a 99 says that the requirement will never be initially satisfied.