1 INFO-VAX	Mon, 02 Jul 2001	Volume 2001 : Issue 363       Contents:+ Re: A black week for the computer industry?  Re: a letter from Rich Marcello  RE: Anonymous FTP and TCPIP 5.1  Re: C-Kermit 8.0 Beta  Re: C-Kermit 8.0 Beta * Re: Capellas admits move anti-competitive?0 Re: Combining lines of DCL code into one line???0 Re: Combining lines of DCL code into one line???D Re: Compilers go to Intel, hobbyist, CSLG, etc. goes out the window?D Re: Compilers go to Intel, hobbyist, CSLG, etc. goes out the window? Re: FUD * Re: Hobby LIcense: One USER, or one LOGIN?; Re: I  (of all people) just got a letter from Rich Marcello  RE: Mozilla 0.9 on 7.3 RE: Mozilla 0.9 on 7.3 Mozilla 9.0 on 7.3 owner of a file  Re: owner of a file  Qlogic question 
 Re: Rdb troll  Re: RMS file performance Re: RMS file performance Re: Tapesys and VMS 7.3  Re: The Alpha/IA64 Hybrid  Re: The Alpha/IA64 Hybrid  Re: The Alpha/IA64 Hybrid  Re: The Alpha/IA64 Hybrid 1 Re: The death of VMS has been greatly exaggerated 1 Re: The death of VMS has been greatly exaggerated ( Re: Using SCSI controller on QBUS system Re: VMS 7.3 experiences? VMS installation Probs from CD. # Re: VMS installation Probs from CD. # Re: VMS installation Probs from CD. , VMS721_UPDATE V0300 ECO regresses DEC$BASRTL/ Re: Yet Another Reason Why Windoze .ne. OpenVMS / RE: Yet Another Reason Why Windoze .ne. OpenVMS   F ----------------------------------------------------------------------  # Date: Sun, 01 Jul 2001 18:51:31 GMT 4 From: "Terry C. Shannon" <terryshannon@mediaone.net>4 Subject: Re: A black week for the computer industry?; Message-ID: <TiK%6.998$9r6.1588097@typhoon.ne.mediaone.net>   2 "Bill Todd" <billtodd@foo.mv.com> wrote in message" news:9hno9r$2p9$1@pyrite.mv.net...    K > So for VMS's fortunes to *rise*, Compaq will need to do what it has shown  no@ > interest in doing for 3 years now:  actually *market* and more aggressivelyF > develop VMS to indicate to potential new customers that Compaq is as8 > committed to the platform as it would like them to be.   Yep!   ------------------------------  # Date: Sun, 01 Jul 2001 15:31:37 GMT 4 From: "Terry C. Shannon" <terryshannon@mediaone.net>( Subject: Re: a letter from Rich Marcello; Message-ID: <tnH%6.829$9r6.1506433@typhoon.ne.mediaone.net>   C <gazso@ludens.elte.hu> wrote in message news:LILPgltBUDuQ@ludens...  > Rich Marcello wrote in  > > ----- Original Message ----- > A > >> First let me assure you that Compaq will immediately begin a < > >> full port of the Tru64 UNIX, OpenVMS and NonStop Kernel; > >> operating systems and development tools to the Itanium < > >> processor family. This means that all of the enterpriseA > >> features and characteristics that you have relied on will be = > >> there on the Itanium platform. Additionally, Compaq will < > >> continue development and enhancement of these operatingA > >> system environments ensuring that we can continue to deliver 5 > >> leadership capabilities - such as clustering and < > >> availability. Our intention is to have our first Compaq? > >> Itanium-based systems for Tru64 UNIX and OpenVMS available = > >> in 2003 for early ISV testing and generally available in 
 > >> 2004. > ' > Seems here it is what I asked for :-)  > ; > >>                                           Compaq's top > > >> priorities for Alpha-based systems remain unchanged -- to? > >> deliver improved performance and faster implementations of ; > >> the Alpha microprocessor to meet committed performance 7 > >> enhancements, while continuing to provide the most 4 > >> available, scalable systems at the lowest cost.4 >                                ^^^^^^^^^^^^^^^^^^^C > I very hope that it could mean a widening on the hobbyist program D > or an OpenVMS/Home use license at a low cost... Then we could tell? > "Try OpenVMS from Compaq" to our friends, and show how to use B > it as well, tell about the security and the reliability - CompaqI > won't be able to find such an efficient mean of adverisment I guess :-)   H Note that this is a generic customer letter. Last time I saw Mark GorhamE (about four weeks ago) he and his Director of Marketing said that the K educational license program would be improved, the June 25 announcement has + no negative impact on the Hobbyist Program.    > 7 > (let the goat suffice and the cabbage remain as well)  > G > Smposium: that seems to be a good idea, some people of this newsgroup D > living in America could tell Compaq the concerns discussed here... > Will be there someone?  K Oh, probably a lot of "someones." The CETS2001 team is working on adjusting E the schedule to include Q&A and customer feedback sessions on the IFP E transition. These being in addition to the usual Compaq Listens panel  session.   ------------------------------  , Date: Sun, 01 Jul 2001 17:24:04 +0200 (CEST)- From: Freddy Meerwaldt <frederik@freddym.org> ( Subject: RE: Anonymous FTP and TCPIP 5.1K Message-ID: <Pine.LNX.4.21.0107011720230.29064-100000@firewall.freddym.org>    Hi Tom,  Hi comp.os.vms,   C sorry that I have to post this to comp.os.vms, too, but Tom, I have / problems sending E-Mails to your E-Mail Adress: G I always get a mail from Mail Delivery Subsystem back, that relaying to I kednos.com was denied due to excessive spam from webmailer.de (which is a & normal ISP here in Germany.... *sigh*)E Could you please supply me with another E-Mail Adress, so that we can  communicate os-newsgroup, too?   But here the answer:  N > Did you get this working?  I think there is a bug in the install process for > ftp.L > It doesn't create the ANONYMOUS account.  Did it do it for you, or did you > have to do it * > yourself?  If so, how did you set it up?   I did get it running. J I checked the Audit log (didn't think of it before) - and the problem was,+ that it couldn't write to dka0:[tcpip$ftp]. E I just stopped tcpip, then deleted the directory and then started the D services (the directory was re-created), and then I set up the whole# anonymous account again - worked :)    Thanks, Tom 
 Best Regards,  	Freddy    --  N Geek Code 3.1: GCS s+: a--- C+++ UBOU+++ P-- E--- W++ N w--- V++ PGP- t? 5? tv  J ==========================================================================D  Frederik Meerwaldt  ICQ: 83045387  Homepage: http://www.freddym.orgC  Bavaria/Germany              OpenVMS and Unix Howtos and much more I  Solaris, HP/UX, AIX, NetBSD, OpenBSD, IRIX, Tru64, OpenVMS, Ultrix, BeOS    ------------------------------  $ Date: Mon, 2 Jul 2001 00:09:52 +01001 From: "Chris Townley" <news@townleyc.demon.co.uk>  Subject: Re: C-Kermit 8.0 Beta? Message-ID: <994029010.909.0.nnrp-08.d4e45fa5@news.demon.co.uk>   I I will have a go on my hobbyist alpha (Compaq C V6.2-008 on OpenVMS Alpha  V7.3)   F However I could not get the download - got a message that IE could not0 download - server returned extended information.  K I will hook it down at work and have a go on Monday or Tuesday. Do you want  the executables?   --
 Chris Townley  chris@townleyc.demon.co.uk townleyc@spicers.ltd.uk     = "Frank da Cruz" <fdc@watsun.cc.columbia.edu> wrote in message / news:9hlfsf$10m$1@newsmaster.cc.columbia.edu...  > E > I announced C-Kermit 8.0 Beta.02 yesterday on the Kermit newsgroup:  >  >   comp.protocols.kermit.misc >  > You can find it here:  > , >   http://www.columbia.edu/kermit/ck80.html > D > Of course I still keep the VMS version current, and built this oneC > on 5.5 through 7.2 with and without various TCP/IP packages (TGV,  > UCX, TCPware, etc).  > C > Can somebody who has VMS 7.3 and a C compiler please try building 1 > it there?  (Was VMS 7.3 also released for VAX?)  >  > Other builds are needed too: >  >  . Any pre-5.5 VMS version  >  . VMS 6-point-anything on VAX > I > By the way, the new release of C-Kermit includes a built-in FTP client, H > which, because it's built-in to C-Kermit, is also fully scriptable andC > has all the other Kermit file transfer features, such as restart, F > automatic text/binary-mode switching, character-set translation, andL > cross-platform recursive directory-tree transfer.  But it's only for UNIX.I > That's because it would take a better VMS programmer than I am to adapt I > it to VMS, mainly because of all the RMS aspects and the associated FTP H > protocol tricks used for VMS-to-VMS transfers and/or exporting bizarreH > VMS file formats to non-VMS systems, etc.  If anybody is interested in > taking this on, let me know. > F > C-Kermit 8.0 also includes all sorts of security: Kerberos IV and V,G > SSL/TLS, and SRP.  That hasn't been ported to VMS either.  Same deal.  >  > - Frank <fdc@columbia.edu>   ------------------------------   Date: 1 Jul 2001 23:36:33 GMT 0 From: fdc@watsun.cc.columbia.edu (Frank da Cruz) Subject: Re: C-Kermit 8.0 Beta5 Message-ID: <9hoc61$qit$1@newsmaster.cc.columbia.edu>   ? In article <994029010.909.0.nnrp-08.d4e45fa5@news.demon.co.uk>, 0 Chris Townley <news@townleyc.demon.co.uk> wrote:K : I will have a go on my hobbyist alpha (Compaq C V6.2-008 on OpenVMS Alpha  : V7.3)  : H : However I could not get the download - got a message that IE could not2 : download - server returned extended information. : # Oops, typo in the link!  Fixed now:   9   ftp://kermit.columbia.edu/kermit/test/tar/ckv200b02.zip    Thanks for noticing.  M : I will hook it down at work and have a go on Monday or Tuesday. Do you want  : the executables? : E Yes, please.  Here are instructions for VMS C-Kermit binary builders:   : Here's how to build VMS C-Kermit 8.0.200 Beta.02 binaries.: Note: Replace all "200b02" below with whatever the current0 edit number and Alpha/Beta designation might be.  #  . Download the VMS source archive: <      ftp://kermit.columbia.edu/kermit/test/tar/ckv200b02.zip  "  . Unzip it into a fresh directory1    (Let me know if you don't have VMS ZIP/UNZIP).     On each VMS computer:     . Build the network version:   3    @ckvker  (or use "@ckvker m" if "@ckvker" fails)   F    This makes a WERMIT.EXE file, which you can run and use as a Telnet$    client, etc.  Copy WERMIT.EXE to:  "      ckv200b02-PPP-vmsVV-ucxUU.exe  	    where:   %      PPP the platform: "vax" or "axp" ?      VV is the VMS version (two digits, no period) e.g. 62, 73. ?      VV is the UCX version (two digits, no period) e.g. 41, 51.       For example:   "      ckv200b02-axp-vms72-ucx51.exe"      ckv200b02-vax-vms62-ucx41.exe  "  . Build the non-networks version:  8    @ckvker n  (or use "@ckvker mn" if "@ckvker n" fails)  M    Rename the non-nets WERMIT.EXE as above, except put "nonet" in the network     field, for example:  "      ckv200b02-vax-vms62-nonet.exe"      ckv200b02-vax-vms73-nonet.exe  A  . Upload all the ckv200b02-*-vms*-*.exe files in binary mode to:   /      ftp://kermit.columbia.edu/kermit/incoming/   :  . Delete all the ckv200b02-*-vms*-*.exe files if desired.   - Frank    ------------------------------  % Date: Sun, 01 Jul 2001 19:43:02 -0400 ( From: Hamlyn Mootoo <univms@bigfoot.com>3 Subject: Re: Capellas admits move anti-competitive? + Message-ID: <3B3FB586.A45D654D@bigfoot.com>    mulp wrote: L > Those aren't the relevant issues.  The questions are 1) whether the mergerL > of businesses tends to create a monopoly where one didn't previously exist  F This is a matter for possibly the SEC and/or FTC.  I don't believe itsF actionable (I was responding to the query about whether  "good" lawyerF could make something of it), and if it is, what would be your cause of action in a civil suit?   E > and 2) whether it violates the terms of an agreement between the US J > government, Digital, and Intel, that Compaq then ratified to ensure that3 > Alpha remains an independent competitor to Intel.   " What agreement?  Please elaborate.   > M > The latter required that Compaq find two foundaries for Alpha besides Intel @ > and that there be at least one independent holder of Alpha IP.   ------------------------------  % Date: Sun, 01 Jul 2001 14:10:50 -0500 ' From: Steve Sparrow <sdsparrow@aol.com> 9 Subject: Re: Combining lines of DCL code into one line??? O Message-ID: <7B9EB60E3052EB23.BDB4232C9BA200E4.AF096470DAA86A0E@lp.airnews.net>    Bob Kaplow wrote:  > H > I'm trying to do some maybe not quite so simple stuff in a DCL commandN > procedure. It seems in each of these two cases, I should be able to condenseM > 2 or 3 lines of DCL into a single line that doesn't use temporary variables I > to store intermediate results, but so far I've failed to figure out the M > right syntax. Anyone able to show me how to do this? I can't afford to lose  > any more of my hair :-)  >  > $!C > $!      set default to directory that this command file is in ...  > $!D > $ dddev = ''f$parse("''f$environment(""procedure"")'",,,"device")'G > $ dddir = ''f$parse("''f$environment(""procedure"")'",,,"directory")'  > $ set default 'dddev''dddir' > $!0 > $!      set process name to procedure name ... > $!? > $ name  = f$parse("''f$environment(""procedure"")'",,,"name") * > $ set proc /name='f$extract(0, 15, name) > $! >  > advTHANKSance    Personally, I like this one:> $ there = f$parse("A.A;", f$environment("procedure")) - "A.A;" $ set default 'there'  $ !...= $ write sys$output "About to clear out the current directory" 6 $ if f$environment("default") .nes. there then exit 44F $ if f$environment("default") .eqs. f$trnlnm("sys$login") then exit 44 $ delete *.*;*  D I include that last bit for folks that write dcl routines for othersJ where the routine clears out the directory before doing doing the next run   ------------------------------   Date: 1 Jul 2001 19:30:30 -0700 - From: afeldman@gfigroup.com (Alan E. Feldman) 9 Subject: Re: Combining lines of DCL code into one line??? = Message-ID: <af1e4ce6.0107011830.51ae5131@posting.google.com>   p Guy Sherr <guy.sherr-nospam@mail.com> wrote in message news:<Xns90CFEBB7CB89Fguysherrmailcom@207.126.101.100>...> > kaplow_r@eisner.encompasserve.org.mars (Bob Kaplow) wrote in. > news:$HC0KlS3oAVD@eisner.encompasserve.org:  >  [stuff omitted] J > > $ dddev     = ''f$parse("''f$environment(""procedure"")'",,,"device")'M > > $ dddir     = ''f$parse("''f$environment(""procedure"")'",,,"directory")'   > > $ set default 'dddev''dddir'   I use   + $    PROCEDURE = F$ENVIRONMENT("PROCEDURE")  $    PROCEDURE_LOCATION - )         = F$PARSE(PROCEDURE,,,"DEVICE") +   F$PARSE(PROCEDURE,,,"DIRECTORY")B $    LATEST_PROCEDURE = PROCEDURE - F$PARSE(PROCEDURE,,,"VERSION")% $    SET DEFAULT 'PROCEDURE_LOCATION'   E If you must get it in one line, see the other posts. I use the symbol F LATEST_PROCEDURE when I want a self-resubmitting batch job to resubmitA the most current version of itself. Other posts have answered the  process name question.   [more stuff omitted]  D In apparent reference to the original poster's use of double quotes:  J > The double quotes mostly don't need to be there.  All they really do is  > preserve case.    1 Actually, the double quotes do not preserve case:    DCL> TYPE EXAMPLE.COM  $    AEF_DIR = "SYS$LOGIN:" : $    EV "BEGIN ''F$STRING(aef_dir)' ''F$STRING("aef_dir")' ''F$STRING(""aef_dir"")' END"  DCL>
 DCL> @EXAMPLE  $    AEF_DIR = "SYS$LOGIN:" . $    EV "BEGIN SYS$LOGIN: aef_dir AEF_DIR END"$ BEGIN SYS$LOGIN: aef_dir AEF_DIR END  C (EV equals WRITE SYS$OUTPUT.) As you can see, using aef_dir without E any quotes yields the value of the symbol; using single quotes yields ? a case-preserved aef_dir; using double quotes yields an upcased  AEF_DIR!  @ In fact, whenever you are evaluating a lexical function inside a? quoted string, single quotes inside the lexical function is the D correct usage. Here are some examples where double quotes don't work at all.    DCL> TYPE EXAMPLE2.COM  $    DEFINE AEF_DISK DISK$DATA1: $    AEF_DIR = "SYS$LOGIN:" 8 $    EV "BEGIN 1 ''F$GETDVI(""DKA200:"","DIR")' END "   : $    EV "BEGIN 2 ''F$GETDVI(""AEF_DISK:"","DIR")' END "   , $    EV "BEGIN 3 ''F$CVTIME(""2:35"")' END "1 $    EV "BEGIN 4 ''F$PARSE(AEF_DIR+""[]"")' END " 9 $    EV "BEGIN 5 ''F$PARSE(AEF_DIR+""LOGIN.COM"")' END "  	 $    exit  DCL> DCL> @EXAMPLE2;   $    DEFINE AEF_DISK DISK$DATA1:@ %DCL-I-SUPERSEDE, previous value of AEF_DISK has been superseded $    AEF_DIR = "SYS$LOGIN:" ? %DCL-W-ARGREQ, missing argument - supply all required arguments   \0\? %DCL-W-ARGREQ, missing argument - supply all required argumentss  \K\@ %DCL-W-SYMDEL, invalid symbol or value delimiter - check command syntax  \2\@ %DCL-W-SYMDEL, invalid symbol or value delimiter - check command syntax  \"\C %DCL-W-IVOPER, unrecognized operator in expression - check spelling 
 and syntax	  \.COM""\c	 $    exite  C Evidently, you get interesting errors when you use double quotes inrF these cases. If you change all the double quotes to single quotes, all' the commands in EXAMPLE2.COM work fine.t   [yet more stuff omitted]   Disclaimer: JMHO         n Alan E. Feldman          o afeldman&gfigroup.comf   ------------------------------  # Date: Sun, 01 Jul 2001 15:33:44 GMTl4 From: "Terry C. Shannon" <terryshannon@mediaone.net>M Subject: Re: Compilers go to Intel, hobbyist, CSLG, etc. goes out the window?m; Message-ID: <spH%6.830$9r6.1507630@typhoon.ne.mediaone.net>e  ? "Robert Deininger" <rdeininger@mindspring.com> wrote in message/F news:rdeininger-0107011105430001@user-2ive66e.dialup.mindspring.com...G > In article <Wxr%6.734$9r6.1193182@typhoon.ne.mediaone.net>, "Terry C.n- > Shannon" <terryshannon@mediaone.net> wrote:t >aJ > > A month ago Mark Gorham said he was gonna fix the educational license, dunnoo> > > if the Grand Transition will have any effect on this plan. > J > And Marcello said the same thing in December.  Progress is slow, leading% > some folks to say it doesn't exist.- >-  F FWIW Mr. Gorham was pretty specific. Far more so than was Rich back in	 December.   J > Some folks like bad news, as it gives them something to bitch about, and2 > thus a reason to arise and draw breath each day. >6  K It seemed to work pretty well in the Army, especially in the lower enlistedn	 rank. ;-}e   ------------------------------  % Date: Sun, 01 Jul 2001 11:05:42 -0400m2 From: rdeininger@mindspring.com (Robert Deininger)M Subject: Re: Compilers go to Intel, hobbyist, CSLG, etc. goes out the window?oL Message-ID: <rdeininger-0107011105430001@user-2ive66e.dialup.mindspring.com>  E In article <Wxr%6.734$9r6.1193182@typhoon.ne.mediaone.net>, "Terry C.-+ Shannon" <terryshannon@mediaone.net> wrote:    N > A month ago Mark Gorham said he was gonna fix the educational license, dunno< > if the Grand Transition will have any effect on this plan.  H And Marcello said the same thing in December.  Progress is slow, leading# some folks to say it doesn't exist.n  H Some folks like bad news, as it gives them something to bitch about, and0 thus a reason to arise and draw breath each day.   -- 6 Robert Deininger rdeininger@mindspring.coma   ------------------------------   Date: 1 Jul 2001 18:16:04 -0400m/ From: jordan@lisa.gemair.com (Jordan Henderson)f Subject: Re: FUD* Message-ID: <9ho7f4$9o3$1@lisa.gemair.com>  ' In article <3B3E0D77.E03ECA98@fsi.net>,n0 David J. Dachtera <djesys.nospam@fsi.net> wrote: >Larry Kilgallen wrote:a >>  [ >> In article <3B3CF79E.FD041A24@infopuls.com>, Christof Brass <brass@infopuls.com> writes:i >> s< >> > My experience with Slowaris on SPARC isn't quite good -> >> > especially the NFS and NIS+ related parts are a source of= >> > problems. Some servers with certain functions have to bed! >> > rebooted monthly (at least).. >>  I >> I know a Solaris-centric shop that wanted to reboot their VMS machines 5 >> each month because that is "normal" for computers.h >aI >Recent real-life lesson: it is possible to get so accustomed to machinesaB >that *DON'T* need to be rebooted that the procedures to shutdown,H >startup and/or reboot become lost artifacts due to a number of factors. > ? >Unless uptime demands are such that scheduled downtime is near 9 >impossible, I don't necessarily view this as a negative.t >   E I think that it can be a good idea to reboot VMS machines, if you canl+ afford the luxury, in certain environments.   D If you have many people who have overlapping responsibilities towardE system configuration files that only come into play on bootup AND youaE don't have a strict change control procedure THEN it's not a bad ideatC to schedule a reboot at a time when all the people who might changeaE things that pertain to backups (including both system and applicationdD configuration) are available so as to catch bombs someone might have. thrown into your system since the last reboot.  D At one shop I worked in, the machines would only need to be rebootedC on the order of years for upgrades or system/hardware problems.  InuF such an environment, there can be inconsistencies that have crept intoF your configuration files by people who are not even around anymore and can be difficult to unravel.  G I feel that the correct discipline is to have all system configuration  F in CMS and actually have checks in place that alarm unexpected changes? in production systems, but it's a lot of infrastructure that's  7 difficult to get buy-in from management and co-workers.r   >--  >David J. Dachtera >dba DJE Systems >http://www.djesys.com/  >n; >Unofficial Affordable OpenVMS Home Page and Message Board:   >http://www.djesys.com/vms/soho/ > G >This *IS* an OpenVMS-related newsgroup. So, a certain bias in postingss >is to be expected.r >MA >Feel free to exercise your rights of free speech and expression., >aG >However, attacks against individual posters, or groups of posters, arer >strongly discouraged.   -Jordan Henderson. jordan@greenapple.coml   ------------------------------  % Date: Sun, 01 Jul 2001 17:17:20 +0200n2 From: martin@radiogaga.harz.de (Martin Vorlaender)3 Subject: Re: Hobby LIcense: One USER, or one LOGIN?a; Message-ID: <3b3f3f00.524144494f47414741@radiogaga.harz.de>o  ! Hans Vlems (hvlems@iae.nl) wrote:u0 > Mark Vance <mvance@iglou.com> wrote in message% > news:3B3DF757.FA66C5EE@iglou.com... G > > Does the hobbyist license confine you to ONE USER at a time, or one," > > LOGIN of one user at one time. >$F > Assuming that the hobbyist license uses LMF, it depends on what type > of VMS license you have.  > Is it an A, B, C or D license?  3 The hobbyist VMS license is a class A, 0 units one.    cu,    Martin -- rD                         | Martin Vorlaender  |  VMS & WNT programmer1  VMS is today what      | work: mv@pdv-systeme.de=E  Microsoft wants        |    http://www.pdv-systeme.de/users/martinv/e8  Windows NT 8.0 to be!  | home: martin@radiogaga.harz.de   ------------------------------  $ Date: Sun, 1 Jul 2001 22:30:35 +0200* From: dwparsons@t-online.de (Dave Parsons)D Subject: Re: I  (of all people) just got a letter from Rich MarcelloP Message-ID: <Ej0w7lFo08Zw-pn2-K1LDddZcQRvn@jupiter.dwparsons.dialin.t-online.de>  1 Not everyone in europe, I received mine by email.0   Dave  @ On Sun, 1 Jul 2001 10:26:51, "Hans Vlems" <hvlems@iae.nl> wrote:  , > Correct. In Europe we got it by snailmail. > ? > Terry C. Shannon <terryshannon@mediaone.net> wrote in messageE7 > news:6It%6.745$9r6.1232620@typhoon.ne.mediaone.net...o > > > > > "Joe Heimann" <heimann@nog.ecs.umass.edu> wrote in message) > > news:9hlkh7$i0$1@odo.ecs.umass.edu... ) > > > Joe <cstranslations@msn.com> wrote:e& > > > > I just got an email from Rich. > >w > > > > Joem > > >>L > > > I got the same message, looks like it may have been sent to all DECUS/& > > > Encompass registered membership. > >hK > > Yep, this appears to be the case. Given the timing of the announcement,iI > > CETS2001 will likely be the earliest opportunity to get all the lurid $ > > details on the Alpha-->IPF move. > >uL > > Of course, this throws the CETS2001 content development team in overtimeE > > mode, as the existing session schedule will have to be overhauledC > big-time!a > >y > >d >  >    ------------------------------  % Date: Sun, 01 Jul 2001 11:14:46 -0700e! From: Tom Linden <tom@kednos.com>v Subject: RE: Mozilla 0.9 on 7.3 9 Message-ID: <CIEJLCMNHNNDLLOOGNJIMEGACOAA.tom@kednos.com>d   Typo   > -----Original Message-----* > From: Tom Linden [mailto:tom@KEDNOS.COM]& > Sent: Sunday, July 01, 2001 11:04 AM > To: Info-VAX@Mvb.Saic.Coms > Subject: Mozilla 9.0 on 7.3e >b >rB > I downloaded and installed the latest mozilla on a 433au running
 > 7.3.  It iso
 > much slowerrL > than IE on a 544 dual Celeron running W2K, but that may be because it only > has 128MB of* > memory.  It is time to get Opera ported! >eA > How does one get it into the Personal Applictions pop-up menu ?S
 > That shouldrJ > have been included in the install, which otherwise went smoothly withoutL > intervention, except for a misleading  error in the install documentation, > I.E. >s' > $ PRODUCT INSTALL MOZILLA/SOURCE=KITS, >  > It is sufficient witha > $ PRODUCT INSTALL MOZILLAr >S   ------------------------------  $ Date: Sun, 1 Jul 2001 17:16:21 -0400  From: John Santos <JOHN@egh.com> Subject: RE: Mozilla 0.9 on 7.3a4 Message-ID: <1010701170814.357A-100000@Ives.egh.com>  % On Sun, 1 Jul 2001, Tom Linden wrote:o   > Typo >  > > -----Original Message-----, > > From: Tom Linden [mailto:tom@KEDNOS.COM]( > > Sent: Sunday, July 01, 2001 11:04 AM > > To: Info-VAX@Mvb.Saic.Com  > > Subject: Mozilla 9.0 on 7.3M > >h > > D > > I downloaded and installed the latest mozilla on a 433au running > > 7.3.  It is  > > much slower N > > than IE on a 544 dual Celeron running W2K, but that may be because it only > > has 128MB of, > > memory.  It is time to get Opera ported! > >nC > > How does one get it into the Personal Applictions pop-up menu ?T > > That shouldnL > > have been included in the install, which otherwise went smoothly withoutN > > intervention, except for a misleading  error in the install documentation, > > I.E. > >c) > > $ PRODUCT INSTALL MOZILLA/SOURCE=KITSe > >d > > It is sufficient withs > > $ PRODUCT INSTALL MOZILLAa  G Just to clarify: the "/source" issue is a PCSI matter, and doesn't havecG anything specifically to do with MOZILLA (except that it is the MOZILLAu9 docs that are misleading, if I understand you correctly.)   E PCSI looks for kits in the current directory, unless you have told itvD to look elsewhere by either defining the logical name PCSI$SOURCE or  by using the /SOURCE= qualifier.  D The MOZILLA docs shouldn't be assuming what directory you downloadedE the kit into, unless they also give specific instructions about where(G to put it.  (They shouldn't do this; they should allow for flexibility,iD but sometimes it is easier to say "Step 1: put it in [foo].  Step 2:B Install from [foo]" than to say "Step 1: put it anywhere you like.< Step 2: Install from the place where you put it in step 1.")   -- k John Santos  Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  % Date: Sun, 01 Jul 2001 11:03:57 -0700v! From: Tom Linden <tom@kednos.com>v Subject: Mozilla 9.0 on 7.3l9 Message-ID: <CIEJLCMNHNNDLLOOGNJIEEGACOAA.tom@kednos.com>   L I downloaded and installed the latest mozilla on a 433au running 7.3.  It is much slowerlJ than IE on a 544 dual Celeron running W2K, but that may be because it only has 128MB of( memory.  It is time to get Opera ported!  L How does one get it into the Personal Applictions pop-up menu ?  That shouldH have been included in the install, which otherwise went smoothly withoutJ intervention, except for a misleading  error in the install documentation, I.E.  % $ PRODUCT INSTALL MOZILLA/SOURCE=KITSy   It is sufficient withr $ PRODUCT INSTALL MOZILLAr   ------------------------------  $ Date: Sun, 1 Jul 2001 23:09:27 +0200$ From: "@nnib" <annibale@ifrance.com> Subject: owner of a file3 Message-ID: <9ho3eu$18t$1@aldebaran.worldonline.fr>u   Hi,    i'm newbie in VMSi  D I need to change the owner of a file     ( like chown in unix world) How can i do that.....   Thanks @nnibe   ------------------------------  $ Date: Sun, 1 Jul 2001 17:44:07 -0400  From: John Santos <JOHN@egh.com> Subject: Re: owner of a file4 Message-ID: <1010701174004.357C-100000@Ives.egh.com>    On Sun, 1 Jul 2001, @nnib wrote:   > Hi,l >  > i'm newbie in VMS- > F > I need to change the owner of a file     ( like chown in unix world) > How can i do that..... >  > Thanks > @nnibm   $ set file/owner=new_owner   See help.  It is useful.  F See the FAQ.  It tells you about help (and many other useful tidbits.)E The FAQ is posted to this newsgroup every few months and is availablet
 online at:  "     http://www.openvms.compaq.com/.     ftp://rtfm.mit.edu/pub/usenet/comp.os.vms/,     comp.answers and news.answers newsgroups   -- s John Santosr Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  % Date: Sun, 01 Jul 2001 20:35:48 -0600  From: yyyc186@mindspring.com Subject: Qlogic question; Message-ID: <3b3fde9f$1$lllp186$mr2ice@nntp.mindspring.com>t   All,  I I have an Alpha PC164 running VMS and the SRM console.  All was well witheG a pair of 18Gig drives in it.  Today I installed an extra 34Gig drive IeD had laying around.  No biggie...until I checked the drive size afterG initing.  Shows up as 8Gig.  When running the FWUPDATE program it loadseB the driver for Qlisp10x0.  Is this a known "feature" of the QlogicJ controller?  I have seen other older SCSI controllers which cap out around 20Gig.  J Is their a controller BIOS Flash available?  I can stick the controller in$ a regular PC and flash it if needed.   Thanks,t Roland   -- c; -----------------------------------------------------------4 yyyc186@mindspring.com; -----------------------------------------------------------*   ------------------------------   Date: 1 Jul 2001 22:40:53 -0700t+ From: msfrancisusa@netscape.net (M.Francis)o Subject: Re: Rdb troll= Message-ID: <a6cbd3e3.0107012140.1f94bf58@posting.google.com>1   > Malcolm Dunnett wrote: > F > >    The Rdb development group sent an email out ( presumably to all@ > > Rdb customers ) this morning talking about the announcement. > >. > M > I'm an RDB and DBMS customer and have not received any email. I have spokenFJ > verbally to an Oracle RDB and he said something similar to the email youB > have quoted below. I need something more solid than that really.  ; You can only get something more solid once they themselves (# have come up with an approach, no? d  C I received the letter mentioned above, (from Kevin Duffy ?), in an ,> email format. It does appear that they were caught unaware by  the Compaq announcement.  ? Albeit stating the obvious, but I doubt Oracle would have such R? drastically self-defeating strategy as to keep the Rdb team in T= the dark as the engineering trend todate has been to combine  3 innovations, really all the DBMSes and middlewares  8 in the world will soon be offering the same features. ;)  C In anycase, I know I am on the receiving end of email news perhaps hD from metalink settings, or perhaps from having attended a technical  forum way back in '98...   cheers,t Mary   ------------------------------  % Date: Sun, 01 Jul 2001 10:09:03 -0500 1 From: "David J. Dachtera" <djesys.nospam@fsi.net>l! Subject: Re: RMS file performances& Message-ID: <3B3F3D0F.247069D@fsi.net>   Kenneth wrote: > J > Beside file fragmentation, what statistic should I check to for the poor) > performance of the index type RMS file?T  F The count of duplicate records for any key, especially alternate keys.   --   David J. DachteraN dba DJE Systems  http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/   F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.    ------------------------------  % Date: Sun, 01 Jul 2001 18:42:43 -0400 ( From: Hamlyn Mootoo <univms@bigfoot.com>! Subject: Re: RMS file performanceA+ Message-ID: <3B3FA763.386E09D6@bigfoot.com>G  @ You can use the SET FILE/STATISTICS command on any files you are> interested in, then use the MONITOR utility to gather valuableH information on these files. Aside from checking statistics, you can tuneE your RMS indexed files by spitting out an FDL using ANALYZE/RMS, thenCH using EDIT/FDL to do "what-if" scenarios using this FDL.  The main thingF that you want to try to do is get your index depth for each index to 4E or under (lower is better).  To do this you may have to adjust one or < more of several parameters such as bucket size, fill factor,F compression, etc. Just keep in mind that there are trade-offs for eachE parameter you adjust.  These trade-offs depend on whether the file isrB mainly sequentially accessed, or more randomly accessed by key(s),H whether operations to it are more read intensive or write intensive, howH fast your cpu is and whether you are running with lots free cpu time (inG the case of turning on compression), etc. After you get the FDL the waymF you want it use CONVERT/FDL (using the FDL you created) to convert the file to the new structure.     HM     Kenneth wrote: > J > Beside file fragmentation, what statistic should I check to for the poor) > performance of the index type RMS file?a   ------------------------------   Date: 1 Jul 2001 10:06:31 CDTS= From: wayne@tachysoft.xxx.320117.killspam.015d (Wayne Sewell)6  Subject: Re: Tapesys and VMS 7.3. Message-ID: <aOqNQftAM1lH@tachxxsoftxxconsult>  R In article <3B3E5827.1DFE93AE@virgin.net>, Alan Greig <a.greig@virgin.net> writes: > Ed Wilts wrote:% > , >> Here's a non-Itanium post for a change... >>M >> Has anyone upgrade to VMS 7.3 yet and experienced any Tapesys issues?  TheaM >> official story from Software Partners is that we need Tapesys 6.0 which issM >> currently in development.  They say they've done some brief testing on 7.3gN >> with the current version of Tapesys (5.2.25) and it appears to work, but itM >> won't be supported.  Has anyone gone farther than that yet?  How likely am K >> I to experience problems farther down the road that brief testing hasn't   >> found?  Wayne, you out there?    
 Yeah.  :-)  J I've been running 7.3 pretty much exclusively on my test alpha and haven'tM really noticed any difference as far as tapesys is concerned.  Of course, I'm0N running tapesys 6.0 instead of 5.2.x, because that's what I'm testing.  I *do*K have one 7.3 machine running my production 5.2.x tapesys.  Admittedly, thatoJ machine is not running either of the DB processes, just an RQ, and I don't$ normally do backups on that machine.  L I will try to do a couple as time permits.  But of course, tapesys 6.0 is my focus right now.   > O > I did a quick test of Tapesys under 7.3 EFT2 and everything seemed to work. ITN > know there is a problem with ODS-5 disks but that doesn't just apply to 7.3.L > The problem is not that data does not get backed up correctly but that theQ > index files holding the backed up files details can't deal with some ODS-5 filea > names.    J Yes, ods-5 throws the tapesys 5.2.x history database for a loop.  Both theI expanded lengths and the special characters make the permitted file namesmM radically different.  And of course the complete file names have to be storedD1 in the history database.  It's the whole point.  E  N You can run ods-5 backups just fine on 5.2.x; you just can't specify a historyL set.  You might receive warning messages from sysbak.exe about too-long fileN names, but these can be ignored.  sysbak is trying to write the history updateL file, which has too short a record size for ods-5; it doesn't know you won'tN actually be *using* the history update file.  sysbak.bis has that information.    L The history database is completely redesigned for 6.0.  Under 5.2.x, historyG entries contain the complete file spec, including everything except the"N top-level directory, which is implied by the name of the .4r4 file.  The fieldN length is set according to the maximum length of the ods-2 components.  SimplyM expanding this field sounds like the simplest approach, but you would have to J expand it a *lot* because the ods-5 lengths are so much greater.  You haveN longer file names, longer file types, longer directory names, more *levels* ofM directories, so on and so on.  The complete file spec can be extremely large.i  F For instance, the following silly stuff appears on my test ods-5 disk:       Directory BILLYDISK:[000000]    H Dir^!With^#Every^&Possible^'Char^(Such^)As^+And^@And^{And^}And^.And^,And> ^`And^;And^[And^]And^%And^^And^=And^_And^86And^U4321Whew.DIR;1    C Directory HARDY$DKB100:[3046,2,0]     (this is the directory above)o    H SubDir^!With^#Every^&Possible^'Char^(Such^)As^+And^@And^{And^}And^.And^,A And^`And^;And^[And^]And^%And^^And^=And^_And^86And^U4321Whew.DIR;1i    F Directory HARDY$DKB100:[3047,2,0]     (this is the subdirectory above)    F File^!With^#Every^&Possible^'Char^(Such^)As^+And^@And^{And^}And^.And^,H And^`And^;And^[And^]And^%And^^And^=And^_And^86And^U4321Whew.That^'sAll;1    5 Thus, the complete file spec (not including disk) is:e  G [Dir^!With^#Every^&Possible^'Char^(Such^)As^+And^@And^{And^}And^.And^,AcG nd^`And^;And^[And^]And^%And^^And^=And^_And^86And^U4321Whew.SubDir^!WithaG ^#Every^&Possible^'Char^(Such^)As^+And^@And^{And^}And^.And^,And^`And^;AbG nd^[And^]And^%And^^And^=And^_And^86And^U4321Whew]File^!With^#Every^&PosnG sible^'Char^(Such^)As^+And^@And^{And^}And^.And^,And^`And^;And^[And^]Andh1 ^%And^^And^=And^_And^86And^U4321Whew.That^'sAll;1O    N As you can see, the history database would become huge if we continued keepingJ the complete file spec in each record.  The record length would have to beK large to accomodate the above, resulting in a lot of wasted space for filesiO like "[junk]myjunk.dat".   We can't make the file name variable in size becauserL it is used as a key.   As a side node, we can't use the directory or file idM shorthand that dcl does ("Directory HARDY$DKB100:[3047,2,0]").  That requirestO access to the live disk to interpret.  This is *history*, remember.  The actualrM directory may not even exist any more.  That's why you are using tapesys; youaB have to restore it.  :-)   Therefore, the history database must beC self-contained; it must have the complete file spec for every file.h  N For 6.0, we have gone to a hierarchical format for the history, similar to theO structure of the vms directories themselves.  Each entry contains either a fileaJ name or a directory name.  Each entry contains a pointer to the containingF entry.  The file entry points to the directory that contains it.  ThatO directory entry points back to the directory that contains *it*.  The top-leveloN directories point to the disk.  The disk entry points to the node (or node "*"N if no node was specified in the sbattr file).  Additionally, the versions of aN file, which are the entries that actually point to savesets, are now kept in aM completely separate file containing no ascii text at all.  Each version entryeO contains the binary version number, the pointers to the savesets, and a pointernI to the file name entry in the other file.  The pointer records are *very*dL small, so a thousand versions of the same file will take far less space thanD they do today (48 bytes each if the default of 6 saveset pointers is specified).n    6 Say you have the following file names in your history:  1 harpo::harpo_disk:[mydir.junk.stuff]garbage.dat;3 1 harpo::harpo_disk:[mydir.junk.stuff]garbage.dat;2 = harpo::harpo_disk:[mydir.junk.other_stuff]other_garbage.dat;3o= harpo::harpo_disk:[mydir.junk.other_stuff]other_garbage.dat;2 2 chico::chico_disk:[mydir.trash.stuff]garbage.dat;32 chico::chico_disk:[mydir.trash.stuff]garbage.dat;2> chico::chico_disk:[mydir.trash.other_stuff]other_garbage.dat;3> chico::chico_disk:[mydir.trash.other_stuff]other_garbage.dat;21 chico::chico_disk2:[mydir.other_trash]login.com;8o1 chico::chico_disk2:[mydir.other_trash]login.com;7e1 chico::chico_disk2:[mydir.other_trash]login.com;6s    M The convention of keeping everything for a particular top-level directory in oK the same .4r4 file has been retained.  Therefore, all of the above would go-2 into _mydir.4r4 (and the new file _mydir.4r4_ptr).     1	node harpo 2	node chico, 3	disk chico_disk 	pointer to 2 (node chico)/ 4	disk harpo_disk    	pointer to 1 (node harpo)C. 5	dir  mydir		pointer to 3 (chico::chico_disk). 6	dir  mydir		pointer to 4 (harpo::harpo_disk)5 7	dir  junk		pointer to 6 (harpo::harpo_disk:[mydir]) 6 8	dir  trash		pointer to 5 (chico::chico_disk:[mydir])+ 9 	dir  stuff		pointer to 7 (on harpo_disk)s, 10 	dir  stuff		pointer to 8 (on chico_disk)0 11	dir  other_stuff	pointer to 7 (on harpo_disk)1 12 	dir  other_stuff	pointer to 8 (on chico_disk)20 13	file garbage.dat	pointer to 9 (on harpo_disk)1 14	file garbage.dat	pointer to 10 (on chico_disk)c7 15	file other_garbage.dat	pointer to 11 (on harpo_disk)d7 16	file other_garbage.dat	pointer to 12 (on chico_disk) . 17	disk chico_disk2 	pointer to 2 (node chico). 18	mydir 			pointer to 17 (chico::chico_disk2): 19	other_trash		pointer to 18 (chico::chico_disk2:[mydir]) 20	login.com		pointer to 19L   in the .4r4_ptr file  A version 3	pointer to 13 in other file (garbage.dat on harpo_disk)SA version 2	pointer to 13 in other file (garbage.dat on harpo_disk) A version 3	pointer to 14 in other file (garbage.dat on chico_disk) A version 2	pointer to 14 in other file (garbage.dat on chico_disk)rG version 3	pointer to 15 in other file (other_garbage.dat on harpo_disk)1G version 2	pointer to 15 in other file (other_garbage.dat on harpo_disk) G version 3	pointer to 16 in other file (other_garbage.dat on chico_disk)rG version 2	pointer to 16 in other file (other_garbage.dat on chico_disk)e@ version 8	pointer to 20 in other file (login.com on chico_disk2)@ version 7	pointer to 20 in other file (login.com on chico_disk2)@ version 6	pointer to 20 in other file (login.com on chico_disk2)            O With this new format, the records now only have to be as large as a *component*nN of a file name.  This means that the space taken up by histories will actuallyO be *reduced* for ods-2 history sets.  The default record size drops from 124 towO 39.  When you are talking about many many thousands of records, this might have  an impact.  :-)d    * Some of the other features of 6.0 include:   TCP/IP support ICC supportO parallel backups restructured databased installation with vmsinstalC" automated configuration procedures integration with jbv$ improved primary/secondary protocols    O The "parallel backup" means that backups can now be split amongst multiple tapeOM drives automatically.  Say you have five tape drives and thirty disks to backnN up.  With 5.2.x, if you want to split the load, you have to have multiple .sbkN files and balance the load yourself, assigning roughly the same amount of dataL to keep all the drives busy.  In parallel backup mode, you can have one .sbkL file for all thirty disks.  sysbak will clone copies of itself, one for eachL tape drive.  Each clone will operate independently, asking the master sysbakH for the next disk to back up, then performing the assigned backup to itsL dedicated tape drive.  After that backup is complete, the clone will ask forK the next available disk.  All drives will be kept completely busy until alld disks have been backed up.    N Integration with jb means that if you are using tapesys with jb, you no longerF have to keep the two databases in synch.  You can tell jb to store itsL information in the tapesys database rather than in its own native database. M The jb volume record becomes an extension to the tapesys reel record.  The jbnM jukebox definitions become a special type of tapesys location.   This feature J requires jb 4.0 and tapesys 6.0.  If you are using jb with hierarchy *and*N tapesys, jb has a split database mode.  Information about tapesys jukeboxes isO kept in the tapesys database, and information about hierarchy jukeboxes is kept:$ in the jb native database as before.    K By the way, software partners is interested in field test sites for tapesyseN 6.0 and jb 4.0.  If you are a current customer and would like to play with the$ new stuff, contact support@sp32.com.   -- -O ===============================================================================jM 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  :-)iO ===============================================================================wK Hotel guy (after bed demolition):  That bed goes back to Henry the eighth!!aO    Curly: That's nothin'!  We had a bed go back to Sears and Roebuck the fifth!t   ------------------------------  # Date: Sun, 01 Jul 2001 22:33:15 GMT 1 From: "DanO" <danogorchockNO@SPAMcarolina.rr.com>o" Subject: Re: The Alpha/IA64 Hybrid> Message-ID: <LyN%6.54943$Md.15851369@typhoon.southeast.rr.com>   Bill,5I     Interesting information.  Thanks for posting it.  As I read the whole0K thing, it really "stinks" of old time Digital Employees never admitting thedK failure of their original or current company to properly market and advanceuL the Alpha processor.  The writing has been on the wall for a long time.  NotH many will contest the fact that Alpha was/is an execellent architecture.J But what many folks fail to see is that it is a failure, none-the-less, inJ the world of market acceptance.  Another good example is what has happenedH with DEC RDB.  When Larry Ellison's little Oracle company bought it fromK Digital, all of the Digital employees saw this as a great windfall for RDB.hJ Eventually Oracle's offering would be merged into the RDB codebase and RDBJ would rule-the-day on all pplatforms.  Well, RDB never made it off of VMS,I and the other Oracle product has received a ton of engineering, while RDB-I has slowly been left to its own recourse.  I'm not saying that Oracle 8/9uI haven't benefited from RDB technology, but the existing RDB users haven'tcK seen a huge benefit, and they are still locked into VMS.  RDB may have beenm, better, but it didn't "win" the market over.L     I see the Alpha technology following a similar pattern.  Intel will takeJ some of the IP they have bought, and will utilize it now that they legallyE can.  We will not see Alpha become the baseline for an x86 compatiblelI processor, IMHO.  To believe so, I feel is short-sighted and egotistical.qK I'd love to be wrong about this, but let's be realistic.  The only piece oftD Digital still performing well for Compaq is the Storageworks line ofL equipment, and the Service and Support organization.  Everything is going by the wayside.L     The day Digital was bought by a PC manufacturer, foretold the death of aL bygone era.  Intel and Microsoft had won.  When Microsoft dropped Windows NTH support for Alpha, MIPS, and PowerPC, it was also a foreshadowing of theJ future.  When the world's most popular OS no longer runs on your CPU, oddsJ are good that it isn't long for this world.  This is not to say that theseK CPU's don't have other uses.  Either in the ultra high-end, or for embeddedaL applications.  The only real other platforms that are doing OK are SUN's andH IBM's.  Both of them realize that they need to stay up at the enterpriseF level as their offerings will never gain wide market acceptance on the desktop or small server world.  J Hey, these are just my opinions, and we all know everyone's got one.  FeelK free to comment via the newsgroup.  I'm not trying to start a holy war, I'm L just a pretty pragmatic person when it comes to using the right tool for theC job.  When 99% of today's computing needs are satisfied by an IntelcK platform, it might be wise use Intel platforms for 99% of our applications.n   DanO    2 "Bill Todd" <billtodd@foo.mv.com> wrote in message" news:9hlsnc$om2$1@pyrite.mv.net...K > In an attempt to climb out of the hole it jumped into last Monday, CompaqeG > has apparently been energetically leaking information (from employeesaF > purporting to speak on their behalf) about Intel's having internallyL > perceived the error of its ways and now wishing to fix the problems in theI > IA64 architecture by enlisting much or all of the Alpha architecture inc theeD > service of the IA64 instruction set.  Particularly explicit quotes include: >oL > From a Compaq employee in comp.os.linux.alpha (6/26 4:48 A.M. EDT and 6/28 > 4:03 A.M. EDT):m >oK > "Alpha is not dead, its technologie will be implemented in the Itanium v3xE > processor of intel which will be released end of 2003, early 2004."L > H > "All what was planned to be in the EV8 chip will be implemented in the inteloK > itanium v3.  The engineers who are developing the alpha are transfered to 	 > intel."  > F > And in comp.os.vms from a non-employee reporting what he was told by CompaqL > engineers (and Mark Gorham, who may be the new head VMS honcho - I've lost	 > track):o >d > 6/28 9:28 P.M. EDT:  >eH > "With Alpha engineers working on Itanium-II (read: fixing what's wrong withI > Itanium-I with Alpha technology) ... Compaq is helping Intel design then nextJ > generation of IA64 which will be based on Alpha technology and optimized for  > Compaq operating systems." >n > 6/29 9:11 A.M. EDT:h >DI > "Simply put, Intel has finally admitted, at least privately, they don'te knowK > how to design a 64 bit processor.  They need decent engineers, and that'srK > where the xfer of Alpha engineers to Intel fits ... That's the EV8 team'stL > task.  Build a better Itanium than anything Intel or HP could, and call it > Itanium-II." >mL > See also 6/28 8:28 P.M. EDT for more near-quotes-from-Compaq-types leadingH > up to the above.  There were other earlier similar (but less explicit)L > allegations by others, but I didn't have the patience to go back and trackH > them down.  The Inquirer also took note of such activity in an article last > Thursday:  >V) > http://www.theinquirer.net/28060117.htme > I > "Today's spin from Compaq employees has ranged from assertions that thewC > Alpha line was incapable of further performance increases, to theiG > reassurance that the next generation of IA64 chips will be re-brandedt
 > Alphas." >kF > Leaving aside the fact that none of this will necessarily help avoidG > increased doubts about Compaq's commitment to anything non-Wintel andbH > short-and-medium-term negative impact of the coming platform-switch onL > Alpha, VMS, and Tru64 sales, there's still the interesting question of howH > Intel and HP feel about such allegations about the inadequacy of their shinynH > new IA64 architecture.  Even if the allegations are true, reports that InteloJ > is now going to start over from an Alpha base won't exactly be good news forsK > Itanium/McKinley acceptance over the next couple of years, so what's good I > for Compaq's ability to rationalize its divestiture of Alpha may be bad  foruL > Intel/HP business, and vice versa.  And if the allegations are false, then@ > one might expect Intel and HP to be more than a little miffed. > J > I took a quick look today at comp.sys.hp.hardware and comp.sys.hp.hpux - nottG > a peep there about anything Alpha-related.  Comp.sys.intel discussiono seemedG > to center on how Compaq needed Alpha to maintain credibility in their H > high-end business - i.e., surprisingly positive sentiments about Alpha (fromdI > a group with their name), even before the announcement was official anda they( > knew they could afford to be generous. >eK > So I clearly haven't done any exhaustive research (and have no idea whereoJ > such discussion might hang out), but so far haven't stumbled upon a peepF > from Intel, HP, or anyone purporting to speak on their behalf on the matterJ > of Compaq's (alleged) allegations of IA64 inadequacies and its rescue byF > Alpha technology.  If anyone else has, could they provide a pointer? >w	 > Thanks,l >b > - bill > I > [I don't usually cross-post this widely, but I did take care to includea onlyJ > groups where active discussion of Alpha's demise both seemed appropriate ande > had already occurred.] >t >g >c   ------------------------------  # Date: Mon, 02 Jul 2001 03:13:20 GMTi4 From: "Terry C. Shannon" <terryshannon@mediaone.net>" Subject: Re: The Alpha/IA64 Hybrid< Message-ID: <kFR%6.1077$9r6.1783586@typhoon.ne.mediaone.net>  < "DanO" <danogorchockNO@SPAMcarolina.rr.com> wrote in message8 news:LyN%6.54943$Md.15851369@typhoon.southeast.rr.com... > Bill,tK >     Interesting information.  Thanks for posting it.  As I read the whole I > thing, it really "stinks" of old time Digital Employees never admittingw theiE > failure of their original or current company to properly market and0 advance I > the Alpha processor.  The writing has been on the wall for a long time.` NotAJ > many will contest the fact that Alpha was/is an execellent architecture.L > But what many folks fail to see is that it is a failure, none-the-less, in! > the world of market acceptance.^  L That should be intuitively obvious. After almost a decade the installed baseL of Alpha systems is under 1M. And the annual system run rate is 100K, if CPQ	 is lucky.e  I What killed Alpha? Marketing malfeasance and Stupid Strategy Tricks. Pure; and simple.^   ------------------------------   Date: 1 Jul 2001 20:26:47 -0700e! From: sv1104@my-deja.com (sv1104)s" Subject: Re: The Alpha/IA64 Hybrid< Message-ID: <ad943153.0107011926.c5cf008@posting.google.com>  > Can a RISC processor like Alpha be able to implement the ia-64C instruction set? I know that modern ia-32 processors are internallyn: RISC engines, but is it possible to do the same for ia-64?   sv1104   ------------------------------  % Date: Mon, 02 Jul 2001 01:43:22 -0400n# From: Paul DeMone <pdemone@igs.net>^" Subject: Re: The Alpha/IA64 Hybrid& Message-ID: <3B4009FA.6BDDE25@igs.net>   "Terry C. Shannon" wrote:e [...]p  N > That should be intuitively obvious. After almost a decade the installed baseN > of Alpha systems is under 1M. And the annual system run rate is 100K, if CPQ > is lucky.t  J   How much of the total Alpha market does Compaq comprise? In other words,8   how important are APIN, Samsung, and the various OEMs?   > K > What killed Alpha? Marketing malfeasance and Stupid Strategy Tricks. Pures
 > and simple.   ?   Indeed, what kind of oafs can't market the fastest 64 bit MPUe   after 8 years in the market?   --D Paul W. DeMone       The 801 experiment SPARCed an ARMs race of EPICE Kanata, Ontario      proportions to put more PRECISION and POWER into G demone@mosaid.com    architectures with MIPSed results but ALPHA's wells$ pdemone@igs.net      that ends well.   ------------------------------  $ Date: Sun, 1 Jul 2001 14:12:25 -0400' From: "Bill Todd" <billtodd@foo.mv.com>p: Subject: Re: The death of VMS has been greatly exaggerated( Message-ID: <9hnovg$356$1@pyrite.mv.net>  4 "T. S. Murphy" <murphts@swbell.net> wrote in message' news:_rI%6.8$Y36.17784@nnrp3.sbc.net...o   ...s  #   The PAE is useful when you have aoJ > bunch of process which together take up more than 4GB, but not useful if youi- > have one process which needs more than 4GB.a  I My reading of Solomon & Russinovich's Win2K book is that a single process I can access as much physical RAM (i.e., > 4 GB) as it cares to, as long asbJ it's willing to remap portions of its virtual address space to move aroundK in it (though of course it can't address more than 4 GB at any one instant,n using a static map).   >eG > You can see the IA-32 developer manual volume 3, section 3.8 for morev > detailed information.e  L If that explanation differs from my understanding above, would you happen to+ have a pointer to a Web-accessible version?:   Thanks,:   - bill   ------------------------------  $ Date: Sun, 1 Jul 2001 15:42:03 -0400% From: "John Vottero" <John@mvpsi.com>j: Subject: Re: The death of VMS has been greatly exaggerated/ Message-ID: <tjuv7mmjb05k18@news.supernews.com>m  2 "Bill Todd" <billtodd@foo.mv.com> wrote in message" news:9hla53$df7$1@pyrite.mv.net... >32 > "John Vottero" <John@mvpsi.com> wrote in message+ > news:tjs68m3p89kn64@news.supernews.com..._6 > > "Bill Todd" <billtodd@foo.mv.com> wrote in message& > > news:9hiu0m$n32$1@pyrite.mv.net... > > >_6 > > > "John Vottero" <John@mvpsi.com> wrote in message/ > > > news:tjp72vkid095b6@news.supernews.com...h: > > > > "Bill Todd" <billtodd@foo.mv.com> wrote in message* > > > > news:9hdrua$353$1@pyrite.mv.net...	 > > > > >r: > > > > > "John Vottero" <John@mvpsi.com> wrote in message >p > ...t > G > > > > > > It's not that all (or even many) problems need more than 32d bits.n
 > > > It's > > > > > thatH > > > > > > most computers are used to do more than one thing.  A 32 bit chip > > can_ > > > > only > > > > > > address 4GB of RAM.c	 > > > > >sL > > > > > Tell that to Intel and its Xeons (32-bit machines supporting up to > 64 > > GB
 > > > > ofL > > > > > RAM).  It's like telling people a 16-bit PDP-11 could only address > 64 > > KB
 > > > > of( > > > > > RAM (IIRC 4 MB was the limit).	 > > > > >l > > > >.J > > > > The Xeon uses 36 bits for addressing memory.  It's a half assed 36 bita9 > > > > processor.  But, you already know that don't you?c > > > L > > > Without bothering to address the merits of Xeons (or PDP-11s, for thatL > > > matter), the fact remains that Xeons are universally considered 32-bit0 > > > processors and that you were simply wrong. > > >  > >oL > > I'm wrong?  Care to explain how a Xeon accesses memory beyond 4GB with a > 32 > > bit pointer? >aL > I really do try to include the pertinent material from posts I respond to,F > but in this case perhaps I omitted some (since at the time it seemed wholly
 > redundant).n > > > Your text immediately following the first excerpt above was: >oJ > Every day another pointy haired boss says "Tell me again why I can't putK > more than 4GB of RAM in the server.", "Can't we just by machine with more  > DIMM slots?" > J > That makes it crystal-clear that what you're talking about is the amount ofL > RAM that can be installed and used on the machine, not the amount directly8 > addressable under any single mapping by the processor. > H > Are you really so clueless as not to understand the difference betweenH > virtual and physical memory, and how you can have more of one than theG > other?  If so, you should be a lot more temperate in your statements.t >   C Ok, I'll concede on the "point haired boss" comment, it was made tobK illustrate my point that 32 bit processors (that is, processors that use 32oH bits to address memory) are dead.  32 bit processes will be around for aK long time (maybe forever) but the days of machines limited to 4GB of memoryaE are numbered.   The various 32/36 bit processors are just a stop gap.c   ------------------------------  $ Date: Sun, 1 Jul 2001 13:03:32 -0700* From: "Jack Peacock" <peacock@simconv.com>1 Subject: Re: Using SCSI controller on QBUS systemi4 Message-ID: <AoL%6.4604$Ib.487733@news1.primary.net>  4 "T. S. Murphy" <murphts@swbell.net> wrote in message' news:ZwJ%6.9$pk4.32808@nnrp2.sbc.net...eC . Originally it was in a KA-655 system in a H9642 chassis, and I ampG > trying to switch it to a BA-123 chassi> I have a SCSI QBUS controllern. which I am trying to switch from one system to > anothers.l >eB > The controller is a CMD-440/TM board, and it is MSCP compatible. > E I haven't used CMD controllers in a while but as I remember there areAD jumpers to set the CSR and vector.  In the system where they worked,G they might be showing up according to a SYSGEN order, but when you movebD them the order might change and your CSR could be wrong.  Run thru aC SYSGEN with all the devices and see what comes up.  DO you have any." other MSCP controllers on the bus?  C The second possibility is that the interrupt chain might be broken. C Isn't a BA-123 backplane a Q/Q after the CPU and memory slots?  AredE there any gaps on either side after the memory boards up to your CMS?o    Jack Peacock    ------------------------------   Date: 1 Jul 2001 15:02:43 -0500y9 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen) ! Subject: Re: VMS 7.3 experiences? 3 Message-ID: <4728xGRx2mit@eisner.encompasserve.org>   G  In message <Pine.OSF.4.21.0107010849270.12112-100000@athena.csdco.com>o'    John Nebel <nebel@csdco.com> writes:sJ >What experiences have people had with V7.3?  Is it too early to use it inG >a mixed-architecture and wide area production cluster, or can one just=
 >forge ahead?=  F I upgraded a cluster of 3 Alphas and 2 VAXen (all with separate systemF disks).  I had a good deal of trouble on the second VAX and eventuallyD had to set VMSCLUSTER to 0 to make the upgrade run.  It got confusedB trying to remount the CD when it was already mounted.  It may haveC been a device naming issue or an outstanding mount elsewhere in the= cluster.  E The Alpha upgrades were as smooth as silk (as I have come to expect).!  > Operationally it is fine, but I don't strain the cluster much.   ------------------------------  % Date: Sun, 01 Jul 2001 19:02:41 -04000# From: Mark Vance <mvance@iglou.com>o( Subject: VMS installation Probs from CD.) Message-ID: <3B3FAC11.15980782@iglou.com>6  G Hi!  Im trying to install VMS from a SAF (teac)CD with a 512 byte blockoG jumper set on, adn the chain correctly terminated, and with scsi id not"# interfereing with any other device.   B I am using the VMS 7.1 binaries disk to try to install from.  If i
 simply try to    >>> boot Dkb400:  B I get an exe file not found error shorty after the regular mapping% errors and the VMS startup info line.   
 If I do this.e   >>> b/r5:1 dkb400:  ; it says it cant find [sysexe]vaxvmssys.par then goes to thee  	 SYSBOOT>>o   if I say SYSBOOT>> use ANYOLD NAME   C I get an understandable error file not found.  After I've made thate6 error I can now select the [sysexe]vaxvamssys.par file  # SYSBOOT>> use [sysexe]vaxvmssys.para SYSBOOT>> continue.l  H I then get to put in the date and it configures the devices and tells me im in Standalone backup...  ) $ back/image dkb400:vms071.b/save dka300:h  G Gives me a message saying drive is offline , and goes into Mount Verifyl forever.......) Anyone have any Ideas whats going on?????a  F Could it be my cd rom?  it IS jumpered to 512 byte blocks though......   ------------------------------  % Date: Sun, 01 Jul 2001 22:50:50 -0500a1 From: "David J. Dachtera" <djesys.nospam@fsi.net>t, Subject: Re: VMS installation Probs from CD.' Message-ID: <3B3FEF9A.7B6F3E2F@fsi.net>o   Mark Vance wrote:e > I > Hi!  Im trying to install VMS from a SAF (teac)CD with a 512 byte block I > jumper set on, adn the chain correctly terminated, and with scsi id not,% > interfereing with any other device.l > D > I am using the VMS 7.1 binaries disk to try to install from.  If i > simply try tot >  > >>> boot Dkb400: > D > I get an exe file not found error shorty after the regular mapping' > errors and the VMS startup info line.h >  > If I do this.a >  > >>> b/r5:1 dkb400: > = > it says it cant find [sysexe]vaxvmssys.par then goes to thec >  > SYSBOOT>>W > 
 > if I say > SYSBOOT>> use ANYOLD NAME  > E > I get an understandable error file not found.  After I've made that 8 > error I can now select the [sysexe]vaxvamssys.par file > % > SYSBOOT>> use [sysexe]vaxvmssys.parr > SYSBOOT>> continue.  > J > I then get to put in the date and it configures the devices and tells me > im in Standalone backup... > + > $ back/image dkb400:vms071.b/save dka300:N > I > Gives me a message saying drive is offline , and goes into Mount Verifye > forever.......+ > Anyone have any Ideas whats going on?????c > H > Could it be my cd rom?  it IS jumpered to 512 byte blocks though......  E At V7.1, VMS is still rather picky about what non-DEC SCSI devices itu will "play nice" with.  G There is no known fix, given that you're using a boot CD, other than to  try a different CD-ROM drive.h   -- o David J. Dachtera  dba DJE Systemse http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/b  F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.h   ------------------------------  $ Date: Mon, 2 Jul 2001 00:24:40 -0400  From: John Santos <JOHN@egh.com>, Subject: Re: VMS installation Probs from CD.4 Message-ID: <1010702000709.331B-100000@Ives.egh.com>  , On Sun, 1 Jul 2001, David J. Dachtera wrote:   > Mark Vance wrote:o > > K > > Hi!  Im trying to install VMS from a SAF (teac)CD with a 512 byte block:K > > jumper set on, adn the chain correctly terminated, and with scsi id not ' > > interfereing with any other device.w > > F > > I am using the VMS 7.1 binaries disk to try to install from.  If i > > simply try toi > >  > > >>> boot Dkb400: > > F > > I get an exe file not found error shorty after the regular mapping) > > errors and the VMS startup info line.v > >  > > If I do this.p > >  > > >>> b/r5:1 dkb400: > > ? > > it says it cant find [sysexe]vaxvmssys.par then goes to the- > > 
 > > SYSBOOT>>o > >  > > if I say > > SYSBOOT>> use ANYOLD NAMEi > > G > > I get an understandable error file not found.  After I've made thatA: > > error I can now select the [sysexe]vaxvamssys.par file > > ' > > SYSBOOT>> use [sysexe]vaxvmssys.par  > > SYSBOOT>> continue.m > > L > > I then get to put in the date and it configures the devices and tells me > > im in Standalone backup... > > - > > $ back/image dkb400:vms071.b/save dka300:g > > K > > Gives me a message saying drive is offline , and goes into Mount Verify  > > forever.......- > > Anyone have any Ideas whats going on?????B > > J > > Could it be my cd rom?  it IS jumpered to 512 byte blocks though...... > G > At V7.1, VMS is still rather picky about what non-DEC SCSI devices ita > will "play nice" with. > I > There is no known fix, given that you're using a boot CD, other than tob > try a different CD-ROM drive.g  B Actually, it sounds like you got pretty far.  So it might be worthC trying a more recent version of VMS.  7.1 is pretty old, Dec, 1996.rD 7.3 has been out for about a month.  They've improved 3rd-party SCSIE support a lot in Alpha VMS since then.  Don't know about VAX VMS, butf9 there is an ECO for SCSI support that among other things e  H       o  An attempt to mount a disk device can fail with an MEDOFL errorH          if the device returns the minimum amount or required mode sense          data.  
 (It also saysi  H       o  Disk drives with a capacity of greater than 8.6 GB  have  their1          capacity truncated to 8.6 GB upon Mount.e  F which might be the answer to someone who asked about installing a 34GB drive earlier today...)a  D You can't install an ECO on the CD-ROM, but I'm sure these fixes areB rolled into more recent versions of VMS.  I'm not sure if V7.2 wasD released before these patches, but V7.3 definitely should have them.   -- c John Santosx Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  $ Date: Sun, 1 Jul 2001 17:38:58 -0400  From: John Santos <JOHN@egh.com>5 Subject: VMS721_UPDATE V0300 ECO regresses DEC$BASRTLI4 Message-ID: <1010701172639.357B-100000@Ives.egh.com>  ? It installs V01-021 (according to internal version identifier).xA with a date of 29-Dec-1999, replacing V01-025, 11-Apr-2000, whicht- I beleived was installed with DEC BASIC V1.4.a  ; When you try to compile something with BASIC, you then get:sD  %IMGACT-F-SYMVECMIS, shareable image's symbol vector table mismatch;  -IMGACT-F-FIXUPERR, error when BASIC referenced DEC$BASRTLf   The cure is to  - $ rename sys$library:dec$basrtl.exe_old *.exeo( $ install replace sys$library:dec$basrtl; (the install gives a warning message which can be ignored.)oC $ library/replace sys$library:imagelib/share sys$library:dec$basrtly> (this is to prevent linker shareable image mismatch warnings.)  C I think you could also just re-install BASIC, but this was quicker.l   -- h John Santosn Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  % Date: Sun, 01 Jul 2001 11:35:05 -0400I2 From: rdeininger@mindspring.com (Robert Deininger)8 Subject: Re: Yet Another Reason Why Windoze .ne. OpenVMSL Message-ID: <rdeininger-0107011135050001@user-2ivea56.dialup.mindspring.com>  D In article <CIEJLCMNHNNDLLOOGNJIIEFJCOAA.tom@kednos.com>, Tom Linden <tom@kednos.com> wrote:j  L > The past is often prologue.  There was a version of the 21064 (A, I think)L > that was fused in such a way that it could only run the ARC console, hence > NT.N  C There was a 21064PC, which was probably NT-only.  The 21064A was aneJ enhanced 21064, with double the on-board cache and other minor tweeks.  InI the DEC 3000 familiy, for example, the model 700 and 900 systems used theaE 21064A; all the others used the 21064. At the system level, switchinga" processors hardly mattered at all.   -- a Robert Deininger rdeininger@mindspring.com    ------------------------------   Date: 1 Jul 2001 14:51:20 -0500r9 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen)r8 Subject: RE: Yet Another Reason Why Windoze .ne. OpenVMS3 Message-ID: <QLfrT9fDu1xo@eisner.encompasserve.org>d  ] In article <CIEJLCMNHNNDLLOOGNJIIEFJCOAA.tom@kednos.com>, Tom Linden <tom@kednos.com> writes:fL > The past is often prologue.  There was a version of the 21064 (A, I think)L > that was fused in such a way that it could only run the ARC console, hence > NT.2  C Until those clever Linux folk made their operating system boot withp, _either_ the ARC console or the SRM console.   ------------------------------   End of INFO-VAX 2001.363 ************************