Is it possible that the user who held the enqueue was just logging on to TSO and walked away from the terminal while pending broadcast messages were being displayed, filling the screen until the "***" message was displayed at the bottom of a full screen, with more pending messages waiting to be displayed? That, IMHO, might cause a lengthy enqueue on the BRODCAST dataset. OTOH ... waiting next in line was a batch job. What's this job doing with the BRODCAST dataset? Could this have contributed to the 'hung user' - symptoms?
Regards, Ulrich Krueger -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Donnelly, John P Sent: Thursday, January 20, 2011 9:57 AM To: [email protected] Subject: Enqueue on SYS1.BRODCAST We received calls from TSO users who had initiated a TSO LOGON and then just hung; no activity, no messages, just hung. After some angst we discovered with a TASID display: System ENQ contention Line 1 o Command ===> Scroll ===> CS Data set name Owner Requestor Å¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢×¢¢¢¢¢¢¢¢¢¢×¢¢¢¢¢¢¢¢¢¢Õ ... *000070S191M1SYS1.BRODCAST ... BJWWSC ... CJPDSCRX ... Ä¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢¢Ç¢¢¢¢¢¢¢¢¢¢Ç¢¢¢¢¢¢¢¢¢¢Ô We do not understand how this individual acquired this enqueue; we would have expected MASTER... Any comments would be appreciated... John Donnelly National Semiconductor Corporation 2900 Semiconductor Drive Santa Clara, CA 95051 408-721-5640 408-470-8364 Cell [email protected] ---------------------------------------------------------------------- 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
