HLASM Language Reference

Assembler Language Coding Conventions
DBCS2: The DBCS2 constant contains an EBCDIC string which is followed by a
double-byte string. Because there is no space for any double-byte data on the first
line, the end column is extended three columns to the left and the double-byte data
started on the next line. The assembled value of DBCS2 is:
abcdefghijklmnopqrstuvwxyz123456789
DBCS3: The DBCS3 constant contains 22 EBCDIC characters followed by 9
double-byte characters. Alignment of the double-byte data requires that the end
column be extended one column to the left. The SI and SO at the continuation
point are not assembled into the operand. The assembled value of DBCS3 is:
abcdefghijklmnopqrstuv
Source Listing Considerations
For source that does not contain substituted variable symbols, the listing
exactly reflects the source input.
Double-byte data input from code-generation programs, that contain no
substituted variables, are not readable in the listing if the source input was not
displayable on a device capable of presenting DBCS characters.
Refer to “Listing of Generated Fields Containing Double-Byte Data” on
page 249 for details of extended continuation and macro-generated
statements.
Blank Lines
Blank lines are accepted in source programs. In open code, each blank line is
treated as equivalent to a SPACE 1 statement. In the body of a macro definition,
each blank line is treated as equivalent to an ASPACE 1 statement.
Comment Statement Format
Comment statements are not assembled as part of the object module, but are only
printed in the assembly listing. You can write as many comment statements as you
need, provided you follow these rules:
Comment statements require an asterisk in the begin column. Internal macro
definition comment statements require a period in the begin column, followed
by an asterisk. Internal macro comments are accepted as comment statements
in open code.
Any characters of the EBCDIC character set, or double-byte character set can
be used (see “Character Set” on page 11).
Comment statements must lie within the statement field. If the comment
extends into the continuation-indicator field, the statement following the
comment statement is considered a continuation line of that comment
statement.
Comment statements must not appear between an instruction statement and its
continuation lines.
18 HLASM V1R5 Language Reference