CA Dynam for VSE User Guide

DYNCAT Commands
To establish catalog-controlled secondary allocation, q2 and q3 must be
numbers other than zero.
To establish automatic secondary allocation, q2 and q3 must both be zero,
and the ASAMAX and ASAAMT parameters of the DYNAM/D option record must
be defined with a number other than zero. To prohibit automatic secondary
allocation, specify NA, either as a file ID option code or in the DISKOPT=
parameter of DYNCAT DEFINE command.
If ASAMAX, ASAAMT, q2 and q3 are all zero, no secondary allocation is
provided.
SYSnnn
logical unit to use for the extent(s) generated if none was
specified in the DTF. The default is none.
BLKSZ=
Optional parameter. Applicable to both disk and tape. Specifies to CA
Dynam/FI the block size for the file. If specified and CA Dynam/FI is active,
the DTF for the file will be modified. Valid entries are:
Maximum blocksize for tape: 65535
Maximum blocksize for disk: 65535, or
OPT or OPTIMIZE for optimal block size, or
'OPT,nnnnn'
(include single quotes)
When optimal blocking is specified, CA Dynam/FI recalculates the block size
for the physical device on which the file is being created. For FBA devices, the
CISIZE is recalculated. The Catalog is updated when the file is closed for
output to record the actual block size used for the file. When the file is opened
for input, CA Dynam/FI must use this value to build the input DTF correctly.
The last form of this parameter should only be used when the file being
defined in the Catalog does not contain the block size specified by the
programs that read the file. That is, use it when the block size of the file has
already been changed by CA Dynam/FI and the existing file will be used for
input before it is created using the catalog entry. It is intended to be used
when a catalog entry is deleted from the Catalog and redefined, and the file
already exists with optimal block sizes. The current block size should be
specified as the nnnnn value.
CATOPEN=
Optional parameter. Specifies whether newly opened output versions of this
dataset are to be marked as valid versions so they may be cataloged at OPEN.
This will ensure that the version being created will always be considered a
good version even if it is never closed.
YES
NO
This dataset may be cataloged at OPEN.
This dataset should be cataloged at CLOSE.
Chapter 8: Maintaining the Catalog−DYNCAT Program 8–47