Required compiler options for creating listings or CAZLANGX side files
The following are the compiler options needed to produce listings or CAZLANGX side files suitable for Application Performance Analyzer:
OS/VS COBOL:
- DMAP
- NOCLIST
- NOLST
- NOOPT (Note 1)
- PMAP
- SOURCE
- VERB
- XREF
COBOL compilers (other than OS/VS COBOL):
- LIST,NOOFFSET (Note 2)
- NOOPT (Note 1)
- MAP
- SOURCE
- XREF(SHORT) (Note 3)
VisualAge® PL/I:
- AGGREGATE
- ATTRIBUTES(FULL)
- LIST
- NEST
- OPTIONS
- SOURCE
- XREF(FULL)
Enterprise PL/I:
- AGGREGATE
- ATTRIBUTES(FULL)
- LIST
- MAP
- NEST
- SOURCE
- STMT
- NONUMBER
- OFFSET
- XREF(FULL)
- OPTIONS
- NOBLKOFF
PL/I compilers (other than VisualAge PL/I
and Enterprise PL/I):
- AGGREGATE
- ATTRIBUTES(FULL)
- ESD
- LIST
- MAP
- NEST
- OPTIONS
- SOURCE
- STMT
- XREF(FULL)
Assembler:
- ADATA
C/C++:
- LIST
- NOOFFSET
Note:
- Although NOOPT is recommended, the use of OPTIMIZE is allowed (including OPT(1) or OPT(2) for C) , in which case the compiler merges and rearranges statement numbers in the compiled code. The Application Performance Analyzer analysis will be limited to what can be determined from the optimized compiler listing, which can vary from having no effect on the Application Performance Analyzer report, to inaccurate identification of the source line that failed. The source line number will usually be close, but not necessarily accurate with OPTIMIZE. It is dependent on the compiler's rearrangement or elimination of source statements during its optimization processing.
- Although LIST and NOOFFSET are recommended, the use of NOLIST and OFFSET is allowed, in which case Application Performance Analyzer will not be able to warn the user if the compiler listing is not a good match with what is in storage.
- XREF(SHORT) is a minimum requirement; XREF(FULL) is permitted and has no detrimental effect.
- ATTRIBUTES is a minimum requirement; ATTRIBUTES(FULL) is permitted and has no detrimental effect.