Christian D wrote: >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 What is the lockout parameter? >$HASP9207 JES2 CHECKPOINT LOCK HELD What is the duration? >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 ? What about MASDEF HOLD= and perhaps using command $DPCE(CKPT),DETAILS >Any Suggestions or Pointers ? How busy are the volsers where your spool and checkpoints are residing? I hope your volsers only contain those datasets. Check in SDSF the screen with command MAS. Alternatively you can re-configure you checkpoints ($TCKPTDEF,RECONFIG=YES). Or use another set of checkpoints dsn. Alternatively, check your XCF and its usage. Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
