Editing Job Scheduling Definitions in the Edit Environment
This appendix discusses the following:
Job scheduling definition parameters can be edited, moved, copied, deleted, or repeated, by performing IOA Line Editing commands, similar to standard ISPF line commands, from within the Edit environment.
The Edit environment in the Job Scheduling Definition screen is accessed by typing EDIT in the COMMAND field and pressing Enter.
Figure 392 The Edit Environment in The Job Scheduling Definition Screen
JOB: BACKP02 LIB CTM.PROD.SCHEDULE TABLE: BACKUP
COMMAND ===> SCROLL===> CRSR
+---------------------------------------------------------------------+
__ MEMNAME BACKP02 MEMLIB CTM.PROD.JOBLIB
__ OWNER M44 TASKTYPE JOB PREVENT-NCT2 Y DFLT N
__ APPL APPL-L GROUP BKP-PROD-L
__ DESC DAILY BACKUP OF SPECIAL FILES FROM APPL-L
__ OVERLIB CTM.OVER.JOBLIB STAT CAL
__ SCHENV SYSTEM ID NJE NODE
__ SET VAR
__ CTB STEP AT NAME TYPE
__ DOCMEM BACKP02 DOCLIB CTM.PROD.DOC
__ ====================================================================
__ 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 WORKDAYS SHIFT RETRO N MAXWAIT 00 D-CAT
__ MINIMUM PDS
__ DEFINITION ACTIVE FROM UNTIL
__ ====================================================================
__ IN START-DAILY-BACKUP ODAT
COMMANDS: EDIT, DOC, PLAN, JOBSTAT 16.44.31A 2-character Line Editing command field, marked by underscores, is displayed for each line on the screen.
Editing commands are typed directly onto these underscores.
Note: Edit commands cannot be applied to the first line of an IN block or an OUT block.
Incorrectly specified Line Editing commands can be corrected by typing over them correctly. Line Editing commands can be deleted by blanking them out or by specifying the RESET command in the COMMAND field.
The Line Editing commands you enter are processed when Enter is pressed.
All operations available in the Job Scheduling Definition screen can be performed while in the Edit environment. For example, parameter values can be changed, and the job scheduling definition can be saved and exited.
To exit the Edit environment, retype EDIT in the COMMAND field and press Enter. Line Editing command fields are removed from the display.
Line Editing commands can be performed on the following:
Table 304 Subjects of Line Editing Commands
|
Subject |
Description |
|---|---|
|
Single Lines |
One single line on the screen.
|
|
Logical Lines |
All parameter lines for a specific parameter, including its subparameters.
|
|
Logical Blocks |
Functional group of parameter lines. Job scheduling definitions consist of at least one logical block – an ON block. ON block, which consists of its respective parameter lines and the DO statement lines. |
|
Multiple Lines |
User-specified group of parameter lines. A series of DO statements. |
Line Editing CommandsLink copied to clipboard
The following types of line editing commands exist in the Edit environment.
Table 305 Line Editing Commands: Delete Commands
|
Command |
Description |
|---|---|
|
DS |
Delete a single line. |
|
DL |
Delete a logical line. |
|
DB |
Delete a logical block or sub-block. |
|
DD |
Delete lines between two DD specifications. |
|
D |
Delete a line. Control-M determines whether to delete a single or logical line based on the line type. |
Table 306 Line Editing Commands: Copy Commands
|
Command |
Description |
|---|---|
|
CS |
Copy a single line. |
|
CL |
Copy a logical line. |
|
CB |
Copy a logical block or sub-block. |
|
CC |
Copy lines between two CC specifications. |
|
C |
Copy a line. Control-M determines whether to copy a single or logical line based on the line type. |
|
Copy commands are used in conjunction with Location commands. The lines and blocks are placed at the position indicated by Location command A or B (described below). |
|
Table 307 Line Editing Commands: Move Commands
|
Command |
Description |
|---|---|
|
MS |
Move a single line. |
|
ML |
Move a logical line. |
|
MB |
Move a logical block or sub-block. |
|
MM |
Move lines between two MM specifications. |
|
M |
Moves a line. Control-M determines whether to move a single or logical line based on line type. |
|
Move commands are used in conjunction with Location commands. The lines and blocks are placed at the position indicated by Location command A or B, described in Table 310 below. |
|
Table 308 Line Editing Commands: Repeat Commands
|
Command |
Description |
|---|---|
|
RS |
Repeat a single line. |
|
RL |
Repeat a logical line. |
|
RB |
Repeat a logical block or sub-block. |
|
RR |
Repeat lines between two RR specifications. |
|
R |
Repeat a line. Control-M determines whether to repeat a single or logical line based on line type. |
|
The repeated lines and blocks are placed immediately after the lines and blocks marked with the command. |
|
Table 309 Line Editing Commands: Insert Command
|
Command |
Description |
|---|---|
|
I |
Inserts a new logical line or block after the logical line or block marked with an I. |
Table 310 Line Editing Commands: Location Commands
|
Command |
Description |
|---|---|
|
Indication of the position where lines or blocks must be placed. |
|
|
A (After) |
Indicates that lines or blocks must be placed after the line marked with an A. |
|
B (Before) |
Indicates that lines or blocks must be placed before the line marked with a B. |
|
Location commands A and B are used in conjunction with Copy (C, CS, CL, CC), and Move (M, MS, ML, MM) commands. |
|
Maintaining Valid Job Scheduling DefinitionsLink copied to clipboard
Since job scheduling definitions must be syntactically correct at all times, the user must consider the following issues when specifying Line Editing commands:
-
The result of a Line Editing command is dependent on the line on which the command is specified. For example, command D deletes either a single or a logical line based on the line type.
-
Logical lines form a unit and cannot be separated.
When a logical command is specified within a logical line, that is, on a subparameter line or an additional parameter line, the specified operation is performed on the entire logical line.
-
Block commands must be specified on the main lines of the block. For example, to delete an ON block, specify command DB (Delete Block) on the ON line.
-
Blank parameter lines are added automatically by Control-M, to allow the user to specify additional parameters, and cannot be deleted.
-
BMC recommends that, wherever possible, you use commands D, C, R, and M for editing, instead of DS, DL, CS, CL, RS, RL, MS, and ML, because these commands automatically retain the logical structure of the job scheduling definition.
Before: Insert additional DO statements within a DO block using command I (Insert).
Figure 393 Example: Inserting A DO Statement - Before
JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL
COMMAND ===> SCROLL===> CRSR
+--------------------------------------------------------------------+
__ AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS
__ SYSOUT OP (C,D,F,N,R) FROM
__ RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP
__ MAXRERUN 3 RERUNMEM INTERVAL FROM
__ STEP RANGE FR (PGM.PROC) . TO .
__ ON PGMST ANYSTEP PROCST CODES S*** U**** C2000 ***** A/O
__ CODES
I_ DO IFRERUN FROM $ABEND . TO . CONFIRM Y
__ DO RERUN
__ DO
__ ON PGMST PROCST CODES A/O
__ DO
__ ON SYSOUT FROM 001 TO 132 A/O
__ DO
__ ON VAR
__ DO
__ SHOUT WHEN TIME + DAYS TO URGN
__ MS
======= >>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<< =====
COMMANDS: EDIT, DOC, PLAN, JOBSTAT 16.44.31After
Figure 394 Example: Inserting A DO Statement - After
JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL
COMMAND ===> SCROLL===> CRSR
+--------------------------------------------------------------------+
__ AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS
__ SYSOUT OP (C,D,F,N,R) FROM
__ RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP
__ MAXRERUN 3 RERUNMEM INTERVAL FROM
__ STEP RANGE FR (PGM.PROC) . TO .
__ ON PGMST ANYSTEP PROCST CODES S*** U**** C2000 ***** A/O
__ CODES
__ DO IFRERUN FROM $ABEND . TO . CONFIRM Y
__ DO
__ DO RERUN
__ DO
__ ON PGMST PROCST CODES A/O
__ DO
__ ON SYSOUT FROM 001 TO 132 A/O
__ DO
__ ON VAR
__ DO
__ SHOUT WHEN TIME + DAYS TO URGN
__ MS
======= >>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<<< =====
COMMANDS: EDIT, DOC, PLAN, JOBSTAT 14.49.42Before: Delete an ON PGMST block. Use of the DB (Delete Block) command is the preferred method. The DB command removes all parameters, comments, continuation lines, and separator lines of the specified block. DB must be specified on a main line of the block, that is, ON PGMST. In this example, the ON PGMST block is deleted.
Figure 395 Example: Deleting A Block - Before
JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL
COMMAND ===> SCROLL===> CRSR
+--------------------------------------------------------------------+
__ ===================================================================
__ OUT
__ AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS
__ RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP
__ SYSOUT OP (C,D,F,N,R) FROM
__ MAXRERUN 3 RERUNMEM INTERVAL. FROM
__ STEP RANGE FR (PGM.PROC) . TO
DB ON PGMST ANYSTEP PROCST CODES S*** U**** C2000 ***** A/O
__ CODES
__ DO IFRERUN FROM $ABEND . TO . CONFIRM Y
__ DO RERUN
__ DO
__ ON PGMST PROCST CODES A/O
__ DO
__ ON SYSOUT FROM 001 TO 132 A/O
__ DO
__ ON VAR
__ DO
__ SHOUT WHEN TIME + DAYS TO URGN
__ MS
======= >>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<< =====
COMMANDS: EDIT, DOC, PLAN, JOBSTAT 14.52.02After: The ON PGMST ANYSTEP block has been deleted.
Figure 396 Example: Deleting A Block - After
JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL
COMMAND ===> SCROLL===> CRSR
+--------------------------------------------------------------------+
__ ===================================================================
__ OUT
__ AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS
__ RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP
__ SYSOUT OP (C,D,F,N,R) FROM
__ MAXRERUN 3 RERUNMEM INTERVAL. FROM
__ STEP RANGE FR (PGM.PROC) . TO .
__ ON PGMST PROCST CODES A/O
__ DO
__ ON SYSOUT FROM 001 TO 132 A/O
__ DO
__ ON VAR
__ DO
__ SHOUT WHEN TIME + DAYS TO URGN
__ MS
======= >>>>>>>>>>>>>>> END OF SCHEDULING PARAMETERS <<<<<<<<<<< =====
COMMANDS: EDIT, DOC, PLAN, JOBSTAT 14.53.58Example 3
Before: Move multiple DO statements from one sub-block to another. Command MM (Multiple Move) is specified at the beginning and end of the DO statements that are moved. Command A (After) specifies the location after which these lines are placed.
Figure 397 Example: Moving Statements - Before
JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL
COMMAND ===> SCROLL===> CRSR
+--------------------------------------------------------------------+
__ OUT
__ AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS
__ RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP
__ SYSOUT OP (C,D,F,N,R) FROM
__ MAXRERUN 3 RERUNMEM INTERVAL. FROM
__ STEP RANGE FR (PGM.PROC) . TO .
__ ON PGMST ANYSTEP PROCST CODES S*** U**** C2000 ***** A/O
__ CODES
__ DO IFRERUN FROM $ABEND . TO . CONFIRM Y
__ DO RERUN
MM DO COND STEP5_DONE ODAT +
__ DO SHOUT TO TSO-M22 URGENCY R
MM = STEP STEP05 PROCESSED
__ DO
__ ON PGMST STEP05 PROCST CODES S*** A/O
A_ DO IFRERUN FROM $ABEND . TO . CONFIRM N
__ DO
__ ON PGMST PROCST CODES A/O
__ DO After: The two specified DO statements have been moved to the specified location.
Figure 398 Example: Moving Statements - After
JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL
COMMAND ===> SCROLL===> CRSR
+--------------------------------------------------------------------+
__ OUT
__ AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS
__ RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP
__ SYSOUT OP (C,D,F,N,R) FROM
__ MAXRERUN 3 RERUNMEM INTERVAL. FROM
__ STEP RANGE FR (PGM.PROC) . TO .
__ ON PGMST ANYSTEP PROCST CODES S*** U**** C2000 ***** A/O
__ CODES
__ DO IFRERUN FROM $ABEND . TO . CONFIRM Y
__ DO RERUN
__ DO
__ ON PGMST STEP05 PROCST CODES S*** A/O
__ DO IFRERUN FROM $ABEND . TO . CONFIRM N
__ DO COND STEP5_DONE ODAT +
__ DO SHOUT TO TSO-M22 URGENCY R
__ = STEP STEP05 PROCESSED
__ DO
__ ON PGMST PROCST CODES A/O
__ DO Before: Copy ON PGMST and some of its DO statements to another ON PGMST block. Command CC (Multiple Copy) is specified at the beginning and the end of the parameters that is copied. Command B (Before) specifies the location before which these lines are placed.
Figure 399 Example: Copying Statements - Before
JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL
COMMAND ===> SCROLL===> CRSR
+---------------------------------------------------------------------+
__ AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS
__ RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP
__ SYSOUT OP (C,D,F,N,R) FROM
__ MAXRERUN 3 RERUNMEM INTERVAL. FROM
__ STEP RANGE FR (PGM.PROC) . TO .
__ ON PGMST ANYSTEP PROCST CODES S*** U**** C2000 ***** A/O
__ CODES
__ DO IFRERUN FROM $ABEND . TO . CONFIRM Y
__ DO RERUN
__ DO
CC ON PGMST STEP05 PROCST CODES S*** A/O
__ DO IFRERUN FROM $ABEND . TO . CONFIRM N
CC DO COND STEP5_DONE ODAT +
__ DO SHOUT TO TSO-M22 URGENCY R
__ = STEP STEP05 PROCESSED
__ DO
B ON PGMST PROCST CODES A/O
__ DO After: The specified ON PGMST and DO statements have been copied.
Figure 400 Example: Copying Statements - After
JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL
COMMAND ===> SCROLL===> CRSR
+---------------------------------------------------------------------+
__ MAXRERUN 3 RERUNMEM INTERVAL. FROM
__ RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP
__ STEP RANGE FR (PGM.PROC) . TO .
__ ON PGMST ANYSTEP PROCST CODES S*** U**** C2000 ***** A/O
__ CODES
__ DO IFRERUN FROM $ABEND . TO . CONFIRM Y
__ DO RERUN
__ DO
__ ON PGMST STEP05 PROCST CODES S*** A/O
__ DO IFRERUN FROM $ABEND . TO . CONFIRM N
__ DO COND STEP5_DONE ODAT +
__ DO SHOUT TO TSO-M22 URGENCY R
__ = STEP STEP05 PROCESSED
__ DO
__ ON PGMST STEP05 PROCST CODES S*** A/O
__ DO IFRERUN FROM $ABEND . TO . CONFIRM N
__ DO COND STEP5_DONE ODAT +
__ DO
__ ON PGMST PROCST CODES A/O
__ DO Before: Insert a continuation line between existing continuation lines. It is recommended that command RS (Repeat Single) or R (Repeat) be used to repeat the previous line.
Figure 401 Example: Inserting A Line - Before
JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL
COMMAND ===> SCROLL===> CRSR
+----------------------------------------------------------------------+
__ TIME ZONE:
__ ========================================================================
__ OUT
__ AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS
__ RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP
__ SYSOUT OP (C,D,F,N,R) FROM
__ MAXRERUN 3 RERUNMEM INTERVAL. FROM
__ STEP RANGE FR (PGM.PROC) . TO .
__ ON PGMST ANYSTEP PROCST CODES S*** U**** C2000 C3000 A/O A
RS CODES C4000 C5000 C6000 C7000
__ CODES C1200
__ ON PGMST STEP04 PROCST CODES ***** A/O
__ DO IFRERUN FROM $ABEND . TO . CONFIRM Y
__ DO RERUN
__ DO
__ ON PGMST STEP05 PROCST CODES S*** A/O
__ DO IFRERUN FROM $ABEND . TO . CONFIRM N
__ DO COND STEP5_DONE ODAT +
__ DO SHOUT TO TSO-M22 URGENCY R
__ = STEP STEP05 PROCESSED After: The continuation line has been repeated. The repeated line can be modified as necessary.
Figure 402 Example: Inserting A Line - After
JOB: PRDKPL01 LIB CTM.PROD.SCHEDULE TABLE: PRODKPL
COMMAND ===> SCROLL===> CRSR
+----------------------------------------------------------------------+
__ TIME ZONE:
__ =====================================================================
__ OUT
__ AUTO-ARCHIVE Y SYSDB Y MAXDAYS MAXRUNS
__ RETENTION: # OF DAYS TO KEEP 030 # OF GENERATIONS TO KEEP
__ SYSOUT OP (C,D,F,N,R) FROM
__ MAXRERUN 3 RERUNMEM INTERVAL. FROM
__ STEP RANGE FR (PGM.PROC) . TO .
__ ON PGMST ANYSTEP PROCST CODES S*** U**** C2000 C3000 A/O A
__ CODES C4000 C5000 C6000 C7000
__ CODES C4000 C5000 C6000 C7000
__ CODES C1200
__ ON PGMST STEP04 PROCST CODES ***** A/O
__ DO IFRERUN FROM $ABEND . TO . CONFIRM Y
__ DO RERUN
__ DO
__ ON PGMST STEP05 PROCST CODES S*** A/O
__ DO IFRERUN FROM $ABEND . TO . CONFIRM N
__ DO COND STEP5_DONE ODAT +
__ DO SHOUT TO TSO-M22 URGENCY R 
Communities
Support Center
YouTube
Twitter
Facebook
LinkedIn