How to code a Dataset Trigger where the dataset is updated numerous times before it should be Primed.

Document ID : KB000055478
Last Modified Date : 14/02/2018
Show Technical Document Details

COUNT indicates the event is to be scheduled for every n triggers, where n is a number from 0 to 255. A value of 0 results in a schedule for each trigger, as does a value of one. It defaults to one.

If you know that dataset 'CYBER.TEST1.DATASET' is going to be triggered twice to 'CYBER.TEST2.DATASET' being triggered once then code it like 'CYBER.TEST1.DATASET' COUNT(2)

A DSTRIG is either primed or not primed. ESP Workload Manager does not stack the number of times a dataset is updated. Lets take the following example...

If CYBER.TEST1.DATASET is updated 5 times before CYBER.TEST2.DATASET is even updated once, ESP does not keep track of the 5 occurrences. It only knows that the DSTRIG has been primed.

So for example, the event will look like this after updating CYBER.TEST1.DATASET 5 times:

EVENT ID(CYBER.DSTRIG)  SYSTEM(ESP)  REPLACE
SEND 'EVENT DSTRIG HAS BEEN TRIGGERED' USER(CYBER)
DSTRIG CYBER.TEST1.DATASET ANYCLOSE MULTIPLE PRIMED
DSTRIG CYBER.TEST2.DATASET ANYCLOSE MULTIPLE 
ENDDEF

As soon as CYBER.TEST2.DATASET gets updated once, the event looks like this and will send the message...

EVENT ID(CYBER.DSTRIG)  SYSTEM(ESP)  REPLACE
SEND 'EVENT DSTRIG HAS BEEN TRIGGERED' USER(CYBER)
DSTRIG CYBER.TEST1.DATASET ANYCLOSE MULTIPLE
DSTRIG CYBER.TEST2.DATASET ANYCLOSE MULTIPLE
ENDDEF

Note that CYBER.TEST1.DATASET is not primed even though it was updated five times before CYBER.TEST2.DATASET was primed once.

This Frequently Asked Question applies to all supported releases of ESP Workload Manager beginning with 5.x.