HLASM Language Reference

ORG Instruction
If you specify multiple location counters with the LOCTR instruction, the ORG
instruction can alter only the location counter in use when the instruction appears.
Thus, you cannot control the structure of the whole control section using ORG, but
only the part that is controlled by the current location counter.
An ORG statement cannot be used to change sections or LOCTR segments. For
example:
AA
CSECT
X DS D
Y DS F
BB
CSECT
ORG Y
is invalid, because the section containing the ORG statement (BB) is not the same
as the section in AA in which the ORG operand expression Y is defined.
With the ORG statement, you can give two instructions the same location counter
values. In such a case, the second instruction does not always eliminate the
effects of the first instruction. Consider the following example:
ADDR DC A(ADDR)
ORG –4
B DC C'BETA'
In this example, the value of B ('BETA') is destroyed by the relocation of ADDR
during linkage editing.
| The following example shows some examples of ORG using the boundary and
| offset operands:
| origin csect
| ds 235x Define 235 bytes
| org origin,,3 Move location counter back to start + 3
| org ,8 Align on 8 byte boundary
| org ,8,-2 Align to 8 byte boundary -2 bytes
| translate dc cl256' ' Define aligned translate table
| org translate+c'a'
| dc c'ABCDEFGHI'
| org translate+c'j'
| dc c'JKLMNOPQR'
| org translate+c's'
| dc c'STUVWXYZ'
| org translate+c'A'
| dc c'ABCDEFGHI'
| org translate+c'J'
| dc c'JKLMNOPQR'
| org translate+c'S'
| dc c'STUVWXYZ'
| org ,
| end
Using Figure 57 on page 203 as an example, to build a translate table (for
example, to convert EBCDIC character code into some other internal code):
1. Define the table (see ▌1▐ in Figure 57) as being filled with zeros.
2. Use the ORG instruction to alter the location counter so that its counter value
indicates a specific location (see ▌2▐ in Figure 57) within the table.
202 HLASM V1R5 Language Reference