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.

Implementing the Language Processor JCL

See the sub-steps below to determine when you must perform this step.

The language processors support two methods of processing your programs: preprocessing and post-processing. Both of these choices may involve modifications to your compile JCL.

You may use the preprocessor or post-processor (whichever is best for your site as needed.) This section discusses the benefits of the preprocessor and the post-processor and describes when to use them.

To use the language processor, you must have previously completed installation of the ECC load library and also prepared a DDIO file. For each language you are using, you should modify the corresponding compiler procedure to provide for the type of processing you will be implementing.

When running the language processor as a preprocessor, you can specify assembler/compiler options in the CWPPRMO data set or in the PARM statement passed to the preprocessor. The CWPPRMO is an input data set that contains the language processor compiler options. Depending on the method used, it may be necessary to include the LANGPARM command with these options.

If you are currently using the post-processor, and you will be converting to the preprocessor, you are not required to spool your SYSPRINT to a temporary data set.

Important

For each of the following steps, it is possible that you will receive a return code other than zero. Should this occur, note the accompanying language processor error message and refer to the Messages-and-codes for further information.

This section provides information about the following topics:

 

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