1 INFO-VAX	Fri, 10 Aug 2001	Volume 2001 : Issue 441       Contents:  $19.95 Unlimited Internet Access  $19.95 Unlimited Internet Access* Re: ACCVIO problem - any help appreciated. Re: Alpha-IA64 FAQ( Re: Alpha:  an invitation to communicate( Re: Alpha:  an invitation to communicate( Re: Alpha:  an invitation to communicate! Re: Article from Information week ! Re: Article from Information week ! Re: Article from Information week ! Re: Article from Information week ! Re: Article from Information week ! Re: Article from Information week ! Re: Article from Information week  Re: AW: SYBASE on VMS ( Re: Backup Internet MX/SMTP server (ASP)$ Backup Internet MX/SMTP server (ASP)( Re: Backup Internet MX/SMTP server (ASP)( Re: Backup Internet MX/SMTP server (ASP). Re: Can queue manager handle 100.000 entries ?. Re: Can queue manager handle 100.000 entries ?. Re: Can queue manager handle 100.000 entries ?. Re: Can queue manager handle 100.000 entries ? CETS invitation B Re: Comments from a VMS customer (and I would like to stay as one) Compaq/Avnet/Intel Re: Compaq/Avnet/Intel CSWS Authentication question* Re: DECstation 5000 error (was Re: pb dec)5 Re: DECwindows keyboard problem: < > keys do not work  DecWindows trouble on PWS500au" Re: DecWindows trouble on PWS500au Fetchmail lookalike ?? Re: Flip-Chip" Re: Flip-Chip" Re: Flip-Chip" Re: Flip-Chip" RE: Flip-Chip" FTP automation Re: Goodbye, good friend DEC Re: Help, PWS500 locked up. / Re: How to build a bootable media for a 11/780? = Re: I just have to post this - and apoligse later Alpha/Intel = Re: I just have to post this - and apoligse later Alpha/Intel = Re: I just have to post this - and apoligse later Alpha/Intel = RE: I just have to post this - and apoligse later Alpha/Intel = Re: I just have to post this - and apoligse later Alpha/Intel = Re: I just have to post this - and apoligse later Alpha/Intel = Re: I just have to post this - and apoligse later Alpha/Intel = Re: I just have to post this - and apoligse later Alpha/Intel = Re: I just have to post this - and apoligse later Alpha/Intel = Re: I just have to post this - and apoligse later Alpha/Intel  Re: Linker-Warnings in VMS 7.3 Re: Linker-Warnings in VMS 7.3 RE: Microsoft and Code red Re: Microsoft and CR& Re: Migrating from CI to Fiber Channel Re: Missing TK50 in uVAX?  Missing TK50 in uVAX?  Re: Move to Sun  Re: Move to Sun  Re: Move to Sun  Re: Move to Sun  Re: Move to Sun  Re: Move to Sun  Re: Move to Sun  Re: Move to Sun # MS610-EA ES40 Memory - Very Cheap ! . OpenVMS apps and Compaq committment story here& OpenVMS in news at Informationweek.com
 Re: pb dec
 Press Release  Re: Reboot to close a file ???? ! Re: Red Code: where are we going? ! Re: Red Code: where are we going? ! Re: Red Code: where are we going? ! Re: Red Code: where are we going? ! Re: Red Code: where are we going? ! Re: Red Code: where are we going? ) Re: Shameless Grab; Was Re: uVAX 3100 M38  Re: Suggested DCPS features $ Re: Terry Shannon Tech Talk on Tru64& Re: The VMS Opensource Porting Project& Re: The VMS Opensource Porting Project& Re: The VMS Opensource Porting Project Re: Third postcard from Sun   Re: UNIX-cd product distribution+ Using sys$startup:tcpip$define_commands.com / Re: Using sys$startup:tcpip$define_commands.com ' VIRUSES: It's time for a counter attack + Re: VIRUSES: It's time for a counter attack + Re: VIRUSES: It's time for a counter attack  VIRUSES: What about antibodies?  Re: VMS 7.3 experiences? Re: VMS 7.3 experiences? Re: VMS 7.3 experiences?  F ----------------------------------------------------------------------  % Date: Thu, 09 Aug 2001 15:03:19 +0000 " From: Netlink@mclmx.mail.saic.com,) Subject: $19.95 Unlimited Internet Access 8 Message-ID: <iss.6fe.3b7318ad.ad73e.1@mx2.east.saic.com>  a This is an HTML email message.  If you see this, your mail client does not support HTML messages.    ------=_NextPart_LUSQRZVOGM , Content-Type: text/html;charset="iso-8859-1" Content-Transfer-Encoding: 7bit    <html>   <head>4 <meta http-equiv="Content-Language" content="en-us">J <meta http-equiv="Content-Type" content="text/html; charset=windows-1252">9 <meta name="GENERATOR" content="Microsoft FrontPage 4.0"> 8 <meta name="ProgId" content="FrontPage.Editor.Document">$ <title>Netlink offers over 4</title> </head>    <body bgcolor="#808080">  w <p align="center"><font size="6" color="#FF6600" face="Arial"><b><em><u><span style="text-decoration: overline">Netlink 0 Internet Services</span></u></em></b></font></p>M <p align="center">Netlink offers over 4,000 Nationwide Dial-up Access numbers J for your convenience. When you sign-up with Netlink, you will receive:</p> <ul>   <li>=     <p align="center"><b>Free 24/7 Technical Support</b></li>    <li><     <p align="center"><b>10mg of Personal Web-Space</b></li>   <li>:     <p align="center"><b>Two free Email addresses</b></li>   <li><     <p align="center"><b>Unlimited Internet Access </b></li>   <li>+     <p align="center"><b>And More.</b></li>  </ul> J <p align="center"><font size="4" color="#FF6600"><b>Sign-up Today for only $19.95 a month!!</b></font></p> n <p align="center"><a href="http://www.free-hosting.lt/netlink/default.htm">Netlinkinternetservices.com</a></p> <p align="center">&nbsp;</p>   </body>    </html>    ------=_NextPart_LUSQRZVOGM--    ------------------------------  % Date: Thu, 09 Aug 2001 18:07:37 +0000 " From: Netlink@mclmx.mail.saic.com,) Subject: $19.95 Unlimited Internet Access 9 Message-ID: <iss.44bb.3b73436c.b5a5b.1@mx2.east.saic.com>   a This is an HTML email message.  If you see this, your mail client does not support HTML messages.    ------=_NextPart_VGNGSTAWNK , Content-Type: text/html;charset="iso-8859-1" Content-Transfer-Encoding: 7bit    <html>   <head>4 <meta http-equiv="Content-Language" content="en-us">J <meta http-equiv="Content-Type" content="text/html; charset=windows-1252">9 <meta name="GENERATOR" content="Microsoft FrontPage 4.0"> 8 <meta name="ProgId" content="FrontPage.Editor.Document">$ <title>Netlink offers over 4</title> </head>    <body bgcolor="#808080">  w <p align="center"><font size="6" color="#FF6600" face="Arial"><b><em><u><span style="text-decoration: overline">Netlink 0 Internet Services</span></u></em></b></font></p>M <p align="center">Netlink offers over 4,000 Nationwide Dial-up Access numbers J for your convenience. When you sign-up with Netlink, you will receive:</p> <ul>   <li>=     <p align="center"><b>Free 24/7 Technical Support</b></li>    <li><     <p align="center"><b>10mg of Personal Web-Space</b></li>   <li>:     <p align="center"><b>Two free Email addresses</b></li>   <li><     <p align="center"><b>Unlimited Internet Access </b></li>   <li>+     <p align="center"><b>And More.</b></li>  </ul> J <p align="center"><font size="4" color="#FF6600"><b>Sign-up Today for only $19.95 a month!!</b></font></p> n <p align="center"><a href="http://www.free-hosting.lt/netlink/default.htm">Netlinkinternetservices.com</a></p> <p align="center">&nbsp;</p>   </body>    </html>    ------=_NextPart_VGNGSTAWNK--    ------------------------------  $ Date: Thu, 9 Aug 2001 07:59:28 -0400" From: "Hal Kuff" <kuff@tessco.com>3 Subject: Re: ACCVIO problem - any help appreciated. O Message-ID: <3CDB29E5AC9BF018.08ABAE5DC627071A.C1A45C790B9F6E89@lp.airnews.net>   H     We have a similar issue at the SCS for review... we were running 7.1H with V5 of C on a server and moved to 7.2-1h1 with V6.4 of C and startedG getting ACCVIO's ... the issue does not come up on 7.2 with the older C I libraries and RTL .... Originally thought it might be ACRTL2 patch.... By B any chance is this C code adn is the issue with file opens/closes?      6 "Rob Buxton" <rob.buxton@wcc.govt.nz> wrote in message) news:3b71a6c3.3428820@news.wcc.govt.nz...  > Hi Folks,  > 9 > Spent a while on this and I'm getting a tad frustrated. G > We have a program that was working okay until I put a raft of patches  > onto our Production Alpha. > Patches were: 9 > DEC VMS AVAIL_MAN V2.0              Full LP     Install  > 05-AUG-2001 12:14:559 > DEC AXPVMS TCPIP_ECO V5.1-151       Patch       Install  > 05-AUG-2001 12:10:029 > DEC AXPVMS DNVOSIECO03 V7.2         Patch       Install  > 05-AUG-2001 12:03:469 > DEC AXPVMS VMS721_SHADOWING V6.0    Patch       Install  > 05-AUG-2001 12:00:509 > DEC AXPVMS VMS721_RENAME_OLD V1.0   Patch       Install  > 05-AUG-2001 11:59:379 > DEC AXPVMS VMS721_F11X V3.0         Patch       Install  > 05-AUG-2001 11:55:279 > DEC AXPVMS VMS721_RMS V2.0          Patch       Install  > 05-AUG-2001 11:48:579 > DEC AXPVMS VMS721_MANAGE V2.0       Patch       Install  > 05-AUG-2001 11:47:029 > DEC AXPVMS VMS721_AUDSRV V1.0       Patch       Install  > 05-AUG-2001 11:45:319 > DEC AXPVMS VMS721_SYS V10.0         Patch       Install  > 05-AUG-2001 11:34:409 > DEC AXPVMS VMS721_UPDATE V3.0       Patch       Install  > 05-AUG-2001 11:28:19 > A > These Patches were applied to our Development Alpha a few weeks 	 > before. F > So, on both Production and Development Alphas we're running the same% > version of VMS (7.2-1) and Patches. C > On Development the job runs fine, on Production it fails with the  > ACCVIO below.  >  > Print Date = 08-Aug-2001= > %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual < > address=000000000057E000, PC=000000000011EB20, PS=0000001B1 > %TRACE-F-TRACEBACK, symbolic stack dump follows ; >   image    module    routine             line      rel PC  > abs PC > G > I've copied all of the data files it uses to a separate directory and ? > used local assigns to reference the data to ensure there's no H > different data. Still it fails on Production and works on Development. > < > The User Quotas are higher on Production than Development. > F > The run time also varies, the job should take about 7-8 minutes, butB > sometimes it fails immediately and other times after running for3 > several minutes (almost to the end but not quite)  > F > It also works on the VAX variant of the image against the same data. > F > Are there any SYSGEN Parameters that might influence this behaviour? > C > The main difference I can see is that on Production we use Volume H > shadowing and on Development we do not. I've tried moving all the dataH > to a non-shadowed disk but that still failed. Also moved it to a local  > disk to rule out mscp serving. > # > Further tests & checks I've done. ? > Checked the link dates of the image being run on Production &  > Development - it's the same B > Checked the dates on files in sys$library:, sys$loadable_images,H > sys$system to ensure that the order of patches hasn't left a different > image in place. D > Used SDA and Availability Manager to watch for quotas and to watchD > what files are held open and specifically ensure they're the same. > F > On Production, we have two similary configured Alphas, the job failsG > on both. On Development we have two Alphas, the second is on 7.3, the  > job works on both of these.  >  > Bewildered again!  >  > Rob. >    ------------------------------  $ Date: Thu, 9 Aug 2001 14:38:37 -0400' From: "Bill Todd" <billtodd@foo.mv.com>  Subject: Re: Alpha-IA64 FAQ ( Message-ID: <9kulbm$6ld$1@pyrite.mv.net>  1 "Ken Farmer" <kfarmer@tru64.org> wrote in message 9 news:m5kc7.90097$J37.21085447@typhoon.southeast.rr.com...    ...   G > First of all I like to thank you Bill.  Your commentary has been both H > entertaining and informative regarding this issue over the last month.  H Well, entertainment wasn't a real goal (since I certainly don't find theI issue entertaining at all), but I'm glad if it made information available E that might otherwise have been submerged in the Compaq misinformation 
 offensive.   > H > PR arm?  I consider that a compliment.  What exactly did you think the siteK > was supposed to be about?  The purpose of the site is to offer assistance ? > and industry news to sysadmins/developers/tech managers, etc.   D If that's really its purpose, then bad news is as important as good.D Otherwise, you're encouraging such people to make decisions that areA important to them and their businesses on incomplete information.      I'm trying to F > spread positive information about Tru64, not kick it in the teeth or > alienate Compaq.  L As I said, spreading only half the truth is at best misleading, and arguablyK deceitful.  If you depend upon Compaq for resources, then I sympathize, but J if you're going to allow that to influence what you report then you really- need a disclaimer to that effect on the site.    ...   H > I too have been shocked by the decision.  Terry Shannon and myself putJ > together the Alpha Transition Survey, recently available, to try and getL > some kind of an idea of how the technical end of the spectrum was feeling.& > The results will be summarized soon.  L I've been hoping to see them, though IIRC (can't find the survey any more toI check) the survey's wording will leave some important questions up in the  air.  "   I can promise you Compaq will beG > reading it.  To me, that is doing something constructive to voice the L > opinions of others.  I can even go as far as putting up a forum to discussB > this issue.  I recently even emailed you asking if you wanted to participate J > with a constructive article on the site, giving you opportunity to voice' > your opinion, I even offered you cash   I Indeed you did, and I responded that that might be interesting as long as " the cash did not come from Compaq.  %   You stated you didn't think you had ( > anything to offer the Tru64 community.  K What I actually said was that my main expertise involved storage areas that J might not be of central interest to your community, and then left it up to9 you to decide whether that was what you were looking for.   %   What more can I do, set you up your ) > own website, bitchin-at-compaq.com?  :)   F I didn't realize that you were inviting me to comment on the AlphacideH specifically, since your invitation was not specific and was pretty muchI identical to one I received from you quite a while ago (so I suspected it I was simply a generic invitation you send out to people who participate in , comp.unix.tru64).  Sorry if I misunderstood.  K While there are many reasons to bitch at Compaq, my present ones are pretty H tightly focused on incompetence and lack of integrity in its handling ofI Alpha - and even more specifically on its efforts to obscure these issues D with deceit and outright lies.  The newsgroups (though unfortunatelyJ virtually no one else) seem to be covering these issues adequately, but ifG you'd like to open up a forum at tru64.org I'll be happy to participate  there as well.   >  > L > > Of course, the desire to 'stop competing with industry standards' hardlyL > > stops at the hardware interface:  expect VMS and Tru64 to follow as soon > asH > > Compaq deems it convenient, regardless of how its customers may feel about L > > the matter.  And as for compilers, I think the soi-disant 'FAQ' may haveD > > missed the major transfer of compiler technology, ownership, and
 > development 7 > > staff to Intel that accompanied the Alpha decision.  >  > J > Help me out here Bill.  Give me some questions and answers on compilers,L > ownership or development and whatever else you think can offer information > about the transition.   J While there are a small number of things I've been told in confidence, theJ vast majority of what I know in this area I've aired in (and in some casesI originally obtained from) comp.os.vms and comp.arch.  And while I'm quite L well-informed about the future potential that Compaq sacrificed when it axedF Alpha and about its attempts to justify the cancellation on apparentlyJ untenable technical and fiscal grounds (i.e., lies), I'm nowhere nearly asK well-acquainted with the details of the planned transition (since I find it # neither interesting nor desirable).    - bill   >  > Ken  >  >  > -- > Ken Farmer, kfarmer@tru64.org ! > Tru64.org, http://www.tru64.org  > Tru64.org Newsletter: > > http://www2.tru64.org/pages.php?page=Newsletter-Registration >  >    ------------------------------  # Date: Thu, 09 Aug 2001 22:55:39 GMT   From: jlsue <jlsuexxxz@home.com>1 Subject: Re: Alpha:  an invitation to communicate 8 Message-ID: <alr2nt84v8ora3pbn42f3ansr2p0hgrlte@4ax.com>   You completely miss the point.@ If Andrew is going to make these claims, especially with so much? repitition, then he's going to have to answer to these kinds ofV
 questions.  F He can't sit there and demand answers from Compaq, and then ignore his own responsibility.   E The fact is, he made a stupid statement that Sun never said that, and0D that Compaq made the number up.  Now, it's time for him to own up to1 the fact that Sun did really publish the numbers.A  C And his little side-tracking technique to say that Sun has improvedtC those numbers is a complete joke.  He has no idea when that part ofaC the white paper was written in order to compare it to any 'new' SunE numbers.    , On Mon, 06 Aug 2001 11:49:43 -0400, JF Mezei% <jfmezei.spamnot@videotron.ca> wrote:e   >"Main, Kerry" wrote:kK >> I gave you a direct quote and pointer from a Sun WP which clearly states $ >> 400-600nsec as per the following: >t >sM >Mr Main, if I worked hard enough, I could probably find a quote stating thatV >VMS runs at 0.9 VUPS. >eL >Mt Harrisson stated multiple times that Sun has upgraded their motherboardsG >some time ago to have lower memory latency. And Compaq have *slightly*F? >improved VMS performance sicne the days of the Microvax II :-)r >iN >You can go back in time as far as you want to find a competitor's performance@ >numbers lower than your own. And while I grant you that gettingL >always-up-to-date documents may not be an easy task, I think that you couldO >have simply stated that Compaq probably got outdated information with which toiN >make its comparison against Sun instead of starting a "my dick is bigger than >yours" contest with Andrew.   ------------------------------  # Date: Thu, 09 Aug 2001 22:55:38 GMT   From: jlsue <jlsuexxxz@home.com>1 Subject: Re: Alpha:  an invitation to communicateg8 Message-ID: <2lq2ntc3cnns4j94fpp1hs6qgahb66sl7m@4ax.com>  3 On Fri, 03 Aug 2001 17:17:51 +0100, andrew harrisona! <andrew.nospam@uk.sun.com> wrote:P   >t
 >jlsue wrote:m >>  B >> I see.  So if you document a particular behavior, and then someH >> competitor complains that it does exactly what it's documented to do,) >> then you should fix it.  Yeah.  Right.  >> e >e> >Sorry that isn't what you did, try again. You documented the : >fact of the 3x difference and then went on to claim that 7 >this was near UMA and that it would not be a problem. e  @ Exactly.  But it is correct.  Yes or no.  If it is, then there's? nothing to fix.  But that's not to say that you may not want toa9 improve, if possible, and that's for the next generation.lC The fact still remains that it was disclosed in the white paper you, keep complaining about.f  F You haven't proven that it's that much of a problem in the real world.   > E >This is getting boring, how about Oracle apps, WildFire performance dB >was dreadfull for Oracle Apps (you were unable to use OPS) a muchE >smaller and less expensive Sun and a much smaller and less expensive % >IBM box trashed the WildFire result.-  D Uh, yep it is getting boring.  You're about as dense as they come in
 this area.  B Again: a single instance that may or may not be widely applicable.E Your logical progressions are what I am questioning most of all here.bD You try to take specific instances to prove the rule, but that's not how logic works.   >t? >> All I got that comes close is two entries.  Both were in theuH >> fa.alpha-osf-managers newsgroup.  And neither of them had a "Wait forB >> Marvel" comment from Rob Young.  His comments in that vein wereH >> directed at your comments, which, on analysis, were nothing but smoke >> from a non-existent fire. >> p >d1 >Do some more research or check with Rob remembera1 >you arn't generally good at this so a second tryp >might be a good idea. >   E I see.  I explain to you how I've actually done the searches, and youe> can't back up your statements, so you put the blame on others.  D Don't claim that the GS series performance issues are a huge problem@ unless you can back up those claims with real stats.  One or twoC examples just doesn't cut it - and will burn you in the end becausel= I'll take the examples I've seen posted in this same forum to.? highlight how Sun's been lying in their performance claims too.    ------------------------------  $ Date: Thu, 9 Aug 2001 20:35:47 -0400' From: "Bill Todd" <billtodd@foo.mv.com>h1 Subject: Re: Alpha:  an invitation to communicatee( Message-ID: <9kva9a$o5r$1@pyrite.mv.net>  - "jlsue" <jlsuexxxz@home.com> wrote in messagea2 news:2lq2ntc3cnns4j94fpp1hs6qgahb66sl7m@4ax.com...5 > On Fri, 03 Aug 2001 17:17:51 +0100, andrew harrisonh# > <andrew.nospam@uk.sun.com> wrote:    <a lot>o  J Since neither you, nor Andrew, nor Kerry seem to be getting tired of this,G I'll try to inject a modicum of objectivity.  As I understand them, the  facts are as follows:q  G 1.  Wildfire's performance was in fact somewhat overanticipated (by RobcL among others, and I do remember how quickly he changed his tune to "Wait forK Marvel!" - at least in comp.arch - after the initial Wildfire TPC-C figuresaL came out), which made the actual performance a tad disappointing (especially9 when coupled with the delays in Wildfire's introduction).d  H 2.  Wildfire systems nonetheless produced something like $800 million inG revenue in 2000 despite component shortages and less than a full year's K availability and could likely have doubled that revenue in 2001 but for  a)iC the industry-wide slump and  b) the Alpha debacle, so even if theireH performance wasn't quite what people had hoped for it satisfied a lot ofF customers just fine (and I seriously doubt that any customers considerI Wildfire's well-documented performance in anything remotely like the same H category that Sun's customers consider the E10K cache problems and Sun's attempts to hide them).a  J 3.  The Compaq comparison that quoted 600 ns. as the E10K idle latency wasJ simply wrong, either due to incompetence or intentional deceit.  This is aJ moderately subtle point, but since the paper explicitly stated that it was; idle latency it was responsible for that level of subtlety.e  E 4.  Multi-instance cluster-style database TPC-C results are in no waynJ comparable to single-instance TPC-C results - period.  They are to a largeF degree meaningless, since one can generate almost any number one wantsL simply by adding instances and disks ad infinitum (the $/TPC-C figures mightJ have some limited validity, though - as long as one doesn't try to compareG multi-instance results against single-instance results).  Most databasetL applications are nowhere nearly as easily- and fully-partitionable as TPC-C,E and hence cannot easily (and often cannot at all) take advantage of aaH multi-instance database solution.  So if you want to measure a machine's= general-purpose database prowess against its competitors, usee* single-instance configurations or shut up.   - bill   ------------------------------   Date: 9 Aug 2001 12:11:29 -0500i9 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen)o* Subject: Re: Article from Information week3 Message-ID: <n65dGX$rFe5o@eisner.encompasserve.org>f  g In article <Cswc7.732$Yx2.18032@news.cpqcorp.net>, "Sue Skonetski" <susan.skonetski@compaq.com> writes:,7 > http://www.informationweek.com/story/IWK20010808S0007d > - >                   Wednesday, August 8, 2001o > + >                    OpenVMS Is Flying Highe  ? >                    In addition, two servers replace 10 in theiJ >                    predecessor, the Block 10, which also has a differentB >                    operating system inside from EMC Corp.'s DataB >                    General division, when DG was its own systems  9 I didn't realize this was new business.  Congratulations.   G >                    company. The OpenVMS will start three times faster6I >                    and reboot twice as fast. Moreover, the new plane is.  6 But hopefully less often, even normalized per-machine.   ------------------------------  % Date: Thu, 09 Aug 2001 13:18:12 -0400l- From: JF Mezei <jfmezei.spamnot@videotron.ca>a* Subject: Re: Article from Information week, Message-ID: <3B72C5D2.986C7D54@videotron.ca>   Sue Skonetski wrote:F >                    Rich Marcello, general manager and VP of Compaq'sF >                    high-performance systems division, says there areE >                    450,000 OpenVMS systems running worldwide-it's ao4 >                    $3 billion business for Compaq,  P Thanks for that number. So we know how much revenus Compaq thinks VMS generates.        > >                    telecommunications markets. "We have manyF >                    commitment letters out to support OpenVMS throughA >                    2011," says Marcello, "and we even have somet1 >                    government pacts past 2015."   E Interesting that Compaq would make different commitments to differenteL customers. That doesn't yield much confidence.  The mere fact that Compaq isM now forced to put such commitments on paper is an indication of the fact thateI Customers do not trust Compaq to maintain VMS for very long. Do customers L require Microsoft or Sun to write down on paper some commitment to their own	 product ?e   ------------------------------   Date: 9 Aug 2001 13:41:03 -050009 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen)<* Subject: Re: Article from Information week3 Message-ID: <iidNMQ89LbXw@eisner.encompasserve.org>i   In article <rdeininger-0908011400220001@user-2ivea7a.dialup.mindspring.com>, rdeininger@mindspring.com (Robert Deininger) writes:e7 > In article <3B72C5D2.986C7D54@videotron.ca>, JF Mezeib' > <jfmezei.spamnot@videotron.ca> wrote:h >  > A >> >                    telecommunications markets. "We have many I >> >                    commitment letters out to support OpenVMS throughaD >> >                    2011," says Marcello, "and we even have some4 >> >                    government pacts past 2015." >> oH >> Interesting that Compaq would make different commitments to different3 >> customers. That doesn't yield much confidence.  o > I > These sound like detailed contracts to support specific products.  SuchhK > contracts cost money.  Why would Compaq force one-size-fits-all contracts F > on its customers?  If I want Compaq to promise support through 2011,K > that's what I'll negotiate, and pay for.  If someone else wants a promised* > through 2015, I expect they'll pay more.  H I know a company that had such a specific contract to continue to supplyF a certain Alpha model for a number of years.  When push came to shove,F however, they were bought out of the contract with an offer they could* not refuse (for a subsequent Alpha model).   ------------------------------  % Date: Thu, 09 Aug 2001 14:56:37 -0400m2 From: rdeininger@mindspring.com (Robert Deininger)* Subject: Re: Article from Information weekL Message-ID: <rdeininger-0908011456390001@user-2ivea7a.dialup.mindspring.com>  3 In article <iidNMQ89LbXw@eisner.encompasserve.org>,r: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen) wrote:    J > I know a company that had such a specific contract to continue to supplyH > a certain Alpha model for a number of years.  When push came to shove,H > however, they were bought out of the contract with an offer they could, > not refuse (for a subsequent Alpha model).   Sounds reasonable to me.   -- $ Robert Deininger rdeininger@mindspring.comc   ------------------------------  % Date: Thu, 09 Aug 2001 17:10:54 -0400U- From: JF Mezei <jfmezei.spamnot@videotron.ca>E* Subject: Re: Article from Information week, Message-ID: <3B72FC5C.EE2C9418@videotron.ca>   Robert Deininger wrote:eI > These sound like detailed contracts to support specific products.  Such-K > contracts cost money.  Why would Compaq force one-size-fits-all contractse > on its customers?.  J It isn't Compaq that *want* to commit to VMS, it is the customers who wantM written commitments from Compaq. And why should Compaq tell one customer that,E they will only commit to 2010 while they will commit to 2015 to otherL customers ?o  L If Compaq truly intends to commit to VMS, then it should be able to tell all% its customers it will commit to 2015.t  I The fact that Compaq is making different commitments tells me that Compaq/I leaves the room wide open to cancel VMS and then pay some amount to thosenM customers to whom it had made commitments which Compaq won't honour. In otherNN words, Compaq keeps track of how much it will cost it when it cancels VMS at aL specific dat (how many customers will be legally affected because Compaq had committed otherwise).>  4 >  If I want Compaq to promise support through 2011,* > that's what I'll negotiate, and pay for.  M If you don't trust a vendor to be alive then you don't do business with them.tK If you don't trust the vendor to maintain a product, then you don't buy the K product.  Compaq should take a very strong hint if customers distrust it sor0 much that they require such written commitments.  B It shows that the fear that Compaq will cancel VMS is a real fear.   ------------------------------  % Date: Thu, 09 Aug 2001 14:00:20 -0400b2 From: rdeininger@mindspring.com (Robert Deininger)* Subject: Re: Article from Information weekL Message-ID: <rdeininger-0908011400220001@user-2ivea7a.dialup.mindspring.com>  5 In article <3B72C5D2.986C7D54@videotron.ca>, JF Mezeie% <jfmezei.spamnot@videotron.ca> wrote:n    @ > >                    telecommunications markets. "We have manyH > >                    commitment letters out to support OpenVMS throughC > >                    2011," says Marcello, "and we even have somet3 > >                    government pacts past 2015."e > G > Interesting that Compaq would make different commitments to differentc2 > customers. That doesn't yield much confidence.    G These sound like detailed contracts to support specific products.  SuchrI contracts cost money.  Why would Compaq force one-size-fits-all contractsaD on its customers?  If I want Compaq to promise support through 2011,I that's what I'll negotiate, and pay for.  If someone else wants a promiseP( through 2015, I expect they'll pay more.   > The mere fact that Compaq isO > now forced to put such commitments on paper is an indication of the fact that"? > Customers do not trust Compaq to maintain VMS for very long. a  F This is a silly claim.  Real customers with real business needs almost: always commit their contracts to paper.  Nothing new here.   > Do customersN > require Microsoft or Sun to write down on paper some commitment to their own > product ?:  H I have no doubt the customers do want paper, if they have critical needs for their business.p  G If you want microsoft to promise to sell you whatever they are foistingnI when 2011 rolls around, at a price of their choosing, then you don't needr a paper contract.r   -- e Robert Deininger rdeininger@mindspring.comb   ------------------------------  % Date: Thu, 09 Aug 2001 20:14:54 +02000, From: Didier Morandi <Didier.Morandi@gmx.ch>* Subject: Re: Article from Information week& Message-ID: <3B72D31E.9F1A2D39@gmx.ch>   Sue Skonetski posted:e  5 > "and we even have some government pacts past 2015."y  3 Super! I planned to retire in 2015, when I'm 65 :^)-   D.   ------------------------------  # Date: Fri, 10 Aug 2001 02:12:26 GMTK$ From: Scott Vieth <svieth@wi.rr.com> Subject: Re: AW: SYBASE on VMS) Message-ID: <3B7343BF.36370360@wi.rr.com>E  O Before you convince the entire world to use Cache on VMS, check to see if CacheSO will support NUMA on the big AlphaServers.  I heard something earlier this weekhM from someone very NUMA-proficient that Cache won't run properly on a NUMA boxn yet.  O I'd hate to have someone buy a box with eight processors and then find out theyh can only use four of them...  ? Intersystems has promised NUMA support somewhere down the road.<   -Scott  * fabio_compaq@ep-bc.petrobras.com.br wrote:   > Jakobs >c! > Let's open this discussion ok ?p > H > Is there a way to port from Oracle RDB, Ingres, Sybase, Progress under	 > OpenVMSi  >  to Intersystems's Cach ????? > 	 > Regardsr >o > Fbio Cardoso  >c > # >                     <erberj@post. 0 >                     ch>                  Para:N >                                          fabio_compaq@ep-bc.petrobras.com.br. >                     08/08/2001           cc:I >                     11:11                Assunto:     AW: SYBASE on VMSh >e >i >nE > But I cannot see any parallelism between Sybase DB and Intersystemse. > Product. So migration will be max. difficult >d
 > Jakob Erbers >w( >      -----Ursprngliche Nachricht-----/ >      Von: fabio_compaq@ep-bc.petrobras.com.br0, > [SMTP:fabio_compaq@ep-bc.petrobras.com.br]4 >      Gesendet am:   Mittwoch, 8. August 2001 15:02 >      An:  erberj@post.ch" >      Betreff:  Re: SYBASE on VMS > K >      It is a pos-relational database which runs under OpenVMS, WNT, Linux  >n >      Click at. >h" >      http://www.intersystems.com >r >      Regards >u >      Fbio C.  >M( >                          <erberj@post.5 >                          ch>                  Para:" >o% > fabio_compaq@ep-bc.petrobras.com.brp3 >                          08/08/2001           cc:0J >                          10:00                Assunto:     Re: SYBASE on > VMSa > * >      What is Intersystems cache, please? >PC >      <fabio_compaq@ep-bc.petrobras.com.br> schrieb im Newsbeitragi >oJ > news:<OF2785CEFB.37FFE864-ON03256AA2.0043B439@ep-bc.petrobras.com.br>... >t >      People, > A >      What is the most promisor database running under OpenVMS ?  > Intersystems'a >      Cach    ?? >      So migrate to it ...  >m >      Regards >r	 >      FCh > & >                          Arne Vajhj6 >                          <arne.vajhoej@        Para: > Info-VAX@Mvb.Saic.Come4 >                          gtech.com>            cc:K >                                                Assunto:     Re: SYBASE onb > VMSh% >                          07/08/2001-  >                          10:10& >                          Responder a& >                          Arne Vajhj >p >      Jakob Erber wrote:nL >      > Sybase will soon stop its support for its DB product on OpenVMS. Is > there > >      > anybody out there, who is also effected by this step? >P >      Oh yes !o >m >      Arnes >  >      ----------    ------------------------------   Date: 9 Aug 2001 13:48:27 -0500 9 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen)d1 Subject: Re: Backup Internet MX/SMTP server (ASP)'3 Message-ID: <mJX7qzKRuyMd@eisner.encompasserve.org>   W In article <tn5m3ihdukqa56@corp.supernews.com>, "Lou Solomon" <lny98@yahoo.com> writes:n  > > Can anyone recommend a service provider of MX/SMTP services? > N > In case our own mail server goes down I would like to have backup MX records > pointing to someone reliable.t > H > Besides variable storage needs, I would like them to have some "alert"J > system to tell us that they are spooling our mail (rather than them justJ > trying to forward it on to our 'probable' non-working mail server).  OurM > current ISP will backup 10MB of mail (which is not enough for us), and does( > not have any alert system. >  > Thanks in advance. > N > While on this subject, can only recommend a good, reliable Web based company > to handle our DNS services?   / Contact Steve Arnold (Arnold@eisner.decus.org).s   ------------------------------  $ Date: Thu, 9 Aug 2001 14:32:31 -0400% From: "Lou Solomon" <lny98@yahoo.com>I- Subject: Backup Internet MX/SMTP server (ASP)t/ Message-ID: <tn5m3ihdukqa56@corp.supernews.com>t   All:  < Can anyone recommend a service provider of MX/SMTP services?  L In case our own mail server goes down I would like to have backup MX records pointing to someone reliable.c  F Besides variable storage needs, I would like them to have some "alert"H system to tell us that they are spooling our mail (rather than them justH trying to forward it on to our 'probable' non-working mail server).  OurK current ISP will backup 10MB of mail (which is not enough for us), and does  not have any alert system.   Thanks in advance.  L While on this subject, can only recommend a good, reliable Web based company to handle our DNS services?t   Lou Solomonr Intercounty Clearance Corp.o   ------------------------------  % Date: Thu, 09 Aug 2001 22:46:24 -0400m) From: John Johnstone <jj_usenet@mail.com>u1 Subject: Re: Backup Internet MX/SMTP server (ASP)e( Message-ID: <3B7312BF.53B8B7DB@mail.com>   Lou Solomon wrote: > H > Besides variable storage needs, I would like them to have some "alert"J > system to tell us that they are spooling our mail (rather than them justJ > trying to forward it on to our 'probable' non-working mail server).  OurM > current ISP will backup 10MB of mail (which is not enough for us), and doesc > not have any alert system.  E I've never heard of anyone offering an mail relaying alerting service. fromG an ISP but perhaps some have it.  You'll want to be sure that you don'trD routinely have an occasional mail relay through your ISP or else you haveH to find some way to deal with false positive alerts.  Without going intoE all the gory details, my company routinely gets 1 or 2 messages a daye from our ISP's mail relay system.   ------------------------------  % Date: Thu, 09 Aug 2001 22:56:47 -0400e) From: John Johnstone <jj_usenet@mail.com>,1 Subject: Re: Backup Internet MX/SMTP server (ASP)i( Message-ID: <3B73152F.3C0D3278@mail.com>   John Johnstone wrote:t > J > to find some way to deal with false positive alerts.  Without going intoG > all the gory details, my company routinely gets 1 or 2 messages a day'# > from our ISP's mail relay system.e  ! Actually, what I meant to say was   F    my company routinely gets 1 or 2 mail messages a day that have been/    relayed through our ISP's mail relay system.f   ------------------------------  % Date: Thu, 09 Aug 2001 18:30:48 +0200n< From: Jan-Erik =?iso-8859-1?Q?S=F6derholm?= <noone@home.com>7 Subject: Re: Can queue manager handle 100.000 entries ?u( Message-ID: <3B72BAB8.5A4C679F@home.com>  : Or use NBL (from Arne Vajhoe) that sends any file directly; to any smtp server without using either UCX och QMAN. (Alsoo4 OK to send MIME formatted mails with attachments...)   Jan-Erik Sderholm.s   Brian Tillman wrote: > M > If you're worried about queue manager performance, get an SMTP package thatv= > doesn't use the queue manager.  MadGoat's MX comes to mind.P   ------------------------------  % Date: Thu, 09 Aug 2001 20:14:44 +0200e< From: Jan-Erik =?iso-8859-1?Q?S=F6derholm?= <noone@home.com>7 Subject: Re: Can queue manager handle 100.000 entries ?s( Message-ID: <3B72D314.3F3BB0BC@home.com>   Just a note...7 On my hobbyist box (DECpc AXP 150, aka "Jensen") is now : running a DCL script that print a file to a stopped queue.: At aprox 40.000 extries I had to SYSGEN the system because@ low virt mem. Currently att aprox 50.000 entries "and counting".  9 The numbering so far have been (formating from SHO QUE) :n     Entry  Jobname ...   -----  ------- ...       1m       2        3u     ...a    9999e 1000000t 1000001e 1000001s     ...e 1009999  2000000t 2000001h  
 and so on.  < One thing, the entry number on the "SHO QUE" output have nowD reached the left margin, so it's gonna be interesting at 9009999 :-)" I'll be back then (in a few hours)   Jan-Erik Sderholm.5   ------------------------------  % Date: Fri, 10 Aug 2001 00:02:29 +0200s< From: Jan-Erik =?iso-8859-1?Q?S=F6derholm?= <noone@home.com>7 Subject: Re: Can queue manager handle 100.000 entries ?8( Message-ID: <3B730875.8C154938@home.com>  2 Well, shutting down for the day (or rather night). Status:g6 - 87.488 queue entries (highest entry number 8007488).B - QMAN process "Peak WS" = 198.656 and "Peak virt size" = 422.336.? - sys$system:sys$queue_manager.qman$journal now 257.142 blocks.i& - Two more reboots due to "INSVIRMEM".   Notes :r8 - Still adding aprox 6 entries/second as from the start.   No slowdown.F - Takes "forever" to START/QUE/MAN, say 5-10 minutes on my 150Mhz box.; - Can the "journal" be sized when doing START/QUE/MAN/NEW ?b  0 I hope to reach the 100.000'th entry tomorrow...   Jan-Erik Sderholm   ------------------------------  # Date: Fri, 10 Aug 2001 00:55:10 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)7 Subject: Re: Can queue manager handle 100.000 entries ?n/ Message-ID: <OhGc7.7$bB1.3774@news.cpqcorp.net>d  g In article <3B72D314.3F3BB0BC@home.com>, Jan-Erik =?iso-8859-1?Q?S=F6derholm?= <noone@home.com> writes:   0   We have folks with thousands of queues around.  I   Each queue manager can handle a maximum of one hundred thousand entriesdM   in parallel (retained, active, pending, etc), assuming disk space to store rM   all that stuff is available.  Up to five queue managers can be sharing the  F   same queue database.  Multiple disjoint queue databases are possible   within the same cluster.     :Just a note...eB :...now running a DCL script that print a file to a stopped queue.; :At aprox 40.000 extries I had to SYSGEN the system because.A :low virt mem. Currently att aprox 50.000 entries "and counting".i :r: :The numbering so far have been (formating from SHO QUE) : ..    K   Please treat the entry number as an opaque longword value -- a few folks oL   have coded assumptions on the allocation sequence and/or on the magnitude I   of the entry value, and at least one group has gotten caught out by an m   (incorrect) assumption.e    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: Thu, 9 Aug 2001 15:57:33 -04002 From: "Sue Skonetski" <susan.skonetski@compaq.com> Subject: CETS invitation/ Message-ID: <iWBc7.3$bB1.2081@news.cpqcorp.net>   E You 're invited to join us in Anaheim,CA on September 9-14 to immerse G yourself in Compaq-related technology.This year 's symposium covers thevF technical aspects of Compaq 's entire range of enterprise products and< solutions,including access devices,servers,storage,operatingK systems,management systems and third-party solutions --including the latestsG news about Compaq 's plans for Alpha and Itanium roadmaps and products.o  E Featured Speakers include Michael Capellas,Chairman and CEO of Compaq   H Computer Corporation,and members of Compaq 's Senior Leadership team,who/ will be presenting their vision and strategies.e  B Compaq Enterprise Technical Symposium focuses on Key Technologies:  > >Enterprise backup solutions,storage area networking (SAN),and network-attached storage  F (NAS),featuring Compaq StorageWorks Tand Compaq S Nworks Tproducts and services  C >Detailed implementations of Linux,Microsoft Windows NT/2000,NovellA NetWare,OpenVMS T,   and Tru64 TUNIX-  J >Client computing with Compaq workstations,desktops,portables,and Internet access devices  C >Edge of the network applications including technologies,trends andn strategies for security ande  J authentication,content serving such as streaming media,replication and web caching solutionsn  E >Enterprise management solutions,enterprise applications,and industry  solutions featuringo   key Compaq partners.  ; >Applications for e-business,including e-commerce,knowledge  management,businesse  1 intelligence,and customer relationship managemente  G >Wireless technologies including Compaq iP Q THandhelds and Blackberry.a  I >Database solutions,including technologies,architectures and optimization- with Oracle,  # Microsoft,and other Compaq partners5   >Thin client computing  H >High Performance Computing (HPC),high availability and clustered server platforms,featuring.  G the industry standard ProLiant T,AlphaServer T,and overviews of NonStopi THimalaya T   G >IT infrastructures using Compaq DISA and ENSA architectures for highlym
 scaleable andi   available environments  H >Airtight solutions for firewalls,data integrity,and enterprise security concerns  I >Networking strategies and solutions,including wireless,broadband,LAN andu WAN technologies  J >Messaging and collaboration solutions that scale from hundreds to tens of thousands of users  I >Compaq technology roadmaps and directions,for products ranging from palm  tops to data   center systems  : Pre-Conference Seminars (for additional fee):September 8-9  ! Conference Program:September 9-14o  $ Anaheim Convention Center,Anaheim,CA  7 $1395.00 (early bird registration,$1495 after August 10p   th   )includes full conferenceC  J access to Compaq Enterprise Technical Symposium 2001 conference events and  3 bonus admission to ITUG Summit,co-located with CETSa  B Visit www.CETS2001.com or and register on the conference portal or   call 1-888-639-2990,  6 To learn more about this premier educational event and  8 to reserve your place visit www.CETS2001.co or call your   Compaq Representative!   Featured Speakerst   Deep Technical Content   Conference Dates   Location   Cost   Registration Info    ------------------------------  # Date: Thu, 09 Aug 2001 22:55:47 GMTe  From: jlsue <jlsuexxxz@home.com>K Subject: Re: Comments from a VMS customer (and I would like to stay as one) 8 Message-ID: <rt03ntklfsmm24njasgustadfemrn5iea5@4ax.com>  , On Fri, 03 Aug 2001 13:42:28 -0400, JF Mezei% <jfmezei.spamnot@videotron.ca> wrote:D     >nM >Think about it: if you need to add stuff to your machine and the only way is5L >to go from Alpha to IA64 for the whole kit and caboodle, isn't it easier toJ >decentralise your stuff and add the new application on a separate box andK >leave the Alpha-VMS alone in its corner to continue doing what it has been O >doing for years ? This way, you don't have to worry about porting your apps to = >IA64, having dual platforms during a testing period etc etc.o  E The Centralization/De-Centralization process is a never ending cycle.iD Decentralization is great until you get past some critical mass, and> then the cost to support becomes too great, and companies willB consolidate/centralize until that hurts too much, and they they'll decentralize... etc.  2 Keeps the consultants (including myself) employed.   ------------------------------  $ Date: Wed, 8 Aug 2001 11:43:05 -04002 From: "Sue Skonetski" <susan.skonetski@compaq.com> Subject: Compaq/Avnet/Intels2 Message-ID: <J5dc7.712$Yx2.18271@news.cpqcorp.net>  / Dear Newsgroup this is from the Avnet web site.l  
 Warm Regards,    Sue       0        Dear Avnet Enterprise Solutions Customer,  I        Compaq recently announced an agreement with Intel Corporation that * will consolidate Compaq's 64-bit family ofF        servers on to Intel's Itanium processor architecture. With this9 agreement, the Itanium architecture will, by 2004, becomehC        the standard for all Compaq enterprise server product lines,e: providing you with a smooth transition to new products and        technology.  E        We, at Avnet Enterprise Solutions, are very excited about thisr9 merging of technologies because it offers you the best of J        all possible futures - the fabrication proficiency and economies of2 scale of the world's leading volume microprocessorK        producer, and the engineering excellence, 64-bit computing expertisen( and maturity of the Compaq architecture.  I        As veterans of the data center and with over two decades of Compaq-+ experience serving influential Fortune 1000:K        customers, Avnet Enterprise Solutions is more than qualified to workV- with you through this transition. Through our H        world-class technical and financial capabilities, we are ready to3 preserve and enhance your investment in Tru64 UNIX, I        OpenVMS, NSK and Windows OS. Our seamless relationship with Compaqt( will continue to provide you the highest+        level of support and responsiveness.t  0        A lasting commitment to current platformsG        The availability of industry-leading 64-bit technology on Compaqd3 enterprise server platforms and the fundamentals ofrL        scalability, data integrity, availability and reliability will remain( at the forefront of all Compaq products.  J        A full port of the OpenVMS, Tru64 UNIX and NonStop Kernel operating- systems has already begun, along with NonStop G        middleware to the Itanium architecture, ensuring alignment, over . time, of all Compaq 64-bit enterprise servers.  K        The combination of Tru64 UNIX, OpenVMS, NonStop Kernel, Windows 2000 + or Linux with the best 64-bit technology in K        the industry will give you a powerful enterprise-computing engine tol/ meet your continuously challenging environment.d  <        Avnet Enterprise Solutions' "Road to Itanium" ProgramK        One of Avnet Enterprise Solutions' top priorities is to protect yourt2 technology investments today and in the future. InL        response to the Compaq/Intel agreement, our "Road to Itanium" program. is designed to help you develop safe, flexibleE        technical and financial roadmaps to optimize business criticalW0 application performance and enhance the business'        value of technology investments.s  G        Using strategic technical assessment services: Needs Assessment, ( Performance Analysis, Capacity Planning,F        Technology Roadmap; and financial acquisition services: Cost of$ Ownership Assessment, Business ValueE        Assessment, Technology Management Maintenance ServiceSM, Avnet - Enterprise Solutions' technical and financialpH        consultants architect Compaq solutions to help customers minimize2 risk, maximize flexibility and optimize the use ofI        capital through its proven infrastructure methodology as customerst+ make IT changes. Moreover, Avnet EnterpriseMG        Solutions Intel Architecture specialists help ensure a low-risk, - highly flexible path to Itanium architecture.   .        AlphaServer, NonStop, ProLiant RoadmapsE        For the next two and a half years, the roadmap for Alpha-based - systems remains unchanged. Performance boosts L        across all AlphaServer products will occur as planned, beginning with% acceleration enhancements of the EV682I        processor. The Alpha EV7-based AlphaServer systems are expected inr, early 2003, with the first enterprise serverK        based on the next-generation Itanium processor expected in 2004. Alli# Tru64 UNIX and OpenVMS features and E        characteristics will be available on the new server, and mixed 6 clustering of Itanium systems and existing AlphaServer!        systems will be supported.   H        MIPS processor upgrades to the NonStop Himalaya architecture will( continue as planned through 2003, with aC        transition to the Itanium Processor Family by 2004. Existinga7 applications will run on the IPF-based Himalaya with no.H        source code changes; common development tools and management APIs* will simplify application deployments, andI        current peripherals will be supported. Microprocessor support willr0 overlap the architectures, and IPF-based NonStopG        Himalaya systems will run alongside current systems in an Expandm. network or NonStop ServerNet Cluster, ensuring        investment protection.   E        Later this year, Compaq will introduce the first Itanium-based 0 ProLiant systems, advancing the capabilities forG        customers who choose Windows 2000 and Linux on ProLiant as their.* platform of choice for high end computing.H        Compaq will continue, as well, to deliver a roadmap of continuing5 innovation in 32-bit ProLiant servers over the coming-C        years, including ultra-dense, hyper-dense and modular server  innovations.  H        Rest assured that when you are ready to upgrade, you can count on2 Avnet Enterprise Solutions to ease you through the>        migration with thorough, proven technical and financial2 roadmaps.based on years of experience implementingJ        Compaq and Intel solutions. Look forward to a clear and stable path4 to the future, but also know that the tools you rely:        on today will remain viable for many years to come.          Press ReleaseK          Avnet Enterprise Solutions Announces The "Road to Itanium" Programn          Web Site0H          Compaq to Consolidate Entire 64-bit Server Line on the ItaniumT Processor Family          Presentationi'          Road to Itanium -  (268kb ppt)i  L        If you have any questions, please contact your local Avnet Enterprise Solutions account manager.          Sincerely,-          Jim Miltonu)        Vice President and General Managere        North America"        Compaq Computer Corporation?                                                       Dana Huth K                                                       Senior Vice PresidentvF                                                       Avnet Enterprise	 Solutionse        G                           Copyright  1998-2001 Avnet, Inc., U.S.A. Allr rights reserved.   ------------------------------  $ Date: Thu, 9 Aug 2001 13:29:11 -0400' From: "Bill Todd" <billtodd@foo.mv.com>  Subject: Re: Compaq/Avnet/Intela( Message-ID: <9kuh9e$37l$1@pyrite.mv.net>  = "Sue Skonetski" <susan.skonetski@compaq.com> wrote in message , news:J5dc7.712$Yx2.18271@news.cpqcorp.net...   ...e  0 >        AlphaServer, NonStop, ProLiant RoadmapsG >        For the next two and a half years, the roadmap for Alpha-basede > systems remains unchanged.  G Whoopee!!  Yet another voice stating that EV8 will appear after all (itaK *was*, of course, planned to appear before 2004, which starts less than 2.5m years from now).    Performance boostssI >        across all AlphaServer products will occur as planned, beginningo with' > acceleration enhancements of the EV68 K >        processor. The Alpha EV7-based AlphaServer systems are expected ini
 > early 2003,2  J Hmmm.  At least *very* recently, EV7s were expected in 2002.  So, like theC usual Compaq-speak, 'unchanged' means 'we hope you don't notice the  changes...'.  !  with the first enterprise serveriI >        based on the next-generation Itanium processor expected in 2004.1 All0% > Tru64 UNIX and OpenVMS features and? >        characteristics  & except underlying hardware performance  % > will be available on the new serverB   ...C   - bill   ------------------------------   Date: 9 Aug 2001 21:54:36 -0700o1 From: nothome@spammers.are.scum (Malcolm Dunnett) % Subject: CSWS Authentication question , Message-ID: <94taWMHqrkHi@malvm6.mala.bc.ca>  > I've been running the OSU webserver for several years and have% just started experimenting with CSWS.v  > It seems from what I've found so far that one can authenticate: a request against a VMS username/password, but only in the: simple sense of testing for a valid combination ( ie using" the "require valid-user" clause ).  > With OSU it's possible to specify that the user must belong to: a particular group or hold a particular identifier ( using> an ACL-like syntax ). Is there an equivalent way of doing this; with CSWS? I'd like to specify that certain directories areS9 only available to users in the [FACULTY,*] group or users " who hold the REG_CLERK identifier.  8 I've also noticed that some of my OSU scripts don't work< properly when run using MOD_OSU on CSWS. The problem appears; to be that some of the parameters encoded in the URL aren't 7 being passed to the procedure or are not being properlyn/ decoded by CGI_SYMBOLS, eg if I send a url like   5 http://myserver/htbin/cgiapp?param1=test&param2=test2e  >  I get an error in the script saying it hasn't got a value for; param1. I haven't investigated this fully yet but I thought,; I'd see if anyone else had run into this so as to not waste= time chasing a known bug.>     Thanks in advance.  -  ps. I'm running CSWS 1.1 on VMS/Alpha 7.2-1.3   ------------------------------  # Date: Thu, 09 Aug 2001 20:15:08 GMTn2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)3 Subject: Re: DECstation 5000 error (was Re: pb dec)6/ Message-ID: <gbCc7.4$bB1.2368@news.cpqcorp.net>s  U In article <3B72AC7B.5044FE26@gmx.ch>, Didier Morandi <Didier.Morandi@gmx.ch> writes:. :"-[Gj]-" wrote: .. :> error$ :> ??    003    3        qdz    0096  C   The double question mark typically indicates a hard error on the  D   specified device.  I do not immediately know the particular deviceB   involved is here, nor do I have particular copies of the manualsC   for what appears to be a DECstation -- it is a MIPS box, and does0   not run OpenVMS, so...  4 :> i've decserver 5000/240 and i search all infos !!  D   This is very likely a DECstation 5000 model 240 MIPS box, and not    a DECserver.  	 :> error:a
 :> 3/misc/kbd4 :> ?STF (4: Ln#0 Kbd self test)s :> 9 :> 3/misc/mouse=  :> ?STF (4: Ln#1 Pntr self test)  @   You'll need to have a compatible keyboard and mouse connected.D   IIRC, the DECstation MIPS boxes used the old-style interconnects, E   and these are NOT compatible with the PS/2 mice and PS/2 keyboards.     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: Thu, 9 Aug 2001 21:46:14 GMT' From: Rick Dyson <Rick-Dyson@UIowa.EDU>a> Subject: Re: DECwindows keyboard problem: < > keys do not work) Message-ID: <3B7304A6.9E94A55C@UIowa.EDU>    Didier Morandi wrote:o >  > Jim Strehlow wrote:n > K > > When I click on the DECWindows DECterm icon and enter DCL commands, theaG > >  <  and  >  characters above the comma and period keys do not work.- > I > I have the same behaviour and probably all of us. Only the < and > keysl1 > which are on the left of the space bar do work.  >  > D.  C 	Look around in the terminal emulator settings.  There is a setting-J that will toggle between using the "," & "." for both the normal and shiftG values of the keys on the bottom row *OR* you can make the "<" & ">" be4D the result of a shift- operation.  I found this long ago too and wasE confused until I make the change and saved it in all my DECW$* config 	 files. :)j   Rick -- hH Richard L. Dyson                                    rick-dyson@uiowa.eduH  _   _  _____                    http://www-pi.physics.uiowa.edu/~dyson/H | | | ||_   _|  Senior Systems Analyst  --  INFORMM-Cerner Systems Group< | | | |  | |    The University of Iowa Hospitals and ClinicsH | \_/ | _| |_   Information Systems BT1000 GH       Office: 319/384-7016H  \___/ |_____|  Iowa City, IA 52242-1052               FAX: 319/384-7020   ------------------------------  $ Date: Thu, 9 Aug 2001 20:37:11 +02000 From: "Willem Grooters" <Willem@Grooters.100.nl>' Subject: DecWindows trouble on PWS500au 7 Message-ID: <3b72d72e$0$993$19deed1b@news.inter.NL.net>c  	 Hi there,   . hope anyone can show some light on my problem.  D I have a PWS500au, 256Mb memory, VX1 OXYGEN video card. I am using a# LK46W-A2 keyboard, SRM shows "411".a  J Running VMS7.2-1, No DECNet (crashed the system!) ,have installed TCPIP as default protocol.nD For this card, drivers have been downloaded and installed, after all required patches.eK I made no changes in startup-files - so using alle defaults - so DecWindows  will use LOCAL transport.t  E The server DECW$SERVER_0 will start, DTGREET and DTWELCOME will startaI showing up, screen is NOT complete: NO nodename, NO Options-button and NOtF image. Keyboard is dead (no action on any key), mouse can be moved but buttons are dead as well.AD but the system is dead slow: DECW$SERVER_0 process consumes all CPU.G Screensaver works, in that case any key will react - blocking evrythingl else.h  E When using TCPIP as transport, DECW$SERVER will start but DTGREET andoD DTWELCOME do NOT, screens have not shown up. X-terminal sessions areB possible from other systems (PC). Further behavious is no problem!  4 System is accesabel via Telnet without a problem....  L Originally the card was in PCI-slot 3 (the middle one), now in 5 (closest to0 case) - a 64-bit slot. This makes no difference.  F I just installed 7.3 (including DECNet-Plus) because of the (hopefully) better drivers) but the problem persists.o  1 No nasty things in log (DECW$Server_0_error.log).g  % Who can give me a clue where to look?   H I've been told that the driver could be a problem (conatins EV6-specific7 code?) meaning I have been sold an unsuable card.....??s     Willem Grootersr   ------------------------------  # Date: Thu, 09 Aug 2001 19:48:33 GMTe From: dittman@dittman.net + Subject: Re: DecWindows trouble on PWS500au > Message-ID: <lOBc7.2730$Nz2.39298@e420r-atl3.usenetserver.com>  / Willem Grooters <Willem@grooters.100.nl> wrote:iF : I have a PWS500au, 256Mb memory, VX1 OXYGEN video card. I am using a% : LK46W-A2 keyboard, SRM shows "411".e  7 My experience has been the VX1 drivers don't work right1/ on a PWS.  The driver is optimized for the EV6.  -- t Eric Dittman dittman@dittman.net.9 School Zones:  Man's attempt to thwart natural selection.    ------------------------------  # Date: Fri, 10 Aug 2001 04:07:01 GMTt? From: "Mark \(un-MASK\) Forsyth" <forsyMhm@optusAhome.coSm.aKu>  Subject: Fetchmail lookalike ??r" Message-ID: <8emvk9.6la.ln@really>  	 hi there,nL            Does anyone know of a Fetchmail clone for OpenVMS ?  it has to be
 free.....sigh    Ooroou	 Mark F...5   ------------------------------  $ Date: Thu, 9 Aug 2001 15:45:03 -0400  From: John Santos <JOHN@egh.com> Subject: Re: Flip-Chip" 5 Message-ID: <1010809153801.3968B-100000@Ives.egh.com>   + On Fri, 10 Aug 2001, David B Sneddon wrote:s  0 > At 10:04 AM 9/08/01 -0600, Dan O'Reilly wrote:: > > From a Compaq announcement I received via email today: > > L > >"Focal Point --> Compaq announces the latest Intel(r) Pentium(r) III FlipG > >Chip PGA processors at 1.26 GHz and 521K cache for ProLiant industryd > >standard servers."a > >iN > >Didn't DEC own the "Flip Chip" trademark for PDP-8's?  I suppose it doesn't@ > >matter too much, and maybe this is just dating me...<grin>... > >p > >r	 > >------ L > >+-------------------------------+---------------------------------------+L > >| Dan O'Reilly                  |                                       |L > >| Principal Engineer            |  "Why should I care about posterity?  |L > >| Process Software              |   What's posterity ever done for me?" |L > >| http://www.process.com        |                    -- Groucho Marx    |L > >+-------------------------------+---------------------------------------+ > ( > I have some "Flip chips" for PDP-11's. > Am I as old as you?s  C Possibly!  This same topic came up on a PC newsgroup several monthss> ago.  Intel is using "Flip-Chip" to describe its new processorH packaging.  I checked in some old DEC manuals, and they listed Flip-ChipE as a registered trademark, so unless Intel paid Compaq a large sum ofaE money, they are in violation.  (Maybe they did.  Maybe "Flip-Chip" isc> the "Alpha" technology that Intel is incorporating into IA64.)  
 > Regards, > Dave.  > -- aK > David B Sneddon (dbs)  OpenVMS Systems Programmer   dbsneddon@bigpond.comsK > Sneddo's quick guide ...          http://www.users.bigpond.com/dbsneddon/eK > DBS freeware at ...   http://www.users.bigpond.com/dbsneddon/software.htm K > "Life is what happens to you while you're busy making other plans" Lennont  B P.S. I think John Cleese once complained that "the big pond" was aD very disparaging name to apply to one of the world's great bodies of water.   -- e John Santosa Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------   Date: 9 Aug 2001 15:11:17 -0500n9 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen)e Subject: Re: Flip-Chip" 3 Message-ID: <5mZzRzv7lz5$@eisner.encompasserve.org>r  X In article <1010809153801.3968B-100000@Ives.egh.com>, John Santos <JOHN@egh.com> writes:  E > Possibly!  This same topic came up on a PC newsgroup several monthsS@ > ago.  Intel is using "Flip-Chip" to describe its new processorJ > packaging.  I checked in some old DEC manuals, and they listed Flip-ChipG > as a registered trademark, so unless Intel paid Compaq a large sum ofa > money, they are in violation.b  J Registered Trademarks can go dormant and must be renewed or they are lost. IANAL, but I heard it from one.i   ------------------------------  # Date: Thu, 09 Aug 2001 20:06:50 GMTp= From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)n Subject: Re: Flip-Chip"g0 Message-ID: <00A00475.C35DCF09@SendSpamHere.ORG>  X In article <1010809153801.3968B-100000@Ives.egh.com>, John Santos <JOHN@egh.com> writes:, >On Fri, 10 Aug 2001, David B Sneddon wrote: >a1 >> At 10:04 AM 9/08/01 -0600, Dan O'Reilly wrote:s; >> > From a Compaq announcement I received via email today:t >> >M >> >"Focal Point --> Compaq announces the latest Intel(r) Pentium(r) III FlipnH >> >Chip PGA processors at 1.26 GHz and 521K cache for ProLiant industry >> >standard servers." >> >O >> >Didn't DEC own the "Flip Chip" trademark for PDP-8's?  I suppose it doesn'tyA >> >matter too much, and maybe this is just dating me...<grin>...m >> > >> >
 >> >------M >> >+-------------------------------+---------------------------------------+ M >> >| Dan O'Reilly                  |                                       | M >> >| Principal Engineer            |  "Why should I care about posterity?  | M >> >| Process Software              |   What's posterity ever done for me?" |fM >> >| http://www.process.com        |                    -- Groucho Marx    |aM >> >+-------------------------------+---------------------------------------+s >> ,) >> I have some "Flip chips" for PDP-11's.M >> Am I as old as you? >oD >Possibly!  This same topic came up on a PC newsgroup several months? >ago.  Intel is using "Flip-Chip" to describe its new processoroI >packaging.  I checked in some old DEC manuals, and they listed Flip-ChipoF >as a registered trademark, so unless Intel paid Compaq a large sum ofF >money, they are in violation.  (Maybe they did.  Maybe "Flip-Chip" is? >the "Alpha" technology that Intel is incorporating into IA64.)   A That's it!   If you plug it into its carrier one way, it's an IPF C processor.  Pull it out, flip it over, and plug it into the carrierb and it's an Alpha! ;)l   --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM              J   "And of course, I'm a genius, so people are naturally drawn to my fiery I   intellect.  Their admiration overwhelms their envy!" -- Calvin & Hobbesr   ------------------------------   Date: 9 Aug 2001 20:03:25 GMTV1 From: bill@triangle.cs.uofs.edu (Bill Gunshannon)a Subject: Re: Flip-Chip" , Message-ID: <9kuqad$2okf$1@info.cs.uofs.edu>  A In article <5.1.0.14.0.20010810002330.009f96e0@mail.bigpond.com>,P0  David B Sneddon <dbsneddon@bigpond.com> writes:1 |> At 10:04 AM 9/08/01 -0600, Dan O'Reilly wrote:h; |> > From a Compaq announcement I received via email today:. |> >M |> >"Focal Point --> Compaq announces the latest Intel(r) Pentium(r) III FlipoH |> >Chip PGA processors at 1.26 GHz and 521K cache for ProLiant industry |> >standard servers." |> >O |> >Didn't DEC own the "Flip Chip" trademark for PDP-8's?  I suppose it doesn't A |> >matter too much, and maybe this is just dating me...<grin>...i |> n) |> I have some "Flip chips" for PDP-11's.e |> Am I as old as you? |>  2 Does the one with the most win??  I've got lot's!!   billB PS.  I looked at mine real close, but I couldn't see the processor anywhere...d   --  J 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>   n   ------------------------------  $ Date: Thu, 9 Aug 2001 17:05:48 -0500* From: WILLIAM WEBB <WWEBB1@email.usps.gov> Subject: RE: Flip-Chip" - Message-ID: <0033000031840578000002L082*@MHS>e  C =0AI prefer to think that when Intel got the intellectual property,h2 somebody started unpacking the oldest boxes first.  C That means that the PentiVAX 5 chip will come out in about 7 years.n   :^)    WWWebb   > -----Original Message-----1 > From: Info-VAX-Request@Mvb.Saic.Com at INTERNET ) > Sent: Thursday, August 09, 2001 4:44 PMrF > To: Webb, William W - Raleigh, NC; Info-VAX@Mvb.Saic.Com at INTERNET > Subject: RE: Flip-Chip"i >  >g< > In article <1010809153801.3968B-100000@Ives.egh.com>, John > Santos <JOHN@egh.com>h	 > writes:  >cH > > Possibly!  This same topic came up on a PC newsgroup several months=  B > > ago.  Intel is using "Flip-Chip" to describe its new processor; > > packaging.  I checked in some old DEC manuals, and theyy > listed Flip-Chip< > > as a registered trademark, so unless Intel paid Compaq a > large sum of! > > money, they are in violation.  > = > Registered Trademarks can go dormant and must be renewed or  > they are lost.! > IANAL, but I heard it from one.V >=   ------------------------------  % Date: Fri, 10 Aug 2001 10:04:58 +1200e& From: A Bonaveidogo <Asena@fsc.com.fj> Subject: FTP automation ? Message-ID: <001401c1211f$54e9dd40$100a640a@Patrick.fsc.com.fj>-  , This is a multi-part message in MIME format.  + ------=_NextPart_000_0015_01C12183.EA1EBD40v Content-Type: text/plain;/ 	charset="iso-8859-1"D Content-Transfer-Encoding: 7bit   F A colleage wrote a  .BAT file that would FTP the file on the PC (WinntH 4.0).  She wants to schedule it to run daily. When scheduler starts, theA status shows "couldn't start"... On the log file, bad username orhE password , something like that... She used adminstrator which has allY	 the priv.v   What username to be used here? f   NB : it worked when run online   thanks        AB 2    + ------=_NextPart_000_0015_01C12183.EA1EBD40. Content-Type: text/html; 	charset="iso-8859-1"h+ Content-Transfer-Encoding: quoted-printablen  > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD>      @ <META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR></HEAD> <BODY bgColor=3D#ffffff> <DIV>7) <P><FONT size=3D2>A colleage&nbsp;<SPAN =a# class=3D160455621-09082001>wrote=20 E </SPAN>a&nbsp; .BAT file that would FTP the file on the&nbsp;<SPAN=20sH class=3D160455621-09082001>PC (Winnt 4.0).&nbsp; She wants to schedule = it to run=20G daily. When scheduler starts, the status shows "couldn't start"... On =e
 the log=20B file, bad username or password , something like that... She used = adminstrator=20 ) which has all the priv.</SPAN></FONT></P>uH <P><FONT size=3D2><SPAN class=3D160455621-09082001>What username to be = used=20: here?&nbsp;</SPAN></FONT></P> H <P><FONT size=3D2><SPAN class=3D160455621-09082001>NB : it worked when = run=20 online</SPAN></FONT></P> <P><FONT size=3D2><SPAN =i3 class=3D160455621-09082001>thanks</SPAN></FONT></P>r <P><FONT size=3D2><SPAN = 3 class=3D160455621-09082001></SPAN></FONT>&nbsp;</P>n <P><FONT size=3D2><SPAN=20I class=3D160455621-09082001>AB&nbsp;</SPAN></FONT></P></DIV></BODY></HTML=  >h  - ------=_NextPart_000_0015_01C12183.EA1EBD40--b   ------------------------------  # Date: Thu, 09 Aug 2001 22:55:41 GMTA  From: jlsue <jlsuexxxz@home.com>% Subject: Re: Goodbye, good friend DECd8 Message-ID: <qgs2ntg0dlo7se7fv248kcrftiih7j5n1b@4ax.com>  3 On Mon, 06 Aug 2001 16:55:54 +0100, andrew harrisono! <andrew.nospam@uk.sun.com> wrote:e   > 
 >jlsue wrote:m   >> >A >> >Is the may have to migrate in 8 years Compaqs date for endingeA >> >support on Alpha or was it just a number you plucked randomlyU >> >from the air.a >> tH >> The point of the comment is that you will be able to get EV7 systems,A >> when they arrive, and they'll be extrememly good performers.  m >e$ >This is conjecture and speculation.  @ No shit.  But, unlike you, I present it and/or label it as such.= People can do with it as they wish, but they know what it is.  >s >> I'm sure D >> they'll be the top performer, but you'll find some way to "prove", >> something that hasn't come to pass yet.   >-! >More conjecture and speculation.,  E Are you really this stupid.  Do you think anyone reading my statementf? wouldn't know this already?  Do you have such a high opinion ofgC yourself - and such a low opinion of everyone else - that you think4 you need to state this.a   >D >e  >> But anyway, people won't haveB >> to migrate off of them right away - my belief is that, since weG >> haven't started shipping them yet, you'll still have fully supportedp  >> EV7 systems 8 years from now, > ! >More conjecture and speculation.v  ; Re-read it.  "... my belief... " even says, this.  Correct?o   >t4 >Havn't you worked it out yet you are talking about ) >futures which is by nature speculation. e  C Can't you read/understand English well enough that I know this, andE. even am up front about admitting it already?     >r0 >You seem to be stuck in a period that pre-dated2 >the Alpha announcments where people were prepared2 >to accept your conjecture and speculation as fact0 >and to ignore or forget your failure to deliver >against that.  F Oh, but of course *your* speculation and conjecture should be taken as fact, right?   >c1 >Since the 25th you have very little credibility -0 >when speculating about what Compaq will do with6 >Alpha or how Alpha will perform. You need to recover 1 >this and the speculation that you are currently -% >indulging in isn't the way to do it.-  C And your *personal* credibility has hit new lows as well.  You havefD proven to all in this forum that you're just waiting for any kind ofC weakness to show so that you can pounce on it.  You spend almost nouE time (that we've seen) in other forums emitting the strengths of yourD
 own products.4   >U >a) >> so I was making a SWAG estimate at the + >> minimum time before you'd have to do it.   . Huh!  wow!  No comment on this from you, Andy?C Didn't this statement make it obvious to you that my statements are  personal opinions?  	 >> [snip]a >>   > ! >More conjecture and speculation.>   Ho hum.  Yeah, yeah, yeah.   >> >? >> >How about less inane speculation and more actual statementsu: >> >of direction that have some sort of legitimacy. At the; >> >moment all you and your ilk are offering your customerso; >> >appears to be pure speculation, unless you really thinkb: >> >for example that Intel/HP are going to modify Mckinley8 >> >to add Alpha instructions to it at this stage in its >> >design.E >> > >>  I >> Bah!  I'm not the one to talk to about statements of direction.  Don't H >> waste your time.  And why do you somehow morph this into some kind ofA >> argument that's completely off topic?  What's wrong, you  have-% >> nothingn of value that's on-topic?  >>   >h; >So why if you arn't the one to be talking about statementsn: >of direction are you talking about what Compaq may or may >not do ?????????t  F Well, I can read Compaq's statements.  And I can repeat what I've beenF told, and even offer some of my own opinions on the matter.  CertainlyF they're not any less accurate than what you say about Compaq or Sun...? except maybe where you take quotes out of context to prove someeF invalid point, or where you put forth your own opinions as if they are facts.   >rG >> But I can state with just as much certainty as you (and just as much"G >> speculation as you would have about Sparc) that people who invest inCB >> EV7 systems will be able to use those systems for quite awhile. > # >I think this just proved my point.t >s  B Great!  This, then, just proves that Sun's statements on Sparc areE just as invalid (or as valid) as Compaq's statements on EV7.  Because - that's what I've just said in that paragraph.n   ------------------------------  % Date: Thu, 09 Aug 2001 22:35:28 -0400.) From: John Johnstone <jj_usenet@mail.com>o$ Subject: Re: Help, PWS500 locked up.' Message-ID: <3B731030.C6138EA@mail.com>D  C I've seen several systems become hung due to problems with memory.  F Although high IPL can be the culprit, just plain bad memory or a CPU /I motherboard related problem can be fatal.  By bad memory I mean a failurenL that hangs the memory bus and not just a few memory locations that are bad. 8 You can't execute the dump or console code in that case.  ' You might try the system exerciser withl   >>> set auto_action halt >>> init >>> sys_exer   Let it run for a while thenb   >>> show_status    >>> kill_diags
 >>> cat el     Malcolm Dunnett wrote: > N >  I have a PWS 500a running VMS 7.2-1 ( with most of the patches installed ). > G >  Today it was running along fine when it "locked up" ( ie all visibletJ > signs of activity ceased ). It dropped out of the cluster. There were noI > messages logged to the console. A ^P on the console terminal didn't getlI > me the >>>. I thus wasn't able to get a crash dump. After rebooting (by:I > hitting the reset switch ) I checked the error log, but there's nothingP > in there.s > J >  Does the refusal to respond to the console signal a hardware problem orG > could software cause this ( eg looping at a very high IPL ). How doesY? > one go about diagnosing this when you can't get a crash dump?"   ------------------------------  % Date: Fri, 10 Aug 2001 01:12:26 -0000T From: sword7@speakeasy.org8 Subject: Re: How to build a bootable media for a 11/780?/ Message-ID: <tn6d7qla1c7tfb@corp.supernews.com>n  * antonio.carlini <arcarlini@iee.org> wrote: > sword7@speakeasy.org wrote: A >> What files do I need to put on the virtual disk image to boot?u2 >> VMB.EXE, SYSBOOT.EXE, stand-alone backups, etc.  ( > The easiest way to do this is to start' > from scratch and install OpenVMS V7.2e& > onto a disk and then do whatever you& > do to turn that into a virtual disk.  , > (I would start by doing the proper install' > and then making a BACKUP/IMAGE backupu% > and restore onto an LD device using1# > a suitable size for the LD device + > file. Then that file is a block-for-blocke > copy of your bootable disk).  + > Otherwise you have to put a whole heap ofn) > files into the right place and then run % > things like WRITEBOOT to set up thel > bootblock and so on.  B Ok, thank you for information about that.  However, I want to makeJ a bootable virtual disk (RP06 emulation) outside VMS system so that I can B install into my VAX emulator.  I have ODS-2 specs that I found in I Freeware CD v5 at Compaq's web site.  I read it and found the boot block +H is in logical block zero.  That's why I need boot block information how J to load VMB.EXE, SYSBOOT.EXE, etc..  I know that VMB.EXE is searching for G a file called SYSBOOT.EXE in ODS-2 format.  Also, does anyone know any yJ software to create an bootable virtual disk for my VAX emulator that I am 4 writing?  Or I have to write a program to create it?  
 Thank you!   -- Tim Stark   -- -, Timothy Stark	<><	Inet: sword7@speakeasy.orgJ --------------------------------------------------------------------------F "For God so loved the world, that he gave his only begotten Son, that H whosoever believeth in him should not perish, but have everlasting life.. Amen." -- John 3:16 (King James Version Bible)   ------------------------------  % Date: Thu, 09 Aug 2001 20:23:15 +0200t, From: Didier Morandi <Didier.Morandi@gmx.ch>F Subject: Re: I just have to post this - and apoligse later Alpha/Intel& Message-ID: <3B72D513.8077AE0C@gmx.ch>   JF Mezei wrote:d  M > ../.. serious customers do not see this as an upgrade. For one thing, Alphad. > had a quality image that Intel doesn't have.  H Wrong argument. The Alpha engineering group has been sold to Intel. ThisH will not turn these engineers to craps because they receive their salary from a different employer.     D.   ------------------------------  # Date: Thu, 09 Aug 2001 18:23:29 GMTg= From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)dF Subject: Re: I just have to post this - and apoligse later Alpha/Intel0 Message-ID: <00A00467.52F8E47F@SendSpamHere.ORG>  g In article <6ffc7.720$Yx2.18248@news.cpqcorp.net>, "Sue Skonetski" <susan.skonetski@compaq.com> writes:e >Dear Newsgroup, >hL >Ok folks here goes.  For all the people that have sent me mail (flame mail)M >and posted responses about the death of Alpha  I am going to give a personaloG >opinion and ask a few questions and if you want to blast me go for it.. >nE >In all reasonableness did you think that the Alpha Chip was going to K >continue forever?  We upgraded from PDP's to VAXes to Alpha and now we are M >upgrading again.  Not only are we upgrading but we gave several years noticeoM >for your planning purposes.  VMS is committed to continue development on theeM >GS and the next Alpha system and to move onto the Intel platform.  We have aaI >number of engineers in VMS (around 400) and are hiring some more for theh >porting project.-  F I believe that the problem may be that you (Compaq) have used the wordG "upgrade" with nothing to backup and/or substantiate that moving to the G IPF is an upgrade.  Compaq's own web site hosted a paper discussing the G performance issues (comparison and contrast) of Alpha and IPF.  IPF, asn( I recall, was poo-pooed in this paper.    D There are inherent design and implementation flaws in IPF.  Why elseF would Intel seek to employ Alpha engineers and technologies?  They areE followers of the NIH philosophy so, in order to keep their "invented-pE here" ideals, they have to purchase the Alpha "Brain-Forest" from thec Q.     --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM-            -J   "And of course, I'm a genius, so people are naturally drawn to my fiery I   intellect.  Their admiration overwhelms their envy!" -- Calvin & Hobbes    ------------------------------  # Date: Thu, 09 Aug 2001 21:27:20 GMTa From: Dirk Munk <munk@home.nl>F Subject: Re: I just have to post this - and apoligse later Alpha/Intel' Message-ID: <3B730035.8E33A676@home.nl>-  	 Dear Sue,-  N No, we did not think the Alpha Chip was going to continue for ever. But CompaqN vice presidents (Bill Hell and Jesse Lipcon) gave us a solemn commitment to goL on with the Alpha chip only some 18 months ago, with road maps up till EV10.O Compaq broke that commitment to their customers to start with. And then look at P Compaq's marketing the last couple of years ? How much trouble was taken to tellM us, no to proof us that the new Alpha's are superior to Intel's Itanium ? And-L many specialist with a lot more knowledge about processor design than I haveP were of the same opinion. And now suddenly all that has changed, and the Itanium& is superior ? Please, give me a brake.  N And what is "The Alpha Chip" anyway ? A first generation Alpha differs as muchH from a EV7 as a Intel 8086 differs from a Itanium. Intel prefers to giveO different names to every new generation of processors, Digital/Compaq just gave 8 a new number to each generation but kept the name Alpha.  O I think if you would like to typecast the typical VMS enthusiast, then you willlJ see that he/she likes progress, and new developments. But at the same timeJ continuity and (very) high quality of hardware and software. And what doesM Compaq give us with this announcement ? We see a unproved chip design that is O years behind on schedule, with very poor integer performance. And it is made byeO Intel, notorious for its record for recalling processors and chip sets over theIM last five years or so. One of our Oracle engineers welcomed the Itanium move,eO because as he put it "At last we will get reliable Intel systems". That says itpP all, at least if his hope comes true. So many of us VMS die-hards are not at allO convinced that we will end up with a reliable high performance operating system-' on ditto hardware in a couple of years.s  P But what is even worse, from everything I have read since the move was announcedN I have conclude that Compaq even had not done a feasibility study to see if itM is possible to port VMS to Itanium. From that point of view the whole Itanium B move is just a big gamble. Not very encouraging either I'm afraid.  M And then there is the marketing. Compaq could and should have known that many-M Alpha/VMS/Tru64 enthusiasts would not welcome this move at all. By completelyAH ignoring this fact, and not even trying to show that this scepticism wasP anticipated, Compaq has made the impression not knowing what their customers (orJ their technical staff) feel and think about computer systems and operatingP systems. The flaming reactions are typical for very dedicated customers for whomN this announcement and Compaq's lack of sensitivity for their convictions was aJ smack in the face.  I've written it before, these feelings are almost of aO religious nature, and the problem is that Digital marketing or Compaq marketing  has never understood this.  O And another thing. Who do you think is buying your systems ? No, not the CEO or O vice-president who places the signature on the order form. You see, the obvious H choice for a Unix system is a HP or IBM or a Sun (right Andrew ?). TheseN companies have a good reputation with administrative and financial people. YouO know the saying "No one has ever been fired for buying a IBM?". Technical staffrK however may see the virtues of Tru64, and may convince management to go forw6 Compaq. At least that is how things are in my company.  J And do I need to go in to the problems with VMS ?  Never in the history ofP computing has a company been so effective in committing suicide as was done withH the negative marketing of VMS by Digital. My company had hundreds of VMSM systems, and in about a year so we may have 10 left. And today ? I still have O not seen a public VMS advertising campaign, not even a square inch. So how muchiO convincing do you think it takes today if I should try to get a new application)O on VMS ? I can tell you: it is absolutely impossible, no matter how much effortsK we make. In my company Digital gained a reputation of a unreliable supplierlP after it tried to drop VMS, and Compaq has inherited that reputation. I leave itJ to your imagination how the Itanium move and the way it was presented will contribute to this reputation.  M Sometimes you can find small messages like this in newsgroups "Wanted, a goodrP home for my PDP11 / MicroVax II " etc.  I can't imagine anyone placing a similarL message for a Wintel box. If and when your managers and marketing people areI capable of understanding why people formulate a message for a surplus old P fashioned computer system this way, maybe then they will understand a large part  of their customers a bit better.  L If you care to react on this message, please don't use the word "commitment"1 anymore. Somehow I've grown to be allergic to it.r  J And please don't take this rather angry reaction personally. I think I canA safely say we all love the way you contribute to this news group.   
 Kind regards,   	 Dirk Munk/                   Sue Skonetski wrote:   > Dear Newsgroup,1 >aM > Ok folks here goes.  For all the people that have sent me mail (flame mail)>N > and posted responses about the death of Alpha  I am going to give a personalH > opinion and ask a few questions and if you want to blast me go for it. >>F > In all reasonableness did you think that the Alpha Chip was going toL > continue forever?  We upgraded from PDP's to VAXes to Alpha and now we areN > upgrading again.  Not only are we upgrading but we gave several years noticeN > for your planning purposes.  VMS is committed to continue development on theN > GS and the next Alpha system and to move onto the Intel platform.  We have aJ > number of engineers in VMS (around 400) and are hiring some more for the > porting project. >4L > We still have customers that are being supported using PDP's and VAXes whoF > will continue to have their systems supported. Alpha systems will beL > supported into the next decade and longer under support contracts.  Please9 > tell me where else you can get this kind of commitment.a >o > So from my opinion >  >     We are porting VMSD >     And in case you did not know majority of the worlds major chip > manufacturers use VMS 4 >     Alpha Systems will be supported for many years: >     Compaq gave plenty of lead time vs. a 9 month windowM >     This was not a Compaq (Houston) directive but a technical decision madei# > by Alpha engineers that you know.t? >     Engineering is more excited than they have been in years.iL >     I think that this will give VMS exposure in markets where we could not" > go and a good business decision., >     There is plenty of work for all of us. >c$ > Folks what is the real issue here? >o > Sue4   ------------------------------  $ Date: Thu, 9 Aug 2001 16:53:15 -05001 From: "Virginia Metze" <metze@ginny.mrl.uiuc.edu>hF Subject: RE: I just have to post this - and apoligse later Alpha/IntelC Message-ID: <HIEPJKCHFKLJEAJDMOEFIEFGCGAA.metze@ginny.mrl.uiuc.edu>e  B To add to these woes I am not even able to get a price on extended@ warranty.  They want the inventory numbers (on the bottom of theD machine) before they can price maintenance or give extended warranty PRICING.  D I am getting extremely poor response to anything you want to name asF far as sales/maintenance staff is concerned.  If I call the 800 numberG and am lucky enough to get someone who knows us here, then all is well,o but otherwise....a  C Software support for Digital UNIX is still okay.  But I will not bet2 updating my VMS systems after the end of the year.  H I wish the two original partners would get together (Gordon Bell and Ken  Olson) and re-establish Digital.  K Of course Digital has only themselves to blame.  Their sales force believed = it was easier to sell UNIX than VMS and were our worst enemy.t     > -----Original Message-----' > From: Dirk Munk [mailto:munk@home.nl]l) > Sent: Thursday, August 09, 2001 4:27 PMr > To: Info-VAX@Mvb.Saic.ComtH > Subject: Re: I just have to post this - and apoligse later Alpha/Intel >  >i > Dear Sue,  >o? > No, we did not think the Alpha Chip was going to continue forg > ever. But Compaq? > vice presidents (Bill Hell and Jesse Lipcon) gave us a solemn> > commitment to goC > on with the Alpha chip only some 18 months ago, with road maps upd > till EV10.@ > Compaq broke that commitment to their customers to start with. > And then look at@ > Compaq's marketing the last couple of years ? How much trouble > was taken to tell>A > us, no to proof us that the new Alpha's are superior to Intel'su > Itanium ? AndnB > many specialist with a lot more knowledge about processor design
 > than I haveeB > were of the same opinion. And now suddenly all that has changed, > and the Itanium>( > is superior ? Please, give me a brake. > @ > And what is "The Alpha Chip" anyway ? A first generation Alpha > differs as much>J > from a EV7 as a Intel 8086 differs from a Itanium. Intel prefers to give8 > different names to every new generation of processors, > Digital/Compaq just gave: > a new number to each generation but kept the name Alpha. > C > I think if you would like to typecast the typical VMS enthusiast,t > then you willlL > see that he/she likes progress, and new developments. But at the same timeL > continuity and (very) high quality of hardware and software. And what does@ > Compaq give us with this announcement ? We see a unproved chip > design that isC > years behind on schedule, with very poor integer performance. Andq > it is made bytC > Intel, notorious for its record for recalling processors and chipo > sets over the A > last five years or so. One of our Oracle engineers welcomed thec > Itanium move,t: > because as he put it "At last we will get reliable Intel > systems". That says itC > all, at least if his hope comes true. So many of us VMS die-hardst > are not at all@ > convinced that we will end up with a reliable high performance > operating system) > on ditto hardware in a couple of years.  >t? > But what is even worse, from everything I have read since the  > move was announcedC > I have conclude that Compaq even had not done a feasibility study  > to see if itA > is possible to port VMS to Itanium. From that point of view thec > whole Itanium0D > move is just a big gamble. Not very encouraging either I'm afraid. >a? > And then there is the marketing. Compaq could and should haveg > known that manylA > Alpha/VMS/Tru64 enthusiasts would not welcome this move at all.  > By completely J > ignoring this fact, and not even trying to show that this scepticism was> > anticipated, Compaq has made the impression not knowing what > their customers (or.L > their technical staff) feel and think about computer systems and operating? > systems. The flaming reactions are typical for very dedicateda > customers for whom> > this announcement and Compaq's lack of sensitivity for their > convictions was a(L > smack in the face.  I've written it before, these feelings are almost of a@ > religious nature, and the problem is that Digital marketing or > Compaq marketing > has never understood this. >eB > And another thing. Who do you think is buying your systems ? No, > not the CEO or@ > vice-president who places the signature on the order form. You > see, the obviousJ > choice for a Unix system is a HP or IBM or a Sun (right Andrew ?). These: > companies have a good reputation with administrative and > financial people. YoueA > know the saying "No one has ever been fired for buying a IBM?".a > Technical staffsC > however may see the virtues of Tru64, and may convince management  > to go for18 > Compaq. At least that is how things are in my company. >cL > And do I need to go in to the problems with VMS ?  Never in the history ofA > computing has a company been so effective in committing suicide: > as was done withJ > the negative marketing of VMS by Digital. My company had hundreds of VMSB > systems, and in about a year so we may have 10 left. And today ? > I still have? > not seen a public VMS advertising campaign, not even a squareo > inch. So how muchhA > convincing do you think it takes today if I should try to get aa > new applicationpA > on VMS ? I can tell you: it is absolutely impossible, no matter  > how much efforts9 > we make. In my company Digital gained a reputation of aa > unreliable supplierl; > after it tried to drop VMS, and Compaq has inherited thatt > reputation. I leave itL > to your imagination how the Itanium move and the way it was presented will  > contribute to this reputation. >n? > Sometimes you can find small messages like this in newsgroupst > "Wanted, a goodR@ > home for my PDP11 / MicroVax II " etc.  I can't imagine anyone > placing a similar C > message for a Wintel box. If and when your managers and marketing  > people areK > capable of understanding why people formulate a message for a surplus old : > fashioned computer system this way, maybe then they will > understand a large part " > of their customers a bit better. >2A > If you care to react on this message, please don't use the wordb > "commitment"3 > anymore. Somehow I've grown to be allergic to it.o >iL > And please don't take this rather angry reaction personally. I think I canC > safely say we all love the way you contribute to this news group.- >- > Kind regards,- >- > Dirk Munk  >r >d >  >e >h >o >, >a >e > Sue Skonetski wrote: >, > > Dear Newsgroup,i > > B > > Ok folks here goes.  For all the people that have sent me mail > (flame mail)@ > > and posted responses about the death of Alpha  I am going to > give a personal J > > opinion and ask a few questions and if you want to blast me go for it. > > H > > In all reasonableness did you think that the Alpha Chip was going toC > > continue forever?  We upgraded from PDP's to VAXes to Alpha andt > now we areC > > upgrading again.  Not only are we upgrading but we gave severalh > years notice= > > for your planning purposes.  VMS is committed to continues > development on the; > > GS and the next Alpha system and to move onto the Inteld > platform.  We have aL > > number of engineers in VMS (around 400) and are hiring some more for the > > porting project. > >R@ > > We still have customers that are being supported using PDP's > and VAXes wholH > > will continue to have their systems supported. Alpha systems will be; > > supported into the next decade and longer under supportn > contracts.  Please; > > tell me where else you can get this kind of commitment.g > >  > > So from my opinion > >s > >     We are porting VMSF > >     And in case you did not know majority of the worlds major chip > > manufacturers use VMSw6 > >     Alpha Systems will be supported for many years< > >     Compaq gave plenty of lead time vs. a 9 month windowA > >     This was not a Compaq (Houston) directive but a technicalp > decision made % > > by Alpha engineers that you know.gA > >     Engineering is more excited than they have been in years.eA > >     I think that this will give VMS exposure in markets wheree > we could not$ > > go and a good business decision.. > >     There is plenty of work for all of us. > >a& > > Folks what is the real issue here? > >o > > Sue  >e   ------------------------------  % Date: Thu, 09 Aug 2001 22:21:50 -0400e) From: John Johnstone <jj_usenet@mail.com>eF Subject: Re: I just have to post this - and apoligse later Alpha/Intel( Message-ID: <3B730CFE.4B2BE8D5@mail.com>  K My hat's off to you, Dirk, for an extremely well written reply.  Although I C don't agree with you 100%, in one post you've managed to succinctlysC summarize more than a month's worth of this newsgroup's commentary.c     Dirk Munk wrote: >l > Dear Sue,N > P > No, we did not think the Alpha Chip was going to continue for ever. But CompaqP > vice presidents (Bill Hell and Jesse Lipcon) gave us a solemn commitment to goN > on with the Alpha chip only some 18 months ago, with road maps up till EV10.Q > Compaq broke that commitment to their customers to start with. And then look atdR > Compaq's marketing the last couple of years ? How much trouble was taken to tellO > us, no to proof us that the new Alpha's are superior to Intel's Itanium ? AndcN > many specialist with a lot more knowledge about processor design than I haveR > were of the same opinion. And now suddenly all that has changed, and the Itanium( > is superior ? Please, give me a brake. > P > And what is "The Alpha Chip" anyway ? A first generation Alpha differs as muchJ > from a EV7 as a Intel 8086 differs from a Itanium. Intel prefers to giveQ > different names to every new generation of processors, Digital/Compaq just gaves: > a new number to each generation but kept the name Alpha. > Q > I think if you would like to typecast the typical VMS enthusiast, then you will L > see that he/she likes progress, and new developments. But at the same timeL > continuity and (very) high quality of hardware and software. And what doesO > Compaq give us with this announcement ? We see a unproved chip design that isaQ > years behind on schedule, with very poor integer performance. And it is made bysQ > Intel, notorious for its record for recalling processors and chip sets over thepO > last five years or so. One of our Oracle engineers welcomed the Itanium move,eQ > because as he put it "At last we will get reliable Intel systems". That says ithR > all, at least if his hope comes true. So many of us VMS die-hards are not at allQ > convinced that we will end up with a reliable high performance operating systemo) > on ditto hardware in a couple of years.e > R > But what is even worse, from everything I have read since the move was announcedP > I have conclude that Compaq even had not done a feasibility study to see if itO > is possible to port VMS to Itanium. From that point of view the whole ItaniumlD > move is just a big gamble. Not very encouraging either I'm afraid. > O > And then there is the marketing. Compaq could and should have known that manyfO > Alpha/VMS/Tru64 enthusiasts would not welcome this move at all. By completelyiJ > ignoring this fact, and not even trying to show that this scepticism wasR > anticipated, Compaq has made the impression not knowing what their customers (orL > their technical staff) feel and think about computer systems and operatingR > systems. The flaming reactions are typical for very dedicated customers for whomP > this announcement and Compaq's lack of sensitivity for their convictions was aL > smack in the face.  I've written it before, these feelings are almost of aQ > religious nature, and the problem is that Digital marketing or Compaq marketinga > has never understood this. > Q > And another thing. Who do you think is buying your systems ? No, not the CEO ortQ > vice-president who places the signature on the order form. You see, the obviousaJ > choice for a Unix system is a HP or IBM or a Sun (right Andrew ?). TheseP > companies have a good reputation with administrative and financial people. YouQ > know the saying "No one has ever been fired for buying a IBM?". Technical staffmM > however may see the virtues of Tru64, and may convince management to go for 8 > Compaq. At least that is how things are in my company. > L > And do I need to go in to the problems with VMS ?  Never in the history ofR > computing has a company been so effective in committing suicide as was done withJ > the negative marketing of VMS by Digital. My company had hundreds of VMSO > systems, and in about a year so we may have 10 left. And today ? I still havenQ > not seen a public VMS advertising campaign, not even a square inch. So how muchtQ > convincing do you think it takes today if I should try to get a new applicationtQ > on VMS ? I can tell you: it is absolutely impossible, no matter how much effortrM > we make. In my company Digital gained a reputation of a unreliable suppliercR > after it tried to drop VMS, and Compaq has inherited that reputation. I leave itL > to your imagination how the Itanium move and the way it was presented will  > contribute to this reputation. > O > Sometimes you can find small messages like this in newsgroups "Wanted, a good R > home for my PDP11 / MicroVax II " etc.  I can't imagine anyone placing a similarN > message for a Wintel box. If and when your managers and marketing people areK > capable of understanding why people formulate a message for a surplus oldVR > fashioned computer system this way, maybe then they will understand a large part" > of their customers a bit better. > N > If you care to react on this message, please don't use the word "commitment"3 > anymore. Somehow I've grown to be allergic to it.m > L > And please don't take this rather angry reaction personally. I think I canC > safely say we all love the way you contribute to this news group.a >  > Kind regards,g >  > Dirk Munkl   ------------------------------  % Date: Thu, 09 Aug 2001 21:39:38 -0500 1 From: "David J. Dachtera" <djesys.nospam@fsi.net>sF Subject: Re: I just have to post this - and apoligse later Alpha/Intel' Message-ID: <3B73496A.614CDC07@fsi.net>m   Hi, Sue,  $ Please don't take this personally...  > Let me add my voice to the viturally unanimous condemnation...   Sue Skonetski wrote: >  > Dear Newsgroup,o > M > Ok folks here goes.  For all the people that have sent me mail (flame mail) N > and posted responses about the death of Alpha  I am going to give a personalH > opinion and ask a few questions and if you want to blast me go for it. > F > In all reasonableness did you think that the Alpha Chip was going to > continue forever?   G We didn't expect PDP or VAX to live forever, either. When announced, weiC expected VAX to replace PDP, and Alpha to replace VAX. We did *NOT*tE expect, nor did Digital do it, that the "rug would be pulled out fromuE under" PDP in favor of VAX nor VAX in favor of Alpha. The transitionsoE were smooth, well coordinated and executed admirably, though probablya6 not "perfectly", whatever that may mean to the reader.  H As many posters have stated repeatedly, *WHAT* was said is not the heartE of the issue, though it is certainly germane. *HOW* it was done bearsg the brunt of the main assault.  E Some of us, "the OpenVMS faithful" if you will, have been burning the H candle in the middle and at both ends trying to keep alive those few VMSF sites we can manage to maintain. The *WAY* Compaq announced it is whatA killed us - literally pulled the rug out from under us. (PerversenE insight tells me that is EXACTLY what some at Compaq wanted to hear.)lG Faced with Compaq announcements and press releases in their hands, none F of us had a leg to stand on in conferences with our now former OpenVMS clients.  F *THAT* is why many of us are "mad as hell, and we're not going to take this anymore!".r  6 It's not *WHAT* was said, rather *HOW* Compaq said it.  9 > We upgraded from PDP's to VAXes to Alpha and now we are  > upgrading again.  C As Andrew Harrison might point out, that is opinion and conjecture.kE There is no concrete evidence to support the claim that IPF is in any-E way superior to Alpha, since IPF is still in prototype, beta test andeB "early adoption" while Alpha has been in the market place for many years.  = >  Not only are we upgrading but we gave several years noticee > for your planning purposes.a  E Unfortunately, that's not how "the market" read it. Witness: the many H "death of Alpha" articles in recent trade rags, both on-line and in hard copy.p  2 >  VMS is committed to continue development on theC > GS and the next Alpha system and to move onto the Intel platform.s  F Had Compaq said that, and little more, we would not be conducting this thread right now.    >  We have aJ > number of engineers in VMS (around 400) and are hiring some more for the > porting project.  ) Need a senior SysAdmin in there anywhere?    L > We still have customers that are being supported using PDP's and VAXes whoF > will continue to have their systems supported. Alpha systems will beL > supported into the next decade and longer under support contracts.  Please9 > tell me where else you can get this kind of commitment.t  D Given recent history, "commitment" is now a matter of record, rather than claim.    > So from my opinion >  >     We are porting VMSD >     And in case you did not know majority of the worlds major chip > manufacturers use VMS 4 >     Alpha Systems will be supported for many years: >     Compaq gave plenty of lead time vs. a 9 month windowM >     This was not a Compaq (Houston) directive but a technical decision madew# > by Alpha engineers that you know.s? >     Engineering is more excited than they have been in years.tL >     I think that this will give VMS exposure in markets where we could not" > go and a good business decision.  , >     There is plenty of work for all of us.D ...at Compaq. The rest of us out here are starving to death. I can'tE begin to calculate how many hundreds of billions of lost dollars that " represents for Compaq and OpenVMS.  $ > Folks what is the real issue here?  G I hope I've covered that as non-confrontationally as is possible in then
 circumstance.A  F I won't be able to make the upcoming, "Compaq Listens" (sort of) panel0 at CETS-2001, so I'll enter my question(s) here:  D With regard to the recent announcements from Compaq and the market's subsequent responses to them:    A: Has anyone been fired yet?    B: If not, why not?.  H C: What is Compaq doing to quell the global talk of the "death of Alpha"H and try to salvage what little is left of the OpenVMS and Alpha markets?   -- t David J. Dachterat dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/e   ------------------------------  # Date: Fri, 10 Aug 2001 02:42:20 GMT $ From: Scott Vieth <svieth@wi.rr.com>F Subject: Re: I just have to post this - and apoligse later Alpha/Intel( Message-ID: <3B734AC1.8A8D43E@wi.rr.com>   Sue:  O It takes big cajones to step up and face the flame-blasters head-on.  I applaud 
 your bravery.w  N The move from Alpha to IPF is being driven by the market.  Yeah, we'd all likeO to have new Alpha chips coming out until we die but that isn't going to happen.eM Money makes the world turn and if Compaq needs to stop pouring bucks into the 2 Alpha line in order to stay afloat, then so be it.  M The world survived the migrations that you mentioned.  We'll also survive the  migration from Alpha to IPF.  P With the Alpha engineers working on the future IPF chips, the IPF CPUs be better than anything we have today.  L For those folks who want a "lifetime support guarantee" on VMS:  VMS will beK alive only as long as it continues to make money for Compaq.  When it stops P turning a profit, it'll be left by the side of the road.  VMS is not a religion,K it is simply a high-quality piece of software.  These are the same rules incO effect at any other tech company:  if it makes money, great.  If not, put it toh sleep.  N Read the Wallstreet Journal, watch CNBC, call your broker to check on the sizeM of your portfolio:  Times are tough right now and companies are doing what ittP takes to stay alive.  If Compaq needs to kill the Alpha chip to stay alive, thenM they need to kill the Alpha chip.  At least they found a great way to utilizesF the collection of chip-building knowledge as well as a high to deliver- higher-performance VMS systems in the future.e  
 -Scott :^)   Sue Skonetski wrote:   > Dear Newsgroup,b >nM > Ok folks here goes.  For all the people that have sent me mail (flame mail)rN > and posted responses about the death of Alpha  I am going to give a personalH > opinion and ask a few questions and if you want to blast me go for it. >wF > In all reasonableness did you think that the Alpha Chip was going toL > continue forever?  We upgraded from PDP's to VAXes to Alpha and now we areN > upgrading again.  Not only are we upgrading but we gave several years noticeN > for your planning purposes.  VMS is committed to continue development on theN > GS and the next Alpha system and to move onto the Intel platform.  We have aJ > number of engineers in VMS (around 400) and are hiring some more for the > porting project. >tL > We still have customers that are being supported using PDP's and VAXes whoF > will continue to have their systems supported. Alpha systems will beL > supported into the next decade and longer under support contracts.  Please9 > tell me where else you can get this kind of commitment.c >o > So from my opinion >  >     We are porting VMSD >     And in case you did not know majority of the worlds major chip > manufacturers use VMS 4 >     Alpha Systems will be supported for many years: >     Compaq gave plenty of lead time vs. a 9 month windowM >     This was not a Compaq (Houston) directive but a technical decision made # > by Alpha engineers that you know. ? >     Engineering is more excited than they have been in years. L >     I think that this will give VMS exposure in markets where we could not" > go and a good business decision., >     There is plenty of work for all of us. >n$ > Folks what is the real issue here? >u > Suen   ------------------------------  $ Date: Thu, 9 Aug 2001 13:35:19 -0400' From: "Bill Todd" <billtodd@foo.mv.com> F Subject: Re: I just have to post this - and apoligse later Alpha/Intel( Message-ID: <9kuhkt$3fl$1@pyrite.mv.net>  = "Sue Skonetski" <susan.skonetski@compaq.com> wrote in messagew, news:6ffc7.720$Yx2.18248@news.cpqcorp.net... > Dear Newsgroup,  >rG > Ok folks here goes.  For all the people that have sent me mail (flameu mail)bE > and posted responses about the death of Alpha  I am going to give ad personalH > opinion and ask a few questions and if you want to blast me go for it. > F > In all reasonableness did you think that the Alpha Chip was going to > continue forever?t  L Not at all:  we just expected it to last approximately as long as Compaq hadL *committed* (over and over and over, in writing and verbally, and continuing5 right up to the week before June 25th) that it would.i  9   We upgraded from PDP's to VAXes to Alpha and now we are  > upgrading again.  K No, we are not:  IA64 is by any objective assessment a downgrade, and thereeK is thus absolutely no comparison to the other migrations you mention (whichcJ *were* actual upgrades).  I'm disappointed to see such conventional Compaq# bullshit emanating from your mouth.e   ...   H >     This was not a Compaq (Houston) directive but a technical decision made# > by Alpha engineers that you know.   D By all indications from the Alpha engineering group, the above is an
 outright lie.h   ...i  $ > Folks what is the real issue here?  A I've mentioned some of them above, and hardly for the first time.o- Apparently you haven't been paying attention.n   - bill   >o > Suet   ------------------------------  % Date: Thu, 09 Aug 2001 23:16:21 -0400 2 From: rdeininger@mindspring.com (Robert Deininger)F Subject: Re: I just have to post this - and apoligse later Alpha/IntelL Message-ID: <rdeininger-0908012316220001@user-2ivecii.dialup.mindspring.com>  ; In article <3B73496A.614CDC07@fsi.net>, "David J. Dachtera"u <djesys.nospam@fsi.net> wrote:      4 > >  VMS is committed to continue development on theE > > GS and the next Alpha system and to move onto the Intel platform.t > H > Had Compaq said that, and little more, we would not be conducting this > thread right now.   G But Compaq DID say that, I believe on the day of the big announcement.   Perhaps the next day.    --   Robert Deininger rdeininger@mindspring.come   ------------------------------  % Date: Fri, 10 Aug 2001 01:04:33 -0400m' From: "Bill Todd" <billtodd@foo.mv.com> F Subject: Re: I just have to post this - and apoligse later Alpha/Intel( Message-ID: <9kvq1b$5pc$1@pyrite.mv.net>  1 "Scott Vieth" <svieth@wi.rr.com> wrote in message " news:3B734AC1.8A8D43E@wi.rr.com...   ...o  ; > The move from Alpha to IPF is being driven by the market.r  L Really?  As far as one can tell, there is zero market so far for IPF, and inK at least some foreseeable futures there will *never* be that great a marketiE for IPF, so the assertion that this move was market-driven is absurd.   J You could assert that the move was driven by Compaq's *perception* of whatK *future* markets will be like, I suppose.  But for a move this drastic (andkI unpopular), there's a good case to be made that Compaq should have waitedtI until IA64 had at least *started* to prove its worth (not only to Compaq,eH but to the customers who need to be able to believe that this move is in their interests).      Yeah, we'd all likeoI > to have new Alpha chips coming out until we die but that isn't going too happen.eK > Money makes the world turn and if Compaq needs to stop pouring bucks intoa theA4 > Alpha line in order to stay afloat, then so be it.  L Except that every indication from Compaq's own revenue and profit numbers isH that Compaq did *not* need to stop funding Alpha, and that in fact AlphaJ gave Compaq a better return on its investment than any other business thatL Compaq is involved in (save for Tandem, which likely gives a comparable rateK of return but much smaller total return).  Some might observe that Compaq'saJ services arm also generates comparable profit levels, but it remains to be: seen how much this will be affected by the Alpha decision.   >dK > The world survived the migrations that you mentioned.  We'll also survive, ther > migration from Alpha to IPF.  J The question is how many will survive as Compaq customers rather than turn
 elsewhere.   >oK > With the Alpha engineers working on the future IPF chips, the IPF CPUs beI better > than anything we have today.  D Of course they will:  they would have been anyway, since the tide ofH technology lifts all boats, even the sluggish ones.  But it seems likely> that they won't be as good as the Alphas that could have been.   >tK > For those folks who want a "lifetime support guarantee" on VMS:  VMS will  beG > alive only as long as it continues to make money for Compaq.  When it  stopssH > turning a profit, it'll be left by the side of the road.  VMS is not a	 religion,uJ > it is simply a high-quality piece of software.  These are the same rules inK > effect at any other tech company:  if it makes money, great.  If not, putr it toh > sleep.  D If Compaq worked that way, Alpha would be its prime focus and its PCL business would have been dumped.  So your observation, whether worthwhile or/ not, is inapplicable to the current discussion.o  @ I guess Sue isn't the only one who hasn't been paying attention.   - bill   ------------------------------  % Date: Thu, 09 Aug 2001 13:52:11 -0400u* From: John Reagan <john.reagan@compaq.com>' Subject: Re: Linker-Warnings in VMS 7.3i' Message-ID: <3B72CDCB.50201@compaq.com>w  = > On 9 Aug 2001 06:44:15 -0700, lzoedv@cretschmar-logistik.deu > (M.Eismann&W.Richard) wrote: >  >  >>Hello to all OpenVMS-Friends!  >>R >>After we had upgraded from OpenVMS V7.1-1H1 to V7.3 on a Test-Alphaserver we hadI >>compiled our applications without any errors! But now (after successfuldD >>compilation) we get link-warnings with unresolved message-numbers:( >>%LINK-W-NOMSG, Message number 0064A120( >>%LINK-W-NOMSG, Message number 0064A128( >>%LINK-W-NOMSG, Message number 0064A130( >>%LINK-W-NOMSG, Message number 0064A128 >>0 >>Before above upgrade no link-warnings occured! >>% >>An analyze/image of link.exe shows:g) >>       Image Identification Informations >># >>               image name: "LINK" 4 >>               image file identification: "A12-03"C >>               image file build identification: "X913-0060000000"i8 >>               link date/time: 22-MAR-2001 12:52:30.000 >>               linker identification: "A11-50" >>& >>Does anybody have an idea or a hint? >> >>greetingsd >>martin eismann,  >>cretschmar logistik gmbh >>duesseldorf, germany >> >     A Do you have Pascal modules in your application?  I'll bet you do.h  B Before V7.3, when the linker was trying to produce ENTIDENT check E messages, the message would wrap and become truncated.  A change was aG made to the linker to print the message in pieces to avoid any loss of d information.  G It seems that the linker cannot find the messages in the message file.  < Perhaps there is something wrong with the V7.3 installation?  E As for getting the link warnings now when you didn't get them in the iF past, perhaps the linker edit was done wrong?  (I did a review of the A link change made by the engineer working on the linker.  Perhaps   something went wrong there.m  F I'll check things at this end, but can you do me a favor.  Can you do B ANALYZE/OBJECT on the .OBJ files and send me any GSD$_IDC records I contained inside any .OBJ file?  The linker processes and compares those aH records during a LINK to produce the message it was trying to print (if " it could find the right messages).   John Reaganw Compaq Pascal Project Leader john.reagan@compaq.com   ------------------------------  % Date: Thu, 09 Aug 2001 10:16:57 -0400o5 From: David Beatty <David.Beatty@qwertysasasdfgh.com>i' Subject: Re: Linker-Warnings in VMS 7.3-2 Message-ID: <y5pyO6RALQZDCsspsnxNHUuwP9L3@4ax.com>  8 There is a linker patch for VMS V7.3 (VMS73_LINKER) that+ you might want to install.  David R. Beatty   ; On 9 Aug 2001 06:44:15 -0700, lzoedv@cretschmar-logistik.def (M.Eismann&W.Richard) wrote:   >Hello to all OpenVMS-Friends! > Q >After we had upgraded from OpenVMS V7.1-1H1 to V7.3 on a Test-Alphaserver we had H >compiled our applications without any errors! But now (after successfulC >compilation) we get link-warnings with unresolved message-numbers:a' >%LINK-W-NOMSG, Message number 0064A120l' >%LINK-W-NOMSG, Message number 0064A128f' >%LINK-W-NOMSG, Message number 0064A130n' >%LINK-W-NOMSG, Message number 0064A128e >p/ >Before above upgrade no link-warnings occured!d >'$ >An analyze/image of link.exe shows:) >        Image Identification Information  >l# >                image name: "LINK" 4 >                image file identification: "A12-03"C >                image file build identification: "X913-0060000000"a8 >                link date/time: 22-MAR-2001 12:52:30.000 >                linker identification: "A11-50" >r% >Does anybody have an idea or a hint?r >e
 >greetings >martin eismann, >cretschmar logistik gmbhs >duesseldorf, germanyf   ------------------------------  % Date: Fri, 10 Aug 2001 14:15:02 +1000r6 From: "Arena, Steve" <Steve.Arena@pacificpower.com.au># Subject: RE: Microsoft and Code red Q Message-ID: <D750FFBD4936D111842000805F15EFA4043A87A9@meppb1.pacificpower.com.au>e   > RE: Blame the customersT >  > In my humble opinion:i > K > Those of us who come from a VMS background would expect that Windows 2000hL > Server would be "secure" when first installed, ( special features excludedH > ). In fact you might even be tempted to buy W2S rather than another MSK > "Operating Systems" for this reason even if you don't particularly need a*L > server. This is not the case, W2S is not secure when first installed.  AndK > unlike NT4 there doesn't seem to be a checklist to follow to shut all thee4 > open doors - well I haven't been able to find one! > G > On top of this MS sends you "special feature" notices every couple ofc > days,hK > suggesting that for your own good and for the good of the wider communityeH > you should tamper with your system (which you now think may be working1 > reliably at the moment) by installing a patch.   > F > Back in the 1950's and 60's safety features didn't sell cars. In the	 > presentoK > day IT security features are treated the same way. It's an optional extra I > that users and admins  must actively search out, install and maintain -- > it's not easy. o >  >  > 	 > Regardst > Steve  >  >  >  > > -----Original Message-----D > > From:	Mark (un-MASK) Forsyth [SMTP:forsyMhm@optusAhome.coSm.aKu]( > > Sent:	Wednesday, 8 August 2001 20:07 > > To:	Info-VAX@Mvb.Saic.Com ' > > Subject:	Re: Microsoft and Code redn > >  > > D > > "Doc.Cypher" <doc_cypher@redneck.gacracker.org> wrote in message3 > > news:20010807155208.5938.qmail@gacracker.org...v( > > > -----BEGIN PGP SIGNED MESSAGE----- > > >aI > > > On Mon, 06 Aug 2001, JF Mezei <jfmezei.spamnot@videotron.ca> wrote:s > > >e > > > [SNIP] > > >eK > > > >Could this be the achile's heel that starts to bring down Microsoft,e > or > > willL > > > >corporations ignore this major flaw and continue to blindly bet their > > business > > > >on Microsoft stuff ?  > > > >nI > > > >What will it take for corporations to wake up from their Microsoft J > > > >trans/brainwashing and realise that they shouldn't be betting their > > business > > > >on MS software ?p > > > K > > > In the case of the Code Red worm, the fault could be said to lie withnG > > > customers. This is because M$ had issued a patch for the expoit a  > month  > > orE > > > two ago. Of course, you can always blame M$ for failing to haveh
 > adequateI > > > quality management and testing of their product in the first place.d > >  > > ? > > Yes. You can also get well and truly stuck into 'em about ae > vulnerability J > > that allows complete access that they were told about in June 1999 and > yet 4 > > did nothing about until about a month or so ago. > > 	 > > Oorooi
 > > Mark F...e > >  > >  > > >v > > >e
 > > > Doc.
 > > > - --< > > > The bigger the humbug, the better people will like it. > > > ~ Phineas Taylor Barnum. > > http://vmsbox.cjb.net  > > >-# > > > -----BEGIN PGP SIGNATURE-----r > > > Version: 2.6.2 > > >nF > > > iQEVAwUBO28hcsriC3SGiziTAQFeWAf9Gdo8nogeU54IEoALm0sbp/Egq41B8WvEF > > > iKvnCJxr9OU1q7kApQnxoJJOyGq+ZKAGSye29tr+EtXZse8oS7xJ1EtQMxs8kuPeF > > > EtUqQKiG4rVGAIuuZRKssTBRGhCequPD8gWx5ZqKVZ14nHct8bFVRkcMKcU3ZGKTF > > > JyivZxSjkMdwTe9Gc6G9Nb5r/EhsnoC0Ja2GRo5w/pkCJcBK9qp7Pfs9s8a8qHqIF > > > zbTpEFrRhpZ+a02V7wU3Cs+UkeIk3E1QuDgpMh/kns7C++I7ywqlWCMoiMmlxk8x> > > > pJOBUveIq5TOQ23/enc1ewcKkeiqqfycRIkuOT6xbwALck/uUIZyfA== > > > =1uuG-! > > > -----END PGP SIGNATURE-----e > > >1 > >    ------------------------------  + Date: Fri, 10 Aug 2001 02:24:43 +0000 (UTC)e  From: mustang@ucc.asn.au.invalid Subject: Re: Microsoft and CR4* Message-ID: <9kvglb$k1i$1@enyo.uwa.edu.au>  & paddy.o'brien@zzz.tg.nsw.gov.au wrote:M : Shi(r)t (there is no other word!!! -- but I thought I should write it like e : that.)  D : I sent the following as part of the thread that writes CR in full.   [snip]  6 : I get back from our own new wonderful virus rubbish:  F :>From:	TGMAIL::IN%"MAILsweeper@tg.nsw.gov.au"  9-AUG-2001 18:44:55.91% :>To:	IN%"obrien@gecko.tg.nsw.gov.au"  :>CC:	M :>Subj:	RE:Re: Microsoft and C* r* Trapped [Thought I should change that too]o :>P :>The above mesage has been trapped by the Transgrid virus scanner as contaning 2 :>a possible virus.  Please contact the recipient.  G Paddy - tell the guys. They're probably using Trend Interscan Viruswalle or something on an NT box.I Ask them WTF Mickeysoft is a sensitive word, as far as "corporate policy" 
 is concerned.s  B If its too painful, unsubscribe from Info-VAX and read comp.os.vms
 instead...   Cheers /dave    -- e! I don't get mad.... I get stabby.h   ------------------------------  % Date: Thu, 09 Aug 2001 22:14:30 +0100e1 From: Steve Reece <SYSTEM@ipl.demon.co.nospam.uk>o/ Subject: Re: Migrating from CI to Fiber Channel 6 Message-ID: <3B730B46.42C6F851@ipl.demon.co.nospam.uk>  C Any idea when the relevant support might become available for writehG logging on HSG80s?  My boss is complaining that he wants to go for (and @ is migrating to) Fiberchannel disks but would still like to have< minimerge capabilities which are enabled with write logging.   Steve.   Hoff Hoffman wrote:r > l > In article <3B6F2543.7108003C@ipl.demon.co.nospam.uk>, Steve Reece <SYSTEM@ipl.demon.co.nospam.uk> writes:E > :My understanding is that there is not yet the capability for writes > :logging on HSG80s.  > J >   Correct.  Write logging involves both OpenVMS and controller firmware,L >   and the necessary supporting code is not yet available on Fibre Channel. > 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   --  G "A shadow fell over her face; clear, as if the composure were rent like E a veil.  And her lips parted, but only with a short intake of breath.nA Then she said, 'Well, then you are right.  Indeed, we are even.'"p% 		Louis, "Interview with the Vampire"n   ------------------------------   Date: 9 Aug 2001 17:49:35 -0500  From: rivie@localhost.no.domaino" Subject: Re: Missing TK50 in uVAX?6 Message-ID: <slrn9n659k.30h.rivie@localhost.no.domain>  I In article <m3pua4yi5l.fsf@muikku.baana.suomi.net>, Antti Jrvinen wrote:u5 > TK50Z has two connectors, which one should be used?d  D It doesn't matter. They're connected together by the internal cable.   > Should I connect i' > a terminator to the other connector?     Yes.  E > There is only 6 megabytes of memory installed, what kind of memory  / > fits? This thingie doesn't use SIMM -modules?    It uses custom memory boards.o  
 Roger Ivie ivie@cc.usu.edur    > -----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----A http://www.newsfeeds.com - The #1 Newsgroup Service in the World!,> -----==  Over 80,000 Newsgroups - 16 Different Servers! =-----   ------------------------------    Date: 10 Aug 2001 01:37:10 +0300& From: costello@iki.fi (Antti Jrvinen) Subject: Missing TK50 in uVAX?3 Message-ID: <m3pua4yi5l.fsf@muikku.baana.suomi.net>7  
 Dear Sirs,  4 quite a beast, if I may, says upon typing "test 50":   KA410-A V2.2 ID 08-00-2B-08-4B-06      CLK      0000.0001     NVR      0000.0001s  ? DZ       0000.4001o;       00004001 00000001 00000001 00000001 00000000 00000000     MEM      0006.0001u       00600000    MM       0000.0001a    FP       0000.0001o    IT       0000.0001C    HDC      7110.0001t        0004C437 0004C437 00000000  ? TPC      0000.4001tM       FFFFFF05 FFFFFF05 FFFFFF05 FFFFFF05 FFFFFF05 FFFFFF05 FFFFFF05 FFFFFF03r    SYS      0000.0001  ?? NI       0000.7004  V1.2e  F My interest here is tape controller, here marked with "? TPC". I have E a TK50Z in separate box, connected and powered up and if I understandsB corretly the controller doesn't see the tape or the controller mayG be dead or something? What does the "TPC 0000.4001" mean? The followingtB line presents the devices found, last one is the controller itselfJ (I did try changing the SCSI ID to 7, originally it was 0) but what should+ I do to make the controller find the drive?a  E TK50Z has two connectors, which one should be used? Should I connect l% a terminator to the other connector?    6 Disks are of RD54 kind, I think, what is the capacity?  C There is only 6 megabytes of memory installed, what kind of memory e- fits? This thingie doesn't use SIMM -modules?n   --   Antti Jrvinen, costello@iki.fi-5             "concerto for two faggots and orchestra" 0   ------------------------------   Date: 9 Aug 2001 14:00:39 -0400:/ From: jordan@lisa.gemair.com (Jordan Henderson)p Subject: Re: Move to Sun* Message-ID: <9kuj47$ti9$1@lisa.gemair.com>  O In article <9kp80l$4fe$1@pyrite.mv.net>, Bill Todd <billtodd@foo.mv.com> wrote:d >y6 >"Nic Clews" <sendspamhere@127.0.0.1> wrote in message$ >news:3B70159B.39B9475B@127.0.0.1... >> Jack Peacock wrote: >> >J >> > The customer, one of our largest (very large european multinational),I >> > has told us they want to keep our applications but do not want it onsE >> > VMS.  They have an IT policy, in place for several years now, toeM >> > eliminate all VMS based machines and applications.  Replacements are Sun-J >> > for critical servers and NT for web servers (non-critical informationM >> > kiosk type apps).  They are willing to pay substantial sums to implementl >> > their policy. >>J >> Obviously your client has not read the July Gartner report which placesI >> Sun in a weak position with respect to Compaq recent announcement with # >> server consolidation to Itanium.a >tI >Funny about those Gartner reports:  the people who ignored the ones that L >trashed VMS are considered to have been astute, so the suggestion that thisK >customer may be doing something foolish by ignoring their wisdom about Sun  >seems at least questionable.o >w  F Furthermore, didn't we hear here that Gartner pitched the idea to CPQ 3 that they ditch Alpha for IA-64 in the first place?u  B If this is true, it seems like a report like the one above is just" Gartner supporting their "wisdom".  D In any case, Sun has demonstrated a working Solaris on IA-64 over a E year ago.  If Sun does feel they are out on a limb that won't support D them, they'll be able to nimbly jump to a new limb quickly.  Unlike E Compaq, who decided to first cut off the limb they were currently on p' and then climb another tree altogether.A   >l >- billi >r >  >s   -Jordan Hendersone jordan@greenapple.comr   ------------------------------  $ Date: Thu, 9 Aug 2001 14:52:48 -0400' From: "Bill Todd" <billtodd@foo.mv.com>  Subject: Re: Move to Sun( Message-ID: <9kum67$7v2$1@pyrite.mv.net>  < "Jordan Henderson" <jordan@lisa.gemair.com> wrote in message$ news:9kuiol$t3n$1@lisa.gemair.com...- > In article <3B702E8C.9A94A5D8@caltech.edu>,S+ > David Mathog  <mathog@caltech.edu> wrote:mI > >                                                  Here's an example ofc thesL > >sorts of minor changes I've seen. The Solaris C compiler didn't like code > >that didu > >i > >char foo[100] > >v > >   function(&foo) > >A
 > >instead of  > >u > >   function (&foo[0]) > > K > >when the prototype for that parameter was char *, but other than that, In >sD > "didn't like"?  Recent DECC compilers complain about that as well. >nA > Both the Solaris C and the recent DECC compilers are correct toaB > complain.  They aren't equivalent.  The first is a pointer to anA > array of characters (char *[]) and the second is a pointer to as > character (char *).   F Er, IIRC the first is a pointer to a pointer to an array of charactersL (which I would normally write as char **, since I thought that C/C++ pointerG arithmetic resulted in a lack of differentiation between arrays and theaI elements in them when addresses were used - but things could have changedr* since I last studied this area in detail).   - bill   >h > >a > >Regards,k > >n > >David Mathogt > >mathog@caltech.edu. > >f >mK >**************************************************************************d > >*
 > >RIH Compaqo *u >bK >**************************************************************************i > >  > >u >  > -Jordan Hendersone > jordan@greenapple.comt >t >.   ------------------------------   Date: 9 Aug 2001 16:09:14 -04001/ From: jordan@lisa.gemair.com (Jordan Henderson)c Subject: Re: Move to Sun* Message-ID: <9kuqla$8hf$1@lisa.gemair.com>  O In article <9kum67$7v2$1@pyrite.mv.net>, Bill Todd <billtodd@foo.mv.com> wrote:t >d= >"Jordan Henderson" <jordan@lisa.gemair.com> wrote in messageV% >news:9kuiol$t3n$1@lisa.gemair.com...e. >> In article <3B702E8C.9A94A5D8@caltech.edu>,, >> David Mathog  <mathog@caltech.edu> wrote:J >> >                                                  Here's an example of >theM >> >sorts of minor changes I've seen. The Solaris C compiler didn't like codeN >> >that did >> > >> >char foo[100]L >> > >> >   function(&foo)0 >> > >> >instead of >> > >> >   function (&foo[0])> >> >L >> >when the prototype for that parameter was char *, but other than that, I >>E >> "didn't like"?  Recent DECC compilers complain about that as well.a >>B >> Both the Solaris C and the recent DECC compilers are correct toC >> complain.  They aren't equivalent.  The first is a pointer to an B >> array of characters (char *[]) and the second is a pointer to a >> character (char *). >nG >Er, IIRC the first is a pointer to a pointer to an array of characters M >(which I would normally write as char **, since I thought that C/C++ pointer H >arithmetic resulted in a lack of differentiation between arrays and theJ >elements in them when addresses were used - but things could have changed+ >since I last studied this area in detail).. >   ; You are wrong.  See question 6.12 in the C language FAQ at:   C 	ftp://rtfm.mit.edu/pub/usenet-by-hierarchy/comp/lang/c/C-FAQ-list/   C Also, you seem unclear on the subtle differences between arrays andoF pointers in C.  There is not a "lack of differentiation between arraysD and the elements in them when addresses...".  It is true that arraysG "decay" into pointers when passed to functions.  See questions 6.3 and i	 6.4 ibid.i   >- billa >  >> >> > >> >Regards, >> > >> >David Mathog >> >mathog@caltech.edu >> > >>L >>************************************************************************** >> >*o >> >RIH Compaq >* >>L >>************************************************************************** >> > >> > >> >> -Jordan Henderson >> jordan@greenapple.com >> >> >h >e   -Jordan Hendersona jordan@greenapple.comc   ------------------------------  # Date: Thu, 09 Aug 2001 22:55:49 GMTe  From: jlsue <jlsuexxxz@home.com> Subject: Re: Move to Sun8 Message-ID: <ifa3nt08v83q5a6q6dho5g682lc60qmldl@4ax.com>  D On Tue, 7 Aug 2001 13:20:03 -0400, "Bill Todd" <billtodd@foo.mv.com> wrote:     > I >Funny about those Gartner reports:  the people who ignored the ones that.L >trashed VMS are considered to have been astute, so the suggestion that thisK >customer may be doing something foolish by ignoring their wisdom about Sun  >seems at least questionable.t  A Yeah, I was thinking something like that.  I didn't respect theiroB reports before, I'm not going to start just because they're saying something I like to hear.s  9 That said, however, it is nice to see something positive.I   ------------------------------  # Date: Thu, 09 Aug 2001 22:55:48 GMTA  From: jlsue <jlsuexxxz@home.com> Subject: Re: Move to Sun8 Message-ID: <1ba3ntopk92s7dcb60gdkks18b3koe4sj7@4ax.com>  1 On Tue, 7 Aug 2001 07:51:43 -0700, "Jack Peacock"o <peacock@simconv.com> wrote:     >>H >Code is in C, with heavy use in libraries of RMS, SMG, LIB, LBR and VMSI >system calls.  RMS will be replaced with Oracle, the VMS calls are not a F >major problem, but I am concerned about the equivalents for SMG (appsI >are character cell based).  AIX had an Extended Curses library with mosteH >of the same functionality, I'm hoping Solaris has some equivalent.  WebB >based portion is all NT/IIS/Visual Studio with ODBC connection to( >Oracle, not an issue in the conversion.  < Forget screen calls, just re-do it in web format for browser
 interface.   ------------------------------  $ Date: Thu, 9 Aug 2001 19:58:38 -0400' From: "Bill Todd" <billtodd@foo.mv.com>n Subject: Re: Move to Sun( Message-ID: <9kv83l$mo7$1@pyrite.mv.net>  < "Jordan Henderson" <jordan@lisa.gemair.com> wrote in message$ news:9kuqla$8hf$1@lisa.gemair.com...J > In article <9kum67$7v2$1@pyrite.mv.net>, Bill Todd <billtodd@foo.mv.com> wrote:   ...e  I > >Er, IIRC the first is a pointer to a pointer to an array of charactersvG > >(which I would normally write as char **, since I thought that C/C++  pointer4J > >arithmetic resulted in a lack of differentiation between arrays and theL > >elements in them when addresses were used - but things could have changed- > >since I last studied this area in detail).a > >  >u= > You are wrong.  See question 6.12 in the C language FAQ at:o >nD > ftp://rtfm.mit.edu/pub/usenet-by-hierarchy/comp/lang/c/C-FAQ-list/ >rE > Also, you seem unclear on the subtle differences between arrays and H > pointers in C.  There is not a "lack of differentiation between arraysF > and the elements in them when addresses...".  It is true that arraysH > "decay" into pointers when passed to functions.  See questions 6.3 and > 6.4 ibid.s  L The array name (when unaccompanied by brackets) seems to be interpreted as aK pointer in almost all usage (which was what I based the above comment on) -KH with the conspicuous and (at least to me) strange exception of when it'sI operated upon by &.  I've never had occasion to use the construct &foo in<K association with an array foo[], but would have been inclined to guess that9D some construct like &foo[] would have been required to generate what apparently &foo in fact does.0  J But thanks for pointing out this gap in my acquaintance with the language.   - bill   ------------------------------  # Date: Fri, 10 Aug 2001 01:46:24 GMT * From: cjt & trefoil <cheljuba@prodigy.net> Subject: Re: Move to Sun+ Message-ID: <3B733D4A.BDCD7DBB@prodigy.net>   < What's a "PC?"  Does Compaq sell "PC's" with Alphas in them?   Arne Vajhj wrote: >  > cjt & trefoil wrote: > > Arne Vajhj wrote: > > <snip> The > > > statementiK > > > above could be referring to the fact that SUN is not selling hardwaref > > > based on Intel chips.  > > >e
 > > > Arne > >n > > Are AMD chips close enough?e >  > Yes. > * > Are SUN selling PC's with AMD chips in ? >  > Arne   ------------------------------   Date: 9 Aug 2001 13:54:29 -0400e/ From: jordan@lisa.gemair.com (Jordan Henderson)r Subject: Re: Move to Sun* Message-ID: <9kuiol$t3n$1@lisa.gemair.com>  + In article <3B702E8C.9A94A5D8@caltech.edu>,l) David Mathog  <mathog@caltech.edu> wrote:tK >                                                  Here's an example of theuJ >sorts of minor changes I've seen. The Solaris C compiler didn't like code	 >that did  >o >char foo[100] >  >   function(&foo) >, >instead ofe >e >   function (&foo[0]) >nI >when the prototype for that parameter was char *, but other than that, IP  B "didn't like"?  Recent DECC compilers complain about that as well.  @ Both the Solaris C and the recent DECC compilers are correct to @ complain.  They aren't equivalent.  The first is a pointer to an? array of characters (char *[]) and the second is a pointer to a  character (char *).  r   >o	 >Regards,p >c
 >David MathogH >mathog@caltech.edu+ >VK >**************************************************************************w >*K >RIH Compaq                                                               *-K >**************************************************************************0 >4 >    -Jordan Hendersonu jordan@greenapple.comd   ------------------------------  $ Date: Thu, 9 Aug 2001 20:02:45 -04009 From: "D.B. Turner, islandco.com" <dbturner@islandco.com>e, Subject: MS610-EA ES40 Memory - Very Cheap !/ Message-ID: <tn68nthinhfg02@news.supernews.com>o   Special comp.os.vms deal  4 MS610-EA 2GB for ES40 - 10 pieces left at $3500 each     We sell Alpha's & Alpha Parts  http://www.islandco.comL sales@islandco.com Island Computers US Corp.  2700 Gregory Streeto Savannah GA 31404> Tel: 912 447 6622: Fax: 912 201 0096*   ------------------------------  # Date: Thu, 09 Aug 2001 21:10:29 GMTb From: paul@wren.cc.kux.edu7 Subject: OpenVMS apps and Compaq committment story here 0 Message-ID: <3b72fc21.7370237@news.cc.ukans.edu>  D http://dailynews.yahoo.com/h/cmp/20010809/tc/iwk20010808s0007_1.html   ------------------------------  + Date: Thu, 09 Aug 2001 13:53:26 -0500 (CDT)  From: HEINS@lcms.org/ Subject: OpenVMS in news at Informationweek.comd) Message-ID: <01K6XKPEXIHK8ZSPFP@lcms.org>   5 http://www.informationweek.com/story/IWK20010808S0007-   ------------------------------   Date: 9 Aug 2001 17:46:04 GMT 3 From: gartmann@immunbio.mpg.de (Christoph Gartmann): Subject: Re: pb decI0 Message-ID: <9kui8s$9f6$1@n.ruf.uni-freiburg.de>  T In article <Uguc7.321$802.12301@nnrp1.proxad.net>, "-[Gj]-" <gjai@free.fr> writes: >error" >??    003    3        qdz    0096 >help me >i'm speak frenchf >serch doc in french >thanksr >search info dec/linux2 >i've decserver 5000/240 and i search all infos !! >error:w >3/misc/kbdg >?STF (4: Ln#0 Kbd self test)w >e
 >3/misc/mouset >?STF (4: Ln#1 Pntr self test)   Je n'y comprends rien...   Amicalementm    Christoph Gartmann:  H -- --------------------------------------------------------------------+H | Max-Planck-Institut fuer      Phone   : +49-761-5108-464   Fax: -452 |H | Immunbiologie                                                        |H | Postfach 1169                 Internet: gartmann@immunbio.mpg.de     |H | D-79011  Freiburg, FRG                                               |H +--------- http://www.immunbio.mpg.de/home/english/menue.html ---------+   ------------------------------  $ Date: Wed, 8 Aug 2001 16:42:18 -04002 From: "Sue Skonetski" <susan.skonetski@compaq.com> Subject: Press Release2 Message-ID: <fuhc7.724$Yx2.18288@news.cpqcorp.net>  4 From the Nashu (New Hampshire) Telegraph (newspaper)  L http://www.nashuatelegraph.com/Main.asp?SectionID=27&SubSectionID=357&Articl	 eID=37912v       Wednesday, August 08, 2001    Compaq computer takes to the sky  " By EILEEN KENNEDY, Telegraph Staff   kennedye@telegraph-nh.coms  G NASHUA - Technology developed at Compaq's Spit Brook Road facility, and0L elsewhere in New England, is now flying proudly in one of the U.S. Air Force 's newest surveillance planes.  D On Monday, the U.S. Air Force took delivery of a Block 20 E-8C JointI Surveillance Target Attack Radar System plane, which has 20 Alpha serversiF with Open VMS operating systems, from the primary contractor, Northrop
 Grumman Corp.m  L The servers and operating systems are part of a $30 million contract between Compaq and Northrop Grumman.  J This is in addition to $1 billion in unrelated government contracts CompaqK has won with the Social Security Association, the National Security and the  U.S. Postal Service.  F Government work is becoming an increasingly important part of Compaq'sK business these days. Compaq had about $1.5 billion in revenue from the U.S.iE government last year, out of total revenue of $42 billion - about 3.5pB percent of the company's business, according to company officials.  L While the aircraft delivered Monday is the 11th in the production series, itL is the first plane to use commercial off-the-shelf ES40CV Alpha servers with Open VMS operating systems.0  F The AlphaServer systems and other systems on J-STARS provide accurate,H real-time data and analysis about vehicles on the ground and slow-movingJ aircraft for peacekeeping missions and decision-making on the battlefield,G according to a Compaq spokesman. The power of the servers is a welcomedrI addition to the planes, said the spokesman, since they offer 10 times theiL computer capacity and memory of the computers previously used on the planes.  F "Traditionally, equipment used in the military surveillance and combatJ environments has been highly specialized and highly customized," said RichI Marcello, vice president and general manager of Compaq's High PerformancesG Systems division. "The fact that commercially available technology likegI Compaq's Open VMS-based AlphaServer ES40CV systems can be integrated intoeE those environments is a testament to the performance, reliability ande7 functionality of Compaq's industry-leading technology."   L Compaq and Digital Equipment Corp. - before it was acquired by Compaq - haveD been working with Northrup Grumman since 1990, on a variety of otherD programs, according to Mary Ellen Fortier, director of marketing and4 business development for Compaq's Open VMS business.  H When the contract for the J-STAR planes was put out to bid, Compaq was aK natural choice because Northrop Grumman "knew how the product would behave,4K and it would work under the stressful conditions of being on a surveillanced plane," she said.o  K One of the reasons Compaq's Alphas were chosen, she said, is because of theB' amount of security the servers provide.c  F "Security is very important to many customers, but particularly so forL customers like this. No intrusion can get onto the systems, from our country- or from (outside the country)," Fortier said.l  J It shows the quality and power of Compaq's servers when the U.S. Air ForceI is willing to use the "off-the-shelf" products for surveillance in battleTH conditions, Fortier said, and in the end, the taxpayers benefit from the
 cost savings.a  D "We applaud the initiative to use Compaq's commercial, off-the-shelfI AlphaServer systems in the J-STARS aircraft," said Ron Ross, president ofeL Compaq Federal LLC. "And we're equally pleased that more and more governmentH agencies are turning to Compaq whether they need the mobility of an iPACK Pocket PC, Evo desktops or laptop units, Compaq Pro-Liant industry-standards9 services or a total services-led IT enterprise solution."g  G During 2001, Compaq was chosen by more than a dozen federal agencies tooI provide equipment, services or both, according to a Compaq spokesman. ThePH value of federal contracts awarded to Compaq over the past three months,K including some large multi-year agreements, will total more than $1 billionr& if all contract options are exercised.  H Last week, the National Security Agency awarded a 10-year contract worthG more than $2 billion to a group of more than a dozen partner companies,u@ including Compaq. The companies will modernize the technologicalH infrastructure of the agency, which will include using Compaq equipment.  J Earlier this year, the U.S. Postal Service signed an agreement with CompaqH to make Presario Internet PCs and a variety of Internet services optionsJ available at discounts to more than 800,000 post office employees. As partG of the contract, Compaq created a custom portal for postal employees to.' securely access the service's intranet.$  D In April, Compaq was awarded a $30 million contract to update 32,000J computers in the Social Security Administration in 1,000 service locations" across the country in five months.  J Compaq has 2,200 employees in Nashua, with several buildings on Spit BrookF Road, where much of the software for Alpha computers is developed. TheI company also has a software manufacturing and packaging company on Cottonw Road.    ------------------------------  # Date: Thu, 09 Aug 2001 22:55:46 GMTd  From: jlsue <jlsuexxxz@home.com>( Subject: Re: Reboot to close a file ????8 Message-ID: <7603nt47h8l7ur62bm6m0vciqqu9s2hr2m@4ax.com>  , On Fri, 03 Aug 2001 17:50:51 -0400, JF Mezei% <jfmezei.spamnot@videotron.ca> wrote:a  
 >jlsue wrote:a: >> Cust1 pays the annual maintenance contract for hw & sw.G >> Cust2 doesn't, but chooses to use Usenet posts for support, and putsw& >> in a request such as has been made. >cM >If customer without access to CSC makes a very valid and valuable suggestionnH >to engineers via usenet, does this mean that because it hasn't been put; >through channels that the suggestion should be discarded ?   C First, that's a really bit IF.  You've seen the types of notes that F come in via usenet.  Most often very little info is  given.  The pointB is, it takes engineers some time to ferret out all of the relevant@ information to reproduce the problen, but they've got to service paying customers first.    >JG >Please remember that if Compaq insists on keeping onlt the largest VMS-N >customers, will it give all employees within those customers access to CSC toM >make suggestions ? Will it give all developpers in small 3rd party companiesi$ >access to CSC to make suggestions ? >.K >System managers may have access o CSC, but users and programmers generallyrN >wouldn't. And those are the ones who might want to see various user interface >improvements made.8  ; And they should get to know the system manager.  Very well. ; This is nothing new, I made many a CSC call on behalf of my C "customers".  Usually just to get the support person to contact the F user or programmer directly.  Is it a bit of a pain?  Sure, sometimes.   > M >There is a difference between suggesting that one should be able to create a[I >shadow set with 2 different disk drive types, and being able to create a U >prompt greater than 32 characters to provide a certain capability for certain users.a  F Sure.  But what are you driving at?  Neither one is as high a priorityD as, say, improving  I/O speed (which gets lots of discussion in this forum).o   >rO >Furthermore, do not forget that there are consultants who may not be customersEJ >of Compaq per say but work at customers. And those consultants who botherL >making suggestions on usernet are perhaps Compaq's only contacts with those2 >smaller customers supported by those consultants.  @ Exactly.  And they need to make a great deal of effort to fosterF relationships with Compaq to get the help that they need.  It may alsoC include having a support contract with Compaq so that they can have  access to the processes.  C This company's value to their customers is related to the amount ofo@ resources they put to use in communication with the main vendor.   Remember, TANSTAAFL.   >iL >Please remember that during the palmer years, many customers were forced toK >sever relationship with Digital and make purchases through 3rd parties who6M >didn't really care about VMS anmd just pushed papers to make an order resulta! >is some product being delivered.   F Hey, I know all about that.  $63million/year business wasn't enough toD keep some customers.  BUT, we still had our support contracts, which> are somewhat seperate from the product purchasing process.  WeF purchased lots of hardware from 3rd parties, and we always had support contract items on those quotes.o   ------------------------------  % Date: Thu, 09 Aug 2001 20:10:04 +0200e, From: Didier Morandi <Didier.Morandi@gmx.ch>* Subject: Re: Red Code: where are we going?& Message-ID: <3B72D1FD.1BF15216@gmx.ch>   JF Mezei wrote:  > O > How many of these windows users actually realise that they have been infectedrJ > and that their PC is constantly spewing out requests to connect to everyN > possible IP ? Seems that the system does crash now and then due to the worm,P > but to a windows user, that is a normal occurance and therefore does not raise > any suspicions.g  C According to the zdnet article that I do not have its url under the E hand, CD-II reboots the PC with a WEB server R+W access to the system F disk top level directory, and with a telnet port opened somewhere as a
 back door.   D.   ------------------------------   Date: 9 Aug 2001 18:34:07 -0000h+ From: Doc.Cypher <doc_cypher@nym.alias.net>D* Subject: Re: Red Code: where are we going?5 Message-ID: <20010809183407.8764.qmail@nym.alias.net>o  " -----BEGIN PGP SIGNED MESSAGE-----  C On Thu, 09 Aug 2001, JF Mezei <jfmezei.spamnot@videotron.ca> wrote:V >"Doc.Cypher" wrote:G >> According to the following article at Zdnet, the estimated number of 6 >> infected machines is probably in excess of 400,000. >e> >> How many of those Windoze users will actually have backups? >s > N >How many of these windows users actually realise that they have been infectedI >and that their PC is constantly spewing out requests to connect to everyaM >possible IP ? Seems that the system does crash now and then due to the worm,fO >but to a windows user, that is a normal occurance and therefore does not raise  >any suspicions.  I I now have over 400 IP addresses in the list of those that have attempted I to attack my server (Code Red Type II). When I try to connect to port 80, I many appear as the "Under Construction" banner. These, I suspect, will be7F blissfully unaware that a backdoor has been installed in their system.  E Of the more notable ones I encoutered was one within the Swedish postr office!h     Doc. - -- l6 The bigger the humbug, the better people will like it.K ~ Phineas Taylor Barnum.                              http://vmsbox.cjb.nete   -----BEGIN PGP SIGNATURE-----s Version: 2.6.2  @ iQEVAwUBO3HEcsriC3SGiziTAQHTLgf+LIH9YJ/XwQihnBgK2t6ssiSzyDfZs0aT@ /yYir8uJ1YaOkz4/yrd+ug6xfpPA9Jd2t11gi0q5fx/hJ/VtBBkWO4t8z9p9pwRh@ e97n23rVyl6g3RZcq/ugcIZC2iVOsH7gunm8wzh4xYGI/SrmISjTUGNZy2R0FJTP@ 5EaCg25kQWySwgVvyCg/aoX/4eLdchoyOb4b0DQA5c/4B0JSAbsCJuVWgOQol/WY@ 5M0KgNj3LdNu8/F4kyrBZlaTwu6Pfdp2l9OflzQG/DqAyCuPtLoRhEznscnNnbKx8 mC4td3U0C74XcJM7gwi3BGLAoFGq62A+IKFozeZAEBnwuSLOW+v+0w== =moYx  -----END PGP SIGNATURE-----i   ------------------------------  % Date: Thu, 09 Aug 2001 21:12:36 +0200q, From: Didier Morandi <Didier.Morandi@gmx.ch>* Subject: Re: Red Code: where are we going?& Message-ID: <3B72E0A5.E0B1E441@gmx.ch>   "Doc.Cypher" wrote:a  K > I now have over 400 IP addresses in the list of those that have attemptedt( > to attack my server (Code Red Type II)  6 How do you identify it? ?XX is CR-I and ?NN is CR-II ?   D.   ------------------------------  # Date: Thu, 09 Aug 2001 21:26:12 GMTa6 From: "Andy Bustamante" <a_c_bustamante@earthlink.net>* Subject: Re: Red Code: where are we going?D Message-ID: <UdDc7.1199$q46.100443@newsread2.prod.itd.earthlink.net>  L Backups are more difficult since no Microsoft o/s provides a backup utility.  H We had a Storageworks guy come by to talk about fiber who wanted to knowH which third party backup product we planning on installing.  I explainedF that we only sold systems to our customers that provided an integrated3 RELIABLE backup solution, that is we're a VMS shop.      -- Andy Bustamanten Remove the ASCII 95s to replyi        L > What is most worrying is that the second version of Code Red leaves telnetL > access open to the infected computer. All machines thus infected should be7 > completely wiped and rebuilt from known safe backups.- >-= > How many of those Windoze users will actually have backups?o >n >s > Doc.   ------------------------------  $ Date: Thu, 9 Aug 2001 20:46:13 -0400+ From: "John Saunders" <jws@ma.ultranet.com>9* Subject: Re: Red Code: where are we going?+ Message-ID: <9kvatn$56v$1@bob.news.rcn.net>   A "Andy Bustamante" <a_c_bustamante@earthlink.net> wrote in messageo> news:UdDc7.1199$q46.100443@newsread2.prod.itd.earthlink.net... > E > Backups are more difficult since no Microsoft o/s provides a backup  utility.  E You mean a reliable backup utility. They do include unreliable backupo
 utilities. --
 John Saundersi jws@ma.ultranet.comp   ------------------------------   Date: 9 Aug 2001 15:01:35 -0000n4 From: Doc.Cypher <Use-Author-Address-Header@[127.1]>* Subject: Re: Red Code: where are we going?6 Message-ID: <20010809150135.14951.qmail@nym.alias.net>  " -----BEGIN PGP SIGNED MESSAGE-----  C On Wed, 08 Aug 2001, JF Mezei <jfmezei.spamnot@videotron.ca> wrote:* >Didier Morandi wrote:K >> Does this mean that all these poor PC users were infected and that their $ >> IIS is trying to infect my iMac?  > O >Yes. They send an HTTP request to anyone and everyone, and if there is a reply0M >that shows that the server is a microsoft IIS of the right version, then the-O >infected machine will infect the host which will in turn try to infect as manym >machines as it wants. > N >They can't infect your mac, but they will still knock at its door to find out$ >if you are on a MS software or not.  D According to the following article at Zdnet, the estimated number of3 infected machines is probably in excess of 400,000.a  = http://www.zdnet.com/zdnn/stories/news/0,4586,5095260,00.htmlo  J What is most worrying is that the second version of Code Red leaves telnetJ access open to the infected computer. All machines thus infected should be5 completely wiped and rebuilt from known safe backups.s  ; How many of those Windoze users will actually have backups?      Doc. - -- y6 The bigger the humbug, the better people will like it.K ~ Phineas Taylor Barnum.                              http://vmsbox.cjb.net    -----BEGIN PGP SIGNATURE-----e Version: 2.6.2  @ iQEVAwUBO3HEcsriC3SGiziTAQERBgf+K3XAXkei9ZreJYjLK5dwjs4VTIPj4YsA@ Pvhm78yb3aaA5uh7zjkEuRDMIm5ubY6YzspWAYJ6tL2ymlgvvefQfWambevipr1D@ BK4asWGhkGgmf8ecz7hCScQ7C5v0e6pnEorVRXKsy4L4VPzpGTXghVQkJC6JO9y3@ goRXtATCdLMZ/labcVa6m+2PcYPEDSnlACCBIKymvxhV/76KbGAyWEO03oNHQEAA@ g5ZtW4r3DXiR9SMl4Luao+XLwHQYSc84DrIktjiaKCCfhWK0AWDGxBDA8WLMOH4c8 hJ4q2gD/JBypZC+CMRCOk1lhHx/qEodxnL4hVk615Dz0yB61X6fcog== =S1m7w -----END PGP SIGNATURE-----    ------------------------------  % Date: Thu, 09 Aug 2001 19:02:57 +0100t+ From: "antonio.carlini" <arcarlini@iee.org>e2 Subject: Re: Shameless Grab; Was Re: uVAX 3100 M38' Message-ID: <3B72D051.65DF4E3F@iee.org>    Robert DiRosario wrote:4 > J > The only difference between a VAXStation 3100 and a MicroVAX 3100 is theL > VAXStation has a frame buffer (video)  board.  Remove the frame buffer, orH > disable it with the switch on the rear of the system, and it becomes a > MicroVAX.m  % The MicroVAX 3100 (Model 10) and the  ' VAXstation 3100 (Model 30) are not the 6 same apart from a frame buffer!a  + You can, however, make the VAXstation thinkF) it is a VAXserver by flicking the switch. . You cannot (IIRC) remove the mono frame buffer( built into the motherboard (although you  can remove an addon GPX or SPX).  - All of this is moot since he almost certainlys has bad memory.s  % Try pulling the memory and reseating e! (if you happen to have two memory.  boards stacked one on top of the  other, try just using one). This  should at least tell you whether only one of the boards is bad.  # It is pretty unlikely that swappings# in known good memory will result ine% harm to that known good memory. It is,# not impossible, but I've never had h" it happen to me. (Which will be of no comfort to you if things 
 go wrong :0 )n  # You could try running with all the y+ memory pulled. I don't know whether it willn+ get very far ... but if it still reproducesU* the above symptoms for the first few tests( then you probably have an issue with the motherboard.   Antonio2     -- e   ---------------M- Antonio Carlini             arcarlini@iee.orgr   ------------------------------  % Date: Thu, 09 Aug 2001 22:56:54 -0500 / From: Chris Scheers <chris@applied-synergy.com>o$ Subject: Re: Suggested DCPS features3 Message-ID: <3B735B86.E3A19C01@applied-synergy.com>a   JF Mezei wrote:a > K > Here is another question. When a PC is connected to VMS via Pathworks (oroI > whatever the name is this week), does the PC have access to the printereO > information and PPDs, or must it assume a generic printer is connected at thet  > other end of the print queue ?  B When you set up a DCPS print queue on a PC, you generally load theH Windows driver (assuming that you are using some version of Windows) forH the particular printer.  This driver knows the printer specific features (via a PPD or otherwise).r  D Then when you print to the queue, the Windows print driver generatesD PostScript code with the various printer attributes embedded.  (This@ file may not work if redirected to a different printer's queue.)  G This pretty much bypasses DCPS's control.  For example, if I specify on D the Windows side that I want double sided printing, the commands getF embedded directly into the generated PS file and DCPS can not override them.   @ Also, you can not directly access DCPS features.  You can set upC different DCPS print queues (using generic queues going to the samem? execution queue) that have the different DCPS features you wanthE defaulted on the queues.  Then you connect the Windows printer to thea appropriate DCPS queue.T  G For example, the LPS20 print driver I have for Windows doesn't know howeH to do NUMBER_UP.  I can set up two DCPS print queues on the VMS box, oneB without NUMBER_UP and one with NUMBER_UP=2.  Then I can create twoD Windows printers and connect each to a queue.  Finally, when I printF from a Windows application, I select the appropriate printer depending% on whether or not I want NUMBER_UP=2.   ? (If I wanted some other NUMBER_UP, I would need to create a newr, queue/Windows printer combination for that.)  H This is clumsy, but does work.  It requires a separate Windows "printer". for each combination of DCPS options you want.  C AFAIK, there is no way to directly pass /PARAMETER options from thee Windows printer to DCPS.  G -----------------------------------------------------------------------a$ Chris Scheers, Applied Synergy, Inc.  C Voice: 817-237-3360            Internet: chris@applied-synergy.com s   Fax: 817-237-3074n   ------------------------------   Date: 9 Aug 2001 13:15:08 -0700o3 From: utlonghornsrule@yahoo.com (Newbie JrSysAdmin) - Subject: Re: Terry Shannon Tech Talk on Tru64o= Message-ID: <2de05464.0108091215.33970e1b@posting.google.com>F  n "Ken Farmer" <kfarmer@tru64.org> wrote in message news:<iDtc7.107157$TM5.15799642@typhoon.southeast.rr.com>...A > "Robert Deininger" <rdeininger@mindspring.com> wrote in messagelH > news:rdeininger-0808012318320001@user-2iveb8l.dialup.mindspring.com...A > > In article <2de05464.0108081502.56624985@posting.google.com>,p8 > > utlonghornsrule@yahoo.com (Newbie JrSysAdmin) wrote: > >o > > > ">' > > > > Copyright 2001 Terry C. Shannone< > > > > Not affiliated with ... Compaq Computer Corporation. > > >tJ > > > lackey, do you even know what a good hotel room in anaheim costs, or7 > > > did your "non-affiliate" take care of it for you?b > >e: > > What's happened to people's manners in this newsgroup? > >r > > -- > > Robert Deininger > > rdeininger@mindspring.coml >  > H > Plus he's/she's hiding in the shadows behind some alias.  Come out Jr.  < oh, yes, i'm "hiding" while saying my own words, rather thanC bullshitting you by wrapping my name around a compaq press release.cF gotta hand it to shannon, though- compaq's lackeys could not have spun( it any better. simply an amazing grovel.   ------------------------------  % Date: Thu, 09 Aug 2001 09:58:44 -0500e0 From: Patrick Spinler <spinler.patrick@mayo.edu>/ Subject: Re: The VMS Opensource Porting Projectr( Message-ID: <3B72A524.C8970238@mayo.edu>  G Sorry for following up to myself, but one other possible source of gooda9 advice might be found here http://gnv.sourceforge.net (or.+ http://www.sourceforge.net/projects/gnv).  u  D For instance, I see that they have a package: "The CRTL SupplementalB library provides functions typically found on Unix system, but areH missing, incomplete, or incorrect on VMS. It is intended to make porting8 to VMS easier" at http://gnv.sourceforge.net/crtlsup.htm   Again, good luck ! -- Pat   Patrick Spinler wrote: > ) > One request and one bit of information:f > H > My request is that you place the sources somewhere where the communityG > (me, for example :-) ) can easily access and review them, even during-I > the middle of the actual porting.  It'd be a lot easier to make helpful>C > suggestions to your students if we can see what they're doing.  Iu< > suggest using sourceforge with their anonymous cvs access. > G > My other thought is to recommend the people who frequent the vms-perl>G > mailing list (vms-perl-request@lists.perl.org) as folks with a lot oftH > knowledge of porting big unixy applications (perl) to vms.  ApproachedB > nicely, I'm certain many of them would be willing to help answer > specific questions.b > 
 > Good luck !  > -- Pat >  > Bill Gunshannon wrote: > >aH > > It looks like this project, which saw much discussion here, is goingI > > to go forward afterall.  I am writing up project proposals right now.sI > > For a start I am looking at finding students willing to try ports of:i > >   PDKSHkF > >   XRN (based onthe most current Unix sources as suggested by Hoff)= > >   LYX (a word processor like program that uses Tex/Latex)o > >fI > > Any other suggestions, as we still have a lot of students who haven'taM > > picked a project yet??  (not Emacs, these are undergrads, not prodigies.)s > >SK > > And, on another note, I am trying to gather sources of information theypI > > are likely to need.  In the heat of the last discussion a book named, H > > "UNIX OpenVMS Compatibility book" was mentioned.  Does anyone have aF > > copy of this book they would be willing to send me??  (Hoff, is itK > > perhaps available from Compaq??)  Are there any other books that peopleiL > > could send here that I could put into the department library for the useN > > of students doing these ports??  Anybody have URLs of sites with info that > > might prove usefull??  > >iJ > > I am really getting psyched about this now and plan to do everything IJ > > can to make it not only be a success this semester, but hopefully makeJ > > it generate the kind of projects the students want so that more can beH > > done every year. There is also a possibility of this leading to someI > > grad school projects which could tackle the larger packages.  It willo, > > all depend on how it goes this semester. > >  > > bill > >h > > --N > > Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesH > > bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. > > University of Scranton   |B > > Scranton, Pennsylvania   |         #include <std.disclaimer.h> >  > --A >       This message does not represent the policies or positions : >              of the Mayo Foundation or its subsidiaries.J >   Patrick Spinler                       email:  Spinler.Patrick@Mayo.EDU> >   Mayo Foundation                       phone:  507/284-9485   -- t?       This message does not represent the policies or positions 1 	     of the Mayo Foundation or its subsidiaries.e3   Patrick Spinler			email:	Spinler.Patrick@Mayo.EDUm'   Mayo Foundation			phone:	507/284-9485i   ------------------------------  # Date: Thu, 09 Aug 2001 19:20:44 GMTr2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)/ Subject: Re: The VMS Opensource Porting Projecte/ Message-ID: <goBc7.2$bB1.1264@news.cpqcorp.net>s  [ In article <3B72A397.E046F631@mayo.edu>, Patrick Spinler <spinler.patrick@mayo.edu> writes:o  G :My request is that you place the sources somewhere where the community F :(me, for example :-) ) can easily access and review them, even during" :the middle of the actual porting.  E   I can provide that storage.  (FTP downloads, but probably not CVS.)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: Thu, 09 Aug 2001 12:57:35 -0500eC From: "Craig A. Berry" <craig.berry@nospam.SignalTreeSolutions.com>p/ Subject: Re: The VMS Opensource Porting Project I Message-ID: <craig.berry-4ABDCA.12573409082001@newsrump.sjc.telocity.net>r  ( In article <3B72A524.C8970238@mayo.edu>,2  Patrick Spinler <spinler.patrick@mayo.edu> wrote:   >"The CRTL Supplemental-D > library provides functions typically found on Unix system, but areJ > missing, incomplete, or incorrect on VMS. It is intended to make porting: > to VMS easier" at http://gnv.sourceforge.net/crtlsup.htm  G Sounds interesting, I didn't know about this one.  The Compaq-supplied jG porting library, John Malmberg's frontport library, and the sources to tE Perl and other Unixy code that has already been ported would also be   good resources.b  I > > My other thought is to recommend the people who frequent the vms-perlyI > > mailing list (vms-perl-request@lists.perl.org) as folks with a lot ofh@ > > knowledge of porting big unixy applications (perl) to vms.    F Thanks for the recommendation Patrick :-).  Indeed send them our way, D but tell them to do their homework first.  If they have checked the $ FAQ, scoured the C documentation at C <http://www.openvms.compaq.com/commercial/c>, studied the existing sE libraries noted above, and can explain what they want to do and what eG they've already tried, then we may have something to talk about.  "How  F do I implement function xyz() on VMS?" would not be an example of how E to approach us.  I suspect the Wizard, who was recently deluged with  A student questions (or really one question by a pile of different o- students), would appreciate similar courtesy.e   > > Bill Gunshannon wrote:  K > > > For a start I am looking at finding students willing to try ports of:N
 > > >   PDKSH-H > > >   XRN (based onthe most current Unix sources as suggested by Hoff)? > > >   LYX (a word processor like program that uses Tex/Latex)B > > >9K > > > Any other suggestions, as we still have a lot of students who haven'tCO > > > picked a project yet??  (not Emacs, these are undergrads, not prodigies.)B  D Something that's been on my list for awhile but I don't see getting , around to soon is James Clark's SGML parser D (<http://www.jclark.com/sp/>).  If you have a student interested in E text encoding (including SGML's upstart offspring HTML and XML) this cE would be a good choice.  SP is a validating parser that can validate 01 XML as well as SGML and also convert SGML to XML.a  M > > > And, on another note, I am trying to gather sources of information theyy > > > are likely to need.     F Philip Bourne's "Unix for OpenVMS Users" works pretty well in reverse E if you use the index.  Go to <http://www.bhusa.com> and do an author dG search on "Bourne."  As a professor it looks like you might be able to e get a free examination copy.  0 You may want to peruse Compaq's OVMS books page:  2 <http://www.openvms.compaq.com/openvms/books.html>   ------------------------------  $ Date: Wed, 8 Aug 2001 09:12:59 -04005 From: "Fred Kleinsorge" <kleinsorge@star.zko.dec.com>p$ Subject: Re: Third postcard from Sun2 Message-ID: <aMac7.710$Yx2.18142@news.cpqcorp.net>  = Alan Greig wrote in message <3B70258A.B9FBB333@virgin.net>...     L >but not with all the accompanying announcements (death of Alpha, layoffs in VMS  >engineering  J To my knowledge, no engineers in VMS were layed off post-EFI announcement,8 although some non-engineering positions were eliminated.   ------------------------------  $ Date: Thu, 9 Aug 2001 17:29:51 -0600- From: "Dan Notov" <dannoHATES_SPAM@large.com>c) Subject: Re: UNIX-cd product distribution-/ Message-ID: <tn67753sec1606@corp.supernews.com>4  F "Brian Tillman" <tillman_brian@notnoone.notnohow.com> wrote in message news:3b72baf7$1@news.si.com...3 > First, do not post HTML to the comp.os.vms group.  >cG > >HAve    compaq/dec software product library and documentation libraynI > product distribution cd's fot the last seversl years for Unix >and Truen 64 -3 > free if anyone interested email me cleaning houser >aK > Of course, you realize it is illegal, based on the license agreement yourS. > company signed, to give these to anyone, no?J Are you certain about this? My SPL distributions have no license agreementG bundled with it. All the software on the distributions are individually?D licensed, and protected by license PAK's. Why can't a person sell or transfer the package?-  K I've noticed that other Compaq software, such as Smart Start, and QuickFindeK (but not the Software Support CD's). have license agreements that allow thed2 transfer of the license to another party. To whit:  G "...Pusuant to this agreement, you may: a) use the programs on a singleeL computer, b) copy the programs into any computer in readable or printed formK for back-up or modification purposes in support of your use of the programs I [snip]; c) modify the programs and/or merge into another program for your,L use on the single computer; and d) transfer the programs and portions of theI programs contained or merged into other programs. You must also reproducemF and include the copyright notice on any copy, modification, or protion merged into another program..."4  J The agreement goes on to say that your license is automatically terminated if you transfer possession.o  E I admit I'm not the swiftest boat in the ocean, but doesn't the abovee; agreement allow a person to sell the kit to another person?o   ------------------------------  $ Date: Thu, 9 Aug 2001 22:03:06 -03001 From: "valdemir J. santos" <valdemir-@uol.com.br> 4 Subject: Using sys$startup:tcpip$define_commands.com1 Message-ID: <001501c12138$42e566a0$0164a8c0@rede>-  , This is a multi-part message in MIME format.  + ------=_NextPart_000_0012_01C1211F.1192A3108 Content-Type: text/plain;s 	charset="iso-8859-1"e+ Content-Transfer-Encoding: quoted-printableX   Hello VMS gurus:  / I'd like to know how use command definitions=20V5 in the file sys$startup:tcpip$define_commands.com.=20r4 How can I use iptunnel, metricview, tcpver, ttcp,=20- mosy, uuencode, uudecode , etc, to manage,=20-$ test and setting my TCP network ?=20 Thanks to all...  + ------=_NextPart_000_0012_01C1211F.1192A310r Content-Type: text/html; 	charset="iso-8859-1"c+ Content-Transfer-Encoding: quoted-printable   > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD>3 <META content=3D"text/html; charset=3Diso-8859-1" =V http-equiv=3DContent-Type>8 <META content=3D"MSHTML 5.00.3018.900" name=3DGENERATOR> <STYLE></STYLE>  </HEAD>h <BODY bgColor=3D#ffffff>> <DIV><FONT face=3DArial size=3D2>Hello VMS gurus:</FONT></DIV> <DIV>&nbsp;</DIV> C <DIV><FONT face=3DArial size=3D2>I'd like to know how use command =f definitions=20
 </FONT></DIV>t. <DIV><FONT face=3DArial size=3D2>in the file =) sys$startup:tcpip$define_commands.com.=20t
 </FONT></DIV>uF <DIV><FONT face=3DArial size=3D2>How can I use iptunnel, metricview, = tcpver, ttcp,=20
 </FONT></DIV>iE <DIV><FONT face=3DArial size=3D2>mosy, uuencode, uudecode , etc, to =d
 manage,=20
 </FONT></DIV>nD <DIV><FONT face=3DArial size=3D2>test and setting my TCP network ? =
 </FONT></DIV>h, <DIV><FONT face=3DArial size=3D2>Thanks to =! all...</FONT></DIV></BODY></HTML>t  - ------=_NextPart_000_0012_01C1211F.1192A310--w   ------------------------------  % Date: Fri, 10 Aug 2001 12:10:28 +1000 / From: "Phil Howell" <phowell@snowyhydro.com.au> 8 Subject: Re: Using sys$startup:tcpip$define_commands.com2 Message-ID: <7pHc7.1878$813.100102@ozemail.com.au>  < "valdemir J. santos" <valdemir-@uol.com.br> wrote in message+ news:001501c12138$42e566a0$0164a8c0@rede...t Hello VMS gurus:  , I'd like to know how use command definitions2 in the file sys$startup:tcpip$define_commands.com.1 How can I use iptunnel, metricview, tcpver, ttcp,-* mosy, uuencode, uudecode , etc, to manage,! test and setting my TCP network ?c Thanks to all...    : this procedure defines symbols for use as foreign commands so :-3 you run the procedurec you type the commandE if you don't supply any parameters it will usually show you the usagea2 (which is often the same as a unix implementation) eg. 
 $ uudecode DECODE input-file [output-file]   8 or sometimes if you type ? or help you may get some help Phil   ------------------------------  % Date: Thu, 09 Aug 2001 20:54:25 +0200 , From: Didier Morandi <Didier.Morandi@gmx.ch>0 Subject: VIRUSES: It's time for a counter attack& Message-ID: <3B72DC62.18589491@gmx.ch>  F So, we are told here, and it is actually absolutely true, that OpenVMSA is the number 1 operating system in terms of safety, security and H operations continuity (btw, does everyone know here that VMS EngineeringG has been requested one day to increase the number of digits from 3 to 4tH in the Uptime display of the SHOW SYSTEM command, because 999 days could be insufficient?)d  D My personal opinion is that number 2 is MacOS (I'm talking about Mac OS9, not OS-X/Unix-like).o  D Conclusion: When the worldwide IT managers decide to realize one dayF that their business and their companies are in REAL GREAT DANGER, they$ will naturally go OpenVMS and APPLE.   What do you think?  3 (maybe I will not retire in 15 years, after all...)c   D.  H PS: My iMac and its PWs are up since the 5th of august. In 4 days, I hadF 1318 ?XX attacks and 23 ?NN ones. The ?XX are probably from RED CODE-1 and the ?NN from RED CODE-2.   ------------------------------   Date: 9 Aug 2001 15:07:14 -050029 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen) 4 Subject: Re: VIRUSES: It's time for a counter attack3 Message-ID: <jer2oere4KyV@eisner.encompasserve.org>   U In article <3B72DC62.18589491@gmx.ch>, Didier Morandi <Didier.Morandi@gmx.ch> writes: H > So, we are told here, and it is actually absolutely true, that OpenVMSC > is the number 1 operating system in terms of safety, security and J > operations continuity (btw, does everyone know here that VMS EngineeringI > has been requested one day to increase the number of digits from 3 to 4-J > in the Uptime display of the SHOW SYSTEM command, because 999 days could > be insufficient?)  > F > My personal opinion is that number 2 is MacOS (I'm talking about Mac > OS9, not OS-X/Unix-like).- > F > Conclusion: When the worldwide IT managers decide to realize one dayH > that their business and their companies are in REAL GREAT DANGER, they& > will naturally go OpenVMS and APPLE. >  > What do you think?  F I think Apple will undermine this safety advantage by pushing MacOS/X.   ------------------------------  % Date: Thu, 09 Aug 2001 21:43:06 -0500<1 From: "David J. Dachtera" <djesys.nospam@fsi.net>s4 Subject: Re: VIRUSES: It's time for a counter attack' Message-ID: <3B734A3A.4D7FB0F2@fsi.net>0   Didier Morandi wrote:g > H > So, we are told here, and it is actually absolutely true, that OpenVMSC > is the number 1 operating system in terms of safety, security andiJ > operations continuity (btw, does everyone know here that VMS EngineeringI > has been requested one day to increase the number of digits from 3 to 4iJ > in the Uptime display of the SHOW SYSTEM command, because 999 days could > be insufficient?)? > F > My personal opinion is that number 2 is MacOS (I'm talking about Mac > OS9, not OS-X/Unix-like).  > F > Conclusion: When the worldwide IT managers decide to realize one dayH > that their business and their companies are in REAL GREAT DANGER, they& > will naturally go OpenVMS and APPLE. >  > What do you think?   <music>e Beautiful Dreamer... </music>   -- s David J. Dachterao dba DJE Systems- http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/k   ------------------------------  % Date: Thu, 09 Aug 2001 21:10:41 +02003, From: Didier Morandi <Didier.Morandi@gmx.ch>( Subject: VIRUSES: What about antibodies?& Message-ID: <3B72E032.B30A90DD@gmx.ch>  9 http://www.internetwebfactory.com/antibodies-00-index.htmt   D.   ------------------------------  % Date: Thu, 09 Aug 2001 19:35:42 +0930p/ From: Mark Daniel <mark.daniel@wasd.vsm.com.au>u! Subject: Re: VMS 7.3 experiences?,/ Message-ID: <3B726076.DEFB3A20@wasd.vsm.com.au>t  9 YMMV?  (sorry, I always hate to admit being monolingual).c  G Also ... look carefully.  Even VMS Engineering can apparently reproducenH the problem using my thirty or so lines of example C code!  I will admitE the problem seems to be a bit of a moving target.  Sometimes the samen* test induces the problem, other times not.  ! Steve.Spires@yellgroup.com wrote:  > N > Contact:   Tel: 3063  -  IS - Infrastructure, 1st Floor, Bridge Street Plaza > O > Conversely we have upgraded a number of nodes, also clustered and standalone,.. > and have experienced none of these problems. > : > I suppose the real answer to the original question is... >  > YMMV >  > ;^Dk > 	 > Steve St > E > Mark Daniel <Mark.Daniel@wasd.vsm.com.au> on 08/07/2001 06:12:55 AM  > " > To:        Info-VAX@Mvb.Saic.Com- > cc:         (bcc: Steve Spires/YellowPages)sP > From:      Mark Daniel <Mark.Daniel@wasd.vsm.com.au>, 7 August 2001, 6:12 a.m. >  > Re: VMS 7.3 experiences? > D > "Beware the Ides of XFC" lest your RMS integrity die an unpleasant > death. > H > We recently upgraded to 7.3 on two Alpha clusters (7 and 4 systems) asH > well as a miscellany of stand-alone systems.  This was in part to reapF > the benfits of XFC (which looked promising on the two standalones we5 > experimented on - obviously not thoroughly enough)., > E > From the outset we noticed (and reported) %XFCACHE-W-DATALOSS OPCOM?F > messages.  This (seems) to have resulted in at least one applicationI > ACCVIOing.  More recently we noticed RMS index file corruption (ANA/RMSiH > reporting "Unrecoverable error encountered in structure of file") withC > XFC (VIOC) turned on and none with it turned off (same data, same C > application, 2 cycles of investigation).  Without reproducing the F > contents of some two dozen or so emails back and forth with CSC it's8 > difficult to be more specific with these descriptions. > F > CSC and VMS Engineering are working (feverishly I should imagine) on > this.  Expect ECOs shortly.  > F > My recommendation would be DO NOT PROCEDE WITH ANY 7.3 UPGRADE until' > these issues (at least) are resolved.m > : > Moral of the story; at least wait for Service Pack 1 ;^) >  > Rob Young wrote: > >r% > > cmcgav@ionet.net wrote in messagea6 > news:<bbltmt44uv2t2njmqmch61b59d457lnnqm@4ax.com>...I > > > On 2 Jul 2001 12:08:23 -0500, young_r@encompasserve.org (Rob Young)g > > > wrote: > > >o; > > > >In article <C2256A7D.004AA3C1.00@jklh21.valmet.com>,l$ > norm.raphael@jamesbury.com writes: > > > >> > > > >>
 > > > >> Tom,s > > > >>M > > > >> According to the cover letter for V7.3, V6.2 is _not_ supported in an > > > >> migration-modecQ > > > >> (or any other mode) with V7.3.  I have been told this is at least partly 	 > because  > > > >> ofeM > > > >> mount hangs with volume shadowing on one of the Field Test releases.d > > > >>D > > > >> Do you have any experience with this, positive or negative. > > > >> > > > >EN > > > >     Last week I booted an Alpha into a VAX 6.2 cluster.  Alpha runningI > > > >     7.2-1 with latest SYS patch (but not the very latest, the oneMG > > > >     updated Thursday or so?).  Mounted disks not in use, copiedPR > > > >     those files, that's easy.  But I also mounted and copied all files offR > > > >     a VAX based shadowset.  Worked like a charm.  One datapoint does not aR > > > >     case make.  Your mileage may vary.  And the Alpha was removed from the) > > > >     cluster after this operation.c > > > >3' > > > >                             Robp > > >a > > >aJ > > > Well, we are installing a new DS20E system, and did some simple timeG > > > trials with a batch application that does a good mix of reads ande
 > > > writes.  > > >d? > > > The disks were served by an HSG80 dual controller system.  > > >d > > > HSG caching turned off > > >-" > > > 7.2-1    No VIOC        6min  > > > 7.2-1    VIOC cache   4min' > > > 7.3      New XFC cache   9min!!!!e > > >Q > > > HSG caching turned on  > > >-B > > > 7.2-1   VIOC cache, HSG cache                      2min 1secA > > > 7.3      New XFC cache, HSG cache               2min 20 secl > > >dI > > > Needless to say we were surprised and disappointed by the results..  > > > K > > > Plus the IO's reported by the 7.3 runs were much higher than the IO's:G > > > from the 7.2-1 runs. CPU time and buffered were nearly identical.. > > >9D > > > Also all drives would only mount under VIOC compatibilty mode. > > >,G > > > Any ideas? I used the same settings for the 7.3 test as it was anm- > > > upgraded copy of the 7.2-1 system disk.f > >o= > > There is so much here... first, XFC will do pre-fetching:V > >tD > > http://www.openvms.compaq.com:8000/73final/6017/6017pro_077.html > >tI > > In an OpenVMS Cluster, different nodes can use different data caches.aH > > This allows mixed architecture clusters to benefit from XFC. OpenVMSJ > > Alpha nodes can use either XFC or VIOC. OpenVMS VAX nodes can use only) > > VIOC, as described in Section 18.5.6.t > >tI > > XFC improves I/O performance and contains the following features thatm  > > are not available with VIOC: > >  > > Read-ahead caching# > > Automatic resizing of the cachen > > Larger maximum cache sizer= > > No limit on the number of closed files that can be cachedu; > > Control over the maximum size of I/O that can be cached : > > Control over whether cache memory is static or dynamic > >o > > ---c > >cE > > So this tells us all your I/O is random.  Or is it?  When you sayw
 > > "cacheJ > > turned off on the HSG80s", you mean write-back cache?  You didn't turn > > off + > > read cache?  When using XFC, what does:" > >d > > $ analyze/system > > SDA> XFC SHOW SUMMARYs > >t > > reveal?o > >r > > I am peeling through:d > >u< > > http://www.decus.gr.jp/decus99/sessioncd/NOTES/OV166.PDF > >,I > > Slide seventeen shows how you can zoom in on individual files, locate  > > ther- > > file id on a directory/full filename.ext;r > >t > > then in SDA: > > H > > SDA> XFC SHOW FILE/ID=xxx  ! Converted to hex, see slide for details > > I > > With both VIOC and XFC, what are your hit rates:  show memory/cache ?n > >e > > To a another PDF of Ian's: > > < > > http://www.decus.gr.jp/decus99/sessioncd/NOTES/OV167.PDF > > F > > look at individual files with less detail, but mostly good enough: > >r: > > $ show mem/cache/file=(device:[directory]filename.ext) > > 3 > > Slide 32 shows that IO latency is less for XFC.h > > J > > However, on slide 33, we see VIOC outperforming XFC for reads to smallD > > files, 1000 block file , 100000 I/Os and VIOC takes 3 minutes 54 > > seconds,# > > XFC takes 4 minutes 14 seconds.c > >tE > > The tables are turned drastically in slide 34.  1.5 million blockr	 > > file,rE > > 300000 I/Os and XFC takes 17 minutes, 36 seconds... VIOC takes 50  > > minutes" > > 24 seconds.l > >eJ > > So what is going on?  You have small files, guess #1.  Second guess is > > thatI > > you somehow aren't doing the same thing.  To report that you had muchr
 > > higher> > > I/Os on the 7.3 runs on the face of it doesn't make sense. > >:J > > Outline what you are doing, how you are doing it , size of files , XFC	 > > stats  > > before and after, etc. etc.r > >FJ > > Basically, not enough to go on.  By the time there is, you may have it > > figureds > > out :-)7 > >Y > > Robn >  > -- > Illegitimis nil carborundum.   -- 3 Nil Illigitimus Carborundum!   ------------------------------  # Date: Thu, 09 Aug 2001 23:23:49 GMT  From: peter.ranisch@chello.at ! Subject: Re: VMS 7.3 experiences?V) Message-ID: <3B731C00.B2647383@chello.at>l   Well,mF   I can tell only the expierence with my customer, which is runing 7.3G since last October (yes it was a pre FT-2 version which we used) and weA@ had never SW-related data corruption problems. We gained for theB application about 15-20% performance increase (using about 10GB of memory for it).t  H About the same amount of performance increase with the fast-path for theD fibre. Fast-path made it now possible to have upto 250% of interrupt Stack on our GS160.l  E  And last but not least Mini-copy reduced dramaticlly the time to gettG outswapped shadow-memeber quickly back into the production 10-20min periB 18GB drive instead of 2 hours. This feature needs that all clusterE members have to be Mini-copy aware which measn currently at least VMSa 7.3,   peter ranisch at compaq dot comy OpenVMS Ambassdorh   ------------------------------  # Date: Fri, 10 Aug 2001 02:17:40 GMTb$ From: Scott Vieth <svieth@wi.rr.com>! Subject: Re: VMS 7.3 experiences?a) Message-ID: <3B7344F9.CE06F054@wi.rr.com>-  L VMS 7.2-1 for fibre channel works very well.  But be warned that the releaseM notes for the new ACS 8.6 cards specify VMS 7.2-1H1 or 7.3.  I sent a message H to the CSC via DSNlink and asked "How about using the 8.6 cards with VMS 7.2-1?",  K They said the new firmware had not been tested with 7.2-1 so we would be in ! unsupported territory.  JEEEEEEZ!   = So the 8.6 cards will sit on my desk until we move to VMS 7.3    -Scott  J p.s.  We haven't experience any problems with our current ACS 8.5-S cards.  ! norm.raphael@jamesbury.com wrote:   K > Given the messages in this tread and the need to upgrade to support fibre 
 > channel,L > I am beginning to conclude that V7.2-1 for VAX and Alpha would be the best > choiceM > over V7.3 for VAX and Alpha.  This is a production cluster and I sense thatt > there aren  > still unplumbed risks in V7.3. >u- > Anyone care to argue (in the formal sense).w >e > -Normn >e1 > djesys.nospam@fsi.net on 08/07/2001 09:05:39 PMe >n) > Please respond to djesys.nospam@fsi.net- >- > To:   Info-VAX@mvb.saic.com  > cc:A$ > Subject:  Re: VMS 7.3 experiences? >. > Mark Daniel wrote: > >.F > > "Beware the Ides of XFC" lest your RMS integrity die an unpleasant
 > > death.
 > > [snip]< > > Moral of the story; at least wait for Service Pack 1 ;^) > E > Now you know why I refer to "General Availability" as "Gamma Test".s >c > -- > David J. Dachteran > dba DJE Systems: > http://www.djesys.com/ >M* > Unofficial Affordable OpenVMS Home Page:! > http://www.djesys.com/vms/soho/t   ------------------------------   End of INFO-VAX 2001.441 ************************