Enterprise Service Tools - Release Notes

Prerequisites required to use Enterprise Service Tools

The CICSR Service Flow Runtime environment (also known as the CICS Service Flow Feature) is the runtime environment for a Web service created from a service flow project in the Enterprise Service Tools.

The following prerequisites are required to use Enterprise Service Tools:
  • For Web services for CICS project: CICS Transaction Server for z/OSR, Version 3.1
  • For SOAP for CICS project: CICS Transaction Server for z/OS, Version 3.1
  • For IMSTM SOAP Gateway project: IMS V10, and IMS V10 IMS Connect
  • For batch, TSO or UNIXR System Services project: IBMR Batch, TSO and UNIX System Services environments for z/OS
  • For database application project: IBM CICS Transaction Server for z/OS, Version 3.1
  • For service-fow project:
    • CICS Transaction Server for z/OS, Version 3.1
    • CICS service-flow feature of CICS Transaction Server for z/OS, Version 3.1
  • For HATS macro:
    • HATS, Version 6.0.3 or later
    • WebSphereR Application Server, Version 5.1 or 6.0 (required by HATS)

Selecting files to import from a z/OS host

This note supplements the topics in the Enterprise Service Tools online documentation that describe how to import files into an Enterprise Service Tools project directly from a z/OS host.

Most of the wizards that allow you to import files into an Enterprise Service Tools project also allow you (assuming that you have previously done the correct configuration steps in the workbench) to import files directly from a z/OS host, by clicking the Remote button on the appropriate wizard page and then selecting the remote files to import from a directory tree that is generated via an active connection with the z/OS host. Other options on the same wizard pages include the FileSystem button for selecting files to import from the workstation's file system and the Workspace button for selecting files to import from the current workspace that you are using in the workbench.

Wizards that can import files directly from a z/OS host include:
  • The BMS Import wizard
  • The Import Web Services Definition wizard
  • The Import PL/I Files wizard
  • The New Flow wizard (on the Import COBOL Files page)
  • The New Service Flow Project wizard (on the Associate service interface page and on the Specify existing program definitions page)
  • The Import Source Files wizard
To import files from a z/OS host in one of these wizards, you must first configure and activate, in the workbench, one of the following types of connections to a z/OS host:
  • A z/OS connection in the Remote System Explorer (RSE) perspective.
  • A z/OS Project.

For information on creating and activating these connections, see the topics in the online documentation for the RationalR Developer for System zTM that describe how to create a z/OS project and how to create a z/OS connection in the Remote System Explorer (RSE) perspective.

Automatically importing dependent COBOL files from a z/OS host

This note supplements the topics in the Enterprise Service Tools online documentation that describe how to import dependent COBOL files from a z/OS host.

The Enterprise Service Tools wizards that allow you to import COBOL files have an option to also automatically import any COBOL files upon which a COBOL file that you have selected to import has a dependency.

To perform this functionality of automatically importing dependency files, the Enterprise Service Tools wizard uses the View Dependency feature of the Rational Developer for System z. Before using this functionality, you must configure the View Dependency feature.

For more information, see the View Dependency topics in the online documentation for the Rational Developer for System z.

Cannot import a COBOL copybook when the path contains characters other than ASCII 0x00-0x7f

Problem: If you attempt to import a COBOL copybook from your workstation, and the path to the COBOL file contains a character (such as the German u-umlaut character) that is not in the ASCII character range 0x00-0x7f, then the import operation fails and an error message such as the following is displayed in the Remote Error List view:

The 'COPY' library was not found. Skipped to the period terminating the 'COPY' statement.

Workaround: Change the name of any subdirectory in the path that contains the problem characters so that the name contains only characters in the range ASCII 0x00-0x7f. Or, move the COBOL copybook to another subdirectory so that the path contains only characters in the range ASCII 0x00-0x7f.