Native CMS spool files

GDDM V3R2 Base Application Programming Guide

Native CMS spool files

GDDM V3R2 Base Application Programming Guide
SC33-0867-01

GDDM writes 3270 device (family-1) output either directly to a 3270-type terminal or to the virtual punch, according to the name specified in the DSOPEN call. 3270 device output written to a virtual punch is in the form of 80-byte records in the following format:

Record 1

Virtual CCW (8 bytes) including SIO count. The CCW opcode is one of the following:

X'01'

Write

X'05'

Erase/Write

X'0D'

Erase/Write Alternate

X'11'

Write Structured Field.

Record 2

Data stream - as many 80-byte records as are necessary to contain "SIO count" bytes of data.

Record n

Virtual CCW (8 bytes) including SIO count.

Record n+1

Data stream - as many 80-byte records as are necessary to contain "SIO count" bytes of data.

CP SPOOL and CP TAG commands should be used to direct the virtual punch output to a destination that is capable of processing data in the above format (such as RSCS Networking Version 2). The CPSPOOL and CPTAG processing options in DSOPEN can be used to issue such commands automatically.

GDDM writes System Printer output either to a disk file or to the virtual printer, according to the name specified by the DSOPEN call. Data written to a System Printer device contains ASA control characters and, for 3800 devices, Translation Reference Characters (TRCs). The CP SPOOL and CP TAG commands should be used to specify additional special parameters such as CHARS, FLASH, or FCB that may be required for 3800 devices.

GDDM writes trace output either to a disk file or to the virtual printer, according to the file name defined in the current GDDM external defaults (or modified in the CMSTRCE option). If the file name is defined as all blanks, GDDM directs the trace output to the virtual printer.

Notices | Terms of use | Support | Contact z/OS