Testing applications on z/OS

You can test applications on IBM® z/OS® systems by using the mainframe support capabilities of HCL OneTest™ API.
Note: For information on recording requests from a non-z/OS queue manager to a queue on a z/OS queue manager and virtualizing replies from z/OS to a queue on a non-z/OS queue manager without installing the HRVMMQF exit, see Using WebSphere MQ transports on distributed platforms to test traffic to and from WebSphere MQ on z/OS.

HCL OneTest API supports the following features when running on z/OS 2.1 and 2.2:

For more information about z/OS, CICS, and IMS, see IBM z/OS basic skills education knowledge center.

Hardware requirements

No special hardware is needed for any of the z/OS features that are supported by HCL OneTest API .

For general information about HCL OneTest API’s hardware requirements, see the PDF document on the HCL License & Delivery Portal.

For information about z/OS hardware requirements, go to IBM z/OS basic skills education knowledge center.

Software requirements

This section explains the software requirements for z/OS and HCL OneTest API.

z/OS must be installed and configured. For more information, see IBM z/OS basic skills education knowledge center.

HCL OneTest API and HCL Quality Server must be installed.

The following software versions are supported:

  • IBM WebSphere MQ 7.1, 7.5, and 8.0
  • CICS Transaction Gateway 8.0, 8.1, 9.0, 9.1, and 9.2
  • CICS Transaction Server versions 4.1, 4.2, 5.1, and 5.2 for IPIC and DPL
  • IMS 12, 13, and 14 (includes IMS Connect) with the Java API included in IBM IMS Enterprise Suite 2.1, 3.1, or 3.2

The following table describes more requirements for performing specific testing activities.

To perform these actions Install
Record IMS Connect traffic by using the HTTP/TCP proxy HCL Quality Server

HTTP/TCP proxies

Record inbound or outbound IPIC communications to or from CICS programs
Record inbound or outbound web service calls to or from CICS programs
Run tests and stubs on non-local systems HCL OneTest API Agent

For information about setting up and using CICS Transaction Gateway transports, see Before creating CICS transports.

For more information about requirements for recording and virtualizing with CICS Transaction Gateway, see Requirements for CICS Transaction Gateway.

For more information about requirements for recording and virtualizing DPL calls in a CICS Transaction Server, see Recording and virtualizing DPL calls in CICS Transaction Server.

For more information about how to record and test IPIC communications to a CICS Transaction Server, see Configuring HCL OneTest API for recording and virtualizing IPIC traffic.

Feedback