Using DELETE with GDSs and non-VSAM data sets with dependent ALIASes
Generation data sets (GDSs) in a generation data group (GDG) base
object and non-VSAM objects and may have ALIASes, which are also dependent
objects, so you must consider your DELETE mask pattern carefully.
For example, a DELETE mask pattern of MASK NVSAM directed against
a set of GDSs results in the associated ALIASes for those GDSes
being deleted or scratched as well. The safe way to preserve a GDG
BASE, is to perform a DELETE NVSAM with a MASK pattern that
specifically identifies the GDSs. For example, for a UCAT A1, and
a GDG BASE called BASE1, the following command removes the GDSes
and all ALIASes associated with those GDSs:
DELETE A1.BASE1.G%%%%V00 MASK NVSAM You should delete GDG BASE objects with GENERATIONDATAGROUP and RECOVERY parameters specified.
User catalogs can be deleted by specifying both USERCATALOG and RECOVERY.
GDG base objects do not recognize SCRATCH, which is the default in a DELETE command specified with the MASK parameter. A MASK pattern which includes these objects without type-restrictions will have an implied SCRATCH option, resulting in an error.