1 INFO-VAX	Sat, 06 Nov 2004	Volume 2004 : Issue 617       Contents:0 An interesting link about CPU families over time  Re: BA353 configuration question( Re: Ball-park figure for OpenVMS costing* Re: Cluster Ethernet Interconnect question
 eBCVG article 2 Re: Freeware V6 won't mount on old versions of VMS GNV date behavior  GNV date behavior ) how to implement an append only log file? - Re: how to implement an append only log file? - Re: how to implement an append only log file? - Re: how to implement an append only log file? - Re: how to implement an append only log file? ! Re: LNM$SYSCLUSTER_TABLE question  Re: Performance Tuning Re: Performance Tuning Re: Performance Tuning Re: Performance Tuning RE: Performance Tuning Re: Performance Tuning' Re: Service Contract for Alpha Hardware ' Re: Service Contract for Alpha Hardware  Serving HTML CD from VMS Re: Serving HTML CD from VMS Re: Serving HTML CD from VMS. System crash after installing 732-UPDATE-V0300 Re: Time Change   F ----------------------------------------------------------------------  $ Date: Sat, 6 Nov 2004 06:20:53 -0500# From: "John Smith" <a@nonymous.com> 9 Subject: An interesting link about CPU families over time , Message-ID: <BrydnTYW1Z8ALhHcRVn-jA@igs.net>  + http://www3.sk.sympatico.ca/jbayko/cpu.html    ------------------------------  * Date: Sat, 6 Nov 2004 17:20:31 +0000 (UTC)P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)) Subject: Re: BA353 configuration question $ Message-ID: <cmj14u$qdb$1@online.de>  H In article <pan.2004.10.19.22.45.00.16833@access4less.net>, James Nykiel" <jnykiel@access4less.net> writes:   K > I would eventually like to build a cluster consisting of two AlphaStation I > nodes with Ethernet Interconnects, how can the BA353 be integrated into E > this configuration so that its resources (drives) are available the 
 > cluster?  A Here's my advice.  First, get a third member.  I would suggest a  F VAXstation 4000/60 (or /90 if you can find one).  It is small, quiet, H fast (for a VAX) and consumes little power.  That way, you can keep the F cluster up when a node is down (planned or unplanned).  Second, get a C second BA353 and shadow all the disks.  This not only provides the  E availability of shared disks, but redundancy as well.  And it can be  E done with bottom-of-the-line hardware.  Easiest way to go is for all  E nodes to MSCP serve all disks and mount all shadow sets on all nodes.    ------------------------------  * Date: Sat, 6 Nov 2004 17:31:10 +0000 (UTC)P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)1 Subject: Re: Ball-park figure for OpenVMS costing $ Message-ID: <cmj1ou$qdb$3@online.de>  3 In article <clh28b$f1n$1@news.netkonect.net>, Garry * <asdfasdfadsf@asdfasdfasdfre.com> writes:   H > 	I'm considering using OpenVMS for a web server, it'll be for a small J > commercial company, so I'm not sure if I can get away with the Hobbyist  > licence.     You can't and you shouldn't.  ? > Right now I don't want to sign my soul over to HP just for a  J > pricing quote, so can someone give me a ball-park figure for OpenVMS on K > a single processor 1U rackmount? Something like a DS10L, or if I can get  I > one cheap, a supported Itanium machine. I figure I can get the machine  5 > off eBay, so it's just the OS I need the quote for.   G Consider that something like a VAXstation 4000 might be more than fast  I enough for your needs.  The excellent OSU server by Dave Jones runs fine  D on VAX.  Or do you need new hardware so you have support?  Consider G getting a dozen VAXstations, which you should be able to find for next  H to nothing; if one goes, just replace the whole box.  (I'm assuming you H would be running the web server in a cluster, so the customers wouldn't  notice if a node goes down.)   ------------------------------  * Date: Sat, 6 Nov 2004 17:22:23 +0000 (UTC)P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)3 Subject: Re: Cluster Ethernet Interconnect question $ Message-ID: <cmj18f$qdb$2@online.de>  B In article <pan.2004.10.19.05.13.31.544140@access4less.net>, James) Nykiel <jnykiel@access4less.net> writes:    H > If I want to create a cluster with two AlphaStations using an Ethernet? > Interconnect do I need to have two Ethernet adapters in each?    No.    ------------------------------  $ Date: Sat, 6 Nov 2004 10:27:13 -0000> From: "Alex Daniels" <Alex(nospamthanks)Daniels@themail.co.uk> Subject: eBCVG article6 Message-ID: <418ca6fe$0$27537$db0fefd9@news.zen.co.uk>  > Anyone got details of the unreferenced 'study' they allude to.  ( http://www.ebcvg.com/articles.php?id=318   Alex   ------------------------------  # Date: Sat, 06 Nov 2004 14:04:08 GMT " From:   VAXman-  @SendSpamHere.ORG; Subject: Re: Freeware V6 won't mount on old versions of VMS 0 Message-ID: <00A3A768.17896266@SendSpamHere.ORG>  j In article <7NWhuiyCx4yN@eisner.encompasserve.org>, kaplow_r@encompasserve.org.TRABoD (Bob Kaplow) writes:K >Not sure if this is a 'bug' or a 'feature', but I just discovered that the M >VMS Freeware V6 CD is incompatible with older versions of VMS. It looks like L >the problem is that the disk was INITed with a cluster size of 1, resultingD >in too many clusters on the disk to be mapped by 'traditional' VMS. > E >I couldn't mount it on my 7.1-2 system, but could mount it on 7.3-2.   E I posted about this months ago.  A stupid decision.  They won't mount E in my InfoServers either so I had to read in the contents and re-burn ) them to get them to be read everywhere.      --  < http://www.ProvN.com  for the *best* OpenVMS system security=                       solutions that others only claim to be.  --  , Cyber-Terrorism (si'-ber tayr'-or-iz-em) n.:M   The release of, the sale of, or the use of any Micro$oft software product!   --  K VAXman- A Bored Certified VMS Kernel Mode Hacker   VAXman(at)TMESIS(dot)COM    ------------------------------  # Date: Sat, 06 Nov 2004 15:22:23 GMT 0 From: spud_demon@.eTHUNDERMAKER.NET (Spud Demon) Subject: GNV date behavior/ Message-ID: <P_5jd.7$rj3.13869@news.uswest.net>   - Trying to build apache using GNV. I get this:    E$ make P /DSA0/SYS0/SYSCOMMON/GNV/bin/MAKE.EXE: *** Warning: File `Makefile.' has modificD ation time in the future (2004-11-06 10:05:28 > 2004-11-06 09:19:39)O /DSA0/SYS0/SYSCOMMON/GNV/bin/MAKE.EXE: *** No targets specified and no makefile 
 found.  Stop.  E$ (VMS system time is 10:19 now.)    Is this a common problem?     . --Spud Demon		spud_demon -at- thundermaker.netD please quote liberally because Google doesn't get posts from my ISP.   ------------------------------  # Date: Sat, 06 Nov 2004 15:23:45 GMT 0 From: spud_demon@.eTHUNDERMAKER.NET (Spud Demon) Subject: GNV date behavior/ Message-ID: <506jd.8$rj3.14044@news.uswest.net>   - Trying to build apache using GNV. I get this:    E$ make P /DSA0/SYS0/SYSCOMMON/GNV/bin/MAKE.EXE: *** Warning: File `Makefile.' has modificD ation time in the future (2004-11-06 10:05:28 > 2004-11-06 09:19:39)O /DSA0/SYS0/SYSCOMMON/GNV/bin/MAKE.EXE: *** No targets specified and no makefile 
 found.  Stop.  E$ (VMS system time is 10:19 now.)    Is this a common problem?     . --Spud Demon		spud_demon -at- thundermaker.netD please quote liberally because Google doesn't get posts from my ISP.   ------------------------------   Date: 5 Nov 2004 23:42:49 -0800 * From: bonzinib60@arcor.de (Josef Jarousse)2 Subject: how to implement an append only log file?= Message-ID: <ae3d5869.0411052342.76e593e8@posting.google.com>    Hi,    I have the following problem:   E I design a system and I would like it to trace each action the system C does. Especially it would be important that even the programm calls E from the admin are logged too. What I want is a log file which has an C owner that is different from the admin (internal audit for example) C and in which the application writes some informations about started F modules etc.. This log file should be "append-only" so that nobody can delete some entries in it., Is there a way to implement such a log file?   Thanks Jo   ------------------------------  % Date: Sat, 06 Nov 2004 12:48:07 +0200 * From: Mike Rechtman <rechtman@tzora.co.il>6 Subject: Re: how to implement an append only log file?+ Message-ID: <2v3olkF2g4gmsU1@uni-berlin.de>    Josef Jarousse wrote:  > Hi,  >  > I have the following problem:  > G > I design a system and I would like it to trace each action the system E > does. Especially it would be important that even the programm calls G > from the admin are logged too. What I want is a log file which has an E > owner that is different from the admin (internal audit for example) E > and in which the application writes some informations about started H > modules etc.. This log file should be "append-only" so that nobody can > delete some entries in it.. > Is there a way to implement such a log file? >  > Thanks > Jo
 Start with $ HELP AUDIT   two gotchas:H 1. There cannot be, by definition, anything not accessible via VMS to a B sufficiently privileged user. Any logging you start can always be G stopped, permanently or temporarily by the admin. (Under VMS generally  5 called the system manager) - thats one of his duties.   I 2. Logging everything has the unfortunate result of very quickly filling  D up any disk, leading either to loss of data (earliest, latest - you  choose) or some type of DOS.  E When you write "program calls": is that individual "run" commands or  G their equivalent (foreign commands, DCL commands) or do you need to go   to the system-call level?    Mike   --  J New to Usenet? read http://eisner.encompasserve.org/~rechtman/post_hlp.htmE --------------------------------------------------------------------- E Usual disclaimer: All opinions are mine alone, perhaps not even that. D Mike Rechtman                                 *rechtman@tzora.co.il*C    "20% of a job takes 80% of the time, the rest takes another 80%" E ---------------------------------------------------------------------    ------------------------------  # Date: Sat, 06 Nov 2004 10:39:50 GMT # From: "Phil" <dooleys@snowy.net.au> 6 Subject: Re: how to implement an append only log file?= Message-ID: <WR1jd.19344$K7.12374@news-server.bigpond.net.au>   7 "Josef Jarousse" <bonzinib60@arcor.de> wrote in message 7 news:ae3d5869.0411052342.76e593e8@posting.google.com...  > Hi,  >  > I have the following problem:  > G > I design a system and I would like it to trace each action the system E > does. Especially it would be important that even the programm calls G > from the admin are logged too. What I want is a log file which has an E > owner that is different from the admin (internal audit for example) E > and in which the application writes some informations about started H > modules etc.. This log file should be "append-only" so that nobody can > delete some entries in it.. > Is there a way to implement such a log file?3 The "proper" way to do this is to use audit events. 6 You can audit access to any vms object by an audit ACE: and you can add calls to $audit_event in your application. (when you start a module?)> The audit log is owned by system so nobody can delete from it.; Then $analyze/audit takes care of all your audit reporting. 3 see "guide to vms security" for a full explanation.  Phil   ------------------------------  % Date: Sat, 06 Nov 2004 06:35:10 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> 6 Subject: Re: how to implement an append only log file?, Message-ID: <418CB6EA.41A097D6@teksavvy.com>  G Making logging totally bulletproof, even to the system manager is hard.   N Architecturally, you may wish to have an ACP process (much harder to delete byM system manager) receive log resuests from users and write it to the log file. M You'll probably want some form of protocol between the client and this ACP to N authenticate to both the client and to the server that someone hasn't replaced the legitimate programs.  L And the ACP will need to number all log entries and each entry should have aN checksum that includes the log number. And you may want to encrypt the data inN it too. This way, it will be harder for the system manager to figure out whichM entry to remove, and removal of an entry from the log files would result in a N missing log entry number(s). You'll also want those files to be locked without; any sharing so that the system manager cannot look at them.   N (can one even prevent backup/ignore=interlock) from accessing a file opened by an application ?)    ------------------------------   Date: 6 Nov 2004 07:32:42 -0600 - From: Kilgallen@SpamCop.net (Larry Kilgallen) 6 Subject: Re: how to implement an append only log file?3 Message-ID: <l80hXAm02AiZ@eisner.encompasserve.org>   X In article <2v3olkF2g4gmsU1@uni-berlin.de>, Mike Rechtman <rechtman@tzora.co.il> writes:   > two gotchas:J > 1. There cannot be, by definition, anything not accessible via VMS to a D > sufficiently privileged user. Any logging you start can always be I > stopped, permanently or temporarily by the admin. (Under VMS generally  7 > called the system manager) - thats one of his duties.   C That depends on what is meant by the non-word "admin".  If it means C "VMS System Manager" what you say is true.  But the original poster C talked about application actions taken by the "admin", which is not = a typical system manager role in a high-security environment.    ------------------------------  * Date: Sat, 6 Nov 2004 17:57:01 +0000 (UTC)P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)* Subject: Re: LNM$SYSCLUSTER_TABLE question$ Message-ID: <cmj39d$qdb$6@online.de>  - In article <sxGs9xan6lld@cuebid.zko.dec.com>, 2 brooks@cuebid.zko.dec.nospam (Rob Brooks) writes:   E > When a clusterwide logical is defined, the definition is replicated K > across the cluster immediately.  That means that each node in the cluster G > has a local definition of that logical name, such that the definition F > will survive a rolling reboot.  The only way to remove a clusterwideE > logical name definition is to reboot the entire cluster at once (or   > use the DCL command DEASSIGN).    Almost.  Consider the following:   $ sh log testtest 8 %SHOW-S-NOTRAN, no translation for logical name TESTTEST. $ define/log/table=lnm$syscluster testtest foo. $ define/log/table=lnm$syscluster testtest foo. $ define/log/table=lnm$syscluster testtest bar@ %DCL-I-SUPERSEDE, previous value of TESTTEST has been superseded+ $ define/log/table=lnm$process testtest foo + $ define/log/table=lnm$process testtest foo @ %DCL-I-SUPERSEDE, previous value of TESTTEST has been superseded+ $ define/log/table=lnm$process testtest bar @ %DCL-I-SUPERSEDE, previous value of TESTTEST has been superseded  G This looks to me like, in the case of lnm$syscluster, first a check is  F done to see if the value has changed, but not for other tables.  This G makes sense, since probably for other tables it is quicker to redefine  E it than to test it, but the opposite is true for lnm$syscluster.  Of  ! course, the results are the same.    ------------------------------  % Date: Sat, 06 Nov 2004 13:13:00 +0100 3 From: Michael Unger <spam.to.unger@spamgourmet.com>  Subject: Re: Performance Tuning + Message-ID: <2v3tgvF2giphqU1@uni-berlin.de>   ' On 2004-11-06 04:08, "Tim Smith" wrote:   F > Is there any online material, perhaps the relevant Compaq manuals onA > performance tuning - measuring, system parameters, tuning etc.?   : >From the OpenVMS 7.3-2 PDF documentation on the web site:  ! -- OpenVMS Performance Management G -- OpenVMS System Manager's Manual, Volume 2 -- Tuning, Monitoring, and  Complex Systems    and perhaps   - -- OpenVMS Alpha System Analysis Tools Manual    Michael    --  ; Real names enhance the probability of getting real answers. 5 My e-mail account at DECUS Munich is no longer valid.    ------------------------------  $ Date: Sat, 6 Nov 2004 12:50:39 -0000> From: "Alex Daniels" <Alex(nospamthanks)Daniels@themail.co.uk> Subject: Re: Performance Tuning 6 Message-ID: <418cc8a5$0$27546$db0fefd9@news.zen.co.uk>  ? "David J Dachtera" <djesys.nospam@comcast.net> wrote in message % news:418C4376.5C5D02DF@comcast.net...  > Tim Smith wrote: > >  > > Hi,  > > H > > Is there any online material, perhaps the relevant Compaq manuals onC > > performance tuning - measuring, system parameters, tuning etc.?  > C > If you look at the on-line docset, you should find information on D > performance management. It was a whole separate volume at one time# > (OpenVMS Performance Management).  > 5 > There's no simple cookbook that I know of, however.  >   K There is one. The Cookbook of Performance Slowdown, VAX and Alpha, V6.0 and  Up....   Alex  K Copyright (c) 1997, 2001 Compaq Computer Corporation.  All rights reserved.   6 PRODUCT:    Compaq OpenVMS VAX, Versions 6.0 and above8             Compaq OpenVMS Alpha, Versions 6.1 and above   COMPONENT:  Performance   ' SOURCE:     Compaq Computer Corporation      Note: =     For information on performance tuning on OpenVMS VAX V5.n <     systems, reference another article in the OPSYS database     with the query:   +          V5.n Cookbook Performance Slowdown   =     This article is extremely long.  We recommend producing a      hardcopy for reading.      BACKGROUND:   B Occasionally OpenVMS systems may experience performance slowdowns.C The performance degradation is typically due to requirements placed C on one or more of a system's main resources, i.e., CPU, memory, and C the I/O subsystem.  This article describes basic techniques to help 3 determine the cause of the performance degradation.      PREPARATION:  F The following guidelines will help ensure the best possible outcome of  performance analysis and tuning:  & - Collect Baseline Performance Metrics  <   The most efficient technique for determining if a resourceB   limitation exists is by comparing performance metrics which were@   collected during a period of normal system activity to current   system conditions.  >   Unfortunately, you may currently be experiencing performanceB   problems and haven't collected any baseline performance metrics.@   If so, alleviate the current problems and plan to collect thisE   vital information.  This information will assist in avoiding future H   occurrences by providing a useful resource for monitoring performance.  C   Collect the baseline performance metrics during time periods when F   normal resource consumption is at its peak.  If you're unsure of theD   times, evaluate the systems performance for a few days.  After theD   metrics are collected ensure their continued validity with monthly)   comparisons to the current environment.   >   The MONITOR utility may be used for evaluating the operating.   environment and collecting baseline metrics.  
 - Run AUTOGEN   D   AUTOGEN calculates the initial values for key SYSGEN parameters onC   your particular system.  It can solve performance problems caused B   by the manual modification of parameters, typically done withoutG   regard for the complex interrelationships between certain parameters.   A   AUTOGEN is coded to account for the relationship between system C   resources and their parameters.  With this ability and the use of @   performance metrics make it the best tool to use for parameter   modification.   F   Run AUTOGEN whenever the systems configuration is modified.  This isE   particularly important after a significant change to the user load, B   the installation of new applications, or the addition of memory.G   Run the procedure after 1 to 2 days of a normal system load following D   the change.  This allows for the collection of more feedback data.  + - Plan Recovery Procedures and Notify Users   B   Tuning an OpenVMS system may require parameter modification, theA   reallocation of user quotas, or the reconfiguration of hardware C   devices.  Some changes may not produce the desired effect further E   degrading system performance.  This is not meant to dissuade anyone C   from the analysis and tuning of their OpenVMS system.  It's meant A   to heighten awareness regarding the complexity of system tuning <   and to avoid complications leading to unexpected downtime.  )   The following will help ensure success:   8      * Always ensure that any vital data has been saved.?      * Notify users of the planned performance analysis and the %        possible impact on the system. @      * Before applying any of the articles solutions, ensure theC        analysis and possible effects to your system are understood. G      * Because any change to a systems parameter file has the potential E        for causing a system hang, you should review the procedures to *        force crash and reboot your system.          Reference Articles:>          There are many articles in the OPENVMS database whichB          contain procedures to force crash and reboot your system.?          These articles may be found using the following search           string:                      FORCE_CRASH    < STEPS TO INVESTIGATE SYSTEM PERFORMANCE (table of contents):  F    1) RAISE YOUR PRIORITY SO YOU CAN LOOK FOR THE CAUSE OF THE PROBLEMA    2) CHECK FOR CONSOLE ERROR MESSAGES RELATING TO PAGEFILE SPACE @    3) CHECK FOR CONSOLE ERROR MESSAGES RELATING TO POOL PROBLEMSF    4) CHECK FOR CONSOLE ERROR MESSAGES RELATING TO AUDIT SERVER ALARMS@    5) CHECK FOR PROCESSES IN SYSTEM RESOURCE WAIT STATES (RWxxx)C    6) CHECK TO SEE IF A PROCESS IS USING A MAJORITY OF THE CPU TIME !    7) CHECK FOR A MEMORY SHORTAGE +    8) CHECK FOR PAGEFILE SPACE GETTING FULL #    9) CHECK FOR HEAVY PAGE FAULTING '   10) CHECK FOR NONPAGED POOL EXPANSION     11) CHECK FOR HEAVY DIRECT I/O   12) CHECK FOR SWAPPING$   13) CHECK FOR PAGED POOL DEPLETION2   14) CHECK FOR AUTOMATIC WORKING SET DECREMENTING"   15) CHECK FOR HEAVY BUFFERED I/O   16) CHECK PROCESSOR MODES    17) CHECK DECnet ACTIVITY (   18) CHECK DISTRIBUTED LOCKING ACTIVITY  D  1) RAISE YOUR PRIORITY SO YOU CAN LOOK FOR THE CAUSE OF THE PROBLEM  E     At the DCL prompt, issue the 'SET PROCESS/PRIORITY=15' command to G     raise your process priority.  This should help improve the system's G     response to your commands, unless the system is hung or a real-time E     process is taking all the CPU time.  This command requires ALTPRI D     privilege and depending on the exact nature of the slowdown, may$     take several minutes to execute.  C     If you have real-time processes on your system, you may need to E     elevate your priority above them to get timely response.  If this A     is the case, the real-time processes may be in a compute loop ;     blocking other lower priority processes from executing.     ?  2) CHECK FOR CONSOLE ERROR MESSAGES RELATING TO PAGEFILE SPACE   #     Typical errors to look for are:   G         SYSTEM-W-PAGEFRAG, Pagefile badly fragmented, system continuing D         SYSTEM-W-PAGECRIT, Pagefile space critical, system trying to#                            continue   H     These errors indicate that your pagefile is too small to support the#     current activity on the system.        Reference Article:D       [OpenVMS] Reasons for RWMPB/RWMPE States and PAGEFRAG/PAGECRIT                 Messages  <     (Reference the discussion in "8) CHECK FOR PAGEFILE...")    >  3) CHECK FOR CONSOLE ERROR MESSAGES RELATING TO POOL PROBLEMS  1         SYSTEM-W-POOLEXPF, Pool expansion failure   G     This error indicates that OpenVMS failed to allocate free memory to H     extend non-paged dynamic memory because the free page list containedE     less than (64k + MPW_LOLIMIT + FREELIM) pages, on OpenVMS VAX, or      pagelets on OpenVMS Alpha.  '        1. Insufficient physical memory. H        2. An application or layered product is over allocating non-paged/           dynamic memory and causing expansion.   C     (Reference the discussion in "10) CHECK FOR... POOL EXPANSION")     D  4) CHECK FOR CONSOLE ERROR MESSAGES RELATING TO AUDIT SERVER ALARMS  A       AUDSRV-W-RESCRITICAL, security auditing resources exhausted /                             on journal SECURITY F       AUDSRV-I-RESINFO, resource information n blocks needed, n blocks!                         available   D     These errors indicate that the AUDIT$SERVER process has detectedD     that free space on the disk containing the audit server log fileB     has fallen below the WARNING threshold.  This will be the disk,     defined by the logical VMS$AUDIT_SERVER.  @     If not immediately addressed, and disk space falls below the:     defined ACTION threshold, processes will be suspended.  D     To correct this problem, log into an account that has OPER as anB     authorized default privilege and delete unnecessary files fromE     the disk until the free space exceeds the WARNING threshold.  The D     following command will display the WARNING and ACTION thresholds     for the disk:            $ SHOW AUDIT/JOURNAL  ?     For more information, refer to the "OpenVMS Guide To System (     Security", (AA-Q2HLA-TE), section 9.       Reference Article:<       [OpenVMS] Methods Used To Recover Space On System Disk    >  5) CHECK FOR PROCESSES IN SYSTEM RESOURCE WAIT STATES (RWxxx)  E     Use the DCL command "SHOW SYSTEM" to check process states.  These E     are displayed in the "STATE" column.  Look for any processes in a 5     wait state other than HIB, LEF, COM, CUR, or CEF.          Note: C         It is a normal function of the scheduler to place processes A         in differing wait states for one reason or another.  It's A         when processes become hung in a particular state that you D         begin to see an impact on system resources and a degradationA         in performance.  Therefore, multiple samples of the "SHOW B         SYSTEM" display must be analyzed to determine if a problem         exists.   :     Resource Wait states which may indicate a problem are:  	     RWMPB 	     RWMPE E       Waiting for the Modified Page Writer to write the Modified Page E       list (MPL) to the pagefile.  These states usually indicate that #       the pagefile is getting full.          Reference Article:F         [OpenVMS] Reasons for RWMPB/RWMPE States and PAGEFRAG/PAGECRIT                   Messages  	     RWNPG 	     RWPAG E       "Nonpaged Dynamic Memory full" and "Paged Dynamic Memory full". H       These states indicate that the systems pool areas are insufficient+       and that pool expansion has occurred.          Reference Articles: 8         [OpenVMS] How to Troubleshoot a Process in RWNPG8         [OpenVMS] How to Troubleshoot a Process in RWPAG       PFW C       Page Fault Wait.  The process must wait for a page to be read E       in from disk.  This state usually occurs when a disk containing B       a pagefile, or installed image files, is overloaded with I/O)       requests or is encountering errors.   D       (Reference the discussion in "11) CHECK FOR HEAVY DIRECT I/O")       FPG A       Free page wait.  A process is waiting for free memory to be D       placed on the free list.  If processes stay in this state, useB       the following questions to investigate why the Free List has       become depleted:  F         1. Has a pagefile become full, i.e. processes in RWMPx states,B            and the Modified List taken up the rest of free memory?)            (Use the SHOW MEMORY command.)   G         2. Is a single process taking up most of memory?  (Use the SHOW 9            SYSTEM command and check the "Ph.Mem" column.)   D         3. Is SWAPPER able to trim/swap processes to free up memory,A            i.e., do processes have more than WSDEFAULT of memory? A            (Compare the last column, "Ph.Mem", of the SHOW SYSTEM .             display to UAF or PQL_xxx values.)  C         4. Has the swap/pagefile become full?  (Use the SHOW MEMORY             command.)  B         5. Does SHOW MEMORY, SHOW ERROR, or ANALYZE/ERROR show any#            memory or disk problems?          Reference Article:F         [OpenVMS] Reasons for RWMPB/RWMPE States and PAGEFRAG/PAGECRIT                   Messages  	     RWMBX F       Mailbox full.  This process cannot continue writing to a mailbox"       because the mailbox is full.         Reference Articles: 8         [OpenVMS] How to Troubleshoot a Process in RWMBXC         [OpenVMS] How to Read Mailbox, MBAn:, Data Without Removing                    the Messages    v   RWINS (Alpha only) (       Waiting for an innermode semaphore  I       Indicates that a process thread is trying to acquire the inner-mode F       semaphore.  This mutex serializes thread execution in Executive,D       and/or Kernel mode while another thread of the same process is,       currently in Executive or Kernel mode.  D       Multiple threads from a single process may run concurrently onF       different processors in user and supervisor mode. For threads toF       be allowed concurrent execution in an "inner mode", they must be@       considered "thread safe" by OpenVMS Alpha.  If they're notB       considered "thread safe" they must acquire the "per process"2       inner-mode semaphore to serialize execution.  C       (Reference the discussion in "6) CHECK TO SEE IF A PROCESS IS )        USING A MAJORITY OF THE CPU TIME")   	     RWCSV -       Waiting for the CLUSTER_SERVER process.   B       The normal state of the CLUSTER_SERVER process is HIB.  MostG       often processes are hung in this state because the CLUSTER_SERVER D       process is not in HIB, or doesn't exist.  You should check allD       nodes in a cluster to identify which CLUSTER_SERVER process is       hung or missing.         Reference Article:>         [OpenVMS] How to Troubleshoot a Process in RWCSV State  	     RWSCS H       Distributed Lock Manager wait, waiting to coordinate lock activityC       on a cluster.  Processes in a cluster which make heavy use of I       either locks, or the file system, will often be seen in this state.   B       Seeing processes in this state does not always mean that theC       system has a performance problem.  This state may be seen for B       short intervals while processes wait on a resource to become<       available.  Once available, the process will continue.  A       (Reference the discussion in "18) CHECK DISTRIBUTED LOCKING         ACTIVITY")   	     MUTEX F       Mutual Exclusion Semaphore.  This state indicates that a processD       has requested exclusive access to a Mutual Exclusion SemaphoreF       (MUTEX) that can not be granted, or indicates a process resource       limitation.          Reference Article:>         [OpenVMS] How to Troubleshoot a Process in MUTEX State  	     RWAST I       The RWAST is a general purpose 'Resource Wait' state.  It indicates F       that the wait is expected to be satisfied by the delivery and/or)       enqueuing of an AST to the process.   I       Processes can be in RWAST and have NO impact on the other processes E       in the system.  Unless you know the process has a resource that G       is blocking other processes from executing, it is usually best to F       look for other performance related problems before focusing on a       process found in RWAST.          Reference Articles: H         [OpenVMS] How To Troubleshoot A Process In RWAST On VAX or Alpha4         [OpenVMS] How To Troubleshoot a Hung Process       SUSP/       Indicates that the process was suspended.   H       - Processes could be put in this state by the AUDIT_SERVER processF         if disk space on the volume containing its log files reach the         ACTION threshold.   F         (Reference the discussion in "4) CHECK...AUDIT SERVER ALARMS")  E       - A process would also enter a SUSP state if it were the target I         of a SET PROCESS/SUSPEND command.  The command SET PROCESS/RESUME -         should clear this type of suspension.   
         Note: D           Some processes, such as ALL-IN-1, use SUSP as their normal#           state when not executing.   	     COLPG D       Collided Page Wait.  Several processes incur simultaneous pageD       faults on the same shared page.  The first process that faultsC       this page will be placed into PFW.  The second and succeeding &       processes enter the COLPG state.  A       If several processes are in COLPG, this may indicate that a C       shareable image, pagefile, or pageable section file may be on A       a disk that is over saturated with I/O.  This could cause a 7       delay in the resolution of the initial pagefault.   D       (Reference the discussion in "11) CHECK FOR HEAVY DIRECT I/O",        and for the PFW state)N  A  6) CHECK TO SEE IF A PROCESS IS USING A MAJORITY OF THE CPU TIMEi  D     Use the DCL command "MONITOR PROCESS/TOPCPU" to determine if oneB     or more processes are consuming the majority of CPU resources.  F     A typical scenario is for one or more compute-intensive processes,D     often BATCH jobs, blocking interactive users from being selected     to run.e  ?     If the "MONITOR PROCESS/TOPCPU" display shows processes are C     consistently changing, consider adjusting the display interval.a>     The default interval for the MONITOR utility is 3 seconds.@     Decreasing this interval to 1 second may expose other issues@     contributing to CPU consumption and performance degradation,6     e.g., a noisy line generating many login failures.         Example:C         Issuing the following command may show a continual flood ofeA         new process IDs (PIDs), with no associated process names.T  .            $ MONITOR PROCESS/TOPCPU/INTERVAL=1  @     If this is the case, the ACCOUNTING utility may be useful in=     checking for login failures and identifying the device(s)6     generating the noise.m  H     Another scenario is for less frequently scheduled, compute-intensiveF     processes to periodically consume large portions of CPU resources.G     This can be determined by extending the MONITOR utilities interval,aB     which reduces the effects of localized spikes in measuring CPU
     usage.         Example:H         The following command may reveal processes which aren't normally1         seen using the 3 second default interval:1  0             $ MONITOR PROCESS/TOPCPU/INTERVAL=30  H     If the top CPU processes have low priorities, they are not "hogging"E     the system.  These processes are merely taking available CPU timee@     because no process at a higher priority is computable (COM).         Note:uD         Use the DCL command SHOW SYSTEM to determine the priority of@         processes.  Typical priorities for interactive processes"         fluctuate between 4 and 9.  H     If CPU time seems evenly distributed between the top CPU users, thenE     the top CPU users may all be compute-intensive and blocking othere     processes.  D     The CPU resource may simply be overloaded.  This may be revealedC     using the "MONITOR SYSTEM" command to determine the overall CPUoD     consumption, in relationship to the number of COM processes.  If?     the CPU is near 100% busy (top left), check to see how manydB     processes are in the COM state (top right).  If there are moreD     than 6 computable processes, with fairly even consumption of the@     CPU, then the CPU may be saturated by the current work load.  D     Some possible workarounds for CPU saturation caused by work load     are:  F       1. Shift the work load to a time when the CPU is less saturated.  9       2. Acquire a more powerful CPU, or add another CPU.o  4       3. Share the work load with another processor.  H     Examples and workarounds for some of the most common CPU consumption     issues:o  E       - A BATCH job, or several jobs, running CPU intensive programs,sE         at priorities equal to or greater than interactive processes,o-         can easily consume all CPU resources.   *         Limit the impact of batch jobs by:  E           a. Initialize the queues with a lower JOB_LIMIT.  JOB_LIMITeH              specifies the number of concurrent BATCH jobs from a queue.D              Restricting the JOB_LIMIT during prime work hours could-              improve interactive performance.   F           b. Initialize the queues with a lower BASE_PRIORITY.  Due toH              automatic priority boosting in OpenVMS, it's suggested that,              BASE_PRIORITY be set to 1 or 2.  F      - If SWAPPER is the largest consumer of CPU resources, the systemB        may be short on memory and SWAPPER is trying to reclaim it.  @        (Reference the discussions in section 7), 8), 10) and 12)  F      - If OPCOM is one of the top CPU consumers, determine if security@        options are activated.  If so, you may want to reconsiderE        activating security options, or restrict the number of options4        activated.y  D      - If the system is compute bound with a mixture of interactive,C        I/O bound, and compute bound processes, the SYSGEN parameterdB        QUANTUM may be reduced to improve the response time for the        interactive users.,  E        QUANTUM determines the time slice for non-real-time processes,lB        i.e., processes with a base priority between 0 and 15.  TheA        default value is 20, which represents 200 millisecond timec        slices.  F        By reducing QUANTUM you reduce the time a compute-bound processE        uses the CPU without interruption.  Conversely, the larger you F        set QUANTUM, the longer a compute bound process can use the CPU        without interruption.            Note:E            Reducing QUANTUM will increase scheduling overhead because>7            processes have to be rescheduled more often.   F        QUANTUM is a dynamic parameter, i.e., it can be adjusted on theB        active system.  If this parameter is modified and yields noC        noticeable effect, it should be reset to its original value.e  E        If modifying the parameter causes a noticeable change, then do <        the following to ensure it's maintained across boots:  4          1. Use SYSGEN to update the parameter file.                  $ MCR SYSGEN *                SYSGEN> SET QUANTUM <value>$                SYSGEN> WRITE CURRENT                SYSGEN> EXIT   @          2. Include the new value in SYS$SYSTEM:MODPARAMS.DAT toC             preserve the change when AUTOGEN is run.  Adding a note 4             explaining the change is also suggested.  I        Noticeable improvement in response time for interactive processes,sE        perceived to be related to the modification of QUANTUM, may bekE        subjective, since system activity is constantly changing.  TheeB        change may, or may not, benefit the system in the long run.D        Also, larger systems are more likely to benefit from lowering        QUANTUM.n            Note:F            The SYSGEN parameter PRIORITY_OFFSET specifies the priorityG            difference required before a process can preempt the current             process.6  G      - If there are many computable processes on the system with plenty*I        of idle time, class scheduling may be affecting process execution.e          Reference Article: D          [OpenVMS] Process Class Scheduling Anomolies ($SCHED system                    service)e      7) CHECK FOR A MEMORY SHORTAGE.  D     Memory is the most controllable resource on the system.  BecauseA     of this fact, it's the most dynamic and has the potential ford      being the most miss-managed.  =     To determine if memory is a possible cause of performance A     degradation, use the DCL command MONITOR PAGE and observe the*"     Free Page List (FPL) dynamics.  B     If the FPL meets one of the following conditions, you may have     cause for concern.:G  D       1. Fluctuates above and below the SYSGEN parameter FREEGOAL*2.  J       2. Is constantly below the value of the SYSGEN parameter FREEGOAL*2.  H       3. Is constantly below the value of the SYSGEN parameter FREEGOAL.  G       4. Is constantly below the value of the SYSGEN parameter FREELIM.   F     The conditions are listed in ascending order of magnitude, 4 being     the most critical.         Note: I         Conditions 3 & 4 may also be accompanied by outswapped processes.m  C     If one of the above conditions exist a search should be made to 2     determine the cause of the memory consumption.  C        - Use the DCL command SHOW SYSTEM to determine if any singlet>          user or process is consuming large amounts of memory.  F          The display can also show if more than the expected number of          users exists.  @        - Use the DCL command SHOW MEMORY and MEMORY/POOL/FULL toB          determine if the system has acquired a larger than normal          share of memory.m        Reference Articles:E        [OpenVMS] Reasons for RWMPB/RWMPE States and PAGEFRAG/PAGECRIT1                  MessagesRB        [OpenVMS] Details On How Proactive Memory Reclamation Works    )  8) CHECK FOR PAGEFILE SPACE GETTING FULL1  D     Use the DCL command SHOW MEMORY/FILES to determine pagefile use.D     Typically the pagefiles on a busy system should be approximatelyC     50% free.  However, on large memory systems with pagefile sizesaG     nearing 1 Meg, 25-30% free may suffice.  Observation and experienceiF     are the best tools to determine if the 25-30% metric is suited for     you environment.  D     If the pagefile becomes over allocated the system slows down and>     may hang.  Processes may be seen in RWMPB or RWMPE states.       Reference Article:D       [OpenVMS] Reasons for RWMPB/RWMPE States and PAGEFRAG/PAGECRIT                 MessagesE       [OpenVMS] How To Determine PAGEFILE and SWAPFILE Usage From SDAy  C     If a system is operating with insufficient pagefile space, thenoE     pagefile space must be increased.  Depending on the extent of thet/     problem the system may have to be rebooted.e  G     (Reference the discussion in , "2) CHECK FOR CONSOLE ERROR MESSAGESo       RELATING TO PAGEFILE SPACE)  D     Use the SYSGEN command CREATE to extend an existing pagefile, or     create a new one.y         Example:F         The following command will extend a pagefile if the <filespec>G         already exists, and the value provided with the /SIZE qualifiertD         is larger than the existing file.  If the <filespec> doesn't*         exist, a new file will be created.  /              SYSGEN> CREATE <filespec>/SIZE=<n>-  C     The following should be considered in determining if a pagefiler-     should be extended, or a new one created:   B       -  If a pagefile is on the system disk which also contains aF          dumpfile and disk space is limited, the pagefile and dumpfileD          can be combined, or both can be relocated off of the system          disk.            Reference Article: A            [OpenVMS] Managing Dumpfiles on VAX & Alpha Systems or                       Clustersg@            [OpenVMS] How To Create Secondary Page/Swap Files and%                      Remove Primariesi  C       -  If a pagefile is on a disk which incurs heavy IO, move the )          pagefile to a less active drive.             Reference Article:oI            [OpenVMS] Reasons for RWMPB/RWMPE States and PAGEFRAG/PAGECRITe-                      Messages (see "CAUSE 4")m  F       -  If the pagefile is also being used for swapping, increase the3          size of the swapfile, or create a new one.r              Note:C              Use the same command to create or extend a swapfile asu.              you would a pagefile (see above).  E       -  To decrease demand on pagefiles increase the working set forl.          processes with high page fault rates.            Reference Article:oI            [OpenVMS] Reasons for RWMPB/RWMPE States and PAGEFRAG/PAGECRIT -                      Messages (see "CAUSE 2")   1     TEMPORARY FIX TO ALLEVIATE LOW PAGEFILE SPACE   )     If the following conditions are true:i  6       *  The system has lots of free memory available.  1       *  The system cannot be currently rebooted.-  C       *  A secondary pagefile cannot be created due to lack of diskmB          space or PAGFILCNT is too small to allow another pagefile          to be installed.l  G       *  The primary pagefile needs only a "little" more pagefile spaceb.          to keep everyone going to completion.  C       *  All non-essential users have been logged off the system too&          recover their pagefile space.  F     Increase the threshold for the Modified Page List which determines/     when processes are placed in a RWMPx state.A         Example:$        Issue the following commands:  C          $ SHOW MEMORY                   !See available Free Memory            $ RUN SYS$SYSTEM:SYSGEN@          SYSGEN> SHOW MPW_WAITLIMIT      !Get current waitlimit.@          SYSGEN> SET MPW_WAITLIMIT 1500  !Set it to 2 or 3 times@                                          !the current value, but?                                          !less than free memoryt4                                          !available.G          SYSGEN> WRITE ACTIVE            !Set the value on live system.c          SYSGEN> EXIT   G     If the Modified Page List continues to grow, increase MPW_WAITLIMIT 
     again.  C     If processes enter the RWMPx state, increase MPW_LOWAITLIMIT to4B     MPW_WAITLIMIT.  This may allow processes to complete normally.           CAUTION:E           This workaround is intended only as a *TEMPORARY FIX* untileG           the pagefile space can be increased.  If it fails, the systemtG           may hang.  If a reboot is required, force a crash so the dumpn           can be examined.       Reference Articles:eB       [OpenVMS] How To Create Secondary Page/Swap Files and Remove                 PrimarieslF       [OpenVMS] How To Move Satellite Page/Swap Files From System Disk                 To Local DisktI       [OpenVMS] VIRTUALPAGECNT, PGFLQUO, PAGEFILE:  How Are They Related?eB       [OpenVMS] Monitoring Page And Swap File Usage From A Command                 ProcedurekC       [OpenVMS] What Is The Maximum Size For An Installed Pagefile?hE       [OpenVMS] How To Determine PAGEFILE and SWAPFILE Usage From SDAa  E       There are also many articles in the OPENVMS database containing G       procedures to force crash and reboot your system.  These articlesA5       may be found using the following search string:n                      FORCE_CRASH    !  9) CHECK FOR HEAVY PAGE FAULTINGm  D     Page faulting occurs when a process references a page which doesC     not exist in its working set, i.e., an invalid page.  When thisnE     occurs the process must wait for Memory Management to resolve thec1     page fault by validating the referenced page.a         Note:.?         To better understand working set dynamics see the 1st 3 F         questions in the "Detailed Analysis" section, of the following         article:  H           [OpenVMS] Reasons for RWMPB/RWMPE States and PAGEFRAG/PAGECRIT                     Messages  F     Due to the way OpenVMS implements working set management, the page/     fault may be resolved from one of 4 places:l            Free Page List (FPL)E!          Modified Page List (MPL)b          Pagefilee          Disk file  F     If the page fault is resolved from the FPL or MPL (memory resident@     caches) its considered a "Soft" fault.  If resolved from theF     Pagefile or disk file, its considered a "Hard" fault.  Hard faultsC     are more costly than Soft in time and consumption of resources,e4     because an I/O is required for their resolution.  B     Resolving page faults uses CPU power.  Resolving a higher than@     normal number of page faults has a negative impact on systemE     performance.  If this is further aggravated by "Hard" faults, therE     performance impact could be significant on a poorly tuned system,e$     or one with insufficient memory.  F     Use the MONITOR SYSTEM/ALL command to show the overall "Page Fault
     Rate".         Example:         $ MONITOR SYSTEM/ALL1                           OpenVMS Monitor Utilitye.                              SYSTEM STATISTICSF                                   CUR        AVE        MIN        MAXF         Interrupt Stack          8.85       8.82       5.79      10.90F         MP Synchronization       5.24       4.84       3.96       6.05F         Kernel Mode             21.14      21.89      18.84      25.16F         Executive Mode           0.00       0.09       0.00       0.49F         Supervisor Mode          0.00       0.02       0.00       0.16F         User Mode                3.27       3.22       1.82       4.46F         Compatibility Mode       0.00       0.00       0.00       0.00F         Idle Time              361.31     360.71     355.15     364.46F         Process Count          274.00     274.00     274.00     274.00F         Page Fault Rate          0.00       1.41       0.00       5.61F         Page Read I/O Rate       0.00       0.02       0.00       0.16F         Free List Size       19122.00   19123.42   19122.00   19124.00F         Modified List Size    1508.00    1508.14    1508.00    1508.00F         Direct I/O Rate          0.00       0.63       0.00       2.12F         Buffered I/O Rate        0.81       1.74       0.33       3.60  F     The "Page Read I/O Rate" is the simplest indicator of Hard faults.B     To determine if there's excessive Hard faulting, calculate theG     percentage of Hard faults in relationship to the "Page Fault Rate".0  D     On OpenVMS VAX, the acceptable percentage of Hard faults is 10%,     and between 3-5% on Alpha.  A          Hard_Fault% = (Page Read I/O Rate)/(Page Fault Rate)*100   G     To determine if a systems poor performance is due to excessive pageoE     faulting, compare the overall "Page Fault Rate" to the percentage B     of "Kernel Mode" in the MONITOR display.  If the percentage isH     between 25-40% of the CPU, and the "Page Fault Rate" is greater thanA     (CPU_FACTOR x 100) then page faulting may need to be reduced.f         Notes:A         - A CPU_FACTOR table has been included at the end of thisr           article.  A         - Some database and office application products can causen.           higher percentages of "Kernel Mode".  C         - Some Alpha platforms incorporating VLM can withstand pagecA           fault rates far beyond the calculated thresholds in then           paragraph above.  G     If excessive page faulting is indicated, investigate the following:a       - PROCESS WORKING SETS  F       Increase the WSQUOTA for those processes which frequently appearG       in the MONITOR PROCESS/TOPFAULT display, and decrease the WSQUOTAc        for less active processes.  "     - PROACTIVE MEMORY RECLAMATION  B       Set the MMG_CTLFLAGS parameter to enable memory reclamation.  )     - THE SYSTEM WORKING SET IS TOO SMALLa  E       Use the MONITOR PAGE command, checking the "System Fault Rate",eB       to determine if the systems fault rate is greater than 3 perG       second, on average.  If so, use AUTOGEN to increase the parameteri       SYSMWCNT.o  5     - THE SIZE OF PHYSICAL MEMORY MAY BE INSUFFICIENTe  G       If the current workload is considered normal for the system, thenoD       physical memory may have to be increased to accommodate users.=       This can also cause an increase in the Hard fault rate.c       - APPLICATION DESIGN  >       Some application designs induce heavy page faulting.  In=       particular, AI and CAD applications.  If these types ofg@       applications exist, they may be the cause of the high page       fault rate.l       - THE VIOC MAY BE TOO LARGEG  E       Use the SHOW MEMORY/CACHE/FULL command to determine if the sizeb/       of VIOC is inhibiting working set growth.a  	     - XFCa  A       With OpenVMS Alpha, V7.3 and later I/O can be significantly <       enhanced with the use of extended file cache.  This is;       enabled by setting the sysgen parameter VCC_FLAG = 2.s  =       XFC can read larger I/O sizes (than VIOC) and does moreiA       aggressive read ahead algorythms.Setting VCC_FLAG = 1 tellsO'       the system to use the older VIOC.   :       $SHOW MEMORY/CACHE/FULL works for both VIOC and XFC.         Reference Articles: C         [OpenVMS] How to Interpret Info From SHOW MEMORY/CACHE/FULL                    on AlphaC         [OpenVMS] How to Interpret Info From SHOW MEMORY/CACHE/FULLs                   on VAXF         [OpenVMS] Memory Reclamation From The Virtual I/O Cache (VIOC)  -     - THE MODIFIED PAGE LIST MAY BE TOO SMALLf  D       Look at the bottom of the MONITOR PAGE display and observe theB       Modified List Size.  If it oscillate then the MPL may be tooE       small.  A small MPL, or its associated parameters not being setaE       correctly, will cause frequent flushing to disk, increasing the'       Hard fault rate.         Reference Article:F         [OpenVMS] Reasons for RWMPB/RWMPE States and PAGEFRAG/PAGECRIT                   Messages    % 10) CHECK FOR NONPAGED POOL EXPANSIONA  I     Nonpaged pool contains data structures which must be memory resident.pF     These structures are used by components running in system context,G     e.g., UCB's, IRP's, etc., or are shared by multiple processes.  The F     pool consists of 80 fixed-length lists and 1 variable-length list.E     The 80 fixed-length lists range in size from 64 to 5120 bytes, in H     increments of 64 byte.  A population history for the 80 fixed-lengthI     lists is maintained in SYS$SYSTEM:LISTPREPOP.DAT.  This file attempts 5     to repopulate the fixed-length lists during boot.h  G     In OpenVMS VAX versions prior to v6.0, nonpaged pool consisted of a F     variable-length list and 3 fixed-length lists, i.e., SRP's, IRP's,C     and LRP's, each initialized and controlled via their own set ofEH     SYSGEN parameters. With constant vigilance and multiple adjustments,F     these lists could be tuned to for peak performance in relationship3     to the consumption of memory and CPU resources.L  B     OpenVMS VAX, v6.0 and OpenVMS Alpha, introduced "Adaptive PoolD     Management", simplifying the system management overhead required     for its maintenance.       Reference Article:C       [OpenVMS] Adaptive Pool Management: A Description of NonpagedC                 Dynamic Memory  C     OpenVMS Alpha, v7.1, introduced the following SYSGEN parametersTH     which enhance the algorithms for reclaiming space from the lookaside
     lists:            NPAG_GENTLE          NPAG_AGGRESSIVE          NPAG_INTERVAL         Note:K:         For customers running v7.2, Compaq recommends that8         NPAG_GENTLE and NPAG_AGGRESSIVE be left at their2         default values of 85 and 50, respectively.  ?     These parameters can be used to control the "Free Blocks on A     Lookasides" and are defined in detail in the "OpenVMS Version      7.1 Release Notes".i  E     However, 2 facts remain the same in relationship to nonpaged poola     and system performance:g  G       1. If the pool has to expand, system performance will be effectedu$          during the expansion epoch.  I       2. Excess pool expansion, due to either overall demand or excessivecF          code allocation, can consume the memory resource to the pointH          where performance is degraded.  The resource consumption can be8          severe enough to cause system hangs or crashes.  A          (Reference the discussion in "3) CHECK FOR CONSOLE ERRORi-           MESSAGES RELATING TO POOL PROBLEMS)R  G     To determine if pool expansion is affecting, or has affected system :     performance use the DCL command SHOW MEMORY/POOL/FULL.  C     If the "Current Size (bytes)" is greater than the "Initial Sizen@     (NPAGEDYN)", pool expansion has occurred and performance wasG     affected.  However, it's important to note that SOME POOL EXPANSIONyC     IS ACCEPTABLE and not always indicative of a poorly tuned pool.oF     The expansion may be from a singular demand for resources in orderA     to test new code, or a temporary shift in workload.  Its also3C     important to note that PERFORMANCE WAS ONLY AFFECTED DURING THE G     EXPANSION EPOCH.  If no further expansion is observed over a periodtA     of time, then it's safe to assume that system performance wasd     unaffected.e  H     There's cause to monitor pool expansion if it's greater than 10-15%.D     Determine if it was uncharacteristic expansion by monitoring theH     size after it's been reinitialized by a reboot (Wait for a scheduledB     reboot.  A 10-15% expansion in nonpaged pool doesn't justify aD     reboot.).  If it expands again by 10-15%, then AUTOGEN should be     run to tune nonpaged pool.         Note: F         Ensure that the file SYS$SYSTEM:MODPARAMS.DAT does not containD         hardcoded entries for NPAGEDYN or NPAGEVIR.  MIN_ values are         acceptable.T  D     To preclude possible problems in the population history file forE     nonpaged pool, delete SYS$SYSTEM:LISTPREPOP.DAT after AUTOGEN hast(     run just prior to the system reboot.       Reference Articles:sA       [OpenVMS] NPAGEDYN Fragmented as a Result of LISTPREPOP.DATR;       [OpenVMS] Excessive NPAGEDYN Expansion on OpenVMS VAXgG       [OpenVMS] V6.n Pool Expansion Problem - Free Packets On Lookasidee                 Listse  A     If nonpaged pool is constantly expanding, use the System Dumpt@     Analyzer (SDA) in an attempt to determine what types of data'     structures are consuming the space.s         Example:         $ ANALYZE/SYSTEMC         SDA> SET OUTPUT <filename>   ! Direct output to a data filelD         SDA> SHOW POOL/SUMMARY       ! Write information to the file@         SDA> SET OUTPUT TT:          ! Redirect output to screen         SDA> EXITS         Note:uI         Symbols appearing in this listing are defined in another database          article.  D              [OpenVMS] What Do SDA's SHOW POOL/SUMMARY Symbols Mean?  E     Once it has been determined what structures are occupying all thepC     space, any structures which are taking up too much space can bekH     investigated.  For example, the WCB (Window Control Block) structureH     increases as files get more fragmented.  If this structure is takingG     up too much pool space, you may need to compress your disk by doingo      an IMAGE BACKUP and RESTORE.     11) CHECK FOR HEAVY DIRECT I/O  A     Direct I/O performance is one of the main contributors to thed?     overall efficiency of your system.  Direct I/O is typicallyoB     attributed to disk and tape devices and is deemed "Direct I/O"C     because of the direct transfer of data between the users bufferiC     and the device, i.e., little or no non-paged pool buffering, orh!     CPU intervention is required.   F     In evaluating system performance, disk I/O will be the main focus.  F     A poorly managed I/O subsystem can degrade the use of both the CPUF     and memory resource.  If disk data is allowed to become fragmentedD     CPU power is consumed compensating for the fragmented I/O, whichC     robs users of CPU power.  Bottlenecks in the I/O subsystem alsohE     wastes CPU power as users wait for I/O completion before they can C     become computable.  These same bottlenecks may also inhibit the #     efficient management of memory.   C     Traditional methods for analyzing direct I/O performance centerRD     around monitoring the number and types of I/O to a given device.A     Given the wide variation of acceptable I/O rates for devices,e>     i.e., from 20-25 for the RA81 and 140-144 for the RRD44, a@     simpler measurement would be to determine if I/O's must wait     to be processed.  C     The command MONITOR DISK/ITEM=QUEUE can be used to determine if G     disk I/O to a specific device is affecting the systems performance.dD     This display shows I/O's that the device couldn't handle because%     it was processing prior requests.e  G     The following should be investigated if any disk has an "AVE" valuef     of 1 or higher:n  A      a. Use the command MONITOR PROCESS/TOPDIO to determine which A         processes are generating the most direct I/O.  If they're A         accessing the disk in question, attempt to relocate their $         files to less active device.  D      b. Use the SHOW DEVICE/FILES <devname> to determine which files         are being accessed.   C         - If the device contains system files, i.e., page, swap, oro;           log files, relocate them to a less active device.              Note:oB             If activity to a page, swap, or log file is excessive,?             address that limitation prior to correcting any I/OH             limitations.  F        - If the device contains application data, the methods used for2          accessing this data may require analysis.  D     Other areas impacting disk I/O performance are fragmentation and     caching.  D     1. Use the MONITOR IO command and check the SPLIT TRANSFER RATE.F        Split transfers are due to file fragmentation and the inabilityG        to complete the I/O from a single file extent.  Additional I/O's E        are required to account for the fragmentation.  The acceptable          Split Transfer Rate is 5.  B        Alleviate fragmentation with regularly scheduled backup and        restore operations.            Note:A            SCSI disk class drivers may limit the size of the disk,D            transfer.  Large split I/O rates on SCSI based disks used@            for paging, or containing applications which do large?            transfers, and may not be due to file fragmentation.r  D    2. Use the MONITOR FCP command to determine the Window Turn Rate.B       Window turn occur when more retrieval pointers for an activeB       open file need to read.  This may also be indicative of fileF       fragmentation.  A Window Turn Rate in excess of 6 or more should       be investigated.  E       - If file fragmentation  is  a problem, compress the disks withP$         an IMAGE BACKUP and RESTORE.             Note: D             Open files are ignored by Disk compression utilities and?             may never get compressed.  This may contribute to a #             fragmentation  problem.e  E      - Contiguous files larger than 458745 blocks, on a disk with thesG        default number of mapping pointers per window, 7, may also causeT        a high Window Turn Rate.o  @        This can be prevented by increasing the number of mappingB        pointers in the window.  These can be increased to the size@        of the file in blocks, divided by 65000, on a system-wide2        basis, disk-by-disk, or for specific files.          System-Wide:cE          Set the SYSGEN parameter ACP_WINDOW to the number of mappingiE          pointers desired per window.  This change should be added tohF          MODPARAMS.DAT and AUTOGEN run to adjust the size of non-paged          pool.          Disk-by-Disk:D          Include the /WINDOW=n qualifier to the MOUNT command of theC          disk.  This can be added to the file used for mounting theNE          disk at startup, or dynamically with the SET VOLUME/WINDOW=n           command.e          Specific Files:E          Set FAB$B_RTV to the desired number of mapping pointers whenTD          opening the file for access (see the "VMS Record Management/          Services Reference Manual." for more).O  @    3. Use the MONITOR FILE_SYSTEM_CACHE command to determine the@       effectiveness of the file system cache.  If the caches areA       ineffective, delays occur whenever the disk is accessed forl?       more information.  The cache is considered ineffective if B       the "Hit %" is lower than 80, with an "Attempt Rate" greater>       than, or equal to 1 per second (using the "AVE" column).  
         Note:sE           Ignore any cache which averages under 1 attempt per second.   B       If one or more of the caches is deemed ineffective, increase-       the related ACP_cache SYSGEN parameter.r           Example:B           In order to increase the effectiveness of the "File Hdr"A           cache, increase the SYSGEN parameter ACP_HDRCACHE.  See C           the "Guide to OpenVMS Performance Management", Section 5, C           for a complete SYSGEN parameter to ACP cache association.c  A       Add any parameter changes to MODPARAMS.DAT and run AUTOGEN.r  D       It's also possible that file system caches failed to allocatedC       at system startup.  This can be determined by issuing the DCLeA       command SHOW DEVICE/FULL <disk-name> and checking the fieldaE       "Maximum buffers in FCP Cache".  This field shows the number of F       buffers currently allocated for the cache.  If this value is 14,B       there was insufficient PAGEDYN to allocate the entire cache.A       If this has occurred the SYSGEN parameter PAGEDYN should beeC       increased, even if there's an abundance of free paged dynamics
       memory.g  
         Note:iD           Current values for paged dynamic memory may be viewed with0           the DCL command SHOW MEMORY/POOL/FULL.  D    4. Use the command SHOW MEMORY/CACHE/FULL to determine if VirtualD       I/O Cache can be enabled, or enhanced, in an attempt to reduce1       the I/O rates on frequently accessed files.o         Reference Article:C         [OpenVMS] How to Interpret Info From SHOW MEMORY/CACHE/FULLO                   on AlphaC         [OpenVMS] How to Interpret Info From SHOW MEMORY/CACHE/FULLU                   on VAX  D    5. Systems in a cluster sharing disks increase the possibility ofB       I/O bottlenecks.  To determine I/O rates for disks availableB       cluster wide, use the MONITOR CLUSTER command.  This displayC       sums the I/O from all cluster nodes to provide an overall I/Oe       rate for the disks.C  
         Note:aA           The disk farm on most clusters is large and the MONITORnA           CLUSTER display only shows the 6 disks with the highestuD           I/O rate.  To see the I/O rate for all drives in a cluster@           use the following commands to collect MONITOR data and           create an ASCII file:s  8               $ MONITOR/NODISPLAY/RECORD=<FILEA> CLUSTERG               $ MONITOR/NODISPLAY/INPUT=<FILEA>/SUMMARY=<FILEB> CLUSTER   E           Be aware that using the /RECORD qualifier can produce large D           files.  Statistics gathered on a 7 node cluster, with 200+D           disks, for 10 minutes, can produce files in excess of 6000?           blocks.  See the "OpenVMS System Management UtilitiesnF           Reference Manual", section 15, for information regarding the           MONITOR utility.  C       Consider the following to distribute the I/O load and improvex0       throughput for drives with high I/O rates:  A       - Distribute system and user files across several disks and.         HSC requestors.   D       - Create bound volume sets, which help distribute the I/O load         across multiple disks.  F       - If the operations to a disk are mostly reads, Volume Shadowing          may improve performance.  F       - Multiple nodes sharing the same system disk can reduce cluster9         performance if the system disk becomes saturated.   E       - Move Page and swapfiles to non-system disks to reduce the I/OC
         load.S           Reference Article:E           [OpenVMS] How To Move Satellite Page/Swap Files From System &                     Disk To Local Disk     12) CHECK FOR SWAPPING  ?     Use the DCL command "SHOW SYSTEM" or "SHOW MEMORY/SLOTS" toa0     determine if processes have been outswapped.         Example:         $ SHOW MEMORY/SLOTS A                System Memory Resources on 31-JUL-1997 11:29:08.37"=         Slot Usage (slots):   Total   Free  Resident  SwappedaA           Process Entry Slots    70     45        24        1 <-+0A           Balance Set Slots      63     41        22        0   |eA                                                                 |rA           Note:                                                 | A             Both commands show an outswapped process.  ---------+kA                                                                 |.A         $ SHOW SYSTEM                                           | A             OpenVMS V6.2  on a node  31-JUL-1997 11:31:14.60    |.A         Pid    Process Name State Pri  I/O       CPU            |rA         00000081 SWAPPER      HIB    16    0   0 00:00:15.04    | A                    .                 .            .             |aA                    .                 .            .             |oA         0000008F EVL          HIB     6   49   0 00:00:00.48    | A         00000090 REMACP       HIBO    8    --swapped out--  <---+u  ;     Processes are outswapped by OpenVMS for 1 of 3 reasons:s  6       1. Insufficient memory for the current workload.A       2. Insufficient balance set slots for the current workload. >       3. Proactive memory management determines that processes          need to be outswapped.E  <     Swapping is a function of the Memory Management piece of<     OpenVMS, which attempts to ensure the efficient use of a?     systems physical memory in relationship to the requirementsr=     placed on it by the users, applications, and system code. >     The thresholds used to define this relationship are driven?     by the requirements of the operating system and the demands      of the user community.  >     When the current demands on memory resources can no longer;     be managed within memory's physical boundaries, or user @     defined thresholds are reached, Memory Management will begin     to outswap processes.e  ?     Swapping processes out of physical memory isn't necessarilye<     bad.  It should be investigated if the Ave "Inswap Rate"<     of the MONITOR IO display is greater than 1.  Outswapped;     process' are treated like any other process and will bes;     inswapped when they become computable.  However, once a @     process has been outswapped, it will remain outswapped until?     it has work to do and becomes computable.  The process willc;     remain outswapped, even if there's an abundance of freeu     memory and balance slots.e       Reference Article:@       [OpenVMS] Why Processes Are Swapped Out Of Physical Memory    " 13) CHECK FOR PAGED POOL DEPLETION  F     Paged pool contains data structures used by multiple processes butD     not required to be permanently memory-resident.  It contains theA     shareable logical name table, XQP caches, access control list ?     elements, and global section descriptors to name but a few.   E     Performance impacts caused by the depletion of paged pool are the C     degradation in I/O processing due to reduced XQP caches, or the D     inability of users to login because logical name tables can't be     created.  C     To determine if the depletion of paged pool is effecting system 7     performance, use the command SHOW MEMORY/POOL/FULL.W  I     If "Free Space (bytes)" is less than 20% of "Current Size (PAGEDYN)",uC     or the "Size of Largest Block" is less than 20K bytes, then then3     consumption of paged pool needs to be analyzed.i       Reference Article:<       [OpenVMS] Insufficient Dynamic Memory Errors (INSFMEM)  F     Use AUTOGEN with FEEDBACK to modify the PAGEDYN parameter.  EnsureG     that AUTOGEN's input file, SYS$SYSTEM:MODPARAMS.DAT doesn't containtB     an absolute definition for PAGEDYN.  A MIN_ value based on the     following may be included:  5        MIN_PAGEDYN = CUR_PAGEDYN+((CUR_PAGEDYN/10)*2)   C     If paged pool is constantly being depleted, use the System DumpO@     Analyzer (SDA) in an attempt to determine what types of data'     structures are consuming the space.          Example:          $ ANALYZE/SYSTEM E          SDA> SET OUTPUT <filename>   ! Direct output to a data file.mE          SDA> SHOW POOL/SUMMARY       ! Write information to the filerA          SDA> SET OUTPUT TT:          ! Redirect output to screene          SDA> EXIT         Note: @         Symbols appearing in this listing are defined in another         database article.r  A           [OpenVMS] What Do SDA's SHOW POOL/SUMMARY Symbols Mean?n  E     Once it has been determined what structures are occupying all therC     space, any structures which are taking up too much space can beu     investigated.M    0 14) CHECK FOR AUTOMATIC WORKING SET DECREMENTING  D     To determine if Automatic Working Set Decrementing is enabled onB     your system, check the SYSGEN parameters 'PFRATL' and 'WSDEC'.D     If both parameters are set to non-zero values, Automatic Working"     Set Decrementing is turned on.  E     Automatic Working Set Decrementing removes working set pages fromtB     processes that are Page Faulting less than PFRATL.  This oftenB     induces more Page Faulting and can degrade system performance.F     For example, if several SHOW SYSTEM displays indicate that workingF     sets are oscillating (e.g., 'Ph.Mem'" keeps rising and falling forE     many processes), but there is always plenty of memory on the Free G     List, then Automatic Working Set Decrementing could be slowing downL     your system.  F     Automatic Working Set Decrementing should be turned OFF unless youB     know that your system benefits from it.  If you have AutomaticF     Working Set Decrementing turned ON because it was once beneficial,C     you might want to reevaluate its current benefit by testing the F     system for a period of time with it turned OFF.  For most systems,G     this feature decreases system performance rather than increases it.a  H     To turn OFF Automatic Working Set Decrementing, the SYSGEN parameterH     'PFRATL' should be set to 0.  This is a dynamic parameter and can beG     changed on a live system.  If changing PFRATL improves performance,rF     be sure to change this parameter in the SYSGEN CURRENT database soE     the new value will be retained after the next reboot.  You shouldpE     also add this parameter to SYS$SYSTEM:MODPARAMS.DAT so it will ben     retained by AUTOGEN.  E     For more information on Automatic Working Set Decrementing, refernA     to the "Guide to VMS Performance Management", Sections 2.2.1,      4.2.1.7, 5.2.7 and 5.2.8.P         Note: G         Some layered products automatically set the parameters 'PFRATL' ?         and 'WSDEC' in the file SYS$SYSTEM:MODPARAMS.DAT during          installation.e      15) CHECK FOR HEAVY BUFFERED I/O  B     Buffered I/O involves a data transfer between user space and a?     system space buffer in nonpaged pool.  A higher than normalDB     buffered I/O rate will consume nonpaged pool and CPU resources  5     Buffered I/O activity is typically attributed to:E  !          - Communications devicesR          - Line printers          - Graphic devices#          - Instrumentation monitorsi%          - Terminal Emulation Devices           - Mailbox I/O          - Office applications  H     To determine the systems overall buffered I/O rate issue the command     "MONITOR IO".e  F     The best way to determine if the system has a "HEAVY" buffered I/OE     rate is by comparing the current rate with those experienced whenTE     the system's performance wasn't in question. You can also comparee-     the current rate with (CPU_FACTOR x 100).          Note:eH         A CPU_FACTOR table has been included at the end of this article.  =     The MONITOR PROCESS/TOPBIO command can be used to display .     users with the highest buffered I/O rates.     16) CHECK PROCESSOR MODES   B     The time a CPU spends in a given mode (Kernel, Super, Exec, orF     User), or on the interrupt stack, may be indicative of the overallD     performance health of your system.  Use the MONITOR MODE commandD     to determine if your processor is spending excessive time in anyF     one mode.  Use the "AVE" column for a basic assessment of the time     spent in a given mode.  H     The numbers given below are typical numbers for general timesharing,F     engineering/scientific, and commercial (I/O, Database, or ALL-IN-1     intensive) environments.  7                               Kernel  Super  Exec  Usere8       Engineering/Scientific:   10%-    1%     3%   80%+8          General Timesharing:   25%     3%     8%   50%+8                   Commercial:   38%+    1%    10%   40%-  G     However, the best way to determine the CPU mode statistics for your H     environment is by comparing the current rates with those experienced=     when the system's performance was at an acceptable level.R  D     Following are examples and basic explanations for CPU modes in a$     typical timesharing environment:       *  INTERRUPT STACK  D        The time the processor spends responding to interrupts. If itE        averages more than 15%, it could indicate possible high device H        interrupts, often from character interrupt devices such as DZ11s.E        If it is consistently very high (over 70%) it could indicate a <        faulty device continually interrupting the processor.  F        Other things to look for with high interrupt stack time includeC        SCS cluster traffic, DLOCK (Distributed Lock Management) andm        LAVC disk serving.r            Note:D            Often in NI and MI clusters, high interrupt stack time isC            directly proportional to the amount of disk serving on a:C            given node.  Keeping I/O intensive applications on nodes D            with direct access to the applications disks is often the            best solution.        *  MP SYNCHRONIZATIONn  G        The time in which a multiprocessing system experiences acquiringmG        spinlocks.  OpenVMS uses spinlocks to synchronize access to data C        structures shared by the CPUs in a Symmetric Multiprocessing         (SMP) environment.           Reference Article:SD          [OpenVMS] Excessive Amounts Of "MP Synchronization" Time On                    SMP Systemd       *  KERNEL MODE  @        The time the processor spends in system functions such asE        system services, handling page faults, file processing, DECnet.@        processing, handling local lock management and setting up        physical I/O to devices.i  F        File fragmentation can also cause high KERNEL mode time becauseD        I/O operations must be split into multiple requests to accessD        the fragmented pieces of the file. This is most noticeable on        slower processors.s  C        A KERNEL mode time over 25% indicates a possible problem and         should be investigated.            Note:E            Some applications such as ALL-IN-1 often cause KERNEL modecG            times to be greater than 25%, because their services executeyB            in that mode.  These cases are not a cause for concern.  @        INTERRUPT STACK time and KERNEL mode time together should/        average under 40% of the total CPU time.O            CAUTION:iG            Running BACKUP during prime time can greatly degrade overalliC            system performance.  BACKUP can take over 50% of the CPUr'            time, mostly in KERNEL mode.e       *  EXECUTIVE MODEi  D        The time the processor spends in RMS activity, often directly        related to file design.       *  SUPERVISOR MODEH         The time the processor spends in DCL functions.  This is usuallyG        a small amount of time, unless you are heavily using DCL command 0        procedures, such as a DCL menu interface.  H        If SUPERVISOR mode is over 15%, you might consider rewriting some6        of your command procedures as programs instead.            Note:D            Some third-party applications run in SUPERVISOR mode.  InI            these cases, elevated SUPERVISOR mode is normal.  For example, G            earlier versions of the ORACLE [R] product run in SUPERVISORn            mode (5-Apr-1991).        *  USER MODE  D        The time spent running user programs.  This should be as high        as possible.b       *  IDLE TIME  E        The time spent in the NULL process; "unused" CPU time, when no '        process is ready to use the CPU.s     17) CHECK DECnet ACTIVITYl  D     Use the MONITOR DECnet command to examine packet traffic. Add up(     the following from the "AVE" column:  #       a. Arriving Local Packet Ratee$       b. Departing Local Packet Rate#       c. Arriving Trans Packet Ratee  B     If packet traffic is greater than the results from the formulaD     (CPU_FACTOR x 100), there's a possibility that 30% of the CPU is"     being used for communications.         Note: E         A table containing the CPU_FACTOR for most CPU configurations /         is included at the end of this article.O  E     The number of packets observed in the MONITOR display is entirely 9     dependent on the operating environment of the system:   E     - Heavy DECnet traffic should be expected on systems operating asT0       a "server" in a client-server environment.  D     - Configuring a system for routing increases packet traffic. TheE       packet traffic can be decreased using a router, e.g., DECNIS or        RouteAbout.   H     - DECnet buffer configurations can effect packet traffic. By defaultF       DECnet configures the receive buffer size to be the maximum thatG       the device can handle.  However, these values can be modified and &       may be affecting packet traffic.         Reference Article:<         The following article is in the DECNET-VMS database.  H           [DECnet-VAX] Setting DECnet Executor Pipeline Quota, with Case                        Studies  A     - Communication errors may be impacting performance.  Use theF9       following command to check for "Response timeouts":   $          NCP> SHOW EXECUTOR COUNTERS  A       If these errors are being logged it indicates that data was G       transmitted but not acknowledgement.  When this occurs the system1B       must retransmit the data, which consumes CPU power.  InitialH       indications will typically be complaints of slow network response.  G       If "Response timeouts" are being logged and network response timeeE       is affected, troubleshoot the network to determine the cause ofd       the lost packets.   C     If it's believed that network activity is impacting the systems0)     performance, contact network support.e    & 18) CHECK DISTRIBUTED LOCKING ACTIVITY  B     In most computing environments there is a requirement to shareA     resources.  Multiple processes may be required to access, andi>     possibly update, the same database, or file.  To avoid theC     concurrent manipulation of shared resources, hence avoiding the C     likelihood data corruption, a synchronization technique lockingeF     shared resources to specific processes is incorporated in OpenVMS.  A     This synchronization technique is central to the operation ofRD     VMSClusters.  All nodes participate in ensuring the integrity ofE     cluster data through the "Distributed Lock Manager".  This allows C     nodes to coordinate access to resources by allowing any node tof-     serve as the master for a given resource.   F     Locks can be defined on entities such as global sections, volumes,H     files, or records within a file, to name a few.  Locks may be uniqueB     (Root Lock), or associated to an existing lock (Sublock).  TheA     combination of Parent and it's associated sublocks comprise ae     "Resource Tree".  D     In a VMSCluster environment the first node requesting a resourceD     will initially be the resource master.  However, lock mastershipG     for the "Resource Tree" may transition to other nodes, based on the E     setting of certain SYSGEN parameters and the locking activity forFE     the locks in the tree.  This node to node transition of a tree ish7     commonly referred to as "Dynamic Lock Remastering".o  G     If managed incorrectly distributed locking significantly impact theMH     performance of a node, hence degrading the performance of the entire     cluster.  5     Basic rules of thumb for Distributed Locking are:s  A     - The fastest/largest nodes in a cluster should master all ofe       the locks in a cluster:     - Satellite nodes shouldn't be allowed to master locks  1     Parameters Used For Dynamic Lock Remastering:a       - PE1 (Dynamic)t
       <Value> 9         %xFFFFFFFF = Don't remaster trees to other nodes. >                <#> = Only remaster trees containing fewer than"                      <val> #locks.+                  0 = Remaster any size trees       - LOCKDIRWT (Non-dynamic) I          a) Nodes with a higher LOCKDIRWT will be the master of competingcE             locks, i.e., satellites should have this parameter set to 4             zero while boot nodes should be non-zeroA          b) Nodes with equal LOCKDIRWT values use a lock activityr.             algorithm to determine mastership.  B     Distributed locking is suspected of having an impact on systemJ     performance if "Send Credit Waits", transfers waiting on send credits,I     are greater than 10 per second with the following, (variables for theF0     algorithm are derived from "MONITOR DLOCK"):  *                   (In+Out "New ENQ  Rate")0                 + (In+Out "Converted ENQ  Rate")0                 --------------------------------'                        Greater than 100B         Note: B         The number of  "Send Credit Waits" may be determined usingC         the following commands, subtracting the differences between G         intervals and dividing this difference by the number of seconds          per interval:s  *             $ SHOW CLUSTER/CONT/INTERVAL=5             ADD CR_WAITS  C     Processes in RWSCS with a high "outgoing" lock rate, as derivedtF     from MONITOR DLOCK fields, are also indicative of a "remote" nodes6     inability to handle its incoming locking activity:  +                   ("Outgoing New ENQ Rate") 1                 + ("Outgoing Converted ENQ Rate") 1                 ---------------------------------r(                          Greater than 50  E     Monitoring the locking activity of the other cluster nodes should )     reveal the suspect node (see note 1).r  C     Processes in RWCLU, when no nodes have recently entered or leftoG     the cluster, is indicative of lock remastering and another possiblePA     indicator of problems.  However, this is only considered whensD     processes are hung in this state for long periods of time, i.e.,C     longer than 3-5 minutes.  Locks to be remastered are queued andi     handled every 5-8 seconds.  
       Note 1:tI         The simple existence of processes in the RWCLU and RWSCS resourceoI         wait states in and of themselves is not indicative of performancetJ         problems.  Processes are placed in, and removed from, these statesF         many times during normal cluster activity.  They're only to beE         used as a possible indication of problems in conjunction withh,         those symptoms discussed previously.     SUMMARY:  @ For a more detailed analysis of your systems performance use theB "OpenVMS Performance Management" manual, or a performance analysis> application like "POLYCENTER Performance Advisor for OpenVMS".  > The following article may also be of assistance in the future:  B    [OpenVMS] Tuning an OpenVMS System After Adding/Removing Memory     CPU_FACTOR TABLES:  G The CPU_FACTOR variable is an unofficial, gross estimation of a systems H resource potential.  The variable is only meant for use in this article.  =   NO BENCHMARK STUDY WAS CONDUCTED TO DETERMINE THEIR VALUES!   E The CPU_FACTOR tables contain values for a majority of the single CPUMC system running OpenVMS.  To determine the CPU_FACTOR for single CPUhH configurations, use the numeric portion of the output from the followingC command in the tables below, i.e., a "DEC 7000 Model 610" is in thee  Alpha systems table as 7000-610:  *     $ WRITE SYS$OUTPUT F$GETSYI("HW_NAME")  C For multi-CPU configurations, use the output from the above commandoG and search the tables for the single CPU version of your configuration.r  
   Example:H     The "7000-610" is the single CPU version for a "DEC 7000 Model 640".  = Use this CPU_FACTOR in the following command to determine theOD CPU_FACTOR for the multi processor.  Replace the "FAC" variable withF the CPU_FACTOR from the table and "CPU" with the number of CPUs in the multi processor:  3      $ CPU_FACTOR = FAC+((((FAC/10)/2)*16)*(CPU-1))r      $ SHOW SYMBOL CPU_FACTORa      Example:SC      Determining the CPU_FACTOR for a "DEC 7000 Model 640", a 4 CPUs5      multi processor with a single CPU_FACTOR of 132.O  4         $ CPU_FACTOR = 132+((((132/10)/2)*16)*(4-1))          $ SHOW SYMBOL CPU_FACTOR         CPU_FACTOR = 420    "                       VAX Systems:3      +------------+-------+  +------------+-------+o3      | HW_        |CPU_   |  | HW_        |CPU_   |M3      |     Name   | FACTOR|  |     Name   | FACTOR|C3      +------------+-------+  +------------+-------+t3      | 3100-M76   |     5 |  | 3100/SPX   |     3 |e3      | 3100       |     2 |  | 3100-30/40 |     2 | 3      | 3100-80    |     8 |  | 3100-85    |    15 |.3      | 3100-90    |    19 |  | 3100-95    |    27 |b3      | 3400       |     2 |  | 3600       |     2 |z3      | 3900       |     3 |  | 4000 VLC   |     5 |13      | 4000-30    |     1 |  | 4000-60    |    10 | 3      | 4000-90    |    19 |  | 4000-90A   |    24 |G3      | 4000-100   |    19 |  | 4000-105A  |    27 | 3      | 4000-200   |     4 |  | 4000-300   |     6 |R3      | 4000-400   |    13 |  | 4000-500   |    19 |o3      | 4000-600   |    25 |  | 4000-700A  |    33 |e3      | 4000-705A  |    37 |  | 6000-610   |    23 |p3      | 6000-210   |     2 |  | 6000-310   |     3 | 3      | 6000-410   |     5 |  | 6000-510   |    11 | 3      | 7000-600   |    25 |  | 7000-610   |    25 |i3      | 7000-700   |    43 |  | 7000-710   |    43 |l3      | 7000-810   |    52 |  | 8250       |     1 |D3      | 8500       |     3 |  | 8530       |     3 |o3      | 8550       |     4 |  | 8600       |     3 | 3      | 8650       |     4 |  | 8700       |     4 |t3      | 8800       |     4 |  | 8810       |     4 |)3      | 9000-110   |    32 |  | 9000-210   |    30 |t3      | 9000-310   |    32 |  |10000-610   |    25 | 3      +--------- --+-------+  +------------+-------+l  !                    Alpha Systems:l3      +------------+-------+  +------------+-------+r3      | HW_        |CPU_   |  | HW_        |CPU_   | 3      |     Name   | FACTOR|  |     Name   | FACTOR| 3      +------------+-------+  +------------+-------+n3      |  200 4/100 |    54 |  |  200  4/133|    74 | 3      |  200 4/166 |   116 |  |  200  4/233|   113 |A3      |  200 4/266 |   198 |  |  200  4/300|   215 |h3      |  250 4/133 |    74 |  |  250  4/166|   116 |s3      |  250 4/200 |   131 |  |  250  4/233|   131 | 3      |  250 4/266 |   198 |  |  250  4/300|   215 |o3      |  255 4/133 |    74 |  |  255  4/166|   116 |r3      |  255 4/200 |   131 |  |  255  4/233|   180 |c3      |  255 4/266 |   198 |  |  255  4/300|   215 |o3      |  400 4/166 |   116 |  |  400  4/233|   161 | 3      |  400 4/300 |   215 |  |  500  5/266|   329 | 3      |  500 5/300 |   319 |  |  500  5/333|   389 |i3      |  600 5/333 |   412 |  |  600  5/300|   337 | 3      |  600 5/266 |   329 |  | 1000  4/200|   135 |r3      | 1000 4/233 |   165 |  | 1000A 4/266|   197 |b3      | 1000 5/333 |   389 |  | 2000  4/200|   131 |i3      | 2000 4/275 |   202 |  | 2000  5/250|   277 |e3      | 2000 4/233 |   177 |  | 2000  5/300|   319 |r3      | 2000-300   |    80 |  | 2000-500   |    81 |o3      | 2100 4/200 |   131 |  | 2100  4/233|   177 |h3      | 2100 5/300 |   319 |  | 2100  4/275|   202 |l3      | 2100 5/250 |   277 |  | 3000-300   |    66 | 3      | 3000-300L  |    45 |  | 3000-300LX |    68 |u3      | 3000-300x  |    90 |  | 3000-400   |    74 |a3      | 3000-500X  |   110 |  | 3000-500   |    84 |l3      | 3000-600   |   114 |  | 3000-700   |   162 | 3      | 3000-800   |   138 |  | 3000-900   |   200 | 3      | 4000-610   |    94 |  | 4000-710   |   122 | 3      | 7000-610   |   132 |  | 7000-710   |   200 |m3      | 8200 5/300 |   341 |  | 8200 5/350 |   432 |c3      | 8400 5/300 |   341 |  | 8400 5/350 |   432 |t3      |10000-610   |   132 |  |            |       |n3      +------------+-------+  +------------+-------+o     RELATED ARTICLES:I  E The following articles have been referenced throughout this document,=? the majority of which may be found in the OPENVMS or DECNET-VMSvE database.  The titles displayed represents the title text at the times7 this article was written and may change without notice.e  @   [OpenVMS] Reasons for RWMPB/RWMPE States and PAGEFRAG/PAGECRIT             Messages2   [OpenVMS] How to Troubleshoot a Process in RWNPG2   [OpenVMS] How to Troubleshoot a Process in RWPAG2   [OpenVMS] How to Troubleshoot a Process in RWMBX8   [OpenVMS] How to Troubleshoot a Process in RWCSV State8   [OpenVMS] How to Troubleshoot a Process in MUTEX StateB   [OpenVMS] How To Troubleshoot A Process In RWAST On VAX or Alpha.   [OpenVMS] How To Troubleshoot a Hung Process<   [OpenVMS] Why Processes Are Swapped Out Of Physical MemoryA   [OpenVMS] How To Determine PAGEFILE and SWAPFILE Usage From SDA A   [OpenVMS] Managing Dumpfiles on VAX & Alpha Systems or Clustersi>   [OpenVMS] How To Create Secondary Page/Swap Files and Remove             Primaries E   [OpenVMS] How To Move Satellite Page/Swap Files From System Disk Toh             Local DiskE   [OpenVMS] VIRTUALPAGECNT, PGFLQUO, PAGEFILE:  How Are They Related?t>   [OpenVMS] Monitoring Page And Swap File Usage From A Command             ProcedureI?   [OpenVMS] What Is The Maximum Size For An Installed Pagefile?eG   [OpenVMS] Adaptive Pool Management: A Description of Nonpaged Dynamice             Memory=   [OpenVMS] NPAGEDYN Fragmented as a Result of LISTPREPOP.DATf7   [OpenVMS] Excessive NPAGEDYN Expansion on OpenVMS VAXsC   [OpenVMS] V6.n Pool Expansion Problem - Free Packets On Lookasideu             Lists 8   [OpenVMS] Methods Used To Recover Space On System DiskA   [OpenVMS] How to Read Mailbox, MBAn:, Data Without Removing thes             Messages9   [OpenVMS] What Do SDA's SHOW POOL/SUMMARY Symbols Mean?o8   [OpenVMS] Insufficient Dynamic Memory Errors (INSFMEM)=   [OpenVMS] Details On How Proactive Memory Reclamation WorksOF   [OpenVMS] How to Interpret Info From SHOW MEMORY/CACHE/FULL on AlphaD   [OpenVMS] How to Interpret Info From SHOW MEMORY/CACHE/FULL on VAXA   [OpenVMS] Excessive Amounts Of "MP Synchronization" Time On SMP.             System@   [OpenVMS] Memory Reclamation From The Virtual I/O Cache (VIOC)B   [OpenVMS] Discussion Of Processes In The RWxxx Scheduling StatesF   [OpenVMS] Process Class Scheduling Anomolies ($SCHED system service)@   [DECnet-VAX] Setting DECnet Executor Pipeline Quota, with Case                Studies       SEARCH/QUERY WORDS:    CHEAT_SHEET_COOKBOOK IMP_ARTm COMP_ART     REFERENCES:e  / "OpenVMS Performance Management", (AA-R237A-TE)   - "Volume Shadowing for OpenVMS", (AA-PVXMD-TE)w  1 "OpenVMS Guide to System Security", (AA-Q2HLC-TE)o  < "VMS Internals and Data Structures, V5.2", (EY-C171E-DP-ECG)  @ "OpenVMS AXP Internals and Data Structures, V1.5", (EY-Q770E-DP)  B "OpenVMS Alpha System Dump Analyzer Utility Manual", (AA-PV6UC-TE)  @ "OpenVMS VAX System Dump Analyzer Utility Manual", (AA-PV6TB-TE)  2 "OpenVMS Version 7.1 Release Notes", (AA-QSBTB-TE)  < "OpenVMS System Management Utilities Reference Manual: A-L",  (AA-PV5PD-TK)  < "OpenVMS System Management Utilities Reference Manual: M-Z",  (AA-PV5QD-TK)  A "OpenVMS System Manager's Manual: Tuning, Monitoring, and Complext  Systems), (AA-PV5ND-TK)  ; [R] ORACLE is a registered trademark of Oracle Corporation.t   Alex   ------------------------------  % Date: Sat, 06 Nov 2004 14:50:43 +0100E3 From: Michael Unger <spam.to.unger@spamgourmet.com>i Subject: Re: Performance TuningV+ Message-ID: <2v44kqF2hapifU1@uni-berlin.de>e  * On 2004-11-06 13:50, "Alex Daniels" wrote:  M > There is one. The Cookbook of Performance Slowdown, VAX and Alpha, V6.0 and  > Up.... >  > Alex > M > Copyright (c) 1997, 2001 Compaq Computer Corporation.  All rights reserved.c > 8 > PRODUCT:    Compaq OpenVMS VAX, Versions 6.0 and above: >             Compaq OpenVMS Alpha, Versions 6.1 and above >  > COMPONENT:  Performancei > ) > SOURCE:     Compaq Computer Corporation  >  > [...]" > 
 > BACKGROUND:n > D > Occasionally OpenVMS systems may experience performance slowdowns.E > The performance degradation is typically due to requirements placed E > on one or more of a system's main resources, i.e., CPU, memory, and E > the I/O subsystem.  This article describes basic techniques to help 5 > determine the cause of the performance degradation.d >  > [...]   C Why doesn't HP make such articles available in the "normal" OpenVMS D documentation set, e.g., "Documents Supplements" section? (There hasD been a document called "Getting the most out of your Processor" some1 time ago; I don't know if it is still available.)N   Michael    -- s; Real names enhance the probability of getting real answers. 5 My e-mail account at DECUS Munich is no longer valid.h   ------------------------------  $ Date: Sat, 6 Nov 2004 14:35:26 -00006 From: "Alex Daniels" <AlexNoSpamDaniels@themail.co.uk> Subject: Re: Performance Tuningu6 Message-ID: <418ce12c$0$27536$db0fefd9@news.zen.co.uk>  @ "Michael Unger" <spam.to.unger@spamgourmet.com> wrote in message% news:2v44kqF2hapifU1@uni-berlin.de...a <SNIP> >(There hasdF > been a document called "Getting the most out of your Processor" some3 > time ago; I don't know if it is still available.)n >a   It is still available.  2 http://h71000.www7.hp.com/doc/73final/sup/esi.html   Alex   ------------------------------  $ Date: Sat, 6 Nov 2004 11:17:36 -0500' From: "Main, Kerry" <kerry.main@hp.com>  Subject: RE: Performance TuninguR Message-ID: <FD827B33AB0D9C4E92EACEEFEE2BA2FB4A43ED@tayexc19.americas.cpqcorp.net>   > -----Original Message-----? > From: Michael Unger [mailto:spam.to.unger@spamgourmet.com]=20   > Sent: November 6, 2004 8:51 AM > To: Info-VAX@Mvb.Saic.ComF! > Subject: Re: Performance Tuning  >=20, > On 2004-11-06 13:50, "Alex Daniels" wrote: >=20B > > There is one. The Cookbook of Performance Slowdown, VAX and=20 > Alpha, V6.0 ands
 > > Up.... > >=20 > > Alex > >=20A > > Copyright (c) 1997, 2001 Compaq Computer Corporation.  All=20o > rights reserved. > >=20: > > PRODUCT:    Compaq OpenVMS VAX, Versions 6.0 and above< > >             Compaq OpenVMS Alpha, Versions 6.1 and above > >=20 > > COMPONENT:  Performancet > >=20+ > > SOURCE:     Compaq Computer Corporationa > >=20	 > > [...]n > >=20 > > BACKGROUND:  > >=20F > > Occasionally OpenVMS systems may experience performance slowdowns.G > > The performance degradation is typically due to requirements placed G > > on one or more of a system's main resources, i.e., CPU, memory, and G > > the I/O subsystem.  This article describes basic techniques to help 7 > > determine the cause of the performance degradation.0 > >=20	 > > [...], >=20E > Why doesn't HP make such articles available in the "normal" OpenVMStF > documentation set, e.g., "Documents Supplements" section? (There hasF > been a document called "Getting the most out of your Processor" some3 > time ago; I don't know if it is still available.)a >=20	 > Michael  >=20  1 Re: some additional performance on OpenVMS doc's:i  
 Reference:  H HP OpenVMS v7.3-2 System Manager's Manual, Volume 2: Tuning, Monitoring, and Complex SystemsmB http://h71000.www7.hp.com/doc/732FINAL/aa-pv5nh-tk/aa-pv5nh-tk.PDF  * OpenVMS Performance Management (V73 guide)H http://h71000.www7.hp.com/doc/73final/documentation/pdf/OVMS_73_perf_man g.PDFu  ' Getting the most out of your processor:a1 http://h71000.www7.hp.com/doc/73final/sup/esi.pdf   G Also, go to www.Amazon.com and enter"OpenVMS Performance" in the searchi< bar to get listing of a a few books written on this subject.   Regards   
 Kerry Main Senior Consultantl HP Services Canada Voice: 613-592-4660  Fax: 613-591-4477  kerryDOTmainAThpDOTcom (remove the DOT's and AT)=20  $ "OpenVMS has always had integrity .. Now, Integrity has OpenVMS .."   ------------------------------  % Date: Sat, 06 Nov 2004 18:11:34 +0100T3 From: Michael Unger <spam.to.unger@spamgourmet.com>1 Subject: Re: Performance Tuninga+ Message-ID: <2v4fcuF2hknaeU1@uni-berlin.de>a  ) On 2004-11-06 17:17, "Main, Kerry" wrote:    >> -----Original Message-----  >> c >> [...] >>  F >> Why doesn't HP make such articles available in the "normal" OpenVMSF                                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^G >> documentation set, e.g., "Documents Supplements" section? (There hasp    ^^^^^^^^^^^^^^^^^G >> been a document called "Getting the most out of your Processor" some 4 >> time ago; I don't know if it is still available.) >>   >> [...] > 3 > Re: some additional performance on OpenVMS doc's:. >  > [...]  > I > Also, go to www.Amazon.com and enter"OpenVMS Performance" in the searchR> > bar to get listing of a a few books written on this subject.  C I don't want to buy books from various publishers covering specific F OpenVMS topics -- apparently the *contents* are already available fromG HP's (internal?, public?, support?, service?) databases. So "just" makeOE PDF documents from that or even put several related articles into onenD document. ("DECdocument" has been reported here some time ago as theH internal format -- which AFAIK can create PS files as well as plain text files as output.)o   > [...]r > & > "OpenVMS has always had integrity ..  > Now, Integrity has OpenVMS .."  E That should be "HP OpenVMS has always had integrity. Now HP IntegritywG servers have HP OpenVMS." (I got my polo shirt at the OpenVMS Technicalr Update Days recently ...)q   Michael    -- c; Real names enhance the probability of getting real answers.h5 My e-mail account at DECUS Munich is no longer valid.n   ------------------------------  % Date: Sat, 06 Nov 2004 09:52:48 +0100t0 From: Keith Cayemberg <keith.cayemberg@arcor.de>0 Subject: Re: Service Contract for Alpha HardwareB Message-ID: <418c90e1$0$20944$9b4e6d93@newsread2.arcor-online.net>   Alex Daniels wrote:M? > "Keith Cayemberg" <keith.cayemberg@arcor.de> wrote in messagep> > news:418be971$0$22609$9b4e6d93@newsread4.arcor-online.net... >  >><SNIP> >>D >>       - IBM has a contract with HP (actually made with Compaq) toD >>         to work together in making HP systems compatible with ESS@ >>         (shark) and IBM systems compatible with StorageWorks. >>5 >>IBM also develops Software which runs on OpenVMS...  >> >  > <SNIP> > E > Does the Shark support SCSI READL/WRITEL and the forced error flag?n > J > If yes, can you post the output of a SDA> sh dev ddcu (on a Shark served > disk). >  > Thanks >  > Alex >  >    Hi Alex,  I I do not personally have access to such a configuration. However, I will NH attempt to find out from the group which performs the ESS certification  for OpenVMS.  ' IBM Enterprise Storage Server Home Page . http://www.storage.ibm.com/disk/ess/index.html  + IBM Enterprise Storage Server - IBM Redbook P http://publib-b.boulder.ibm.com/Redbooks.nsf/RedbookAbstracts/sg245465.html?Open  B IBM TotalStorage Enterprise Storage Server Interoperability MatrixA http://www-1.ibm.com/servers/storage/disk/ess/interop-matrix.htmlt  $ IBM TotalStorage Product Guide - PDF4 http://www.storage.ibm.com/pguide/SSGProductsweb.pdf     Cheers!o   Keith Cayemberge   ------------------------------  % Date: Sat, 06 Nov 2004 10:01:47 +0100e0 From: Keith Cayemberg <keith.cayemberg@arcor.de>0 Subject: Re: Service Contract for Alpha HardwareB Message-ID: <418c92fc$0$22614$9b4e6d93@newsread4.arcor-online.net>   Larry Kilgallen wrote:  w > In article <418be971$0$22609$9b4e6d93@newsread4.arcor-online.net>, Keith Cayemberg <keith.cayemberg@arcor.de> writes:  >  > & >>IBM SCR - Security Controls Reporter1 >>http://sdsg.lagaude.ibm.com/sdsgSCR/ScrRoot.htmt. >>IBM SCR - Download Extractors - SECAUDIT_VMSQ >>http://sdsg.lagaude.ibm.com/sdsgSCR/download_extractor/ScrExtractorDownload.htmR >  > F > From two different positions on the Internet I get the equivalent of >  > + >>NEWS> spawn nslookup sdsg.lagaude.ibm.comm >> >>Spawning subprocesso >>Server:  LOCALHOST >>Address:  127.0.0.1e >>I >>*** LOCALHOST can't find SDSG.LAGAUDE.IBM.COM: Non-existent host/domaine >> >><Return> to continue NEWS     F Sorry Larry, it appears this OpenVMS Software is for internal IBM use F only. It's being used by IBM Global Services to fulfill SLA contracts 6 with our customers having OpenVMS (and other) systems.   Cheers!i   Keith Cayemberge. IBM Business Services GmbH - Hannover, Germany   ------------------------------   Date: 6 Nov 2004 08:02:20 -0600 4 From: kaplow_r@encompasserve.org.TRABoD (Bob Kaplow)! Subject: Serving HTML CD from VMSu3 Message-ID: <NIAJAcW48J$P@eisner.encompasserve.org>n  K I want to take the VMS HTML Docs CD and use my VMS system to serve it up totH our network. I'm not running a web server, Pathworks, Samba, or anythingI like that on the VMS system. I know I did this before with FTP, but now IsG can't seem to get it to work. IIRC what I'd done before is to create anu; account whose default directory was the CD and then surf tor6 ftp://user:password@host/index.html What am I missing?    1 	Bob Kaplow	NAR # 18L	TRA # "Impeach the TRA BoD" & 		>>> To reply, remove the TRABoD! <<<K Kaplow Klips & Baffle:	http://nira-rocketry.org/LeadingEdge/Phantom4000.pdf L     www.encompasserve.org/~kaplow_r/    www.nira-rocketry.org    www.nar.org  1 	26-October, 2001: A day that will live in infamyn4 	Support Freedom: http://www.indefenseoffreedom.org/  I         We must have faith in our democratic system and our Constitution, K         and in our ability to protect at the same time both the freedom andi'         the security of all Americans. o   ------------------------------   Date: 6 Nov 2004 16:00:43 +0100 . From: huber@NOBODY-mppmu.mpg.de (Joseph Huber)% Subject: Re: Serving HTML CD from VMSo+ Message-ID: <c21HHMpoG5CT@vms.mppmu.mpg.de>m  j In article <NIAJAcW48J$P@eisner.encompasserve.org>, kaplow_r@encompasserve.org.TRABoD (Bob Kaplow) writes:M > I want to take the VMS HTML Docs CD and use my VMS system to serve it up tohJ > our network. I'm not running a web server, Pathworks, Samba, or anythingK > like that on the VMS system. I know I did this before with FTP, but now IhI > can't seem to get it to work. IIRC what I'd done before is to create ann= > account whose default directory was the CD and then surf toS8 > ftp://user:password@host/index.html What am I missing?  8 Could You say more detailed what exactly does not work ?F I just tested with my system, where the CD is served by an infoserver, and it certainly works.5! What has changed on Your system ?   VMS version ? Which FTP server ? Which browser ?aE What is the error message on the browser side ? on the VMS FTP serverS side ?9 If You have changed the browser, this may be the problem:R< some browsers of MS Win provenience have problems with some < VMS FTP servers: I switched to HG FTP in pure Unix mode, and have no more problems.A To find out if the browser is the problem, use a command-line FTP C client to get the file: if this works, You have a browser-ftpserverm problem.  e -- R6    Joseph Huber, Muenchen  http://www.huber-joseph.de/   ------------------------------  # Date: Sat, 06 Nov 2004 15:14:52 GMTe5 From: brad@rabbit.dnsalias.org (Bradford J. Hamilton)o% Subject: Re: Serving HTML CD from VMSa. Message-ID: <MT5jd.471675$mD.398559@attbi_s02>  j In article <NIAJAcW48J$P@eisner.encompasserve.org>, kaplow_r@encompasserve.org.TRABoD (Bob Kaplow) writes:L !I want to take the VMS HTML Docs CD and use my VMS system to serve it up toI !our network. I'm not running a web server, Pathworks, Samba, or anythingCJ !like that on the VMS system. I know I did this before with FTP, but now IH !can't seem to get it to work. IIRC what I'd done before is to create an< !account whose default directory was the CD and then surf to7 !ftp://user:password@host/index.html What am I missing?U  O Hmm, this seems to work for me on my hobbyist system (thanks, BTW - it's alwaysa nice to learn something new!).  6 Could there be a file or directory permission problem?   !snip!  J __________________________________________________________________________A Bradford J. Hamilton                    "All opinions are my own"iK bMradAhamiPltSon-at-coMmcAast.nPeSt     "Lose the MAPS, and replace '-at-' b0                                          with @"   ------------------------------   Date: 6 Nov 2004 09:03:52 -0700v1 From: nothome@spammers.are.scum (Malcolm Dunnett) 7 Subject: System crash after installing 732-UPDATE-V0300 - Message-ID: <ZlJ20XYuULM7@malvm7.mala.bc.ca.>g  ; Anyone else seen problems with the VMS732-UPDATE-V0300 kit?8  2 I installed this kit on Friday and on Friday nightA my system crashed during an Oracle export. The crash dump showed:     ! System State at Time of Exceptione! ---------------------------------e>         Arg    = FFFFFFFF.80120B60  EXE_STD$WRTMAILBOX_C+00930$         Arg    = 00000000.00000B03  P %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=000000000000& 0000, PC=FFFFFFFF80120B60, PS=00000B03    E Which looks to me like a bug in a Mailbox routine ( access  violationsD at virtual address 0 ). Oracle jobs make heavy use of mailbox I/O toF communicate with the server process when using the "bequeath" adapter.  ' The hardware is a dual processor DS20E.e  F I'll open a support call on Monday, but just thought I'd see if anyoneC else has seen this ( and provide the group with one data point that > suggests you might not want to install this update just yet ).  M =============================================================================aB Malcolm Dunnett      Malaspina University-College   Email: dunnettE                                                      Host: mala.bc.casH Information Systems  Nanaimo, B.C. CANADA V9R 5S5     Tel: (250)740-6297   ------------------------------  * Date: Sat, 6 Nov 2004 17:43:54 +0000 (UTC)P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) Subject: Re: Time Change$ Message-ID: <cmj2gq$qdb$4@online.de>  F In article <RIBgd.32133$R05.26886@attbi_s53>, brad@rabbit.dnsalias.org (Bradford J. Hamilton) writes: A  J > Not until you upgrade to V7.3 (at least).  A new SYSGEN parameter calledN > AUTO_DLIGHT_SAV comes into play to assist in "automatic" spring forward/fall > back operations.  F SYSMAN> do pipe mc sysman help sys_para | sea sys$pipe AUTO_DLIGHT_SAV2 %SYSMAN-I-OUTPUT, command execution on node DANEELB   AUTO_DLIGHT_SAV       AWSMIN     AWSTIME    BALSETCNT  BORROWLIM2 %SYSMAN-I-OUTPUT, command execution on node ELIJAHB   AUTO_DLIGHT_SAV       AWSMIN     AWSTIME    BALSETCNT  BORROWLIM2 %SYSMAN-I-OUTPUT, command execution on node GLADIAB   AUTO_DLIGHT_SAV       AWSMIN     AWSTIME    BALSETCNT  BORROWLIM SYSMAN> do sh sys/noproc2 %SYSMAN-I-OUTPUT, command execution on node DANEELJ OpenVMS V7.3  on node DANEEL   6-NOV-2004 18:44:11.37  Uptime  76 17:12:422 %SYSMAN-I-OUTPUT, command execution on node ELIJAHJ OpenVMS V7.3  on node ELIJAH   6-NOV-2004 18:44:12.58  Uptime  76 14:42:322 %SYSMAN-I-OUTPUT, command execution on node GLADIAK OpenVMS V7.3-1  on node GLADIA   6-NOV-2004 18:44:13.27  Uptime  5 16:53:35  SYSMAN>e  F The parameter is in the SYSMAN help on VAX.  It shouldn't be there if G this parameter doesn't exist on VAX.  I don't want to test it and have eA the nodes with times an hour apart---has anyone used this on VAX?m   ------------------------------   End of INFO-VAX 2004.617 ************************ds in RMS activity, often directly        related to 9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9     9    9    9    9    9    9    9    9    9    	9    
9    9    9    
9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9     9    !9    "9    #9    $9    %9    &9    '9    (9    )9    *9    +9    ,9    -9    .9    /9    09    19    29    39    49    59    69    79    89    99    :9    ;9    <9    =9    >9    ?9    @9    A9    B9    C9    D9    E9    F9    G9    H9    I9    J9    K9    L9    M9    N9    O9    P9    Q9    R9    S9    T9    U9    V9    W9    X9    Y9    Z9    [9    \9    ]9    ^9    _9    `9    a9    b9    c9    d9    e9    f9    g9    h9    i9    j9    k9    l9    m9    n9    o9    p9    q9    r9    s9    t9    u9    v9    w9    x9    y9    z9    {9    |9    }9    ~9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    9    