CICS routing transaction, CRTE

You can use the CICS® routing transaction, CRTE, with IPIC, LU6.2, or MRO links to run transactions that are on a connected remote system, instead of defining these transactions as remote in the local system.

CRTE is particularly useful for infrequently used transactions, or for transactions such as CEMT that are on all systems.

Ensure that the terminal through which CRTE is started is defined on the remote system or is defined as shippable in the local system. The terminal operator needs RACF® authority if the remote system is protected.

Security checking in the AOR for transactions that run under CRTE does not depend on what is specified on ATTACHSEC (for MRO and LU6.2 links) or USERAUTH (for IPIC links), nor does it depend on the user ID signed on in the TOR. Instead, security checking depends on whether the user signs on when using CRTE:
  • If the user does not sign on, the surrogate terminal created is associated with the AOR default user. When a transaction is run, the security checks are carried out against this default user. A check is also made against the link user ID to see whether the routing application itself has authority to access the resource.
  • If the user does sign on, using the CESN transaction while running CRTE, the surrogate points to the user ID of the signed-on user. For transactions attempting to access resources, security checking is made against the user ID of the signed-on user in the surrogate and the link user ID.