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.

DELETEDelete a Key-Sequenced VSAM Cluster in a Catalog: Example6In this example, a key-sequenced cluster is deleted. Alternate indexes and pathsrelated to the key-sequenced cluster are deleted automatically by access methodservices. <strong>Access</strong> method services will dynamically allocate the key-sequenced dataset so that the data can be overwritten (as specified by the ERASE option).//DELET1 JOB ...//STEP1 EXEC PGM=IDCAMS//DD1 DD VOL=SER=VSER02,UNIT=3380,DISP=OLD,// DSNAME=EXAMPLE.KSDS01//SYSPRINT DD SYSOUT=A//SYSIN DD *DELETE -EXAMPLE.KSDS1 -FILE(DD1)PURGE -ERASE -CATALOG(GGGUCAT2)/*The DELETE command deletes the key-sequenced VSAM cluster from theGGGUCAT2 catalog. Its parameters are:vvvvvEXAMPLE.KSDS1, which is a key-sequenced VSAM cluster, is the entryname ofthe object being deleted.FILE is not required but improves per<strong>for</strong>mance if specified.PURGE specifies that the cluster is to be deleted regardless of its retentionperiod or date.ERASE specifies that the cluster’s data component be overwritten with binaryzeros. If the NOERASE attribute was specified when the cluster was defined oraltered, this is ignored.CATALOG identifies the catalog, GGGUCAT2, containing the cluster’s entries.Delete Two Key-Sequenced Clusters in a Catalog: Example 7In this example, two key-sequenced clusters, EXAMPLE.KSDS01 andEXAMPLE.KSDS02, are deleted from a catalog. It shows how more than onecataloged object is deleted with a single DELETE command.//DELET3 JOB ...//STEP1 EXEC PGM=IDCAMS//SYSPRINT DD SYSOUT=A//SYSIN DD *DELETE -(EXAMPLE.KSDS01 -EXAMPLE.KSDS02) -PURGE -CLUSTER/*The DELETE command deletes the key-sequenced clusters EXAMPLE.KSD01 andEXAMPLE.KSD02. Both entries are dynamically allocated in order <strong>for</strong> theirrespective catalog recovery areas (CRA) to be updated. The parameters are:vvvEXAMPLE.KSDS01 and EXAMPLE.KSDS02 identify the objects to be deleted.These are the entrynames of two key-sequenced clusters.PURGE specifies that the cluster be deleted regardless of its retention period ordate.CLUSTER specifies that EXAMPLE.KSDS01 and EXAMPLE.KSDS02 identifycluster catalog records.230 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!