1 INFO-VAX	Sun, 26 Nov 2000	Volume 2000 : Issue 660       Contents:( Re: Compaq Linux (RedHat or SCO/Caldera) Re: Connecting a CD-writer.. Re: Connecting a CD-writer.. Re: Connecting a CD-writer.. Re: DEFRAG with BACKUP/IMAGE Re: DEFRAG with BACKUP/IMAGE Re: EBay vs. QXL Eigen 	 Re: Eigen  Re: Enterprise Toolkit Problem< Re: HSJ40 dual-redundant controller rolling firmware upgrade  Need Alpha Firmware V6.7 PLEASE!> Need one file from Alpha AXP Systems Firmware Update 5.3 (old) Performance problems Re: Performance problems Re: Performance problems Re: Performance problems Re: Performance problems Test  F ----------------------------------------------------------------------  % Date: Sat, 25 Nov 2000 19:27:12 -0600 % From: Keith Brown <kbrown780@isd.net> 1 Subject: Re: Compaq Linux (RedHat or SCO/Caldera) ' Message-ID: <3A2066F0.4CF60337@isd.net>   * fabio_compaq@ep-bc.petrobras.com.br wrote: > C > Do you know if Compaq decided what will be the "Official Linux" ? I > At Compaq homepage theres a promotion of preinstalled RedHat on DL360, 0 > but Compaq is a long term partner of SCO . . . >  > Click here >  > For RedHat > @ > http://www.directplus.compaq.com/html/redhatlinux7_launch.html >  > For SCO/Caldera  > J > http://news.cnet.com/news/0-1003-200-3730654.html?tag=st.ne.1002.bgif.ni    F Try also http://www.linux-mandrake.com/    The best Linux distribution   --   Keith Brown  kbrown780@isd.net    ------------------------------  % Date: Sat, 25 Nov 2000 13:59:22 -0600 7 From: "David J. Dachtera" <djesys.nospam@earthlink.net> % Subject: Re: Connecting a CD-writer.. - Message-ID: <3A201A1A.FD784D01@earthlink.net>    Paul Sture wrote:  > [snip]I > There you have it in a nutshell. The drive doesn't do a simple function ( > such as obeying a manual eject button. > ! > Not worth supporting yet, IMHO.   H Might be a defective unit, also. The one I have is the only one of these I have ever seen in operation.   --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/   F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.    ------------------------------  % Date: Sat, 25 Nov 2000 16:07:41 -0500 2 From: "Richard B. Gilbert" <DRAGON@compuserve.com>% Subject: Re: Connecting a CD-writer.. 7 Message-ID: <200011251607_MC2-BC15-EDB5@compuserve.com>   F         Everyone seems to have all these ideas for **someone else** to? implement!  Someone else usually seems to mean VMS Engineering.   G         The Unix guys seem to just go ahead and implement them.  What's J wrong with the VMS community?  You think there's a market?  Invest half a=  J man year of your time, produce a product of commercial quality, and try t= o J get your money out of it.  Everyone will want it and almost no one will p= ay* for it.  They will all want it to be FREE!  + Message text written by "David J. Dachtera" J >What would it take for someone to write an appropriate driver to make up=  . for the "generic SCSI" shortfalls of DKDRIVER?   "Where's the market?", you ask.   : How many posts/threads have there been on that topic here?   Any further questions?<    ------------------------------  % Date: Sat, 25 Nov 2000 16:07:17 -0600 7 From: "David J. Dachtera" <djesys.nospam@earthlink.net> % Subject: Re: Connecting a CD-writer.. - Message-ID: <3A203815.74762BB7@earthlink.net>    "Richard B. Gilbert" wrote:  > H >         Everyone seems to have all these ideas for **someone else** toA > implement!  Someone else usually seems to mean VMS Engineering.  > C >         The Unix guys seem to just go ahead and implement them.     7 Does the expression "open source" mean anything to you?   E There IS a source license available for OpenVMS; however, even Compaq G and OpenVMS Engr'g. admits that this kit lacks all the pieces necessary E to rebuild the entire operating environment from source, unlike *BSD,  Linux, etc.    > What's  > wrong with the VMS community?   D I've seen more than one poster here express a sentiment which can beF summarized as: if OpenVMS Engr'g. didn't issue it, we won't even think about implementing it.   > You think there's a market?   B I *KNOW* there is, but I am frequently the only one who holds suchG faith. Witness: the lack of action on Affordable OpenVMS and/or OpenVMS > Marketing, despite direct communication with top management at2 OpenVMS/Compaq, both privately and in public fora.   > Invest half a  > man year of your time,  D ...not to mention selling your soul and those of your entire kinship0 into indentured servitude for seven millennia...  5 > produce a product of commercial quality, and try to M > get your money out of it.  Everyone will want it and almost no one will pay , > for it.  They will all want it to be FREE!  F ...or at least affordable. No *ONE* customer is going return my entireH investment or put my step-daughter all the way through college to a PhD.  F ...then again, there's the whole discussion about margin vs. volume...   No easy answers, eh?   --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/   F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.    ------------------------------  + Date: Sun, 26 Nov 2000 00:46:30 +0100 (CET) : From: "Gotfryd Smolik, VMS lists" <gotfryd@stanpol.com.pl>% Subject: Re: DEFRAG with BACKUP/IMAGE J Message-ID: <Pine.LNX.4.21.0011260039030.21478-100000@irys.stanpol.com.pl>  + On Tue, 21 Nov 2000, Leigh G. Bowden wrote:   M +We did a defrag of some of the disks on a AS2100 4/233 two node cluster with M +FDDI interconnect.  Attached is a HSZ40C with "lots" of disks on six shelves , +and configured RAID 0+1. Both run VMS v6.2.+                                    ********    [...] G +The BACKUP/IMAGE seemed to propogate all disk and file characteristics M +except the INDEXF.SYS location which returned to the middle. I haven't tried L +any exhaustive tests as such but I played around with the /INIT and /NOINIT4 +flags to see if this made a difference. It did not. + D +What is the way of defragging a disk and maintaining the INDEXF.SYS
 +location?      Boot from CD-ROM a VMS 7.X.> AFAIR up to (or only ? but I remember trouble in 5.X) VMS 6.2 9 BACKUP has a bug in the /NOINIT qualifier and ignores it.   @  If you have only some big files - then do a "normal" (noimage) > BACKUP, will suggest /OWNER=ORIGINAL which also saves the file protection.   ?  If you have lot of ACLs and get to trouble with saving it then < ask me on "GS@...." - restoring it with DCL commandprocedure: is relatively simple. If you can get both the disk mounted/ (old and new) then check for SET SECURITY/LIKE.     Regards - Gotfryd   --  E ===================================================================== F $ ON F$ERROR("LANGUAGE","ENGLISH","IN_MESSAGE").GT.F$ERROR("NORMAL") - 		THEN EXCUSE/OBJECT=ME . $!                        GS@stanpol.zabrze.plE =====================================================================    ------------------------------  + Date: Sun, 26 Nov 2000 00:52:56 +0100 (CET) : From: "Gotfryd Smolik, VMS lists" <gotfryd@stanpol.com.pl>% Subject: Re: DEFRAG with BACKUP/IMAGE J Message-ID: <Pine.LNX.4.21.0011260047190.21478-100000@irys.stanpol.com.pl>  ( On Tue, 21 Nov 2000, David Beatty wrote:   + ; +Initialize the new disk with the characteristics you want, 6 +like headers and position of INDEXF.SYS, then perform  +the restore with /NOINITIALIZE.                   *************    +David R. Beatty  8 BTW: can you answer *after* the related part of original*  messages ? Is much more readable, thanks.    To meritum:   [...] M +>any exhaustive tests as such but I played around with the /INIT and /NOINIT 5 +>flags to see if this made a difference. It did not.   <  David, you have cut off the part with VMS version; but some; older version *really* ignores the /NOINIT qualifier, Leigh  is (most probably) right !    Regards - Gotfryd   --  E ===================================================================== F $ ON F$ERROR("LANGUAGE","ENGLISH","IN_MESSAGE").GT.F$ERROR("NORMAL") - 		THEN EXCUSE/OBJECT=ME . $!                        GS@stanpol.zabrze.plE =====================================================================    ------------------------------  % Date: Sun, 26 Nov 2000 00:11:22 -0500 & From: Jerome Fine <jhfine@idirect.com> Subject: Re: EBay vs. QXL + Message-ID: <3A209B7A.D9143F54@idirect.com>    >Roy Omond wrote:    > >Jordan Henderson wrote:G > > Also, some firewalls will watch protocol level traffic for HTTP and H > > start keeping track if suspicious requests are coming from a certainG > > address.  Suspicious being defined as poorly defined (too much data M > > in an attempt to hit a buffer overflow exploit) or known exploits against N > > a range of configurations.  Enough of these suspicious requests will causeL > > the firewall to shutdown any access from that address.  This policy willN > > frustrate the black hat who is trying a range of exploits to find one that# > > works in a given configuration. G > Hmmm... then how about explicitly broadcasting something you're *not*  > running.  Yep, I've got it !   Jerome Fine replies:  O Why can't the firewall present a simple "easily exploited" system to suspicious K requests instead of something that is hard to knock over - like W98 or some Q other server OS that is likely to be there and "might" not have a firewall.  That P way, it might also be possible to trace the "black hat" source while the attemptK is taking place.  That would seem to be much more effective in the long run P since any black hat would run the risk of being identified.  It seems to me thatN the network was built without safeguards in mind which would have been trivialN to include right from the start and would not have prevented a legitimate userL (who is easily identified right now in any case) from reasonable access, butB would have stopped any spam generators and other such persons fromI unreasonable activity - something simple like requiring an origin address  to be attached to all messages?   H Why is it that the simple cost of pennies for protection up front at theB beginning are allowed to grow into millions for lack of reasonableC foresight and greed by many companies who either don't care or else C are actually the ones who take advantage or benefit in the long run  from any problems?   Sincerely yours,   Jerome Fine    ------------------------------  % Date: Sat, 25 Nov 2000 15:54:43 -0700 + From: "Barry Treahy, Jr." <Treahy@mmaz.com>  Subject: Eigen( Message-ID: <3A204332.567D0B1C@mmaz.com>  H Does anyone know if Eigen, the VMS software 'utilities' company is still" around and so, their web site URL?   Barry    --  ? Barry Treahy, Jr  *  Midwest Microwave  *  Vice President & CIO   A E-mail: Treahy@mmaz.com * Phone: 480/314-1320 * FAX: 480/661-7028    ------------------------------    Date: 25 Nov 2000 22:27:04 -0500/ From: jordan@lisa.gemair.com (Jordan Henderson)  Subject: Re: Eigen* Message-ID: <8vpvu8$42v$1@lisa.gemair.com>  ( In article <3A204332.567D0B1C@mmaz.com>,* Barry Treahy, Jr. <Treahy@mmaz.com> wrote:I >Does anyone know if Eigen, the VMS software 'utilities' company is still # >around and so, their web site URL?  >    http://www.nserver.com/eigen/    >Barry >  >--  > @ >Barry Treahy, Jr  *  Midwest Microwave  *  Vice President & CIO > B >E-mail: Treahy@mmaz.com * Phone: 480/314-1320 * FAX: 480/661-7028 >  >  >    -Jordan Henderson  jordan@greenapple.com    ------------------------------  # Date: Sun, 26 Nov 2000 05:40:18 GMT 2 From: Shraga_Broyer@bmc.nospam.com (Shraga Broyer)' Subject: Re: Enterprise Toolkit Problem - Message-ID: <3a20a04a.338175911@news.bmc.com>   B I sometimes "touch" files on the VMS (By renaming the files to theF same name) in order to encourage MMS to do its thing.  The fact that IE then have files on my NT that are not checked out but are more recent E than the CONTINUUS database causes me a great grief (i.e large amount E of errors which I then have to manually handle) when I get the latest  updates of the team.    C On Fri, 24 Nov 2000 11:33:02 -0500, "John Vottero" <John@mvpsi.com>  wrote:  @ >"Shraga Broyer" <Shraga_Broyer@bmc.nospam.com> wrote in message( >news:3a1a6165.102121302@news.bmc.com... >> Hi.G >> I have an OpenVMS Enterpeise Toolkit V1.2-2 for Visual Studio. It''s E >> connecting my development environment which is NT 4.0 and my ALPHA D >> with OpenVMS 6.2-1H3.  I have a problem: The "SYNCHRONIZE" buttonI >> transfers updated files from the VMS to the NT even if they are marked G >> as "READ-ONLY" on the NT without any  warning (such as "This file is G >> marked as read-only, are you sure?"). This became an issue because I C >> am working with a source control software ("CONTINUUS") and this H >> behaviour is VERY not in synch with the required check-out mechanism. >> Any suggestions? 
 >> Thanks! > F >I think that's just the way it works.  Visual Studio seems to use theK >READ-ONLY attribute as a marker to mean that the file is under source code B >control and it isn't checked out.  When the Enterprise Toolkit isD >synchronizing it expects to have to overwrite files that are markedJ >READ-ONLY, it just means that you don't have them checked out but someoneI >else has modified the file.  How did the server file get updated without " >being checked out from CONTINUUS? >  >  >  >    ------------------------------  % Date: Sat, 25 Nov 2000 13:55:57 -0600 7 From: "David J. Dachtera" <djesys.nospam@earthlink.net> E Subject: Re: HSJ40 dual-redundant controller rolling firmware upgrade - Message-ID: <3A20194D.70CC27C1@earthlink.net>   
 Lee wrote: > J > The HSJ V3.4 release notes stipulate adjacent rolling upgrades.  So doesL > Compaq Support.  However, I do not recall receiving HSJ V3.3.  I am hopingM > for confirmation one way or another.  There seems to be an inconsistency in J > Compaq's suggested rolling upgrade path.  The release notes mention only > V2.7, V3.2, and V3.4.   ; Do you have a support contract? If you do, give 'em a call.   / > My last rolling upgrade to V3.2 caused "mount 8 > verification" messages but no loss of shadow members.   G This is normal when changing MSCP hosts of dual-pathed devices. Nothing G to be concerned about - it means everything is working right as long as  the MntVerify clears.    > Every shadow? > member is dual-pathed and dual-powered in each computer room.   	 Good job!    --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/   F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.    ------------------------------  % Date: Sat, 25 Nov 2000 16:03:40 -0700 . From: "John R. Lawson, Jr." <Mage@DirecPC.com>) Subject: Need Alpha Firmware V6.7 PLEASE! 4 Message-ID: <7zXT5.4223$925.182602@news.direcpc.com>  L I was once (in a former lifetime) the developer that maintained the ISL bootK code in VMS (both VAX and Alpha) for booting off InfoServer boxes, and from J virtual disk files under POLYCENTER Software Distribution (RSM).  It dawnsK on me that booting into an ISL is not very much different from booting into I a VMScluster, so I created a non-writeable LAD service of my Alpha system ! disk, and booted my MUSTANG with:        >>> boot -fi APB.EXE ewa0   H And magically, the ISL boot menu came up!  When I went out to search theK network for LAD services, it told me that it could not communicate with the  network ... HMMMMM!!!!  K I then took a SANDPIPER (of similar vintage, with latest firmware (V7.0) asuG well, but *does* boot into VMScluster), and booted it into the ISL, ands8 voila!  It finds services and is able to boot from them.  K So ... I then took out my trusty/crusty old Alpha Firmware V6.6 floppy, andNG re-loaded it into my MUSTANG ... Now it boots into the ISL and actually G *FINDS SERVICES ... AND CAN BOOT FROM THEM ... at least up to the point=< where SYSBOOT complains that it needs to be at Firware V6.7.  I So .... This means that it's the V7.0 firmware that disables the ethernetzG card!  I found V6.9 firmware on the same CD as 7.0, and it has the same=K problem.  So, somewhere after 6.6, and before/at 6.9, the ethernet card was0 "broken" by the Alpha firmware!d  L The absolute minimum firmware needed to run E7.3 is 6.7 ... but I can't findJ 6.7 anywhere ... it's on the "Alpha AXp Systems Firmware Update 5.3 CDROM"K ... Does anyone have one of these laying around?  I only need one file fromc it:s       [ALPHA200]AS200_V6_7.EXE  K Can someone look through their old stuff and see if you have this old disk,hK with this old firmware update, please?  My hope is that the "problem" isn't L introduced 'til 6.8 or 6.9 ... I guess I have a 67% chance of success ... OrD else maybe I could file an SPR against the firmware???????!!!!!&&&&&   Mage   ------------------------------  % Date: Sat, 25 Nov 2000 16:13:12 -0700o. From: "John R. Lawson, Jr." <Mage@DirecPC.com>G Subject: Need one file from Alpha AXP Systems Firmware Update 5.3 (old)n4 Message-ID: <0IXT5.4224$925.182864@news.direcpc.com>  K The file I need is [ALPHA200]AS200_V6_7.EXE ... I can't use a later versionsE of the firmware, as it introduces problems with the ethernet card andlH booting into VMSclusters (and from LAD).  If anyone happens to have this. file, please, please, please forward it to me!   John Lawsonr Mage@ChannelPoint.comr
 (719)867-9204t   ------------------------------  % Date: Sat, 25 Nov 2000 22:28:23 +0100n+ From: "Robert de Boer" <r.e.deboer@kpn.com>k Subject: Performance problems . Message-ID: <8vpbe9$sse$1@info.service.rug.nl>  J I am running OpenVMS 6.2-1H3 on an Alpha 8400 with Oracle 7.1. Four  weeksI ago I made some adjustements and now I have a strange kind of performancehH problem. Occasionly the modified page list goes up to 130.000 pages. TheJ effect is that processes hang for several minutes before the modified page2 writer has finished writing pages to the pagefile.  " The modifications I have made are:# - increased SGA-size Oracle to 41MBt7 - increased working sets parameters WSEXTENT and WSQUO.o  K I have already set MPW_HILIM on 65535, MPW_LOWAITLIM on 64511 and MPW_LOLIMh	 on 61000.r   My questions are:lI - I don't know where the pages above 65535 on the modified page list comemK from. Can someone give me a hint how to determine/examine where those pagesa
 come from?J - Has someone else experienced  this kind of problem? Where came the pagesH on the modified page list from? What did you do about it? Have you got a workaround?V  
 with regards,i Robert de Boer   ------------------------------  % Date: Sat, 25 Nov 2000 16:16:19 -0600 7 From: "David J. Dachtera" <djesys.nospam@earthlink.net>a! Subject: Re: Performance problems4- Message-ID: <3A203A33.B95421D1@earthlink.net>-   Robert de Boer wrote:N > [snip]M > I have already set MPW_HILIM on 65535, MPW_LOWAITLIM on 64511 and MPW_LOLIMg > on 61000.D  E First guess time (without more specific info. re: your environment): m  > Try putting MPW_LOLIMIT back down closer to the default value.   From: V7.1-2& $ MC SYSMAN HELP PARA PARA MPW_LOLIMIT [SNIP]?          MPW_LOLIMIT ensures that a certain number of pages aren	 availableyD          on the modified-page list for page faults. If the number isG          too small, the caching effectiveness of the modified-page list/D          is reduced. If it is too high, less memory is available for9          processes, so that swap (and page) may increase.:  B Try putting MPW_LOWAITLIMIT back down closer to the default value.   From: V7.1-2* $ MC SYSMAN HELP PARA PARA MPW_LOWAITLIMIT [SNIP]F          MPW_LOWAITLIMIT specifies the threshold at which processes inD          the miscellaneous wait state MPWBUSY are allowed to resume.>          MPW_LOWAITLIMIT increases system performance for fast
 processorsE          with large memories by reducing the amount of time processesr)          spend in the MPWBUSY wait state.m  G See how that goes, but take specific knowledge of your environment into4? consideration before deciding on a target value for either one.:   -- h David J. Dachteraa dba DJE Systemsm http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/2  F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.N   ------------------------------    Date: 26 Nov 2000 02:23:25 +0100) From: maulis@ludens.elte.hu (Maulis Adam)a! Subject: Re: Performance problemsi! Message-ID: <aZKLHoJixHpN@ludens>I  \ In article <8vpbe9$sse$1@info.service.rug.nl>, "Robert de Boer" <r.e.deboer@kpn.com> writes:L > I am running OpenVMS 6.2-1H3 on an Alpha 8400 with Oracle 7.1. Four  weeks   How much is your total memory?  ' I think at least 2Gbytes (262144 pages)     K > ago I made some adjustements and now I have a strange kind of performancesJ > problem. Occasionly the modified page list goes up to 130.000 pages. The   Pages or pagelets?    L > effect is that processes hang for several minutes before the modified page4 > writer has finished writing pages to the pagefile.  % Thats correct of your configuration:    E  - When the ModifiedPageList grow up to MPW_WAITLIMIT the most paging:@    process is go to the RWMPB process state. It's released when K    the modified page writer writes out enough page (the ModifiedPageList is !    shrinked to MPW_LOWAITLIMIT. )h  D    I assume that your MPW_WAITLIMIT are 65535 pages. (1/2 Gbyte, the,    architectural maximum in VMS 6.2 systems)  @    There are a  65535 pages - 64511 pages = 1024 pages = 8Mbytes?    between MPW_WAITLIMIT and  MPW_LOWAITLIMIT. So your machine i>    forced to write out 8 Mbytes to a (think) busy system disk.           > $ > The modifications I have made are:% > - increased SGA-size Oracle to 41MBd9 > - increased working sets parameters WSEXTENT and WSQUO.a > M > I have already set MPW_HILIM on 65535, MPW_LOWAITLIM on 64511 and MPW_LOLIMo > on 61000.n >  > My questions are:aK > - I don't know where the pages above 65535 on the modified page list comeg > from.    may mix page/pagelets ?a        L > - Has someone else experienced  this kind of problem? Where came the pagesJ > on the modified page list from? What did you do about it? Have you got a
 > workaround?n    C - To lower MPW_HILIMIT. (at least 65536-MPW_WRTCLUSTER*MPW_IOLIMIT)y?   Insert only MPW_HILIMIT, MPW_LOLIMIT, MPW_WRTCLUSTER  to the  F   sys$system:modparams.dat. Let autogen calculate the  MPW_LOWAITLIMIT/   and MPW_WAITLIMIT. (around the MPW_HILIMIT). e-   (Thats supply the quick process response .)s    6 > Where came the pages on the modified page list from?   It's hard question..   some workaround:   Simplify the paging algorithm:. - let the process' WSEXTENT and WSQUOTE equal.A - let the (this is the default) BORROWLIM and GROWLIM and FREELIMe
     equal.    < Your problem is may be derived from the following situation:  0 - WSINC extremly high (comparable with FREEGOAL)0 - FREELIM extrelmy low (less than half of WSINC)  ;    - the free list is above of FREEGOAL, the system thinks         there is enough free pages.9    - a process requires some memory. The system increaseso7      its working set with WSINC. The free list shrinks  3      bellow FREELIM in few steps. The system thinks-:      there is no enough pages, so trying to write out some;      pages from ModifiedPageList. System cannot write from,t8      because the ModifiedPageList below the MPW_LOLIMIT.*      (Your MPW_LOLIMIT is extremly hight.)  i7      So, the swapper triming lower one of your process' 5      working set. From actual size to WSQUOTA (or, ifeE     actual size bellow than WSQUOTA) to max(SWPOUTPGCNT,SWPOUTPGCNT).e  G      There may be a plenty of pages that get into the ModifiedPageList.A     - or the following situation:I  J - your pagefile is too little. In a production, big system always let the <   pagefile's reservable count be positive. ($ SHOW MEM/FILE)  K   (I can't remember correctly, but I think there is an 1 Gbyte limitations p$    per pagefiles on VMS 6.* systems)     >  > with regards,  > Robert de Boer >  >    Workaround:    - Much lower MPW_LOLIMIT: - do not specify by hand MPW_WAITLIMIT and MPW_LOWAITLIMIT' - let the FREELIM more than 1.5 * WSINC2, - let the FREEGOAL more than 6 times FREELIM(   (so your WSINC cannot be a huge value)  6 -  If some process extremly paging ( $ MON PROC/TOPF )D   try increase its WSDEF, WSQUOTA = WSEXTENT to a much higher value.( - insert a pagefile to the separate disk       Regards, Adam MaulisC    H (I tuned an alphaserver 8400 (2 CPUs, 2Gbytes ram, VMS 6.2-1H3, RDB 6.1)A  a good while two years ago. The average page faults lowered fromoC 8000/sec to 300/sec. I worked at this two months. My boss could notuG understand this, so I think now, it could be more simple to buy another2G 2 Gigs of mem. Nowdays I have a job at university: no money no boss :-)d   ------------------------------    Date: 26 Nov 2000 00:59:42 -0500* From: young_r@eisner.decus.org (Rob Young)! Subject: Re: Performance problems2+ Message-ID: <wCDFoA5gYkkz@eisner.decus.org>o  B This one comes up occasionally and is/was one of my few complaints3 regarding the memory manager.  Here is an analysis:w    > http://www.deja.com/[ST_rn=ps]/getdoc.xp?AN=632467958&fmt=text  * From: young_r@eisner.decus.org (Rob Young) Subject: Re: system slow Date: 08 Jun 2000 00:00:00 GMT Newsgroups: comp.os.vmse  C In article <r5E%4.137$244.2520@typhoon.elp.rr.com>, "Jim Kozlowski"i <jkozlow1@elp.rr.com> writes:D* > We have an Alpha 200 running openVMS 6.1I > System running fine until 2 months ago...at that time we replaced a 1gb/K > drive with a 2gb drive (i do not know drive model off hand) new drive wase > not system disk.G > We added the disk space to accomodate a software upgrade which has ush8 > running two different version of synergy concurrently.J > It seems, that since that time, the system runs much slower. At times itJ > will suspend all activity for 20-30 seconds at a time. Processes will be > suspended.J > I need some troubleshooting help. What can I monitor to determine if the; > hesitation is disk or software or something else related.s > Thank youa > Jim Ki >     L         The problem for the hang may be that you are short on memory.. to a N         point... this is most likely happening during busy or peak periods of          the day.  @         Unfortunately, Deja is brain-dead these days... they areD         re-archiving everything or somesuch.  Otherwise, I would cutC         and paste this analysis in here.  As it is , I have to wingoA         it but hope to follow-up tomorrow as I believe I saved its7         to a file also (at work).  [I did, it is below]t  E         I am going to be rather disjointed but not on purpose.  SorrynE         for the secondhand effort but the work is done before and why E         try to be accurate... you can do the verification tomorrow...t    ,                 1)  Memory is getting tight.=                 2)  Gets down to 2 times freegoal on freelisthD                 3)  Ticker kicks in trimming back 25% of mostly idle,                         processes.  Problem:  I                                 25% trim of large working sets in largisheH                                 memory config (1 gig or more) results inK                                 60 MByte being freed up (more or less can'tg;                                 say without poking around).o  N                 4)  Contents of Freed memory must be written to backing store,/                         i.e. pagefile  Problem:t  I                                 Takes time to write out 60 MByte, this is G                                 what the "hang" is all about (for those >                                 that are effected, see below).                   Verifcation:  1                         Open up a window and run:w  (                         $ monitor system  E                 When hang occurs , note number of processes in MWAIT.y                 What or why?  E                 Write a cheap DCL that finds and displays the MWAITs:     %                         $ counter = 0h                         $ loop:q/                         $ counter = counter + 1h5                         $ show system/output=show.tmpe1                         $ search show.tmp "RWMPB"n+                         $ delete show.tmp;*.A                         $ if counter .gt. 12 then exit ! Whatevero'                         $ wait 00:00:05t#                         $ goto loopt    D         That is my guess at your "hangs".  Very annoying.  Solution?H         Buy more memory.   Remember they are periodic hangs, most likelyH         at peak when memory is tight.   My suggested solution posted outL         here about 1-2 [2-3] years ago was to add bit values to MMG_CTLFLAGS<         to kick in 2 other algorithms.  The "kinder" ticker.  E         The current ticker and its 25% trim REGARDLESS of free memoryoG         is freeing up way too much in one swipe.  A "kinder" ticker maysM         operate on the principal of when memory gets down to 4 times FREEGOALpF         free, trim 25% of mostly idle processes UNTIL 8 times FREEGOALD         is free.  Maybe you get a bunch of oscillation but you avoidD         the annoying system hangs.  THAT is *very* difficult to dealF         with when sitting in the system manager hot seat.  However, itI         does help to find the cause and let management know something cans         be done about it.   I         Others will mention we need more information about your slowness.   )                 Are you maxed out on CPU?D                 etc.  H         One other thing... it may be tricky to catch the hang in action.H         Be at the ready during peaks and you may just want to tweek thatJ         pitiful DCL code above to save all the show systems and then laterN         search the *.tmp files for "RWMPB"  (Resource Wait Modified Page Busy)*         i.e. busy writing to the pagefile.  E         Also, who is "hung"?  Someone that is in the process of beingeN         paged out... one of the unlucky ones that is "mostly" idle.  That justJ         so happens to try to do something when the paging is taking place.G         I typically was seeing 7-10 in RWMPB out of a user community ofIG         600-700 interactive.   This may be like a tide (don't know, but F         could be) whereby when their memory is written out they becomeM         responsive.  So the "hang" situation has a lot of potential customersiD         in that timeframe.  These are folks that would typically logI         on, read mail , run reports and turn their attention to somethingdI         else.  To be dubbed "mostly idle" by the ticker, you have to have F         not used 1% CPU in the prior 30 seconds.  That is a wide fieldC         there.  So many potential candidates.  Since the ticker is -G         going after everyone that meets that criteria, viola!  Many arelF         being paged right when they decide to run another report, make"         another entry or whatever.  F         That is why you may not be seeing it and others are... you mayI         have all active windows and be telling yourself and others: "hey,e*         I'm not hung up!"  True statement.  O         You can be part of the fun at times too by opening up another session, iN         maybe editing a file and not touching it then when everyone is "hung" N         see if you can scroll up and down.. you may be in the middle of being J         paged out and paged back in again... you too are "hung up."  I wasK         lucky a few times and I too was "hung up!"  So I could let everyoneeI         else know that I was "hung up" and we could share in the sadness.V   ---e  ? 	My idea for a fix revolved around adding a bit to MMG_CTLFLAGS = 	to allow a "kinder" ticker in bit 3 and a LONGMIN swapper inc= 	bit 2 to counteract the 25% trim of mostly idle pages throwny4 	to the page file at one shot!  Something like this:    + Date: Fri, 16 Jan 1998 17:26:15 -0500 (EST)   L         I got an idea to improve memory management.  Here is the scenario...L         currently I have 1 Gig and I get many processes using hefty WSEXTENTK         as applications are large.  Mem gets down to 2 x FREEGOAL, tickler =M         [ticker] comes along and tickles and now I have MWAIT as mucho pages  B 	are being written to backing store.  Of course very shortly folksO         fault back in, free memory slinks back down to 2 x FREEGOAL, etc.  This          is annoying because:  9                         1) CPU is being chewed by SWAPPER -                         2) Cycle is repeating]O                         3) Long Dormant folks in applications are still holdingi>                            onto (in several cases) many pages.  K         Looking at 3 makes me want to swap them out but I can't force that. N         Raising LONGWAIT to 300 is helping a bit overall but is still getting >         me.   [This last statement is misleading, if a processM         hasn't performened any activity in LONGWAIT seconds (default 30) thenoH         it is considered idle.  By raising to 300 seconds, this helps toJ         sort out the truly idle from the people that stopped to take a sipG         of their coffee.  Also, this isn't examined until the "troller"wH         comes into play at 1 x FREEGOAL pages free so is not an accurate         statement.]L  @         So, why not solve 3 by adding a new bit to MMG_CTLFLAGS?  D         Pay attention to the new bit 2 below [and bit 3, that was my 	later revision/idea] . . .   
 Parameters     MMG_CTLFLAGS  F        MMG_CTLFLAGS is a bit mask used to enable and disable proactiveG        memory reclamation mechanisms. The following values are defined:m          Bit    Descriptionn  ?        0      Reclamation enabled by trimming from periodicallynG               executing, but otherwise idle processes. This occurs when G               the size of the free list drops below two times FREEGOAL.s  D        1      Reclamation enabled by outswapping processes that haveE               been idle for longer than LONGWAIT seconds. This occurs B               when the size of the free list drops below FREEGOAL.  D        2      Reclamation enabled by outswapping processes that haveE               been idle for longer than LONGMIN minutes.  This occurs N               when the size of the free list drops below three times FREEGOAL.  K        3      Reclamation enabled by kicking in the "ticker" when free list?L               drops below 4 times FREEGOAL and HALTS activity when free list)               has 8 times FREEGOAL pages.u  &        4-7    Reserved for future use.     $ mcr sysgen show longminoH Parameter Name            Current    Default     Min.     Max.     Unit  DynamicmH --------------            -------    -------    -------  -------   ----  -------lL LONGMIN                      1200      65535          5    65535   Mins    D   $ mcr sysgen show mmg_ctlflagsH Parameter Name            Current    Default     Min.     Max.     Unit  DynamicsH --------------            -------    -------    -------  -------   ----  -------IM MMG_CTLFLAGS                    7          7         0       255 Bit-mask   DR  H         In other words, anyone idle for 20 hours is probably out for theG         day... swap their backside out and give me that 10000+ pages so N         I don't have to tickle.  If things really get tight, tweek LONGMIN to 3         60 minutes, resetting to 20 hours at 6 p.m.   < 	[Note: recent discussion points out many sites for securityB 	purposes don't allow connections day to day.  Funny, but the siteE 	I was at when I wrote the above had just the OPPOSITE policy.  Don't E 	kill sessions, hence the LONGMIN idea.  In hindsight, it is probablyr> 	a non-starter but the "kinder" ticker sounds more plausable.]   ---B  1 	This statement of yours below is oh so familiar:i  K > - I don't know where the pages above 65535 on the modified page list comebM > from. Can someone give me a hint how to determine/examine where those pagesa  ? 	Took me about 2 weeks to figure out what was going on.  I usedrC 	DSNlink and poured through every MPW related article I could find.hD 	FWIW, the amount of memory being snagged by the ticker (from above)H 	- about 60 MBytes - (thrown to Modified List), in conjunction with the D 	MPW write cluster size and disk capabilities, HSJs ,etc. it worked A 	out to be about a 1.5-2 minute "hang" each time it happened for  # 	RWMPBs to go away.  Very annoying.h    \ In article <8vpbe9$sse$1@info.service.rug.nl>, "Robert de Boer" <r.e.deboer@kpn.com> writes:L > I am running OpenVMS 6.2-1H3 on an Alpha 8400 with Oracle 7.1. Four  weeksK > ago I made some adjustements and now I have a strange kind of performanceeJ > problem. Occasionly the modified page list goes up to 130.000 pages. TheL > effect is that processes hang for several minutes before the modified page4 > writer has finished writing pages to the pagefile. > $ > The modifications I have made are:% > - increased SGA-size Oracle to 41MB49 > - increased working sets parameters WSEXTENT and WSQUO.  > M > I have already set MPW_HILIM on 65535, MPW_LOWAITLIM on 64511 and MPW_LOLIMp > on 61000.a >  > My questions are:lK > - I don't know where the pages above 65535 on the modified page list comefM > from. Can someone give me a hint how to determine/examine where those pages  > come from?L > - Has someone else experienced  this kind of problem? Where came the pagesJ > on the modified page list from? What did you do about it? Have you got a
 > workaround?a >   @ 	Yeah... buy more memory or get the source listings and re-write 	the memory manager.   	Hope this helps.y     				RobI   > with regards,. > Robert de Boer >  >    ------------------------------    Date: 26 Nov 2000 01:36:08 -0500* From: young_r@eisner.decus.org (Rob Young)! Subject: Re: Performance problemsI+ Message-ID: <cs8$BYV1PHp+@eisner.decus.org>8  X In article <wCDFoA5gYkkz@eisner.decus.org>, young_r@eisner.decus.org (Rob Young) writes:  M >> - Has someone else experienced  this kind of problem? Where came the pagesXK >> on the modified page list from? What did you do about it? Have you got ao >> workaround? >> o > B > 	Yeah... buy more memory or get the source listings and re-write > 	the memory manager. >   A 	There are some other things you can do that will limit the hang.   A 	You can speed up the writes considerably by putting the pagefileg? 	on HSJ/HSZ/HSG mirror disk (for redundancy, certainly would beaA 	a drag to take a hit on a pagefile disk and go down) and turn on D 	write-back caching for that disk.  Ensure that mirror is doing onlyE 	*one* thing and that is managing that pagefile.  If you really wanna @ 	get frisky, crank up CACHE_FLUSH_TIMER to ensure it catches allE 	the writes (or can hold more) prior to committing them to a platter.h   				Robe   ------------------------------  % Date: Sun, 26 Nov 2000 03:24:26 +0100a  From: Paul Sture <paul@sture.ch>
 Subject: Testh+ Message-ID: <VA.000001a1.009c3a08@sture.ch>    test message - please ignore ___n
 Paul Sture Switzerland    ------------------------------   End of INFO-VAX 2000.660 ************************