Whether you are working in Windows or UNIX, you can expect the same results from the sample programs.
Synchronous Sample
When "prog1" CALLs "prog2", AcuConnect automatically starts "prog2" on the server with the runtime flags and configuration file specified in the sample "client.cfg" file. This is equivalent to typing, "wrun32 -b -le prog2.err -c cblconfig prog2.acu" on an NT server or "runcbl -b -le prog2.err -c cblconfig prog2.acu" on a UNIX server.
If the connection is successful, the following displays on the client:
Number of customers between 35 and 39: 003
If the connection is unsuccessful, the following displays.
Call to server was unsuccessful!
Refer to "Connection Refused " for troubleshooting advice.
Asynchronous Sample
When "asynch.acu" CALLs "prog2", AcuConnect automatically starts prog2 on the server with the runtime flags and configuration file specified in the sample "client.cfg" file. Since C$ASYNCRUN was CALLed as well, however, AcuConnect allows the client program, "asynch.acu", to continue running this time.
If the connection is successful, the following displays on the client:
age-group-count immediately after async call:
Begin sleep for 5
End sleep, call asyncpoll
Number of customers between 35 and 39: 003
If the connection is unsuccessful, the following displays.
CALL ERROR#: nn
Refer to "Connection Refused" for troubleshooting advice.
NOTE: Click here to see the source code of "prog1", "asynch" and "prog2". To see the contents of "server.cfg" and "client.cfg", click here.