Exit Point

User Exits › Member Existence Exit Interface › Exit Point

Exit Point

Using these parameters, the exit point must set one of the return Codes in register 15 as shown below.

Return Code	Purge Request?	Interpretation	Verify Flag Setting
0	No	Member found (member validated by the exit)	blank
4	No	Member not found (member rejected by the exit)	V
8	No	Nothing processed	unchanged
12	No	Error encountered	V
0	Yes	Member purged or didn't exist	N/A
4	Yes	Member doesn't exist, exit has message to be reported	N/A
8	Yes	Exit doesn't support purge	N/A
12	Yes	Error encountered	N/A

Notes:

In case of an error, the exit sets the error code and error message and returns to the caller.
The verify flag is not used for exit Codes 7, 8, and A.
If the return code is not 0 or 8, CA‑PanAPT displays the first error message generated and contained in the field APCS02XX‑MSG. CA‑PanAPT ignores all other fields.
If the return code is not 0 or 8 for Codes 1 through 6, or if the return code is not 0 for Code A, messages are written to the ISPF Log file. The Log file can be viewed online using ISPF Dialog Test, LOG facility (=7.5). For Code 7, messages are viewed online during the BAK action. For Code 8, messages are written to the APCS5310-01 report.
If the return code is 8, verify flags remain the same and there is no error message or Log message.
Any other return code is treated as an internal error. CA‑PanAPT displays the message contained in the field APCS02XX‑MSG.

Important! The member existence exit is called from many different places in the online and batch Move process in an effort to give the most current information about each member of the Move Request. Verifying existence is resource intensive; it requires allocation/deallocation as well as open and close processing for each member. If an exit verified each member each time the exit was called, much of the information would be redundant and the online response time would be degraded.

The sample exits provide a compromise between response time and currency of information. If you find that the information is not current enough and want to add the overhead of an additional verification, you can insert an entry into the verify table (APAMXTBL‑TABLE or APCCXTBL-TABLE for COBOL) for each exit that allows the extra verify process.

For example, suppose you want to ensure that the verify flag is current for a member in any of the following conditions:

The member had been previously verified (verify flag is blank)
After Change processing (Code=4)
Auto Retrieve is not enabled (N)

Insert the following entry into the verify TABLE of each exit:

DC CL3' 4N' VERIFY DONE, POST‑CHANGE, NO AUTO RETRIEVE

These Codes are explained in the source code for each of the sample exits. Note that the exits can perform additional edits on each member based upon information in the Inventory Record and/or the point in the Move processes from which the exit is being called. You can use this information to call your security system if you desire.