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

Chapter 16. DEFINE NONVSAMUsing Access Method Services, you can set up jobs to execute a sequence ofcommands with a single invocation of IDCAMS. Modal command execution isbased on the success or failure of prior commands.The DEFINE NONVSAM command defines a catalog entry for non-VSAM datasets or a collection of objects. The syntax of the DEFINE NONVSAM command is:DEFINENONVSAM(NAME(entryname)DEVICETYPES(devtype[ devtype...])VOLUMES(volser[ volser...])[COLLECTION][FILESEQUENCENUMBERS(number[ number...])][OWNER(ownerid)][RECATALOG|NORECATALOG][TO(date)|FOR(days)])[CATALOG(catname)]DEFINE can be abbreviated: DEFA sequence of commands commonly used in a single job step includesDELETE––DEFINE––REPRO or DELETE––DEFINE––BLDINDEX. You can specifyeither a DD name or a data set name with these commands. When you refer to aDD name, however, allocation occurs at job step initiation. This could result in ajob failure if a command such as REPRO follows a DELETE––DEFINE sequencethat changes the location (volser) of the data set. A failure can occur with eitherSMS-managed data sets.To avoid potential failures with a modal command sequence in your IDCAMS job:vSpecify the data set name instead of the DD name; orv Use a separate job step to perform any sequence of commands (for example,REPRO, IMPORT, BLDINDEX, PRINT, or EXAMINE) that follow a DEFINEcommand.Restrictions:1. You cannot rename a non-VSAM data set that contains an indirect volumeserial number.2. You cannot use %SYS conversion for any non-VSAM data set that contains anindirect volume serial number.3. The program or function that deletes and re-catalogs non-VSAM data sets thatcontain indirect volume serial numbers cannot re-catalog them with indirectvolume serial numbers.For information on generation data group wrapping rules, see z/OS MVS JCLReference.© Copyright IBM Corp. 1973, 2004 181