Hold Queue
The following table shows the IBM® Connect:Direct® Status values for the Hold Queue:
| Status Value | Explanation |
|---|---|
| HC (Held for Call) | Process is submitted with HOLD=CALL specified. A session started from either node causes IBM Connect:Direct to place this Process on the wait queue in WC status, and eventually in the execution queue (EX) when the first Process finishes. Note: If the SNODE is defined with a null IP address, the Processes will
be released serially. Refer to the HOLD parameter in SUBMIT
Command for more information.
|
| HE (Held in Error) | The Process was submitted and received an error unrelated to allocation or session errors. The Process is being checkpointed and REQUEUE=YES is specified. A common error that causes IBM Connect:Direct to place the Process in HE status is an out of space condition (Sx37 ABEND). |
| HI (Held Initially) | Process is submitted with HOLD=YES specified. |
| HO (Held by Operator) | An exception response is sent from the other node during FMH exchanges at Process negotiation or step termination. It also occurs if an FMH is invalid or is sent out of sync, or if the remote node is not defined in the network map. |
| HP (Held due to Process Error) | An exception response is sent from the other node during EXIT exchanges at Process negotiation or step termination. HP also occurs if an EXIT is invalid, sent out of sync, or if the remote node is not defined in the Network map. |
| HR (Held Retain) | Process is submitted with RETAIN=YES specified or being held for Process retry (intelligent retry). |
| HS (Held for Suspension) | The operator issued a SUSPEND PROCess command. You can release the Process later. The Process will run (Held for Suspension) when IBM Connect:Direct is recycled. |
| RA (Held for Restart Due to Allocation Error) | During Process execution, an allocation error occurred that matched those specified in the initialization parameters. This status enables the Process to restart after the allocation problem is resolved. |
| RH (Restart Held) | Either the Process is being held awaiting a connection to an inactive node by the Intelligent Session Retry feature (see Intelligent Session Retry ) or a checkpointed Process is executing when an error such as a lost session or an I/O error occurred. This status enables the copy to restart when the session is reestablished. |
| WC (Wait For Connection) | Session establishment is attempted, including retries if specified, and failed. The current Process is put on the wait queue (and later EX Q) if a session with that node is established later. It also can be released. |
The following table shows the applicable commands for the Hold Queue:
| Applicable Command | Description |
|---|---|
| Change Process | Modifies Process attributes |
| Delete Process | Removes the Process from the queue |
| Select Process | Displays Process status and state |