using keys and specifying the original length.
Note that there is limited support from the CMS file system for BDAM-created
files (sparse). Sparse files are manipulated with CMS commands but are not
treated as sparse files by most CMS commands. The number of records in the
FST are treated as a valid record number.
The number of records in the data set extent must be specified using the
FILEDEF command. The default size is
The minimum LRECL for a CMS BDAM file with keys is eight bytes.
Reading
The
CMS users can read as sequential and partitioned data sets that that reside on as
disks. The CMS
and the as QSAM,
The CMS
tial files that reside on
sequential files from
reading sequential files on
The following as Release
with CMS to read as data sets and
BLDL
FIND
GET
READ
SYNADAF
SYNADRLS
WAIT
CMS supports the following disk formats for the as and
partitioned access methods:
Split cylinders
User labels
Track overflow
Alternate tracks
As in as, the CMS support of the
attempting to backspace over a tape mark or when a beginning of an extent is
found on an as data set or a VSE file. If the data set or file contains split
cylinders, an attempt to backspace within an extent, resulting in a cylinder switch,
also produces a return code of 4.
Before CMS can read an as data set or VSE file that resides on a non-CMS disk,
you must issue the CMS ACCESS command to make the disk on which it resides
available to CMS. The format of the ACCESS command can be found in the
file identification when accessing an as or
as Macro Simulation