Exit XALTENF
Exit XALTENF is invoked by the terminal allocation program when the terminal that an ATI request from transient data or interval control requires is unknown in this system. The exit program is expected to give a return code indicating whether the terminal exists on another connected CICS® system and, if so, on which one.
- Exit-specific parameters
-
- UEPALEVT
- Address of 2 bytes containing the type of request. The equated
values of the types are:
- UEPALESD
- START command with data
- UEPALES
- START command without data
- UEPALETD
- Transient data trigger level reached.
- UEPALTR
- Address of 1 byte containing an indication of whether the task
issuing the START command was started by transaction routing. The
equated values are:
- UEPALTY
- A START command was being processed and the task issuing the command was transaction routed to.
- UEPALTN
- A START command was not being processed or a START command was being processed but the task issuing the command was not transaction routed to.
- UEPALFS
- Address of 1 byte containing an indication of whether the START
command was function shipped. The equated values are:
- UEPALFY
- A START command was being processed and the START was function shipped.
- UEPALFN
- A START command was not being processed or a START was being processed but it was not function shipped.
- UEPALTRN
- Address of 4 bytes containing the name of the transaction to be run.
- UEPALRTR
- Address of 4 bytes containing the name of the terminal on which the transaction should run. (If a transient data trigger level was reached and the transient data queue definition specified a system, then this would contain a system identifier.)
- UEPALCTR
- Address of 4 bytes containing, for START commands, the name of
the current terminal if the command was transaction routed, or the
name of the session if the command was function shipped.
For other START commands and for transient data trigger events, the field pointed to contains blanks.
- UEPALNTI
- Address of 8 bytes containing, for function-shipped START commands,
the netname of the last system from which the request came.
For START commands issued in this system by transaction routing to a task, the netname of the last system from which the task was routed.
For other START command situations and for transient data trigger level events, the field pointed to contains blanks.
- UEPALSYI
- Address of 4 bytes containing, if UEPALNTI contains a netname,
the corresponding sysid.
If UEPALNTI does not contain a netname, the field pointed to is blank.
- UEPALNTO
- Address of 8 bytes containing the contents of UEPALNTI.
If it sets a return code of ‘UERCNETN', your exit program must place in this field the netname of the system to which the ATI request should be sent.
- UEPALSYO
- Address of 4 bytes containing the contents of UEPALSYI.
If it sets a return code of ‘UERCSYSI', your exit program must place in this field the sysid of the system to which the ATI request should be sent.
- UEPALNNI
- Address of a 4-byte input field containing the netname of the terminal on which the transaction is to run, if this is known to CICS. If CICS does not know the netname, the addressed field contains blanks.
- UEPALNNO
- Address of a 4-byte input/output field containing, on invocation, the contents of UEPALNNI. Your exit program can use this field to supply the netname of the terminal on which the transaction is to run. It is important that your exit program supply a terminal netname if the TOR to which it directs the ATI request is a member of a z/OS® Communications Server generic resource.
- Return codes
-
- UERCTEUN
- Terminal unknown, reject request.
- UERCNETN
- Terminal known, netname returned in UEPALNTO.
- UERCSYSI
- Terminal known, sysid returned in UEPALSYO.
- XPI calls
- You can use:
- INQ_APPLICATION_DATA
- INQUIRE_SYSTEM.
No other XPI calls should be used.