1 INFO-VAX	Sun, 25 Mar 2001	Volume 2001 : Issue 168       Contents:@ Re: Alpha or Vax has to check if a Sun server is still alive HOW@ Re: Alpha or Vax has to check if a Sun server is still alive HOW  Re: Boring the pants off the COV- Re: Communication to local PC ports from VMS. P Re: DECevent 3.3 abort with"_DIAGNOSE-FAT:  Automatic analysis is still running.# Re: POSIX Streams, File Permissions # Re: POSIX Streams, File Permissions # Re: POSIX Streams, File Permissions # Re: POSIX Streams, File Permissions  Printing jpeg files on VMS, Re: Problem Booting Installed VMS 7.2 System! Re: VMS source listings omittings ! Re: VMS source listings omittings , Re: Will the VIOC be fixed in VMS Alpha 7.3?, Re: Will the VIOC be fixed in VMS Alpha 7.3?  F ----------------------------------------------------------------------    Date: 25 Mar 2001 16:24:24 -00004 From: Doc.Cypher <Use-Author-Address-Header@[127.1]>I Subject: Re: Alpha or Vax has to check if a Sun server is still alive HOW 6 Message-ID: <20010325162424.20714.qmail@nym.alias.net>  " -----BEGIN PGP SIGNED MESSAGE-----  = On 23 Mar 2001, Paul Repacholi <prep@prep.synonet.com> wrote: / >"anonymous" <verledentijd@hotmail.com> writes:  > G >> I need to check every hour if a Sun station is still up and running. D >> And if not than the DCL procedure should page or sms or something" >> like that.  But how do I start, > E >TO do it reliably, you need to turn it around. The other system must ? >send a heart-beat to the monitoring system every <time>. If no D >heat-beat is heard by <time>+10% ( say ) or id it *is* heard beforeB >90% of the interval, you declare the machine insane and raise the >alarm.     Insane? I'd diagnose Sun-stroke.     Doc.   -----BEGIN PGP SIGNATURE-----  Version: 2.6.2  @ iQEVAwUBOr0m8sriC3SGiziTAQGrzQf/UTW4LOdq8EQQe4qMLjaiKOmVVJyOH+Pw@ BN3wC1E+PNheqHAj4J8KN79NN/R5ZL0+bwHwxGISlyhyCOoPQ3n2CTNLDVcnVDUj@ rZoaGAKyDfG+Yd9xUvi/O5cf047sfaCji8jGMyGGZ2KX259Q0bBTZVuN+Gwa7PXA@ 87dWa+7d1Q3ckmjebJBRNPPkAFeMe5uJUMONPynYqBiLGyO/l9wVhwHE+NgX4WDd@ pRMksq9+odAwSBv+BL/+M5s0rKMxVEZGHKQv0nt5strNHZXm4Tj7oTg10MDYqxbv8 upPOSVOgCz4AYLYvoBNXxJ5l3gMh/dpC5X/gAp/10dYjdwWgTb081Q== =boY3  -----END PGP SIGNATURE-----    ------------------------------    Date: 26 Mar 2001 01:26:55 +0800, From: Paul Repacholi <prep@prep.synonet.com>I Subject: Re: Alpha or Vax has to check if a Sun server is still alive HOW - Message-ID: <873dc1lpy8.fsf@prep.synonet.com>   6 Doc.Cypher <Use-Author-Address-Header@[127.1]> writes:  ? > On 23 Mar 2001, Paul Repacholi <prep@prep.synonet.com> wrote: 1 > >"anonymous" <verledentijd@hotmail.com> writes:  > > I > >> I need to check every hour if a Sun station is still up and running. F > >> And if not than the DCL procedure should page or sms or something$ > >> like that.  But how do I start, > > G > >TO do it reliably, you need to turn it around. The other system must A > >send a heart-beat to the monitoring system every <time>. If no F > >heat-beat is heard by <time>+10% ( say ) or id it *is* heard beforeD > >90% of the interval, you declare the machine insane and raise the	 > >alarm.  > " > Insane? I'd diagnose Sun-stroke.  7 Are you sure? Zinc cream is protective with sun stroke.    --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.   ------------------------------   Date: 25 Mar 2001 08:08:41 GMT- From: djweath@attglobal.net (Dave Weatherall) ) Subject: Re: Boring the pants off the COV 5 Message-ID: <DTiotGxQ0bj6-pn2-Of6bXsqY2Wcr@localhost>   B On Fri, 23 Mar 2001 13:01:36, Christof Brass <brass@infopuls.com>  wrote:   > Dave Weatherall wrote: > > E > > On Thu, 22 Mar 2001 00:44:38, Christof Brass <brass@infopuls.com> 
 > > wrote: > >  > > > [SNIP] > > C > > By the way , have you picked up the use of the word 'crap' from I > > British colleagues? We do have a terrible habit of saying things like H > > 'and all that crap'. We use it instead of 'stuff' or 'things' or theH > > more correct collective term for what we are referring to. I used toI > > do it (still do, sadly) until I realised that it was being taken as a I > > pejorative (herabsetzend) instead of the collective (sammelwort) that 6 > > I'd intended. I try to be more careful these days. > >  > > Cheers - Dave. >  > Thanks for your words. > = > If UNIXification of VMS is the only way to survive than I'd ; > prefer to give it up. What I don't like is the mixture of B > technical and economical and marketing arguments. What I learnedB > from this NG is that DECpaq is responsible for the non-technical > forces against VMS.  > ? > I honestly don't know where I picked up the word "crap". As I ? > learned English from movies, technical books and listening to > > NGs because I learned Latin and Greek at school thanks to my@ > parents which should be 10 years tortured to death for that. I > use it to denote shit. > 5 > Did you pick up the German words from a dictionary?   D I checked 'pejorative' in the 4 volume Langenscheidt that my German B parents-in-law gave us as a wedding present. I've never heard the D other, more obvious translation, 'pejorativ' used. I have lived and F worked in Munich for 20 years now. It helps if you pick up some of the	 lingo ;-)    Cheers - Dave.   ------------------------------  % Date: Sun, 25 Mar 2001 13:11:37 +0200 - From: "Olek Koodziejczyk" <olekk@kki.net.pl> 6 Subject: Re: Communication to local PC ports from VMS.& Message-ID: <99kk1i$d7f$1@news.tpi.pl>  0 I'm sorry for not being clear in my last e-mail.   I would like to explain : G I want to connect a device to a "COM" PC computer port (special kind of E printer). I'd like to control the device (sending and receiving data)  throught Open VMS.   Regards, Olek Kolodziejczyk  E Uytkownik Olek Koodziejczyk <olekk@kki.net.pl> w wiadomoci do grup 0 dyskusyjnych napisa:99denm$r0h$1@news.tpi.pl...L > Is possibility communication with local PC computer ports "COM" from VMS ? I 3 > connecting via terminal program to VMS (from PC).  >  > Olek Kolodziejczyk >  >    ------------------------------  % Date: Sun, 25 Mar 2001 09:29:15 +0300 % From: Gabriel Sterk <gabi@aipm.co.il> Y Subject: Re: DECevent 3.3 abort with"_DIAGNOSE-FAT:  Automatic analysis is still running. 2 Message-ID: <001a01c0b4f4$eaa9f280$2c46bf10@manai>  P We have the same problem in our cluster. On one node, an ES40, Decevent 3.3 runs fine, L on another node, an Axp 4100, we get the the abort msg. As with other things which O don't pressure me, I just go around the problem and issue the DIAG command from  the @ node it works on, like:  DIAG $1$DGA1:[SYS1.SYSERR]ERRLOG.SYS  .   Regards,
 Gabriel Sterk   L P.s. I think DEQ suggests to use the 'COMPAQ ANALYZE" tool (but I'm not sure about that).   > -----Original Message-----) > From: Paul Sture [mailto:paul@sture.ch] & > Sent: Friday, March 23, 2001 8:00 PM > To: Info-VAX@Mvb.Saic.Com < > Subject: DECevent 3.3 abort with "_DIAGNOSE-FAT: Automatic > analysis is still running."  >  >  > Hi,  > " > Has anyone seen similar to this? >  > This on Alpha V7.2-1H1.  > = > Since installing DECEVENT 3.3, on one cluster it runs fine. 
 > On another,  > DIAGNOSE fails with: >  > DECevent V3.3 F > _DIAGNOSE-FAT:  Automatic analysis is still running. Please shutdown > and reissue command. > %SYSTEM-F-ABORT, abort > E > No DECevent process is running on the system. Even after performing ? > @SYS$STARTUP:DECEVENT$SHUTDOWN, the same message is produced.  > D > And, BTW, according to the release notes DIAG apparently now needs	 > SYSLCK.  > : > The DECEVENT startup log also contains the same message: >  > $ verify = 0 > $ completion_code = 1  > $ cfmg :== DIAGNOSE  > $ set default DIA$:[MANAGER]' > $ DEFINE/JOB SYS$LOGIN DIA$:[MANAGER] ) > $ DEFINE/JOB SYS$SCRATCH DIA$:[MANAGER] F > $ SET PROCESS/PRIVLEDGE=(NOALL,DIAGNOSE,TMPMBX,NETMBX,SYSLCK,SYSPRV) > $ SHOW PROCESS/QUOTA > > > 23-MAR-2001 15:53:36.08   User: SYSTEM           Process ID: >  2020045A @ >                           Node: MYNODE           Process name: > "DECevent_MYNODE"  >  > Process Quotas:  >  Account name: SYSTEM H >  CPU limit:                      Infinite  Direct I/O limit:       100H >  Buffered I/O byte count quota:     99424  Buffered I/O limit:     100H >  Timer queue entry quota:              19  Open file quota:         98H >  Paging file quota:                125280  Subprocess quota:        12H >  Default page fault cluster:           64  AST quota:              324H >  Enqueue quota:                      2000  Shared file limit:        0H >  Max detached processes:                0  Max active jobs:          0 > $ cfmg start MYNODE  >  > DECevent V3.3 F > _DIAGNOSE-FAT:  Automatic analysis is still running. Please shutdown > and reissue command. > %SYSTEM-F-ABORT, abort: >   SYSTEM       job terminated at 23-MAR-2001 15:53:36.21 >  >   Accounting information: F >   Buffered I/O count:                108      Peak working set size: > 6400B >   Direct I/O count:                   22      Peak virtual size: > 176448@ >   Page faults:                       476      Mounted volumes: > 0 E >   Charged CPU time:        0 00:00:00.14      Elapsed time:       0 
 > 00:00:00.33  > ? > I think my next step is to investigate quotas, but I wondered  > if anyone  > else has seen this.  > ___  > Paul Sture
 > Switzerland    ------------------------------   Date: 25 Mar 2001 08:08:39 GMT- From: djweath@attglobal.net (Dave Weatherall) , Subject: Re: POSIX Streams, File Permissions5 Message-ID: <DTiotGxQ0bj6-pn2-jP6b51dbsywg@localhost>   B On Fri, 23 Mar 2001 23:20:16, Christof Brass <brass@infopuls.com>  wrote:   > Dave Weatherall wrote: .. > > E > > > But why "real, stupid" ("Unix/Posix case-sensitive file name")? @ > > > Is it stupid to make a difference between "MAC" and "Mac"? > > G > > Chris it does sound a little incongruous for someone who dislikes C I > > and Unix to imply that they consider case sensitivity in names (ala C   > > and Unix) a 'good' thing :-) > > D > > I don't think it a good thing but then again I do Fortran  for a > > living.  ..@ > Dislike is a very friendly word and a strong understatement to > say the least.= > Again: I like case sensitivity in filenames sometimes but I B > don't like all sorts of characters in filenames. But what I like: > is not important because only the case sensitivity has aA > technical background. E.g. there are programming languages that = > take Mac and MAC as beeing different. To have the option to 0 > adjust this per directory may be very usefull.   Point taken and understood.    Cheers - Dave.   ------------------------------    Date: 25 Mar 2001 12:53:29 -00004 From: Doc.Cypher <Use-Author-Address-Header@[127.1]>, Subject: Re: POSIX Streams, File Permissions6 Message-ID: <20010325125329.23838.qmail@nym.alias.net>  " -----BEGIN PGP SIGNED MESSAGE-----  8 On 24 Mar 2001, carl@gerg.tamu.edu (Carl Perkins) wrote:   <snip>  @ >Case sensitivity in filesystems (which, in Unixoid systems also@ >leads directly to case sensitivity in commands) is also stupid.G >Why should either the computer or I care if I type in "print foo.txt", B >"Print Foo.Txt", "PRINT foo.TXT", or any of the other of the 2^11D >possible variations? In all of these cases I just want to print the >text file called foo.    J For what it's Wirth, surely you wanted to print the file formerly known as FOO.TXT      Doc.   -----BEGIN PGP SIGNATURE-----  Version: 2.6.2  @ iQEVAwUBOr0m8sriC3SGiziTAQELTgf8CnD9WFto4iNLGmW1YeoXkabWWYMHbCa1@ dZYOYp+A+r+EUtzXxQL9mmM1WMM1GVoWtCcQobGPxvQvqAMF9QhbVh3qWbNw9eI2@ GYSTTinoWiCzxrBpgqDopMuycd/vVPO+ynF/YgbC5AMJgcKf9gy6vKQBUF0qCheG@ rhWD6JQ//uBH4ic5DgQuJJTF7c7n5vD+GZCysAs21BWtgaGIqgdwzNv4DWq4aGRi@ lCI2sCwGPk2Yjm0TNodb2Sbe3LXKNvcaiSR1thv2E1vdzGMBo6fZ1ib/U28cERWv8 1uCjb12nPbPZHm0mEcsEFbkG62lq66Wdzl2iehwcUc9mwylw+4VPeQ== =RKXg  -----END PGP SIGNATURE-----    ------------------------------    Date: 25 Mar 2001 20:52:44 +0800, From: Paul Repacholi <prep@prep.synonet.com>, Subject: Re: POSIX Streams, File Permissions- Message-ID: <87ofuqko2r.fsf@prep.synonet.com>   + Christof Brass <brass@infopuls.com> writes:   = > Again: I like case sensitivity in filenames sometimes but I B > don't like all sorts of characters in filenames. But what I like: > is not important because only the case sensitivity has aA > technical background. E.g. there are programming languages that = > take Mac and MAC as beeing different. To have the option to 0 > adjust this per directory may be very usefull.  C Excuse me? You want to change a fundermental part of the DCL syntax F (what is a file-spec) and have it changed because of what is or is not in some directory today?   Now I've heard everthing.    --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.   ------------------------------    Date: 26 Mar 2001 01:21:50 +0800, From: Paul Repacholi <prep@prep.synonet.com>, Subject: Re: POSIX Streams, File Permissions- Message-ID: <877l1dlq6p.fsf@prep.synonet.com>   6 Doc.Cypher <Use-Author-Address-Header@[127.1]> writes:  F > >possible variations? In all of these cases I just want to print the > >text file called foo.   > L > For what it's Wirth, surely you wanted to print the file formerly known as	 > FOO.TXT   % But it is probably of little Wirth :)    --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.   ------------------------------  % Date: Sun, 25 Mar 2001 16:00:53 +0200 " From: "Dirven" <tdn36618@tijd.com># Subject: Printing jpeg files on VMS 9 Message-ID: <EBnv6.5474$yz3.173937@iguano.antw.online.be>    Hello,  & I have many JPG files on my VMS-disks.  1 Is it possible to print these files to a printer.   ) $ print/queu=printer1 photo.jpg ....... ?   ! I don't have postscript printers.   ! I only have "pcl based" printers.   
 Best regards,   	 T. Dirven  Belgium    ------------------------------   Date: 24 Mar 2001 21:59:16 CDT= From: wayne@tachysoft.xxx.412538.killspam.015a (Wayne Sewell) 5 Subject: Re: Problem Booting Installed VMS 7.2 System . Message-ID: <V4ZlKSR28iNk@tachxxsoftxxconsult>  Q In article <7%1v6.677$ya4.355429@nntp2.onemain.com>, <tsm@palindrome.org> writes: J > A co-worker of mine gave me a DEC 3000-300XL system. It had DIGITAL Unix0 > installed on it, and I installed VMS over it.   M I have seen this with other formerly enunuchs systems.  I guess their default # boot flags must be a,0.  See below.    >I have the Hobbyist Alpha CD N > (VMS version 7.2), and installed it from an RRD42. The install process seemsM > to go OK, but when I try to boot the hard drive which I installed VMS on, I  > get the following error: > H > %APB-F-BADSYSROOT, System root [SYSA.] does not exist, check bootflags >     K It says to check the boot flags.  That's exactly where the problem is.  The  boot flags should be 0,0.     
 If you do   
 b -fl 0,0    the system will come up.    N The first number is the system root.  It is normally 0 for [sys0.], though youM can alternatively specify 1 for [sys1.], 2 for [sys2.], and so on.  Your boot N flags are obviously set to a,0, so the console is trying to find the operatingG system in root [sysa.], which normally does not exist on a system disk.       ! To make it a permanent change, do    set boot_osflags 0,0  2 and you can boot without the -fl 0,0 from then on.  O Note: this is on an alphastation 200.  It's probably the same for the 3000.  If L you do a "sho boot*", you should see the correct name with the current value (probably a,0 at the moment).     L > I tried installing three different times in total. Twice with the standardH > RZ25L disk, and one with a generic 1GB disk. (I thought maybe it was aE > problem with the disk). In all cases, I get the exact same problem.   L It has nothing to do with the disk or with the operating system installed on it.  It's in the console.V  M > I have the newest console revision (V7.0) and PAL code (V5.56) installed ons0 > the system. Everything seems to be up to date.  E Nothing is wrong with the console code, just the values stored in thet non-volatile memory.  L > Any clues on this one? I searched the web & Usenet for that error message,K > and got only one hit - somebody who was trying to boot a non-bootable CD.m4 > How could that error apply to a hard drive bootup?    L The console makes no distinction between cdroms and disks when booting.   InP case of the non-bootable CDROM, the operating system is not on the disk at all. N In your case, the operating system is not located where the console boot flagsE say it will be.  Either way, the console can't find the system root. -     -- -O ===============================================================================:M Wayne Sewell, Tachyon Software Consulting  (281)812-0738  wayne@tachysoft.xxxp: http://www.tachysoft.xxx/www/tachyon.html and wayne.html  K change .xxx to .com in addresses above, assuming you are not a spambot  :-)EO =============================================================================== O Dean Wormer to Flounder: "Fat, drunk, and stupid is no way to go through life."u   ------------------------------  + Date: Sun, 25 Mar 2001 11:26:30 +0000 (UTC)e9 From: Roar =?iso-8859-1?Q?Thron=E6s?= <roart@nvg.ntnu.no> * Subject: Re: VMS source listings omittings- Message-ID: <99kkl6$pjj$1@tyfon.itea.ntnu.no>   , Richard Jordan <rjordan@mars.mcs.net> wrote:H : Of course if you really want to see all the expurgated source, all youI : might have to do is get a job at microsoft in Redmond, who received all   F I was tempted to mention Microsoft myself, but did not want this to be a long thread.  - : the good stuff almost free some time ago ;)/  E (Among them sensitive algorithms, trade secrets, very innovative codeS and patent pending code.)Z  E Did not Compaq and Microsoft exchange code giving the other part fullQH rights of utilization? (Maybe apart from Microsoft making VMS and Compaq making Windows)vI The recent Advanced Server for OpenVMS is supposedly based on source codew from Microsoft. F I do not know whether Microsoft has had any use of the VMS source, butE would be delighted to know. (It would possibly require major redesignoC and code changes in Windows' already too large code base, maybe tool late in the life of the OS?)E Sun supposedly(?) got the Windows source via AT&T, but could they get7< the VMS source the same way? (That could be more dangerous?)  M I have heard rumours saying that VMS 1.0 was planned with clustering in mind.>C Clusters came after 5 years in 1983, but 5 years then were "slower" D with regard to development than now. An eventual redesign/rewrite of/ the sources might not have been that extensive. = Redesign of Unix and Windows might not be that easy, or what?m   --  
 -Roar Throns-   ------------------------------    Date: 26 Mar 2001 00:31:47 +0800, From: Paul Repacholi <prep@prep.synonet.com>* Subject: Re: VMS source listings omittings- Message-ID: <87k85dlsi4.fsf@prep.synonet.com>   ( Roar Throns <roart@nvg.ntnu.no> writes:  F > I have heard rumours saying that VMS 1.0 was planned with clusteringF > in mind.  Clusters came after 5 years in 1983, but 5 years then were; > "slower" with regard to development than now. An eventual E > redesign/rewrite of the sources might not have been that extensive.a? > Redesign of Unix and Windows might not be that easy, or what?2  A I doubt that. V1 was just enought to get going. Many of the utilsj where still RSX ones.t  @ The key steps to clustering where MSCP with the UDA-50 and later@ CI-780 and HSC50, then the lock manager and the $enq $deq systemB sevices. Another big factor was the class/port driver idea.  These< where in VMS before V4.  At that point, the lock manager was distributed and away it went...   D MSCP and sharing a HSC was possible in 3.x. With V4, you could share% dual port Massbus drives as well btw.   E The lack of this in V1 can be seen by the fact that the IRP had to beoB extended to the CDIRP to get the IO system to sing. V1 was kept to= what was needed to get a 32 bit paging system out and usable.    --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.   ------------------------------  # Date: Sun, 25 Mar 2001 12:48:26 GMT = From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)n5 Subject: Re: Will the VIOC be fixed in VMS Alpha 7.3? 0 Message-ID: <009F9888.7026F3BB@SendSpamHere.ORG>  P In article <3ABD4114.2150D591@wi.rr.com>, Scott Vieth <svieth@wi.rr.com> writes: >Hi: >dF >Currently, the size of the VIOC on VMS Alpha is fixed at VCC_MAXSIZE.H >I thought I read a while back that a future version of VMS was going to? >let the VIOC grow and shrink as the system needed memory (like  >the VIOC does on VMS VAX).  >iA >Is this fixed in VMS Alpha 7.3 or do I need to wait for a futurej	 >version?  >  >Thanks, >e >-Scott :^)  >G  I Not really "fixed" bu revamped.  The eXtended File Cache (XFC) will be intI V7.3 and replaces the VIOC.  It's a far better caching system and reportsi$ to cache much more file system data.  u --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM             2O city, n., 1. a place where trees are cut down and streets are named after them.c   ------------------------------  % Date: Sun, 25 Mar 2001 13:36:24 -0500@2 From: norm lastovica <norman.lastovica@oracle.com>5 Subject: Re: Will the VIOC be fixed in VMS Alpha 7.3?o* Message-ID: <3ABE3AA8.6D8D3E21@oracle.com>  & "Brian Schenkenberger, VAXman-" wrote: > R > In article <3ABD4114.2150D591@wi.rr.com>, Scott Vieth <svieth@wi.rr.com> writes: > >Hi: > > H > >Currently, the size of the VIOC on VMS Alpha is fixed at VCC_MAXSIZE.J > >I thought I read a while back that a future version of VMS was going toA > >let the VIOC grow and shrink as the system needed memory (likev > >the VIOC does on VMS VAX).m > > C > >Is this fixed in VMS Alpha 7.3 or do I need to wait for a future  > >version?2 > K > Not really "fixed" bu revamped.  The eXtended File Cache (XFC) will be inDK > V7.3 and replaces the VIOC.  It's a far better caching system and reports & > to cache much more file system data.  4 	I've been field testing various 7.3 base levels for= quite some time now.  I have had very good luck with the XFC.,> It caches way more data, self-tunes, doesn't use S0/S1 address; space, etc. etc. etc.  I'd think that for some systems, XFCu0 would be plenty enough reason to upgrade to 7.1.8 	Here's an example SHOW MEMORY/CACHE from my just-booted	 desk-top:t   TNA23:> sho mem/caches@               System Memory Resources on 25-MAR-2001 13:30:14.15  B Extended File Cache  (Time of last reset:  5-FEB-2001 17:59:48.22)N     Allocated (Mbytes)           66.55    Maximum size (Mbytes)         128.00N     Free (Mbytes)                 0.12    Minimum size (Mbytes)           0.23O     In use (Mbytes)              66.42    Percentage Read I/Os              88%hO     Read hit rate                   91%   Write hit rate                     0%nN     Read I/O count             1433372    Write I/O count               192133N     Read hit count             1314257    Write hit count                    0N     Reads bypassing cache          746    Writes bypassing cache           471N     Files cached open              462    Files cached closed              559N     Vols in Full XFC mode            0    Vols in VIOC Compatible mode       3N     Vols in No Caching mode          0    Vols in Perm. No Caching mode      0   ------------------------------   End of INFO-VAX 2001.168 ************************