Control statements
You enter control statements:
- z/OS®
- In SYSIN and, optionally, in a PDS member specified by a COPY control statement. This member must belong to the PDS specified by the COPYLIB DD statement.
- CMS
- In the file filename DISASM (where you invoked the Disassembler using the command ASMD filename) and, optionally, in a MACLIB member specified by a COPY control statement. This member must belong to a MACLIB specified by the GLOBAL MACLIB CMS command.
- z/VSE®
- In SYSIPT and, optionally, in a Librarian member specified by a COPY control statement. This member must belong to a library specified in the search chain.
The following rules apply to control statements:
- Columns 1–72 can contain only data.
- Columns 73–80 can be used for any desired purpose. In addition, columns beyond the last specified may be used for any purpose.
- Hexadecimal fields may contain only the hexadecimal digits 0–9 and A–F, while decimal fields may contain only digits 0–9.
- You must specify the module-CSECT statement in the first statement in the input stream. For more details on the Module CSECT statement see Module-CSECT statement (required).
- DSECT definitions may not include any other control statement.
- USING statements for DSECTs must be entered after the DSECT definition.
- DATA-only statements and program USING statements may be entered in any order except within DSECT definitions.
The COPY control statement may be used to switch the input stream to a member of the COPYLIB file which contains additional control statements. COPY statements are not allowed in these supplemental control statement members. That is, COPY statements may not cause nesting COPYing. After the COPY member input is exhausted, the original input stream is resumed. This control statement is especially helpful where a large common DSECT is used by multiple CSECTs in a module.