CC initialization includes the time DFSMSdss spends filtering data sets. Therefore, the more precisely you specify the data sets to be processed, the sooner the initialization is completed and the sooner you can update your data again. Here are some ways to reduce initialization time:

• Keep data to be dumped by one DUMP command cataloged in one catalog, if possible.
• Do not specify the DYNALLOC keyword if you do not need dynamic allocation for your data sets.
• Specify fully or almost fully qualified data set names. This reduces the amount of time that DFSMSdss spends searching the catalogs for data sets to process.
• Specify smaller groups of data sets to process together in a DFSMSdss operation.
• Minimize the use of wildcards with the INCLUDE keyword.
• Minimize the use of sophisticated BY filtering to determine the data to be processed.
• Ensure that DFSMSdss can obtain serialization on all data sets being processed.
• Specify WAIT(0,0) to prevent DFSMSdss from waiting for serialization when it cannot be obtained.
• Do not specify the NOTIFYCONCURRENT keyword if you do not need notification of each data set included in the CC session.
• Do not specify the SPHERE keyword if you are not processing VSAM spheres.
• Use the ADMINISTRATOR keyword or DASDVOL RACF® protection (where applicable) to bypass authorization checks for each data set being processed.
• Ensure that the volumes containing the VTOC and catalog entries for the data sets to be processed have caching enabled. Also ensure that the catalogs involved are enabled for the in-storage cache (ISC) or the catalog data space cache (CDSC).
• Ensure that data sets being processed have not been migrated by DFSMShsm.

CC uses storage in the control unit cache and in the processor. Here are some ways to minimize the storage needed:

• Limit the amount of data included in the CC operation.
• Use CC during periods of low update activity (as most backups are currently done today).
• Concentrate the update activity in a subset of the data being processed by CC.