State transitions in LUTYPE6.1 migration-mode conversations
In this section, the state table shows the state transitions that occur when transactions engage in LUTYPE6.1 conversations in migration mode. The state table includes the commands available and the states returned when starting a back-end transaction using the SEND [FMH|ATTACHID] command with the transaction identifier imbedded in first four bytes of user data.
For back-end transactions started by CONNECT PROCESS, use the tables in State transitions in APPC mapped conversations, but remember that the BUILD ATTACH, SEND ATTACHID, SEND FMH, and EXTRACT ATTACH commands are also available.
The commands you can issue, coupled with the EIB flags that can be set after execution, are shown on the first column of the table. The possible conversation states are shown across the top of the table. The states correspond to the columns of the table. The intersection of a row (command and EIB flag) and a column (state) represents the state transition, if any, that occurs when a particular command returning a particular EIB flag is issued in a particular state. A number at an intersection indicates the state number of the next state. Other symbols represent other conditions, as follows:
| Symbol | Meaning |
|---|---|
| N/A | Cannot occur. |
| × | The EIB flag is any one that has not been covered in earlier rows, or it is irrelevant (but see the note on EIBSIG if you want to use ISSUE SIGNAL). |
| Abend code | The command is not valid in this state. Issuing a command in a state in which it is not valid usually causes an ATCV abend. When a different abend code applies, this is shown in the tables. |
| = | Remains in current state. |
| End | End of conversation. |