Scheduling IBM Connect:Direct Activity
IBM® Connect:Direct® places a Process in a queue based on the parameters that affect scheduling. You can specify scheduling parameters in the Process statement or the submit command.
Scheduling parameters are listed in the following section:
- retain=yes|no|initial
- hold=yes|no|call
- startt=[([date|day] [, hh:mm:ss | [am | pm]])
The following table shows how scheduling parameters affect the logical queues.
Scheduling Parameter | Queue | Comments |
---|---|---|
None of the scheduling parameters specified | Wait | The Process remains in the Wait queue until IBM Connect:Direct establishes a session with the remote node. After a session is established, the Process moves to the Execution queue. |
retain=yes | Hold | A copy of the Process executes once, unless you specify a startt parameter value. Specify a day or time or both for the Process to start. |
retain=no | Wait (if no other parameters are specified) | The Process remains in the Wait queue until IBM Connect:Direct establishes a session with the remote node. The default is no. |
retain=initial | Hold | A copy of the Process remains in the Hold queue and executes every time the Process Manager is initiated. |
retain=yes and hold=no or hold=call | Hold | A copy of the Process remains in the Hold queue to be executed when released. |
hold=yes | Hold | You can execute the Process by specifying the change process command with the release parameter. |
hold=no | Wait (if no other parameters are specified) | The default for hold is no. |
hold=call | Hold | The Process remains in the queue until the remote node starts a session with the local node or another Process starts a session with that remote node. |
startt | Timer | When the scheduled day or time occur, the Process is moved to the Wait queue. |
Each Process in the TCQ has an associated status value. Each status value has a unique meaning that is affected by the logical queue in which the Process is placed. Status values for each queue are shown in the tables in the following sections. You can use the select process command to examine that status of Processes in the TCQ. For example, the following command displays all Processes in the TCQ with execution status:
select process status=EX;