DELETE Parameters. IBM z/OS Version 2 Release 3

PDF

เอกสาร

โฆษณา

Chapter 20. DELETE

The DELETE command deletes catalogs, VSAM data sets, non-VSAM data sets, and objects. The syntax of the DELETE command is:

Command

DELETE

Parameters

(

entryname[ entryname ...])

[ALIAS|

ALTERNATEINDEX|

CLUSTER|

GENERATIONDATAGROUP|

LIBRARYENTRY|

NONVSAM|

NVR|

PAGESPACE|

PATH|

TRUENAME|

USERCATALOG|

VOLUMEENTRY|

VVR]

[ERASE|NOERASE]

[FILE(

ddname)]

[FORCE|NOFORCE]

[MASK|NOMASK]

NODISCONNECT

[PURGE|NOPURGE]

[RECOVERY|NORECOVERY]

[SCRATCH|NOSCRATCH]

[CATALOG(

catname)]

For VSAM RLS recoverable data sets, DELETE CLUSTER removes all pending recovery information for the sphere.

Recommendation:

Do not delete any entryname for which there is any activity on any system in the sysplex, that is, active units of recovery, commits or back outs.

Before deleting any entryname for which there is currently no activity but for which there are shunted log records, use the SHCDS PURGE command to clear the owed sync point (commit or back out). Otherwise, when the sync point is eventually retried, it will fail. In addition, you might receive unpredictable results on a future backout if a data set with the same name is later created.

DELETE can be abbreviated: DEL

DELETE Parameters

The DELETE command uses the following parameters.

Required Parameters

(entryname[ entryname...]) names the entries to be deleted. If you want to delete more than one entry, you

229

DELETE

| must enclose the list of entrynames in parentheses. The maximum number of entrynames you can specify is 100. You can code a generic name to delete multiple entries with one entryname. For example, GENERIC.*.BAKER is a generic name where * is any 1-to-8 character simple name. If you specify a generic name on the LEVEL keyword, only one qualifier can replace an asterisk (*). This applies when you either explicitly specify or default to

NOMASK.

When you specify the MASK keyword, you can specify only one entryname, which is then considered a filter key. A filter key is an expanded generic name that allows for more versatile generic characters. The system only honors a filter key when the MASK keyword is specified in the DELETE command.

(NOMASK is the default.)

If you specify entry names that include the following generics, the system considers them filter keys and so they can only be used when you specify

MASK: v Double asterisks (**), which represent multiple qualifiers within a data set name v Percent signs (%), which represents one to eight percent characters within a qualifier v An asterisk within a qualifier

For additional information on using MASK or NOMASK keyword see

“Optional Parameters” on page 232.

If you are deleting a member of a non-VSAM partitioned data set, you must specify entryname in the format: pdsname(membername). The membername can contain wild card charaters %, and * to DELETE more than one members at a time.

The partitioned data set name directory is read to obtain a list of members, and each member in the list is filtered using the membername with the wildcard.

If a member name or alias name in the list matches the filter criteria, the member or alias is deleted. If the data set is a PDSE and the member name matches the criteria, the member and all aliases are deleted; if the data set is a

PDS, only the aliases matching the filter criteria are deleted.

If you specify the entryname in the format of a partition data set, pdsname(*) or

pdsname(**) , the command deletes all the members in the partition data set. If the partitioned data set is not a PDSE, the directory is reinitailized when using

pdsname(*), but not for pdsname(**).

If you are deleting a non-VSAM data set that was defined by coding

DEVICETYPES(0000) and VOLUMES(******), then DELETE only uncatalogs the data set. It does not scratch the data set from the SYSRES volume.

In a TSO environment, when specifying the MASK parameter, the entryname is considered to be a string for the mask. Therefore, the UserID is not prefixed to the entryname as is normally done for other TSO DELETEs.

Using DELETE with the MASK Filter Option

When you use DELETE with the MASK filter option, the command extends across multiple levels of qualifiers as well as across multiple catalogs.

Using DELETE with MASK for Dependent Cluster Objects:

Consider the following when deleting dependent objects when using generic MASK filtering:

230

z/OS DFSMS Access Method Services Commands

DELETE

v If you specify a base CLUSTER mask pattern, the command will delete all associated AIXs and PATHs. Any subsequent AIX or PATH specification via

MASK will result in a CC=8 not found because the objects have already been deleted.

v If you specify an AIX mask pattern on your DELETE, it will delete all PATHs associated between this AIX and its base CLUSTER. Any subsequent PATH specified in a generic delete results in a CC=8 because the PATH has been deleted already.

v When deleting objects with dependent objects, consider the sequence of DELETE commands carefully.

Based on these considerations, we recommend the following: v To DELETE all CLUSTER objects, restrict the MASK pattern to CLUSTER objects, which deletes all associated AIX and PATH objects as well.

If you want to DELETE just the PATH objects, restrict the MASK pattern to the

PATH subtype. Any subsequent AIX or CLUSTER MASK DELETE will then successfully delete AIX and CLUSTER objects.

v To DELETE AIXs after deleting PATH objects, restrict the MASK pattern to the

AIX subtype.

