What do consider or perceive makes it Looping? Is it high CPU Utilization, is it something else?
Any messages in SYSLOG at the time of the even that might provide some insight? Any dumps or abends that occurred during this time? Did you contact the owner of the STC (Providing it is vendor supported and not home grown)? It is hard to provide suggestions not knowing the STC or what the HOOK goes into. What automation tools do you have available? Tivoli Omegamon, CA SYSVIEW, CA OPS/MVS, other? How would you normally monitor for this type of condition? Does someone just "notice" something is not quite right? Lizette -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of KUMAR Anil Sent: Thursday, September 12, 2013 8:46 AM To: [email protected] Subject: STC looping and caused the virtaul memory csa shortage Hi All, Recently we had an issue in one LPARs where in a product STC (which starts, plants a hook and then ends) was looping. It consumed csa/ecsa and the LPAR was affected very much. We are looking at suggestions /inputs on how to handle these situations. If there are any automations put in place to handle such situations (for e.g. a particular STC should not start more than 5 times or a HOOK resource's status being captured), please provide details. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
