I would suggest that you figure out how much CPU your STC typically takes and specify a TIME= at about that level. Then you can SLIP on 322 to take an abend.
Of course, depending on the criticality of the STC, you should consider making it automatically restart. On Wed, 30 May 2018 22:00:01 -0500 Munif Sadek <[email protected]> wrote: :>Is there a way to slip trap on a module/STC if it starts consuming higher MSU in zOS 2.3. :>My problem is a vendor product where a user exit is being repetitively called, issuing unnecessary GETMAIN/FREEMAIN. Vendor has asked us to dummy out user exit and fix will come in the next release. This problem is intermittent, generally happens once every couple of hours during online window. :>Dummied out User exit has provided relief, still management perceived notion that Mainframe is expansive and Vendor reluctance to disclose what process is initiating call to this exit, is there a way I can set a slip trap whenever CPU usage is spiked so that I can go back to vendor with SVC DUMP/ Systrace (Mod names) of the exact problem. :>We do have Strobe but strobe can not automate this request without integration with iStrobe and BMC Caze. :>Did look at SLIP documentation but can not find relevant information. -- Binyamin Dissen <[email protected]> http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
