Changes to CICS transactions

This section summarizes the changes to the CICS® transactions across supported CICS releases.

If you are upgrading from an end-of-service release, you can find information about the changes that are relevant to those releases in Summary of changes from end-of-service releases.

If there are changes to the category 2 transactions, you must rerun the DFH$CAT2 CLIST provided in SDFHSAMP library.

For information about the changes to the CICS main terminal transaction CEMT, see Changes to CEMT.

Highlights of changes across supported releases of CICS TS

Table 1 lists new and changed CICS-supplied transactions in each supported CICS TS release. The number following the transaction name indicates its security category. The links provided take you to the relevant tables below where brief descriptions of the changes are provided.

Table 1. Highlights of CICS transactions changes across supported releases of CICS TS
5.4 5.5 5.6 6.1
NEW:
NEW with APAR:
NEW: NEW: NEW:
CHANGED:
CHANGED with APAR:
CHANGED:
CHANGED with APAR:
CHANGED: CHANGED:
  • All Category 1 transactions:

    The RACF check to validate the CICS region user ID is entitled to run a Category 1 transaction is removed at this release.

  • CDBT 2
  • CEPD 1
  • CJSA 2
  • CJSU 2

Changes to CICS transactions by release of CICS TS

View changes by transaction.

The program and CSD group for these transactions are shown in List of CICS transactions.

CDBE
Security category: 1
5.4 5.5 5.6 6.1
  NEW    
CDBF
Security category: 2
5.4 5.5 5.6 6.1
Security category: 1 CHANGED to a Category 2 transaction    
CDBP
Security category: 1
5.4 5.5 5.6 6.1
  NEW    
CDBQ
Security category: 2
5.4 5.5 5.6 6.1
Security category: 1 CHANGED to a Category 2 transaction    
CDBT
Security category: 2
5.4 5.5 5.6 6.1
      CHANGED:

The SPURGE attribute has been changed from SPURGE(NO) to SPURGE(YES).
CEDA, CEDB, CEDC
Security category: 2
5.4 5.5 5.6 6.1
    CHANGED:

The dataset associated with the CSD for the local region is now displayed on the panel in format DSN=<dataset name>.

  
CEDG
Security category: 2
5.4 5.5 5.6 6.1
NEW      
CEDY
Security category: 2
5.4 5.5 5.6 6.1
NEW      
CEMN
Security category: 2
5.4 5.5 5.6 6.1
  NEW OPTIONS to set URIMAP and WEBSERVICE resource limits    
CEPD
Security category: 1
5.4 5.5 5.6 6.1
      CHANGED:

Enhanced to generate an SMF type 110 subtype 1 CICS monitoring record every 2000 events processed by CEPD tasks in the region.
CEPR
Security category: 2
5.4 5.5 5.6 6.1
NEW      
CESF
Security category: 3
5.4 5.5 5.6 6.1
    CHANGED:

Now subject to the control of GMTRAN=(,DISCONNECT) so that the terminal session is disconnected upon sign-off.

  
CFCT
Security category: 1
5.4 5.5 5.6 6.1
NEW with APAR PI97207 NEW    
CHCK
Security category: 1
5.4 5.5 5.6 6.1
NEW      
CJSA
Security category: 2
5.4 5.5 5.6 6.1
      CHANGED: The SHUTDOWN attribute has been changed from SHUTDOWN(DISABLED) to SHUTDOWN(ENABLED)
CJSS
Security category: 1
5.4 5.5 5.6 6.1
    NEW  
CJSU
Security category: 2
5.4 5.5 5.6 6.1
      CHANGED: The SHUTDOWN attribute has been changed from SHUTDOWN(DISABLED) to SHUTDOWN(ENABLED)
CJXA
Security category: 2
5.4 5.5 5.6 6.1
    NEW  
