Rational Developer for System z, Version 7.6

Using the local include preprocessor

Rational® Developer for System z® provides a local include preprocessor that allows you to incorporate external source files into your programs by using include directives other than the PL/I directive %INCLUDE or COBOL COPY statement.
Before using the local include preprocessor, you need to have created a local property group and associated it with a local PL/I source file or local project.
The local include preprocessor is located in the bin directory of the Rational Developer for System z installation path. The file name is PPINCL01.EXE.
You can use the local include preprocessor with an individual PL/I program or a local z/OS® project containing one or more PL/I programs. you can also use it alone or as part of a multi-preprocessor build operation.
  • When the include preprocessor is the only preprocessor called before a compile, the input file is the COBOL or PL/I program that was selected for a Syntax Check or Show Dependencies operation.
  • When the include processor is called for a project build, each COBOL or PL/I program in the project is processed and then compiled. The input file in this case is the current COBOL or PL/I source that is being processed.
  • When the include preprocessor is called as part of a multiple-preprocessor operation and is invoked after a previous preprocessor, the input file to the include preprocessor is the output file from the previous active preprocessor. This file is the one listed in the previous active preprocessor's Preprocessor Output File Name entry field. See Using multiple local preprocessors for more information about setting up multiple-preprocessor operations.

To use the local include preprocessor:

  1. Open the property group editor for the property group associated with the resource or project and navigate to the PL/I page.
  2. From the list on the left, click Local Preprocessor to open the Local Preprocessor page.
  3. To add a new local preprocessor to the property group, click New.
  4. Complete the fields in the Preprocessor Options section of the Local Preprocessor page
    Preprocessor Description
    Type a description, such as "Include preprocessor."
    Preprocessor Name (fully qualified)
    Type the full path name for the include preprocessor. You can use the ${INSTDIR} variable to point to the Rational Developer for System z installation directory. This variable is used to find the include preprocessor.
    Preprocessor Arguments
    The include preprocessor can take the following arguments:
    • TRACE(ON|OFF) On the workstation, this option provides additional output to the TPF Remote Console. On 390 systems, this option provides additional JES output. This output is intended for use by an IBM® technical support representative and should not be used during the regular course of development because it increases the amount of unwanted output and can decrease performance. If you need to contact your IBM technical support representative for problem determination, you can copy this output it into your correspondence. The default for this option is TRACE(OFF). If the option is not specified, the default value is used.
    • FORMAT(ON|OFF) On the workstation and on 390 systems, this option changes the readability of the XML generated for error messages. FORMAT(ON) causes the statement table to be written in 6 columns, making the XML file more readable. Setting this option significantly decreases the performance of parsing the XML file, causing operations to take longer. The default for this option is FORMAT(OFF). If the option is not specified, the default value is used.
    Preprocessor Output File Name
    Specify a file name to be used for preprocessor output. If you omit this option, an output file name is generated.
    Support Error Feedback
    Select this check box to log errors generated by the preprocessor. Selecting this check box enables the Error Feedback XML File Name field. This option is enabled by default.
    Error Feedback XML File Name
    Specify the unqualified name of the XML file to be generated for error feedback. If you omit this option, an error feedback XML file name is generated.
    Environment Variables (Set Statements)
    Specify any environment variables to be passed to the preprocessor. This field contains a value for the SYSLIB, but you should change the value to point to the folder containing your include files.

Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)