Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Moving system data sets z/OS DFSMSdss Storage Administration SC23-6868-01 |
|
Some system data sets do not require movement, either because they are allocated during system generation or because they are built at IPL time. Other system data sets, however, can be moved by DFSMSdss for various reasons. Unless excluded, system data sets are copied. However, they generally remain open while the system is running and cannot be scratched or uncataloged because the DELETE and UNCATALOG options apply only to data sets not in use. Frequently, system data sets are prefixed with a high-level qualifier of SYS1. The PROCESS(SYS1) keyword can be used for a data set copy operation of a SYS1 data set to move it to a preallocated target or to copy it with the DELETE option. PROCESS(SYS1) does not apply to VTOCIX or VVDS. To limit the use of the PROCESS keyword, you need to set up a RACF® FACILITY class profile. For more information about RACF FACILITY class profiles, see z/OS Security Server RACF Security Administrator's Guide. Note: The PROCESS(SYS1) option does not lift the restrictions
on the processing of volume VVDSs or VTOC indexes.
When the
PROCESS(SYS1) keyword is not specified, you cannot move
system data sets the way you normally move data sets with DFSMSdss.
In order for DFSMSdss to move system data sets, you must do one of
the following:
When a data set copy operation
is used to copy the following data
sets, space is defined for the target data set but no data is copied:
|
Copyright IBM Corporation 1990, 2014
|