Hi, Recently in one of our sandbox system we had HASP263 messages flooding up in the console.
I found a note in Manuals about Deadlock or to know how to The following messages are typical of poor management of HOLD, DORMANCY, and LOCKOUT settings or are symptomatic of a system problem: $HASP263 WAITING FOR ACCESS TO JES2 CHECKPOINT $HASP9207 JES2 CHECKPOINT LOCK HELD When issued together, these messages can be due to JES2 spending a lot of time processing a specific request or because JES2 is a victim of another problem. A useful command to help diagnose this is the following: $D PERFDATA(EVENT) >From your experience which Parm of JES Should be tuned enough to avoid the DEAD locks in future ? We have two LPARS in a SYSPLEX participating in MAS. Zos at 1.11. Any Suggestions or Pointers ? Chris ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
