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

DELETEallocate the entry name. Dynamic allocation requires that the volumes bemounted as permanently resident or reserved.When more than one volume is to be identified (for example, a multivolumedata set), FILE identifies the DD statement that specifies all volumes. If in anyof the above cases the volumes are of a different device type, use concatenatedDD statements. All volumes that contain associations to a cluster being deletedmust also be included on the DD statement referenced by the FILE parameter.When deleting multivolume non-VSAM data sets with the SCRATCH option,DELETE SCRATCH processing requires access to each volume in the entry’scatalog record before the scratch can be issued. This requires either all volumesto be mounted, online, and allocatable to the job, or the use of the FILEparameter specifying a DD statement allocating at least one mountable unit(not permanently resident or reserved). Deferred mount must be specified onthe DD statement so that allocation will flag the UCB to allow remove/mountrequests to be issued for the unit as required during delete processing. If accessto the volumes cannot be provided, use DELETE NOSCRATCH to uncatalogthe non-VSAM data set and the user will assume the responsibility ofscratching the format-1 DSCBs from all the volumes. If RACF is installed, youmust have access authority under RACF to specify DELETE NOSCRATCH.When the FILE parameter points to a DD statement that has DISP=SHR thedata set can be deleted when allocated to another user, but is not open.The use of this DD name in subsequent commands in the same invocation ofIDCAMS may not work properly. Specifically, DEFINE, BLDINDEX, REPRO,and IMPORT may fail if these commands refer to the same DD name foroutput from those commands. This is because those commands will usevolume and device-related information that may no longer be applicable.BLDINDEX, REPRO, and IMPORT should use the OUTDATASET keywordinstead of OUTFILE to avoid this problem.FORCE|NOFORCEspecifies whether entries that are not empty should be deleted.FORCElets you delete generation data groups, tape library entries, and usercatalogs without first ensuring that these entries are empty.Attention: The FORCE parameter deletes all clusters in the catalog.If you delete a generation data group using FORCE:vvvvProper access authority to the RACF resource for catalog functions isnecessary for DELETE GDG FORCE. The DELETE GDG FORCE functionshould not be used to redefine the GDG limit value. ALTER LIMITshould be used instead.The GDG entry is deleted even though it might point to non-VSAMentries in the catalog.Each SMS-managed non-VSAM data set entry pointed to by the GDGbase entry is deleted before the GDG base entry is deleted. Thenon-VSAM data set is scratched.Each non-SMS-managed non-VSAM data set entry pointed to by theGDG base entry is deleted before the GDG base entry is deleted.However, the non-VSAM data set’s space and contents on the volumeare undisturbed.If you delete a tape library entry using FORCE:Chapter 20. DELETE 223