Preparing Enterprise COBOL for z/OS® Version 4 programs
Perform the following steps for compiling your Enterprise COBOL
for z/OS® Version 4 programs
using the compiler options suggested in Examples of compiler options and source information files that
are supported by ADFz products for Enterprise COBOL for z/OS Version 4:
- Create libraries (PDSE is suggested unless PDS is required in your organization) for SYSDEBUG files. Create one or more SYSDEBUG libraries for each environment, such as test, and production.
- Create a corresponding SYSDEBUG library for each load library.
Specify
LRECL=(80 to 1024),RECFM=FB,BLKSIZE=(multiple of lrecl < 32K)
. - For all programs in both test and production environments, specify the following compiler
options:
TEST(NOHOOK,SEPARATE,EJPD),LIST,MAP,SOURCE,NONUMBER,XREF(SHORT)
.The
TEST
compiler option is required if you plan to use z/OS® Debugger to debug a program. TheTEST
option is optional if you plan to use Fault Analyzer for z/OS® or Application Performance Analyzer for z/OS®.The
SEPARATE
suboption produces a SYSDEBUG file.NOHOOK
andSEPARATE
produce a production-ready module that can still be debugged.If the
OPT
option is also used,EJPD
might reduce optimization but enables the debugger’sJUMPTO
andGOTO
commands. These commands are disabled whenOPT
andNOEJPD
are both used. - When the
TEST
option is not used, save the compiler listing in a file, or use the IPVLANGX utility program to create a LANGX file. To minimize JCL changes, IPVLANGX has aliases to match names. These are:- z/OS® Debugger
- EQALANGX
- Fault Analyzer for z/OS®
- IDILANGX
- Application Performance Analyzer for z/OS®
- CAZLANGX
- The
LIST
,MAP
,SOURCE
, andXREF
options are needed only if a compiler listing or a LANGX file is used to provide source information to Fault Analyzer for z/OS® or Application Performance Analyzer for z/OS®. If a SYSDEBUG file is used with these products or if you are not using Fault Analyzer for z/OS® or Application Performance Analyzer for z/OS®, theLIST
,MAP
,SOURCE
, andXREF
options are optional. - The
NONUMBER
compiler option is needed only if a compiler listing file is used to provide source information to Application Performance Analyzer for z/OS®. If a SYSDEBUG file is used with Application Performance Analyzer for z/OS®, or if you are not using Application Performance Analyzer for z/OS®, theNONUMBER
option is optional. - Code a SYSDEBUG DD in the JCL of the compiler step:
Save the SYSDEBUG file that is produced by the compiler in the SYSDEBUG library and specify a member name that is equal to the program name of your application program. This file is the source information file for z/OS® Debugger, Fault Analyzer for z/OS® and Application Performance Analyzer for z/OS®.//SYSDEBUG DD DSN= SYSDEBUG.pds(pgmname),DISP=SHR
- Modify the promotion process to promote SYSDEBUG files. When a load module is promoted, for example from test to production, promote the corresponding SYSDEBUG file or files. A promotion can be a recompile, copy, or move. Perform the same steps with the SYSDEBUG file that you perform with the module during promotion.
- Optionally, include a z/OS® Debugger Language Environment® (LE) exit
module into the load module during the linkage editor step. This inclusion
is one way to enable z/OS® Debugger panel 6
in ISPF, a simple panel-driven method to start the debugger automatically
when a program runs, without JCL changes, based on the program name
and user ID. Use module EQADBCXT for batch programs (including IMS™ batch), EQADICXT for IMS/TM programs
and EQADDCXT for DB2® stored
procedures. Do not include the exit module for CICS® programs.
You can also use module EQAD3CXT for batch programs, IMS/TM, IMS™ BTS programs, and DB2® type MAIN stored procedures.