Installing the CallAPI for VMS

The Automation Engine supplies a CallAPI for VMS. It enables calls in the Automation Engine from your own programs, which can be written in a particular programming languages such as C, C++, or COBOL.

UCXBV??C is a CallAPI utility that can be called from the command line.

A two-character code is assigned for each supported VMS variant and is used in some CallAPI file names.

Note: In this document, the specific code is replaced by ??.

In Automic Automation Kubernetes Edition, CallAPIs establish a connection to a TCP load balancer. The address of the load balancer must be defined on both sides: the Automation Engine and the CallAPI. The only exceptions are the CallAPIs for Java and SAP, which must be upgraded to use TLS/SSL to connect to the Automation Engine. These two CallAPIs establish a connection with the Java communication process (JCP) through an HTTPS load balancer.

More information:

To install the CallAPI for VMS

You must transfer the supplied files to the host using FTP:

openIP address
User name = UC4
Password = <as specified>
cd SRC
pwd(check directory)
put MAKEXAMP.COM
put UCXBVXXC.C
put UCCALL3.H
bin
put UCXBV??C.OLB
cd ../BIN
pwd(check directory)
putUCXBV??C.EXE
ascii
put API_START.COM
put UCXBVXXC.INI
put UCX.MSL
bye

Adjust the INI file (UCXBVXXC.ORI.INI) of the VMS CallAPI to your system environment, see Call API VMS INI file.

Note: You can keep your existing INI file even if there is a new Automation Engine version and adjust it as required.