Jobs Scheduling Definitions in the SMART Table

You should now exit the SMART Table Entity and create the job scheduling definitions in table IDGS2.

Exit the SMART Table Entity. Upon exiting the SMART Table Entity the first time, a blank Job Scheduling Definition screen is displayed.
As with all job scheduling definitions, JOB: is displayed  in the upper left corner. Notice, however, that the GROUP field already has a value, which is IDGRP4. The name specified in the GROUP field of the SMART Table Entity is not automatically assigned as the GROUP name of the jobs in the SMART Table. Only jobs whose GROUP name is blank are assigned the GROUP name from the SMART Table Entity.

JOB:          LIB CTM.TEST.SCHEDULE                             TABLE: IDGS2

COMMAND ===>                                                    SCROLL===> CRSR

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

  MEMNAME             MEMLIB

  OWNER   ID          TASKTYPE JOB    PREVENT-NCT2   DFLT  N

  APPL                                GROUP IDGRP4

  DESC

  OVERLIB                                                   STAT CAL

  SCHENV                         SYSTEM ID                  NJE NODE

  SET VAR

  CTB STEP AT         NAME            TYPE

  DOCMEM              DOCLIB

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

  SCHEDULE RBC

  RELATIONSHIP (AND/OR) O

  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 05  D-CAT

  MINIMUM          PDS

  DEFINITION ACTIVE FROM          UNTIL

COMMANDS: EDIT, DOC, PLAN, JOBSTAT, JVER                            07.38.42

Notice that job scheduling definitions in SMART Tables contain two Basic Scheduling parameter fields not found in tables with disabled SMART Table attributes: SCHEDULE RBC and RELATIONSHIP.

The SCHEDULE RBC field enables you to assign to the job scheduling definition any desired sets of basic scheduling criteria that you defined in the SMART Table Entity.
Specify IDJOB2 in the MEMNAME field and the name of the JCL library you are using in the MEMLIB field.
Specify JOB2 in the DESC field. Your entries in the General parameters section are displayed as follows:
+-----------------------------------------------------------------------------

  MEMNAME IDJOB2      MEMLIB   CTM.TEST.JCL

  OWNER   ID          TASKTYPE JOB    PREVENT-NCT2   DFLT  N

  APPL                                GROUP IDGRP4

  DESC    JOB2

  OVERLIB                                                   STAT CAL

  SCHENV                         SYSTEM ID                  NJE NODE

  SET VAR

  CTB STEP AT         NAME            TYPE

  DOCMEM  IDJOB2     DOCLIB

  ===========================================================================
Specify EOW in the SCHEDULE RBC field. A new SCHEDULE RBC field opens up.
Specify EOM in the new SCHEDULE RBC field, and then specify EXERCISES in the third SCHEDULE RBC field that opens up.
This job is now eligible for scheduling if either the EOW or EOM sets of basic scheduling criteria in the SMART Table Entity are satisfied. The EXERCISES criteria must also be satisfied to enable you to complete these instructions.

Your entries in the Basic Scheduling parameters section are displayed as follows:

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

  SCHEDULE RBC EOW

  SCHEDULE RBC EOM

  SCHEDULE RBC EXERCISES

  SCHEDULE RBC

  RELATIONSHIP (AND/OR) O

  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 05  D-CAT

  MINIMUM          PDS

  DEFINITION ACTIVE FROM          UNTIL

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

It is unnecessary to specify an IN condition for this job. Although IDJOB1 is a prerequisite to this job, you already defined IDJOB1-ENDED-OK as an IN condition for the entire table.

Therefore, the Runtime Scheduling parameter section should be empty, as shown in Figure 40.

Figure 40 Runtime Scheduling Parameter Section

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

  IN

  CONTROL

  RESOURCE

  PIPE

  FROM TIME         +     DAYS    UNTIL TIME      +     DAYS

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

The Post-processing section requires an OUT condition for this job because it is a prerequisite to IDJOB3. But you must decide whether to define Post-processing parameters in case the job ends NOTOK, that is, you need to decide whether the SMART Table Entity post-processing parameters are sufficient, or whether IDJOB2 requires its own additional post-processing definitions. For purposes of this exercise, assume that the SMART Table Entity Post-processing actions are sufficient.

Now you can define the Post-processing parameters.
In the OUT field, specify the condition IDJOB2-ENDED-OK   ODAT +. Your entries in the Post-processing parameters section are displayed as follows:
  ===========================================================================

  OUT      IDJOB2-ENDED-OK      ODAT +

  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 <<<<<<<<<<<<<<<< =====
Save this job scheduling definition and exit the job scheduling definition. The Job List screen is displayed.
JOB LIST     LIB: CTM.TEST.SCHEDULE                             TABLE: IDGS2

COMMAND ===>                                                    SCROLL===> CRSR

OPT  NAME ---  TYP --- DESCRIPTION -----  GROUP: IDGRP4               ---------

     IDGS2      T SMART TABLE ENTITY IN TABLE IDGS2

     IDJOB2     J  PRELIMINARY CALCULATIONS

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

