Using Link3270 single transaction mode

Single transaction mode allows a client to run a single transaction. The bridge facility is automatically created, then deleted at the end of the transaction. This mechanism is more efficient and easier to program than session mode, if only one transaction is being run. It is particularly suited to inquiry transactions.

To run in single transaction mode, your client program must supply the name of the user transaction in the BRIH_TRANSACTIONID field of the bridge message header (BRIH). See Link3270 message header (BRIH) for a description of the BRIH. The following parameters may also be optionally defined:

Your client program must also create BRIV vectors for any input commands. If you add data to a BRIV, you must also update the BRIH-DATALENGTH field. See Updating data length fields .

To use single transaction mode your application must satisfy the following restrictions, otherwise session mode should be used:

Updating data length fields

If you add data to a BRIV you must update the following fields to include the length of the data:

If you add a BRIV to a message, you must add the value in the BRIV header vector length field to BRIH-DATALENGTH.

Related concepts
The Link3270 bridge mechanism
Link3270 programming considerations
Related tasks
Establish Link3270 suitability
Using the Link3270 bridge
Writing the Link3270 client
Using Link3270 messages
Using Link3270 session mode
Calling the Link3270 bridge
Using data conversion with Link3270
Related reference
Link3270 message formats
Link3270 diagnostics
[[ Contents Previous Page | Next Page Index ]]