Rational Developer for System z

Step B8. The Compilation and Installation Options page of the Generate Runtime Code wizard

On this page of the wizard you can specify compilation, build, and configuration actions that you want the wizard to perform on the remote z/OS® system. (These actions occur after the generated output files are copied to the remote z/OS system.)

For more information on the files described in this topic see Files created by the Generate Runtime Code wizard.

This topic contains the following subtopics:

General information

Note: This page of the Generate Runtime Code wizard is available only if:
  • You select the check box Generate to another location on the File selection page of the wizard; and

  • You select the check box Generate to a remote location on the Selection of target locations page of the wizard.

Table 1 shows for each field on this page of the wizard the conditions under which the field is enabled:
Table 1. When fields are enabled in the Compilation and Installation Options page
Field: Conditions required for this field to be enabled: CICS® Service Flow Runtime:
Level 2.0:1 Level 1.0:1
Submit compile JCLs The following options are selected:
  • Create compile JCL on the File selection page
Yes Yes
Submit resource definition JCL The following options are selected:
  • Create resource definitions JCL on the File selection page
The following options are not selected:
  • Have SFR manage creation of Program, Transaction, and ProcessType resource definitions on the File selection page

  • Install the Program, Transaction, and ProcessType resources on the current page
Yes Yes
Submit property file update JCL No conditions. No Yes
CICS System/Region You have created and started a connection to a CICS Resource Definition server (see Step B4. (Optional) Create a connection to a CICS Resource Definition server).

Yes Yes
Refresh
Configure No conditions. Yes Yes
Install the Program, Transaction, and ProcessType resources You have created and started a connection to a CICS Resource Definition server (see Step B4. (Optional) Create a connection to a CICS Resource Definition server).

The following options are not selected:
  • Have SFR manage creation of Program, Transaction, and ProcessType resource definitions on the File selection page

  • Submit resource definition JCL on the current page

Yes Yes
Rescan the Service Flow pickup directory You have created and started a connection to a CICS Resource Definition server (see Step B4. (Optional) Create a connection to a CICS Resource Definition server).

Yes

No

Request Pipeline Scans You have created and started a connection to a CICS Resource Definition server (see Step B4. (Optional) Create a connection to a CICS Resource Definition server).

Yes Yes
List of active pipelines You have selected the check box Request Pipeline Scans. Yes Yes
Radio buttons:
  • Perform actions on Finish
  • Save CICS resource definitions to manifest file
No conditions. Yes Yes
1See CICS Service Flow Runtime Levels 1.0 and 2.0.

Setting the fields on this page of the wizard

