Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Modify the JCL to run the PL/I Language Processor

You must perform this step if the following is true:

  • You are installing BMC AMI DevX Code Debug for CICS or BMC AMI DevX Code Debug for TSO and you are licensed for the PL/I language processor.

This step contains instructions for both the PL/I language preprocessor and post-processor. You should follow the instructions that apply to the type of processing you will be performing.

Preprocessor

SLCXCNTL sample library member CXPLIPRE contains sample JCL necessary to run the PL/I language preprocessor.

Modify the compile step of your PL/I JCL:

  •  On the EXEC statement, change the name of your compiler to CWPPMAIN and add the following to any existing PL/I compiler options:

LANGUAGE(compiler version)

See PL-I-compiler-options for a list of the compiler versions that can be specified with the LANGUAGE command. The default compiler for PL/I is the compiler currently in use on your system.

Important

The LANGUAGE command may be specified in the CWPPRMO command stream rather than on the EXEC statement.

  • Add the ECC SLCXLOAD DSN to the STEPLIB or JOBLIB concatenation if it is not in the link list.
  • Add the CWPDDIO DD statement to specify the name of the source listing DDIO file you will be using. The source listing DDIO file may be in standard DDIO, shared directory, or database format.

Important

 If the source member is to be used by BMC AMI DevX Code Debug for CICS, the source listing file specified here must be VSAM.

  • Determine the language processor options you will use as input and add them to the EXEC parameter, or add a CWPPRMO DD statement that points to the appropriate options. Sample options are contained in SLCXCNTL sample library member CXLPPLI to provide the smallest output to the source listing file (for minimizing space). If you use these options, and you will be using the PL/I language preprocessor, add LANGUAGE(xxx) to the EXEC PARM or to the CWPPRMO DD statement.

Post-processor

You can use the post-processor to process compile listings that were previously stored, or you can modify your PL/I compile JCL to pass the compiler listing to the post-processor as described below.

  • Check the PL/I compiler options.

  • Change the PL/I compile JCL to write the compiler listing (SYSPRINT) to a sequential file for use as input to the PL/I language post-processor. A sample of the necessary JCL is shown below.

    //SYSPRINT DD UNIT=SYSDA,SPACE=(CYL,(100,10)),DCB=BLKSIZE=19069,
    //            DISP=(MOD,PASS)

    The above example is a temporary file. You can save the JCL as a permanent file to be reused as shown in the example below:

    //SYSPRINT DD DSN=CX,STORED.LISTINGS(MEMBER)

     The SYSPRINT file will be LRECL=133, RECFM=FBA.

LCX SCNTL Sample Library Members for PL/I Language Processor

Member

Purpose

CXPLI

Processes compiler listings through the language post-processor. Add this JCL after your PL/I compile step and before your link edit step (if one exists). CXPLI can be customized to meet your site’s requirements.

CXPLI2

Postprocesses compiler listings stored from a previous compile job. Use this JCL to process listings that have been previously compiled and stored in machine-readable format.

  • The CWPLOAD file must be allocated using DISP=OLD or DISP=SHR.
  •  The object module that is processed by the post-processor must be used as input to the linkedit step.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*