122 Exploring WebSphere Studio Enterprise Developer V5.1.2
Important information that might be entered here is the SYSLIB variable where the DB2
installation directory is provided. If needed, you can also specify the CICS Transaction Server
installation directory here.
You can specify additional environment variables in the field at the bottom of the tab.
The Local Compile Options is shown in Figure 6-11 to indicate that a preprocessor needs to
be invoked during the syntax check. Preprocessor options are optional and available when
you select the Invoke pre-processor option.
Figure 6-11 The Local Compiler Options settings for the New Project
We explain what needs to be specified in this tab in Figure 6.6.2 on page 132.
JCL Substitution
When JCL generation is used, JCL procs on the host are embedded in the generated job. In
6.7, “Generating JCL” on page 137, we explain in detail how to generate JCL.
The JCL procs can take advantage of the variable substitution in the JCL, as shown in
Figure 6-12 on page 123.
Chapter 6. Remote development: MVS projects 123
Figure 6-12 The JCL Substitution tab
Let us use an example to visualize the principle of JCL substitution. Suppose that the COBOL
compile procedure has been changed, where the following values reflects the compile
parameters:
(ADEXIT(ELAXMGUX)),ADATA,LIB,TEST&PARM
Also let us assume that side files should be generated for debug. The variable PARM is now
to be added to the JCL Substitution tab. Click the Add button and fill in the Variable name and
the value of that variable, as shown in Figure 6-13.
Figure 6-13 Add a user variable for JCL substitution
Confirm this by clicking OK, and the variable appears in the list, as shown in Figure 6-14.
Figure 6-14 User variable PARM added to the list
Every time JCL is generated for COBOL compilation, the PARM variable in the generated job
is replaced by the value of that variable.
We click the Next button to advance to the next window.
6.3.3 PL/I settings
For the PL/I settings, refer to the discussion about these settings in Chapter 4, “Remote
development: Defining remote systems” on page 51. In addition, the previous section can be
124 Exploring WebSphere Studio Enterprise Developer V5.1.2
of help. No additional information is applicable for this window. Just notice the replacement of
<HLQ> by JNDRES3 as the HLQ for the project we chose to create, as shown in Figure 6-15.
Figure 6-15 The PL/I Settings window for the New Project
Click Next to go to the Assembler settings.
6.3.4 Assembler settings
As with the windows and tabs discussed in the previous sections, the settings for the
assembler programs are similar to those defined in the system definition. Again, the
difference is that <HLQ> is replaced by the actual HLQ, JNDRES3, in our examples.
6.3.5 Link options
For the link options, there is also not much to be described. The replacement of the HLQ is
the only difference.
6.3.6 Application entry point
Here, specify the entry point of the application. There is no additional information at the
project level as compared to the information already laid out in the system definitions.

Get Exploring WebSphere Studio Enterprise Developer V5.1.2 now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.