Device Macroinstruction
Parameters
- tname mname
- identifies the device translation table and macroinstruction for the device class. These must match the table and macroinstruction names shown in Table 1. These cannot be changed because CP code references these names.
- CCW=cmd
- identifies the command code. The cmd is expressed in hex in the range X'00' to X'FF'.
- DATAXFER=NO
- DATAXFER=YES
- indicates if the command causes a data transfer on the channel.
- DIAGNOS=NO
- DIAGNOS=YES
- indicates if the command is a diagnostic CCW.
- MULTI=NO
- MULTI=YES
- indicates if the command is a multitrack operation. This is an internal CP flag.
- PREPROC=NO
- PREPROC=YES
- indicates if preprocessing is required. This is an internal CP flag.
- RONLY=NO
- RONLY=YES
- indicates if the command is prohibited (command rejected) on a read-only device.
- SEEKREQ=NO
- SEEKREQ=YES
- indicates if orientation is required. That is, this CCW must have been preceded in the channel program by a SEEK CCW.
- SIMULATE=NO
- SIMULATE=YES
- indicates if CCW simulation is required. This is an internal CP flag.
- SPECIAL=NO
- SPECIAL=YES
- indicates that further checking is required, such as:
- Certain opcodes need no data translation
- Certain opcodes must be first in the channel program
- For certain opcodes, user class is checked.
This is an internal CP flag.
- STATMOD=NO
- STATMOD=YES
- indicates if the device can set STATUS MODIFIED.
- SYSBUSY=NO
- SYSBUSY=YES
- indicates if the command is allowed to be issued to a tape device that is currently marked as busy with a system function such as SPXTAPE. If it is not allowed, a unit check is returned with command reject set in the sense data.
- VALID=NO
- VALID=YES
- indicates if the command is valid. VALID=NO causes a command reject for this CCW.
- MODE=LINE
- MODE=FULL
- MODE=BOTH
- indicates the screen mode.
- TYPE=WRITE
- TYPE=READ
- TYPE=SELECT
- TYPE=CTRL
- indicates type of command.
- LAST=NO
- LAST=YES
- indicates if this is the last invocation for a particular device table. It must be specified as YES for the last invocation in order to generate a device table.
Examples
Examples are not provided because you should be using the ASSEMBLE files as the base for your changes.
You cannot create new tables, labels, device classes, or supported device types. You can modify only existing tables and entries.
