Set Temporary Data Set Allocation Options panel
Panel and field definitions
- Temporary data set allocation defaults
-
- Unit
- Can be one of these:
- A 3-digit hexadecimal device number.
- A 4-digit hexadecimal device number prefixed with a slash (/).
- Device type (generic name).
- Group name (installation-defined symbolic name).
- Data class
- Name of a data class defined in your Storage Management System (SMS) installation. Do not enter a value on a system without SMS.
- Storage class
- Name of a storage class defined in your Storage Management System (SMS) installation. Do not enter a value on a system without SMS.
- Management class
- Name of a management class defined in your Storage Management System (SMS) installation. Do not enter a value on a system without SMS.
- Default High Level Qualifiers
-
- Temporary Data Sets
- Can be any multi-level qualifier, which is used by File Manager as
the high-level qualifier (HLQ) in names of created data sets. You can use these symbols as part of
the HLQ:
- &USER
- Represents the user ID.
- &PREFIX
- Represents the TSO prefix.
- Auxiliary Data Set Allocation Defaults
-
- High Level Qualifier
- Can be any multi-level qualifier, which is used by File Manager as
the high-level qualifier (HLQ) in names of created data sets. You can use these symbols as part of
the HLQ:
- &USER
- Represents the user ID.
- &PREFIX
- Represents the TSO prefix.
- Data class
- Name of a data class defined in your Storage Management System (SMS) installation. Do not enter a value on a system without SMS.
- Storage class
- Name of a storage class defined in your Storage Management System (SMS) installation. Do not enter a value on a system without SMS.
- Management class
- Name of a management class defined in your Storage Management System (SMS) installation. Do not enter a value on a system without SMS.
- Model Data Set Name
- A data set name to be used as the model file for defining the auxiliary
data set for a full function edit session. The TSO prefix (as defined for your user ID) is
used as the high-level qualifier for any name that is not enclosed in quotation marks.
A model file should be used to determine the volume placement of the auxiliary data set in a non-SMS environment. The model file must be a VSAM cluster. It should be defined as a RRDS or VRRDS depending on the attributes of the data set being edited. You can provide both RRDS and VRRDS models by specifying a model data set name that does not exist and represents a prefix for the data set name that will be used.
The model data set that File Manager uses is the name you provided suffixed with
.RRDS
for fixed and.VRRDS
for variable length records. - Auxiliary Data Set Name
- A data set name to be used as the auxiliary file
for a full function edit session.
The TSO prefix (as defined for your user ID) is
used as the high-level qualifier for any name
that is not enclosed in quotation marks.
The auxiliary file must be a REUSEable RRDS file, whose record length definitions must be compatible with the file being edited.
If this field is left blank, a RRDS file is automatically defined for the edit session and subsequently deleted.
It should be defined as a RRDS or VRRDS depending on the attributes of the data set being edited.
You can provide both RRDS and VRRDS data sets by specifying a data set name that does not exist and represents a prefix for the data set name that will be used.
The auxiliary data set that File Manager uses is the name you provided suffixed with
.RRDS
for fixed and.VRRDS
for variable length records.
Parent panels
Child panels
- None.
Equivalent functions
- None.