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

DEFINE CLUSTERRECORDS(primary[ secondary])|TRACKS(primary[ secondary])}[VOLUMES(volser[ volser...])][BUFFERSPACE(size)][CONTROLINTERVALSIZE(size)][ERASE|NOERASE][EXCEPTIONEXIT(entrypoint)][FILE(ddname)][FREESPACE(CI-percent[ CA-percent])][KEYS(length offset)][MODEL(entryname[ catname])][NAME(entryname)][OWNER(ownerid)][RECORDSIZE(average maximum)][REUSE|NOREUSE][SHAREOPTIONS(crossregion[ crosssystem])][SPANNED|NONSPANNED][SPEED|RECOVERY][WRITECHECK|NOWRITECHECK])][INDEX ({CYLINDERS(primary[ secondary])|KILOBYTES(primary[ secondary])|MEGABYTES(primary[ secondary])|RECORDS(primary[ secondary])|TRACKS(primary[ secondary])}[VOLUMES(volser[ volser...])][CONTROLINTERVALSIZE(size)][EXCEPTIONEXIT(entrypoint)][FILE(ddname)][MODEL(entryname [ catname])][NAME(entryname)][OWNER(ownerid)][REUSE|NOREUSE][SHAREOPTIONS(crossregion[ crosssystem])][WRITECHECK|NOWRITECHECK])][CATALOG(catname)]DEFINE Abbreviation: 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.Attention: IBM does not recommend doing a delete and define for the same dataset inside a single step, or even in the same job, with DFSMStvs. The delete throwsup an exclusive ENQ that is not released until the job terminates. This is not aproblem most of the time because the job owns the ENQ, so it has no troubleallocating the data set. If, however, the unit of recovery ended up in backout forany reason, DFSMStvs would be unable to allocate the data set, and the UR wouldbe shunted.146 z/OS V1R6.0 DFSMS Access Method Services for Catalogs