IBM CICS Transaction Server for z/OS open beta program

CICS Transaction Server for z/OS open beta (April 2026 update)

Introduction

IBM CICS Transaction Server for z/OS (CICS TS) open beta is available for clients who want to explore potential new CICS capability and assess its value to their business. This offering and its education materials can be downloaded, at no charge, from the IBM CICS TS open beta website. Details on each item listed below are available in the What's new? topic.

Planned availability

• April 10, 2026. Available for download >>> here <<<.

Description

The following capabilities are available as part of the CICS TS open beta:

• Developer productivity

  • Support for Java 25

    CICS TS open beta now supports IBM Semeru Runtime Certified Edition for z/OS, version 25. This support enables developers to use the latest Java 25 language features and provides the opportunity to port Java applications, APIs, and frameworks to run in CICS TS with fast, local and secure access to CICS programs and data.

    This enhancement is also available for CICS TS 6.1, 6.2, 6.3 with APAR PH69930, and CICS TS 5.6 with APAR PH70466.

    To prepare CICS applications to run in new versions of Java JDK, refer to topic Migrating applications to new Java versions in IBM Documentation.

  • Liberty JVM server file locations are now provided on the INQUIRE command

    The CICS command INQUIRE JVMSERVER now provides the file locations for server.xml and messages.log, and the Java version in use. This enables CICS Explorer and other tools to make it easier to navigate to these files to make configuration changes and to diagnose problems.

• Security

  • Flexible CICS surrogate security configuration

    Best practice when adopting a zero trust strategy is for all CICS security classes to be active. This includes surrogate security checks that controls a user's ability to perform an action on behalf of a different user. The existing system initialization parameter XUSER=YES enforces security checks for all of the following scenarios:

    • Installing a resource containing a USERID attribute
    • EXEC CICS QUERY SECURITY USERID(user2)
    • EXEC CICS START TRANSID USERID(user2)
    • Running a transaction on another user's terminal
    • Submitting a job to the JES scheduler to be run by a different user

     

    CICS TS open beta extends the XUSER parameter to allow just one or multiple combinations of the above security checks to be made. This more flexible approach enables users to be more precise and only permit the scenarios required.

  • Improve performance of outbound TCP/IP connections using AT-TLS

    Performance improvements have been made when establishing outbound TCP/IP connections that are secured with Application Transparent - Transport Layer Security (AT-TLS). Outbound HTTP requests will now use an S8 TCB for socket requests instead of using the SO TCB, resulting in better multi-tasking and higher throughput in scenarios where partner systems are slow to respond. This change applies to WEB OPEN and INVOKE SERVICE commands that specify SCHEME(HTTP) using a URIMAP or as part of the command.
    
    Some of these changes are also available for CICS TS 6.1 and 6.2 with APAR PH69208, and CICS TS 6.3 with APAR PH69463.

• Management

  • OpenTelemetry context propagated when using Distributed Transaction Processing (DTP) over MRO

    OpenTelemetry (OTel) tracing provides a holistic and comprehensive view of the flow of application components. Furthermore, OTel enables issues to be quickly identified by site reliability engineers using dashboards, analytics, and automation, and then to engage subject matter experts, such as CICS administrators, with diagnostic information in a trace to resolve an issue.
    
    CICS TS 6.3 participates in OTel tracing by capturing, propagating, and emitting spans for each CICS transaction without requiring application changes. CICS receives OTel context from clients, such as web services, Liberty applications, and IBM z/OS middleware. CICS TS propagates OTel context across CICS regions and IBM middleware that participates in the transaction. At the end of the transaction, CICS produces an OTel trace span that includes key diagnostic information and then makes it available to z/OS.
    
    CICS TS open beta extends this capability to propagate OTel context when an application uses the DTP command SEND or CONVERSE to initiate a transaction in another CICS region, in particular when those regions are connected using Multi-region Operation (MRO). The OTel trace will show the target transaction issuing the RECEIVE command as a child of the calling transaction. No application changes are required.

  • OpenTelemetry context propagated over RETURN TRANSID command

    CICS TS open beta further extends OTel support to propagate context to include transactions initiated by the RETURN TRANSID command. The OTel trace will show the initiated transaction as a child of the transaction issuing the command. No application changes are required.

  • Simplified configuration 

    Configuring a CICS region can be complex, with many options and locations to specify values. To aid simplification, all CICS region configuration can now be specified in a single easy-to-understand YAML file with in-editor contextual help and completion. YAML files are ready to be checked into source-code management systems, for sharing, history tracking, control, and automation.

    A new IBM z/OS middleware configuration tool can discover CICS region configuration to create YAML files, and use YAML files to provision and de-provision CICS regions, including their required data sets, system initialization parameters, and startup JCL. The new configuration tool runs on z/OS and is available as part of the IBM z/OS middleware configuration tool beta program. To sign up and download the configuration tool visit https://ibm.biz/zconfig-join.

IBM early programs

CICS TS open beta is part of IBM early programs that enable clients to acquire early releases of a product for the purposes of testing it before being made commercially available. Participants in early programs typically gain insight into IBM strategy and direction. Participants can also accrue earlier benefits and payback from new features, and can gain a competitive edge and the opportunity for public recognition as a technology leader. Early programs participants are encouraged to provide feedback and articulate their own requirements to IBM, with the potential to help influence and shape future IBM products.

Typically, product offerings that are provided by early programs:

• Have no charge.
• Have no support.
• May not be used for productive purposes.
• Contain a disabling device that will prevent it from being used after the test period ends.
• Are not warranted, such that IBM does not warrant that any version of the early program that is formally released or made commercially available (if any) will be similar to, or compatible with, early release versions.

To find out more about IBM early programs contact the CICS Early Programs coordinator at cicsep@uk.ibm.com.

Planned availability

• April 10, 2026. Available for download >>> here <<<.

Key prerequisites

• The minimum required hardware prerequisite is IBM z14® or subsequent 64-bit IBM z/Architecture® processors.
• The minimum required level of operating system is IBM z/OS, 3.1 (5650-ZOS).
• The minimum required level of Java is IBM Semeru Runtime Certified Edition for z/OS 17.0.7.0.
• To install CICS TS using z/OSMF Software Management, both z/OSMF Software Management and Workflows must be installed and enabled on the driving system.

Publications

Online documentation for CICS TS open beta and is available from IBM Documentation. The documentation is refreshed regularly to reflect feedback from users, and includes changes that result from continuous delivery and IBM Service. Note that not all content that is marked Beta may describe function that is available in this open beta release. For details of the documentation provided by CICS, including offline and PDF options, see What documentation is available.