Vectors for 3270 transactions using the CICS-WebSphere MQ bridge
The CICS-WebSphere MQ bridge emulates all the functions of the CICS® terminal API, including minimum function BMS. When you use the CICS-WebSphere MQ bridge to run 3270 transactions, you use vectors to represent EXEC CICS commands in request and reply messages.
Vectors are identified in bridge messages by strings of numeric characters known as vector descriptors. Each vector descriptor is the CICS EIBFN value of the EXEC CICS command that it represents. For example, 0402 is the EIBFN value for EXEC CICS RECEIVE and also the vector descriptor of the RECEIVE vector. Vectors are further qualified by the letters I and O to show whether they are inbound (to the CICS-WebSphere MQ bridge) or outbound (from the CICS-WebSphere MQ bridge). Messages can contain several concatenated vectors.
An inbound message that is sent to the CICS-WebSphere MQ bridge to run a 3270 transaction must include a vector structure after the MQCIH, unless you start a transaction with no data. Inbound messages can contain multiple RECEIVE MAP vectors in anticipation of future RECEIVE MAP requests from the CICS transaction. The application needs to know the flow of control in the transaction so that it can construct the message.
An outbound message can contain request vectors or reply vectors. These descriptions do not mean that they go to the request queue or the reply queue; all outbound messages go to the reply queue. A CICS transaction uses a request vector to request data from the non-CICS application that is acting as the virtual terminal. A CICS transaction uses a reply vector when it does not expect any data back. No such distinction is made for inbound vectors.
Outbound messages can contain several vectors; for example, as a result of successive EXEC CICS SEND MAP commands being issued by a transaction. The CICS transaction does not control whether the outbound message contains a single vector or multiple vectors. If the transaction issues a command that generates a request vector, the request vector is always the last one in the message.
- Inbound vectors:
-
- RECEIVE
- RECEIVE MAP
- CONVERSE
- RETRIEVE
- Outbound reply vectors (no further data is required in the next inbound message):
-
- SEND
- SEND CONTROL
- SEND MAP
- SEND TEXT
- ISSUE ERASEAUP
- Outbound request vectors (further data is required in the next inbound message):
-
- RECEIVE
- RECEIVE MAP
- CONVERSE
Each of these vectors is an architected structure followed by variable-length data. All the vectors have a common header, but their structures differ. For information about the structures, see Link3270 message formats .
The vector structure definitions are available in C-language header file dfhbrmqh.h and COBOL copybook DFHBRMQO. Include them in any application that uses the bridge. These members are provided only with CICS Transaction Server on z/OS®. If you want to create your application on another platform, copy them to that environment.
RETRIEVE vector
If the CICS 3270 transaction issues an EXEC CICS RETRIEVE … QUEUE(data-area) command to retrieve its start data, the non-CICS application must send a message to the CICS-WebSphere MQ bridge with a RETRIEVE vector structure, which is defined in C as brmq_retrieve. The structure contains a character field of length 8 bytes in which the non-CICS application must specify the name of the temporary storage queue that contains the data to be retrieved. A message containing a RETRIEVE vector is always the first in an exchange representing a conversation or pseudoconversation.