Generating and submitting JCL

JCL generation, remote syntax check, show dependencies, and remote project builds use JCL procedures that are included with the Developer for z/OS® product instead of the remote 390 build server.

Your MVS system administrator must configure the sample JCL procedures according to the installation and site requirements. Refer to the Host Configuration Guide to locate instructions and details that are related to configuring the JCL procedures. These procedures are run to accomplish any compile, link, or run requests that are submitted from the workbench.

The default properties on the client include the default names that are used in the default procedures. If you decide to specify any compiler options, then a statement is generated to override the compiler options in the procedure. In general, when properties are specified, then those settings are used to override the PROC statements.

By default SYSIN, SYSLIB, and SYSLIN are generated by the workbench-generated JCL. Typically, when you use the compiler procedures, you provide the SYSIN and SYSLIB. For Developer for z/OS procedures, the generation also provides the SYSLIN card.

Customizing JCL procedure support: With customized JCL procedure support, you can supply or remove positional parameters from the JCL procedure. The parameter and value pair are treated as properties. The rules for inheritance, export, and import apply to these properties. You can specify user variable and value pairs in the Assembler, COBOL, PL/I, Link, and Run wizard and property tab pages.

You can also customize the build steps in the procedures that your MVS system administrator defined. For more information about customizing build steps, see Customizing build steps).