SIRD-11

**** JOB=xxxxxxxx (nnnn) EXECUTION REQUIREMENTS **** JCLID=nnn
SYSTEM=ssssssss DESC=d...d
DUE-OUT yy.ddd/hhmm DEAD-LINE yy.ddd/hhmm
SUBMIT yy.ddd/hhmm MAINID=xxx
SCHID=nnn PROSE#=pppppppp ERQD=nnn ENSAT=nnn IRQD=nnn
INSAT=nnn MCNT=nnn FLAGS=xx/xx/xx/xx/xx/xx/xx

*** REQUIREMENTS ***
*** JOB PROSE ***

Reason:

This message is issued to the CA Workload Automation SE Master Station or to an alternate station (LTERM) defined in the database entry for the job xxxxxxxx. The message is produced for each job when it enters the request queue due to calendar, trigger, or DEMAND scheduling. Input requirements and their status will be described immediately following the REQUIREMENTS heading. Job prose, if defined in a #QDESC segment, is listed immediately following the JOB PROSE heading. The SYSTEM (sssssss) and the DESC (d...d) value also come from the job prose definition.

The status fields in the message are as follows:

DUE-OUT

Indicates the date/time when the job must complete execution.

DEAD-LINE

Indicates the date/time calculated when the job must begin execution to finish by DUE-OUT time. The value is determined by subtracting the average runtime for the job from DUE-OUT.

SUBMIT

Indicates the date/time specified as a must-submit value in the schedule definition.

MAINID

Indicates the system identifier. If present, MAINID indicates where the job should (or should not) be submitted.

ERQD

Indicates a count of total external requirements.

ENSAT

Indicates a count of external requirements not satisfied.

IRQD

Indicates a count of total internal requirements.

INSAT

Indicates a count of internal requirements not satisfied.

MCNT

Indicates a master count of unsatisfied requirements for the job.

FLAGS

Provides hexadecimal values matching the following fields from the JQREC macro DSECT. The fields are listed in order of appearance in the message.

JQFLG1
JQFLG2
JQJFLG1
JQJFLG2
JQJFLG3
JQJFLG4
JQJFLG5

Note: If a satisfied job requirement is followed by the text "(DRMODE)," the requirement was satisfied because CA Workload Automation SE is in disaster recovery mode, and the predecessor job has an inactive disaster recovery class.

Action:

None.