CRTE (Routing Transaction)

To run transactions owned by a connected CICS® region.

Syntax

CRTE SYSID{=sysId | (sysId) }

Options

sysId: the four-character key of the Communications Definitions (CD) entry that defines the remote region in which the transaction is to run.

Example:

To route to the remote region whose local CD definition is called REG1:

CRTE SYSID=REG1

Description

You can use CRTE to run transactions that reside on a connected remote CICS 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 reside on all systems. It avoids the necessity of defining the remote CEMT in the local system with a different name.

The transactions that are run can include pseudoconversational transactions in addition to CRTE itself.

The terminal through which CRTE is run must be defined on the remote system (the application-owning region) or it must be shipped from the local region (the terminal-owning region).

The routing transaction verifies that the specified remote region is known and is available. If it is, a message confirms that a routing session to the required region is started. You can then clear the screen and enter the transaction code for the transaction to be run on that system. Enter input of the form:

yyyyzzzzzz...

where yyyy is the name by which the required remote transaction is known on the remote region, and zzzzzz... is the initial input to that transaction. Subsequently, you can use the remote transaction as if you have defined it locally and run it in the ordinary way. In fact, you use the terminal as if it were connected directly to the remote region.

When using CRTE, security checking on the remote system is not affected by the user ID that you used to sign on to the local system. Instead, security checking depends on whether you sign on by using CESN or CESL while using CRTE.

If you do not sign on (if you do not use CESN/CESL), you are given the remote region’s default user ID. When a transaction is run, the security checks are performed against this default user. A check is also done against the link user ID to see whether the remote system itself has authority to access the resource. Therefore, access is granted to those resources defined for the default user ID that are also defined for the link user ID. If a link user ID is not specified, access is granted to those resources defined for the default user ID that are also defined in the Communications Definitions (CD) entry TSLKeyMask and RSLKeyMask attributes.
If you do sign on to the remote region while running CRTE (using CESN or CESL), access is granted to those resources defined for the signed on user ID that are also defined for the link user ID. If a link user ID is not specified, access is granted to those resources defined for the default user ID that are also defined in the Communications Definitions (CD) entry TSLKeyMask and RSLKeyMask attributes.

You end a routing session by entering the CANCEL keyword. This keyword automatically signs you off from the connected region (assuming that you were signed on in that region). When a routing session is ended, CICS displays the message:

ROUTING SESSION TO SYSTEM sysId TERMINATED

If you have used CRTE to route transactions through more than one system, you must enter CANCEL the same number of times that you entered CRTE to end the routing session.

Note: In a chain of CRTE sessions, different systems can be in different locales. The term locale is used to refer to a subset of a user's environment that defines conventions for a specified culture, such as time formatting, numeric formatting, monetary formatting, and character classification, conversion, and collation. Refer to your operating system documentation for more information about locales and how they are used.

Although the routing transaction is implemented as a pseudoconversational transaction, CICS holds the terminal from which the transaction is run until CICS terminates the routing session.

While a terminal is in a routing session with another region (that is, during the period between entering CRTE and CANCEL) the terminal cannot receive messages that are delivered by automatic transaction initiation (ATI).

See CESN (Signon) and CESL (Signon Long) for information about what user ID is used and what level of security you are given when using CRTE to change user IDs after you have used CRTE.

Starting and ending CRTE

You start the CRTE transaction directly by entering the tranid CRTE. The transaction ends when the CANCEL keyword is used.