Preparing to remote debug in standard mode

About this task

Note: This chapter is not applicable to IBM® Wazi Developer for Red Hat® CodeReady Workspaces.

To prepare to remote debug in standard mode, you must compile your program with certain compiler options.

You can specify compiler options in the following ways:
  • Creating and managing property groups in the Property Group Manager (See Resource management with property groups.)
  • Specifying the options in the COBOL and PL/I Compile Step Options window, which generates JCL (See COBOL and PL/I step options.)
  • Editing the JCL directly.

Procedure

To add compiler options to the JCL directly, complete the following steps:

  1. Open the JCL file in the Remote Systems view of the z/OS® Projects perspective.
  2. Specify the following options:
    Table 1. Compiler options for debugging
    Compiler Required options Recommended options
    z/OS C and C++ DEBUG or DEBUG(FORMAT(DWARF)) DEBUG(NOHOOK) for better generated code
    Enterprise COBOL for z/OS V6.2 and later TEST or TEST(SEPARATE)1  
    Enterprise COBOL for z/OS V5 and V6.1 TEST  
    Enterprise COBOL for z/OS V3.4 and V4 SOURCE,LIST,XREF,MAP,NONUM NOTEST for better performance
    Enterprise PL/I for z/OS V4 and V5 (31-bit) TEST(NOHOOK) TEST(NOHOOK,SEPARATE) for better performance
    Enterprise PL/I for z/OS V5 (64-bit) TEST  
    High Level Assembler V1.6 ADATA  

1 With TEST the debug data is placed in a NOLOAD segment in the program object. With TEST(SEPARATE) the debug data is placed in a separate debug file.