Administration Guide > Installation > New Installation > Installing the CallAPI for BS2000

Installing the CallAPI for BS2000

This document guides you through the new installation of a CallAPIA programming interface that processes a script in the Automation Engine system. It can be called directly from within the program itself or from a different program. for BS2000.

A CallAPI for BS2000 is supplied with AE. This interface enables calls in AE from your own programs, which can be written in programming languages such as C, COBOL, or Assembler. UCXBB2?C serves as a utility that can be called from a procedure or enter jobAn Automation Engine object type for a process that runs on a target system., for example.

A one-character code has been assigned for each supported BS2000 variant. This code is used in some CallAPI file names. Details are described in "terminology". In this document, the specific code is replaced by "?."

You can specify the CodeTable that should be used in the INI file of the BS2000 CallAPI. Enter the name of the CodeTable objectAutomation Engine controlled activities and processes are structured in the form of objects. See also: Task in the section [GLOBAL] of the parameter codetable=.

Supplied Files

The CallAPI files are packed as TAR files. The relevant TAR file is found in the sub-directory of the appropriate  BS2000 variant in IMAGE:AGENTS\BS2000:

Transfer the required TAR file to the BS2000 system using any text file transferTransfers files from one computer to another. A particular Automation Engine object type (FileTransfer object).. It can then be extracted using the utility BS2-TAR or the BS2-TOOLS version 2.00W or later (both are products of Automic software).

The TAR file contains the files listed below, which are supplied with the BS2000 packageA Package is an instance (a version, a revision, a tag, …) of your application and defines the content which you want to deploy. Here you decide, if you want to deploy the entire application or just a few specified components.. The characters "x.xxx" replace the part of the file name that shows the current Automation EngineThis component drives an Automation Engine system and consists of different types of server processes. version:

File name Description
x.xxx.UCXBB2?C.INI INI file for the utility
x.xxx.UCXBB2?C.LIB LMS Plamlibrary

The LMS Plamlibrary contains all elements that are required for programming.

Element name Description
UCXBB2?C Type L Utility for calling the CallAPI

UCCALL3 Type L

Large module that should be included or dynamically reloaded to the program used by the CallAPI
UCCALL3 Type M Assembler macro for the interface description
UCCALL3.H Type S C-header file for the interface description
UCCALL3.CPY Type S

COBOL copy for the interface description

SAMPLE.COBOL Type D Sample source for using the CallAPI from a COBOL program

 


Procedure

1.

Setting up the system environmentAn Environment consists of Deployment Targets which represent your endpoints. Different environments are used for different phases in the software delivery cycle, for example Development, QA, Staging, Production. An environment is typically set up once and used by several applications.

 

See also:

CallAPI for BS2000

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH