CA Dynam for VSE User Guide

Basic Components
For example,
// DLBL SDDOUT,'##TEMP01'
// EXTENT ,SYS006,POOL01,1,0,1,15
If the data set name is longer than 8 characters, the name will be truncated. A
temporary data set will always be CPU- and partition-dependent. Any
expiration date or retention days specified on the DLBL statement will be
ignored.
Note: A temporary data set can never be catalog-controlled. If no EXTENT
statement is submitted, CA Dynam/D uses the default allocation defined in the
DYNAM/D option record (with DEFALOC).
Logical Units
We recommend that you omit logical unit specifications from JCL for all files
processed under CA Dynam/D control. In regard to Direct Access (DA) files,
the main requirement made by VSE concerns the logical units assigned to
them, if they contain multiple extents or span multiple volumes.
For more information about logical unit assignments in general, and
specifically for DA files, see SYS Number Considerations and Modifying Logical
Unit Assignments (LUBS).
File Type
Restrictions are placed on the file type, especially when EXTENT statements
will be omitted so that allocation information is taken from the Catalog. Either
omit the file type from the DLBL statement, or specify it as SD.
If an ISAM or DA file is defined in the Catalog, the DLBL statement must still
indicate SD. CA Dynam/D will override the SD value to match the file type
specified in a program's DTF. You must follow this convention because VSE Job
Control will only allow a DLBL statement without an EXTENT statement for SD
files.
Example,
// JOB ACCESS CATALOGED DATA SET
// DLBL SDDINP,'DISK.FILE'
// EXEC PROGRAM
CADD028I ACCESSED FILE=SDDINP SYS001=202 SYSWK1 X=0/72/1
Chapter 4: Disk File Management 4–9