Execution Queue
The following table shows the IBM® Connect:Direct® status values for the Execution Queue:
| Status Value | Explanation |
|---|---|
| EX | Node is in Process control and executing the displayed Process. |
| WC (Waiting for Connection) | Process control is in negotiation while the two nodes determine which Process executes next, based on priority. |
| PR.CNTL | This node is not in Process control. This status occurs: (1) during Process negotiation where highest priority on either node runs next, or (2) when the current node is the SNODE during Process execution. |
| SS | Session with other node is being started. |
The following table shows IBM Connect:Direct task state values for Processes in the Execution Queue:
| Task State | Explanation |
|---|---|
| DISPATCH | Task is waiting to dispatch |
| INACTIVE | Task can be dispatched but inactive |
| VTAM I/O | Task is waiting on VTAM request |
| P=SNODE | PNODE equals SNODE task |
| VSAM I/O | Waiting on VSAM I/O request |
| MISC | Miscellaneous I/O, such as a WTO |
| FILE I/O | Non-VSAM I/O |
| LOCK | Waiting for IBM Connect:Direct locked resource |
| SUBTASK | Waiting on a subtask, such as open or close, allocation, security, or RUN TASK |
| RUNNING | Executing instructions |
| TCA SCAN | TCA scan |
| TIMER | Waiting for timer event |
| ATTACH | Waiting for attached tape drive |
| ALLOCATE | Waiting for allocation to complete |
| MOUNT | Waiting for tape mount |
| OPEN | Waiting for OPEN to complete |
The following table shows the Subtask state values for the Execution Queue. The first characters of the subtask request state indicate the session protocol such as TCP or LU6.2.
| Subtask State | Explanation |
|---|---|
| ADOPT V2 | Performing Adopt |
| CALL V2 | Performing Call |
| INIT V2 | Performing Initialization |
| CLEANUP | Performing Cleanup |
| HANGUP | Performing Hangup |
| SEND V2 | Performing Send |
| SEND RSP | Performing Send Response |
| SEND SIG | Performing Send Signal |
| RECV V2 | Performing Receive |
| ANSWER V2 | Performing Answer |
| IOCTL V2 | Performing I/O Control |
| GET BUF | Performing I/O Control Get Buffer |
| RDY RCV | Performing I/O Control Ready Receive |
The following table shows the transport state values for the Execution Queue:
| Transport State | Explanation |
|---|---|
| NO SESSION | No VTAM session |
| SESSION EST | Session with another node being established |
| NO REQUEST | No VTAM request outstanding |
| RECEIVE | Waiting on VTAM RECEIVE request |
| OPEN | Waiting on VTAM OPEN request |
| CLOSE | Waiting on VTAM CLOSE request |
| SETLOGON | Waiting on VTAM SETLOGON request |
| REQSESS | Waiting on a request session request |
| OPNDST | Waiting on an open destination request |
| CLSDST | Waiting on a close destination request |
| GENCB EXTLST | Waiting on a GENCB EXLIST |
| GENCB ACB | Waiting on a GENCB ACB |
| GENCB NIB | Waiting on a GENCB NIB |
| GENCB RPL | Waiting on a GENCB RPL |
| REJSESS | Waiting on a reject session request |
| SESSIONC | Waiting on a session cancel request |
| INQUIRE | Waiting on an inquire request |
| OPNSEC | Waiting on an open secondary request |
| RSHUTD | Waiting on a request shutdown request |
| SIMLOGON | Waiting on a simulate logon request |
| SND RESPONSE | Waiting on a send response request |
| WAIT FOR +DR | Waiting on a definite response request |
| VTAM I/O | Waiting on VTAM request |
| SEND | Waiting on VTAM send request |
| DACTSESS | waiting on LU6.2 deactivate session request |
| RCVFMH5 | Waiting on LU6.2 receive FMH-5 request |
| REJECT | Waiting on LU6.2 reject conversation request |
| ACTSESS | Waiting on LU6.2 activate session request |
| ALLOC ALLOCD | Waiting on LU6.2 allocate conversation until available request |
| PRERECV | Waiting on LU6.2 prepare to receive request Note: In a IBM Connect:Direct/Plex environment, the LU6.2
connection protocol does not enable the IBM Connect:Direct Manager to redirect work to
one of its servers. The remote node must address the server on which you want to run an LU6.2
Process. To do this, specify the node name and VTAM address of the IBM Connect:Direct Server on which the Process
is to run in the remote server's network map. Use the same CDPLEX.SERVER.NODE and CDPLEX.VTAM
specified for the local initialization parameters for the IBM Connect:Direct Server you are trying to
address.
|
| CNOS | Waiting on LU6.2 change number of session request |
| DELLOC | Waiting on LU6.2 deallocate conversation request |
| SEND CONFRMD | Waiting on LU6.2 send confirmation request |
| 6.2 RECEIVE | Waiting on LU6.2 receive request |
| 6.2 SEND | Waiting on LU6.2 send request |
| SEND ERROR | Waiting on LU6.2 send error request |
| DISPLAY | Waiting on LU6.2 display session limit request |
| DEFINE | Waiting on LU6.2 define session limits request |
| ALLOC IMMED | Waiting on LU6.2 allocate conversation immediately request |
The following table shows the allocate state values for the Execution Queue:
| Allocate State Value | Explanation |
|---|---|
| SVC99 | Performing SVC99 |
| CAT SEARCH1 | CAMLST locate |
| READ VTOC | CAMLST search |
The following shows the applicable command descriptions for the Execution Queue:
| Applicable Command | Description |
|---|---|
| Flush Process | Terminates and deletes an executing Process |
| Select Process | Displays Process status and state |
| Suspend Process | Terminates and moves an executing Process on the hold queue |