Both the SMART Table Entity and the job scheduling definition that you created are listed in the Job List screen. Note the TYP field. This field identifies the type of entity listed. Valid values are: T, which identifies SMART Table Entity, and J, which identifies Job Scheduling Definition.

You can now create the remaining job scheduling definitions, beginning with IDJOB3.
Perform an Insert (Option I) next to IDJOB2. A job scheduling definition that contains many of the same values as found in IDJOB2 is displayed.
Specify IDJOB3 in the MEMNAME field (the MEMLIB field is already filled in).
Specify JOB3 in the DESC field. The Basic Scheduling parameters found in IDJOB2 appear in IDJOB3.
  ===========================================================================

  SCHEDULE RBC EOW

  SCHEDULE RBC EOM

  SCHEDULE RBC EXERCISES

  SCHEDULE RBC

  RELATIONSHIP (AND/OR) O

  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 05  D-CAT

  MINIMUM          PDS

  DEFINITION ACTIVE FROM          UNTIL

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

Recall that you want this job to be scheduled at end of week and end of month (just like IDJOB2), but only if those days do not fall on a Saturday or Sunday. Therefore, you will keep these Basic Scheduling parameter values, and specify several additional values as well.

Previously, you learned that the SCHEDULE RBC field is followed by a RELATIONSHIP field and a set of Basic Scheduling Criteria:
- The Basic Scheduling criteria allow you to define scheduling criteria apart from the criteria found in the Schedule RBCs.
- The RELATIONSHIP field determines the relationship between these criteria and the Schedule RBCs. Valid values are A (And) or O (Or):
  - The A value is more restrictive. In addition to the Schedule RBC criteria being satisfied, the basic scheduling criteria of the job, itself, must also be satisfied.
  - The O value is less restrictive. Even if the Schedule RBC criteria of the job are not satisfied, the job can be scheduled if its basic scheduling criteria are satisfied.
You should schedule job IDJOB3 only if the EOM, EOW (or EXERCISES) criteria are satisfied and the day is weekday (Monday through Friday).
Specify A (And) in the RELATIONSHIP field.
Specify 1,2,3,4,5 in the WDAYS field.
Note: You want this job to be scheduled on the day you perform this exercise. Adjust the WDAYS value so that it includes the day on which you are working.

Your entries in the Basic Scheduling parameters section are displayed as follows, except as adjusted to ensure that the WDAYS field contains your current working day:

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

  SCHEDULE RBC EOW

  SCHEDULE RBC EOM

  SCHEDULE RBC EXERCISES

  SCHEDULE RBC

  RELATIONSHIP (AND/OR) A

  DAYS                                                          DCAL

                                                                     AND/OR

  WDAYS   1,2,3,4,5                                             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 05  D-CAT

  MINIMUM          PDS

  DEFINITION ACTIVE FROM          UNTIL

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

There were no Runtime scheduling parameters specified in IDJOB2, so none appear in IDJOB3. But you must add the relevant condition to make this job dependent on IDJOB2.
Add the IN condition: IDJOB2-ENDED-OK ODAT. Your entry in the Runtime Scheduling parameters section is displayed as follows:
===========================================================================

IN       IDJOB2-ENDED-OK      ODAT

CONTROL

RESOURCE

PIPE

FROM TIME         +     DAYS    UNTIL TIME      +     DAYS

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

The Post-processing parameters contain the same OUT condition as IDJOB2. Normally, you would change the string JOB2 to JOB3 in the OUT condition to make the OUT condition correct. But for this exercise you will do something different.

In the exercises you have previously performed in this guide, you defined OUT conditions indicating that the job ended OK, even when that job is not a prerequisite to other jobs. This is good practice, but not a requirement. To demonstrate this, since no other job is dependent on this job, you should delete the condition.
Delete the OUT condition. The Post-processing parameter section will be empty, and the entire job scheduling definition is displayed as follows:
JOB: IDJOB3   LIB CTM.TEST.SCHEDULE                             TABLE: IDGS2

COMMAND ===>                                                    SCROLL===> CRSR

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

  MEMNAME IDJOB3      MEMLIB   CTM.TEST.JCL

  OWNER   ID          TASKTYPE JOB    PREVENT-NCT2   DFLT  N

  APPL                                GROUP IDGRP4

  DESC    JOB3

  OVERLIB                                                   STAT CAL

  SCHENV                         SYSTEM ID                  NJE NODE

  SET VAR

  CTB STEP AT         NAME            TYPE

  DOCMEM  IDJOB3      DOCLIB

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

  SCHEDULE RBC EOW

  SCHEDULE RBC EOM

  SCHEDULE RBC EXERCISES

  SCHEDULE RBC

  RELATIONSHIP (AND/OR) A

  DAYS                                                          DCAL

                                                                     AND/OR

  WDAYS   1,2,3,4,5                                             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 05  D-CAT

  MINIMUM          PDS

  DEFINITION ACTIVE FROM          UNTIL

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

  IN       IDJOB2-ENDED-OK      ODAT

  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                                    13.52.12
