SMART Table Scheduling
This chapter includes the following topics:
OverviewLink copied to clipboard
When defining job scheduling definitions, it is good practice to group together related job scheduling definitions. This is not a requirement—related jobs can belong to different groups, or not belong to any group—but it can be useful. For example, if related jobs belong to the same group, you can use the group name to filter the Active Environment screen so that only the jobs in that group are displayed. But greater functionality than just ease of filtering a display can be provided by assigning a set of jobs to a SMART Table.
The major advantage of defining SMART Tables is that they enable you to define basic scheduling criteria, runtime scheduling criteria and post processing criteria that apply to the jobs in the SMART Table as a whole.
PreparationsLink copied to clipboard
In the exercises in the previous chapters of this guide, you created the JCL for five jobs, IDJOB1 through IDJOB5. To simplify preparation for this chapter, you will utilize all five of these JCLs.
In addition, you will utilize one of the job scheduling definitions that you created in Chapter 1, "Introduction to Control-M" the job scheduling definition for IDJOB1, in table IDGS1. For the remaining jobs, you will creates new job scheduling definitions in a new table (IDGS2), as part of the exercises.
Before continuing with the exercises, you should perform the following preparatory steps:
-
In the JCL of IDJOB5, change the JCL of step S5 so that it sets a return code of C0008 instead of C0000.
-
Ensure the following, which should be the case if you completed all of the steps in the previous chapters of this guide:
-
The JCL for step S1 in IDJOB3 sets a return code of C0000, and not C0008.
-
All conditions from previous exercises in this guide do not appear in, or are deleted from, the IOA Conditions/Resources screen.
-
All job orders from previous exercises in this guide do not appear in, or are deleted from, the Active Environment screen.
-
You are now ready to look at SMART Table scheduling. For purposes of these exercises, you should assume that the new table contains jobs that must run at end of week and at end of month.
Creating a SMART TableLink copied to clipboard
-
Enter the IOA Online Facility and display the Scheduling Definition Facility entry panel.
CopyCopied to clipboard----------- CONTROL-M SCHEDULING DEFINITION FACILITY - ENTRY PANEL ---------(2)
COMMAND ===>
SPECIFY LIBRARY, TABLE, JOB
LIBRARY ===> CTM.TEST.SCHEDULE
TABLE ===> (Blank for table selection list)
JOB ===> (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
In this chapter, you will create a new table called IDGS2; in the previous chapters of this guide you used a table called IDGS1.
Notice the field SMART TABLE. Valid values for this field are Y (SMART Table) or [Enter] (Table that handles jobs individually). In previous chapters of this guide, you ignored this field because the default value [Enter] served your purpose when you worked with table IDGS1. Now, however, you want to define the new table, IDGS2, to be a SMART Table.
A SMART Table contains a mechanism for defining parameters that apply to the table as a whole.
In the previous chapters, whenever you defined a job scheduling definition in table IDGS1, the parameters in the job scheduling definition could only be applied to that job. For example, a TIME FROM value, or a DO SHOUT value, in the job scheduling definition for IDJOB3, applied only to IDJOB3. If you wanted to apply the same parameters to IDJOB4, you had to define the parameters in the job scheduling definition of IDJBO4.
SMART Tables have a special kind of scheduling definition, called a SMART Table Entity, that is used to apply parameters to all jobs in the table. Each SMART Table has one, and only one, SMART Table Entity, as well as its job scheduling definitions. When you first request creation of a SMART Table from the Scheduling Definition entry panel, the SMART Table entity definition screen is displayed.
SMART Table EntityLink copied to clipboard
You can now request creation of SMART Table IDGS2, and take a look at the SMART Table Entity.
-
In the Entry Panel, enter IDGS2 in the TABLE field and Y in the SMART TABLE field.
Once you specify a SMART Table name in the TABLE field, you will not be able to change the name from the SMART Table Entity Scheduling Definition panel.
CopyCopied to clipboardSPECIFY LIBRARY, TABLE, JOB
LIBRARY ===> CTM.TEST.SCHEDULE
TABLE ===> IDGS2 (Blank for table selection list)
JOB ===> (Blank for job selection list)
SMART TABLE ===> Y ( Y - for new SMART Table )
The SMART Table Entity scheduling definition is displayed.
Figure 37 SMART Table Entity Scheduling Definition
TBL CTM.TEST.SCHEDULE(IDGS2)
COMMAND ===> SCROLL===> CRSR
+-----------------------------------------------------------------------------+
TABLE IDGS2 GROUP
OWNER ID
APPL
DESC
ADJUST CONDITIONS N TBL MAXWAIT 05
SET VAR
DOCMEM IDGS2 DOCLIB
===========================================================================
SCHEDULE RBC
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
SCHEDULE RBC ACTIVE FROM UNTIL
===========================================================================
IN
CONTROL
===========================================================================
COMMANDS: EDIT, DOC, PLAN, JOBSTAT 11.51.58
Although the SMART Table Entity scheduling definition is similar to the job scheduling definition, there are differences. The first thing to note is that the term TBL in the upper left corner identifies the definition as a SMART Table Entity.
The next thing to note is that the first field in the definition, under the COMMAND line, is the TABLE field, followed by the GROUP field on the same line. Note also that there is no MEMLIB field.
In a regular job scheduling definition, the MEMNAME parameter contains the name of the JCL member of the job. However, a SMART Table Entity does not have a JCL member.
By default, the name you specified in the TABLE field automatically gets placed in the DOCMEM field.
-
In the GROUP field, specify the name IDGRP4, which is the name of our group.
-
In the DESC field, specify SMART TABLE ENTITY FOR TABLE IDGS2. The entries in the General parameters section appear as shown below:
CopyCopied to clipboard+----------------------------------------------------------------------------+
TABLE IDGS2 GROUP IDGRP4
OWNER ID
APPL
DESC SMART TABLE ENTITY FOR TABLE IDGS2
ADJUST CONDITIONS N TBL MAXWAIT 05
SET VAR
DOCMEM IDGS2 DOCLIB
===========================================================================
Schedule RBCs and Other Basic Scheduling ParametersLink copied to clipboard
You can now look at the Basic Scheduling parameters section. The first field to note is the SCHEDULE RBC field. This field only appears in definitions in SMART Tables.
-
In the SCHEDULE RBC field, specify the name EOW, which stands for END-OF-WEEK. In the LEVEL field, specify either TBL or CTM. (If the Schedule RBC’s level is set to TBL, the rule-based calendar is defined in the SMART Table Entity. If the Schedule RBC’s level is set to CTM, the rule-based calendar is defined in the IOA Calendar Facility.) In the WDAYS field, specify the value 0, which means the last day of the week.
CopyCopied to clipboard===========================================================================
SCHEDULE RBC EOW LEVEL TBL
DAYS DCAL
AND/OR
WDAYS 0 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
SCHEDULE RBC ACTIVE FROM UNTIL
===========================================================================
SCHEDULE RBC LEVEL
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
SCHEDULE RBC ACTIVE FROM UNTIL
===========================================================================Notice that a new, blank set of Basic Scheduling criteria opens up.
Thus far, in each of your job scheduling definitions, you have been limited to defining only one set of Basic scheduling parameters. This is because a job scheduling definition can have only one occurrence of the Basic Scheduling parameter section.
SMART TABLE Entities, on the other hand, can have multiple occurrences of the Basic scheduling parameters section. Once you have defined a set of Basic Scheduling parameters, a new, blank section of Basic Scheduling parameters opens to enable you to define another set.
You distinguish between the sets of Basic Scheduling parameters in the SMART TABLE Entity by assigning a name to each set in the SCHEDULE RBC field.
In In the exercises in the previous chapters of this guide, you created the JCL for five jobs, IDJOB1 through IDJOB5. To simplify preparation for this chapter, you will utilize all five of these JCLs.
In addition, you will utilize one of the job scheduling definitions that you created in Chapter1, "Introduction to Control-M," the job scheduling definition for IDJOB1, in table IDGS1. For the remaining jobs, you will creates new job scheduling definitions in a new table (IDGS2), as part of the exercises.
Before continuing with the exercises, you should perform the following preparatory steps:
-
In the JCL of IDJOB5, change the JCL of step S5 so that it sets a return code of C0008 instead of C0000.
-
Ensure the following, which should be the case if you completed all of the steps in the previous chapters of this guide:
-
The JCL for step S1 in IDJOB3 sets a return code of C0000, and not C0008.
-
All conditions from previous exercises in this guide do not appear in, or are deleted from, the IOA Conditions/Resources screen.
-
All job orders from previous exercises in this guide do not appear in, or are deleted from, the Active Environment screen.
-
You are now ready to look at SMART Table scheduling. For purposes of these exercises, you should assume that the new table contains jobs that must run at end of week and at end of month.the "Preparations" section above, you determined that the jobs in this table will run at the end of the week and at the end of the month. You have just defined the basic scheduling criteria for the end of the week run. You can now define the basic scheduling criteria for the end of the month run.
-
-
In the empty SCHEDULE RBC field, specify the name EOM, which stands for END-OF-MONTH. In the LEVEL field, specify either TBL or CTM. In the DAYS field, specify the value L1, which means the last day of the month.
In an actual operational environment, these sets of Basic Scheduling criteria would be enough to achieve your goals. However, because you want to be able to perform these exercises on any day of the month, you will define one more set of Basic scheduling criteria for purposes of this guide only.
-
In the blank SCHEDULE RBC field, specify the name EXERCISES. In the LEVEL field, specify either TBL or CTM. In the DAYS field, specify the value ALL.
Your entries in the Basic Scheduling parameter section are displayed as shown in Figure38.
Figure 38 Basic Scheduling Parameter Section
CopyCopied to clipboard===========================================================================
SCHEDULE RBC EOW LEVEL TBL
DAYS DCAL
AND/OR
WDAYS 0 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
SCHEDULE RBC ACTIVE FROM UNTIL
===========================================================================
SCHEDULE RBC EOM LEVEL TBL
DAYS L1 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
SCHEDULE RBC ACTIVE FROM UNTIL
===========================================================================
SCHEDULE RBC EXERCISES LEVEL TBL
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 05
SCHEDULE RBC ACTIVE FROM UNTIL
===========================================================================
SCHEDULE RBC LEVEL
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
SCHEDULE RBC ACTIVE FROM UNTIL
===========================================================================
Runtime Scheduling ParametersLink copied to clipboard
All Runtime Scheduling fields found in the SMART TABLE Entity are also found in the job scheduling definition.
In Preparations, you determined that you would continue to use the job scheduling definition of IDJOB1 in table IDGS1.
Assume that job IDJOB1, in table IDGS1, must end OK before any of the jobs in table IDGS2 can run. You will now add the condition necessary to establish this job dependency.
-
In the IN field, specify the condition IDJOB1-ENDED-OK ODAT. Your entry in the Runtime Scheduling parameter section is displayed.
CopyCopied to clipboard===========================================================================
IN IDJOB1-ENDED-OK ODAT
CONTROL
FROM TIME + DAYS UNTIL TIME + DAYS
===========================================================================
On Table End and Other Post-Processing ParametersLink copied to clipboard
Like the job scheduling definition, the SMART Table Entity contains OUT and SHOUT WHEN statements, and DO blocks. However, instead of regular ON blocks, the SMART Table Entity contains ON TABLE-END blocks.
Unlike the ON block, which applies to the individual job, the ON TABLE-END block applies to the jobs in the SMART Table as a whole. Valid values for the ON TABLE-END field are as follows:
Table 10 Valid Values For the ON TABLE-END Statement
|
Value |
Description |
|---|---|
|
OK |
Subsequent DO actions are performed for each job in the SMART Table only if the end status of the SMART Table Entity is OK, that is, all scheduled jobs in the SMART Table ended OK. |
|
NOTOK |
Subsequent DO actions are performed for each job in the SMART Table if the end status of the SMART Table Entity is NOTOK, that is, at least one job in the SMART Table ended NOTOK. |
Not all DO statements that are valid in the job scheduling definition are valid in the SMART Table Entity. The DO statements listed below can be specified in the SMART Table Entity. Several of these DO statements have not been described in this guide, but they are all described in the Control-M for z/OS User Guide:
-
DO COND
-
DO OK
-
DO MAIL
-
DO FORCEJOB
-
DO SET
-
DO NOTOK
-
DO SHOUT
You can now fill in the Post-processing parameters of the SMART Table Entity.
-
In the OUT field, specify the condition IDGS2-ENDED-OK ODAT +.
-
In the ONTABLE-END field, specify the value OK.
-
In the accompanying DO field, specify SHOUT, and enter the following message in the DO SHOUT statement :
PROCESSING OF TABLE IDGS2 ENDED OK.
-
In the blank ONTABLE-END field, specify the value NOTOK.
-
In the accompanying DO field, specify COND, and fill in the DO COND statement with the following: IDGS2-END-NOTOK ODAT +.
-
In the next DO field, specify SHOUT, and enter the following message in the DO SHOUT statement:
PROBLEM WITH TABLE PROCESSING. AT LEAST ONE JOB DID NOT END OK.
Your entries in the Post-processing parameter section are displayed as shown in Figure 39.
Figure 39 Post-Processing Parameter Section
CopyCopied to clipboard+-----------------------------------------------------------------------------+
OUT IDGS2-ENDED-OK ODAT +
ON TABLE-END OK
DO SHOUT TO TSO-M21 URGENCY R
= PROCESSING OF TABLE IDGS2 ENDED OK
DO
ON TABLE-END NOTOK
DO COND IDGS2-END-NOTOK ODAT +
DO SHOUT TO TSO-M21 URGENCY R
= PROBLEM WITH TABLE PROCESSING. AT LEAST ONE JOB DID NOT END OK
DO
ON TABLE-END
DO
SHOUT WHEN TIME + DAYS TO URGN
MS
======= >>>>>>>>>>>>>>>>>>>>> END OF TABLE PARAMETERS <<<<<<<<<<<<<<<<<< ======
Logic of the SMART Table Entity Scheduling DefinitionLink copied to clipboard
The following points about the logic of your SMART Table Entity should be noted:
-
The SMART Table Entity is used to help determine and control the processing of the jobs in the table.
-
You defined the following three sets of Basic Scheduling Criteria:
-
EOW criteria result in jobs being scheduled on the last day of the of week.
-
EOM criteria result in jobs being scheduled on the last day of the month.
-
EXERCISES criteria result in jobs being scheduled every day, for purposes of the exercises in this guide.
You will soon see how these sets of scheduling criteria apply to the job scheduling definitions in this table.
-
-
You defined an IN condition: IDJOB1-ENDED-OK. This condition is set when job IDJOB1 in table IDGS1 ends successfully. This means that successful completion of IDJOB1 is a prerequisite to the submission of the jobs in table IDGS2 that are scheduled according to Basic scheduling criteria in the SMART Table Entity.
-
You defined an OUT condition that is set only when all scheduled jobs in table IDGS2 end OK. This condition can be used as an IN condition to some other job that requires successful completion of the jobs in table IDGS2 as a prerequisite.
-
You defined two sets of ON TABLE-END/DO parameters:
-
The first set applies if all the scheduled jobs in the table end OK. It shouts a message to that effect,
-
The second set applies if any of the scheduled jobs in the table ends NOTOK. It shouts a message to that effect; and it sets an appropriate condition that can, for example, be used to run an auxiliary job.
-
You are about to exit the SMART Table Entity and create the job scheduling definitions in table IDGS2. However, before doing so, outline the logic you would like to see in the job scheduling definitions.
Planned Logic of the Job Scheduling DefinitionsLink copied to clipboard
As mentioned above, you want successful completion of job IDJOB1 to be a prerequisite to the running of the jobs in table IDGS2. In addition to this, the following logic should apply:
-
Table IDGS2 will contain jobs IDJOB2, IDJOB3, IDJOB4, and IDJOB5.
-
IDJOB2 is a prerequisite to IDJOB3, and IDJOB4 is a prerequisite to IDJOB5. However, IDJOB3 is NOT a prerequisite to IDJOB4.
-
IDJOB2 should be run both at end of week and end of month, and during the exercise.
-
IDJOB3 should be run following IDJOB2, at end of week or month, and during the exercise, provided that the day is a weekday, that is, on Monday, Tuesday, Wednesday, Thursday, or Friday.
-
IDJOB4 should be run both at end of week and at end of month, but should also run on several other days of the month: the 8th, the 14th, and, so the exercise will work, the day that you perform this exercise.
-
IDJOB5 should run following IDJOB4, but only at end of week and end of month, and during the exercise. It should not run the other days specified.
Jobs Scheduling Definitions in the SMART TableLink copied to clipboard
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.
CopyCopied to clipboardJOB: 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 07.38.42Notice 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:
CopyCopied to clipboard+-----------------------------------------------------------------------------
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:
CopyCopied to clipboard===========================================================================
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 Figure40.
Figure 40 Runtime Scheduling Parameter Section
CopyCopied to clipboard===========================================================================
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:
CopyCopied to clipboard===========================================================================
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.
CopyCopied to clipboardJOB 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.
CopyCopied to clipboard===========================================================================
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.
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:
CopyCopied to clipboard===========================================================================
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:
CopyCopied to clipboard===========================================================================
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:
CopyCopied to clipboardJOB: 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 Figure41.
Figure 41 Job Scheduling Definition for IDJOB4
CopyCopied to clipboardJOB: 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:
CopyCopied to clipboardJOB: 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 Figure42.
Figure 42 Job List Screen for a SMART Table Entity
CopyCopied to clipboardJOB 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 <<<<<<<<<<<<<<<< =====
Saving the TableLink copied to clipboard
-
Exit the Job List screen. The Exit Option window is displayed.
-
Specify Y in the SAVE field to save table IDGS2. The table is saved, and the entry panel is displayed. (The first time, you must create the Smart table before saving it, by specifying Y in CREATE field.)
Points to Remember Concerning SMART Table SchedulingLink copied to clipboard
Before ordering the SMART Table Entity and its jobs, note the following points about SMART Table scheduling:
-
Only the SMART Table Entity can be ordered. Individual jobs in the SMART Table cannot be ordered, although they can be forced.
-
When a SMART Table Entity is ordered, its schedule RBCs are checked to see if the SMART Table Entity is eligible for scheduling. If none of the sets of scheduling criteria for the SMART Table Entity is satisfied, neither the SMART Table Entity, nor any of its jobs, are ordered. In this case, even if the basic scheduling criteria of the job itself are satisfied, and an OR relationship is defined, the job is not scheduled.
-
If at least one set of scheduling criteria is satisfied, each job is checked to see if it can be scheduled according to the combination of its schedule RBCs, basic scheduling criteria, and the defined AND/OR relationship.
SMART Table Entity Ordering and Job OrderingLink copied to clipboard
You can now order the SMART Table Entity and all of the jobs in table IDGS2. Remember that these jobs are dependent on successful completion of IDJOB1 in table IDGS1, but you will not immediately order that job.
-
Reenter table IDGS2.
-
Enter the ORDER option by the SMART Table Entity only. The SMART Table Entity and all its jobs are ordered.
When a SMART Table Entity is ordered, all the jobs in the SMART Table that should be scheduled that day are automatically ordered as well. Because all the jobs have the Schedule RBC EXERCISES, they were all ordered.
-
Enter the Active Environment screen and filter the display using the IDGS filter. The screen is displayed as follows:
Notice that the SMART Table Entity, and all its jobs, have a status of Wait Schedule.
CopyCopied to clipboardFilter: IDGS ------- Control-M Active Environment ------ UP <D> - (3)
COMMAND ===> SCROLL ==> CRSR
O Name Owner Odate Jobname JobID Typ ----------- Status ------------
IDGS2 ID 020201 TBL Wait Schedule
IDJOB2 ID 020201 JOB Wait Schedule
IDJOB3 ID 020201 JOB Wait Schedule
IDJOB4 ID 020201 JOB Wait Schedule
IDJOB5 ID 020201 JOB Wait Schedule
========= >>>>>>>>>>>>> Bottom of Jobs List <<<<<<<<<<<<< ========
-
Request the Why screen, Option ?, for the SMART Table Entity.
CopyCopied to clipboard------------------------ IDGS2 SCHEDULING ANALYSIS --------------------(3.?)
COMMAND ===> SCROLL===> CRSR
OPT DESCRIPTION
CONDITION JOB1-ENDED-OK ODATE 0202
====== >>>>>>>>>>>>>>>>>>>>> END OF "WHY" LIST <<<<<<<<<<<<<<<<<<<<< =====As predicted, the job is waiting for condition IDJOB1-ENDED-OK. You should now order IDJOB1.
-
Display the Job List screen for table IDGS1 and job order IDJOB1.
-
Return to Active Environment screen. Job IDJOB1 is scheduled and awaiting confirmation.
-
Confirm IDJOB1 and then watch the impact on the SMART Table Entity and jobs in table IDGS2.
Job IDJOB1 changes to a status of Wait Submission, then is submitted, then executed, and finally, it ends OK. At that point, the status of the SMART Table Entity changes to Active, and the status of jobs IDJOB2 and IDJOB4 changes to Wait Submission.
CopyCopied to clipboardFilter: IDGS ------- Control-M Active Environment ------ UP <D> - (3)
COMMAND ===> SCROLL ==> CRSR
O Name Owner Odate Jobname JobID Typ ----------- Status ------------
IDGS2 ID 020201 TBL Active
IDJOB2 ID 020201 JOB Wait Submission
IDJOB3 ID 020201 JOB Wait Schedule
IDJOB4 ID 020201 JOB Wait Submission
IDJOB5 ID 020201 JOB Wait Schedule
IDJOB1 ID 020201 COURSE7A/14348 JOB Ended "OK"
========= >>>>>>>>>>>>> Bottom of Jobs List <<<<<<<<<<<<< ========From that point on, the processing continues. Once job IDJOB2 ends OK, job IDJOB3 is submitted; once IDJOB4 ends OK, job IDJOB5 is submitted.
Job IDJOB3 ends OK, but IDJOB5 does not, due to the condition code C0008. Because at least one of the jobs in the SMART Tables—IDJOB5—ended NOTOK, the SMART Table Entity ends NOTOK. At the end of processing, the status of the jobs appears as follows:
CopyCopied to clipboardFilter: IDGS ------- Control-M Active Environment ------ UP <D> - (3)
COMMAND ===> SCROLL ==> CRSR
O Name Owner Odate Jobname JobID Typ ----------- Status ------------
IDGS2 ID 020201 TBL Ended- Not "OK"
IDJOB2 ID 020201 M21 /14373 JOB Ended "OK"
IDJOB3 ID 020201 M21 /14375 JOB Ended "OK"
IDJOB4 ID 020201 M21 /14374 JOB Ended "OK"
IDJOB5 ID 020201 M21 /14376 JOB Ended- Not "OK" Due to CC
IDJOB1 ID 020201 COURSE7A/14372 JOB Ended "OK"
========= >>>>>>>>>>>>> Bottom of Jobs List <<<<<<<<<<<<< ========You can go back and correct the JCL for IDJOB5, and then rerun the job.
-
Edit the JCL for IDJOB5, which you can do using the JCL option in the current screen, and change the output condition code in step S5 from C0008 to C0000. Then exit back to the Active Environment screen
In the previous chapter, you learned about reruns in context of restarts, but it is also possible to rerun a failed job from the beginning. Do this for IDJOB5.
-
Enter option R (Rerun) for job IDJOB5. The Rerun/Restart window is displayed. In this case, the With Restart value is N (No restart).
CopyCopied to clipboardFilter: IDGS ------- Control-M Active Environment ------ UP <D> - (3)
COMMAND ===> SCROLL ==> CRSR
O Name Owner Odate Jobname JobID Typ ----------- Status ------------
IDGS2 ID 020201 TBL Ended- Not "OK"
IDJOB2 ID 020201 +---------------------------------(3.R)+
IDJOB3 ID 020201 | Job IDJOB5 Is to be Rerun |
IDJOB4 ID 020201 | Please Confirm Y (Y/N) |
R IDJOB5 ID 020201 | With Restart N (?/Y/N) |o CC
IDJOB1 ID 020201 | ---------------------------------- |
========= >>>>>>>>>>>>> | From Step/Proc . | < ========
| To Step/Proc . |
| Recapture Abend Codes (Y/N) |
| Recapture Cond Codes (Y/N) |
| Step Adjustment (Y/N) |
| Restart Parm Member Name IDJOB5 |
+--------------------------------------+
-
Enter Y (Yes) in the Confirm field of the window. The job is rerun.
Go into the IOA Conditions/Resources screen and see the results of these job runs.
The second run of the job ends OK, and so does the SMART Table Entity. The Active Environment screen is displayed as follows:
CopyCopied to clipboardFilter: IDGS ------- Control-M Active Environment ------ UP <D> - (3)
COMMAND ===> SCROLL ==> CRSR
O Name Owner Odate Jobname JobID Typ ----------- Status ------------
IDGS2 ID 020201 TBL Ended "OK"
IDJOB2 ID 020201 M21 /14373 JOB Ended "OK"
IDJOB3 ID 020201 M21 /14375 JOB Ended "OK"
IDJOB4 ID 020201 M21 /14374 JOB Ended "OK"
IDJOB5 ID 020201 M21 /14393 JOB Ended "OK" (Run 2)
Prior Run: Ended- Not "OK" Due
to CC
IDJOB1 ID 020201 COURSE7A/14372 JOB Ended "OK"
========= >>>>>>>>>>>>> Bottom of Jobs List <<<<<<<<<<<<< ======== -
Go to the IOA Conditions/Resources screen, Screen 4. Specify your ID as a prefix to filter the display. Remember to ensure that the current date appears in the DATE UNTIL field under the Scroll amount.
CopyCopied to clipboard-------------------------- IOA CONDITIONS/RESOURCES ------------------------(4)
COMMAND ===> SCROLL ===> CRSR
PREFIX ===> ID COND Y CONTROL Y RES Y STAT Y DATE 0202 - 0202
OPT TYPE CONDITION/RESOURCE IOAID USE QUANTITY MAX *P RBA DATE
COND IDJOB1-ENDED-OK 0202
COND IDJOB2-ENDED-OK 0202
COND IDJOB4-ENDED-OK 0202
COND IDGS2-END-NOTOK 0202
COND IDJOB5-ENDED-OK 0202
COND IDGS2-ENDED-OK 0202
======== >>>>>>>>>>>>>>>> B O T T O M O F L I S T <<<<<<<<<<<<<<<< ========Notice the following:
-
The conditions follow the order in which they were issued:
-
There is an ENDED-OK condition for jobs IDJOB1, IDJOB2, and IDJOB4. (IDJOB3 did not have an OUT condition).
-
There is an END-NOTOK condition for SMART Table IDGS2 because of the CC problem in IDJOB5. There is no such condition for IDJOB5 because you did not define it.
-
This is followed by the ENDED-OK for IDJOB5, after the rerun, and finally, the ENDED-OK status is displayed for the SMART Table IDGS2.
-
-
Advantages of SMART Table SchedulingLink copied to clipboard
SMART Table scheduling is not always desired. But in those situations in which SMART Table scheduling is desirable, use of a SMART Table simplifies the process and provides several advantages. Some of these are discussed below:
-
Schedule RBCs simplify basic scheduling.
Once a set of basic scheduling parameters is defined in the SMART Table Entity, all jobs that require that set of scheduling parameters can utilize them simply by specifying the schedule RBC name in the appropriate field. The more complex and detailed the scheduling parameters, the greater the advantage.
-
Multiple sets of scheduling criteria can be specified for each job.
Regular job scheduling definitions provide for one set of scheduling criteria. However, in a SMART Table, the SMART Table Entity can include multiple sets of scheduling criteria, and any number of these can be specified in any job scheduling definition in the SMART Table. This enables the job to utilize multiple sets of basic scheduling criteria.
-
Easier definition of prerequisite conditions and required resources is enabled for each job.
Defining an IN condition in a SMART Table Entity makes all jobs in that table dependent on that condition without defining the IN condition in all the individual job scheduling definitions. The more jobs in the SMART Table that have no predecessor job other than the predecessor of the SMART Table Entity, the greater this advantage.
-
Easier Post-processing definition is enabled for each job.
If you want to define Post-processing that should be performed only if any of the jobs ended NOTOK, it is much easier to define the conditional Post-processing once in the SMART Table Entity, rather than repeatedly in each job scheduling definition.
If you want to define Post-processing that should be defined if all the jobs ended OK, this is also easier to do in SMART Tables if there are jobs not belonging to the same hierarchy of dependence.
-
Easier triggering of jobs in a different table is facilitated.
If the submission of a job in another table depends on the outcome of all the jobs in the current table, this is easier to define in a SMART Table.
-
Exit the Online facility.
This completes the steps in this chapter of the Control-M for z/OS Getting Started Guide.
ReviewLink copied to clipboard
In this chapter you
-
created a SMART Table
-
defined a SMART Table Entity with multiple sets of scheduling criteria and with a dependency on successful completion of a job from another table
-
used Schedule RBCs to appropriately (according to job) assign sets of scheduling criteria to each job
-
defined additional criteria for two of the jobs in the SMART Table—using an AND relationship with the additional criteria in one of the jobs, and using an OR relationship in the other job
-
defined two separate lines of dependency in the jobs in the SMART Table—IDJOB3 dependent on IDJOB2, and IDJOB5 dependent on IDJOB4—but no dependency between IDJOB3 and IDJOB4
-
ordered the SMART Table Entity with the result that all jobs in the table that should have been scheduled that day were also ordered
-
observed that the SMART Table Entity ended NOTOK when one of the jobs in the SMART Table ended NOTOK
-
learned the advantages of using a SMART Table over a table that handles jobs individually
Recommended ReadingLink copied to clipboard
Before continuing with the next chapter, you should read the following in the Control-M for z/OS User Guide:
-
In Chapter 2
-
information in the Scheduling Definition facility topics relating to SMART Tables and SMART Table scheduling
-
status changes of the Active Environment screen related to SMART Table scheduling and job scheduling definitions in SMART Tables
-
reasons in the Why screen related to SMART Table jobs and SMART Table Entities
-
the SMART Table Entity in the Zoom screen
-
-
In Chapter 3
-
summary information related to SMART Table scheduling
-
detailed parameter descriptions of the following SMART Table scheduling parameters
-
ADJUST CONDITIONS
-
ON TABLE-END
-
RELATIONSHIP
-
SCHEDULE RBCS
-
-
information that relates to SMART Table scheduling in the following parameters
-
DO statements
-
MEMNAME
-
ON
-
-
Communities
Support Center
YouTube
Twitter
Facebook
LinkedIn