Defining the CICSPlex SM transactions in a CMAS

If transaction–attach security is active in a CMAS (that is, SEC=YES and XTRAN=YES∨classname are specified in the system initialization parameters), you must define to RACF® the CICSPlex® SM transactions that run in a CMAS. The following is a list of the transaction IDs that you must define to RACF for CICSPlex SM.

  • BMLT
  • LCPP
  • Start of changeLCMUEnd of change
  • LECI
  • LECR
  • LECS
  • LEEI
  • LEER
  • LEMI
  • LEMS
  • LENS
  • LMIR
  • LNCI
  • LNCS
  • LNMI
  • LNMS
  • LPDG
  • LPLK
  • LPLT
  • LPRT
  • LPSC
  • LPSM
  • LRLT
  • Start of changeLSGTEnd of change
  • LSRT
  • LWTM
  • MCCM
  • MCTK
  • MMEI
  • MMIS
  • MMST
  • PEAD
  • PELT
  • PMLT
  • PNLT
  • PPLT
  • PRLT
  • PRPR
  • PSLT
  • TICT
  • TIRT
  • TIST
  • TSMH
  • TSPD
  • TSSC
  • TSSJ
  • WMCC
  • WMGR
  • WMLA
  • WMQB
  • WMQM
  • WMQS
  • WMSC
  • WMWC
  • WMWT
  • WSCL
  • WSLW
  • XDBM
  • XDNC
  • XDND
  • XDNE
  • XDNR
  • XDNS
  • XDSR
  • XLEC
  • XLEV
  • XLNX
  • XLST
  • Start of changeXLMTEnd of change
  • XQST
Note: A list of these transactions is also contained in the CSD group EYU310G0.

The region userid, and any userid that may be specified on the PLTPIUSR system initialization parameter, must have authority to attach these transactions. In addition, and depending on the security attributes specified for any CMTCMDEF or CMTPMDEF, any userids which may flow from connected CMASs should have authority to attach these transactions. See Overview of intercommunication security for information on intercommunication security. For information about creating a CMAS to CMAS link definition, see CICSPlex System Manager Administration.

Start of changeThe region userid, and any userid that may be specified on the PLTPIUSR system initialization parameter, must have authority to attach these transactions. In addition, and depending on the security attributes specified for any CMTCMDEF or CMTPMDEF, any userids which may flow from connected CMASs should have authority to attach these transactions. Note that the CICS default userid may flow if the connected CMAS or MASs are defined as equivalent systems. End of change
The following transactions are supplied for debugging purposes under the guidance of IBM® support personnel, and are associated with a terminal:

CODB
COD0
COD1
COD2
COLU

They must be defined to RACF if transaction security is active, regardless of the CICS release running as the CMAS. Authority to initiate these transactions should be restricted to only those users who may become involved in working with IBM to resolve CICSPlex SM problems.

Start of changeGive users access to the CESD shutdown-assist transaction. Users who can attach CICSPlex SM transactions or define debugging transactions need access to CESD in case of CMAS failure.End of change

The COSD transaction allows a terminal user to shut down a CMAS. Access to this transaction should be granted only to those users who may need to shut down a CMAS