Thanks for your reply. I thought about attaching a screen print but I tried so many variations of this, including the 2 you showed, I couldn't really include them all. I have had success with the examples you showed with non-cyclic jobs. The problem I'm having is they don't work with the cyclic jobs I've tried but thanks again for your reply.
1 of 1 people found this helpful
We do shout for jobs running long but have been having problems we're trying to diagnose & it seems that those set to run as time over avg run time don't work but when set to absolute time ie job has run greater than x time, they work. There's a cmd you have to run to compile the stats that allows the avg run time to work (ctmjsa "*") but it doesn't seem to work under our cmv9 windows but was under cmv7 solaris. We're still trying some variations as we have some shouts that work but others don't & they're set the same way so we're scratching our heads.
In the past, I did try to send shouts on long running jobs using the
average run time but they never seemed to work for me so I gave up on it
and just used absolute time. Sorry that I have no suggestions for you with
your problem but if I come up with something I'll be sure to let you know.
On Fri, Jun 8, 2018 at 5:00 PM, Jeffrey Jordan <firstname.lastname@example.org>
I tried the long running setup you mentioned and this time it worked! I have no idea why it wouldn't work for me before. I'm sure I tried that before but now that it works I'm really doubting my memory. haha
Thanks again for your reply.