ESP Workload Automation

Hello, having concerns about a Data set trigger. I set-up this data set trigger and it's not pulling the second data set:. Here is my event:

/*************************************************/
/* DEFINED BY T370480 AT 08.35 ON WED 9OCT2013 */
/* LAST RUN AT UNKNOWN */
/*************************************************/
EVENT ID(PROD.PAS961M) SYSTEM(ESPM) REPLACE
INVOKE 'SUOGP.ESP.PROC(PAS961M)'
DSTRIG 'PRAAS.AS002M.DELCNTL.PIAP.G-' MULTIPLE
DSTRIG 'PRAAS.AS946M.DELCNTL.PIAP.G-' MULTIPLE
ENDDEF

When both file arrives it should have "PRIMED" on the event and it does not. Here's is the output from SARVS on job PAS961M:
//* SUBMITTED BY ESP AT 04.13.33 ON WEDNESDAY OCTOBER 9TH, 2013
//* SYSTEM ESPM, SUBSYSTEM ESPM
//* REQUESTED BY EVENT PROD.PAS961M
//* EVENT TRIGGERED BY USER PROD
//* JCL COPIED TO SUOGP.ESP.COPYJCL
//* TRIGGERED ON CREATION BY JOB PAS002M
//* OF DATA SET PRAAS.AS002M.DELCNTL.PIAP.G0005V00
//* JCL FROM SUOPP.PROD.JCL(PAS961M)

As you can see it only picked up the first dataset name.

Not sure where to go from here or how to correct it.

Any help or sugesstion would be greatly appreciated.

Thank you
Jerri Henley
ESP scheduler

I'm not sure what you mean by 'Should have "PRIMED" in the event' but are you sure both datasets aren't arriving causing the triggering of the event? This sounds very much like the scenario covered in the Examples Cookbook for 'Providing a variable for all data sets in a DSTRIG Event' (search for global variables, it's on page 98 of my book). The book will do a far better job of explaining it all to you than I ever could so you should give it a look and see if this might be the issue.

HTH

Cheers,
Greg

jerri.henley wrote:

Hello, having concerns about a Data set trigger. I set-up this data set trigger and it's not pulling the second data set:. Here is my event:

/*************************************************/
/* DEFINED BY T370480 AT 08.35 ON WED 9OCT2013 */
/* LAST RUN AT UNKNOWN */
/*************************************************/
EVENT ID(PROD.PAS961M) SYSTEM(ESPM) REPLACE
INVOKE 'SUOGP.ESP.PROC(PAS961M)'
DSTRIG 'PRAAS.AS002M.DELCNTL.PIAP.G-' MULTIPLE
DSTRIG 'PRAAS.AS946M.DELCNTL.PIAP.G-' MULTIPLE
ENDDEF

When both file arrives it should have "PRIMED" on the event and it does not. Here's is the output from SARVS on job PAS961M:
//* SUBMITTED BY ESP AT 04.13.33 ON WEDNESDAY OCTOBER 9TH, 2013
//* SYSTEM ESPM, SUBSYSTEM ESPM
//* REQUESTED BY EVENT PROD.PAS961M
//* EVENT TRIGGERED BY USER PROD
//* JCL COPIED TO SUOGP.ESP.COPYJCL
//* TRIGGERED ON CREATION BY JOB PAS002M
//* OF DATA SET PRAAS.AS002M.DELCNTL.PIAP.G0005V00
//* JCL FROM SUOPP.PROD.JCL(PAS961M)

As you can see it only picked up the first dataset name.

Not sure where to go from here or how to correct it.

Any help or sugesstion would be greatly appreciated.

Thank you
Jerri Henley
ESP scheduler

Look in the ESP Log
You should see something like this.

xxxxxxx.PGT4R17 scheduled, DSTRIG, Unconditional
Event bypassed, waiting for multiple trigger to complete

In the event you would only see 1 primed DSN at this point.
When next file is created, should see in the log..

xxxxxxx.PGT4R17 scheduled, DSTRIG, Unconditional
Multiple trigger completed for above Event
Appl PGT4R17.750 created, slot 00001D22
Appl PGT4R17.750, Slot 00001D22, now under Appl Manager control
Job PGT4R17 in Appl PGT4R17.750 Resources Satisfied
APPL PGT4R17.750 JOB PGT4R17 READIED
xxxxxxx.PGT4R17 scheduled, for Job PGT4R17 in Appl PGT4R17.750, Unconditional
PARMS: ESPTRDSN(XXXXXXX.X.NDM.ENS.RESELL.DP17.TRNM.G0001V00)

The DSN in the ESP log is the one that will show up in the jobs output LOG.
It will only show 1 of them in the jobs log.

//* TRIGGERED ON CREATION BY JOB PAS002M
//* OF DATA SET PRAAS.AS002M.DELCNTL.PIAP.G0005V00

Hello RBennett, thanks for the iinformatiom. I was asumming that I should have seen both of the DNS in the log. In viewing the logs, at first I did not see "Multiple trigger complete for the above Event.'
What I undersrand about the "PRIMED". If the event was triggered, it would show "PRIMED" next to each DNS. Is that correct?

Thanks Jerri
ESP Scheduler

So when a DSN is created, then the event shows PRIMED.

As soon as both are created the event is fired and the primed is removed and event reset.

So to catch the event with both DSN PRIMED, would be rare, you would need to be really QUICK...

Ok RBennett, understand now.

Once again, thanks for the informatiom.

Jerri Henley
ESP scheduler