- ALIAS| ALTERNATEINDEX| CLUSTER| GENERATIONDATAGROUP| LIBRARYENTRY| NONVSAM| NVR| PAGESPACE| PATH| TRUENAME| USERCATALOG| VOLUMEENTRY| VVR
the type of object or entry to be deleted. If the object to be deleted is a catalog, truename entry,
or VSAM volume record, USERCATALOG, TRUENAME, NVR, or VVR is required. If you delete a migrated data set without specifying the entry type, DFSMShsm will delete the data set without recalling it.
- specifies that the entry to be deleted is an alias entry.
- specifies that the object to be deleted is an
alternate index and its data and index entries. When a path entry is associated with the alternate
index, the path entry is also deleted.
When the alternate index has the to-be-upgraded attribute and it is the only such alternate index associated with the base cluster, the base cluster's upgrade-set entry is also deleted.
Exception: If RLS recovery is associated with the alternate index, all knowledge of the recovery is lost as part of the delete operation.
- specifies that the object to be deleted is
a cluster, its associated data and index entries, and any related paths and alternate indexes.
When deleting a VVDS, entryname must be the restricted name 'SYS1.VVDS.Vvolser'.
Exception: If RLS recovery is associated with the sphere, all knowledge of the recovery is lost as part of the delete operation.
- specifies that the entry to be deleted is a generation data group
(GDG) entry. To delete a generation data group that is not empty, you must specify either the FORCE
or the RECOVERY parameter. When FORCE is used, all SMS-managed generation data sets pointed to by
the GDG base are scratched. Generation data sets are also removed from the catalog when you use
For both SMS-managed and non-SMS-managed GDGs, if you use RECOVERY, the GDG entry is deleted from the catalog and generation data sets remain unaffected in the VTOC. To delete a GDG using RECOVERY or FORCE, you must specify both GENERATIONDATAGROUP and RECOVERY or GENERATIONDATAGROUP and FORCE.
The FORCE and RECOVERY generation data set parameters require RACF® FACILITY class authorization. For information concerning RACF authorization levels, see Security Authorization Levels.
- specifies that
the entry to be deleted is a tape library entry. You must specify the FORCE parameter to delete a
tape library entry that is not empty. A tape library entry is not empty when tape volume entries are
still associated with it.
To delete a tape library entry, you must have authorization to RACF FACILITY class profile STGADMIN.IGG.LIBRARY.
Because access method services cannot change the library manager inventory in an automated tape library, ISMF should be used for normal tape library delete functions. The access method services DELETE LIBRARYENTRY command should be used only to recover from volume catalog errors.
Abbreviation: LIBENTRYor LIBENT
- specifies that the entry to be
deleted is a cataloged non-VSAM data set entry or object entry.
If the non-VSAM data set has aliases that are defined using RELATE parameter, all of its ALIAS entries are deleted when you use the DELETE command.
If the non-VSAM data set has aliases that are defined using SYMBOLICRELATE parameter, the ALIAS entries are NOT deleted when you use the DELETE command. See z/OS DFSMS Managing Catalogs
If the non-VSAM data set is partitioned, you can delete one of its members by specifying pdsname(membername).
If the non-VSAM data set does not have an entry in a catalog, you can delete its format-1 DSCB from the VTOC by using the SCRATCH function of the IEHPROGM utility. See z/OS DFSMSdfp Utilities.
Use this parameter to delete generation data sets (GDSs). You can rerun the job step to reclaim a GDS that is in deferred roll-in state, if GDS reclaim processing is enabled (it is enabled by default). For more information about GDS reclaim processing, see z/OS DFSMSdfp Storage Administration.
SMS does not support temporary non-VSAM data sets.
Exception: You can use RACF commands to specify an ERASE attribute in a generic or discrete profile for a non-VSAM data set. Use of the attribute renders all allocated DASD tracks unreadable before space on the volume is made available for reallocation. Refer to the appropriate RACF publications for information about how to specify and use this facility.
- specifies that the
object to be deleted is an SMS-managed non-VSAM volume record (NVR) entry. This parameter must be
specified to delete an NVR from a VSAM volume data set (VVDS) and its corresponding record from the
VTOC. The NVR/VTOC entries are deleted only if the related non-VSAM object catalog entry does not
exist. Similar to DELETE VVR, the FILE parameter must specify the DD statement name that identifies the volume containing the VVDS. If you select a catalog through alias orientation or by use of the catalog parameter, it must match the catalog name in the isolated NVR (unless you have read authority to the RACF FACILITY class STGADMIN.IGG.DLVVRNVR.NOCAT).Note: If the DELETE NVR command is issued against a non-VSAM data set that is not SMS-managed, the DSCB for the data sets is SCRATCHed (deleted). If cataloged, the data set's entry is not deleted from the catalog.
- specifies that an
inactive page space is to be deleted. A page space is identified as
activeduring the operator's IPL procedure.
To delete a page space in an SMS-managed user catalog you must include the CATALOG parameter.
- specifies that a path entry is to be deleted. No entries associated with the path are deleted.
- specifies that the
object to be deleted is the truename entry for a data or index component of a cluster or alternate
index, or the name of an alternate index. This parameter must be specified to delete a truename
entry. The truename entry is deleted only if the associated base record is missing or is
- specifies that
the object to be deleted is a user catalog.
See the CATALOG(catname) parameter for deleting a specific catalog. Specify USERCATALOG only when you want to delete the entire CATALOG.
The catalog connector entry in the master catalog is deleted. If the user catalog has aliases, all the catalog's alias entries in the master catalog are deleted.
To delete a user catalog when it is empty (that is, it contains only its self-describing entries and its volume's VVDS entry), you must specify USERCATALOG. To delete a user catalog that is not empty, you must specify both USERCATALOG and FORCE.
If you are deleting the catalog as part of recovering from a backup copy, you might want to use the RECOVERY option instead. For more information, see the RECOVERY keyword.
You can set up your system so that when you specify RECOVERY with DELETE USERCATALOG, the system issues WTOR message IDC1999I requesting confirmation before deleting the user catalogs. Use the modify command to enable or disable this WTOR feature as follows:
F CATALOG,DISABLE(DELRECOVWNG). By default, the WTOR is disabled. See the MODIFY command in z/OS MVS System Commands.
- specifies that
the entry to be deleted is a tape library volume.
To delete a tape volume entry, you must have authorization to RACF FACILITY class profile STGADMIN.IGG.LIBRARY. Because access method services cannot change the library manager inventory in an automated tape library, ISMF should be used for normal tape library delete functions. The access method services DELETE VOLUMEENTRY command should be used only to recover from volume catalog errors.
Abbreviation: VOLENTRY or VOLENT
- specifies that the
objects to be deleted are one or more unrelated VSAM volume record (VVR) entries. To delete a VVR
from both the VSAM volume data set (VVDS) and from the VTOC, you must specify this parameter.
The VVR entry is deleted only if the related cluster or alternate-index data and index component catalog entries do not exist. When VVR is specified, the component name of the cluster or alternate-index to which the VVR was related must be specified in the entryname parameter. If you select a catalog through alias orientation or by use of the catalog parameter, it must match the catalog name in the isolated VVR (unless you have read authority to the RACF FACILITY class STGADMIN.IGG.DLVVRNVR.NOCAT).
The FILE parameter must specify the DD statement name that identifies the volume on which the VVDS resides.Note: If the catalog search order does not orient to the original catalog in the VVR, and the user does not have READ authority to STGADMIN.IGG.DLVVRNVR.NOCAT, in this case the master catalog name must be specified in the CATALOG parameter as follows.
- specifies the name
of the catalog that contains the entries to be deleted. See Catalog Search Order for DELETE for the
order in which catalogs are searched.
This parameter cannot be used to delete a user catalog, and is ignored when you delete members of a partitioned data set or the tape library entry.To specify catalog names for SMS-managed data sets, you must have authority from the RACF STGADMIN.IGG.DIRCAT FACILITY class. See Storage Management Subsystem (SMS) Considerations for more information.
- identifies the catalog that contains the entry to be deleted.
- specifies whether the components of a cluster or alternate index to be deleted are to be erased
(overwritten with binary zeros). This parameter overrides whatever was coded when the cluster or
alternate index was defined or last altered. Specify this parameter only when a cluster or an
alternate index entry is to be deleted. If you use ERASE, one of the following conditions must be true:
- The entry is in the master catalog.
- The qualifiers in the entry's qualified name are the catalog's name or alias.
- specifies that the
components are to be overwritten with binary zeros when the cluster or alternate index is deleted.
If ERASE is specified, the volume that contains the data component must be mounted.
If the cluster is protected by a RACF generic or discrete profile and the cluster is cataloged in a catalog, use RACF commands to specify an ERASE attribute as part of this profile so that the data component is automatically erased upon deletion.
- specifies that the
components are not to be overwritten with binary zeros when the cluster or alternate index is
NOERASE will not prevent the component from being erased if the cluster is protected by a RACF generic or discrete profile that specifies the ERASE attribute and the cluster is cataloged in a catalog. You can use RACF commands to alter the ERASE attribute in a profile.
- [EXCLUDE(entryname|mask key[ entryname|mask key...])
- Specifies up to 100 entry names or mask keys to be excluded from the list of entries produced by the MASK parameter of DELETE. This parameter is only valid with the MASK parameter.
- specifies the name of
the DD statement that identifies:
- The volume that contains a data set to be deleted with SCRATCH.
- The data set to be deleted if ERASE is specified.
- The partitioned data set from which a member (or members) is to be deleted.
- The volumes that contain VVDS entries for the objects cataloged.
- The VVDS volume that contains a VVR or NVR to be deleted.
Use of the FILE parameter improves the performance of the DELETE command.
When you delete a data set, the volume referred to in the DD statement must be the same as the volume referred to in the usercatalog.
If you do not specify FILE and VSAM requires access to a volume or volumes during the delete processing, VSAM tries to dynamically allocate the volumes. When the entryname is pdsname(membername) VSAM dynamically allocate the entire PDS rather then the pdsname(member).
When more than one volume is to be identified (for example, a multivolume data set), FILE identifies the DD statement that specifies all volumes. If in any of the above cases the volumes are of a different device type, use concatenated DD statements. All volumes that contain associations to a cluster being deleted must 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's catalog record before the scratch can be issued. This requires either all volumes to be mounted, online, and allocatable to the job, or the use of the FILE parameter specifying a DD statement allocating at least one mountable unit (not permanently resident or reserved). Deferred mount must be specified on the DD statement so that allocation will flag the UCB to allow remove/mount requests to be issued for the unit as required during delete processing. If access to the volumes cannot be provided, use DELETE NOSCRATCH to uncatalog the non-VSAM data set and the user will assume the responsibility of scratching the format-1 DSCBs from all the volumes. If RACF is installed, you must have access authority under RACF to specify DELETE NOSCRATCH.
When the FILE parameter points to a DD statement that has DISP=SHR the data 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 of IDCAMS may not work properly. Specifically, DEFINE, BLDINDEX, REPRO, and IMPORT may fail if these commands refer to the same DD name for output from those commands. This is because those commands will use volume and device-related information that may no longer be applicable. BLDINDEX, REPRO, and IMPORT should use the OUTDATASET keyword instead of OUTFILE to avoid this problem.
- specifies whether entries that are not empty should be deleted.
- lets you delete
generation data groups, tape library entries, and user catalogs 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:
If you delete a tape library entry using FORCE:
- Proper access authority to the RACF resource for catalog functions is necessary for DELETE GDG FORCE. The DELETE GDG FORCE function should not be used to redefine the GDG limit value. ALTER LIMIT should be used instead.
- The GDG entry is deleted even though it might point to non-VSAM entries in the catalog.
- Each SMS-managed non-VSAM data set entry pointed to by the GDG base entry is deleted before the GDG base entry is deleted. The non-VSAM data set is scratched.
- Each non-SMS-managed non-VSAM data set entry pointed to by the GDG base entry is deleted before the GDG base entry is deleted. However, the non-VSAM data set's space and contents on the volume are undisturbed.
- No VVDSs are deleted
- An IKJ56220I is possible when perform in DELETE GDG FORCE against a GDG with a large limit and GDSs with many candidate volumes. Similar to limitations imposed on concatenated data sets in a single DD, allocation of an entire GDG is dependent on the size of the TIOT. DELETE GDG FORCE is a unique command that requires allocation of all generation data sets under a GDG in order to perform the forced delete.
- The tape library entry is deleted even if tape volume entries are still associated with the specified tape library.
- Any tape volume entries associated with a deleted tape library entry will remain in the catalog for these tape volume entries.
If you delete a user catalog using FORCE:
Attention: The FORCE parameter deletes all clusters in the catalog.
- The user catalog is deleted even if it contains entries for objects that have not been deleted.
- All data sets cataloged in the user catalog as well as the catalog data set itself are deleted. All volumes on which these data sets reside must be included with the FILE parameter.
- All VSAM clusters are automatically deleted, but the contents of each cluster and alternate index are not erased. (If you specify FORCE, the ERASE parameter is ineffective.)
- SMS-managed non-VSAM data set entries in the user catalog are deleted and the data sets are scratched.
- Non-SMS-managed non-VSAM data set entries in the user catalog are deleted, but the data sets are not scratched. A non-SMS-managed non-VSAM data set can be located with its DSCB in the volume's VTOC.
- If you are using the XFACILIT class STGADMIN.IGG.DELAUDIT.catalogname to restrict deletion of data sets in the user catalog, those data sets to which the user does not have authority will not be deleted, but the user catalog will be deleted. The entries failing the delete will not be accessible until they are recataloged.
- causes the DELETE
command to end when you request the deletion of a generation data group, tape library entry, or user
catalog that is not empty.
- The MASK parameter specifies that the entryname is a filter key. The entryname or filter key
might contain mask characters such as *, ** or % and is used to search for entries to delete that
match the filter key.
- The MASK keyword cannot be specified with the following keywords:
- TRUENAME (TRUENAME)
- Non-VSAM Volume record (NVR)
- VSAM Volume Record (VVR)
- PDSE/PDS member data set
- Library Entry (LIBRARYENTRY)
- Tape Volume entry (VOLUMEENTRY)
The DELETE MASK command allows only one entry-name to be specified. If there are multiple entry-names specified, the request will fail with error messages.When you specify a filter key with the MASK operand, the following rules apply:
- An asterisk (*) represents 1 to 8 characters in a level of a catalog entry.
- Double asterisks (**) represents multiple qualifiers within a catalog entry. The double asterisks (**) must be preceded by a period, and the double asterisks can be followed by either a period or a blank.
- Percent sign (%) allows 1 to 8 percent signs (%) specified in each qualifier.
- The high level qualifier of the filter key must be fully qualified unless the CATALOG parameter is also supplied. In other words, the high level qualifier cannot contain a *, ** or %. ABC%.DATA.SET and **.DATA.SET and A*.DATA.SET are all examples of an invalid mask. If you want to specify names like ABC%.DATA.SET or **.DATA.SET or A*.DATA.SET where the high level qualifier is not fully qualified, you must also specify the CATALOG parameter.
- When using asterisk within a qualifier, this is considered as a mask entry name and a MASK keyword must be specified. Examples are 'A.B*.C', 'AB.CD*', 'AB.*CD.'.
- NOMASK is the default. With NOMASK the entryname can be fully qualified or a generic name. When
using a generic name, the asterisk(*) will only replace one single qualifier. Here are examples of how DELETE works using MASK, NOMASK or omitting the MASK or NOMASK parameter, given the following data sets.
1) AAA.BBB.AAA.DDD 2) AAA.BBB.CCC.DDD 3) AAA.BBB.CCC.DDD.EEE 4) AAA.BBB.CCC 5) BBB.DDD.AAC.BBC.EEE 6) BBB.DDD.ABC.BBC.EEE 7) BBB.DDD.ADC.BCCD.EEEE 8) CCC.GDG.BASE1 This entry is an empty GDG base. It has no entries 9) CCC.GDG.BASE2 This entry is not an empty GDG base. It has entries 10) CCC.GDG.BASE2.G0001V00 This is an entry that belongs to CCC.GDG.BASE2 11) CCC.GDG.BASE2.G0002V00 This is an entry that belongs to CCC.GDG.BASE2 12) CCC.GDG.FLAT.FILE This is a non-GDGWhen NOMASK or parameter is omitted, the following are the results:
DELETE AAA.* results in no data sets being deleted DELETE AAA.* NOMASK results in no data sets being deleted DELETE AAA.* MASK results in no data sets being deleted DELETE AAA.BBB.* results in the deletion of data set #4 DELETE AAA.BBB.* NOMASK results in the deletion of data set #4 DELETE AAA.BBB.*.DDD results in the deletion of data sets #1 and #2 DELETE AAA.BBB.* MASK results in the deletion of data set #4 DELETE AAA.BBB.*.DDD NOMASK results in the deletion of data sets #1 and #2 DELETE AAA.BBB.*.DDD.EEE results in the deletion of data set #3. DELETE AAA.BBB.*.DDD.EEE NOMASK results in the deletion of data set #3. DELETE AAA.BBB.AAA.DDD MASK results in the deletion of data sets #1 DELETE CCC.GDG.* results in the deletion of data set #9 and an error message is issued for data set #10, #11, and #12 because the base is not empty DELETE CCC.GDG.* NOMASK results in the deletion of data set #9 and an error message is issued for data set #10, #11, and #12 because the base is not empty DELETE CCC.GDG.BASE1 results in the deletion of data set #9 DELETE CCC.GDG.BASE1 NOMASK results in the deletion of data set #9 DELETE CCC.GDG.BASE2 results in the deletion of no data sets as the GDG base has entries. DELETE CCC.GDG.BASE2 NOMASK results in the deletion of no data sets as the GDG base has entries.When MASK is specified, the following are the results:
DELETE AAA.** MASK results in deletion of #1 #2 #3 and #4 DELETE BBB.DDD.** MASK results in deletion of #5 #6 #7 and #8 DELETE BBB.DDD.BBC.A%C.BBC.EEE MASK results in deletion of #5 #6 DELETE BBB.DDD.ADC.B%%%.EEEE MASK results in deletion of #7 #8 DELETE AAA.*.** MASK results in deletion of #1 to #4 DELETE BBB.DDD.A*.BBC.EEE MASK results in deletion of #5 #6 DELETE BBB.DDD.A*C.BBC.EEE MASK results in deletion of #5 #6 DELETE CCC.GDG.BASE2.* MASK results in deletion of #11 and #12 GDG DELETE CCC.GDG.BASE2.G%%%%V00 MASK results in deletion of #11 and #12 DELETE CCC.GDG.BASE2.G*V00 MASK results in deletion of #11 and #12 DELETE CCC.GDG.BASE2.G%%%%V00 MASK NVSAM results in deletion of #11 and #12 DELETE CCC.GDG.BASE2.G*V00 MASK NVSAM results in deletion of #11 and #12
- Use the NODISCONNECT parameter with the USERCATALOG parameter to retain alias information associated with the user catalog you are deleting. The catalog can then be redefined (DEFINE USERCATALOG) with the RECONNECT option to restore the saved alias information.
- specifies whether
the entry is to be deleted regardless of the retention period specified. If this parameter is used
for objects that do not have a date associated with them (for example, VVRs, aliases, and
non-SMS-managed non-VSAM data sets), the PURGE|NOPURGE parameter is ignored and the object is
deleted. This parameter cannot be used if a truename entry is to be deleted. PURGE must be specified to delete an OAM non-VSAM entry, because it has a never-expire retention.
- specifies that the
entry is to be deleted even if the retention period, specified in the TO or FOR parameter, has not
When deleting a tape library volume entry, PURGE must be specified if the volume's retention period has not expired.
PURGE works the same way for migrated objects as it does for non-migrated objects. PURGE overrides any DFSMShsm control over the deletion of VSAM base clusters and non-VSAM data sets. It causes the migrated data set to be deleted regardless of the expiration date.
- specifies that the
entry is not to be deleted if the retention period has not expired.
- specifies whether a user catalog, a VSAM volume data set (VVDS), or a generation data group
(GDG) is to be deleted in preparation for recovery.
- When RECOVERY is
specified and the entry name identifies a user catalog, the user catalog is to be replaced with an
imported backup copy. The user catalog, its VSAM volume record (VVR), and its VTOC entries are
deleted. The VVR and DSCBs, for each of the objects defined in the user catalog, are not deleted or
scratched. If the catalog is RACF-protected, alter authority is required.
VSAM must be able to read the VVDS or be able to process it as an ESDS for the function to complete successfully.
When RECOVERY is specified and entryname identifies a VVDS, the VVDS is unusable or inaccessible and must be rebuilt by deleting, redefining, and loading the appropriate VSAM data sets on the volume. The VVDS entry's DSCB will be scratched from the VTOC. The CATALOG parameter must contain the name of the master catalog when a VVDS is deleted with the RECOVERY parameter. If RACF protected, ALTER authority is required.
When RECOVERY is specified and the entry name identifies a GDG, the SMS-managed or non-SMS-managed GDG entry is deleted from the catalog and generation data sets remain unaffected in the VTOC.
If a VVDS contains a catalog entry or a system data set (SYS1.) entry that is cataloged in a master catalog, the VVDS catalog entry and the DSCB of the associated VVDS will not be removed.
If you delete a generation data group (DELETE GDG RECOVERY) using RECOVERY, proper authority to the RACF resource for catalog function is necessary.
See the USERCATALOG parameter for information about using RECOVERY with
- indicates that
the entry is to be processed as described by the other parameters specified.
- specifies whether a data set is to be removed from the VTOC of the volume on which it resides.
This parameter can be specified only for a cluster, an alternate index, a page space, or a non-VSAM
data set. Exception:
- The SCRATCH parameter is not applicable to tape library and tape volume entries because they have no VVDS or VTOC entries. IDCAMS DELETE will determine if the data set to be deleted is a tape data set and issue the NOSCRATCH option on the delete request. For a data set on tape, using the NONVSAM parameter with a fully qualified entryname might cause dynamic allocation of the data set, and therefore a tape mount. To avoid the tape mount in this situation, either specify NOSCRATCH or omit NONVSAM.
- If data set contains indirect or symbolic VOLSER, the scratch parameter will be ignored, if specified.
- specifies that a
data set is to be scratched from (removed from the VTOC of) the volume on which it resides. For VSAM
data sets and SMS-managed non-VSAM data sets, the VSAM volume data set (VVDS) entry is also removed.
DELETE SCRATCH will ignore any missing data set components (such as VVRs or F1 DSCBs) and will scratch all the data set parts that can be found at the time the request is issued.
When SCRATCH is specified for a VVDS, the VVDS is scratched and the catalog entry for the VVDS is removed. The VVDS must be empty.
If the catalog entry does not exist for a non-VSAM data set, you can use the SCRATCH function of the OS/VS IEHPROGM utility to remove the format-1 DSCB from the VTOC.If you select SCRATCH, one of the following statements must be true:
If you specify SCRATCH when deleting a non-VSAM data set defined with an esoteric device type, SYSDA for example, the DELETE will be unsuccessful under the following circumstances:
- The entry is in the master catalog.
- One or more of the qualifiers in the entry's qualified name is the same as the catalog's name or alias.
- The FILE parameter is specified.
Note: If the VVDS indicates that the data set is owned by a catalog other than that catalog identified through the usual catalog search order for DELETE, a DELETE NOSCRATCH is done against the catalog that resulted from the catalog search, and a zero return code is returned to the user. For example, if you specify a DELETE SCRATCH command against a data set in Catalog A, and the VVDS indicates that the data set is owned by Catalog B, a DELETE NOSCRATCH operation is done against Catalog A, and the data set remains intact and accessible from Catalog B. See Catalog Search Order for DELETE for information on the catalog search order for DELETE.
- Input/output configuration is changed resulting in addition or deletion of one or more esoteric device types.
- The esoteric device type definitions on the creating and using systems do not match when the catalog is shared between the two systems.
- specifies that
the catalog entry is to be deleted from the catalog without mounting the volume that contains the
object defined by the entry. VVDS and VTOC entries are not deleted.
If RACF is installed, you must have access authority under RACF to specify NOSCRATCH. With proper authority, DELETE NOSCRATCH is allowed on SMS-managed VSAM and non-VSAM data sets, thus deleting the BCS entry in the catalog without accessing the VVDS or VTOC.Attention:
- DELETE NOSCRATCH can result in uncataloged SMS-managed data sets.
- DELETE NOSCRATCH cannot be issued against a VSAM data set which is currently open.
NOSCRATCH removes the catalog entry for a VVDS. This entry can be reinstated with DEFINE RECATALOG. If the volume is mounted and usable, the VVDS is checked to ensure that the catalog entry being removed has no data sets in the VVDS. If the catalog entry indicates there are data sets in the VVDS, the VVDS's VSAM volume control record (VVCR) is removed and the catalog entry for the VVDS is removed.
If the volume is mounted and you specify NOSCRATCH for a VSAM volume data set (VVDS), the catalog entry for the VVDS is removed, and the catalog back pointer in the VSAM volume control record (VVCR) is removed.You should specify NOSCRATCH for the following:
- If the format-1 DSCB of a non-VSAM data set has already been scratched from the VTOC.
- If you are deleting a non-VSAM data set that was defined with a device type named by the user (for example, SYSDA) and the device type is not valid.
- If the object is defined in a catalog and you want to recatalog the object in the same catalog.
- After you convert a volume, the names of catalogs owning data sets on the volume will still be in the VVCR. Only catalogs that reside on the converted volume need to have their names in the VVCR. You can remove unneeded catalog names from the VVCR by using DELETE VVDS NOSCRATCH with the CATALOG parameter referencing the catalog to be deleted from the VVCR. For coexistence, an error indication is still returned if there are VVR or NVRs on the volume for the referenced catalog.
- NOSCRATCH affects the DFSMShsm delete function interaction for VSAM base clusters and non-VSAM data sets. It causes the migrated data set to be recalled because a migrated data set cannot be uncataloged.
- Specifies that the catalog entries selected by the DELETE command with the MASK parameter should be displayed and not deleted. This parameter is only valid with the MASK parameter.