From: CRDGW2::CRDGW2::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX" 27-FEB-1992 16:26:07.09 To: ARISIA::EVERHART CC: Subj: MWAIT V1.06 out now From: RELAY-INFO-VAX@CRVAX.SRI.COM@SMTP@CRDGW2 To: Everhart@Arisia@MRGATE Received: by crdgw1.ge.com (5.57/GE 1.123) id AA13393; Thu, 27 Feb 92 15:26:54 EST Message-Id: <9202272026.AA13393@crdgw1.ge.com> Received: From SUN2.NSFNET-RELAY.AC.UK by CRVAX.SRI.COM with TCP; Thu, 27 FEB 92 12:20:51 PST Received: from ncdlab.ulcc.ac.uk by sun2.nsfnet-relay.ac.uk via JANET with NIFTP id <14667-0@sun2.nsfnet-relay.ac.uk>; Thu, 27 Feb 1992 13:09:33 +0000 Date: Thu, 27 Feb 92 13:00 GMT From: Nick de Smith To: INFO-VAX <@nsfnet-relay.ac.uk:INFO-VAX@KL.SRI.com> Subject: MWAIT V1.06 out now (from: Nick de Smith, NICK@NCDLAB.ULCC.AC.UK) Hi, The MWAIT utility (V1.06) is now available from VMSSERV@NCDLAB.ULCC.AC.UK by sending the text: SEND MWAIT.PACKAGE in the BODY of a mail message. MWAIT V01.05 is also in directory [.ATG] on the Fall '91 US VMS SIG tapes. Please note that for various reasons this VMSSERV may not be available for more than a couple more weeks 8-( Some of the new features in 1.05/1.06 (apart from improved documentation): 1. Now independant of VMS V5.x version (1.05) 2. Details of the AST status are now given including blocked ASTs. You can use this information to check is a process is blocked at AST level, or from having ASTs delivered. The current and previous processor modes are also displayed so that if more than 1 AST level is active, you can determine which is executing (1.05/1.06). 3. PC resolution for RWAST processes now includes all loaded device drivers. If A specific (known) VMS thread is not the cause of the RWAST, the PC is checked to see if it lies in a loaded driver. If it does, the name of the driver and the offset within that driver are given (1.06). 4. Much better RWAST, RWMBX and JIB wait analysis. MWAIT now gives details about how much quota or resource the process is lacking, and which devices/files/channels the requests are being made for. MWAIT displays the register values for processes that SDA cannot/does not (1/06/1.05). eg. $ MWAIT 20A00452 Pid User name Process name Prior State Port 20A00452 NICK NICK_1 6/4 RWAST -Sub- Wait mask: 00000001, Cluster: 0, Time: 0 00:00:00.08 0: E0000001, 1: 00000000 Mode: Current: KERNEL, Previous: USER AST status: Active: (none), Enabled: KESU Process resource wait is ENABLED. Process has no BIO left (BIOCNT zero). Process has 100. outstanding BIO operations (BIOCNT: 0., BIOLM: 100.) Process has 2. outstanding ASTS active (ASTCNT: 98. ASTLM: 100.) Process registers: R0: 00000001 R1: 00000001 R2: 80408F5A R3: 00000010 R4: 80408F20 R5: 8037C470 R6: 7FFC9F90 R7: 00000030 R8: 80138148 R9: FFA00001 R10: 00000030 R11: 00000003 AP: 7FF15928 FP: 7FFE77E4 PC: 801DE68E PSL: 00C00001 Quota: R1 = quantity, R2 = address, R3 = width(bits). -> (Requested: 1. unit, Available: 0. units) -> Quota wait on: Buffered I/Os remaining count (BIOCNT: 0.) $! Better detail now on requests like this. $ MWAIT 20200534 Pid User name Process name Prior State Port 20200534 NICK NICK_1 6/4 RWMBX -Sub- Wait mask: 00000002, Cluster: 0, Time: 0 00:00:00.43 0: E0000000, 1: 00000000 Mode: Current: USER, Previous: USER -> AST status: Active: U, Enabled: KESU, AST(s) waiting Process resource wait is ENABLED. -> Attempting to write 8. bytes to MBA2454: on channel 0060 (hex) -> Messages: 6., Quota (bytes): Initial = 50., Remaining = 2. $! RWMBX now gives details on the request and device that is central to the $! problem. Note that this example is also in an AST and has others waiting. $ MWAIT 202000E2 Pid User name Process name Prior State Port 202000E2 NICK NICK_1 4/4 JIBYT -Sub- Wait mask: 80D78190, Cluster: 0, Time: 0 00:01:49.44 0: E0000000, 1: 00000000 Mode: Current: KERNEL, Previous: KERNEL AST status: Active: (none), Enabled: KESU Job buffered I/O count exhausted -> (Requested: 2080. bytes, Available: 1632. bytes, Quota: 39424.) $! For BYTCNT and other quota problems, the amount of quota needed together with $! the current availability is now displayed. Full documentation in the kit. [end]