Introduction to the Scheduling Definition Facility

You are about to create a Control-M job scheduling definition for each of the jobs, IDJOB1 and IDJOB2, that you just defined. The JCL member name of the job should be used as the name of its corresponding job scheduling definition.

Job scheduling definitions are stored in tables (members) in a scheduling library. A default scheduling library name automatically appears in the entry panel. Ensure that you use a test library or your own work library. You should not use the JCL library.

For purposes of illustration in this guide, the scheduling library is identified as CTM.TEST.SCHEDULE. In this library, you will be creating a table called IDGS1. Use your unique identifier as the first characters of the table name.

You can now begin defining the job scheduling definition for IDJOB1.

Fill in the LIBRARY, TABLE, and JOB name fields in the entry panel. The request appears similar to Figure 2.

Figure 2 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 ===> IDJOB1 (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

After entering the entry panel request, the Job Scheduling Definition screen is displayed. A full job scheduling definition, which contains more lines than your screen can display, is illustrated in Figure 3.

Note that the first line in the screen, which is displayed above the COMMAND line, contains the same information about the job that you provided in the entry panel.

Figure 3 Job Scheduling Definition Screen

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

COMMAND ===> SCROLL===> CRSR

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

MEMNAME IDJOB1 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 IDJOB1 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 SHIFT RETRO N MAXWAIT 00 D-CAT

MINIMUM PDS

DEFINITION ACTIVE FROM UNTIL

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

IN

CONTROL

RESOURCE

PIPE

FROM TIME + DAYS UNTIL TIME + DAYS

DUE OUT TIME + DAYS PRIORITY SAC CONFIRM

TIME ZONE:

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

OUT

AUTO-ARCHIVE Y SYSDB Y 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 <<<<<<<<<<<<<<<< =====

COMMANDS: EDIT, DOC, PLAN, JOBSTAT 11.17.00

The Job Scheduling Definition screen is divided into sections, with each section separated from another by a line of equal signs (= =). Later, you will learn more about these sections and the fields they contain. The following table describes the fields of the Job Scheduling Definition screen that you will complete during these exercises.

Table 1 Job Scheduling Definition Screen Field Descriptions

Field	Description
MEMNAME	Name of the member that contains the JCL of the job.
MEMLIB	Name of the library that contains the JCL of the job.
GROUP	Name of the group to which the job belongs.
DESC	Free text description of the job.
DAYS	Days of the month to schedule the job.
CONFIRM	Yes/No indicator (Y/N) specifying whether manual confirmation is required before the job can be submitted.
OUT	Prerequisite conditions to be added and/or deleted when the job ends OK

Fill in the fields as indicated in the following table.

Table 2 Values for Job Scheduling Definition Screen Fields

Field	Value to Enter (in Bold), and Explanation
MEMNAME	IDJOB1. This value, taken from the entry panel, already appears, because you specified the JCL member name in the JOB field of the entry panel.
MEMLIB	Name of the library containing JCL member IDJOB1. For purposes of illustration, you should use CTM.TEST.JCL
GROUP	IDGRP1. This name will later be used to filter the display of jobs in the Active Environment screen by Group name.
DESC	THIS JOB MUST BE RUN BEFORE IDJOB2 (to remind you what this job does).
DAYS	ALL (Schedule the job every day.)
CONFIRM	Y (Yes - you want manual confirmation for the job.)
OUT	IDJOB1-ENDED-OK ODAT + (After specifying IDJOB1-ENDED-OK, press Tab to get to the field in which to enter ODAT.)

The Job Scheduling Definition screen is displayed as shown in Figure 4.

Figure 4 Job Scheduling Definition Screen Showing Completed Fields

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

COMMAND ===> SCROLL===> CRSR

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

MEMNAME IDJOB1 MEMLIB CTM.TEST.JCL

OWNER ID TASKTYPE JOB PREVENT-NCT2 DFLT N

APPL GROUP IDGRP1

DESC THIS JOB MUST BE RUN BEFORE IDJOB2

OVERLIB STAT CAL

SCHENV SYSTEM ID NJE NODE

SET VAR

CTB STEP AT NAME TYPE

DOCMEM IDJOB1 DOCLIB

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

DAYS ALL 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

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

IN

CONTROL

RESOURCE

PIPE

FROM TIME + DAYS UNTIL TIME + DAYS

DUE OUT TIME + DAYS PRIORITY 00 SAC CONFIRM Y

TIME ZONE:

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

OUT IDJOB1-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 PROCST CODES A/O

DO

SHOUT WHEN TIME + DAYS TO URGN

MS

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

COMMANDS: EDIT, DOC, PLAN, JOBSTAT 11.17.00

Exit the Job Scheduling Definition screen. The Job List screen is displayed.
Figure 5 Job List Screen

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

COMMAND ===>                                                    SCROLL===> CRSR

OPT  NAME ----- DESCRIPTION ---------------------------------------------------

     IDJOB1     THIS JOB MUST BE RUN BEFORE JOB2

====== >>>>>>>>>>>>>>>>    NO MORE JOBS IN TABLE     <<<<<<<<<<<<<<<<<<< =====





































OPTIONS S SEL D DEL I INS O ORDER F FORCE J JCL C COPY P PLN T JOBSTAT 15.37.39

The format of the Job List screen may be different than the format indicated in the screen example shown above. The different formats of the Job List screen will be discussed later in this chapter. The following procedure will ensure that you are working with the desired format.
Enter DESC in the COMMAND field of the Job List screen.
The Job List screen has the same format as the screen example shown above.

The Job List screen contains the list of jobs in the table. In this case, since you created a new table and only one job, there is only one job (IDJOB1) in the list. Notice that the description you provided in the job scheduling definition appears next to the job name in the Job List screen. Providing useful identifying information in the DESC field of the job scheduling definition can help you with job identification in the Job List screen.

You will now create the job scheduling definition for IDJOB2. You could do this much the same way that you created IDJOB1, that is, by returning to the entry panel and there specifying the name IDJOB2. But instead, you will create the job from the Job List screen.
Type I (Insert) in the OPT (Option) field to the left of the entry for IDJOB1, and press Enter.
JOB LIST     LIB: CTM.TEST.SCHEDULE                             TABLE: IDGS1

COMMAND ===>                                                    SCROLL===> CRSR

OPT  NAME ----- DESCRIPTION ---------------------------------------------------

I   IDJOB1     THIS JOB MUST BE RUN BEFORE IDJOB2

====== >>>>>>>>>>>>>>>>    NO MORE JOBS IN TABLE     <<<<<<<<<<<<<<<<<<< =====

The Job Scheduling Definition screen is displayed. When you create a new job using the I (Insert) option in the Job List screen, the newly created job contains most of values defined in the job by which you specified the I option. Only the MEMNAME, DOCMEM, and DESCRIPTION values are not carried over; instead, these fields are left blank.

JOB:          LIB CTM.TEST.SCHEDULE                             TABLE: IDGS1

COMMAND ===>                                                    SCROLL===> CRSR

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

  MEMNAME             MEMLIB   CTM.TEST.JCL

  OWNER   ID          TASKTYPE JOB    PREVENT-NCT2 Y DFLT  N

  APPL                                GROUP IDGRP1

  DESC

  OVERLIB                                                   STAT CAL

  SCHENV                         SYSTEM ID                  NJE NODE

  SET VAR

  CTB STEP AT         NAME            TYPE

  DOCMEM              DOCLIB

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

  DAYS    ALL                                                   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          SHIFT       RETRO N MAXWAIT 00  D-CAT

  MINIMUM          PDS

  DEFINITION ACTIVE FROM          UNTIL

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

  IN

  CONTROL

  RESOURCE

  PIPE

  TIME: FROM       UNTIL       PRIORITY 00  DUE OUT       SAC      CONFIRM Y

  TIME ZONE:

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

  OUT      IDJOB1-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          PROCST          CODES                               A/O

    DO

  SHOUT WHEN           TIME       +     DAYS     TO                  URGN

    MS

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

COMMANDS: EDIT, DOC, PLAN, JOBSTAT                                    11.17.00
Type IDJOB2 in the MEMNAME field. The DOCMEM field will automatically be filled in with the same value. Leave the DESC field blank.
+-----------------------------------------------------------------------------+

    MEMNAME IDJOB2     MEMLIB   CTM.TEST.JOBLIB

    OWNER   M44         TASKTYPE JOB    PREVENT-NCT2 Y DFLT  N

    APPL                                GROUP IDGRP1

    DESC

    OVERLIB                                                   STAT CAL

    SCHENV                         SYSTEM ID                  NJE NODE

    SET VAR

    CTB STEP AT         NAME            TYPE

    DOCMEM  IDJOB2      DOCLIB

    ===========================================================================
In the IN field, define the same value you had defined as the OUT value in  JOB1 (IDJOB1-ENDED-OK ODAT). You should press Tab before typing ODAT, as you did in IDJOB1. The + from the OUT value is not specified. After defining the IN value, delete the Y from the CONFIRM field.
    ===========================================================================

    IN       IDJOB1-ENDED-OK        ODAT

    CONTROL

    RESOURCE

    PIPE

    FROM TIME         +     DAYS    UNTIL TIME      +     DAYS

    DUE OUT TIME      +     DAYS    PRIORITY 00  SAC    CONFIRM

    TIME ZONE:

    ===========================================================================
Change the plus sign (+) to a minus sign (-) in the OUT statement.
    ===========================================================================

    OUT      IDJOB1-ENDED-OK      ODAT -

    AUTO-ARCHIVE            SYSDB           MAXDAYS      MAXRUNS

The IN and the OUT fields are used for specifying conditions. These conditions can be used to create job dependencies.

In this exercise, you used condition IDJOB1-ENDED-OK to ensure that IDJOB2 would not be submitted until IDJOB1 successfully completed:
- You made IDJOB1-ENDED-OK an IN condition for IDJOB2, which means that IDJOB2 cannot be run until this condition exists, that is, until IDJOB1-ENDED-OK has been created.
- You made IDJOB1-ENDED-OK an OUT condition of IDJOB1, specifying a plus sign in the appropriate place in the condition definition, which means that the condition will only be created after IDJOB1 completed successfully.
Therefore, IDJOB1 must complete successfully before IDJOB2 can be submitted.

Specifying the same condition as an OUT condition with a minus sign in IDJOB2 removes the condition once IDJOB2 has successfully ended. This ensures that an old occurrence of the condition will not satisfy the IN criteria.

Note also that every condition has an associated date value. This can be an explicitly defined date, such as 0909, or a valid keyword value that represents a date. ODAT is a keyword value that defaults to the current original scheduling date of the job. The original scheduling date, and other date concepts, are discussed in Chapter 5, "AutoEdit and JCL."
Exit the job scheduling definition for IDJOB2. The Job List screen is displayed. IDJOB2 now appears in the list, but since you did not define a description for it, no description appears for the job.
Figure 6 Job List Screen

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

COMMAND ===>                                                    SCROLL===> CRSR

OPT  NAME -------- DESCRIPTION ------------------------------------------------

     IDJOB1        THIS JOB MUST BE RUN BEFORE IDJOB2

     IDJOB2

====== >>>>>>>>>>>>>>>>>>>    NO MORE JOBS IN TABLE     <<<<<<<<<<<<<<<< =====



































OPTIONS S SEL D DEL I INS O ORDER F FORCE J JCL C COPY P PLN T JOBSTAT 14.58.14

Notice the options at the bottom of the Job List screen. You will now use one of them, the O (Order) option, to order these two jobs.
Request option O (Order) in the OPT field for both IDJOB1 and IDJOB2.
If a confirm window is displayed, confirm the job order by entering Y in the CONFIRM field.
Figure 7 Confirm Window

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

COMMAND ===>                +-------------------------------+   SCROLL===> CRSR

OPT  NAME ---               |   CONFIRM Y   ODATE 020201    | -----------------

O   IDJOB1     <===========|   ASK FOR EACH ONE  Y         |

O   IDJOB2                 +-------------------------------+

====== >>>>>>>>>>>>>>>>>>>    NO MORE JOBS IN TABLE     <<<<<<<<<<<<<<<< =====

For each job ordered, the Job Order Messages screen with messages similar to the following will be displayed:

Figure 8 Job Order Messages Screen

------------------------ CONTROL-M JOB ORDER MESSAGES --------------------(2.O)

COMMAND ===>                                                    SCROLL===> CRSR

-------------------------------------------------------------------------------

19.40.14 JOB501I CTMJOB STARTED

19.40.16 JOB528I MEMBER IDJOB1   ID=0006I ODATE 020201 PLACED ON ACTIVE JOBS F

19.40.16 JOBD6BI NUMBER OF JOBS ORDERED -        1

19.40.16 JOB525I CTMJOB ENDED

======= >>>>>>>>>>>>>>>>>>    END OF MESSAGE LIST    <<<<<<<<<<<<<<<<<<< =====
Press PF03/PF15 or enter the END command to exit the Job Order Messages screen each time it is displayed.
The Job List screen is displayed.

You can now enter the Active Environment screen and check the results of the job orders. You do not have to return to the IOA Primary Option Menu to request Option 3, the Active Environment screen. Instead, by preceding an option with an equal sign (=), you can move directly there from where you are.
Enter =3 in the COMMAND field.
The Active Environment screen is displayed.

Parent Topic

Introduction to Control-M