Previous Topic: Distributed Transaction ParticipantNext Topic: General Limitation on Data Passed Between DPC and DPS Applications


Data Representation

A cooperative flow provides the mechanism for a PStep (the DPC) to pass control and data to a remote PStep (the DPS). The data in the Export View of the Pstep is passed to the Remote PStep and received into the Import View of the Remote Pstep.

A DPC and DPS can execute in different environments and on different machine architectures, for example, where the DPC is an ASCII machine and the DPS is an EBCDIC machine. Numeric data would be represented differently in the environments that execute the DPC and DPS.

To accommodate the various environments that support cooperative flows, view data is transmitted in a platform-independent encoded buffer. This proprietary buffer format is known as a Common Format Buffer (CFB). The encoded CFB is used to exchange view data that is transmitted between a DPC and DPS. For more information, see Common Format Buffer.

CA Gen offers support for cooperative flows where the DPC and DPS operate in the same execution environment. These environments provide transport mechanisms that allow the data to be transmitted without using the CFB. These environments include Tuxedo clients flowing to Tuxedo servers, Java clients flowing to EJB servers, and .NET clients flowing to .NET servers. Each of these environments use a data format or transmission technique that is native to its respective environment.

CA Gen transmits view data in the format that best suits the execution environments of the DPC and DPS involved in the cooperative flow.