3270 transaction message structure for the CICS-WebSphere MQ bridge
The examples in this section show the structures of request and reply messages when a non-CICS application runs a CICS® 3270 transaction through the CICS-WebSphere MQ bridge. CICS-WebSphere MQ bridge vectors are used in the messages to represent the EXEC CICS commands in the transaction.
- A terminal user can enter the transaction name, followed (optionally) by data. The transaction can obtain any data that follows its identifier by issuing an EXEC CICS RECEIVE command when it starts.
- A preceding transaction at the terminal stops with EXEC CICS RETURN TRANSID( transid ); the terminal sends a 3270 data stream and starts a new transaction. A transaction that is started in this way obtains the data in the 3270 data stream by issuing an EXEC CICS RECEIVE MAP or EXEC CICS RECEIVE command, depending on whether it uses BMS (Basic Mapping Support) mapping or terminal control.
- An application issues an EXEC CICS START command. The started transaction issues an EXEC CICS RETRIEVE command to retrieve any data that has been specified on the START command.
The CICS-WebSphere MQ bridge can emulate any of these ways of starting CICS transactions. It can also emulate a terminal user sending and receiving screens of data from the transaction. These emulations are achieved by using CICS-WebSphere MQ bridge vectors, which represent the EXEC CICS command being emulated and provide any data that is needed. The data needed by a CICS transaction accompanies inbound messages, and the data needed by a CICS-WebSphere MQ bridge application accompanies outbound messages.