Calling the ECI
Calls to ISPW functions are provided though the WZZECI interface module.
This is an LE-compliant routine that can be called (either statically or dynamically) from any other LE program.
All calls to WZZECI must include a common data structure in which an OBJECT and METHOD identify the type of call. Other parameters may be required, depending upon the type of call.
All ECI sessions must begin with a call to initialize the ISPW environment and end with a call to clean up the session. Between these two calls, any number of other calls may be made.
Syntax and examples for calling ECI using API
The ISPW product includes a COBOL driver program named ECICOBDR, found in the SAMP library, which serves as an example of invoking ECI through the API. This program demonstrates how to call ECI using a host language, specifically COBOL.
To illustrate a sample ECI invocation for adding a container, use the following example:
where:
- WZZECI is the program to be called for ECI invocation.
- WZZECI-PARM should contain the necessary ECI parameters to carry out the action.
The parameters are provided through the SYSIN DD input. Ensure that the dataset supplied for the parameters contains the input properly displaced. The length of each field is specified under the action head in the ECI Functions and Calls documentation. Refer to ECI-Functions-and-Calls for details on the fields and their respective lengths, and make sure to adhere to these lengths.
Example:
The following JCL example demonstrates the execution of the ECICOBDR program for task load.
//STEP01 EXEC PGM=WZZRCJOB,REGION=0M,TIME=1440,
// PARM='Default/ECICOBDR SERVERDD'
//ISPLOG DD SYSOUT=*,DCB=(RECFM=FBA,LRECL=121,BLKSIZE=1210)
//STEPLIB DD DISP=SHR,DSN=ISPW.CONFIG.AUTHLOAD
//SYSIN DD DISP=SHR,DSN=PINKRA0.ECI.INPUT(TASKLOAD)
//SERVERDD DD *
SERVERID=XXXX
XMEMID=XXXX
/*
//FILEOUT DD SYSOUT=*
//SYSOUT DD SYSOUT=*
The following is an example for input parameters: