CAISDI/els Event Trigger Utility Commands

Learn how to use the Event Trigger Utility to manually trigger events to call CAISDI/els.
Required roles: systems programmer
All
Broadcom
mainframe products that use CAISDI/els call it when a specific event or condition occurs. The call to CAISDI/els is referred to as “triggering the event.” You can use the CAISDI/els Event Trigger Utility, CSDETRIG, 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
Service Desk Manager
tickets that are based on condition codes. In this case, create your own events to augment the ones that are supplied by the product. The Event Trigger Utility triggers any events that you create.
See the following example:
//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 has the following control parameters:
PRODUCT=
Specifies the product code for the product whose event you want to trigger.
EVENT=
Specifies the six-character event code 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.
The Event Trigger Utility assumes that any other parameters are symbolic parameters that provide detailed event data. In the previous example, 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 your assigned values are substituted into the summary or description texts. Any value that you specify in the PARM= of the JCL EXEC statement can be passed directly into the control statements or comments. The &PARM symbolic is replaced with the value that you specified in the PARM= of the JCL EXEC statement before the control statement is parsed. In this example, the MSG symbolic parameter is assigned the value “Test message text.” This text string replaces all occurrences of &MSG in the L0E231 event text. The length of the control statement, including the substitution of the &PARM value, cannot exceed 200 characters.