User Exits › Member Existence Exit Interface

Member Existence Exit Interface

The Member Existence Exit serves two purposes. The primary purpose is to verify that a member to be moved exists on the sending library. If the daily move job cannot find the member when it is time to move it, part of the processing fails and some Move Requests are not completed in a timely manner.

The Verify flag for each member of a Move Request displays the result of the most recent execution of the exit. You can view these flags on the Member Moves panel during Move Request Add, Change, or Inquire activities.

In addition to verifying member existence, the Member Existence Exit is also used to remove a member from the test library when a purge of the member is requested. Of the exits distributed with CA‑PanAPT, only the PDS Member Existence Exit supports purging members.

CA‑PanAPT provides several sample Member Existence Exits. You can use the executable forms of these exits, modify the source, and compile them to make new exits, or you can create your own exits. If you do modify the sample exits, select a new name for your new exit and leave the original for future comparisons. Users can then recognize immediately that the new exit is not identical to the sample described in CA‑PanAPT guides because it has a different name. The sample CA‑PanAPT member existence exits are in the following table.

Note: For CA‑Librarian, CA‑Panvalet, and CA‑Panexec member existence exits, their load libraries must be available both to CA‑PanAPT online and to job APJJ5310. When using the member existence exit for CA‑Panexec members, CA‑Panexec PTF 1005604 is required.