Post-Processing Parameters Section

The fields in the fourth section of the Job Scheduling Definition screen correspond to the Job Scheduling Definition Post-Processing parameters.

    ===========================================================================

    OUT     

    AUTO-ARCHIVE            SYSDB           MAXDAYS      MAXRUNS

    RETENTION:  # OF DAYS TO KEEP      # OF GENERATIONS TO KEEP

    SYSOUT OP   (C,D,F,N,R)                                              FROM

    MAXRERUN     RERUNMEM                              INTERVAL       FROM

    STEP RANGE         FR (PGM.PROC)          .          TO          .

    ON PGMST          PROCST          CODES                               A/O

      DO

    SHOUT WHEN           TIME       +     DAYS     TO                  URGN

      MS

  ======= >>>>>>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<<<<<< =====

These Post-Processing parameters define actions to be performed by Control-M after the job ends. Basically, these can be divided into three main groups—those relevant if the job ends OK, those relevant under specified circumstances, and those that are always relevant.

The OUT parameter has already been discussed, and those discussions are relevant only if the job ends OK. Table 7 explains several other Post-Processing parameters.

Table 7 Post-Processing Parameters ON and DO Statements

Note that this section contains a SHOUT WHEN statement. This statement, which is not examined in this chapter, is different than the DO SHOUT statement.

You had previously decided to request the following post-processing activities:

• If the job ends OK, which is a condition code of less than C0008
  • the prerequisite condition of the successful run from the previous month, should be deleted
  • a new prerequisite condition indicating that the job ended OK should be created.
• If the job ends NOTOK, that is, it has a condition code of C0008 or higher
  • a condition must be created to indicate that the job ended NOTOK.
  • an appropriate message must be shouted to your user ID.
  • auxiliary job IDJOB4 must be run to perform additional processing.

You can now define the necessary values.

1. Fill in the OUT fields with the following value:
   IDJOB3-ENDED-OK  ODAT +

   After filling in the second condition, a new, blank OUT condition line is opened to enable you to specify another condition.

2. In the ON block, specify ANYSTEP in the PGMST (program step) field, and specify the value >C0007 in the CODES field. A value equal to or greater than C0008 is synonymous with a value greater than C0007.
3. In the DO field, type COND and press Enter.

   The DO COND statement is opened, as is a blank DO statement for specification of another DO statement.

4. Fill in the DO COND fields with the following values:

   IDJOB3-END-NOTOK   ODAT +

5. In the blank DO field, type SHOUT and press Enter.

   The DO SHOUT statement is opened, as is a blank DO statement for specification of another DO statement, as shown below.

        DO SHOUT     TO                     URGENCY  
         =
        DO

6. In the DO SHOUT statement, specify your user ID in the TO subparameter field; replace the R (Regular) with U (Urgent) in the URGENCY field; and specify the message FRIDAY FISCAL RESULTS RUN FAILED following the equal sign (=).

   Note that the only urgency value, other than R and U,  is V, which signifies a Very Urgent message.

7. In the blank DO field, type FORCEJOB and press Enter.

   The DO FORCEJOB statement is opened, as is a blank DO statement for specification of another DO statement, as shown below.

        DO FORCEJOB  TABLE                  JOB                       DATE
                     LIBRARY
        DO

8. In the DO FORCEJOB statement, specify the current table name (IDGS1)in the TABLE field; specify IDJOB4 in the JOB field; specify ODAT in the DATE field; and specify the current scheduling library name in the LIBRARY field.

   This section of the job scheduling definition appears as shown below:

     ===========================================================================
  OUT      IDJOB3-ENDED-OK      ODAT +                                        
                                                                             
  AUTO-ARCHIVE            SYSDB           MAXDAYS      MAXRUNS                
  RETENTION:  # OF DAYS TO KEEP      # OF GENERATIONS TO KEEP                 
  SYSOUT OP   (C,D,F,N,R)                                              FROM   
  MAXRERUN     RERUNMEM                              INTERVAL       FROM      
  STEP RANGE         FR (PGM.PROC)          .          TO          .          
  ON PGMST ANYSTEP  PROCST          CODES >C0007                          A/O
    DO COND          IDJOB3-END-NOTOK     ODAT +                              
    DO SHOUT     TO  ID                 URGENCY U                            
     = FRIDAY FISCAL RESULTS RUN FAILED                            
    DO FORCEJOB  TABLE   IDGS1          JOB   IDJOB4              DATE ODAT   
                 LIBRARY CTM.TEST.SCHEDULE                                   
    DO                                                                        
  ON PGMST          PROCST          CODES                               A/O   
    DO                                                                        

   You have now finished defining IDJOB3.

9. Exit the job scheduling definition of IDJOB3.

   The Job List screen is displayed. This is where you can take a closer look at the use of IN, OUT, and DO COND conditions, and their date qualifiers, to create job dependencies.