The global user exits XICTENF and XALTENF

You, as user of the system, know how this routing problem could be solved, and CICS gives you a way of communicating your solution to the system. The two global user exits XICTENF and XALTENF have been provided.

XICTENF is driven when interval control processes a START command and discovers the associated termid is not defined to the system. XALTENF is driven from the terminal allocation program also when the termid is not defined.

The terminal allocation program schedules requests resulting both from the eventual execution of a START command and from the transient data queue trigger mechanism. This means that a START command could result in an invocation of both exits.

The program you provide to service one or both of these global user exits has access to a parameter list containing this information:
  • Whether the ATI request resulted from: a START command with data, a START command without data, or a transient data queue trigger.
  • Whether the START command was issued by a transaction that had been the subject of transaction routing.
  • Whether the START command was function-shipped from another region.
  • The identifier of the transaction to be run.
  • The identifier of the terminal with which the transaction should run.
  • The identifier of the terminal associated with the transaction that issued the START command, if this was a routed transaction, or the identifier of the session, if the command was function-shipped. Otherwise, blanks are returned.
  • The netname of the last system the START request was shipped from or, if the START was issued locally, the netname of the system last transaction-routed from. Blanks are returned if no remote system was involved.
  • The sysid corresponding to the returned netname.

On exit from the program, you tell CICS whether the terminal exists and, if it does, you supply either the netname or the sysid of the TOR. CICS sends the ATI request to the region you specify. As a result, the terminal definition is shipped from the TOR to the AOR, and transaction routing proceeds normally.

There is therefore a solution to the problem shown in Figure 1. It is necessary only to write a small exit program that returns the CICS-supplied parameters unchanged and sets the return code for 'netname returned'.

The events that follow are shown in Figure 1:
  1. The interval control program accepts the START command and signals acceptance to the issuing system if this is required.
  2. After the specified interval has expired, or immediately if no interval was specified, the terminal allocation program tries to schedule the ATI request. It finds no terminal defined and takes the exit XALTENF, which again supplies the required netname.
  3. The ATI request is shipped to CICA. CICA allocates a relay transaction, establishes a transaction routing link to transaction X1 in CICB, and ships a copy of the terminal definition for T1 to CICB.
Figure 1. Resolving a 'terminal not known' condition on a START request
The picture illustrates the preceding text. It shows a terminal-owning region, CICA, connected to an AOR, CICB. On CICA, terminal T1 and the menu transaction, M1, are defined as local resources; transaction X1 is defined as owned by CICB.On CICB, transaction X1 is defined as local. There are no terminals defined.On CICA, the menu transaction M1 issues an EXEC CICS START TRANSID(X1) TERMID(T1) command. Seeing that X1 is owned by CICB, CICA function-ships the request to CICB. On CICB, the CICS interval control program, finding that it has no knowledge of terminal T1, drives the XICTENF global user exit. The exit program returns the netname CICA. The CICS terminal allocation program drives the XALTENF global user exit, which also returns the netname CICA. Now that it knows the owner of terminal T1, CICB ships the request to CICA, the terminal-owning region, for routing. CICA allocates a relay transaction, establishes a transaction routing link to transaction X1 in CICB, and ships a copy of the terminal definition for T1 to CICB.

The example in Figure 1 shows only one of many possible configurations. From this elementary example, you can see how to approach a solution for the more complex situations that can arise in multiregion networks.



dfht1c0054.html | Timestamp icon Last updated: Sunday, 4 June 2017