The problem is that the SVC99 dynamic allocation is unconditional. If the resource is already owned, the subsequent allocation request fails. At that point there is no enqueue conflict to show in any monitor because no exclusive or shared waiter was added for that resource in the GRS list.
Static allocation is an option because allocation services causes the job to wait (indefinitely) for enqueued datasets named in your JCL. This is a perennial issue that begs to be resolved. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Joseph W Gentile Sent: Tuesday, September 22, 2015 11:04 AM To: [email protected] Subject: Re: Dataset enqueue, how to find the culprit. Hi, you could also run ISGECJES from SAMPLIB (z/OS 2.1). It is a simple dataset enqueue contention monitor written in assembler. It won't go back in time. It will alert you to dataset contention going forward. We wrote an article about it in z/OS Hot Topics Issue 27, page 54. http://publibfp.dhe.ibm.com/epubs/pdf/e0z3n100.pdf -Joe Joe Gentile z/OS GRS Lead (845)435-2184 (T/L 295-2184) [email protected] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
