Modify the JCL to run the Assembler Language Processor


You must perform this step if you are licensed for the Assembler language processor option for any product.

You can optionally perform this step if you are installing BMC AMI DevX Code Debug for TSO and you are licensed for the Assembler language processor. BMC AMI DevX Code Debug for TSO users can either perform this step now in batch mode, or online as part of the BMC AMI DevX Code Debug for TSO installation procedure.

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

SLCXCNTL sample library member CXASMPRE contains sample JCL necessary to run the Assembler language preprocessor.

Preprocessor

Modify the assembly step of your Assembler JCL:

  • On the EXEC statement, change the name of your compiler to CWPAMAIN and add the following to any existing assembler options:

     LANGUAGE(assembler version)

See Assembler-options for a list of the assembler versions that can be specified with the LANGUAGE command. The default assembler is Assembler H.

Warning

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.

    Warning

    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 CXLPASM to provide the smallest output to the source listing file (for minimizing space). When using these parameters, a printout of the listing from the DDIO file will contain only the source statements. The XREF will not be written to the DDIO file. If you use these options and you will use the Assembler language preprocessor, add LANGUAGE(xxx) to the EXEC PARM or to the CWPPRMO DD statement.
  • Specify the compiler (and release) you will use by including it as a parameter of the LANGUAGE command in your EXECUTE parameter or CWPPRMO DD statement.

Post-processor

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

  • Check the assembler options.
  • Change your assembler JCL to write the compiler listing (SYSPRINT) to a sequential file for use as input to the Assembler language post-processor. A sample of the necessary JCL is shown below.
//SYSPRINT DD UNIT=SYSDA,SPACE=(TRK,(25,20)),DCB=BLKSIZE=16093,
//            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.
  •  Add SLCXCNTL sample library member CXASM as the post-processor step following your assembler step. CXASM can be customized to meet your site’s requirements.
Warning

Important

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*

BMC AMI Enterprise Common Components 17.02