The IXLYCMPL macro provides the format of the complete exit parameter list. Include that macro as well as IXLYCON in your program.

When the complete exit returns to XES, you can no longer access the data in the CMPL.

You should be aware that in order to preserve the logical ordering of events, XES will not inform the user of other events related to this resource until it has received control back from the complete exit. Any processing that is to be performed by XES to inform the user of additional status of the subject resource (such as executing the notify exit, informing the user of asynchronous request completion through a subsequent invocation of the complete exit, or resuming a suspended work unit representing a synchronous request) will not be attempted until the complete exit returns control to XES. These interdependences with regard to the presentation of resource information to the user introduce the possibility of a user's protocol creating a deadlock scenario. For example, issuing a synchronous IXLLOCK request to alter a resource from within a complete exit that is executing on behalf of the same resource is one such case in which a deadlock could occur. (The complete exit will be suspended awaiting completion of the alter request, but XES will not be able to perform this processing until the exit returns control from the current invocation.

XES does not support the detection or resolution of deadlock scenarios. The prevention of such occurrences is the responsibility of the connected users of XES services.