Start CAISDI/els
Learn how to start the CAISDI/els component by using the CASDIELS procedure.
Required roles: systems programmer |
|---|
The CASDIELS procedure looks like this:
//CASDIELS PROC PRODUCT=, // CMD=ELSSTART, // SYSOUT='X' //*------------------------------------------------- //CASDIELS EXEC PGM=CSDECNTL,PARM='&PRODUCT' //STEPLIB DD DSN=CAI.CAW0LIB,DISP=SHR //SYSIN DD DSN=CAISDI.PARMLIB(&CMD),DISP=SHR //SYSPRINT DD SYSOUT=&SYSOUT //REPORT DD SYSOUT=&SYSOUT
The CAISDI parameter library contains several members that start and stop the CAISDI/els component. For example, the ELSSTART member contains the control statements to establish CAISDI/els. The ELSSTART member can look like this:
DEFAULTS SD_AUTODEF=yes Create contacts and assets DEFINE PRODUCT=CA-1,EVENTLIB=cai.caievent,PRODCNTL=al0cntl,MASK=l0* DEFINE PRODUCT=ALLOCATE,EVENTLIB=cai.caievent,PRODCNTL=xfgcntl,MASK=xf*
The CAISDI/soap address space, CASOAP, must be up and available for CAIDSDI/els to start up.
To ensure that the interface is always activated after an IPL, issue the following operator command from the system console or include it in your IPL procedures:
S CASDIELS
The CAISDI/els Interface Controller, CSDECNTL, loads the event definitions from the products into shared memory. CSDECNTL creates a Product Event Table for each product that is defined to this interface. The collection of Product Event Tables and other memory-resident control blocks are referred to as the Event Control Structure. Initializing the Event Control Structure enables CAISDI/els. Although you start the CAISDI/els Interface Controller with a console command, it is not a “started task” in the traditional sense. The Interface Controller establishes the interface and then terminates. If no problems occur, CSDECNTL completes with a return code of zero. The interface is ready for use. If the return code is not zero, examine the processing log that was written to the SYSPRINT DD statement.