What's new?
You might also like to refer to the CICS Transaction Server for z/OS V5.4 announcement letter.

CICS asynchronous API
This release introduces four EXEC CICS API commands: RUN TRANSID, FETCH CHILD, FETCH ANY, and FREE CHILD. Using these commands, an application developer can run asynchronous transactions in CICS, pass and consume data, and reduce the challenges that are involved in the management and execution of programs.
The CICS asynchronous API uses a parent-child model, enabling application developers to use an asynchronous programming model that can improve the responsiveness of applications, especially those applications that make multiple calls to external services, or which spend a lot of time waiting for the responses of other transactions.
As part of the parent-child model, the asynchronous API flows the security context of the parent task to the child task, ensuring that the children of any given parent task have the correct security authorization to run. New statistics are also provided to monitor the activity of the asynchronous services domain.

Support for Java EE 7 Full Platform
Java developers require access to the latest Java Standard Edition (Java SE) and Enterprise Edition (Java EE) APIs. In addition to the existing support for Java SE applications, CICS TS now supports Java applications that are written to the Java EE 7 Full Platform specification using the embedded version of WebSphere Application Server Liberty (Liberty).
Java EE 7 provides a wealth of features that allow Java developers to quickly and easily write web applications, web service applications, enterprise applications, and Java batch applications. It also provides a number of standard connectors such as JDBC, JCA, and JMS that allow Java applications to operate with applications and data outside a Java runtime environment.
Java applications that are hosted in CICS TS are integrated with CICS tasks by default. This allows applications that are written in different programming languages to share core characteristics such as CICS security, transactionality, management, and monitoring. Using Java capabilities directly in CICS can provide a simple and powerful way to modernize CICS applications, without the requirement to unnecessarily distribute application components across multiple runtimes.
Additionally, a new standard-mode option is added to the Liberty JVM server. This mode is designed for applications that do not require tight integration with CICS by default, but benefit from the performance of Java on z/OS and proximity to data provided by IBM DB2 for z/OS and IBM MQ for z/OS.
Support for Java EE 7 Web Profile, a subset of Java EE 7 Full Platform, is also available on CICS TS 5.3 with APAR PI63877. Support for standard-mode Liberty is also available on CICS TS 5.3 with APAR PI58375.

Enable CICS programs to invoke a Java EE application
A CICS program is now able to invoke a Java™ EE application that is running in a Liberty JVM server. You can invoke a Java EE application as the initial program of a CICS transaction, or by using the EXEC CICS LINK command or EXEC CICS START command from any CICS program.
This can be used if you want to write new function in Java as part of your CICS application, invoke Java code from part of an existing web application, or if you want to re-implement existing COBOL applications in Java.
This capability is also available on CICS TS 5.3 with APAR P167640 and APAR PI58375.

New web services commands
The EXEC CICS TRANSFORM command converts JSON data and a language structure. The following commands are now available:
- TRANSFORM DATATOJSON to convert application data to JSON.
- TRANSFORM JSONTODATA to convert JSON to application data.
This capability is also available on CICS TS 5.3 with APAR PI54841.

New parameters for DFHLS2WS
New optional parameters, PORT-NAME, BINDING-NAME, and SERVICE-NAME, are added to the high-level language to WSDL conversion (DFHLS2WS) procedure to prevent your program name from being shown in the port and portType name, the binding name, and the service name in the generated WSDL document.
If you specify the following optional parameters, the PGMNAME name is not included in the generated WSDL 1.1 document:
- BINDING-NAME
- OPERATION-NAME
- PORT-NAME
- REQUEST-NAMESPACE
- RESPONSE-NAMESPACE
- SERVICE-NAME
- WSDL-NAMESPACE

New MAPPING-OVERRIDES option for schema-to-PL/I conversion
A new MAPPING-OVERRIDES option, HYPHENS-AS-UNDERSCORES, is available in the DFHWS2LS, DFHJS2LS, and DFHSC2LS assistants. You can use this option to convert any hyphens in the schema to underscores, rather than the character X. Using this option can improve the readability of the generated PL/I language structures.
This capability is also available on CICS TS 5.3 with APAR PI57467.

New WIDE-COMP3 option for schema-to-COBOL or schema-to-PL/I conversion
A new WIDE-COMP3 option, FULL, is available in the DFHWS2LS, DFHJS2LS, and DFHSC2LS assistants. You can use this option to generate packed decimal fields that are large enough to hold all valid values. The maximum size is 31 digits.
This capability is also available on CICS TS 5.3 with APAR PI47466.

