Embedding COBOL CALLs

AcuConnect achieves remote application access with standard COBOL CALLs. Just as you would CALL a local application component, you can CALL a remote application component using AcuConnect.

For example, if the name of the remote program that you want to invoke were "prog2.acu", you would embed the following statement into your client application:

CALL "prog2.acu".

Or, if you added "CODE-SUFFIX acu" to the "client.cfg" file, you could just embed:

CALL "prog2".

AcuConnect supports ACUCOBOL-GT's standard usage of the CALL verb, so you could embed:

CALL "prog2" USING {parameter} . . .

CALL "prog2" ON {EXCEPTION} statement-1.

or any other possibility documented in the ACUCOBOL-GT User's Guide. (Exception: AcuConnect Version 4.2 does not support the use of CALL THREAD, CALL PROGRAM, or CALL RUN).

The configuration file on the client, "client.cfg ", specifies the complete remote path of the CALLed program, so you don't have to specify the path in the application code. This way, you can redistribute the application in your network as often as necessary without changing a single line in your code.