IBM SC34-6814-04 Server User Manual


 
Good morning message program exit XGMTEXT
When invoked
Before the good morning message is transmitted.
Exit-specific parameters
UEPTCTTE
Address of the terminal control table terminal entry (TCTTE). The
TCTTE can be mapped using the DSECT DFHTCTTE.
UEPTIOA
Address of the terminal input/output area (TIOA). The TIOA can be
mapped using the DSECT DFHTIOA. However, fields TIOASAL and
TIOASCA are not programming interfaces.
Return codes
UERCNORM
Continue processing.
UERCPURG
Task purged during XPI call.
XPI calls
All can be used.
HTTP client open and send exits: XWBAUTH, XWBOPEN and
XWBSNDO
Exits XWBAUTH, XWBOPEN, and XWBSNDO are invoked during processing of
EXEC CICS WEB CONVERSE, EXEC CICS WEB OPEN, EXEC CICS INVOKE WEBSERVICE, and
EXEC CICS WEB SEND commands. They are used in making HTTP client requests
from CICS as an HTTP client, which is a facility provided by CICS Web support. For
details of these exits, see the CICS Internet Guide.
Related concepts
“The HTTP client sample exit programs” on page 20
These sample programs are for use with the Web domain exits, XWBOPEN and
XWBAUTH,.
Intersystem communication program exits XISCONA and XISLCLQ
The two exits in the intersystem communication program allow you to control the
length of intersystem queues.
There are several methods that you can use to control the length of intersystem
queues. For a description of the available methods, see the CICS
Intercommunication Guide.
The XISCONA exit
Important
It is recommended that you use the XZIQUE exit, in the VTAM working-set module,
to control the length of intersystem queues, rather than XISCONA. (XZIQUE is
described in “XZIQUE exit for managing MRO and APPC intersystem queues” on
page 249.) XZIQUE provides more functions, and is of more general use than
XISCONA (it is driven for function shipping, DPL, transaction routing, and distributed
transaction processing requests, whereas XISCONA is driven only for function
shipping and DPL). If you enable both exits, XZIQUE and XISCONA could both be
driven for function shipping and DPL requests, which is not recommended.
138 Customization Guide