Sections of the Job Scheduling Definition

1. Enter the IOA Online Facility and request the Scheduling Definition facility.

   The Scheduling Definition entry panel is displayed.

2. Enter your library and table names in the LIBRARY and TABLE fields, and IDJOB3 in the JOB field. The request appears as shown below:

   Figure 21 Control-M Scheduling Definition Facility - Entry Panel

  ----------- CONTROL-M SCHEDULING DEFINITION FACILITY - ENTRY PANEL ---------(2)

   COMMAND ===>

   SPECIFY LIBRARY, TABLE, JOB

      LIBRARY ===> CTM.TEST.SCHEDULE

      TABLE   ===> IDGS1               (Blank for table selection list)

      JOB     ===> IDJOB3              (Blank for job selection list)

      SMART TABLE         ===> (Y - for new SMART Table)

   SHOW JOB DOCUMENTATION   ===> N     (Y/N)

   AUTO-SAVE DOCUMENTATION  ===> N     (Y/N)

  USE THE COMMAND SHPF TO SEE PFK ASSIGNMENT                             23.00.04

The Job Scheduling Definition screen for IDJOB3 is displayed.

Figure 22 Job Scheduling Definition Screen

  JOB: IDJOB3   LIB CTM.TEST.SCHEDULE                             TABLE: IDGS1

  COMMAND ===>                                                    SCROLL===> CRSR

  +-----------------------------------------------------------------------------+

    MEMNAME IDJOB3      MEMLIB  

    OWNER   ID          TASKTYPE JOB    PREVENT-NCT2   DFLT  N

    APPL                                GROUP

    DESC   

    OVERLIB                                                   STAT CAL

    SCHENV                         SYSTEM ID                  NJE NODE

    SET VAR

    CTB STEP AT         NAME            TYPE

    DOCMEM  IDJOB3      DOCLIB  

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

    DAYS                                                          DCAL

                                                                       AND/OR

    WDAYS                                                         WCAL

    MONTHS  1- Y 2- Y 3- Y 4- Y 5- Y 6- Y 7- Y 8- Y 9- Y 10- Y 11- Y 12- Y

    DATES

    CONFCAL                      RETRO N MAXWAIT 00   D-CAT

    MINIMUM          PDS

    DEFINITION ACTIVE FROM          UNTIL                     

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

    RESOURCE

   COMMANDS: EDIT, DOC, PLAN, JOBSTAT                                    11.17.00

In Introduction to Control-M, you learned that the job scheduling definition is partitioned into sections, each section separated from the preceding section by a line of equal signs.

To familiarize yourself with several more fields in these sections, you will fill in the job scheduling definition for IDJOB3. To do this, you must first outline the type of processing you expect for IDJOB3, which requires that you assume the following:

• IDJOB3 is an application that tabulates certain fiscal results once a month.
• IDJOB3 should always be scheduled on the last Friday of the month.
• IDJOB3 should be submitted only if the previous execution of the job (during the previous month) ended OK.
• IDJOB3 should be submitted only if the following resources are available:
  • 1 tape drive
  • 5 units of a CPU resource called IDCPOWER:
• IDJOB3 should be submitted from sometime between the hours of 11:00 p.m. on Friday night and 4:00 a.m. on Saturday Morning.
• IDJOB3 should be considered a critical path job with a priority of 5.
• IDJOB3 should be automatically submitted, no requirement for manual confirmation.
• If IDJOB3 ends OK, the appropriate reports are generated by the application.
• If the budget for IDJOB3, as defined in the application, was exceeded, the job returns a condition code of C0008 or above, depending on the amount by which the budget was exceeded, and the job should end NOTOK.
• If IDJOB3 ends OK, a prerequisite condition should be created indicating that it ended OK and the corresponding condition from the previous month’s run should be deleted.
• If IDJOB3 ends NOTOK, that is, if it has a condition code of C0008 or higher, the following should occur:
  • A condition should be created stating that the job ended NOTOK.
  • An appropriate message should be sent, or shouted, to user OPER1.
  • An auxiliary job, called IDJOB4, should be run to perform additional processing.

You can now fill in the job scheduling definition of IDJOB3. Note that fields are described only briefly in the following sections, and that not all fields are discussed. Detailed descriptions for all fields of the Job Scheduling Definition screen are discussed in the Control-M for z/OS User Guide.