CKBR
Security category: 2
5.4 5.5 5.6 6.1
CHANGED with APAR PH22136: CKBR now handles temporary errors that occur when issuing MQOPEN and MQGET requests. Rather than terminating, CKBR will retry every minute for up to an hour. If the error is not resolved after an hour, the monitor transaction will then terminate. CHANGED with APAR PH22136: CKBR now handles temporary errors that occur when issuing MQOPEN and MQGET requests. Rather than terminating, CKBR will retry every minute for up to an hour. If the error is not resolved after an hour, the monitor transaction will then terminate. CHANGED: New parameter SMFMQGET, instructing CICS to write SMF type 110 records for MQGET requests issued by the CICS-MQ bridge.

CKBR now handles temporary errors that occur when issuing MQOPEN and MQGET requests. Rather than terminating, CKBR will retry every minute for up to an hour. If the error is not resolved after an hour, the monitor transaction will then terminate.

  
CKTI
Security category: 2
5.4 5.5 5.6 6.1
CHANGED:

The default user ID for the CKTI transaction processing messages for resource MQINI(DFHMQINI) is changed to the value specified in either DFLTUSER or PLTPIUSR.

CHANGED with APAR PH22136:

CKTI now handles abends produced when starting user transactions. If an abend occurs when the CKTI transaction attempts to start the user transaction, rather than terminating, CKTI will now send the trigger message to the dead-letter queue, and trigger monitor processing continues.

CKTI now handles temporary errors that occur when issuing MQOPEN and MQGET requests. Rather than terminating, CKTI will retry every minute for up to an hour. If the error is not resolved after an hour, the monitor transaction will then terminate.

 CHANGED with APAR PH22136:

CKTI now handles abends produced when starting user transactions. If an abend occurs when the CKTI transaction attempts to start the user transaction, rather than terminating, CKTI will now send the trigger message to the dead-letter queue, and trigger monitor processing continues.

CKTI now handles temporary errors that occur when issuing MQOPEN and MQGET requests. Rather than terminating, CKTI will retry every minute for up to an hour. If the error is not resolved after an hour, the monitor transaction will then terminate.

 CHANGED:

CKTI now handles abends produced when starting user transactions. If an abend occurs when the CKTI transaction attempts to start the user transaction, rather than terminating, CKTI will now send the trigger message to the dead-letter queue, and trigger monitor processing continues.

CKTI now handles temporary errors that occur when issuing MQOPEN and MQGET requests. Rather than terminating, CKTI will retry every minute for up to an hour. If the error is not resolved after an hour, the monitor transaction will then terminate.

  
CLGR
Security category: 1
5.4 5.5 5.6 6.1
      NEW

CICS user journal automatic recovery
CMPE
Security category: 1
5.4 5.5 5.6 6.1
NEW      
CNJL
Security category: 1
5.4 5.5 5.6 6.1
  NEW    
CNJW
Security category: 2
5.4 5.5 5.6 6.1
  NEW    
COHT, COIE, COIR, COI0, CONA, COND, CONH, CONL, CONM, COWC
Security category: 1
5.4 5.5 5.6 6.1
CHANGED to Category 1 transactions      
CPIW
Security category: 2
5.4 5.5 5.6 6.1
      NEW

A direct clone of CPIH used to handle WS-AT protocol messages.

URIMAP DFHRSURI now specifies TRANSCTION(CPIW) instead of CPIH. If you are using a customized version of DFHRSURI that no longer specifies TRANSACTION(CPIH), no action is needed and you can continue to use your customized DFHRSURI unchanged.

However, if the CSD is being shared with a back level region, and if the CICS-supplied DFHWSAT group has been installed (instead of a customized DFHRSURI), take one of the following actions:
  • Make sure authority is given to run CPIW.
  • Install a customized version of DFHRSURI that specifies TRANSACTION(CPIH), ahead of the DFHWSAT group.
CQRC
Security category: 1
5.4 5.5 5.6 6.1
    NEW  
CSFE
Security category: 2
5.4 5.5 5.6 6.1
    CHANGED:

CSFE has been enhanced to allow authorized users to change the CONFDATA settings.

  
CWDP
Security category: 2
5.4 5.5 5.6 6.1
    NEW  
CWGQ
Security category: 2
5.4 5.5 5.6 6.1
  NEW