Support for mapping level 4.1 in the CICS assistants
Mapping level 4.1 is added to the web services assistants, XML assistants, and JSON assistants. This mapping level implements improved mappings for simple arrays generated bottom-up from existing copybooks. It also adds the ability for CICS to auto-detect uninitialized trailing storage in arrays, and to omit those records from the generated XML/JSON form.
This capability is also available on CICS TS 5.3 with APAR PI67641.

Enhancement of sockets domain (SO)
The sockets domain allows data that is received or sent over a TCP/IP socket to reside in any valid data location, which is normally either 31-bit (above-the-line) storage or 64-bit (above-the-bar) storage. This change relieves 31-bit storage, depending on the size of the HTTP body that is sent or received.
As a result, the following EXEC CICS WEB commands are changed:
For the WEB RECEIVE (Server) command, CICS receives the body of the server HTTP request into above-the-bar storage if the HTTP request contains a Content-Length header or is sent as a chunked request. The body is copied into below-the-bar storage only when CICS needs to provide a below-the-bar version for the server application.
- If the HTTP server body is held in a container before it is sent to the server, CICS keeps the body in and sends it from above-the-bar storage.
- If the HTTP server body is held in an application buffer and needs to be copied or converted before it is sent, CICS keeps the body in and sends it from above-the-bar storage.

EXCI support for channels and containers
The external CICS interface (EXCI) can pass more than 32 K of data. EXCI now supports passing a CHANNEL with its set of containers, instead of passing a COMMAREA, when linking to a CICS program from a non-CICS address space.
EXCI supports issuing EXEC CICS PUT CONTAINER, GET CONTAINER, MOVE CONTAINER, DELETE CONTAINER, and DELETE CHANNEL commands in batch.
EXCI also provides the ability to do code page conversion in and out of containers.
A channel can be specified on both the EXEC API (EXEC CICS LINK) and the call level API (DPL_REQUEST).
Any CICS applications that are coded to the channels and containers API and invoked by CICS Distributed Program Link (DPL) can now also be invoked unchanged from an EXCI client, including CICS applications that run on previous releases of CICS TS that support channels and containers.

New execution diagnostic facility transactions
New transactions CEDG and CEDY, read-only forms of CEDF and CEDX, are now available. You can examine application programs by using CEDG and CEDY, but you cannot modify resources or alter the execution of commands.

Decision Server Insights Event format
The Decision Server Insights Event format is an XML representation of a CICS event that is recognized by the Decision Server Insights component of IBM® Operational Decision Manager. This format can also be used by any consumer that can recognize the Decision Server Insights Event format.
This capability is also available on CICS TS V5.1 and CICS TS V5.2 with APAR PI55133, and on CICS TS V5.3 with APAR PI55134.

Additional Event Processing (EP) enhancements
- Addition of new transient data queue (TDQ) EP adapter to emit events to any consumer that can read events from a TD queue.
- Custom EP adapters are passed capture data in a printable (character) form. A new set of containers (DFHEP.CHAR.nnnnn) is passed to custom EP adapters, which contain a printable version of the raw capture data that is passed in the DFHEP.DATA.nnnnn containers.
- Addition of the MESSAGE_TEXT capture item on a MESSAGE system event to allow the complete message text to be captured.
Learn more about TDQ adapter ...

Support for Kerberos mutual authentication through the EXEC CICS VERIFY TOKEN command
New options OUTTOKEN and OUTTOKENLEN are added to VERIFY TOKEN to support Kerberos mutual authentication.
This capability is also available on CICS TS V5.3 with APAR PI56774.

NOSUSPEND option on EXEC CICS named counter server commands
- DEFINE COUNTER and DEFINE DCOUNTER
- DELETECOUNTER and DELETE DCOUNTER
- GET COUNTER and GET DCOUNTER
- QUERY COUNTER and QUERY DCOUNTER
- REWIND COUNTER and REWIND DCOUNTER
- UPDATE COUNTER and UPDATE DCOUNTER

New resource, MQMONITOR, provides a better mechanism for controlling MQ trigger and bridge monitors
A new RDO-defined resource, MQMONITOR, is provided to complement the existing MQCONN resource. You can use this new resource to configure an MQMONITOR, which can be a trigger monitor, an MQ bridge monitor, or a user-written monitor.
Configuration options include the ability to specify a transaction ID to be used by the monitor, the user ID under which a monitor task runs, and the user ID to be used by the monitor to start the application tasks if an alternative user ID is not provided by the application. The AUTOSTART option automatically starts monitors when the CICS-MQ connection is started. Monitors are automatically stopped when the CICS-MQ connection is stopped. Any number of MQMONITOR resources can be defined and installed. Using the MQMONITOR resource removes the need to use the CKQC transaction to start and stop monitors manually.
With the introduction of the MQMONITOR resource, CICS now differentiates between the userID under which the transaction that is monitoring the MQ queue runs (the MONUSERID) and the userID under which the initiated transactions run. This userID (the USERID) is used by default, unless it is otherwise provided. This has implications for any MQMONITOR resources that are dynamically created when an MQCONN is installed. See Review the use of MQCONN for details.

