Getting listings

Get the information that you need for debugging by requesting the appropriate compiler listing with the use of compiler options.

About this task

Attention: The listings produced by the compiler are not a programming interface and are subject to change.

Table 1. **Using compiler options to get listings**
Use	Listing	Contents	Compiler option
To check a list of the options in effect for the program, statistics about the content of the program, and diagnostic messages about the compilation To check the locale in effect during compilation	Short listing	List of options in effect for the program Statistics about the content of the program Diagnostic messages about the compilation¹ Locale line that shows the locale in effect	`NOSOURCE`, `NOXREF`, `NOVBREF`, `NOMAP`, `NOLIST`
To aid in testing and debugging your program; to have a record after the program has been debugged	Source listing	Copy of your source	SOURCE
To find certain data items; to see the final storage allocation after reentrancy or optimization has been accounted for; to see where programs are defined and check their attributes	Map of `DATA DIVISION` items	All `DATA DIVISION` items and all implicitly declared items Embedded map summary (in the right margin of the listing for lines in the `DATA DIVISION` that contain data declarations) Nested program map (if the program contains nested programs)	MAP²
To find where a name is defined, referenced, or modified; to determine the context (such as whether a verb was used in a `PERFORM` block) in which a procedure is referenced; to determine the file from which a copybook was obtained	Sorted cross-reference listing of names; sorted cross-reference listing of `COPY/BASIS` statements and copybook files	Data-names, procedure-names, and program-names; references to these names `COPY/BASIS` text-names and library names, and the files from which associated copybooks were obtained Embedded modified cross-reference provides line numbers where data-names and procedure-names were defined	XREF^2,3
To find the failing verb in a program or the address in storage of a data item that is moved while the program is running	`PROCEDURE DIVISION` code and assembler code produced by the compiler³	Generated code	LIST^2,4
To find an instance of a certain verb	Alphabetic listing of verbs	Each verb used, number of times each verb was used, line numbers where each verb was used	VBREF
To eliminate messages, turn off the options (such as `FLAG`) that govern the level of compile diagnostic information. To use your line numbers in the compiled program, use the `NUMBER` compiler option. The compiler checks the sequence of your source statement line numbers in columns 1 through 6 as the statements are read in. When it finds a line number out of sequence, the compiler assigns to it a number with a value one higher than the line number of the preceding statement. The new value is flagged with two asterisks. A diagnostic message indicating an out-of-sequence error is included in the compilation listing. The context of the procedure reference is indicated by the characters preceding the line number. The assembler listing is written to the listing file (a file that has the same name as the source program but with the suffix .wlist).

Example: short listing
Example: SOURCE and NUMBER output
Example: MAP output
Example: embedded map summary
Example: nested program map
Example: XREF output: data-name cross-references
Example: XREF output: program-name cross-references
Example: XREF output: COPY/BASIS cross-references
Example: XREF output: embedded cross-reference
Example: VBREF compiler output

related tasks
Generating a list of compiler messages

related references
Messages and listings for compiler-detected errors