1 INFO-VAX	Wed, 11 Apr 2001	Volume 2001 : Issue 203       Contents: Re: 3rd party memory products  Access Mode  Re: Access Mode  Re: Access Mode  Re: Access Mode  Re: Access Mode  Re: Access Mode  Re: Another Win for OpenVMS  Re: Another Win for OpenVMS  Re: Another Win for OpenVMS " Re: Charlie Matco's US Mirror Site+ Re: CI based cluster for max I/O perf. How? + RE: CI based cluster for max I/O perf. How?  Re: Corba on OpenVMS AXP2 Re: Flipping from big-endian to little endian in C2 Re: Flipping from big-endian to little endian in C Re: FTP hijacking of VMS sites. Re: Help needed with RMS Character Field Index0 Re: HELP: Problem in DEC BASIC reading IP Socket0 Re: How can I get the hardware-id number(newbie)0 RE: How can I get the hardware-id number(newbie)0 Re: How can I get the hardware-id number(newbie)0 RE: How can I get the hardware-id number(newbie)0 Re: How can I get the hardware-id number(newbie) Re: How not to add patches. How to set the date format for insert statment Re: KZPCA-AA Works fine !  Re: KZPCA-AA Works fine ! ( Re: London, England Technical Update Day+ NetBackUp / MultiNet - does the combo work?  RE: NSA is Linux not OpenVMS RE: NSA is Linux not OpenVMS6 Re: OpenVMS Frequently Asked Questions (FAQ), Part 3/56 Re: OpenVMS Frequently Asked Questions (FAQ), Part 3/56 Re: OpenVMS Frequently Asked Questions (FAQ), Part 3/56 Re: OpenVMS Frequently Asked Questions (FAQ), Part 3/56 Re: OpenVMS Frequently Asked Questions (FAQ), Part 3/56 Re: OpenVMS Frequently Asked Questions (FAQ), Part 3/53 Re: Q: Converting a VAX 6000-420 to a VAX 6000-620? 3 Re: Q: Converting a VAX 6000-420 to a VAX 6000-620? = Re: Rumour Has It That CHARLIE MATCO HAS RISEN FROM THE GRAVE 
 Silent Sun Re: Silent Sun Re: Silent Sun Re: Silent Sun Re: Silent Sun Re: Silent Sun SMP_SPINWAIT3 Re: Solaris tmpfs (was Re: VMS-Related: Affordable) 3 Re: Solaris tmpfs (was Re: VMS-Related: Affordable) 3 Re: Solaris tmpfs (was Re: VMS-Related: Affordable) 3 Re: Solaris tmpfs (was Re: VMS-Related: Affordable) 3 Re: Solaris tmpfs (was Re: VMS-Related: Affordable) 3 Re: Solaris tmpfs (was Re: VMS-Related: Affordable) 3 Re: Solaris tmpfs (was Re: VMS-Related: Affordable) 3 Re: Solaris tmpfs (was Re: VMS-Related: Affordable) 3 Re: Solaris tmpfs (was Re: VMS-Related: Affordable) 7 Re: strange behaviour of DIRECTORY with long file names 7 Re: strange behaviour of DIRECTORY with long file names 7 Re: strange behaviour of DIRECTORY with long file names ' Re: Upgrading a 4000/60 the easy??? way  Re: VMS friendly website??? @ Re: Why set PYHSICALPAGES? (was: [Q] Adding Memory to a MV 3100)@ Re: Why set PYHSICALPAGES? (was: [Q] Adding Memory to a MV 3100) [INFO] apologies [Q] %SYSTEM-I-BOOTUPGRADE  Re: [Q] %SYSTEM-I-BOOTUPGRADE   F ----------------------------------------------------------------------  % Date: Wed, 11 Apr 2001 11:09:45 -0400   From: jamese@beast.dtsw.army.mil& Subject: Re: 3rd party memory products0 Message-ID: <01041111094588@beast.dtsw.army.mil>  J "john nixon" <jnixon@cfl.rr.com> wrote on Tue, 10 Apr 2001 11:54:35 GMT in2 <%vCA6.13574$nD5.2393324@typhoon.tampabay.rr.com>:  M > I buy VMS systems because VMS is reliable.  With that in mind, I don't want M > to risk my data integrity by scrimping on memory.  However, paying a factor 5 > of 12 times more for Compaq memory seems excessive.  > L > A 4GB memory option from Compaq for an ES40 costs over $51,000.  I can buyM > similar memory from DataRam for about 1/12th of that.  Since I need four of H > these 4GB options, that adds up to a whole lot of money.  If I buy theL > DataRam memory, I can buy a 4GB option or two for spares.  Can anyone giveK > me any logical reasons for not doing this?  I have very little experience I > with 3rd party memory in Alpha VMS systems.   It seems 3rd party memory K > prices have come down a lot recently, but not Compaq's.  Is Compaq so big J > and slow that they cannot react to market conditions?  If so, that would > explain a lot.  H I have used 3rd party memory in several systems, with excellent results.' Howerver, here are some considerations:   E -> Field Service - I have not had Compaq FS, DEC FS, or Bell Atlantic F    (when they were in the business) refuse to service a processor justF    because it had foreign memory.  They probably will not give you any@    service if it is an obvious memory error. There can be fingerC    pointing if the error is not easily diagnosed. You might want to 5    retain a set of Compaq memory for error diagnosis.   B -> If there is a memory error, you may have to send it back to theC    vendor for replacement. Whether they send you one as soon as you =    call and do not wait to receive the bad part is up to your 2    relationship.  You may want to by a backup set.  : Ed James                           ed.james@telecomsys.com5 TeleCommunications Systems, Inc.   voice 410-295-1919 ; 2024 West Street, Suite 300              800-810-0827 x1919 5 Annapolis, MD 21401-3556           fax   410-280-1094    ------------------------------  % Date: Wed, 11 Apr 2001 09:58:09 +0000 ; From: Lai King Leung <laikingLeung@streetmanagement.org.uk>  Subject: Access Mode= Message-ID: <2C9B186BDAA4D4118F2A009027620DA101079B9C@GEORDI>    Hi    G I'm trying to set the access mode attribute in the system call function @ sys$crelnm.  I want to create my logical with supervisor mode - L PSL$C_SUPER.  ( I have full system manager privileges on my system).  When I compile the program I get   K     status = SYS$CRELNM( 0, &log_table_dsc, &monthly_log_dsc, PSL$C_SUPER ,  &loglist ); > .............................................................^A %CC-E-UNDECLARED, In this statement, PSL$C_SUPER is not declared.  at line number 57 in file ...   E What header file do I need to resolve this - platform is Cpmpaq Alpha  running Open VMS v6.2 ?   . I tried seeting the value manually as follows:   int acmode = 2; C status = SYS$CRELNM( 0, &log_table_dsc, &monthly_log_dsc, (unsigned  char*)acmode, &loglist );   : This compiled but on running I got an access violation !!!   Regards  Lai King/ * : mailto:laikingleung@streetmanagement.org.uk    ------------------------------  % Date: Wed, 11 Apr 2001 05:24:25 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca>  Subject: Re: Access Mode, Message-ID: <3AD422C7.8CD64E51@videotron.ca>   Lai King Leung wrote: C > %CC-E-UNDECLARED, In this statement, PSL$C_SUPER is not declared.  > at line number 57 in file ...  > - > What header file do I need to resolve this     try #include <psldef.h>    ------------------------------    Date: 11 Apr 2001 14:41:18 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de>  Subject: Re: Access ModeH Message-ID: <y41yqzlic1.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  B Also, you have to pass the access mode by value, not by reference.   	Jan   ------------------------------  % Date: Wed, 11 Apr 2001 08:20:58 -0600 = From: Arlen Williams <remove.arlen.williams@remove.sabre.com>  Subject: Re: Access Mode0 Message-ID: <3AD413E9.41FA4237@remove.sabre.com>   Lai King Leung wrote:  > 0 > I tried seeting the value manually as follows: >  > int acmode = 2; E > status = SYS$CRELNM( 0, &log_table_dsc, &monthly_log_dsc, (unsigned  > char*)acmode, &loglist );  > < > This compiled but on running I got an access violation !!! > 	 > Regards 
 > Lai King  D You needed (unsigned char *) &acmode as the paramater. It needed the address of acmode.   Arlen    ------------------------------  # Date: Wed, 11 Apr 2001 15:50:42 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) Subject: Re: Access Mode2 Message-ID: <m3%A6.787$fB6.19929@news.cpqcorp.net>  { In article <2C9B186BDAA4D4118F2A009027620DA101079B9C@GEORDI>, Lai King Leung <laikingLeung@streetmanagement.org.uk> writes:   H :I'm trying to set the access mode attribute in the system call functionA :sys$crelnm.  I want to create my logical with supervisor mode -  M :PSL$C_SUPER.  ( I have full system manager privileges on my system).  When I  :compile the program I get : L :    status = SYS$CRELNM( 0, &log_table_dsc, &monthly_log_dsc, PSL$C_SUPER , :&loglist );? :.............................................................^ B :%CC-E-UNDECLARED, In this statement, PSL$C_SUPER is not declared. ..       You could use      #include <psldef.h>   C   To find a definition, you can search the Compaq C (or DEC C) text D   file reference area in SYS$SYSROOT:[DECC$LIB...] for the symbol(s)   in question.  C   That said, a far better solution -- and a solution that does not  E   require the user to have very powerful privileges -- is to use the  E   existing lib$set_logical call to define the specified logical name     in supervisor mode.      :int acmode = 2;D :status = SYS$CRELNM( 0, &log_table_dsc, &monthly_log_dsc, (unsigned :char*)acmode, &loglist ); ..; :This compiled but on running I got an access violation !!!   C   Probably at PC address 2, if you check the ACCVIO arguments.  You D   will want to pass acmode by reference.  There may well be another A   problem with the itemlist, but insufficient information on that    argument was included.  -   In summary, I'd use lib$set_logical here...   N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Wed, 11 Apr 2001 10:06:09 -0700 ! From: Shane.F.Smith@Healthnet.com  Subject: Re: Access ModeD Message-ID: <OF505C6526.0DE93A61-ON88256A2B.005DC5C4@foundation.com>  K I got fed up trying to track this kind of stuff down, so I set up a logical K pointing to DEC C's reference copy header files. Now one solution fits all: K SEARCH DECC_INCLUDE:*.H {whatever}. Trivial fix, but it does save me grief.    Shane           A JF Mezei <jfmezei.spamnot@videotron.ca> on 04/11/2001 02:24:25 AM   9 Please respond to JF Mezei <jfmezei.spamnot@videotron.ca>    To:   Info-VAX@Mvb.Saic.Com  cc:    Subject:  Re: Access Mode      Lai King Leung wrote: C > %CC-E-UNDECLARED, In this statement, PSL$C_SUPER is not declared.  > at line number 57 in file ...  > , > What header file do I need to resolve this   try #include <psldef.h>    ------------------------------   Date: 11 Apr 2001 07:40:03 CDT= From: wayne@tachysoft.xxx.065234.killspam.015d (Wayne Sewell) $ Subject: Re: Another Win for OpenVMS. Message-ID: <tArVokUFnNCG@tachxxsoftxxconsult>  Q In article <3AD34DE3.BC93094D@hsc.vcu.edu>, Jim Agnew <Agnew@hsc.vcu.edu> writes: Q > Also for faster surfin', and to KILL ALL THE AD SITES..  see the following url.  > ! > http://www.smartin-designs.com/  >  > the gist of it is to modify your c:\windows\hosts file to set the dns entries for the known ads and spammers to 0.0.0.0 and voila!!! >  > it makes my pc unstable, tho..  there is another ip address they use, but my pc then hangs while trying to resolve those..  however  > on a faster machine... >     N I do this on my vms machines.  I don't use 0.0.0.0, however.  I use an address; that is valid for my subnet, but doesn't have a web server.   N The problem with the domain name approach is that it filters only a portion ofI the ads, those from sites that are nothing *but* ads, such as the dreaded O ads.doubleclick.net.  In other words, the ads have a domain name different from N the material you want to see.  In many cases, the majority of the cases as farO as I can see, the ads are kept directly on the server maintaining the web page, L as in "http://site.you.want/ads/promo1.jpg".  If you disable the ip address,L you get rid of the ads, but you can no longer access the web site at all, so what difference does it make?   N It has been my experience that domain-name-based filtering is largely useless.M Most of the ads come straight through to get in your face.  Filtering works a & hell of a lot better at the URL level.  M I use Internet Junkbuster and I love it.  I rarely see the muhfugging ads any L more.  Junkbuster is basically a proxy server whose whole purpose in life isM filtering ads.  It scans the urls as they go by, and matches them with common O ad patterns in a configuration file.  When it sees a url that appears to be the M jpeg for an ad, it doesn't pass it though.  Instead, you see either the empty N space where the ad would have been or the broken-jpeg icon, depending on whichM variant of junkbuster you are using.  Either way, you don't the the annoying, 6 possibly resource wasting (if animated) advertisement.  L Another advantage of using a proxy server filter is that browsers on all theB machines in the network can use it.  I get rid of the ads both forI netscape/mozilla on vms and the billybox browser.  I don't use the latter < unless I have to, but when I do, the ads are gone there too.  L Junkbuster is the sole reason I have a machine running linux.  That and SETID are the only two programs running on zeppo, my lone linux machine.    H Junkbuster is available as a linux RPM, both the regular version and theF blanking version.  I think it's on the redhat list, so if you run thatJ automatic RPM downloader program, you should see it.  There's also a billyM version of junkbuster, but it didn't seem to work as reliably.  (So what else = is new?  How can anything work reliably in that environment?)      www.junkbusters.com          --  O =============================================================================== M Wayne Sewell, Tachyon Software Consulting  (281)812-0738  wayne@tachysoft.xxx : http://www.tachysoft.xxx/www/tachyon.html and wayne.html  K change .xxx to .com in addresses above, assuming you are not a spambot  :-) O =============================================================================== B Jed Clampett, checking into hotel: "This place got a cement pond?"+ Ellie May: "And do yuh let critters in it?"    ------------------------------  % Date: Wed, 11 Apr 2001 09:04:52 -0400 # From: Jim Agnew <Agnew@hsc.vcu.edu> $ Subject: Re: Another Win for OpenVMS+ Message-ID: <3AD45674.FDEC04B6@hsc.vcu.edu>   z I was having LOTS of problems with Netscape 4.7, then upgraded to 4.77, and now it's LOTS better.  must be the sunspots...   "David J. Dachtera" wrote: >  > "Terry C. Shannon" wrote: 
 > > [snip]K > > Ah, Netscape... the browser for crash test dummies. I used to use it on P > > Windoze, but got sick of the multiple daily browser crashes and went over toB > > Internet Exploder. At least it is more reliable than Netscape. >  > In what reality? > F > I've seen IE do stupid things that NS is too smart to even THINK of! > I > ...like forgetting how to go back or forward because it forgot where it = > came from or where it had been but went back at my request.  > F > Then again, I've seen NS hose up WhineBloze so bad you couldn't even/ > shut it down (no big accomplishment, really).  >  > -- > David J. Dachtera  > dba DJE Systems  > http://www.djesys.com/ > < > Unofficial Affordable OpenVMS Home Page and Message Board:! > http://www.djesys.com/vms/soho/  > H > This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings > is to be expected. > B > Feel free to exercise your rights of free speech and expression. > H > However, attacks against individual posters, or groups of posters, are > strongly discouraged.    ------------------------------  % Date: Wed, 11 Apr 2001 09:15:02 -0400 # From: Jim Agnew <Agnew@hsc.vcu.edu> $ Subject: Re: Another Win for OpenVMS* Message-ID: <3AD458D6.A9EEAFB@hsc.vcu.edu>   hey, Thanks!!!!    Jim...   Wayne Sewell wrote:  > S > In article <3AD34DE3.BC93094D@hsc.vcu.edu>, Jim Agnew <Agnew@hsc.vcu.edu> writes: S > > Also for faster surfin', and to KILL ALL THE AD SITES..  see the following url.  > > # > > http://www.smartin-designs.com/  > >  > > the gist of it is to modify your c:\windows\hosts file to set the dns entries for the known ads and spammers to 0.0.0.0 and voila!!! > >  > > it makes my pc unstable, tho..  there is another ip address they use, but my pc then hangs while trying to resolve those..  however  > > on a faster machine... > >  > P > I do this on my vms machines.  I don't use 0.0.0.0, however.  I use an address= > that is valid for my subnet, but doesn't have a web server.r > P > The problem with the domain name approach is that it filters only a portion ofK > the ads, those from sites that are nothing *but* ads, such as the dreaded Q > ads.doubleclick.net.  In other words, the ads have a domain name different fromoP > the material you want to see.  In many cases, the majority of the cases as farQ > as I can see, the ads are kept directly on the server maintaining the web page,eN > as in "http://site.you.want/ads/promo1.jpg".  If you disable the ip address,N > you get rid of the ads, but you can no longer access the web site at all, so > what difference does it make?  > P > It has been my experience that domain-name-based filtering is largely useless.O > Most of the ads come straight through to get in your face.  Filtering works a ( > hell of a lot better at the URL level. > O > I use Internet Junkbuster and I love it.  I rarely see the muhfugging ads anytN > more.  Junkbuster is basically a proxy server whose whole purpose in life isO > filtering ads.  It scans the urls as they go by, and matches them with commonoQ > ad patterns in a configuration file.  When it sees a url that appears to be the O > jpeg for an ad, it doesn't pass it though.  Instead, you see either the emptysP > space where the ad would have been or the broken-jpeg icon, depending on whichO > variant of junkbuster you are using.  Either way, you don't the the annoying,t8 > possibly resource wasting (if animated) advertisement. > N > Another advantage of using a proxy server filter is that browsers on all theD > machines in the network can use it.  I get rid of the ads both forK > netscape/mozilla on vms and the billybox browser.  I don't use the latterS> > unless I have to, but when I do, the ads are gone there too. > N > Junkbuster is the sole reason I have a machine running linux.  That and SETID > are the only two programs running on zeppo, my lone linux machine. > J > Junkbuster is available as a linux RPM, both the regular version and theH > blanking version.  I think it's on the redhat list, so if you run thatL > automatic RPM downloader program, you should see it.  There's also a billyO > version of junkbuster, but it didn't seem to work as reliably.  (So what elsel? > is new?  How can anything work reliably in that environment?)f >  > www.junkbusters.coma >  > --Q > ===============================================================================aO > Wayne Sewell, Tachyon Software Consulting  (281)812-0738  wayne@tachysoft.xxx : > http://www.tachysoft.xxx/www/tachyon.html and wayne.htmlM > change .xxx to .com in addresses above, assuming you are not a spambot  :-)oQ > ===============================================================================-D > Jed Clampett, checking into hotel: "This place got a cement pond?"- > Ellie May: "And do yuh let critters in it?"d   ------------------------------    Date: 11 Apr 2001 15:57:22 -00004 From: Doc.Cypher <Use-Author-Address-Header@[127.1]>+ Subject: Re: Charlie Matco's US Mirror Site46 Message-ID: <20010411155722.19059.qmail@nym.alias.net>  " -----BEGIN PGP SIGNED MESSAGE-----  C On 10 Apr 2001, mathog@seqaxp.bio.caltech.edu (David Mathog) wrote:nK >In article <9atdqd$q89$1@pyrite.mv.net>, "Bill Todd" <billtodd@foo.mv.com>e >writes:L >>Whatever one may think of much of Andrew's verbiage, every once in a whileN >>he's right on the mark.  This post should be required reading for the entireK >>Compaq management chain.  On second thought, that's not likely to make anlK >>adequate impression:  they should be required to recite it in unison eachoL >>and every morning until corporate behavior makes it clear that the need to >>do so has expired. > I >Unfortunately the date of that expiration will almost certainly coincide I >with the end of Compaq.  (They're no worse than RP, so it will probably iA >take them the same 5-10 years to completely kill their company.)  >tF >Which is one reason why it's probably time to resuscitate freeVMS. OrH >rather, to make a really _OPEN_VMS,  that will run on nonQ platforms. IE >always felt that the hobbyist program was just a move to squish such L >development - and to get the people in this group to stop griping publicly.C >It didn't accomplish the latter but it did accomplish the former. s  K And it would seem that a little bit of advertising is the latest attempt toeJ shut down the griping. It won't work. COE may be life support for VMS, but* it isn't life as we would like to know it.     Doc.   -----BEGIN PGP SIGNATURE-----t Version: 2.6.2  @ iQEVAwUBOtI+8sriC3SGiziTAQFUpQf/YXZD31CwuX1d/z5HDsuLVC8S2ZeDTkqL@ wiDJK1O33Dp/i2L0PCBlyDcgpyTxDu5YlyR5ROcs7QLmoyGutKcvfWyCRKkzAp4L@ gS9c1uvhsWIbSjYabZpv1PqLyhQNBPWJZ45ceE1zTvhuq7HOfStk+YCrDRaTFIsr@ agbd18f9durCFWhLKjcGM8b8Rlaz+psQ25/6awbDo8ucPY7TnLMVLVS4CE+eoz/P@ 9eu3br85nX0dSqiPwoCk3+HOvFIV5IVsXPaAcgabqZT6Bbl/Qc208KCtXANZDC1X8 n5fwAooHbGD4wHpe4N9PgBoFjo1KKUUX0WV17RKDlkPYBckNGthPjA== =x38u  -----END PGP SIGNATURE------   ------------------------------    Date: 11 Apr 2001 10:01:23 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de>s4 Subject: Re: CI based cluster for max I/O perf. How?H Message-ID: <y4itkb6f1o.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  ) prosullivan@aol.com (PROSULLIVAN) writes:n  N > Note: with VMS you will need to check your disk cluster size - simple thingsL > like increasing that can reduce fragmentation and speed up IO accordingly.  N Other approaches to this problem are better. Do a suitable initial allocation,N use reasonable extent sizes, use Glenn Everhart's automatic extent calculator.   	Jan   ------------------------------  % Date: Wed, 11 Apr 2001 09:50:58 -0500 * From: WILLIAM WEBB <WWEBB1@email.usps.gov>4 Subject: RE: CI based cluster for max I/O perf. How?- Message-ID: <0033000021187609000002L092*@MHS>   8 =0AI've not seen this extent calculator and websearching is not proving fruitful.    Where, pray tell, is it located?   TIA    WWWebb   > -----Original Message-----1 > From: Info-VAX-Request@Mvb.Saic.Com at INTERNETl) > Sent: Wednesday, April 11, 2001 4:19 AM-D > To: Webb, William W Raleigh, NC; Info-VAX@Mvb.Saic.Com at INTERNET6 > Subject: RE: CI based cluster for max I/O perf. How? >: >c+ > prosullivan@aol.com (PROSULLIVAN) writes:o >n; > > Note: with VMS you will need to check your disk clustert > size - simple things> > > like increasing that can reduce fragmentation and speed up > IO accordingly.t >e< > Other approaches to this problem are better. Do a suitable > initial allocation,1= > use reasonable extent sizes, use Glenn Everhart's automatice > extent calculator. >c
 >      Jan >=   ------------------------------  % Date: Wed, 11 Apr 2001 13:15:19 +0200h$ From: "Jakob Erber" <erberj@post.ch>! Subject: Re: Corba on OpenVMS AXPb Message-ID: <3ad43cc8$1@hcwe67>-   Hi All,-  H thanks a lot for all your inputs. After all there are CORBA products for OpenVMS.< May be, it is of use for you, if I publish my findings here:  H - IONAs Orbix products is annouced to be avail on VMS in June, Java onlyJ - The well known TAO freeware Orb is ported to VMS by www.ociweb.com (C++)K - Critical Path (www.cp.net) seems to have a very interesting CORBA productc
 for VMS, too.)? - There is a port of the freeware C++ (and Python, I think) Orb!:    OmniOrb for VMS, which we already use with good results@ - And last but not least ww.ois.com has even a product for Ada95 (OrbExpress) for VMS   best regards   Jakobe        5 "Jakob Erber" <erberj@post.ch> schrieb im Newsbeitragn news:3ad167a4$1@hcwe67...cG > Despite all signs that OpenVMS will be there for a long time to come,  therecI > is still support missing for software, I find vital for an important OSn > plattform. >gK > For example, as far as I can see, there is no Corba product available for 3 > VMS, which offers proffessionell support as well.m >oL > There are some very good freeware Orbs, but can you use them for a mission > critical system? >  > best regards >t > Jakobm >g >    ------------------------------    Date: 10 Apr 2001 09:17:47 -0500- From: koehler@encompasserve.org (Bob Koehler).; Subject: Re: Flipping from big-endian to little endian in C,3 Message-ID: <yKC8NtEVv6Qv@eisner.encompasserve.org>   \ In article <3ACED07F.4CA8A637@videotron.ca>, JF Mezei <jfmezei.spamnot@videotron.ca> writes:N > I have to read a rather large amount of binary data (2 byte signed integers)1 > in C. The data is stored as big-endian shorts. b > P > If I have a entire row of 4800 big-endian signed shorts in consecutive memory,M > what would be the most efficient to flip all of them to litte-endian ? (VAXh > architecture, DEC-C).   G Check to see if MOVTC is implemented or emulated on the VAX in questionoJ (write sys$output f$getsyi("character_emulated").  Those which have MOVTC K can swap 512 bytes per instruction pretty fast.  Those which emulate MOVTC CG can't keep up with a simple loop (the emulator will do the loop for you   but trapping to it is overhead).  G The trick to this is to use a swap list (char array of 1, 0, 3, 2, ...)nE as the "input string", the input data as the "translation table", andaF the output data as the "output string", then build the 4800 shorts 512 bytes at a time.  H You can also swap bits using this technique.  Worked great on our 11/780E (MOVTC hardware suppport) but we stopped doing it when we switched to-  MicroVAX II's (MOVTC emulation).  F ----------------------------------------------------------------------? Bob Koehler                     | Computer Sciences Corporationm= NASA GSFC Flight Software       | Federal Sector, Civil GroupgE                                 | please remove ".aspm" when replying    ------------------------------  % Date: Wed, 11 Apr 2001 12:25:49 -0400n2 From: "John Gemignani, Jr." <john@ossc.DELETE.net>; Subject: Re: Flipping from big-endian to little endian in Cv+ Message-ID: <3ad48659$1@newsfeed.vitts.com>    You are correct, sir.e  L The (r1) points to one buffer and the (r2) to another.  I take that on blind faith.  ' Do I win the home game to take with me?X   ;)   -John   6 "Pat Rankin" <rankin@eql.caltech.edu> wrote in message( news:9APR200119482935@eql.caltech.edu.... > In article <3ad1e207$1@newsfeed.vitts.com>,\9 >  "John Gemignani, Jr." <john@ossc.DELETE.net> writes...o" > >> >     outbuf[i+1] = inbuf[i];I > >> >                           000C          movb    (r1)[r0],1(r2)[r0] " > >> >     outbuf[i] = inbuf[i+1];I > >> >                           0012          movb    1(r1)[r0],(r2)[r0]r > >n > >    Bug.t > >sH > >    The result would be two bytes of inbuf[i], as you didn't preserve [i+1]  > >    before overwriting it.f >,@ >      Thanks for playing, but the judges have just disqualifiedA > you for not reading the code you're commenting about.  There iso@ > no overwriting taking place; both the source and the generatedA > instructions illustrate that.  (You'll have to take it on faith,B > that the caller isn't passing the same array for both arguments.A > I don't know how many times I'm going to have to say that using A > separate input and output buffers lets you avoid copying things.A > into and back out of a temporary; this is the third so far....)  > ? >      And regarding an earlier response:  the Fortran compilerf@ > does generate better code for comparable source.  And the fact> > that it is allowed to assume that inbuf[] and outbuf[] don't> > overlap but the C compiler isn't appears not to matter here.> > However, I am using quite old versions of both compilers, so, > either of them could have improved by now. >t4 >                 Pat Rankin, rankin@eql.caltech.edu   ------------------------------  % Date: Wed, 11 Apr 2001 10:32:49 +0200f. From: stoeri@iap.tuwien.ac.at (Herbert Stoeri)' Subject: Re: FTP hijacking of VMS sitesa= Message-ID: <stoeri-1104011032490001@eapmc3.iap.tuwien.ac.at>i  I You can't prevent peopole from uploading junk, if you have an anonymouslyfG writable - e.g. [.incoming] - directory. The usual strategy would be to C make the incoming directory writable for an anonymous user, but notnH readable. A site administrator would periodically review the content andH move interesting stuff into an anonymously readable, but write protectedG directory, e.g. [.contrib]. While not preventing the upload of junk, itaJ makes this useless for the hijacker and protects you from beeing abused as( a distribution site for hacked software.    D In article <9alg6r$bt7$1@hecate.umd.edu>, bleau@umtof.umd.edu wrote:  I > Hello, folks.  I just noticed a lot of oddly named files - directories,yO > actually - in my system's anonymous ftp area.  They weren't created by anyoneoD > associate with our site.  One associate of mine gave me his guess: > A > i don't know if this is the case here, but i read articles from A > people who's anonymous ftp areas have been "hijacked" by peopleuA > distributing large files like movies.  typically, a 1MB file isrF > uploaded to check the speed.  if the hijacker thinks the speed is ok? > lots of directories are created and movie parts are uploaded.i > . > see http://www.macintouch.com/ftphijack.html > O > I think this subject deserves some discussion.  It's the first I heard of it,o1 > and I've been managing VMS systems for a while.h > O > Has anyone experienced this phenomenon?  Has is cropped up at VMS sites?  AreSB > there standard ways of combating it?  Should this be in the FAQ? >  > Lawrence Bleau > University of Maryland$ > Physics Dept., Space Physics Group > 301-405-6223 > bleau@umtof.umd.edu=  D +---------------------------------+--------------------------------+D | Herbert Stoeri                  | Phone: ++43(1)58801/13460      |D | Institut fuer Allgemeine Physik | Fax:   ++43(1)58801/13499      |D | Technische Universitaet Wien    | email: stoeri@iap.tuwien.ac.at |   ------------------------------    Date: 10 Apr 2001 09:27:44 -0500- From: koehler@encompasserve.org (Bob Koehler)t7 Subject: Re: Help needed with RMS Character Field Indexa3 Message-ID: <s6o40Xi1ULB5@eisner.encompasserve.org>   L In article <9asbl2$2uc$1@news.netmar.com>, Gabriel_hogan@hotmail.com writes: >  > Hi,hP > 	I have a sequential RMS file of fixed record length. I want to index the fileN > on a character field (third field, length 30, contains surnames). To do thisO > I need to extract the character field, reverse it and insert the new field atw< > the beginning of each record before indexing it with FDL.  > O > Has anyone had to do this before and if so, is there a VMS tool to do this orp > how did you go about it? l >   B The primary key of a keyed indexed file does not have to be at the% begining of the record.  Why move it?I  7 The key can be ascending or descending, why reverse it?b  H Sounds like you just need to write up the FDL for the keyed indexed file and convert/fdl.  F ----------------------------------------------------------------------? Bob Koehler                     | Computer Sciences Corporationi= NASA GSFC Flight Software       | Federal Sector, Civil Group E                                 | please remove ".aspm" when replying/   ------------------------------  % Date: Wed, 11 Apr 2001 11:49:58 -0600o4 From: "Michael D. Ober" <mdo.@.wakeassoc.com.nospam>9 Subject: Re: HELP: Problem in DEC BASIC reading IP Socketp2 Message-ID: <bP0B6.190$Xl1.301644@news.uswest.net>  L Thanks, that did it.  The code I copied has this same bug.  Fortunately, I'm' replacing that code with this new code.0 -- Thanks, 
 Mike Ober.  = "Randy Park" <rjpark@mindspring.com.nospaam> wrote in message - news:9b06ui$lk3$1@nntp9.atl.mindspring.net...e= > Pass IOSB by REF rather than LOC(IOSB).  For static stringsc; > the LOC function returns the address of the data, but fore9 > dynamic strings the LOC function returns the address ofT > the string header. >l? > Michael D. Ober <mdo.@.wakeassoc.com.nospam> wrote in message . > news:8eKA6.815$QA6.249639@news.uswest.net...L > > Sorry about not providing the IOSB structure.  I get all 0's in the IOSB > atD > > the end of this particular QIOW call and reuse the IOSB variable > throughout& > > this application with no problems. > >t > > ! IO STATUS BLOCK STRUCTURE  > > RECORD TYPE$_IOSB  > >      WORD CONDITIONn > >      WORD TRANSFER_COUNT > >      LONG INFO > > END RECORD TYPE$_IOSBs > > DECLARE TYPE$_IOSB IOSB  > >r > > -- > > Mike Ober. > >eC > > "Ruslan R. Laishev" <Laishev@SMTP.DeltaTel.RU> wrote in message,. > > news:3AD352F6.A183F7D5@SMTP.DeltaTel.RU... > > > How the IOSB is defined ?l > > >. > > >h > > > Michael D. Ober wrote: > > > >fK > > > > I am unable to get the number of bytes to return in the IOSB when I  > readK > > > > from a channel that has been created as an IP Socket.  All other IP 
 > > Socket > > > > QIO calls are working. > > > >m. > > > > =============== CODE ================= > > > > IPIN = "" F > > > > RETVAL = SYS$QIOW(0, CLIENT_SOCKET, IO$_READVBLK, LOC(IOSB), & > > > >             , , &s+ > > > >             LOC(IPIN), LEN(IPIN), &l > > > >             0, 0, 0, 0)t. > > > > ====================================== > > > >i# > > > > IPIN is defined as follows:t2 > > > >  COMMON (IPBUFFER) STRING IPOUT = 32000, &H > > > >                                          STRING IPIN     = 32000 > > > >cH > > > > All other calls to SYS$QIOW are correctly filling the IOSB.  Any > ideas? > > > >e
 > > > > -- > > > > Thanks,h > > > > Mike Ober. > > >a > > > -- > > > Cheers, Ruslan.sC > > > +---------------pure personal opinion-----------------------+t? > > >     RADIUS Server for OpenVMS project - www.radiusvms.comw< > > >       vms-isps@dls.net - Forum for ISP running OpenVMS@ > > >   Mobile: +7 (901) 971-3222, AIM nickname:"VMS hardworker" > >o > >t >  >s   ------------------------------  % Date: Wed, 11 Apr 2001 12:28:03 +0100   From: steven.reece@quintiles.com9 Subject: Re: How can I get the hardware-id number(newbie) H Message-ID: <OFF9286634.E32773B5-ON80256A2B.003E4CA0@qedi.quintiles.com>   David,J If you're getting a checksum error when keying in the license details thenJ it indicates that you transcribed something on the license PAK incorrectlyD when entering the license on your system.  The checksum verifies the1 information entered onto the system from the PAK.a Steve.   David M. Heller wrote:) >>>When requesting my hobbyist license ontG line(http://www.montagar.com/htbin/ohp_hobreg) it asks for a CPU serialdD number(it won't work unless I enter a number) When I get the licenseC back via by email it shows that number as being the hardware_id # IsA enter all the info exactly as shown in my email and I still get a G checksum error I've tried about every number that I can find inside the= case to no avail!= <<<=   ------------------------------  % Date: Wed, 11 Apr 2001 08:20:31 -0500 * From: WILLIAM WEBB <WWEBB1@email.usps.gov>9 Subject: RE: How can I get the hardware-id number(newbie) - Message-ID: <0033000021177688000002L082*@MHS>b  4 =0AIt is possible to edit the email into a .COM file6 and get it to the hobbyist system by hook or by crook.  < If you do the VMS licenses and the UCX license by hand, then4 you can FTP the one for the layered products over...   WWWebb   > -----Original Message-----1 > From: Info-VAX-Request@Mvb.Saic.Com at INTERNETe) > Sent: Wednesday, April 11, 2001 7:29 AM D > To: Webb, William W Raleigh, NC; Info-VAX@Mvb.Saic.Com at INTERNET; > Subject: RE: How can I get the hardware-id number(newbie)g >q >. > David,? > If you're getting a checksum error when keying in the license. > details then< > it indicates that you transcribed something on the license > PAK incorrectlyvF > when entering the license on your system.  The checksum verifies the3 > information entered onto the system from the PAK.g > Steve. >  > David M. Heller wrote:+ > >>>When requesting my hobbyist license on:> > line(http://www.montagar.com/htbin/ohp_hobreg) it asks for a > CPU serialF > number(it won't work unless I enter a number) When I get the licenseE > back via by email it shows that number as being the hardware_id # InC > enter all the info exactly as shown in my email and I still get a > > checksum error I've tried about every number that I can find > inside the > case to no avail!i > <<<e >=   ------------------------------    Date: 11 Apr 2001 08:47:51 -0500- From: koehler@encompasserve.org (Bob Koehler)o9 Subject: Re: How can I get the hardware-id number(newbie)o3 Message-ID: <xkeTBgG1C5kU@eisner.encompasserve.org>p  \ In article <3AD3D5CD.6104AD1E@videotron.ca>, JF Mezei <jfmezei.spamnot@videotron.ca> writes: > N > I beleive that the hobbyist licence program on the web does request that youP > enter the hardware ID of the target machine. If you are without one, I can see > how it would be difficult. >   C So what do you put in for Charon-VAX?  I'm under the impression the2B hobbyist version of Charon-VAX is supported under the hobbyist VMS license.  F ----------------------------------------------------------------------? Bob Koehler                     | Computer Sciences CorporationC= NASA GSFC Flight Software       | Federal Sector, Civil GroupXE                                 | please remove ".aspm" when replyinge   ------------------------------  % Date: Wed, 11 Apr 2001 10:26:33 -0500-* From: WILLIAM WEBB <WWEBB1@email.usps.gov>9 Subject: RE: How can I get the hardware-id number(newbie)i- Message-ID: <0033000021194882000002L022*@MHS>j  D =0AFor my Multia, I had to put in the number on the motherboard, and
 it worked.   YLMV (Your Licensing May Vary)   WWWebb   > -----Original Message-----1 > From: Info-VAX-Request@Mvb.Saic.Com at INTERNET ) > Sent: Wednesday, April 11, 2001 8:52 AMiD > To: Webb, William W Raleigh, NC; Info-VAX@Mvb.Saic.Com at INTERNET; > Subject: RE: How can I get the hardware-id number(newbie)b >i >i7 > In article <3AD3D5CD.6104AD1E@videotron.ca>, JF Mezeie* > <jfmezei.spamnot@videotron.ca> writes: >? > > I beleive that the hobbyist licence program on the web does0 > request that you; > > enter the hardware ID of the target machine. If you ares > without one, I can see > > how it would be difficult. > >L >*E > So what do you put in for Charon-VAX?  I'm under the impression thenD > hobbyist version of Charon-VAX is supported under the hobbyist VMS
 > license. >OH > ---------------------------------------------------------------------= -eA > Bob Koehler                     | Computer Sciences Corporationg? > NASA GSFC Flight Software       | Federal Sector, Civil Group H >                                 | please remove ".aspm" when replying=   >=   ------------------------------  % Date: Wed, 11 Apr 2001 13:05:40 -0400i% From: "John Vottero" <John@mvpsi.com> 9 Subject: Re: How can I get the hardware-id number(newbie)y/ Message-ID: <td93ndm0focedf@news.supernews.com>t  > "David M. Heller" <dheller1@rochester.rr.com> wrote in message* news:3AD3BC99.8D65DEF0@rochester.rr.com... > Thanks for the reply > ( > When requesting my hobbyist license onI > line(http://www.montagar.com/htbin/ohp_hobreg) it asks for a CPU serialoF > number(it won't work unless I enter a number) When I get the licenseE > back via by email it shows that number as being the hardware_id # IrC > enter all the info exactly as shown in my email and I still get abI > checksum error I've tried about every number that I can find inside the  > case to no avail!y >   K The hardware ID number on a license PAK has nothing to do with the hardwaret the PAK is used on.)  L If you are getting a checksum error when trying to register a PAK either youF entered something incorrectly or the e-mail was corrupted in it's tripI through the internet (or maybe they're generating bogus hobbyist PAKs but  that's doubtful).f  G The hobbyist e-mail is actually a DCL command procedure, extract it andb execute it.o   ------------------------------  % Date: Wed, 11 Apr 2001 08:26:46 -0400i7 From: David Beatty <David.Beatty@sasSPAMITUPTHEZZZ.com> # Subject: Re: How not to add patchesr2 Message-ID: <Dk3UOvyq8tIgge8uPENKutoyPf8N@4ax.com>  < Having recently performed this upgrade, if you had installed) as follows you would have had no problem:r       VMS721_PCSIp"     *** logout and log back in ***     VMS721_UPDATE )     *** all others using the wildcard ***   9 If you notice, just about every VMS V7.2-1 patch requires  the PCSI and UPDATE patches.   David R. Beatty0  D On 10 Apr 2001 17:52:30 -0500, kuhrt@encompasserve.org (Marty Kuhrt) wrote:  ? >I did a nifty job of shooting myself in the foot last week.  IE@ >thought I'd share my adventures so that others may not limp so. >e< >Upgraded a system from 7.1-2 to 7.2-1, which was a painlessB >operation.  I then went to install the CRTL, DV, PCSI, RMS, SCSI,< >and UPDATE patches.  Knowing the PRODUCT command could take= >wildcards, I did the update in one swell foop by typing PRODn? >INSTALL *.  I then answered all the questions and deferred thea@ >reboot(s) until I had all of them done.  Man, did that make for >an unusable system. >p@ >Unfortunately, I couldn't figure out an easy way to back out of> >the patches.  Reinstalling 7.2-1 from the CD over the gutshot> >7.2-1 system pulled all the patches and put me back to square@ >one.  I then installed the patches in the CSC acceptable manner= >which is UPDATE, reboot, PCSI, SYS, reboot, RMS, reboot, DV,tA >reboot, CRTL, reboot.  Tedious, but the system is now working as"
 >expected. >tA >The moral of the story:  Just because the command has a wildcardt' >option doesn't mean you should use it.h >s >Gimpy   ------------------------------  % Date: Wed, 11 Apr 2001 11:35:36 -0400t+ From: Jorge Valenzuela <jvalen@alefdata.cl> 7 Subject: How to set the date format for insert statmentM+ Message-ID: <3AD479C8.2863F290@alefdata.cl>-   Hello:  D     I am new in RDB for Alpha Open VMS and i can set the date format
 display to DD/MM/YYYY with the commandl       SET  DATE FORMAT DATE 28.t  B     But it always ask me the dates fields for insert int he format dd-mmm-yyyy (02-dec-2001),' how to set this format for the insert ?   7     I am using a VB 5 app. conecting to RDB via ODBC32.@    A                                                 thanks in advancen     Jorge V.S.'010410d       --H ////////////////////////////////////////////////////////////////////////   //  ALEF DATA S.A.  //5 //  Fn:(562) 695-6600  //  Jorge Valenzuela Sepulvedaa2 //  Fx:(562) 697-2037  //  Jefe Area de Ingeniera1 //  Agustinas 1141 piso 7. //  jvalen@alefdata.clP- //  Santiago, Chile  //  alefdata@alefdata.cl<G ///////////////////////////////////////////////////////////////////////E   ------------------------------  # Date: Wed, 11 Apr 2001 12:36:45 GMT & From: "john nixon" <jnixon@cfl.rr.com>" Subject: Re: KZPCA-AA Works fine !: Message-ID: <xdYA6.5259$_U.786688@typhoon.tampabay.rr.com>  D I don't suppose you will get around to trying this out on an AS2100?  7 "islandco.com" <dbturner@islandco.com> wrote in messagee) news:td7aa53hrl376b@news.supernews.com..., > FYI - Allk >oE > Installed a KZPCA-AA in PWS433, 500 and 600, XP1000 DS20 and AS1200  >  > Works fine in all instancesT >eL > Reason I posted this is because I saw a note a couple of weeks ago stating* > that these didn't work in PWS systems  -L > They''re very quick and also work with th U160 disks which for some reason > are cheaper than SCSI-2m >  >eH > We are evaluating some other cheap boards next week also: 53C895 based > U2Wide cards, no namet >gH > WIll post results - this is a replacement for KZPBA-CA if it works for only > about $200 >a > DT >  >p > -- > David Turner! > Island Computers US Corporation  > 2700 Gregory Street  > Savannah GA 31404i > Tel: 912 447 6622e > Fax:912 201 0096 > sales@islandco.com >u >h >    ------------------------------  % Date: Wed, 11 Apr 2001 09:41:37 -0400 8 From: "Island Computers US Corp" <dbturner@islandco.com>" Subject: Re: KZPCA-AA Works fine !/ Message-ID: <td8nnelvd6h657@news.supernews.com>-  H Actually - we don't have a 2100 any longer - it was actually sent to the
 scrap yard  J If you want to try one -I can get one out to you with a credit card number   Davidr   -- Island Computers US Corporation. 2700 Gregory Streetv	 Suite 150  Savannah GA 31404, Tel: 912 447 6622n Fax: 912 201 0096- sales@islandco.com www.islandco.com  C This message and any files transmitted with it are confidential andnJ may be privileged and/or subject to the provisions of privacy legislation.H They are intended solely for the use of the individual or entity to whomE they are addressed. If the reader of this message is not the intendedt
 recipient,G please notify Island Computers US Corp immediately and then delete thisi message.I You are notified that reliance on, disclosure of, distribution or copyingh of this message is prohibited.    1 "john nixon" <jnixon@cfl.rr.com> wrote in messageo4 news:xdYA6.5259$_U.786688@typhoon.tampabay.rr.com...F > I don't suppose you will get around to trying this out on an AS2100? >i9 > "islandco.com" <dbturner@islandco.com> wrote in message + > news:td7aa53hrl376b@news.supernews.com...i
 > > FYI - Allf > > G > > Installed a KZPCA-AA in PWS433, 500 and 600, XP1000 DS20 and AS1200t > >i > > Works fine in all instancesc > > F > > Reason I posted this is because I saw a note a couple of weeks ago statingi, > > that these didn't work in PWS systems  -G > > They''re very quick and also work with th U160 disks which for somet reason > > are cheaper than SCSI-2e > >e > >uJ > > We are evaluating some other cheap boards next week also: 53C895 based > > U2Wide cards, no namen > >eJ > > WIll post results - this is a replacement for KZPBA-CA if it works for > only > > about $200 > >? > > DT > >  > >  > > -- > > David Turner# > > Island Computers US Corporations > > 2700 Gregory StreetG > > Savannah GA 31404  > > Tel: 912 447 6622  > > Fax:912 201 0096 > > sales@islandco.com > >- > >- > >- >+ >    ------------------------------  % Date: Wed, 11 Apr 2001 08:11:37 -0400t2 From: "Sue Skonetski" <susan.skonetski@compaq.com>1 Subject: Re: London, England Technical Update Day:2 Message-ID: <ZRXA6.775$fB6.19551@news.cpqcorp.net>  L I can not give an honest answer to the question of will the same informationJ be presented at DECUS Lisbon because I have not seen the presentations.  IJ am sure there will be some overlap, but none of the speakers are the same.   Suee  = "Sue Skonetski" <susan.skonetski@compaq.com> wrote in messagev, news:PPoz6.648$fB6.17182@news.cpqcorp.net... > Dear Newsgroup,h >i > As promised. >rJ > Here is the URL for the OpenVMS Technical Update days in London England. >r4 > http://www.wordsbureau.co.uk/vms-technical-update/ >e/ > It works from Netscape and Internet explorer.e >g > Warm Regards,  >  > Sueo >h >t >o   ------------------------------   Date: 11 APR 2001 16:09:39 GMT+ From: Dave Greenwood <greenwoodde@ornl.gov>f4 Subject: NetBackUp / MultiNet - does the combo work?2 Message-ID: <11APR01.16093960@feda01.fed.ornl.gov>  = Is anyone using using NetBackUp over MultiNet?  Successfully?t  F I help some folks with their VMS systems work and they're trying to doA all their backups with NetBackUp.  It "used to work" but it isn't-H working currently.  The vendor wants to blame the MultiNet UCX emulationI but I'm not so sure the problem is MultiNet's.  I was wondering if anyone & else was using NetBackUp and MultiNet?  D Briefly, what happens is that the NetBackUp server makes the initialG connection to the VMS system and we can see a process created to handle D that connection.  But the server apparently tries to open up anotherG connection that doesn't succeed and eventually the server times out ande	 gives up.a  
 $ mu show/ver C Process Software MultiNet V4.3 Rev A-X, AlphaServer 4000 5/300 2MB,s OpenVMS AXP V7.2-1  C The NetBackup client is V3.4Beta1, the server is v3.2 on hpux 10.2.u  C There were a bunch of messages about NetBackUp on comp.os.vms a fewCE months ago, including some posted by someone who described himself as @ the creator the NetBackUp VMS client.  Unfortunately mail to the/ address he posted fails ("unknown local-part").    Thanks,o Dave --------------9 Dave Greenwood                Email: Greenwoodde@ORNL.GOVsH Oak Ridge National Lab        %STD-W-DISCLAIMER, I only speak for myself   ------------------------------  % Date: Wed, 11 Apr 2001 09:05:17 -0500I* From: WILLIAM WEBB <WWEBB1@email.usps.gov>% Subject: RE: NSA is Linux not OpenVMSS- Message-ID: <0033000021183524000002L042*@MHS>   * =0AAre you Andrew's less intelligent twin?  6 The initials VMS were derived from a secret encryption# scheme applied to the initials NSA.   9 NSA without VMS would be like Microsoft without bad code.S  : But now that we've told you this, we'll have to shoot you.   WWWebb   > -----Original Message-----1 > From: Info-VAX-Request@Mvb.Saic.Com at INTERNET ' > Sent: Tuesday, April 10, 2001 7:59 AMgD > To: Webb, William W Raleigh, NC; Info-VAX@Mvb.Saic.Com at INTERNET# > Subject: NSA is Linux not OpenVMSa >n > 
 > Click at >h? > http://news.cnet.com/news/0-1003-200-5551168.html?tag=3Dcd_mh  >  >=) > Is really needed the OpenVMS for NSA  ?  >N	 > Regards  >  > FC >=   ------------------------------  % Date: Wed, 11 Apr 2001 10:24:26 -0300 ) From: fabio_compaq@ep-bc.petrobras.com.brI% Subject: RE: NSA is Linux not OpenVMStL Message-ID: <OF37374388.E9A311B1-ON03256A2B.00499372@ep-bc.petrobras.com.br>  > Andrew's twin ????? Not bad idea.... I am almost becoming ....   Regards    FC        ; WILLIAM WEBB <WWEBB1@email.usps.gov> em 11/04/2001 11:05:17c  6 Favor responder a WILLIAM WEBB <WWEBB1@email.usps.gov>             Info-VAX@Mvb.Saic.Come      % Assunto: RE: NSA is Linux not OpenVMSO      ' Are you Andrew's less intelligent twin?   6 The initials VMS were derived from a secret encryption# scheme applied to the initials NSA.o  9 NSA without VMS would be like Microsoft without bad code.d  : But now that we've told you this, we'll have to shoot you.   WWWebb   > -----Original Message-----1 > From: Info-VAX-Request@Mvb.Saic.Com at INTERNET-' > Sent: Tuesday, April 10, 2001 7:59 AM0D > To: Webb, William W Raleigh, NC; Info-VAX@Mvb.Saic.Com at INTERNET# > Subject: NSA is Linux not OpenVMSD >O >2
 > Click at >O= > http://news.cnet.com/news/0-1003-200-5551168.html?tag=cd_mht >  >h) > Is really needed the OpenVMS for NSA  ?a > 	 > Regardsd >t > FC >o   ------------------------------  % Date: Wed, 11 Apr 2001 10:05:22 +0200i! From: Didier Morandi <Dmo@ims.ch> ? Subject: Re: OpenVMS Frequently Asked Questions (FAQ), Part 3/5 & Message-ID: <3AD41042.BC01EF18@ims.ch>   july ?   Hoff Hoffman wrote:o > ! > Archive-name: dec-faq/vms/part3o > Posting-Frequency: quarterly > Last-modified: 10 Jul 2001   ------------------------------  # Date: Wed, 11 Apr 2001 15:41:51 GMTt2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)? Subject: Re: OpenVMS Frequently Asked Questions (FAQ), Part 3/5m2 Message-ID: <3X_A6.786$fB6.19929@news.cpqcorp.net>  J In article <3AD41042.BC01EF18@ims.ch>, Didier Morandi <Dmo@ims.ch> writes: :july ?1 :p :Hoff Hoffman wrote: :> m" :> Archive-name: dec-faq/vms/part3 :> Posting-Frequency: quarterlye :> Last-modified: 10 Jul 2001e  E   I have it on good authority that the perpetrator of that particular I   error -- and another error involving inconsistencies among the various  F   entries for the posting frequency -- had suffered from an episode ofG   TBF (Transient Brain Fade).  TBF is usually benign, and can normally OG   be remediated through application of AVT (Accumulated Vacation Time).   H   More seriously, I wanted to get a copy of the OpenVMS FAQ updated for H   inclusion onto the OpenVMS Freeware release, and "found" a few cycles G   (too few, in retrospect) to apply the accumulated updates to the FAQ.m  N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Wed, 11 Apr 2001 12:03:09 -0400i# From: Jim Agnew <Agnew@hsc.vcu.edu>i? Subject: Re: OpenVMS Frequently Asked Questions (FAQ), Part 3/5a+ Message-ID: <3AD4803D.393E1EBB@hsc.vcu.edu>    HMM..  Maybe the person in question could up grade their brain OS to WindowsTP, Windows Telepath, documented in rec.humor.funny'su home page... ;-)   (just kidding!!!)a   Jimo   Hoff Hoffman wrote:  > L > In article <3AD41042.BC01EF18@ims.ch>, Didier Morandi <Dmo@ims.ch> writes:	 > :july ?v > :  > :Hoff Hoffman wrote: > :>$ > :> Archive-name: dec-faq/vms/part3! > :> Posting-Frequency: quarterlyi > :> Last-modified: 10 Jul 2001t > G >   I have it on good authority that the perpetrator of that particular>J >   error -- and another error involving inconsistencies among the variousH >   entries for the posting frequency -- had suffered from an episode ofH >   TBF (Transient Brain Fade).  TBF is usually benign, and can normallyI >   be remediated through application of AVT (Accumulated Vacation Time).o > I >   More seriously, I wanted to get a copy of the OpenVMS FAQ updated for-I >   inclusion onto the OpenVMS Freeware release, and "found" a few cycles I >   (too few, in retrospect) to apply the accumulated updates to the FAQ.  > P >  ---------------------------- #include <rtfaq.h> -----------------------------L >       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.comP >  --------------------------- pure personal opinion ---------------------------N >    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------   Date: 11 Apr 2001 17:03:31 GMT1 From: bill@triangle.cs.uofs.edu (Bill Gunshannon)r? Subject: Re: OpenVMS Frequently Asked Questions (FAQ), Part 3/5q, Message-ID: <9b22p3$2jaa$1@info.cs.uofs.edu>  + In article <3AD4803D.393E1EBB@hsc.vcu.edu>,a&  Jim Agnew <Agnew@hsc.vcu.edu> writes: |> HMM..  Maybe the person in question could up grade their brain OS to WindowsTP, Windows Telepath, documented in rec.humor.funny's |> home page... ;-)n |> d  C WindowsTP??  Sounds like someone trying to rip off the PlayStation6n commercial.0   bill   -- tJ Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>   i   ------------------------------  % Date: Wed, 11 Apr 2001 10:19:11 -0700-! From: Shane.F.Smith@Healthnet.com-? Subject: Re: OpenVMS Frequently Asked Questions (FAQ), Part 3/5iD Message-ID: <OFFF9F118A.6B71E0E1-ON88256A2B.005F06ED@foundation.com>  G Urgh. Bill Gates as Alfred Bester..... [Shudder] Where's Lyta Alexanderh when you need her!?    Shane-          7 Jim Agnew <Agnew@hsc.vcu.edu> on 04/11/2001 09:03:09 AMm  / Please respond to Jim Agnew <Agnew@hsc.vcu.edu>w   To:   Info-VAX@Mvb.Saic.Come cc:b  @ Subject:  Re: OpenVMS Frequently Asked Questions (FAQ), Part 3/5    D HMM..  Maybe the person in question could up grade their brain OS to< WindowsTP, Windows Telepath, documented in rec.humor.funny's home page... ;-)   (just kidding!!!)h   Jimw   Hoff Hoffman wrote:p >bD > In article <3AD41042.BC01EF18@ims.ch>, Didier Morandi <Dmo@ims.ch> writes: 	 > :july ?t > :c > :Hoff Hoffman wrote: > :>$ > :> Archive-name: dec-faq/vms/part3! > :> Posting-Frequency: quarterlyt > :> Last-modified: 10 Jul 2001l >eG >   I have it on good authority that the perpetrator of that particulardJ >   error -- and another error involving inconsistencies among the variousH >   entries for the posting frequency -- had suffered from an episode ofH >   TBF (Transient Brain Fade).  TBF is usually benign, and can normallyI >   be remediated through application of AVT (Accumulated Vacation Time).  >eI >   More seriously, I wanted to get a copy of the OpenVMS FAQ updated for)I >   inclusion onto the OpenVMS Freeware release, and "found" a few cyclesnI >   (too few, in retrospect) to apply the accumulated updates to the FAQ.1 >:2 >  ---------------------------- #include <rtfaq.h> -----------------------------:5 >       For additional, please see the OpenVMS FAQ --P www.openvms.compaq.com4 >  --------------------------- pure personal opinion ---------------------------h1 >    Hoff (Stephen) Hoffman   OpenVMS Engineeringo hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Wed, 11 Apr 2001 13:24:45 -0400c# From: Jim Agnew <Agnew@hsc.vcu.edu>r? Subject: Re: OpenVMS Frequently Asked Questions (FAQ), Part 3/51+ Message-ID: <3AD4935D.300DBC8D@hsc.vcu.edu>e  j it was a spoof on the windows95 upgrade to win31, i think...  it was really, really hilarious at the time.   j.   Bill Gunshannon wrote: > - > In article <3AD4803D.393E1EBB@hsc.vcu.edu>,-( >  Jim Agnew <Agnew@hsc.vcu.edu> writes: > |> HMM..  Maybe the person in question could up grade their brain OS to WindowsTP, Windows Telepath, documented in rec.humor.funny's > |> home page... ;-)w > |> > E > WindowsTP??  Sounds like someone trying to rip off the PlayStation6r
 > commercial.o >  > bill >  > --L > Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesF > bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. > University of Scranton   |@ > Scranton, Pennsylvania   |         #include <std.disclaimer.h>   ------------------------------  # Date: Wed, 11 Apr 2001 16:14:41 GMTn% From: bdc@world.std.com (Brian Chase),< Subject: Re: Q: Converting a VAX 6000-420 to a VAX 6000-620?& Message-ID: <GBMyGI.Lp4@world.std.com>  ' In article <3AD38E97.3AB5244E@iee.org>,c* antonio.carlini <arcarlini@iee.org> wrote: > Brian Chase wrote:  # > >   VAX 6000-600 CPUs     (check)-# > >   VAX 6000-600 RAM      (check)01 > >   XMI-2 card cage       (part number anyone?)a, > >   T2019 3.3V Power Reg  (Same as H7242?)A > >   XBIA+ Module          (XMI half of the XMI<->VAXBI bridge?)l+ > >   XTC Module            (What is this?)  > > @ > >   And then any necessary cables to hook this stuff together. >m3 > The above basically turns your XMI-1 chassis intoa0 > an XMI-2 chassis by changing all the bits that  > are different between the two. > . > Except that if you go this route you *don't** > use the T2019 and you *do* use the H7242* > (which replaces one the the H7214 IIRC). > [...]  > ( > The *easy* route is to pick up a T20190 > from ebay or wherever. Make sure it comes with, > the (blue?) powerbus cabling. The T2019 is* > an XMI module like any other XMI module,- > except it sits in slot 2 and blocks slot 1.3  L Okay.  Good.  I was getting a lot of information from a number of sources.  F Much of it blended different aspects these two seperate upgrade paths.  + > The upside is that you will have time for/. > a life. The downside is that you essentially( > lose 2 slots and can support at most 4% > KA65A or KA66A CPUs. Is this reallyR$ > a problem :-) (Plus you cannot use > battery backup).  G I can live with all those limitations.  The one advantage of going this I route is that it should be easier to change the system between running aseJ a VAX 6000-400 and a VAX 6000-600.  (Which is actually useful given that IJ hope to use the system for assisting with the development of NetBSD/vax on the VAX 6000 platform).   N > > I'm beginning to think it'll be cheaper to just freight ship the the wholeH > > VAX 6000-600 chasis than to scrounge all the necessary bits to do anI > > upgrade.  And hey, then I'd have *two* VAX 6000s in the basement.  My M > > neighbors are going to start wondering about me... more than they alreadyd > > do.e >r/ > I would go for the ready-built chassis. Apart 2 > from anything else it would look *so* impressive > in the basement.    I I'm still very much considering this, it'll depend on the costs involved.yA I'll just have to be sure that I never move from my current home.    -brian.e -- aF --- Brian Chase | bdc@world.std.com | http://world.std.com/~bdc/ -----D  On Earth it's always something.  In Heaven it's always Kibo.  -- K.   ------------------------------  # Date: Wed, 11 Apr 2001 16:19:26 GMTh% From: bdc@world.std.com (Brian Chase)w< Subject: Re: Q: Converting a VAX 6000-420 to a VAX 6000-620?& Message-ID: <GBMyoE.2F8@world.std.com>  ' In article <3AD20ED8.2AD9E3B9@iee.org>,u* antonio.carlini <arcarlini@iee.org> wrote: > Paul Repacholi wrote:S1 > > "antonio.carlini" <arcarlini@iee.org> writes:7  J > > > So I think the short answer is: T2019 and that widget you plug in atI > > > the back (sorry, no part number ... I can hit the IPBs if you thinke* > > > you might have it but are not sure). > > 5 > > Two blue power buses that go to the bottom slots?n > > E > > 17-002751-01 abd another cumming hidden under the main power bus.  >n5 > I cannot find a number for the powerbus cable and Iu4 > the manual does not say anything about playng with6 > any other cables. (I'll read more carefully if Brian' > actually gets all the bits together!)s  B Yeah, if you could get the part numbers for both cables, that'd beJ helpful.  The reseller with which I'm dealing has asked for the numbers so7 they can be sure I get my T2019 with everything I need.i   -brian." -- uF --- Brian Chase | bdc@world.std.com | http://world.std.com/~bdc/ -----D  On Earth it's always something.  In Heaven it's always Kibo.  -- K.   ------------------------------    Date: 11 Apr 2001 10:54:20 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de>fF Subject: Re: Rumour Has It That CHARLIE MATCO HAS RISEN FROM THE GRAVEH Message-ID: <y47l0ru88z.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  % Paul DeMone <pdemone@igs.net> writes:   F > Expect 1+ GHz EV68 to ship within several months along with a secondG > generation chipset. The Cu EV68 has been shown to clock over 1.4 GHz. G > The touted performance of EV68 at 1.3 GHz (800/1000 SPEC2k) will take H > about a 3.5 GHz P4 to match in SPECint2k and about a 6 GHz P4 to match? > it in SPECfp2k IIRC my scaling calculations right. Woof woof.:  H In Colarusso's ESILUG presentation (all 8 MB PPT of it - when will theseH people ever learn!?), there are numbers on the ES45-1000 in violation of SPEC CPU2000's reporting rules.i   	Jan   ------------------------------    Date: 10 Apr 2001 09:33:32 -0500- From: koehler@encompasserve.org (Bob Koehler)c Subject: Silent Sun 3 Message-ID: <qVF5HDY49cSJ@eisner.encompasserve.org>e  ] In article <3AD1F399.2E84375F@uk.sun.com>, andrew harrison <andrew.nospam@uk.sun.com> writes:  >  > Ok. I will let you decide. >    OK, I decided.  I'll keep VMS.  B Today I got a copy of CERT Advisory CA-2001-07.  Compaq's responseF included.  SGI's response included.  IBM's response included.  Various= Linux shippers responded.  No response from Sun was included.p  G Some responded "no problem".  Some responded "we have a fix".  And somec< responded "we see the problem and are looking into the fix".  G Now who's being quiet about security holes?  Couldn't Sun at least have-? responded "we're looking into it" in time to be included on ther	 advisory?r  F ----------------------------------------------------------------------? Bob Koehler                     | Computer Sciences Corporation = NASA GSFC Flight Software       | Federal Sector, Civil GroupiE                                 | please remove ".aspm" when replyingi   ------------------------------  % Date: Wed, 11 Apr 2001 13:40:37 +0100d0 From: andrew harrison <andrew.nospam@uk.sun.com> Subject: Re: Silent Sune* Message-ID: <3AD450C5.247D5F18@uk.sun.com>   Bob Koehler wrote: > _ > In article <3AD1F399.2E84375F@uk.sun.com>, andrew harrison <andrew.nospam@uk.sun.com> writes:n > >h > > Ok. I will let you decide. > >  >   > OK, I decided.  I'll keep VMS. > D > Today I got a copy of CERT Advisory CA-2001-07.  Compaq's responseH > included.  SGI's response included.  IBM's response included.  Various? > Linux shippers responded.  No response from Sun was included.5 >   = This advisory is dated the 10th of April. I would be suprisedt< if everyone had got arround to responding with a fix or even	 replying.N  B As for Compaq they have sent out the standard we are investigating this response. b  ( You could do this with a mail responder.  I > Some responded "no problem".  Some responded "we have a fix".  And some-> > responded "we see the problem and are looking into the fix". > I > Now who's being quiet about security holes?  Couldn't Sun at least haveSA > responded "we're looking into it" in time to be included on the  > advisory?1 >   C I would suggest that you really are grasping at staws. Not having aj responseH to an advisory that is a day old is rather different to not having ever G replied to an advisory which you were vunerable to when the advisory isi over a year old.  = I generally read your posts with interest but this was a postM@ that Kerry would have been proud of, not to your usual standard.   Regardsh Andrew Harrison  Enterprise IT Architect    ------------------------------    Date: 11 Apr 2001 11:19:56 -0500- From: koehler@encompasserve.org (Bob Koehler)A Subject: Re: Silent Sun 3 Message-ID: <wGhq9RQiC32S@eisner.encompasserve.org>j  ] In article <3AD450C5.247D5F18@uk.sun.com>, andrew harrison <andrew.nospam@uk.sun.com> writes:5 > D > As for Compaq they have sent out the standard we are investigating > this response.   >   F Actually they included "Initial tests indicate Compaq's ftp service is% not vulnerable."  Not quite the same.o  F ----------------------------------------------------------------------? Bob Koehler                     | Computer Sciences Corporationw= NASA GSFC Flight Software       | Federal Sector, Civil GroupaE                                 | please remove ".aspm" when replying1   ------------------------------  % Date: Wed, 11 Apr 2001 16:38:45 +0100 - From: Tim Llewellyn <tim.llewellyn@bbc.co.uk>N Subject: Re: Silent Sun ) Message-ID: <3AD47A85.5E36F077@bbc.co.uk>n   Bob Koehler wrote:  _ > In article <3AD450C5.247D5F18@uk.sun.com>, andrew harrison <andrew.nospam@uk.sun.com> writes:l > >lF > > As for Compaq they have sent out the standard we are investigating > > this response. > >  >eH > Actually they included "Initial tests indicate Compaq's ftp service is' > not vulnerable."  Not quite the same.2  O I would be more convinced if they said "ftp services" not "ftp service". Compaq I supplies more than one IP capable OS. OK, Tru64 and TCPIP$ share the same.Q code. What about all those people stuck on UCX 4.x or older? Are they vulnerable?e Older versions of Tru64?    -- 6 Tim Llewellyn, OpenVMS Infrastructure, Remarcs Project0 MedAS at the BBC, Whiteladies Road, Bristol, UK.A Email tim.llewellyn@bbc.co.uk. Home tim.llewellyn@cableinet.co.uk   A I speak for myself only and my views in no way represent those of  MedAS or the BBC.o   ------------------------------  # Date: Wed, 11 Apr 2001 16:30:03 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) Subject: Re: Silent Sun12 Message-ID: <fE%A6.793$fB6.20009@news.cpqcorp.net>  ] In article <3AD450C5.247D5F18@uk.sun.com>, andrew harrison <andrew.nospam@uk.sun.com> writes:gC :As for Compaq they have sent out the standard we are investigatingB :this response.  :e) :You could do this with a mail responder.p  %   So Sun has no mail responders?  :-)n  N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Wed, 11 Apr 2001 17:12:34 +0100d0 From: andrew harrison <andrew.nospam@uk.sun.com> Subject: Re: Silent Sunr* Message-ID: <3AD48272.730E901E@uk.sun.com>   Bob Koehler wrote: > _ > In article <3AD450C5.247D5F18@uk.sun.com>, andrew harrison <andrew.nospam@uk.sun.com> writes:  > > F > > As for Compaq they have sent out the standard we are investigating > > this response. > >- > H > Actually they included "Initial tests indicate Compaq's ftp service is' > not vulnerable."  Not quite the same.- >   6 Given Compaqs tendency to ignore OpenVMS completely do2 you think that they are refering to all their ftp 3 services on all their OS's in this response. Or are-0 they as is generally the case refering to Tru64.  0 The only OS that Compaq do with a posted fix for Naptha for example is Tru64.   regardsr Andrew HarrisonD Enterprise IT Architectv   ------------------------------  % Date: Wed, 11 Apr 2001 12:58:16 -0400O  From: jamese@beast.dtsw.army.mil Subject: SMP_SPINWAIT.0 Message-ID: <01041112581666@beast.dtsw.army.mil>   Hello,  3 I received this URL to the new OpenVMS Times today:15 http://www.openvms.compaq.com/openvmstimes/index.html   4 In it there is an "OpenVMS Tech Tips" box that says:  9     If your Alpha system has more than one CPU, make sure>3     SYSGEN parameter SMP_SPINWAIT is set to 3000000o  $     -- Guy Peleg, OpenVMS Ambassador   Well, I am running:   ,     AlphaServer 4000 5/400 4MB VMS  V7.1-1H1  
 which has:  M Parameter Name         Current    Default     Min.      Max.     Unit Dynamic M --------------         -------    -------    -------   -------   ---- -------mH SMP_SPINWAIT             100000     100000         1    8388607 10 usec.  H The only references to SMP_SPINWAIT I can find in DSNLINK are in releaseF notes for versions 6.2 and later.  They describe a problem if you haveH an SMP system with CIPCA adapters and say to set SMP_SPINWAIT to 300000.+ This is a standalone system without CIPCAs.e  7 Does anyone have any other information on SMP_SPINWAIT?i   Thank you very much,  : Ed James                           ed.james@telecomsys.com5 TeleCommunications Systems, Inc.   voice 410-295-1919 ; 2024 West Street, Suite 300              800-810-0827 x1919d5 Annapolis, MD 21401-3556           fax   410-280-1094a   ------------------------------    Date: 10 Apr 2001 10:24:17 -0500+ From: young_r@encompasserve.org (Rob Young)s< Subject: Re: Solaris tmpfs (was Re: VMS-Related: Affordable)3 Message-ID: <ufBzpF7L4Xuk@eisner.encompasserve.org>c  ] In article <3AD30BCD.214B91D3@uk.sun.com>, andrew harrison <andrew.nospam@uk.sun.com> writes:  > Hoff Hoffman wrote:  >> w` >> In article <3AD1F484.9C8E4598@uk.sun.com>, andrew harrison <andrew.nospam@uk.sun.com> writes: >> d> >> :Sort of. Solaris has an in-memory filesystem called tmpfs. >> :> >> :/tmp is normally mounted as a tmpfs volume but some people; >> :also use it for things like Sybase TMPDB. It never getse7 >> :flushed to disk unless you run out of memory and it| >> :gets paged.y >> aH >>   A good idea, but certainly not the implementation that I would haveL >>   chosen.  I'd have gone the route of a host-based RAM disk with pageableJ >>   memory, and the same file system everything else uses.  (Why?  A diskI >>   device is a whole lot less involved than a file systems.  I'd preferi3 >>   to avoid maintaining yet another file system.)  >> n > 5 > You can also do that. There are vendors who provideA2 > SBus or PCI NVRAM RAM disks that then have a UFS6 > type filesystem on them. One I have seen also has a . > disk attached that is used to flush the data2 > to disk if there is a power failure. The disk is# > obviously battery backed as well.o > 2 > But people tend to use these devices where they 0 > need very high performance persistent storage. >   A 	Going forward (12 months?) , this is not a problem.  The RamDiskcD 	will be one member of a shadowset.  Reads go to the RamDisk, writesF 	go to both.  The disk based shadowset of course has writeback caching? 	turned on so it is catching the writes and flushing without a i. 	problem as there is no reads to contend with.  < 	John AtoZ has shadowing RamDisks as a bullet on his slides.   >h7 > tmpfs is used where people need very high performance  > but non-persistent storage.c >   9 	You do the best you can with what you have to work with.d   				Rob    ------------------------------  % Date: Wed, 11 Apr 2001 13:33:01 +0100A0 From: andrew harrison <andrew.nospam@uk.sun.com>< Subject: Re: Solaris tmpfs (was Re: VMS-Related: Affordable)* Message-ID: <3AD44EFD.883FE849@uk.sun.com>   Rob Young wrote: > _ > In article <3AD30BCD.214B91D3@uk.sun.com>, andrew harrison <andrew.nospam@uk.sun.com> writes:- > > Hoff Hoffman wrote:i > >>b > >> In article <3AD1F484.9C8E4598@uk.sun.com>, andrew harrison <andrew.nospam@uk.sun.com> writes: > >>@ > >> :Sort of. Solaris has an in-memory filesystem called tmpfs. > >> :@ > >> :/tmp is normally mounted as a tmpfs volume but some people= > >> :also use it for things like Sybase TMPDB. It never gets-9 > >> :flushed to disk unless you run out of memory and it  > >> :gets paged.c > >>J > >>   A good idea, but certainly not the implementation that I would haveN > >>   chosen.  I'd have gone the route of a host-based RAM disk with pageableL > >>   memory, and the same file system everything else uses.  (Why?  A diskK > >>   device is a whole lot less involved than a file systems.  I'd prefer 5 > >>   to avoid maintaining yet another file system.)a > >> > >s7 > > You can also do that. There are vendors who provide,4 > > SBus or PCI NVRAM RAM disks that then have a UFS7 > > type filesystem on them. One I have seen also has ae0 > > disk attached that is used to flush the data4 > > to disk if there is a power failure. The disk is% > > obviously battery backed as well.  > >h3 > > But people tend to use these devices where they 2 > > need very high performance persistent storage. > >| > J >         Going forward (12 months?) , this is not a problem.  The RamDiskM >         will be one member of a shadowset.  Reads go to the RamDisk, writestO >         go to both.  The disk based shadowset of course has writeback caching?G >         turned on so it is catching the writes and flushing without a@7 >         problem as there is no reads to contend with.  >   & You can do this now. The PCI and SBus 3 RAMdisks currently available for Solaris appear as  4 disk devices to the OS. Because of this you can use 7 Veritas or Solaris's volume manager to mirror this Ram u2 disk to a normal physical disk. You can with both / volume managers then specify the read priority  - to use the Ram Disk for reads rather than theh
 normal drive.e    E >         John AtoZ has shadowing RamDisks as a bullet on his slides.a >  > >h9 > > tmpfs is used where people need very high performance  > > but non-persistent storage.r > >y > B >         You do the best you can with what you have to work with. >    Not really.   > tmpfs is standard with the OS and uses the available physical : memory to get big performance gains for files that do not 7 need to be retained. It has little or no cost but is a y big win for this kind of app.   < Ramdisk is more costly but does provide non-volatile storage: you use if for different things than you use tmpfs for but  it also costs much more as well.   Regardst Andrew Harrison  Enterprise IT Architectu   ------------------------------   Date: 11 Apr 2001 14:57:50 GMT2 From: mathog@seqaxp.bio.caltech.edu (David Mathog)< Subject: Re: Solaris tmpfs (was Re: VMS-Related: Affordable), Message-ID: <9b1rde$anj@gap.cco.caltech.edu>  a In article <ufBzpF7L4Xuk@eisner.encompasserve.org>, young_r@encompasserve.org (Rob Young) writes:  > B >	Going forward (12 months?) , this is not a problem.  The RamDiskE >	will be one member of a shadowset.  Reads go to the RamDisk, writesgG >	go to both.  The disk based shadowset of course has writeback caching'@ >	turned on so it is catching the writes and flushing without a / >	problem as there is no reads to contend with.a  E Won't this largly wipe out the performance advantage that the RAMdisk*H offers?  To keep everything shadowed the RAMdisk will have to wait untilK everything hits the disk.  Worst case the RAMdisk will peak out at 20Mb/secaI (or whatever the physical limit is for the disk) which is a heck of a loteF (100X !) slower than the 2Gb/sec the RAMdisk will do on a DS10 withoutB shadowing.  Reads should still be fast though, although maybe only: marginally faster than a regular disk with XFC turned on.    > = >	John AtoZ has shadowing RamDisks as a bullet on his slides.  >s  H Seems like given a choice between a shadowed RAMdisk and a working file K cache (read and write) the latter would be better in most instances, giving F better performance for (roughly) the same amount of memory usage.  If L physical storage is never required, the RAMdisk will win.  (This is another J reason why Alphas should have tons of cheap memory, but no use beating on J that dead horse, Compaq can't give us that and maintain their 50% margins.H So somebody else will - soon - and there's another opportunity down the  drain.)n   Regards,   David Mathog mathog@seqaxp.bio.caltech.eduo? Manager, sequence analysis facility, biology division, Caltech sJ **************************************************************************J *                                RIP VMS                                 *J **************************************************************************   ------------------------------    Date: 11 Apr 2001 11:35:54 -0500+ From: young_r@encompasserve.org (Rob Young)g< Subject: Re: Solaris tmpfs (was Re: VMS-Related: Affordable)3 Message-ID: <dCN3s1tAUFRp@eisner.encompasserve.org>b  a In article <9b1rde$anj@gap.cco.caltech.edu>, mathog@seqaxp.bio.caltech.edu (David Mathog) writes: c > In article <ufBzpF7L4Xuk@eisner.encompasserve.org>, young_r@encompasserve.org (Rob Young) writes:s >>C >>	Going forward (12 months?) , this is not a problem.  The RamDisk0F >>	will be one member of a shadowset.  Reads go to the RamDisk, writesH >>	go to both.  The disk based shadowset of course has writeback cachingA >>	turned on so it is catching the writes and flushing without a t0 >>	problem as there is no reads to contend with. > G > Won't this largly wipe out the performance advantage that the RAMdisktJ > offers?  To keep everything shadowed the RAMdisk will have to wait untilM > everything hits the disk.  Worst case the RAMdisk will peak out at 20Mb/seckK > (or whatever the physical limit is for the disk) which is a heck of a lot H > (100X !) slower than the 2Gb/sec the RAMdisk will do on a DS10 withoutD > shadowing.  Reads should still be fast though, although maybe only< > marginally faster than a regular disk with XFC turned on.  >   : 	"wait until it hits the	disk" ... actually, the paragraph1 	right above that talks about "writeback caching"5  < 	I think of course there is a place for this idea (shadowing< 	a RamDisk) and it probably isn't for everyone.  John AtoZ's; 	presentation shows a hiearchy for reads (can't do much forn< 	writes in a sense) and I believe this has been beaten about4 	before.  The hiearchy is for preferred read source:   		1)  Local RamDiskAA 		2)  Remote RamDisk   ! Note: Read_Cost can prevent this if needn-                                      ! arisesu 		3)  Local disk  ; 	and you can pretty much play out the rest right on down top 	MSCP served disk.  A 	The place for this?  Pathalogical ramdom reads, where worst caser= 	time to read is at RamDisk speed.  If today *average* randomyB 	read from platter is in the neighborhood of 7 ms (15 K drives, is@ 	that close Bill?  Not bothering to drill Google) , RamDisk willD 	be much faster (How much?  Don't know).  We see other presentations? 	where 48 Gigs is Galactic Shared Memory section.  Maybe a goodg> 	use for this would be to stick Oracle/RDB indexes in Galactic 	Shared Memory.   < 	Writes?  I see write times of 1 ms using writeback cache on= 	controllers so WORST CASE write is 1 ms.  That *still* isn'tw@ 	nearly as fast as Linux (as we have learned) but going forward,D 	XFC with writebehind (VCC_WRITEBEHIND) AND writedelay , should make: 	up a great deal of this ground for non-persistant writes.  @ 	You can see a staircase of choices.  XFC fast as Linux?  Should# 	be close.  *Much* improved anyhow.l  A 	Keep in mind, if business is the target...  the shadowed RamDiskm? 	is a killer as *worst* case reads AND writes are 1 ms or less o 	(I believe, correct if wrong)   >>> >>	John AtoZ has shadowing RamDisks as a bullet on his slides. >> > J > Seems like given a choice between a shadowed RAMdisk and a working file M > cache (read and write) the latter would be better in most instances, givingoH > better performance for (roughly) the same amount of memory usage.  If N > physical storage is never required, the RAMdisk will win.  (This is another L > reason why Alphas should have tons of cheap memory, but no use beating on L > that dead horse, Compaq can't give us that and maintain their 50% margins.J > So somebody else will - soon - and there's another opportunity down the 	 > drain.)o >   > 	Even if shadowed RamDisk, writeback caching at the controller> 	level masks write latencies very effectively.  If folks have > 	a 2, 5, 10 Gig RamDisk they are a big enough shop to be using 	expensive storage controllers.o  > 	I'm not as pessimistic because I believe Big Business and Big= 	Agencies are lathering for features and functionalities suchn; 	as this.  Money is money and maybe you can have 20 Gigs ofeB 	RamDisk, but not in 8 instances.  Move that RamDisk into GalacticD 	Shared Memory and today 8 instances see it (as non-persistent :-( )9 	someday shadowed and someday much more than 8 instances.r  8 	Nice , highly-scalable, *persistent* I/O . . . someday.   				Robe   ------------------------------    Date: 11 Apr 2001 17:48:17 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de> < Subject: Re: Solaris tmpfs (was Re: VMS-Related: Affordable)H Message-ID: <y4r8yzqvy6.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  4 mathog@seqaxp.bio.caltech.edu (David Mathog) writes:  J > Seems like given a choice between a shadowed RAMdisk and a working file M > cache (read and write) the latter would be better in most instances, giving C > better performance for (roughly) the same amount of memory usage.-  L The same performance, for _most_ cases. The RAM disk gives you more control,- however, which in many cases is a Good Thing.g   	Jan   ------------------------------  # Date: Wed, 11 Apr 2001 16:29:24 GMT02 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)< Subject: Re: Solaris tmpfs (was Re: VMS-Related: Affordable)2 Message-ID: <ED%A6.792$fB6.20009@news.cpqcorp.net>  ] In article <3AD44EFD.883FE849@uk.sun.com>, andrew harrison <andrew.nospam@uk.sun.com> writes:o  ' :You can do this now. The PCI and SBus o4 :RAMdisks currently available for Solaris appear as 5 :disk devices to the OS. Because of this you can use l8 :Veritas or Solaris's volume manager to mirror this Ram 3 :disk to a normal physical disk. You can with both e0 :volume managers then specify the read priority . :to use the Ram Disk for reads rather than the :normal drive.  E   Please take the discussions of Solaris to a newsgroup more releventHG   to the topic, unless of course this material and this information is s.   intended to market Solaris to OpenVMS users.  A   Hardware-based RAMdisks have been available for a long time for0C   OpenVMS and for other platforms and have been able to operate in RE   a host-based shadowset for a while now on OpenVMS.  Software-based nD   RAMdisks have also been available for quite some time, too.  DisksC   and disk I/O paths have been merrily adding and enhancing cachingdG   capabilities, too.  Though the old controller-based and non-volatile aF   caching hardware that some UNIX systems used never really caught on I   with customers -- the DIGITAL offering was known as PrestoServe, IIRC. o  E   Support for disparate geometries among shadowset volumes on OpenVMS-F   also now permits these volumes to be shadowed across any other disk F   volumes, so long as the total number of logical blocks match across J   all volumes in the shadowset.  It matters not if the individual members F   of the shadowset are hardware RAMdisk, host-based software RAMdisk, C   emulated disk (eg: TU58), physical disk, or RAID controller.  ThehD   shadowset volumes can be shadowed across hundreds of miles and can.   be accessed entirely in parallel, of course.  ? :tmpfs is standard with the OS and uses the available physical a; :memory to get big performance gains for files that do not "8 :need to be retained. It has little or no cost but is a  :big win for this kind of app.  G   This is what OpenVMS uses caching or host-based RAMdisks for, though tI   this is obviously a quite different approach than a "discardable" file sI   system such as tmpfs.  Part of the engineering work going into OpenVMS yJ   involves providing file system improvements for temporary files and for H   applications using open-write-close-open-write-close and similar file I   processing sequences.  And a large part of the new work on the new I/O sG   caching first appears in V7.3, with additional enhancements underway.w  = :Ramdisk is more costly but does provide non-volatile storagem; :you use if for different things than you use tmpfs for buth! :it also costs much more as well.T  I   Host-based (software-based) RAMdisks need not use non-volatile storage.a  F   Hardware-based RAMdisks may or may not have associated non-volatile 
   storage.  N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Wed, 11 Apr 2001 17:37:57 +0100L0 From: andrew harrison <andrew.nospam@uk.sun.com>< Subject: Re: Solaris tmpfs (was Re: VMS-Related: Affordable)* Message-ID: <3AD48865.4C6CFC8E@uk.sun.com>   Hoff Hoffman wrote:n > _ > In article <3AD44EFD.883FE849@uk.sun.com>, andrew harrison <andrew.nospam@uk.sun.com> writes:o > ( > :You can do this now. The PCI and SBus5 > :RAMdisks currently available for Solaris appear ass6 > :disk devices to the OS. Because of this you can use9 > :Veritas or Solaris's volume manager to mirror this Ram64 > :disk to a normal physical disk. You can with both1 > :volume managers then specify the read prioritym0 > :to use the Ram Disk for reads rather than the > :normal drive. > G >   Please take the discussions of Solaris to a newsgroup more releventsH >   to the topic, unless of course this material and this information is0 >   intended to market Solaris to OpenVMS users. >   7 This posting was origionally in response to Bill Todds n5 posting about the methods that UNIX uses for type of  6 I/O. It seems prefectly reasonable to respond to this - with information about how Solaris does this.    Regardse    sC >   Hardware-based RAMdisks have been available for a long time fortD >   OpenVMS and for other platforms and have been able to operate inF >   a host-based shadowset for a while now on OpenVMS.  Software-basedF >   RAMdisks have also been available for quite some time, too.  DisksE >   and disk I/O paths have been merrily adding and enhancing cachinggH >   capabilities, too.  Though the old controller-based and non-volatileG >   caching hardware that some UNIX systems used never really caught onsJ >   with customers -- the DIGITAL offering was known as PrestoServe, IIRC. > G >   Support for disparate geometries among shadowset volumes on OpenVMS.G >   also now permits these volumes to be shadowed across any other diskaG >   volumes, so long as the total number of logical blocks match acrossrK >   all volumes in the shadowset.  It matters not if the individual members G >   of the shadowset are hardware RAMdisk, host-based software RAMdisk,mE >   emulated disk (eg: TU58), physical disk, or RAID controller.  TheaF >   shadowset volumes can be shadowed across hundreds of miles and can0 >   be accessed entirely in parallel, of course. > @ > :tmpfs is standard with the OS and uses the available physical< > :memory to get big performance gains for files that do not9 > :need to be retained. It has little or no cost but is au  > :big win for this kind of app. > H >   This is what OpenVMS uses caching or host-based RAMdisks for, thoughJ >   this is obviously a quite different approach than a "discardable" fileJ >   system such as tmpfs.  Part of the engineering work going into OpenVMSK >   involves providing file system improvements for temporary files and for)I >   applications using open-write-close-open-write-close and similar fileaJ >   processing sequences.  And a large part of the new work on the new I/OI >   caching first appears in V7.3, with additional enhancements underway.C > ? > :Ramdisk is more costly but does provide non-volatile storage:= > :you use if for different things than you use tmpfs for bute# > :it also costs much more as well.l > K >   Host-based (software-based) RAMdisks need not use non-volatile storage.y > G >   Hardware-based RAMdisks may or may not have associated non-volatiley >   storage. > P >  ---------------------------- #include <rtfaq.h> -----------------------------L >       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.comP >  --------------------------- pure personal opinion ---------------------------N >    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   --   Andrew Harrisona Enterprise IT Architecte   ------------------------------    Date: 11 Apr 2001 13:05:21 -0500+ From: young_r@encompasserve.org (Rob Young)h< Subject: Re: Solaris tmpfs (was Re: VMS-Related: Affordable)3 Message-ID: <edgi1HfYkOYC@eisner.encompasserve.org>s  g In article <ED%A6.792$fB6.20009@news.cpqcorp.net>, hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) writes:    > G >   Support for disparate geometries among shadowset volumes on OpenVMSrH >   also now permits these volumes to be shadowed across any other disk H >   volumes, so long as the total number of logical blocks match across L >   all volumes in the shadowset.  It matters not if the individual members H >   of the shadowset are hardware RAMdisk, host-based software RAMdisk, E >   emulated disk (eg: TU58), physical disk, or RAID controller.  ThesF >   shadowset volumes can be shadowed across hundreds of miles and can0 >   be accessed entirely in parallel, of course. >   B 	I apologize for misreading and/or misinterpreting a slide.  I see0 	(regarding Futures) a slide bullet that says:    % 		Decram and non-Decram mixed supporta  A 	and interpreted that to mean shadowing RamDisks wasn't supportede@ 	yet.  Seems it is, is that correct?  What then does that bullet 	mean?   				Rob    ------------------------------    Date: 11 Apr 2001 13:09:37 -0500+ From: young_r@encompasserve.org (Rob Young) < Subject: Re: Solaris tmpfs (was Re: VMS-Related: Affordable)3 Message-ID: <sjDaVOb2EaLH@eisner.encompasserve.org>   a In article <edgi1HfYkOYC@eisner.encompasserve.org>, young_r@encompasserve.org (Rob Young) writes: i > In article <ED%A6.792$fB6.20009@news.cpqcorp.net>, hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) writes:  >  >> kH >>   Support for disparate geometries among shadowset volumes on OpenVMSI >>   also now permits these volumes to be shadowed across any other disk tI >>   volumes, so long as the total number of logical blocks match across uM >>   all volumes in the shadowset.  It matters not if the individual members hI >>   of the shadowset are hardware RAMdisk, host-based software RAMdisk, eF >>   emulated disk (eg: TU58), physical disk, or RAID controller.  TheG >>   shadowset volumes can be shadowed across hundreds of miles and cane1 >>   be accessed entirely in parallel, of course.1 >> t > D > 	I apologize for misreading and/or misinterpreting a slide.  I see2 > 	(regarding Futures) a slide bullet that says:   > ' > 		Decram and non-Decram mixed supportr > C > 	and interpreted that to mean shadowing RamDisks wasn't supportediB > 	yet.  Seems it is, is that correct?  What then does that bullet > 	mean? >    	Do I get a do over?  % 	If you check out slide 50 , you see:e  ( 		"Mixing Decram and non-Decram devices"  , 		Can be shadowed but it remains unsupported  ' 		Will be supported in a future releasea  < 	Since 7.3 is "almost soup", is that what we are looking at?   				Robe   ------------------------------  % Date: Wed, 11 Apr 2001 10:01:29 +0200h! From: Didier Morandi <Dmo@ims.ch>t@ Subject: Re: strange behaviour of DIRECTORY with long file names& Message-ID: <3AD40F59.25EB76FA@ims.ch>   JF,h  . How do you succeed to use the caret character?! Which OpenVMS version do you use?    D.  = ISLKP2_dmo> crea Ceci_est_un_exemple_de_fichier_comportant^.aeM %DCL-W-PARMDEL, invalid parameter delimiter - check use of special characterst  \^\     Jean-Francois Marchal wrote: > @ > I tried to create some long file names to test an application. ../..e   ------------------------------    Date: 11 Apr 2001 10:41:48 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de>g@ Subject: Re: strange behaviour of DIRECTORY with long file namesH Message-ID: <y4bsq3u8tv.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  @ "Jean-Francois Marchal" <jean-francois.marchal@x9000.fr> writes:  C > I must add that i dint insert the ~[52466,7,0] in the file names.*I > They appeared after a rename on an initial file to have a longer name !   J I thought this was the way file names that didn't fit are returned - it is3 the file id of the file (or directory) in question.1   	Jan   ------------------------------  % Date: Wed, 11 Apr 2001 08:23:06 -0400:7 From: David Beatty <David.Beatty@sasSPAMITUPTHEZZZ.com>-@ Subject: Re: strange behaviour of DIRECTORY with long file names2 Message-ID: <hUvUOjdIAbXeIBaVXhILeA6inphl@4ax.com>  8 I was suggesting the same as Hoff -- his reply and mine # were posted at about the same time.p   Four possibilities:   6     1.  Does DSA2: have a translation?  I would assumeE          that it probably doesn't, but you might want to look anyway.g  <     2.  Any cross-linked directories, like you would find onA          the system disk?  You might be able to find out by doingt9          a DIR _DSA2:[000000...] /FILE_ID/OUTPUT=file andn          scanning the file.   3     3.  The disk or directory structure is corrupt.t  *     4.  You've found a "feature" of ODS-5.   David R. Beattyi  ; On Tue, 10 Apr 2001 21:57:39 +0200, "Jean-Francois Marchal"c' <jean-francois.marchal@x9000.fr> wrote:k  8 >Sorry .. I do not understand what you are suggesting .. > @ >X9000$CUS has only one translation, and DSA2 on which it relies9 >is the name of the disk, without any synomym anywhere ..  >tL >"David Beatty" <David.Beatty@sasSPAMITUPTHEZZZ.com> a crit dans le message. >news: NGHTOrgvE4QMsuyjw0uw37qYnYto@4ax.com... >>- >> Make that first and third translations ...a >>3 >> On Tue, 10 Apr 2001 14:39:53 -0400, David Beattye. >> <David.Beatty@sasSPAMITUPTHEZZZ.com> wrote: >> >> >9 >> >How about a SHOW LOGICAL X9000$CUS/FULL ?  Looks likewI >> >the logical has three translations, the second and third of which arev >> >concealed. >> > >> >David R. Beatty  >> >? >> >On Tue, 10 Apr 2001 19:57:26 +0200, "Jean-Francois Marchal"e+ >> ><jean-francois.marchal@x9000.fr> wrote:t >> >C >> >>I tried to create some long file names to test an application.i >> >>Created 3 files ...1 >> >>What I get after that is pretty strange ....v- >> >>For what reason do I see 3 directories ?r >> >>e >> >>e
 >> >>$ sh def   >> >>  x9000$cus:[infotel.files] >> >>$ dir *.dir& >> >>%DIRECT-W-NOFILES, no files found >> >>$
 >> >>$ dir >> >> ( >> >>Directory X9000$CUS:[Infotel.files] >> >>r >> >>gM >> >>Ceci_est_un_exemple_de_fichier_comportant^_toutes_sortes_de_caractres_aeM >> >>ccentus_et_spciaux^.dans_son_nom_^&_dans_son_extension_permis_par_la.aeM >> >>vec_un_MAXIMUM--DE--254_caractres__sans_compter_tous_les_  >> >>autres_a;1r >> >>e >> >>Total of 1 file.c >> >> / >> >>Directory DSA2:[X9000.CUS.][Infotel.files]a >> >>l >> >>wM >> >>Ceci_est_un_exemple_de_fichier_comport~[52466,7,0].avec_un_MAXIMUM--DE--rC >> >>254_caractres__sans_compter_tous_les_autres_a;1  >> >> M >> >>Ceci_est_un_exemple_de_fichier_comport~[52467,6,0].avec_un_MAXIMUM--DE-- C >> >>254_caractres__sans_compter_tous_les_autres__;1K >> >>m >> >>Total of 2 files. >> >>.( >> >>Directory X9000$CUS:[Infotel.files] >> >> G >> >>create_relative.txt;1                   create_relative_file.com;2 > >> >>DECC$CRTL.OLB;3     DECC$RTLDEF.TLB;3   LMF$LICENSE.LDB;1: >> >>rmsrel1.EXE;1       rmsrel1.for;3       rmsrel1.OBJ;1/ >> >>rudy.dat;1          tcpip$ftp_server.bck;1r >> >>VMS$LAYERED.DAT;1 >> >>  >> >>Total of 11 files.o >> >>t, >> >>Grand total of 3 directories, 14 files. >> >>$ >> >>  >> >>  >> >l   ------------------------------  % Date: Wed, 11 Apr 2001 10:56:06 +0100s* From: "Richard Brodie" <R.Brodie@rl.ac.uk>0 Subject: Re: Upgrading a 4000/60 the easy??? way, Message-ID: <9b19o9$11ne@newton.cc.rl.ac.uk>  ? "Robert Deininger" <rdeininger@mindspring.com> wrote in messagerF news:rdeininger-1004011228590001@user-2ive7ol.dialup.mindspring.com...  I > The proper thing to do would be to run DECNET_CONFIG on the new system.fK > Are you certain that DECnet startup hangs if the device isn't found?  I'd C > expect it to report the failure and let you continue, with DECnet  > basically not working.  A I've done this in the past - definitely bad news for some Phase Va> versions, if not all. I would go with removing the device from9 NET$CSMACD_STARTUP.NCL, then running the configure scriptt after booting the new system.i   ------------------------------  % Date: Wed, 11 Apr 2001 09:44:18 -0400h8 From: "Island Computers US Corp" <dbturner@islandco.com>$ Subject: Re: VMS friendly website???/ Message-ID: <td8nsc14lcit84@news.supernews.com>r   Well  F It works with Linux Red Hat 7.0 Alpha (which runs very fast on Alpha -I Thankyou) and Tru64 Unix 5.1 both being Netscape 4.76.. or something like  that ?  ; VMS ain't been tested but I don't see why it shouldn't work>H Netscape is very touchy about things it doesn't recognise when a page is designed in Frontpage.   DT   -- Island Computers US Corporation  2700 Gregory Streetl	 Suite 150  Savannah GA 31404n Tel: 912 447 6622  Fax: 912 201 0096f sales@islandco.com www.islandco.com  C This message and any files transmitted with it are confidential andyJ may be privileged and/or subject to the provisions of privacy legislation.H They are intended solely for the use of the individual or entity to whomE they are addressed. If the reader of this message is not the intendedt
 recipient,G please notify Island Computers US Corp immediately and then delete this. message.I You are notified that reliance on, disclosure of, distribution or copyings of this message is prohibited.    9 "Peter Watkinson" <peterw@u.genie.co.uk> wrote in message 6 news:3ad35a20.5731007@newshost.netscapeonline.co.uk...@ > On Tue, 10 Apr 2001 12:52:53 -0400, "Island Computers US Corp"  > <dbturner@islandco.com> wrote: >l= > >OUt of curiosity - anyone checked out website this morningeH > >We had a fella redo it for Netscape so it should work a little better > >Still uses frames though... > >f > >r > >DT  >s
 > Hi Dave, >vG > Pete opens up sewer lid crawls out and croaks - "looks OK in Netscape E > and IE Alpha NT" - crawls back under lid and returns to the depths.d >MD > PS don't sell the Low Cost Alphas too quick I want one for VMS and > Tru64. >n >  regards,b >t >p > Peter Watkinsont > Email: peterw@u.genie.co.ukw* > Internet: http://you.genie.co.uk/peterw/C > Windsurf International.com http://www.windsurf-international.com/I, > PW Navigate.com http://www.pwnavigate.com/ >a >n   ------------------------------  % Date: Wed, 11 Apr 2001 12:03:31 +0200a: From: "Gotfryd Smolik, VMS lists" <gotfryd@stanpol.com.pl>I Subject: Re: Why set PYHSICALPAGES? (was: [Q] Adding Memory to a MV 3100)eJ Message-ID: <Pine.LNX.4.21.0104111148520.23893-100000@irys.stanpol.com.pl>  $ On Tue, 10 Apr 2001, JF Mezei wrote:   +Chris Scheers wrote:s +> oJ +> I'm probably missing something obvious (that would be nothing new), but+ +> why does AUTOGEN even set PHYSICALPAGES?a    Can anyone comment some word ? 0  On one system (AS255, VMS 7.2-1, patched) have: ++++++++++++++" $ sea sys$system:modparams.dat phy' %SEARCH-I-NOMATCHES, no strings matched  $ sea sys$system:*.rep* phya' %SEARCH-I-NOMATCHES, no strings matched  $ sea sys$system:*par*.* phy   ******************************# SYS$SYSROOT:[SYSEXE]SETPARAMS.DAT;7    set PHYSICAL_MEMORY %XFFFFFFFF $ mc sysgen sho physG Parameter Name           Current    Default     Min.      Max.     Unit G --------------           -------    -------    -------   -------   ----rM PHYSICAL_MEMORY                -1         -1        10         -1 Mbytes     a $  ++++++++++++++G +> I thought that PHYSICALPAGES (and PHYSICAL_MEMORY) were only used ton% +> restrict memory for special needs.  [...]iK +But looking at various systems, PHYSICALPAGES seems to be written into thesB +parameters (both ACTIVE and CURRENT) with te actual memory value.  ,  Was memory upgraded (added) in the system ?C  Was set values for PHYSICALPAGES or PHYSICAL_MEMORY in MODPARAMS ?wH  I am only curious for the reason (means: *when* AUTOGEN sets PHY*MEM*),D may it depend of the MODPARAMS settings ? (b.ex. value "0" may *not*F mean "unlimited" but "set to current size" !). Excuse me, haven't RTFM4 on this moment :], correction and flaming allowed :)  O +Wouldn't it have been possible to have PHYSICAL PAGES set to "0" in the stored-I +parameters and then when the system boots, the active parameter reflectsnJ +actual physical memory unless overrriden by a non-zero stored parameter ?  .  You see - not. The value is "unlimited" (-1).  F +What happens when the stores PHYSICALPAGES is greater than the actualO +available memory ? Does VMS automatically adjust the memory size to match real:L +memory, or does it blindly assume that SYSGEN'S paramemer is correct at the1 +risk of writin to non existant physical memory ?s    No.G  Althought can't configm that all seen by me system has set PHY* to -1,<. but for sure much time have seen this setting.    Regards - Gotfryd= PS: fast check on one VMS 7.1-2 does the same result: PHY*=-1R -- kE =====================================================================.F $ ON F$ERROR("LANGUAGE","ENGLISH","IN_MESSAGE").GT.F$ERROR("NORMAL") - 		THEN EXCUSE/OBJECT=ME . $!                        GS@stanpol.zabrze.plE =====================================================================k   ------------------------------  % Date: Wed, 11 Apr 2001 11:11:07 +0100s* From: "Richard Brodie" <R.Brodie@rl.ac.uk>I Subject: Re: Why set PYHSICALPAGES? (was: [Q] Adding Memory to a MV 3100)s, Message-ID: <9b1ake$13as@newton.cc.rl.ac.uk>  < "Chris Scheers" <chris@applied-synergy.com> wrote in message- news:3AD36C42.D3959E24@applied-synergy.com...f  I > I'm probably missing something obvious (that would be nothing new), butf* > why does AUTOGEN even set PHYSICALPAGES?  > I believe at some point there were some edge cases on big ironB where you could cripple a machine, sometimes even to the extent it@ was unbootable, by adding real memory. The new page tables would* eat all your pool, or something like that.  A In retrospect, I'm sure silently ignoring the new memory gave DECO< support folks more grief than the original problem ever did.   ------------------------------  % Date: Wed, 11 Apr 2001 10:09:44 +0200h! From: Didier Morandi <Dmo@ims.ch>  Subject: [INFO] apologiess% Message-ID: <3AD41148.795988A@ims.ch>e  P I recently complained about a missing OpenVMS Freeware CD at my Customer's place8 and wrote that the previous system manager left with it.  I Yesterday, I found it in a safe. I apologize and ask the "previous systemo. manager" (in case he reads this) to excuse me.   D. --  6 MORANDI Consultants, Swiss Quality Computer Consulting6 avenue de Granges-Paccot 2, 1700 Fribourg  Switzerland1     Tel: +41.79.705.46.70 - Fax: +41.26.465.13.58)4  Visit our Web site at http://Didier.Morandi.Free.fr   ------------------------------  % Date: Wed, 11 Apr 2001 11:38:16 +0200e! From: Didier Morandi <Dmo@ims.ch> " Subject: [Q] %SYSTEM-I-BOOTUPGRADE& Message-ID: <3AD42608.D7EC4610@ims.ch>  M I just upgraded an Alphaserver 4100 from 7.1 to 7.2-1 and when it rebooted, It got this message:o  8 %SYSTEM-I-BOOTUPGRADE, Coordinated startup not performed   Help/messages doesn't help.r# I found this keyword on the Web in    @ http://www.openvms.compaq.com:8000/72final/6521/6521pro_002.html  E but it is the VAX upgrade manual and the information is not relevant.e, What is the meaning of this message, please?   Thanks,  D.   ------------------------------  # Date: Wed, 11 Apr 2001 16:01:27 GMTc2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)& Subject: Re: [Q] %SYSTEM-I-BOOTUPGRADE2 Message-ID: <rd%A6.788$fB6.19929@news.cpqcorp.net>  J In article <3AD42608.D7EC4610@ims.ch>, Didier Morandi <Dmo@ims.ch> writes:N :I just upgraded an Alphaserver 4100 from 7.1 to 7.2-1 and when it rebooted, I :got this message: :s9 :%SYSTEM-I-BOOTUPGRADE, Coordinated startup not performedA  H   It means that you seeing output from part of the OpenVMS upgrade, and J   it means that the OpenVMS upgrade is not performing a complete and full D   and normal upgrade.  This message is usually one of a selection ofD   messages indicating that this is NOT a normal OpenVMS bootstrap.    E   If you really want to know the details  of this message, well, you -H   (should already) know how to do this yourself by simply poking around H   inside the installation kit and inside the OpenVMS command procedures.G   (Not intending to be rude.)  In this case, please look in the OpenVMSmG   SYLOGICALS.TEMPLATE for the string "coordinated startup" -- you will  F   find some details...  A search of the OpenVMS website for the stringC   "coordinated startup" will also return a pointer to some COM for mG   OpenVMS documentation, documentation which includes a pointer to the i-   SYLOGICALS.TEMPLATE file mentioned above...p    N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------   End of INFO-VAX 2001.203 ************************