Previous Topic: Data Set Requirements for Jobs in the QueueNext Topic: Use VRM


SIRD-11 Message

Use REQUIREMENT-LIST: Y on the DB.1 panel for a job. With this option, 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, dates and times are associated with those job requirements on the message.

Business Value:

This best practice helps you understand time calculations on the SIRD-11 message and helps with troubleshooting issues with job predecessors.

Additional Considerations:

The following are examples of the SIRD-11 message.

Note: If the predecessor job is added as a predecessor after the last run of a job, the results are different. That situation is not discussed in these scenarios. Take some precautions (a special watch, at least) the first time a job runs in CA WA CA 7 Edition (or has a new predecessor added).

Example: SIRD-11 message with a predecessor job that is not satisfied

Job USERABC has requirement of USERABC1, which is NOT SATISFIED when it comes into the queue:

SIRD-11 **** JOB=USERABC (0003) EXECUTION REQUIREMENTS **** JCLID=000
        SYSTEM= DESC= 
        DUE-OUT 06.159/0932 DEAD-LINE 06.159/0932 MAINID=
        SCHID=030 PROSE#=**NONE** ERQD=000 ENSAT=000 IRQD=001 INSAT=001
        MCNT=002 FLAGS=24/0C/00/02/80/00/02
        *** REQUIREMENTS *** 
_______ INTERNAL JOB=USERABC1 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:

LJOB,JOB=USERABC                                            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  
                                                                            
USERABC 000 USERABC         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:

LJOB,JOB=USERABC1                       
JOB    ----JCL----  SYSTEM  USR MAIN PROSE  SCHED  --NUMBER OF-  LAST-RUN  
NAME   ID  MEMBER   -NAME-  -ID -ID- DSNBR DSNBR  STP DDS RUNS   DATE/TIME 
                                                                            
USERABC1 000 USERABC1        010 ALL *NONE* 000172 001 005 0001 04125/1115

Example: SIRD-11 message with a predecessor job that is satisfied

Job USERABC has requirement of USERABC1 which IS SATISFIED when it comes into the queue:

SIRD-11 **** JOB=USERABC  (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=USERABC1   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:

LJOB,JOB=USERABC1
JOB    ----JCL----  SYSTEM  USR MAIN PROSE  SCHED --NUMBER OF-   LAST-RUN  
NAME    ID  MEMBER  -NAME- -ID -ID- DSNBR  DSNBR  STP DDS RUNS   DATE/TIME 
                                                                             
USERABC1 000 USERABC1      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:

LJOB,JOB=USERABC                                                             
JOB   ----JCL----   SYSTEM  USR MAIN PROSE  SCHED  --NUMBER OF-  LAST-RUN   
NAME  ID  MEMBER   -NAME-  -ID - ID- DSNBR  DSNBR  STP DDS RUNS  DATE/TIME  
                                                                            
USERABC  000 USERABC       010 ALL  *NONE* 000044 000 000 0000  05233/1241

Example: SIRD-11 message with a predecessor job that has never run

Job USERABC has requirement of USERABC2 which has never run when it comes into the queue:

SIRD-11 **** JOB=USERABC  (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                                   
_______ INTERNAL JOB=USERABC2   DATE/TIME=05233/12:41:31


LJOB,JOB=USERABC2                                           
JOB   ----JCL----  SYSTEM  USR MAIN PROSE  SCHED  --NUMBER OF-   LAST-RUN   
NAME  ID  MEMBER   -NAME-  -ID -ID- DSNBR  DSNBR  STP DDS RUNS   DATE/TIME  
                                                                            
USERABC2 000 USERABC2      010 SY1  *NONE* *NONE* 000 000 0000  00000/0000

Only one date/time on the job requirement is listed in the SIRD-11 message, and it is the date/time that the job that has the requirement last ran:

LJOB,JOB=USERABC                                                            
JOB   ----JCL----  SYSTEM  USR MAIN PROSE  SCHED  --NUMBER OF-   LAST-RUN   
NAME   ID  MEMBER  -NAME-  -ID -ID- DSNBR  DSNBR  STP DDS RUNS   DATE/TIME  
                                                                            
USERABC  000 USERABC       010 ALL  *NONE* 000044 000 000 0000  05233/1241

Example: SIRD-11 message with a predecessor job that has run, but the successor job has never run

Job USERABC2, which has never run, has a requirement of USERABC which has run when it comes into the queue:

LJOB,JOB=USERABC2                                           
JOB   ----JCL----  SYSTEM  USR MAIN PROSE  SCHED  --NUMBER OF-   LAST-RUN   
NAME  ID  MEMBER   -NAME-  -ID -ID- DSNBR  DSNBR  STP DDS RUNS   DATE/TIME  
                                                                            
USERABC2 000 USERABC2      010 SY1  *NONE* *NONE* 000 000 0000  00000/0000


SIRD-11 **** JOB=USERABC2 (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=USERABC 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:

LJOB,JOB=USERABC                                                           
JOB   ----JCL----   SYSTEM  USR MAIN PROSE  SCHED  --NUMBER OF-  LAST-RUN   
NAME    ID  MEMBER   -NAME-  -ID -ID- DSNBR  DSNBR  STP DDS RUNS DATE/TIME  
                                                                            
USERABC  000 USERABC       010 ALL  *NONE* 000044 000 000 0000  05233/1241

Example: SIRD-11 message where both predecessor job and successor job have never run

Job USERABC2, which has never run, has requirement of USERABC3 which has never run when it comes into the queue:

LJOB,JOB=USERABC2                                           
JOB   ----JCL----  SYSTEM  USR MAIN PROSE  SCHED  --NUMBER OF-   LAST-RUN   
NAM   ID  MEMBER   -NAME-  -ID -ID- DSNBR  DSNBR  STP DDS RUNS   DATE/TIME  
                                                                            
USERABC2 000 USERABC2      010 SY1  *NONE* *NONE* 000 000 0000  00000/0000 

LJOB,JOB=USERABC3                                                           
JOB   ----JCL----  SYSTEM  USR MAIN PROSE  SCHED  --NUMBER OF-   LAST-RUN   
NAME  ID  MEMBER   -NAME-  -ID -ID- DSNBR  DSNBR  STP DDS RUNS   DATE/TIME  
                                                                            
USERABC3 000 USERABC3      010 SY1  *NONE* *NONE* 000 000 0000  00000/0000 
                                                                            
SIRD-11 **** JOB=USERABC2 (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=USERABC3   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.