Queuing Parameters
The RETAIN, HOLD, and STARTT parameters queue Processes as described in following table.
| Parameters | Queue | Comments |
|---|---|---|
| None | Wait | Process remains on the Wait queue until IBM® Connect:Direct® can start a session with the SNODE. The Process then moves to the Execution queue. |
| RETAIN=INITIAL | Hold | Process automatically executes each time IBM Connect:Direct is initialized with TCQ=WARM. This setting is useful for Processes that contact other IBM Connect:Direct nodes each time IBM Connect:Direct completes initialization. This action causes any work queued on the remote node for the local node to begin. |
| RETAIN=YES | Hold | A copy of the Process is kept in the Hold queue after it has executed. The
Process does not execute again until it is released by a CHANGE PROCESS command. You can use RETAIN=YES, combined with STARTT, to run a Process at a periodic interval. For example, RETAIN=YES and STARTT=(Tuesday, 3pm) starts the Process every Tuesday at 3 pm; RETAIN=YES and STARTT=(,12:00) starts the Process each day at noon. |
| HOLD=YES | Hold | Process remains in the Hold queue until someone releases the Process. |
| HOLD=CALL | Hold | Process is automatically moved from the Hold queue to the Wait queue when the SNODE contacts the node on which the Process resides. |
| STARTT | Timer | When the scheduled time and date arrive, the Process is put on the wait queue
and is available for execution. You can use RETAIN=YES, combined with STARTT, to run a Process at a periodic interval. For example, RETAIN=YES and STARTT=(Tuesday, 3pm) starts the Process every Tuesday at 3 pm; RETAIN=YES and STARTT=(,12:00) starts the Process each day at noon. You can also use the Timer queue for session retry and file allocation retry based on IBM Connect:Direct initialization parameters specified by a particular installation. When you exhaust retry limits, the Process is moved to the Hold queue with an HE status. |
When you submit a Process, IBM Connect:Direct puts it in the appropriate logical queue based on Process statement routing parameters listed in the preceding table. See Process Execution Example for an illustration of how IBM Connect:Direct executes a Process.