1 INFO-VAX	Wed, 24 Oct 2001	Volume 2001 : Issue 591       Contents:
 Re: <None>
 Re: <None> Re: Advanced Server  Re: BACKUP ACCVIO  Backup tape-label problem  RE: BCC support in VMSMAIL Re: BCC support in VMSMAIL Re: BCC support in VMSMAIL( CLD & error handling from within program, Re: CLD & error handling from within program Compaq financial humour !  Re: Compaq financial humour !  Re: Compaq financial humour ! & Compaq OpenVMS Network Monitoring Tool* Re: Compaq OpenVMS Network Monitoring Tool* Re: Compaq OpenVMS Network Monitoring Tool* Re: Compaq OpenVMS Network Monitoring Tool$ Re: Compaq: VMS is alive and kicking$ Re: Compaq: VMS is alive and kicking$ Re: Compaq: VMS is alive and kicking$ Re: Compaq: VMS is alive and kicking4 Re: Converting an ODS-2 to an ODS-5 file system disk4 Re: Converting an ODS-2 to an ODS-5 file system disk4 Re: Converting an ODS-2 to an ODS-5 file system disk Re: copy files in DCLedit  DECWriter III available I Re: dynamic_cast failure in Compaq C++ version 6.3 on VMS on DEC Alpha... I Re: dynamic_cast failure in Compaq C++ version 6.3 on VMS on DEC Alpha...  Re: ECC  Re: ECC  Re: ECC  Re: ECC  Re: ECC 2 Finding GNU "find" that builds from source for VMS6 Re: Finding GNU "find" that builds from source for VMS) Re: Fwd: Compaq: VMS is alive and kicking ) Re: Fwd: Compaq: VMS is alive and kicking ) Re: Fwd: Compaq: VMS is alive and kicking ) Re: Fwd: Compaq: VMS is alive and kicking ! Re: How know last system restart? ! Re: How know last system restart? ! Re: How know last system restart? ! Re: How know last system restart? = How to redirect output&error into a single file in sys$creprc A Re: How to redirect output&error into a single file in sys$creprc  Re: I am changing jobs Re: It's Friday  Re: mode nibble??  Re: mode nibble?? = Re: PC164, OVMS7.2, isacfg and graphic cards (MACH64, S3 968) = Re: PC164, OVMS7.2, isacfg and graphic cards (MACH64, S3 968) B Re: SAMBA VMS and Windows XP - Re: Windows XP reality check please7 Re: SEDT problems on RedHat 7.1 (was Re: EDT for Linux) 7 Re: SEDT problems on RedHat 7.1 (was Re: EDT for Linux) 3 Re: Shared file access under NT and VMS question... ! Re: Single or Multiple Sys Disks? ! Re: Single or Multiple Sys Disks?  Re: Socket problem-URGENT  Re: TPU/EVE Spelling Checker( Re: vt420 soft characters example (drcs)# Re: Windows XP reality check please  Re: Working sets' Re: WRITEBOOT and dual-boot bootblocks? ' Re: WRITEBOOT and dual-boot bootblocks? ' Re: WRITEBOOT and dual-boot bootblocks? ' Re: WRITEBOOT and dual-boot bootblocks? / Re: X server and SET DISPLAY on different port? / Re: X server and SET DISPLAY on different port? / Re: X server and SET DISPLAY on different port? / Re: X server and SET DISPLAY on different port? / Re: X server and SET DISPLAY on different port? / Re: X server and SET DISPLAY on different port? / Re: X server and SET DISPLAY on different port?  XP1000 problems  Re: XP1000 problems  Re: XP1000 problems # Re: [MOZILLA] Burner of CPU time!!!   F ----------------------------------------------------------------------    Date: 24 Oct 2001 03:47:05 +0800, From: Paul Repacholi <prep@prep.synonet.com> Subject: Re: <None> M Message-ID: <87u1wqf8au.fsf@k9.i-did-not-set--mail-host-address--so-shoot-me>   / koehler@encompasserve.org (Bob Koehler) writes:   G >    Right now I think there's a problem of lack of information.  Which D >    "set of hardware components"?  And why should I have to contact  >    Microsoft if I change them?  D Someone experimented with a test version and forwarded the result toD either the Register or The Inquirer. (Sorry, can't remember) But theA other one and /. probably picked it up anyway. Should be in their  archive.   --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------  % Date: Tue, 23 Oct 2001 23:15:37 +0100 / From: "Adam Price" <adam+usenet@pappnase.co.uk>  Subject: Re: <None> C Message-ID: <g%lB7.57157$uh1.6251568@news6-win.server.ntlworld.com>    "Paul Repacholi" <prep@prep.synonet.com> wrote in message news:87u1wqf8au.fsf@k9.i-did-not-set--mail-host-address--so-shoot-me... 1 > koehler@encompasserve.org (Bob Koehler) writes:  > I > >    Right now I think there's a problem of lack of information.  Which F > >    "set of hardware components"?  And why should I have to contact" > >    Microsoft if I change them? > F > Someone experimented with a test version and forwarded the result toF > either the Register or The Inquirer. (Sorry, can't remember) But theC > other one and /. probably picked it up anyway. Should be in their 
 > archive. For details see   1 http://www.theregister.co.uk/content/4/20282.html 1 http://www.theregister.co.uk/content/4/20433.html    ------------------------------    Date: 24 Oct 2001 04:27:19 +0800, From: Paul Repacholi <prep@prep.synonet.com> Subject: Re: Advanced ServerM Message-ID: <87itd6f6fs.fsf@k9.i-did-not-set--mail-host-address--so-shoot-me>   A The licences you have, plus the extra 50 should be fine for up to # 90 people to have access at a time.    Don't you have CSLG there?   --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------  % Date: Tue, 23 Oct 2001 22:36:09 +0200   From: Paul Sture <paul@sture.ch> Subject: Re: BACKUP ACCVIO+ Message-ID: <VA.00000495.05105ad9@sture.ch>   B In article <oRiMdDNO4y6S@tachxxsoftxxconsult>, Wayne Sewell wrote:P > In article <VA.00000493.2b57f98f@sture.ch>, Paul Sture <paul@sture.ch> writes: > > Alpha VMS V7.2-1H1 > > J > > Before I report this to CSC, anyone experiencing BACKUP ACCVIOs? I've K > > had it more than once now. Nothing relevant in the hardware error logs.  > > F > > One of my backups failed with an access violation on mounting the F > > second tape volume. Volume 2 was not initialized by the operation , > > (still had a saveset from August on it). > >  > > From the logfile:  > >  > > (23:12) $!" > > (23:12) $    backup/noassist -* > >           DSA127:[*...]/since=backup -. > >           /ignore=(interlock,label_proc) -6 > >           $1$MUA25:DSA127_SUN.bck /media=compact -G > >           /label=(03WSG0,03WSG1,03WSG2,03WSG3,03WSG4,03WSG5,03WSG6) 4 > > %BACKUP-I-RESUME, resuming operation on volume 2? > > %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual > > > address=0000000056415366, PC=0000000000000000, PS=00000000, > > (00:03) $    bck_stat   = "4/%X1000000C" > > (00:03) $    set noverify ; > > Status of this backup-operation :        (Severity : 4)  > >  > > Other details: > > 0 > > Tape type TZ88 on HSJ50-AX controller HSJ27.K > > Disk being backed up is a 2 member shadowset. Each member consists of 3 > > > striped (9 GB) disks on HSJ50-AX controllers HSJ29, HSJ31.1 > > Firmware version V57J-1 on these controllers.  > >  > K > I assume you are current with your backup patches.  There have been a few H > accvios in backupshr.  I remember one case where the accvio was in theO > condition handler.  The backup got some *other* error, such as input file not O > found, and the bug in the condition handler essentially *converted* the error  > to an accvio!  >  Thanks for the info. ___ 
 Paul Sture Switzerland    ------------------------------   Date: 23 Oct 2001 19:31:36 GMT3 From: gartmann@immunbio.mpg.de (Christoph Gartmann) " Subject: Backup tape-label problem0 Message-ID: <9r4gio$8jm$1@n.ruf.uni-freiburg.de>   Hello,  H OpenVMS 7.1-2 & and a Sony SDT9000 DDS-3 DAT drive: from time to time we get the following error:  G $ BACKUP/NOLOG/NOCRC/GROUP=0/IGNORE=INTERLOCK/NOASSIST/NOALIAS/VERIFY - *   /IMAGE DISKG: MKA500:23OCT01DG.BCK     -   /REWIND/SAVE_SET/LABEL=DG04 -    /BLOCK_SIZE=32256 / %MOUNT-I-MOUNTED, DG04 mounted on _MPI6$MKA500: E %BACKUP-W-MOUNTERR, volume 1 on _MPI6$MKA500 was not mounted because  +  its label does not match the one requested < %BACKUP-I-OPERASSIST, operator assistance has been requested  F Note that the tape has the correct label and that VMS even reports it.F Nevertheless it claims that the label is wrong. Why? When I unload the2 tape in question and reload it everything is fine:  * %BACKUP-I-OPREPLY, operator reply is "NEW"/ %MOUNT-I-MOUNTED, DG04 mounted on _MPI6$MKA500: Q %BACKUP-W-ACCONFLICT, DISKG:[000000]QUOTA.SYS;1 is open for write by another user 1 %BACKUP-I-STARTVERIFY, starting verification pass    Thus, what happens here?   Regards,    Christoph Gartmann   H -- --------------------------------------------------------------------+H | Max-Planck-Institut fuer      Phone   : +49-761-5108-464   Fax: -452 |H | Immunbiologie                                                        |H | Postfach 1169                 Internet: gartmann@immunbio.mpg.de     |H | D-79011  Freiburg, FRG                                               |H +--------- http://www.immunbio.mpg.de/home/english/menue.html ---------+   ------------------------------  # Date: Tue, 23 Oct 2001 22:32:43 GMT L From: winston@SSRL.SLAC.STANFORD.EDU ("Alan Winston - SSRL Admin Cmptg Mgr")# Subject: RE: BCC support in VMSMAIL 8 Message-ID: <00A03F60.6BD0FA3D@SSRL04.SLAC.STANFORD.EDU>  Z In article <0033000039230021000002L012*@MHS>, WILLIAM WEBB <WWEBB1@email.usps.gov> writes:+ >=0ABut were they "To:" or were they "Cc:"?  >   O I know you were kidding, but I'll explain anyway: Our admin types, most of whom N are on Exchange/Outlook  make a  mental distinction between "To:" (which meansM "you are the person who should take action on this message") and "CC:" (which M means "FYI").  Losing the distinction meant they had to read the messages and F think about whether they had to do anything, which slowed things down.  I The ones on Exchange seeing only the addresses on the Exchange server was K impetus for a big push from Admin to get all the scientists and other staff J off of VMS and onto Exchange, which was only thwarted by the global switchJ to PMDF MAIL.  It would have been much harder to justify staying with VMS  if nobody logged into it.      -- Alan    >:^) >  >WWWebb  >  >> -----Original Message----- 2 >> From: Info-VAX-Request@Mvb.Saic.Com at INTERNET* >> Sent: Tuesday, October 23, 2001 9:36 AME >> To: Webb, William W Raleigh, NC; Info-VAX@Mvb.Saic.Com at INTERNET & >> Subject: RE: BCC support in VMSMAIL >> >># >> Thank you all for your feedback. ; >> Aside from relplies here I have received about 50 mails.  >>> >> General response is : we want BCC and  make sure we support >> all transports. >>> >> Well majority have spoken we will have BCC support soon. As >> soon as the >> development >>6 >> work is over I will post a note in this conference.? >> I know there is a lot of work to be done in VMSMAIL, however  >> we need to start  >> with something. >> >> Guy >>- >> Alan Winston - SSRL Admin Cmptg Mgr wrote:  >>9 >> > In article <3BD3EC5E.E683DA66@compaq.com>, Guy Peleg  >> <guy.peleg@compaq.com>  >> > writes: >> > >> > > >> > >Hello All, >> > >G >> > >Lately I have been playing with the idea of adding BCC support to  >> > >VMSMAIL.4 >> > >I would like to get your feedback about this : >> > > >> > >Do we really need this ? >> >> >> > First, despite the crankiness of the rest of this note, I >> want to say that = >> > I really appreciate your participating in this forum and  >> giving customers / >> > a say in the development process.  Thanks.  >> >? >> > If I were still on VMSMAIL I would really like this, but I  >> (and all my> >> > command-line users) are using PMDF MAIL.  BCC gets used a >> fair amount here;; >> > probably not daily, but regularly, and there are cases  >> where nothing else  >> > will answer the need. >> >; >> > >Do we need to have  BCC support sending messages from  >> VMSMAIL to VMSMAIL # >> > >or VMSMAIL to Exchange only ?  >> >? >> > If the support isn't for everything - which probably means  >> for every supported; >> > mail transport - it isn't worth doing.  Picture a user  >> sending a message via@ >> > BCC; if it fails, or (worse) if the messages go through but >> the recipient@ >> > list isn't suppressed, that user will lose all faith in VMS >> MAIL and use  >> > something else. >> >@ >> > I would rather see you fix the peculiarities in To: and CC: >> processing with1 >> > addresses that involve different transports.  >> >< >> > (First, the distinction between To: and CC: is lost and >> everything ends up > >> > as a To: address.  Second, the only addresses a recipient >> on another system8 >> > sees are the ones on that system, so if they do the >> equivalent of a reply/all, ? >> > it only gets their local recipients, not the whole list it  >> was sent to.  This > >> > wreaked havoc around here, and was the reason why we made >> all our users use >> > PMDF MAIL instead.) >> > >> > -- Alan >> > >> >I >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= J >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=. >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D6 >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D5 >> >  Alan Winston --- WINSTON@SSRL.SLAC.STANFORD.EDU ; >> >  Disclaimer: I speak only for myself, not SLAC or SSRL  >> Phone:  650/926-3056 9 >> >  Physical mail to: SSRL -- SLAC BIN 69, PO BOX 4349,  >> STANFORD, CA  94309-0210  >> >I >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= J >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=. >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D6 >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>=   O =============================================================================== 0  Alan Winston --- WINSTON@SSRL.SLAC.STANFORD.EDUM  Disclaimer: I speak only for myself, not SLAC or SSRL   Phone:  650/926-3056 M  Physical mail to: SSRL -- SLAC BIN 69, PO BOX 4349, STANFORD, CA  94309-0210 O ===============================================================================    ------------------------------  % Date: Tue, 23 Oct 2001 21:16:25 -0500 1 From: "David J. Dachtera" <djesys.nospam@fsi.net> # Subject: Re: BCC support in VMSMAIL ' Message-ID: <3BD62479.A8EE71AD@fsi.net>    Brian Tillman wrote: > D > >"Need" is a relative term.  To have any hope of appearing to be a( > >useful mail program, BCC is required. > K > Interesting thought.  Could you explain how BCC is useful for anything at  > all other than SPAM?  @ When you want to send out a notice and include management in theG distro., without the grunts knowing that management is reading the same G message they are, or when you need to send out a notice to a group, but - e-mail addresses should be kept confidential.   6 There are other applications, I'm sure (besides spam).   --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  % Date: Wed, 24 Oct 2001 07:34:29 +0200 & From: Guy Peleg <guy.peleg@compaq.com># Subject: Re: BCC support in VMSMAIL * Message-ID: <3BD652E5.FC5653B2@compaq.com>  B VMSMAIL used to merge CC line and To line. This problem was fixed.J The fix can be obtained by installing VMSxx_MAIL ECO and latest TCPIP ECO.   Guy    WILLIAM WEBB wrote:   ) > But were they "To:" or were they "Cc:"?  >  > :^)  >  > WWWebb >  > > -----Original Message-----3 > > From: Info-VAX-Request@Mvb.Saic.Com at INTERNET + > > Sent: Tuesday, October 23, 2001 9:36 AM F > > To: Webb, William W Raleigh, NC; Info-VAX@Mvb.Saic.Com at INTERNET' > > Subject: RE: BCC support in VMSMAIL  > >  > > $ > > Thank you all for your feedback.< > > Aside from relplies here I have received about 50 mails. > > ? > > General response is : we want BCC and  make sure we support  > > all transports.  > > ? > > Well majority have spoken we will have BCC support soon. As  > > soon as the  > > development  > > 7 > > work is over I will post a note in this conference. @ > > I know there is a lot of work to be done in VMSMAIL, however > > we need to start > > with something.e > >b > > Guy  > >u. > > Alan Winston - SSRL Admin Cmptg Mgr wrote: > > : > > > In article <3BD3EC5E.E683DA66@compaq.com>, Guy Peleg > > <guy.peleg@compaq.com>
 > > > writes:r > > >p > > > >i > > > >Hello All,o > > > >nH > > > >Lately I have been playing with the idea of adding BCC support to > > > >VMSMAIL. 5 > > > >I would like to get your feedback about this :V > > > >k > > > >Do we really need this ?V > > >o? > > > First, despite the crankiness of the rest of this note, Ip > > want to say that> > > > I really appreciate your participating in this forum and > > giving customers0 > > > a say in the development process.  Thanks. > > >o@ > > > If I were still on VMSMAIL I would really like this, but I > > (and all my ? > > > command-line users) are using PMDF MAIL.  BCC gets used aa > > fair amount here;f< > > > probably not daily, but regularly, and there are cases > > where nothing else > > > will answer the need.  > > >A< > > > >Do we need to have  BCC support sending messages from > > VMSMAIL to VMSMAIL$ > > > >or VMSMAIL to Exchange only ? > > >n@ > > > If the support isn't for everything - which probably means > > for every supportedm< > > > mail transport - it isn't worth doing.  Picture a user > > sending a message viaaA > > > BCC; if it fails, or (worse) if the messages go through bute > > the recipienttA > > > list isn't suppressed, that user will lose all faith in VMS  > > MAIL and use > > > something else.e > > >tA > > > I would rather see you fix the peculiarities in To: and CC:t > > processing withs2 > > > addresses that involve different transports. > > >e= > > > (First, the distinction between To: and CC: is lost andg > > everything ends up? > > > as a To: address.  Second, the only addresses a recipient9 > > on another system 9 > > > sees are the ones on that system, so if they do thep > > equivalent of a reply/all,@ > > > it only gets their local recipients, not the whole list it > > was sent to.  This? > > > wreaked havoc around here, and was the reason why we madeD > > all our users useu > > > PMDF MAIL instead.)k > > >l
 > > > -- Alan  > > >  > > >gB > > ============================================================== > > =================e6 > > >  Alan Winston --- WINSTON@SSRL.SLAC.STANFORD.EDU< > > >  Disclaimer: I speak only for myself, not SLAC or SSRL > > Phone:  650/926-3056: > > >  Physical mail to: SSRL -- SLAC BIN 69, PO BOX 4349, > > STANFORD, CA  94309-0210 > > >eB > > ============================================================== > > =================  > >    ------------------------------   Date: 23 Oct 2001 19:10:54 GMT3 From: gartmann@immunbio.mpg.de (Christoph Gartmann)Y1 Subject: CLD & error handling from within programo0 Message-ID: <9r4fbu$7ir$1@n.ruf.uni-freiburg.de>   Hello,  J I would like to use a CLD from within a Pascal program. So far, so good. IL wrote the .CLD-file, I wrote my program and I linked the CLD-object togetherG with the program object file. Everything works as expected. If I omit a<M required parameter, DCL asks for the paramter via LIB$GET_INPUT. If I enter aoE valid paramter value all is fine. If I enter something invalid I get:t  A %CLI-W-IVKEYW, unrecognized keyword - check validity and spelling"  \HUGO\r/ %TRACE-W-TRACEBACK, symbolic stack dump followsaJ   image    module    routine             line      rel PC           abs PCO                                             0 FFFFFFFF8006F0C0 FFFFFFFF8006F0C0nO                                             0 FFFFFFFF8006F0C0 FFFFFFFF8006F0C0 O                                             0 FFFFFFFF8006F0C0 FFFFFFFF8006F0C0 O  MIST                                       0 00000000000106B4 00000000000206B4 O  MIST  MIST  P_GET_COMMAND                 27 0000000000000120 0000000000020120lO  MIST  MIST  MIST                          39 00000000000001F8 00000000000201F8bO                                             0 FFFFFFFF855ED178 FFFFFFFF855ED178r
 RC=    229472"    O So after the whole "stack dump" control returns to the program which in turn is5N able to write out the status code of dcl$parse. My question: is there a way toM omit this "stack dump"? I mean, the status code is sufficient and the programh' is able to take the appropriate action.B   Regards,    Christoph Gartmanng  H -- --------------------------------------------------------------------+H | Max-Planck-Institut fuer      Phone   : +49-761-5108-464   Fax: -452 |H | Immunbiologie                                                        |H | Postfach 1169                 Internet: gartmann@immunbio.mpg.de     |H | D-79011  Freiburg, FRG                                               |H +--------- http://www.immunbio.mpg.de/home/english/menue.html ---------+   ------------------------------  # Date: Tue, 23 Oct 2001 21:00:27 GMT32 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)5 Subject: Re: CLD & error handling from within programe1 Message-ID: <LTkB7.852$RL6.9731@news.cpqcorp.net>g  f In article <9r4fbu$7ir$1@n.ruf.uni-freiburg.de>, gartmann@immunbio.mpg.de (Christoph Gartmann) writes:  F :I would like to use a CLD from within a Pascal program....If I enter  :something invalid I get:r : B :%CLI-W-IVKEYW, unrecognized keyword - check validity and spelling : \HUGO\0 :%TRACE-W-TRACEBACK, symbolic stack dump follows ..  I   You need to create a signal handler, as the CLI routines tend to signalW<   errors.  At its simplest, you can use something like this:  !     lib$establish(lib$sig_to_ret)b  E   Most any OpenVMS application source code module that calls the CLI 0/   routines will include a handler of some sort.R  F   Pascal has its own ESTABLISH mechanism, used to establish a handler.D   You'll need to check the Pascal documentation to determine exactlyE   what you need to do here, assuming one of the resident Pascal gurus C   does not deign to contribute the incantation.  Also check through D   the PASCAL$EXAMPLES: directory contents, particularly HANDLER.PAS.  N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Tue, 23 Oct 2001 22:56:35 -0400i- From: JF Mezei <jfmezei.spamnot@videotron.ca>D" Subject: Compaq financial humour !, Message-ID: <3BD62DD1.C6D73BE4@videotron.ca>  " Time for the 3rd quarter comedy...     from:u: http://www.compaq.com/newsroom/presspaq/102301/Remarks.pdf   Some funny ones:   ##Page We had severalL key wins during the quarter, including a 3-year, $50 million dollar contract with BT1J Ignite in the U.K. The company will deploy 50,000 Compaq ProLiant servers4 to power its Web hosting services throughout Europe. ##  K What fun it will be to manage 50,000 wintel boxes. (especially with that ne  Microsoft licensing scheme).    + And another one with the word "commitment":S   ##L We also reinforced our commitment to the Alpha road map that we outlined forK our customers in June. Last week, for example, we introduced a powerful newb0 mid-range server  the Compaq AlphaServer ES45. ##    L Interesting use of "mid-range". Perhaps they want to leave the "high end" to IA64 ?    N Of course, during the audio presentation (available from Compaq's web site at:9 http://www.compaq.com/newsroom/presspaq/102301/index.htmli  H VMS is not mentioned, but Nonstop and Windows and Unix are mentioned. No surprise there.9   ------------------------------  % Date: Tue, 23 Oct 2001 23:15:40 -0400B- From: JF Mezei <jfmezei.spamnot@videotron.ca>j& Subject: Re: Compaq financial humour !, Message-ID: <3BD63248.DB36D927@videotron.ca>   Some more tidbits:   Revenu:hN Enterprise Group: 2.4 billion   (The segment reported a loss of $104 million.)* 	Industry standard server: 			 1.4 billion5 	Business Critical Solutions Group was 0.590 billion O  S/ Enterprise Storage Group: $412 million dollars,I    L So for the enterprise servers, it seems that wintel has the biggest share of8 revenus, with VMS/UNIX/TANDEM sharing a 590 million pie.   ------------------------------  % Date: Wed, 24 Oct 2001 07:14:36 +0200s& From: John McLean <mcleanj@dplanet.ch>& Subject: Re: Compaq financial humour !* Message-ID: <3BD64E3C.B526423F@dplanet.ch>   JF Mezei wrote:r >  > Some more tidbits: > 	 > Revenu:-P > Enterprise Group: 2.4 billion   (The segment reported a loss of $104 million.)F >         Industry standard server:                        1.4 billion= >         Business Critical Solutions Group was 0.590 billion  > 1 > Enterprise Storage Group: $412 million dollars,G > N > So for the enterprise servers, it seems that wintel has the biggest share of: > revenus, with VMS/UNIX/TANDEM sharing a 590 million pie.    G My first take is that they  seem to be blaming market conditions rather H than any confusion and uncertainty about Alpha-to-Intel and Compaq-to-HP plans.  E One thing I will do sometime soon is take a look at sales compared to E actual income.  Compaq has a great record of saying sales in PC's are-G much higher than any other product but forgetting that profit/income is D peanuts.  It takes the profit of a lot of PC sales to equal one VMS, Unix or Tandem box.:     John McLeani   ------------------------------  + Date: Tue, 23 Oct 2001 14:21:25 -0400 (EDT)e0 From: "Katherine M. Pohl" <POHLKM@mail.suny.edu>/ Subject: Compaq OpenVMS Network Monitoring Tool . Message-ID: <01K9UDJR9IW0004N0L@mail.suny.edu>  J Does Compaq have a network monitoring tool (besides ECP data collector and PAWZ) available for OpenVMS? Thanks,o Kathye   ------------------------------  % Date: Tue, 23 Oct 2001 20:41:01 +0200s. From: "Jesper Naur" <jesper.naur@post.tele.dk>3 Subject: Re: Compaq OpenVMS Network Monitoring Tooln= Message-ID: <3bd5b803$0$25384$edfadb0f@dspool01.news.tele.dk>h  9 Katherine M. Pohl <POHLKM@mail.suny.edu> wrote in messageo( news:01K9UDJR9IW0004N0L@mail.suny.edu...L > Does Compaq have a network monitoring tool (besides ECP data collector and > PAWZ) available for OpenVMS?	 > Thanks,t > Kathy   E On the Freeware V4 CD, there is a program EMON, which is not too bad.w       Best regards     Jesper Naur    ------------------------------  % Date: Tue, 23 Oct 2001 20:53:50 +0200F" From: "Hans Vlems" <hvlems@iae.nl>3 Subject: Re: Compaq OpenVMS Network Monitoring ToolM( Message-ID: <9r4e7i$5fn$1@news.IAEhv.nl>  A Well, in VMS 4.7 there was a patch available for MONITOR.EXE thatL* allowed the command "MONITOR ETHERNET"....   Hans  9 Katherine M. Pohl <POHLKM@mail.suny.edu> wrote in message ( news:01K9UDJR9IW0004N0L@mail.suny.edu...L > Does Compaq have a network monitoring tool (besides ECP data collector and > PAWZ) available for OpenVMS?	 > Thanks,t > Kathyv   ------------------------------  % Date: Tue, 23 Oct 2001 21:48:14 -0400k( From: "Kenneth Randell" <jetr@erols.com>3 Subject: Re: Compaq OpenVMS Network Monitoring Toolh+ Message-ID: <9r56lg$49s$1@bob.news.rcn.net>A  . Depends on how and what you want to monitor...  H If you just want ethernet traffic generated on your system, it's not tooL hard (documented someplace, my old brain just doesn't remember) via calls to the driver to get statsC  E You can get line counters from UCX or DECNET via appropriate commandsu  I If you really want to look at all traffic, the freeware package mentionedhK works okay, but in my experience needs a lot of horsepower on a busy net to  keep up.   Ken Randellt  9 Katherine M. Pohl <POHLKM@mail.suny.edu> wrote in messageh( news:01K9UDJR9IW0004N0L@mail.suny.edu...L > Does Compaq have a network monitoring tool (besides ECP data collector and > PAWZ) available for OpenVMS?	 > Thanks,A > Kathyg   ------------------------------    Date: 23 Oct 2001 13:39:27 -0500+ From: young_r@encompasserve.org (Rob Young)s- Subject: Re: Compaq: VMS is alive and kickingw3 Message-ID: <GBFfZBIs0aJT@eisner.encompasserve.org>>  S In article <3BD5A8A1.2E10CFFD@dplanet.ch>, John McLean <mcleanj@dplanet.ch> writes:s >  >> vM >> The only "writing on the wall" right now is being scribbled in crayon by a  >> few people in this group. >> e: >> You guys take reading chicken entrails to a new height. >  > E > Not so.  Take Gartner Report "HP/Compaq Merger: Hard Choices on thed1 > Server Side" by George Weiss, dated 6 Sep 2001.  > B > It concludes "Enterprises should carefully assess new-generationJ > systems, such as blades, for upgrade and support continuity, and migrateG > OpenVMS and other legacy software without awaiting the outcome of thed > acquisition."  >   C 	But have you read that out loud?  How much sense can that possiblyaG 	make?  If the merger is final year-end, and that is dated Sept 6 2001,sF 	how do you "migrate without awaiting the outcome of the acquisition"? 	oA 	Isn't that just a bit silly?  Most of us wait months for such a >D 	project to be approved let alone get the go ahead.  George Weiss isE 	a funny guy.  Too many shutdown reboot cycles on his PC I would say.>   >  > and M > http://techupdate.zdnet.com/techupdate/stories/main/0,14179,2817135,00.html=G > on October 10 from the same writer as "VMS is alive and kicking" (ie.3 > David Berlind) ..D > J > 'For example, Compaq has customers running Tru64 Unix and OpenVMS on theC > Alpha architecture and, now that Alpha has been discontinued, theyC > company's plan was to migrate them to Tru64 or Windows running onc > Itanium.'S >  	L 	Joker Joker Joker.9  @ 	He is speaking in past tense:  "company's plan was to migrate."@ 	It is a present tense reality.  "They are currently migrating."? 	When or how did that become past tense?  Anyone have a link to=( 	OpenVMS no longer being ported to IA64?   > and later ...= > J > 'According to Gartner's McGuckin, "All roads lead to HP-UX or Windows XPG > on Itanium." In other words, existing Tru64 and OpenVMS customers areLE > now looking at HP-UX (instead of Tru64) or Windows XP as their onlyS > options.'6 >   ? 	Yawn.  Tell that to the NSK guys too, guess that is their onlyFC 	option also.  Migrate them to Windows XP too.  Who are these guys?=? 	Who among us at a corporate level (anyone?) has this going on:-  D "existing OpenVMS customers are now looking at HP-UX [as an option]"  < 	Everyone knows the VMS migration path is to Sun Solaris or  	Windows XP/Windows 98.1   				Rob    ------------------------------    Date: 24 Oct 2001 05:04:11 +0800, From: Paul Repacholi <prep@prep.synonet.com>- Subject: Re: Compaq: VMS is alive and kickinguM Message-ID: <873d4af4qc.fsf@k9.i-did-not-set--mail-host-address--so-shoot-me>A  6 "Terry C. Shannon" <terryshannon@mediaone.net> writes:  E > If the IPF port is successful (and there is no technical reason whyiB > it won't be so) VMS should enjoy a larger addressable market. OfA > course, the financial news that's coming out tomorrow after the D > market closes isn't gonna be too auspicious for VMS... or anything > else in the HPSD and NSD.m  > Why so? The itanic is an industry joke, and at the best people; are in 'wait and see'. The Alpha on the other hand had huge-	 respect.       -- e< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.D@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------  % Date: Tue, 23 Oct 2001 18:51:50 -0400   From: John Santos <JOHN@egh.com>- Subject: Re: Compaq: VMS is alive and kickinge5 Message-ID: <1011023185049.1681F-100000@Ives.egh.com>r  % On Tue, 23 Oct 2001, Bill Todd wrote:    > 1 > john nixon <jnixon@cfl.rr.com> wrote in messagej: > news:sIWA7.392977$aZ.78559839@typhoon.tampabay.rr.com...N > > As ususal, you are much more eloquent, informed and well researched than I > > am.  > >  > > However, you are wrong.  > I > That's always possible, though on the basis of past history improbable.a > I'll try to explain below.   [...].  = "We had to destroy the operating system in order to save it."I  I > So I understand why you find my attitude painful, but suggest that it'sb2 > likely better grounded in reality than your own. >  > - bill   --   John Santos  Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  # Date: Tue, 23 Oct 2001 23:28:41 GMTg* From: "Bill Todd" <billtodd@metrocast.net>- Subject: Re: Compaq: VMS is alive and kicking ? Message-ID: <J2nB7.581985$Lw3.35645044@news2.aus1.giganews.com>o  + John Santos <JOHN@egh.com> wrote in messagey/ news:1011023185049.1681F-100000@Ives.egh.com...e' > On Tue, 23 Oct 2001, Bill Todd wrote:, >s > >t3 > > john nixon <jnixon@cfl.rr.com> wrote in messaget< > > news:sIWA7.392977$aZ.78559839@typhoon.tampabay.rr.com...I > > > As ususal, you are much more eloquent, informed and well researched  than I	 > > > am.  > > >I > > > However, you are wrong.r > > K > > That's always possible, though on the basis of past history improbable.M > > I'll try to explain below. >o > [...]f > ? > "We had to destroy the operating system in order to save it."h  G No:  we just need to destroy its current (negligent, or worse) owner too allow it to survive.   - bill   ------------------------------  % Date: Tue, 23 Oct 2001 14:13:22 -0400 - From: "Peter Weaver" <peter.weaver@stelco.ca> = Subject: Re: Converting an ODS-2 to an ODS-5 file system disks2 Message-ID: <mriB7.45466$Z2.687095@nnrp1.uunet.ca>  @ "Fred Kleinsorge" <kleinsorge@star.zko.dec.com> wrote in message+ news:kciB7.827$RL6.9577@news.cpqcorp.net... D > The simple truth is that most VAX customers are running the oldest possibleJ > version that they can safely get away with.  Lots of V5.1, with the restL > mostly dragged forward by cluster version compatability issues with Alpha. >...  > Where did that "simple truth" come from? Can you post numbers?  K Most VAX customers I know are at V7.x. If I broke it done by machine rathertF than customers, then I only know one VAX that is at V6.x, that is in a" company that only has the one VAX.  @ I have never seen a VAX that was upgraded because the Alpha was.   ------------------------------  % Date: Tue, 23 Oct 2001 14:53:53 -0400 5 From: "Fred Kleinsorge" <kleinsorge@star.zko.dec.com> = Subject: Re: Converting an ODS-2 to an ODS-5 file system disk-1 Message-ID: <72jB7.837$RL6.9674@news.cpqcorp.net>=  I No.  I don't have any recent numbers.  It is my guess, from numbers I didiF see a few years ago, that V5.1-2 (or some such ancient vintage) is theJ widest used VAX version.  The reason being that the customers were "stuck"I because of a LP.  Of course, Y2K may have wiped out a lot of them.  And I H *have* seen VAX's upgraded because new Alpha hardware required a new VMSL version, which in turn required the nodes in the cluster to be upgraded to a compatable version.m  J Customers who easily have moved to recent VMS versions, also can "usually"  move easily to Alpha - and have.      ! Peter Weaver wrote in message ... A >"Fred Kleinsorge" <kleinsorge@star.zko.dec.com> wrote in messageo, >news:kciB7.827$RL6.9577@news.cpqcorp.net...E >> The simple truth is that most VAX customers are running the oldestc	 >possiblerK >> version that they can safely get away with.  Lots of V5.1, with the restpF >> mostly dragged forward by cluster version compatability issues with Alpha. >>...s >t? >Where did that "simple truth" come from? Can you post numbers?c >aL >Most VAX customers I know are at V7.x. If I broke it done by machine ratherG >than customers, then I only know one VAX that is at V6.x, that is in ab# >company that only has the one VAX.  > A >I have never seen a VAX that was upgraded because the Alpha was.  >  >    ------------------------------    Date: 24 Oct 2001 05:21:14 +0800, From: Paul Repacholi <prep@prep.synonet.com>= Subject: Re: Converting an ODS-2 to an ODS-5 file system disk M Message-ID: <87wv1mdpdh.fsf@k9.i-did-not-set--mail-host-address--so-shoot-me>2  / Kilgallen@SpamCop.net (Larry Kilgallen) writes:M  F > One aspect of the "indirectly" is the question about what version ofD > VMS is being used.  I believe they get few Alpha customers runningC > V6.1 but many VAX customers running V5.5.  If those VAX customersu; > wanted innovation more than stability they would upgrade.t  F If those customers could get their drivers updated, they would jump atB it. It is a shocker that people whould not get up to 5.5-2 though, rembering the joys of 5.x...   --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.n@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------  % Date: Tue, 23 Oct 2001 21:34:13 -0500 1 From: "David J. Dachtera" <djesys.nospam@fsi.net>b" Subject: Re: copy files in DCLedit' Message-ID: <3BD628A5.E3A62CF0@fsi.net>-   Eran wrote:2 >  > Hi,2E > I try to copy files fron one directory to another using the DCLeditc > tool.DB > I need to do it in DOS environment and therefore I can't use the > "copyFiles" command. > Any suggestions? > Thanks  A It seems no one here understands either "DCLedit" or "copyFiles".i  G Are you sure this is VMS jargon? Can you explain further what you're upe to?s   -- g David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/p   ------------------------------   Date: 23 Oct 2001 18:48:41 GMT1 From: bill@triangle.cs.uofs.edu (Bill Gunshannon)   Subject: DECWriter III available, Message-ID: <9r4e29$151e$1@info.cs.uofs.edu>  @ Is there anyone here who is still using DECWriter III printers??C I have one, still on the palette along with a supply of spare partsn for keeping it running.d  ? Is there anyone within pick-up distance of Scranton, PA who cant@ use this??  I find myself in the need of clearing some space and3 as much as I hate to give it up, the time has come.   ? Of course, I would gladly take some QBUS trinkets in trade, butP> there are no strings attached.  I just would like to see it go to a good home.-   bill   -- aJ Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>   n   ------------------------------    Date: 23 Oct 2001 11:14:47 -07004 From: jemelter@rockwellcollins.com (James E. Melter)R Subject: Re: dynamic_cast failure in Compaq C++ version 6.3 on VMS on DEC Alpha...= Message-ID: <29cc9a0a.0110231014.6500afbc@posting.google.com>.  y jemelter@rockwellcollins.com (James E. Melter) wrote in message news:<29cc9a0a.0110221142.7ad69f53@posting.google.com>... E > Is anyone aware of any problems with using dynamic_cast<> in Compaqt > C++ v6.3?g > F > I am attempting to port a C compiler written originally in MicrosoftC > C++ 6.0 to a DEC(Now Compaq) Alpha system hosted with OpenVMS 7.1 G > using Compaq C++ v6.3 CXX compiler(whew). All C compiler source filesfE > eventually compiled and linked after minimal tweaking, but failures D > occur at runtime in code where the C++ dynamic_cast<> construct is: > used to downcast a base class pointer to a derived classG > pointer(assertions fail). I've tried using the following to determine0 > if the typecast should work(alla Stroustroup): > F > cout<<"====================================================="<<endl;: > cout<<"pParent type is "<<typeid(*pParent).name()<<endl;F > cout<<"====================================================="<<endl; > H > and the type is correct so the downcast should work, but the assertionE > still fails in this code immediately following(Note that Child is a ! > subclass of Parent, obviously):m > 4 >     Child *pChild= dynamic_cast<Child *>(pParent); >     assert (pParent!= NULL); > H > Isolating problematic code is difficult in this case because there areE > so many source files(So far 87, just to isolate these two lines). IsG > can say for sure that this code uses a lot of STL or Standard LibraryiD > containers as well as the library string class. The source code isD > basically littered with the dynamic_cast construct but I think theG > failures are all related(this is only one case). It may not always be-D > a bad thing to use dynamic_cast, but to me it seems like they over+ > used it(a somewhat lack of polymorphism).C > G > Hopefully someone out there is aware of Compaq C++ 6.3 dynamic_cast<>z? > limitations? Or maybe there is a workaround for this? Compaq?e > ' > Thanks in advance for any assistance.  "James E. Melter" wrote: > F > cout<<"====================================================="<<endl;: > cout<<"pParent type is "<<typeid(*pParent).name()<<endl;F > cout<<"====================================================="<<endl; >rH > and the type is correct so the downcast should work, but the assertionE > still fails in this code immediately following(Note that Child is aa! > subclass of Parent, obviously):o >t4 >     Child *pChild= dynamic_cast<Child *>(pParent); >     assert (pParent!= NULL);   assert (pChild != NULL);  ?????e  ; If your assert was firing, then pChild would have been 0 as 9 well.  And I believe it's perfectly fine to invoke typeidh< on what looks like a dereferenced null pointer (someone have? chapter/verse?).  And on the pedantic side, zero is the defineda non-object:n   assert (0 != pChild);o   or   assert (pChild);   --M Monty Brandenberg, Software Consultant                              MCB, Inc.M   ------------------------------    Date: 23 Oct 2001 11:16:28 -07004 From: jemelter@rockwellcollins.com (James E. Melter)R Subject: Re: dynamic_cast failure in Compaq C++ version 6.3 on VMS on DEC Alpha...< Message-ID: <29cc9a0a.0110231016.2e1de4c@posting.google.com>  y jemelter@rockwellcollins.com (James E. Melter) wrote in message news:<29cc9a0a.0110221142.7ad69f53@posting.google.com>...mE > Is anyone aware of any problems with using dynamic_cast<> in Compaqa > C++ v6.3?. > F > I am attempting to port a C compiler written originally in MicrosoftC > C++ 6.0 to a DEC(Now Compaq) Alpha system hosted with OpenVMS 7.1oG > using Compaq C++ v6.3 CXX compiler(whew). All C compiler source files E > eventually compiled and linked after minimal tweaking, but failuresgD > occur at runtime in code where the C++ dynamic_cast<> construct is: > used to downcast a base class pointer to a derived classG > pointer(assertions fail). I've tried using the following to determine 0 > if the typecast should work(alla Stroustroup): > F > cout<<"====================================================="<<endl;: > cout<<"pParent type is "<<typeid(*pParent).name()<<endl;F > cout<<"====================================================="<<endl; > H > and the type is correct so the downcast should work, but the assertionE > still fails in this code immediately following(Note that Child is aM! > subclass of Parent, obviously):- > 4 >     Child *pChild= dynamic_cast<Child *>(pParent); >     assert (pParent!= NULL); > H > Isolating problematic code is difficult in this case because there areE > so many source files(So far 87, just to isolate these two lines). IaG > can say for sure that this code uses a lot of STL or Standard LibraryyD > containers as well as the library string class. The source code isD > basically littered with the dynamic_cast construct but I think theG > failures are all related(this is only one case). It may not always be D > a bad thing to use dynamic_cast, but to me it seems like they over+ > used it(a somewhat lack of polymorphism).p > G > Hopefully someone out there is aware of Compaq C++ 6.3 dynamic_cast<>@? > limitations? Or maybe there is a workaround for this? Compaq?n > ' > Thanks in advance for any assistance.r  # Oops, the snippit should have read:d  D cout<<"====================================================="<<endl;8 cout<<"pParent type is "<<typeid(*pParent).name()<<endl;D cout<<"====================================================="<<endl;. Child *pChild= dynamic_cast<Child *>(pParent); assert (pChild!= NULL);   F I apologize. Thanks for spotting the typo. Affirmative on the, "And on& the pedantic side, zero is the definedA non-object"; I'm porting a compiler; I didn't write it. When thisfF section of code executes, of course I verified that pParent was valid.D Otherwise, I wouldn't have been able to do this prior to the failure7 on dynamic_cast<>(debug session of "problematic" code):i    ! DBG> examine *pParentEnvironment d  ? *FunctionDefinition::FunctionDefinition(DeclarationSpecifier *,sD Declarator *, Environment *, AAMPCError &, int, const std::string &)( ::pParentEnvironment: class Environment ;     m_typedefTable: class map<std::string, QualifiedType *,oC std::less<std::string>, std::allocator<std::pair<const std::string,t Qual ifiedType *>>> -E         _RWt: class _RWrb_tree<std::map<std::string, QualifiedType *,t> std::less<std::string>, std::allocator<std::pair<const std::st9 ring, QualifiedType *>>>::key_type, std::map<std::string,eA QualifiedType *, std::less<std::string>, std::allocator<std::pairy         <const std::string,  l#             _RWbuffer_size:     36 n!             _RWbuffer_list: classeD _RWrw_basis<_RWrwstd::_RWrb_tree<std::map<std::string, QualifiedType *, std::less<std::string>, st 7 d::allocator<std::pair<const std::string, QualifiedTypepC *>>>::key_type, std::map<std::string, QualifiedType *, std::less<sth/             d::string>, std::allocator<std::pa n>                 inherit allocator<std::pair<const std::string,3 QualifiedType *>>  (has no non-static data members)r(                 _RWdata_:       9141840 "             _RWfree_list:       0 )             _RWnext_avail:      10802604 c!             _RWlast:    10802604 d!             _RWheader:  10802576 h"             _RWnode_count:      0 "             _RWinsert_always:   0 =             _RWkey_compare: struct less<std::string>  (has noo non-static data members)A                 inherit binary_function<std::string, std::string,L' bool>  (has no non-static data members)47     m_structTable: class map<std::string, TypeStruct *,.C std::less<std::string>, std::allocator<std::pair<const std::string,l TypeStru ct *>>> B         _RWt: class _RWrb_tree<std::map<std::string, TypeStruct *,A std::less<std::string>, std::allocator<std::pair<const std::strin A g, TypeStruct *>>>::key_type, std::map<std::string, TypeStruct *, 9 std::less<std::string>, std::allocator<std::pair<const st8         d::string, TypeStruc -#             _RWbuffer_size:     36  !             _RWbuffer_list: classiD _RWrw_basis<_RWrwstd::_RWrb_tree<std::map<std::string, TypeStruct *, std::less<std::string>, std::@A allocator<std::pair<const std::string, TypeStruct *>>>::key_type,n9 std::map<std::string, TypeStruct *, std::less<std::stringr/             >, std::allocator<std::pair<const   >                 inherit allocator<std::pair<const std::string,0 TypeStruct *>>  (has no non-static data members))                 _RWdata_:       10754032  "             _RWfree_list:       0 )             _RWnext_avail:      10802676 D!             _RWlast:    10802676 s!             _RWheader:  10802648 r"             _RWnode_count:      0 "             _RWinsert_always:   0 =             _RWkey_compare: struct less<std::string>  (has non non-static data members)A                 inherit binary_function<std::string, std::string, ' bool>  (has no non-static data members),5     m_unionTable: class map<std::string, TypeUnion *,rC std::less<std::string>, std::allocator<std::pair<const std::string,-	 TypeUnion- *>>> -A         _RWt: class _RWrb_tree<std::map<std::string, TypeUnion *,HB std::less<std::string>, std::allocator<std::pair<const std::string> , TypeUnion *>>>::key_type, std::map<std::string, TypeUnion *,< std::less<std::string>, std::allocator<std::pair<const std::         string, TypeUnion *> W#             _RWbuffer_size:     36 y!             _RWbuffer_list: classmC _RWrw_basis<_RWrwstd::_RWrb_tree<std::map<std::string, TypeUnion *,  std::less<std::string>, std::a? llocator<std::pair<const std::string, TypeUnion *>>>::key_type, : std::map<std::string, TypeUnion *, std::less<std::string>,/             std::allocator<std::pair<const std a>                 inherit allocator<std::pair<const std::string,/ TypeUnion *>>  (has no non-static data members)i)                 _RWdata_:       10803608 -"             _RWfree_list:       0 )             _RWnext_avail:      10803660 -!             _RWlast:    10803660 ,!             _RWheader:  10803632 B"             _RWnode_count:      0 "             _RWinsert_always:   0 =             _RWkey_compare: struct less<std::string>  (has noi non-static data members)A                 inherit binary_function<std::string, std::string,@' bool>  (has no non-static data members)B3     m_enumTable: class map<std::string, TypeEnum *,lC std::less<std::string>, std::allocator<std::pair<const std::string,. TypeEnum *>> > @         _RWt: class _RWrb_tree<std::map<std::string, TypeEnum *,C std::less<std::string>, std::allocator<std::pair<const std::string,r;  TypeEnum *>>>::key_type, std::map<std::string, TypeEnum *,s? std::less<std::string>, std::allocator<std::pair<const std::str.         ing, TypeEnum *>>>:: e#             _RWbuffer_size:     36 .!             _RWbuffer_list: classiB _RWrw_basis<_RWrwstd::_RWrb_tree<std::map<std::string, TypeEnum *, std::less<std::string>, std::al-= locator<std::pair<const std::string, TypeEnum *>>>::key_type,W= std::map<std::string, TypeEnum *, std::less<std::string>, stdS/             ::allocator<std::pair<const std::s i>                 inherit allocator<std::pair<const std::string,. TypeEnum *>>  (has no non-static data members))                 _RWdata_:       10803672  "             _RWfree_list:       0 )             _RWnext_avail:      10803724 s!             _RWlast:    10803724 i!             _RWheader:  10803696  "             _RWnode_count:      0 "             _RWinsert_always:   0 =             _RWkey_compare: struct less<std::string>  (has nos non-static data members)A                 inherit binary_function<std::string, std::string,h' bool>  (has no non-static data members)a;     m_enumConstantTable: class map<std::string, TypeEnum *,.C std::less<std::string>, std::allocator<std::pair<const std::string,  TypeE-
 Enum *>>> @         _RWt: class _RWrb_tree<std::map<std::string, TypeEnum *,C std::less<std::string>, std::allocator<std::pair<const std::string, ;  TypeEnum *>>>::key_type, std::map<std::string, TypeEnum *,7? std::less<std::string>, std::allocator<std::pair<const std::stre         ing, TypeEnum *>>>:: r#             _RWbuffer_size:     36 5!             _RWbuffer_list: class B _RWrw_basis<_RWrwstd::_RWrb_tree<std::map<std::string, TypeEnum *,  std::less<std::string>, std::all= locator<std::pair<const std::string, TypeEnum *>>>::key_type,*= std::map<std::string, TypeEnum *, std::less<std::string>, stdV/             ::allocator<std::pair<const std::s t>                 inherit allocator<std::pair<const std::string,. TypeEnum *>>  (has no non-static data members))                 _RWdata_:       10803736 a"             _RWfree_list:       0 )             _RWnext_avail:      10803788 r!             _RWlast:    10803788 g!             _RWheader:  10803760 p"             _RWnode_count:      0 "             _RWinsert_always:   0 =             _RWkey_compare: struct less<std::string>  (has now non-static data members)A                 inherit binary_function<std::string, std::string,i' bool>  (has no non-static data members)e.     m_varFuncDeclTable: class map<std::string,6 VariableFunctionDeclaration *, std::less<std::string>, std::allocator<std::pair<const/  std::string, VariableFunctionDeclaration *>>>  4         _RWt: class _RWrb_tree<std::map<std::string,6 VariableFunctionDeclaration *, std::less<std::string>, std::allocator<std::pair<s? <const std::string, VariableFunctionDeclaration *>>>::key_type, ; std::map<std::string, VariableFunctionDeclaration *, std::l          ess<std::string>, st 2#             _RWbuffer_size:     36 g!             _RWbuffer_list: classs6 _RWrw_basis<_RWrwstd::_RWrb_tree<std::map<std::string,, VariableFunctionDeclaration *, std::less<std7 d::string>, std::allocator<std::pair<const std::string, C VariableFunctionDeclaration *>>>::key_type, std::map<std::string, Vi/             ariableFunctionDeclaration *, std: I>                 inherit allocator<std::pair<const std::string,A VariableFunctionDeclaration *>>  (has no non-static data members)u)                 _RWdata_:       10803800 c"             _RWfree_list:       0 )             _RWnext_avail:      10803852 .!             _RWlast:    10803852  !             _RWheader:  10803824  "             _RWnode_count:      0 "             _RWinsert_always:   0 =             _RWkey_compare: struct less<std::string>  (has no  non-static data members)A                 inherit binary_function<std::string, std::string,w' bool>  (has no non-static data members)-     __vptr:     1396536  DBG>      Thanks for your interest though.   ------------------------------  % Date: Tue, 23 Oct 2001 14:05:39 -0400D5 From: "Fred Kleinsorge" <kleinsorge@star.zko.dec.com>i Subject: Re: ECC1 Message-ID: <VkiB7.829$RL6.9604@news.cpqcorp.net>e  F Not all VAXes.  And it's a bit more complicated of a guess to know for+ "sure" what a page might be being used for.s  K Address errors on the system bus, or bus switch are usually at least parityiJ protected, and usually fatal.  Although on some of the stuff there is ECC.    D Paul Repacholi wrote in message <87itd7gybq.fsf@prep.synonet.com>...8 >"Fred Kleinsorge" <kleinsorge@star.zko.dec.com> writes: >wE >> Generally systems VMS runs on have ECC with single bit correction,OG >> and multi-bit detection.  Most systems will crash on a "hard" double F >> bit error.  We do have memory scrubbing logic.  I don't remember ifE >> the 8600 had the code in it to attempt to fail a process, or if its >> was just the 9000.n >e@ >VaxVMS would examine the page tables and: reload the page if it< >was RO, Kill the process if it was process private, or else >the system. >hD >The 8600 had some tricks to provide 'parity protection' for address7 >errors as well. Don't know id the 9Ks did that at all.I >u >--a= >Paul Repacholi                               1 Crescent Rd.,s8 >+61 (08) 9257-1001                           Kalamunda.A >                                             West Australia 6076k/ >Raw, Cooked or Well-done, it's all half baked. G >EPIC, The Architecture of the future, always has been, always will be.|   ------------------------------  % Date: Tue, 23 Oct 2001 19:01:33 -0400-) From: "Neil Rieck" <n.rieck@sympatico.ca>2 Subject: Re: ECC9 Message-ID: <qFmB7.8546$NP.1133355@news20.bellglobal.com>j   >RI > I believe so. IIRC the difference was that the later memory modules hade the ECC K > on the module itself. The 4 + 1 business always seemed a kludge, althoughs therea2 > was no doubt a good reason to do it at the time. >4J IIRC, in the old days you required 39 bits of memory to support 32 bits ofL data (right now I'm thinking of the memory modules used on the PDP-11/44 andI the phrase "SYNDROME BITS" keeps popping up). I believe that modern SIMMsAH only come in 8 or 9 bit varieties. Does anyone know how ECC memory works with VAX or Alpha?  
 Neil Rieck Kitchener/Waterloo/Cambridge,i Ontario, Canada.! http://www3.sympatico.ca/n.rieck/t   ------------------------------  # Date: Wed, 24 Oct 2001 00:19:32 GMTn2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) Subject: Re: ECC1 Message-ID: <oOnB7.857$RL6.9660@news.cpqcorp.net>   e In article <qFmB7.8546$NP.1133355@news20.bellglobal.com>, "Neil Rieck" <n.rieck@sympatico.ca> writes:=  K :IIRC, in the old days you required 39 bits of memory to support 32 bits of M :data (right now I'm thinking of the memory modules used on the PDP-11/44 and J :the phrase "SYNDROME BITS" keeps popping up). I believe that modern SIMMs$ :only come in 8 or 9 bit varieties.   2   Also known as 32 and 36 bit SIMMs, respectively.  9 :Does anyone know how ECC memory works with VAX or Alpha?t     It depends on the box.  %   Some systems use parity protection.i  "   Some systems use ECC protection.  G   It would not surprise me to learn that there are systems around with s   no ECC and no parity.   E   With some systems, there is a fifth SIMM in each memory bank.  This 4   provides the necessary bits for ECC.  (See below.)  G   With others, the use of 36-bit SIMMs means you have eight extra bits eI   per quadword, which is enough for ECC.  (See below.)  The 36-bit SIMMs oB   also allow for byte parity, for those systems that implement it.  1   With yet others, there are custom 39-bit SIMMs.n  H   With n check bits, you can ECC-protect 2^(n-1) bits, this includes theI   check bits and the data bits.  Eight check bits will ECC-protect up to nB   72 bits.  64 data bits plus 8 check bits covers 72 total bits.    I   While parity can slow performance ("Parity is for farmers" is a famous <G   Cray quote), the more memory you have, the more you will tend to see =G   spurious bit-flips from alpha particle hits.  (These alpha particles sH   -- helium nuclei -- can originate within the plastic chip carriers or J   within the metal layers used for the chips, as well as from cosmic rays.L   Folks that provide semiconductors and related products go to some lengths I   to reduce the likelyhood that materials will generate alpha particles.)C  K   Parity and ECC also have obvious hardware and design costs, and they can tJ   potentially also increase the frequency of crashes.  But without parity H   and/or ECC, you can see problems resulting from particle hits.  One ofK   the more "surprising" costs can result from a common perception that any SF   memory error logged means the memory is faulty -- this is one of theK   reasons why OpenVMS has heuristics on its soft-error logging.  TANSTAAFL.w  N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------    Date: 24 Oct 2001 10:02:00 +0800, From: Paul Repacholi <prep@prep.synonet.com> Subject: Re: ECC- Message-ID: <87zo6hn6cn.fsf@prep.synonet.com>p  4 hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) writes:  3 >   With yet others, there are custom 39-bit SIMMs.   D Or for the faint of heart, 40 bits. 39 for anger, plus a spare! Plus' it fits 10 4 bit chips much better. ;) n  = Down side for all of them, is that is a *chip* dies, or there 6 is a common error, neither SEC nor DED is of much use.   -- g< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.=@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------  # Date: Wed, 24 Oct 2001 02:45:08 GMT * From: "Bill Todd" <billtodd@metrocast.net> Subject: Re: ECC? Message-ID: <TWpB7.582803$Lw3.35746526@news2.aus1.giganews.com>c  7 Paul Repacholi <prep@prep.synonet.com> wrote in message ' news:87zo6hn6cn.fsf@prep.synonet.com... 6 > hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) writes: >a5 > >   With yet others, there are custom 39-bit SIMMs.o >uF > Or for the faint of heart, 40 bits. 39 for anger, plus a spare! Plus( > it fits 10 4 bit chips much better. ;) >e? > Down side for all of them, is that is a *chip* dies, or theret8 > is a common error, neither SEC nor DED is of much use.  @ Isn't that what IBM's 'chipkill' approach is designed to handle?   - bill   ------------------------------  # Date: Tue, 23 Oct 2001 20:32:47 GMT * From: Ben Armstrong <ben@bgpc.dymaxion.ca>; Subject: Finding GNU "find" that builds from source for VMSa1 Message-ID: <slrn9tbkve.52i.ben@bgpc.dymaxion.ca>a  B I came across a great little project, gnv.sourceforge.net, but theA utilities bundled with their distribution are binary only (oh the H horrors!) Anyway, as I need to still support venerable old VAXen, I haveC a pressing need for a source kit for GNU find that compiles both ond  VMS/Alpha and VMS/VAX platforms.  # Some GNU find for VMS/Alpha trivia:T  F The binary for FIND.EXE distributing with GNV's tarball reports itself thusly:s   	$ find -version 	GNU find version 4.1m  B To add to the confusion, there is a FIND.EXE from Hunter Goatley'sG freeware collection, but that is a completely different animal, and notb at all what I need.o  G I have looked at the tarball from the GNU project for find, and despite G a passing reference to VMS in one of the comments in the code, it comestF with no support for building it on VMS.  What is worse, typical of GNUF packages, it depends on autotools to build it, and GNV doesn't provideE autotools.  GNV only goes so far as providing make, a compiler, bash,tH and a bunch of support utilities.  So this means a "hand-rolled for VMS"B Makefile needs to be devised, much as GNV has done for bash.  DoesE anyone know of the whereabouts of such a beast?  Surely this FIND.EXE:G that GNV is distributing didn't just descend to earth from the heavens!T   Earnestly pursuing GNU,g
 Ben Armstrongo -- :G       Ben Armstrong                -.       Medianet Development Group,6E       BArmstrong@dymaxion.ca         `-.    Dymaxion Research LimitedeH       <URL: http://www.dymaxion.ca/>    `-  Halifax, Nova Scotia, Canada   ------------------------------  % Date: Tue, 23 Oct 2001 19:46:36 -0500mC From: "Craig A. Berry" <craig.berry@nospam.SignalTreeSolutions.com>>? Subject: Re: Finding GNU "find" that builds from source for VMS:I Message-ID: <craig.berry-A4EA0B.19463523102001@newsrump.sjc.telocity.net>s  1 In article <slrn9tbkve.52i.ben@bgpc.dymaxion.ca>, ,  Ben Armstrong <ben@bgpc.dymaxion.ca> wrote:  & >So this means a "hand-rolled for VMS"D > Makefile needs to be devised, much as GNV has done for bash.  DoesG > anyone know of the whereabouts of such a beast?  Surely this FIND.EXEkI > that GNV is distributing didn't just descend to earth from the heavens!   ! Well, there's a Perl script here:<  < <http://w4.lns.cornell.edu/~pvhp/perl/vms/devel/make2mms.pl>  F that will take the Makefile and give you a rough cut of a descrip.mms C that you can use with MMS or MMK.  It's still a royal pain. Martin  2 Vorlaender has further described the process here:  G <http://www.pdv-systeme.de/users/martinv/VMS_Programming_FAQ.html#4.1.>c  6 And you will probably have to also cook up a config.h.   ------------------------------  % Date: Tue, 23 Oct 2001 18:04:25 -0000r- From: wspencer@ap.nospam.org (Warren Spencer) 2 Subject: Re: Fwd: Compaq: VMS is alive and kicking7 Message-ID: <914387B18warrenspencer1977@207.126.101.97>a  + kenrbnsn@rbnsn.com (Ken Robinson) wrote in r< <5.1.0.14.2.20011022050653.0432eaf0@mail.rbnsn.com> in part:  + >>http://cgi.zdnet.com/slink?154076:1596553t     How about this quote:n  D "But, as Compaq's OpenVMS vice president Mark Gorham explained, the E company's commitment to the operating system has never been stronger"o  & So this is starship OpenVMS at warp 9?   ws   --     Warren Spencer' Senior Software Engineer (not a writer)  The Associated Press  L ** My employer does not necessarily agree with my statements - neither do I  **   ------------------------------  % Date: Tue, 23 Oct 2001 14:14:10 -0400  From: William_Bochnik@acml.com2 Subject: Re: Fwd: Compaq: VMS is alive and kicking> Message-ID: <OF991AB00A.79086E78-ON85256AEE.00641A6D@acml.com>  ? um, 1% of your resources now, 1% of your resources since buyings Digital.....   semantics?n        a                                                                                                  ta                     wspencer@ap.n                                                                :a                     ospam.org                    To:  Info-VAX@Mvb.Saic.Com                      ta                                                  cc:                                             fa                     10/23/2001           Subject:     Re: Fwd: Compaq: VMS is alive and kicking  ta                     02:04 PM                                                                     ea                     Please                                                                       :a                     respond to                                                                   ya                     wspencer                                                                      a                                                                                                  0a                                                                                                  r      * kenrbnsn@rbnsn.com (Ken Robinson) wrote in< <5.1.0.14.2.20011022050653.0432eaf0@mail.rbnsn.com> in part:  + >>http://cgi.zdnet.com/slink?154076:1596553s     How about this quote:o  ? "But, as Compaq's OpenVMS vice president Mark Gorham explained,  then; company's commitment to the operating system has never beent	 stronger"g  & So this is starship OpenVMS at warp 9?   ws   --   Warren Spencer' Senior Software Engineer (not a writer)t The Associated Press  > ** My employer does not necessarily agree with my statements - neither do I **          F ______________________________________________________________________;  The information contained in this transmission may contain @ privileged and confidential information and is intended only forA the use of the person(s) name above.  If you are not the intendeda= recipient, or an employee or agent responsible for delivering:3 this message to the intended recipient, any review, @ dissemination, distribution or duplication of this communication? is strictly prohibited.  If you are not the intended recipient,>A please contact the sender immediately by reply e-mail and destroy # all copies of the original message.    ------------------------------  % Date: Tue, 23 Oct 2001 19:04:24 -0400 ) From: "Neil Rieck" <n.rieck@sympatico.ca>62 Subject: Re: Fwd: Compaq: VMS is alive and kicking9 Message-ID: <4ImB7.8554$NP.1134180@news20.bellglobal.com>t  : "Warren Spencer" <wspencer@ap.nospam.org> wrote in message1 news:914387B18warrenspencer1977@207.126.101.97...:, > kenrbnsn@rbnsn.com (Ken Robinson) wrote in> > <5.1.0.14.2.20011022050653.0432eaf0@mail.rbnsn.com> in part: > - > >>http://cgi.zdnet.com/slink?154076:1596553r >n >s > How about this quote:m >>E > "But, as Compaq's OpenVMS vice president Mark Gorham explained, thetG > company's commitment to the operating system has never been stronger"E > ( > So this is starship OpenVMS at warp 9? >mH Let's hope it's 9.9 (BTW, OpenVMS on Alpha really seems to be warp speed compared to VAX)  
 Neil Rieck Kitchener/Waterloo/Cambridge,6 Ontario, Canada.! http://www3.sympatico.ca/n.rieck/R   ------------------------------  # Date: Tue, 23 Oct 2001 23:30:21 GMTn* From: "Bill Todd" <billtodd@metrocast.net>2 Subject: Re: Fwd: Compaq: VMS is alive and kicking? Message-ID: <h4nB7.581993$Lw3.35646268@news2.aus1.giganews.com>a  2 Neil Rieck <n.rieck@sympatico.ca> wrote in message3 news:4ImB7.8554$NP.1134180@news20.bellglobal.com...  >s< > "Warren Spencer" <wspencer@ap.nospam.org> wrote in message3 > news:914387B18warrenspencer1977@207.126.101.97... . > > kenrbnsn@rbnsn.com (Ken Robinson) wrote in@ > > <5.1.0.14.2.20011022050653.0432eaf0@mail.rbnsn.com> in part: > > / > > >>http://cgi.zdnet.com/slink?154076:1596553l > >  > >  > > How about this quote:  > >tG > > "But, as Compaq's OpenVMS vice president Mark Gorham explained, thenI > > company's commitment to the operating system has never been stronger"  > >m* > > So this is starship OpenVMS at warp 9? > >sJ > Let's hope it's 9.9 (BTW, OpenVMS on Alpha really seems to be warp speed > compared to VAX)  J I'm afraid it may have been meant ironically, as in "THIS is as good as it gets???"   - bill   ------------------------------  % Date: Tue, 23 Oct 2001 21:22:45 -0500r1 From: "David J. Dachtera" <djesys.nospam@fsi.net>e* Subject: Re: How know last system restart?' Message-ID: <3BD625F5.FB578A7A@fsi.net>:   Carl Perkins wrote:r > ) > "Tom Linden" <tom@kednos.com> writes...g- > }Now, if I wanted to define in my login.comi > }rB > }uptime=3D=3D the below text, how do I escape the double quotes? > ( > The easiest way is not to do so, i.e.: > 4 > $ uptime :== Write Sys$Output F$GetSYI("BOOTTIME") > C > If you really want to use the plain old "==" definition operator,a4 > you can escape the double quotes by doubling them: > 7 > $ uptime == "Write Sys$Output F$GetSYI(""BOOTTIME"")"( >  > I prefer the former.   Actually, I prefer:R   $ say :== write sys$output* $ btime == "''say' f$getsyi(""boottime"")"" $ uptime :== show system/noprocess   --   David J. Dachtera2 dba DJE SystemsR http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------   Date: 23 Oct 2001 21:26 CDTc' From: carl@gerg.tamu.edu (Carl Perkins)i* Subject: Re: How know last system restart?- Message-ID: <23OCT200121262343@gerg.tamu.edu>p  3 Michael Zarlenga <zarlenga@conan.ids.net> writes...o) }Carl Perkins <carl@gerg.tamu.edu> wrote:a) }: The easiest way is not to do so, i.e.:  } 5 }: $ uptime :== Write Sys$Output F$GetSYI("BOOTTIME")R } D }: If you really want to use the plain old "==" definition operator,5 }: you can escape the double quotes by doubling them:f } 8 }: $ uptime == "Write Sys$Output F$GetSYI(""BOOTTIME"")" }  }: I prefer the former.s }  }I would, too, if it worked. }  }--  }-- Mike Zarlengat  F Nuts. I suspected I didn't manage to cancel that before it propigated.F After typing it in and sending it, I said to myself "that doesn't lookF right" and actually tested it. Then I entered a Cancel command for it. Not fast enough, aparently.    --- Carl   ------------------------------   Date: 23 Oct 2001 21:54 CDTu' From: carl@gerg.tamu.edu (Carl Perkins)r* Subject: Re: How know last system restart?- Message-ID: <23OCT200121545293@gerg.tamu.edu>c  5 "David J. Dachtera" <djesys.nospam@fsi.net> writes...  }  }Actually, I prefer: }  }$ say :== write sys$output,+ }$ btime == "''say' f$getsyi(""boottime"")"o# }$ uptime :== show system/noprocessa }--  }David J. Dachtera  D Well, what I actually *use* is a symbol, "uptime*s", which @s a .comA file which loops through all the nodes in the cluster and returns B the boot time and calculated uptime for each (along with node name and system hardware type).   --- Carl   ------------------------------  % Date: Tue, 23 Oct 2001 22:34:07 -0500l1 From: "David J. Dachtera" <djesys.nospam@fsi.net>r* Subject: Re: How know last system restart?' Message-ID: <3BD636AF.C0623DC8@fsi.net>2   Carl Perkins wrote:0 > 7 > "David J. Dachtera" <djesys.nospam@fsi.net> writes...E > }e > }Actually, I prefer: > }3 > }$ say :== write sys$outputR- > }$ btime == "''say' f$getsyi(""boottime"")"t% > }$ uptime :== show system/noprocess  > }--e > }David J. Dachtera > F > Well, what I actually *use* is a symbol, "uptime*s", which @s a .comC > file which loops through all the nodes in the cluster and returnsdD > the boot time and calculated uptime for each (along with node name > and system hardware type).  6 I suppose one could also (in a .COM in your DCL$PATH):  5 o Use F$CSID() to loop through the nodes in a cluster 3 o For each node, get NODENAME and BOOTTIME, then do 6   SHOW SYSTEM/NOPROCESS/NODE=node to show the uptime+.   Kewl. Also:i   $ SHOW SYSTEM/NOPROCESS/CLUSTERa  H ...works "out of the box" with no further DCL programming, if that's all	 you want.r   -- f David J. Dachteran dba DJE Systemsa http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/.   ------------------------------    Date: 23 Oct 2001 13:45:10 -0700, From: ezharkov@yahoo.com (Eugene A. Zharkov)F Subject: How to redirect output&error into a single file in sys$creprc= Message-ID: <af0b5c61.0110231245.5771adeb@posting.google.com>S  @ The following example creates two versions of the test.log file.6 Is there an easy way to tell creprc to make just one ?  	 $ cc test, $ link test. $ mcr []test spawn   ---C   #include <stdio.h> #include <stdlib.h>d #include <string.h>  #include <starlet.h> #include <descrip.h> #include <lib$routines.h>t #include <ssdef.h> #include <prcdef.h>r  " int main (int argc, char **argv) {   if (argc == 1) {,     fprintf (stdout, "message to stdout\n");,     fprintf (stderr, "message to stderr\n");   }n   else {$     $DESCRIPTOR (image, "test.exe");%     $DESCRIPTOR (output, "test.log");u$     $DESCRIPTOR (error, "test.log");     $DESCRIPTOR (name, "test");eA     int status = sys$creprc (NULL, &image, NULL, &output, &error,s. 			     0, 0, &name, 0, 0, 0, PRC$M_DETACH);       if (status == SS$_NORMAL)s       printf ("OK\n");
     else {&       printf ("FAILURE %x\n", status);       lib$signal (status);     }    }t }e   ------------------------------  # Date: Tue, 23 Oct 2001 21:04:32 GMTi2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)J Subject: Re: How to redirect output&error into a single file in sys$creprc1 Message-ID: <AXkB7.853$RL6.9604@news.cpqcorp.net>   l In article <af0b5c61.0110231245.5771adeb@posting.google.com>, ezharkov@yahoo.com (Eugene A. Zharkov) writes:A :The following example creates two versions of the test.log file.f7 :Is there an easy way to tell creprc to make just one ?p ..B :    int status = sys$creprc (NULL, &image, NULL, &output, &error,/ :			     0, 0, &name, 0, 0, 0, PRC$M_DETACH);  l  B   You could specify the error argument as NULL, causing errors and+   output to both be routed to the output...o   :    if (status == SS$_NORMAL)  C   I'd encourage use of the condition value format, and not a directoA   match against a condition value.  Why?  Well, your routine willfA   report all successful status values -- except SS$_NORMAL -- as  >   a failure.  Instead, yse something like this stsdef.h macro:  %   if (!$VMS_STATUS_SUCCESS( status ))T     failure case...-   :    } :  } :}  C   You will want to explicitly set an exit status, via exit() or vialC   a return off the end of the main.  If you don't explicitly set an-A   exit value, DCL procedures calling this image can be left with -B   unexpected junk in $STATUS (and $SEVERITY), as these symbols get8   whatever was left in register R0 when the image exits.  N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Tue, 23 Oct 2001 21:26:45 -0500h1 From: "David J. Dachtera" <djesys.nospam@fsi.net>n Subject: Re: I am changing jobs.' Message-ID: <3BD626E5.EC3B8B21@fsi.net>    Hamlyn Mootoo wrote: > [snip] I honestly didn't8 > know there was a group specifically for VMS marketing.  D Neither did I. When do they start work? That is to say, when do theyF come forth with their first effort? So, far we've seen nothing I wouldE associate with a marketing group, rather perhaps a freshman marketingc student.   -- M David J. Dachterad dba DJE Systemsc http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/R   ------------------------------    Date: 24 Oct 2001 05:25:45 +0800, From: Paul Repacholi <prep@prep.synonet.com> Subject: Re: It's FridayM Message-ID: <87r8rudp5y.fsf@k9.i-did-not-set--mail-host-address--so-shoot-me>r  1 StevenU@POBoxes.com (Steven P. Underwood) writes:a  C > My 4 year old daughter has her own VMS account on my AlphaStation F > 400/233.  She likes to type "letters" and can spell her own name, soF > I set it up to open the editor for her when she logs in.  It's a lotD > safer than letting her have at it on the Win95 box.  I still don'tF > know how she has changed some of the things she has on that machine.  G Go and get Nethack and install it for her. Best favor you can do a kid.MB X.... ah, xboing!! is another one that keeps them out of mischief.   -- r< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.o@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------  % Date: Tue, 23 Oct 2001 14:15:30 -0400N5 From: "Fred Kleinsorge" <kleinsorge@star.zko.dec.com>n Subject: Re: mode nibble??1 Message-ID: <8uiB7.831$RL6.9577@news.cpqcorp.net>u   Eh?  What architecture?l   nuallain wrote in messaget4 <352b9262.0110230608.73ad9568@posting.google.com>...C >Could someone help to descibe what a mode nibble's function is?  IpD >understand that the mode nibble is the first 4 bits on the op code.E >What does this do?  Does it describe the number of operands that theaB >op code will be handling so as to allocate enough memory for this >number of operands? >  >Thanks.   ------------------------------  # Date: Tue, 23 Oct 2001 19:22:35 GMTu2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) Subject: Re: mode nibble??1 Message-ID: <%rjB7.840$RL6.9666@news.cpqcorp.net>f  i In article <8uiB7.831$RL6.9577@news.cpqcorp.net>, "Fred Kleinsorge" <kleinsorge@star.zko.dec.com> writes:t :Eh?  What architecture? :s :nuallain wrote in message5 :<352b9262.0110230608.73ad9568@posting.google.com>... D :>Could someone help to descibe what a mode nibble's function is?  IE :>understand that the mode nibble is the first 4 bits on the op code. F :>What does this do?  Does it describe the number of operands that theC :>op code will be handling so as to allocate enough memory for this. :>number of operands?S  K   I'm guessing this is a reference to the four-bit IA-64 template encoding :K   field; the field that describes the types of instructions present in the  G   bundle.  Pointers to the Intel IA-64 documentation are in the OpenVMS@H   FAQ, and this template encoding stuff is in volume one, chapter three.  K   But yes, we definitely need some additional context -- parallel printers f#   have a nibble mode, for instance.r  N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Tue, 23 Oct 2001 20:42:33 -0400 0 From: "Island Computers" <dbturner@islandco.com>F Subject: Re: PC164, OVMS7.2, isacfg and graphic cards (MACH64, S3 968)/ Message-ID: <ttc34nlljibab8@news.supernews.com>e  I Actually we purchased a load of IBM branded S3Trio64 2mb PCI cards - theyc work perfectly   DEC used the Number 9 Brandd  . Any S3Trio64 based PCI card should work though   David0   -- David Turner   We sell Alpha systems & partsr http://www.islandco.com6 sales@islandco.com Island Computers US Corp./ 2700 Gregory Street1 Savannah GA 31404  Tel: 912 447 6622e Fax: 912 201 0096a1 Michael Joosten <joost@c-lab.de> wrote in messageh news:3BBF7EAA.6113@c-lab.de... > Island Computers wrote:b > >tI > > You know - for a few bucks you can buy a cheap S3Trio64 1MB PCI VideoS Card" > > which is enough for DECwindows > > ! > > It's a hell of a lot easier !l > >d > > -- > > David Turner >hJ > That's probably the way I'll go. As the SYS$CONFIG.DAT uses explicit PCIE > ids, I probably have to look exactly for a specific S3Trio64 brand,jC > preferably with 2MB, haven't I? What model did you bundle in your0	 > offers?O >2I > Still, I'd like to know what problem this ISA table stuff is caused by.c >s > Thanks, Michaela > --, > Michael Joosten, SBS C-LAB, joost@c-lab.de, > Fuerstenallee 11, 33094 Paderborn, Germany. > Phone: +49 5251 606127, Fax: +49 5251 606065: > C-LAB is a cooperation of University Paderborn & SIEMENS   ------------------------------  % Date: Tue, 23 Oct 2001 21:04:40 -0500:1 From: "David J. Dachtera" <djesys.nospam@fsi.net> F Subject: Re: PC164, OVMS7.2, isacfg and graphic cards (MACH64, S3 968)' Message-ID: <3BD621B8.C256FBC0@fsi.net>    Island Computers wrote:e > K > Actually we purchased a load of IBM branded S3Trio64 2mb PCI cards - theyM > work perfectly >  > DEC used the Number 9 Brand  > 0 > Any S3Trio64 based PCI card should work though  = Do they work with vanilla VMS/DECwindows or do I need Open3D?    --   David J. Dachterao dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------   Date: 23 Oct 2001 20:39 CDT ' From: carl@gerg.tamu.edu (Carl Perkins) K Subject: Re: SAMBA VMS and Windows XP - Re: Windows XP reality check please - Message-ID: <23OCT200120393500@gerg.tamu.edu>   8 John Malmberg <Malmberg@dskwld.zko.dec.compaq> writes... }Carl Perkins wrote:I }> I havn't done an activation. There are currently two XP systems on ourkK }> net so one of the occasions was to mess with it to figure out how to geteH }> them to talk to the Samba server I'm running on VMS - which isn't tooK }> hard to do (but the connection is slow (the W2K buffer size negotiation rF }> patch might improve that, but I havn't gotten around to it yet) andK }> occasionally disconnects requiring reentering the password, and possiblymG }> username, for no known reason, usually when left running overnight)._  J }> (The changes needed to get Samba to work were all done via the security }> policy thingy.) } H }What changes?  Enabling plain-text passwords is not required for SAMBA  }2.0.6 on OpenVMS. }  }Is there something else?i }  }-John }Malmberg@dskwld.zko.dec.compaqr }Personal Opinion Only   I'm still using 2.0.3.  K Unfortunately, at the moment I can't find any record of exactly what I did.hM (Not a good sign - I'll have to figure it out again next time instead of justtJ looking it up.) Enabling plain text passwords was only one of the things IK did before it started to work. I think there were at least 2 other settingsuG I changed as well, although I may have fiddled with more stuff than was6& necessary, but I don't remember what.   6 It does work, other than the above mentioned problems.   --- Carl   ------------------------------    Date: 23 Oct 2001 14:51:15 -0700$ From: leeroth@my-deja.com (Lee Roth)@ Subject: Re: SEDT problems on RedHat 7.1 (was Re: EDT for Linux)< Message-ID: <d0e744c9.0110231351.789f80d@posting.google.com>   >  > : Lee (an old fart from DEC) > < > Hi, Lee. The name sounds familiar.  I'm also an ex-DECcie.  D ... that's because I'm an ex-'boxer just like you- but I just did it on the sidet& instead of a career like you did.  ;^}  D Thanks for the tip... I'll just plug the definitions in directly andA skip the includes. This is just for my use, not for distribution.   * Shoulda learned C instead of Perl I guess.   Thanks!n   Leet   ------------------------------    Date: 23 Oct 2001 21:47:27 -0700$ From: leeroth@my-deja.com (Lee Roth)@ Subject: Re: SEDT problems on RedHat 7.1 (was Re: EDT for Linux)= Message-ID: <d0e744c9.0110232047.78958a33@posting.google.com>4  @ Well, the brute force method got it to compile correctly and *it works!* after compiling!!!  = I kept doing compile/blowup/edit then repeat until it worked."  / I did evil stuff to file 'vars.c' and 'vars.h':9   $diff ../s0/vars.c ./vars.c2 291c291. < uid_t My_UID;r ---c
 > int My_UID;n 293c293n < gid_t My_GID;. ---0
 > int My_GID;f 305c305n < struct winsize ws; ---  > /*struct winsize ws;*/     $ diff ../s0/vars.h ./vars.h   139,141c139,141o < extern uid_t My_UID; < extern gid_t My_GID; ---e > extern int My_UID; > extern int My_GID;  D I'm posting this in case some other poor unfortunate wants to do the6 same thing I did (get SEDT compiled under RedHat 7.1).  C Thanks for all the suggestions... I guess I'm a 'C' programmer now,o right?  8^))   Lee    ------------------------------  # Date: Tue, 23 Oct 2001 18:29:23 GMTe2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)< Subject: Re: Shared file access under NT and VMS question...1 Message-ID: <7GiB7.833$RL6.9707@news.cpqcorp.net>o  _ In article <20011023135459.17436.00000819@mb-ch.aol.com>, casinoop2@aol.com (CasinoOp2) writes:mO :It would really be nice if an NT program could access this file as well as VMSo :programs. Any idea out there?  H   What are you using to "map" the OpenVMS drive to the Windows NT box?  G   NFS?  SMB?  Something else?  (I'd guess it is whatever is mapping the D   file is also holding it locked, and potentially with good reason.)  H   If you want to continue to use your current NT configuration, you can G   probably simulate what you want using a network connection to a local I   application server running on OpenVMS, serving the files to the WindowstH   NT client.  You could create your own FAL-like server, in other words.  ?   Does Windows NT have the concept of distributed file sharing?f  N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------    Date: 23 Oct 2001 13:21:43 -0500+ From: young_r@encompasserve.org (Rob Young)$* Subject: Re: Single or Multiple Sys Disks?3 Message-ID: <VPm9hJfR2Vvz@eisner.encompasserve.org>a  Y In article <3BD58F71.1E80C13C@vmmc.org>, Jack Trachtman <Jack.Trachtman@vmmc.org> writes:uI > After all these years managing stand alone VMS systems, I'll finally beo= > getting to manage two clustered systems: 2xES45 and 3xES45.c > D > My question: How to choose between single system disk and multipleF > disks.  The first is easier to manage, but the second allows rolling* > upgrades w/less down time for the users. > - > Could I get some thoughts on this?  Thanks.l >   < 	You could do rolling upgrades even if a single system disk.  < 		1)  Backup/image/igno=interlock sys$sysdevice: new_device: 		2)  Shutdown a nodee 		3)  Boot node off new_device:. 		4)  Upgrade New_device:h  = 	etc.  New_device: becomes your new system disk when all are : 	booted off that upgraded disk.,  - 	What kind of storage?  Multiple controllers?$  A 	If multiple controllers and you don't have an aversion to volume ? 	shadowing , you may wish to shadow across controller pairs fori) 	system disks and other critical volumes.   H 	In most clusters I would recommend a single system disk shadowed acrossE 	separate controllers.  If not using shadowing, make sure your system-( 	disk is a mirror-set at the controller.  B 	I can't see using multiple system disks in clusters that small as 	an advantage.   				Robs   ------------------------------   Date: 24 Oct 2001 00:59:37 GMT1 From: lewisspam@lumina.mitre.org (Keith A. Lewis)m* Subject: Re: Single or Multiple Sys Disks?( Message-ID: <9r53pp$502$1@top.mitre.org>  ~ Jack Trachtman <Jack.Trachtman@vmmc.org> writes in article <3BD58F71.1E80C13C@vmmc.org> dated Tue, 23 Oct 2001 08:40:34 -0700:H >After all these years managing stand alone VMS systems, I'll finally be< >getting to manage two clustered systems: 2xES45 and 3xES45. > C >My question: How to choose between single system disk and multiple E >disks.  The first is easier to manage, but the second allows rollingu) >upgrades w/less down time for the users.u >t, >Could I get some thoughts on this?  Thanks.  K Most of your management-time savings comes from having a single sysuaf.dat,pK vmsmail_profile.data, qman$master.dat, and such.  Once you have moved thesefJ files to a good place (the clustering manual recommends NOT a system disk,I for a symetric 2-member cluster I think I'd put those files on the quoruml disk).  K The only issue left is upgrades.  Do you want to do them once or twice?  If-L you're more cautious than lazy, you'll want to check out new software on oneL machine first, so you'll want 2 system disks.  That's my advice -- no matterJ what the size of your cluster, have 2 system disks.  Keep the root numbersB unique in case you want to switch a machine from one to the other.  / --Keith Lewis              klewisspam@mitre.org?> The above may not (yet) represent the opinions of my employer.   ------------------------------  % Date: Wed, 24 Oct 2001 09:48:40 +0500e4 From: Valentin Likoum <valentin.likoum@ncc.volga.ru>" Subject: Re: Socket problem-URGENT2 Message-ID: <26464985.20011024094840@ncc.volga.ru>  H On 23.10.2001 mergoktas@erdemir.com.tr <mergoktas@erdemir.com.tr> wrote:  < > I have tcp/ip server task which can accept 16 simultaneous= > connections. Task is written in FORTRAN by using QIO system L > services. All I/O(s) are done by AST routines, accepting a new connection= ,s0 > reading from a socket and writing to a socket.  2 > DEC TCP/IP Services for OpenVMS VAX Version V3.3* > on a VAX 4000-400 running OpenVMS V5.5-2  L > My clients request some data from the server at every 5 seconds by sendin= gtL > 10 bytes long message. Server responds about 400 bytes data for each requ= est.  L > The system works 2 or 3 hours without any problem but after that I have t= he > following report from UCX.   UCX>> sh dev bg585/full L > =A0Device_socket: bg585 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0LO=& CAL =A0 =A0 =A0 =A0 =A0 =A0 =A0 REMOTEL > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Port: =A0 =A0=6  =A0 =A0 =A0 5500 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 1051N > =A0 =A0 =A0 =A0 =A0 Type: STREAM =A0 =A0 =A0 =A0Host: =A0 =A0 CAL21 =A0 =A0="  =A0 =A0 =A0 =A0 =A0 165.156.2.162F > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Service:  N > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=D  =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0RECEIVE =A0 =A0 =A0 SENDL > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Qu=L eued I/O =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A0 =A0 0=  L > =A0 =A0 =A0 =A0Q0LEN =A0 =A0 =A0 =A0 0 =A0 =A0 =A0 =A0 =A0 =A0 Socket buf=5 fer bytes =A0 =A0 =A0 =A0 =A0 0 =A0 =A0 =A0 =A0 60019lL > =A0 =A0 =A0 =A0QLEN =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A0 =A0 Socket b=3 uffer quota =A0 =A0 =A0 16000 =A0 =A0 =A0 =A0 60000 L > =A0 =A0 =A0 =A0QLIMIT =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 =A0 =A0 Total buff=7 er alloc =A0 =A0 =A0 =A0 =A0 =A00 =A0 =A0 =A0 =A0 68712TL > =A0 =A0 =A0 =A0TIMEO =A0 =A0 =A0 =A0 0 =A0 =A0 =A0 =A0 =A0 =A0 Total buff=3 er limit =A0 =A0 =A0 =A064000 =A0 =A0 =A0 =A0240000-L > =A0 =A0 =A0 =A0ERROR =A0 =A0 =A0 =A0 0 =A0 =A0 =A0 =A0 =A0 =A0 Buffer or =7 I/O waits =A0 =A0 =A0 =A05610 =A0 =A0 =A0 =A0 =A0 =A0 0-L > =A0 =A0 =A0 =A0OOBMARK =A0 =A0 =A0 0 =A0 =A0 =A0 =A0 =A0 =A0 Buffer or I/=7 O drops =A0 =A0 =A0 =A0 =A0 0 =A0 =A0 =A0 =A0 =A0 =A0 0dL > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0I/=C O completed =A0 =A0 =A0 =A0 =A0 =A0 =A05609 =A0 =A0 =A0 =A0 =A05611uL > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0By=9 tes transferred =A0 =A0 =A0 =A0 56090 =A0 =A0 =A0 1572393e   > =A0 Options: =A0REUSEADR$ > =A0 State: =A0 =A0ISCONNECTED PRIV > =A0 RCV Buff: WAIT > =A0 SND Buff: None  L > When I have above picture from UCX, I still able to receive data from cli= entt > side,m/ > but ofcourse can not send data to the client.n  L > Since the "Socket buffer bytes" exceeds the "Socket buffer quota", socket=  getsn > inL > SUSPENDED mode. If I close the socket and initiate a new connection from = client > sideG > it starts working normally. But some time later same problem happens.e  L > I analized the network traffic at packet level when the send buffer of th= es; > socket started to stack data. There was no packet at all.S  A > I think I have enough room for non-paged dynamic memory on VMS.V  L > What can be the reason with socket settings or some VMS parameters or any= thinge > else ?L > And what is the latest version of UCX that I can use on VAX 4000-400 runn= inge > OpenVMS V5.5-2?h > Please help. URGENT. > Thanks a lot in advance.    D   Do you have the latest ECO installed? It was ECO 10 for UCX 3.3 on Alpha, don't know for VAX.     --=20    Valentin Likoumk   valentin.likoum@ncc.volga.ru   ------------------------------   Date: 24 Oct 2001 00:42:26 GMT1 From: lewisspam@lumina.mitre.org (Keith A. Lewis))% Subject: Re: TPU/EVE Spelling Checkerl( Message-ID: <9r52pi$4o1$1@top.mitre.org>  { Jim Becker <jbecker@ui.urban.org> writes in article <3BD50414.2A393556@ui.urban.org> dated Tue, 23 Oct 2001 01:45:56 -0400:h; >You can get DECspell from the OpenVMS Freeware CD or from: : >http://www.openvms.compaq.com/openvms/freeware/index.html  ( I got it from the freeware CD V5, and...  6         Beginning installation of SPLAXP V1.5 at 00:31  6 %VMSINSTAL-I-RESTORE, Restoring product save set A ...  ;                  This DECspell kit for OpenVMS Alpha is for.  1                             * INTERNAL USE ONLY *'  J         The DECspell product has been retired and can no longer be ordered         by customers.t  H         The kit is NOT to distributed via any "shareware" method either,5         the dictionary is copyright Houghton Mifflin.m   Heh heh, I'm telling!a  / --Keith Lewis              klewisspam@mitre.org,> The above may not (yet) represent the opinions of my employer.   ------------------------------   Date: 24 Oct 2001 01:52:22 GMT/ From: Thomas Dickey <dickey@saltmine.radix.net>31 Subject: Re: vt420 soft characters example (drcs)e* Message-ID: <9r56sm$c1b$2@news1.Radix.Net>  9 In comp.os.vms Adam Maulis <maulis@ludens.elte.hu> wrote:0 > Hi,0  * > there is a little utility to demonstrate9 > the vt420 DRCS (dinamically redefinable character sets)   5 > I looked for any vt420 soft character demonstrationt, > but I couldnot find any. So I wrote it :-)  O there's a simple test-screen in vttest which demos drcs (but I don't distributee1 fonts with it - used some that DECUS had online):    	http://dickey.his.com/vttest/ 	ftp://dickey.his.com/vttest/    -- g= Thomas E. Dickey <dickey@radix.net> <dickey@herndon4.his.com>  http://dickey.his.comd ftp://dickey.his.com   ------------------------------    Date: 23 Oct 2001 16:49:40 -0500- From: Kilgallen@SpamCop.net (Larry Kilgallen)., Subject: Re: Windows XP reality check please3 Message-ID: <l7Yp2BkdEqMH@eisner.encompasserve.org>o  W In article <ttb4uj2r230kc4@news.supernews.com>, "John Vottero" <John@mvpsi.com> writes:-< > "Bob Koehler" <koehler@encompasserve.org> wrote in message/ > news:B$oqGDvvaP$Z@eisner.encompasserve.org...-A >> In article <tt8dbab4ksr02a@news.supernews.com>, "John Vottero"S > <John@mvpsi.com> writes: >>M >> > There is a home version of OpenVMS.  It just costs about 5 times as muchu > as
 >> > Windows.3 >>F >>    Free is too expensive?  When I think of home version, I think of >>    hobbyist.f >> >  > home != hobbyist.S  , But hobbyist = home, by license restriction.   ------------------------------   Date: 23 Oct 2001 21:04 CDT2' From: carl@gerg.tamu.edu (Carl Perkins)E Subject: Re: Working sets - Message-ID: <23OCT200121045379@gerg.tamu.edu>h   In article <rdeininger-2310011159050001@user-2ive7bq.dialup.mindspring.com>, rdeininger@mindspring.com (Robert Deininger) writes...pI }In article <rF7B7.284$c5.2244@newsfeeds.bigpond.com>, "Jaime H. Barroco"2' }<jbarroco@broadway.bigpond.com> wrote:> }  }> All,, }>   }> I have great3 }  }  }It's a Boo! } / }In the midst of the word he was trying to say,c' }In the midst of his laughter and glee,i& }He softly and silently vanished away,% }For the Snark was a Boojum, you see.e } ) }(from memory, probably not quite right.)  }  }--  }Robert Deiningerg }rdeininger@mindspring.com  D Hm. The end of "The Hunting of the Snark, an Agony in Eight Fits" byB Lewis Carrol (Hey, I get to give a spoiler warning on comp.os.vms,F how odd! So: Warning, if you don't want to know how it turns out until& you have read it yourself, stop now!):  =  "It's a Snark!" was the sound that first came to their ears,-,       And seemed almost too good to be true.0  Then followed a torrent of laughter and cheers:*       Then the ominous words "It's a Boo-"  3  Then, silence.  Some fancied they heard in the air         A weary and wandering sigh1  That sounded like "-jum!" but the others declarei(       It was only a breeze that went by.  2  They hunted till darkness came on, but they found(       Not a button, or feather, or mark,7  By which they could tell that they stood on the groundn-       Where the Baker had met with the Snark.e  /  In the midst of the word he was trying to say, ,       In the midst of his laughter and glee,,  He had softly and suddenly vanished away---,       For the Snark *was* a Boojum, you see.   --- Carl   ------------------------------  % Date: Tue, 23 Oct 2001 14:39:55 -0400t5 From: "Fred Kleinsorge" <kleinsorge@star.zko.dec.com>-0 Subject: Re: WRITEBOOT and dual-boot bootblocks?1 Message-ID: <1RiB7.834$RL6.9733@news.cpqcorp.net>A  % Robert Deininger wrote in message ...i2 >In article <7e%A7.786$RL6.8716@news.cpqcorp.net>,% >hoffman@xdelta.zko.dec.nospam wrote:@ >w >zK >Come to think of it, VMS "fat binaries" would be very useful, even if theynH >only supported Alpha and IPF.  It might also be useful to support imageG >sections optimized for different generations within the same processorSK >family, in the same image file.  Is this a practical thing to implement ine >a future version of VMS?e >i    K We took a hard, long look at Fat Binaries.  It's a lot harder than it seemseF when you first look at it.  And all of the schemes we came up with had something nasty/ugly with it.n  F In the end, the simplest solution was what we recommend - the user canJ create multiple versions of an application for different architectures, orJ different optimizations.  They need to have different names.  you can thenI either assign logical names for the images to point to the "correct" one.bL Or you can create multiple subdirectories for different architectural images0 to reside in, and have appropriate search lists.  K So, FOO.EXE might be in FOO:[BIN.EV6] and FOO:[BIN.ALPHA] and FOO:[BIN.VAX]iF and you have a logical name BAR that translates to (on say a Alpha EV6H system) FOO:[BIN.EV6], FOO:[BIN.ALPHA] if FOO.EXE isn't in EV6, it would) find it in the generic "ALPHA" directory.n  A Of course, I think it would be a great idea if we made it easier.e  K My own opinion was that it was a mistake to call Alpha executables .EXE, weiK should have called them something else (say .AEX).  And the image activator2K "could" be made smarter to automatically look for different images - but ofr* course, this could impact activation time.  J I myself have written applications that have modules multiply compiled forJ different architectures, with runtime logic to detect the architecture andK use the right logic - mostly this was XServer code that needed to do things ) differently for various IO space methods.i  L BTW - The compilers can emit code that takes advantage of some architectural2 features using AMASK (if I recall the name right).   ------------------------------  # Date: Tue, 23 Oct 2001 19:25:41 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)0 Subject: Re: WRITEBOOT and dual-boot bootblocks?1 Message-ID: <VujB7.841$RL6.9637@news.cpqcorp.net>o  i In article <1RiB7.834$RL6.9733@news.cpqcorp.net>, "Fred Kleinsorge" <kleinsorge@star.zko.dec.com> writes:   M :BTW - The compilers can emit code that takes advantage of some architecturaln3 :features using AMASK (if I recall the name right).u  K   The current compilers do use AMASK-protected instruction sequences within.H   loops -- the processor jumps to an instruction sequence that best usesI   the available instruction set.  Please see the OpenVMS FAQ for general wJ   details on the use of the /ARCHITECTURE and /OPTIMIZE=TUNE capabilities "   present in the recent compilers.  N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Tue, 23 Oct 2001 21:51:56 +0100o% From: "a.carlini" <arcarlini@iee.org>:0 Subject: Re: WRITEBOOT and dual-boot bootblocks?' Message-ID: <3BD5D86C.1DC5E122@iee.org>o   Christopher Smith wrote: > G > Out of curiosity, which VAXStation system is The One? :)  (Or are yousL > referring to the VAXStation which was an add-on for the 11/780 (I think)?)  * I presume that's the VAXstation 8000 - all* the others I can think of have VMB in ROM.  / I don't think anyone classes the VAXstation 100l' and VAXstation 500 (and the other early + pre VS1 add-ons as a VAXstation in anythingo other than name).    Antonio    -- u   ---------------o- Antonio Carlini             arcarlini@iee.org    ------------------------------    Date: 24 Oct 2001 04:21:43 +0800, From: Paul Repacholi <prep@prep.synonet.com>0 Subject: Re: WRITEBOOT and dual-boot bootblocks?M Message-ID: <87ofmyf6p4.fsf@k9.i-did-not-set--mail-host-address--so-shoot-me>e  4 rdeininger@mindspring.com (Robert Deininger) writes:  : > Are you asking for a brave soul who has actually built aD > dual-architecture boot disk by hand?  That seems like a nasty job;C > at least one architecture would have to be diverted away from the-C > SYS$COMMON directory tree.  I guess it could be made to work, bute5 > installations and upgrades would likely be painful.-  H VAX$COMMON and AXP$COMMON. Near had the sucker working. Point sys$commonC at flavour d'arch and away you go. The problem is that a few thingsg( went looking for VMS$COMMON from memory.   --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.a@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------  % Date: Tue, 23 Oct 2001 20:35:27 +0200p. From: "Jesper Naur" <jesper.naur@post.tele.dk>8 Subject: Re: X server and SET DISPLAY on different port?= Message-ID: <3bd5b6e3$0$25393$edfadb0f@dspool01.news.tele.dk>a  3 David Froble <davef@tsoft-inc.com> wrote in message	& news:3BD59BE6.1060003@tsoft-inc.com...& > Brian Schenkenberger, VAXman- wrote:I > >>>>Is it possible to run the DECwindows server such that it will use ae > >>>>
 > >>differentk > >>K > >>>>port (a port other than port 6000)?  If so, can a SET DISPLAY commandd > >>>> > >>then bee > >>& > >>>>directed to this new port?  How? > >>>> > >>If you say > >>> > >>   $ set display/create/trans=tcpip/node=<node>/server=<n> > >>= > >>the applications will attempt to connect to port 6000+<n>r > >> > >l > > How about port 100?i > >a > >r >o2 > What happens if you use a value of -5900 for n ? >   F I have tried this, and it actually seems to work! I checked this usingH TCPTRACE (or TCPIPTRACE if you're on UCX 4.x or earlier), and it clearly@ attempts to connect to port 100. Also, -5920 results in port 80.  H Brian, you mention, that you patched DECW$TRANSPORT_TCPIP.EXE to get theI server listening on another port. Does that mean, that you have found theB6 port number hardwired in the compiled/executable code?       Best regards     Jesper Naurg   ------------------------------  # Date: Tue, 23 Oct 2001 20:19:42 GMTt= From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)s8 Subject: Re: X server and SET DISPLAY on different port?0 Message-ID: <00A03F66.FC5F0909@SendSpamHere.ORG>  n In article <3bd5b6e3$0$25393$edfadb0f@dspool01.news.tele.dk>, "Jesper Naur" <jesper.naur@post.tele.dk> writes: >m4 >David Froble <davef@tsoft-inc.com> wrote in message' >news:3BD59BE6.1060003@tsoft-inc.com...e' >> Brian Schenkenberger, VAXman- wrote:sJ >> >>>>Is it possible to run the DECwindows server such that it will use a >> >>>>  >> >>different >> >>eL >> >>>>port (a port other than port 6000)?  If so, can a SET DISPLAY command >> >>>>. >> >>then be >> >>h' >> >>>>directed to this new port?  How?o >> >>>>a >> >>If you sayo >> >>o? >> >>   $ set display/create/trans=tcpip/node=<node>/server=<n>s >> >>a> >> >>the applications will attempt to connect to port 6000+<n> >> >>m >> > >> > How about port 100? >> > >> > >>3 >> What happens if you use a value of -5900 for n ?  >> > G >I have tried this, and it actually seems to work! I checked this usingnI >TCPTRACE (or TCPIPTRACE if you're on UCX 4.x or earlier), and it clearlyeA >attempts to connect to port 100. Also, -5920 results in port 80.o >nI >Brian, you mention, that you patched DECW$TRANSPORT_TCPIP.EXE to get the1J >server listening on another port. Does that mean, that you have found the7 >port number hardwired in the compiled/executable code?h   Yes.    G DUMP SYS$SHARE:DECW$TRANSPORT_TCPIP.EXE and search for 1770 (that's hexO
 for 6000).   Also, from:/  I DISK$ALPHA0721LS4:[V72-1_DECW.DECW$COMMON.TRANSPORT.LIS]XPORT_TCPIP.LIS;1m     :e   :    :n[     1      3195     BASE_TCP_PORT = 6000 ;              ! TCP port used by server number 0.n   :p   :    :2-     3      4900     sockaddrin [SIN$W_PORT] =vY     3      4901         SWAP_SHORT( ( BASE_TCP_PORT + .itcc [ixtcc$l_server_number] ) ) ;t   :t   :    :rl     3      5261     sockaddrin [SIN$W_PORT] = swap_short( ( BASE_TCP_PORT + .xtpb [xtpb$w_display_num] ) ) ;   :f   :C   :         J The difficult part was devising the proper instruction sequence to overlayK the existing Alpha instruction sequence such that the code implementing the K addition of the server number and the byte swap would function properly.  I K found that simply changing the instruction 203F1770 ( LDA R1,6000(R31) ) to=K 203F0077 ( LDA R1,119(R31)  ; port 119/NNTP) did not do what I had expected  it would do.  J Unfortunately, while this all works locally, it still does not allow me toL export a display through a firewall which had port 21,23,25,80 and 119 open.I I get a connection (as is evidenced by {UCX/TCPIP} SHOW DEVICE) but thereA' is no communications on the socket.  :(    --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM=             J   "And of course, I'm a genius, so people are naturally drawn to my fiery I   intellect.  Their admiration overwhelms their envy!" -- Calvin & HobbesA   ------------------------------  % Date: Tue, 23 Oct 2001 23:27:13 +02006. From: "Jesper Naur" <jesper.naur@post.tele.dk>8 Subject: Re: X server and SET DISPLAY on different port?= Message-ID: <3bd5def6$0$29057$edfadb0f@dspool01.news.tele.dk>   H Brian Schenkenberger, VAXman- <system@SendSpamHere.ORG> wrote in message* news:00A03F66.FC5F0909@SendSpamHere.ORG...L > Unfortunately, while this all works locally, it still does not allow me toH > export a display through a firewall which had port 21,23,25,80 and 119 open.OK > I get a connection (as is evidenced by {UCX/TCPIP} SHOW DEVICE) but thereA) > is no communications on the socket.  :(A >A > --  H Can you provide the TCP[IP]TRACE output from the X-client side during an1 attempt of starting the X-client DECW$PUZZLE? Eg:5   From one terminal session say:  0 $ TCP[IP]TRACE <node>/OUTPUT=<file>/PACKET=10000  & From another on the same machine, say:  9 $ SET DISPLAY/CREATE/NODE=<node>/TRANS=TCPIP/SERVER=-59200 $ MC DECW$PUZZLE  F When this has failed, kill the first session with CTRL/Y, and post the= result (I assume, that there will be relatively few packets).i       Best regards     Jesper Naura   ------------------------------  % Date: Wed, 24 Oct 2001 00:11:16 +0200u. From: "Jesper Naur" <jesper.naur@post.tele.dk>8 Subject: Re: X server and SET DISPLAY on different port?= Message-ID: <3bd5e978$0$71942$edfadb0f@dspool01.news.tele.dk>t  H Brian Schenkenberger, VAXman- <system@SendSpamHere.ORG> wrote in message* news:00A03F66.FC5F0909@SendSpamHere.ORG...K > >Brian, you mention, that you patched DECW$TRANSPORT_TCPIP.EXE to get theeL > >server listening on another port. Does that mean, that you have found the9 > >port number hardwired in the compiled/executable code?e >  > Yes. >nI > DUMP SYS$SHARE:DECW$TRANSPORT_TCPIP.EXE and search for 1770 (that's hexn > for 6000). >5
 > Also, from:h >.K > DISK$ALPHA0721LS4:[V72-1_DECW.DECW$COMMON.TRANSPORT.LIS]XPORT_TCPIP.LIS;1l >   :wL >     1      3195     BASE_TCP_PORT = 6000 ;              ! TCP port used by server number 0. >   :@/ >     3      4900     sockaddrin [SIN$W_PORT] = = >     3      4901         SWAP_SHORT( ( BASE_TCP_PORT + .itccg [ixtcc$l_server_number] ) ) ;: >   :EK >     3      5261     sockaddrin [SIN$W_PORT] = swap_short( ( BASE_TCP_PORTb" + .xtpb [xtpb$w_display_num] ) ) ; >   :0  L What you show is not quite, what I understand by 'hardwired in the code' (byC that, I would expect the constant '6000' period and no calculations.F whatsoever). It appears however, that the port number is calculated byI taking the constant BASE_TCP_PORT and adding the 'server number'. I wouldSJ not at all be surprised, if the 'ixtcc$l_server_number' was the digit "0",L you normally see in for example the process name DECW$SERVER_0. I would also? expect, that if you figured out how to start a server with namenB DECW$SERVER_1, it would listen on port 6001 - there is code in theI SYS$[STARTUP|MANAGER]:DECW$*.COM files to create such a server (albeit, ItI haven't figured out how to actually do that). OTOH, maybe a server number G of -5920 (with a process name DECW$SERVER_-5920) would be stressing thenK concept too far... if not for other reasons, then because the 17 charactersO; would blow the 15-character process name length limitation.d  L Still, the TCP[IP]TRACE output from an unsuccesful DECW$PUZZLE attempt would be interesting.i       Best regards     Jesper Naur<   ------------------------------  # Date: Tue, 23 Oct 2001 23:43:36 GMTd= From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-) 8 Subject: Re: X server and SET DISPLAY on different port?0 Message-ID: <00A03F83.7840B006@SendSpamHere.ORG>  n In article <3bd5def6$0$29057$edfadb0f@dspool01.news.tele.dk>, "Jesper Naur" <jesper.naur@post.tele.dk> writes: >tI >Brian Schenkenberger, VAXman- <system@SendSpamHere.ORG> wrote in messageo+ >news:00A03F66.FC5F0909@SendSpamHere.ORG...rM >> Unfortunately, while this all works locally, it still does not allow me tocI >> export a display through a firewall which had port 21,23,25,80 and 119r >open.L >> I get a connection (as is evidenced by {UCX/TCPIP} SHOW DEVICE) but there* >> is no communications on the socket.  :( >> >> --g > I >Can you provide the TCP[IP]TRACE output from the X-client side during ani2 >attempt of starting the X-client DECW$PUZZLE? Eg: >o >From one terminal session say:G >a1 >$ TCP[IP]TRACE <node>/OUTPUT=<file>/PACKET=100008 >b' >From another on the same machine, say:o > : >$ SET DISPLAY/CREATE/NODE=<node>/TRANS=TCPIP/SERVER=-5920 >$ MC DECW$PUZZLEs >oG >When this has failed, kill the first session with CTRL/Y, and post thex> >result (I assume, that there will be relatively few packets).  D Tell you what.  I'll do it for both a functioning connection and theG one that fails.  I'll post back here when I've compiled the informationDD and give your a URL.  No need to clutter c.o.v. with oddles of hexa- decimal gobbledegook.0 --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COMa            gJ   "And of course, I'm a genius, so people are naturally drawn to my fiery I   intellect.  Their admiration overwhelms their envy!" -- Calvin & Hobbesb   ------------------------------  # Date: Tue, 23 Oct 2001 23:45:31 GMT = From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)s8 Subject: Re: X server and SET DISPLAY on different port?0 Message-ID: <00A03F83.BCAA6735@SendSpamHere.ORG>  n In article <3bd5e978$0$71942$edfadb0f@dspool01.news.tele.dk>, "Jesper Naur" <jesper.naur@post.tele.dk> writes: >iI >Brian Schenkenberger, VAXman- <system@SendSpamHere.ORG> wrote in message + >news:00A03F66.FC5F0909@SendSpamHere.ORG...rL >> >Brian, you mention, that you patched DECW$TRANSPORT_TCPIP.EXE to get theM >> >server listening on another port. Does that mean, that you have found thew: >> >port number hardwired in the compiled/executable code? >> >> Yes.  >>J >> DUMP SYS$SHARE:DECW$TRANSPORT_TCPIP.EXE and search for 1770 (that's hex
 >> for 6000).s >> >> Also, from: >>L >> DISK$ALPHA0721LS4:[V72-1_DECW.DECW$COMMON.TRANSPORT.LIS]XPORT_TCPIP.LIS;1 >>   :M >>     1      3195     BASE_TCP_PORT = 6000 ;              ! TCP port used by  >server number 0.u >>   :0 >>     3      4900     sockaddrin [SIN$W_PORT] => >>     3      4901         SWAP_SHORT( ( BASE_TCP_PORT + .itcc >[ixtcc$l_server_number] ) ) ; >>   :L >>     3      5261     sockaddrin [SIN$W_PORT] = swap_short( ( BASE_TCP_PORT# >+ .xtpb [xtpb$w_display_num] ) ) ;r >>   : > M >What you show is not quite, what I understand by 'hardwired in the code' (bymD >that, I would expect the constant '6000' period and no calculationsG >whatsoever). It appears however, that the port number is calculated byo  : Call it waht you will but 6000 is "hardwired in the code".   --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM             iJ   "And of course, I'm a genius, so people are naturally drawn to my fiery I   intellect.  Their admiration overwhelms their envy!" -- Calvin & Hobbesu   ------------------------------   Date: 24 Oct 2001 00:12:29 GMT1 From: lewisspam@lumina.mitre.org (Keith A. Lewis)f8 Subject: Re: X server and SET DISPLAY on different port?( Message-ID: <9r511d$49u$1@top.mitre.org>   system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-) writes in article <00A03F66.FC5F0909@SendSpamHere.ORG> dated Tue, 23 Oct 2001 20:19:42 GMT:tK >Unfortunately, while this all works locally, it still does not allow me toyM >export a display through a firewall which had port 21,23,25,80 and 119 open.rJ >I get a connection (as is evidenced by {UCX/TCPIP} SHOW DEVICE) but there( >is no communications on the socket.  :(  I Back around Decwindows 1.2-3 I had a problem using a far-away server.  ItmH turned out that DWMotif was only listening on one of my several ethernetL interfaces (EWA0)!  I switched the configuration around so that EWA0 was theH connection to the outside, and it started working.  I thought they wouldD have fixed that by now, but you know what happens when you assume...  / --Keith Lewis              klewisspam@mitre.orgI> The above may not (yet) represent the opinions of my employer.   ------------------------------  % Date: Tue, 23 Oct 2001 20:45:22 -0400 ! From: Sam Hoblit <hoblit@bnl.gov>w Subject: XP1000 problems& Message-ID: <3BD60F22.3020306@bnl.gov>   Hi -  < We recently purchased an XP1000 workstation on ebay and have; added it to our cluster running VMS 7.2-1. We configured it B as a satellite being served from a DPS 600au. Most all the current? VMS patches have been installed (UPDATE 300, etc.), and 3 otherdA alphas boot from the same system disk. When the XP1000 arrived wehA upgraded the firmware to the most recent version available on thea compaq web site, version 5.9.n  C The first problem is that if we set the ethernet adapter to 100MB/s E mode, it establishes a connection with our switch, and then downloadsrA the boot image via lan mop just fine. Then, as soon as VMS startsuC to run it checks the integrated (EWA0) adapter and issues a messagefC saying the adapter is set to autoconfigure by the console, which it-@ then sets to 10Mb/sec. This kills the rest of the transfer sinceE the switch is set to 100Mb. If we set the ethernet adapter to twistedcE pair or full-duplex twisted, VMS recognized this and leaves it alone.gE If we try setting it to autoconfigure, we never get a connection (ouriB other machines don't like this setting either). It seems VMS isn't? seeing the console setting for the ethernet adapter. We're alsoiC handicapped since we have no manuals for the system - bought as is.sD We'd really prefer to run this system at the higher speed. Any ideas# or suggestions will be appreciated!   A The second problem involves as powerstorm 300 graphics board that B produces what appears to be a bad scan rate or some other problem,F even in VGA mode. Our monitor (sony multiscan 400ps) can't lock on it.@ You can barely pick out the VGA screen if you try, but in normal? graphics mode it's a mess. We noticed a set of jumpers near thelC middle of the graphics board. Does this board need to be configured C to run in an XP1000? It's the only graphics board in the system and:; positioned in the first PCI slot, so it should be ok there.6  / thanks in advance for any ideas or suggestions,   
 Sam Hoblit   ------------------------------  $ Date: Tuesday, 23 OCT 2001 21:44 EDT. From: Bryan Jensen <bjj100@arlvax.arl.psu.edu> Subject: Re: XP1000 problems, Message-ID: <9r56od$17hq@r02n01.cac.psu.edu>  K My favorite was when the XP1000 went into 10base2 mode (it has no hardware 0B to support that of course, but that's what VMS said it was doing).  = I have yet to call Compaq support on this, but after I copied 5 sys$common:[sys$ldr]sys$ewdriver_de500ba.exe_old;2 to@: sys$common:[sys$ldr]sys$ewdriver_de500ba.exe and rebooted, all worked as desired.  a  & In article <3BD60F22.3020306@bnl.gov>,&    Sam Hoblit <hoblit@bnl.gov> writes: >Hi -e >g= >We recently purchased an XP1000 workstation on ebay and haveh< >added it to our cluster running VMS 7.2-1. We configured itC >as a satellite being served from a DPS 600au. Most all the currentu@ >VMS patches have been installed (UPDATE 300, etc.), and 3 otherB >alphas boot from the same system disk. When the XP1000 arrived weB >upgraded the firmware to the most recent version available on the >compaq web site, version 5.9. >uD >The first problem is that if we set the ethernet adapter to 100MB/sF >mode, it establishes a connection with our switch, and then downloadsB >the boot image via lan mop just fine. Then, as soon as VMS startsD >to run it checks the integrated (EWA0) adapter and issues a messageD >saying the adapter is set to autoconfigure by the console, which itA >then sets to 10Mb/sec. This kills the rest of the transfer since F >the switch is set to 100Mb. If we set the ethernet adapter to twistedF >pair or full-duplex twisted, VMS recognized this and leaves it alone.F >If we try setting it to autoconfigure, we never get a connection (ourC >other machines don't like this setting either). It seems VMS isn'tr@ >seeing the console setting for the ethernet adapter. We're alsoD >handicapped since we have no manuals for the system - bought as is.E >We'd really prefer to run this system at the higher speed. Any ideas>$ >or suggestions will be appreciated!   ------------------------------  % Date: Tue, 23 Oct 2001 20:59:46 -0500(C From: "Craig A. Berry" <craig.berry@nospam.SignalTreeSolutions.com>> Subject: Re: XP1000 problemsI Message-ID: <craig.berry-5AC84C.20594623102001@newsrump.sjc.telocity.net>t  C In article <3BD60F22.3020306@bnl.gov>, Sam Hoblit <hoblit@bnl.gov> c wrote:   > We're alsoE > handicapped since we have no manuals for the system - bought as is.   I <http://www.compaq.com/support/workstations/professionalworkstationxp1000d .html>    ? > The second problem involves as powerstorm 300 graphics board P  > <http://www.openvms.compaq.com/wizard/openvms_faq.html#MGMT24>   ------------------------------  % Date: Tue, 23 Oct 2001 14:44:26 -0400n5 From: "Fred Kleinsorge" <kleinsorge@star.zko.dec.com> , Subject: Re: [MOZILLA] Burner of CPU time!!!1 Message-ID: <gViB7.835$RL6.9708@news.cpqcorp.net>   L But it really isn't a "performance problem".  It just happens to wake up andI check for events every so often, so over time it accumulates a little CPUt time if left running idle.      L david20@alpha1.mdx.ac.uk wrote in message <9r47pl$8eg$1@aquila.mdx.ac.uk>...D >In article <DUgB7.820$RL6.8977@news.cpqcorp.net>, "Fred Kleinsorge"% <kleinsorge@star.zko.dec.com> writes:dH >>VMS will address select() and fork() in a future version.  It's in ourC >>plans.  Since doing a select() as described is a widely used UNIXcE >>convention, it's not likely to get a warm reception as something tol change.t >> >iI >I wasn't suggesting that the Mozilla writers needed to change it for any>I >other platform just that you put in some ifdef VMS pieces of code to use> >something better for VMS. >>J >Having Mozilla unusable due to perfomance on VMS until VMS 7.4 / VMS 8 or# >whenever is not really acceptable.p >n >David Webbr >VMS and Unix team leadera >CCSSi >Middlesex Universityn   ------------------------------   End of INFO-VAX 2001.591 ************************