1 INFO-VAX	Sun, 16 Jul 2000	Volume 2000 : Issue 395       Contents:3 Re: Alpha PWS500a(u) - Which machines will run VMS?  Analyzing Process Dump Analyzing Process Dump% RE: Apache for Open VMS, performance?  Re: Building TK50's  Re: Building TK50's " RE: CMQ/Dec with a sense of Humor?" Re: CMQ/Dec with a sense of Humor?" Re: CompactTape II sources (TK70)? DHCP  Differences in Fortran versions?$ Re: Differences in Fortran versions?$ Re: Differences in Fortran versions?$ Re: Differences in Fortran versions?# Re: Is my solution SAMBA ? Thanks.. # Re: Is my solution SAMBA ? Thanks..  Re: OpenVMS/Alpha and PERL RGB VLC Monitor Question* Re: SQL+ODBC options, inexpensive or free?M Re: Switching from VXT (x/motif) clients to PC(java 2) clients (a 
 question) " Re: TeX (was: VMS Pascal question) UCX and DHCP Re: UCX and DHCP VAXstation VLC terminal  Re: VMS 7.3 wish list  Re: VMS Pascal question : vms$common - syscommon problems after retoring system disk: vms$common - syscommon problems after retoring system disk  F ----------------------------------------------------------------------  % Date: Sun, 16 Jul 2000 03:07:25 -0400  From: quayle@pobox.com< Subject: Re: Alpha PWS500a(u) - Which machines will run VMS?. Message-ID: <397126ED.15314.353F964@localhost>  = I'm using a PWS500au with 2 SCSI disks; it came with factory- $ installed VMS, and works just great.  > Cost me $4k, including the VMS and NAS licenses.  I suspect a ( licenseless box would cost half as much.     --Stan  
 ----------G Stanley F. Quayle, P.E.   N8SQ   +1 614-868-1363   Fax: +1 614 868-1671 1 8572 North Spring Ct. NW, Pickerington, OH  43147 = Preferred address:  stan@stanq.com       http://www.stanq.com    ------------------------------  % Date: Sun, 16 Jul 2000 17:08:39 +0300 ' From: "Shay E. Cohen" <shayc@ncc.co.il>  Subject: Analyzing Process Dump 0 Message-ID: <8ksfld$n00$1@news.netvision.net.il>  % I'm trying to analyze a process dump:  $ ANALYZE/PROCESS file.DMP  J When getting the debugger prompt I try to examine some variables but I get an error message:  DBG> examine b@ %DEBUG-W-SYMNOTACT, non-static variable 'A\main\b' is not active   I have VAX/VMS V5.5-2.   ------------------------------  % Date: Sun, 16 Jul 2000 12:44:08 -0400 2 From: "Richard B. Gilbert" <DRAGON@compuserve.com> Subject: Analyzing Process Dump 7 Message-ID: <200007161244_MC2-AC71-1075@compuserve.com>   F         I think it's trying to tell you that the variable is allocatedD dynamically at run time and has not yet been created or, it has beenJ created, used, and the storage freed again.  In short, the variable did n= ot% exist at the time the dump was taken!     ' Message text written by "Shay E. Cohen" & >I'm trying to analyze a process dump: $ ANALYZE/PROCESS file.DMP  J When getting the debugger prompt I try to examine some variables but I ge= t  an error message:  DBG> examine b@ %DEBUG-W-SYMNOTACT, non-static variable 'A\main\b' is not active   I have VAX/VMS V5.5-2. <    ------------------------------  % Date: Sun, 16 Jul 2000 11:49:31 -0400 + From: "Main, Kerry" <Kerry.Main@compaq.com> . Subject: RE: Apache for Open VMS, performance?J Message-ID: <910612C07BCAD1119AF40000F86AF0D805284540@kaoexc4.kao.dec.com>   David,  E Since Apache on OpenVMS is still in beta, I suspect comparing it to a I production release on another platform would be like comparing apples and 	 oranges.    H For that matter, comparing a beta version of any product to a productionK version on another platform may make for interesting discussions, but since H beta versions of products usually have all sorts of debug code loaded inK them (I have no idea if the OpenVMS Apache does or not), it does not really  make for a fair comparison.   J One thing that Customers may find of interest with OpenVMS Apache ClustersK will be shared common files with full read-write update capability from all H systems and common startups for multiple servers, load balanced, cluster wide batch queues etc.  B Will Apache on OpenVMS beat OSU from a performance point of view?   L My personal $.02 (and based only on pure speculation) is that it likely will* not, because OSU is optimized for OpenVMS.  J If a Customer asked me which to use, I would respond with - If performanceJ and integration with the host OS is the prime reason for looking for a webK server on OpenVMS, my personal recommendation would be to use OSU. Lets not K forget that David Jones has put together an excellent web server product on  OpenVMS.  H If a Customer wants to run applications that require Apache and yet, youE still want to take advantage of the features provided by OpenVMS (and G possibly clusters), then Apache on OpenVMS would also be a good choice.   F Btw - a new update (July 12) for Apache beta on OpenVMS is aavailable:F http://www.openvms.digital.com/openvms/products/ips/apache/apache.html   Regards,  
 Kerry Main Senior Consultant,
 Compaq Canada  Professional Services  Voice : 613-592-4660 FAX   : 819-772-7036 Email : kerry.main@compaq.com        -----Original Message-----# From: mathog@seqaxp.bio.caltech.edu & [mailto:mathog@seqaxp.bio.caltech.edu]& Sent: Thursday, July 13, 2000 12:03 PM To: Info-VAX@Mvb.Saic.Com * Subject: Apache for Open VMS, performance?    B Can somebody at Compaq provide benchmark or other performance testC information for Apache on OpenVMS vs. Apache on Linux (or Tru64) on J identical hardware?   And while you're at it, how about a test against theJ OSU and WASD servers - which is what most OpenVMS customers are using now.  E The bits which most interest me, and presumably anybody serious about  "e-business" are:   !  1.  "raw" html page serving rate K  2.  scripted html page serving rate (speed for pages produced by Perl/java  scripts)F  3.  transaction processing rates (max rate of form based input, to a )      database back end and/or flat files) $  4.  all of the above, through https  @ Apache does a lot of IO, but since it is essentially a read onlyI application, there is at least in this instance a significant chance that K the results will be comparable.   If I had to guess though, I'd expect that I the currently feeble file caching that OpenVMS offers is going to cause a J major performance hit when the tests hit a large number of pages in randomJ order, unless this version of Apache implements its own cache, as does the OSU server.    Thanks,    David Mathog mathog@seqaxp.bio.caltech.edu ? Manager, sequence analysis facility, biology division, Caltech     ------------------------------  # Date: Sun, 16 Jul 2000 17:10:53 GMT 8 From: Veli =?iso-8859-1?Q?K=F6rkk=F6?= <korkko@decus.fi> Subject: Re: Building TK50's( Message-ID: <3971B7D5.6216103E@decus.fi>  F If I recall things correctly, DEQNA support ceases COMPLETELY at V6.0.B Cluster support ended at V5.4-3 or at V5.5(-2). Cannot speak aboutC other protocols like LAT and DECnet but I would expect them to work  at say V5.5-2.   _veli    "John E. Malmberg" wrote:  > D > Bill Gunshannon <bill@triangle.cs.uofs.education> wrote in message( > news:8kfiva$2cla$1@info.cs.uofs.edu...: > > In article <8kfg3l$d1p$2@mailint03.im.hou.compaq.com>,9 > >  hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) writes:  > > |>! > > |>   Which specific MicroVAX?  > > ! > > A pair of MicroVAX-II (KA630) 5 > > One with 16M of memory and one with 9M of memory.  > >  > > |>@ > > |>   Which specific system disk do you have on the MicroVAX? > > F > > Right now, I have RD54's for both of them.  Kind of hoping I could- > > get some SMD disks working at some point.  > >  > > |>D > > |>   Do you have a network between the MicroVAX and another VAX? > > F > > let's start this with a description of just what I have and what I > > am trying to do. > > G > > I have a VAX 4000-100 (with a QBUS expansion box) running OVMS-7.1. H > > I have a pair of MicroVAX-II's one is currently running MicroVMS-4.4G > > and the other is currently parts in a box hopefully soon to be made # > > into a functioning MicroVAX-II.  > > I > > The 4000 has SCSI and thus CDROM's.  The running MicroVAX has a TK50. I > > It also has DECNET so communications between the two running machines H > > is possible.  I have another MicroVAX (not running VMS) that I couldH > > borrow an RA82 and a KDA50 from if that is the only practical way toI > > do this, but I was hoping there was a simple (relatively) way to make < > > install tapes for VMS and for selected Layered Products. > M > Watch out.  That old of MicroVAX hardware may have a DEQNA not a DELQA, and ' > that is very important to your plans.  > M > The DEQNA is not very useful anymore for VMS.  It will work with some early M > versions of UCX, but not the current.  It stops working for DECNET/LAT/LAVC # > not too much higher that VMS 4.7.  > I > If you have a DEQNA, you will need to keep a backup of your current 4.x N > system image, because after you upgrade, the only networking that I am aware$ > of that will still work is CMU-IP. >  > > |>E > > |>   Do you have a CD-ROM drive that you can relocate over to the  > MicroVAX, L > > |>   or a disk you can relocate from the MicroVAX to another VAX system? > > L > > No to the first, but the second seems likely assuming KDA50's and RA82's > > are still supported in 7.1.  > % > According to the S.P.D. that is ok.  >  > > |>N > > |>   The usual approach involves building a standalone BACKUP kit onto theK > > |>   TK50 cassette, then relocating the VMS*.% and DECW*.% savesets out  > > |>   onto the media. > > L > > That sounds simple enough, but I wasn't sure if there was something lessD > > obvious that I was unaware of.  You mention DECW*.%.  Isn't that > DECWindows??E > > Is that needed for a box that has no graphics capability??  Would  > DECWindowsM > > even run (even remotely to an Xterminal) on machines with so little RAM??  > K > Yes, you can do it if you do not mind waiting for the windows to show up. N > Response will not be the best.  Once the DECterm is up, though it is not tooL > bad, even with as low as 6M on a VAXstation 2000.  A MicroVAX II having noH > graphics hardware should be be a little faster than a VAXstation 2000. > * > > I appreciate any help you can provide. > L > With that configuration, If you have compatable network hardware availableN > for the MicroVAX IIs, I would simply make the VAX 4000-100 a LAVC boot node.< > Then I would configure that MicroVAX IIs to be satellites. >  > > --N > > Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesH > > bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. > > University of Scranton   |B > > Scranton, Pennsylvania   |         #include <std.disclaimer.h> >  > -John  > wb8tyw@qsl.network   ------------------------------  + Date: Sun, 16 Jul 2000 12:33:34 -0500 (CDT)  From: sms@antinode.org Subject: Re: Building TK50's) Message-ID: <00071612333380@antinode.org>   8 From: Veli =?iso-8859-1?Q?K=F6rkk=F6?= <korkko@decus.fi>  H > If I recall things correctly, DEQNA support ceases COMPLETELY at V6.0.D > Cluster support ended at V5.4-3 or at V5.5(-2). Cannot speak aboutE > other protocols like LAT and DECnet but I would expect them to work  > at say V5.5-2.       Notes in my archives suggest:  K       According to the release notes for VMS V5.5 (1991), starting with VMS K    V5.4-3, the DEQNA was not supported by the VAXcluster software, and "VMS K    V5.5 withdraws support for the DEQNA device, except for access using the F    QIO or ALTSTART interfaces.  Within 18 months, a release of the VMSH    operating system will withdraw _all_ support for the DEQNA; after youH    install that future release, the Ethernet driver will place the DEQNA9    device in an OFFLINE state, rendering it inoperative."   H    Presumably, "that future release" was V6.0, but VMS would pretty much  ignore a DEQNA from V5.5 onward.  H ------------------------------------------------------------------------  C    Steven M. Schweda               (+1) 651-699-9818  (voice, home) C    382 South Warwick Street        (+1) 763-781-0308  (voice, work) G    Saint Paul  MN  55105-2547      (+1) 763-781-0309  (facsimile, work) 9    sms@antinode.org                sms@provis.com  (work)    ------------------------------    Date: 16 Jul 2000 10:28:05 -05001 From: kaplow_r@eisner.decus.org.mars (Bob Kaplow) + Subject: RE: CMQ/Dec with a sense of Humor? + Message-ID: <zTvkXqsl+VYA@eisner.decus.org>    In article <1137A4A23A51D311B2D600105A1D5213019AEE9B@seantexch.unitedad.com>, Terry Marosites <TMarosites@unitedad.com> writes: K >    My first VMS class was in Orlando Fl. (Near Disney World), Dec at that N > time had developed a two node cluster with the nodes as snow and white (theyC > also had 7 terminal servers, can you name the terminal servers).  N > I am sure with info-vax group you can collect some very strange cluster nameN > and node name configuration. Even just looking at some of the old orange and9 > gray wall references there were some fun name in them.    H One of my favorites was the MARX cluster in the Bedford training center:. Groucho, Chico, Harpo, Gummo, Zeppo, and Karl!   	Bob Kaplow	  E SPAM:	spamrecycle@ChooseYourmail.com	uce@ftc.gov	postmaster@127.0.0.1    ------------------------------  % Date: Sun, 16 Jul 2000 14:41:51 +0100 $ From: Andy Burns <andy@burns.uk.net>+ Subject: Re: CMQ/Dec with a sense of Humor? 8 Message-ID: <fqe3nss2qlrhc3s9cdjahgivt13501n0cc@4ax.com>   Bob Kaplow wrote:   I >One of my favorites was the MARX cluster in the Bedford training center: / >Groucho, Chico, Harpo, Gummo, Zeppo, and Karl!   G one of our customers call(ed) his ronnie, reggie and violet as his boss  wouldn't let him buy a cray !      --  
 Andy Burns   ------------------------------  % Date: Sun, 16 Jul 2000 11:12:15 -0400 2 From: "Richard B. Gilbert" <DRAGON@compuserve.com>+ Subject: Re: CompactTape II sources (TK70)? 7 Message-ID: <200007161112_MC2-AC72-8AD4@compuserve.com>   E         I believe that the tape was identical and the cartridges were  obviously interchangable. H I think that the increase in capacity was all, or mostly, due to writingF additional tracks and that the difference was that the cartridges were  specified to tighter tolerances.  # Message text written by Jerome Fine . >There used to be a VERY excellent summary at:  5 http://www.anacomp.com/Magnetics/Memorex/m-ctdlt.html   H which showed that the same specifications were given for both CompacTapeH for the TK50  AND  FOR  CompacTape II for the TK70.  The only differenceH I have seen in practice is that the label for the CompacTape is in BROWN and G the label for the CompacTape II is in BLUE - aside for the higher price  that DECJ charged when the tapes were new.  I do not think I saved the page, but it=  
 definitelyJ stated that the physical characteristics of the tapes were identical.  Di= d  anyone else  retain a copy?  J I have a friend who may still have his bulk eraser plus he may even have = a  few H CompacTape II media.  Please contact me directly if you are interested.<   ------------------------------  # Date: Sun, 16 Jul 2000 15:53:55 GMT ! From: TGS <tgsi@bellatlantic.net> 
 Subject: DHCP . Message-ID: <3971DB18.91298B@bellatlantic.net>  E I am running OVMS 7.2-1.  Using UCX and I am interested in setting up  DHCP.   G Can anyone offer any advice or instructions, websites maybe.  Any ideas  are appreciated.   Thanks  
 Jim Maroun tgsi@bellatlantic.net    ------------------------------  # Date: Sun, 16 Jul 2000 14:43:57 GMT ! From: Beyonder <beyonder@vrx.net> ) Subject: Differences in Fortran versions? ' Message-ID: <3971CA2F.C5BC66BC@vrx.net>   : Can someone explain this to me... I'd really like to know.? I have an old fortran source code from 1989 (1992 with updates) = that compiled and ran fine with no errors or warnings at all. 9 runs like a charm... that is, on a vax11/750 or vax11/780 / running vms from 1989-1994 written and compiled : using fortran 77 (perhaps a bit of fortran IV, don't know)5 originally written on a PDP11 in 1988/1989 and ported   C in any case, I take this same exact code, and try to get it to work A on a modern system (vax or alpha) openvms 7.2 current fortran 77. F no dice. I get compiler errors or warnings, ok, so clean up the stuff.C compiles fine, no errors, no warnings, but the program has run-timeS' crashes, and in some cases, just hangs.   ' Has fortran 77 (DEC) changed that much?hF Is there no way I'm going to get my stuff working without some seriousF recoding? and what happens to the program with all these logic changes I now have to do?M  @ Does anyone out there have an OLD vax still running the OLD vms?A I have a system with vms5.5 kicking around but not sure if I havei fortran on it. anyone have the old one?  H Then the question is, can I take an EXE from the old vms and will it run8 on the new vax or alpha ? (inquiring minds want to know)   augh...a   Dan.   ------------------------------  % Date: Sun, 16 Jul 2000 10:54:44 -0400 + From: Tim Shoppa <shoppa@trailing-edge.com>(- Subject: Re: Differences in Fortran versions?s1 Message-ID: <39719474.71C3FB34@trailing-edge.com>    Beyonder wrote:H > < > Can someone explain this to me... I'd really like to know.A > I have an old fortran source code from 1989 (1992 with updates) ? > that compiled and ran fine with no errors or warnings at all. ; > runs like a charm... that is, on a vax11/750 or vax11/780-1 > running vms from 1989-1994 written and compiled < > using fortran 77 (perhaps a bit of fortran IV, don't know)7 > originally written on a PDP11 in 1988/1989 and portedF > E > in any case, I take this same exact code, and try to get it to workoC > on a modern system (vax or alpha) openvms 7.2 current fortran 77.tH > no dice. I get compiler errors or warnings, ok, so clean up the stuff.E > compiles fine, no errors, no warnings, but the program has run-time1) > crashes, and in some cases, just hangs.r > ) > Has fortran 77 (DEC) changed that much?f  < No, but chances are that what you originally wrote used some< behaviors that were officially "undefined" in the Fortran 77= standard.  Things like assuming the order that variables willa? appear in memory, that an integer passed to a routine expectingtF a float will be interpreted in (roughly) the manner you expected, etc.    Examples that I still often see:  A Declare two arrays, A(100) and B(100).  Clear A(1...200) to clear> out both arrays.  Ughhh!!!!T  E A little more subtle, there are often assumptions about the alignment > of variables in common blocks.  These assumptions work OK on a? -11 or VAX, but may not work with the default compiler flags onu	 an Alpha.y  D Pass a small integer (i.e. 1) to a routine expecting a REAL argument@ there.  This works fine with the old floating point formats, but> is a no-no with IEEE floats (as used on most modern machines).  J > Then the question is, can I take an EXE from the old vms and will it run: > on the new vax or alpha ? (inquiring minds want to know)  B It'll run just fine on a VAX.  On an Alpha you'll need to VEST it.   Tim.   ------------------------------  # Date: Sun, 16 Jul 2000 15:51:53 GMTI! From: Beyonder <beyonder@vrx.net>I- Subject: Re: Differences in Fortran versions?D' Message-ID: <3971DA15.D03563D2@vrx.net>m   Tim Shoppa wrote:   > > No, but chances are that what you originally wrote used some> > behaviors that were officially "undefined" in the Fortran 77? > standard.  Things like assuming the order that variables willcA > appear in memory, that an integer passed to a routine expectingaH > a float will be interpreted in (roughly) the manner you expected, etc.  ? probably more than likely. lots of non-standard stuff in there.bN but it HAS been successfully ported to gnu fortran (linux) although it has the8 same problems there, as with the other modern compilers.  C > Declare two arrays, A(100) and B(100).  Clear A(1...200) to clear  > out both arrays.  Ughhh!!!!r  ! the code proabably does this too.a  G > A little more subtle, there are often assumptions about the alignmentr@ > of variables in common blocks.  These assumptions work OK on aA > -11 or VAX, but may not work with the default compiler flags onf > an Alpha.e  C Doesn't work on a modern vax. actually the vax and alpha behave thesM same way with the code (which is nice). some routines cause the code to hang.SI For instance, the way the code generates random numbers is one of the big H headaches. the old fortran used "RAN", which really doesn't exist today.M and the way RANDO works is fairly contrary to what the code was trying to do. L for example: if a seed of "2" is chosen, the code will hang, every time with the new compiler/vms versions.  M I've tried to clean this up but I think I'll have better luck getting someoneo8 with an old fortran/vax/vms to compile the damn thing...  F > Pass a small integer (i.e. 1) to a routine expecting a REAL argumentB > there.  This works fine with the old floating point formats, but@ > is a no-no with IEEE floats (as used on most modern machines).    this the code does in abundance!  D > It'll run just fine on a VAX.  On an Alpha you'll need to VEST it.  M never heard of "VEST" but doesn't matter since I still need the compiled code  in the first place.n  9 Anyone out there with an old vax/old vms/old fortran ? :)6   Dan.   ------------------------------  % Date: Sun, 16 Jul 2000 12:24:15 -0400g+ From: Tim Shoppa <shoppa@trailing-edge.com> - Subject: Re: Differences in Fortran versions?h1 Message-ID: <3971A96F.414366D2@trailing-edge.com>i   Beyonder wrote:a > A > probably more than likely. lots of non-standard stuff in there.hP > but it HAS been successfully ported to gnu fortran (linux) although it has the: > same problems there, as with the other modern compilers.  ) I would *not* call that a succesful port!A  E > Doesn't work on a modern vax. actually the vax and alpha behave theiO > same way with the code (which is nice). some routines cause the code to hang.eK > For instance, the way the code generates random numbers is one of the bigeJ > headaches. the old fortran used "RAN", which really doesn't exist today.  G Huh?  Most all Fortran run-time libraries that support "VAX extensions"o; (and I think this covers *all* commercial Fortran compilerse! available today) will have RAN().e  D > for example: if a seed of "2" is chosen, the code will hang, every* > time with the new compiler/vms versions.  D 2 is hardly a good choice for an initial seed, but a code that hangs. solid with some seeds is *not* a working code!  O > I've tried to clean this up but I think I'll have better luck getting someonei: > with an old fortran/vax/vms to compile the damn thing...  B If this program does anything important, you'll probably have muchD better luck re-implementing it from scratch.  IMHO you're misleadingE yourself if you're trying to find a bug-compatible compiler to handle,C the inherently bug-ridden sources.  I think it was pure coincidenceoD that this piece of code ever appeared to do what it was supposed to.  A If worse comes to worse, I *do* have a fairly complete collections? of VMS and layered product distributions going back to VMS 3.0.-; But again, I don't think you'd be doing yourself a favor byu doing this.e   Tim.   ------------------------------  % Date: Sun, 16 Jul 2000 10:32:08 -0400l2 From: "William Hymen" <t18_pilot@hotmail.spam.com>, Subject: Re: Is my solution SAMBA ? Thanks..8 Message-ID: <RCjc5.323010$MB.5351911@news6.giganews.com>  J I don't purchase the software. Can I assume that NFS is a Compaq supportedJ product?  It's one of the banks requirements that the software be licensed  by a vendor that supply support.   Bill  3 Jack Peacock <peacock@simconv.com> wrote in messagey8 news:_J3c5.22789$MT.726342@news-west.usenetserver.com...= "William Hymen" <t18_pilot@hotmail.spam.com> wrote in message 2 news:pV2c5.319758$MB.5309861@news6.giganews.com.... > On VAX 6.2 , I have vms developers coding c,2 > and I need to see the same directory as a mapped > drive/folder on NT >jG If you have NFS on the VAX you can use the NFS gateway in the Microsoft4F NT Services for Unix.  VMS directories mapped to NFS appear on networkD neighborhood. There are some limitations in how NFS handles VMS fileE types (watch out for RELATIVE files), and there is a bottleneck goingaA through the NT gateway server, but it's cheap, and best of all noRF clients to load anywhere.  The VMS memory requirements are far smaller than Pathworks too.e    Jack Peacocki   ------------------------------  % Date: Sun, 16 Jul 2000 10:57:24 -0500u) From: "John E. Malmberg" <wb8tyw@qsl.net>t, Subject: Re: Is my solution SAMBA ? Thanks... Message-ID: <sn3mehsvnd619@corp.supernews.com>  H Until you test SAMBA with your application, you will not know if it will work.   E Current releases of SAMBA for OpenVMS do not support any sort of filenK sharing, and will require that you set your Windows PCs to allow plain textf
 passwords.  - But the license fees are vary reasonable. :-)s  H The NFS program on the VMS side is usually bundled with what ever TCP/IPJ program that you have.  I do not know if all the variants of the licensing allow the use of NFS.u   -John  wb8ytw@qsl.network   ------------------------------  % Date: Sun, 16 Jul 2000 11:38:02 +0200l  From: Paul Sture <paul@sture.ch># Subject: Re: OpenVMS/Alpha and PERL + Message-ID: <VA.0000007d.2988bf91@sture.ch>X  G In article <396EC2CB.A3BFC43C@EDV-Berater-GmbH.de>, Lothar Geyer wrote:s7 > From: Lothar Geyer <Lothar.Geyer@EDV-Berater-GmbH.de>e > Newsgroups: comp.os.vms2% > Subject: Re: OpenVMS/Alpha and PERL ' > Date: Fri, 14 Jul 2000 08:35:39 +0100  >   C > I know a PERL compiler for the PDP-11 (RSX-11M), created by BrownU > Bovery(?), which is now ABB.  A Asea Brown Bovery (or is it Boveri?). Now called Alstom. Their HQ 5 is only a few hundred meters from where I sit now ;-)b  * >The software has to be ported to an AlphaB > running OpenVMS. There is more than one way to do this (hardwareB > emulation a.s.o.). If there is a PERL compiler this would be theG > simplest way. Another one would be to translate PERL to FORTRAN (somerI > time ago DEC had a package to "translate" text files as I remember. Anyo > other suggestions? > S Do you have any contact or department names? Being so close and having friends who hU work there it could well be possible for me to find out if the product still exists, n is available etc.r   mfgh ___b
 Paul Sture Switzerland    ------------------------------  % Date: Sun, 16 Jul 2000 11:07:16 -0400i0 From: arturo saavedra <arturo.saavedra@wcom.com>! Subject: RGB VLC Monitor QuestioniC Message-ID: <NDBBJFNBJJHKADILJHIJIEOOEKAA.arturo.saavedra@wcom.com>   K Is there a chance that I could use my RGB VLC monitor as a regular monitor,lC that is, I'd like to use it as a monitor on a PW500au but the Alphas) workstation does not have RGB connection.e   thanks   -----Original Message-----8 From: Bob Kaplow [mailto:kaplow_r@eisner.decus.org.mars]$ Sent: Sunday, July 16, 2000 11:28 AM To: Info-VAX@Mvb.Saic.Como+ Subject: RE: CMQ/Dec with a sense of Humor?     
 In articleH <1137A4A23A51D311B2D600105A1D5213019AEE9B@seantexch.unitedad.com>, Terry+ Marosites <TMarosites@unitedad.com> writes: K >    My first VMS class was in Orlando Fl. (Near Disney World), Dec at that H > time had developed a two node cluster with the nodes as snow and white (theyeB > also had 7 terminal servers, can you name the terminal servers).I > I am sure with info-vax group you can collect some very strange clusterN nameJ > and node name configuration. Even just looking at some of the old orange and)8 > gray wall references there were some fun name in them.  H One of my favorites was the MARX cluster in the Bedford training center:. Groucho, Chico, Harpo, Gummo, Zeppo, and Karl!   	Bob Kaplowi  E SPAM:	spamrecycle@ChooseYourmail.com	uce@ftc.gov	postmaster@127.0.0.1i   ------------------------------  % Date: Sun, 16 Jul 2000 13:17:35 +0100r5 From: "Chris Casey" <Chris.Casey@HendersonNOSPAM.com>v3 Subject: Re: SQL+ODBC options, inexpensive or free? ) Message-ID: <8ks95f$etd$1@soap.pipex.net>V  K Jeff Coffield wrote in message <396F6732.FAD1D23E@DigitalSynergyInc.com>...- >David Mathog wrote: >-J >> What are the options, if any, for a free (or very inexpensive) SQL+ODBCG >> program for OpenVMS Alpha?   One of my users has a project which may6J >> require this, performance shouldn't be that big an issue, but cost will be.  >>J >> Am I the only one who finds it odd that the OpenVMS guys are working soG >> hard on Apache without, apparently, having provided in any way for am serverJ >> database smaller than RDB or Oracle?  I wonder what the intended market is    K There are certainly other (and far better) databases available on VMS which1) are cheaper and have much less footprint..F I you want to see one which is taking market share from Oracle look at www.intersys.com.l   ------------------------------  % Date: Sun, 16 Jul 2000 07:28:29 -0700 ' From: Mickey Stein <yekkim@pacbell.net>(V Subject: Re: Switching from VXT (x/motif) clients to PC(java 2) clients (a 
 question)+ Message-ID: <3971C68D.FF73D199@pacbell.net>   > <!doctype html public "-//w3c//dtd html 4.0 transitional//en"> <html>I Just realized how much easier this was to write than I thought. All I had L to do was drop the accept() and replace it with a socket() call, eliminatingF the port# since it's taken care of already by tcpip set service. works great, <br>&nbsp;&nbsp;&nbsp; thanks,3 <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mick-
 <br>&nbsp; <p>Carl Perkins wrote:D <blockquote TYPE=CITE>Mickey Stein &lt;yekkim@pacbell.net> writes...6 <br>}I've got a project that was coded originally in C6 <br>}on VMS. and a GUI-builder "de jour" (teleuse) was6 <br>}used to generate the front-end templates that are6 <br>}in x/motif format. A decision was made to convert7 <br>}the front-end clients to PC's running java 2. I'veo6 <br>}done some initial legwork and verified that there/ <br>}seems to be no significant problems on the-3 <br>}front-end by coding up a number of prototypes, 7 <br>}attaching to a socket-server that I built into the>5 <br>}Server code on VMS and doing transactions. Also,-6 <br>}the server application can basically have the old7 <br>}GUI "gutted" and be run as a background app serverg! <br>}sitting at a/some socket(s).  <br>}n3 <br>}Yet another summary: We're going from a systemu/ <br>}where each client used a VXT, started withe5 <br>}decw$login and executed it's code in the contextr6 <br>}of a typical VMS loginout process. We're going to5 <br>}a system where it's not so clear how the contextw5 <br>}is handled. Of course, it's not difficult to use 7 <br>}the Java front end to send requests to the server,o7 <br>}request authorization on the old accounts by usingK5 <br>}$hash_password, $getuai, etc.. What seems reallya6 <br>}problematic to me is that there's no longer a VMS2 <br>}context for each client because I'm not using6 <br>}loginout in any way (because it's not clear to me6 <br>}how to do such a thing). Recoding the Server code1 <br>}is beyond the scope of the project and using 1 <br>}something like xcursion(x-server) won't workn5 <br>}either because the GUI no longer is supported so 3 <br>}it's got to go. If I haven't mentioned it, theI7 <br>}Server is a 4100 Alpha-cluster running VMS 7.2 andd5 <br>}the Server(s) is written in DEC C. I ported thisu5 <br>}project vax to alpha a few years ago so the code   <br>}is quite "old" (86' or so). <br>}15 <br>}Q: If anyone can give any ideas as to how 50-100n7 <br>}clients can use VMS loginout (or something similarn2 <br>}using system services?) thus having their own6 <br>}context (well, a process to execute in) and still5 <br>}be using the java front end, I'd sure appreciate-7 <br>}hearing them. Really, the other big factor here isr2 <br>}obviously that each client will wind up being4 <br>}serialized without it's own context, thread, or5 <br>}process. I don't know that the old code will runo7 <br>}without breaking any number of decthreads rules. I 3 <br>}also don't know that decthreads is any sort ofr1 <br>}viable answer to the context/login situation 3 <br>}because any number of ancillary routines (like84 <br>}..com files) are used to manage processes which0 <br>}wouldn't do much good if there were no user <br>}process&lt;g>)8 <br>}a( <br>}&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; tia,
 <br>} Mick, <p>The solution is to create user processes.D <p>Instead of having a single server that sits on a port and handlesL <br>all the connections, you need to have your IP stack create a new processJ <br>for each incoming connection much the way that Telnet, FTP, POP, IMAP,F <br>SAMBA etc. do it (depending on your IP software, some of these may notoI <br>work that way - they all do with Multinet). Then each user is runnings a F <br>separateinstance of the server in the context of a process running under H <br>their own username. This requires somewhere from a bit more to a lot moreH <br>resources then a single-server type operation, but that shouldn't be a?F <br>problem. It is what you used to do and it won't use more resources thanJ <br>it used to, probably somewhat less - you are dropping X-windows acrossH <br>a network (and X is not known for being light on the resource usage) forr0 <br>comparatively simple network communications.H <p>A single server (or fixed pool of servers) solution probably requiresF <br>modifying the server to, at the very least, use the Persona system sevices'I <br>to change its context to that of the user who's request it is working  on <br>at the time. <p>--- Carl</blockquote> </html>r   ------------------------------  % Date: Sun, 16 Jul 2000 19:11:12 +0010a% From: paddy.o'brien@zzz.tg.nsw.gov.auw+ Subject: Re: TeX (was: VMS Pascal question)h5 Message-ID: <01JRUGID85QQ001SYM@tgmail.tg.nsw.gov.au>t  % OT, but thus has this thread evolved.    Wayne Sewell wrote:   M >The computer world has gone to shit in many ways, mostly due to billy gates.p  < You can exclude the word "computer" from the above sentence.   >>Sigh.  What happened to theu >> Good Old Days? :-)s >n >Good question.w  M Well, billy boy was born and sortta grew up, and that f**ked the world as we r know it.  Q However, the definition of "good old days" really depends upon when you grew up. yO For most of us, our late teens and early twenties, whichever decade that was.  tM Those fleeting memories of irresponsibilities as we approach our dotage.  In  Q this respect, nothing to do with billy or computers (unless you have always been g a nerd).   ***o  9 Slightly more On-T for the way this thread has digressed.r  I I found that the Freeware CD was the best source for installing TeX (and .N friends) on VMS.  The elegance of WEB, etc., is so typical of reading Knuth's ) books.  All source seems to be available.s  I As a total disdainer of anything from billy (and other WYSIWYG products, pM including DECwrite, but especially anything from bg), this is the only "word i  processor" I use for my reports.   Regards, Paddy   Paddy O'Brien, Transmission Development,w
 TransGrid, PO Box A1000, Sydney South,  NSW 2000, Australiae   Tel:   +61 2 9284-3063 Fax:   +61 2 9284-3050& Email: paddy.o'brien@zzz.tg.nsw.gov.au  M Either "\'" or "\s" (to escape the apostrophe) seems to work for most people,y; but that little whizz-bang apostrophe gives me little spam.-   ------------------------------  # Date: Sun, 16 Jul 2000 16:13:04 GMTn( From: Mark Saad <2saad_m@spcvxa.spc.edu> Subject: UCX and DHCP F Message-ID: <Pine.PMDF.4.21L.0007161207520.8114-100000@spcvxa.spc.edu>  H I am trying to set up a DHCP server on VMS 7.2-1 I don't have any of theI documentation on UCX and I was wondering if anyone knows the files I needeD to edit. Also Is it worth it to go to compaq and try and get some ofH documents from them? I am a student and I don't have much money to throw around.   	 Mark Saad  St. Peter's Collegek Academic Computer Center 2saad_m@spcvxa.spc.edu   ------------------------------  % Date: Sun, 16 Jul 2000 12:21:04 -0500a) From: "John E. Malmberg" <wb8tyw@qsl.net>  Subject: Re: UCX and DHCP 7 Message-ID: <13e401bfef4a$3a21b850$020a0a0a@xile.realm>   / Mark Saad <2saad_m@spcvxa.spc.education> wrote:d  J > I am trying to set up a DHCP server on VMS 7.2-1 I don't have any of theK > documentation on UCX and I was wondering if anyone knows the files I needaF > to edit. Also Is it worth it to go to compaq and try and get some ofJ > documents from them? I am a student and I don't have much money to throw	 > around.e  K The Compaq TCP/IP (formerly UCX) product documentation is on-line at a link " from http://www.openvms.compaq.com   -Johnu wb8tyw@qsl.network   ------------------------------  % Date: Sun, 16 Jul 2000 07:35:38 -0400a2 From: "Richard B. Gilbert" <DRAGON@compuserve.com>  Subject: VAXstation VLC terminal7 Message-ID: <200007160735_MC2-AC72-B4FB@compuserve.com>,  J         Connect a terminal to the MMJ connector on the back, move switch = S3J (on the left side) to the up position.   Power cycle the box (it's the on= ly time the switch is sensed).     & Message text written by "Dan O'Reilly" > =c  F Having a brain dump here.  How (and where) do I connect a serial cableG to a VS VLC?  I have one that won't boot, so I need to see the console.h5 I don't normally have anything connected to this one.u <u   ------------------------------  % Date: Sun, 16 Jul 2000 11:38:04 +0200E  From: Paul Sture <paul@sture.ch> Subject: Re: VMS 7.3 wish list+ Message-ID: <VA.0000007e.2988c796@sture.ch>o  @ In article <8kneg7$kg2@gap.cco.caltech.edu>, David Mathog wrote:4 > From: mathog@seqaxp.bio.caltech.edu (David Mathog) > Newsgroups: comp.os.vmsn  > Subject: Re: VMS 7.3 wish list  > Date: 14 Jul 2000 16:18:15 GMT > f > In article <20000713210053.29959.00000222@ng-md1.aol.com>, dashw459@aol.comeatspam (Doug W.) writes:M > >VMS is an exceptional operating system.  However, even the most entrenchedr7 > >supporter probably would like to see a few changes.   > * > Actually, my change list is rather long. >  > > With VMS 7.3 underR > >development, perhaps now is a good time to make requests.  No one likes to hear9 > >a squeaking wheel, but squeaking just might help VMS.   > = > Hope springs eternal, squeak away.  Just don't expect much.u > L > Anyway, as a small but useful step towards a bit more restraint in the OS,L > and better compatibility with other OS's how about at 7.4 simplify the useG > of text file types, so that they all default to stream-lf.  Right nowlC > consider the files produced by this common sequence of commands: o >  >   $ c_program -out killme.txte >   $ create killme2.txt" >   $ open/write ofil: killme3.txt >   $ close ofil:  > 6 > Three files are produced, and these are their types: > J >  name                      Record Format               Record AttributesH >  killme.txt                stream-LF                   carriage-returnH >  killme2.txt               variable                    carriage-return> >  killme3.txt               variable-with-fixed-control print > + One trick in case 3 is to do the following:f      $ create killme3.txte"    $ open /append ofil killme3.txt  > (I've never used the colon in an open or close statement, BTW)  L > What advantage is there in having so many different types of text files?  @ > The one that I can see is that you can sometimes coerce a fileB > transferred improperly to be recognized as a text file via a SETG > FILE/ATTR=RFM:STM. So you can get rid of the extra CRs, for instance,-. > without having to read and rewrite the file. > I > But if you're creating and using the text files _locally_, why use more J > than one text format?   We're always giving Unix heat for having crypticK > commands  - but really the difficulties those cause pale in comparison toqL > the complications that these semicompatible text file types present.  JustM > try to explain to nontechnical users why one text file can be sorted easilycH > and another cannot, or why APPEND works smoothly with some text files, > while for others it does:  >   > $ append foobar.txt killme.txtp > %APPEND-W-INCOMPAT, USRDISK:[USERS.MATHOG]FOOBAR.TXT;1 (input) and USRDISK:[USERS.MATHOG]KILLME.TXT;2 (output) >  have incompatible attributesa > J Yeah, but that's just a warning, and always has been AFAICR. I have in theI past used a combination of the create then open/append or just simply EDTe to get around that.t  G > And it isn't just nontechnical users who are affected.  Since in some L > instances if there is a preexisting file of a given name the newly createdN > higher numbered version will pick up its RMS organization from the existing K > file I occasionally encounter text file incompatibility problems like the < > one above in DCL procedures that normally work correctly.  > M > In particular, the two VARIABLE record formats are a real pain to share viaRJ > NFS or SMB. As viewed from Unix or Windows the first one has two "extra"M > bytes at the front of each line and no terminator, the latter has four suchiG > bytes and no terminator.  The only way to safely move them to anotherrL > system is to use something like ASCII FTP - which if you're going to Unix,1 > converts them to stream-lf on that end anyway. v > H > However, if everything is to make stream-lf by default, then how aboutI > FINALLY making SORT, TYPE, and the rest of the standard utilities smarttF > enough to handle stream-lf properly?  Users should not need to set a: > logical to force SORT to ignore the nonsensical C RTL's  >  >       Longest Record: 32767<  I Now that is a very valid complaint. I am told that a better way is to usedL a different syntax in C to write output files in the first place (don't ask,I I'm not a C expert), but of course when porting stuff, your point stands.e  I I recently had a developer trying to sort a 5,000 block file and SORT ran 9 out of space on a disk with 20,000,000 free blocks on it.pJ Whilst EDT provided the quick and dirty solution, the better solution was:  G --------------------start of DCL -------------------------------------- ) $! take the fdl definition from SYS$INPUTi0 $ CONVERT /FDL=SYS$INPUT  infile.dat outfile.dat FILE'      ORGANIZATION            sequentialn   RECORD,      CARRIAGE_CONTROL        carriage_return%      FORMAT                  variable  $ ! Convert Job done, now sort: + $ SORT outfile.dat *.*        ! do the sorteH ----------------------end of DCL ---------------------------------------     >  > and  > " >    $ type/tail streamlf_file.txt > G > should be able to work properly on a large stream-lf file and not do:b >  > $ type/tail SWISSPROT.SEQ;1eK > %TYPE-W-OPENIN, error opening MSCDISK:[SWISSPROT]SWISSPROT.SEQ;1 as inpute: > -SYSTEM-E-UNSUPPORTED, unsupported operation or function- > -RMS-F-ORG, invalid file organization valuea > L > I find this case particularly annoying - TYPE can certainly tell that the 4 > file type is stream-lf, then it can look up        >  >   End-of-File VBN: 85205,  >   Offset: %X'0093' > K > and work backwards from there.  Pat Rankin's EXTRACT/tail can handle this J > file type, and transfer the exact same file to a Unix system and "tail" J > will have no problem with it.  Back when we used to have POSIX installedK > I used to use the "tail" from that for these sorts of operations - and itC > worked just fine.  H > I > Can you imagine the criticism we would heap upon any other OS that had tJ > these sorts of ridiculous glitches - a SORT that chokes on trivial text M > files and a "tail" that won't tail a large file - the only kind you really v > need it for??? > L > Note that I'm not saying "get rid of all these text file types" - VMS willK > have to continue to support them until the last version ships.  I'm only oJ > saying that a single default text file type would be preferable to the N > we have now. > K I am afraid I cannot agree to the idea of the default type being stream-lf.tJ Apart from the probability it would break too many things the purist in meM cannot stand this idea of wasting cpu cycles scanning strings for an lf (yes,pN we're back to the null-terminated string subject again). Besides which, I likeR the idea of having binary data in records, which totally precludes lf termination.  P As to SORT, TYPE, EDT, TPU (to name just a few) supporting stream-lf I do agree. ___s
 Paul Sture Switzerlandp   ------------------------------   Date: 15 Jul 2000 23:57:17 CDT= From: wayne@tachysoft.xxx.293778.killspam.0223 (Wayne Sewell)   Subject: Re: VMS Pascal question. Message-ID: <Q$186II6iufS@tachxxsoftxxconsult>   In article <rdeininger-1507001142270001@user-2ivebf7.dialup.mindspring.com>, rdeininger@mindspring.com (Robert Deininger) writes:eo > In article <4BYuMN2WwauR@tachxxsoftxxconsult>, wayne@tachysoft.xxx.293778.killspam.0223 (Wayne Sewell) wrote:p >  > Q >> Well, yes and no.  As mentioned above, it is actually written in WEB (predates L >> and is unrelated to the world wide web), which is a higher-level languageN >> including code *and* documentation for the program.  A WEB program includesN >> both Pascal and TeX source.  You run the WEAVE processor against the sourceL >> file to get a TeX document, which becomes the documentation.  You run theQ >> TANGLE processor against the same source file to get a Pascal source, which isfP >> then compiled to be the executable code.  It is the one system where the code: >> and documentation are *guaranteed* to be in synch.  :-) >> h >> .; >> > with full intentions of multi-platform portability... h >> sP >> A lot of that is actually provided by WEB rather than Pascal.  WEB contains aQ >> mechanism called "change files", which contain implementation-specific stuff. iN >> A change file basically says "replace particular chunks of code in the mainN >> file with these other chunks".  Both WEAVE and TANGLE merge the change fileK >> into the main file on the fly, so you can create implementation-specific Q >> executables.  You would basically have a vms change file, a linux change file,e >> etc.s >> > >>   >> nP >> I would say see my book on the topic (Weaving a Program: Literate ProgrammingN >> in WEB), but it's been out of print for a few years and is a little hard to >> come by.  :-) >   I > I never heard of this book.  Was it promoted by the old Digital stealthb >marketing division? u    P No, can't blame them for this one.  Van Nostrand Reinhold stealth marketing. :-)  0 It is mentioned in the Literate Programming FAQ.  ( > What's the status of WEB these days?    K I am not sure.  I haven't worked with it for many years.  Again, if you aresM interested, the literate programming FAQ is the place to start.  I don't knowm@ where it is archived these days, but the pertinent newsgroup is I comp.programming.literate.  You should be able to track down the faq fromo there.  ' >Could I find a VMS version somewhere?    E If you can find Tex, you can typically find WEB and Metafont with it.d  M The TeX on the freeware cdrom appears to contain tangle and weave.  These tworL programs, plus the webmac.tex file containing the WEB TeX macros, *are* web.  O > Are there dialects available that work with languages other than Pascal?  AdaS > perhaps?  Fortran?    F I think there was a fortran version.  There are several C versions.  IM personally developed a Modula-2 version for the book.   Even worked out a wayoK to derive both the definition module and the implementation module from the)O same MWEB source file.   The TANGLE for MWEB equivalent was called MANGLE.  :-)o  1 > I _like_ WEB, but I've never had it available!     Get the freeware cd and you do!   1 > I've often wondered why WEB did not catch on.  o   Me too.    >I sadly conclued that too manyrQ > programmers are just too lazy.  The growth of c, oonix, and microsoft-certified O > quality has only reinforced my opinion.  Writing Knuth-quality code is hard > H > work, and most folks can't be bothered.  (Many exceptions reading thisK > newsgroup, I trust!) >  > TeX: The Program should be required study in CS P > programs.  Instead, kids are getting CS degress these days without reading (or3 > writing) many programs longer than 2 pages. >  > >  L The computer world has gone to shit in many ways, mostly due to billy gates.   >Sigh.  What happened to the > Good Old Days? :-)   Good question.   --  O ===============================================================================hM Wayne Sewell, Tachyon Software Consulting  (281)812-0738  wayne@tachysoft.xxx8: http://www.tachysoft.xxx/www/tachyon.html and wayne.html  K change .xxx to .com in addresses above, assuming you are not a spambot  :-)bO ===============================================================================uO Otter, on dining with Bluto:"It's perfectly safe if you keep your arms and legsl 			away from his mouth."   ------------------------------  % Date: Sun, 16 Jul 2000 20:08:10 +1000n% From: Tezza <tezza@hunterlink.net.au>FC Subject: vms$common - syscommon problems after retoring system disks8 Message-ID: <t513nss9jrt94dkq7l1vovftmnlb9i381c@4ax.com>  D I have a problem that occurred after backing up an Alpha system disk( and restoring it to another test system.  A The original system was a DEC 4000 running Alpha OpenVMS V6.2-1h1t? booted from the CD ROM.  I backed up the disk using the commandr3 $backup/image/rewind dkb100: mkd500:sysdsk.bck /logw
 /ignore=label   E I then restored the backup to another similar system which was bootedaD off an OpenVMS V7.2-1 CD ROM.  I restored the disk using the command  $backup/image mkc100: dkb0: /log  @ An attempt to boot the second system off the newly restored diskD failed as the file sysboot.exe could not be found.  After once againD booting the system off the CD ROM I mounted the restored system disk@ and found that the sysbot.exe file was there but the directories4 vms$common returned file not found when doing a $dirC dkb0:[000000]*.dir, I then went further down the directory tree anda0 found that sycommon.dir returned the same error.  F I then rebooted the system off the OpenVMS V6.2-1h1 CD ROM and did the@ restore again and this time those directory entries were created	 correctlyi  D Can someone tell me why this didn't work as expected when the systemB was restored using the OpenVMS V7.2-1 CD ROM ?  Is this a bug or a& restriction that I didn't know about ?     --     Bye, Terry   ' terry.whitford@hunterlink.net.au [home]n  % terry.whitford@steggles.com.au [work]    ------------------------------  % Date: Sun, 16 Jul 2000 07:30:32 -0400e2 From: "Richard B. Gilbert" <DRAGON@compuserve.com>C Subject: vms$common - syscommon problems after retoring system diskt7 Message-ID: <200007160730_MC2-AC72-B4E4@compuserve.com>m  C         It is a bug!  It has been reported here before but you haveeF provided more detail than I have seen in the other reports.  Somebody,J between V6.2 and V7.2, screwed up BACKUP's handling of Alias files and/or=   directories.  H         Hoff and Andy Goldstein are supposedly looking into it.   If youJ have software support, you should complain vigorously!!!!    (Hoff/Andy: =  ! have you found out anything yet?)s  J         Try USING BACUP /NOALIAS both to make and to restore the backup. =  J It is "highly recommended".  We have reports that that doesn't work eithe= r 7 but confirmation one way or the other might be helpful.d    8 Message text written by INTERNET:tezza@hunterlink.net.auE >I have a problem that occurred after backing up an Alpha system disk:( and restoring it to another test system.  A The original system was a DEC 4000 running Alpha OpenVMS V6.2-1h1e? booted from the CD ROM.  I backed up the disk using the commandh3 $backup/image/rewind dkb100: mkd500:sysdsk.bck /log- /ignore=3Dlabel,  E I then restored the backup to another similar system which was bootedjD off an OpenVMS V7.2-1 CD ROM.  I restored the disk using the command  $backup/image mkc100: dkb0: /log  @ An attempt to boot the second system off the newly restored diskD failed as the file sysboot.exe could not be found.  After once againD booting the system off the CD ROM I mounted the restored system disk@ and found that the sysbot.exe file was there but the directories4 vms$common returned file not found when doing a $dirC dkb0:[000000]*.dir, I then went further down the directory tree and-0 found that sycommon.dir returned the same error.  F I then rebooted the system off the OpenVMS V6.2-1h1 CD ROM and did the@ restore again and this time those directory entries were created	 correctly2  D Can someone tell me why this didn't work as expected when the systemB was restored using the OpenVMS V7.2-1 CD ROM ?  Is this a bug or a& restriction that I didn't know about ?   <I   ------------------------------   End of INFO-VAX 2000.395 ************************