CA Dynam for VSE User Guide

Using Other Software with CA Dynam/FI
To correct the situation, simply include the proper label information in the job
stream. CA Dynam/FI determines that no DTF modifications are necessary,
and the file is ignored.
Logical Unit Number
If the only CA Dynam/FI option specified for a file is an overriding logical unit
number on a DLBL statement, the new logical unit should be different from the
one specified on the file's EXTENT statement. If the units are the same, FI may
not create a virtual DTF for the file. CA Dynam/FI will appear "not to work" for
the file.
To correct this situation, change the logical unit.
TRUNCS Support
All output files under the control of CA Dynam/FI are created with TRUNCS
support. This may, under some conditions, cause the end-of-file record to be
written on the last track of a file where it normally would not have been
placed. If the file is then read using a program which does not require any CA
Dynam/FI file changes and the logic module used to read the file does not
specify 'TRUNCS=YES', the last block of data and the end-of-file record may
not be read.
Therefore, if CA Dynam/FI is used to create a disk file, it should also be used
to read the file. This will ensure that both input and output logic modules
always contain compatible options.
Physical I/O
Programs and products that use physical I/O (PIOCS) are incompatible with CA
Dynam/FI.
Checkpointing
Tape files for which checkpointing is done cannot be modified by CA
Dynam/FI.
Wrong Length Record Error (WLRERR) Routines
CA Dynam/FI always replaces any existing WLRERR routines in the program
with its own. This may cause unusual results in programs that "expect" wrong
length records to exist in a file and perform special processing when they do
occur.
Chapter 6: Controlling File Independence 6–41