| Types of files generated: | Description: | Link to subtopic below: |
|---|---|---|
| COBOL source files and copy books |
|
COBOL source files and copy books |
| JCL files |
|
JCL files |
| Web service files |
|
Web service files |
| XML-COBOL conversion file | File containing conversion
subprograms for inbound and outbound data.
|
XML-COBOL conversion file |
| Service flow properties file |
|
Service flow properties file |
| File and target runtime environments for which this file is generated: | How to use this file: | z/OS® destination: | File names: | File extensions: |
|---|---|---|---|---|
| Main program for the flow Runtime
environments:
|
Compile this program into a library allocated
to DFHRPL in your CICS system. Note: You can set options in the Generate Runtime Code wizard
to have the wizard automatically create a compile JCL and submit the
compile JCL to z/OS (see Step B6. The File selection page of the Generate Runtime Code wizard and Step B8. The Compilation and Installation Options page of the Generate Runtime Code wizard).
|
Partitioned data set that contains COBOL source. | Program in the generation properties editor | .cbl |
| Message copy books Runtime environments:
Note: If you select the option Generate
Internal Data Structures in the generation properties
editor, then these copy books are inlined in the program rather than
in separate files.
|
When the compiler compiles a COBOL file it also automatically compiles any copy book files that are included in the COBOL file. | Partitioned data set that contains COBOL copy books | Generated from message names | .cpy |
| File and target runtime environments for which this file is generated: | How to use this file: | z/OS destination: | File names: | File extensions: |
|---|---|---|---|---|
| Compile JCL used to compile the generated COBOL
source code.This file is generated only if the option Create
compile JCL is selected in the Generate Runtime Code wizard. Runtime environments:
|
Submit this JCL file to z/OS to compile the generated source
code. Note: You can set an option in the Generate
Runtime Code wizard to have the wizard automatically submit this compile
JCL to z/OS (see Step B8. The Compilation and Installation Options page of the Generate Runtime Code wizard).
|
Partitioned data set that contains JCL | Same as program names that they compile | .jcl |
| Compile JCL to compile the Web service XML converters
and create CICS resources for
those programs. Runtime environments:
Note: The CICS resource
definitions are commented out by default. You should restore them
if you need that function.
|
Submit this JCL file to z/OS to compile the generated source
code. Note: You can set an option in the Generate
Runtime Code wizard to have the wizard automatically submit this compile
JCL to z/OS (see Step B8. The Compilation and Installation Options page of the Generate Runtime Code wizard).
|
Partitioned data set that contains JCL | Same as the program name | .jcl |
| Properties file update JCL used to update the CICS Service Flow Runtime properties
file. Runtime environments:
This file is always generated, if the
runtime version is CICS Service Flow
Runtime: Level 1.0.
|
Submit this JCL to z/OS to update the CICS Service Flow Runtime properties file with information about your generated program. | Partitioned data set that contains JCL | @ + first 7 letters of the request name specified in the generation properties editor | .jcl |
| CICS Resource
Definition job used to create resource definitions for the generated
programs This file is generated only if the option Create
resource definitions JCL is selected in the Generate Runtime
Code wizard. Runtime environments:
|
Submit this JCL file to z/OS to create the resource definitions
for your generated program. Note: You can set an
option in the Generate Runtime Code wizard to have the wizard automatically
submit this resource definition JCL to z/OS (see Step B8. The Compilation and Installation Options page of the Generate Runtime Code wizard).
|
Partitioned data set that contains JCL | # + first 7 letters of the request name specified in the generation properties editor | .jcl |
| File and target runtime environments for which this file is generated: | How to use this file: | z/OS destination: | File names: | File extensions: |
|---|---|---|---|---|
| Web service definition file used by Web service
clients. Runtime environments:
|
|
Any valid path on z/OS UNIX System Services | Specified in the generation properties editor | .wsdl |
| WSBind file used by CICS to define the WEBSERVICE resource
as a result of the PIPELINE SCAN command. Runtime
environments:
|
At run time, CICS uses information in the Web service binding file to perform the mapping between application data structures and SOAP messages. | z/OS UNIX System Services path used by the CICS PIPELINE | Specified in the generation properties editor | .wsbind |
By default, when the Generate Runtime Code wizard generates COBOL source code for a Web service, the generated source code uses the CICS interpretive conversion feature of Web Services for CICS (see Runtime XML conversion: compiled or interpretive).
However, in two situations the Generate Runtime Code wizard generates source code that uses the compiled conversion feature of Web Services for CICS. One of these situations is when an Arabic code page is selected in the generation properties editor, and the other situation is when you specifically tell the wizard in the generation properties editor that you want it to generate source code that uses compiled conversion.
To cause the Generate Runtime Code wizard to generate source code for compiled conversion, and to generate the additional COBOL source file containing the conversion subprograms, follow these steps in the generation properties editor:
Table 5 describes the generated COBOL source file that contains the two XML-COBOL conversion subprograms.
| File and target runtime environments for which this file is generated: | How to use this file: | z/OS destination: | File name: | File extensions: |
|---|---|---|---|---|
| File containing the two XML-COBOL data-format
conversion subprograms. Runtime environments:
|
Compile the file into a library allocated to DFHRPL in your CICS system. | Partitioned data set that contains COBOL source code members | Converter program name prefix1 + beginning letters of the name of the flow file + D | .cbl |
Table notes:
|
||||
| File and target runtime environments for which this file is generated: | How to use this file: | z/OS destination: | File names: | File extensions: |
|---|---|---|---|---|
| Service flow properties file (see the subtopic
below: Service flow properties file). Runtime environments:
|
The service flow properties file contains properties of the generated program and is used by the CICS Service Flow Runtime to configure CICS. | See Service flow pickup directory. | The flow name. | .sfp |
This file is new in Rational® Developer for System z® Version 7.1 and replaces the properties file update JCL file.
If the length of this file exceeds 32600 characters then the Generate Runtime Code wizard terminates with an error and displays an error message.
The service flow pickup directory on your remote z/OS system is the directory to which you should copy service flow properties (.sfp) files.
There is only one service flow pickup directory per CICS region.
The system administrator determines the location of the service flow pickup directory.