Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Building MAC entries SMP/E for z/OS Commands SA23-2275-01 |
|
In the process of reading and writing inline assembler input and building an ASSEM entry, the operation field (operation codes) of each assembler statement is scanned. If column 1 of the assembler statement is blank, SMP/E considers the first character string found to be the operation code. If column 1 is not blank, the second character string found is the operation code. For each operation code found, SMP/E determines whether it is a macro invocation or an assembler instruction. It does so by using its default set of OPCODE definitions. SMP/E's default set of OPCODE definitions identifies all the operation codes in ESA/390 Principles of Operation, SA22-7201, as well as all the assembler instructions supported by the High Level Assembler (ASMA90). You may optionally provide your own OPCODE member to override SMP/E's default set of OPCODE definitions. The user-provided OPCODE member is a text member stored in a user-allocated PDS named SMPPARM. You are not required to allocate the SMPPARM data set, unless you want to supply your own user-defined member. The operation fields (operation codes) of the assembler input are scanned during JCLIN processing and are compared to the OPCODE definitions (either user-defined or default). SMP/E uses the following method to determine whether an assembler
instruction is an OPCODE or a macro:
For a description of the format of the OPCODE member control cards, see the "SMP/E OPCODE Member Control Statements" section in SMP/E for z/OS Reference. For each macro found in the assembly input, SMP/E takes these actions:
Note: After JCLIN processing that creates a new MAC
entry, the only data present in the MAC entry is the set of GENASM
subentries. Additional data, such as the distribution library, is
added to the MAC entry during the installation of the SYSMOD supplying
the actual macro.
|
Copyright IBM Corporation 1990, 2014
|