Release notes
IBM® z/OS® Connect release notes.
This product contains the following versioned components.
| Component | Version |
|---|---|
| IBM z/OS Connect Server | 3.0.100 |
| IBM z/OS Connect Designer zosConnect-3.0Containers |
3.0.100 |
| IBM z/OS Connect Operator zosConnect-3.0Containers |
1.0.14 |
| IBM z/OS Connect CASE package zosConnect-3.0Containers |
1.0.15 |
| IBM z/OS Connect development tools for Visual Studio Code zosConnect-3.0 |
1.0.1 |
| IBM z/OS Connect
API provider
Gradle plug-in
zosConnect-3.0 |
1.5.0 |
| IBM z/OS Connect
API requester
Gradle plug-in
zosConnect-3.0Started task |
1.3.0 |
| IBM z/OS Connect API toolkit zosConnect-2.0 |
3.3.0.10, 3.4.0.3 |
| IBM z/OS Connect
build toolkit zosConnect-2.0 |
1.20 |
| Liberty version | 25.0.0.9 |
| Gradle zosConnect-3.0 |
9.0.0 |
| Aqua zosConnect-2.0 |
3.3, 3.4 |
Known issues and limitations
- OpenAPI 3.1 Specification
- IBM z/OS Connect 3.0 does not support the OpenAPI 3.1 specification.
- Model Context Protocol (MCP)
- IBM z/OS Connect has the following known restrictions
when using MCP:
- Security is not yet available for the
zosconnect:mcp-1.0feature and therefore it is not recommended to enable this feature in production environments until security is available. - Monitoring is not yet available for APIs invoked as MCP tools.
- Security is not yet available for the
- Running an IBM z/OS Connect Server in a CICS Liberty JVM
-
- JCICS connections are only available with the zosConnect-3.0 base feature for API provider.
- The use of tracking tokens when monitoring JCICS connections is not supported.
- JVM server has a thread limit of 256 for a single JVM server in CICS®. For more information, see
CICS task and thread management.
- IBM z/OS Container Platform restriction
- There is a known issue with the use of AsyncIO and IBM z/OS Connect running in a container on z/OS. If you have an angel process started which provides
access to the AsyncIO feature that your IBM z/OS Connect
container connects to, you need to replace the bootstrap.properties in your z/OS Connect API image with the
following.
This can be done by creating a bootstrap.properties file in your z/OS Connect API project directory and adding the following line to the Dockerfile.org.osgi.framework.system.packages.extra=com.ibm.zos.smf,com.ibm.jzos,com.ibm.jzos.fields,com.ibm.os390.security org.osgi.framework.command.execpermission=/bin/chmod 0550 ${abspath} com.ibm.ws.tcpchannel.useZosAio=falseCOPY --chmod=755 bootstrap.properties /config/bootstrap.properties
- OpenAPI 3 specification support for API provider
-
z/OS Connect Designer supports most OpenAPI features, but the following features are not currently supported:
- Response range definitions 1XX, 2XX, 3XX, 4XX, and 5XX as described here:
https://swagger.io/docs/specification/describing-responses/.
OpenAPI documents containing response ranges cannot be imported by using z/OS Connect Designer.
- Operation definitions for HEAD and TRACE HTTP methods.
OpenAPI documents containing such operations can be imported by using z/OS Connect Designer. HEAD and TRACE operations are ignored.
- Remote or URL references as described here:
https://swagger.io/docs/specification/using-ref/.
OpenAPI documents containing references to external definitions cannot be imported by using z/OS Connect Designer.
- When mapping array items, only the immediate parent array fields are available for mapping.
- Response range definitions 1XX, 2XX, 3XX, 4XX, and 5XX as described here:
- JSONata4Java limitations
- IBM z/OS Connect uses the open source Java™ version of JSONata called
JSONata4Javathat does not implement all of the JSONata functions. TheJSONata4Javaproject does not implement the following JSONata functions.- Path operators
-
^(...) (Order-by) - Other operators
... ~> | ... | ...| (Transform)- String functions
- Only patterns such as
xxx
are recognized as strings. Strings cannot be delimited with slashes/xxx/. - Numeric functions
-
$formatInteger()$parseInteger()
- Java
-
- The
IBM_JAVA_ZOS_TDUMPJAVA environment variable is deprecated with Java 8.
- The
- Using IMS API provider and requester
- API requester using the IMS TM Resource Adapter
can not be used in the same z/OS Connect Server as IMS
z/OS Assets that is, can not be used
if
<feature>zosconnect:ims-1.0</feature>is configured.
If you find a problem with IBM z/OS Connect, and the Known issues and limitations section has helped you resolve your problem, see Troubleshooting section.