Installing the CallAPI for z/OS

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

UCXBM25C is a CallAPI utility that can be called from the command line of the operating system, a script, or a job.

You can specify the CodeTable that should be used in the INI file of the z/OS CallAPI. Enter the name of the CodeTable object in the codetable= parameter in the [GLOBAL] section. The IBM standard code table is used if nothing is specified in this parameter, see Call API z/OSINI file.

Important! The communication between the Java Communication Process (JCP) and the Proxy uses TLS/SSL exclusively. Because the CallAPI does not natively support TLS/SSL and still connects to the Communication Process (CP), it cannot connect directly to the Proxy nor the JCP). However, you can route CallAPI connections through the TLS Gateway to secure them. For more information, see TLS Gateway. The exceptions are the Java and SAP CallAPIs which already use TLS/SSL to connect to the Automation Engine. They communicate directly with the JCP and use trusted certificates to authenticate their identity to other communication partners.

More information:

For additional information about the different certificate types and examples of how they could be created and used, see What Kind of Certificates Should I Use for Automic Automation v21.

Important! Please note that these are only examples, not a requirement for Automic Automation and they are not meant to replace the product documentation.

In Automic Automation Kubernetes Edition, CallAPIs establish a connection to a TCP load balancer. The address of this load balancer must be configured on both ends—the Automation Engine and the CallAPI. The only exceptions are the Java and SAP CallAPIs, which must be updated to use TLS/SSL when connecting to the Automation Engine. These two CallAPIs establish a direct connection to the Java Communication Process (JCP) through an HTTPS load balancer. In this setup, you can also route the connections of the other CallAPIs through the TLS Gateway to securely reach the HTTPS load balancer.

More information:

To Install the CallAPI for z/OS

To install the CallAPI for z/OS you must create the load library using the utility TSO RECEIVE. The delivery directory contains a samplec file (UCXBM25C.INI), which can be used for any text file transfer to z/OS. You can keep your existing INI file even if there is a new Automation Engine version and adjust it as required.

Note: If UCXBM25C is an ALIAS (link) that points to UCCALL3I, change it to point to UCCALL4.

Example

//UCCALL EXEC PGM=UCXBM25C,REGION=65M,

change to:

//UCCALL EXEC PGM=UCCALL4,

The load library can be transferred with any file transfer (such as IND$FILE without ASCII/EBCDIC conversion or CR/LF conversion).