Rational Developer for System z

Local JCL templates and the global JCL templates

This section describes the use of local JCL templates and global JCL templates.

For information about modifying local JCL templates and global JCL templates see Modifying global JCL templates and local JCL templates.

There are two levels of JCL templates:
- Local JCL templates:
Each service flow project has one set of JCL templates that apply only to that service flow project. (These are also called project-specific JCL templates.)
- Global JCL templates:
There is a single, global set of JCL templates that applies to all the service flow projects in the workspace.

The names and the default contents of each set of local JCL templates are the same as the names and default contents of the global JCL templates.

The reason for having both global and local JCL templates is so that you can modify the text of a global JCL template (for example, the compile JCL template DFHMAXCJ) that affects all your service flow projects, and you can still be able to override that text with a different value in a local version of the same JCL template (DFHMAXCJ).

When you enable a set of local JCL templates for a service flow project (for example, project SFP_001) then whenever the Generate Runtime Code wizard is working in that service flow project and needs a template (for example, the compile JCL template DFHMAXCJ) then the wizard uses the local version of the template instead of the global version.

When you disable a set of local JCL templates for a service flow project (this is the default state) and the Generate Runtime Code wizard needs a template for that service flow project, then the wizard uses the global version of the template.


Feedback