CA Dynam for VSE User Guide

Defining Independent Files
SORT and Compiler Work File Considerations:
An important application of partition IDs is the definition of SORT work files or
any compiler work files. With the partition ID feature of CA Dynam/D, you
eliminate the need for separate sets of DLBL and EXTENT statements for each
partition.
Files must be defined for all partitions. However, the same label information
can be used for all jobs in any partition.
Multi-CPU Files
In a multi-CPU environment (real or virtual) using a shared DASD facility, you
can use CPU IDs to ensure file uniqueness from different CPUs. (Remember
that CPU IDs can be used together with partition IDs.) To define
CPU-independent files, enter the information on the DLBL statement in the
following format:
// DLBL filename,'CPU--.file-id'
At processing time, CA Dynam/D will substitute the second '-' with the singleletter
CPU ID generated from the System adapter option record.
Use with Identical File IDs
An important application of partition and CPU IDs is the definition of disk files
(such as sort, compiler, or library files) that can have identical file IDs in two
or more machines or partitions. CA Dynam/D eliminates the maintenance of
multiple sets of labels. Thus, the same Job Control statements can be run from
anywhere with complete file uniqueness. For example:
// JOB DYNAM
// DLBL IJSYSLN,'===.SYSLNK'
// EXTENT SYSLNK,POOL01,1,0,1,12
This is run on a machine with the serial number 32315, in the BG partition.
System Adapter option record is coded in the following ways:
CPUID id=A,SERIAL=0000215043810000
CPUID id=B,SERIAL=0003231543410000
CPUID id=C,SERIAL=0002096843610000
Note: For more information about updating the System Adapter option record,
see the CA CIS Administration Guide.
The VTOC entry for this file would appear as follows:
'BGB.SYSLNK'
Chapter 4: Disk File Management 4–39