Communications/Transactions Guide and Reference
In VisualAge Smalltalk Server, the implementation of CPI-C is the same
regardless of the target environment. You can use the following classes
for CPI-C communication:
- AbtCPICConnectionSpec
- AbtCPICConversation
- AbtCPICError
- AbtCPICErrorDataComplete
- AbtCPICReception
The process below assumes that you have setup the appropriate side
information on the client and have defined the transaction to the
server. The sample program shows a simple two-way conversation between
a front-end transaction running from CICS on the workstation and a back-end
transaction residing on CICS Transaction Server.
- Note:
- With normal CICS setup for workstations, the back-end transaction cannot use
CPI-C; that is, a back-end transaction residing on CICS cannot use
CPI-C. This is because an APPC RECEIVE_ALLOCATE command is issued
before control passes to the user transaction. A possible solution is
to specify a user-written program rather than faaclpin.exe
in the workstation's program path and filename field of the CPI-C program
definition of the back-end transaction. The user-written program can
use the external call interface (ECI) to invoke the back-end program, which
then runs as a standard CPI-C back-end.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]