Preparing OS/VS COBOL programs

Perform the following steps for compiling your OS/VS COBOL programs:

  1. Allocate libraries (PDSE is suggested unless PDS is required for your organization) for LANGX files. Allocate one or more LANGX libraries for each environment, such as test and production.
  2. Create a corresponding LANGX library for each load library. Specify LRECL=1562 or greater,RECFM=VB,BLKSIZE= lrecl+4 to 32k.
  3. For all programs, such as batch, CICS®, and IMS™, in both test and production environments, compile with the NOBATCH, NOCLIST, NOCOUNT, DMAP, NOLST, PMAP, SOURCE, NOSYMDMP, NOTEST, NOOPT, VERB, XREF(SHORT) compiler options. The module is production-ready and can be debugged using z/OS® Debugger.
  4. Modify the SYSPRINT DD in the compiler step to refer to a file. It can be either a permanent or temporary file. This is the input to the IPVLANGX utility.
  5. Add a step after the compiler step to run the ADFz IPVLANGX utility. This utility program reads the compiler listing and generates a LANGX file, which is the source information file for z/OS® Debugger, Fault Analyzer for z/OS® and Application Performance Analyzer for z/OS®. Save the LANGX file in the LANGX file library, and specify a member name that is equal to the program name of your application program.
  6. Modify the promotion process to promote LANGX files. When a load module is promoted, for example, from test to production, promote the corresponding LANGX file or files. A promotion can be a recompile, copy, or move. Perform the same steps with the LANGX file that you perform with the module during promotion.