Removal of TCB switch for Java applications that access MQ
CICS Java applications that run in an OSGi JVM can now use the MQ Classes for Java and the MQ Classes for JMS to access IBM MQ for z/OS from a T8 TCB instead of forcing a move to an L8 TCB.
The CICS-MQ task-related user exit changed to take advantage of an enhancement to the RMI that allows TRUEs to run on any key 8 TCB, not just an L8 TCB. The REQUIRED option on the ENABLE PROGRAM command is used to specify that a task-related user exit must run on an open TCB. If OPENAPI is specified with REQUIRED, an L8 TCB is used. If OPENAPI is not specified, any key 8 open TCB is used. Hence the CICS-MQ TRUE is enabled with the REQUIRED option but not the OPENAPI option.
The change in TCB switch behavior affects the results that you see in CICS monitoring and statistics. TCB usage for Java MQ applications is changed in that MQ CPU time is now accumulated against a T8 TCB. End of task syncpoint processing is still accumulated on an L8 TCB.

Improved management of JVM servers and associated CICS tasks
The ability to robustly manage workloads is critical to an application server. CICS can now remove disruptive tasks from the JVM server by using the PURGE option on the SET TASK command. (This command should be used with caution and with the understanding that objects that are modified by that application might be left in an inconsistent state.) In addition, when disabling the JVM server by using the SET JVMSERVER command, CICS can now remove associated threads and tasks in an orderly sequence in most situations.

Non-Java support for JSON web services
JSON messages can now be processed in CICS regions with no Java configuration. You don't have to configure and install a JVM server. Performance and throughput for many workloads will be better than when using a JVM server to process JSON messages.
To set up CICS as a non-Java JSON service provider, you must configure a provider pipeline that uses the CICS-supplied program DFHPIJT as the terminal handler. For detailed instructions, see Creating the CICS infrastructure for a non-Java JSON service provider.

System autoinstall of program definitions for Language Environment
CICS now uses system autoinstall to install program definitions for Language Environment® as required, removing the need to maintain definitions in the CEE CSD group. Only those programs that are used have their definitions installed.
This capability is also available on CICS TS V5.1 and CICS TS V5.2 with APAR PI60388 and APAR PI73184, and on CICS TS V5.3 with APAR PI60389.

Changes to the CICS IPIC heartbeat function
The CICS IPIC heartbeat function is changed. IPIC heartbeat messages are sent out only if the connected CICS region is running in a different sysplex.

XPTKT now defaults to making a RACF check before generating a PassTicket
The CICS system initialization parameter, XPTKT, now defaults to YES. This means that CICS makes a RACF® check before generating a PassTicket. If you have applications that generate PassTickets by using the EXEC FEPI REQUEST PASSTICKET, EXEC CICS REQUEST PASSTICKET, or EXEC CICS REQUEST ENCRYPTPTKT commands, you must create RACF definitions to allow regions (and, optionally, user IDs or groups) to generate PassTickets.

3270 Intrusion Detection Service (IDS)
This service allows CICS to detect if 3270 emulators invalidly modify protected fields, potentially compromising the security of an application. You can opt into this capability with a feature toggle, as described in Specifying feature toggles. You configure this service by using feature toggle com.ibm.cics.bms.ids.
CICS BMS 3270 IDS works with the z/OS Communications Server 3270 Intrusion Detection Service to provide an IDS that handles all 3270 or BMS applications. The BMS only service was previously called BMS 3270 data stream validation and was configured using a user replaceable module (URM).

Support for ABSTIME format in EXTRACT STATISTICS command
The EXTRACT STATISTICS SPI command now can return the time at which the counters for the requested statistics were last reset in ABSTIME format, through the new LASTRESETABS option. ABSTIME specifies the absolute time, which can be transformed into any familiar format by using the FORMATTIME command. You can now handle time periods that cross a day boundary more easily.

New fields added to TCP/IP statistics
New fields are added to TCP/IP global statistics and TCP/IP services resource statistics to provide more information about TCP/IP performance.
- New fields in TCP/IP: Global statistics
- The new fields better illustrate how well connections are reused to give a view of connection persistence for a CICS region.
- New fields in TCP/IP services: Resource statistics
- Some new fields illustrate how well connections are reused to give a view of connection persistence for connections into a specific TCPIPSERVICE.
- Some new fields show the effects of performance tuning for HTTP connections on a TCPIPSERVICE.
- Some new fields show the socket backlog and details on connections that are dropped to help diagnostics when CICS is under stress.

