370 I/O Reference Summary


A CWW is 64 bits (8 bytes) in length. Here is the layout of the CCW

 0        8        16       24       32       40       48       56
+--------+--------+--------+--------+--------+--------+--------+--------+
|  CMD   |    Data Addr (24 bits)   | FLAGS  |00000000|    Length       |
+--------+--------+--------+--------+--------+--------+--------+--------+

Command Code (Bits 0-7) Specifies the I/O operation to be performed.

Data Address (Bits 8-31) Specifies the location in main storage for the data associated with the I/O operation.

Chain Data Flag (CD) (Bit 32) When set to one indicates the chaining of data. It causes the storage area of the next CCW to be used with the current I/O operation. The use of data chaining allows data to be transferred to or from noncontiguous areas of storage in a single I/O operation.

Command Chain (CC) (Bit 33) When set to one, and when the CD flag is set to zero, indicates the chaining of commands. When the operation of the current CCW is complete and Command Chaining is active, the next CCW will become the new current I/O operation.

Suppress Length Indication (SLI) (Bit 34) When set to one and the CD flag is set to zero, the incorrect length indication is suppressed.

Skip (SKIP) (Bit 35) When set to one the transfer of information is suppressed for read and sense operations.

Program Controlled Interrupt (PCI) (Bit 36) When set to one the channel will generate an interruption condition when the CCW begins execution in the channel.

Indirect Data Address (IDA) (Bit 37) When set to one indicates indirect addressing. The data address of the CCW points to an Indirect Address List instead of directly to the data.

Count (Bits 48-63) Specifies the number of bytes to be used for the I/O operation.

Bits 38-47 should always be set to zeros.

Flag Summary
80 - Chain Data
40 - Command Chain
20 - Suppress Incorrect Length
10 - Skip
08 - PCI
04 - Indirect Data Address

2 Comments

    • There is no timestamp unless it is part of the data. The CKD format is how the data is physically maintained on the DASD device. The CDK format tells you how the data is stored on the disk drive. It is up to the application programmer to determine what is contained in the data.
      MVS does have a type of a file system but it is a bit different from how file systems are implemented on Linux, Unix, Windows, etc. For MVS the file system is maintained by the VTOC (Volume Table of Contents). Basically it keeps up with what tracks on the disk belong to which data sets. There is some meta-data in the VTOC. The VTOC is made of of DSCB blocks. The DSCB Format 4 contains information about a specific data set. There is some date information maintained in the DSCB. For MVS 3.8 I don’t remember exactly what date information is maintained.

Leave a Reply

Your email address will not be published. Required fields are marked *