09.07.2015 Views

z/OS V1R6.0 DFSMS Access Method Services for Catalogs

z/OS V1R6.0 DFSMS Access Method Services for Catalogs

z/OS V1R6.0 DFSMS Access Method Services for Catalogs

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

ALTERSMS might not use candidate volumes <strong>for</strong> which you request specific volsers.Some user-specified volsers. <strong>for</strong> an SMS-managed data set can result in anerror. To avoid candidate volume problems with SMS, you can request thatSMS choose the given volser used <strong>for</strong> a candidate volume. To do this, you cancode an * <strong>for</strong> each volser that you request. If, however, you request bothspecified and unspecified volsers in the same command, you must enter thespecified volsers first in the command syntax.To ensure that the operation has completed correctly, the execution of ALTERREMOVEVOLUMES should be followed by a listing of the VTOC on the targetvolume. If ALTER REMOVEVOLUMES did not scratch any data sets allocatedto job steps, it can still complete with return code zero. Both the basic catalogstructure (BCS) and the VSAM volume data set (VVDS) might be allocated toanother job or TSO/E user. If so, these entities are not scratched, and anyfuture access method services commands that depend on ALTERREMOVEVOLUMES completing normally might be unsuccessful. To ensurethat the operation has completed correctly, follow the execution of ALTERREMOVEVOLUMES with a listing of the VTOC on the target volume.Exceptions:1. If a volume to be removed contains data that belongs to the entry beingaltered, the volume is not removed.2. Volume cleanup is not supported if the volume is SMS managed.Abbreviation: RVOLREUSE|NOREUSEControls setting the REUSE indicator <strong>for</strong> VSAM data sets. A data set thatrequires the REUSE attribute be changed to ″reusable″ cannot be an alternateindex nor can it have an associated alternate index. The data set also cannot bea key-sequenced data set (KSDS) with one or more key ranges.ROLLINIndicates whether an SMS-managed generation data set (GDS) is to berolled-in. The generation data set must be SMS managed and either in adeferred rolled-in state or a rolled-off state. For more in<strong>for</strong>mation about rollingin GDSs, see z/<strong>OS</strong> <strong>DFSMS</strong>: Using Data Sets <strong>for</strong> more in<strong>for</strong>mation.Abbreviation: ROLSCRATCH|N<strong>OS</strong>CRATCHSpecifies whether generation data sets, when they are uncataloged, are to beremoved from the VTOC of the volume where they reside.SCRATCHRemoves the data set’s <strong>for</strong>mat-1 DSCB from the VTOC so that the data setcan no longer be accessed, and, <strong>for</strong> SMS-managed data sets, the non-VSAMvolume record (NVR) is removed from the VVDS.Abbreviation: SCRN<strong>OS</strong>CRATCHIndicates that the data set’s <strong>for</strong>mat-1 DSCB is not to be removed from theVTOC and, <strong>for</strong> SMS-managed data sets, the NVR entry remains in theVVDS.Abbreviation: NSCRSHAREOPTIONS(crossregion[ crosssystem])Is used when a data or index component of a cluster, alternate index, or thedata component of a catalog can be shared among users. However,68 z/<strong>OS</strong> <strong>V1R6.0</strong> <strong>DFSMS</strong> <strong>Access</strong> <strong>Method</strong> <strong>Services</strong> <strong>for</strong> <strong>Catalogs</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!