Using a MASK pattern for Objects other than CLUSTER, NONVSAM, and

GDS:

Using DELETE with a MASK pattern will delete only CLUSTER,

NONVSAM, and GDS (Generation Data Set) objects. To delete other objects, you must specify a type parameter, such as PATH or AIX. When you use a type to restrict the objects to delete, IBM suggests that you specify a DELETE with dependent objects first, then their base objects - this avoids possible conflicts with objects already deleted. For example, v

To DELETE PATH objects, do so with MASK and PATH type restrict parameter.

You can then issue a DELETE with an AIX parameter, and finally issue a

DELETE with a CLUSTER parameter. If you issue the first DELETE with

CLUSTER, the command deletes all three sets of objects underneath the matching cluster.

v To delete a GDG BASE and its GDSes, first issue a DELETE with MASK for the

GDSs only using a NONVSAM parameter and then delete the GDG BASEs with a GENERATIONDATAGROUP parameter.

Using DELETE with MASK in a TSO environment:

In a TSO environment, an

entryname is considered to be a string for the mask. Therefore, the userID is not prefixed to the entryname as is normally done for other TSO DELETEs.

Deleting GDS objects:

When you delete GDS objects under a GDG base using a

MASK pattern, note that the GDS might not be in ascending numeric sequence. See

Chapter 2, “Modal Commands,” on page 17 for more information.

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

Chapter 20. DELETE

231

DELETE

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.

Deleting USERCATALOG objects:

v You cannot specify both MASK and FORCE with a USERCATALOG object because FORCE is not supported with a generic DELETE and USERCATALOG.

Instead, specify RECOVERY, which is allowed for both MASK and NOMASK

DELETE of USERCATALOGs. FORCE is not supported because it would enable anyone to DELETE an unlimited amount of USERCATALOGs in one statement, leaving no way to recover the data other than system back-up.

v User catalog 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.

Optional Parameters

specifies 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.

ALIAS

specifies that the entry to be deleted is an alias entry.

ALTERNATEINDEX

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.

Abbreviation:

AIX

CLUSTER

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.

Abbreviation:

232

z/OS DFSMS Access Method Services Commands

DELETE

GENERATIONDATAGROUP

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 FORCE.

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 Appendix A, “Security Authorization Levels,” on page 385.

Abbreviation:

GDG

LIBRARYENTRY

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

NONVSAM

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.

Chapter 20. DELETE

233

DELETE

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.

Abbreviation:

NVSAM

NVR

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.

PAGESPACE

specifies that an inactive page space is to be deleted. A page space is identified as “active” during the operator's IPL procedure.

To delete a page space in an SMS-managed user catalog you must include the CATALOG parameter.

Abbreviation:

PGSPC

PATH

specifies that a path entry is to be deleted. No entries associated with the path are deleted.

TRUENAME

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 inaccessible.

Abbreviation:

TNAME

USERCATALOG

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

234

z/OS DFSMS Access Method Services Commands

DELETE

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,ENABLE(DELRECOVWNG) or F CATALOG,DISABLE(DELRECOVWNG). By default, the WTOR is disabled. See the MODIFY command in z/OS MVS

System Commands.

Abbreviation:

UCAT

VOLUMEENTRY

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:

VOLENTRYor VOLENT

VVR

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.

CATALOG(catname) specifies the name of the catalog that contains the entries to be deleted. See

“Catalog Search Order for DELETE” on page 11 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” on page 2 for more

information.

catname

identifies the catalog that contains the entry to be deleted.

Chapter 20. DELETE

235

DELETE

Abbreviation:

CAT

ERASE|NOERASE

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: v The entry is in the master catalog.

v The qualifiers in the entry's qualified name are the catalog's name or alias.

ERASE

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.

Abbreviation:

ERAS

NOERASE

specifies that the components are not to be overwritten with binary zeros when the cluster or alternate index is deleted.

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.

Abbreviation:

NERAS

FILE(ddname) specifies the name of the DD statement that identifies: v The volume that contains a data set to be deleted with SCRATCH.

v The data set to be deleted if ERASE is specified.

v The partitioned data set from which a member (or members) is to be deleted.

The volumes that contain VVDS entries for the objects cataloged.

v 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.

236

z/OS DFSMS Access Method Services Commands

DELETE

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.

FORCE|NOFORCE

specifies whether entries that are not empty should be deleted.

FORCE

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: v 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.

v The GDG entry is deleted even though it might point to non-VSAM entries in the catalog.

v 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.

v 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.

v No VVDSs are deleted v 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.

If you delete a tape library entry using FORCE:

Chapter 20. DELETE

237

DELETE

v 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.

v The user catalog is deleted even if it contains entries for objects that have not been deleted.

v 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.

v 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.) v SMS-managed non-VSAM data set entries in the user catalog are deleted and the data sets are scratched.

v 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.

Abbreviation:

FRC

NOFORCE

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.

Abbreviation:

NFRC

MASK|NOMASK

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.

MASK

The MASK keyword cannot be specified with the following keywords: v TRUENAME (TRUENAME) v Non-VSAM Volume record (NVR) v VSAM Volume Record (VVR) v

