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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

DELETEv If data set contains indirect or symbolic VOLSER, the scratch parameter willbe ignored, if specified.SCRATCHspecifies that a data set is to be scratched from (removed from the VTOCof) the volume on which it resides. For VSAM data sets and SMS-managednon-VSAM data sets, the VSAM volume data set (VVDS) entry is alsoremoved.When SCRATCH is specified <strong>for</strong> a VVDS, the VVDS is scratched and thecatalog entry <strong>for</strong> the VVDS is removed. The VVDS must be empty.If the catalog entry does not exist <strong>for</strong> a non-VSAM data set, you can usethe SCRATCH function of the <strong>OS</strong>/VS IEHPROGM utility to remove the<strong>for</strong>mat-1 DSCB from the VTOC.If you select SCRATCH, one of the following statements must be true:vvvThe entry is in the master catalog.One or more of the qualifiers in the entry’s qualified name is the sameas the catalog’s name or alias.The FILE parameter is specified.If you specify SCRATCH when deleting a non-VSAM data set defined withan esoteric device type, SYSDA <strong>for</strong> example, the DELETE will beunsuccessful under the following circumstances:vvInput/output configuration is changed resulting in addition or deletionof one or more esoteric device types.The esoteric device type definitions on the creating and using systemsdo not match when the catalog is shared between the two systems.Note: If the VVDS indicates that the data set is owned by a catalog otherthan that catalog identified through the usual catalog search order <strong>for</strong>DELETE, a DELETE N<strong>OS</strong>CRATCH is done against the catalog that resultedfrom the catalog search, and a zero return code is returned to the user. Forexample, if you specify a DELETE SCRATCH command against a data setin Catalog A, and the VVDS indicates that the data set is owned byCatalog B, a DELETE N<strong>OS</strong>CRATCH operation is done against Catalog A,and the data set remains intact and accessible from Catalog B. See “CatalogSearch Order <strong>for</strong> DELETE” on page 11 <strong>for</strong> in<strong>for</strong>mation on the catalogsearch order <strong>for</strong> DELETE.Abbreviation: SCR226 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>N<strong>OS</strong>CRATCHspecifies that the catalog entry is to be deleted from the catalog withoutmounting the volume that contains the object defined by the entry. VVDSand VTOC entries are not deleted.If RACF is installed, you must have access authority under RACF tospecify N<strong>OS</strong>CRATCH. With proper authority, DELETE N<strong>OS</strong>CRATCH isallowed on SMS-managed VSAM and non-VSAM data sets, thus deletingthe BCS entry in the catalog without accessing the VVDS or VTOC.Attention DELETE N<strong>OS</strong>CRATCH can result in uncataloged SMS-manageddata sets.N<strong>OS</strong>CRATCH removes the catalog entry <strong>for</strong> a VVDS. This entry can bereinstated with DEFINE RECATALOG. If the volume is mounted andusable, the VVDS is checked to ensure that the catalog entry being

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

Saved successfully!

Ooh no, something went wrong!