Programming hints with respect to CICS applications

CICS transactions have to be designed and coded to comply with the Distributed Transaction Programming (DTP) paradigm. For a description of this programming paradigm, see the IBM CICS documentation, for example the "CICS Distributed Transaction Programming Guide".

The following restrictions and rules have to be considered to allow outbound communication by means of BeanConnect:

• A CICS partner application may never use SYNCPOINT or ISSUE PREPARE itself. Instead, it may only do so when requested to by the EJB in the Java EE application server.

• Basic conversation is not possible. Basic conversation is programmed for CICS by using commands that begin with GDS, such as EXEC CICS GDS ALLOCATE, for example.

• BeanConnect always establishes LU6.2 conversations with SYNCLEVEL 0 or 2 and never with SYNCLEVEL 1. The SYNCLEVEL of an incoming conversation can be queried in CICS-API using EXTRACT PROCESS.

• The default value of the communication property endConversation is false for CICS partners and true for UTM partners.