AXQDSNAL
The AXQDSNAL
member is
used to override new file allocations for Advanced Archive for DFSMShsm. The purpose
pf this member is to give you limited allocation control over data sets that are dynamically
allocated by Advanced Archive for DFSMShsm. Most Advanced Archive for DFSMShsm disk data sets can be changed through this
member.
Overall logical statement layout
A data set name or a data set name mask (a data set name that uses wildcard characters)
One or more keyword-value pairs
Logical transaction format details
Each statement within the AXQDSNAL data is a data set name or a data set name mask that is followed by subordinate keyword and value clauses.
The data set name mask can be a specific data set name or a data set name that includes wildcard characters.
Statements are free-form in the sense that keyword position and order do not matter.
Statements can be continued from one row to the next by using the hyphen (
-
) continuation character. A statement ends when a given row is not continued.The overrides are limited to new data sets; you cannot override allocation information for existing data sets.
Statement coding rules
Every statement must begin with a data set name. The data set name must match a data set that belongs to Advanced Archive for DFSMShsm. A mistyped data set name renders the statement useless.
The data set name may begin in any column.
The data set name may contain wildcard characters:
*
,**
,%
The first entry in AXQDSNAL that matches a given Advanced Archive for DFSMShsm data set name is used for overriding the allocation. If duplicate entries exist, only the first occurrence is used.
An entry whose wildcard characters make the data set name very generic could match an allocation request other than that for which it was intended.
If the file being overridden is a generation data set, specify the generation data set base name; do not use wildcards to identify the G0000V00.
Keyword-value pairs are separated by one or more blank spaces. The keyword, equal sign (
=
), and keyword value are not separated from each other by blank spaces (keyword=value
, for example). Every keyword and its value must begin and end in a single statement.An asterisk (
*
) in column 1 is interpreted as a comment.Errors are reported in a report DD
//ALLOCDSN
.
Useful applications
AXQDSNAL
, you can alter
the requested space allocation to better suit your environment. For
example:ARCHIVE.MGR.DBBKUP ALLOC=CYL PRIMARY=1000 SECONDARY=100
ADV.ARCHV.DBBKUP ALLOC=CYL PRIMARY=1000 SECONDARY=100
Supported keywords
Keyword | Description |
---|---|
ALLOC= |
Change the default allocation type to TRK or
CYL. Example: JCL equivalent: Notes: If this keyword is specified, its value must be either TRK or CYL. |
PRIMARY= |
Specify a different primary allocation. Example: JCL equivalent: Notes: The value can be any positive integer that is less than or equal to 16,777,215. Space must be available. |
SECONDARY= |
Specify a different secondary allocation or
nullify a secondary allocation. Example: JCL equivalent: Notes: The value can be any positive integer that is less than or equal to 16,777,215. Space must be available. In some cases, it might be useful to specify 0. |
DIRBLKS= |
Specify a different quantity for PDS directory
blocks. Example: JCL
equivalent: |
RLSE= |
Specify whether you want space released when
a data set is closed. Example: JCL equivalent: |
VOLCOUNT= |
Specify the maximum number of volumes to which
a data set can extend. Example: JCL equivalent: Notes: |
FREE= |
Specify whether you want the data set to be
deallocated when it is closed. Example: JCL equivalent: Notes: |
PREEXIST= |
Specify whether you want an existing data set
to be scratched. Example: JCL equivalent: |
DATACLAS= |
Specify the SMS data class. Advanced Archive for DFSMShsm
specifies the data class using DYNAMIC-ALLOCATION-DATA-CLASS ; this parameter
granularly specifies a different data class. DATACLAS=NONE causes the parameter to
be ignored.Example:
JCL equivalent:
Notes: You must specify a valid SMS data class. |
STORCLAS= |
Specify the SMS storage class. Advanced Archive for DFSMShsm
specifies the storage class using DYNAMIC-ALLOCATION-STORAGE-CLASS ; this parameter
granularly specifies a different storage class. STORCLAS=NONE causes the parameter
to be ignored.Example:
JCL equivalent:
Notes: You must specify a valid SMS storage class. |
MGMTCLAS= |
Specify the SMS management class. Advanced Archive for DFSMShsm
specifies the management class using DYNAMIC-ALLOCATION-MANAGEMENT-CLASS ; this
parameter granularly specifies a different management class. MGMTCLAS=NONE causes
the parameter to be ignored.Example:
JCL equivalent:
Notes: You must specify a valid SMS management class. |
VOLSER= |
Specify a target volume serial number. Advanced Archive for DFSMShsm specifies volume serial number based on
DYNAMIC-ALLOCATION-VOLSER ; this parameter granularly specifies a different volume
serial number. VOLSER=NONE causes the parameter to be ignored.Example:
JCL equivalent:
Notes: You may specify only one volume serial number. |
UNIT= |
Specify a unit type. Advanced Archive for DFSMShsm allocates the
unit type based on DYNAMIC-ALLOCATION-UNIT ; this parameter granularly specifies a
different unit type. Example:
JCL equivalent:
|
LRECL= |
Specifies a different record length than the one that was specified by Advanced Archive for DFSMShsm. Example:
JCL equivalent:
Notes: You many specify any positive integer in the range 1 – 32760. |
BLKSIZE= |
Specifies a different record length than the one that was specified by Advanced Archive for DFSMShsm. Example:
JCL equivalent:
Notes: You many specify any positive integer in the range 0 – 32760. If you specify 0, block size is determined when the data set is opened and closed. |
DSORG= |
Specifies a different data set organization type than the one that was
specified by Advanced Archive for DFSMShsm. Example:
JCL equivalent:
|
RECFM= |
Specifies a different record format than the one that was specified by Advanced Archive for DFSMShsm. Example:
JCL equivalent:
Notes: E, V, U, B, A, and M are supported record formats. |