z/OS DFSMS Access Method Services Commands
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Optional Parameters

z/OS DFSMS Access Method Services Commands
SC23-6846-01

CATALOG(catname)
identifies the catalog in which the non-VSAM data set, or OAM object is to be defined. See Catalog Selection Order for DEFINE for the order in which a catalog is selected when the catalog's name is not specified.
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.
catname/alias
Names the catalog or an alias that can be resolved to a catalog. For example, if alias ABCD relates to catalog SYS1.USERCAT, then specifying either ABCD or SYS1.USERCAT will cause the entry to be defined in SYS1.USERCAT.

Abbreviation: CAT

If the catalog's volume is physically mounted, it is dynamically allocated. Mount the volume as permanently resident or reserved.

COLLECTION
specifies that the entry being defined is an Object Access Method (OAM) entry. This parameter is required when you define an OAM entry. If you use COLLECTION, you must also specify the RECATALOG parameter.

Abbreviation: COLLN

FILESEQUENCENUMBERS(number[ number...])
specifies the file sequence number of the non-VSAM data set being defined. FILESEQUENCENUMBERS is not applicable for an OAM non-VSAM entry and is ignored if specified.

This number indicates the position of the file being defined with respect to other files on the tape. If the data set spans volumes or if more than one volume is specified, you must specify a file sequence number for each volume. Either 0 or 1 indicates the first data set on the tape volume. The default is 0.

Abbreviation: FSEQN

OWNER(ownerid)
identifies the owner of the non-VSAM data set, or OAM object.
RECATALOG|NORECATALOG
specifies whether the catalog entries for the non-VSAM data set are to be re-created or are to be created for the first time. If RACF is installed, RACF access authority, defined under SMS, is required.

Exception: If OWNER is not specified, the TSO userid is the default ownerid.

RECATALOG
specifies that the catalog entries are re-created if valid VVDS entries are found on the primary VVDS volume. If valid VVDS entries are not found on the primary VVDS volume, the command ends. RECATALOG can be specified only for an SMS-managed data set.

Catalog entries can be re-created only in the catalog specified in the NVR except for entries that are swap space, page space, or SYS1 data sets. In a multihost environment, non-SYS1 IPL data sets that are SMS-managed cannot be recataloged to a different catalog from the one specified in the NVR. SMS-managed IPL data sets must be SYS1 data sets to be shared in a multihost environment.

The VOLUMES and DEVICETYPES parameters are required, specified as they were when the data set was originally defined. If the CATALOG, OWNER, or FILESEQUENCENUMBERS parameters were specified for the original define, they should be respecified with RECATALOG.

Exception: RECATALOG must be specified when you use the COLLECTION parameter. DEFINE RECATALOG COLLECTION is intended to be used to rebuild catalog entries.

Abbreviation: RCTLG

NORECATALOG
creates the catalog entries for the first time.

Abbreviation: NRCTLG

TO(date)|FOR(days)
specifies the retention period for the non-VSAM data set being defined. If neither a TO nor FOR is specified, the non-VSAM data set can be deleted at any time.

For non-SMS-managed non-VSAM data sets, the correct retention period is selected in the catalog entry. The VTOC entry might not contain the correct retention period. Issue a LISTCAT command to see the correct expiration date.

For SMS-managed data sets, the expiration date in the catalog is updated and the expiration date in the format-1 DSCB is changed. Should the expiration date in the catalog not agree with the expiration date in the VTOC, the VTOC entry overrides the catalog entry. In this case, issue a LISTVTOC to see the correct expiration date.

Exception: TO|FOR is not applicable for an OAM non-VSAM entry and is ignored if specified. With OAM, a never-expire retention is assigned to the entry which then requires you to specify the PURGE parameter of the DELETE command to delete the OAM non-VSAM entry.

TO(date)
Specifies the earliest date that a command without the PURGE parameter can delete the non-VSAM data set. Specify the expiration date in the form yyyyddd, where yyyy is a four-digit year (to a maximum of 2155) and ddd is the three-digit day of the year from 001 through 365 (for non-leap years) or 366 (for leap years).

The following four values are "never-expire" dates: 99365, 99366, 1999365, and 1999366. Specifying a "never-expire" date means that the PURGE parameter will always be required to delete the non-VSAM data set. For related information, see the "EXPDT Parameter" section of z/OS MVS JCL Reference.

Note:
  1. Any dates with two-digit years (other than 99365 or 99366) will be treated as pre-2000 dates. (See note 2.)
  2. Specifying the current date or a prior date as the expiration date will make the non-VSAM data set immediately eligible for deletion.
FOR(days)
specifies the number of days to keep the non-VSAM data set being defined. The maximum number is 93000. If the number is 0 through 92999 (except for 9999), the entry is retained for the number of days indicated. If the number is either 9999 or 93000, the entry is retained indefinitely. There is a hardware imposed expiration date of 2155.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014