B3270 protocol

The b3270 process accepts operation requests from the user interface and sends back indications. These messages are sent on b3270's standard input and output, or (via the callback resource) over a socket. Unlike the s3270 protocol, all b3270 operations are asynchronous; the next command is accepted immediately. The results of each operation are reported asynchronously. Emulator state changes are reported also asynchronously.

When b3270 receives input end-of-file, it exits.

Protocol Description
b3270 runs in one of two modes: XML and JSON. The mode is controlled by the json resource, and defaults to XML

XML Mode
b3270 operations and indications are formatted as UTF-8 -encoded XML. b3270 input is a document called b3270-in. b3270 output is a document called b3270-out. So the input stream to b3270 must begin with the following: &lt;xml version="1.0" encoding="UTF-8"?&gt; &lt;b3270-in&gt;

The input stream should end with: &lt;/b3270-in&gt;

This will cause b3270 to exit.

Similarly, the entire b3270 output stream is bracketed by: &lt;xml version="1.0" encoding="UTF-8"?&gt; &lt;b3270-out&gt; and: &lt;/b3270-out&gt;





White space is allowed around XML elements, but plain text is never used in the protocol. All information is conveyed by elements and their attributes.

XML elements sent from the UI to the emulator are referred to as operations. XML elements sent from the emulator to the user interface are referred to as indications.

Operations and indications are transmitted as complete XML elements. For example, the connection indication tells the user interface about changes to the state of the host session.



Similarly, a run operation sent to the emulator tells it to run an action and the run-result indication tells the user interface that an action is complete.



b3270 actions run asynchronously, and may complete in a different order than they were sent.



JSON Mode
Under construction.

Pass-Through Actions
b3270 supports pass-through actions, which are emulator actions implemented by the user interface. An example of a pass-through action would be wx3270's UCopy action, used to copy selected text to the clipboard. b3270 has no knowledge of the clipboard, but it would be useful to allow this action to appear in keymaps, scripts, macros and sourced files processed by the the emulator. Yet b3270 cannot anticipate this and every other possible UI operation.

To support such an action, the UI can use the register operation at initialization time to inform b3270 of actions it would like to have passed through to it. When b3270 encounters one of these actions, it generates a passthru indication to the UI, giving the action name, parameters and a unique tag. When the UI has processed the action, it uses the succeed or fail operation operation to complete the action, giving back the unique tag and optional result text.



The pass-through mechanism is also used to implement password prompting for TLS certificates. The action name TlsKeyPassword is reserved for this purpose. If a password is needed to use an TLS client certificate, b3270 will invoke the TlsKeyPassword action. If the user interface has not registered a pass-through for TlsKeyPassword, then the TLS password operation will fail, and the host session will not be established. If a pass-through has been registered, a passthru indication will be generated for it. If the action succeeds, the TLS password will come from the result text. If the action fails, the TLS password operation and host session will fail.

Initialization
When b3270 starts up, it sends an initialize indication. Within that element are a series of initialization indications to the user interface. The first is a hello. These indications give the initial state of the emulator, with useful information like the code page, model number, and TLS options supported.