Example: OFFSET compiler output

The following example shows a compiler listing that has a condensed statement listing, global tables, WORKING-STORAGE information, and literals. The listing is output from the OFFSET compiler option.

DATA VALIDATION AND UPDATE PROGRAM   IGYTCARA Date 03/19/2021  Time 10:48:16
 . . .
  (1)     (2)     (3)
 LINEID  HEXLOC  VERBCODE      LINEID  HEXLOC  VERBCODE      LINEID  HEXLOC  VERBCODE
 000011  0001B8  DISPLAY       000012  0001CC  PERFORM       000021  0001D0  IF
 000022  0001E2  MOVE          000024  0001EA  MOVE          000012  000204  PERFORM
 000013  000214  DISPLAY       000014  000228  PERFORM       000021  00022C  IF
 000022  00023E  MOVE          000024  000246  MOVE          000014  00024A  PERFORM
 000015  00025A  DISPLAY       000021  000272  IF            000022  000284  MOVE
 000024  00028C  MOVE          000016  000290  PERFORM       000017  0002A0  DISPLAY
 000018  0002B8  STOP

(1): Line number. Your line numbers or compiler-generated line numbers are listed.
(2): Offset, from the start of the program, of the code generated for this verb (in hexadecimal notation).
The verbs are listed in the order in which they occur and are listed every time an instruction is generated for a different line/statement pair than the previous instruction.
(3): Statement used.

Note: Due to the out of line code used for error message formatting, Language Environment® generated offsets, as indicated in "From compile unit {name} at entry point {name} at compile unit offset {offset}...", might be outside the offset range of the program. In these cases, refer to the statement number in the COBOL message (IGZnnnns) to locate the problem.

Related references
OFFSET