Submit Exit Processing Flow

The following figure illustrates the execution order of the SUBMIT command:

The Submit exit processing flow is:

1. 1. After you issue an IBM Connect:Direct SUBMIT command or SUBMIT statement, the API SUBMIT command processor calls the Unauthorized Stage 1 Submit exit, if it exists. If it doesn’t exist or returns RC=0, the API SUBMIT command processor calls the Authorized Stage 1 Submit exit, if it exists. If it returns RC<8 or doesn’t exist, the submit is successful and the process is put on the TCQ.
2. If the API submit is successful, the DTF SUBMIT command processor calls the Stage 2 Submit exit, if it exists. If it returns RC=0, the Submit has completed successfully.

IBM Connect:Direct provides a sample Submit exit in $CD.SDGASAMP library, called DGAXSUBX, which you can use as a model for either the Unauthorized Stage 1 (DMCXSUBM) exit, or the Stage 2 (SUBMIT.EXIT = modname) exit.

IBM Connect:Direct also provides a sample Submit exit in $CD.SDGASAMP library, called DGAXSUBA, which you can use as a model for the Authorized Stage 1 Submit Exit (DMCXSUBA).