Previous Topic: Server Side ExitsNext Topic: COBOL—CICS and IMS Server Manager Runtime Exits


C—Transaction Enabler, Server Manager Runtime Exits

The following table gives a brief description of the C exits. These user exits are invoked from the Transaction Enabler components and Distributed Processing generated for C.

Server Side: Language: C Function Area: Server Manager/Server Runtime

User Exit Name

Source Code

Description

SRVRERROR

tirserrx.c

Server to server error exit that is invoked when an error condition occurs during server-to-server flow.

TIRDCRYP

tirdcryp.c

Server side cooperative flow decryption exit (CFB only)

TIRELOG

tirelog.c

Server side Error logging and Error token creation exit.

TIRMTQB

tirmtqb.c

Runtime Message Table Exit number to error text translation exit. The passed in error number is used to obtain a standardized error message string defined within the exit.

TIRNCRYP

tirncryp.c

Server side cooperative flow encryption exit (CFB only)

TIRSECR

tirsecr.c

Security check interface. This exit provides an opportunity for a server to validate the user ID as returned from TIRUSRID.

TIRSECV

tirsecv.c

Validates security given Client Userid, Client Password, Client Security Token retrieved from the security offset of an enhanced CFB. This exit will not be called if the CFB is not an enhanced security CFB.

TIRSYSID

tirsysid.c

Allows modification of the system ID. This user exit returns a default system ID, the value of which depends on the platform on which the server is executing.

TIRUSRID

tirusrid.c

Allows modification of the user ID. This routine returns a default user ID, the value of which depends on the platform on which the server is executing. The returned ID is passed to TIRSECR for validation.

TIRXINFO

tirxlat.c

This user exit provides information about the local environments os, codepage and default padding character. The os and codepage are passed to the TIRXLAT exit.

TIRXLAT

tirxlat.c

This national language translation exit allows conversion of textual data based on from/to codepage and operating system information.

USEREXIT

dpsuetdm

This user exit supports multiple APIs for access to user data and transaction data when the target server resides on an HP NonStop host. USEREXIT is called twice–just after the request data is received from the Distributed Processing Client (DPC), and again just before response data is returned to the DPC.

Note: For more information about the user exits, see the User Exit Reference Guide.