PDSE/PDS member data set v Library Entry (LIBRARYENTRY) v 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: v An asterisk (*) represents 1 to 8 characters in a level of a catalog entry.

v 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.

v Percent sign (%) allows 1 to 8 percent signs (%) specified in each qualifier.

238

z/OS DFSMS Access Method Services Commands

DELETE

v 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.

v 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.'.

See Catalog Search Interface User's Guide in z/OS DFSMS Managing

Catalogs for more information regarding data set name filter keys.

NOMASK

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

8) BBB.DDD.ADC.BCCD.EEEE

9) CCC.GDG.BASE1

10) CCC.GDG.BASE2

11) CCC.GDG.BASE2.G0001V00

12) CCC.GDG.BASE2.G0002V00

13) CCC.GDG.FLAT.FILE

This is a empty GDG base, no entries

This GDG base is not empty, it has entries

Entry belonging to CCC.GDG.BASE2

this is a non-GDG

When NOMASK or parameter is omitted

, the following are the results:

DELETE AAA.*

DELETE AAA.* NOMASK

DELETE AAA.* MASK

DELETE AAA.BBB.*

DELETE AAA.BBB.* NOMASK

DELETE AAA.BBB.*.DDD

results in no data sets being deleted results in no data sets being deleted results in no data sets being deleted results in the deletion of data set #4 results in the deletion of data set #4 results in the deletion of data sets #1 and #2

DELETE AAA.BBB.* MASK

DELETE AAA.BBB.*.DDD NOMASK

DELETE AAA.BBB.*.DDD.EEE

DELETE AAA.BBB.*.DDD.EEE NOMASK

DELETE AAA.BBB.AAA.DDD MASK

DELETE CCC.GDG.*

DELETE CCC.GDG.* NOMASK

DELETE CCC.GDG.BASE1

results in the deletion of data set #4 results in the deletion of data sets #1 and #2 results in the deletion of data set #3.

results in the deletion of data set #3.

results in the deletion of data sets #1 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 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 results in the deletion of data set #9

DELETE CCC.GDG.BASE1 NOMASK

DELETE CCC.GDG.BASE2

DELETE CCC.GDG.BASE2 NOMASK results in the deletion of data set #9 results in the deletion of no data sets as the GDG base has entries.

results in the deletion of no data sets as the GDG base has entries.

When MASK is specified

, the following are the results:

Chapter 20. DELETE

239

DELETE

DELETE AAA.** MASK

DELETE BBB.DDD.** MASK

DELETE BBB.DDD.BBC.A%C.BBC.EEE MASK

DELETE BBB.DDD.ADC.B%%%.EEEE MASK

DELETE AAA.*.** MASK

DELETE BBB.DDD.A*.BBC.EEE MASK

DELETE BBB.DDD.A*C.BBC.EEE MASK

DELETE CCC.GDG.BASE2.* MASK results in deletion of #1 #2 #3 and #4 results in deletion of #5 #6 #7 and #8 results in deletion of #5 #6 results in deletion of #7 #8 results in deletion of #1 to #4 results in deletion of #5 #6 results in deletion of #5 #6 results in deletion of #11 and #12 GDG

DELETE CCC.GDG.BASE2.G%%%%V00 MASK

DELETE CCC.GDG.BASE2.G*V00 MASK

DELETE CCC.GDG.BASE2.G%%%%V00 MASK NVSAM

DELETE CCC.GDG.BASE2.G*V00 MASK NVSAM results in deletion of #11 and #12 results in deletion of #11 and #12 results in deletion of #11 and #12 results in deletion of #11 and #12

NODISCONNECT

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.

PURGE|NOPURGE

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.

PURGE

specifies that the entry is to be deleted even if the retention period, specified in the TO or FOR parameter, has not expired.

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.

Abbreviation:

PRG

NOPURGE

specifies that the entry is not to be deleted if the retention period has not expired.

Abbreviation:

NPRG

RECOVERY|NORECOVERY

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.

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.

240

z/OS DFSMS Access Method Services Commands

DELETE

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

Abbreviation:

RCVRY

NORECOVERY

indicates that the entry is to be processed as described by the other parameters specified.

Abbreviation:

NRCVRY

SCRATCH|NOSCRATCH

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

: v 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.

v If data set contains indirect or symbolic VOLSER, the scratch parameter will be ignored, if specified.

SCRATCH

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.

Chapter 20. DELETE

241

DELETE

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: v The entry is in the master catalog.

v One or more of the qualifiers in the entry's qualified name is the same as the catalog's name or alias.

v The FILE parameter is specified.

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: v Input/output configuration is changed resulting in addition or deletion of one or more esoteric device types.

v The esoteric device type definitions on the creating and using systems do 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 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” on page 11 for information on the catalog

search order for DELETE.

Abbreviation:

SCR

NOSCRATCH

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:

v DELETE NOSCRATCH can result in uncataloged SMS-managed data sets.

v DELETE NOSCRATCH cannot be issued against a VSAM data set which is currently open.

For more information on cloning zFS, see the VOLUMES parameter in

Access Method Services DEFINE CLUSTER command.

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.

242

z/OS DFSMS Access Method Services Commands