April 1, 1981 ACCESS METHOD SUPPORT The manipulation of data is governed by an access method. To facilitate
the execution of OS Code under eMS, the processing program must see data
as OS would present it. For instance, when the processors expect an
access method to acquire input source cards sequentially, CMS invokes specially written routines that simulate the OS sequential access method and pass data to the processors in the format that the OS access methods
would have produced. Therefore, data appears in storage as if it had
been manipulated using an OS access method. For example, block
descriptor words (BOW), buffer pool management, and variable records are
updated in storage as if an OS access method had processed the data.
The actual writinq to and reading from the I/O device is handled by CMS file manaqement. Note that the character string X'61FFFF61' is by eMS as an end of file indicator.
The essential work of the volume table of contents (VTOe) and the
data set control block (OSCB) is done in eMS by a master file directory (MFO) which updates the disk contents, and a file status table (FST) (one for each data file). All disks are formatted in physical blocks of 800 bytes. eMS continues to update the OS format, within its own format, on the device, for files whose number is 4. That is, the
block and record descriptor words (BOW and ROW) are written along with
the data. If a data set consists of blocked records, the data is
written to, and read from, the I/O device in physical blocks, rather
than loqical records. eMS also simulates the specific methods of
manipulating data sets.
To accomplish this simulation, CMS supports certain essential macros
for the following access methods: BDAM BPAM BSAM/QSAM VSAM (direct) --identifying a record by a key or by its
relative position within the data set.
(partitioned) --seeking a named member within data set.
(sequential) --accessing a record in a sequence in
relation to preceding or following records.
(direct or sequential) --accessing a record sequentially
or directly by key or address. CMS support of OS VSAM files is based on DOS/VS Access Method Services and Virtual Storage Access Method (VSAM). Therefore, the OS user is restricted to those
functions available under "DOS/VS Access Method Services." See the section "eMS Support for as and DOS VSAM Functions" for details. CMS also updates those portions of the OS control blocks that are
needed by the as simulation routines to support a program durinq
execution. Most of the simulated supervisory OS control blocks are
contained in the following two eMS control blocks: CMSCVT simulates the communication vector table. Location 16 contains
the address of the CVT control section.
278 IBM VM/370 System Programmer's Guide
Page of GC20-1807-7 As Updated April 1, 1981 by TNL GN25-0829 CMSCB B" __ # ______ 6 __ ____ 6 _____ _______ ______ a or an OPEN (SVC 19) is issued for a data set. The CMS Control
Block consists of a file control block (FCB) for the data file,
and partial simulation of the job file control block (JFCB),
input/output block (lOB), and data extent block (DEB).
The data control block (DCB) and the data event control block (DECB)
are used by the access method simUlation routines of CMS. MQte: The results may be unpredictable if two DCBs access the same data
set at the same time.
The GET and PUT macros are not supported for use with spanned records
except in GET locate mode. READ, WRITE, and GET (in locate mode) are
supported for spanned records, provided the filemode number is 4, and
the data set is physical sequential format.
GET (QSAM) All the QSAM options of GET
handled the same as move mode.
number is 4, and the last block
(X' 61 FFFF61 ) must be pr esent
record.
GET (QISAM) QISAM is not supported in CMS. PUT (QSAM) are supported. Substitute mode is
If the DCBRECFM is FB, the filemode
is a short block, an EOF indicator
in the last block after the last
All the QSAM options of PUT are supported. Substitute mode is
handled the same as move mode. If the DCBRECFM is FB,. the filemode
number is 4, and the last block is a short block, an EOF indicator is
written in the last block after the last record. When LOCATE mode is used with PUT, issue an explicit CLOSE prior to
returning to CMS to obtain the last record. PUT (QISAM) QISAM is not supported in CMS. PUTX PUTX support is provided only for data sets opened for QSAM-UPDATE with simple buffering. READ/WRITE (BISAM) BISAM is not supported in CMS. READ/WRITE (BSAM and BPAM)
All the BSAM and BPAM options of READ and WRITE are supported except
for the SE option (read backwards).
READ (Offset Read of Keyed BDAM dataset)
This type of READ is not supported because it is used only for
spanned records.
READ/WRITE (BDAM)
All the BDAM and BSAM (create) options of READ and WRITE are
supported except for the Rand RU options. When an input or output error occurs, do not depend on as sense
bytes. An error code is supplied by CMS in the ECB in place of the
sense bytes. These error codes differ for various types of devices and
their meaning can be found in under DMS message 120S. Part 3. Conversational Monitor System (CMS) 279
Previous Page Next Page