Job Requirement information in the SIRD-11 message for CA 7
search cancel

Job Requirement information in the SIRD-11 message for CA 7

book

Article ID: 27673

calendar_today

Updated On:

Products

CA 7 Workload Automation

Issue/Introduction

What does the Job Requirement information in the SIRD-11 message mean?

 

Environment

Release:
Component: 7

Resolution

If you have REQUIREMENT-LIST: Y on the DB.1 screen for a job, when that job comes into the request queue an SIRD-11 message is sent to the browse data set. If job requirements exist for the job entering the queue, then there are dates and times associated with those job's requirements on the message. This article describes the dates and times that appear for job requirement information in the SIRD-11 message.

Five different scenarios are discussed in this document

  1. SIRD-11 message with a predecessor job that is not satisfied
  2. SIRD-11 message with a predecessor job that is satisfied
  3. SIRD-11 message with a predecessor job that has never run
  4. SIRD-11 message with a predecessor job that has run, but the successor job has never run.
  5. SIRD-11 message where neither predecessor job nor successor job has ever run
  1. Job JOB1 has requirement of JOB2 which is NOT SATISFIED when it comes into the queue:
    SIRD-11 **** JOB=JOB1 (0003) EXECUTION REQUIREMENTS **** JCLID=000SYSTEM= DESC= DUE-OUT 06.159/0932 DEAD-LINE 06.159/0932 MAINID=SCHID=030 PROSE#=**NONE** ERQD=000 ENSAT=000 IRQD=001 INSAT=001MCNT=002 FLAGS=24/0C/00/02/80/00/02*** REQUIREMENTS *** _______ INTERNAL JOB=JOB2 DATE/TIME=05233/12:41:31.67 04125/11:15:31 
    • The first date/time on the job requirement listed in the SIRD-11 message is the date/time that the requirement should have run to be initially satisfied:
      JOB=JOB1                                            DATE=06.159    PAGE 0001                                                                                   
      JOB ----JCL---- SYSTEM USR MAIN PROSE SCHED --NUMBER OF- LAST-RUN
      NAME ID MEMBER -NAME- -ID -ID- DSNBR DSNBR STP DDS RUNS DATE/TIME
      JOB1 000 JOB1 010 ALL *NONE* 000044 000 000 0000 05233/1241
    • The second date/time on the job requirement listed in the SIRD-11 message is the date/time that the job that is the requirement last ran:
      JOB=JOB2                                           DATE=06.159    PAGE 0001   
      JOB ----JCL---- SYSTEM USR MAIN PROSE SCHED --NUMBER OF- LAST-RUN
      NAME ID MEMBER -NAME- -ID -ID- DSNBR DSNBR STP DDS RUNS DATE/TIME
      JOB2 000 JOB2 MSRTEST 010 ALL *NONE* 000172 001 005 0001 04125/1115
  2. Job JOB1 has requirement of JOB2 which IS SATISFIED when it comes into the queue:
    SIRD-11 **** JOB=JOB1  (0005) EXECUTION REQUIREMENTS **** JCLID=000                  
    SYSTEM= DESC=
    DUE-OUT 06.159/0935 DEAD-LINE 06.159/0935 MAINID=
    SCHID=030 PROSE#=**NONE** ERQD=000 ENSAT=000 IRQD=001 INSAT=000
    MCNT=001 FLAGS=24/0C/00/02/80/00/02
    *** REQUIREMENTS ***
    _______ JOB ON HOLD
    ___X___ INTERNAL JOB=JOB2 DATE/TIME=06159/08:35:09.53 05233/12:41:31
    • The first date/time on the job requirement listed in the SIRD-11 message is the date/time that the job that is the requirement last ran:
      JOB=JOB2                                            DATE=06.159    PAGE 0001   
      JOB ----JCL---- SYSTEM USR MAIN PROSE SCHED --NUMBER OF- LAST-RUN
      NAME ID MEMBER -NAME- -ID -ID- DSNBR DSNBR STP DDS RUNS DATE/TIME
      JOB2 000 JOB2 MSRTEST 010 ALL *NONE* 000172 001 005 0001 06159/0835
    • The second date/time on the job requirement listed in the SIRD-11 message is the date/time that the job that has the requirement last ran:
      JOB=JOB1                                            DATE=06.159    PAGE 0001                                                                                   
      JOB ----JCL---- SYSTEM USR MAIN PROSE SCHED --NUMBER OF- LAST-RUN
      NAME ID MEMBER -NAME- -ID -ID- DSNBR DSNBR STP DDS RUNS DATE/TIME
      JOB1 000 JOB1 010 ALL *NONE* 000044 000 000 0000 05233/1241
  3. Job JOB1 has requirement of JOB3 which has never run when it comes into the queue:
    JOB=JOB3                                             
    JOB ----JCL---- SYSTEM USR MAIN PROSE SCHED --NUMBER OF- LAST-RUN
    NAME ID MEMBER -NAME- -ID -ID- DSNBR DSNBR STP DDS RUNS DATE/TIME
    JOB3 000 JOB3 MINE 010 SY1 *NONE* *NONE* 000 000 0000 00000/0000
    • There is only one date/time on the job requirement listed in the SIRD-11 message and it is the date/time that the job that has the requirement last ran:
      JOB=JOB1                                            DATE=06.159    PAGE 0001                                                                                   
      JOB ----JCL---- SYSTEM USR MAIN PROSE SCHED --NUMBER OF- LAST-RUN
      NAME ID MEMBER -NAME- -ID -ID- DSNBR DSNBR STP DDS RUNS DATE/TIME
      JOB1 000 JOB1 010 ALL *NONE* 000044 000 000 0000 05233/1241
  4. Job JOB3 which has never run has requirement of JOB1 which has run when it comes into the queue:
    JOB=JOB3                                            
    JOB ----JCL---- SYSTEM USR MAIN PROSE SCHED --NUMBER OF- LAST-RUN
    NAME ID MEMBER -NAME- -ID -ID- DSNBR DSNBR STP DDS RUNS DATE/TIME
    JOB3 000 JOB3 MINE 010 SY1 *NONE* *NONE* 000 000 0000 00000/0000

    SIRD-11 **** JOB=JOB3 (0008) EXECUTION REQUIREMENTS **** (NON-EXECUTABLE)
    SYSTEM= DESC=
    DUE-OUT 06.159/0952 DEAD-LINE 06.159/0952 MAINID=1
    SCHID=001 PROSE#=**NONE** ERQD=000 ENSAT=000 IRQD=001 INSAT=001
    MCNT=002 FLAGS=26/0C/20/02/00/40/00
    *** REQUIREMENTS ***
    _______ JOB ON HOLD
    _______ INTERNAL JOB=JOB1 DATE/TIME=06159/08:51:12.18 05233/12:41:31.67
    • The first date/time on the job requirement listed in the SIRD-11 message is the date/time that the job that has the requirement came into the queue.

    • The second date/time on the job requirement listed in the SIRD-11 message is the date/time that the job that is the requirement last ran:
      JOB=JOB1                                            DATE=06.159    PAGE 0001                                                                                   
      JOB ----JCL---- SYSTEM USR MAIN PROSE SCHED --NUMBER OF- LAST-RUN
      NAME ID MEMBER -NAME- -ID -ID- DSNBR DSNBR STP DDS RUNS DATE/TIME
      JOB1 000 JOB1 010 ALL *NONE* 000044 000 000 0000 05233/1241
  5. Job JOB3  which has never run has requirement of JOB4 which has never run when it comes into the queue:
    JOB=JOB3                                             
    JOB ---JCL---- SYSTEM USR MAIN PROSE SCHED --NUMBER OF- LAST-RUN
    NAME ID MEMBER -NAME- -ID -ID- DSNBR DSNBR STP DDS RUNS DATE/TIME
    JOB3 000 JOB3 MINE 010 SY1 *NONE* *NONE* 000 000 0000 00000/0000
    JOB=JOB4 DATE=06.159 PAGE 0001
    JOB ----JCL---- SYSTEM USR MAIN PROSE SCHED --NUMBER OF- LAST-RUN
    NAME ID MEMBER -NAME- -ID -ID- DSNBR DSNBR STP DDS RUNS DATE/TIME
    JOB4 000 JOB4 MINE 010 SY1 *NONE* *NONE* 000 000 0000 00000/0000
    SIRD-11 **** JOB=JOB3 (0009) EXECUTION REQUIREMENTS **** (NON-EXECUTABLE)
    SYSTEM= DESC=
    DUE-OUT 06.159/1040 DEAD-LINE 06.159/1040 MAINID=1
    SCHID=001 PROSE#=**NONE** ERQD=000 ENSAT=000 IRQD=001 INSAT=001
    MCNT=002 FLAGS=26/0C/20/02/00/40/00
    *** REQUIREMENTS ***
    _______ JOB ON HOLD
    _______ INTERNAL JOB=JOB4 DATE/TIME=06159/09:39:04.21
    • Only one date/time is listed on the job requirement listed in the SIRD-11 message and it is the time that the job with the requirement came into the queue.