JES2 and JES3 detach processing are quite different as shown in section B of Figure 1. During JES termination processing, only JES2 provides clean up when terminating normally. Neither JES2 abnormal termination nor JES3 termination (except JES3 FSS, as stated in Figure 1) frees either an installation-defined XCF group member or any members that were previously attached.

Therefore, for JES2 normal termination only, JES2 calls exit IXZXIT03 to issue the detach macro IXZXIXDT. IXZXIT03 first frees the storage that was obtained for exits IXZXIT01 and IXZXIT02. IXZXIT03 then detaches any installation-defined members. That is, if you use exit IXZXIT03 to call the IXZXIXAT macro during JES initialization, you must invoke IXZXIXDT to detach that member in IXZXIT03. JES2 then continues termination and clean-up processing. As discussed, the same requirement is not relevant to JES3.

Attention:

Whenever you issue the IXZXIXDT macro, each invocation causes exit IXZXIT03 to get control. If you do not code IXZXIT03 to prevent subsequent recursive calls, JES XCF attempts to again detach the installation-defined member, and JES XCF produces a dump. Be certain to add similar code to that shown in Figure 1 if you detach an installation-defined group.

Figure 1. Exit IXZXIT03 attach/detach processing