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 Start of change09/08/2017End of change  Time 10:48:16
 . . .
 (1)     (2)    (3)
LINE #  HEXLOC  VERB       LINE #  HEXLOC  VERB       LINE #  HEXLOC  VERB
000880 0026F0 DISPLAY      000881 002702 PERFORM      000933 002702 OPEN
000934 002722 IF           000935 00272C DISPLAY      000936 002736 PERFORM
001389 002736 DISPLAY      001390 002740 DISPLAY      001391 00274A DISPLAY
001392 002754 DISPLAY      001393 00275E DISPLAY      001394 002768 DISPLAY
001395 002772 DISPLAY      000937 00277C PERFORM      001434 00277C DISPLAY
001435 002786 STOP         000939 0027A2 MOVE         000940 0027AC WRITE
000941 0027D6 IF           000942 0027E0 DISPLAY      000943 0027EA PERFORM
001389 0027EA DISPLAY      001390 0027F4 DISPLAY      001391 0027FE DISPLAY
001392 002808 DISPLAY      001393 002812 DISPLAY      001394 00281C DISPLAY
001395 002826 DISPLAY      000944 002830 DISPLAY      000945 00283A PERFORM
001403 00283A DISPLAY      001404 002844 DISPLAY      001405 00284E DISPLAY
001406 002858 DISPLAY      001407 002862 CALL         000947 002888 CLOSE
(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 statement (in hexadecimal notation).

The statements are listed in the order in which they occur and are listed once for each time they are used.

(3)
Statement used.
Notes: Start of change
  • The optimizer might inline paragraphs, move code around or indeed place it after the body of the program if little used, such as the error message formatting code. This might make the OFFSET report less useful than it was with previous compilers. You can refer to the LIST output instead (note that OFFSET and LIST are mutually exclusive options). For details, see Reading LIST output.
  • 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.
End of change

related references  
OFFSET