Enterprise Service Tools - Release Notes

Supported runtime environments

The following table shows the runtime environments supported for each type of project in Enterprise Service Tools:
Table 1. Supported runtime environments for each type of project
Type of project: Supported runtime environments:
Web services for CICS® project
  • CICS Transaction Server for z/OS® V3.1
  • CICS Transaction Server for z/OS V3.2
SOAP for CICS project
  • CICS Transaction Server for z/OS V2.2 and 2.3
IMS™ SOAP Gateway project
  • IMS Version 10 integrated with IMS Connect
  • IMS SOAP Gateway Version 10
    Note: The correlator format in IMS SOAP Gateway Version 9 is deprecated, and therefore is not supported in IBM® Rational® Developer for System z® 7.1 and above
IMS Web 2.0 project
  • IMS Web 2.0 runtime in IBM Mashup Hub

    The IMS Web 2.0 runtime component is described in the help page in IBM Mashup Hub when you specify to create an IMS feed. For more information about IMS Web 2.0 and IBM Mashup Hub, go to http://www.ibm.com/ims and click the link "IMS and Web 2.0" under the Hightlights box.

  • IMS Version 9 and Version 10, integrated with IMS Connect

    For more information about the integrated IMS Connect function of IMS, see "IMS Connect and TCP/IP communications" in the Information Management Software for z/OS Solutions Information Center at http://publib.boulder.ibm.com/infocenter/imzic.

Batch, TSO, z/OS UNIX® System Services project
  • Batch, TSO, and z/OS UNIX System Services environments for z/OS
Database application project
  • CICS Transaction Server for z/OS V3.1
  • CICS Transaction Server for z/OS V3.2
Service flow project
  • CICS Service Flow Runtime for CICS Transaction Server for z/OS V3.1 (requires CICS Transaction Server for z/OS V3.1).

  • CICS Service Flow Runtime for CICS Transaction Server for z/OS V3.2 (requires CICS Transaction Server for z/OS V3.2).

  • Rational Host Access Transformation Services (HATS) V6.0.3 or higher (requires WebSphere® Application Server V5.1 or V6.0)

Selecting files to import from a remote z/OS system

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 remote z/OS system.

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 remote z/OS system, 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 system. 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 remote z/OS system 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 remote z/OS system 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 system:
  • 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 Rational Developer for System z 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 remote z/OS system

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

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 copy book when the path contains characters other than ASCII 0x00-0x7f

Problem: If you attempt to import a COBOL copy book 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 copy book to another subdirectory so that the path contains only characters in the range ASCII 0x00-0x7f.