Optional Parameters
- CATALOG(catname)
- Identifies
the catalog in which the generation data group is to be defined. If
the catalog's volume is physically mounted, it is dynamically allocated.
The volume must be mounted as permanently resident or reserved. See Catalog Selection Order for DEFINE for the order in which a catalog is selected
when the catalog's name is not specified.
Abbreviation: CAT
- 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 cluster
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.
- EMPTY|NOEMPTY
- Specifies what action
is to be taken for the catalog entries for the GDG base when the number
of generation data sets in the GDG base is equal to the LIMIT value
and another GDS is to be cataloged. The disposition of the actual
data sets uncatalogued from the GDG base is determined by the setting
of the SCRATCH/NOSCRATCH parameter for the GDG base.
- EMPTY
- remove
all GDS entries from GDG base when a new GDS is created that causes
the GDG LIMIT to be exceeded.
Abbreviation: EMP
- NOEMPTY
- remove
only the oldest GDS entry when a new GDS is created that causes GDG
LIMIT to be exceeded.
Abbreviation: NEMP
EXTENDED|NOEXTENDED
- Specifies whether the GDG is to be in extended format or not.
- EXTENDED
- allow
up to 999 generation data sets (GDSs) to be associated with the GDG.
Abbreviation: EXT
- NOEXTENDED
- allow
up to 255 generation data sets (GDSs) to be associated with the GDG.
This is the default value.
Abbreviation: NEXT
- FIFO|LIFO
- Specifies the order in which the GDS list is returned for data
set allocation when the GDG name is supplied on the DD statement.
- FIFO
- The order is the oldest GDS defined to the newest GDS.
- LIFO
- The order is the newest GDS defined to the oldest GDS. This is the default value.
The JCL keyword GDGORDER can be used to override the value specified here to allow individual jobs to select the order of the data.
- OWNER(ownerid)
- Identifies the generation data set's owner.
For TSO users, if the owner is not identified with the OWNER parameter, the TSO userid is the default ownerid.
- PURGE|NOPURGE
- Specifies whether to override expiration dates when a generation
data set (GDS) is rolled off and the SCRATCH parameter is set. PURGE
will override the expiration date and cause the VTOC entry to be deleted
regardless of the expiration date. PURGE is ignored when NOSCRATCH
is specified, either explicitly or as the default.
The default NOPURGE can be changed with the Catalog parmlib member (IGGCATxx) variable GDGPURGE.
- SCRATCH|NOSCRATCH
- Specifies what action
is to be taken for a generation data set located on disk volumes when
the data set is uncataloged from the GDG base as a result of EMPTY/NOEMPTY
processing. For generation data sets located on tape, this parameter
has no effect. You can override the SCRATCH|NOSCRATCH attribute when issuing the DELETE command.
- SCRATCH
- The
GDS is deleted from all disks it occupies when uncataloged from the
GDG base, regardless of whether it is SMS-managed or not.
Abbreviation: SCR
- NOSCRATCH
- If
the data set is a non-SMS managed data set it is not removed from
any of the volumes it occupies. If the data set is an SMS-managed
data set it is recataloged as a non-VSAM data set in rolled-off status,
and is no longer associated with the GDG base. It is not deleted
from any of the SMS-managed volumes it occupies.
Abbreviation: NSCR
The default can be changed from NOSCRATCH to SCRATCH
with the Catalog parmlib member (IGGCATxx) variable GDGSCRATCH.