Application Integration Guide > CallAPI > Platforms for CallAPIs > CallAPI for GCOS8

CallAPI for GCOS8

The following document includes information and notes required for using the CallAPI for GCOS8.

	1.	CallAPI and own Program

The AE CallAPI may be called from your own programs. This requires sound knowledge of the programming language in which this program was written.

CallAPI and own program

The program ucxbxxxc.c is available as C source code. The corresponding structure definition is stored in the file uccall3.h. Update the example with your data and adjust the JCL files to your environment. In doing so, you create an RU and test the CallAPI.

	1.	CallAPI and Utility

The CD we supply includes the utility ucxbgc8c which may be called from a job.

CallAPI and utility

The processing steps defined with AE Script are read from the standard input. The INI and script files may also be defined using file code.

Example

In the first example, the CallAPI for GCOS8 is called.

$$dismiss
$      ident   uc4
$      run     rufile=uc4/callapi/exec/ucxbgc8c,
$      etc     runame=ucxbgc8c
$      privity
$      limits 9999,,,50k
$      dmpopt savdmp=(mini)
$      data    cz
$      ascii
ucxbgc8c ini=uc4/callapi/data/ucxbgc8ci \
script=uc4/callapi/data/script
$      endjob

In the second example, the CallAPI is called with the INI and script files being defined with file code.

$$dismiss
$      ident   uc4
$      run     rufile=uc4/callapi/exec/ucxbgc8c,
$      etc     runame=ucxbgc8c
$      privity
$      limits 9999,,,50k
$      dmpopt savdmp=(mini)
$      data    cz
$      ascii
$      prmfl   SC,r,s,uc4/callapi/data/script
$      prmfl   IN,r,s,uc4/callapi/data/ucxbgc8ci
ucxbgc8c ini=fc*IN script=fc*SC
$      endjob