z/OS Connect

z/OS Connect

z/OS Connect

Truly RESTful APIs to and from your IBM Z mainframe

 View Only

z/OS Connect 3.0.88 now with support for CICS Liberty JVM Server

By Kate Bittles posted Tue December 17, 2024 11:42 AM

  

z/OS Connect 3.0.88 is now available with support for z/OS Connect to run within a CICS Liberty JVM Server for OpenAPI 3 APIs (zosConnect-3.0), upgrades to the z/OS Connect Gradle plug-ins, support for Gradle 8.11.1 and APAR fixes. For more information, see PH64142: z/OS Connect V3.0.87. If you’re new to IBM z/OS Connect, find out more here.

New

z/OS Connect can now be run within a CICS Liberty JVM Server. z/OS Connect has also been updated to include a JCICS connection that is configured using the new zosconnect_cicsJcicsConnection element. A CICS IPIC connection is not required to access transactions within the same CICS region. When using the JCICS connection and configuring the target CICS application with Concurrency(Threadsafe), z/OS Connect will have a quicker request response time than when using an IPIC connection. For more information, see Running a z/OS Connect native server within CICS.

Enhancements

  • The version of the API provider Gradle plug-in is upgraded to 1.4.7.
  • The version of the API requester Gradle plug-in is upgraded to 1.2.1
  • From 3.0.88, z/OS Connect supports Gradle 8.11.1.

Fixes

  • PH64003 - skipHostnameVerificationForHosts does not effect IBM z/OS Connect IPIC connections to CICS. For more information, see Configuring IPIC High Availability.
  • PH64148 - A java.lang.NullPointerException is reported when an attempt is made to invoke an ARA that is not installed.
  • PH61028 - z/OS Connect Designer incorrectly caches mapping file contents which are invalid after the OpenAPI document or z/OS Asset is updated. For more information, see Common errors encountered when an OpenAPI document is updated.
  • PH62141 - When using an incorrectly described composite type results in message DFHPI9729E being written.
  • PH62470 - The copybook indentation is incorrect when a one-character field name is specified in the openapi.yaml document.
  • PH63865 - An empty array is treated as a failure in a successful OpenAPI 3 API provider scenario.
  • PH63937 - Specifying SBAQLIB1 on a z/OS API requester job results in an abends0C1.
  • PH64070 - Updating to V3.0.81.0 or later, causes existing API providers to fail with message BAQR1778E, “PLI” is not valid.
  • PH64211 - Parameters in headers, with the same root specified, are not found in the request mapping file.

Keep in touch

If you have any feedback on this blog article, the enhancements in this release, or anything else that is related to IBM z/OS Connect content and information, please go to the z/OS Connect community and post your feedback on the discussion forum.

Get started today

Use the links below to find out more, and to get started with IBM z/OS Connect V3.0.88 now!

What is z/OS Connect OpenAPI 3?

What is z/OS Connect OpenAPI 2?

Download V3.0.88 now

Download the z/OS Connect (OpenAPI 3) Server and Designer

Install the z/OS Connect (OpenAPI 2) server and API Toolkit

IBM z/OS Connect API provider Gradle Plugin

IBM z/OS Connect API requester Gradle Plugin

Find out more about IBM z/OS Connect OpenAPI 3.

0 comments
28 views

Permalink