CA Service Desk Configuration › CAISDI/elmds Backout Procedure › How to Implement Standalone CAISDI/els › Run Standalone CAISDI/els › Starting CAISDI/els

Starting CAISDI/els

The CAISDI/els component is started using the CASDIELS procedure:

//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 are designed to facilitate the starting and stopping of the CAISDI/els component. The ELSSTART member, which you previously configured, contains the control statements necessary to establish CAISDI/els. For example, 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.

The following operator command can be issued from the system console or can be included in your IPL procedures to ensure that the interface is always activated after an IPL:

S CASDIELS

The CAISDI/els Interface Controller, CSDECNTL, loads the event definitions from the various products into shared memory. For each product defined to this interface, CSDECNTL creates a Product Event Table. The collection of Product Event Tables and other memory-resident control blocks is referred to as the Event Control Structure. Once the Event Control Structure has been initialized, CAISDI/els is enabled. While the CAISDI/els Interface Controller is started with a console command, it is not a “started task” in the traditional sense. It establishes the interface and then terminates. If there were no problems, CSDECNTL completes with return code of zero. The interface is ready for use. If the return code is not zero, examine the processing log written to the SYSPRINT DD statement.