Validity of Link3270 requests
At any time, the bridge facility is considered to be in a specific state .
Some requests are only valid is the facility is in an appropriate state. If the request is not valid, BRIH-RETURNCODE is set to the value indicated in Table 1.
Possible states are:
- Not Allocated
- Allocated
- Conversational
- Transaction Ended
The following table will help you to decide when a request
is valid, and what the resulting state will be. If a request is
invalid,
the state does not change:
| Request | Not Allocated | Allocated | Conversational | Transaction ended |
|---|---|---|---|---|
| Allocate Facility | valid ->Allocated | note⁸ | note⁸ | note⁸ |
| Run Transaction | valid² | valid⁴ | invalid³ | valid⁴ |
| Continue Conversation | invalid¹ | invalid⁵ | valid⁴ | invalid⁵ |
| Get More Message | invalid¹ | invalid⁶ | valid/invalid⁷ | valid/invalid⁷ |
| Resend Message | invalid¹ | invalid⁶ | valid ->Conversational | valid ->Transaction ended |
| Delete Facility | invalid¹ | valid ->Not Allocated | invalid³ | valid ->Not Allocated |
Note:
- BRIH-RETURNCODE set to BRIHRC-INVALID-FACILITYTOKEN.
- This is defined as single transaction mode.
- BRIH-RETURNCODE set to BRIHRC-FACILITYTOKEN-IN-USE.
- The resulting stated depends on whether the transaction issues further requests for which there is no BRIV. Possible new states are Conversational or Transaction-ended
- BRIH-RETURNCODE set to BRIHRC-TRANSACTION-NOT-RUNNING.
- BRIH-RETURNCODE set to BRIHRC_NO-DATA.
- The resulting state depends on whether there is more data to send ( indicated by BRIH-REMAININGDATALENGTH).
- This state is not relevant, as Allocate always creates a new facility.