For more information on the files described in this topic see Files created by the Generate Runtime Code wizard.
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.
| 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:
|
Yes | Yes |
| Submit resource definition JCL | The following options are selected:
|
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:
|
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 |
| Perform actions on Finish | No conditions. | Yes | Yes |
| Save CICS resource definitions to manifest file | No conditions. | Yes | Yes |
| 1See CICS Service Flow Runtime Levels 1.0 and 2.0. | |||
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).
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).
Follow these steps to have the wizard run a scan for a particular CICS pipeline:
Select the checkbox Request Pipeline Scans.
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.
For a pipeline scan to be effective, your WSBind file must be located in the pickup directory associated with the pipeline. Therefore, normally:
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.
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.
In the output subfolder for this generation properties file in the EST Project Explorer (see Subfolders in which generation properties files and runtime output files are stored).
In the output directory for z/OS UNIX® System Services that you selected (see Step B7. The Selection of target locations page of the Generate Runtime Code wizard).
The wizard automatically updates the manifest generation settings in local generation folder.
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.