Rational Developer for System z, Version 7.6

Configuring the JCL job parameters

This topic covers the parameters for configuring the JCL job.

To configure the JCL job parameters, click Configure JOB Card. These parameters can also be modified in the z/OS Database Application preferences dialog.

To modify the project settings, select the UML model name. You can configure the parameters listed later in this section.
Note: In the dialog, the asterisk indicates parameters that are required for automatic deployment, in order to generate artifacts.
CICS®
Transaction name
This parameter specifies the CICS transaction name.

Example: CPIH

This parameter is required for automatic deployment.

DSN System
This parameter specifies the data source name.

Example: DSN7

This parameter is required for automatic deployment.

User
This parameter specifies the user name.

Example: USER1

This parameter is required for automatic deployment.

Group
This parameter specifies the group.

Example: USERGRP

This parameter is required for automatic deployment.

DB2® Bind Options
Specify the bind plan name that you want.

Example: WAMBIND

This parameter is required for automatic deployment.

DB2 Bind Package
Specify the bind package name that you want.

Example: WAMPKG

This parameter is required for automatic deployment.

Pipeline
URI Prefix
This parameter specifies the Uniform Resource Identifier namespace and the associated prefix.

Example: http://thezossystem.ibm.com:9989/usertest

This parameter is required for automatic deployment.

Automatic Remote Deployment
This option moves files to the remote system. If the Generate JCL Files option is enabled, the JCL files are submitted automatically.
Generate JCL Files
Select this option to generate the JCL files.
JCL Prefix
Type the required prefix for the JCL files.

Example: COBO

MVS™
Target MVS System
This is the system that compiles the generated COBOL code and runs the program.

Example: thezossystem.ibm.com

This parameter is required for automatic deployment.

Host Code Page
This setting specifies the code page on the target MVS system.

Example: IBM-037

This parameter is required for automatic deployment.

COBOL Source PDS
This parameter is the location of the source COBOL code that is generated by the Database Application Generator and placed on the target MVS system.

Example: USER1.WAM.COBOL

This parameter is required for automatic deployment.

JCL Source PDS
This parameter is the data set for the JCL copy books.

Example: USER1.WAM.JCL

This parameter is required for automatic deployment.

Copy Member PDS
This parameter specifies the copy member data set.

Example: USER1.WAM.COPYLIB

This parameter is required for automatic deployment.

Object Library PDS
This parameter specifies the object library data set.

Example: USER1.WAM.OBJLIB

This parameter is required for automatic deployment.

Load Library PDS
This parameter specifies the load library data set used by CICS.

Example: USER1.WAM.LOADLIB

This parameter is required for automatic deployment.

DBRM Library PDS
This parameter specifies the database request module data set.

Example: USER1.WAM.DBRMLIB

This parameter is required for automatic deployment.

DB2 Load Library PDS
This parameter specifies the database load library.

Example: USER1.WAM.DBRMLIB

Automatic Remote Deployment
This option moves files to the remote system. If the Generate JCL Files option is enabled, the JCL files are submitted automatically.
Generate JCL Files
Select this option to generate the JCL files.
JCL Prefix
Type the required prefix for the JCL files.

Example: COBO

z/OS® UNIX® System Services
Target z/OS UNIX System
This parameter specifies the location of the target z/OS UNIX System Services system.

Example: thezossystem.ibm.com

This parameter is required for automatic deployment.

WSBIND File Location
This parameter specifies the target location of the WSBIND file used by Web Services.

Example: /u/user1/wsbind

This parameter is required for automatic deployment.

WSDL File Location
This parameter specifies the target location of the WSDL file.

Example: /u/user1/wsdl

This parameter is required for automatic deployment.

Automatic Remote Deployment
This option moves files to the remote system. If the Generate JCL Files option is enabled, the JCL files are submitted automatically.
Generate JCL Files
Select this option to generate the JCL files.
JCL Prefix
Type the required prefix for the JCL files.

Example: COBO


Terms of use | Feedback

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