Listing of generated fields
The different fields in a macro-generated statement or a statement
generated in open code appear in the listing in the same column as they
are coded in the model statement, with the following exceptions:
- If the substituted value in the name or operation field is too
large for the space available, the next field is moved to the
right with one space separating the fields.
- If the substituted value in the operand field causes the remarks
field to be displaced, the remarks field is written on the next line,
starting in the column where it is coded in the model statement.
- If the substituted value in the operation field of a
macro-generated statement contains leading spaces, the spaces
are ignored.
- If the substituted value in the operation field of a model
statement in open code contains leading spaces, the spaces are
used to move the field to the right.
- If the substituted value in the operand field contains leading
spaces, the spaces are used to move the field to the right.
- If the substituted value contains trailing spaces, the spaces
are ignored.
Listing of generated fields containing double-byte data
If the DBCS assembler option is specified, then the following
differences apply:
- Any continuation indicators present in the model
statement are discarded.
- Double-byte data that must be split at a continuation point is
always readable on a device capable of presenting DBCS
characters--SI and SO are inserted
at the break point, and the break-point always occurs between
double-byte characters.
- The continuation indicator is extended to the left, if
necessary, to fill space that cannot be filled with double-byte
data because of alignment and delimiter considerations. The maximum
number of columns filled is 3.
- If continuation is required and the character to the left of the
continuation indicator is X, then
+ is used as the continuation indicator so as to
clearly distinguish the position of the end column. This applies to
any generated field, regardless of its contents, to prevent
ambiguity.
- Redundant SI/SO pairs may be present in a field after substitution.
If they occur at a continuation point, the assembler does not
distinguish them from SI and SO inserted
in the listing by the assembler to preserve
readability. Refer to the generated
object code to resolve this ambiguity.
For more information, see Table 37.
[ Top of Page | Previous Page | Next Page | Contents | Index ]