|
|
|
|
|
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.
Parent Topic |