CA Service Desk Configuration › Verify the File Server Installation › Configure CAISDI/elmds › Consider the CAISDI/els Event Trigger Utility

Consider the CAISDI/els Event Trigger Utility

Some CA products call CAISDI/els when a specific event occurs or condition arises. A call to CAISDI/els is referred to as triggering an event. The Event Trigger Utility can be used to trigger events manually.

For CAISDI/elmds, the Event Trigger Utility is CDYFELS1. For installations that use CASDIELS (standalone CAISDI/els), the utility is CSDETRIG. The same JCL used with CASDIELS can be used with CAISDI/elmds, substituting CDYFELS1 for CSDETRIG. For CAISDI/elmds, the JCL parsing rules for continuation are the same as for the ELSSTART configuration file.

The Event Trigger Utility is useful in verifying network connections and verifying that all components are connecting properly. You can invoke this utility from within production job streams to open CA Service Desk tickets that are based on condition codes. You can create your own events to augment the ones that are supplied by CA Technologies products. Use the Event Trigger Utility to trigger your own events.

Sample Event Trigger Utility JCL:

//TRIG   JOB  (account)'Systems',CLASS=A
//*
//EVENT   EXEC PGM=CDYFELS1,PARM='Test message text'
//STEPLIB  DD  DSN=CAI.CAW0LOAD,DISP=SHR    
//SYSIN    DD  *
TRIGGER PRODUCT=CA-1,EVENT=L0E231,JOB=MYJOB,DSN=TEST.DATA.SET.NAME,MSG=”&PARM”
//SYSPRINT DD  SYSOUT=A

The Event Trigger Utility has two control parameters:

PRODUCT=

The product code of the CA product whose event you are triggering.

EVENT=

The six character event code you are triggering. All event member names are eight characters. A six character code followed by a two character language code. This parameter identifies the code, not the member name.

Any other parameters that are seen by the Event Trigger Utility are considered to be symbolic parameters to provide detailed event data. In the sample JCL, the JOB, DSN, and MSG parameters are set up as symbolic parameters. The values that you assign &JOB, &DSN, and &MSG, replace them in the summary or description text of the L0E231 event.

Any value that you specify with PARM= in the EXEC statement can be passed directly into the control statements or comments. The &PARM symbolic is replaced before the control statement is parsed, with the value you specified in PARM= of the EXEC statement. In this example, the MSG symbolic parameter is assigned the value “Test message text”. This text replaces each occurrence of &MSG in the L0E231 event text. The parameter data that is passed through PARM= cannot exceed 120 characters.

Using the Event Trigger Utility, you can trigger events of your own making. Construct a product control member and a set of product event members for your own purposes. Execute the Event Trigger Utility as a job step whenever you want to open a CA Service Desk ticket.