CDS ENABLE DSN(ACS.DBASENEW) NEWLOC

Note: TSO 3.2 may create a single extent data set even when no secondary quantity is specified.

It is not necessary to initialize the CDS copy, that is, you do not have to execute SLICREAT or copy another CDS copy to the new data set.

Assume that ACS.DBASECPY has been disabled and deleted (or uncataloged), and ACS.DBASENEW has been allocated and cataloged. The following command enables the renamed and relocated CDS:

CDS ENABLE DSN(ACS.DBASENEW) NEWLOC

Note: MVS uses catalog services to resolve the volume and unit definitions, if not specified.

If a rename or relocate operation fails, CDS definitions are restored to what they were before the command was issued. Users must modify CDSDEF control statements to keep them consistent with the active CDS.

Relocating an Uncataloged CDS Copy

Assume that ACS.DBASECPY has been disabled and deleted (or uncataloged), and ACS.NOTCATLG has been allocated and cataloged. The following command relocates an uncataloged CDS copy:

CDS ENABLE DSN(ACS.NOTCATLG) NEWVOL(HSC001),NEWUNIT(ABC)

Users must modify CDSDEF control statements to make them consistent with the CDS definitions in this command. If a rename or relocate operation fails, CDS definitions are restored to what they were before the command was issued.

Note: The NEWVOL and NEWUNIT parameters are required for VM.

Expanding a CDS - Scenario

Before expanding all CDSs, each CDS must be disabled one at a time and created with a larger space allocation in the JCL. Then, all CDS copies must be enabled before issuing the following command:

CDS EXPAND

Chapter 2. Host Software Component Functions 55

1st ed., 6/30/04 - 312579601

Page 85
Image 85
StorageTek 6 Relocating an Uncataloged CDS Copy, Expanding a CDS - Scenario, Cds Enable Dsnacs.Dbasenew Newloc, Cds Expand