Rational Developer for System z
Enterprise COBOL for z/OS, Version 4.1, Compiler and Runtime Migration Guide


Applications with VS COBOL II programs

FDUMP compiler option
The FDUMP compiler option is not supported in Enterprise COBOL, but its function is. FDUMP is mapped to the TEST(SYM) compiler option.
TEST compiler option
The TEST compiler option syntax has been modified to allow you to specify whether and where compiled-in hooks should be located, and whether dictionary and CALC tables should be generated. Five hook-location suboptions are possible: ALL, NONE, STMT, PATH, and BLOCK. Two symbol-table suboptions are possible: SYM and NOSYM.

When you compile with the TEST(...,SYM,...) option, the compiler generates additional symbolic information for the enhanced debugging capabilities that Version 3 of Debug Tool provides. This additional information might increase the size of the application load module if you also use TEST(...,SYM,NOSEPARATE). To reduce the size of a load module, specify the TEST(...,SYM,SEPARATE) suboption.

In an application that mixes VS COBOL II programs and Enterprise COBOL programs, Debug Tool can only debug the VS COBOL II programs that are compiled with TEST.

Batch debugging considerations
Debug Tool provides a function equivalent to the batch mode of COBTEST, along with some additional features.

In batch mode, Debug Tool gets its input from an input file and Debug Tool output is written to an output file similar to COBTEST batch mode. The differences between Debug Tool batch mode and COBTEST batch mode are that the COBTEST commands, RECORD, QUALIFY, RESTART, GO, and RUN, behave differently in batch mode than in interactive mode. With Debug Tool, all commands behave the same in both modes.

Some Debug Tool commands, such as fullscreen commands, are not allowed in batch mode.


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)