1 INFO-VAX	Mon, 17 Dec 2001	Volume 2001 : Issue 699       Contents:< =?iso-8859-1?Q?Este_a=F1o_ahorre_en_tarjetas_navide=F1as!!?=  Re: Compaq now a takeover target  Re: Compaq now a takeover target  Re: Compaq now a takeover target  Re: Compaq now a takeover target  Re: Compaq now a takeover target  Re: Compaq now a takeover target  Re: Compaq now a takeover target  Re: Compaq now a takeover target  Re: Crash (SYSDUMP.DMP) question  Re: CXX and the Hobbyist license
 DLT sounds Re: DLT sounds Re: DLT sounds Re: global foreing command# I would like to lease time on a VAX ' Re: I would like to lease time on a VAX ' Re: I would like to lease time on a VAX # Re: More about Alpha and the merger # Re: More about Alpha and the merger # Re: More about Alpha and the merger # Re: More about Alpha and the merger # Re: More about Alpha and the merger # Re: More about Alpha and the merger # Re: More about Alpha and the merger # Re: More about Alpha and the merger # Re: More about Alpha and the merger # Re: More about Alpha and the merger # Re: More about Alpha and the merger # Re: More about Alpha and the merger ( Re: More DSSI cluster problems/questions Re: Purging sysuaf.dat Re: Purging sysuaf.dat- Receiving message errors from another nodes.. 1 Re: Receiving message errors from another nodes.. & SDLT embarassing hardware support call Re: vms 3.x question Re: VMS file hex editor?  F ----------------------------------------------------------------------  % Date: Sun, 16 Dec 2001 16:24:57 -0400 * From: "Emailer.cl" <emailer@mediatools.cl>E Subject: =?iso-8859-1?Q?Este_a=F1o_ahorre_en_tarjetas_navide=F1as!!?= 1 Message-ID: <WEBSASP6fZOhsjiGCw40000f6dd@websasp>   , This is a multi-part message in MIME format.  , ------=_NextPart_000_3DA1C_01C1864E.33A0ECC0 Content-Type: text/plain;  	charset="iso-8859-1" + Content-Transfer-Encoding: quoted-printable   2 Si no puede ver este mail, por favor oprima AQU=CDJ <http://www.emailer.cl/mailing.asp?num=3D4875133933651&sess=3D78400169780= &no  mbre=3D &emp=3D>=20   <http://www.emailer.cl> 	=20   	 	 	 	 	 	 	 =09
  	 	 	 =09  		 		 	 	 =09  	 =09  		 =09  	 =09   	 =09   	=200 Este a=F1o ahorre en tarjetas navide=F1as...	=20  =09 OFERTA NAVIDE=D1A=20  USD $38.00 x 10.000 env=EDos	=20  =09@ Emailer es la soluci=F3n profesional de E-mailing que Ud. estaba= esperando, integrando texto, gr=E1ficas, sonido y movimiento.   B Emailer es un motor de env=EDo de correo masivo basado en Web y NO< comercializa bases de datos de correos electr=F3nicos.	  =09
  	 	 	 =095 Si no desea volver a recibir este mail, oprima AQU=CD J <http://www.emailer.cl/unsuscribe.asp?num=3D865832743645058&sess=3D754011= 780 . 15&mail=3DInfo-VAX@mvb.saic.com>  (unsuscribe)  <http://www.emailer.cl>=20   , ------=_NextPart_000_3DA1C_01C1864E.33A0ECC0 Content-Type: text/html; 	charset="iso-8859-1" + Content-Transfer-Encoding: quoted-printable   $ <!DOCTYPE HTML PUBLIC"-//IETF//DTD =G HTML//EN">=0D<html>=0D<head>=0D<title>Mailing</title></head>=0D<table = B border=3D'0' width=3D'100%'><tr><td><center><font face=3D'arial' =H size=3D'1' color=3D'black'>Si no puede ver este mail, por favor oprima = </font><a = J href=3D"http://www.emailer.cl/mailing.asp?num=3D4875133933651&sess=3D7840=C 0169780&nombre=3D &emp=3D" target=3D"_blank"><font face=3D'arial' =  size=3D'1' =C color=3D'black'>AQU=CD</a></font></center></td></tr></table><body = F topmargin=3D"0" leftmargin=3D"0" marginheight=3D"0" marginwidth=3D"0">H <table width=3D"100%" border=3D"0" cellspacing=3D"0" cellpadding=3D"0" = bgcolor=3D"#101078">   <tr>     <td align=3D"center"> ;       <table width=3D"539" border=3D"0" cellspacing=3D"0" =  cellpadding=3D"0">         <tr>/           <td height=3D"60" valign=3D"top"><a = % href=3D"http://www.emailer.cl"><img = ? src=3D"http://www.mediatools.cl/emailer/navidad/img/logo.gif" = 2 width=3D"269" height=3D"59" border=3D"0"></a></td>
         </tr>        </table>	     </td>    </tr> 	   <tr>=20 +     <td align=3D"center" height=3D"430">=20 ?       <table border=3D"0" cellpadding=3D"0" cellspacing=3D"0" =  width=3D"539">D         <!-- fwtable fwsrc=3D"mail_navidad.png" fwbase=3D"nav.gif" =? fwstyle=3D"Generic" fwdocid =3D "742308039" fwnested=3D""0" -->          <tr>=20            <td><img =A src=3D"http://www.mediatools.cl/emailer/navidad/img/spacer.gif" = , width=3D"12" height=3D"1" border=3D"0"></td>           <td><img =A src=3D"http://www.mediatools.cl/emailer/navidad/img/spacer.gif" = , width=3D"16" height=3D"1" border=3D"0"></td>           <td><img =A src=3D"http://www.mediatools.cl/emailer/navidad/img/spacer.gif" = - width=3D"124" height=3D"1" border=3D"0"></td>            <td><img =A src=3D"http://www.mediatools.cl/emailer/navidad/img/spacer.gif" = - width=3D"288" height=3D"1" border=3D"0"></td>            <td><img =A src=3D"http://www.mediatools.cl/emailer/navidad/img/spacer.gif" = , width=3D"57" height=3D"1" border=3D"0"></td>           <td><img =A src=3D"http://www.mediatools.cl/emailer/navidad/img/spacer.gif" = , width=3D"30" height=3D"1" border=3D"0"></td>           <td><img =A src=3D"http://www.mediatools.cl/emailer/navidad/img/spacer.gif" = , width=3D"12" height=3D"1" border=3D"0"></td>           <td><img =A src=3D"http://www.mediatools.cl/emailer/navidad/img/spacer.gif" = + width=3D"1" height=3D"1" border=3D"0"></td> 
         </tr>          <tr>=20 '           <td><img name=3D"nav_r1_c1" = D src=3D"http://www.mediatools.cl/emailer/navidad/img/nav_r1_c1.gif" =- width=3D"12" height=3D"12" border=3D"0"></td> I           <td colspan=3D"5" bgcolor=3D"#FFFFFF"><img name=3D"nav_r1_c2" = D src=3D"http://www.mediatools.cl/emailer/navidad/img/nav_r1_c2.gif" =. width=3D"515" height=3D"12" border=3D"0"></td>'           <td><img name=3D"nav_r1_c7" = D src=3D"http://www.mediatools.cl/emailer/navidad/img/nav_r1_c7.gif" =- width=3D"12" height=3D"12" border=3D"0"></td>            <td><img =A src=3D"http://www.mediatools.cl/emailer/navidad/img/spacer.gif" = , width=3D"1" height=3D"12" border=3D"0"></td>
         </tr>          <tr>=20 I           <td rowspan=3D"7" bgcolor=3D"#FFFFFF"><img name=3D"nav_r2_c1" = D src=3D"http://www.mediatools.cl/emailer/navidad/img/nav_r2_c1.gif" =. width=3D"12" height=3D"366" border=3D"0"></td>6           <td rowspan=3D"7" bgcolor=3D"#FFFFFF"> </td>I           <td rowspan=3D"4" bgcolor=3D"#FFFFFF"><img name=3D"nav_r2_c3" = D src=3D"http://www.mediatools.cl/emailer/navidad/img/nav_r2_c3.gif" =/ width=3D"124" height=3D"111" border=3D"0"></td> 6           <td rowspan=3D"2" bgcolor=3D"#FFFFFF"> </td>I           <td colspan=3D"2" bgcolor=3D"#FFFFFF"><img name=3D"nav_r2_c5" = A src=3D"http://www.mediatools.cl/emailer/navidad/img/spacer.gif" = + width=3D"1" height=3D"1" border=3D"0"></td> I           <td rowspan=3D"7" bgcolor=3D"#FFFFFF"><img name=3D"nav_r2_c7" = D src=3D"http://www.mediatools.cl/emailer/navidad/img/nav_r2_c7.gif" =. width=3D"12" height=3D"366" border=3D"0"></td>           <td><img =A src=3D"http://www.mediatools.cl/emailer/navidad/img/spacer.gif" = + width=3D"1" height=3D"9" border=3D"0"></td> 
         </tr>          <tr>=20 I           <td colspan=3D"2" bgcolor=3D"#FFFFFF"><img name=3D"nav_r3_c5" = A src=3D"http://www.mediatools.cl/emailer/navidad/img/spacer.gif" = + width=3D"1" height=3D"1" border=3D"0"></td>            <td><img =A src=3D"http://www.mediatools.cl/emailer/navidad/img/spacer.gif" = , width=3D"1" height=3D"15" border=3D"0"></td>
         </tr>          <tr>=20 I           <td colspan=3D"2" bgcolor=3D"#FFFFFF"><img name=3D"nav_r4_c4" = D src=3D"http://www.mediatools.cl/emailer/navidad/img/nav_r4_c4.gif" =G width=3D"345" height=3D"75" border=3D"0" usemap=3D"#nav_r4_c4Map"></td> 6           <td rowspan=3D"3" bgcolor=3D"#FFFFFF"> </td>           <td><img =A src=3D"http://www.mediatools.cl/emailer/navidad/img/spacer.gif" = , width=3D"1" height=3D"75" border=3D"0"></td>
         </tr>          <tr>=20 D           <td rowspan=3D"2" colspan=3D"2" bgcolor=3D"#FFFFFF"> </td>           <td><img =A src=3D"http://www.mediatools.cl/emailer/navidad/img/spacer.gif" = , width=3D"1" height=3D"12" border=3D"0"></td>
         </tr>          <tr>=20 ;           <td bgcolor=3D"#FFFFFF"><img name=3D"nav_r6_c3" = A src=3D"http://www.mediatools.cl/emailer/navidad/img/spacer.gif" = + width=3D"1" height=3D"1" border=3D"0"></td>            <td><img =A src=3D"http://www.mediatools.cl/emailer/navidad/img/spacer.gif" = , width=3D"1" height=3D"15" border=3D"0"></td>
         </tr>          <tr>=20 %           <td bgcolor=3D"#FFFFFF">=20 A             <table width=3D"124" border=3D"0" cellspacing=3D"0" = ! cellpadding=3D"0" height=3D"177">                <tr>=20 #                 <td width=3D"122" = J background=3D"http://www.mediatools.cl/emailer/navidad/img/emailer1.gif">=@ <object classid=3D"clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" =J codebase=3D"http://download.macromedia.com/pub/shockwave/cabs/flash/swfla=7 sh.cab#version=3D5,0,0,0" width=3D"124" height=3D"177"> )                     <param name=3Dmovie = B value=3D"http://www.mediatools.cl/emailer/navidad/swf/fx_nav.swf">7                     <param name=3Dquality value=3Dhigh>                      <embed =A src=3D"http://www.mediatools.cl/emailer/navidad/swf/fx_nav.swf" =  quality=3Dhigh =J pluginspage=3D"http://www.macromedia.com/shockwave/download/index.cgi?P1_=G Prod_Version=3DShockwaveFlash" type=3D"application/x-shockwave-flash" =  width=3D"124" height=3D"177">                      </embed>=20                     </object></td>               </tr>              </table>           </td> B           <td colspan=3D"3" bgcolor=3D"#FFFFFF" valign=3D"top">=20B             <table width=3D"100%" border=3D"0" cellspacing=3D"0" = cellpadding=3D"8">               <tr>=20 C                 <td align=3D"center"><font size=3D"3"><b><i><font = B color=3D"#000066" face=3D"Verdana, Arial, Helvetica, sans-serif" = size=3D"4">Este=20,                   a=F1o ahorre en tarjetas =) navide=F1as...</font></i></b></font></td>                </tr>                <tr>=20 +                 <td align=3D"center"><img = D src=3D"http://www.mediatools.cl/emailer/navidad/img/nav_r8_c5.gif" =! width=3D"303" height=3D"42"></td>                </tr>                <tr>=20 D                 <td align=3D"center"><b><i><font color=3D"#000066" =C size=3D"4" face=3D"Verdana, Arial, Helvetica, sans-serif">OFERTA=20 !                   NAVIDE=D1A <br> B                   USD $38.00 x 10.000 env=EDos</font></i></b></td>               </tr>              </table>           </td>            <td><img =A src=3D"http://www.mediatools.cl/emailer/navidad/img/spacer.gif" = - width=3D"1" height=3D"180" border=3D"0"></td> 
         </tr>          <tr>=20 ?           <td bgcolor=3D"#FFFFFF" colspan=3D"4" height=3D"70" = G valign=3D"bottom"><font size=3D"1" color=3D"#000066" face=3D"Verdana, = ( Arial, Helvetica, sans-serif">Emailer=20F             es la soluci=F3n profesional de E-mailing que Ud. estaba =
 esperando,=20 B             integrando texto, gr=E1ficas, sonido y movimiento.<br>             <br>G             Emailer es un motor de env=EDo de correo masivo basado en =  Web y NO comercializa=20A             bases de datos de correos electr=F3nicos.</font></td>            <td><img =A src=3D"http://www.mediatools.cl/emailer/navidad/img/spacer.gif" = , width=3D"1" height=3D"60" border=3D"0"></td>
         </tr>          <tr>=20 '           <td><img name=3D"nav_r9_c1" = D src=3D"http://www.mediatools.cl/emailer/navidad/img/nav_r9_c1.gif" =- width=3D"12" height=3D"12" border=3D"0"></td> 5           <td colspan=3D"5"><img name=3D"nav_r9_c2" = D src=3D"http://www.mediatools.cl/emailer/navidad/img/nav_r9_c2.gif" =. width=3D"515" height=3D"12" border=3D"0"></td>'           <td><img name=3D"nav_r9_c7" = D src=3D"http://www.mediatools.cl/emailer/navidad/img/nav_r9_c7.gif" =- width=3D"12" height=3D"12" border=3D"0"></td>            <td><img =A src=3D"http://www.mediatools.cl/emailer/navidad/img/spacer.gif" = , width=3D"1" height=3D"12" border=3D"0"></td>
         </tr>        </table>	     </td>    </tr>  </table> <map name=3D"nav_r4_c4Map"> 9   <area shape=3D"rect" coords=3D"24,6,267,54" href=3D"#"> @ </map><table border=3D'0' width=3D'100%'><tr><td><center><font =H face=3D'arial' size=3D'1' color=3D'black'>Si no desea volver a recibir = este mail, oprima </font><a = K href=3D"http://www.emailer.cl/unsuscribe.asp?num=3D865832743645058&sess=3D= C 75401178015&mail=3DInfo-VAX@mvb.saic.com" target=3D"_blank"><font = 6 face=3D'arial' size=3D'1' color=3D'black'>AQU=CD</a> =: (unsuscribe)</font></center></td></tr><tr><td><center><a =% href=3D"http://www.emailer.cl"><img = ; src=3D"http://www.emailer.cl/img/logo_emailer_bottom.gif" = = border=3D"0"></a></center></td></tr></table></body>=0D</html> . ------=_NextPart_000_3DA1C_01C1864E.33A0ECC0--   ------------------------------  % Date: Sun, 16 Dec 2001 14:42:20 -0800 ' From: David Mathog <mathog@caltech.edu> ) Subject: Re: Compaq now a takeover target + Message-ID: <3C1D234C.5F962676@caltech.edu>    John McLean wrote: >  > Tim Llewellyn wrote:O > > how much HPUX compared to Solaris is out there in academia? Surely a reason N > > for Solaris' strong apps portfolio is the number of graduates with Solaris
 > > exposure?  > I > Yeah.  And we all saw the long-term advantage that Unix gained over VMS D > by getting into academia.  The graduates were familiar with it and! > recommended it for their sites.   F I'm sorry to report that the average undergraduate no longer knows the
 posterior end G of his digestive system from a hole in the ground when it comes to Unix 
 - and lookF where I'm posting this from.  They do still use Unix systems, but they don't know it, becauseB they have no idea what OS is sitting at mail.myuniversity.edu, and Eudora, Netscape, and Outlook @ Express aren't going to tell them. The CS guys are obviously the exception, as are mostH students who have worked in labs, but the rest of them only know Windows and Macs and they F will look at you as if you've got three heads if you suggest that they log onto a machineC through telnet and run a command line program.   Software which has 
 neither a web E interface and/or native GUI on Windows and/or Mac just isn't anything D they want to deal with.  Considering the ubiquity of computers these daysF it's also ironic that fewer and fewer of them can program in C (forget about Fortran). F The bright side, if you can call it that, is that a lot of them can do amazing things in G Excel and Mathemetica, and some even do Perl.  Don't ask me how anybody  can make- sense of Perl without having learned C first.   H Anyway, the point being, that all most of these kids know is Windows and Mac, and as there D are no big Mac servers, when they have to recommend something in the future, they will E probably recommend Windows, no matter how inappropriate it may be for  the problem.   Regards,   David Mathog mathog@caltech.edu   ------------------------------   Date: 16 Dec 2001 13:27:51 CDT= From: wayne@tachysoft.xxx.524703.killspam.00bd (Wayne Sewell) ) Subject: Re: Compaq now a takeover target . Message-ID: <ukRbHdwDq6th@tachxxsoftxxconsult>  t In article <Qd3T7.13919$Sj1.8594113@typhoon.ne.mediaone.net>, "Terry C. Shannon" <terryshannon@mediaone.net> writes:@ > "John McLean" <mcleanj@swissonline.delete.ch> wrote in message0 > news:3C1C72D5.E08FBF6@swissonline.delete.ch... >> >> >> JF Mezei wrote: >> > >> > "Terry C. Shannon" wrote:J >> > > I see your point, but I would prefer to characterize IBM as the BMW >> > > purveyor. >> >F >> > Nop, IBM is the purveyor of Cadillacs.  Old, big, heavy, but very > comfortable,I >> > works everytime and is a luxury. But little known to most, there are 	 > Caddies 5 >> > that zing and do provide surprising performance.  >> >H >> > Digital was Rolls Royce. The parts of rolls were sold with the name > purchased 4 >> > by that common car maker : Volkswagon (Compaq). >> >M >> > Had it been Chrysler that had bought Daimlmer Benz, than Chrysler=Compaq  > and J >> > Daimler=Digital. Mercedes has great quality, reliability, but not the	 > fastest J >> > car in town, but overall great value sold at a premium because of its > name8 >> > Chrylser was best known for making its K-car boxes. >> >> >> ...and Microsoft ???  > < > Oh, that's a tough one. I'm torn between Yugo and Trabant.  + Skateboard with most of the wheels missing?t   -- dO ===============================================================================eM Wayne Sewell, Tachyon Software Consulting  (281)812-0738  wayne@tachysoft.xxxw: http://www.tachysoft.xxx/www/tachyon.html and wayne.html  K change .xxx to .com in addresses above, assuming you are not a spambot  :-)UO ===============================================================================eN Sparky (from Bring It On): "In cheerleading, we throw people in the air.  Fat  	people don't go as high."   ------------------------------  % Date: Mon, 17 Dec 2001 00:47:58 +0100a( From: Bernd Paysan <bernd.paysan@gmx.de>) Subject: Re: Compaq now a takeover targetm& Message-ID: <3C1D32AE.CEAAA7DD@gmx.de>   Hank Oredson schrieb:a > > ...and Microsoft ??? >  > Citroen of course :-)   E In a world where Citroen sells only 2CVs ;-). Actually, the inventive E part of Citroen that put hydropneumatics into cars, and had the firstrF front-driven car, is long past. Citroen nowadays is only one brand forG Pegeuot plattforms, and except the hydropneumatics in the most luxuroustA models, there's nothing special (even the 2CV was discontinoued).e   -- e Bernd Paysan7 "If you want it done right, you have to do it yourself"w http://www.jwdt.com/~paysan/   ------------------------------  % Date: Mon, 17 Dec 2001 00:59:00 +0100-( From: Bernd Paysan <bernd.paysan@gmx.de>) Subject: Re: Compaq now a takeover targeta& Message-ID: <3C1D3544.64E3AB3D@gmx.de>  ! david20@alpha2.mdx.ac.uk schrieb:nP > I've never used HP-UX or IBM's AIX. However looking at bug reports leads me toL > suspect that the quality of HP-UX is about on a par with Solaris ie pretty
 > abysmal.  C I used HP-UX as student. When I installed Linux on my 486 (in earlyrD 1995), I was positively surprised. Given how much Linux has advanced? since back then, I hope that HP-UX has advanced a lot, too ;-).6  D I prefer a self-cooked meal over a burger or a pizza any day. If youF compare commercial OS offerings to restaurants, Linux is something youG get from an amateur hobby cook. The quality might differ, and new cooks.A need training, but the average quality easily exceeds the average  commercial offering.   -- n Bernd Paysan7 "If you want it done right, you have to do it yourself"g http://www.jwdt.com/~paysan/   ------------------------------  + Date: Mon, 17 Dec 2001 02:37:09 +0000 (UTC)a0 From: "Rupert Pigott" <Darkb00ng@btinternet.com>) Subject: Re: Compaq now a takeover targetr/ Message-ID: <9vjlok$2nm$1@helle.btinternet.com>l  3 Bernd Paysan <bernd.paysan@gmx.de> wrote in message8  news:3C1D32AE.CEAAA7DD@gmx.de... > Hank Oredson schrieb:/ > > > ...and Microsoft ??? > >e > > Citroen of course :-)3 >CG > In a world where Citroen sells only 2CVs ;-). Actually, the inventivec  G Bah everyone denegrates 2CVs... But in truth they are excellent motors,>H especially considering the age of the design. Everything is very easy toI work on, very easy to fix, spares are readily available. With a couple of3J people you can easily lift the engine out without any hoists. Not that youF ever need to because you can take off the bonnet (hood) and wings veryK easily anyways. The ONLY thing which is a PITA are the inboard disc brakes.' :)  L Good fuel economy, and I looked at the emissions, on my 2CV they were a mereE 20% of the limit. It's just design to a different philosophy from thedI plastic laden jellymoulds of today. They certainly don't strike me as the#* Microsoft of computing, maybe the CP/M. :)   Cheers,b Rupert   ------------------------------   Date: 17 Dec 2001 03:02:33 GMT& From: peter@abbnm.com (Peter da Silva)) Subject: Re: Compaq now a takeover targetl% Message-ID: <9vjn89$d1a@web.nmti.com>t  4 In article <3C1C72D5.E08FBF6@swissonline.delete.ch>,3 John McLean  <mcleanj@swissonline.delete.ch> wrote:  > ....and Microsoft ???   	 "Ginger".    --  +  `-_-'   In hoc signo hack, Peter da Silva. E   'U`    "A well-rounded geek should be able to geek about anything."tL                                                        -- nicolai@esperi.org          Disclaimer: WWFD?   ------------------------------  % Date: Mon, 17 Dec 2001 00:09:14 -0500i- From: JF Mezei <jfmezei.spamnot@videotron.ca>a) Subject: Re: Compaq now a takeover targeth* Message-ID: <3C1D7DF9.AF505C@videotron.ca>   IsraelRT wrote:/ > >...and Microsoft ???/ > D > Microsoft = Kia / Daewoo but with better marketing and management.  F No, Microsoft is Lada or Yugo or Trabant. Very inexpensive to buy, but requires a LOT of maintenance.   ------------------------------  % Date: Mon, 17 Dec 2001 00:23:00 -0500i- From: JF Mezei <jfmezei.spamnot@videotron.ca>i) Subject: Re: Compaq now a takeover target , Message-ID: <3C1D8133.C2A15B6C@videotron.ca>   "Terry C. Shannon" wrote:/H > You know this, I know this, pimply youths know this, but it seems that% > Compaq marketing doesn't know this.c  K Compaq marketing knows this. But they will be pushing Wintel boxes to homestL and schools. It is clear that Compaq has absolutely no intentions of growingL VMS beyond is small niche. All indications lead to a slow widthdrawal of VMS by narrowing the niche markets.s  H It used to be 6 markets, but now I think it is down to a couple, right ?   ------------------------------  % Date: Sun, 16 Dec 2001 20:11:26 +0000r% From: "a.carlini" <arcarlini@iee.org>c) Subject: Re: Crash (SYSDUMP.DMP) questiont' Message-ID: <3C1CFFEE.4EE280F1@iee.org>    Lorin Ricker wrote:=H > Question:  What can I look at (e.g., in SYSGEN) to be *certain* that a6 > crash-dump will go to SYSDUMP.DMP, not PAGEFILE.SYS?  % Given that you wish to be *sure* that % you will catch a crash dump when this # fairly rare event occurs, you read i and implement the advice in the % other posts. Then you pick a suitable># time and you go and try a dry run -h just to be sure :-)c  ) BTW: Even if it goes to PAGEFILE.SYS, youD! can still use SDA COPY can't you?>   Antonio/   --     --------------- - Antonio Carlini             arcarlini@iee.orgg   ------------------------------  # Date: Mon, 17 Dec 2001 00:18:07 GMTm- From: "John E. Malmberg" <wb8tyw@qsl.network> ) Subject: Re: CXX and the Hobbyist licenseD* Message-ID: <3C1D3F9C.6090409@qsl.network>   Dave Parsons wrote:=    > Hi,  >C  > Does anyone know whether DEC CXX is available under the Hobbyisti#  > programme, and if so from where?4  G The Hobbyist program provides the license, but apparently the software D/ did not make the cut for fitting on the CD-ROM.o  F  > I have CXX-V in the layered products license but I can not find any  > software for it on the CD.f  E You will either need to purchase a media copy, or find a local friend=	 with one.o  G  > I have been round & round the Compaq site and the nearest I came wasm$  >  a Personal version for ca $2000.  E Be careful about the part numbers.  That could be for a license only DF with no media or documentation.  It's the media and documentation kit 5 that you are looking for to use with a hobby license.    -John2 wb8tyw@qsl.network Personal Opinion Only#   ------------------------------  % Date: Sun, 16 Dec 2001 14:16:02 -0800/' From: David Mathog <mathog@caltech.edu>e Subject: DLT sounds0+ Message-ID: <3C1D1D22.4D68A5D2@caltech.edu>/  E One of our DLT 4000s has started making a loud whirring sound when it3 moves the tape."G (It sounds rather a lot like a sewing machine.) Sometimes when it firsto startsH up it also makes a bit of a banging noise which goes away after a minute	 or two.  mD Even so, the tapes it writes validate ok.  Is this one of those "its getting oldpE and noisy" sorts of problems or is it more of the "it's about to drop  dead" variety?  H Admittedly this has nothing to do with VMS, but I know a lot of you have DLT drives."   Thanks,3   David Mathog mathog@caltech.edu   ------------------------------  % Date: Sun, 16 Dec 2001 23:23:01 +0100t1 From: John McLean <mcleanj@swissonline.delete.ch>o Subject: Re: DLT sounds/5 Message-ID: <3C1D1EC5.731BC879@swissonline.delete.ch><   David Mathog wrote:  > X > One of our DLT 4000s has started making a loud whirring sound when it  moves the tape.Q > (It sounds rather a lot like a sewing machine.) Sometimes when it first  starts=S > up it also makes a bit of a banging noise which goes away after a minute  or two.mS > Even so, the tapes it writes validate ok.  Is this one of those "its  getting old V > and noisy" sorts of problems or is it more of the "it's about to drop dead" variety? > V > Admittedly this has nothing to do with VMS, but I know a lot of you have DLT drives. > 	 > Thanks,  >  > David Mathog > mathog@caltech.edu    H I'd be looking for a nylon cog that has gone cactus.  Could be somethingH simple as a split pin (do they have them to hold the cogs ?) or as nasty& as a cog tooth gone missing in action.  D If its out of warranty, take it apart, ...see what you can find  :-)     John McLeanm   ------------------------------  % Date: Sun, 16 Dec 2001 15:00:59 -0800n' From: David Mathog <mathog@caltech.edu>= Subject: Re: DLT sounds + Message-ID: <3C1D27AB.AF212080@caltech.edu>w   David Mathog wrote:/ > G > One of our DLT 4000s has started making a loud whirring sound when itm > moves the tape.dI > (It sounds rather a lot like a sewing machine.) Sometimes when it firstx > startsJ > up it also makes a bit of a banging noise which goes away after a minute	 > or two.   5 Sorry to follow up on my own post.  It finally struck 4 me that maybe the tape was somehow not fully loaded,1 so I gave the cartridge load lever a little shove 9 and it went "Clunk" and all the odd noises instantly wente5 away and the normal tape sounds returned.  Apparently 7 this particular unit (maybe all DLT4000s and I've nevero2 hit this state before) has a position for the tape5 release handle which is good enough to tell the drive15 that the tape is loaded, but not quite good enough tof really lock the tape in place.   Regards,   David Mathog mathog@caltech.edu   ------------------------------  # Date: Sun, 16 Dec 2001 23:07:04 GMTm) From: martin.hunt@inl.co.nz (Martin Hunt)"# Subject: Re: global foreing command 7 Message-ID: <3c1d28e6.12397536@news.wlg.netlink.net.nz><  , On Fri, 14 Dec 2001 00:39:17 -0500, JF Mezei% <jfmezei.spamnot@videotron.ca> wrote:f   >Phillip wrote:  >>  D >> I have figured out how to set up foreing commands with the cmd :=L >> full:[spec]file.exe at the DCL command line, but I have yet to figure out: >> how to figure out how to add it globaly for all users.  >i- >nitpick   command :== "$full:[spec]file.exe"g  ? And I was wondering what a "foreing" command was - I guess that  "foreign" was intended.F   > C >The easiest way to add it to all users is to add its definition inlA >SYS$MANAGER:SYLOGIN.COM which gets executed when anyone logs in.m     ---  Martin Hunts Systems Administratorn Independent Newspapers Limited
 Wellington New Zealand    ------------------------------  # Date: Sun, 16 Dec 2001 19:38:30 GMTb7 From: "Patrick J. Gleason" <ora68@nehemiah.idkcomp.com>m, Subject: I would like to lease time on a VAX4 Message-ID: <3C1CF83E.6D63D8B2@nehemiah.idkcomp.com>  = I have a large internet application for VMS which has been inc developmentiD for three years on an Alpha.  Customers are asking for a VAX versionB now.  Does anyone know of a service where I could buy some time on a VAX with DEC C 6.2 or newer?  ? I don't need a lot of time because the program has already beenD extensivelyDH tested and debugged on an Alpha.  Hence, I don't think I can justify the costE of buying and maintaining a VAX along with the Alpha.  I just need to C recompile and link.  I even have a customer who will let me test on7 theirr% VAX, but they do not have a compiler.a   ------------------------------  % Date: Sun, 16 Dec 2001 16:06:27 -0500 ' From: Howard S Shubs <howard@shubs.net>e0 Subject: Re: I would like to lease time on a VAX< Message-ID: <howard-7E2F68.16062716122001@enews.newsguy.com>  4 In article <3C1CF83E.6D63D8B2@nehemiah.idkcomp.com>,9  "Patrick J. Gleason" <ora68@nehemiah.idkcomp.com> wrote:6  A > I don't need a lot of time because the program has already been<
 > extensively J > tested and debugged on an Alpha.  Hence, I don't think I can justify the > costG > of buying and maintaining a VAX along with the Alpha.  I just need to8E > recompile and link.  I even have a customer who will let me test ong > theira' > VAX, but they do not have a compiler.o  O Given what a small VAX would cost these days ($nnn at most), it might be worth aB your time.  The problem would be the cost of the software.  <sigh> -- i Howard S ShubsD "Run in circles, scream and shout!"  "I hope you have good backups!"( Golf vs Bug: VW has been cutting corners   ------------------------------  % Date: Mon, 17 Dec 2001 00:07:38 +01001 From: Dirk Munk <munk@home.nl>0 Subject: Re: I would like to lease time on a VAX' Message-ID: <3C1D293A.9C64B13F@home.nl>.  K I didn't check this, but if I'm not mistaken you can compile and  / or linkoD VAX software on a Alpha. Could be a compiler and link option switch.   Regards,   Dirk   "Patrick J. Gleason" wrote:   ? > I have a large internet application for VMS which has been inw
 > developmentoF > for three years on an Alpha.  Customers are asking for a VAX versionD > now.  Does anyone know of a service where I could buy some time on  > a VAX with DEC C 6.2 or newer? >tA > I don't need a lot of time because the program has already beens
 > extensivelyeJ > tested and debugged on an Alpha.  Hence, I don't think I can justify the > costG > of buying and maintaining a VAX along with the Alpha.  I just need toeE > recompile and link.  I even have a customer who will let me test onu > theirs' > VAX, but they do not have a compiler.t   ------------------------------  % Date: Sun, 16 Dec 2001 20:03:11 +0000s% From: Alan Greig <a.greig@virgin.net>o, Subject: Re: More about Alpha and the merger* Message-ID: <3C1CFDFE.734868D5@virgin.net>   Duane Sand wrote:   C > Yeah.  The current sales (w/o any roadmap surgery) already sucked.D > to the point where all Alpha manufacturing could be easily handledD > by a minor lower-wage secondary factory in U.K that was originally) > intended to handle only European sales.a >   P I think you much malign "DEC Ayr" The "AY" manufacturing prefix on DEC parts hasH been around for a long time. The Microvax 3100 was even designed at Ayr.  N Ayr, Livingston, Edinburgh all once formed a coherent part of DEC in Scotland.M The Alpha chip fab in Edinburgh, Software Engineering at Livingston (SpiralogwN etc) and the Ayr manufacturing plant. All within about 50 miles of each other.  P It is not a "minor lower wage secondary factory" but rather one of the remaining# parts of DEC's one time excellence.n   > = > The company began with a manufacturing plan to quickly movea> > a LOT more Wildfires than what transpired.  Perhaps the realA > revenue expectation/hope was far higher than the reported goal.. >./ >    -- Duane Sand, not speaking for Compaq etc:   --
 Alan Greig   ------------------------------  % Date: Sun, 16 Dec 2001 23:19:54 +0100<1 From: John McLean <mcleanj@swissonline.delete.ch>T, Subject: Re: More about Alpha and the merger5 Message-ID: <3C1D1E0A.E0694DB9@swissonline.delete.ch>    Duane Sand wrote:e > =1   > John McLean wrote: > > ... snip ...J > > At the end of June, Terry Shannon stated at least twice that he belie= ved D > > that the Alpha termination notion had originated about mid-June. > =   H > Terry's sometimes wrong.  Completion !=3D origination.  And 10 days???  E Sorry, I did Terry a disservice.  He said start of June.  I know it'stD not important to othe things you said, but let me be correct on this point. > =e  J > I'm aware of three facts showing the Alpha axe began falling months ear= lier:  > =a  E > 1. My VP saying that the negotiations with Intel were taking monthsdJ > longer to conclude than originally expected.  (And from earlier dealing= s J > with Intel, I've learned how very long it takes to negotiate even trivi= al > things with Intel.)n >uH > 2. Winkler's Jan 26 gaffes saying Himalaya was to be delivered on IPF.  G That might of have only been a fore-runner to Alpha plans.  Winkler has H been known to speak out of line with Compaq thinking on other occasions.  =  B > 3. Some of my co-worker friends were the ones doing a top-secretF > contingency study of changing to an IPF port, mentioned in Winkler's@ > Jan 26 statements as a small team working on Himalaya for IPF.J > (For me, this detail confirms the general accuracy of Greig's reporting=  C > of what Winkler said, in now-unavailable parts of the Jan 26 live= > coverage.)  ? As you have said previously companies should make these kind ofyA assessements on an ongoing basis.  As you said here, "contingency E study".  It doesn't mean that any decision had been made, but it doesa, mean that alternatives were being evaluated.    > > Beyond that, my recollection is that the Himalaya division'sB > very good profits had been barely covering Alpha division losses > for several quarters.o  G Here's revenue (for what it's worth) and income for the last 7 quarters  for "Enterprise"$ (all figures in millions of dollars)  J Q3-01:  revenue=3D$2376, income=3D -$104    (first full quarter after Alp= ha
 announcement)a% Q2-01:  revenue=3D$2711, income=3D$74f& Q1-01:  revenue=3D$2908, income=3D$132J Q4-00:  revenue=3D$4111, income=3D$581  (using revised segments as per Ap= ro 2001) / Q3-00:  revenue=3D$3811, income=3D$493  (ditto) / Q2-00:  revenue=3D$3441, income=3D$383  (ditto)/& Q1-00:  revenue=3D$2953, income=3D$262  G Yes we don't have the *income* break down but we can find the followings. comments in the quarterly financial statements  B (Sep 2000) "Business Critical Servers revenue increased during theF quarter primarily due to increased sales of ALPHASERVER(TM) GS systems2 offset by lower Compaq HIMALAYA(TM) system sales."  B (Apr 2001) (with respect to Enterprise Computing) "Such growth [inE Storage] was offset primarily by lower revenue from industry standard,B servers as the economic slowdown in the United States led to lowerD technology spending and a competitive pricing environment."  (ie. noF mention of Business Critical servers, presumably because they achieved nothing notable).i  F perhaps you are thinking of a June 00 statement (from almost 18 months	 back) ...t  F "Business Critical Server revenue declined during the quarter and year to date periods primarilyo= due to product transition and component shortages for the newr AlphaServer=99 GS product line.gE As a result, Business Critical Servers experienced lower than plannede shipments. PartiallyK offsetting this decline were strong sales of Compaq NonStop=99 Himalaya=99=:  	 systems."o    =  > > The delayed delivery and modest sales of Wildfire was likelyD > the real killer, the final disappointment.  Last week I toured the: > immense empty factory in Fremont where Wildfires for the; > North American market were to be built. We expected to ber< > selling huge numbers of them.  There was some long-pent-up: > demand, but then nothing.  So Wildfire manufacturing was> > severely downsized to match the small demand, and off-shored* > to a small secondary factory in the U.K.  C I was led to believe the figures were rather higher and that Galaxyc@ systems were selling quite well.  (Admittedly their architectureE probably reduces income for Compaq because it means that the customera) doesn't buy several individual machines.)A  D As Alan Greig has indicated, there could be more than one reason forG manufacturing them in Scotland.  Don't forget that European labour lawseE make it much harder to retrench people when a company wants to reducetF its headcount.  Give the Scots some productive work to do and boot theH Fremont people out the door doesn't sound all that nice, but it may have been a factor.  =  = > I think Alpha fans keep reaching for extraneous reasons forC; > why Alpha was killed.  It must be incompetent marketeers.i? > It must be some twisted Microsoft conspiracy.  It must be theoA > other evil Borg, Intel.  It must be incompetent and destructives= > and morally corrupt management.  It must be Carly.  It muste@ > be some huge payoff.   Yeah, right.  It couldn't be that DEC's= > Alpha business plan based on chip technology leadership was ? > a loser (or an expensive tie) in a world of 2GHz consumer PCs-A > and exponential fab investments.  Being beaten at its own game!0= > Oh, the shame!  It must be all those other reasons instead!:  ; Sarcasm doesn't become you when we're having an intelligentd
 discussion...s  =    > > The Alphacide/Trees upheaval became leaked to my level in my? > group about 5 days before the public announcement on June 25.dE > By this time, it was being handled in a rush, to do whatever triageaD > we could do with our broken product plans, and to prepare a publicA > roll-out of the new roadmap in an effective positive way.  WithuC > continued strong need-to-know secrecy within our workgroups untilB> > the public announcement.  The secrecy was explained to us as= > controlling access to and contamination by "material insidep? > information" that was expected to wildly affect stock prices.BB > (But then at announcement day, stock prices didn't move at all.)@ > My VP said yes when I asked if all this secrecy was at Intel's
 > insistence.h  > This is still inconclusive with respect to a decision date forH Alpha-to-Intel.  It appears that it could have been any time prior to 20G June.  Evaluations before that, and discussions/negotiations with Intel E but when was it decided to accept the terms & conditions of Intel, inc6 other words when did someone say "Yes, we'll do it." ?    D > My impression is that Intel is partially financing the development< > of IPF versions of Himalaya, VMS, and Tru64, and is givingE > Compaq additional discounts on Intel chips, and will be subsidizings@ > marketing of IPF systems.  Stuff that doesn't directly show upA > on Intel quarterly reports now.  (If Tru64 gets canned, perhapst8 > that would only save Intel some money, not Compaq/HP.)  E I find it curious that the only mention by Intel is in the subsequento> financial statement which made a one-sentence reference to the@ "transfer" of Alpha.  I would have thought that if any money wasF involved Intel would be required to file a submission with the SEC andC to let their stockholders know of this "material event" (to use SECt
 terminology).e  = Now does financing the development versions of the OSes, pluswG subsidizing marketing qualify as a "deductible business expense" ?  YoudH know, money spent to make other money.  Does Intel get any such expenses as a tax break ?  F If they do, then didn't Compaq get sizable tax breaks with Alpha R & D ??    =    @ > Complicated deals with Intel are not made in a day or two likeH > you imagine.  It was not a simple quick case of "I'll cut off the nose& > on my face.  Is that okay with you?"  B I didn't mean a day or two :-)  but given the relatively clear-cutH nature of the deal and what might be a small degre of haggling, I didn'tG see why it should take more than a few weeks, especially if Compaq werer" hell-bent on getting rid of Alpha.  / BTW, do you know if Alpha was offered to AMD ??     =  D > I agree that a merger of enterprise divisions would be impractical; > if PA-RISC, Alpha, and IPF were all carried forward, plus:= > non-IPF versions of MPE, VMS, Himalaya, and multiple Unixes: > of opposite endiannesses.1  H Well, it may have started that way but there would have been culling andH convergence at some point down the track.  With everything now targettedG for IPF the culling and convergence - and its justification - is ratherb more simple.  =  ; > Note that 4-10 months ago, HP announced that PA-RISC chipp: > development would cease after some version, and recently9 > announced that HP's chip design team members were to bei< > offered positions at Intel in a similar manner to Compaq's@ > shedding of Alpha chip designers.  Shortly after the HP/Compaq? > merger plan was announced, HP abruptly announced an EndOfLife-< > date for supporting their MPE operating system.  All thoseA > actions are consistent with trying to restructure themselves todA > be profitable, regardless of whether the merger happens or not. 1 > Very parallel to Compaq's problems and actions.t  H But just where can we draw the line between individual restructuring andD restructuring with a possible merger in mind ??  Who is to know what1 Capellas and Fiorina were talking about and when.a  =    =   > > ... snip ...D > > if the merger went ahead then it didn't matter greatly if CompaqF > > lost money to Intel (and basically had to pay Intel to take Alpha) > =u   > huh???  and huhh??? E > Intel didn't "take Alpha" and certainly wasn't paid to do anything.o9 > Compaq killed off future Alpha chips and Alpha markets.a@ > Intel bought a crack chip designer team and top compiler team.@ > Intel bought the rights to use Alpha circuit patents freely in= > IPF implementations without being sued again.  Intel boughtn= > Compaq's commitment to use IPF rather than Alpha or PowerPCh: > or whatever chips in Compaq's future enterprise systems.> > There is no doubt in my mind that Intel is paying Compaq big? > time for all those things, even if the payment isn't visible.g    H The only word that we have that Intel are going to support some level ofH promotion at some undefined date is a press release from Compaq, there'sG been nothing from Intel (who of course will benefit in a large way fromnF such promotion).  Compaq was the company who were reassuring customersE about the future of Alpha on NT just weeks before terminating it; andsG about Alpha in Alphaservers just weeks before announcing termination. =e  G I'll only believe that Intel are compensating Compaq in any way when it  actually happens.s  B > John, I don't understand your theory about some huge "in-processA > technology" debit or credit dating from the Digital acquisition @ > that still has to be paid by someone. For me to understand it,A > please explain it the simple way you would to a naive relative.n  E Okay.  In simple terms the development of Alpha to this point in timea> was surely worth something and that something was probably not insignificant.  J =46rom Compaq's 1998 Annual financial report where the purchase of Digita= l: was discussed.  F "Approximately $3.2 billion of the purchase price represents purchasedH in-process technology that had not yet reached technological feasibility@ and had no alternative future use.  Accordingly, this amount wasA immediately expensed in the Consolidated Statement of Income upon A consummation of the acquisition.  The value assigned to purchasedtF in-process technology, based on a valuation prepared by an independentE third-party appraisal company, was determined by identifying research-B projects in areas for which technological feasibility had not beenD established, including UNIX/OpenVMS ($1.6 billion), NT Systems ($800F million), storage ($2.7 billion) and others ($600 million).  The value? was determined by estimating the costs to develop the purchasednG in-process technology into commercially viable products, estimating the1D resulting net cash flows from such projects, and discounting the net* cash flows back to their present value.  "  
 And later =85   >  "Compaq plans to use cash to develop the purchased in-processF technology related to the Digital acquisition into commercially viableE products.  This primarily consists of the completion of all planning, B designing, prototyping, high-volume manufacturing verification andH testing activities that are necessary to establish that a product can be@ produced to meet its design specifications, including functions,H features and technical performance requirements.  Bringing the purchasedE in-process technology to market also includes developing firmware ands? diagnostic software, device driver development, and testing the C technology for compatibility and interoperability with commercially0G viable products.  As of the date of acquisition, the estimated costs to:? be incurred to develop the purchased in-process technology into1F commercially viable products totaled approximately $3.1 billion in theH aggregate through the year 2005.  The remainder to be spent is estimatedH to be: $510 million in 1999, $660 million in 2000, $630 million in 2001,H $520 million in 2002, $400 million in 2003, $210 million in 2004 and $90 million in 2005."     @ There would have been a variety of items which were part of thisH in-process technology, such as the Storage Area Network (SAN) stuff that9 has (IIRC) first been released under Compaq, not Digital.   G A sizeable component of this technolgy would have been Alpha, as it waswB in the state at the time.  If my recollection is correct, an Alpha< release was running about 12 months late and logic says thatG considerable work had already been done on it, work that had a value torD any purchaser.  Undoubtedly there was also work to be done, so Alpha? development was part of that $3.1 billion of development costs.l  C We are in the same situation with Alpha now.  Considerable work has D apparently done on EV8 and if Intel is going to reap the benefits ofF that work because they now own that expertise and knowledge, then they should be paying for it.  G By deferring any compensation whatsoever until some time in the future, D Compaq has not translated that into any immediate income - just someE general notion of sharing marketing costs - and this means that HP is E paying less for Compaq right now than it otherwise would have done if?$ Compaq had the money from Intel now.     John McLeanh   ------------------------------  # Date: Sun, 16 Dec 2001 23:22:53 GMTc4 From: "Terry C. Shannon" <terryshannon@mediaone.net>, Subject: Re: More about Alpha and the merger= Message-ID: <h1aT7.15350$Sj1.8863934@typhoon.ne.mediaone.net>   > "John McLean" <mcleanj@swissonline.delete.ch> wrote in message/ news:3C1D1E0A.E0694DB9@swissonline.delete.ch...a     Duane Sand wrote:: >1 > John McLean wrote: > > ... snip ...L > > At the end of June, Terry Shannon stated at least twice that he believedD > > that the Alpha termination notion had originated about mid-June. >(F > Terry's sometimes wrong.  Completion != origination.  And 10 days???  E Of course I'm sometimes wrong. My first marriage is (was) prima facie B evidence of wrongheadedness. So no disservice implied or imagined.  E Sorry, I did Terry a disservice.  He said start of June.  I know it'sgD not important to othe things you said, but let me be correct on this point.  G The origination-completion period to which you refer is WRT the "Trees"nJ marketing campaign. Initial collateral development began perhaps two-three( weeks prior to the June 25 announcement.  D Discussions with multiple well-placed folks indicate that the actualI decision to abandon Alpha occurred in 4FQ00, perhaps in November. At thati3 point fewer than a dozen people were "in the loop."h  C The issue became one of timing: "when do we drop the A(lpha)-Bomb?"e  H Presumably that decision was made on or about April 2001, that being the6 time at which Compaq realized that 2FQ was gonna suck.   > E > I'm aware of three facts showing the Alpha axe began falling months- earlier:  & <deleted, but interesting nonetheless>  H The ironic thing is that the IPF transition will IMHO be easiest for theJ Himalaya group since the original plan was to go from Mips to IPF. Much ofD the heavy lifting was done before Compaq bought DEC and subsequentlyC announced that the Yosemite Project would result in an Alphabetizedh	 Himalaya.=  L In retrospect there were other data points that could have been leveraged toG predict Alpha's doom. A discussion I had with an architectural adept inyK October 2000 may not have been "the handwriting on the wall" for Alpha, buttE the palaver rendered it evident that IPF would play a leading role in % post-Marvel Blade-and-fabric servers.c  % Per usual, hindsight is always 20-20!n   cheers,i   terry s    ------------------------------  % Date: Mon, 17 Dec 2001 00:32:13 +0100 1 From: John McLean <mcleanj@swissonline.delete.ch>f, Subject: Re: More about Alpha and the merger5 Message-ID: <3C1D2EFD.363B68B2@swissonline.delete.ch>    Duane Sand wrote:e  n ... = > I think Alpha fans keep reaching for extraneous reasons ford; > why Alpha was killed.  It must be incompetent marketeers.h   Well, let's see...  H Last I heard (early 2000 I think) was that Compaq's sales philosophy wasD Windows at the low end, Unix for general purpose and in the high-end6 preferably Himalaya unless they wanted VMS clustering.  G Updating this a bit, let's slot Windows Servers (Proliant stuff) before  unix as we go up the scale.a  H I'll put a (very) rough estimate on the target sales percentages to give# you some idea of how it might look:   Windows PCs 60%'  Windows Servers 10%  (takes us to 70%)o  Unix 20% (90%)k  Himalaya (say 6%)+  and that leaves VMS with about 4% of salesh    D For VMS this is clearly a tough deal when many in this group believeF that VMS is equal to Unix for most things, better at some and worse at% others, but essentially fairly equal.H  G Now Compaq has also transferred a lot of VMS clustering technology intosD Tru64 (things like single-system image).  This means that one of theH main reasons for choosing VMS (or having Compaq sales people force it onG you) is disappearing.  (Telco's, banks, lotteries etc all like the ideaf of clustering.)   F For Alpha as a whole this would be okay, if only Compaq could properlyE promote (or market) this technically superior version of Unix, but itDH doesn't seem able to and customers are buying Unix from other vendors or using Linux.  H Now Linux is getting clustering too, so it doesn't matter who the vendor? is, the market that Compaq will for VMS is disappearing.  AftereE originally saying that they would not support Red Hat Linux on Alpha,cF Compaq have changed their tune, but in all probability it is too late.  C So, to summarise... Compaq haven't done all they might have done toMF promote VMS (and hence Alpha) sales, but instead they have transferredH its major features to a non-selling product that Compaq prefers that the8 customers to buy, but those customers see the product asE indistinguishable from many others and for various reasons, they will  buy elsewhere.  D Nett results ... VMS sales down, Unix sales not increased, therefore> Alpha sales decrease.  Linux-on-Alpha first abandoned and thenC reinstated, but maybe too late to chck the slide in Alpha sales foro LInux.    5 Now tell me that this is not incompetent marketeers !n     John McLeanr   ------------------------------  # Date: Mon, 17 Dec 2001 00:08:30 GMTo. From: "Duane Sand" <Duane.Sand@mindspring.com>, Subject: Re: More about Alpha and the merger/ Message-ID: <2IaT7.11286$MM5.1039946@rwcrnsc53>e   "Alan Greig" wrote >g > Duane Sand wrote:rE > > Yeah.  The current sales (w/o any roadmap surgery) already suckedhF > > to the point where all Alpha manufacturing could be easily handledF > > by a minor lower-wage secondary factory in U.K that was originally+ > > intended to handle only European sales.  >oN > I think you much malign "DEC Ayr" The "AY" manufacturing prefix on DEC partsN > has been around for a long time. The Microvax 3100 was even designed at Ayr.F > Ayr, Livingston, Edinburgh all once formed a coherent part of DEC in	 Scotland. O > The Alpha chip fab in Edinburgh, Software Engineering at Livingston (SpiralogrI > etc) and the Ayr manufacturing plant. All within about 50 miles of eache other.H > It is not a "minor lower wage secondary factory" but rather one of the	 remaininga% > parts of DEC's one time excellence.e  K I meant minor as in "less capacity", not less quality.  And at that, I haveaG no idea how big a facility Ayr is and how it compared to the productionaE capacity previously set up for Wildfires at Fremont.  I assumed (fromtE Ayr being initially allocated to do only European shipments) that itsrI Wildfire-specific capacity was relatively less than was set up at FremontnH for handling all other regions. If so, then Wildfire-etc capacity is nowF signficantly less than was prepared for Wildfire's rollout period when both factories were available.  K Silicon valley housing costs and wages are probably higher than Scotland's,nB so it makes lots of cents for skilled work to be moved out to moreC productive places when they can handle the workload.  Fine with me. F But I found the difference between Alpha expectations and actual Alpha shipments alarming.e     -- Duane Sandw   ------------------------------  # Date: Mon, 17 Dec 2001 00:11:09 GMTt4 From: "Terry C. Shannon" <terryshannon@mediaone.net>, Subject: Re: More about Alpha and the merger= Message-ID: <xKaT7.15477$Sj1.8897178@typhoon.ne.mediaone.net>s  K One of the more interesting (and defensible) assessments I've seen of late.u  > "John McLean" <mcleanj@swissonline.delete.ch> wrote in message/ news:3C1D2EFD.363B68B2@swissonline.delete.ch...h >v >t > Duane Sand wrote:  >h > ...o? > > I think Alpha fans keep reaching for extraneous reasons for = > > why Alpha was killed.  It must be incompetent marketeers.g >e > Well, let's see... >oJ > Last I heard (early 2000 I think) was that Compaq's sales philosophy wasF > Windows at the low end, Unix for general purpose and in the high-end8 > preferably Himalaya unless they wanted VMS clustering. >cI > Updating this a bit, let's slot Windows Servers (Proliant stuff) before  > unix as we go up the scale.a >tJ > I'll put a (very) rough estimate on the target sales percentages to give% > you some idea of how it might look:- >  Windows PCs 60%) >  Windows Servers 10%  (takes us to 70%)  >  Unix 20% (90%)o >  Himalaya (say 6%)- >  and that leaves VMS with about 4% of saless >  >iF > For VMS this is clearly a tough deal when many in this group believeH > that VMS is equal to Unix for most things, better at some and worse at' > others, but essentially fairly equal.I >vI > Now Compaq has also transferred a lot of VMS clustering technology intocF > Tru64 (things like single-system image).  This means that one of theJ > main reasons for choosing VMS (or having Compaq sales people force it onI > you) is disappearing.  (Telco's, banks, lotteries etc all like the idean > of clustering.)  >dH > For Alpha as a whole this would be okay, if only Compaq could properlyG > promote (or market) this technically superior version of Unix, but ithJ > doesn't seem able to and customers are buying Unix from other vendors or > using Linux. >iJ > Now Linux is getting clustering too, so it doesn't matter who the vendorA > is, the market that Compaq will for VMS is disappearing.  AftereG > originally saying that they would not support Red Hat Linux on Alpha,tH > Compaq have changed their tune, but in all probability it is too late. >IE > So, to summarise... Compaq haven't done all they might have done to H > promote VMS (and hence Alpha) sales, but instead they have transferredJ > its major features to a non-selling product that Compaq prefers that the: > customers to buy, but those customers see the product asG > indistinguishable from many others and for various reasons, they wille > buy elsewhere. >rF > Nett results ... VMS sales down, Unix sales not increased, therefore@ > Alpha sales decrease.  Linux-on-Alpha first abandoned and thenE > reinstated, but maybe too late to chck the slide in Alpha sales fori > LInux. >f >e7 > Now tell me that this is not incompetent marketeers !s >i >i
 > John McLeanp   ------------------------------  # Date: Mon, 17 Dec 2001 02:09:18 GMT . From: "Duane Sand" <Duane.Sand@mindspring.com>, Subject: Re: More about Alpha and the merger- Message-ID: <itcT7.10630$KY.432823@rwcrnsc54>u   "John McLean" wrote: >o > > Duane Sand wrote: G > > I'm aware of three facts showing the Alpha axe began falling monthso earlier: > > G > > 1. My VP saying that the negotiations with Intel were taking monthshL > > longer to conclude than originally expected.  (And from earlier dealingsM > > with Intel, I've learned how very long it takes to negotiate even triviali > > things with Intel.)I > >iJ > > 2. Winkler's Jan 26 gaffes saying Himalaya was to be delivered on IPF. >tI > That might of have only been a fore-runner to Alpha plans.  Winkler hasOJ > been known to speak out of line with Compaq thinking on other occasions.  A You mean he regularly announces as already-accomplished fact, hisoA personal ideas of hypothetical future unsettling changes to majorp; profitable product lines, without discussion with Capellas?c> I believe he was prematurely speaking what he and Capellas had7 jointly decided and had already begun steering towards.   D > > 3. Some of my co-worker friends were the ones doing a top-secretH > > contingency study of changing to an IPF port, mentioned in Winkler'sB > > Jan 26 statements as a small team working on Himalaya for IPF.K > > (For me, this detail confirms the general accuracy of Greig's reportingnE > > of what Winkler said, in now-unavailable parts of the Jan 26 livep > > coverage.) >mA > As you have said previously companies should make these kind ofrB > assessments on an ongoing basis.  As you said here, "contingencyB > study".  It doesn't mean that any decision had been made, but it3 > does mean that alternatives were being evaluated.o  A But we don't in fact do migration contingency studies except when.B the current supplier's road map is very very doubtful.  Why do one@ for expiration of Alphas, when the EV7 chip was complete and the9 Himalaya port to EV7 was very far along with no barriers?t6 Because someone upstairs was preparing to make EV8 etc= very very doubtful.  The Winkler gaffe indicates that Winklero@ at least, thought EV8 cancellation was definite back in January.  F > ... various quotes of revenues (but no profit/loss info) snipped ...  @ > This is still inconclusive with respect to a decision date forJ > Alpha-to-Intel.  It appears that it could have been any time prior to 20I > June.  Evaluations before that, and discussions/negotiations with Intel G > but when was it decided to accept the terms & conditions of Intel, inh8 > other words when did someone say "Yes, we'll do it." ?  @ You are asking for the date at which Alpha was executed after noA last-minute reprieves, but are thinking of that date as the trialn? and sentencing date. In retrospec, I think Alpha's sentence was C silently declared the day Capellas announced his 180-day initiativen: to drastically change the company and we all got copies of7 "Where's My Cheese?".  (See if you can pin down a Carly   merger discussion back to then.)   > ... snip ...A > I would have thought that if any money was involved Intel wouldd@ > be required to file a submission with the SEC and to let theirF > stockholders know of this "material event" (to use SEC terminology).  > Why?  Does Intel publically document every patent or copyright3 license transaction?  Or every marketing agreement?d Does Microsoft?r  @ The SEC rules about material events has to do with early insiderD or favored-circle stock trading based on information that is shortly7 due to become public knowledge and change stock prices.p? At the June 25 announcement, the whole world learned everythingi= it is likely to know this year about that deal.  Most company ; annoucements do not generate SEC paperwork, even if many ofc; them are considered material and handled carefully to avoide insider trading accusations.    B > > Complicated deals with Intel are not made in a day or two likeE > > you imagine.  It was not a simple quick case of "I'll cut off the - > > nose on my face.  Is that okay with you?"  >iD > I didn't mean a day or two :-)  but given the relatively clear-cut > nature of the deal   Clear cut?  Hah!  / > and what might be a small degree of haggling, C > I didn't see why it should take more than a few weeks, especiallyt3 > if Compaq were hell-bent on getting rid of Alpha.c  D Intel does nothing quick.  And Compaq Houston prides itself on doingG deals for good bargains;  that's what it thinks its core competency is.i  1 > BTW, do you know if Alpha was offered to AMD ??,  ; I doubt it.  AMD burned Compaq some years ago on an earlierm6 agreement to work together on chips for the Alpha bus.< They're not trusted as partners.  And AMD currently makes no5 chips that Compaq deems ready for enterprise systems. 7 And AMD believes their x86-64 extensions for the Hammerp5 systems will do quite well in AMD's market space; AMDe8 had no need for Alpha instruction set or Alpha software.   > ... snips ...,D > > John, I don't understand your theory about some huge "in-processC > > technology" debit or credit dating from the Digital acquisition ) > > that still has to be paid by someone.s >i? > Okay.  In simple terms the development of Alpha to this pointA; > in time was surely worth something and that something wasu > probably not insignificant.  > ... <snip> ...= > If my recollection is correct, an Alpha release was runninga< > about 12 months late and logic says that considerable work; > had already been done on it, work that had a value to anys< > purchaser.  Undoubtedly there was also work to be done, so4 > Alpha development was part of that $3.1 billion of > development costs. >e< > We are in the same situation with Alpha now.  Considerable: > work has apparently done on EV8 and if Intel is going to: > reap the benefits of that work because they now own that= > expertise and knowledge, then they should be paying for it.e >s: > By deferring any compensation whatsoever until some timeB > in the future, Compaq has not translated that into any immediateA > income - just some general notion of sharing marketing costs --o< > and this means that HP is paying less for Compaq right now; > than it otherwise would have done if Compaq had the moneyi > from Intel now.i   I still don't get all that.n  . The hopefully-fair stock-exchange ratio for HP4 acquiring Compaq was picked solely from stock market9 forces, the average historical ratio of prices and  stock:7 capitilizations of the two companies over recent years.17 It didn't try in any way to do a bottoms-up asset sheetn4 appraisal of what the breakup value of Compaq was toA possible third parties.  It didn't try to use inside information.e  9 There may have been various tax games played in the post-d7 acquistion accounting for Compaq's purchase of Digital.i7 But ultimately the price paid for Digital was the priced4 Compaq was willing to pay and Digital was willing to accept, and nothing else.   1 Unless you personally hold lots more shares of HP 5 than of Compaq, or vice versa, then the price set forn4 acquiring Compaq is basically irrelevant to anything7 except the chances of this whole deal being voted down.i  2 The "in-process technology" notion sounds like the: distinction we use between "product research" costs, which4 have to be accounted for as an immediate bottom-line7 cost in the year in which the wages and costs happened,t6 versus "development" costs where costs can be formally3 postponed (for tax purposes? financial results?) toa: the year in which the product finally ships.  In my group,4 we now say that when all software subsystem external4 specs are approved, we know the product is buildable: and all the rest is just cranking it out.  That allows the/ detailed design, coding  & testing phases to beh creatively financed.  8 As to the Intel agreement, I think absolutely all of the3 not-finished hardware and software work was totallyi5 useless and valueless to Intel. As is the EV8 work toh7 HP and now Compaq.  If there are big one-time writeoffsl7 to clear up some creative financings of discarded work,a5 the burden of those writeoffs would effect the mergedi4 company regardless of whether the write-off happened before or after the merge.  1 Was Compaq more desirable as an acquiree after ita+ shed the awkward & unwanted Alpha business?n1 Yes, if IPF works out and enough customers can be'8 retained through the migrations.  Does it matter whether4 that shedding occurs before or after an acquisition?4 Not really, if it was going to be killed either way.  ,   -- Duane Sand, not speaking for Compaq etc   ------------------------------    Date: 16 Dec 2001 20:44:07 -0600+ From: young_r@encompasserve.org (Rob Young)-, Subject: Re: More about Alpha and the merger3 Message-ID: <WKch2kmG9DU2@eisner.encompasserve.org>e  ^ In article <itcT7.10630$KY.432823@rwcrnsc54>, "Duane Sand" <Duane.Sand@mindspring.com> writes: > "John McLean" wrote:  B >> As you have said previously companies should make these kind ofC >> assessments on an ongoing basis.  As you said here, "contingencyaC >> study".  It doesn't mean that any decision had been made, but it 4 >> does mean that alternatives were being evaluated. > C > But we don't in fact do migration contingency studies except whenyD > the current supplier's road map is very very doubtful.  Why do oneB > for expiration of Alphas, when the EV7 chip was complete and the; > Himalaya port to EV7 was very far along with no barriers?p8 > Because someone upstairs was preparing to make EV8 etc? > very very doubtful.  The Winkler gaffe indicates that Winkler B > at least, thought EV8 cancellation was definite back in January.  = 	Yes... and much to Alan Greig's credit he spotted this as hehB 	was/is listening very carefully to every word Mr. Winkler states.- 	A quick cull of c.o.v reveals the following:a  % From: Alan Greig (a.greig@virgin.net)f$ Subject: Re: Himalaya / Alpha / VMS  Newsgroups: comp.os.vmsi Date: 2001-01-29 13:45:15 PST    Hoff Hoffman wrote:a  = > In article <3A735EB9.9BEE165D@infopuls.com>, Christof Brassi <brass@infopuls.com> writes: > I >   Himalaya will be moving to Alpha, with the implementation of lockstep 0 >   in the next Alpha microprocessor core (EV7). >r  O What did Winkler mean when he failed to mention this as the future for HimalayasN and said that Tandem/Himalaya technology was about to be implemented on Intel?M Was he just plain wrong. If so where is the retraction? I take it you are not  denying that he said this?   --
 ALan Greig   ---n  F 	In hindsight , it was a blunder of major proportions on Mr. Winkler'sC 	part but it does show that Alpha was Dead then but no one knew it.s  E 	But in the whole scheme of things, maybe not such a bad blunder now, B 	eh?  I mean after all, if someone points to an "Alpha conspiracy"H 	Compaq can point out that there were public indications that internally2 	Compaq was moving NSK development to IA64, right?   > G >> ... various quotes of revenues (but no profit/loss info) snipped ...  > A >> This is still inconclusive with respect to a decision date foreK >> Alpha-to-Intel.  It appears that it could have been any time prior to 20oJ >> June.  Evaluations before that, and discussions/negotiations with IntelH >> but when was it decided to accept the terms & conditions of Intel, in9 >> other words when did someone say "Yes, we'll do it." ?e > B > You are asking for the date at which Alpha was executed after noC > last-minute reprieves, but are thinking of that date as the trial2A > and sentencing date. In retrospec, I think Alpha's sentence wasnE > silently declared the day Capellas announced his 180-day initiativea< > to drastically change the company and we all got copies of9 > "Where's My Cheese?".  (See if you can pin down a Carlyr" > merger discussion back to then.) >   A 	Yep... in hindsight, this seems most plausible doesn't it?  I amlC 	willing to bet that there are internal communications to seal thataD 	as a fact... elsewise the June 25th timing smells very bad.  Now asD 	to why June 25th?  We've kicked that around quite a bit... but thatC 	appears to have given Carly F. a starting point to go and say heretB 	is what we plan AND the HP board can't question Alpha baggage andB 	all that entails.  The important point from Compaq's quid pro quoA 	problem (knifing Alpha to get the deal) isn't a problem as that f@ 	decision was made MANY months before BUT implemented June 25th.   				Rob    ------------------------------  # Date: Mon, 17 Dec 2001 03:15:54 GMT 4 From: "Terry C. Shannon" <terryshannon@mediaone.net>, Subject: Re: More about Alpha and the merger= Message-ID: <KrdT7.15979$Sj1.9026895@typhoon.ne.mediaone.net>)   > >tD > > You are asking for the date at which Alpha was executed after noE > > last-minute reprieves, but are thinking of that date as the trialcC > > and sentencing date. In retrospec, I think Alpha's sentence wastG > > silently declared the day Capellas announced his 180-day initiatives> > > to drastically change the company and we all got copies of; > > "Where's My Cheese?".  (See if you can pin down a Carlyc$ > > merger discussion back to then.) > >a > B > Yep... in hindsight, this seems most plausible doesn't it?  I amD > willing to bet that there are internal communications to seal thatE > as a fact... elsewise the June 25th timing smells very bad.  Now as E > to why June 25th?  We've kicked that around quite a bit... but that D > appears to have given Carly F. a starting point to go and say hereC > is what we plan AND the HP board can't question Alpha baggage andmC > all that entails.  The important point from Compaq's quid pro quo.A > problem (knifing Alpha to get the deal) isn't a problem as that.A > decision was made MANY months before BUT implemented June 25th.s >e  J As a famous cowboy once said, "Follow the Money." Why June 25 was selectedJ (as opposed to June 21 or June 27 or June 14 or whatever) is known only toK Compaq. But it's a safe bet that the deal was enacted and publicized in theeG waning days of 2FQ01 to enable CPQ to take the financial write-off thatnC enabled the firm to turn a 2FQ paper profit consistent with earlieroK guidance. This despite the fact that 2FQ revenues were about half a billiont dollars below expectations.s  H As for internal communications, I'd venture to guess that they are quiteL scarce. After all, email can have a way of coming back to haunt you. Only USF Presidential Administrations can get away with a "the ZIP drive ate myL email" defense. Hence the paper--or electron--trail is probably quite faint.  L So the ever-popular "what did they know and when did they know it?" question remains in play.   ------------------------------  # Date: Mon, 17 Dec 2001 04:00:33 GMT * From: "Bill Todd" <billtodd@metrocast.net>, Subject: Re: More about Alpha and the merger@ Message-ID: <B5eT7.35407$Zd.3294174@bin1.nnrp.aus1.giganews.com>  9 "Duane Sand" <Duane.Sand@mindspring.com> wrote in messagee( news:al5T7.9682$Kg2.1193261@rwcrnsc51... > "Bill Todd"  wrote:    ...   , > > I think it's time you put up or shut up. >m@ > Sorry, it's not in my job parameters to be publishing Compaq's? > per-product financial details for you, even had I bothered toa8 > write down the information we got verbally from our VP > and department heads.u  L Fair enough:  that's the same quality information I have about VMS's (and byG reasonably straight-forward extension Alpha's) profitability.  So there I appears to have been a major divergence of opinion at the Compaq VP level H about this matter, and while one *might* expect Alpha's owners to have aH somewhat better handle on their own numbers than your people that's only supposition.   - bill   ------------------------------  % Date: Mon, 17 Dec 2001 00:32:11 -0500f- From: JF Mezei <jfmezei.spamnot@videotron.ca>t, Subject: Re: More about Alpha and the merger, Message-ID: <3C1D8359.D538AAA8@videotron.ca>   Duane Sand wrote:r? > Who cares at all about revenue?  Profit is what matters to mye& > employment and the company's health.  L In all fairness to Tandem, Digital used to be magnitudes larger than Tandem.N And for all the harm that was done to VMS, it is still a larger installed baseG than Tandem. It is possible that during one quarter, Tandem sales would-O generate more profits than VMS/Tru64, but over a whole year, I really doubt it.d  L However, with the death of Alpha and Tru64, it now very possible that TandemK may become Compaq's largest enterprise product, at which point it will alsooK become Compaq's only enterprise product because at that point VMS will haveo5 shrunk to a point where Compaq can afford to kill it.i   ------------------------------  % Date: Mon, 17 Dec 2001 00:36:21 -0500e- From: JF Mezei <jfmezei.spamnot@videotron.ca>I, Subject: Re: More about Alpha and the merger, Message-ID: <3C1D8453.6E627E3C@videotron.ca>   John McLean wrote:I > That might of have only been a fore-runner to Alpha plans.  Winkler hasmJ > been known to speak out of line with Compaq thinking on other occasions.  L Out of line with the spin control at the time, but out of line with Compaq's long term strategy ? s  N I trust what Winkler says. I don't agree with it, I hate it,  but I trust that) it represents's Compaq's true directions.s   ------------------------------  # Date: Mon, 17 Dec 2001 01:29:01 GMTn- From: "John E. Malmberg" <wb8tyw@qsl.network> 1 Subject: Re: More DSSI cluster problems/questions ( Message-ID: <3C1D502B.30407@qsl.network>  8 [Excuse any extra blank lines please, known MOZILLA bug]   Robert DiRosario wrote:s   > 7 > I set ALLCLASS to 2 and FORCEUNI to 1 for all drives.     B The SYSGEN parameter ALLOCLASS needs to be set to 2 on all of the 5 OpenVMS systems that are connected to the DSSI disks.e  C This will usually require that you set it in MODPARAMS.DAT and use i) AUTOGEN to set the new system parameters.   D It is a requirement that the ALLOCLASS sysgen parameter for OpenVMS 4 matches the ALLCLASS parameter for the DSSI devices.  H In a cluster where a DSSI bus is connected to more than one host, it is A required that the DSSI ALLCLASS and corresponding OpenVMS sysgen n ALLOCLASS parameter not be 0.e  I I stated that in my first response.  Have you made sure that the OpenVMS p SYSGEN parameters are correct?    E > The disk alloc. class on the HSD10 is 2, the tape alloc. class is 0a; > and there are no SCSI devices connected to the HSD10 yet.i    H If you do not plan to put any tape drives on the DSSI bus or HSD10, you % can ignore the tape allocation class.e  H If you plan to use tape devices on the DSSI bus or HSD10, then you must H set a non-zero tape alloc. class, for both OpenVMS and the HSD1O.  Both  must be set to the same value.  F You can use the same value as ALLOCLASS, to be consistent, or you can  use separate values.     ; > DSSI bus 1 is the "cluster bus".  This host is DSSI ID 7,e0 > other systems will be at DSSI ID's 4, 5 and 6.    I Ok, what are the other system types, and what type of DSSI interconnects t. are being used?  This could also be important.  ? The KFQSA interface can not be used for a cluster interconnect.c     , > DSSI ID, UNITNUM,  NODENAME, (Device type)$ >  1,       1,         "D1",  (RF73)$ >  2,       2,         "D2",  (RF72)= >  3,       3,         "SYSTEM",  (RF72, cluster system disk)l > 5 > DSSI bus 0, this system only, host is at DSSI ID 7.  > + > DSSI ID, UNITNUM, NODENAME, (Device type) $ >  0,        10,      "D10",  (RF35)$ >  1,        11,      "D11",  (RF35)$ >  2,        12,      "D12",  (RF72)$ >  3,        13,      "D13",  (RF72)' >  6,        NA,      "HSD1",  (HSD10,)e    G The HSD10 needs to have a value that is used as an offset for the SCSI  F lun numbers under it.  I forget the name of this parameter, as it has ) been several years since I last did this.n  @ If you do not set this offset, then you may have some conflicts.    d > So, >>>show dev gives: >  >  DIA0 (RF35) D10 >  DIA1 (RF35) D11 >  DIA2 (RF72) D12 >  DIA3 (RF72) D13 >  DIA7 (HSX0) HSD1 	 >  *  (7)     n > DIB1 (RF73) D1 > DIB2 (RF72) D2 > DIB3 (RF72) SYSTEM > * (7)h >  > SCSI, Adapter 6i >  -DKA300 (RZ35)f >  -DKA400 (RRD45) >  > UQSSP disk controller 0  > UQSSP tape controller 0t >   -MUA0 (TK70) >  > EZA0 > XQA0 > XQB0 > 2 > I'm not sure why the HSD10 is DIA7 and not DIA6.    C I am not sure either.  The HSD10 is a bus translation device, not aaE SCSI device.  I do not remember it being visible at all until it has   some devices on it.a  E It could be a configuration error.  The SCSI bus on it is terminated y correctly of course?  G I would review the HSD10 documentation and setup to find out why it is A4 showing up at all as a disk.  That just seems wrong.      > So the system sees everything. >   > Boot VMS 7.1 and do "show dev" > 
 > VAXA$DKA300s
 > VAXA$DKA400  >  > $2$DIA0 (D10)  > $2$DIA1 (D1) > $2$DIA2 (D12)  > $2$DIA3 (SYSTEM) > $2$DIA7 (HSD1) >   > Three DSSI drives are missing! > 3 > If I set the drives on one bus to alloc. class 1,n/ > the drives on the other bus to alloc. class 2a' > and set FORCEUNI to 0 for all drives,n > I see all of the drives: > 	 > $1$DIA0t	 > $1$DIA1 	 > $1$DIA2l	 > $1$DIA3e	 > $1$DIA7 	 > $2$DIA1e	 > $2$DIA2 	 > $2$DIA3  > + > Is there some other parameter on the DSSI  > disks I need to set?    K First can you verify that your SYSGEN parameter ALLOCLASS is set correctly?r    / Then I usually use FORCEUNI of 0 on DSSI bus 0.t    G And if there are HSD devices on the DSSI busses, I set the unit number eF of the devices to be 1000 * bus # plus the plug id.  Before I started 1 using HSD devices, I used 10 * bus + the plug id.   B The SCSI devices on the HSD10 will show up as 10 * their SCSI id. H number, so I set it's offset so that the thousands digit corresponds to G the DSSI bus number, and the 100s digit corresponds to the HSD number,  G starting at zero.  This allows you to look at an OpenVMS device number a& and tell directly where the device is.   This will give you:i   DSSI bus 0:a     $2$DIA0:     $2$DIA1:     $2$DIA2:     $2$DIA3:=        And assuming 5 disk devices on the HSD10, and that thet@        HSD10 is plugged into slot 0 of a storageworks enclosure.       $2$DIA10:p       $2$DIA20:s       $2$DIA30:a       $2$DIA40:h       $2$DIA50:m   DSSI bus 1:e      $2$dia1001:      $2$dia1002:      $2$dia1003:  G Now if you decide to put the HSD10 on BUS 1, then the convention would  $ have it the drives on it show up as:         $2$dia1010:          $2$dia1020:o         etc.    m  6 A Second HSD10 on BUS 1, I would configure as follows:         $2$DIA1110:o         $2$DIA1120:c         etc:    I Again, this is just a convention that I recommend as it makes it easy to  6 relate the physical disks to the OpenVMS device names.  F Since the ususal convention is to have the DIA0: device as the system @ disk, I assume that you have some reason to use a different one?  C OpenVMS and the console rom do not care of course, but it could be r0 confusing if there are multiple system managers.  F Also, you can use more than one DSSI bus for the cluster interconnect  traffic.   -Johny wb8tyw@qsl.network Personal Opinion Only    > Thanks	 > Robert,a > KA3ZYX >  >    > "John E. Malmberg" wrote:  >  >  >>Robert DiRosario wrote:d >>E >> > On a VAX 4000/106A with two DSSI buses, do the drives on the two G >> > buses need to have the same allocation class, or can each bus havea" >> > a different allocation class? >> >D >> > I gave all the drives on one bus allocation class 1 and all theD >> > drives on the second bus allocation class 2 and set UNITNUM andH >> > FORCEUNI to  0 on all the drives.  When I boot VMS 7.1 (from a SCSIH >> >  drive), "show dev" shows all the drives.  A VMS admin at work toldB >> >  me the system won't serve the disks with this configuration. >> >H >> > If I set the allocation class on all drives to 1, FORCEUNI to 1 andH >> > give each drive a unit unit number "show dev" only sees some of the >> > drives. >> ># >> > How do I configure the drives?e >>9 >>All drives on a bus must have a uniquely numbered plug.n >>F >>When you do a >>>show device prompt, they should show up as DIAn and! >>DIBn, where "n" is the plug ID.o >>E >>The allocation class of all non-SCSI drives on a system must be theCH >>same.  And it must match the ALLOCLASS SYSGEN parameter on any OpenVMS >>hosts on the DSSI bus. >>G >>Now each DSSI drive must also have a unique unit number in a cluster.sI >>This unit number defaults to the drive ID plug value.  Obviously with aqI >>limit of 8 devices on a bus, with two buses, there are bound to be some 2 >>duplicates unless UNITNUM and FORCEUNI are used. >>J >>To make things easy, I usually use the default plug values for the firstG >>DSSI bus, and add an offset divisible by 10 to it for the second DSSIo >>bus and subsequent ones. >>F >> > Also, do I need to set the SYSTEMID for each disk or will VMS set' >> > that when I configure the cluster?m >>F >>The NODENAME of each DSSI element needs to be unique to the cluster.I >>Normally the random name that it is factory initialized with is fine tocI >>use.  If you do assign a name, use only 6 characters.  The elements cano7 >>accept 8, but I am not sure if OpenVMS currently can.  >>I >>I have never changed the SYSTEMID of any DSSI elements.  I would expects  >>that it also should be unique. >> >>-John. >>wb8tyw@qsl.network >>Personal Opinion Onlyd >>   ------------------------------  % Date: Mon, 17 Dec 2001 00:15:46 -0500d- From: JF Mezei <jfmezei.spamnot@videotron.ca>x Subject: Re: Purging sysuaf.datr+ Message-ID: <3C1D7F82.C05E312@videotron.ca>e   Larry Kilgallen wrote:; >         2. Some usernames which never receive a login areo7 >            actually used by some (misguided) product.e  K But a proper analysis of your SYSUAF and careful planning in seeting up thegN SYSUAF would have have all those "mainetance" accounts in a group number belowJ a certain number, so when checking for inactive accounts, one would eitherG exclude anything below a certain group number, or only select potential.5 deletion candidatyes inside a range of group numbers.m   ------------------------------  # Date: Mon, 17 Dec 2001 05:57:26 GMT - From: "John E. Malmberg" <wb8tyw@qsl.network>5 Subject: Re: Purging sysuaf.dat * Message-ID: <3C1D8F24.9080902@qsl.network>   JF Mezei wrote:i   > Larry Kilgallen wrote: > ; >>        2. Some usernames which never receive a login aret7 >>           actually used by some (misguided) product.r >> > M > But a proper analysis of your SYSUAF and careful planning in seeting up theHP > SYSUAF would have have all those "mainetance" accounts in a group number belowL > a certain number, so when checking for inactive accounts, one would eitherI > exclude anything below a certain group number, or only select potentiali7 > deletion candidatyes inside a range of group numbers.r    , Unfortunately, sometimes you inherit a mess.  C So create an identifier like "NORMAL_USER" and grant it to all the  0 accounts that are supposed to be able to expire.  A It may not be safe to modify accounts that are there for special t: purposes, or the modifications may be removed by upgrades.    gE Also then run a report to get a list of the accounts that do not haveeJ this identifier.  It can help you determine if you have too many untrained( people with system management privilege.     -Johne wb8tyw@qsl.network Personal Opinion Onlyt   ------------------------------  % Date: Sun, 16 Dec 2001 22:02:07 -0200a1 From: "Valdemir J. Santos" <valdemir-@uol.com.br>e6 Subject: Receiving message errors from another nodes..5 Message-ID: <001701c1868e$12794520$4e09c5c8@valdemir>r  , This is a multi-part message in MIME format.  + ------=_NextPart_000_0014_01C1867D.4DE56DC0i Content-Type: text/plain;r 	charset="iso-8859-1"d+ Content-Transfer-Encoding: quoted-printablea  F Im my new job I=B4m monitoring 15 VAX machines in network environment.B I=B4d like know how receive OPCOM messages from these 15 nodes,=20E in the main machine.  Is there any way to do this ? Actually, I=B4m =s
 issuing=20D SET HOST  command constantly, searching for errors messages in other, nodes. It=B4s a tiring job. How avoid this ? Thanks in advance...  + ------=_NextPart_000_0014_01C1867D.4DE56DC05 Content-Type: text/html; 	charset="iso-8859-1"2+ Content-Transfer-Encoding: quoted-printable   > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD>3 <META content=3D"text/html; charset=3Diso-8859-1" =a http-equiv=3DContent-Type>9 <META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR>l <STYLE></STYLE>  </HEAD>e <BODY bgColor=3D#ffffff>H <DIV><FONT face=3DArial size=3D2>Im my new job I=B4m monitoring 15 VAX = machines in=20! network environment.</FONT></DIV>eD <DIV><FONT face=3DArial size=3D2>I=B4d like know how receive OPCOM = messages from these=20 15 nodes,&nbsp;</FONT></DIV>@ <DIV><FONT face=3DArial size=3D2>in the main machine. &nbsp;Is = there</FONT><FONT=20E face=3DArial size=3D2> any way to do this ? Actually, I=B4m issuing =t
 </FONT></DIV>eE <DIV><FONT face=3DArial size=3D2>SET HOST&nbsp; command constantly, =. </FONT><FONT=20t8 face=3DArial size=3D2>searching for errors messages in = other</FONT></DIV>H <DIV><FONT face=3DArial size=3D2>nodes. It=B4s a tiring job. How avoid = this=20  ?</FONT></DIV>, <DIV><FONT face=3DArial size=3D2>Thanks in =% advance...</FONT></DIV></BODY></HTML>)  - ------=_NextPart_000_0014_01C1867D.4DE56DC0--t   ------------------------------   Date: 17 Dec 2001 02:04:55 GMT) From: leslie@clio.rice.edu (Jerry Leslie).: Subject: Re: Receiving message errors from another nodes..' Message-ID: <9vjjs7$4c4$1@joe.rice.edu>o  0 Valdemir J. Santos (valdemir-@uol.com.br) wrote:F : Im my new job I'm monitoring 15 VAX machines in network environment.? : I'd like know how receive OPCOM messages from these 15 nodes, D : in the main machine.  Is there any way to do this ? Actually, I'm 	 : issuing F : SET HOST  command constantly, searching for errors messages in other, : nodes. It's a tiring job. How avoid this ? : Thanks in advance...  A I've seen this mentioned in some other newsgroups, but don't have  any first-hand knowledge:v      http://www.bb4.com/4    Big Brother System and Network Monitor - Welcome   3   "B i g    B r o t h e r    i s    W a t c h i n gt      Are you Available?e  A    Big Brother monitors System and Network-delivered services fort>    availability. Your current network status is displayed on aF    color-coded web page in near-real time. When problems are detected,C    you're immediately notified by e-mail, pager, or text messaging.f  H    Big Brother is provided in source code format for Unix and Linux, andH    precompiled for Windows NT and Windows 2000. User contributed clientsD    are also available for Netware, Mac OS/9, VMS, AS/400 and VM/ESA.       BB4 Technologies is different  F    We don't advertize. If you're here then either you've found us in a?    search, read something about us, or most likely a friend has "    recommended Big Brother to you.  -    Big Brother is Free for Non-Commercial Usee  B    We believe that everyone should have access to Big Brother. BigH    Brother is free for non-commercial use, as defined by our Better than    Free license...".  < If you have money to spend, there's HP OpenView, BMC Patrol.  4 --Jerry Leslie     (my opinions are strictly my own)   ------------------------------  % Date: Sun, 16 Dec 2001 13:57:26 -0600e& From: "Bill Farmer" <bfarmer@wcfa.com>/ Subject: SDLT embarassing hardware support calla; Message-ID: <3c1cfbc3$0$26379$39cecf19@nnrp1.twtelecom.net>m  K Just to save others, the SDLT drives apparently have a high temp sensor and). spits the tape back out if drive is over temp.  G We received a 3U rack mount enclosure from Compaq with two SDLT drives.aK Being good software guys, we immediately removed the covers to see if thereo  was any OpenVMS software inside.  K While running test backups on our 8400 VMS test box, both drives proceed toe fail.1  K Call 1-800-OK-COMPAQ.  Got the usual response ... Oh, that's what one looksjE like.  We will send out a hardware guy with replacement drives (after8L deciding that the only thing common between the drives is the power supply).  K Field Service guy shows up two days later with two new drives and new powernL supply (that's the only three things in the enclosure) and we report that we
 had fixed it.a  L What we did is put the cover back on so the field service guy would not knowL the software geeks had been inside the case.  Drives work fine when the case9 fan can draw air through the SDLT drive and cool it down.,  G OBTW, the OK-COMPAQ guy said if we were to use the DECtape III cleaningeI cartridge, we would destroy the drive in a matter of seconds.  Seems thatoJ there a special cleaning tape needed (No Compaq Part Number yet ... but isE available as a Quantum part MR-SACCL-01 from your local DEC (oops ...-J Compaq) reseller.  I don't know from personal experience whether drive canG be "destroyed in a matter of seconds", however, I did tell you to look.r   Happy holidays to everyone!C   Bill   ------------------------------  % Date: Mon, 17 Dec 2001 01:44:17 -0000t1 From: "Chris Townley" <news@townleyc.demon.co.uk>  Subject: Re: vms 3.x questiongB Message-ID: <1008555260.24624.0.nnrp-01.d4e45fa5@news.demon.co.uk>  - "Hans Vlems" <hvlems@iae.nl> wrote in messagee+ news:6N0T7.1558$8p1.6109@typhoon.bart.nl...aF > Go to [SYS0.SYSMGR} and look at the name of the system startup file.E > It it is SYSTARTUP.COm then it is a VMS V3.x distribution (possibly0 earlier,' > but I've never seen a VMS V2 system).q< > For VMS V4 and V5 it is SYSTARTUP_Vx.COM. After that it is > SYSTARTUP_VMS.COM.  K ISTR that VMS4.7 on which I started had SYSTARTUP.COM the _Vnn came in withu 5.0    --
 Chris Townleye   ------------------------------  % Date: Sun, 16 Dec 2001 22:51:54 -0000 / From: Michael Zarlenga <zarlenga@conan.ids.net>n! Subject: Re: VMS file hex editor?a/ Message-ID: <u1q9cajn56fm01@corp.supernews.com>a  1 frank brown <frank.brown@ci.seattle.wa.us> wrote:iN : Is there a hex editor available for VAX/VMS?  I want to change some bytes in : a binary file.  
 GNU Emacs.   It's hex mode is just awesome.   -- t -- Mike Zarlenga   ------------------------------   End of INFO-VAX 2001.699 ************************