6100 BSC Programming Manual

6100 BSC Link and Station Management
REQUESTS AND FUNCTIONS APPLICABLE TO WRITE STATE. The following
requests are permitted in WRITE state. Some requests have
different functions when the line is in other states. For
complete descriptions of the requests, see Section 3.
-----------------------------------------------------------------
| |
| |
| FETCH CONFIGURATION, to retrieve line parameters. You can |
| find out the values of line parameters, but you can't |
| change them in this state. This request does not cause a |
| change of state. |
| |
| |
| FETCH STATISTICS, to retrieve line quality and usage data. |
| This request does not cause a change of state. |
| |
| |
| WRITE DATA, to send the next message and accept the |
| acknowledgement. The line state when this request completes |
| successfully is WRITE. |
| |
| |
| READ DATA, to send an EOT sequence and change the state to |
| CONTROL, then wait to accept a line bid and a message. |
| |
| |
| WRITEREAD DATA, to send the next message and accept a |
| conversational reply. The line state when this request |
| completes with text is READ; the line state when this |
| request completes with an acknowledgement is WRITE. |
| |
| |
| CONTROL, to disrupt the WRITE in progress and change the |
| state to DISCONNECTED, or to send a TTD sequence. If |
| you use this request to send a TTD sequence, the line |
| state upon completion is WRITE. |
| |
| |
| SETMODE, to change the retry count or the block length |
| for transparent text. This request does not cause a |
| change of state. |
| |
| |
| ABORT, to stop a request in progress, for example, a |
| WRITE request. The line remains in the state in which |
| the work was interrupted. |
| |
-----------------------------------------------------------------
2-21