z/OS Connect

Truly RESTful APIs to and from your IBM Z mainframe

View Only

Back to Blog List

z/OS Connect v3.0.78 is now available with PL/I support for generating z/OS Assets for API requesters and API provider API First

By Kate Bittles posted Wed February 21, 2024 06:08 AM

We have released V3.0.78 of IBM z/OS Connect with a new programmatic choice for developers creating OpenAPI 3 API requesters and API provider API First. Since IBM z/OS Connect v3.0.65, developers have been able to create the API requester and the generated artifacts only with COBOL. As of IBM z/OS Connect v3.0.78, developers can also create the same artifacts using PL/I.

The IMS mobile templates have been updated with the note that existing IMS service provider configurations will not be affected by this change that is available from v3.0.78.

For more information, see PH59261: z/OS Connect V3.0.78 and if you’re new to IBM z/OS Connect, find out more here.

Enhancements

From V3.0.78, support is provided for developers using the PL/I programming language for API requester CICS and z/OS applications, along with API provider API First. The sample code associated with the z/OS Connect Redbook API requester sample for the Getting Started tutorials has also been updated to include PL/I in addition to the existing COBOL programs. For more information on the Getting Started tutorial, see Creating a z/OS Connect API requester project and z/OS application.

As with COBOL, programmers should ensure dynamic linkage is used where possible between the z/OS application code and the Host API load module supplied with IBM z/OS Connect to enable your program to use, without relinking, the most current version of the Host API load module and the associated transport modules delivered through regular z/OS Connect product maintenance. When static linkage is used, you must relink your z/OS application program to benefit from the latest maintenance. For more information, see Linking by dynamic calls.

The version of the API provider Gradle plug-in is upgraded to V1.4.1.
The version of the API requester Gradle plug-in is upgraded to V1.1.2.
The IMS mobile related templates (available with z/OS Connect (OpenAPI 2) have been updated to contain the configuration examples that were previously in the ims-services.xml, ims-interactions.xml and ims-connections.xmlfiles.
The version of Liberty that is embedded in IBM z/OS Connect is upgraded to V23.0.0.12. For more information, see What is new in this release of Liberty in the WebSphere® Application Server for z/OS Liberty documentation.

Maintenance

PH54217 - The CICS® API provider support for z/OS Connect OpenAPI 3 incorrectly returned HTTP status code 500 when a request timed out.
PH59592 - Message SRVE0321E is reported in the z/OS Connect OpenAPI 3 server's messages.log file when the configuration includes a web-ext element that exposes the server's configuration directory as a web application.
PH56143 - Data transformation fails and message BAQR1138E is reported when a colon is included in an element name.
PH55092 - z/OS Connect API requester reports a data transformation error while processing the response data when no response schema is defined for the successful completion scenario.
PH52321 - The imsServiceRegistryHome attribute is no longer used when the imsmobile:imsmobile-2.0 feature is specified. The IBM z/OSConnect IMS service provider configurations are now added to the server.xml. Existing IMS service provider configurations will not be affected by this change.

Get 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.