0 INFO-VAX	Thu, 03 Feb 2005	Volume 2005 : Issue 68      Contents: Re: %DCL-W-OKTAB again...  Re: %DCL-W-OKTAB again...  Re: %DCL-W-OKTAB again...  Re: %DCL-W-OKTAB again... L CPU Error: ANAL/ERROR output -- request for interpretation of severity of itP Re: CPU Error: ANAL/ERROR output -- request for interpretation of severity of it8 Re: disposition of largest private DEC collection in USA FA: DEC VAX/VMS Documentation 9 Re: How do I use terminal emulator with escape sequences?  HP rx2600 rack mount conversion # Re: HP rx2600 rack mount conversion # Re: HP rx2600 rack mount conversion  Intrusion attempts Re: Intrusion attempts Re: Intrusion attempts Re: Intrusion attempts# Re: Is there a FAQ for this group ?  Re: NFS v3 client support  Re: Official Logo  Re: OT: Battersea Power Station  Re: OT: Battersea Power Station  Re: OT: Battersea Power Station  Re: OT: Battersea Power Station 1 REBOOT or SHUTDOWN, how to tell in SYSSHUTDWN.COM 5 Re: There goes the volume market. Remind me again.... 5 Re: There goes the volume market. Remind me again.... 5 Re: There goes the volume market. Remind me again.... " Re: vaxcluster vms v5.5-2 and v7.3  F ----------------------------------------------------------------------  % Date: Thu, 03 Feb 2005 04:13:23 -0500 ' From: Dave Froble <davef@tsoft-inc.com> " Subject: Re: %DCL-W-OKTAB again..., Message-ID: <4201EB33.9030908@tsoft-inc.com>    David B Sneddon - bigpond wrote:   > Christoph, > > > The following program also generates the %DCL-W-OKTAB status6 > when it is in fact trying to exit with SS$_NORMAL... >  > $ create oktab.bas >         program oktab  > = >         option  type = explicit,                          & = >                 constant type = integer,                  & 4 >                 size = (integer long, real double) > * >         external long function  sys$exit > 8 >         declare long constant   array_size = 261440/161 >         declare long            condition_value ' >         declare long            magic  > < >         map (rubbish)   long dummy_array (1 to array_size) > . >         condition_value = 1     ! ss$_normal" >         magic = array_size - 131/ >         dummy_array (magic) = condition_value  > 6 >         call sys$exit (dummy_array(magic))      !*** >  >         end program  > $ basic oktab  > $ link oktab
 > $ run oktab ; > %DCL-W-OKTAB, command tables are already in latest format  > < > The argument to sys$exit is passed by the wrong mechanism. > 
 > Regards, > Dave   Yep!  Good example.  From HELP:    SYSTEM_SERVICES       $EXIT  
      Argument               code   "           OpenVMS usage:cond_value+           type:         longword (unsigned) !           access:       read only             mechanism:    by valueA           Longword value to be saved in the process header as the G           completion status of the current image. If you do not specify F           this argument in a macro call, a value of 1 is passed as theH           completion code for VAX MACRO and VAX BLISS-32, and a value of*           0 is passed for other languages.  = The change to the example above to preclude such mistakes is:   2 	external long function  sys$exit( LONG by value )  F But 'REAL' programmers don't need such compiler help, or do they?  :-)   Dave   ------------------------------  % Date: Thu, 03 Feb 2005 10:16:46 +0000 - From: David B Sneddon <dbsneddon@bigpond.com> " Subject: Re: %DCL-W-OKTAB again...* Message-ID: <4201FA0E.7040706@bigpond.com>  ! Dave Froble was overheard to say:  > ? > The change to the example above to preclude such mistakes is:  > 7 >     external long function  sys$exit( LONG by value )  > H > But 'REAL' programmers don't need such compiler help, or do they?  :-) >  > Dave  @ But then surely 'REAL' programmers KNOW all the system services,? all the relevant parameters and their passing mechanisms... ;-)    Regards, Dave.  --  D David B Sneddon (dbs)  VMS Systems Programmer  dbsneddon@bigpond.comD Sneddo's quick guide ...     http://www.users.bigpond.com/dbsneddon/D DBS freeware     http://www.users.bigpond.com/dbsneddon/software.htm   ------------------------------   Date: 3 Feb 2005 10:40:52 GMT . From: JONESD@ecr6.ohio-state.edu (David Jones)" Subject: Re: %DCL-W-OKTAB again...: Message-ID: <ctsv3k$igc$1@charm.magnus.acs.ohio-state.edu>  * In message <42016F96.4070807@bigpond.com>,;   David B Sneddon - bigpond <dbsneddon@bigpond.com> writes: = >The following program also generates the %DCL-W-OKTAB status 5 >when it is in fact trying to exit with SS$_NORMAL...   H Iteresting, but the program in question is written in C and exits by wayI of its main() function returning a value of -32592.  Some sort of strange J interaction between DCL and the pthread exit handler seems to be going on.    < David L. Jones               |      Phone:    (614) 292-6929- Ohio State University        |      Internet: L 140 W. 19th St. Rm. 231a     |               jonesd@er6s1.eng.ohio-state.edu: Columbus, OH 43210           |               vman+@osu.edu  1 Disclaimer: I'm looking for marbles all day long.    ------------------------------  % Date: Thu, 03 Feb 2005 12:32:47 -0500 ' From: Dave Froble <davef@tsoft-inc.com> " Subject: Re: %DCL-W-OKTAB again...* Message-ID: <4202603F.30806@tsoft-inc.com>   David B Sneddon wrote:  # > Dave Froble was overheard to say:  >  >>@ >> The change to the example above to preclude such mistakes is: >>8 >>     external long function  sys$exit( LONG by value ) >>I >> But 'REAL' programmers don't need such compiler help, or do they?  :-)  >> >> Dave  >  > B > But then surely 'REAL' programmers KNOW all the system services,A > all the relevant parameters and their passing mechanisms... ;-)     P 'Real' programmers get old and forgetful.  That include file with all the often / used external declarations has many saves.  :-)    ------------------------------   Date: 3 Feb 2005 08:15:53 -0800 . From: spamsink2001@yahoo.com (Alan E. Feldman)U Subject: CPU Error: ANAL/ERROR output -- request for interpretation of severity of it < Message-ID: <b096a4ee.0502030815.cc4c6f6@posting.google.com>  E Can someone tell me how serious this is? Should I stop using this CPU 2 right away or only if more errors come up? Thanks.  /  ******************************* ENTRY      27.  ******************************* F  ERROR SEQUENCE 7053.                            LOGGED ON:        SID 13000202F  DATE/TIME  3-FEB-2005 00:06:52.32                            SYS_TYPE 03260901   SYSTEM UPTIME: 21 DAYS 14:36:38E  SCS NODE: NODEX                                              VAX/VMS  V6.1   >  INT54 ERROR KA51  CPU Microcode Rev # 2.  CONSOLE FW REV# 2.6@                       Standard Microcode Patch    Patch Rev # 1.           REVISION        00000000         SYSTAT          00000001 :                                        ATTEMPTING RECOVERY        FLAGS           00000002 5                                        KA51 subpacket      KA51 REGISTER SUBPACKET           BPCR            ECC80004         PAMODE          00000000 C                                        30 bit physical address mode         MMEPTE          8890E9B0         MMESTS          1C008004         PCSCR           01000200 F                                        Patchable control store enabled?                                        standard microcode patch E                                        CPU microcode Patch Rev # = 1.         ICSR            00000001 @                                        virtual instruction cache enabled         ECR             000000CA C                                        full external interval timer  enabled         TBSTS           800001D0         PCCTL           FFFFFC13 B                                        pcache enabled for D-stream	 reference B                                        pcache enabled for I-stream	 reference D                                        pcache parity error detection enabled         PCSTS           FFFFF820         CCTL            00000021 ;                                        backup cache enabled <                                        BCACHE TAG RAM SPEED:A                                        read = 3 cycles, write = 3  cycles=                                        BCACHE DATA RAM SPEED: A                                        read = 2 cycles, write = 3  cycles@                                        512 kilobyte backup cache        BCEDSTS         00000000         BCETSTS         00000000         MESR            800A1114 C                                        O-BIT ERROR SYNDROME  = 8(X) 8                                        low bank selected>                                        check bit in error = c3B                                        LOST MEMORY CORRECTABLE ECC ERROR B                                        CORRECTABLE O-BIT ECC ERROR4                                        ERROR SUMMARY        MMCDSR          09CBC000 F                                        2600 cycles before disown write tmeoutA                                        enable logging soft errors 6                                        CQBIC on CP_I02        CESR            00000000         CMCDSR          0000C108 >                                        DMA prefetching enabledF                                        3200 Cycles Before NDAL Timeout?                                        144 cycles before cp1 mt  timeout B                                        144000 cycles before cp2 mt timeout >                                        cp1 interrupts pending:+                                        none >                                        cp2 interrupts pending:+                                        none         CEFSTS          00019200         NESTS           00000000         NEOCMD          00000F03         NEICMD          00000000         DSER            00000000         MMEADR          002AD800         VMAR            000007E0         TBADR           00000000         PCADR           FFFFFFF8         BCEDIDX         00000000         BCEDECC         00000000         BCETIDX         00000000         BCETAG          00000000         MEAR            50D5AEC0 C                                        main memory error address  =  0356BB00A                                        ndal commander id  = 05(X)         MOAMR           00000000            CSEAR1          00000000         CSEAR2          00000000         CIOEAR1         00004200         CIOEAR2         00000300         CNEAR           00000000         CEFADR          E0000300         NEOADR          036C1E00         NEDATHI         00000000         NEDATLO         00000000         QBEAR           0000000F         DEAR            00000000         IPCR0               0020 C                                        Local Memory External Access  Enabled /  ******************************* ENTRY      28.  *******************************    ------------------------------   Date: 3 Feb 2005 08:21:41 -0800 $ From: "AEF" <spamsink2001@yahoo.com>Y Subject: Re: CPU Error: ANAL/ERROR output -- request for interpretation of severity of it B Message-ID: <1107447701.476581.19180@g14g2000cwa.googlegroups.com>  E Another datum: I just noticed that the uptime reported here, 21 days, D is wrong. It's been up for 278 days (according to SHOW SYSTEM). I'veD seen such mismatches before with longish uptimes, but with VMS v6.2!   Advice welcome. Thanks again.    Alan E. Feldman wrote:G > Can someone tell me how serious this is? Should I stop using this CPU 4 > right away or only if more errors come up? Thanks. > 1 >  ******************************* ENTRY      27. ! > ******************************* = >  ERROR SEQUENCE 7053.                            LOGGED ON:  SID 
 > 13000202$ >  DATE/TIME  3-FEB-2005 00:06:52.32 SYS_TYPE
 > 03260901" >  SYSTEM UPTIME: 21 DAYS 14:36:38G >  SCS NODE: NODEX                                              VAX/VMS  > V6.1 > @ >  INT54 ERROR KA51  CPU Microcode Rev # 2.  CONSOLE FW REV# 2.6B >                       Standard Microcode Patch    Patch Rev # 1. > ! >        REVISION        00000000 ! >        SYSTAT          00000001 < >                                        ATTEMPTING RECOVERY! >        FLAGS           00000002 7 >                                        KA51 subpacket  >  >  KA51 REGISTER SUBPACKET > ! >        BPCR            ECC80004 ! >        PAMODE          00000000 E >                                        30 bit physical address mode ! >        MMEPTE          8890E9B0 ! >        MMESTS          1C008004 ! >        PCSCR           01000200 @ >                                        Patchable control store enabled A >                                        standard microcode patch G >                                        CPU microcode Patch Rev # = 1. ! >        ICSR            00000001 B >                                        virtual instruction cache	 > enabled ! >        ECR             000000CA E >                                        full external interval timer 	 > enabled ! >        TBSTS           800001D0 ! >        PCCTL           FFFFFC13 D >                                        pcache enabled for D-stream > reference D >                                        pcache enabled for I-stream > reference F >                                        pcache parity error detection	 > enabled ! >        PCSTS           FFFFF820 ! >        CCTL            00000021 = >                                        backup cache enabled > >                                        BCACHE TAG RAM SPEED:C >                                        read = 3 cycles, write = 3  > cycles? >                                        BCACHE DATA RAM SPEED: C >                                        read = 2 cycles, write = 3  > cyclesB >                                        512 kilobyte backup cache! >        BCEDSTS         00000000 ! >        BCETSTS         00000000 ! >        MESR            800A1114 E >                                        O-BIT ERROR SYNDROME  = 8(X) : >                                        low bank selected@ >                                        check bit in error = c3D >                                        LOST MEMORY CORRECTABLE ECC > ERROR D >                                        CORRECTABLE O-BIT ECC ERROR6 >                                        ERROR SUMMARY! >        MMCDSR          09CBC000 B >                                        2600 cycles before disown write  > tmeoutC >                                        enable logging soft errors 8 >                                        CQBIC on CP_I02! >        CESR            00000000 ! >        CMCDSR          0000C108 @ >                                        DMA prefetching enabled@ >                                        3200 Cycles Before NDAL Timeout A >                                        144 cycles before cp1 mt 	 > timeout D >                                        144000 cycles before cp2 mt	 > timeout @ >                                        cp1 interrupts pending:- >                                        none @ >                                        cp2 interrupts pending:- >                                        none ! >        CEFSTS          00019200 ! >        NESTS           00000000 ! >        NEOCMD          00000F03 ! >        NEICMD          00000000 ! >        DSER            00000000 ! >        MMEADR          002AD800 ! >        VMAR            000007E0 ! >        TBADR           00000000 ! >        PCADR           FFFFFFF8 ! >        BCEDIDX         00000000 ! >        BCEDECC         00000000 ! >        BCETIDX         00000000 ! >        BCETAG          00000000 ! >        MEAR            50D5AEC0 E >                                        main memory error address  = 
 > 0356BB00C >                                        ndal commander id  = 05(X) ! >        MOAMR           00000000  > ! >        CSEAR1          00000000 ! >        CSEAR2          00000000 ! >        CIOEAR1         00004200 ! >        CIOEAR2         00000300 ! >        CNEAR           00000000 ! >        CEFADR          E0000300 ! >        NEOADR          036C1E00 ! >        NEDATHI         00000000 ! >        NEDATLO         00000000 ! >        QBEAR           0000000F ! >        DEAR            00000000 ! >        IPCR0               0020 E >                                        Local Memory External Access 	 > Enabled 1 >  ******************************* ENTRY      28. ! > *******************************    ------------------------------  % Date: Thu, 03 Feb 2005 01:20:29 -0800  From: Joe Smith <joe@inwap.com> A Subject: Re: disposition of largest private DEC collection in USA 0 Message-ID: <VcmdnSKB0axCcZzfRVn-qQ@comcast.com>   Jay Maynard wrote:; > On 2005-02-01, Carl Appellof <doctorcja@yahoo.com> wrote: . >>>We know what hollywood would do to them. :( >>K >>Hey!  Hollywood immortalized a PDP-10 opcode in the movie "TRON" (opcode    >>666, the Number of the Beast). >  > Oh? Tell me more.   H And the computer graphics in the TRON movie were calculated on a PDP-10.  $ > Newsgroups: alt.folklore.computers > Subject: Re: Foonly F-1 ? > References: <db952829.0301281042.68b538be@posting.google.com> ) > From: jwusenet5@smoe.org (Jeff Wasilko) , > Message-ID: <1qcm1b-nf4.ln@proxy.smoe.org>% > Date: Mon, 03 Feb 2003 18:35:49 GMT  > ? > In article <db952829.0301281042.68b538be@posting.google.com>, & > GanjaTron <ganjatron@gmx.net> wrote: >>Greetings, programs! >>D >>Just wondering: whatever happened to the (one and only) Foonly F-14 >>used by III (Triple I) to produce the CGI in TRON? > A > I worked at triple-I (after the Movie division went elsehwere), I > and I've got a scan of a couple of documents related to the Foonly and   > the Tron project:  > 0 > http://www.smoe.org/jeffw/triple-i_history.pdf > 1 > Some other web sites that might be of interest:  > % > http://vhost2.zfx.com/~dave/f1.html ( > http://vhost2.zfx.com/~dave/ddyer.html? > http://www.accad.ohio-state.edu/~waynec/history/tree/iii.html  >  > -jeff    ------------------------------  % Date: Thu, 03 Feb 2005 12:12:13 -0500 - From: Steve Kulpa <stevekulpaFUDGE@yahoo.com> & Subject: FA: DEC VAX/VMS Documentation8 Message-ID: <knm401t294n2jehdvskauknkncb0s04cds@4ax.com>  
 Greetings,= I just dumped some DEC VAX/VMS docs on e-bay, along with some $ Oracle books, vintage hardware, etc.  @ Feel free to take a look - hope this link works as it sure looks funny:  W http://search.ebay.com/_W0QQfgtpZ1QQfrppZ25QQfsooZ1QQfsopZ1QQsassZbig-daddy-enterprises      thanks for looking!  Steve  Steve Kulpa 
 Knoxville, TN  VAX/VMS fan since Version 2    ------------------------------  $ Date: Thu, 3 Feb 2005 07:32:37 -0500) From: "Neil Rieck" <n.rieck@sympatico.ca> B Subject: Re: How do I use terminal emulator with escape sequences?9 Message-ID: <PRoMd.2946$lw4.706990@news20.bellglobal.com>   = "Keith Cayemberg" <keith.cayemberg@arcor.de> wrote in message < news:42014462$0$18568$9b4e6d93@newsread4.arcor-online.net..." > john_20_28_2000@yahoo.com wrote: > C Unless I've missed it, I haven't seen anyone describe direct cursor K addressing. I've got an alarm delivery application that uses SYS$BRKTHRU to E put messages on line 24 of selected terminals and it works like this.   0 esc7          (save the current cursor position)" esc[24;1H (go to row 24, column 1)* xxx             (output the alarm message)" esc[0K      (clear to end of line)' esc8          (restore cursor position)   L Like other examples listed by others, I've declared all my escape sequences M in a file which is included by anyone wishing to do direct manipulation of a  H terminal or printer. Check out the following link if you are interested.  = http://www3.sympatico.ca/n.rieck/demo_vms/device_controls.zip     
 Neil Rieck Kitchener/Waterloo/Cambridge,  Ontario, Canada.8 http://www3.sympatico.ca/n.rieck/links/cool_openvms.html   ------------------------------  # Date: Thu, 03 Feb 2005 17:40:31 GMT " From:   VAXman-  @SendSpamHere.ORG( Subject: HP rx2600 rack mount conversion0 Message-ID: <00A3ED76.02EAF52C@SendSpamHere.ORG>  F I have one of the rx2600 servers from the Itanium Developer's Forum.  D This unit arrived in the "Jersey Wall" floor pedestal configuration.E I need to rack mount this system.  Has anyone here done the same and, E if so, what is the part number.  I have found a part number searching E HP's site (MFG#: A9911A) which says it is "HP Integrity rx2600 server E rack bezel upgrade.  As luck would have it, there's no picture and no D specification.  It seems to me to only be the face plate and it is aC tad pricey for just that if it does not contain all of the mounting  hardware to stuff it in a rack.   E I have sent several emails about this to the folks that organized the E IDF but have not received a single response.  I have a lot of Itanium / here that I can't use if I can't rack mount it.   D Perhaps some of the VMS engineering folk here know who to ask within! HP.  All I need is the part #(s).    --  < http://www.ProvN.com  for the *best* OpenVMS system security=                       solutions that others only claim to be.  --  , Cyber-Terrorism (si'-ber tayr'-or-iz-em) n.:M   The release of, the sale of, or the use of any Micro$oft software product!   --  K VAXman- A Bored Certified VMS Kernel Mode Hacker   VAXman(at)TMESIS(dot)COM    ------------------------------  $ Date: Thu, 3 Feb 2005 13:21:38 -0500< From: "Peter Weaver" <WeaverConsultingServices@sympatico.ca>, Subject: Re: HP rx2600 rack mount conversion, Message-ID: <36f8dnF4tv2bhU1@individual.net>    VAXman- @SendSpamHere.ORG wrote: >...G > IDF but have not received a single response.  I have a lot of Itanium 1 > here that I can't use if I can't rack mount it.  >...  H While searching for information about the RX2600 I noticed that there isG a manual named hp workstations zx6000, hp server rx2600 - tower to rack C and rack to tower system conversion guide (a7857-90017) on the page  http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual&locale=en_US&docIndexId=179911&taskId=101&prodTypeId=15351&prodSeriesId=447335   B The document mentions some part numbers, but I have not read it inD detail to see if it gives the part number you are looking for. MaybeA searching on the part numbers if gives might turn up what you are  looking for.   --   Peter Weaver Weaver Consulting Services Inc.  Canadian VAR for CHARON-VAX  www.weaverconsulting.ca    ------------------------------   Date: 3 Feb 2005 10:27:42 -0800 ! From: kenneth.randell@verizon.net , Subject: Re: HP rx2600 rack mount conversionC Message-ID: <1107455262.334578.101620@c13g2000cwb.googlegroups.com>   ! VAXman-  @SendSpamHere.ORG wrote: F > I have one of the rx2600 servers from the Itanium Developer's Forum.  F > This unit arrived in the "Jersey Wall" floor pedestal configuration.G > I need to rack mount this system.  Has anyone here done the same and, G > if so, what is the part number.  I have found a part number searching G > HP's site (MFG#: A9911A) which says it is "HP Integrity rx2600 server G > rack bezel upgrade.  As luck would have it, there's no picture and no F > specification.  It seems to me to only be the face plate and it is aE > tad pricey for just that if it does not contain all of the mounting ! > hardware to stuff it in a rack.  >   ? Looks to me like you want AB376A for the actual rack-mount kit.   = This is called out on page 5 of the QuickSpecs and also here:   N http://www.hp.com/products1/servers/integrity/entry_level/rx2620/supplies.html  B A9911A looks to me like just the front plastic cover bezel. If I'mE right, then there are two parts for it; A7231-04055 which is the left E bezel & latch, A7231-04053, which is the right side.  I got this from G the rx2600 I have, but it was ordered with the pedastal conversion kit.    ------------------------------  $ Date: Thu, 3 Feb 2005 08:55:51 -0500* From: "Syltrem" <syltremzulu@videotron.ca> Subject: Intrusion attempts 4 Message-ID: <E8qMd.2739$df.104601@tor-nn1.netcom.ca>   Hi   When I do the following:$ $ SET AUDIT/ALARM/ENABLE=LOGFAIL=ALL  J I will get a message similar to this one when a failed login attempt is is detected    F %%%%%%%%%%%  OPCOM   3-FEB-2005 08:41:24.96  %%%%%%%%%%%    (from node	 KRONOS at    3-FEB-2005 08:41:24.97) ( Message from user AUDIT$SERVER on KRONOS4 Security alarm (SECURITY) on KRONOS, system id: 10509 Auditable event:          Local interactive login failure 1 Event time:                3-FEB-2005 08:41:24.97 " PID:                      204B826B# Process name:             _VTA2781: ! Username:                 <login> = Terminal name:            VTA2781, _NTY3751, [166.110.120.82]   Remote node fullname:     TELNET" Remote username:          A66E7852; Status:                   %LOGIN-F-NOSUCHUSER, no such user   E Is there any way to determine what username was actually entered? The I AUDIT$SERVER message always shows <login> unless an actual username (i.e. ' one that exists in sysuaf) was entered.    Thanks   --   Syltrem    OpenVMS 7.3-1 + Oracle 8.1.7.4H http://pages.infinit.net/syltrem (OpenVMS related web site, en franais)% ---zulu is not in my email address---    ------------------------------   Date: 3 Feb 2005 07:21:25 -0800 ) From: "Ken Robinson" <kenrbnsn@rbnsn.com>  Subject: Re: Intrusion attempts C Message-ID: <1107444085.084699.272990@f14g2000cwb.googlegroups.com>    Syltrem wrote: > Hi >  > When I do the following:& > $ SET AUDIT/ALARM/ENABLE=LOGFAIL=ALL > F > I will get a message similar to this one when a failed login attempt is is 
 > detected >  > C > %%%%%%%%%%%  OPCOM   3-FEB-2005 08:41:24.96  %%%%%%%%%%%    (from  node > KRONOS at  >   3-FEB-2005 08:41:24.97) * > Message from user AUDIT$SERVER on KRONOS6 > Security alarm (SECURITY) on KRONOS, system id: 1050; > Auditable event:          Local interactive login failure 3 > Event time:                3-FEB-2005 08:41:24.97 $ > PID:                      204B826B% > Process name:             _VTA2781: # > Username:                 <login> ? > Terminal name:            VTA2781, _NTY3751, [166.110.120.82] " > Remote node fullname:     TELNET$ > Remote username:          A66E7852= > Status:                   %LOGIN-F-NOSUCHUSER, no such user  > G > Is there any way to determine what username was actually entered? The E > AUDIT$SERVER message always shows <login> unless an actual username  (i.e. ) > one that exists in sysuaf) was entered.   A If the person enters the invalid name enough times to trigger the 9 breakin detection then the message includes the username.   8 %%%%%%%%%%%  OPCOM   3-FEB-2005 10:15:23.86  %%%%%%%%%%%' Message from user AUDIT$SERVER on XXXXX A Security alarm (SECURITY) and security audit (SECURITY) on XXXXX,  system id: 1929 : Auditable event:          Remote interactive login failure1 Event time:                3-FEB-2005 10:15:23.85 " PID:                      000008E4! Process name:             _TNA48: ! Username:                 <login> < Terminal name:            TNA48:, _TNA48:, Host: XXXXX Locn: _FTA6:/ROBINSON # Remote node id:           458140170  Remote node fullname:     XXXXX ) Remote username:          TELNET_0AAA4E1B ; Status:                   %LOGIN-F-NOSUCHUSER, no such user    xxxxx$8 %%%%%%%%%%%  OPCOM   3-FEB-2005 10:15:36.65  %%%%%%%%%%%' Message from user AUDIT$SERVER on XXXXX A Security alarm (SECURITY) and security audit (SECURITY) on XXXXX,  system id: 1929 > Auditable event:          Remote interactive breakin detection1 Event time:                3-FEB-2005 10:15:36.65 " PID:                      000008E5! Process name:             _TNA49:   Username:                 NOUSER< Terminal name:            TNA49:, _TNA49:, Host: XXXXX Locn: _FTA6:/ROBINSON # Remote node id:           458140170  Remote node fullname:     XXXXX ) Remote username:          TELNET_0AAA4E1B ; Status:                   %LOGIN-F-NOSUCHUSER, no such user    Ken    ------------------------------  $ Date: Thu, 3 Feb 2005 12:48:42 -0500* From: "Syltrem" <syltremzulu@videotron.ca> Subject: Re: Intrusion attempts 4 Message-ID: <wstMd.2759$df.104773@tor-nn1.netcom.ca>  G I have tried and it works as you say but only returns the LAST username D tried (I can try 5 different usernames and only the last one will be recorded in the message). J It would be great if we could have the info before that. I wonder why they don't supply the info. Thanks   --   Syltrem    OpenVMS 7.3-1 + Oracle 8.1.7.4H http://pages.infinit.net/syltrem (OpenVMS related web site, en franais)% ---zulu is not in my email address--- > "Ken Robinson" <kenrbnsn@rbnsn.com> a crit dans le message de= news:1107444085.084699.272990@f14g2000cwb.googlegroups.com...  >  > Syltrem wrote: > > Hi > >  > > When I do the following:( > > $ SET AUDIT/ALARM/ENABLE=LOGFAIL=ALL > > H > > I will get a message similar to this one when a failed login attempt > is is  > > detected > >  > > E > > %%%%%%%%%%%  OPCOM   3-FEB-2005 08:41:24.96  %%%%%%%%%%%    (from  > node
 > > KRONOS at  > >   3-FEB-2005 08:41:24.97) , > > Message from user AUDIT$SERVER on KRONOS8 > > Security alarm (SECURITY) on KRONOS, system id: 1050= > > Auditable event:          Local interactive login failure 5 > > Event time:                3-FEB-2005 08:41:24.97 & > > PID:                      204B826B' > > Process name:             _VTA2781: % > > Username:                 <login> A > > Terminal name:            VTA2781, _NTY3751, [166.110.120.82] $ > > Remote node fullname:     TELNET& > > Remote username:          A66E7852? > > Status:                   %LOGIN-F-NOSUCHUSER, no such user  > > I > > Is there any way to determine what username was actually entered? The G > > AUDIT$SERVER message always shows <login> unless an actual username  > (i.e. + > > one that exists in sysuaf) was entered.  > C > If the person enters the invalid name enough times to trigger the ; > breakin detection then the message includes the username.  > : > %%%%%%%%%%%  OPCOM   3-FEB-2005 10:15:23.86  %%%%%%%%%%%) > Message from user AUDIT$SERVER on XXXXX C > Security alarm (SECURITY) and security audit (SECURITY) on XXXXX,  > system id: 1929 < > Auditable event:          Remote interactive login failure3 > Event time:                3-FEB-2005 10:15:23.85 $ > PID:                      000008E4# > Process name:             _TNA48: # > Username:                 <login> > > Terminal name:            TNA48:, _TNA48:, Host: XXXXX Locn: > _FTA6:/ROBINSON % > Remote node id:           458140170 ! > Remote node fullname:     XXXXX + > Remote username:          TELNET_0AAA4E1B = > Status:                   %LOGIN-F-NOSUCHUSER, no such user  >  > xxxxx$: > %%%%%%%%%%%  OPCOM   3-FEB-2005 10:15:36.65  %%%%%%%%%%%) > Message from user AUDIT$SERVER on XXXXX C > Security alarm (SECURITY) and security audit (SECURITY) on XXXXX,  > system id: 1929 @ > Auditable event:          Remote interactive breakin detection3 > Event time:                3-FEB-2005 10:15:36.65 $ > PID:                      000008E5# > Process name:             _TNA49: " > Username:                 NOUSER> > Terminal name:            TNA49:, _TNA49:, Host: XXXXX Locn: > _FTA6:/ROBINSON % > Remote node id:           458140170 ! > Remote node fullname:     XXXXX + > Remote username:          TELNET_0AAA4E1B = > Status:                   %LOGIN-F-NOSUCHUSER, no such user  >  > Ken  >    ------------------------------   Date: 3 Feb 2005 11:59:05 -0600  From: briggs@encompasserve.org Subject: Re: Intrusion attempts 3 Message-ID: <Uv4Zb812uvI5@eisner.encompasserve.org>   a In article <wstMd.2759$df.104773@tor-nn1.netcom.ca>, "Syltrem" <syltremzulu@videotron.ca> writes: I > I have tried and it works as you say but only returns the LAST username F > tried (I can try 5 different usernames and only the last one will be > recorded in the message). L > It would be great if we could have the info before that. I wonder why they > don't supply the info.  B The concern that I have heard expressed is that if someone is in aF hurry, they are likely to type their password into the username field.@ If this makes it into a log file or operator console hardcopy or  whatever, that becomes an issue.  B So the compromise position is that you log the username only if it? is a superficially valid username (exists in the UAF) and don't = log it if it is facially invalid (does not exist in the UAF).   C One assumes that the bad guys aren't using this as a covert channel < to determine which usernames are valid by listening to OPCOM< console chatter in the next room and counting the characters2 in the login failure audits being printed to OPA0:   	John Briggs   ------------------------------  # Date: Thu, 03 Feb 2005 19:06:58 GMTn& From: hoffman@hp.nospam (Hoff Hoffman), Subject: Re: Is there a FAQ for this group ?2 Message-ID: <mDuMd.7165$iZ5.6235@news.cpqcorp.net>  h In article <nhk201hdac9k1hiogp8h22v9bu4l8iruth@4ax.com>, John Laird <nospam@laird-towers.org.uk> writes:5 :On Wed, 02 Feb 2005 15:24:05 -0500, Tom Rauschenbach # :<tomsusenet@tomsdomain.org> wrote:  :r0 :>Does a FAQ for this group get posted monthly ?  E   No.  It's comparatively huge, so I don't reposted it.  I also don'teE   receive many updates of late, save for references to various rottedi   URLs.    :>Is it on a W3 page anywhere ?  :  :www.hp.com/go/openvms/faq/  : M :Google search for "comp.os.vms faq" brings up a slightly out-of-date versionO :at www.faqs.org S  A   The January 2005 edition is wandering out with the OpenVMS V8.2 @   release; it's on the Freeware, and will be posted at the aboveB   website in the near future.  Once I am able to confirm the kits,C   files and such are posted, I will be cross-posting the FAQ out to-B   the various newsgroups, where faqs.org and other sites will pick   it up.  B   The biggest change in the new edition are "live" HTML links, perB   popular requests.  (The HTML-format FAQ is still hard to search,A   however.)  Various older and now rotted URLs have been updated,eB   as well, and the edition obviously includes V8.2-related OpenVMS   information, as well.o  = :- the definitive version is hosted by HP as it is maintainede> : by an OpenVMS engineering stalwart (Stephen "Hoff" Hoffman).  >   Isn't there a prescription cream for stalwart removal?   :-)  N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq N  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.como   ------------------------------  $ Date: Thu, 3 Feb 2005 09:38:28 -0500= From: "John Gemignani, Jr." <john@nfw-invalid.cibtrikker.com>a" Subject: Re: NFS v3 client support, Message-ID: <EJGdnQBP_OL5qp_fRVn-pQ@dls.net>  9 "Andrew Burghardt" <abob@speakeasy.net> wrote in message n, news:hLadnY71D_oSDpzfRVn-jw@speakeasy.net... > Hi.u >tM > Has support for nfsv3 been added to the TCPIP nfs client? I noticed it has  J > been added to the server since v5.1 or so, but I haven't found a recent I > definitive answer about the client. I have TCPIP v5.4 ECO 1 on a DS20E  M > from which I want to send large image files (a select few being > 4GB) off h5 > to a RAID rack attached to a Proliant Linux server.d > 	 > Cheers.  >d > Andrew  = No, it hasn't and it definitely won't be in the next release.    -John    ------------------------------   Date: 3 Feb 2005 07:29:42 -0600e; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler)n Subject: Re: Official Logo3 Message-ID: <eyTg4K+AKgqJ@eisner.encompasserve.org>m  d In article <mddbrb267zv.fsf@panix5.panix.com>, Rich Alderson <news@alderson.users.panix.com> writes:8 > Alan Frisbie <Usenet02_REMOVE@Flying-Disk.com> writes: > # >> The Cheshire Cat was a good one.- > 0 > Of course, Chester was *not* the Cheshire Cat.      Chester?  IIRC Albert.b   ------------------------------  % Date: Thu, 03 Feb 2005 18:21:31 +110004 From: Paddy O'Brien <paddy.o'brien@transgrid.com.au>( Subject: Re: OT: Battersea Power Station/ Message-ID: <4201D0FB.3000504@transgrid.com.au>l   Roy,   :-)y   ROTFLM*O   Regards, Paddy   Roy Omond wrote: > Paddy O'Brien wrote: >  >> VAXman- wrote:  >> [...snip...]  >> >>>nH >>> Surely that trek didn't take you across the Millenium foot bridge at >>> that time. h >> >>E >> Yes, you are right.  I am suffering from Altzhiemers or something.  >  > D > Bummer!  And there was me imagining that Paddy "Norfolk Lad" could > actually Walk on Water :-) > , > Ah well, another myth gone down the drain.      G ***********************************************************************0  C "This electronic message and any attachments may contain privilegedc> and confidential information intended only for the use of the B addressees named above.  If you are not the intended recipient of C this email, please delete the message and any attachment and adviseeB the sender.  You are hereby notified that any use, dissemination, 7 distribution, reproduction of this email is prohibited.i  A If you have received the email in error, please notify TransGrid iA immediately.  Any views expressed in this email are those of the g= individual sender except where the sender expressly and with tC authority states them to be the views of TransGrid.  TransGrid uses4> virus-scanning software but excludes any liability for viruses contained in any attachment.  < Please note the email address for TransGrid personnel is now$ firstname.lastname@transgrid.com.au"  G ***********************************************************************-   ------------------------------  % Date: Thu, 03 Feb 2005 18:34:48 +1100d4 From: Paddy O'Brien <paddy.o'brien@transgrid.com.au>( Subject: Re: OT: Battersea Power Station/ Message-ID: <4201D418.1000902@transgrid.com.au>a   John,r  I Yes, probably happy days.  No responsibilities, no kids -- but then I've kD loved the kids and grandkids.  Used to play in a darts team for the + local and in a "pop" band at holiday camps.   I I started work with Eastern Electricity Board at 16.  I gained my degree AE later in life with the Open University -- and my last 18 yrs of life tD with Open VMS :-)  In .uk and .au, I've now worked for 43 1/2 years.  C After EEB, I moved to CEGB HQ next to St Pauls in centre of London.    Regards, Paddy   John Laird wrote:-3 > On Wed, 02 Feb 2005 19:10:11 +1100, Paddy O'Brien5) > <paddy.o'brien@transgrid.com.au> wrote:l >  >  >>John Laird wrote:E >>D >>>I've worked for the CEGB too, but only as a student.  Happy days. >>>g >> >>John,e >>' >>Not able to write to your address ...a >>E >>Where did you work, with whom, are/were you an electrical engineer?  >  > E > Shouldn't be anything wrong with my email address (the nospam@ is a*N > misnomer) but every now and again I think something objects (wrongly) to theM > hyphen, which is quite valid.  You can try my work address which is john at: > yrl dot co dot uk. > J > I worked two summers at the Marchwood research labs in the late 70s.  MyL > first introduction to "proper" computing, including naturally, Adventure -L > on a GEC 4080 ;-)  Running simulations, adapting software, etc.  I had oneL > boss who managed to set fire to his wastepaper basket just behind him, andL > by the time that had triggered a smoke alarm, caused building evacuation ,N > and two volunteers went back in to investigate, he was still sat at his deskJ > merrily smoking his pipe and ignoring the alarm...  Park St used to sendF > down a couple of trees worth of line printer output every day, iirc. > J > Pay in the first summer was about 45/week which wasn't at all bad.  TheN > following year I phoned up to see if I should apply again and they said thatK > wasn't necessary and a job was mine if I wanted it.  On day one, I had to N > drop into personnel to get a pass and it was casually mentioned that after aM > bit of thought they had upped the pay - to 69/week !  Through the summer I I > managed to earn about half of what my annual student grant amounted to, K > which in those days was enough to live on.  And after all that, one of mylM > supervisors wrote me a reference which my first full-time employers told meP4 > had clinched my first job.  As I said, happy days. >       G ***********************************************************************   C "This electronic message and any attachments may contain privileged > and confidential information intended only for the use of the B addressees named above.  If you are not the intended recipient of C this email, please delete the message and any attachment and advise B the sender.  You are hereby notified that any use, dissemination, 7 distribution, reproduction of this email is prohibited.   A If you have received the email in error, please notify TransGrid  A immediately.  Any views expressed in this email are those of the  = individual sender except where the sender expressly and with  C authority states them to be the views of TransGrid.  TransGrid uses > virus-scanning software but excludes any liability for viruses contained in any attachment.  < Please note the email address for TransGrid personnel is now$ firstname.lastname@transgrid.com.au"  G ***********************************************************************O   ------------------------------  % Date: Thu, 03 Feb 2005 18:44:18 +1100B4 From: Paddy O'Brien <paddy.o'brien@transgrid.com.au>( Subject: Re: OT: Battersea Power Station/ Message-ID: <4201D652.7000308@transgrid.com.au>    VAXman- wrote:h > In article <42008938.2050607@transgrid.com.au>, Paddy O'Brien <paddy.o'brien@transgrid.com.au> writes: > {...snip...} > G >>>Surely that trek didn't take you across the Millenium foot bridge at  >>>that time.    >>>  >>D >>Yes, you are right.  I am suffering from Altzhiemers or something. >>J >>I did not even go by Tower Bridge.  I am just remembering 20+ years ago 4 >>and just a few memories of the old power stations. >  > J > I was picturing you taking a deep breath and actually walking across. :) > G Roy Omond felt the same :-)  My grandkids seem to get worried about my   long hair and moustache too.   >  >  > < >>At 60 years old, I am just doing this little memory thing. >  > K > Don't sweat it...  My memories of London are probably pretty good because0L > I have been there 5 times since spring of 2002.  When is the last time you > where there? >  Brian,  I Not been back since I came to .au in 1982.  My parents came over here in  E 1990 and my "kid brother" came in 2001 for my daughter's wedding.  I EI hdn't seen him for about 25 years, and he told me how much my birth town  $ of Norwich had changed since I left.   Regards, Paddy      G ***********************************************************************e  C "This electronic message and any attachments may contain privileged > and confidential information intended only for the use of the B addressees named above.  If you are not the intended recipient of C this email, please delete the message and any attachment and advise B the sender.  You are hereby notified that any use, dissemination, 7 distribution, reproduction of this email is prohibited.0  A If you have received the email in error, please notify TransGrid 0A immediately.  Any views expressed in this email are those of the 2= individual sender except where the sender expressly and with lC authority states them to be the views of TransGrid.  TransGrid uses > virus-scanning software but excludes any liability for viruses contained in any attachment.  < Please note the email address for TransGrid personnel is now$ firstname.lastname@transgrid.com.au"  G ***********************************************************************g   ------------------------------  % Date: Thu, 03 Feb 2005 17:19:50 +0100m0 From: Keith Cayemberg <keith.cayemberg@arcor.de>( Subject: Re: OT: Battersea Power Station@ Message-ID: <42024f26$0$814$9b4e6d93@newsread2.arcor-online.net>   Paddy O'Brien wrote:   > A few snips. >  > Keith Cayemberg wrote: > = >> Just curious, is/was VMS being used in this power station?P >> > Keith, > I > In my days (up to 1982), CEGB was an IBM/Amdahl shop -- 360/370. A few *K > other OS's for minor applications, but I cannot remember the details.  I 3# > cannot remember any DEC machines.N > C > Way back, I was one of the first to install remote access to our 3F > technical programs from our computing centre -- Park Street next to E > Bankside PS.  And the journey Vaxman did was my frequent pickup of RK > output.  Our building was adjacewnt to St Pauls, until we eventually had tH > a remote printer, I had to make that journey for output.  What fun we  > had in the 1960's :-)  > H Thanks for the feedback. When I followed the Wiki link provided by John F Laird, I realized from the closing dates that the adoption of OpenVMS  would be improbable. > 7 >> I'm also fascinated by it's impressive architecture.  >>H > I loved the history of the UK.  Castles, cathedrals and all the rest. H > And, power stations (even gas holders) had something about them.  Pre I > nationalisation, many cities (I was born in Norwich at end of war) had  H > local stations. They might not get too many architectural awards, but  > they had a certain ambience. > I I thought a little more about the attractiveness of the BPS, and I think C< it's in part due to the breakout optimism of the new age of A industrialization that it expresses. Here in Germany, most early cD industrial age architecture didn't survive the wars. Most buildings D which were rebuilt in a former style, were either cathedrals, noble C estates or train stations. Industrial purposed buildings were more  I likely to rebuild in the bland international style. Although there are a eD few exceptions. The Continental Tyre Factory in Hannover-Limmer for A instance looks like a moated castle, at least from the riverside.hB This factory was actually pictured to represent the stability and H security of OpenVMS in a recent iX Magazine article (in German) written I by Andreas Gruhl from Hannover. The article is not available online, but A a PDF can be purchased here.  . http://www.heise.de/kiosk/archiv/ix/04/03/089/     Cheers!y   Keith Cayemberg    ------------------------------  % Date: Thu, 03 Feb 2005 11:49:57 -0600 ( From: brandon@dalsemi.com (John Brandon): Subject: REBOOT or SHUTDOWN, how to tell in SYSSHUTDWN.COM1 Message-ID: <05020311495780@dscis6-0.dalsemi.com>0  F I am wondering if there is a way to capture the P2 flag when executing SYS$SYSTEM:SHUTDOWN.COM   . For example, I have the following two symbols:  Q REBOOT == "@SYS$SYSTEM:SHUTDOWN 0 REBOOT NO YES YES YES REMOVE_NODE,REBOOT_CHECK" U SHUTDOWN == "@SYS$SYSTEM:SHUTDOWN 0 STANDALONE NO YES NO NO REMOVE_NODE,REBOOT_CHECK"E  < (Nothing more than the standard REBOOT and SHUTDOWN symbols) P2 = REBOOT or STANDALONEE    F In SYS$SYSTEM:SYSHUTDWN.COM I log the SHUTDOWN request in a text file:  ( $ TYPE SYS$MANAGER:_SHUTDOWN_<node>.XXX;G SHUTDOWN/REBOOT (SHUTDOWN) on <node> requested by <user> at <date-time>     M During STARTUP if this file is detected then I can assume that the server was K SHUTDOWN and did not experience a CRASH.  If the file is NOT there then the  server CRASHed.     H Therefore I can differentiate between a CRASH and a requested SHUTDOWN. L However it would be nice to differentiate between a REBOOT and a STANDALONE.  M I could change the symbols (REBOOT and SHUTDOWN) to execute a command file to  do so but I would rather not.     
 Any ideas?     John "REBOOT" Brandonu VMS Systems Administrator * firstname.lastname.spam.me.not@dalsemi.com   ------------------------------  % Date: Thu, 03 Feb 2005 22:13:02 +0800  From: prep@prep.synonet.comd> Subject: Re: There goes the volume market. Remind me again....- Message-ID: <877jlp7mvl.fsf@prep.synonet.com>   / JF Mezei <jfmezei.spamnot@teksavvy.com> writes:    > David Mathog wrote:0  D >> run major companies, as Carly and Curly are.)  HP got in bed withF >> Intel on Itanium, spent ungodly sums on developing it, scuttled allD >> of their other processors in its favor BEFORE it was available to >> replace them   ; > Actually you can blame DEC for this.. (Ironic isn't it ?)   % I'm not sure where you get this from.   @ > I think that Digital really scared the market when it launchedF > Alpha. HP probably figured there was no way it could compete againstB > Alpha and figured the only way would be to team up with Intel to > produce a competitor.C  
 Not quite.  D hp had a research line that came from the VLIW machines that ?Cydra?F built, and included Plahdoh et al. They looked at the comming walls inF CPU performance, just as the Prism/Alpha people did. See the Alpha ARMF for that. The path they picked was reasonable *at the time*. Their end9 result was that it was a better bet to bank on a compilerAF break-through and go with agressive speculative execution than to backB being able to get Out-of-Order, renaming CPUs working. Hence EPIC.  D > So, HP launches a project with Intel to compete against Alpha, andA > that scared the bejesus out of Digital which was already in the0D > process of self destructing (to a point where DEC had announced itF > woudl post Tru64 to IA64 since at that time, IA64 was to replace the" > 8086 as the "industry standard".  C hp had lots of problems, so they went to intel and proposed a joint.@ development. This had CPU independant pluses for both. It got hpH an out from FABs, with out having to be totally at the mercy of merchantI FAB houses. Intel was able to dump the rest of the industry from its coatoD tails by putting all the EPIC/unobtainium/itanic stuff in a seperateB company that had NO cross licences with anyone. hp and intel only, every one else can take a bath.3  C > From a management point of view, up to that point, HP's decisions D > couldn't be faulted. However, as soon as it became clear that IA64B > was a dog (if DEC's engineers could write white papers about howB > IA64 was flawed in its whole architecture, then Shirley HP wouldB > have had access to this information too), well, that is when the > problem really started.   D The EV6 blew hp's second half of why they did EPIC out of the water.C It was the existance proof that an agressive OoO CPU could not onlya0 work, but it would deliver outragous performace.  ? > Should HP have cancelled IA64 when it became clear this was ao > mistake of EPIC proportions ?s  D Rumour was, that hp engineers said just that, and wanted to kill theF dog. intel, and possible hp managment said onward no matter, full tilt ahead and damb the windmills!!1m  E > What I find interesting is that meanwhile, despite the fact that it0D > was slated for auto-destruct, PA-Risc was able to keep up with the@ > Jones' and remain a viable competitive platform in the market.  F > So HP never really scuttled Pa-Risc prematurely. In fact, they still+ > have one or two Pa-Riscs iterations left.s  C Well, yes and no. They stuck its head in the bucket, but forgot theoD water... So the PA3 had to do a Lazerus, and on it went. And on, andF into another decade, and another century, finaly matching the schedule0 slipage of Babbage, then it limped out the door.  F By this time it had already killed MIPS and Alpha, so even if it never= warmed a clock, it was not a total failure by some standards.a   Pass the Leppard...   @ Note that the claims are now 5x rather than 2x so that is a sort of an advance.   -- e< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.a@                                              West Australia 6076* comp.os.vms,- The Older, Grumpier Slashdot. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------  % Date: Thu, 03 Feb 2005 17:48:13 +0100 0 From: Keith Cayemberg <keith.cayemberg@arcor.de>> Subject: Re: There goes the volume market. Remind me again....@ Message-ID: <420255ce$0$822$9b4e6d93@newsread2.arcor-online.net>   prep@prep.synonet.com wrote:  1 > JF Mezei <jfmezei.spamnot@teksavvy.com> writes:  >  >  >>David Mathog wrote:y >  > D >>>run major companies, as Carly and Curly are.)  HP got in bed withF >>>Intel on Itanium, spent ungodly sums on developing it, scuttled allD >>>of their other processors in its favor BEFORE it was available to >>>replace them  >  > ; >>Actually you can blame DEC for this.. (Ironic isn't it ?). >  > ' > I'm not sure where you get this from.h >  > @ >>I think that Digital really scared the market when it launchedF >>Alpha. HP probably figured there was no way it could compete againstB >>Alpha and figured the only way would be to team up with Intel to >>produce a competitor.i >  >  > Not quite. > F > hp had a research line that came from the VLIW machines that ?Cydra?H > built, and included Plahdoh et al. They looked at the comming walls inH > CPU performance, just as the Prism/Alpha people did. See the Alpha ARMH > for that. The path they picked was reasonable *at the time*. Their end; > result was that it was a better bet to bank on a compilertH > break-through and go with agressive speculative execution than to backD > being able to get Out-of-Order, renaming CPUs working. Hence EPIC. >  > D >>So, HP launches a project with Intel to compete against Alpha, andA >>that scared the bejesus out of Digital which was already in theeD >>process of self destructing (to a point where DEC had announced itF >>woudl post Tru64 to IA64 since at that time, IA64 was to replace the" >>8086 as the "industry standard". >  > E > hp had lots of problems, so they went to intel and proposed a joint B > development. This had CPU independant pluses for both. It got hpJ > an out from FABs, with out having to be totally at the mercy of merchantK > FAB houses. Intel was able to dump the rest of the industry from its coatVF > tails by putting all the EPIC/unobtainium/itanic stuff in a seperateD > company that had NO cross licences with anyone. hp and intel only,! > every one else can take a bath.  >  > C >>From a management point of view, up to that point, HP's decisions D >>couldn't be faulted. However, as soon as it became clear that IA64B >>was a dog (if DEC's engineers could write white papers about howB >>IA64 was flawed in its whole architecture, then Shirley HP wouldB >>have had access to this information too), well, that is when the >>problem really started.0 >  > F > The EV6 blew hp's second half of why they did EPIC out of the water.E > It was the existance proof that an agressive OoO CPU could not onlyx2 > work, but it would deliver outragous performace. > & AlphaPowered - Technical PresentationsS http://web.archive.org/web/20010203183000/alphapowered.com/alpha_tech_presents.html     Alpha and IA64 White Paper - PDF^ http://web.archive.org/web/20010203183000/http://alphapowered.com/presentations/alpha_ia64.pdf   > ? >>Should HP have cancelled IA64 when it became clear this was ac >>mistake of EPIC proportions ?  >  > F > Rumour was, that hp engineers said just that, and wanted to kill theH > dog. intel, and possible hp managment said onward no matter, full tilt! > ahead and damb the windmills!!1  >  > E >>What I find interesting is that meanwhile, despite the fact that iteD >>was slated for auto-destruct, PA-Risc was able to keep up with the@ >>Jones' and remain a viable competitive platform in the market. >  > F >>So HP never really scuttled Pa-Risc prematurely. In fact, they still+ >>have one or two Pa-Riscs iterations left.  >  > E > Well, yes and no. They stuck its head in the bucket, but forgot thehF > water... So the PA3 had to do a Lazerus, and on it went. And on, andH > into another decade, and another century, finaly matching the schedule2 > slipage of Babbage, then it limped out the door. > H > By this time it had already killed MIPS and Alpha, so even if it never? > warmed a clock, it was not a total failure by some standards.e >  > Pass the Leppard...  > B > Note that the claims are now 5x rather than 2x so that is a sort > of an advance. >    ------------------------------  $ Date: Thu, 3 Feb 2005 12:00:51 -0500# From: "John Smith" <a@nonymous.com>l> Subject: Re: There goes the volume market. Remind me again...., Message-ID: <gP2dnXXQ4sZZxZ_fRVn-hg@igs.net>   Keith Cayemberg wrote: >o( > AlphaPowered - Technical Presentations >rL http://web.archive.org/web/20010203183000/alphapowered.com/alpha_tech_presen ts.html, >F" > Alpha and IA64 White Paper - PDF > L http://web.archive.org/web/20010203183000/http://alphapowered.com/presentati ons/alpha_ia64.pdf    J I think I will e-mail these links to the HP BoD and to all the Wall Street$ analysts, and press contacts I know.  ) "Bubble, bubble, toil and trouble......."  -- Bill Shakespeare%   ------------------------------  # Date: Thu, 03 Feb 2005 19:20:46 GMT # From: hoff@hp.nospam (Hoff Hoffman) + Subject: Re: vaxcluster vms v5.5-2 and v7.3a2 Message-ID: <iQuMd.7167$iZ5.5239@news.cpqcorp.net>  Z In article <9eac7199.0502010043.369f54d@posting.google.com>, br@b-riis.dk (Bendix) writes:G :I am trying to add a VAX running VMS v7.3 to a cluster with two VAX'esA :running VMS v5.5-2.  H   The official version support matrix is in the Cluster Software Product$   Description; in the Cluster SPD.    A   The (undocumented) cluster software protocol check -- which canLF   potentially be somewhat more lenient than the official configurationA   support, but that the software check succeeds does not mean thewF   configuration will work nor that the configuration will be supportedD   -- are based on the system data cell CLU$GB_CLUVER -- the versions8   must be within one for the protocol check to succeed.   :   You will fail the hard limit with V5.5-2 and V7.3, IIRC.  E   But again, the official mixed-version cluster support is the matrixmC   within the Cluster Software Product Description -- you might welltB   see crashes, corruptions or other problems, even if the protocolA   check passes.  This version check is the hard limit for mixing EA   versions, in other words, and does not necessarily indicate ther&   actual range of versions might work.  B   I don't immediately have a mapping of the CLU$GB_CLUVER versions    from various OpenVMS releases.  N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faqvN  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.coma   ------------------------------   End of INFO-VAX 2005.068 ************************