COBOL and PL/I step options
Purpose
The options that you specify on this window are used to generate JCL for the selected procedure. The information that 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.Fields
Append compiler options to the PARM card: Select this checkbox to append the compiler options to the JCL procedure PARM card. Clear it to replace the options currently specified in the PARM card. This checkbox is enabled when you type a value into the Compiler options field.
If you
are using COBOL and specifying a list of compiler options that is too long to include in the
generated JCL, the OPTFILE compiler option will be generated, and the specified
compiler option will be written in an inline file in the generated JCL card
FELOPTF, which is referenced by the SYSOPTF card by default in the
ELAXFCOC JCL compiler procedure. 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 your compiler options contain more than 100 characters, a +DD:FELOPTF compiler option is generated which directs PL/I to reference the JCL card FELOPTF that contains your compiler options.
- For COBOL,
ELAXMGUXis a user exit responsible for obtaining error records from the compilation. There must be aSTEPLIBto the data set containing the memberELAXMGUX, orELAXMGUXmust 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.
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.
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.
SYSLIB: Specify libraries for resolving copybooks or include files. To add a library to this list, click Add. To reorder the list, click the Up and Down buttons. To delete a library from the list, select it and click Remove.
COPYLOC: Specify libraries and set copybook locations. The copybook added using COYPLOC are added to the list of libraries at the tail end. You can load UNIX based copybooks in this way particularly. To add UNIX files, PATH is
used instead of DSN (for MVS files).
Support Error Feedback: Select this checkbox 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: Specify your own JCL, such as additional data definitions (DD cards). 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 Runtime Environments page.