Sent: Friday, March 13, 2009 10:15 AM To: [email protected] Subject: System Loop or System Hung Not Sure Which
Yesterday, the system started displaying the following messages on SYSLOG for z/os v1.4: $HASP9212 MVS NOT DISPATCHING JES2 MAIN TASK DURATION 000:01:55:09 $HASP9301 JES2 MAIN TASK ALERTS CLEARED It displayed these messages over and over. The Operations Supervisor did say that jobs were processing just fine. They could not enter any commands to the OS at all. Unfortunately, I was not here so a stand-alone dump was not taken. ... George Rodriguez Specialist, Systems Programmer Network & Technical Services (561) 357-7652 (office) (561) 707-3496 (mobil) School District of Palm Beach County 3348 Forest Hill Blvd. Room B-332 West Palm Beach, FL. 33406-5869 These messages are created by the JES2 Health Monitor: http://publib.boulder.ibm.com/infocenter/zos/v1r9/index.jsp?topic=/com.ibm.zos.r9.hasa700/has2a77075.htm Here is an explanation: http://www-01.ibm.com/support/docview.wss?uid=isg1OA06186 If some process higher in dispatching priority than JES2 is consuming all CPU resources, that could explain why no operator commands could be entered, but it would not explain why jobs were processing just fine, unless JES2's dispatching priority was way too low. More research is needed. Read through the whole second link, which describes an APAR. There could even be a bug in the JES2 health monitor. I found the above by Googling for both JES2 message numbers. Google and read the other hits. Open an ETR with IBM. Bill Fairchild Rocket Software ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
