Previous Topic: NonStop Runtime User ExitsNext Topic: Comm Config Files


Modifying User Exits

User exit source code is provided in the C language so that you can modify them to meet custom site requirements. To assist with the lifecycle of user exits, the TACL macro MKEXITS is provided. This macro can be found in the subvolume where the IT has been installed. You can use MKEXITS to perform the following tasks:

Note: When working with user exits, link all user exits for a particular library (the set of runtime user exits in UEXITCO or the set of distributed processing server user exits in DPSUECO) regardless of the number of changes as the NLD linker program does not let you individually link one exit at a time. Therefore, track source code changes across all the user exits to prevent unexpected functionality to be included in the user exit libraries.

Important! Failure to link all user exits result in application failures due to unresolved externals at execution time.

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

The following server-side user exits are documented in the User Exit Reference Guide:

Name

Description

TIRDCRYP

Server Decryption Exit

TIRELOG

Server Error Logging and Error Token Creation Exit

TIRMTQB

Runtime Message Table Exit

TIRNCRYP

Server Encryption Exit

TIRSECR

Security Check Interface Exit

TIRSECV

Server Client Security Validation Exit

TIRSYSID

Server System ID Exit

TIRUSRID

Server User ID Exit

TIRXINFO

Server System Code Page and Operating System Id

TIRXLAT

National Language Translation User Exit

USEREXIT

NonStop RSC/MP Distributed Processing Flow Data Access Exit

Note: Not all of the user exits in the UEXITSC archive are documented in this appendix. For this user exits not directly involved in processing a cooperative flow, see the User Exit Reference Guide.