New options to dump non-CICS address and data spaces
New options, JOBLIST and DSPLIST, are added to the INQUIRE SYSDUMPCODE and SET SYSDUMPCODE commands to dump additional non-CICS address spaces and data spaces when a CICS dump is triggered.
You can set JOBLIST and DSPLIST only through the SET SYSDUMPCODE SPI command or the CEMT SET SYDUMPCODE command. JOBLIST and DSPLIST are inquire-only for CPSM SYSDUMP.

New system initialization parameter allows preset userid terminals to share a single ACEE
A new system initialization parameter, SNPRESET, allows userid terminals that are associated with the same user ID to share a single ACEE. You can save storage by specifying SNPRESET=SHARED.

New option to restart a CICS region after a normal shutdown
A new option, RESTART, is added to the PERFORM SHUTDOWN command to support the automatic restart of CICS regions even if they shut down normally.
If you specify the RESTART option on the PERFORM SHUTDOWN command for a CICS region, when the region shuts down normally, it is restarted by MVS Automatic Restart Manager (ARM) after the shutdown.

VSAM data set access control is extended for GDPS/Active-Active availability solutions
To enhance the IBM GDPS®/Active-Active (GDPS/AA) availability solution to support replication of VSAM data for active-standby and active-query configurations, you can now set VSAM data sets to allow only replication programs to have full access, and other programs to have read access only.
The AVAILABILITY option of the SET DSNAME and INQUIRE DSNAME commands has a new CVDA value, RREPL. If you specify AVAILABILITY(RREPL) for a VSAM data set, full access to the data set is restricted to REPLICATOR programs. Other programs only have read access. The new AVAILABILITY(RREPL) option allows you to set up a fence that is specific to a VSAM data set, rendering the data set accessible only for read and replication. To remove the fence, issue a SET DSNAME AVAILABILITY(AVAILABLE) command.
The SET PROGRAM and INQUIRE PROGRAM SPI commands have a new option, REPLICATION, which allows you to specify REPLICATOR programs. For a REPLICATOR program to update a VSAM data set in the AVAILABILITY state of RREPL, the program must be executed in the region that owns the data set.

New previous transaction association data
To enable more efficient use of the new CICS asynchronous API, association data identifies the local or parent task of a request to attach a task by an EXEC CICS RUN TRANSID command to allow the transaction tracking and monitoring of parent and child tasks. The new association data also works for EXEC CICS START commands that are not a new point of origin.

Support for the z/OS Workload Manager Health API
CICS now uses the z/OS Workload Manager Health (IWM4HLTH) API as a means of controlling the flow of work into a CICS region. This service is used to inform z/OS WLM of the health state of a server (in this context, a CICS region). This can allow a CICS region to have a warm-up process after the end of system initialization until the region is fully ready to receive work.
The WLMHEALTH system initialization parameter specifies the parameters to be used by CICS on z/OS WLM Health API (IWM4HLTH) calls, which CICS makes to inform WLM about the health state of a CICS address space. You can view the z/OS WLM health service settings for CICS regions through the INQUIRE WLMHEALTH SPI command or the CEMT INQUIRE WLMHEALTH command. You can also change the health service settings by using the SET WLMHEALTH SPI command or CEMT SET WLMHEALTH.
The primary user of CICS regions' health indicator values is TCP/IP, but the values are also used by CICS and CPSM components. When TCP/IP is configured, the health indicator feeds into the WLM server recommendations to sysplex distributor, affecting when connections are established with a CICS region. In CICS, the health indicator affects when MQ trigger monitors, the MQ Bridge, and user-written MQ consumers that are using the MQMONITOR resource are started and stopped. In addition, CPSM workload management takes into account the health state of target AORs when deciding where to route work.

New CMCI URI parameter OVERRIDEWARNINGCOUNT
- RESOURCELIMIT is set to WARNING.
- DEFAULTWARNCNT is non-zero (which means a non-zero default warning count limit).
OVERRIDEWARNINGCOUNT is applicable to DELETE, GET, and PUT requests, but accepted by POST with no effect.

Changes to defaults of resource definition attributes
- To avoid the inadvertent use of 24-bit storage, defaults of the following attributes are changed:
- DATALOCATION on program definitions
- TASKDATALOC on transaction definitions
- To allow better recovery from failure and stall scenarios, defaults of attributes that affect
transaction purgeability are changed:
- SPURGE and TPURGE on transaction definitions

