Use CICS transactions with the bridge

 

Without using WebSphere MQ, a CICS transaction can be started in several ways, including:

• A terminal user can enter the transaction name, followed (optionally) by data. The transaction can obtain any data that follows its identifier by issuing EXEC CICS RECEIVE when it starts.

• A preceding transaction at the terminal terminates 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 EXEC CICS RECEIVE MAP or EXEC CICS RECEIVE, 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 EXEC CICS RETRIEVE to retrieve any data that has been specified on the START command.

A transaction that has been invoked at a terminal can subsequently issue commands such as EXEC CICS CONVERSE, EXEC CICS SEND MAP, and EXEC CICS RECEIVE MAP in a conversation or pseudoconversation with a terminal user.

The CICS 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 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 bridge application accompanies outbound messages.

• Using CICS bridge vectors
  

• CICS 3270 bridge message structure
  

• Application programming for the CICS 3270 bridge
  

• Writing applications using CICS Basic Mapping Support
  

• Transactions with start data
  

• Transactions with EXEC CICS syncpoint
  

 

Parent topic:

3270 applications

fg15520_