Inbound BRIV vectors

One BRIV vector is required containing the data requested by every EXEC CICS® command for 3270 terminal input issued by the user transaction.

The following commands are supported:
  • CONVERSE
  • RECEIVE
  • RECEIVE MAP
Note: If the application issues CONVERSE, and there is an inbound converse vector to satisfy this request, then the output from the converse is used to build an output SEND vector.
When the user transaction issues the command, the bridge mechanism searches the inbound message for the first BRIV that matches the command type. For RECEIVE MAP commands it attempts to match the MAPSET and MAP if these have been supplied by the client. RECEIVE MAP vectors are processed in order, and those that do not match the current command are discarded until a match is found. Blank names in the vector match any command.

Where there are several input vectors of different types, the order is not important.

For 'conversational' transactions (see Conversational transactions ) when the client is asked for further input, the previous inbound message vectors (except RETRIEVE vectors) are discarded when a new inbound message is received. Note that RETRIEVE vectors can only flow in the first message of the first transaction in a session. See Using Link3270 session mode for an explanation of the session programming mode.