09.07.2015 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

DEFINE NONVSAM||||||||||||||||Catalog entries can be re-created only in the catalog specified in the NVRexcept <strong>for</strong> entries that are swap space, page space, or SYS1 data sets. In amultihost environment, non-SYS1 IPL data sets that are SMS-managedcannot be recataloged to a different catalog from the one specified in theNVR. SMS-managed IPL data sets must be SYS1 data sets to be shared in amultihost environment.The VOLUMES and DEVICETYPES parameters are required, specified asthey were when the data set was originally defined. If the CATALOG,OWNER, FOR, TO, or FILESEQUENCENUMBERS parameters werespecified <strong>for</strong> the original define, they should be respecified withRECATALOG.Exception: RECATALOG must be specified when you use theCOLLECTION parameter. DEFINE RECATALOG COLLECTION isintended to be used to rebuild catalog entries.Abbreviation: RCTLGNORECATALOGcreates the catalog entries <strong>for</strong> the first time.Abbreviation: NRCTLGTO(date)|FOR(days)specifies the retention period <strong>for</strong> the non-VSAM data set being defined. Ifneither a TO nor FOR is specified, the non-VSAM data set can be deleted atany time.For non-SMS-managed non-VSAM data sets, the correct retention period isselected in the catalog entry. The VTOC entry might not contain the correctretention period. Issue a LISTCAT command to see the correct expiration date.For SMS-managed data sets, the expiration date in the catalog is updated andthe expiration date in the <strong>for</strong>mat-1 DSCB is changed. Should the expirationdate in the catalog not agree with the expiration date in the VTOC, the VTOCentry overrides the catalog entry. In this case, issue a LISTVTOC to see thecorrect expiration date.Exception: TO|FOR is not applicable <strong>for</strong> an OAM non-VSAM entry and isignored if specified. With OAM, a never-expire retention is assigned to theentry which then requires you to specify the PURGE parameter of the DELETEcommand to delete the OAM non-VSAM entry.TO(date)Specifies the earliest date that a command without the PURGE parametercan delete the non-VSAM data set. Specify the expiration date in the <strong>for</strong>myyyyddd, where yyyy is a four-digit year (to a maximum of 2155) and ddd isthe three-digit day of the year from 001 through 365 (<strong>for</strong> non-leap years) or366 (<strong>for</strong> leap years).The following four values are ″never-expire″ dates: 99365, 99366, 1999365,and 1999366. Specifying a ″never-expire″ date means that the PURGEparameter will always be required to delete the non-VSAM data set. Forrelated in<strong>for</strong>mation, see the ″EXPDT Parameter″ section of z/<strong>OS</strong> MVS JCLReference, SA22-7597.Notes:1. Any dates with two-digit years (other than 99365 or 99366) will betreated as pre-2000 dates. (See note 2.)2. Specifying the current date or a prior date as the expiration date willmake the non-VSAM data set immediately eligible <strong>for</strong> deletion.Chapter 16. DEFINE NONVSAM 185

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!