Follow these steps:
  1. In the JCL Submission group:

    Submit compile JCLs
    Select this check box if you want the wizard to submit to MVS™ the JCL files that perform compilations of the COBOL source code file and copy book files.
    Submit resource definition JCL
    Select this check box if you want the wizard to submit to CICS the JCL file that defines the resource definitions for your program.
    Submit property file update JCL
    Select this check box if you want the wizard to submit to CICS the JCL file that updates the properties file of the CICS Service Flow Runtime.
  2. In the CICS Resource Definitions group:

    CICS System/Region
    Each entry in this list is the name of a connection to a CICS Resource Definition server (see Create and install CICS resources using the Application Deployment Manager).
    You must define and activate each of these connections on the Connections page of the Preferences window (see Step B4. (Optional) Create a connection to a CICS Resource Definition server ).
    Note: If you are running the Generate Runtime Code wizard and you have not created and started a connection to a CICS Resource Definition server then you can still do so by clicking the Configure button on this page of the wizard (see Configure).
    Refresh
    Click this button to refresh:
    • The list of connections to CICS Resource Definition servers in the CICS System/Region list.
    • The list of pipelines in the Request Pipeline Scans list.

    Configure
    Click this button to open the Connections page of the Preferences window where you can create and start a connection to a CICS Resource Definition server (see Step B4. (Optional) Create a connection to a CICS Resource Definition server ).

    Install the Program, Transaction, and ProcessType resources

    Select this check box if you want the wizard to install the Program, Transaction, and ProcessType resources for your program into CICS using the connection to a CICS Resource Definition server that you selected in the CICS System/Region list on this page of the wizard (see CICS System/Region).

    Important:
    • Essential terms in the resource definition JCLs are specified using the actual values that you substitute for the placeholders (such as hlq, hlqcics, and hlqcobol) in the JCL templates (see Placeholders in JCL templates).
    • You need to substitute actual values for the placeholders, otherwise the submissions of the JCLs to create these resources will fail.
    • Therefore, before you select this check box, you should verify that the JCL templates (DFHMAXRP, DFHMAXRT, and DFHMAXRR ) that affect these three resource definition JCLs are customized for the remote z/OS system on which you want the JCLs to run (see Step B2. (Recommended) Customize the JCL templates).
    Rescan the Service Flow pickup directory
    Select this check box if you want the wizard to request the CICS Service Flow Runtime to perform a scan of the service flow property pickup directory.
    Here the CICS Service Flow Runtime (instead of CICS itself ) scans the service flow property pickup directory to detect and process any new SFP files in that directory (see Service flow properties file).
    The wizard requests this scan after it copies the output files (including the SFP file) to the remote z/OS system.

    The wizard displays a message in the Details text area of the results window, stating whether this scan was performed successfully or failed (see Step B9. Check the results from running the Generate Runtime Code wizard).

    Request Pipeline Scans
    Select this check box if you want the wizard to run a pipeline scan on one or more of the CICS pipelines that are active in the CICS Resource Definition server that you selected in the CICS System/Region list on this page of the wizard (see CICS System/Region).

    Follow these steps to have the wizard run a scan for a particular CICS pipeline:

    1. Select the checkbox Request Pipeline Scans.

    2. In the table beneath the check box the wizard displays the active pipelines in the CICS Resource Definition server that you selected in the CICS System/Region list.

      Scan
      In the Scan column select the check box beside each pipeline on which you want the wizard to run a scan.
      Note: The wizard selects a checkbox automatically if the path in the Pickup directory field matches the path that you specified in either of two controls (see Table 2):
      Table 2. Controls that cause the wizard to automatically select the checkbox
      Tool: Location: Control:
      Generation properties editor Outbound Web Service Request invoke type Remote WSBind file location list box
      Generate Runtime Code wizard Selection of target locations page WSBind file list box
      Pipeline
      This column displays the name of the pipeline.
      Pickup directory
      This column displays the pipeline's pickup directory.
    A pipeline scan causes CICS to search the pickup directory of the specified pipeline for new WSBind files and to process any new WSBind files that it finds. The result of a pipeline scan on a new WSBind file is that CICS starts the Web service specified in the WSBind file and starts managing requests and responses for it.
    Important:

    For a pipeline scan to be effective, your WSBind file must be located in the pickup directory associated with the pipeline. Therefore, normally:

    1. In the WSBind field of the Selection of target locations page of the Generate Runtime Code wizard, where you specify a directory (such as /u/user25/cicsts32/wspickup) to which you want the wizard to copy the new WSBind file, you should specify a directory that is the pickup directory for the CICS pipeline (such as estpipe) that you want to use.

    2. Then in the Scan column select the check box beside the CICS pipeline (such as estpipe) whose pickup directory is the same directory (/u/user25/cicsts32/wspickup) into which you told the wizard to copy the new WSBind file.

    Perform actions on Finish
    Click this button to have the Generate Runtime Code wizard perform the actions that you have selected in the CICS Resource Definitions group:
    • Install the Program, Transaction, and ProcessType resources
    • Rescan the Service Flow pickup directory
    • Request Pipeline Scans
    Save CICS resource definitions to manifest file
    Click this button to have the wizard create or update the manifest file in the following locations:
    Note:
    • If you have an active connection to a CICS Resource Definition server then:
      • For the attributes used in creating CICS resource definitions the wizard downloads the default attributes set by the system administrator.
      • The wizard automatically updates the manifest generation settings in local generation folder.

  3. Click Finish.

After the wizard terminates, it opens the Runtime Code Generation Complete window. Click Details for information about which operations were performed and whether any errors occurred.


Feedback