Choose MODE=SYNCEXIT to specify that the request be processed synchronously, if possible. If the request cannot be completed synchronously, control returns to the caller with a return and reason code indicating that processing of the request is not complete. When processing of the request completes, the exit routine specified at connect time gets control. (The exit routine is specified on the COMPLETEEXIT parameter on the IXGCONN request.)
You can use the REQDATA parameter with MODE=SYNCEXIT to specify user-defined information relating to the request. For example, you can use REQDATA to specify information about control blocks needed by the complete exit. Your application must be in supervisor state, system key to use the MODE=SYNCEXIT and REQDATA parameters.
When a system logger request cannot be completed synchronously, system logger schedules an SRB to complete processing of the request before it returns control to the caller. While the SRB runs independent of the requesting task, the SRB might encounter an error from which it cannot recover. The SRB ensures that the error condition is percolated to the task that issued the system logger request.
Your complete exit provides a mechanism for system logger services to let you know when your asynchronously processed system logger IXGBRWSE, IXGDELET, or IXGWRITE request completes. You provide the address of your complete exit using the COMPLETEEXIT parameter when you issue the IXGCONN REQUEST=CONNECT macro to connect to the log stream. You will be informed of request completion through your complete exit if you specify MODE=SYNCEXIT and the system processes your request asynchronously.
You must be running in supervisor state and a system key to specify MODE=SYNCEXIT on a IXGBRWSE, IXGDELET, or IXGWRITE system logger service request.