Application Integration Guide > CallAPI > Platforms for CallAPIs > CallAPI for z/OS

CallAPI for z/OS

The following document includes information and notes required for using the CallAPI for z/OS.

Define the CodeTable to be used in the INI file of the z/OS CallAPI. Enter the name of the CodeTable object in the parameter codetable= of the section [GLOBAL]. IBM's default code table is used if this parameter is empty.

	1.	CallAPI and individual program

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

CallAPI and individual program

	2.	CallAPI and utility

The delivery directory includes the utility UCXBM25C which is available in the load library. It can be used in z/OS jobs.

CallAPI and utility

The AE Script which is to be processed in the Automation Engine is read from SYSIN.

You can also use the data definition instead of the dataset names (see example).

If the utility should be used in a job, the user must be authorized to communicate via TCP/IP.

The parameter REGION= should be set at least to 65M, otherwise errors occur.

Example

Dataset names must be adjusted to your installationation and z/OS configurationA set of constituent components that make up a system. This includes information on how the components are connected including the settings applied..

//UC4JOB   JOB ......
//UCCALL   EXEC PGM=UCXBM25C,REGION=65M,
//    PARM='INI=UC4.UCXBM25C.INI LOGON=0004,SMITH,UC4'
//STEPLIB DD DSN=UC4.UCXJM25.LOAD,DISP=SHR
//*        You can use the following command
//*        instead of the PARM INI=AE-inifile
//*UCINI    DD DSN=AE-inifile,DISP=SHR
//SYSIN    DD *
:SET &RUNNR = ACTIVATE_UC_OBJECT(JOBS,ExampleL1)
:IF &RUNNR = '0000000'
:   SET &ERROR = SYS_LAST_ERR_NR
:   STOP MSG,51,'ACTIVATION ERROR: &ERROR'
:ELSE
:   STOP NOMSG,50,'JOB WAS STARTED WITH RunID &RUNNR'
:ENDIF
/*
//