1 INFO-VAX	Wed, 11 Jul 2001	Volume 2001 : Issue 381       Contents: Re: Alpha 2100A blue screen :-( 5 Re: Alpha fiasco looses $30M deal to IBM in Singapore 5 Re: Alpha fiasco looses $30M deal to IBM in Singapore 5 Re: Alpha fiasco looses $30M deal to IBM in Singapore  ALTRAN CETS2001 InquiryD Re: Compilers go to Intel, hobbyist, CSLG, etc. goes out the window?D Re: Compilers go to Intel, hobbyist, CSLG, etc. goes out the window?D Re: Compilers go to Intel, hobbyist, CSLG, etc. goes out the window?D Re: Compilers go to Intel, hobbyist, CSLG, etc. goes out the window?D RE: Compilers go to Intel, hobbyist, CSLG, etc. goes out the window?D RE: Compilers go to Intel, hobbyist, CSLG, etc. goes out the window?D Re: Compilers go to Intel, hobbyist, CSLG, etc. goes out the window? CPQ is laying off 4000 more  Re: CPQ is laying off 4000 more ( Datatrieve Accounting Record for OpeNVMS! Re: DEC Notes available, someone?  Re: Experience with EMC storage  Re: Experience with EMC storage 1 Re: exploitable buffer overflows in VMS possible?  Re: FreeVMS  Re: FUD  Re: Hobbyist
 Re: Hobbyists 
 Re: Hobbyists 
 Re: Hobbyists 
 Re: Hobbyists 
 Re: Hobbyists 
 Re: Hobbyists 
 Re: Hobbyists = RE: If you operate VMS systems, what really are your choices?  Increasing VT420 luminosity..." Re: Increasing VT420 luminosity...( Re: Keystrokes for VT100/VT220 emulation" Re: Memo:  Sure Console Connection Memory Channel II  RE: Memory Channel II   Re: MX V4.2 installation problem  Re: MX V4.2 installation problem Re: OpenVMS and IP StorageO OpenVMS COBOL DCOB$ADDI4, DCOB$CVT_I4_Q , DCOB$CVT_O_I4, DCOB$EXPI4 LINK ERRORS 
 Re: Perl 5.6?  Re: Printer hookups & Re: Removing a Vax cluster environment& Re: Removing a Vax cluster environment$ RE: Terry Shannon Tech Talk on IA-64$ Re: Terry Shannon Tech Talk on IA-64$ Re: Terry Shannon Tech Talk on IA-64$ Re: Terry Shannon Tech Talk on IA-64( Re: The end of Computer Associates ????? vaxes  Re: VMS on IA64 (technical)  Re: VMS on IA64 (technical)  Re: VMS V7.3 SPD Error Re: VMS V7.3 SPD Error Re: VMS V7.3 SPD Error Re: VMS V7.3 SPD Error Re: VMSTAR question   F ----------------------------------------------------------------------    Date: 10 Jul 2001 11:15:09 -07001 From: jason_odonnell@erinet.com (Jason O'Donnell) ( Subject: Re: Alpha 2100A blue screen :-(= Message-ID: <5c8ffd05.0107101015.68745150@posting.google.com>    FIXED!!!  E Remember to use a null modem cable.  My pinout was wrong.  Once I got F the right cable, I got gibberish.  Since gibberish is well known to beE baud rate, I corrected it to 9600.  I now get the "P0>>>".  I can now . take it from here.  BTW: the OS_TYPE was UNIX.   Thanks All.    JMOD   ------------------------------  # Date: Tue, 10 Jul 2001 18:45:43 GMT 4 From: "Terry C. Shannon" <terryshannon@mediaone.net>> Subject: Re: Alpha fiasco looses $30M deal to IBM in Singapore8 Message-ID: <r3I27.25$bj6.17813@typhoon.ne.mediaone.net>  J "Brian Schenkenberger, VAXman-" <system@SendSpamHere.ORG> wrote in message* news:009FECCF.CA2ABF91@SendSpamHere.ORG...G > In article <gRG27.1016$LH4.817548@typhoon.ne.mediaone.net>, "Terry C. , Shannon" <terryshannon@mediaone.net> writes: > > E > >"Brian Schenkenberger, VAXman-" <system@SendSpamHere.ORG> wrote in  message - > >news:009FECBD.3F316A51@SendSpamHere.ORG...  > > L > >> It does not matter what happens within the walls.  It is the perception ofF > >> what is happening within the walls that is going to have more far reaching
 > >> effects.  > >  > >Point well taken! > L > Perhaps next time you're rubbing elbows within the walls you can get these" > morons to understand that point. >   H Lord knows, I've tried. So have many others. The folks in the enterpriseJ business are receptive, but a lot of the messaging comes out of Houston...   ------------------------------  % Date: Tue, 10 Jul 2001 17:00:06 -0400 ' From: "Bill Todd" <billtodd@foo.mv.com> > Subject: Re: Alpha fiasco looses $30M deal to IBM in Singapore( Message-ID: <9ifq58$nhl$1@pyrite.mv.net>  ? "Terry C. Shannon" <terryshannon@mediaone.net> wrote in message 4 news:yxD27.906$LH4.710089@typhoon.ne.mediaone.net...   ...   ? > The strategy going forward is Intel-Oracle-and-Unix centered.   G And this is *good* news for VMS?  Unix is a significantly more credible L replacement for VMS than Windows shows any sign of being in the near future:I if these are the morons who recently thought to replace VMS with Windows, G why won't they be even more enthusiastic about replacing VMS with Unix?    - bill   ------------------------------    Date: 10 Jul 2001 17:09:37 -0700+ From: morton_john@hotmail.com (John Morton) > Subject: Re: Alpha fiasco looses $30M deal to IBM in Singapore= Message-ID: <2d9340de.0107101609.700dd64c@posting.google.com>    Compaq Death Spiral   M http://www.washingtonpost.com/wp-srv/aponline/20010710/aponline171821_000.htm    The Associated Press% Tuesday, July 10, 2001; 5:18 p.m. EDT   E HOUSTON &#8211;&#8211; In its second wave of staffing cuts this year, C Compaq Computer Corp. said Tuesday it was trimming 4,000 more jobs, A bringing the total number of workers it plans to cut this year to  8,500.   -- Inspiration Technology  Z David Mathog <mathog@caltech.edu> wrote in message news:<3B4B1D11.680AD63C@caltech.edu>... > "Terry C. Shannon" wrote:  >  > >  > > On the surface >  > and at every other level > < > > it seems to be a strategic blunder of the first order toN > > publish Alpha's obituary three years ahead of time, but Compaq had reasons+ > > for committing to a high-risk strategy.  > 8 > Like what?  A large portfolio of Compaq "put" options? > 
 > Regards, >  > David Mathog > mathog@caltech.edu   ------------------------------  % Date: Tue, 10 Jul 2001 16:18:48 -0300 ) From: fabio_compaq@ep-bc.petrobras.com.br  Subject: ALTRAN L Message-ID: <OF08388479.B8EBD36E-ON03256A85.006A067B@ep-bc.petrobras.com.br>   Hey Sirs  J Do you know if ALTRAN is a good company ? They are hiring OpenVMS / Oracle RDB ! professionals here in Brazil ....      Regards    FC   ------------------------------  % Date: Tue, 10 Jul 2001 17:11:28 -0500 & From: Jenny Butler <jbutler@utmem.edu> Subject: CETS2001 Inquiry 6 Message-ID: <03bb01c1098d$444a4000$bf01c084@utmem.edu>  L      As you probably know, the Compaq symposium (CETS2001) is in Anaheim, CAI  this September.  The web site is already posting session information and  registration -K  www.cets2001.com.  I am managing the Birds of a Feather session scheduling  for the event.G These are "working group" sessions where attendees may gather and share  technical details regarding G a specific area, such as "automated system alerts using VMS/DCL" or any  directed discussion I of a technical nature.  BOF sessions are very useful in that one user may  have solved a problem thatL another is dealing with.  There is no presentation, just a focused topic and a discussion leader who 3 will be there and keep folks more or less on track. I      If you are planning on attending CETS2001 (excellent event) and have  some area ofD interest that you might lead a BOF session for, please contact me at jbutler@utmem.edu.G  This is a very easy way to learn and contribute to the user community. H                                                                  Thanks,J                                                                      Jenny Butler   ------------------------------  # Date: Tue, 10 Jul 2001 19:38:32 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)M Subject: Re: Compilers go to Intel, hobbyist, CSLG, etc. goes out the window? 2 Message-ID: <YQI27.508$rc5.39349@news.cpqcorp.net>  ` In article <gailkts7m07ddqe6b776pur00crd4807mq@4ax.com>, Alan Greig <a.greig@virgin.net> writes:1 :On Mon, 09 Jul 2001 17:06:46 -0400, Steve Lionel ! :<Steve.Lionel@compaq.com> wrote:  :  : F :>As for "somebody must know" - hah!  My initial understanding is thatB :>the list includes Fortran, C/C++, GEM, Math Library, Ladebug andG :>performance tools.  (I may have left something out.)  SDL is not part  :  :What about BLISS?  K   Compaq will be selling various compilers for OpenVMS on IPF, and I would  K   personally expect that an IPF version of Bliss and of SDL (or a compiler  I   for SDL files that produces compatible results) will be made available  I   as Freeware.  I've been involved with compiler-related discussions here J   in OpenVMS Engineering, and I (unfortunately :-) expect to be even more I   involved with these and with the other related technical discussions...   H   OpenVMS itself requires Bliss, Macro32, SDL, and other tools.  (I willJ   be building a current list of tools and of module counts Real Soon Now.)  L   Note: Per discussions with Mark Gorham (OpenVMS VP), the OpenVMS hobbyist ;   program continues, and is expected to be extended to IPF.   G   Infering much, the reason that Tom Linden likely started this thread  H   probably involves an interest in the availability of a code generator I   for the Kednos PL/I product on IPF -- I don't know of the availability  K   of or plans for the availability of an IPF code generator, nor do I know  H   what (if any) plans Kednos has (or has announced) to port PL/I to IPF.E   (AFAIK, Kednos, Oracle Rdb engineering and few other organizations  F   outside of Compaq are directly tied into and directly using the GEM 0   code generator to generate Alpha object code.)  M   SDL is currently based on PL/I, and SDL might itself be in use to generate  M   PL/I definition files -- SDL is widely used within OpenVMS, within various  J   compilers, and within various Compaq-internal and customer applications J   and associated application build environments.  (In other words, OpenVMSK   engineering would have to overhaul extensive amounts of code if we don't  J   have a "native" compiler for SDL files available -- the current SDL tool?   will work nicely for a "cross-build" environment, of course.)   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: Tue, 10 Jul 2001 21:57:12 +0100 + From: "antonio.carlini" <arcarlini@iee.org> M Subject: Re: Compilers go to Intel, hobbyist, CSLG, etc. goes out the window? ' Message-ID: <3B4B6C28.4023D941@iee.org>    Larry Kilgallen wrote:J > What features that cannot be classified as "bug fixes" are needed in theI > existing C and Fortran compilers (the two that I have seen mentioned) ?  > H > Certainly when Fortran02 is standardized, support for the new featuresG > will be of interest, but just as much of interest to Intel as Compaq.    C99 support?   Antonio    --     --------------- - Antonio Carlini             arcarlini@iee.org    ------------------------------    Date: 10 Jul 2001 18:17:06 -05009 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen) M Subject: Re: Compilers go to Intel, hobbyist, CSLG, etc. goes out the window? 3 Message-ID: <pNlgm$Z+xvei@eisner.encompasserve.org>   g In article <YQI27.508$rc5.39349@news.cpqcorp.net>, hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) writes:   N >   Note: Per discussions with Mark Gorham (OpenVMS VP), the OpenVMS hobbyist = >   program continues, and is expected to be extended to IPF.   @ That would be a considerable improvement over the situation whenA Alpha was introduced, as the ASAP program supported Alpha but not + VAX.  2 out of 3 is better than 1 out of 2.    ------------------------------    Date: 10 Jul 2001 18:19:23 -05009 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen) M Subject: Re: Compilers go to Intel, hobbyist, CSLG, etc. goes out the window? 3 Message-ID: <0UYdyGjhwNFw@eisner.encompasserve.org>   U In article <3B4B6C28.4023D941@iee.org>, "antonio.carlini" <arcarlini@iee.org> writes:  >  >  > Larry Kilgallen wrote:K >> What features that cannot be classified as "bug fixes" are needed in the J >> existing C and Fortran compilers (the two that I have seen mentioned) ? >>  I >> Certainly when Fortran02 is standardized, support for the new features H >> will be of interest, but just as much of interest to Intel as Compaq. >  > C99 support?  ? That seems to be the same thing as my (hypothetical) Fortran02. E There is no reason Intel should be less interested in it than Compaq.    ------------------------------  % Date: Tue, 10 Jul 2001 16:08:23 -0700 ! From: Tom Linden <tom@kednos.com> M Subject: RE: Compilers go to Intel, hobbyist, CSLG, etc. goes out the window? 9 Message-ID: <CIEJLCMNHNNDLLOOGNJIMEEBCPAA.tom@kednos.com>   I Well, we do intend to be on the new architecture with PL/I and using GEm, L would be the most direct route.  Our alternative is to take our retargetable back-endJ running on Tru64 (this is quite similar to GEM, and probably more general,H using a rammar to define architecture) and to port that.  This is a much! bigger job because the front-ends J have diverged over the years and it is the front end that is importatnt toL the customer, in the sense that it has known behavior in terms of semantics,5 options and the like.  And yes we do use SDL as well.   B It will likely take a month before we can have a roadmap in place.   > -----Original Message-----; > From: Hoff Hoffman [mailto:hoffman@xdelta.zko.dec.nospam] ' > Sent: Tuesday, July 10, 2001 12:39 PM  > To: Info-VAX@Mvb.Saic.Com G > Subject: Re: Compilers go to Intel, hobbyist, CSLG, etc. goes out the 	 > window?  >  > ? > In article <gailkts7m07ddqe6b776pur00crd4807mq@4ax.com>, Alan $ > Greig <a.greig@virgin.net> writes:3 > :On Mon, 09 Jul 2001 17:06:46 -0400, Steve Lionel # > :<Steve.Lionel@compaq.com> wrote:  > :  > : H > :>As for "somebody must know" - hah!  My initial understanding is thatD > :>the list includes Fortran, C/C++, GEM, Math Library, Ladebug andI > :>performance tools.  (I may have left something out.)  SDL is not part  > :  > :What about BLISS? > @ >   Compaq will be selling various compilers for OpenVMS on IPF,
 > and I would C >   personally expect that an IPF version of Bliss and of SDL (or a 
 > compilerJ >   for SDL files that produces compatible results) will be made availableK >   as Freeware.  I've been involved with compiler-related discussions here K >   in OpenVMS Engineering, and I (unfortunately :-) expect to be even more K >   involved with these and with the other related technical discussions...  > J >   OpenVMS itself requires Bliss, Macro32, SDL, and other tools.  (I willL >   be building a current list of tools and of module counts Real Soon Now.) > < >   Note: Per discussions with Mark Gorham (OpenVMS VP), the > OpenVMS hobbyist= >   program continues, and is expected to be extended to IPF.  > H >   Infering much, the reason that Tom Linden likely started this threadI >   probably involves an interest in the availability of a code generator J >   for the Kednos PL/I product on IPF -- I don't know of the availabilityB >   of or plans for the availability of an IPF code generator, nor > do I know J >   what (if any) plans Kednos has (or has announced) to port PL/I to IPF.F >   (AFAIK, Kednos, Oracle Rdb engineering and few other organizationsG >   outside of Compaq are directly tied into and directly using the GEM 2 >   code generator to generate Alpha object code.) > B >   SDL is currently based on PL/I, and SDL might itself be in use
 > to generate ? >   PL/I definition files -- SDL is widely used within OpenVMS,  > within variousK >   compilers, and within various Compaq-internal and customer applications L >   and associated application build environments.  (In other words, OpenVMSC >   engineering would have to overhaul extensive amounts of code if 
 > we don'tL >   have a "native" compiler for SDL files available -- the current SDL toolA >   will work nicely for a "cross-build" environment, of course.)  > 2 >  ---------------------------- #include <rtfaq.h> > ----------------------------- 5 >       For additional, please see the OpenVMS FAQ --  www.openvms.compaq.com*  --------------------------- pure personal# opinion --------------------------- L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Tue, 10 Jul 2001 21:00:33 -0500 % From: Keith Brown <kbrown780@isd.net>oM Subject: RE: Compilers go to Intel, hobbyist, CSLG, etc. goes out the window?M/ Message-ID: <tkncg54ks61jd7@corp.supernews.com>    Tom Linden wrote:   K > Well, we do intend to be on the new architecture with PL/I and using GEm,oA > would be the most direct route.  Our alternative is to take ours > retargetable back-endpL > running on Tru64 (this is quite similar to GEM, and probably more general,J > using a rammar to define architecture) and to port that.  This is a much# > bigger job because the front-endseL > have diverged over the years and it is the front end that is importatnt toC > the customer, in the sense that it has known behavior in terms of? > semantics,7 > options and the like.  And yes we do use SDL as well.r > D > It will likely take a month before we can have a roadmap in place. >  >> -----Original Message----- < >> From: Hoff Hoffman [mailto:hoffman@xdelta.zko.dec.nospam]( >> Sent: Tuesday, July 10, 2001 12:39 PM >> To: Info-VAX@Mvb.Saic.ComH >> Subject: Re: Compilers go to Intel, hobbyist, CSLG, etc. goes out the
 >> window? >> >>@ >> In article <gailkts7m07ddqe6b776pur00crd4807mq@4ax.com>, Alan% >> Greig <a.greig@virgin.net> writes:n4 >> :On Mon, 09 Jul 2001 17:06:46 -0400, Steve Lionel$ >> :<Steve.Lionel@compaq.com> wrote: >> : >> :I >> :>As for "somebody must know" - hah!  My initial understanding is thatoE >> :>the list includes Fortran, C/C++, GEM, Math Library, Ladebug andnJ >> :>performance tools.  (I may have left something out.)  SDL is not part >> : >> :What about BLISS?  >>A >>   Compaq will be selling various compilers for OpenVMS on IPF,u >> and I wouldD >>   personally expect that an IPF version of Bliss and of SDL (or a >> compilereK >>   for SDL files that produces compatible results) will be made available L >>   as Freeware.  I've been involved with compiler-related discussions hereL >>   in OpenVMS Engineering, and I (unfortunately :-) expect to be even moreL >>   involved with these and with the other related technical discussions... >>K >>   OpenVMS itself requires Bliss, Macro32, SDL, and other tools.  (I will1G >>   be building a current list of tools and of module counts Real Soon:
 >>   Now.) >>= >>   Note: Per discussions with Mark Gorham (OpenVMS VP), thet >> OpenVMS hobbyistI> >>   program continues, and is expected to be extended to IPF. >>I >>   Infering much, the reason that Tom Linden likely started this threadoJ >>   probably involves an interest in the availability of a code generatorK >>   for the Kednos PL/I product on IPF -- I don't know of the availability C >>   of or plans for the availability of an IPF code generator, norM >> do I knowK >>   what (if any) plans Kednos has (or has announced) to port PL/I to IPF.$G >>   (AFAIK, Kednos, Oracle Rdb engineering and few other organizationsmH >>   outside of Compaq are directly tied into and directly using the GEM3 >>   code generator to generate Alpha object code.). >>C >>   SDL is currently based on PL/I, and SDL might itself be in user >> to generate@ >>   PL/I definition files -- SDL is widely used within OpenVMS, >> within variousmL >>   compilers, and within various Compaq-internal and customer applicationsE >>   and associated application build environments.  (In other words, L >>   OpenVMS engineering would have to overhaul extensive amounts of code if >> we don'teH >>   have a "native" compiler for SDL files available -- the current SDLG >>   tool will work nicely for a "cross-build" environment, of course.)o >>3 >>  ---------------------------- #include <rtfaq.h>d  >> -----------------------------6 >>       For additional, please see the OpenVMS FAQ -- > www.openvms.compaq.com, >  --------------------------- pure personal% > opinion --------------------------- 3 >    Hoff (Stephen) Hoffman   OpenVMS Engineering  R >    hoffman#xdelta.zko.dec.comt >  >   J As a longtime fan of PL/I I am pleased to hear that PL/I will continue to  be available on iVMS.> -- e Keith Brown  kbrown780@isd.net7   ------------------------------  # Date: Wed, 11 Jul 2001 01:45:20 GMTi- From: goathunter@goatley.com (Hunter Goatley)iM Subject: Re: Compilers go to Intel, hobbyist, CSLG, etc. goes out the window? 1 Message-ID: <3b4baf8c.117211891@news.process.com>r  J On Tue, 10 Jul 2001 12:06:00 -0400, Steve Lionel <Steve.Lionel@compaq.com> wrote:  D >On Tue, 10 Jul 2001 10:23:14 +0100, Alan Greig <a.greig@virgin.net> >wrote:l >  >>What about BLISS?- >-G >Funny you should ask.  BLISS is owned by GEM, but is currently in "bugJG >fix only" mode.  Many of us think that an IPF version of BLISS will beoG >needed.  This is one of MANY details that still need to be worked out.p >DI I sure hope so!  Maybe I better dust off my "Why We Need BLISS For Alpha"l! white paper, just in case.... 8-)d   Hunter ------9 Hunter Goatley, Process Software, http://www.process.com/t9 goathunter@goatley.com     http://www.goatley.com/hunter/    ------------------------------    Date: 10 Jul 2001 19:05:24 -05003 From: mcdermott@encompasserve.org (C. M. McDermott),$ Subject: CPQ is laying off 4000 more3 Message-ID: <mjgx4pCZQ9yM@eisner.encompasserve.org>w  	 Hi Folks,8   More layoff's for CPQ...  M http://www.washingtonpost.com/wp-srv/aponline/20010710/aponline171821_000.html   Here is part of the article....t    P "We are committed to taking aggressive actions during this period of slow demandM to make permanent improvements in our business model," said Michael Capellas, F Compaq chairman and chief executive officer. "It is now clear that theH economic slowdown is spreading overseas, and we will therefore move moreG swiftly and go even deeper in our structural cost reduction programs." t  K Compaq will take a restructuring charge of about $490 million in the second06 quarter, which it said was mostly related to job cuts.  E The company is expected to save $900 million annually from the total r reductions.   N So far, Compaq has cut 3,500 jobs in a restructuring program announced earlierL this year. Before Compaq started trimming its work force, it employed 67,000 people.   M "We are aggressively executing against the restructuring program we announcedoN in March," chief financial officer Jeff Clarke said. "However, further actions> are required, and we will address these with similar urgency."  N Compaq is scheduled to reveal complete second-quarter results after the market closes July 25.h  K Shares of Compaq fell 44 cents to $13.76 in trading Tuesday on the New Yorkr; Stock Exchange, but rose to $14.05 in after-hours trading. u     -- y   ------------------------------  # Date: Wed, 11 Jul 2001 03:25:41 GMTn4 From: "Terry C. Shannon" <terryshannon@mediaone.net>( Subject: Re: CPQ is laying off 4000 more: Message-ID: <VGP27.677$bj6.390685@typhoon.ne.mediaone.net>  @ "C. M. McDermott" <mcdermott@encompasserve.org> wrote in message- news:mjgx4pCZQ9yM@eisner.encompasserve.org...o > Hi Folks,E >   More layoff's for CPQ... >  >oL http://www.washingtonpost.com/wp-srv/aponline/20010710/aponline171821_000.ht m  >t! > Here is part of the article....y >y > K > "We are committed to taking aggressive actions during this period of slow  demandE > to make permanent improvements in our business model," said Michael 	 Capellas, H > Compaq chairman and chief executive officer. "It is now clear that theJ > economic slowdown is spreading overseas, and we will therefore move moreH > swiftly and go even deeper in our structural cost reduction programs." >hF > Compaq will take a restructuring charge of about $490 million in the second8 > quarter, which it said was mostly related to job cuts. >g  I $185M of the restructuring charge reflects a writedown of cancelled Alphat development activities...e   ------------------------------  % Date: Tue, 10 Jul 2001 17:52:12 -0400i" From: "Hal Kuff" <Kuff@Tessco.Com>1 Subject: Datatrieve Accounting Record for OpeNVMScO Message-ID: <BBCFECEC89E3BAF0.188A8E8586CF4217.125A0F5CEC81E921@lp.airnews.net>S  J Can someone send me (or tell me where I might find) the OpenVMS accounting record definition(s) for DTR?a   ------------------------------  % Date: Tue, 10 Jul 2001 22:43:14 +0200o> From: "Jean-Francois Marchal" <jean-francois.marchal@x9000.fr>* Subject: Re: DEC Notes available, someone?. Message-ID: <9ifpb2$s1s$1@reader1.imaginet.fr>  3 There is a WEBnotes interface used at DECUS France,v8 based on Netscape Fastrack. You can do almost everithing6 you are able to do with the traditionnal VT interface.! There might be a port to WASD ...b   Jean-Franois Marchal  X9000 - LYON (FR)     E "Larry Kilgallen" <Kilgallen@eisner.decus.org.nospam> a crit dans le 6 message news: $tFQjS1DC6Wr@eisner.encompasserve.org... > In articleA <rdeininger-0907012316130001@user-2ivea5o.dialup.mindspring.com>,i4 rdeininger@mindspring.com (Robert Deininger) writes: > > In article? <Pine.LNX.4.21.0107091848070.8093-100000@firewall.freddym.org>,I2 > > Freddy Meerwaldt <frederik@freddym.org> wrote: > >o > >> Hi Steve, > >>K > >> > >Anyway, we would like to install DEC Notes on it, but I only have ah( > >> > >slightly outdated version handy. > >> >H > >> > The last DEC Notes kit is 2.5A from 1993.  Is that what you have? > >>
 > >> Yupp!I > >> A real pity that DEC stopped developing DEC Notes - it's a very nicej
 > >> product.  > >sK > > Yes, it is nice.  Out of curiosity, what would you like to see added toI it?n > > K > > There's a Notes-to-Web converter around somewhere, likely on one of thedJ > > freeware CDs.  I don't know if it's read-only, or if you can use it to > > post and reply to notes. > L > The one used on DECUServe, originally written by a DECUS member in Europe,J > is read-only.  The DECUServe technical committee has done quite a bit ofL > thinking but not much coding toward providing read-write access.  It looksK > easier and easier the farther you are from the problem.  Remember, one of-J > the bit advantages to the quality of discourse on Notes (at least in the> > public arena) is strong authentication and thus attribution. >i > http://eisner.decus.org/   ------------------------------    Date: 10 Jul 2001 11:09:46 -0700( From: kparris@my-deja.com (Keith Parris)( Subject: Re: Experience with EMC storage= Message-ID: <cb85fed2.0107101009.287594b3@posting.google.com>:  V cyKoloth <koloth@tmisnet.com> wrote in message news:<3B468B8A.4AEE99D5@tmisnet.com>...F > 2) I was not aware of the cache not being mirrored or redundant.  DoI > people using EMC solutions recommend two boxes and do host based volumec$ > shadowing, or some other solution?  E For the very highest availability, you eliminate any single points ofhE failure.  Despite the internal redundancy, an EMC box itself can be aIF single point of failure.  But since a single EMC (Symmetrix) box is soB expensive, people are reluctant to buy two and shadow across them.  E Oh, and ask EMC if they support SCSI Read_Long/Write_Long. :-)  Underr9 DSA, a Forced Error Flag is set on a sector if you get ansF uncorrectable read error.  This ensures that every subsequent time youC read that sector you know the data is in error, until you overwrite9C it.  (On ordinary SCSI disks, you get an error indication the firstrA time you read the bad data, but then (what's left of) the data istF copied (revectored) to another sector and you never get any indication? afterward that the data is now (at least partially) bogus).  To F simulate a Forced Error Flag on SCSI, HBVS uses the SCSI Read_Long and= Write_Long operations, which read and write the data plus the-D associated ECC.  By writing the data inverted, but with the originalD ECC, HBVS can force the drive to generate an ECC error each time the? data is re-read.  (And by re-inverting the data and checking iteA against the ECC, HBVS can tell if this was a Forced Error FlaggedB sector or not.)e  F If HBVS needs to write a simulated Forced Error Flag and the SCSI diskD doesn't support Read_Long/Write_Long, it must kick the entire volume$ out of the shadow set at that point.  F > 3) Does having the cached mirrored and the external batteries on theE > Compaq's HSG80 make it reliable enough to just use controller based>/ > mirroring versus host based volume shadowing?t  F Depends on the level of availability you require.  Experience tells meE there exist some number of hardware failure scenarios where a pair oflD tightly-coupled controllers can't tell between the two of them which? one has a fault, particularly if the fault symptoms look to thee: controller(s) like a failure that could be external to theE controller(s).  In those cases it takes an observer somewhere outsideAB the pair (like VMS driver code) to tell what's really working, andC take the appropriate action.  So I recommend HBVS across controllert# pairs for the highest availability. C -------------------------------------------------------------------yC Keith Parris | parris at encompasserve dot org | VMS consulting on:aC Clusters, Disaster Tolerance, Internals, Perfornamce, Storage & I/O    ------------------------------  # Date: Tue, 10 Jul 2001 23:19:13 GMTr( From: Terry Kennedy <terry@gate.tmk.com>( Subject: Re: Experience with EMC storage' Message-ID: <GGA641.M5v@spcuna.spc.edu>t  * Keith Parris <kparris@my-deja.com> writes:G > Oh, and ask EMC if they support SCSI Read_Long/Write_Long. :-)  Under[; > DSA, a Forced Error Flag is set on a sector if you get an H > uncorrectable read error.  This ensures that every subsequent time youE > read that sector you know the data is in error, until you overwrite E > it.  (On ordinary SCSI disks, you get an error indication the first C > time you read the bad data, but then (what's left of) the data isSH > copied (revectored) to another sector and you never get any indicationA > afterward that the data is now (at least partially) bogus).  To>H > simulate a Forced Error Flag on SCSI, HBVS uses the SCSI Read_Long and? > Write_Long operations, which read and write the data plus the F > associated ECC.  By writing the data inverted, but with the originalF > ECC, HBVS can force the drive to generate an ECC error each time theA > data is re-read.  (And by re-inverting the data and checking itiC > against the ECC, HBVS can tell if this was a Forced Error FlaggedF > sector or not.)   G   Not to disagree with a Storage Architect 8-) but doesn't it write thegI data normally and complement the ECC? That's what was done back on HSC's.   4         Terry Kennedy             http://www.tmk.com2         terry@tmk.com             New York, NY USA   ------------------------------  % Date: Tue, 10 Jul 2001 22:31:31 +0200d= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>M: Subject: Re: exploitable buffer overflows in VMS possible?) Message-ID: <3B4B6623.B03C8D02@gtech.com>    "Bart Z. Lederman" wrote:c> > I would be a bit surprised if you could exploit this type of= > a hole on VMS, particularly on Alpha.  Programs are divideda> > into code and data segments, and you can't execute something< > in a data segment.  This is moderatly enforced on the VAX,; > though it is possible to write to the code segment at run = > time and execute the code (I wrote some diagnostic programs > > some years ago which did this).  However, it's very strongly< > enforced on the Alpha.  The buffers themselves which would< > have to overflow are in a segment of memory which is going< > to be marked to allow writes, but is also going to have to; > be marked as 'no execute'.  Code is in segments which arei* > going to be marked execute and no write.  + I thougth noexe was an ignored attribute !?r   Arne   ------------------------------  # Date: Wed, 11 Jul 2001 00:17:47 GMT.0 From: Monty Brandenberg <mcbinc@ne.mediaone.net> Subject: Re: FreeVMS/ Message-ID: <3B4B9B2B.5E82DFC2@ne.mediaone.net>"   Fred Kleinsorge wrote: > 5 > Monty!  You wanna come back & help port to Itanium?y >    Sure, but it'll cost ya.... :-)u   --  M Monty Brandenberg, Software Consultant                              MCB, Inc.-M mcbinc@world.std.com                                          P.O. Box 426188oM mcbinc@ne.mediaone.net                              Cambridge, MA  02142-0021- 617.864.6907   ------------------------------  % Date: Tue, 10 Jul 2001 17:30:49 -0400 ' From: "Bill Todd" <billtodd@foo.mv.com>  Subject: Re: FUD( Message-ID: <9ifrus$pi3$1@pyrite.mv.net>  , <LBohan@dbc.spam_less..com> wrote in message2 news:of5mkt028aeuf0gijer5dorc6mksbhaq35@4ax.com...6 > On Fri, 06 Jul 2001 02:47:13 GMT, "Terry C. Shannon"$ > <terryshannon@mediaone.net> wrote: > F > >You have a point about the economic futility. Assume CPQ ships 100K AlphasI > >per year. Assume (being generous) an average config has 5 CPUS. If theT AlphahJ > >effort cost CPQ $250M per year, each CPU they shipped would have a $500 R&De > >overhead surtax. Ouch.t >.1 > If one added Capella's salary (29,000,000 USD),d) > the surtax might go up an addtl $58 ,,,s >e7 > but I suppose Capellas does other things unrelated tos4 > Alpha R&D/production, such that he can't be really3 > be considered an Alpha-related expense  alone ...a  K OTOH, if you add up the lost opportunity costs to Alpha of his stewardship,c5 they likely exceed Compaq's profits over that period.o   - bill   ------------------------------  % Date: Tue, 10 Jul 2001 21:13:30 -0500M% From: Keith Brown <kbrown780@isd.net>e Subject: Re: Hobbyist / Message-ID: <tknd8dechviv5f@corp.supernews.com>o   Robert Alan Byer wrote:g  / > Let's see, this is what I have running now...> >  > VAXStation-4000/60, OpenVMSn! > AlphaStation-200 4/233, OpenVMS-! > AlphaStation-250 4/266, OpenVMSe > AlphaStation 500/333, OpenVMS  > AlphaPC 164 500MHz, OpenVMS" > AlphaPC 164SX 533MHz, Tru64n >  > I have offline...  >  > AlphaStation-250 4/266% > Two AlphaPC 164's with 500MHz CPU'sm > MicroVAX-3400a > VAXServer-3300 > Several VAXStation-3100's> > A > All the working machines are clustered together on a Cisco 2924p@ > Enterprise switch hooked into my in-home 100 meg network.  I'm7 > connnected to the internet via a 256K SDSL circuit :}e > , > More info on my machines can be found at.. >   > http://www.ourservers.net/docs > J > I'm in the process of upgrading machines and re-organizing my network :}, > (why do I have all this, because I can :}) > t  < If Kenny dies every show maybe it should be an NT node   ;-) --   Keith Brownc kbrown780@isd.net    ------------------------------  % Date: Tue, 10 Jul 2001 17:49:58 -0400>, From: "Michael L. Umbricht" <mikeu@osfn.org> Subject: Re: Hobbyists( Message-ID: <3B4B7886.C59AAF5C@osfn.org>  G At home: a VAX-11/750, VAXstation 3540 and an AXPpci33.  And a bunch ofc VAXstation 3100's.  E The Retro-Computing Society has an 8550 and 6200 (although we haven't  got the @ three-phase powered wired up yet.)  Plus a bunch of MicroVAX and VAXstations.   -mikeu   http://www.osfn.org/rcsd   Jason O'Donnell wrote: >  > All, > E > It seems that there are several OpenVMS Hobbyists in this group.  IeB > was just curious what systems people have in their homes runningE > OpenVMS.  Any GS series?  As soon as I get things organized, I willd) > have a 2100A RM and and a 2000 at home.  >  > JMOD   ------------------------------  % Date: Tue, 10 Jul 2001 22:00:22 -0400e- From: Michael Austin <miaustin@bellsouth.net>  Subject: Re: Hobbyists- Message-ID: <3B4BB335.25B7F946@bellsouth.net>   G I have 2 2100's (200mhz and a 2 CPU 275mhz) both running OpenVMS 7.2-1. B Both with Apache and Perl/Mod_Perl   works really great!  With DSLD (using a Linksys Router/Hub plus an 8-port hub with 6 systems on theC network.  Now If I couldonly get the ISP to provide static PPPoE IPo
 addresses.   Michael Austin DBA Consultant.o   Jason O'Donnell wrote:   > All, > E > It seems that there are several OpenVMS Hobbyists in this group.  IaB > was just curious what systems people have in their homes runningE > OpenVMS.  Any GS series?  As soon as I get things organized, I will ) > have a 2100A RM and and a 2000 at home.A >- > JMOD   ------------------------------  % Date: Tue, 10 Jul 2001 21:16:37 -0500 1 From: "David J. Dachtera" <djesys.nospam@fsi.net>o Subject: Re: Hobbyists' Message-ID: <3B4BB705.335665A8@fsi.net>    Michael Austin wrote:a > I > I have 2 2100's (200mhz and a 2 CPU 275mhz) both running OpenVMS 7.2-1.SD > Both with Apache and Perl/Mod_Perl   works really great!  With DSLF > (using a Linksys Router/Hub plus an 8-port hub with 6 systems on theE > network.  Now If I couldonly get the ISP to provide static PPPoE IPS > addresses.  G From hanging out over in comp.dcom.xdsl, I've learned about dynamic DNSTD services. All you need is a way to acquire your "leased" IP address,F then you send an update to a service that will serve your name/address via DNS.  2 Not sure how you would do that from VMS, though...   -- . David J. Dachtera  dba DJE Systemsn http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/e  F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.    ------------------------------    Date: 10 Jul 2001 19:40:21 -07001 From: jason_odonnell@erinet.com (Jason O'Donnell)@ Subject: Re: Hobbyists< Message-ID: <5c8ffd05.0107101840.2967e11@posting.google.com>  1 Sounds like a lot of VAXes have found good homes!s  ; I cut my teeth on an 11/750.  How does one of those compare/B performance wise to say an AlphaServer 1000?  I have seen a lot of 1000s on eBay for sale.    JMOD   ------------------------------  % Date: Tue, 10 Jul 2001 22:11:12 -0500k% From: "Rich Jordan" <rjordan@mcs.net>s Subject: Re: Hobbyists5 Message-ID: <TpP27.15465$j02.229139@news.goodnet.com>"  G AlphaStation 200 4/233 (an upgraded 4/166), dual booting NT and OpenVMSiI V7.2-1 until I get a real network connection at home.  VAXstation 3100/76eJ SPX, V7.2, PWS600au, V.2-1 (this one has real licenses, not hobbyist), and an Alpha Multia.    Jason O'Donnell wrote in message4 <5c8ffd05.0107092238.4ae55a50@posting.google.com>... >All,  >0D >It seems that there are several OpenVMS Hobbyists in this group.  IA >was just curious what systems people have in their homes runningyD >OpenVMS.  Any GS series?  As soon as I get things organized, I will( >have a 2100A RM and and a 2000 at home. >a >JMODt   ------------------------------  % Date: Tue, 10 Jul 2001 21:22:52 -0600J% From: Dan O'Reilly <dano@process.com>o Subject: Re: HobbyistsB Message-ID: <5.1.0.14.2.20010710211405.00af1d80@ntbsod.psccos.com>  	 Hmmmm....e  F AlphaStation 200 4/233, 9gb internal, RRD45, 4gb external, 192mb (VMS)H VAXstation 4000 VLC, 1gb internal, 24mb memory, RRD40 (headed for Ebay!)J 2x Alpha Multia on a pizza box, 2x2gb, 64mb memory (1 VMS, 1 Digital UNIX)G VAXstation 4000 Model 60,  2x4gb,1x2gb, 52mb memory, TK50, TLZ07, RRD42r  I All of this on a home network with 3 PC's, 1 laptop and 2 networked laser08 printers, using an ISDN router for outside connectivity.  F (...plus the equipment my company supplies for me, ain't sayin' what!)    Jason O'Donnell wrote in message5 ><5c8ffd05.0107092238.4ae55a50@posting.google.com>.... > >All,o > >pF > >It seems that there are several OpenVMS Hobbyists in this group.  IC > >was just curious what systems people have in their homes runningtF > >OpenVMS.  Any GS series?  As soon as I get things organized, I will* > >have a 2100A RM and and a 2000 at home.   ------I +-------------------------------+---------------------------------------+"I | Dan O'Reilly                  |                                       | I | Principal Engineer            |  "Why should I care about posterity?  |sI | Process Software              |   What's posterity ever done for me?" |oI | http://www.process.com        |                    -- Groucho Marx    | I +-------------------------------+---------------------------------------+o   ------------------------------  % Date: Tue, 10 Jul 2001 21:32:49 -0700-% From: Dean Woodward <deanw@rdrop.com>  Subject: Re: Hobbyists) Message-ID: <3B4BD6F1.F534983E@rdrop.com>o   VT520 console terminal    AS1200 (dual 533Mhz) (VMS 7.2.1)#   7 x RZ29 drives / RAID controllere   DPWS 500au  (VMS 7.2.1)d  # 3 166 Mhz Multias (not running yet)    HSZ40c 4 BA356 shelvesd   12 x RZ28 drives    9 x RZ29 drives    1 x TZ89-   ------------------------------  % Date: Tue, 10 Jul 2001 15:08:14 -0400 + From: "Main, Kerry" <Kerry.Main@compaq.com>:F Subject: RE: If you operate VMS systems, what really are your choices?R Message-ID: <BE56C50EA024184DAF48F0B9A47F5CF4AD7EE5@kaoexc01.americas.cpqcorp.net>   Jon,  ( re: not wanting to go to OpenVMS/IA64 ..  I >>> We have a LOT of clients on VMS, I'd hate to see them all get told to  migrate over to AIX.<<  A Which I am sure you have heard is moving to IA64 as well ..AIX 5Lr (optionally Power4 as well).  
 Reference:& http://www-1.ibm.com/servers/monterey/I "...whose primary goals have been to enhance AIX with proven technologiesoH and to deliver the industry's best enterprise-class UNIX for Intel's new0 64-bit microprocessor based systems (Itanium)."    Regards,  
 Kerry Main Senior Consultantr Compaq Canada Inc. Professional Services, Voice: 613-592-4660y Fax  :  819-772-7036 Email: Kerry.Main@Compaq.com     -----Original Message-----' From: Jon [mailto:jsmyth69@hotmail.com]l Sent: June 27, 2001 10:40 AM To: Info-VAX@Mvb.Saic.ComvF Subject: Re: If you operate VMS systems, what really are your choices?    4 David Spencer <spencer@spaamfree.recneps.com> wrote:  D >Okay, suppose you've got a lot of Alpha gear that's running VMS (orE >Tru64 for that matter).  Right about now you've got to be looking atn> >your choices down the road. As everybody knows, in the future? >you're going to need more computing capacity. Given the recent F >shocking news about Alpha going to Intel (and basically disappearing) >- what are your choices?r >t >1) Stick with Alphas. > F >You could snap up systems as they're released up to the point that noB >new revisions are available. Then you go into the used market andE >add additional systems and keep clustering. This might work out okaydC >as long as you can keep getting parts and somebody to maintain theiH >systems. You might actually do pretty well on the used gear as a numberG >of folks would be swapping out old Alphas for Itaniums or other vendory >gear... >i >2) Make the leap to Itanium.e > G >You trust that Compaq and Intel know what they're doing. Hang in thereeG >with what you've got until the new iVMS systems are available. By 2003AF >those Itanium systems will be as fast and as reliable as your currentE >(or the currently available) Alphas on the market. Then you make thes7 >conversion to the new hardware and keep on trucking...l >o+ >3) Given the advance warning, get out now.e >iI >You've decided against #1 because you're not sure you want to get lockedME >into the same systems forever. Number 2 isn't for you either becauseCH >you're not impressed by Intel's track record on this chip, and besides,A >if you're going to be doing a conversion why not interview otherW	 >vendors?: >  >e >Which number are you and why?  C  #3 is what my company is taking.  Once word of the change got out, F our salespeople started squaking about not being able to make a profitD off of any intel sales.  The execs have made an announcement that weD are now looking at selling ONLY ibm systems.  I've convinced them toD adopt a wait and see view, but it doesn't look good here.  We have aC LOT of clients on VMS, I'd hate to see them all get told to migratet over to AIX.   ------------------------------  % Date: Tue, 10 Jul 2001 19:11:49 -0300o1 From: "Valdemir J. Santos" <valdemir-@uol.com.br> ' Subject: Increasing VT420 luminosity...r< Message-ID: <000a01c1098d$512ee0f0$154c88c8@unipobjetivo.br>  , This is a multi-part message in MIME format.  + ------=_NextPart_000_0007_01C10974.2BC2AF40t Content-Type: text/plain;g 	charset="iso-8859-1" + Content-Transfer-Encoding: quoted-printablet   Hello all guys:H  9 Im my job I have any VT420  terminals, with 10 years old. 2 Is there any way to increase yours luminosity ?=20? (I know that electronic technicians adjust a internal component >  in the terminal, but I don't know which is this component...) Thanks for your information...    + ------=_NextPart_000_0007_01C10974.2BC2AF40i Content-Type: text/html; 	charset="iso-8859-1"e+ Content-Transfer-Encoding: quoted-printablee  > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD>3 <META content=3D"text/html; charset=3Diso-8859-1" =l http-equiv=3DContent-Type>6 <META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR> <STYLE></STYLE>t </HEAD>  <BODY bgColor=3D#ffffff>= <DIV><FONT face=3DArial size=3D2>Hello all guys:</FONT></DIV>o <DIV>&nbsp;</DIV>uC <DIV><FONT face=3DArial size=3D2>Im my job I have any VT420&nbsp; =, terminals, with 10=20a years old.</FONT></DIV>dE <DIV><FONT face=3DArial size=3D2>Is there any way to increase yours =- luminosity ?=20-
 </FONT></DIV>-F <DIV><FONT face=3DArial size=3D2>(I know that electronic technicians = adjust a=20u internal component</FONT></DIV>lJ <DIV><FONT face=3DArial size=3D2>&nbsp;in the terminal, but I don't know = which is=20  this component...)</FONT></DIV>r2 <DIV><FONT face=3DArial size=3D2>Thanks for your = information...</FONT></DIV>  <DIV>&nbsp;</DIV></BODY></HTML>c  - ------=_NextPart_000_0007_01C10974.2BC2AF40--e   ------------------------------    Date: 10 Jul 2001 19:34:21 -0500+ From: kuhrt@encompasserve.org (Marty Kuhrt)a+ Subject: Re: Increasing VT420 luminosity...e3 Message-ID: <$HCXjnGur5gW@eisner.encompasserve.org>   p In article <000a01c1098d$512ee0f0$154c88c8@unipobjetivo.br>, "Valdemir J. Santos" <valdemir-@uol.com.br> writes:. > This is a multi-part message in MIME format. > - > ------=_NextPart_000_0007_01C10974.2BC2AF40o > Content-Type: text/plain;s > 	charset="iso-8859-1"n- > Content-Transfer-Encoding: quoted-printable(  . First off, try not to post using MIME or HTML.   > Hello all guys:I > ; > Im my job I have any VT420  terminals, with 10 years old.h4 > Is there any way to increase yours luminosity ?=20A > (I know that electronic technicians adjust a internal componenta@ >  in the terminal, but I don't know which is this component...)  > Thanks for your information...  B There are some adjustable trim pots on the board inside.  Be very A careful when adjusting them, it is best to use a wood or plastic iB stick to do the adjustment.  There aren't many of these adjustmentC pots, and I think they are marked, but if not trial and error will  ? quickly reveal which one does brightness, contrast, etc.  I've .= done it dozens of times and only been knocked on my rump once-9 (monitor started to slide and I grabbed the wrong place).i   ------------------------------    Date: 10 Jul 2001 17:53:31 -0700- From: afeldman@gfigroup.com (Alan E. Feldman)-1 Subject: Re: Keystrokes for VT100/VT220 emulationr< Message-ID: <af1e4ce6.0107101653.746b4b9@posting.google.com>  _ "Thys de Wet" <thys@it.sun.ac.za> wrote in message news:<9ies2r$10o7$1@news.adamastor.ac.za>...a > M > Is there a VMS command that will display the value of a key pressed? I need E > to sort out some emulation stuff for use with the DEC Multinationale > Character set. > H > If I press the Insert key i would like to see the following displayed: > <ESC>[34x  > or whatever the string is.  B Start an EDT session (EDIT/EDT filename). Press the ESC key twice.D That should produce an escape character in the file. If that doesn'tC produce an escape character in the file, try Ctrl/[ instead -- thatuB really ought to work. (In EDT, an escape character is displayed as' <ESC>, but acts as a single character.)n  C Now, press ESC or Ctrl/[ (that's control-left-bracket) *once*, theneD press the key whose secret escape sequence you want to know. Voila'!E The desired sequence appears! (It may well work in other editors -- Io can't try that right now.)  D (You can also do this at a command prompt, but it's not as neat, and not recommended. [YMMV])   Disclaimer: JMHO   &-) Alan E. Feldmanr afeldman&gfigroup.com    ------------------------------    Date: 10 Jul 2001 11:24:36 -0700( From: kparris@my-deja.com (Keith Parris)+ Subject: Re: Memo:  Sure Console Connection = Message-ID: <cb85fed2.0107101024.3cc8e1b7@posting.google.com>-  C I had exactly the same symptoms a while back when the Cisco networkoE went down (reportedly due to a spanning tree problem that resulted in@E floods of recirculated packets), and serveral Alpha hosts with DE600s5- crashed due to a bug at the time in EIDRIVER.n  F In response, we disconnected the terminal servers we used for PCM fromA the Cisco boxes and created a small private LAN of DEC bridges to.E connect the Alpha running PCM to the terminal servers (and allowed no B IP network connections at all to this LAN).  We also switched fromD using Telnet to the terminal servers back to using LAT, so we didn't0 need any IP router on the new small private LAN.C ------------------------------------------------------------------- C Keith Parris | parris at encompasserve dot org | VMS consulting on:/C Clusters, Disaster Tolerance, Internals, Perfornamce, Storage & I/Ol   ------------------------------  % Date: Tue, 10 Jul 2001 17:57:14 -0400t" From: "Hal Kuff" <Kuff@Tessco.Com> Subject: Memory Channel IIO Message-ID: <AF7B4F558A07431F.07E486EE21AF071A.6FB45E715C020939@lp.airnews.net>   ? In a powerpoint presentation on relative performance of ClusteruK Interconnects for OpenVMS 7.3 the engineer mentions that the Memory ChanneleJ II driver for 7.2x had issues.....  Does anyone know how stable the driver for 7.2-1H1 is?0   ------------------------------  % Date: Tue, 10 Jul 2001 18:27:54 -050060 From: arturo saavedra <arturo.saavedra@wcom.com> Subject: RE: Memory Channel IIC Message-ID: <MOEAJKGGEIMGCCPEPJBHAENGFAAA.arturo.saavedra@wcom.com>i  E We run a pair of GS80s with memory channel.. and have problems during K reboots in which we bugcheck continuously until we reset both ports via theaI mc_diag command from console.  Engineering is in the process of rewritingiK the driver for 7.2-1h1.  Part of our problem is that we are running withoutr0 a MC Hub which was recommended but not required.     -----Original Message-----' From: Hal Kuff [mailto:Kuff@Tessco.Com]o$ Sent: Tuesday, July 10, 2001 4:57 PM To: Info-VAX@Mvb.Saic.Com  Subject: Memory Channel II    ? In a powerpoint presentation on relative performance of Cluster K Interconnects for OpenVMS 7.3 the engineer mentions that the Memory Channel-J II driver for 7.2x had issues.....  Does anyone know how stable the driver for 7.2-1H1 is?j   ------------------------------  % Date: Tue, 10 Jul 2001 16:49:55 -0400V; From: "Brian Tillman" <tillman_brian@notnoone.notnohow.com> ) Subject: Re: MX V4.2 installation problemo$ Message-ID: <3b4b6aba$1@news.si.com>  L >This used to install fine (it is, in fact, the same exact distribution thatL >I had installed about a year ago before some recent upgrades - there do notI >appear to have been any updates to the package since then, or since 1995 & >even, so I didn't download it again).  H The current MX is V5.1 (commercial version).  V4.2 was the last freewareE version.  You should ask your question in vmsnet.mail.mx or send your A question to mx-list@madgoat.com (the mailing list is gated to thee newsgroup).  --A Brian Tillman                   Internet: tillman_brian at si.comuA Smiths Aerospace                          tillman at swdev.si.com = 3290 Patterson Ave. SE, MS      Addresses modified to prevente< Grand Rapids, MI 49512-1991     SPAM.  Replace "at" with "@"8        This opinion doesn't represent that of my company   ------------------------------  % Date: Tue, 10 Jul 2001 22:53:13 +0200 = From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com>s) Subject: Re: MX V4.2 installation problem,) Message-ID: <3B4B6B39.9F4093F5@gtech.com>n   Carl Perkins wrote:rM > This used to install fine (it is, in fact, the same exact distribution that M > I had installed about a year ago before some recent upgrades - there do not2J > appear to have been any updates to the package since then, or since 1995' > even, so I didn't download it again).0 > K > After some upgrading, most notably from VMS Alpha V6.1 to V7.2-1 but witheK > other stuff including Multinet V4.1B-X to V4.3A-X (which shouldn't mattereB > since MX uses NETLIB) I have discovered that MX doesn't install. > I > The reson for the attempted reinstallation is that the old installationa9 > doesn't work due to a shareable image version mismatch.e > % > The installation attempt ends with:P > 8 > %VMSINSTAL-I-RESTORE, Restoring product save set E ...) > %MX-I-LINKING, Linking image MX_SMTP... . > %LINK-W-MULCLUOPT, cluster  multiply definedK >         in options file GERGX$DKA0:[SYS0.SYSUPD.MX042]MX_SMTP.ALPHA_OPT;2 ? > %VMSINSTAL-E-INSFAIL, The installation of MX V4.2 has failed.d > J > It's a pity that it doesn't give a hint as to what it's actually talkingH > about - like *what* cluster, even or what line of MX_SMTP.ALPHA_OPT isF > triggering this. I was about to go for the trial and error method ofG > unpacking saveset E, deleting a line from this file, repacking E, and K > attempting to reinstall to see if I could determine which line is failinga7 > but that seemed excessively tedious - thus this post.g > - > MX_SMTP.ALPHA_OPT;2 contains the following:  > , > VMI$KWD:SMTP.ALPHA_OLB/INCLUDE=MX_SMTP/LIB > VMI$KWD:COMMON.ALPHA_OLB/LIB > MX_SHR:.EXE/SHAREb > NETLIB_SHRXFR:/SHARE > VMI$KWD:MX_FLQ_SHR.EXE/SHARE > F > Which doesn't exactly leap out and point to a culprit for me. I haveK > no idea which of the above is defining a cluster that is already defined.a > H > (I did try to build from source, which also fails gruesomely before itG > even gets to the part where it turns out that you need BLISS, which I0N > havn't installed. That build fails due to being unable to find a DESCRIP.MMS, > file that I beleive is, in fact, present.) > H > Just in case it was the netlib line in the ALPHA_OPT file that was theI > problem, I installed the most recent NETLIB (V2.3B) rather than the one,G > that comes with the MX042 package. Didn't help (which didn't actuallyn2 > surprise me, but it was easy to do so I did it). > I > I compared the contents of SMTP.ALPHA_OLB and COMMON.ALPHA_OLB and theyt' > have no modules or symbols in common.h > K > Has anyone actually installed MX042 on this (or any other recent) version 	 > of VMS?A > A > Any hints as to where the problem lies and what to do about it?   B There are a known problem iN MX 4.2 and nwer VMS versions with the .OPT files.u  G It is very easy to fix. Just unpack savesets edit .OPT files and createj! new savesets and you are all set.1   But:H   - the MX mail-list archives which described what to change are offlineG   - I have the fixes on my hobbyist system back home, but I can not get $     to it rigth now (I am in the US)  H So I am afraid you wil need to get someone else to send you the changes.   Arne   ------------------------------    Date: 10 Jul 2001 17:45:07 -0700( From: kparris@my-deja.com (Keith Parris)# Subject: Re: OpenVMS and IP Storagew< Message-ID: <cb85fed2.0107101645.5ff1f6a@posting.google.com>  } fabio_compaq@ep-bc.petrobras.com.br wrote in message news:<OF753DF5E1.66E92298-ON03256A84.005D4263@ep-bc.petrobras.com.br>...5= > Any idea if OpenVMS will support IP Storage in the future ?   C If IP-based storage succeeds in the marketplace, then yes, odds are  good that VMS will support it.  ? We live in interesting times: on the one hand, you've got Fibre C Channel (which network folks like Cisco feel is a feeble attempt at2F networking technology designed by a bunch of storage idiots) competingC against iSCSI, SCSI-over-IP, etc. (which storage folks like Seagate E feel is a feeble attempt at storage technology designed by a bunch ofh8 network idiots).  The market will decide which succeeds.  F I'm told that one disadvantage IP-based storage has at present is thatB the IP protocol stack is complex enough that running it consumes aC large percentage of a server's CPU horsepower to try to drive it at-F today's gigabit+ rates with today's LAN adapters.  Success of IP-basedC storage may depend on implementing at least some of the IP stack ing7 the host adapter hardware rather than in host software.m  4 > If there is the possibility  of clustering etc ???  C At least some in VMS Engineering have considered the possibility of A implementing SCS over IP.  I think it's technically possible.  Do > folks feel there would be a big demand for this feature?  (TheF TruCluster folks actually did it, but then again, they have decided to@ use a different protocol for 5.0 and following, as I recall from> reading the 5.0 TruCluster documentation, due to problems they1 experienced related to some of the timers in IP.),  B Put another way: Do you feel your IP network is reliable enough to< serve as a VMScluster interconnect?  How about its latency?  Bandwidth?  Cost?h  @ I fear that SCS over IP might end up a lot like SCSI Clusters --= useful at the low end and in niches, but with enough inherentsD performance and reliability issues that it doesn't become mainstream VMScluster technology.  D On the other hand, given IP's universal presence (and the increasingF difficulty of getting bridged VMScluster interconnects from companies'E networking departments) outweigh the technical disadvantages and makeoC it easier for VMS Clusters to survive and thrive in Cisco-dominatedm	 networks?OC ------------------------------------------------------------------- C Keith Parris | parris at encompasserve dot org | VMS consulting on:oC Clusters, Disaster Tolerance, Internals, Performance, Storage & I/Oe   ------------------------------    Date: 10 Jul 2001 14:07:48 -07001 From: wguerrero@csh.cl (Wilson Guerrero-Coltters)fX Subject: OpenVMS COBOL DCOB$ADDI4, DCOB$CVT_I4_Q , DCOB$CVT_O_I4, DCOB$EXPI4 LINK ERRORS= Message-ID: <6c30805d.0107101307.38af2f10@posting.google.com>e   Regards,# This message is only informational. 2 I am one of the so many IT consultants that bosses. want the damn thing already done by yesterday! So, here is the situation:5 1-. VAX COBOL Version 5.0 system developed years ago.t0 Hardware: a VAX (you don't wanna know the model); 2-. Problem: migrate the system to ALPHA DS10 OpenVMS 7.2-1c Compaq COBOL Version 2.7.o 3-. I don't know COBOL. :-) 8 4-. Just installed the damn thing and started to compile: the programs. No big problems, almost. A few modifications? (I learned a few of COBOL), a few programs remade (in C, what ao9 p.i.t.a is COBOL about descriptors!!!, I give up! ), etc. $ Like I said no big problems until... 5-. + DUA1:[A_HORNOS.DIR_MET]>compilar SAH_L050P1y& %LINK-W-NUDFSYMS, 4 undefined symbols:# %LINK-I-UDFSYM,         DCOB$ADDI4 s& %LINK-I-UDFSYM,         DCOB$CVT_I4_Q & %LINK-I-UDFSYM,         DCOB$CVT_O_I4 # %LINK-I-UDFSYM,         DCOB$EXPI4 m8 %LINK-W-USEUNDEF, undefined symbol DCOB$ADDI4 referenced)         in psect $LINK$ offset %X00000080,H         in module SAH_L050A file DUA1:[A_HORNOS.DIR_PRB]SAH_LIBOBJ.OLB;1K by the way "compilar" is just a DCL procedure that cobol/link the programs.eI 6-. So, I lost the way. I search the entire web and no even one reference # to one of the lines above, NOT ONE!dB 7-. Yeah, I know I would have to RTFM! But, remember I just wanted5 the thing already so my bosses stop bothering me. :-)  8-. Well, I read:o3 COBOL027_RELEASE_NOTES.PDF, page 50, line number 1.i There it is!!!!g= [OpenVMS] If the LINK of a COBOL program fails with any DCOB$ O undefined symbols, it is possible that the RTL has not been properly installed.cI Oh, god, I haven't installed that thing!!! o I didn't installed properly,  well I don't remember!  9-. So, I read a few lines from:9 Compaq COBOL for OpenVMS Alpha Systems Installation Guide- and here it is:e, $ PRODUCT INSTALL COBRTL/VERSION=2.7-603B -  $_/SOURCE=DEVICE:[DIRECTORY]+ $ PRODUCT INSTALL COBOL/VERSION=2.7-1209 - i $_/SOURCE=DEVICE:[DIRECTORY] in THAT ORDER! 10-. Problem solved.  / I just wanted to send this message so the words O OpenVMS COBOL DCOB$ADDI4, DCOB$CVT_I4_Q , DCOB$CVT_O_I4, DCOB$EXPI4 LINK ERRORStL appear in the web somewhere. Maybe it could be of use to another unfortunate guy like me.   That's all for now.m Saludos, Wilson.s   ------------------------------  # Date: Tue, 10 Jul 2001 19:05:46 GMTe2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) Subject: Re: Perl 5.6?2 Message-ID: <emI27.503$rc5.39211@news.cpqcorp.net>  ` In article <Bsu27.6104$GI4.275814@typhoon.mn.mediaone.net>, Ed Wilts <ewilts@ewilts.org> writes:I :Now that Compaq nicely bundles perl and mod_perl, what are the plans to PB :keep it current?  As of this week, Compaq still has 5.5.3 online.  F   Perl 5.6.1 is on the agenda for building and kitting, assuming that F   I can't unload the work onto some other unsuspecting engineer.  Due D   to comments and feedback received, Perl 5.6 was skipped.  And withC   all that said, I've been a little busy with some other work that OG   has recently cropped up.  And of course, you're free to download and w   build your own Perl...  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: Tue, 10 Jul 2001 16:43:33 -0400T; From: "Brian Tillman" <tillman_brian@notnoone.notnohow.com>D Subject: Re: Printer hookups" Message-ID: <3b4b693d@news.si.com>   >I want-F >to hook up a network printer so that they all can share.  I have been >looking at therJ >web, particulartly HP and Lexmark network printers.  None of the printers? >mentioned in their advertisement supporting OpenVMS platforms.9 >My questions are,E >are there any printers out there that support this OpenVMS platform?   J You can support any network-attached printer you like from VMS is you haveB the proper software.  You need a TCP/IP package and either DCPS or, ScriptServer on your VMS system.  That's it. --A Brian Tillman                   Internet: tillman_brian at si.com A Smiths Aerospace                          tillman at swdev.si.coma= 3290 Patterson Ave. SE, MS      Addresses modified to prevent < Grand Rapids, MI 49512-1991     SPAM.  Replace "at" with "@"8        This opinion doesn't represent that of my company   ------------------------------  # Date: Wed, 11 Jul 2001 01:06:31 GMTl0 From: "Ambrose, Joseph" <jambrose@optonline.net>/ Subject: Re: Removing a Vax cluster environmentr< Message-ID: <rEN27.111758$2W4.19367322@news02.optonline.net>   Nick,u  . Thanks for the suggestions. I'll pass them on.  = As far as a hobbyist goes. he won't have to look very far <g>e  
 Thanks again..  - "Nic Clews" <nclews@csc.com> wrote in messagen6 news:a720d610.0107100329.a59dc73@posting.google.com...= > "Ambrose, Joseph" <jambrose@optonline.net> wrote in message 8 news:<6Ns27.104130$2W4.17578389@news02.optonline.net>...G > > In a cost cutting measure, my boss has asked me to dissolve the VAXr Cluster-L > > from our dual VAX 4000-500a cluster to enable me to split the system and* > > physically shut down one of the CPU's. > >nG > > I told him we could shutdown and halt one of the processors and thet clustero7 > > would continue, he wants to physically shut it off.u > >rL > > This is not possible now because some of the drives are also in the same9 > > enclosure. Therefore dropping the system on its head.[ > > A > > I need to break the cluster to do what he has asked. How to ?n >)H > Cost cutting, presumably licencing or software support? With a pair ofH > systems, one should be on 'dependent support' but problems experiencedG > have to be reproduced on your main system, is this an alternative for  > you? >sH > Still, You could purchase a BA400X to contain the disks, same size and7 > shape as a 4500 but just has disk/tape bays for DSSI.h > B > Why is it necessary to pull the box you're no longer using? YourG > operating system license (licence?) does allow you to run software ontH > an alternative system should the 'main' system be unavailable. DisableH > the clustering, remove the 'alternate' root, then just be careful thatB > only one or the other system boots, put a duff entry in the boot& > device field so it has to be manual. >yF > I don't know if you physically removed the CPU and memory if the boxE > would still power up, as I understand it, those switched mode PSU's G > need a load to start properly. However FS may not then touch you with  > a barge pole.o >sG > Anyhow, check the voting scheme and ensure rest of system(s) run lessaH > any votes lost, delete node specific licences from the LMF database to@ > be legal, possibly re-evaluate the whole cluster situation and! > determine if its really needed.  > C > Finally I'm quite sure that if your boss wishes to avoid disposalnE > costs, a kind hobbyist person in your vicinity will assist with thesH > final removal of your system! Just remember to power everything off to! > avoid blowing those DSSI fuses.i >t* > Regards, Nic Clews CSC Computer Sciences > nclews at csc dot com-   ------------------------------  # Date: Wed, 11 Jul 2001 01:08:16 GMT 0 From: "Ambrose, Joseph" <jambrose@optonline.net>/ Subject: Re: Removing a Vax cluster environmente< Message-ID: <4GN27.111760$2W4.19370771@news02.optonline.net>  ) Yup, NYC, I'll contact my support people.f   thanks!s  < "David J. Dachtera" <djesys.nospam@fsi.net> wrote in message! news:3B4B195E.58A79582@fsi.net...3 > "Ambrose, Joseph" wrote: > >oG > > In a cost cutting measure, my boss has asked me to dissolve the VAXp Cluster L > > from our dual VAX 4000-500a cluster to enable me to split the system and* > > physically shut down one of the CPU's. > > G > > I told him we could shutdown and halt one of the processors and the1 cluster07 > > would continue, he wants to physically shut it off.u > >:L > > This is not possible now because some of the drives are also in the same9 > > enclosure. Therefore dropping the system on its head.l > >dA > > I need to break the cluster to do what he has asked. How to ?n > >e > > VMS 6.2o > G > In a two node cluster, you should be running with quorum disk so that F > either node can run without the other being booted. If this is true,I > then just shut the one vax down to the console and leave it there until-J > you can get some down time. Then, shutdown the cluster, recable the diskH > power so it does not depend on the other VAX, set the surviving node'sH > VAXCLUSTER parameter to zero(0) (use conversational boot), and off you > go.n >cD > Now - if you're talking DSSI disks in the other VAX 4000, that may@ > present further challenges. Best to contact your local serviceG > organization (assuming you are under contract) for advice/assistance.u >1G > I tried to look up your locale (area 212?) on your "Award Winning Web.+ > Site", but it's currently extremely slow.t > G > Ah - ok, you're in New York City. Best to contact someone local then.i > Too far for me.  >  > -- > David J. Dachterat > dba DJE Systemsa > http://www.djesys.com/ >e< > Unofficial Affordable OpenVMS Home Page and Message Board:! > http://www.djesys.com/vms/soho/e >9H > This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings > is to be expected. >sB > Feel free to exercise your rights of free speech and expression. >iH > However, attacks against individual posters, or groups of posters, are > strongly discouraged.    ------------------------------  % Date: Tue, 10 Jul 2001 14:40:57 -0400m+ From: "Main, Kerry" <Kerry.Main@COMPAQ.com>a- Subject: RE: Terry Shannon Tech Talk on IA-64 R Message-ID: <BE56C50EA024184DAF48F0B9A47F5CF4AD7EED@kaoexc01.americas.cpqcorp.net>  I Actually, the V5 tpmC results by most vendors have been out since the mid- March timeframe.  
 Reference:; http://www.ideasinternational.com/benchmark/tpc/tpccnc.html?F http://www.ideasinternational.com/infofile/itpcc.html (for differences between V3 and V5).D   Regards,   Regards,
 Kerry Main Senior Consultantr Compaq Canada Inc. Professional Servicesc Voice: 613-592-4660t Fax  :  819-772-7036 Email: Kerry.Main@Compaq.com     -----Original Message-----1 From: cjt & trefoil [mailto:cheljuba@prodigy.net]e Sent: July 10, 2001 1:50 PM  To: Info-VAX@Mvb.Saic.Como- Subject: Re: Terry Shannon Tech Talk on IA-64      I assume you mean TPC-C?  # http://www.tpc.org/tpcc/default.aspn  F "The TPC has released a new version of TPC-C (V5.0) which replaces the	 previous  J version (V3.5).  ...  The first TPC-C V5 results will become available in  March 2001."  L So it seems everybody has to redo their benchmarks as a result of the change  K to V5.0.  That's an expensive process that takes time.  You're just seeing S the early returns.   Michael Austin wrote:- > J > it is interesting that everyone I see is clamouring for Sun, yet they do not " > even place in the TPM/C ratings. >  > Michael Austin > DBA Consultant >  > Pio Baettig wrote: > 5 > > "Jeff Killeen" <Jeff@IDM-IO.com> wrote in message 8 > > news:TjB27.11989$4M3.2688848@typhoon1.gnilink.net... > > >b" > > > ----- Original Message -----8 > > > From: "Terry Shannon" <Terry.Shannon@CETS2001.com> > > > To: <jeff@killeen.cc>d+ > > > Sent: Tuesday, July 10, 2001 12:19 AMt& > > > Subject: Terry Shannon Tech Talk > >   > > > They've Killed Alpha! Why? > > >lL > > > Compaq really didn't have much choice. Economic realities played a big > > roleB > > > in the decision to terminate Alpha chip development upon the
 completion ofOI > > > the EV79 processor. Do the math: based on an estimated ship rate ofb ~100KLJ > > > Alpha systems per year, Compaq's Alpha chip consumption was ~250K to ~500KoK > > > CPUs per year. Given Alpha design and development costs of ~$250M peri	 > > year,tH > > > fixed overhead added as much as $1K to the cost of each Alpha chip Compaq > > > shipped. > >  > > etc etct > >tG > > Turn the prizes down, you will ship more thus this 1K overhead goesl down. IfJ > > others survive with mass production, also Compaq should HAVE BEEN able to.nJ > > But Capellas wants to turn Compaq into a service and software company.9 > > Wonder how they will compete to IBM & MS & friends...N > > Look at the newest > > K http://www.tpc.org/tpcc/results/tpcc_perf_results.asp?resulttype=nonclusternE > > TPC benchmark, first line. 'nuff said. I wouldn't have dumped thetI > > architecture, but pushed with low cost entry level machines. Take theu prizesJ > > down for the DS10, you will sell more, consequently win more. But this would L > > be longer term and not shareholder-satisfying within 5 min what seems to be! > > the target of the taken move.n > >r= > > Interesting read: http://www.theinquirer.net/09070116.htm  > >  > > Kind regards > >u > > Pio Baettigi   ------------------------------  % Date: Tue, 10 Jul 2001 17:26:24 -0400h' From: "Bill Todd" <billtodd@foo.mv.com>h- Subject: Re: Terry Shannon Tech Talk on IA-64o( Message-ID: <9ifrmn$otr$1@pyrite.mv.net>  H If Compaq isn't paying for this kind of support, it certainly should be.   - bill  1 "Jeff Killeen" <Jeff@IDM-IO.com> wrote in message-4 news:TjB27.11989$4M3.2688848@typhoon1.gnilink.net... >7 > ----- Original Message -----4 > From: "Terry Shannon" <Terry.Shannon@CETS2001.com> > To: <jeff@killeen.cc>0' > Sent: Tuesday, July 10, 2001 12:19 AM_" > Subject: Terry Shannon Tech Talk >m >a > Dear Jeff, >EL > This is the first in a series of "Tech Talks" by Terry Shannon.  This Tech? > Talk will be on IA-64: Good Questions You Will Need to Answerg >uJ > We live in interesting times. Compaq and Intel on June 25 announced thatB > Alpha, long the fastest processor on the planet, would reach its
 productionH > omega with the ~2004 introduction of the Alpha 21364 EV79 part. CompaqJ > subsequently will base all its enterprise systems on forthcoming members ofF > Intel's IPF (Itanium Processor Family), a.k.a. IA-64, microprocessor lineup.rB > Under the terms of the non-exclusive agreement-an agreement that
 representsH > an undeniable coup for Intel-Compaq will consolidate its entire 64-bitJ > platform and OS lineup on the IPF architecture beginning in 2004. In theH > near term, nothing will change. New Alpha systems and upgrades will beF > rolled out through 2004, and all incumbent systems will be supported throughrJ > 2012. Compaq already has started porting NSK, Tru64 UNIX, and VMS to the IPFrL > while transferring key Alpha processor and compiler technology, tools, and! > engineering resources to Intel.  >V > They've Killed Alpha! Why? >eH > Compaq really didn't have much choice. Economic realities played a big roleL > in the decision to terminate Alpha chip development upon the completion ofK > the EV79 processor. Do the math: based on an estimated ship rate of ~100KnL > Alpha systems per year, Compaq's Alpha chip consumption was ~250K to ~500KG > CPUs per year. Given Alpha design and development costs of ~$250M pert year,nK > fixed overhead added as much as $1K to the cost of each Alpha chip Compaq J > shipped. Absent a dramatic increase in AlphaServer adoption rates, Alpha was L > indicted by the law of diminishing returns, and tried and convicted in theL > court of the marketplace. What's more, SKC believes Compaq became privy toJ > McKinley performance information that drove a stake through the heart of theh? > Alpha "we're twice as fast as anyone else" value proposition.c >y > So, Will IPF Be Alpha-Inside?t >oL > Good question! Given the radical differences in the Alpha superscalar RISCH > and the IPF EPIC architectures, it's uncertain exactly which pieces of AlphaaI > technology can be incorporated into future IPF chips. (Indeed, the true-H > unification of a RISC and EPIC architecture would be the Mother of AllG > Architectural Shotgun Marriages.) Intel will likely capitalize on the/J > on-chip memory controller, interprocessor communications interfaces, andF > on-chip routing technology that EV7 brings to the table; whether IPFH > designers can leverage the EV8 processor's simultaneous multithreadingK > design remains to be seen. With McKinley a done deal the question becomessI > what will the Compaq impact be on the third-generation Madison IPF chipo the K > generation after Deerfield IPF chip. How will Compaq execute its strategy-- > before it can fully impact IPF chip design?a >t > Wildfire, Marvel, then What? >kL > Mongo systems based on CPU Blades and an InfiniBand fabric, just as CompaqL > planned to deliver.  The High Performance Systems Division began designing adK > post-Marvel processor-neutral enterprise server that leverages CPU bladeswK > and InfiniBand fabric well over a year ago, with a projected availability  inG > the middle of the decade. (Those familiar with the ISSG's BladeRunneroE > architecture and the forthcoming QuickBlade server can consider thePK > enterprise server to be "QuickBlade on Steroids."  Since the platform was4H > designed from the ground up to be architecture-neutral, the IPF-InsideD > strategy will not impact the design team. Freed from the burden ofG > developing-and funding-Alpha CPUs, Compaq can focus more resources on0K > system-level enhancements and product differentiators such as RAS, common1B > management tools, middleware, advanced partitioning and resource
 managementL > capabilities, etc-in short, all the underpinnings for the firm's long-term > Server Utility vision. >O > Details, We Need Details!d >vK > I will be expanding on this and other subjects during the opening sessiono onI > Sunday night at the Compaq Enterprise Technical Symposium to be held in 8 > Anaheim September 8-14.  For more details please visitL > http://www.CETS2001.com.  I also routinely cover the Compaq cross currentsJ > in my publication "Shannon Knows Compaq".  For more details please visit > http://www.acersoft.com. >p >y! > Copyright 2001 Terry C. Shannon  >e >a >w >n   ------------------------------    Date: 10 Jul 2001 16:54:39 -07003 From: utlonghornsrule@yahoo.com (Newbie JrSysAdmin)7- Subject: Re: Terry Shannon Tech Talk on IA-64C= Message-ID: <2de05464.0107101554.3a6ac54e@posting.google.com>R  b Michael Austin <miaustin@bellsouth.net> wrote in message news:<3B4AF477.4682221F@bellsouth.net>...N > it is interesting that everyone I see is clamouring for Sun, yet they do not" > even place in the TPM/C ratings. >  > Michael Austin > DBA Consultant >  > Pio Baettig wrote: > 5 > > "Jeff Killeen" <Jeff@IDM-IO.com> wrote in message-8 > > news:TjB27.11989$4M3.2688848@typhoon1.gnilink.net... > > >o" > > > ----- Original Message -----8 > > > From: "Terry Shannon" <Terry.Shannon@CETS2001.com> > > > To: <jeff@killeen.cc>.+ > > > Sent: Tuesday, July 10, 2001 12:19 AMW& > > > Subject: Terry Shannon Tech Talk >  o  > > > They've Killed Alpha! Why? > > >aL > > > Compaq really didn't have much choice. Economic realities played a big >  role.P > > > in the decision to terminate Alpha chip development upon the completion ofO > > > the EV79 processor. Do the math: based on an estimated ship rate of ~100KnP > > > Alpha systems per year, Compaq's Alpha chip consumption was ~250K to ~500KK > > > CPUs per year. Given Alpha design and development costs of ~$250M perc >  year,O > > > fixed overhead added as much as $1K to the cost of each Alpha chip Compaq- > > > shipped. > >> > > etc etc- > >-P > > Turn the prizes down, you will ship more thus this 1K overhead goes down. IfN > > others survive with mass production, also Compaq should HAVE BEEN able to.J > > But Capellas wants to turn Compaq into a service and software company.9 > > Wonder how they will compete to IBM & MS & friends...1 > > Look at the newestO > > http://www.tpc.org/tpcc/results/tpcc_perf_results.asp?resulttype=nonclusteriE > > TPC benchmark, first line. 'nuff said. I wouldn't have dumped theuP > > architecture, but pushed with low cost entry level machines. Take the prizesP > > down for the DS10, you will sell more, consequently win more. But this wouldO > > be longer term and not shareholder-satisfying within 5 min what seems to bee! > > the target of the taken move.s > >t= > > Interesting read: http://www.theinquirer.net/09070116.htmd > >t > > Kind regards > >  > > Pio Baettigp     michael-  D maybe sun is busy actually developing and selling their product, andE maybe sun sysadmins are busy working on these systems since they willaD all still have jobs 5 years from today. welcome to anonymity- signed, up for your windows certification class yet?   ------------------------------  # Date: Wed, 11 Jul 2001 00:15:22 GMT & From: "Jeff Killeen" <Jeff@IDM-IO.com>- Subject: Re: Terry Shannon Tech Talk on IA-64-6 Message-ID: <uUM27.550$l%.214419@typhoon2.gnilink.net>  
 Revised...  6 This is the first in a series of "Tech Talks" by Terry8 Shannon. This Tech Talk will be on IA-64: Good Questions You Will Need to Answer0  9 We live in interesting times. Compaq and Intel on June 25l7 announced that Alpha, long the fastest processor on thee7 planet, would reach its production omega with the ~2004n1 introduction of the Alpha 21364 EV79 part. Compaq74 subsequently will base all its enterprise systems on5 forthcoming members of Intel's IPF (Itanium ProcessorN7 Family), a.k.a. IA-64, microprocessor lineup. Under thea7 terms of the non-exclusive agreement--an agreement thath4 represents an undeniable coup for Intel--Compaq will; consolidate its entire 64-bit platform and OS lineup on the 5 IPF architecture beginning in 2004. In the near term,h: nothing will change. The AlphaServer and OS roadmap remain9 intact and essentially unchanged through 2003, and Compaqr; will continue to build and sell Alpha systems through 2013, : and as long thereafter as sufficient demand exists. (Alpha9 products will be supported for at least five years beyondd8 their final purchase date, so ongoing support is assured6 through 2018.) Compaq already has started porting NSK,; Tru64 UNIX, and VMS to the IPF while transferring key Alphar9 processor and compiler technology, tools, and engineerings resources to Intel.    They've Killed Alpha! Why?  5 Given technical and economic realities, Compaq really ; didn't have much choice. A detailed technical assessment of 4 the IPF and Alpha product roadmaps revealed that IPF6 products would in the reasonably near term marginalize1 Alphas sustainable performance advantage valuee5 proposition. Although primarily a technical decision,h2 Compaqs announcement that it will terminate Alpha6 development upon the completion of the EV79 CPU has an4 economic component as well. Do the math: based on an4 estimated ship rate of ~100K Alpha systems per year,; Compaq's Alpha chip consumption was ~250K to ~500K CPUs per 8 year. Given Alpha design and development costs of ~$250M9 per year, fixed overhead added as much as $1K to the costt4 of each Alpha chip Compaq shipped. Absent a dramatic: increase in AlphaServer adoption rates, Alpha was indicted: by the law of diminishing returns, and tried and convicted  in the court of the marketplace.   So, Will IPF Be Alpha-Inside?   7 Its uncertain exactly which pieces of Alpha technologyu; actually can be incorporated into future IPF chips, but then9 cross-pollination of Intel and Alpha developers in and of 6 itself should enrich the IPF architecture. The on-chip0 memory controller, interprocessor communications: interfaces, and on-chip routing technology that EV7 brings8 to the table should be of particular interest to the IPF8 development team. With McKinley a done deal the question: becomes one of when Compaq will be able to impact IPF chip9 development. In the meantime, itll be interesting to see.8 how Compaq will execute its strategy before it can fully impact IPF chip design.J   Wildfire, Marvel, then What?  ; Mongo systems based on CPU Blades and an InfiniBand fabric,b8 just as Compaq planned to deliver. Well over a year ago,: Compaqs High Performance Systems Division began designing4 a post-Marvel enterprise server that will leverage a0 processor blade and InfiniBand switched fabric3 architecture. (InfiniBand is a new low latency highd0 bandwidth I/O and interconnect architecture that7 incorporates many of the concepts of Compaqs ServerNet 8 architecture. Those familiar with the ISSG's forthcoming9 IA-32-based QuickBlade server can consider the future IPFh9 enterprise server to be "QuickBlade on Steroids.") Slatede4 to debut in the middle of the decade, the server was; designed to beand still will bethe successor to the next-u3 generation GS-Series product, the EV7-based Marvel. : (Featuring a modular design that leverages EV7s glueless8 SMP on-chip routing and interconnect technology, Marvel4 will support up to 64 Alpha EV7 processors and offer9 significant improvements in performance, scalability, andr5 cost of ownership. Prototype Marvel systems using EV7t- processors are now running in Compaqs labs.)u    4 The IPF consolidation poses no adverse impact on the7 delivery of Marvel systems or on the development of thee7 post-Marvel enterprise server. Freed from the burden ofg8 developing and funding Alpha CPUs, Compaq can focus more2 resources on system-level enhancements and product5 differentiators such as RAS, common management tools, 9 middleware, advanced partitioning and resource managementt9 capabilities, etc-in short, all the underpinnings for thea' firm's long-term Server Utility vision.t   Details, We Need Details!n  9 I will be expanding on this and other subjects during thet8 kickoff session on Sunday night at the Compaq Enterprise9 Technical Symposium to be held in Anaheim September 8-14. 8 For more details please visit http://www.CETS2001.com. I4 also routinely cover the Compaq cross currents in my; publication "Shannon Knows Compaq". For more details pleasey visit http://www.acersoft.com.     Copyright 2001 Terry C. Shannon    ------------------------------  % Date: Tue, 10 Jul 2001 14:16:31 -0400:; From: "Brian Tillman" <tillman_brian@notnoone.notnohow.com>A1 Subject: Re: The end of Computer Associates ?????c" Message-ID: <3b4b46c7@news.si.com>  " >Page you are viewing has expired.  	 Try here. 1 http://news.cnet.com/news/0-1003-200-6340499.htmle -- oA Brian Tillman                   Internet: tillman_brian at si.comoA Smiths Aerospace                          tillman at swdev.si.coma= 3290 Patterson Ave. SE, MS      Addresses modified to prevent < Grand Rapids, MI 49512-1991     SPAM.  Replace "at" with "@"8        This opinion doesn't represent that of my company   ------------------------------  % Date: Tue, 10 Jul 2001 15:54:26 -0700u. From: Hank Vander Waal <hvanderw@novagate.com> Subject: vaxes; Message-ID: <000601c10993$45a68cf0$9c96a8c6@manufact5l8vs8>?  
 Hey Brian,  L Hudsonville Ice Cream just turned their 3100 off and went to a Alpha station8 200 so if you need another 3100/30 (LOL)  let me know !!  F So not only do they make the best ice cream the run the best operating	 system !!b  , So now I only have 4 Vaxes left to support !A So if anyone is interested in a system for home use let me know !.   Hank Vander Waal CISh Hudsonville MI   ------------------------------  % Date: Tue, 10 Jul 2001 14:39:07 -0400c; From: "Brian Tillman" <tillman_brian@notnoone.notnohow.com>/$ Subject: Re: VMS on IA64 (technical)$ Message-ID: <3b4b4c13$1@news.si.com>  @ >It is not even easy to find a production VAX system any longer.  & Come to my company.  We've 20 of them. -- .A Brian Tillman                   Internet: tillman_brian at si.comSA Smiths Aerospace                          tillman at swdev.si.com = 3290 Patterson Ave. SE, MS      Addresses modified to preventr< Grand Rapids, MI 49512-1991     SPAM.  Replace "at" with "@"8        This opinion doesn't represent that of my company   ------------------------------    Date: 10 Jul 2001 15:56:26 -0500- From: frey@encompasserve.org (Sharon Guthrie)o$ Subject: Re: VMS on IA64 (technical)3 Message-ID: <v+GlMZtIdFBW@eisner.encompasserve.org>   b In article <3b4b4c13$1@news.si.com>, "Brian Tillman" <tillman_brian@notnoone.notnohow.com> writes:A >>It is not even easy to find a production VAX system any longer.  > ( > Come to my company.  We've 20 of them.  J In fact, all across the US... there are many of them running Enhanced 911 L dispatching systems.  (Now THERE's a tribute to not only VMS but to the VAX M platform as well.)  Most of them are two-node clusters, and in approximately eE the 4000 family of machines.  For about the past year or so, our hot rP enhancement request has been to upgrade our CAD software to Alpha for clients.  : But there are still MANY of them running solidly on Vaxen.   Sharon Guthrie tN (Oh, and I think I've heard that one of our clients is still running on a PDP M also, but I don't know if that's just a rumor or if it's true.  I'll have to  + ask around and see.  That would be a kick.)    ------------------------------  + Date: Tue, 10 Jul 2001 12:46:25 -0500 (CDT)a From: sms@antinode.org Subject: Re: VMS V7.3 SPD Errorh) Message-ID: <01071012462534@antinode.org>e  2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)  H >   Due to media availability, OpenVMS VAX systems upgrading to releasesI >   after V7.3 will require access to (and the ability to bootstrap from)d >   a CD-ROM drive.c  ?    After some minor repair to [VMS$COMMON.SYSEXE]STARTUP.MAN in@F VMS072.B, it was possible to make a working TK50 kit from the HobbyistG CD-ROM kit for V7.2.  Is there any hope for this remaining possible for F versions after 7.3?  Clearly, it's a higher priority for us non-paying> customers with obsolete junk than it is for serious customers.  G    Is installation from tape being purposely disabled?  Ignored and not1C supported?  Tested but not acknowledged (or supported)?  Tested andE= supported, but you must make your own tapes?  (Did I miss anyn possibilities?)   H ------------------------------------------------------------------------  C    Steven M. Schweda               (+1) 651-699-9818  (voice, home)lC    382 South Warwick Street        (+1) 763-781-0308  (voice, work)cG    Saint Paul  MN  55105-2547      (+1) 763-781-0309  (facsimile, work)o9    sms@antinode.org                sms@provis.com  (work)n   ------------------------------  % Date: Tue, 10 Jul 2001 14:11:28 -0400I+ From: John Eisenschmidt <jeisensc@aaas.org>e Subject: Re: VMS V7.3 SPD Errort# Message-ID: <sb4b0d29.042@aaas.org>u  G I seem to recall when the announcement was made that VMS VAX would be =oE shipping exclusively on CD-ROM, it was because Q was having trouble =eG obtaining a quantity of tapes. I don't think it was because they were =oG trying to alienate customers...to do that they give the best RISC CPU =g3 known to man to the robber barons known as "Intel".r   Damn, there I go again.P  0 >>> <sms@antinode.org> 07/10/2001 1:46:25 PM >>>2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)  H >   Due to media availability, OpenVMS VAX systems upgrading to releasesI >   after V7.3 will require access to (and the ability to bootstrap from)o >   a CD-ROM drive.   ?    After some minor repair to [VMS$COMMON.SYSEXE]STARTUP.MAN intF VMS072.B, it was possible to make a working TK50 kit from the HobbyistG CD-ROM kit for V7.2.  Is there any hope for this remaining possible fornF versions after 7.3?  Clearly, it's a higher priority for us non-paying> customers with obsolete junk than it is for serious customers.  G    Is installation from tape being purposely disabled?  Ignored and notaC supported?  Tested but not acknowledged (or supported)?  Tested ando= supported, but you must make your own tapes?  (Did I miss anyl possibilities?)m  H ------------------------------------------------------------------------  C    Steven M. Schweda               (+1) 651-699-9818  (voice, home)oC    382 South Warwick Street        (+1) 763-781-0308  (voice, work)!G    Saint Paul  MN  55105-2547      (+1) 763-781-0309  (facsimile, work)P9    sms@antinode.org                sms@provis.com  (work)f   ------------------------------  # Date: Tue, 10 Jul 2001 20:24:08 GMT,2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) Subject: Re: VMS V7.3 SPD Error 2 Message-ID: <IvJ27.515$rc5.39336@news.cpqcorp.net>  B In article <01071012462534@antinode.org>, sms@antinode.org writes:3 :From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)o :tI :>   Due to media availability, OpenVMS VAX systems upgrading to releasespJ :>   after V7.3 will require access to (and the ability to bootstrap from) :>   a CD-ROM drive. :e@ :   After some minor repair to [VMS$COMMON.SYSEXE]STARTUP.MAN inG :VMS072.B, it was possible to make a working TK50 kit from the HobbyistwH :CD-ROM kit for V7.2.  Is there any hope for this remaining possible for :versions after 7.3?  H   Possible?  Sure.  I know of no plans to explicitly disable this stuff.  F   If I were in your situation, I would get a spare disk of 600+ MB, orE   I would acquire and configure a CD-ROM drive.  I would also build anG   standalone BACKUP root on a non-system disk and/or I would install a oG   "spare" copy of OpenVMS VAX on a non-system disk.  (With these steps,eH   you can "image" a tape-based copy of the CD-ROM distribution kit onto E   the "spare" disk, and proceed from there as if you had a CD-ROM...)o  H :   Is installation from tape being purposely disabled?  Ignored and notD :supported?  Tested but not acknowledged (or supported)?  Tested and> :supported, but you must make your own tapes?  (Did I miss any :possibilities?)  E   AFAIK, not maintained, not tested, not supported.  This may further F   include (not) maintaining standalone BACKUP on tape media, though I C   do not know of an explicit decision in that area -- I'll check oni	   that.  s  D   CD-ROM is (or soon will be) the only available and only supported 2   distribution/load/ISL mechanism for OpenVMS VAX.  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: Tue, 10 Jul 2001 23:23:38 -0400 2 From: rdeininger@mindspring.com (Robert Deininger) Subject: Re: VMS V7.3 SPD Error-L Message-ID: <rdeininger-1007012323380001@user-2ive73q.dialup.mindspring.com>  2 In article <ivG27.495$rc5.38938@news.cpqcorp.net>,$ hoffman@xdelta.zko.dec.nospam wrote:  H >   Due to media availability, OpenVMS VAX systems upgrading to releasesI >   after V7.3 will require access to (and the ability to bootstrap from)e >   a CD-ROM drive.   G How about a locally-attached booted disk, containing an image backup ofgC the VMS CD (created on another VMS system)?  This is the method you 7 suggested for CD-less alpha systems, and it works fine.-   Works, but not "supported"?8  8 Not that I hope to fire up a microvax II anytime soon...   -- - Robert Deininger rdeininger@mindspring.comn   ------------------------------  % Date: Tue, 10 Jul 2001 16:39:51 -0400 ; From: "Brian Tillman" <tillman_brian@notnoone.notnohow.com>  Subject: Re: VMSTAR question$ Message-ID: <3b4b685e$1@news.si.com>  I >How do I take a back of all the files in the main dir and all the subdircJ >with the VMSTAR.exe utility. When I try to backup it only takes the filesE >from the current dir and just copies the empty dir without any files   J Did you specifiy the [...] on the file spec?  i.e., to TAR a directory and its subdirectories, you use:  ' $ vmstar/create myfile.tar [somedir...]0  J This will tar the directory SYS$DISK:[SOMEDIR] and all its subdirectories.   By the way, tar is NOT backup. --A Brian Tillman                   Internet: tillman_brian at si.comoA Smiths Aerospace                          tillman at swdev.si.coms= 3290 Patterson Ave. SE, MS      Addresses modified to prevente< Grand Rapids, MI 49512-1991     SPAM.  Replace "at" with "@"8        This opinion doesn't represent that of my company   ------------------------------   End of INFO-VAX 2001.381 ************************