Exit the job scheduling definition. You can now create the job scheduling definition for IDJOB4.
Perform an INSERT (I) next to IDJOB3. A job scheduling definition similar to that belonging to IDJOB3 is displayed.
Specify IDJOB4 in the MEMNAME field.
Specify JOB4 in the DESC field. The Basic Scheduling parameters found in IDJOB3 appear in IDJOB4.
You can now make the necessary changes.
Specify O (Or) in the RELATIONSHIP field.
Delete the values in the WDAYS field.
Specify 08,14 and the current working day of the month in the DAYS field.
By defining the current working day in the DAYS field, you can see how the Or Relationship works.
Delete the EXERCISES value from the SCHEDULE RBC field.
If the day on which you perform these exercises satisfies the EOW or EOM criteria, delete the schedule RBCs of the satisfied criteria from the job scheduling definition.
The Basic scheduling criteria should only be satisfied by the DAYS parameter, not by any schedule RBCs in the job scheduling definition. If the Or relationship works as expected, the job will still be scheduled.

The IN condition from IDJOB3 now appears in IDJOB4. It should be deleted.
Delete the following IN condition: IDJOB2-ENDED-OK ODAT.
There was no OUT condition in IDJOB3, so none appears in IDJOB4. You should add the appropriate condition.
Add the following OUT condition: IDJOB4-ENDED-OK ODAT +. The job scheduling definition for IDJOB4 is displayed as shown in Figure 41.
Figure 41 Job Scheduling Definition for IDJOB4

JOB: IDJOB4   LIB CTM.TEST.SCHEDULE                             TABLE: IDGS2

COMMAND ===>                                                    SCROLL===> CRSR

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

  MEMNAME IDJOB4      MEMLIB   CTM.TEST.JCL

  OWNER   ID          TASKTYPE JOB    PREVENT-NCT2   DFLT  N

  APPL                                GROUP IDGRP4

  DESC    JOB4

  OVERLIB                                                   STAT CAL

  SCHENV                         SYSTEM ID                  NJE NODE

  SET VAR

  CTB STEP AT         NAME            TYPE

  DOCMEM  IDJOB4      DOCLIB

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

  SCHEDULE RBC EOW

  SCHEDULE RBC EOM

  SCHEDULE RBC

  RELATIONSHIP (AND/OR) O

  DAYS    02,08,14                                              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 05  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      IDJOB4-ENDED-OK      ODAT +

  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                                    15.01.32
Exit the job scheduling definition.
You can now create the job scheduling definition for IDJOB5.
Perform an INSERT (I) next to IDJOB4. A job scheduling definition similar to that belonging to IDJOB4 is displayed.
Specify IDJOB5 in the MEMNAME field.
Specify JOB5 in the DESC field. The Basic Scheduling parameters found in IDJOB4 appear in IDJOB5.
You can now make the necessary changes.
Replace all deleted schedule RBCs so that the job scheduling definition contains schedule RBCs EOW, EOM, and EXERCISES.
Delete the values specified for the DAYS parameter.
The job should only be scheduled according to the specified schedule RBCs. You should make this job dependent on successful completion of IDJOB4.
Add the following IN condition: IDJOB4-ENDED-OK ODAT.
In the OUT condition, change the string JOB4 to JOB5. The job scheduling definition is displayed as follows:
JOB: IDJOB5   LIB CTM.TEST.SCHEDULE                             TABLE: IDGS2

COMMAND ===>                                                    SCROLL===> CRSR

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

  MEMNAME IDJOB5      MEMLIB   CTM.TEST.JCL

  OWNER   ID          TASKTYPE JOB    PREVENT-NCT2   DFLT  N

  APPL                                GROUP IDGRP4

  DESC    JOB5

  OVERLIB                                                   STAT CAL

  SCHENV                         SYSTEM ID                  NJE NODE

  SET VAR

  CTB STEP AT         NAME            TYPE

  DOCMEM  IDJOB5      DOCLIB

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

  SCHEDULE RBC EOW

  SCHEDULE RBC EOM

  SCHEDULE RBC EXERCISES

  SCHEDULE RBC

  RELATIONSHIP (AND/OR)

  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 05  D-CAT

  MINIMUM          PDS

  DEFINITION ACTIVE FROM          UNTIL

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

  IN       IDJOB4-ENDED-OK      ODAT

  CONTROL

  RESOURCE

  PIPE

  FROM TIME         +     DAYS    UNTIL TIME      +     DAYS

  DUE OUT TIME      +     DAYS    PRIORITY     SAC    CONFIRM

  TIME ZONE:

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

  OUT      IDJOB5-ENDED-OK      ODAT +

  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                                    15.18.22
Exit the job scheduling definition. The Job List screen is displayed as shown in Figure 42.
Figure 42 Job List Screen for a SMART Table Entity

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

COMMAND ===>                                                    SCROLL===> CRSR

OPT  NAME ---  TYP --- DESCRIPTION -----  GROUP: IDGRP4               ---------

     IDGS2      T SMART TABLE ENTITY IN TABLE IDGS2

     IDJOB2     J  JOB2

     IDJOB3     J  JOB3

     IDJOB4     J  JOB4

     IDJOB5     J  JOB5

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

Parent Topic

Creating a SMART Table