CA Service Desk Configuration › CAISDI/elmds Backout Procedure › How to Implement Standalone CAISDI/els › Run Standalone CAISDI/els › CAISDI/els Event Trigger Utility Commands

CAISDI/els Event Trigger Utility Commands

All CA Technologies products using CAISDI/els call it when a specific event occurs or when a condition arises. The call to CAISDI/els is referred to as “triggering the event”. The CAISDI/els Event Trigger Utility, CSDETRIG, can be used to trigger events manually. This utility is useful in verifying the network connections and ensuring that all components are connecting properly. You can also incorporate this utility into production job streams where conditional step execution would invoke this utility and open CA Service Desk tickets that are based on condition codes. In this case, you can create your own events to augment the ones that are supplied by the product. The Event Trigger Utility triggers any events that you create.

Consider this sample JCL:

//TRIG   JOB  (account)'Systems',CLASS=A
//*
//EVENT   EXEC PGM=CSDETRIG,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 only has two control parameters:

PRODUCT=

The product code of the product whose event you want to trigger.

EVENT=

The six character event code you want to trigger. 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” seen by the Event Trigger Utility are taken to be symbolic parameters to be used in providing detailed event data. In the previous example, the “parameters” JOB, DSN, and MSG are set up as symbolic parameters. If the event L0E231 contains &JOB, &DSN, and &MSG embedded in the summary or description texts, then the values you assigned them are substituted into the summary or description texts. Note the use of the PARM= on the JCL EXEC statement. Any value that you specify on the PARM= can be passed directly into the control statements or comments. The &PARM symbolic is replaced with the value you specified in the PARM= of the JCL EXEC statement before the control statement is parsed. In this example, the MSG symbolic parameter would be assigned the value “Test message text” and any place in the L0E231 event text where &MSG was found, this text string would then replace it. The length of the control statement, including the substitution of the &PARM value, must not exceed 200 characters.

Using the Event Trigger Utility, you can trigger events of your own making. You simply 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.