CALLing Multiple Programs

With AcuConnect in distributed processing, you can start multiple applications on the server at the same time by invoking multiple instances of the runtime.

In addition, programs that have been CALLed using AcuConnect can CALL other programs on the same server as normal, or on a different server using AcuConnect. For example, program 1 on a client machine can CALL program 2 on Server A. In turn, program 2 can CALL program 3 on Server B, and program 3 could even CALL program 4 on Server C, and so on.

To start multiple programs in this fashion, you must design your application components to perform remote CALLs, then provide the necessary configuration files.

When CALLing multiple programs, be aware of the following:

• If a "second generation" AcuConnect program (such as program 3 on Server B in the example above) requires a password from the first generation program, the password must be supplied using the acu_client_password variable coded into the CALLing program. Otherwise, the authentication will fail, because the first generation AcuConnect program has no way to handle an interactive password screen. See Passwords for more information on using passwords with AcuConnect.
• Each successive generation of AcuConnect programs can have its configuration file and runtime flags specified by its CALLing program using the ACUCONNECT_RUNTIME_FLAGS variable. See ACUCONNECT_RUNTIME_FLAGS for more information on the ACUCONNECT_RUNTIME_FLAGS variable.
• Runtime configuration variables are not passed from one program to the next when you use AcuConnect. So, instead of creating code name aliases for all the programs in the client configuration file, you should provide only the variables relevant to the first generation programs you are CALLing. The first generation programs need their own configuration variables to be used in CALLing second generation programs, and so forth.