1 INFO-VAX	Mon, 13 Aug 2001	Volume 2001 : Issue 448       Contents: Alpha Access to VAX Data Re: Alpha Access to VAX Data Re: Alpha Access to VAX Data Re: Alpha Access to VAX Data( Re: Alpha:  an invitation to communicate( Re: Alpha:  an invitation to communicate$ Re: AMD and Samsung could save Alpha$ Re: AMD and Samsung could save Alpha$ Re: AMD and Samsung could save Alpha! Re: Article from Information week 4 FTP Copy of variable record length file - VMS to VMS8 Re: FTP Copy of variable record length file - VMS to VMS Re: FYI   Re: Help! Boot Block Information  Re: Help! Boot Block Information  Re: Help! Boot Block Information  Re: Help! Boot Block Information  Re: Help! Boot Block Information  Re: Help! Boot Block Information( Re: How to trace memory usage - THANKS !8 Re: HWRPB (Alpha) blundering in the dark - info required8 Re: HWRPB (Alpha) blundering in the dark - info required= Re: I just have to post this - and apoligse later Alpha/Intel = RE: I just have to post this - and apoligse later Alpha/Intel = Re: I just have to post this - and apoligse later Alpha/Intel = Re: I just have to post this - and apoligse later Alpha/Intel ! Re: Lemmings, was Re: Move to Sun ! Re: Lemmings, was Re: Move to Sun  Link with $PRCDEF module Re: Link with $PRCDEF module Re: Linker-Warnings in VMS 7.3 Re: Linker-Warnings in VMS 7.3 Re: Linker-Warnings in VMS 7.3 Re: Linker-Warnings in VMS 7.3 Re: Mike Capellas' Diary Re: Missing TK50 in uVAX? - Re: Mozilla M0.9.3, August 3rd release; Java?  Re: OpenVMS  + Itanium2 Re: OpenVMS apps and Compaq committment story here2 Re: OpenVMS apps and Compaq committment story here. Re: Pseudo Terminals to emulate LAT Terminals?0 Re: Slow time and bad memory - are they related? Still no RDB (was Re: Lemmings) " Re: Storageworks retirement letter" Re: Storageworks retirement letter$ Re: Terry Shannon Tech Talk on Tru64A Re: The Alpha Systems Customer Update will no longer be published A Re: The Alpha Systems Customer Update will no longer be published A Re: The Alpha Systems Customer Update will no longer be published A Re: The Alpha Systems Customer Update will no longer be published & Re: The VMS Opensource Porting Project! Re: VAX/ALPHA FORTRAN and me! :-) # Re: VIRUSES: What about antibodies? # Re: VIRUSES: What about antibodies? # Re: VIRUSES: What about antibodies? # Re: VIRUSES: What about antibodies? # Re: VIRUSES: What about antibodies? # Re: VIRUSES: What about antibodies?  VMS 6.21-H3 host crashing P Re: VMS: Nothing Stops It (was "I just have to post this - and apoligse later Al! Writing to a DOS floppy under VMS % RE: Writing to a DOS floppy under VMS  Re: X window Display Setting Re: X window Display Setting Re: X window Display Setting  F ----------------------------------------------------------------------  % Date: Mon, 13 Aug 2001 08:53:01 -0400 < From: "Symons, Jeff (Innovations)" <jeff.symons-eds@eds.com>! Subject: Alpha Access to VAX Data Q Message-ID: <80C532CF88BDD4118DB700508BE326367EBCC6@camkm202.exca01.exch.eds.com>   E 	 Is it possible to access RMS data files, residing on disks in a VAX I cluster, running VMS V5.5-2H4, from a cluster of Alpha (ES40's), which is H running VMS V7.3? Or do I have to upgrade the VAX, and then cluster them	 together?    ------------------------------    Date: 13 Aug 2001 08:25:51 -05009 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen) % Subject: Re: Alpha Access to VAX Data 3 Message-ID: <cp$lFFucm+QA@eisner.encompasserve.org>    In article <80C532CF88BDD4118DB700508BE326367EBCC6@camkm202.exca01.exch.eds.com>, "Symons, Jeff (Innovations)" <jeff.symons-eds@eds.com> writes:G > 	 Is it possible to access RMS data files, residing on disks in a VAX K > cluster, running VMS V5.5-2H4, from a cluster of Alpha (ES40's), which is J > running VMS V7.3? Or do I have to upgrade the VAX, and then cluster them > together?   D It would be easier just to use DECnet (or Backup if it is a one-time) transfer).  No software upgrade required.    ------------------------------  % Date: Mon, 13 Aug 2001 11:43:46 -0400 2 From: norm lastovica <norman.lastovica@oracle.com>% Subject: Re: Alpha Access to VAX Data * Message-ID: <3B77F5B2.D405E050@oracle.com>  3 I agree with Larry.  You can (almost always) access 5 RMS files via DECnet as though they were local files. 4 Just change the logical name that refers to the file4 to include the remote node name.  Ie, if the logical> used to access the file translates to "DISK$FOO:[BAR]FILE.DAT"7 just define it to be "somenode::DISK$FOO:[BAR]FILE.DAT" # and let decnet and FAL do the rest.    Larry Kilgallen wrote: >  > In article <80C532CF88BDD4118DB700508BE326367EBCC6@camkm202.exca01.exch.eds.com>, "Symons, Jeff (Innovations)" <jeff.symons-eds@eds.com> writes:N > >        Is it possible to access RMS data files, residing on disks in a VAXM > > cluster, running VMS V5.5-2H4, from a cluster of Alpha (ES40's), which is L > > running VMS V7.3? Or do I have to upgrade the VAX, and then cluster them
 > > together?  > F > It would be easier just to use DECnet (or Backup if it is a one-time+ > transfer).  No software upgrade required.    --  > norman lastovica / oracle rdb engineering / usa / 610.696.4685   ------------------------------  # Date: Mon, 13 Aug 2001 16:28:20 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)% Subject: Re: Alpha Access to VAX Data 1 Message-ID: <EeTd7.58$bB1.10980@news.cpqcorp.net>    In article <80C532CF88BDD4118DB700508BE326367EBCC6@camkm202.exca01.exch.eds.com>, "Symons, Jeff (Innovations)" <jeff.symons-eds@eds.com> writes:F :	 Is it possible to access RMS data files, residing on disks in a VAXJ :cluster, running VMS V5.5-2H4, from a cluster of Alpha (ES40's), which isI :running VMS V7.3? Or do I have to upgrade the VAX, and then cluster them 
 :together?     Yes, via DECnet FAL.    M   Upgrading OpenVMS VAX to a more recent version will allow you to configure  N   a cluster of OpenVMS Alpha and OpenVMS VAX nodes, and you can then directly    share RMS files.  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: 13 Aug 2001 09:17:00 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de> 1 Subject: Re: Alpha:  an invitation to communicate H Message-ID: <y4r8uge8er.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  5 Eric Smith <eric-no-spam-for-me@brouhaha.com> writes:   L > Actually, neither sterilizing the scalpel nor making sure that the staples4 > are present are the responsibility of the surgeon.  M Of course they are her resposibility, even if he isn't doing the actual work.    	Jan   ------------------------------  % Date: Mon, 13 Aug 2001 12:12:56 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca> 1 Subject: Re: Alpha:  an invitation to communicate , Message-ID: <3B77FC87.58ABC7EA@videotron.ca>  N > > Actually, neither sterilizing the scalpel nor making sure that the staples6 > > are present are the responsibility of the surgeon.  K The point of the argument was that many corporations are returning to their J core competencies and outsourcing the rest (whether that is good or bad is another argument alltogether).  L If Compaq considers that designing chips is not part of its core competency,N then it gives top management enough argument for a decision to donate Alpha to= someone who can make better use of its patents and engineers.   N And just because such a decision may look very stupid to some who are involvedK in Alpha and VMS, I would think that those who bought Compaq shares as a PC L commodity manufacturer would probably be very happy to see Compaq return itsH focus to building wintel boxes as cheaply and competitively as possible.  C Wasn't Compaq's stock in the $50 range before it acquired Digital ?   L When Pfeiffer was ousted, it was probably a strong signal that those who had/ opposed the Digital takeover were now in power.     H Compaq killed Digital when you look in hindsight. Had Pfeiffer not givenH instructions to Palmer on what to ditch to make Digital small enough forN Compaq to buy (remember that the stupid Palmer had admitted on CNN that he hadL been working with Pfeiffer for 3 years prior to the takeover announcement toJ shape Digital into something Pfeiffer wanted), well had that downsizin notJ happened and the talk of a serious offer from Compaq during those 3 years,J either Palmer would have fixed up Digital to succeed or he would have beenF ousted and replaced by someone who could have done something with DEC.  N It didn't take long for Pfeiffer to be ousted after the Digital takeover, even- in the face of no replacement being in sight.    ------------------------------  % Date: Mon, 13 Aug 2001 12:38:35 +0100 ( From: Nic Clews <sendspamhere@127.0.0.1>- Subject: Re: AMD and Samsung could save Alpha ) Message-ID: <3B77BC3B.53F00D4E@127.0.0.1>    JF Mezei wrote:  >  > unixguys wrote:  > > ( > >     AMD and Samsung could save Alpha > >     day  > 0 > That would be the biggest irony, wouldn't it ? > L > Compaq drops Alpha, moves VMS to intel. Meanwhile, AMD picks up Alpha, andM > makes it industry standard, leaving IA64 as a small niche market thing. VMS P > would once again be relegated to some not so popular chip. (I wonder if Compaq9 > would re-instate VMS on Alpha if that were to happen ?)   F I think AMD shot themselves in the foot already. When Compaq (Digital)C licenced the Alpha technology to AMD, AMD's part of the deal was to E "make a motherboard Alpha compatible". That didn't happen, and Compaq C wouldn't be amused, so a deal with AMD for the Alpha wasn't helped. H (I've paraphrased recollections from my chip studies, but I'm reasonably sure of the accuracy of this).  G However I also think that the "Noboby got fired for buying Intel" (sic) C applies here. PC types will quite happily argue the night away over G which is better, AMD or Intel, regardless of the 'OS' they're trying to # run on them is what really matters.   G Even if AMD did pick up Alpha and run with it, could you say AMD is the F betamax of the VHS 'Intel' world? How could AMD convince itself if was economically viable so to do?    --  ( Regards, Nic Clews CSC Computer Sciences nclews at csc dot com    ------------------------------  % Date: Mon, 13 Aug 2001 12:03:54 -0400 ' From: "Bill Todd" <billtodd@foo.mv.com> - Subject: Re: AMD and Samsung could save Alpha ( Message-ID: <9l8tp8$f9p$1@pyrite.mv.net>  5 "Nic Clews" <sendspamhere@127.0.0.1> wrote in message # news:3B77BC3B.53F00D4E@127.0.0.1...    ...   I > Even if AMD did pick up Alpha and run with it, could you say AMD is the H > betamax of the VHS 'Intel' world? How could AMD convince itself if was > economically viable so to do?   H It would be difficult.  Alpha and VMS (and to at least a significant butI possibly lesser degree Tru64) had a synergy together than they don't have E separately, and for AMD to depend upon Compaq to keep VMS (and Tru64) G competitive on an AMD Alpha would be even stupider than Compaq's recent K actions.  Linux alone likely isn't nearly sufficient to justify the cost of J continued Alpha development, though Linux plus Win64 might be if MicrosoftJ and AMD got together (not that I expect that to happen:  AMD will be lucky, if Microsoft even deigns to support x86-64).   - bill   >  > --* > Regards, Nic Clews CSC Computer Sciences > nclews at csc dot com    ------------------------------  % Date: Mon, 13 Aug 2001 13:51:23 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca> - Subject: Re: AMD and Samsung could save Alpha , Message-ID: <3B781393.2ADCB3CB@videotron.ca>   Bill Todd wrote:J > It would be difficult.  Alpha and VMS (and to at least a significant butK > possibly lesser degree Tru64) had a synergy together than they don't have G > separately, and for AMD to depend upon Compaq to keep VMS (and Tru64) I > competitive on an AMD Alpha would be even stupider than Compaq's recent M > actions.  Linux alone likely isn't nearly sufficient to justify the cost of  > continued Alpha development   L You forget that Alpha might have other uses, such as Nintendo game boxes etcK etc. Also, didn't Ford at one point embed alphas in cars ? (or was that the  powerpc chip ?)   N And don't forget that Windows still runs on Alphas, it just isn't productized.I AMD might have the clout to get Microsoft to productize Windows on Alpha.   I If, when Windows on Alpha was canned by Compaq at a time where Compaq had M already decided that Alpha was to be killed, then it would explain why Compaq M wasn't interested in getting Windows on Alpha to continue. But if one decides H to make Alpha a competitive mainstream chip, then one could easily rival Intel's bloated IA64.    ------------------------------    Date: 13 Aug 2001 18:12:41 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de> * Subject: Re: Article from Information weekH Message-ID: <y4g0awym4m.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  / JF Mezei <jfmezei.spamnot@videotron.ca> writes:   L > But in this case, it isn't the services that Compaq wants money for, it isO > some form of assurance that Compaq will continue to support a product. I find N > it totally silly that customers should have to pay a special amount of moneyJ > specified in a contract to get an assurance that the vendor won't kill a > profitable product.   H Whether the product is profitable is neither here nor there. If you wantH something you can rely on, you need a contractually binding commitment, H one that costs the company concerned real money if they break it. UnlessJ you do so, nothing will stop Microsoft from following IBM's historic lead J and refuse to offer their software for sale tomorrow, instead insisting on@ per-use licenses payable in advance (similar to postage stamps).   	Jan   ------------------------------    Date: 13 Aug 2001 03:24:57 -07006 From: andrew.rycroft@intrinsitech.com (Andrew Rycroft)= Subject: FTP Copy of variable record length file - VMS to VMS = Message-ID: <58ba0101.0108130224.5c22e720@posting.google.com>    Hi,   ? I am using FTP to copy files from one VMS system to another VMS  system. The exact command is :-    $ COPY/FTP/ANON ll.com alpha2::   F Both systems are running UCX v5.0a. The files are sequential, variableC length record files. On doing a $ DIR/FULL the source file shows :-   B Record format:      Variable length, maximum 255 bytes, longest 61 bytes    The target file shows :-  A Record format:      Variable length, maximum 255 bytes, longest 0  bytes   ) i.e. it has lost the longest record data.   > Have tried using COPY/FTP/ANON/FDL, but this displays the same problem.  F Any suggestions on how to preserve the longest record length attribute in FTP file copies appreciated.   C I am using UCX v5.0a, and I have another site with the same problem  using UCX v4.2.    Thanks Andrew   ------------------------------   Date: 13 Aug 2001 10:34:17 GMT3 From: gartmann@immunbio.mpg.de (Christoph Gartmann) A Subject: Re: FTP Copy of variable record length file - VMS to VMS 0 Message-ID: <9l8af9$h1s$1@n.ruf.uni-freiburg.de>  v In article <58ba0101.0108130224.5c22e720@posting.google.com>, andrew.rycroft@intrinsitech.com (Andrew Rycroft) writes: >Hi, > @ >I am using FTP to copy files from one VMS system to another VMS  >system. The exact command is :- >   >$ COPY/FTP/ANON ll.com alpha2:: > G >Both systems are running UCX v5.0a. The files are sequential, variable D >length record files. On doing a $ DIR/FULL the source file shows :- > C >Record format:      Variable length, maximum 255 bytes, longest 61  >bytes >  >The target file shows :-  > B >Record format:      Variable length, maximum 255 bytes, longest 0 >bytes > * >i.e. it has lost the longest record data. > ? >Have tried using COPY/FTP/ANON/FDL, but this displays the same 	 >problem.  > G >Any suggestions on how to preserve the longest record length attribute   >in FTP file copies appreciated. > D >I am using UCX v5.0a, and I have another site with the same problem >using UCX v4.2.  I You could zip your files before and transfer the zip file in binary mode. ? I don't know whether UCX has a "TYPE VMS" option like Multinet.t   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: Mon, 13 Aug 2001 08:22:37 +0200 (MET DST) & From: Rudolf Wingert <win@fom.fgan.de> Subject: Re: FYI6 Message-ID: <200108130622.IAA26120@sinet1.fom.fgan.de>  
 Hello Sue,  K we are all so sorry about your damaged hand and wish that it will be intacti and cure as soon as possible.o   Best regards Rduolf Wingert    ------------------------------  % Date: Mon, 13 Aug 2001 02:51:39 -0000  From: sword7@speakeasy.org) Subject: Re: Help! Boot Block Information / Message-ID: <tneg5r6i7pmqa6@corp.supernews.com>/  3 Robert Deininger <rdeininger@mindspring.com> wrote:sM > In article <tne1bnqgqf2nf6@corp.supernews.com>, sword7@speakeasy.org wrote: - > Alpha or VAX.  I belive they are different.i   I mean VAX architecture.  L >> I have two samples (first three longwords) on my OpenVMS Installation CD H >> and my virtual disk image file.  I displayed them by using 'od -t x4 2 >> /dev/cdrom' and 'od -t x4 vms072.dsk' on Linux. >> t" >> On the OpenVMS Installation CD: >> m >>   0000 - 010C1101 >>   0004 - 194B0002 >>   0008 - 00000000  K > I don't think CDs are ODS-2.  They are ODS-3 or -4, I think, which is whye# > the new VMS file system is ODS-5.m  H Well, I only have ODS-1 and ODS-2 specs. :-(  What is difference betweenB ODS-2 and ODS-5 specifications?  Well, LBN #0 always is boot block regardless of ODS version.  $ >> On the virtual disk (vms072.dsk): >> e >>   0000 - 010C1101 >>   0004 - AFE5000A >>   0008 - 00000000  - > Dunno anything about these virtual disks...n   -- Tim Stark   --  , Timothy Stark	<><	Inet: sword7@speakeasy.orgJ --------------------------------------------------------------------------F "For God so loved the world, that he gave his only begotten Son, that H whosoever believeth in him should not perish, but have everlasting life.. Amen." -- John 3:16 (King James Version Bible)   ------------------------------  % Date: Mon, 13 Aug 2001 12:22:12 -0000a From: sword7@speakeasy.org) Subject: Re: Help! Boot Block Informationo/ Message-ID: <tnfhjk8c1k03d0@corp.supernews.com>t  5 John Laird <john@laird-towers.freeserve.co.uk> wrote:SJ > If you swap the two 16-bit words of the 2nd longword, it will make a lotH > more sense !  There is a good, historic, reason why some longwords are* > arranged like this, left as an exercise.  H > So, if you dump block 2194B of your CD, or block AAFE5 of your virtualJ > disk, you should see the first block of VMB.EXE - it contains some ASCIIJ > strings such as "%BOOT-F-Unable to load boot file due to memory errors".H > Interestingly, my home machine has "<label> is a not a system disk" inE > its bootblock of its most assuredly bootable system disk, but again-H > there is a good reason for this (which I had to correct before I could > confirm your problem).  I > I don't have a copy of the IDS manual to hand to help further with thiseG > (or anywhere near the technical knowledge), but I would recommend youcE > reread that section more carefully to see if it clarifies the point-G > about the VBN.  I would be surprised if it does not (although perhapsnI > there is a general discussion earlier about such things, look for ODS-2pJ > structure refs), but it is the kind of gotcha that will give you lots of > headaches to come.  # > Wishing you luck in your project.s   John:D  G Thank you for information.  Yesterday, I was figured out on the dumped r: first block from CD and vms072.dsk.  I finally understand.  E When I disassembled that and recongized that first longword contains: D "NOP, BRB 000F".  I studied disassembled short program and found outF that 2nd longword is word-swapped LBN number (first block of VMB.EXE).B Also, I found location 20 and 24 too.  Location 20 contains numberF of blocks to be loaded.  Location 24 contains relative offset from theG starting of the good memory to be loaded.  Then jump to (R6).  I had noRE idea where contents of R6 come from.  I believe that it jumped to then( routine to load VMB.EXE into the memory.  G However, I do not have the IDS manual.  Where can I get the IDS manual?6  C Ok, I will implement that into my VAX emulator to boot any devices n3 by using location 0004, 0020, and 0024 effectively.a  
 Thank you!   -- Tim Stark   -- k, Timothy Stark	<><	Inet: sword7@speakeasy.orgJ --------------------------------------------------------------------------F "For God so loved the world, that he gave his only begotten Son, that H whosoever believeth in him should not perish, but have everlasting life.. Amen." -- John 3:16 (King James Version Bible)   ------------------------------  % Date: Mon, 13 Aug 2001 11:42:56 +0100-4 From: John Laird <john@laird-towers.freeserve.co.uk>) Subject: Re: Help! Boot Block Information 8 Message-ID: <f5bfntcna2ovkpvvhc35ehrqr1pkk02a5g@4ax.com>  ? On Sun, 12 Aug 2001 22:38:47 -0000, sword7@speakeasy.org wrote:5  
 >Hello folks:0 >BG >Does anyone know about boot block information (LBN 0 on ODS-2 format)?<H >I was trying out on first three longwords but they does not make sense J >that my VMS Internals and Data Structure handbook explains.  It said thatG >there are three longwords on the boot block information (on page 899).e >eH >    - The size of the bootstrap program to be loaded by the boot block  >      program. > >    - The starting LBN of the bootstrap program to be loaded.A >    - A relative offset into the block of good memory where thisr >      program is to be loaded.- >-J >I have two samples (first three longwords) on my OpenVMS Installation CD F >and my virtual disk image file.  I displayed them by using 'od -t x4 0 >/dev/cdrom' and 'od -t x4 vms074.dsk' on Linux. >n  >On the OpenVMS Installation CD: >  >  0000 - 010C1101 >  0004 - 194B0002 >  0008 - 00000000 >c" >On the virtual disk (vms072.dsk): >  >  0000 - 010C1101 >  0004 - AFE5000A >  0008 - 00000000 >mE >Well, it does not make sense that my handbook explains.  Does anyonenA >know about boot block program to load VMB.EXE into the memory too	 >execute?r  H If you swap the two 16-bit words of the 2nd longword, it will make a lotF more sense !  There is a good, historic, reason why some longwords are( arranged like this, left as an exercise.  F So, if you dump block 2194B of your CD, or block AAFE5 of your virtualH disk, you should see the first block of VMB.EXE - it contains some ASCIIH strings such as "%BOOT-F-Unable to load boot file due to memory errors".F Interestingly, my home machine has "<label> is a not a system disk" inC its bootblock of its most assuredly bootable system disk, but againlF there is a good reason for this (which I had to correct before I could confirm your problem).  G I don't have a copy of the IDS manual to hand to help further with thisrE (or anywhere near the technical knowledge), but I would recommend youtC reread that section more carefully to see if it clarifies the pointdE about the VBN.  I would be surprised if it does not (although perhapsiG there is a general discussion earlier about such things, look for ODS-2eH structure refs), but it is the kind of gotcha that will give you lots of headaches to come.  ! Wishing you luck in your project.      	Johnn -- a
 John Laird Yezerski Roper Ltd   ------------------------------  % Date: Mon, 13 Aug 2001 11:43:11 +0100 ( From: Nic Clews <sendspamhere@127.0.0.1>) Subject: Re: Help! Boot Block Information ) Message-ID: <3B77AF3F.CAA10E40@127.0.0.1>'   sword7@speakeasy.org wrote:   H > Does anyone know about boot block information (LBN 0 on ODS-2 format)?H > I was trying out on first three longwords but they does not make senseK > that my VMS Internals and Data Structure handbook explains.  It said thatvH > there are three longwords on the boot block information (on page 899). > H >     - The size of the bootstrap program to be loaded by the boot block >       program.? >     - The starting LBN of the bootstrap program to be loaded. B >     - A relative offset into the block of good memory where this  >       program is to be loaded. > J > I have two samples (first three longwords) on my OpenVMS Installation CDF > and my virtual disk image file.  I displayed them by using 'od -t x41 > /dev/cdrom' and 'od -t x4 vms074.dsk' on Linux.d  2 Not sure that's the best way to display. See this:  5 $ dump sys$sysdevice:[000000]indexf.sys/block=count=1   > Dump of file SYS$SYSDEVICE:[000000]INDEXF.SYS;1 on 13-AUG-2001 11:20:52.53 ; File ID (1,1,0)   End of file block 18538 / Allocated 18540:  3 Virtual block number 1 (00000001), 512 (0200) bytes3  <  11002211 00000000 FC8D0006 010C1101 ............".. 000000<  00000100 E5020018 00000000 0000001F ............... 000010<  00000257 00000000 00000200 00000057 W...........W... 000020<  B054E2AF D001318F BB6EEEAF C0CDAF9F .n.1.ЯT 000030<  58B5AFD0 BAAF58B0 BCAFC0AF B058C2AF XXЯX 000040<  008FC000 0150E866 1610AEDD 55D1AFD0 ЯUݮ..fP.... 000050<  AFD096AF D66E0000 02008FC0 55000002 ...U.....n֯.Я 000060<  FC00008F CA01318F BA8ED5E2 54F55893 .XT..1.... 000070<  00000000 00000000 9E176EA3 AFC052FF .Rn.......... 000080 [cut]c  B $ dump/head/block=count=0 sys$sysdevice:[vms$common.sysexe]vmb.exe  D Dump of file SYS$SYSDEVICE:[VMS$COMMON.SYSEXE]VMB.EXE on 13-AUG-2001 11:22:06.34               ;1D8 File ID (1748,3,0)   End of file block 87 / Allocated 90  (                              File Header   Header area  [snip snip snip...]    Map area     Retrieval pointers0         Count:         90        LBN:     457869  / Checksum:                                 60768o $  $ lbn=457869 $ sh sym lbn4   LBN = 457869   Hex = 0006FC8D  Octal = 00001576215  B Check out the THIRD longword (L to R) from the dump of INDEXF.SYS,+ here's one I prepared earlier (as above)...   <  11002211 00000000 FC8D0006 010C1101 ............".. 000000  C Note the FC8D0006. In DUMP, as the longwords are presented right to E left, this is the same as 0006FC8D. (check the docs to understand thea
 DUMP format).   B Alpha is slightly different. Work out the hex value of the LBN for9 SYS$SYSDEVICE:[VMS$COMMON.SYSEXE]APB.EXE in the same way.p  E When you DUMP the first block of the INDEXF.SYS, you will notice thateC the hex value of the LBN is in fact stored at the 'back end' of the  first block (last line).  C I guess this allows you to make a disk both Alpha and VAX bootable,  pointing to thev& correct LBN of the APB.EXE or VMB.EXE.  H In SYS$SYSTEM you will see a file called WRITEBOOT.EXE on VAX and Alpha,
 this does theo, job for you, run it and see, but be careful!  E As to size and load location, I'm familiar with a 200 (hex) as in the A dump of the VAX file above, but nothing more. Anyone else want to  illucidate?    -- s( Regards, Nic Clews CSC Computer Sciences nclews at csc dot com    ------------------------------  % Date: Mon, 13 Aug 2001 15:44:20 +0100m4 From: John Laird <john@laird-towers.freeserve.co.uk>) Subject: Re: Help! Boot Block Information 8 Message-ID: <mepfntcklggobjo8col239ghddu9pnj4b7@4ax.com>  F On Mon, 13 Aug 2001 11:43:11 +0100, Nic Clews <sendspamhere@127.0.0.1> wrote:  C >Check out the THIRD longword (L to R) from the dump of INDEXF.SYS, , >here's one I prepared earlier (as above)... > = > 11002211 00000000 FC8D0006 010C1101 ............".. 0000007 >9D >Note the FC8D0006. In DUMP, as the longwords are presented right toF >left, this is the same as 0006FC8D. (check the docs to understand the >DUMP format).   With respect, what rubbish !  F The hex versions are presented R-L, the ASCII L-R, but within each hexH longword, all is as is should be (assuming you worship the little endianF diety) with low bits to the right, high bits to the left, thus lettingB you read across longword (or word or byte if you choose those dumpD options) boundaries perfectly naturally.  Start at the rightmost hexE digit and then keep working left.  No need to swap anything mentally.   H The *second* longword is FC8D0006, not the third as you suggest, but theC reason this is not the expected value of 0006FC8D is because *it ispE defined to be word-swapped on-disk*.  This will almost certainly date H back to pre-Vax days.  Other longword items in ODS-2 format are just theF same - block-counts in file headers come to mind.  For fun, see if theH various non-IEEE floating point layouts make more sense word-swapped too ;-)a  6 Tim may well not have access to a VMS box, by the way.     	John  -- -
 John Laird Yezerski Roper Ltd   ------------------------------    Date: 13 Aug 2001 08:45:56 -0700) From: P.Young@unsw.EDU.AU (Patrick Young)R) Subject: Re: Help! Boot Block InformationD= Message-ID: <55f85d77.0108130745.73db0d58@posting.google.com>   Q sword7@speakeasy.org wrote in message news:<tne1bnqgqf2nf6@corp.supernews.com>...e > Hello folks: > H > Does anyone know about boot block information (LBN 0 on ODS-2 format)?I > I was trying out on first three longwords but they does not make sense hK > that my VMS Internals and Data Structure handbook explains.  It said thatuH > there are three longwords on the boot block information (on page 899). > I >     - The size of the bootstrap program to be loaded by the boot block   >       program.? >     - The starting LBN of the bootstrap program to be loaded.cB >     - A relative offset into the block of good memory where this  >       program is to be loaded. > K > I have two samples (first three longwords) on my OpenVMS Installation CD  G > and my virtual disk image file.  I displayed them by using 'od -t x4 m1 > /dev/cdrom' and 'od -t x4 vms074.dsk' on Linux.a > ! > On the OpenVMS Installation CD:n >  >   0000 - 010C1101. >   0004 - 194B0002  >   0008 - 00000000v >   @ It's a while since I've looked at VAX related boot blocks. AlphaD bootblocks are quite different (the Alpha boot block being simpler).  = You may want to take a look at $BTBDEF in sys$library:lib.req   > macro BTB$B_NOP1 = 0,0,8,0 %;           !  Contains NOP opcode  	   .... 01a  > macro BTB$B_BRB = 1,0,8,0 %;            !  Contains BRB opcode  	   .... 11L  F macro BTB$B_BRB_OFFSET = 2,0,8,0 %;     !  Contains PC relative offset	 of branch   	   .... 0Cy  > macro BTB$B_NOP2 = 3,0,8,0 %;           !  Contains NOP opcode  	   .... 01m  C macro BTB$L_LBN1 = 4,0,32,1 %;          !  Starting LBN of 1st boota file     .... 194B0002C    T? Therefore a dump/pag=save/block=st=%x2194b (+1? I'm not 100% innE concentration mode currently - too late at night) should show you theo contents of VMB.EXE.   ------------------------------  % Date: Mon, 13 Aug 2001 17:52:02 +0200 6 From: "Chris Breemer" <chris_breemer@nl.compuware.com>1 Subject: Re: How to trace memory usage - THANKS !t5 Message-ID: <997717922.792053@c1204.nl.compuware.com>:   Hi all,fK Thanks to everybody who replied. Sounds like GETJPI has all I need and lotsn more.u  	    Cheersa  
         Chris0   ------------------------------  % Date: Mon, 13 Aug 2001 11:36:56 -0400d5 From: "Fred Kleinsorge" <kleinsorge@star.zko.dec.com> A Subject: Re: HWRPB (Alpha) blundering in the dark - info requiredd1 Message-ID: <QuSd7.48$bB1.10675@news.cpqcorp.net>B  > antonio.carlini wrote in message <3B746496.9A5F16B@iee.org>... >  >l >Patrick Young wrote:dC >> download area). Not much use regarding the SRM console though. IV4 >> remember kind of expecting SRM source code when I) >> bought it :-( - only SRM flash images.r >o) >SRM sources were not generally availablee+ >even within Digital. The EBSDK should haveh- >the SR*O*M sources for at least some boards.O >F    J Depends.  If you needed access, it wasn't particularly hard to have it.  IK did.  However, there were at least 3 versions of the SRM console maintainedcH by different groups - servers, workstations, and reference boards.  Most8 people did need - or want - access to the SRM code base.   ------------------------------  # Date: Mon, 13 Aug 2001 16:23:07 GMTs2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)A Subject: Re: HWRPB (Alpha) blundering in the dark - info required-1 Message-ID: <L9Td7.55$bB1.11017@news.cpqcorp.net>   T In article <3B746496.9A5F16B@iee.org>, "antonio.carlini" <arcarlini@iee.org> writes:) :The handbook is available electronicallyt- :(at least, I've just found a copy I stashed m( :away some time ago). I *thought* that I+ :had a copy of the AARM in PDF but I cannot ' :locate it and it might just be wishfuld :thinking on my part :-)     FAQ.    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: 13 Aug 2001 06:45:15 -0700+ From: mend0070@tc.umn.edu (Phil Mendelsohn)rF Subject: Re: I just have to post this - and apoligse later Alpha/Intel= Message-ID: <9fffd0d8.0108130545.130b2bff@posting.google.com>g  U Scott Vieth <svieth@wi.rr.com> wrote in message news:<3B7721D9.4F269F87@wi.rr.com>... 8 > Isn't *every* company is the business of making money?  F Are you in management or something?  :)  Companies are about more thanD buying and selling shares and having board meetings.  And managementE is supposed to be about increasing revenues, not cutting costs.  That'8 means sales, and that means building better mouse traps.  C What new/better moustrap has Compaq ever built?  They've repackaged @ PC's in a multitude of ways, but have never invented anything --= "costs too much, bad for business.  Just use existing stuff."s  B And now they want to dictate that they know better than the market= what the individual consumer wants.  Personally, that sort ofl: "business" doesn't make me feel like I'm in a particularlyD free-market.  Or rational society, either, but that's off topic.  Or+ not, but it's not a rant I'll go into here.i  q > Why should Compaq be singled out and criticized for doing something that every other company is striving to do?-  ? All companies that do similar things should be criticized in myG@ opinion, but Compaq's the only one that is germane to this list.   Phil   > ?????  >  > -Scott >  > Phil Mendelsohn wrote: > t > > mend0070@tc.umn.edu (Phil Mendelsohn) wrote in message news:<9fffd0d8.0108101316.62d9d250@posting.google.com>...J > > > The real issue here, is that Compaq appears to be in the business of2 > > > making rather than that of making computers. > >  > > That should have read: > >rJ > > "Compaq appears to be in the business of making money rather than that > > of making computers."o > >n > > So much for being pithy.   ------------------------------  % Date: Mon, 13 Aug 2001 10:33:34 -0500.+ From: Christopher Smith <csmith@amdocs.com> F Subject: RE: I just have to post this - and apoligse later Alpha/IntelL Message-ID: <3B55D7F383B0D31197D9009027541CBF1170DB1D@cmiexch1.cmi.itds.com>   > -----Original Message-----1 > From: Richard Brodie [mailto:R.Brodie@rl.ac.uk]a  6 > "Rudolf Wingert" <win@fom.fgan.de> wrote in message 2 > news:200108100603.IAA20920@sinet1.fom.fgan.de...  : > > P.S. Alpha to IA 64 (64bit to 64bit) will be never an  > upgrade. It is the? > >      same level, other design. Alpha to Playstation (64bit e > to 128bit) > >      would be an upgrade.a  = > It's hard to tell from here but that was a joke, wasn't it?o  J Who knows.  I'd personally love to see VMS on a Playstation 2. :)  ...or aI Sega Dreamcast. (Note that the latter, AFAIK, isn't fully 128-bit)  Aside E from being very amusing, it would certainly be affordable, and nethersH console has any ties with microshaft to speak of.  (Well, Dreamcast usesB windows ce for its built-in menu system, actually, but that's all)  L That said, I'd prefer Alpha to either of the above, but I'd prefer either of the above to wintel.   Regards,   Chrisd    ! Christopher Smith, Perl Developerr Amdocs - Champaign, IL   /usr/bin/perl -e '? print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n");  'w  -   ------------------------------  % Date: Mon, 13 Aug 2001 11:49:49 -0400 5 From: "Fred Kleinsorge" <kleinsorge@star.zko.dec.com>oF Subject: Re: I just have to post this - and apoligse later Alpha/Intel1 Message-ID: <XGSd7.50$bB1.11004@news.cpqcorp.net>n  A Hamlyn Mootoo wrote in message <3B74BCCC.36612E2C@bigfoot.com>...  >n >o >Sue Skonetski wrote:n >  We have aK >> number of engineers in VMS (around 400) and are hiring some more for the  >> porting project.t >aH >Care to release names of these 400. (I'm guessing most of them wouldn't >mind)?4  B I would bet many of them would.  Nothing like getting bombarded byH headhunters.  Note that "VMS engineering" encompasses more than just the  folks who write the kernel code.  >   Also, this "HIRING".  When Compaq sold those machines in theE >article to the military, was it in exchange for some sort of stealthlG >technology related to hiring?  Or is this another cross application of-F >Compaq's stealth VMS marketing technology?  Hiring? For the VMS port?F >Where????????  I see the recruiters advertising for Linux and True-64 >porting help, but not VMS.c >o    J For what we need, putting an ad into a trade rag would be a waste of time.@ We can and will hire specific people with specific skills (knownB quantities).  We will augment that with limited term employees and- contractors where we need extra general help.k   ------------------------------  % Date: Mon, 13 Aug 2001 12:25:58 -0400s- From: JF Mezei <jfmezei.spamnot@videotron.ca>tF Subject: Re: I just have to post this - and apoligse later Alpha/Intel, Message-ID: <3B77FF94.E8355BF1@videotron.ca>   Christopher Smith wrote:D > Who knows.  I'd personally love to see VMS on a Playstation 2. :)   @ Or Playstation, Sega et all that would have been based on Alpha.   ------------------------------  % Date: Mon, 13 Aug 2001 02:08:07 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca>l* Subject: Re: Lemmings, was Re: Move to Sun, Message-ID: <3B776EBC.1FE56ED2@videotron.ca>   "David J. Dachtera" wrote:C > Until we see Compaq firm up its commitments (by backing them with0G > tangible evidence) and its courses of action, I'm sure you can expect0H > attrition in OpenVMS professionals, sites, ISVs, OEMs and other Compaq" > partners, etc. across the board.  N Yes, but that is because Compaq pre-anounced the murder of Alpha before it wasL time, leaving a void of a few years between the announced death of Alpha and9 first VMS systems capable of running on that IA64 thingy.r  N The lack of public ISV commitments at this point in time may be understandable but it doesn't mean it is good.v  L Once IA64 stops being vapourware for VMS customers, perhaps a better pictureM will emerge. Until then. VMS' future remains in the dark, so speculation frome& customers is perfectly understandable.  K Compaq must have factored this when it made its decision to give the family K jewels to Intel and they must have known that announcing the death of AlphaoI prematurely would result on lost sales etc, but my guess is that the lost L sales represent an amount that Compaq is comfortable with since with all theJ money thye got from Intel, they will be able to replace those profits with> their new strategic endeavours in the solutions/service arena.   ------------------------------    Date: 13 Aug 2001 08:17:30 -05009 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen) * Subject: Re: Lemmings, was Re: Move to Sun3 Message-ID: <mgx7MFNhE+6r@eisner.encompasserve.org>p  [ In article <3B774543.7959D837@fsi.net>, "David J. Dachtera" <djesys.nospam@fsi.net> writes:  > JF Mezei wrote:0 >> : >> mulp wrote:P >> > will be buying IA64 systems to run VMS or Tru64.  For the ISVs that supportN >> > VMS, Tru64, and Windows, VMS will likely be the lowest priority port (VMSK >> > customers buy VMS systems only after things are mature, so there is no N >> > reason to rush to deliver VMS software since customers won't buy it until& >> > its been out for a few years....) >> lM >> That is a good point, and perhaps why we haven't seen much in terms of ISV Q >> commitment to VMS on IA-64 and won't see significant commitments for some timeo >> to come.  >> rO >> I guess that the lack of ISV commitments at this point in time is normal and ! >> we can't draw conclusions yet.  >  > First guess time:  > C > Until we see Compaq firm up its commitments (by backing them withg/ > tangible evidence) and its courses of action,r  0 I don't think ISV management is worried by that.  D But certainly you cannot expect ISVs to make annoucements until they have:h  $ 	A date for availability of IA64 VMS/ 	A date for availability of the tools they need   @ That does _not_ mean that ISVs are pessimistic about delivery of@ these items, but they cannot make firm plans (much less announce$ them) until these items are handled.   ------------------------------  % Date: Mon, 13 Aug 2001 11:57:51 -0400.( From: "Thomas Steuver" <steuver@nku.edu>! Subject: Link with $PRCDEF module / Message-ID: <tnfua6crb88d17@corp.supernews.com>W  J I have a Fortran program with the EXTERNAL PRC$M_DETACH command and I needF to link with the $PRCDEF module in the system macro library.  (See theJ OpenVMS Programming Concepts Manual under 1.5 Creating a Detached Process)H I'm lost as to the proper syntax of the link command.  Can someone help?   Thanks,. Tom Steuver0   ------------------------------  # Date: Mon, 13 Aug 2001 16:54:56 GMTp= From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-) % Subject: Re: Link with $PRCDEF moduleS0 Message-ID: <00A0077F.9E1C0DA7@SendSpamHere.ORG>  Z In article <tnfua6crb88d17@corp.supernews.com>, "Thomas Steuver" <steuver@nku.edu> writes:K >I have a Fortran program with the EXTERNAL PRC$M_DETACH command and I needrG >to link with the $PRCDEF module in the system macro library.  (See thesK >OpenVMS Programming Concepts Manual under 1.5 Creating a Detached Process) I >I'm lost as to the proper syntax of the link command.  Can someone help?o >o >Thanks, >Tom Steuver >f >D  / 	INCLUDE '($PCRDEF)'	! Include PRC$ definitions.  ? might be a whole lot easier and it's always worked well for me.  --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM             0J   "And of course, I'm a genius, so people are naturally drawn to my fiery I   intellect.  Their admiration overwhelms their envy!" -- Calvin & HobbesM   ------------------------------    Date: 13 Aug 2001 00:00:45 -07009 From: lzoedv@cretschmar-logistik.de (M.Eismann&W.Richard)t' Subject: Re: Linker-Warnings in VMS 7.3'= Message-ID: <6d280ea8.0108122300.3fde3200@posting.google.com>o   Hello John!t  [ John Reagan <john.reagan@compaq.com> wrote in message news:<3B741479.4070009@compaq.com>...S Can you post the results of: > < > $ anal/image/select=(link,ident,build) sys$system:link.exe > 0 > so I can verify exactly which linker you have? >  Here it is :P LZOA09:[000000.LZOSRC]> anal/image/select=(link,ident,build) sys$system:link.exe   SYS$COMMON:[SYSEXE]LINK.EXE;1  22-MAR-2001 12:52:30.00s "A12-03" "X913-0060000000"s LZOA09:[000000.LZOSRC]>-     This is amazing too:; The linker seems to find the message in some circumstances:o& %LINK-W-NOMSG, Message number 0064A128& %LINK-W-NOMSG, Message number 0064A130P %LINK-W-ENTIDMTCH, PAS$ENVIRONMENT_TIME ident of 15-APR-1998 18:46:59 for entity  SBR_INTERFACEH         in module NKG_GET file NKG_RUNTIME_DEVICE:[LIB]NKG_LIBRARY.OLB;24         does not match ident of  9-JUL-2001 12:51:514         in module BUCHER file LZO_LINK_LIB_DEVICE:[L3 I 'd never seen this before! Maybe I was blind ....   
 > John ReaganD > Compaq Pascal Project Leader   ------------------------------    Date: 13 Aug 2001 08:20:30 -05009 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen)h' Subject: Re: Linker-Warnings in VMS 7.3 3 Message-ID: <zcHoS4InJbVg@eisner.encompasserve.org>a  x In article <6d280ea8.0108122124.170da1b@posting.google.com>, lzoedv@cretschmar-logistik.de (M.Eismann&W.Richard) writes:] > John Reagan <john.reagan@compaq.com> wrote in message news:<3B73E446.8070205@compaq.com>...fE >> That is the ANAL/OBJ from one of your .OBJ files.  The set of IDC nI >> records shows which environments that it used.  I need to see the IDC 8J >> records from EVERY .OBJ file or module that is seen by the linker.  It = >> is comparing them and perhaps generating the "mismatched" pE >> PAS$ENVIRONMENT_TIME message.  With just the single .OBJ file you OG >> listed, the linker would never generate an IDC mismatch since there f >> aren't "two" of any of them.n > G > EVERY OBJ-File? All our object-files are stored in some obj-librariesaB > (OLB) and AFAIK the number of really all objects is approx. 2000+ > files! Do you really need EVERY obj-file?R  E The traditional approach for this is for you (the customer) to decide-E that you don't really want to burden John with your whole applicationoE and you don't really want to fight your own security department about.J releasing it, so you create a small example that demonstrates the problem.   ------------------------------  % Date: Mon, 13 Aug 2001 10:44:56 -0400l* From: John Reagan <john.reagan@compaq.com>' Subject: Re: Linker-Warnings in VMS 7.3 ) Message-ID: <3B77E7E8.6070203@compaq.com>M   M.Eismann&W.Richard wrote: > G > EVERY OBJ-File? All our object-files are stored in some obj-librarieslB > (OLB) and AFAIK the number of really all objects is approx. 2000+ > files! Do you really need EVERY obj-file?  > C In theory yes.  As the linker processes all the object modules, it oE collects and compares IDC records as it goes along.  If it processes hE 2000 object modules to link the application, I'd need to see the IDC hG records for any of those 2000 object modules (probably not all of them g contain IDC records).e   > D > Is it possible to do analyze/obj for a complete object-library? If@ > yes, i would do it and zip&mail the output to your e-mail-box? >  0H We may want to wait until we get the message file thing resolved first. 4   That will give us the information needed (I hope).     John Reagan  Compaq Pascal Project Leader   ------------------------------  % Date: Mon, 13 Aug 2001 10:52:26 -0400r* From: John Reagan <john.reagan@compaq.com>' Subject: Re: Linker-Warnings in VMS 7.3$) Message-ID: <3B77E9AA.6090001@compaq.com>R   M.Eismann&W.Richard wrote: >  > This is amazing too:= > The linker seems to find the message in some circumstances:y( > %LINK-W-NOMSG, Message number 0064A128( > %LINK-W-NOMSG, Message number 0064A130R > %LINK-W-ENTIDMTCH, PAS$ENVIRONMENT_TIME ident of 15-APR-1998 18:46:59 for entity >  SBR_INTERFACEJ >         in module NKG_GET file NKG_RUNTIME_DEVICE:[LIB]NKG_LIBRARY.OLB;26 >         does not match ident of  9-JUL-2001 12:51:516 >         in module BUCHER file LZO_LINK_LIB_DEVICE:[L5 > I 'd never seen this before! Maybe I was blind ....C >   I That is even stranger.  The code in the linker for printing IDC warnings u essentially looks like:-  # IF size of message is less than 250e THENE     SIGNAL single ENTIDMTCH message that contains all the informationl ELSEL     SIGNAL 4 different messages each containing a portion of the information  F You sure you only got 2 of the NOMSG messages and not 4?  I don't see  how that is possible.d  E Also, I'm a little surprised by the truncated ENTIDMTCH message.  It eH seems that the new code to compute the length doesn't work all the time 2 either.  Guy will have to track this down as well.   John Reaganu Compaq Pascal Project Leader   ------------------------------  % Date: Mon, 13 Aug 2001 08:32:44 -0400e5 From: David Beatty <David.Beatty@qwertysasasdfgh.com>R! Subject: Re: Mike Capellas' Diaryw2 Message-ID: <3ch3O93kFQ1OK2Avhw4mRMotJI3X@4ax.com>  % Why, yes it is!  ;-)  David R. Beattye  . On Mon, 13 Aug 2001 12:13:19 +0100, Alan Greig" <alan.greig@intl.fmcti.com> wrote:  ( >http://www.theinquirer.net/10080105.htm >e >This is actually quite funny.   ------------------------------  # Date: Mon, 13 Aug 2001 16:22:01 GMTd2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)" Subject: Re: Missing TK50 in uVAX?1 Message-ID: <J8Td7.54$bB1.10967@news.cpqcorp.net>0  \ In article <m37kwbinlp.fsf@muikku.baana.suomi.net>, costello@iki.fi (Antti Jrvinen) writes:  6   Fifteen year old iron is going to be entertaining...  5 :hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) writes:6 :> : ? TPC      0000.4001.Q :> :      FFFFFF05 FFFFFF05 FFFFFF05 FFFFFF05 FFFFFF05 FFFFFF05 FFFFFF05 FFFFFF03( :> aF :>   That's the tape controller, and the diagnostics didn't like it... :h. :No. It has MicroVMS 4.something installed,...     So?t  K   If the console doesn't like "it", then the operating system probably also-   won't like "it".    G   You must get the console self-tests to work first, then you can (and  H   probably should) try to load (more recent) OpenVMS VAX and try to use    the system.   C   Most VAX and Alpha systems learn about the configuration from theaJ   console -- and on more recent systems, this design becomes more central,I   as OpenVMS learns more (or all) about the system and I/O configuration PI   from the console.   OpenVMS Galaxy is centrally dependent on the systemrH   configuration information that is provided to each instance by the SRM
   console.  K :"show dev" didn't show anything resembling a tape so the about only thing  A :I could do was trying to change controller address, no success. o  K   MicroVAX 2000 and VAXstation 2000 systems do not themselves particularly lL   have I/O controller addresses.  Messing with addresses on the almost-SCSI J   bus on the MicroVAX 2000 will get you in trouble -- it's not SCSI, it's K   "almost-SCSI".  With the almost-SCSI, peripheral devices are expected to iM   be at known addresses, and SCSI devices are not particularly known to work.a  % "I also tried hooking that tape drivenF :to a NCR scsi card sitting in linux-box but it didn't find anything: H :is the tape dead or is the bus really a non-scsi-bus and a scsi-adapter) :really is supposed not to find anything?k  '   The MicroVAX 2000 does not have SCSI.m  K   If the device is the SCSI variant of the TK, then you have a dead device oK   or a bad Linux software or hardware configuration.  If the device is the iL   almost-SCSI variant, then Linux and a SCSI connection may or may not work 
   with it.   :> :   SYS      0000.0001c :> :?? NI       0000.7004  V1.2m :>  
 :>   Network.a :sF :Yes, if I remove ethernet cable, it doesn't boot right away but gives4 :me the >>> -prompt .. how to disable autoboot, btw?  D   IIRC, the relevent commands (specific to the MicroVAX 2000 and the   VAXstation 2000 series) are:       TEST 51C       TEST 52o       TEST 53n  F   The former sets the default boot device (blank is sniffer, specifiedG   device otherwise), the middle sets the R5 (VMB) value (see the FAQ), kI   and the latter sets the power-up behaviour code.  Codes: 1 is restart, o   2 is reboot, 3 is halt.-  ?   EK-ZNAGG-GZ is the VAXstation 2000 Hardware Information docs.m  < :>   You must have the TK50Z-F*, and not the TK50Z-G* drive. :>  ; :>   The TK50Z-F* (usually -FA) must be at bus address one.D :8" :TK50Z-F3 says label in the back.  :1/ :>   You do not have a SCSI bus on this system.  :m" :So TK50Z-F3 is not a SCSI device?  F   The bus is almost-SCSI, not SCSI.  The TK50Z-F* has the ROM code forC   the MicroVAX 2000 and VAXstation 2000 series almost-SCSI adapter.6  E   There have been various previous discussions of the almost-SCSI bus 8   found on the VAXstation 2000 and MicroVAX 2000 series.    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: Mon, 13 Aug 2001 11:04:58 GMTc' From: Colin Blake <colin@theblakes.com>u6 Subject: Re: Mozilla M0.9.3, August 3rd release; Java?, Message-ID: <3B77B406.F7466BA@theblakes.com>  8 "Patrick MOREAU, CENA Athis, Tel: 01.69.57.64.40" wrote:  J > And I noticed the same problem with 0.9.3 than with 0.9.2 : inability to5 > display background images (no problems with 0.9.1)." >\M > Have you noticed the problem ? I've tried some incantations into preference1 > files but without success.   Its a bug. Its being worked.1 http://bugzilla.mozilla.org/show_bug.cgi?id=94431n   ------------------------------  % Date: Mon, 13 Aug 2001 01:03:51 -0500n/ From: Chris Scheers <chris@applied-synergy.com>3 Subject: Re: OpenVMS  + Itanium 3 Message-ID: <3B776DC7.63FC72FE@applied-synergy.com>g   Fred Kleinsorge wrote: > H > Snapshot, or fastboot, was IIRC something that was mostly aimed at theM > desktop/workstation.  The main problem with it (aside from few people usingeF > it) was that I don't believe it worked for clusters, only standalone
 > systems.  2 Actually, I used it for device driver development.  G With snapshot and FBOOT=1 in the machine's config, A VAXstation 4000-60e@ took 45 seconds to go from power on to logged in and productive.  G -----------------------------------------------------------------------c$ Chris Scheers, Applied Synergy, Inc.  C Voice: 817-237-3360            Internet: chris@applied-synergy.com     Fax: 817-237-3074a   ------------------------------  % Date: Mon, 13 Aug 2001 12:18:24 -0400 5 From: "Fred Kleinsorge" <kleinsorge@star.zko.dec.com> ; Subject: Re: OpenVMS apps and Compaq committment story herec1 Message-ID: <I5Td7.53$bB1.10645@news.cpqcorp.net>h  = Arne Vajhj wrote in message <3B754B0A.6AE29E93@gtech.com>...r >Larry Kilgallen wrote:-5 >> I am not convinced that any decisionmakers either:5 >> >>         a. read comp.os.vms	 >>    or:e( >>         b. are upset about Alpha-IA64 >t: >I doubt many real decision-makers read comp.os.vms - they# >get their info from other sources.  >t= >I am pretty sure, that 50% of decision-makers has read abouty6 >the Alpha to IA-64 switch and has ordered the company& >immediatetly to stop buying Alpha's ! >-    K So what is your source of information for this 50% number?  Or is that youre guess?   ------------------------------  % Date: Mon, 13 Aug 2001 19:13:47 +02003= From: Arne =?iso-8859-1?Q?Vajh=F8j?= <arne.vajhoej@gtech.com> ; Subject: Re: OpenVMS apps and Compaq committment story herew) Message-ID: <3B780ACB.7BDD63FA@gtech.com>o   Fred Kleinsorge wrote:? > Arne Vajhj wrote in message <3B754B0A.6AE29E93@gtech.com>... ? > >I am pretty sure, that 50% of decision-makers has read aboutt8 > >the Alpha to IA-64 switch and has ordered the company( > >immediatetly to stop buying Alpha's ! > >  > M > So what is your source of information for this 50% number?  Or is that yourh > guess?  # Sorry if I was not specific enough.m  D It is my estimate based on comments in this forum and in other fora.  & It is not based on a marketing survey.   Arne   ------------------------------  % Date: Mon, 13 Aug 2001 15:50:57 +0100u4 From: John Laird <john@laird-towers.freeserve.co.uk>7 Subject: Re: Pseudo Terminals to emulate LAT Terminals?e8 Message-ID: <g1qfnt8q3t8hbhvglhrjipak66d564icp8@4ax.com>  E On 12 Aug 2001 10:57:48 -0700, JanWermusch@hotmail.com (Jan Wermusch)  wrote:  G >Did I get it right: if the software uses the LAT-specific calls, theree# >is no way to simulate the devices?o   Not easily !  @ You could look at WRQ's Reflection package - quite reasonable VTB emulation and it *can talk LAT*, so your users will create LTAnnnnE devices when they log in, just as they would on the terminal servers.0H However, the terminal server and port information for each terminal port will be "fake".L  F Do you know why this application is making LAT-specific calls at all ?G Is it doing something clever like transferring whole user sessions fromdD one port to another (which would probably need true pseudo-terminals$ anyway such as VTA or FTA devices) ?     	Johnr -- 4
 John Laird Yezerski Roper Ltd   ------------------------------  % Date: Mon, 13 Aug 2001 11:41:29 -0500S  From: norm.raphael@jamesbury.com9 Subject: Re: Slow time and bad memory - are they related?o4 Message-ID: <C2256AA7.005B7214.00@jklh21.valmet.com>   Thanks, Bob (I think),  A "anything's possible" is not the definative answer I was seeking.w   -Norme        ; koehler@bessta.gsfc.nasa.aspm.gov on 08/10/2001 04:08:41 PM'  3 Please respond to koehler@bessta.gsfc.nasa.aspm.gove   To:   Info-VAX@mvb.saic.coma cc: : Subject:  Re: Slow time and bad memory - are they related?          O In article <C2256AA4.00620114.00@jklh21.valmet.com>, norm.raphael@jamesbury.comt writes:e > > >Is it possible that the bad memory caused the time situation? >i  F Depends on the failure mode and model of VAX.  If it was causing noise& on the system bus anything's possible.  F ----------------------------------------------------------------------? Bob Koehler                     | Computer Sciences Corporationa= GSFC Code 582 Flight Software   | Federal Sector, Civil Group I                                 | please remove any ".aspm" when replyingd   ------------------------------  % Date: Mon, 13 Aug 2001 15:18:42 +01000% From: Alan Greig <a.greig@virgin.net>k( Subject: Still no RDB (was Re: Lemmings)8 Message-ID: <t4ofnto25piiqntrpg3bj0gge19un5lnkb@4ax.com>  @ On 13 Aug 2001 08:17:30 -0500, Kilgallen@eisner.decus.org.nospam (Larry Kilgallen) wrote:     >lA >That does _not_ mean that ISVs are pessimistic about delivery ofpA >these items, but they cannot make firm plans (much less announcee% >them) until these items are handled.n  ? Yet Oracle announced that they would support Oracle products on-A Tru64/IA64 on day one. Currently they answer "No decision yet" onaD questions regarding support of any Oracle product, including RDB and DBMS, on VMS/IA64.     -- Alan   ------------------------------  % Date: Mon, 13 Aug 2001 12:22:44 -0400o- From: JF Mezei <jfmezei.spamnot@videotron.ca> + Subject: Re: Storageworks retirement letterR, Message-ID: <3B77FED3.EEF53EE6@videotron.ca>   Alan Greig wrote: F > As a result of this retirement, Compaq SOFTWARE Services (ie licenseB > subscription, software update distribution services and softwareG > telephone support) will no longer be available for the above items aseE > of 30th Jan 2002. Note hardware maintenance continues for the aboveh > items.    I Shouldn't Compaq first have announced thatthe software was to be declaredtD mature, but continuing software and hardware support with only minorL fixes/patches to be made available if need be ? Announce a migration path asL was announced and then a year or two later, if migration has gone well, then. you announce widthdrawal of software support ?  L The way I see this, this "180 day transformation" is forcing that department@ to streamline its product line ASAP even at the cost of Compaq's1 credibility/trustability in the enterprise field.n   ------------------------------  % Date: Mon, 13 Aug 2001 12:04:53 -050041 From: "Dave Gudewicz" <david.gudewicz@abbott.com>:+ Subject: Re: Storageworks retirement letter)8 Message-ID: <9l91lh$j7f$1@fizban.fizban.pprd.abbott.com>  L Interesting to note that the HSZ80, while not on the retirement list, is not on the migration list.   Dave...e  9 "Alan Greig" <alan.greig@intl.fmcti.com> wrote in message 2 news:8iffnt8178nrckh0p20hc18b8u9rg52ntl@4ax.com... > F > I've scanned in the letter from Compaq and OCRd it. Here is the textE > of the letter. I can email a physical scanned image if anyone needsM > one. >e > ====== >L > Compaq Computer LimitedN > Worton Grange Imperial Way > Reading Berkshire RG2 OTET >A >  > Telephone 0118 986 8711i > Fax 01189867969C > www.compaq.co.uk >2 >  >  >o >n > ALAN GREIG > .... > Address ommitted > .... >d > 21st June 2001 >I! > Dear Software Service Customer,h >bF > Compaq Computer Limited, Customer Services UK and Ireland, wishes to< > inform you that we have begun a retirement process for theE > distribution and services for the software of the following storagel > hardware items:L >eG > HS1CP, HSD3O, HSD5O, HSJ3O, HSJ4O, HSJ5O, HSZ4O, HSZ5O, HSZ7O, RA41O,gF > AA450, RA3000 wfth HSZ22 (for NT/Alpha, Novell Netware, Sun Solaris, > HP-UX, IBM-AIX)i >eF > As a result of this retirement, Compaq SOFTWARE Services (ie licenseB > subscription, software update distribution services and softwareG > telephone support) will no longer be available for the above items asoE > of 30th Jan 2002. Note hardware maintenance continues for the aboves > items. >OH > In addition software services for the RA3000 with HSZ22 (for NT/Intel,G > VMS/Alpha, Unix/Alpha) will end on 31st July 2003. Again the hardware. > maintenance will continue. >yG > A migration path is offered with 50% off the storage controller priceeH > (le HSG8O and HSJ8Os). We can also offer leasing options for those whoB > would prefer to lease the new storage controllers and associated > equipment. >lD > The suggested migration paths for those who wish to upgrade are as
 > follows: >o > HSDxx migrate to HSG8O! > HSJxx migrate to HSG8O or HSJ8Oh > HSZxx migrate to HSG8O" > HS1 CP migrate to HSG8O or HSJ8O! > RA41O migrate to HSG8O or HSJ8Oo! > RA450 migrate to HSG8O or HSJ8O $ > RA3000 with HSZ22 migrate to HSG8O >l4 > The options currently available are the following:@ > i) Continue with your current storage hardware and continue to0 > receive hardware maintenance support services.D > ii) Migrate to the relevant HSx8O option and related storage under > a leasing arrangement.B > iii) Migrate to the relevant HSx8O option as a straight purchase > arrangement. >lF > For further information on migration and leasing options please callG > our Glasgow call centre on 0845 270 4114 quoting campaign code 01 SMLn >  > Yours faithfully,e >m >l >  >o > Trish Sandys > Compaq Computer Ltdi > Compaq Customer Services1 > Registered Office: Hotharn House 1 Heron SquareI< > Richmond Surrey TW9 IEJRegistered n England number 1792087 >d >s > -- > Alan   ------------------------------    Date: 13 Aug 2001 09:50:17 -00004 From: Doc.Cypher <Use-Author-Address-Header@[127.1]>- Subject: Re: Terry Shannon Tech Talk on Tru64m5 Message-ID: <20010813095017.1178.qmail@nym.alias.net>s  " -----BEGIN PGP SIGNED MESSAGE-----  = On Sun, 12 Aug 2001, "Bill Todd" <billtodd@foo.mv.com> wrote: 9 >"Doc.Cypher" <doc_cypher@nym.alias.net> wrote in message-1 >news:20010812081105.25855.qmail@nym.alias.net...m >o >... > @ >> Now Jr, please refrain from personal attacks in your posting. >eJ >While I agree that anonymous posts raise doubts about the poster, I don'tJ >agree that characterizing Terry as a Compaq 'lackey' constitutes personalM >abuse:  rather, it's properly descriptive of his stance since June 25th (andnJ >to some degree for at least 6 months before that).  An examination of hisH >posts and his newsletter (at least the issues I've seen recently) wouldM >leave an otherwise uninformed individual with the impression that Compaq had9L >at most to dot a few 'i's and cross a few 't's to make its 'bold' AlphacideG >a textbook example of business foresight and acumen, opposed only by asL >handful of malcontents.  'Balance' in coverage of this issue is clearly not >in his repertoire.f  K As one of the "malcontents", I too cannot understand the steps which CompaqaJ have taken. Given their past record, I have zero trust in their ability toF manage an asset like VMS. Considering this, I - and doubtless others -K would dearly love to know what the payload of this "NDA virus" is. If it istF another one of these stupid roadmaps, I'm sorry, they don't carry much weight around here.e  7 For those reasons, I agree with Bill Todd's assessment.t  L >Why this is the case I don't know.  He's appeared to enjoy hob-nobbing withK >Compaq mucky-mucks in the past, voiced interest in a marketing position ataG >Compaq at least a couple of times, and of course depends upon internalsL >contacts for material for his newsletter - all of which would be ill-servedL >by being too critical of the corporation and *might* be promoted by bendingL >over backwards in the opposite direction.  Or he could legitimately believeF >what I suspect several other Compaq apologists believe:  that adverseE >reactions to an almost certainly irreversible decision can only hurtaM >whatever viability VMS still has, and that therefore the only sensible thing.% >to do is try to make the best of it.<  J However, without the above assessment, calling Terry Shannon a "lackey" isI simply resorting to name calling. Done without a justification I considere) the name calling to be a personal attack.   G >I part company with these people at the point where they seem eager toFL >proselytize others in the hope that sheer numbers will save VMS.  Trying toJ >minimize the perception of risk (and there's unquestionably a significantM >risk in committing to VMS at this point for any activity that requires it tosM >be kept technically-current and competitive with actively-developing systemseI >over time) in the hope that others will (unknowingly) shoulder it and ineI >doing so help reduce your *own* risk is not a nice thing to do:  I doubtaL >that this is the conscious intent of some of these people, but that doesn't >change its effect.i >b >- billr  J My own opinion is, that it is all too easy to believe that Compaq does notG care about VMS. I believe that promoting their own operating systems intJ publications such as Terry's is merely preaching to the converted. This isK essential, and I view such as basic marketing. That Terry has supported his B writing here is all that I would expect, and if it has damaged his' reputation in some quarters - so be it.   B However, there is a need to promote VMS in the mainstream media ifK companies are to retain their faith or be converted. I do not see this, nornK do I see the investment in education that will build a sustainable level of-I support for the operating system. No information given to me under an NDA G is going to change that, Compaq must convince me by actions. After all, 2 their word has been proven to carry little weight.     Doc. - -- n6 The bigger the humbug, the better people will like it.K ~ Phineas Taylor Barnum.                              http://vmsbox.cjb.nete   -----BEGIN PGP SIGNATURE-----  Version: 2.6.2  @ iQEVAwUBO3cKcsriC3SGiziTAQEeoggAsOQaQp/x8RmsW+vTp9uHZxe8bk/VgVUH@ NTmJqobNo3HaTUo1KlTMp+E3buMmv2aIEYhYPdLWTgTq8YaaGYpoE/EKKzKZsjjX@ IUnETSksiihVuxUWzf7tS5iP8/h45biaJx3KQ2aWneKMjrroOGHvYTObyNNhtR6t@ T64StpIchGy22QV9oPpzoyu7xl9ILHVgWeskrPf8UHnEeLvcCPxh6Z1wVVD0HfHs@ m0my2KzCTSo4vqhepIgxJ2Xm8Lt6vDcmKpH/O8WFDsMLqwVcmviN8LCV/BDUZ8C68 8hPTVnZqRmRU10X2SbIkzr8cL2yEL8QgW9YxPFQ+R6ZMwqRt9g3Img== =K7v+e -----END PGP SIGNATURE-----s   ------------------------------  % Date: Mon, 13 Aug 2001 10:34:11 +0100e, From: Alan Greig <alan.greig@intl.fmcti.com>J Subject: Re: The Alpha Systems Customer Update will no longer be published8 Message-ID: <9f7fntckl0kf8kqbslr34q07f4idep1egd@4ax.com>  2 On Sat, 11 Aug 2001 12:36:30 +0200, Didier Morandi <Didier.Morandi@gmx.ch> wrote:    M >The Alpha Systems Customer Update will no longer be published.  We encourager  C That's highly re-assuring. Just the sort of thing customers need to0C hear right now. Yeh, honestly we'll continue updating Alpha for thenB next few years but we can't even be bothered to keep the customers@ informed. Couldn't they at least have waited until EV7 came out?  ? Compaq want rid of the Alpha embarrassment as fast as possible.3     -- Alan   ------------------------------  % Date: Mon, 13 Aug 2001 11:15:22 -0400o2 From: rdeininger@mindspring.com (Robert Deininger)J Subject: Re: The Alpha Systems Customer Update will no longer be publishedL Message-ID: <rdeininger-1308011115240001@user-2iveah6.dialup.mindspring.com>  C In article <9f7fntckl0kf8kqbslr34q07f4idep1egd@4ax.com>, Alan Greig-" <alan.greig@intl.fmcti.com> wrote:  4 > On Sat, 11 Aug 2001 12:36:30 +0200, Didier Morandi  > <Didier.Morandi@gmx.ch> wrote: >  > O > >The Alpha Systems Customer Update will no longer be published.  We encouragei > E > That's highly re-assuring. Just the sort of thing customers need toaE > hear right now. Yeh, honestly we'll continue updating Alpha for thecD > next few years but we can't even be bothered to keep the customersB > informed. Couldn't they at least have waited until EV7 came out? > A > Compaq want rid of the Alpha embarrassment as fast as possible..   Nice out-of-context job, Alan.  H He was announcing a new venue for this information, if you had read (and" quoted) a bit more of his message.  G A less diabolical interpretation is that Compaq is trying to cut costs,sJ including printing and mailing costs, perhaps to avoid laying off quite so many people.   -- - Robert Deininger rdeininger@mindspring.com    ------------------------------  % Date: Mon, 13 Aug 2001 16:46:30 +0100t% From: Alan Greig <a.greig@virgin.net>aJ Subject: Re: The Alpha Systems Customer Update will no longer be published8 Message-ID: <tksfntg642ujcsf15bd5e84it7g8vj573a@4ax.com>  E On Mon, 13 Aug 2001 11:15:22 -0400, rdeininger@mindspring.com (Robert  Deininger) wrote:t     >e >Nice out-of-context job, Alan.n >oI >He was announcing a new venue for this information, if you had read (andh# >quoted) a bit more of his message.s  F I did read it and these are not new venues. I am already subscribed toE OpenVMS Times. Perhaps if Compaq listened to its customers instead of-D just assuming most of the posters are a bunch of nutters with no say' over purchasing we might get somewhere.r  A On the plus side I received my first unsolicited call from Compaq-: today regarding the migration so that's something I guess. >eH >A less diabolical interpretation is that Compaq is trying to cut costs,K >including printing and mailing costs, perhaps to avoid laying off quite sop
 >many people.V  D When figuring out what DEC then Compaq will do next over the last 20E years or so I have found that the 'diabolical' interpretation is very F often correct.  I have just booted my first TOPS20 system in well over@ a decade (under Bob Supnik's KS10 emulator) and that brings back	 memories.   8       Simh Alan's TOPS20 V4.1, TOPS-20 Monitor 4.1(5471)      @      @LOGIN CCD-ARGh)       Job 4 on TTY46 13-Aug-2001 16:27:15a
      @SYS ALLt*       Mon 13-Aug-2001 16:27:25  Up 0:07:50-       1+3 Jobs   Load av   0.02   0.02   0.01m  F       Job  CJB Line Program State  Time     Limit    User, <Directory><         4*   3   46  SYSTAT  RUN   0:00:00           CCD-ARG  =         1        42  PTYCON  TI    0:00:03           OPERATOR:=         2    0   44  BATCON  RUN   0:00:00           OPERATORD=         3    1   45  PTYCON  TI    0:00:01           OPERATORr      @  A I just hope I'm not booting VMS under emulators only in ten yearss time.a -- Alan   ------------------------------  # Date: Mon, 13 Aug 2001 16:25:23 GMTr2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)J Subject: Re: The Alpha Systems Customer Update will no longer be published1 Message-ID: <TbTd7.56$bB1.11055@news.cpqcorp.net>s  o In article <ZpZt6YuGTvmC@eisner.encompasserve.org>, Kilgallen@eisner.decus.org.nospam (Larry Kilgallen) writes:r  3 :There is no supported PDF reader shipped with VMS.-  I   True.  That said, two functional PDF viewers are available, and one of rL   the two -- an easily-installed kit -- ships with OpenVMS via the Freeware.  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: Mon, 13 Aug 2001 09:03:47 -0500e1 From: Robert Alan Byer <byer@mail.ourservers.net>u/ Subject: Re: The VMS Opensource Porting Projecta3 Message-ID: <3B7797F3.54456451@mail.ourservers.net>   E I think the GNU GCL LISP system would be great.  When I asked about aiE LISP system a few months back I got a TON of replies from people thatu, also were wanting a LISP system for OpenVMS.  H I started a port, but ran into a few problems and stopped and I would beB happy to forward what I have to whoever to help progress it along.   -- -  @  +------------------+--------------------------+---------------+@  | Robert Alan Byer | byer@mail.ourservers.net | ICQ #65926579 |@  +------------------+--------------------------+---------------+@  | Send an E-mail request to obtain a copy of my PGP key.      |@  +-------------------------------------------------------------+@  | "It is by caffeine alone I set my mind in motion.  It is by |@  |  cans of cola the thoughts aquire speed, the hands aquire   |@  |  shakes, the shakes become a warning.  It is by caffeine    |@  |  alone I set my mind in motion."                            |@  +-------------------------------------------------------------+   ------------------------------   Date: 13 AUG 2001 15:28:01 GMT+ From: Dave Greenwood <greenwoodde@ornl.gov>n* Subject: Re: VAX/ALPHA FORTRAN and me! :-)2 Message-ID: <13AUG01.15280115@feda01.fed.ornl.gov>  = In a previous article, Paul Lentz <plentz@airmail.net> wrote:r [snip]J > I've tried FORTRAN/EXTEND/ALIGN and managed to get it to compile, but itG > blows up when I try to run it, and even got linker errors a couple ofy > times.  I I don't believe you've posted the messages you get when you don't include C /ALIGN but they are almost certainly *informational*, as opposed toiD indicating errors.  As others have said, the penalty for non-aligned access is performance.  L What I want to emphasize is that /ALIGN will affect the layout of your data,H possibly adversely.  Without the /ALIGN qualifier, your COMMON areas areF packed (like on VAX) but records in data structures are not (unlike onB VAX).  Specifying /ALIGN puts COMMON data on "natural" boundaries,G thereby eliminating non-aligned data messages - but changing the layoutc9 of your COMMONs compared to the way they were on the VAX.r  H You MUST examine the use of your COMMON areas and data structures to see% whether /ALIGN is appropriate or not.0  D Btw, you can eliminate the informational alignment messages (without9 actually changing alignments) by using /WARN=NOALIGNMENT.F   > BETH20::HYPERMAN!> link 6 > ctif_create_daily_fraud_axp,sys$library:SQL$USER/LIB' > %LINK-W-NUDFSYMS, 1 undefined symbol:s# > %LINK-I-UDFSYM,         GET_ARGS n8 > %LINK-I-UDFSYM,         VMH$FIXEDQ_UR (Weak Reference)8 > %LINK-I-UDFSYM,         VMH$FIXEDQ_UW (Weak Reference)? > %LINK-I-UDFSYM,         VMHDEB$TRACE_FREE_VM (Weak Reference) C > %LINK-I-UDFSYM,         VMHDEB$TRACE_FREE_VMLIST (Weak Reference)c> > %LINK-I-UDFSYM,         VMHDEB$TRACE_GET_VM (Weak Reference)? > %LINK-I-UDFSYM,         VMHDEB$TRACE_RET_VMH (Weak Reference)o8 > %LINK-W-USEUNDEF, undefined symbol GET_ARGS referenced+ >         in psect $LINK$ offset %X000001B0 0 >         in module CTIF_CREATE_DAILY_FRAUD file# > BILL00:[CTIF.SRC]CTIF_CREATE_DAILn > Y_FRAUD_AXP.OBJ;4g [snip] > Here's the code at 2767... >    >  AJ >            2767         STAT = GET_ARGS (ARGS, MAX_ARGS, NUM_ARGS)      8 >            2768         IF (STAT .NE. SS$_NORMAL) THENC >            2769             PRINT *, MODULE,'Error encountered ino > GET_ARGS func`A >            2770             PRINT *, ' Fortran status = ', STATb( >            2771             GO TO 8000> >            2772         ELSEIF (NUM_ARGS .NE. MAX_ARGS) THENF >            2773             PRINT *, MODULE,' Wrong # of arguments.'( >            2774             GO TO 8000 >            2775         ENDIF. >   H I'm inclined agree with the others who said that GET_ARGS is most likelyF a Macro program to check the number of arguments on the calling stack.F The (VMS-only) intrinsic routine IARGCOUNT() will return the number ofD arguments passed to a subroutine.  I'd guess that the ARGS parameterE in the call above returns an array of flags indicating whether or notLF specific parameters were passed.  On alpha you can use %LOC(parameter)C to determine whether that parameter was passed.  As an alternative,s( look at the IARGPTR() intrinsic routine.  D Another reasonable interpretation of the above code is that GET_ARGSE parses part of a command line.  In that case you'll need to find youre source for the routine.D  = I have no idea what the VMH$xxxx and VMHDEB$xxxx symbols are.A   Dave --------------9 Dave Greenwood                Email: Greenwoodde@ORNL.GOVXH Oak Ridge National Lab        %STD-W-DISCLAIMER, I only speak for myself   ------------------------------  % Date: Mon, 13 Aug 2001 01:08:37 -0700 % From: GreyCloud <wholland@tscnet.com>a, Subject: Re: VIRUSES: What about antibodies?O Message-ID: <7458728B1999C01A.5BFBE23F5F7AA6A0.F507A71E10C262B9@lp.airnews.net>t   Didier Morandi wrote:    > GreyCloud wrote: > >N > > Didier Morandi wrote:/ > >)? > > > http://www.internetwebfactory.com/antibodies-00-index.htmi > >nJ > > Nope!  Not a good idea, considering it was done before... and the good5 > > ol' FBI raked the poor fellow over the coals too!a >g/ > You can tell us more on this? I'm interested.h >e > D.  L The concept of using a friendly agressive virus to counter-attack a virus is" still a virus in the DOJs' eyes...K hence its against the law even tho it would benefit.  This particular topic80 I saw in the mosh pit of comp.os.linux.advocacy.   ------------------------------  % Date: Mon, 13 Aug 2001 19:35:31 +0010O% From: paddy.o'brien@zzz.tg.nsw.gov.au , Subject: Re: VIRUSES: What about antibodies?5 Message-ID: <01K73HV9N3DU003VY5@tgmail.tg.nsw.gov.au>t  
 Greycloud:  K >The concept of using a friendly agressive virus to counter-attack a virus t is# >still a virus in the DOJs' eyes...dL >hence its against the law even tho it would benefit.  This particular topic1 >I saw in the mosh pit of comp.os.linux.advocacy.    OT, but ...n    L I haven't tried to track the thread(s) that you refer to, but this does not  make sense.1  C How can a virus be friendly?  Isn't "friendly aggressive" mutually  
 exclusive?  L I thought the antidote to a virus was a vaccine.  Is the DoJ bogging itself L down again with its (seemingly) total lack of IT knowledge such that it can E make no real-world IT decisions - just decisions that complicate for   compliance the IT world?   Regards, Paddy   ------------------------------  + Date: Mon, 13 Aug 2001 10:44:18 +0000 (UTC)k' From: david20@alpha2.mdx.ac.uk (D.Webb)1, Subject: Re: VIRUSES: What about antibodies?+ Message-ID: <9l8b22$g8m$1@aquila.mdx.ac.uk>l  w In article <7458728B1999C01A.5BFBE23F5F7AA6A0.F507A71E10C262B9@lp.airnews.net>, GreyCloud <wholland@tscnet.com> writes:5 >a >n >Didier Morandi wrote: >  >> GreyCloud wrote:  >> > >> > Didier Morandi wrote: >> >@ >> > > http://www.internetwebfactory.com/antibodies-00-index.htm >> >K >> > Nope!  Not a good idea, considering it was done before... and the goodu6 >> > ol' FBI raked the poor fellow over the coals too! >>0 >> You can tell us more on this? I'm interested. >> >> D.t >mM >The concept of using a friendly agressive virus to counter-attack a virus is # >still a virus in the DOJs' eyes... L >hence its against the law even tho it would benefit.  This particular topic1 >I saw in the mosh pit of comp.os.linux.advocacy.o >k >t  : This has been done a couple of times in the recent past :-  ? 1) Max Butler released a worm which fixed a BIND vulnerability  @    and got 18 Months - see http://www.securityfocus.com/news/221   ando  F 2) Cheese worm - see http://news.cnet.com/news/0-1003-200-5949401.html    
 David Webb VMS and Unix team leader CCSS Middlesex University   ------------------------------  % Date: Mon, 13 Aug 2001 19:12:52 +0200o, From: Didier Morandi <Didier.Morandi@gmx.ch>, Subject: Re: VIRUSES: What about antibodies?& Message-ID: <3B780A95.8A516602@gmx.ch>   "D.Webb" wrote:g > @ > 1) Max Butler released a worm which fixed a BIND vulnerabilityB >    and got 18 Months - see http://www.securityfocus.com/news/221  = "Less altruistically, Butler's program created a back door one7 every system it penetrated, which the hacker could have  used to gain access later".d  G The trout, all the trout and only the trout, would a Pakistan friend ofw	 mine say.-   D.   ------------------------------  % Date: Mon, 13 Aug 2001 19:14:29 +0200i, From: Didier Morandi <Didier.Morandi@gmx.ch>, Subject: Re: VIRUSES: What about antibodies?& Message-ID: <3B780AF6.F5ADA654@gmx.ch>  & paddy.o'brien@zzz.tg.nsw.gov.au wrote: > M > I thought the antidote to a virus was a vaccine.  Is the DoJ bogging itselfaM > down again with its (seemingly) total lack of IT knowledge such that it canoF > make no real-world IT decisions - just decisions that complicate for > compliance the IT world?  H As all of us know, a vaccine kills the virus. My idea is to use the door  opened by the virus to close it.  
 Different.   D.   ------------------------------  % Date: Mon, 13 Aug 2001 11:16:17 -0600t% From: Dan O'Reilly <dano@process.com>S, Subject: Re: VIRUSES: What about antibodies?B Message-ID: <5.1.0.14.2.20010813111529.0431c238@ntbsod.psccos.com>  , At 11:12 AM 8/13/2001, Didier Morandi wrote: >"D.Webb" wrote: > >cB > > 1) Max Butler released a worm which fixed a BIND vulnerabilityD > >    and got 18 Months - see http://www.securityfocus.com/news/221 >d> >"Less altruistically, Butler's program created a back door on8 >every system it penetrated, which the hacker could have >used to gain access later". >aH >The trout, all the trout and only the trout, would a Pakistan friend of
 >mine say.  , ..or "so long, and thanks for all the fish".  !           - R.I.P. Douglas Adams.s     ------I +-------------------------------+---------------------------------------+ I | Dan O'Reilly                  |                                       | I | Principal Engineer            |  "Why should I care about posterity?  |aI | Process Software              |   What's posterity ever done for me?" |MI | http://www.process.com        |                    -- Groucho Marx    |vI +-------------------------------+---------------------------------------+i   ------------------------------  % Date: Mon, 13 Aug 2001 10:35:17 -0400r/ From: "Jorge, Carlos " <Carlos.Jorge@gtech.com>n" Subject: VMS 6.21-H3 host crashingM Message-ID: <93B94D806AC4D3118AFC00508B91AA4001F20647@bzmail02.mis.gtech.com>o   Fellows,  H We have been experiencing some strange behaviour on a VMS host since the; beginning of the last week, could someone please help us ? -  K We have a system running on an Alpha Server 8400, 2 CPUs/440Mhz, 2Gb of RAMAJ memory, and last monday we installed a new version using three huge memoryK shareable areas, one of them with 313Mb and the others with 370Mb each. DueTF to our processing constraints and requirements, we lock these areas onJ memory to avoid swapping. When our processing system is up and running, we4 have more or less 366Mb of free physical RAM memory.  J Our VMS version is 6.21-H3, our system is written in fortran language, ourL fortran compiler version is 6.2-508.  The main problem is that sometimes theF Alpha host crashes, mainly when we are doing backups.  This crash alsoI happens - sometimes - we are recording/reading files on tapes.  We have a  TZ88 tape drive.  9 The backup command that we normally use is the following: F backup/bloc_size=65024/media_format=comp/log/ignore=label <disk files> mag1:<saveset name>.bck/savs) mag1 is a logical name for out tape drived  J Up to the present moment we have experienced this crash into two different ways:yJ 1. The Alpha host hungs completely: no new session can be opened.  We have to reboot the systemF 2. A crash dump is printed on system console and after that we see the# "P00>>>" prompt. The halt code is 7   G When we were developing the system, we faced many problems with our VMSrC version, like limitations for working sets (WSMAX 1048756 = 512Mb).p   Thanks in advance, _______________________b Carlos Antonio Rodrigues Jorge cjorge@gtech.com Senior Software Engineer" Gtech Brasil Ltda - Rio de Janeiro   ------------------------------  % Date: Mon, 13 Aug 2001 08:36:24 -0400r5 From: David Beatty <David.Beatty@qwertysasasdfgh.com>rY Subject: Re: VMS: Nothing Stops It (was "I just have to post this - and apoligse later Alo2 Message-ID: <scl3O1ILP+viLSLrsI8sCyRJtOgS@4ax.com>  * On Sat, 11 Aug 2001 08:17:03 GMT, Burnie M& <burniem.NOSPAM@ozemail.com.au> wrote:  2 >On Fri, 10 Aug 2001 15:51:49 -0400, "John W. Hom"  ><j.hom.1@alumni.nyu.edu> wrote: >r >>David Mathog wrote (in part):m >>@ >>> The other issue that perhaps should be mentioned explicitly, >>B >>> and which accounts for a lot of the heat in these discussions, >>> >>> is that when Compaq forces people with 20 years of OpenVMS >>? >>> experience off the OS they very much devalue those 20 years  >>? >>> of hard earned knowledge.   We take this personally becauses >>A >>> it is personal, very personal.  You're good at what you do.  u >> >>? >>I still have two pristine, unused bumper stickers issued from C >>Digital when we were all celebrating the 20th anniversary of VMS. ? >>Along with all the graphic elements were the huge words "VMS"A >>and "Nothing Stops It."e >> >>Sigh.e >> >>John >  >s >Except Compaq ? >c  @ Funny ... I was just thinking the same thing ... David R. Beatty   ------------------------------  % Date: Mon, 13 Aug 2001 17:05:14 -0000-K From: Binyon Steve Contr Det 4 AFC2TIG/ASRCC <Steve.Binyon@kirtland.af.mil>o* Subject: Writing to a DOS floppy under VMS; Message-ID: <61B330D3E7DFD3118A740090271EE321713444@TACCSF>u   Hello all...  L Question one, is there an archive of this list? I just joined and was hoping8 that there would be some info sent to me to this effect.  H The real question is:  Is it possible to write to a DOS formatted floppyJ under the VMS system, much like you can do under Unix (mount -t msdos...)?3 This is under OpenVMS 7.1 running on a Alpha au600.i  L Sorry, I just know these two questions are a popular FAQ, but I did read theK FAQ from which I got this mailing list address from and didn't see them.         Steve Binyon System Administrator TACCSF steve.binyon@kirtland.af.mil (505) 846-8800   ------------------------------  % Date: Mon, 13 Aug 2001 13:49:24 -0500s* From: WILLIAM WEBB <WWEBB1@email.usps.gov>. Subject: RE: Writing to a DOS floppy under VMS- Message-ID: <0033000032113258000002L082*@MHS>a  6 =0ALook for MGPCX and say 'Thank you, Hunter Goatley.'  4 I believe it may be on the freeware CD; if not, then0 it's available over the net from various venues.   WWWebb   > -----Original Message-----1 > From: Info-VAX-Request@Mvb.Saic.Com at INTERNETt' > Sent: Monday, August 13, 2001 1:14 PM F > To: Webb, William W - Raleigh, NC; Info-VAX@Mvb.Saic.Com at INTERNET, > Subject: Writing to a DOS floppy under VMS >A >: > Hello all... >4? > Question one, is there an archive of this list? I just joined  > and was hoping: > that there would be some info sent to me to this effect. > 9 > The real question is:  Is it possible to write to a DOS  > formatted floppy> > under the VMS system, much like you can do under Unix (mount > -t msdos...)?n5 > This is under OpenVMS 7.1 running on a Alpha au600.s >e? > Sorry, I just know these two questions are a popular FAQ, but1 > I did read the9 > FAQ from which I got this mailing list address from and  > didn't see them. >o >n > Steve Binyon > System Administrator > TACCSF > steve.binyon@kirtland.af.mil > (505) 846-8800 >=   ------------------------------  # Date: Mon, 13 Aug 2001 11:12:32 GMT ' From: Colin Blake <colin@theblakes.com>O% Subject: Re: X window Display Setting-- Message-ID: <3B77B5CC.337BAC83@theblakes.com>-  B Not sure if I'm answering the correct question, but to find the IPG address of a Windoze system I run winipcfg (either from Start->Run or ao" DOS window just enter "winipcfg").   Colin.   ------------------------------  % Date: Mon, 13 Aug 2001 09:08:09 -0700-, From: "James Gessling" <jgessling@yahoo.com>% Subject: Re: X window Display Setting 4 Message-ID: <9l8u1b$82ftb$1@ID-46415.news.dfncis.de>  1 > Question 1. How I know to Client's IP Address ?4 >4F If you had telnet'ed to the box from your PC (or wherever you want the1 display to be set too).  Use something like this:s  < $       ttnode = f$getdvi("TT:", "TT_ACCPORNAM") - "[" - "]"E $       set display/create/node='ttnode'/trans=tcpip  ! xxx = your IPo address   & Thanks to Alan Gilbert for this trick.   Jima   ------------------------------  % Date: Mon, 13 Aug 2001 12:34:27 -0400-5 From: "Fred Kleinsorge" <kleinsorge@star.zko.dec.com>n% Subject: Re: X window Display Setting#1 Message-ID: <LkTd7.59$bB1.10916@news.cpqcorp.net>-  B You might look into enabling XDM on your VMS system (see the TCPIPK documentation).  With XDMCP enabled, you can connect to the VMS system from-
 excursion.      K James Gessling wrote in message <9l8u1b$82ftb$1@ID-46415.news.dfncis.de>...e2 >> Question 1. How I know to Client's IP Address ? >>G >If you had telnet'ed to the box from your PC (or wherever you want they2 >display to be set too).  Use something like this: >-= >$       ttnode = f$getdvi("TT:", "TT_ACCPORNAM") - "[" - "]"-F >$       set display/create/node='ttnode'/trans=tcpip  ! xxx = your IP >address >r' >Thanks to Alan Gilbert for this trick.P >F >Jim >d >!   ------------------------------   End of INFO-VAX 2001.448 ************************