Rational Developer for System z

COBOL and PL/I step options

Use the COBOL and PL/I Compile Step Options to edit a shipped COBOL or PL/I compilation step.

Purpose

The options you specify on this window are used to generate JCL for the selected procedure. The information you provide on this window pertains to remote COBOL or PL/I compiler options. Use the Local Compiler Options page to set options for local compilations.
Note: For fields that take partitioned data sets as their value, you can drag a partitioned data set name from the Remote Systems view, z/OS Projects or Enterprise Projects view, or Remote z/OS Search results view and drop it in the field. To change the order of partitioned data set names in a field, place the cursor in the field and click Change Order from the pop-up menu.

Fields

Append compiler options to the PARM card: Select this check box to append the compiler options to the JCL procedure PARM card. Clear it to replace the options currently specified in the PARM card.

Compiler Options: The list of COBOL or PL/I compiler options, separated by spaces. This list constitutes a PARM parameter for the EXEC statement used to compile your program. This field is limited to 100 characters and the limit is imposed by the JCL processing. Rational® Developer for System z® displays a warning when this limit is reached. This limit includes not only the characters you type into this field, but also any parameters that are concatenated with these parameters, such as when the CICS® or DB2® runtime environments are enabled.

Note: If you are reaching this limit in your compilations due to several compiler options specified, check your JES listing to ensure that you are not specifying duplicate compiler options. Your JCL compile procedure should contain the default compiler options required for error feedback, as well as any site-specific standards for compiler options.

If you are specifying a list of compiler options that is longer than 100 characters for COBOL, consider using the OPTFILE compiler option along with the SYSOPTF card. This can be tailored in your JCL compile procedure for COBOL. See the related topics for more information about the OPTFILE compiler option.

If you are using PL/I, and you have more than 100 characters to specify for your compiler options, you can use an options file to contain your compiler options. See the related topics for more information about using an options file.

For COBOL, ELAXMGUX is a Developer for System z user exit responsible for obtaining error records from the compilation. There must be a STEPLIB to the data set containing the member ELAXMGUX, or ELAXMGUX must be in the LPA or system load module libraries. See the compiler options reference in the COBOL Programming Guide for details on specific options.

For PL/I, the compiler option XINFO(XML) must be specified for error messages to be routed to the task list. See the PL/I Programming Guide for details on specific options.

Listing Output Data Set: The name of the listing data set used for the compilation. The listing data set should be a partitioned data set. This data set is used to make up a SYSPRINT card for the compilation.

The SYSPRINT data set for compilations with Enterprise PL/I for z/OS® V3.R1 must have a record format of VBA and a record length of 132. The SYSPRINT data set for compilations with Enterprise PL/I for z/OS V3.R2 must have a record format of VBA and a record length of 137.

Debug Data Set: The name of the debug side file data set where the compiler generates the debug side files. This option is only valid if your compiler's TEST option has its SEPARATE suboption set. The debug side file data set is used to generate the SYSDEBUG DD card during compilation. If no value is specified in this field, the SYSDEBUG DD card is not generated. Debug Tool also uses this side file. The SYSDEBUG data set can be F or FB, with LRECL ranging from 80 to 1024.

Note: For PL/I, this option is only valid if you are using the Enterprise PL/I Compiler Version 3 Release 5, with Debug Tool Version 6 Release 1.

Object Deck Data Set: The name of the object deck data set used for the compilation. The object deck data set should be a partitioned data set. This data set is used to make up a SYSLIN card for the compilation.

Copy Libraries: The list of partitioned data sets containing segments of COBOL or PL/I source that are the COPY or INCLUDE files. These data set names should be separated by spaces.

Support Error Feedback: Select this check box to log errors generated by the compiler.

Data Set Qualifier for Compiler Errors: Errors generated by the compiler are logged to a file that is named with this qualifier. This function is supported only if Support Error Feedback is enabled.

Additional JCL: This field allows you to specify your own JCL. Additional data definitions (DD cards) can be specified here. The contents of this field are echoed at the end of the compilation step. You must specify syntactically correct JCL.

IMS library: Name your IMS™ library. Specify only one entry. This field appears only when IMS is selected on the Runtimes page.


Feedback