Operation Considerations
This chapter includes the following topics:
Restart after a system crash
Control-M/Restart handling of restart following a system crash depends on the value specified in the SEARCH parameter in the CTRPARM member in the IOA PARM library.
The SEARCH parameter controls the searching for uncataloged data sets on all mounted disks if Control-M/Restart recognizes that the original job run failed due to a system crash. This search is part of data set cleanup. Valid values are described in Table 33.
Table 33 SEARCH Parameter Values
|
Value |
Description |
|---|---|
|
YES |
Control-M/Restart starts searching for uncataloged data sets on all mounted disks. |
|
NO |
Suppresses this processing; Control-M/Restart does not start searching. |
|
CONFIRM |
Control-M/Restart issues the CTR303I and CTR304I messages and then waits for an operator's confirmation before starting to search the data sets. |
As noted above, if the SEARCH parameter has a value of CONFIRM, the operator is prompted (Yes/No) for instructions following a system crash. The operator can either confirm the search (YES) or cancel the search (NO).
Multi-CPU environments
Consider the following when running Control-M/Restart in a multi-CPU environment:
-
When the original job runs on the same CPU as the Control-M monitor, the DAARCH data set contains a set of pointers to the archived SYSDATA.
-
If the restart job is also submitted on the same CPU, there are no special concerns. However, if the restart job can be submitted on a different CPU, certain concerns must be addressed if the restart is to be successful:
-
The SYSDATA of the previous runs must be archived on a disk that is shared between CPUs. (Read access is sufficient since the Control-M/Restart step only requires read access to the SYSDATA.)
-
The SYSDATA must also be in a catalog that can be accessed from all CPUs on which the job can run.
If different catalogs are used in each CPU, or if JOBCAT or STEPCAT JCL statements are used in the job, the restart job is run in the same CPU in which it originally executed. If the restart job runs in a different CPU than the original one, and different catalogs are used, the results of the restart are unpredictable.
-
When the original job runs on a different (remote) node than the Control-M monitor, the DAARCH data set contains the actual archived SYSDATA. Therefore, access of the SYSDATA during restart is not a problem.
-
However, the considerations concerning catalogs remains. If all systems at the execution node do not share a common catalog, ensure that the restart executes on a system from which the required catalogs can be accessed.
IF/THEN/ELSE JCL blocks
Control-M/Restart can simulate and evaluate IF/THEN/ELSE JCL blocks, and restart the job from within the IF/THEN/ELSE JCL block when necessary, only if the IFADJ parameter in the CTRPARM member in the IOA PARM library is set to YES.
In this case, IF/THEN/ELSE JCL statements (or the COND parameter) operate as if backward-referenced steps were included in the restart run and are able to reference the correct condition code (meaning, the condition code of the backward-referenced step) from the previous unsuccessful run of the job. In this manner, the fact that the backward-referenced step is not included in the restart job is totally invisible to the COND and IF/THEN/ELSE parameters.
If the IFADJ parameter is set to NO, Control-M/Restart does not handle IF/THEN/ELSE JCL blocks. In this case, do not use Control-M/Restart to restart jobs containing IF/THEN/ELSE blocks because the results are unpredictable.
Generation data sets (GDG)
Adjustment of generation number by the CONTROLR step is not done by modifying the JCL of the job. The original JCL may actually be in an invoked procedure that cannot be modified.
Instead, Control-M/Restart modifies the reference to the real name of the generation data set. Every generation number in a given job run relates to a specific data set name. Control-M/Restart retrieves the data set names from the SYSDATA of the previous runs of the job, and replaces the data set names that were chosen by the system in the restart run.
The above action can be detected in the following ways:
-
a message in the report produced by the CONTROLR step
-
the IEF285I messages of the job
To ensure proper GDG processing, BMC recommends that you review the settings of the relevant parameters in the CTRPARM member in the IOA PARM library. These parameters (MODGDGN ENHGDG, IGNFLUSH, and SAMEGDG), are described in the INCONTROL for z/OS Installation Guide.
$DEFAULT parameter member
UNITNAME definition
To determine the location of all data sets, Control-M/Restart uses UNITNAME definition statements in the control parameters to associate esoteric unit names with actual device types.
It is recommended that the $DEFAULT parameter member contain UNITNAME definition statements to enable Control-M/Restart to locate all required data sets.
Under certain circumstances, Control-M/Restart needs to search for a data set on all the disks that belong to a specified unit (for example, to scratch uncataloged data sets after a computer crash, and the data sets are allocated using the UNIT parameter without a VOL parameter).
For proper location of the data sets, Control-M/Restart uses UNITNAME definitions that are contained (in priority order from highest to lowest) in the control parameter member used for the restart, the $DEFAULT member of the Control-M/Restart parameter library, and an internal table of UNITNAME definitions. UNITNAME definitions are listed by Control-M/Restart as part of its output. For an example of this listing, see Sample Control-M/Restart job restart execution.
These definitions are accessed when the job is restarted. If a change is made to the UNIT definitions at the site, either after an IPL or dynamically, the UNITNAME definitions for Control-M/Restart must be updated to reflect these changes. If the UNITNAME definitions are incorrect, Control-M/Restart may not perform the restart correctly.
Valid format for UNITNAME definitions is described in Control parameters in the Control-M/Restart PARM library.
File exclusion
BMC recommends that this member contain EXCLUDE DSN statements for important data set prefixes or names, such as
-
SYS1*
-
IPO1*
-
databases
-
installed software products
"Helping" Control-M/Restart
A basic assumption of Control-M/Restart logic is that the user has not assisted the restart process in any way.
Control-M/Restart is designed to restart exactly the same job. Any modifications made by the user make the job into a different job. If modifications are made, a successful restart of the job cannot be guaranteed. Therefore, you must be careful not to change the JCL, especially in the following ways:
-
modifying the name or generation number of a data set
-
adding and deleting steps
Exceptions include changing the file size in response to a space abend, for example, Sx37, or changing the name of an input data set. In these cases, you can perform the changes.
You must also not delete or move relevant files, unless absolutely necessary, as in the case of disk damage.
Indicating non-restartable steps: CTRNORST DD
You can indicate that restart not begin at a particular step by specifying the CTRNORST DD statement for the step. During step adjustment, if the recoverable step selected by Control-M/Restart contains the CTRNORST DD statement, step adjustment continues to the preceding recoverable step. If adjustment reaches the first job step and the first job step contains the CTRNORST DD statement, restart is not performed.
The format of the CTRNORST DD statement is
//CTRNORST DD DUMMYFor customers who have converted from CA-11 to Control-M/Restart, the following DD statement is also supported for compatibility:
//UCC11NR DD DUMMYFor more information, see NONRESTARTABLE_STEP parameter and NONRESTARTABLE_PGM parameter.
Space for archived sysouts
Ensure that enough space is available to archive SYSDATA for all jobs that execute under Control-M and for which a Y value for AUTO-ARCHIVE is specified either explicitly or by default. Control-M allocates space as needed on the devices defined by the AMVOL and AMUNIT parameters in the CTRPARM member in the IOA PARM library, until all available space on the volumes is allocated.
-
If SYSDB=Y is specified (recommended)
-
The SYSDATA of all jobs is written to a common data set until it is filled; then a new data set is automatically allocated. This minimizes the space required in the catalog and in the VTOC on the defined disk.
-
If SYSDB=N is specified
-
Since every job execution results in one cataloged data set, make sure that the VTOC of the defined disks is large enough to contain all the data sets, and that enough space is available in the catalog. It is recommended that a user catalog be defined for the prefix defined in the AMPREFR parameter in the CTRPARM member in the IOA PARM library.
Do not release unused space from SYSDATA files by automated data management products (such as FDR and DMS/OS).
Deleting archived SYSDATA
Deletion of archived SYSDATA is performed automatically by the Control-M New Day procedure (started task CONTDAY) or by the CTMCAJF utility. For more information about the New Day procedure, refer to the INCONTROL for z/OS Administrator Guide.
The New Day procedure deletes archived SYSDATA if the job does not reside in the History Jobs file and either of the following conditions is true:
-
The job order is deleted from the Active Jobs file (therefore the archived SYSDATA is no longer needed). A job order is usually deleted from the Active Jobs file after it has completed OK.
-
The maximum number of days to retain archived SYSDATA, or the maximum number of job runs for which the SYSDATA is retained, has been exceeded. These values are specified in the MAXDAYS and MAXRUNS subparameters of the AUTO-ARCHIVE parameter in the Control-M job scheduling definition.
Whether, and how long, a job is on the History Jobs file depends on the values of the RETENTION parameters in the job scheduling definition.
Control-M/Restart and tape management systems
The presence or absence of a tape management system (such as Control-M/Tape) determines how Control-M/Restart handles tape volume reuse when a restarted job re-executes steps that created new tape data sets in previous runs.
If a tape management system is in use, Control-M/Restart does not attempt to reuse the same tape volume during the rerun.
When there is no tape management system, Control-M/Restart attempts to reuse the same tape volume during the job rerun.
Presence or absence of a tape management system is indicated in the TAPEMS parameter in the CTRPARM member in the IOA PARM library.
For full functionality of the Control-M/Restart interface to tape management systems, the CTRX001 Control-M/Restart exit may be necessary. For more information, see the CTRX001T and CTRX001Z sample exits in the IOA SAMPEXIT library.
Control-M/Restart and SMS
At sites in which SMS (System Managed Storage) is implemented, BMC recommends that you review the setting of the VOLISMS parameter in the CTRPARM member in the IOA PARM library. This parameter is described in the INCONTROL for z/OS Installation Guide.
Control-M/Restart interface to Control-M/Analyzer
To ensure functionality of the Control-M/Restart interface to Control-M/Analyzer, CTRX001Q Control-M/Restart Exit may be necessary. For more information, see the sample exit in the IOA SAMPEXIT library.
Control-M/Restart interface to third party vendor products
To ensure functionality of the Control-M/Restart interface to HSM (Hierarchical Storage Manager), the CTRX001H Control-M/Restart Exit may be necessary. For more information, see the sample exit in the IOA SAMPEXIT library.
To ensure functionality of the Control-M/Restart interface to BETA91, the CTRX001B Control-M/Restart Exit may be necessary. For more information, see the sample exit in the IOA SAMPEXIT library.
To ensure functionality of the Control-M/Restart interface to DMS/OS, the CTRX001D Control-M/Restart Exit may be necessary. For more information, see the sample exit in the IOA SAMPEXIT library.
To ensure functionality of the Control-M/Restart interface to the IDCAMS IBM utility and other applications that dynamically allocate files, it may be necessary to set the NFILVS99 parameter in the CTRPARM member in the IOA PARM library to Y (Yes). This parameter is described in the INCONTROL for z/OS Installation Guide.
Control-M/Restart handles only those data sets that are specified in DD statements in the JCL of jobs. It does not handle dynamically allocated data sets, with the exception of the cases affected by setting the NFILVS99 parameter to Y (Yes).
Sample Control-M/Restart job restart execution
The following is a sample of a job that was restarted by Control-M/Restart. (Lines that are bolded are discussed in notes following the sample execution.) Control-M/Restart was instructed to attempt restart from STEP005 if any job step abended. In the Job Scheduling Definition screen (Screen 2), the parameters illustrated in Figure 7 were entered.
Figure 7 Parameters entered in the job scheduling definition - sample Control-M/Restart job restart execution
STEP RANGE ANYSTEP FR (PGM.PROC) STEP001 . TO STEP008 .
STEP RANGE FR (PGM.PROC) . TO .
ON PGMST ANYSTEP PROCST CODES S*** U**** A/O
DO IFRERUN FROM STEP005 . TO . CONFIRM N
DO RERUN
DOThe previous run of PRDJBGL5 abended in STEP006.
Figure 8 Sample Control-M/Restart job restart execution
J E S 2 J O B L O G -- S Y S T E M F D S F -- N O D E N O D E 1
18.43.51 JOB 3144 IEF677I WARNING MESSAGE(S) FOR JOB PRDJBGL5 ISSUED
18.43.51 JOB 3144 $HASP373 PRDJBGL5 STARTED - INIT 1 - CLASS A - SYS FDSF
18.43.51 JOB 3144 IEF403I PRDJBGL5 - STARTED - TIME=18.43.51
18.44.17 JOB 3144 CTR082I RESTARTING FROM STEP STEP003 . TO STEP STEP009 .
18.44.52 JOB 3144 IEF404I PRDJBGL5 - ENDED - TIME=18.44.52
18.44.52 JOB 3144 $HASP395 PRDJBGL5 ENDED
------ JES2 JOB STATISTICS ------
10 AUG 98 JOB EXECUTION DATE
124 CARDS READ
528 SYSOUT PRINT RECORDS
0 SYSOUT PUNCH RECORDS
36 SYSOUT SPOOL KBYTES
1.01 MINUTES EXECUTION TIME
1 //PRDJBGL5 JOB ,GPL,MSGCLASS=X,CLASS=A, JOB 3144
// MSGLEVEL=(1,1)
***------------ SUBMITTED BY CONTROL-M -------
**************************************************************
**** S T E P 0 0 1 **
**************************************************************
2 //RESTART EXEC PROC=CONTROLR,
// PARM='RR,PRDJBGL5,000BU,RL,.STEP005,,ACS'
3 XXCONTROLR PROC ARCHF=NULLFILE, FOR FUTURE USE
XX PRM=,
XX STEPLIB='IOA.PROD.LOAD', CONTROL-R LOAD LIBRARY
XX OLPREFR='CTRO', OPERATIONS LIBRARY PREFIX
XX OLVERR='CTRPROD', OPERATIONS LIBRARY VERSION
XX OUT='*',
XX OUTDUMP='Z'
********************************************************************
***** THE CONTROL-R STEP ****
***** ------------------ ****
***** ****
***** THIS STEP PERFORMS THE MAIN RESTART TASKS: ****
***** - RESTART STEP ADJUSTMENT ****
***** - FILE, CATALOG AND GDG ADJUSTMENT ****
***** - CONDITION CODE RECAPTURE ****
***** ****
********************************************************************
4 XXCONTROLR EXEC PGM=CTRCTR,PARM='&PRM',REGION=4000K
5 XXSTEPLIB DD DISP=SHR,DSN=&STEPLIB
6 //DAARCH DD *,DCB=(LRECL=132)
X/DAARCH DD DISP=SHR,DSN=&ARCHF
7 XXDACTRCTL DD DISP=SHR,DSN=&OLPREFR..&OLVERR..CTR.PARM
8 XXSYSPRINT DD SYSOUT=&OUT
9 XXDATRACE DD SYSOUT=&OUTDUMP
10 XXCDAMSNAP DD SYSOUT=&OUTDUMP
11 XXSYSABEND DD SYSOUT=&OUTDUMP
12 //STEP001 EXEC PGM=IEBGENER
13 //SYSPRINT DD SYSOUT=*
14 //SYSUT1 DD DISP=SHR,DSN=PRDJBGL.JOBLIB(INFILE)
15 //SYSUT2 DD DSN=PRDJBGL.GDG.GRP07(+1),
// DISP=(,CATLG,DELETE),UNIT=SYSDA,
// DCB=(MODEL,RECFM=FB,LRECL=80,BLKSIZE=6160),
// SPACE=(TRK,1)
16 //SYSOUT DD SYSOUT=*
17 //SYSIN DD DUMMY
**************************************************************
**** S T E P 0 0 2
**************************************************************
18 //STEP002 EXEC PGM=PRDJBTST
19 //STEPLIB DD DISP=SHR,DSN=PRDJBGL.LOAD
20 //TESTFILE DD DISP=SHR,DSN=PRDJBGL.GDG.GRP07(+1)
**************************************************************
**** S T E P 0 0 3
**************************************************************
21 //STEP003 EXEC PGM=SORT,REGION=5000K
22 //SORTIN DD DISP=SHR,DSN=PRDJBGL.GDG.GRP07(+1)
23 //SORTOUT DD DSN=&ZMN1,DISP=(,PASS),
// UNIT=SYSDA,SPACE=(TRK,1),
// DCB=(MODEL,RECFM=FB,LRECL=80,BLKSIZE=6160)
24 //SORTWK01 DD UNIT=SYSDA,SPACE=(CYL,(5,25))
25 //SORTWK02 DD UNIT=SYSDA,SPACE=(CYL,(5,25))
26 //SORTWK03 DD UNIT=SYSDA,SPACE=(CYL,(5,25))
27 //SYSPRINT DD SYSOUT=*
28 //SYSOUT DD SYSOUT=*
29 //SYSUDUMP DD SYSOUT=*
30 //SYSIN DD * GENERATED STATEMENT
**************************************************************
**** S T E P 0 0 4
**************************************************************
31 //STEP004 EXEC PGM=SORT,REGION=5000K
32 //SORTIN DD DISP=(OLD,PASS),DSN=&ZMN1
33 //SORTOUT DD DSN=PRDJBGL.GDG.GRP07(+2),
// DISP=(,CATLG,DELETE),UNIT=SYSDA,
// DCB=(MODEL,RECFM=FB,LRECL=80,BLKSIZE=6160),
// SPACE=(TRK,1)
34 //SORTWK01 DD UNIT=SYSDA,SPACE=(CYL,(5,25))
35 //SORTWK02 DD UNIT=SYSDA,SPACE=(CYL,(5,25))
36 //SORTWK03 DD UNIT=SYSDA,SPACE=(CYL,(5,25))
37 //SYSPRINT DD SYSOUT=*
38 //SYSOUT DD SYSOUT=*
39 //SYSUDUMP DD SYSOUT=*
40 //SYSIN DD * GENERATED STATEMENT
**************************************************************
**** S T E P 0 0 5
**************************************************************
41 //STEP005 EXEC PGM=SORT,REGION=5000K
42 //SORTIN DD DISP=SHR,DSN=PRDJBGL.GDG.GRP07(+2)
43 //SORTOUT DD DSN=PRDJBGL.GDG.GRP08(+1),
// DISP=(,CATLG,DELETE),UNIT=SYSDA,
// DCB=(MODEL,RECFM=FB,LRECL=80,BLKSIZE=6160),
// SPACE=(TRK,1)
44 //SORTWK01 DD UNIT=SYSDA,SPACE=(CYL,(5,25))
45 //SORTWK02 DD UNIT=SYSDA,SPACE=(CYL,(5,25))
46 //SORTWK03 DD UNIT=SYSDA,SPACE=(CYL,(5,25))
47 //SYSPRINT DD SYSOUT=*
48 //SYSOUT DD SYSOUT=*
49 //SYSUDUMP DD SYSOUT=*
50 //SYSIN DD * GENERATED STATEMENT
**************************************************************
**** S T E P 0 0 6
**************************************************************
51 //STEP006 EXEC PGM=PRDJBTST
52 //STEPLIB DD DISP=SHR,DSN=PRDJBGL.LOAD
**************************************************************
**** S T E P 0 0 7 **
**************************************************************
53 //STEP007 EXEC PGM=SORT,REGION=5000K
54 //SORTIN DD DISP=OLD,DSN=&ZMN1
55 //SORTOUT DD DSN=PRDJBGL.GDG.GRP08(+2),
// DISP=(,CATLG,DELETE),UNIT=SYSDA,
// DCB=(MODEL,RECFM=FB,LRECL=80,BLKSIZE=6160),
// SPACE=(TRK,1)
56 //SORTWK01 DD UNIT=SYSDA,SPACE=(CYL,(5,25))
57 //SORTWK02 DD UNIT=SYSDA,SPACE=(CYL,(5,25))
58 //SORTWK03 DD UNIT=SYSDA,SPACE=(CYL,(5,25))
59 //SYSPRINT DD SYSOUT=*
60 //SYSOUT DD SYSOUT=*
61 //SYSUDUMP DD SYSOUT=*
62 //SYSIN DD * GENERATED STATEMENT
**************************************************************
**** S T E P 0 0 8 **
**************************************************************
63 //STEP008 EXEC PGM=SORT,REGION=5000K,COND=(0,NE,STEP002)
64 //SORTIN DD DISP=SHR,DSN=PRDJBGL.GDG.GRP08(+2)
65 //SORTOUT DD DSN=&ZMN2,DISP=(,PASS),
// UNIT=SYSDA,SPACE=(TRK,1),
// DCB=(MODEL,RECFM=FB,LRECL=80,BLKSIZE=6160)
66 //SORTWK01 DD UNIT=SYSDA,SPACE=(CYL,(5,25))
67 //SORTWK02 DD UNIT=SYSDA,SPACE=(CYL,(5,25))
68 //SORTWK03 DD UNIT=SYSDA,SPACE=(CYL,(5,25))
69 //SYSPRINT DD SYSOUT=*
70 //SYSOUT DD SYSOUT=*
71 //SYSUDUMP DD SYSOUT=*
72 //SYSIN DD * GENERATED STATEMENT
**************************************************************
**** S T E P 0 0 9 **
**************************************************************
73 //STEP009 EXEC PGM=SORT,REGION=5000K,COND=(0,NE,STEP002)
74 //SORTIN DD DISP=OLD,DSN=&ZMN2
75 //SORTOUT DD DSN=PRDJBGL.GDG.GRP07(+3),
// DISP=(,CATLG,DELETE),UNIT=SYSDA,
// DCB=(MODEL,RECFM=FB,LRECL=80,BLKSIZE=6160),
// SPACE=(TRK,1)
76 //SORTWK01 DD UNIT=SYSDA,SPACE=(CYL,(5,25))
77 //SORTWK02 DD UNIT=SYSDA,SPACE=(CYL,(5,25))
78 //SORTWK03 DD UNIT=SYSDA,SPACE=(CYL,(5,25))
79 //SYSPRINT DD SYSOUT=*
80 //SYSOUT DD SYSOUT=*
81 //SYSUDUMP DD SYSOUT=*
82 //SYSIN DD * GENERATED STATEMENT
STMT NO. MESSAGE
-
4 IEF653I SUBSTITUTION JCL - PGM=CTRCTR,PARM='',REGION=4000K
5 IEF653I SUBSTITUTION JCL - DISP=SHR,DSN=IOA.PROD.LOAD
6 IEF653I SUBSTITUTION JCL - DISP=SHR,DSN=NULLFILE
7 IEF653I SUBSTITUTION JCL - DISP=SHR,DSN=CTRO.CTRPROD.CTR.PARM
8 IEF653I SUBSTITUTION JCL - SYSOUT=*
9 IEF653I SUBSTITUTION JCL - SYSOUT=Z
10 IEF653I SUBSTITUTION JCL - SYSOUT=Z
11 IEF653I SUBSTITUTION JCL - SYSOUT=Z
54 IEF648I INVALID DISP FIELD- PASS SUBSTITUTED
74 IEF648I INVALID DISP FIELD- PASS SUBSTITUTED
IEF236I ALLOC. FOR PRDJBGL5 CONTROLR RESTART
IEF237I 269 ALLOCATED TO STEPLIB
IEF237I JES2 ALLOCATED TO DAARCH
IEF237I 271 ALLOCATED TO DACTRCTL
IEF237I JES2 ALLOCATED TO SYSPRINT
IEF237I JES2 ALLOCATED TO PRTDBG
IEF237I JES2 ALLOCATED TO CDAMSNAP
IEF237I JES2 ALLOCATED TO SYSABEND
IEF237I 273 ALLOCATED TO SYS00001
IEF285I CTRSYS.JOBSDB.J03009.D1191637.S01.N000100 KEPT
IEF285I VOL SER NOS= WORK01.
IEF237I 263 ALLOCATED TO SYS00002
IEF142I PRDJBGL5 CONTROLR RESTART - STEP WAS EXECUTED - COND CODE 0000
IEF285I IOA.PROD.LOAD KEPT
IEF285I VOL SER NOS= CONT05.
IEF285I JES2.JOB03144.SI000101 SYSIN
IEF285I CTRO.CTRPROD.CTR.PARM KEPT
IEF285I VOL SER NOS= CONT03.
IEF285I JES2.JOB03144.SO000108 SYSOUT
IEF285I JES2.JOB03144.SO000109 SYSOUT
IEF285I JES2.JOB03144.SO000110 SYSOUT
IEF285I JES2.JOB03144.SO000111 SYSOUT
IEF285I CATALOG.USER KEPT
IEF285I VOL SER NOS= D50CAT.
IEF373I STEP /CONTROLR/ START 98222.1843
IEF374I STEP /CONTROLR/ STOP 98222.1844 CPU 0MIN 05.86SEC SRB 0MIN 00.17SEC
VIRT 508K SYS 356K
IEF236I ALLOC. FOR PRDJBGL5 STEP003
IEF237I 26B ALLOCATED TO SORTIN
IEF237I 263 ALLOCATED TO SYS00431
IEF237I 273 ALLOCATED TO SORTOUT
IEF237I 26B ALLOCATED TO SORTWK01
IEF237I 26B ALLOCATED TO SORTWK02
IEF237I 273 ALLOCATED TO SORTWK03
IEF237I JES2 ALLOCATED TO SYSPRINT
IEF237I JES2 ALLOCATED TO SYSOUT
IEF237I JES2 ALLOCATED TO SYSUDUMP
IEF237I JES2 ALLOCATED TO SYSIN
IEF142I PRDJBGL5 STEP003 - STEP WAS EXECUTED - COND CODE 0000
IEF285I PRDJBGL.GDG.GRP07.G0030V00 KEPT
IEF285I VOL SER NOS= WORK02.
IEF285I CATALOG.USER KEPT
IEF285I VOL SER NOS= D50CAT.
IEF285I SYS98222.T184351.RA000.PRDJBGL5.ZMN1 PASSED
IEF285I VOL SER NOS= WORK01.
IEF285I SYS98222.T184351.RA000.PRDJBGL5.R0000001 DELETED
IEF285I VOL SER NOS= WORK02.
IEF285I SYS98222.T184351.RA000.PRDJBGL5.R0000002 DELETED
IEF285I VOL SER NOS= WORK02.
IEF285I SYS98222.T184351.RA000.PRDJBGL5.R0000003 DELETED
IEF285I VOL SER NOS= WORK01.
IEF285I JES2.JOB03144.SO000114 SYSOUT
IEF285I JES2.JOB03144.SO000115 SYSOUT
IEF285I JES2.JOB03144.SO000116 SYSOUT
IEF285I JES2.JOB03144.SI000102 SYSIN
IEF373I STEP /STEP003 / START 00222.1844
IEF374I STEP /STEP003 / STOP 00222.1844 CPU 0MIN 00.36SEC SRB 0MIN 00.04SEC
VIRT 776K SYS 240K
IEF236I ALLOC. FOR PRDJBGL5 STEP004
IEF237I 273 ALLOCATED TO SORTIN
IEF237I 26B ALLOCATED TO SORTOUT
IEF237I 263 ALLOCATED TO SYS00432
IEF237I 26B ALLOCATED TO SORTWK01
IEF237I 273 ALLOCATED TO SORTWK02
IEF237I 26B ALLOCATED TO SORTWK03
IEF237I JES2 ALLOCATED TO SYSPRINT
IEF237I JES2 ALLOCATED TO SYSOUT
IEF237I JES2 ALLOCATED TO SYSUDUMP
IEF237I JES2 ALLOCATED TO SYSIN
IEF142I PRDJBGL5 STEP004 - STEP WAS EXECUTED - COND CODE 0000
IEF285I SYS00222.T184351.RA000.PRDJBGL5.ZMN1 PASSED
IEF285I VOL SER NOS= WORK01.
IEF285I PRDJBGL.GDG.GRP07.G0031V00 CATALOGED
IEF285I VOL SER NOS= WORK02.
IEF285I CATALOG.USER KEPT
IEF285I VOL SER NOS= D50CAT.
IEF285I SYS00222.T184351.RA000.PRDJBGL5.R0000004 DELETED
IEF285I VOL SER NOS= WORK02.
IEF285I SYS00222.T184351.RA000.PRDJBGL5.R0000005 DELETED
IEF285I VOL SER NOS= WORK01.
IEF285I SYS00222.T184351.RA000.PRDJBGL5.R0000006 DELETED
IEF285I VOL SER NOS= WORK02.
IEF285I JES2.JOB03144.SO000117 SYSOUT
IEF285I JES2.JOB03144.SO000118 SYSOUT
IEF285I JES2.JOB03144.SO000119 SYSOUT
IEF285I JES2.JOB03144.SI000103 SYSIN
IEF373I STEP /STEP004 / START 00222.1844
IEF374I STEP /STEP004 / STOP 00222.1844 CPU 0MIN 00.36SEC SRB 0MIN 00.04SEC
VIRT 776K SYS 252K
IEF236I ALLOC. FOR PRDJBGL5 STEP005
IEF237I 26B ALLOCATED TO SORTIN
IEF237I 263 ALLOCATED TO SYS00434
IEF237I 273 ALLOCATED TO SORTOUT
IEF237I 26B ALLOCATED TO SORTWK01
IEF237I 273 ALLOCATED TO SORTWK02
IEF237I 273 ALLOCATED TO SORTWK03
IEF237I JES2 ALLOCATED TO SYSPRINT
IEF237I JES2 ALLOCATED TO SYSOUT
IEF237I JES2 ALLOCATED TO SYSUDUMP
IEF237I JES2 ALLOCATED TO SYSIN
IEF142I PRDJBGL5 STEP005 - STEP WAS EXECUTED - COND CODE 0000
IEF285I PRDJBGL.GDG.GRP07.G0031V00 KEPT
IEF285I VOL SER NOS= WORK02.
IEF285I CATALOG.USER KEPT
IEF285I VOL SER NOS= D50CAT.
IEF285I PRDJBGL.GDG.GRP08.G0023V00 CATALOGED
IEF285I VOL SER NOS= WORK01.
IEF285I SYS00222.T184351.RA000.PRDJBGL5.R0000007 DELETED
IEF285I VOL SER NOS= WORK02.
IEF285I SYS00222.T184351.RA000.PRDJBGL5.R0000008 DELETED
IEF285I VOL SER NOS= WORK01.
IEF285I SYS00222.T184351.RA000.PRDJBGL5.R0000009 DELETED
IEF285I VOL SER NOS= WORK01.
IEF285I JES2.JOB03144.SO000120 SYSOUT
IEF285I JES2.JOB03144.SO000121 SYSOUT
IEF285I JES2.JOB03144.SO000122 SYSOUT
IEF285I JES2.JOB03144.SI000104 SYSIN
IEF373I STEP /STEP005 / START 00222.1844
IEF374I STEP /STEP005 / STOP 00222.1844 CPU 0MIN 00.33SEC SRB 0MIN 00.04SEC
VIRT 776K SYS 252K
IEF236I ALLOC. FOR PRDJBGL5 STEP006
IEF237I 261 ALLOCATED TO STEPLIB
IEF237I 263 ALLOCATED TO SYS00436
IEF142I PRDJBGL5 STEP006 - STEP WAS EXECUTED - COND CODE 0000
IEF285I PRDJBGL.LOAD KEPT
IEF285I VOL SER NOS= CONT04.
IEF285I CATALOG.USER KEPT
IEF285I VOL SER NOS= D50CAT.
IEF373I STEP /STEP006 / START 00222.1844
IEF374I STEP /STEP006 / STOP 00222.1844 CPU 0MIN 00.03SEC SRB 0MIN 00.00SEC
VIRT 12K SYS 232K
IEF236I ALLOC. FOR PRDJBGL5 STEP007
IEF237I 273 ALLOCATED TO SORTIN
IEF237I 26B ALLOCATED TO SORTOUT
IEF237I 263 ALLOCATED TO SYS00437
IEF237I 273 ALLOCATED TO SORTWK01
IEF237I 26B ALLOCATED TO SORTWK02
IEF237I 273 ALLOCATED TO SORTWK03
IEF237I JES2 ALLOCATED TO SYSPRINT
IEF237I JES2 ALLOCATED TO SYSOUT
IEF237I JES2 ALLOCATED TO SYSUDUMP
IEF237I JES2 ALLOCATED TO SYSIN
IEF142I PRDJBGL5 STEP007 - STEP WAS EXECUTED - COND CODE 0000
IEF285I SYS00222.T184351.RA000.PRDJBGL5.ZMN1 PASSED
IEF285I VOL SER NOS= WORK01.
IEF285I PRDJBGL.GDG.GRP08.G0024V00 CATALOGED
IEF285I VOL SER NOS= WORK02.
IEF285I CATALOG.USER KEPT
IEF285I VOL SER NOS= D50CAT.
IEF285I SYS00222.T184351.RA000.PRDJBGL5.R0000010 DELETED
IEF285I VOL SER NOS= WORK01.
IEF285I SYS00222.T184351.RA000.PRDJBGL5.R0000011 DELETED
IEF285I VOL SER NOS= WORK02.
IEF285I SYS00222.T184351.RA000.PRDJBGL5.R0000012 DELETED
IEF285I VOL SER NOS= WORK01.
IEF285I JES2.JOB03144.SO000123 SYSOUT
IEF285I JES2.JOB03144.SO000124 SYSOUT
IEF285I JES2.JOB03144.SO000125 SYSOUT
IEF285I JES2.JOB03144.SI000105 SYSIN
IEF373I STEP /STEP007 / START 00222.1844
IEF374I STEP /STEP007 / STOP 00222.1844 CPU 0MIN 00.33SEC SRB 0MIN 00.04SEC
VIRT 776K SYS 252K
IEF202I PRDJBGL5 STEP008 - STEP WAS NOT RUN BECAUSE OF CONDITION CODES
IEF272I PRDJBGL5 STEP008 - STEP WAS NOT EXECUTED.
IEF373I STEP /STEP008 / START 00222.1844
IEF374I STEP /STEP008 / STOP 00222.1844 CPU 0MIN 00.00SEC SRB 0MIN 00.00SEC
VIRT 0K SYS 0K
IEF202I PRDJBGL5 STEP009 - STEP WAS NOT RUN BECAUSE OF CONDITION CODES
IEF272I PRDJBGL5 STEP009 - STEP WAS NOT EXECUTED.
IEF373I STEP /STEP009 / START 00222.1844
IEF374I STEP /STEP009 / STOP 00222.1844 CPU 0MIN 00.00SEC SRB 0MIN 00.00SEC
VIRT 0K SYS 0K
IEF237I 273 ALLOCATED TO SYS00003
IEF285I SYS00222.T184451.RA000.PRDJBGL5.R0000003 KEPT
IEF285I VOL SER NOS= WORK01.
IEF285I SYS00222.T184351.RA000.PRDJBGL5.ZMN1 DELETED
IEF285I VOL SER NOS= WORK01.
IEF375I JOB /PRDJBGL5/ START 00222.1843
IEF376I JOB /PRDJBGL5/ STOP 00222.1844 CPU 0MIN 07.27SEC SRB 0MIN 00.33SECThe following notes relate to the lines in bold type in this sample run:
-
The Restart Decision message shows that the job was restarted at STEP003.
-
The CONTROLR step was added to this job. The parameters passed to the CONTROLR step are described in Table34.
Table 34 Parameters passed to CONTROLR step in sample restart
|
Parameter |
Description |
|---|---|
|
RR |
Indicates a real restart, not a simulation |
|
PRDJBGL5 |
Indicates the name of the control parameter member |
|
000BU |
Control-M order ID |
|
RL |
Indicates to Control-M/Restart to read all the SYSDATA of previous runs, and that the original job was not run on another node in an NJE network |
|
.STEP005 |
Indicates that the job restart begins from this PGMSTEP |
|
ACS |
Indicates that abend codes and condition codes are recaptured and step adjustment is performed, if necessary |
-
STEP008 and STEP009 have a condition code reference to a step that was not executed in the restart. Control-M/Restart captures the condition codes from the execution history.
-
Archived (compressed) SYSDATA of the previous run of the PRDJBGL5 job is dynamically allocated by the CONTROLR step. On this sample run, the name of this archived file starts with the prefix CTRSYS.JOBSDB.
-
Previous runs of the PRDJBGL5 job cataloged data set PRDJBGL5.GDG.GRP07.G0031V00 in STEP004 and data set PRDJBGL5.GDG.GRP08.G0023V00 in STEP005 before abending in STEP006. These data sets were uncataloged and deleted by Control-M/Restart.
-
In the current run, data set PRDJBGL5.GDG.GRP07.G0031V00 was created in STEP004 and data set PRDJBGL5.GDG.GRP08.G0023V00 was created in STEP005. The generations created in the restart have the same generation numbers as in the previous unsuccessful run.
-
Execution of STEP008 and STEP009 was bypassed correctly according to the condition code from STEP002, even though STEP002 itself was not executed during the restart run.
CONTROLR step messages
Figure 9 CONTROLR step messages – Example 1
18.43.53 CTR001I CONTROL-M/RESTART REL 6.1.00-980B STARTED FOR JOB PRDJBGL5
18.43.53 CTR008I PROCESSING PARAMETERS: RR,PRDJBGL5,000BU,RL,.STEP005,,ACSThe first message above indicates that Control-M/Restart restarted the job. The second message displays the restart parameters that were passed to the CONTROLR step.
Figure 10 CONTROLR step messages – Example 2
EXCLUDE DSN SYS1*
EXCLUDE DSN IPO1* The prefixes of data sets to be excluded from File Catalog and GDG Adjustment processing (as defined in the $DEFAULT or $EXCLUDE members) are listed (above).
Figure 11 CONTROLR step messages – Example 3
* THIS SUBSECTION CONTAINS DIRECT ACCESS DEVICE DEFINITIONS *
UNITNAME SYSDA DEVICE DASD
UNITNAME SYSALLDA DEVICE DASD
UNITNAME DISK DEVICE DASD
UNITNAME DIRECT DEVICE DASD
* THIS SUBSECTION CONTAINS UNIT RECORD DEVICE DEFINITIONS *
UNITNAME TAPE DEVICE TAPE
UNITNAME TAPEC DEVICE TAPE
UNITNAME CASSET DEVICE TAPE
UNITNAME TAPEHI DEVICE TAPE
UNITNAME TAPE* DEVICE TAPE The correspondence between generic unit names and device types are listed from the user-defined $DEFAULT member.
Figure 12 CONTROLR step messages – Example 4
DEFAULT UNITNAME TAPE DEVICE TAPE
DEFAULT UNITNAME TAPEHI DEVICE TAPE
.
.
.
DEFAULT UNITNAME 3350 DEVICE DASD
DEFAULT UNITNAME 3380 DEVICE DASD
DEFAULT UNITNAME 3390 DEVICE DASD
*
*PARAMETERS SPECIFIED USING ONLINE:
*
RECAPTURE ABEND CODE=YES/NO
RECAPTURE COND CODE=YES/NO
STEP ADJUSTMENT=YES/NO
*
SUMMARY OF PARAMETERS IN EFFECT:
*
RECAPTURE ABEND CODE=YES/NO
RECAPTURE COND CODE=YES/NO
STEP ADJUSTMENT=YES/NO
*
14.37.58 CTR059I =========== ANALYZE PHASE STARTED ===========
14.37.58 CTR041I DATASET WILL BE SCRATCHED FROM VOLUME "WORK01"
14.37.58 CTR042I DATASET WILL BE UNCATALOGED
14.37.58 CTR038I DSN=CTR.GEN.SAS.G0042V00 DD=SYSUT2 STEP=COPY PROCSTEP=
14.38.03 CTR060I ========== EXECUTION PHASE STARTED ==========
14.38.03 CTR085I DATASET "CTR.GEN.SAS.G0042V00" SCRATCHED FROM VOL=WORK01
14.38.03 CTR090I CORRECTING REFERENCE OF GDG DATASET TO "CTR.GEN.SAS.G0041V00"
FROM:
14.38.03 CTR038I DSN=CTR.GEN.SAS.G0042V00 DD=SYSUT2 STEP=COPY PROCSTEP=
14.38.03 CTR082I RESTARTING FROM STEP COPY . TO STEP STEP09 .
14.38.03 CTR003I RESTART OF JOB M0500012 ENDED SUCCESSFULLY Definitions of unit names are built into Control-M/Restart and need not be duplicated in either the $DEFAULT member or the member specifically named in the PARM field.
Some Control-M/Restart messages, including those listed above, are described in Table 35.
Table 35 Control-M/Restart Messages
|
Message |
Description |
|---|---|
|
CTR059I |
Control-M/Restart works in two phases. The first phase analyzes what is done. |
|
CTR060I |
The second phase actually executes the necessary adjustments (delete data sets, adjust generation numbers, and so on). |
|
CTR147I/CTR038I |
Control-M/Restart adjusts the generation number. |
|
CTR041I/CTR042I |
As part of the File Catalog and GDG Adjustment facility, the data set must be scratched and uncataloged. |
|
CTR043E/CTR038I |
A data set needed for restart does not exist. In this case the missing data set is a temporary data set that MVS deleted at the end of the previous unsuccessful run. Control-M/Restart determines a step from which restart can be successfully performed. |
|
CTR039I |
Control-M/Restart has determined that the job can be restarted from STEP003. |
|
CTR081I |
Control-M/Restart recaptured condition codes from the previous run of the job. |
|
CTR090I/CTR038I |
Control-M/Restart has corrected the generation numbers for GDG data sets. |
|
CTR085I/CTR087I |
The data set has been successfully scratched and uncataloged. |
|
CTR082I |
This message indicates the step range that the restarted job executes. |
|
CTR003I |
Control-M/Restart has completed the re-start of the job successfully. Of course, at this point the result of the execution of the restarted job is not known. |
Communities
Support Center
YouTube
Twitter
Facebook
LinkedIn