06-19-2012 02:15 PM - edited 03-01-2019 08:54 AM
I am running 5.3.1.366 in several environments (Dev, Test, Prod) When I try to lower the system queue to 0 so that no new jobs launch, my entry is overwritten and goes back to the previous set number. Even if I set it to 1 it goes back to the previous number. This is happening on all 3 masters, so I don't think it is a quirk with my install. In earlier versions of 5.3.1 I was able to do this.
Has anyone else experienced this? In dev, I stopped Tidal and snuck into the database and edited the limit (definitely not supported by Tidal, but wanted to see what would happen.) My zero setting stayed 0.
I haven't called Tidal Support about this yet...wondering if it is just me.
Thanks!
Michelle
06-19-2012 05:23 PM
Did someone write a system event to trap the change, and then performed some action to reset?
Sent from Cisco Technical Support iPad App
06-21-2012 11:15 AM
Have found system events that send email or snmp traps when the limit is lowered, but no actions that reset the value.
Michelle
09-22-2016 04:36 AM
Bump. Is there a event to trigger the system queue to zero automatically in TES? this would be very helpful.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide