Hi Lizette; I looked at the log and did not see any JES2 commands issued. The syslog stopped recording shortly after the messages. No SVC dump produced. Thanks
Lizette Koehler <[email protected]> Sent by: IBM Mainframe Discussion List <[email protected]> 01/26/2009 12:06 PM Please respond to IBM Mainframe Discussion List <[email protected]> To [email protected] cc Subject Re: *$HASP9211 JES2 MAIN TASK NOT RUNNING Do you know if any JES2 commands were issued about 1 minute prior to JES2 producing the $HASP9211 message? You might look through syslog to see. Or was an SVC Dump produced during this time? Have you looked at RMF Mon III to see what JES2 was doing at the time? The $HASP9211 message states: JES2 issues this message in response to a $JDJES or a $JDSTATUS monitor command or as a highlighted message. Based on context, this message can indicate an alert or an incident JES2 is tracking. This message is issued when the JES2 main task has been waiting at its normal wait for the duration specified. There are indicators that the main task does have work to do and should be running, but it is not. System Action: If the condition persists, JES2 reissues this message every 30 seconds with updated information. Operator Response: Monitor alerts indicate potential reasons why JES2 is not functioning properly. If this condition persists, notify your system programmer. System Programmer Response: JES2's main task might not be running because of improper tuning of MVS parameters or because of a problem in the JES2 address space. If the condition persists, investigate tuning and operational considerations first. For example, consider if online applications have been tuned to run before JES2 (not a recommended practice), or if the operator has issued a command that requires heavy use of system resources. Lizette >JES2 WAS AT THE TOP IN CPU - WHEN I LOOKED AT TMON. >NO $ COMMANDS WORKED. >I WILL LOOK AT THE PTFS AND SEE WHAT FITS >I'M ON Z/OS 1.7 AND NOT SUPPORTED, >MAYBE Z/OS 1.9 CAN FIX THIS. >THANKS >GM > > > >> > >I would probably start here > > OA13994 UR1 4/30/08 LOOP IN >HASCHAM START IO OR CHANNEL END APPENDAGE >WHEN BUFFER > OA06186 PER 7/12/04 VARIOUS >PROBLEMS CAN CAUSE MISLEADING JES2 MONITOR >MESSAGES. > OA21050 PER 10/17/07 >BPXOINIT LOOPING, CONSUMING CPU , JES2 MAIN TASK >NOT RUNNING > >---------------------------------------------------------------------- > ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
