Entry Point Names

Installation and Configuration › Named User Exit Enablement › Entry Point Names

Entry Point Names

The following table identifies the exits that can be linked with IDMSUXIT and the name of the entry point that must be used in each case.

Exit	Entry Point Name
User ID exit for batch jobs using the 10.2 services interface	BTCIDXIT
RELOAD error exit	DBLUEREX
IDD batch compiler exit *	IDDEXITB
IDD online compiler exit *	IDDEXITO
ARCHIVE JOURNAL exit	IDMSAJNX
IDMSCALC exit	IDMSCLCX
IDMSDBIO duplex exit	IDMSDPLX
IDMSDBIO IO statistics exit	IDMSIOXT
IDMSDBIO I/O exit	IDMSIOX2
IDMSDBIO journal exit	IDMSJNL2
OLQ DML exit	OLQDMLX
Schema batch compiler exit*	SCHEXITB
Schema online compiler exit*	SCHEXITO
Subschema batch compiler exit *	SUBEXITB
Subschema online compiler exit *	SUBEXITO
SYSGEN batch compiler exit *	SGNEXITB
SYSGEN online compiler exit *	SGNEXITO
Ticker exit	TCKREXIT
User ID exit for batch jobs	USRIDXIT
Wait exit	WAITEXIT
Write to operator exit **	WTOEXIT
Write to operator reply exit **	WTOREXIT

* See the section Compiler Exits and Entry Points
**See the section Enabling WTOEXIT and WTOREXIT

Compiler Exits and Entry Points

Each compiler calls separate exit entry points in each of the batch and online environments. If you have separate exit modules for each compiler and each environment, you must change their entry points as indicated in the table in Entry Point Names. There are two ways you can change an entry point:

Change the entry point name in the source code and recompiling the program.
Use appropriate binder directives to change the entry point name when including the exit module in the link of IDMSUXIT.

We recommend changing the program source code and recompiling.

If you use the same exit module for more than one compiler or in more than one environment, you can continue to do so by changing the exit module to include entry points for each of the compilers and environments in which the module is to be used. Alternatively, you can use binder directives to change the name of one or more external references to match the name of your module’s entry point in IDMSUXIT. We recommend changing your exit program.

WTOEXIT and WTOREXIT Implementation

There are three ways you can implement WTO and WTOR exits:

By linking your exit routines with IDMSUXIT.
By specifying the name of the WTO and WTOR exits using DC/UCF system startup parameters.
In z/VSE, by linking your exit routines as phases WTOEXIT and/or WTOREXIT.

Note: If the second or third technique is used, CA IDMS dynamically loads the exit modules during startup and ignores any corresponding exit routine linked with IDMSUXIT.

For more information on using an OPS/MVS API rule as a replacement for the WTOEXIT, see the Appendix Sample OPS/MVS API rule. This can lead to improved performance when using the CA IDMS zIIP feature.

Note: You must link your exit modules with IDMSUXIT if you want to invoke the WTO and WTOR exits in batch jobs.