Embedding COBOL CALLs

AcuConnect in distributed processing 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 is prog2.acu, you embed the following statement into your client application:

CALL "prog2".

If you have not set the ACUCOBOL-GT configuration variable CODE_SUFFIX, the runtime system first attempts to locate an object file called prog2.acu and then an object file called prog2 with no suffix.

Or, if you have added "CODE_SUFFIX obj" to the client.cfg file, the runtime looks only for an object file called prog2.obj on the remote machine.

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.

Note: You can use all forms of CALL documented in the ACUCOBOL-GT Reference Manual with AcuConnect, with the following exception: AcuConnect does not support the use of CALL THREAD, CALL PROGRAM, or CALL RUN to a remote server.

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.