The common generation properties are generation properties that are present in each of the three flow types. The first common generation property is the Flow Type, which you use to set the flow type of the flow to Nonterminal, FEPI, or Link3270 Bridge.
The additional generation properties are additional properties that occur only in the selected flow type. The FEPI flow type and the Link3270 Bridge flow type each have additional generation properties. The Nonterminal flow type has only the common generation properties
The Web service properties are additional generation properties that can be present in each of the three flow types. The editor displays these properties only when the list Generate Web service Files in the common generation properties is set to Web Services for CICS.
Table 1 shows which ones of these three groups of generation properties are used with each flow type:
| Nonterminal flow type: | FEPI flow type: | Link3270 Bridge flow type: |
|---|---|---|
|
|
|
You can use the generation properties editor to modify either a main flow or an invoked flow (see A flow). The generation properties editor does not distinguish between the two.
For more information about the common generation properties see the CICS® Service Flow Runtime User's Guide (see Supported runtime environments for each project type).
| NAME: | DESCRIPTION: | VALUE RANGE: | DEFAULT VALUE: |
|---|---|---|---|
| Flow Type | The primary type of nodes contained in the flow. Depending on the type selected, additional properties that apply to all nodes of that type appear in the editor. |
|
Non Terminal |
| Request Name | This is the name that you
want the CICS Service Flow
Runtime to use to identify the service flow. This name is used to
start the service flow by name at run time. This name is also defined in CICS as the process type for the flow. |
None. This is a required field. | None. This is a required field. |
| Program Name | This is the name that you want to be given to the main COBOL file that is generated to contain the source code for the service flow. | String value: 1-8 characters | Derived from the flow name (see Table 3) |
| Transaction ID | This is the transaction id that you want to be used for the new service flow in CICS. | String value: 1-4 characters | First 4 characters of the Program Name |
| Run Mode | Processing mode for the transaction conducted by the flow |
|
SYNC |
| Comment | Text describing the runtime code that will be generated | N/A | "GENERATE NAVIGATOR MODULE " + the node name |
| Persistent | Select to have the request and session data remain if the session fails. | N/A | Not selected |
| Generate Internal Data Structures | Select to generate the data structures directly into the generated COBOL source programs. This option produces a limited set of modules (JCL and CBL) required for deployment to the host. | N/A | Not selected |
| Generate Web Service Files | Options to generate converters and support files for a non-SOAP deployment (such as CTG or MQ) or for a Web Services for CICS deployment |
|
None |
| Host code page | Used for the following purposes:
|
Select from list of code pages | Current language |
The Web service generation properties can be present in each of the three flow types (Nonterminal, FEPI, and Link3270 Bridge) and therefore are common generation properties.
The generation properties editor displays these properties only when the option Web Services for CICS is selected in the Generate Web service files list (see Considerations when creating a Web service ).
This option is simpler and is recommended. In the runtime settings, you have to specify only the request name and the user data.
Also, a COBOL source code file is generated that contains subprograms to do the XML-COBOL conversion (see XML-COBOL conversion file).
This option is available only for backwards compatibility and is not recommended otherwise. In the runtime settings, you have to specify additional runtime settings.
On the workbench's main menu select . The Preferences window opens.
In the Preferences window, in the left pane, select .
In the Compiler level list select the level of the COBOL compiler that you want to use.
<service name="DFHMADPLService">
<port binding="tns:DFHMADPLHTTPSoapBinding" name="DFHMADPLPort">
<!-- This soap:address indicates the location
of the Web service over HTTP. -->
<soap:address location="http://system.company.com:8181/servicedir/sfp005"/>
...
...(lines omitted)
</port>
</service>
To specify a location for the End Point URI field you can either:
Select a location from the list:
If you have created and activated a connection to a CICS Resource Definition server (see Step B4. (Optional) Create a connection to a CICS Resource Definition server) and if a query from the connection to the remote CICS region is successful then this field is a list of directories on the remote z/OS® system from which you can select a location.
Select a location from the list or type an entry.
Type a location:
Otherwise this field is an input field.
Type a valid location into the input field.
CICS uses this portion of the URI to resolve the resources used for the Web service. This value is derived from the End Point URI and cannot be changed within the generation properties editor.
The Generate Runtime Code wizard uses the name that you specify here (for example, SFP03) for the WSBind file that it creates (for example, SFP03.wsbind) in the generation subfolder.
The WSBind file contains information that is used to define the Web service to CICS (see Step B8. The Compilation and Installation Options page of the Generate Runtime Code wizard).
The Web service definition file is used by the callers of the Web service. This file is not required by CICS but the runtime code generation facility can deploy this file to the host system, as a means of providing a known storage location for it. CICS can use this file for Web service validation.
The HFS stands for "hierarchical file system", as in UNIX. Here you should type the complete path of the directory in z/OS UNIX System Services in which CICS should look for the WSDL file generated by the Generate Runtime Code wizard (for example, /u/user25/cicsts32/sfp01 ) (see Step B7. The Selection of target locations page of the Generate Runtime Code wizard).
This option is available only when the target runtime environment is the CICS Service Flow Runtime for CICS Transaction Server for z/OS V3.2 or later.
This option is available only when the target runtime environment is the CICS Service Flow Runtime for CICS Transaction Server for z/OS V3.2 or later.