Changes to the way that CICS handles unused HTTP persistent connections
If you are using a TCPIPSERVICE resource for CICS web support with the HTTP protocol, when a command is issued to close the TCPIPSERVICE and there are unused HTTP persistent connections, CICS now ensures that the TCPIPSERVICE closes within 30 seconds or within the time as specified in the TCPIPSERVICE SOCKETCLOSE attribute if this value is less than 30 seconds.

Support for IBM Health Checker for z/OS
IBM Health Checker for z/OS provides a foundation to help simplify and automate the identification of potential configuration problems. CICS TS now supports three health checker rules that define best practice for CICS TS security. If a CICS region becomes non-compliant with these security best practices, a warning message is issued so that you can take corrective actions.

Support for system rules in CICS policies
If you want to monitor the state of system resources or the overall health of a CICS system, you can define system rules in CICS policies. System rules define an automated action to be performed (issue a message or emit a CICS event) when something of interest happens in a CICS system, such as a resource state change, a threshold that is crossed, or an unusual system state or action.
System rules provide equivalent function to system events, which are now deprecated. You should use system rules instead.
Following the introduction of system rules, policy threshold rules are renamed to policy task rules.

CICSPlex SM tasks in a MAS changed to be system tasks
Tasks that are internally initiated by CICSPlex® SM in a MAS and that have transaction IDs beginning with the characters CO are changed to run as CICS system tasks. As a result, these tasks are no longer displayed among active tasks in a MAS that is at CICS TS Version 5.4 or later. Web User Interface (WUI) tasks and CPSM utility transactions (for example COLM for starting the MAS agent initialization) continue to run as user tasks.
- A MAS can now have an initial user task count of zero tasks, even when the MAS agent is active.
- In a CICSPlex, where workload target regions are a mix of both CICS TS V5.4 and lower releases, the workload distribution favors target regions that run CICS TS V5.4 because those regions have a lower initial user task count. CICSPlex SM WLM continues as normal to select the target region with the lowest routing weight and the bias disappears as the CICS TS V5.4 target regions calculated routing weight starts to equal or exceed that of the lower CICS TS releases.
- It is no longer possible to purge CPSM internal system tasks, protecting the system from accidental damage.

New STALLASYCNT and STALLASYTSK system parameters for CICSPlex SM
Two new system parameters, STALLASYCNT and STALLASYTSK, are introduced to CICSPlex SM to enable the tracking and STALL detection of asynchronous tasks.

Change in TCB allocation for Liberty threads
To alleviate the potential impact of Liberty thread pooling on zIIP-eligibility of workloads, tasks that run as Liberty threads now invoke a TRUE on the T8 TCB that CICS provided to the Liberty ThreadPool. All other tasks continue to invoke it on the QR TCB.
This capability is also available on CICS TS V5.3 with APAR PI54263.

Support for new deployment tasks in DFHDPLOY
DFHDPLOY is enhanced to perform PIPELINE SCAN, PROGRAM NEWCOPY, and PROGRAM PHASEIN. This enables automation to be written to update these resources without requiring the direct use of the CICSPlex SM API.
This capability is also available on CICS TS V5.1, CICS TS V5.2, and CICS TS V5.3 with APAR PI72104.

Feature toggles to enable new features that are available to in-service or open beta CICS releases
CICS delivers features on a continual basis to enhance its capabilities. You can now enable new features that are made available to in-service or open beta CICS releases by configuring feature toggles. This mechanism gives you more control over the enablement of such features.

z/OS Provisioning Toolkit, a command-line utility to rapidly provision and deprovision CICS and other z/OS environments
IBM z/OS Provisioning Toolkit (z/OS PT) is a simple command-line utility that uses the IBM z/OS Management Facility (z/OSMF) REST API to rapidly provision and deprovision CICS and other z/OS development environments. System programmers can set up the environments, authorize access to individuals or teams, and set provisioning controls and limits. Then, using a command-line interface, application developers can quickly provision and deprovision environments, without needing mainframe administration skills or authority.

Changes to documentation
- Documentation for CICS Explorer® in IBM Knowledge Center is published independently from the documentation for CICS Transaction Server. The CICS Explorer documentation is in CICS Explorer User Guide.
- The table of contents in IBM Knowledge Center is streamlined into fewer sections.
- There are a number of changes to the way that the PDF manuals are structured and delivered.
- IBM Knowledge Center V2.0 withdrew support for creating bespoke PDFs. As a consequence, the collections that were provided to support this facility are also withdrawn from the CICS documentation.