1 INFO-VAX	Mon, 03 Apr 2006	Volume 2006 : Issue 185       Contents:$ Re: Device stuck in MntVerifyTimeout Re: DVD+RW drives on Alpha 8.x Re: DVD+RW drives on Alpha 8.x HSX Cache Size Re: Intel to sell itanium?6 Re: looking for used DEC hardware (D,NL,B,UK,DK,S,N,F)6 Re: looking for used DEC hardware (D,NL,B,UK,DK,S,N,F)) Medusa V7 with Decwindows and Vax VMS 5.x - Re: Medusa V7 with Decwindows and Vax VMS 5.x - Re: Medusa V7 with Decwindows and Vax VMS 5.x . Re: Opinion: I was just trying to sell OpenVMS. Re: Opinion: I was just trying to sell OpenVMS. Re: Opinion: I was just trying to sell OpenVMS Remvoing LAT Messages  Re: Remvoing LAT Messages  Re: Remvoing LAT Messages  Re: VAX 7000 series / Wanted:FreeWare or Commercial CORBA for OpenVMS 3 Re: Wanted:FreeWare or Commercial CORBA for OpenVMS   F ----------------------------------------------------------------------   Date: 3 Apr 2006 07:35:54 -0500  From: briggs@encompasserve.org- Subject: Re: Device stuck in MntVerifyTimeout 3 Message-ID: <1FtX9iLvDbqi@eisner.encompasserve.org>   [ In article <442D995F.EA7B556@teksavvy.com>, JF Mezei <jfmezei.spamnot@teksavvy.com> writes: ! > briggs@encompasserve.org wrote: L >> If memory serves, the effect of $ DISMOUNT /ABORT is to abort any current  >> I/O operations on the drive.  > C > In this particular case, it will warn you that there is already a ' > pending dismount and not do anything.  > I > You can't do a SHOW DEV/FILES on the disk because it is in mount verify   > timeout with dismount pending.  B I believe that it will work but show you no file names.  It is theB display of file names that requires disk access.  If you are afterE processes with open files, it will help you identify those processes.   @ You are certainly correct that it will not help you identify the+ names of any installed files on the volume.   E While the device is in mount verify but not yet timed out, $ SHOW DEV ? /FILES will hang.  (Not a good thing if you're working from the B console terminal, OPA0:).  After mount verification has timed out, it should no longer hang.   * > But if you know the exact file names youH > can INSTALL DELETE them. (or INSTALL PURGE , but then the rest of your< > system is also deinstalled and you might as well rebooot).   > That was oneP > of the main reasons for my suggestion some time ago of a INSTALL PURGE/DEVICE= > C >> What the OP needs to do first is to identify the installed files ? >> ($ INSTALL LIST) and then uninstall them ($ INSTALL REMOVE).  > H > LIST hangs because the drive is not accessible from the system's point0 > of view. (at least this is how I remember it).  J I've written scripts that parsed the result of $ INSTALL LIST to determineH the file names to $ INSTALL REMOVE.  (Or $ INSTALL DELETE -- I no longer: remember which one is appropriate).  Those scripts worked.  D It would not surprise me if $ INSTALL LIST were to hang when used onD a device for which mount verification was still pending (had not yet timed out).    ------------------------------  $ Date: Mon, 3 Apr 2006 12:56:16 +0200? From: "Eberhard Heuser-Hofmann" <vaxinf@chemie.uni-konstanz.de> ' Subject: Re: DVD+RW drives on Alpha 8.x 0 Message-ID: <001501c6570d$3b887db0$05072286@vg2>   Tom   M I saw a similar effect with a HP dvd640i drive. There is only one "solution"   so far: F install a PCI-IDE-controller and load the dqdriver for the controller.E You cannot boot from this DVD drive but you can read and write if the 
 system is up.    Hope this helps  Eberhard   --- Original Message -----  # From: "Tom Linden" <tom@kednos.com>  To: <Info-VAX@Mvb.Saic.Com> & Sent: Saturday, April 01, 2006 3:00 AM# Subject: DVD+RW drives on Alpha 8.x     K >I have a Plextor 716A which seems to work in an AXP 8.2 system although I   >have  > yet tried writing  >  > FREJA> sho sysJ > OpenVMS V8.2  on node FREJA  31-MAR-2006 16:55:24.36  Uptime  8 20:42:03 > FREJA> sho dev/full $7$DQA0: > H > Disk $7$DQA0: (FREJA), device type PLEXTOR DVDR   PX-716A, is online,  > file- K >     oriented device, shareable, served to cluster via MSCP Server, error  	 > logging  >     is enabled.  > ; > Just tried installing a Plextor 740A in an AXP 8.3 system  >  > ODIN> sho sys I > OpenVMS F8.3  on node ODIN  31-MAR-2006 16:57:29.29  Uptime  0 00:28:30  > ODIN> sho dev/full $6$DQA0:  > L > Disk $6$DQA0: (ODIN) is online, file-oriented device, shareable, served to8 >     cluster via MSCP Server, error logging is enabled. >  > Both systems are XP1000's  > D > Is there an updated list of supported devices?  Is there a driver  > available  > to support this device?  >  > Tom    ------------------------------  % Date: Mon, 03 Apr 2006 06:47:02 -0700 # From: "Tom Linden" <tom@kednos.com> ' Subject: Re: DVD+RW drives on Alpha 8.x ) Message-ID: <op.s7fpwoemzgicya@hyrrokkin>    Hi Eberhard,  H This is on an XP1000 which comes with the Toshiba IDE CDROM.  I have hadF 4 fail, and as they do I replace them with DVD drives.  The XP1000 hasI an onboard IDE controller.  Anyway, I put the 740 in a W2K box and bought H another 716A off ebay.  I downloaded your software for trial in FebruaryG but haven't had a chance to try it yet, been reorganizing and upgrading  my cluster.    Tom < n Mon, 03 Apr 2006 03:56:16 -0700, Eberhard Heuser-Hofmann  & <vaxinf@chemie.uni-konstanz.de> wrote:   >  > Tom  > E > I saw a similar effect with a HP dvd640i drive. There is only one    > "solution" so far:H > install a PCI-IDE-controller and load the dqdriver for the controller.G > You cannot boot from this DVD drive but you can read and write if the  > system is up.  >  > Hope this helps 
 > Eberhard > @ > --- Original Message ----- From: "Tom Linden" <tom@kednos.com> > To: <Info-VAX@Mvb.Saic.Com> ( > Sent: Saturday, April 01, 2006 3:00 AM% > Subject: DVD+RW drives on Alpha 8.x  >  > L >> I have a Plextor 716A which seems to work in an AXP 8.2 system although  	 >> I have  >> yet tried writing >> >> FREJA> sho sys K >> OpenVMS V8.2  on node FREJA  31-MAR-2006 16:55:24.36  Uptime  8 20:42:03  >> FREJA> sho dev/full $7$DQA0:  >>J >> Disk $7$DQA0: (FREJA), device type PLEXTOR DVDR   PX-716A, is online,   >> file-G >>     oriented device, shareable, served to cluster via MSCP Server,    >> error logging >>     is enabled. >>< >> Just tried installing a Plextor 740A in an AXP 8.3 system >> >> ODIN> sho sysJ >> OpenVMS F8.3  on node ODIN  31-MAR-2006 16:57:29.29  Uptime  0 00:28:30 >> ODIN> sho dev/full $6$DQA0: >>L >> Disk $6$DQA0: (ODIN) is online, file-oriented device, shareable, served   >> to 9 >>     cluster via MSCP Server, error logging is enabled.  >> >> Both systems are XP1000's >>F >> Is there an updated list of supported devices?  Is there a driver   >> available >> to support this device? >> >> Tom >    ------------------------------   Date: 3 Apr 2006 08:07:35 -0700 ! From: richard.anderson@canada.com  Subject: HSX Cache Size C Message-ID: <1144076855.712068.228050@v46g2000cwv.googlegroups.com>   C Is there a sizable advantage to increasing one's cache from 32Mb to  64Mb or even 128 Mb?   ------------------------------   Date: 3 Apr 2006 09:17:38 -0700 - From: "Andrew" <andrew_harrison@symantec.com> # Subject: Re: Intel to sell itanium? C Message-ID: <1144081058.170063.210770@u72g2000cwu.googlegroups.com>    Karsten Nyblad wrote:   G > I do not know of any systems designed for business applications which E > are capable of executing more than 128 processes or threads in true I > parallel.  I think it is a dangerous assumption that OSes, DBMSes, etc. A > will scale beyond 128 processes and threads.  That is just 4 T1 G > processors.  (Yes I do not that the current T1 processors can only be F > used in one socket systems.)  It might be possible to get DBMSes andG > OSes to scale even more, but that will not happen in the near future.   F You seem to be confusing what a platform (OS/Hardware) can support and3 what the application/OS infrastructure can support.   C True there are not that many OS/Platform combinations which support G enough execution units to allow 128 simultaneous hardware threads to be G executed however there are a few. Solaris on SPARC does and Sun/Fujitsu B have the benchmark results to prove it in the commercial space forF Java/J2EE/DBMS workloads.  Itanium/Linux does in the HPC space and SGIC also has the benchmark results to prove this as well. You also have E specialised environments to support Java deployments for example Azul E have a custom developed Java deploment environment which supports 384  hardware threads.   F >From and application perspective there is nothing to stop Oracle, DB2F and most Java deployment environments from scaling to support 100's of? hardware threads. The same applies to web servers, fileservers,  messaging, authentication etc.  G In addition most modern OS's now support some form of software/hardware C partitioning, Solaris 10.x Zones and the upcoming T1 virtualisation C layer for the Sun T series systems which allow you to host multiple C different OS's or personalities in these you can run separate apps. B This allows you to consolidate workloads into a single virtualisedB server with each indevidual workload having a guaranteed number of hardware threads to support it.    Regards  Andrew Harrison    ------------------------------   Date: 3 Apr 2006 10:22:39 -0700 ' From: "syslost" <wm.reynolds@gmail.com> ? Subject: Re: looking for used DEC hardware (D,NL,B,UK,DK,S,N,F) C Message-ID: <1144084959.857077.162940@i40g2000cwc.googlegroups.com>   " I have about 15 rz26s and 30 rz28s  D The company I work for is going to be replacing them, Ill see what I
 can work out.    ------------------------------  % Date: Mon, 03 Apr 2006 10:42:32 -0700 # From: "Tom Linden" <tom@kednos.com> ? Subject: Re: looking for used DEC hardware (D,NL,B,UK,DK,S,N,F) ) Message-ID: <op.s7f0s6gczgicya@hyrrokkin>   J On Mon, 03 Apr 2006 10:22:39 -0700, syslost <wm.reynolds@gmail.com> wrote:  $ > I have about 15 rz26s and 30 rz28s > F > The company I work for is going to be replacing them, Ill see what I > can work out.  > 8 Just out of curiosity, with what are you replacing them?   ------------------------------  $ Date: Mon, 3 Apr 2006 10:26:21 +0200% From: "nst" <NorbertATstadlersDOTnet> 2 Subject: Medusa V7 with Decwindows and Vax VMS 5.x' Message-ID: <4430dc31@news.arcor-ip.de>   M We do have Medusa 6 (Yes its six) under VWS but in order to convert our .SHE  L files we need a V7 with Decwindows. There are appr. 70k files which must be L converted. Our plan is to use the x-client on VMS and the  x-server on a pc.I Question: do you have a Medusa 7 kit available? Maybe also a keyfile. We  = have a KEYFILE.BIN but I am not sure if it will work with V7.  Any help is appreciated,   Norbert    ------------------------------  $ Date: Mon, 3 Apr 2006 08:39:01 -0400* From: "FredK" <fred.nospam@nospam.dec.com>6 Subject: Re: Medusa V7 with Decwindows and Vax VMS 5.x, Message-ID: <44311765$1@usenet01.boi.hp.com>  0 "nst" <NorbertATstadlersDOTnet> wrote in message! news:4430dc31@news.arcor-ip.de... I > We do have Medusa 6 (Yes its six) under VWS but in order to convert our  .SHEJ > files we need a V7 with Decwindows. There are appr. 70k files which must beJ > converted. Our plan is to use the x-client on VMS and the  x-server on a pc. J > Question: do you have a Medusa 7 kit available? Maybe also a keyfile. We? > have a KEYFILE.BIN but I am not sure if it will work with V7.  > Any help is appreciated, > 	 > Norbert  >   I I assume this is Medusa the CAD application (although I have no idea what I Medusa "7" is.  I'm not sure you will find a lot of specialized help here D (but I might be suprised).  Try www.medusa4.com - their FAQ has someJ information on keyfiles/licenses.  They also appear to have downloads etc.   ------------------------------  $ Date: Mon, 3 Apr 2006 18:27:24 +0200% From: "nst" <NorbertATstadlersDOTnet> 6 Subject: Re: Medusa V7 with Decwindows and Vax VMS 5.x) Message-ID: <44314cfb$1@news.arcor-ip.de>   6 "FredK" <fred.nospam@nospam.dec.com> wrote in message & news:44311765$1@usenet01.boi.hp.com... >  > F Fred, when PTC sold Medusa in 2001/2002 to Schroer I think all legacy  implementations got lost.    Norbert    ------------------------------   Date: 3 Apr 2006 04:34:08 -0700 - From: "Andrew" <andrew_harrison@symantec.com> 7 Subject: Re: Opinion: I was just trying to sell OpenVMS B Message-ID: <1144064048.187281.16580@e56g2000cwe.googlegroups.com>   GreyCloud wrote: > Michael Kraemer wrote: >  > > Bob Koehler schrieb: > >  > >>H > >>    While VMS is not immune to social engineering attacks, I'm quiteC > >>    sure none of my VMS users knows the administrator password.  > >> > > K > > Well, the VMS boxes (VAX and alpha) I have "inherited" for hobbyist use  > > were quite easy to "crack". C > > Once you have access to the console you can apply the published H > > procedure to reset the SYSTEM password and the box is at your hands.I > > I didn't even need original OS media for that (as I would have needed  > > e.g. for AIX). > >  > J > Yet no one could crack VMS at the Las Vegas DEFCON trials.  How is that? >   B As you know none of the "hackers" attempting to break into OpenVMSC during the DEFCON session had any experience of OpenVMS most didn't  even know what it was.  & Hardly a good test or a good example.    Regards  Andrew Harrison    ------------------------------   Date: 3 Apr 2006 07:16:34 -0500 ; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) 7 Subject: Re: Opinion: I was just trying to sell OpenVMS 3 Message-ID: <vCCd+OE2w0Lc@eisner.encompasserve.org>   V In article <495onqFnar1jU1@individual.net>, bill@cs.uofs.edu (Bill Gunshannon) writes: >   I > Because nobody there had any experience with VMS.  Because most of them K > had probably never even heard of it.  And mostly because they really just N > didn't give a damn about VMS.  Now, can we finally put this canard to rest!! >   G    No.  Of course not.  DEFCON9 didn't pronouce VMS to be "something we A    never heard of" they decided to call it "Cool and Unhackable".    ------------------------------  * Date: Mon, 3 Apr 2006 15:13:16 +0000 (UTC) From: david20@alpha2.mdx.ac.uk7 Subject: Re: Opinion: I was just trying to sell OpenVMS ) Message-ID: <e0re2c$m0d$1@news.mdx.ac.uk>   V In article <49agmcFnob1fU2@individual.net>, bill@cs.uofs.edu (Bill Gunshannon) writes:> >In article <443000d1$0$60779$157c6196@dreader1.cybercity.dk>,/ >	Karsten Nyblad <nospam@nospam.nospam> writes:  >> Bill Gunshannon wrote: J >>> Stock brokers are not hackers.  Hackers do not have INTERNET access toJ >>> the machines that actually process the transactions.  Come to think of& >>> it, neither do the stock brokers!! >>  7 >> They are smart enough to be capable of learning it.   > G >Possibly, and the average shade-tree mechanic is capable of installing : >a Jensen supercharger on his street-car.  But they don't. > G >>                                                     All it takes is  F >> some criminal organization putting hackers and some crocked trader 
 >> together.   > E >If you can subvert an insider, he doesn't need to "hack the system". A >There have been a number of recen "accidents" reported where bad D >transactions resulted in multi-million dollar mistakes.  When theseD >happened, the money didn't disappear.  Someone lost on the deal and) >someone else gained.  No hacking needed.  > E >>           Of course the stock exchanges know this and build their  F >> systems such that they can not be hacked by a trader.  However, at 3 >> requires an OS, firewalls, etc. of high quality.  > E >No. all it requires is that there be no direct outside access.  Once D >you breech physical security (usually using social engineering, notI >technology) all bets are off.  And even VMS can't protect you from that!  >    Rubbish.M Insiders have been a major threat to computer systems since long before most  ' systems were connected to the internet.   
 David Webb Security team leader CCSS Middlesex University         >bill  >  >-- K >Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolves E >bill@cs.scranton.edu     |  and a sheep voting on what's for dinner.  >University of Scranton   | B >Scranton, Pennsylvania   |         #include <std.disclaimer.h>      ------------------------------   Date: 3 Apr 2006 06:20:50 -0700 + From: "Shawn M." <shawnm1964@sbcglobal.net>  Subject: Remvoing LAT MessagesB Message-ID: <1144070450.562323.36650@i40g2000cwc.googlegroups.com>   Hi all,   G I have an Alpha Server running OpenVMS 7.2-1 which used to use LAT.  We B have since turned LAT off a long time, but when I reboot I see the? following messages and want to remove whatever is calling them.    Thanks,    Shawn   " Message from user LATACP on ALPHA1 LATACP initialized       %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values %LAT-W-INVCMD, invalid commandG -CLI-W-VALREQ, missing qualifier or keyword value - supply all required  values$ %SET-W-NOTSET, error modifying LTA1:" -SYSTEM-F-HANGUP, data set hang-up$ %SET-W-NOTSET, error modifying LTA2:" -SYSTEM-F-HANGUP, data set hang-up$ %SET-W-NOTSET, error modifying LTA3:" -SYSTEM-F-HANGUP, data set hang-up$ %SET-W-NOTSET, error modifying LTA4:" -SYSTEM-F-HANGUP, data set hang-up$ %SET-W-NOTSET, error modifying LTA5:" -SYSTEM-F-HANGUP, data set hang-up$ %SET-W-NOTSET, error modifying LTA6:" -SYSTEM-F-HANGUP, data set hang-up$ %SET-W-NOTSET, error modifying LTA7:" -SYSTEM-F-HANGUP, data set hang-up$ %SET-W-NOTSET, error modifying LTA8:" -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA17: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA18: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA19: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA20: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA21: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA22: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA23: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA24: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA33: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA34: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA35: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA36: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA37: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA38: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA39: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA40: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA49: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA50: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA51: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA52: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA53: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA54: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA55: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA56: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA65: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA66: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA67: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA68: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA69: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA70: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA71: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA81: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA82: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA83: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA84: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA85: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA86: " -SYSTEM-F-HANGUP, data set hang-up% %SET-W-NOTSET, error modifying LTA87: " -SYSTEM-F-HANGUP, data set hang-up   ------------------------------   Date: 3 Apr 2006 07:01:44 -0700 $ From: "Wilm" <w4.boerhout@planet.nl>" Subject: Re: Remvoing LAT MessagesC Message-ID: <1144072904.560325.301520@t31g2000cwb.googlegroups.com>   J >>>I have an Alpha Server running OpenVMS 7.2-1 which used to use LAT.  WeE >>>have since turned LAT off a long time, but when I reboot I see the B >>>following messages and want to remove whatever is calling them.  5 1. What exactly did you do when you "turned LAT off"? E 2. I suspect your startup stream still calls an old LAT command file. 9 Apart from the obvious SYS$MANAGER:SYSTARTUP_VMS.COM, all C SYS$MANAGER:SY*.COM files should be inspected for the phrase "LAT". E 3. The error %SET-W-NOTSET, error modifying LTA87: ,-SYSTEM-F-HANGUP, D data set hang-up result from SET TERM LTAnnnn: command, so all above1 files should also be checked for the phrase "LTA"    HTH, /Wilm    ------------------------------   Date: 3 Apr 2006 06:59:30 -0700 3 From: "Ralf Gaertner" <ralf.gaertner@t-systems.com> " Subject: Re: Remvoing LAT MessagesC Message-ID: <1144072770.475386.223470@u72g2000cwu.googlegroups.com>   E Disable the call of SYS$STARTUP:LAT$STARTUP.COM from one of the usual F startup procedures (usually SYS$MANAGER:SYSTARTUP_VMS.-COM) and remove SYS$MANAGER:LAT$SYSTARTUP.COM    ------------------------------   Date: 3 Apr 2006 02:36:22 -0700  From: etmsreec@yahoo.co.uk Subject: Re: VAX 7000 seriesC Message-ID: <1144056982.415002.160330@e56g2000cwe.googlegroups.com>    Timothy Stark wrote: > L >Is it possible to emulate VAX 7000 that supports different two processors -L >NVAX+ and Alpha 21064?  Because I recently noticed that Charon-VAX provides >VAX 6000 series emulation.  >   G There is an article in the OpenVMS Tech Journal that explains that they F went for the 6000 series because it was much more straightforward than	 the 7000.   E In terms of conversion, I think you'll find it's the same chassis and F backplane, but some of the options that the VAX 7000 would support areG unsupported on the Alpha versions (whether as a DEC7000 or as an 8400). C  IIRC, the conversion kit was a SCSI controller and internal CD-ROM F drive, plus different CPUs and potentiall memory too.  The clock chipsC would have needed changing too, as they did on moving from speed to F speed in Alpha processors (the 625MHz had a different clock board than+ the one two speed hikes down, for example).    ------------------------------   Date: 3 Apr 2006 01:44:28 -0700 + From: "Ruslan R. Laishev" <zator@yandex.ru> 8 Subject: Wanted:FreeWare or Commercial CORBA for OpenVMSC Message-ID: <1144053868.826202.130880@u72g2000cwu.googlegroups.com>   
 Hello All!  D I have got a task to implement a provisioning interface from privateF company Billing system under OpenVMS to SDHLR (Lucent), I  looking for? freeware or commercial CORRBA implementation for OpenVMS/Alpha.   $ Thanks for any pointers an oppinion.   ------------------------------  $ Date: Mon, 3 Apr 2006 14:28:49 +0200/ From: "Johnny Willemsen" <jwillemsen@remedy.nl> < Subject: Re: Wanted:FreeWare or Commercial CORBA for OpenVMS6 Message-ID: <44311503$0$11069$e4fe514c@news.xs4all.nl>   Hi,   M See www.theaceorb.nl for a commercial sponsored activitiy to port ACE/TAO to   OpenVMS.   Regards,   Johnny Willemsen  7 "Ruslan R. Laishev" <zator@yandex.ru> wrote in message  = news:1144053868.826202.130880@u72g2000cwu.googlegroups.com...  > Hello All! > F > I have got a task to implement a provisioning interface from privateH > company Billing system under OpenVMS to SDHLR (Lucent), I  looking forA > freeware or commercial CORRBA implementation for OpenVMS/Alpha.  > & > Thanks for any pointers an oppinion. >    ------------------------------   End of INFO-VAX 2006.185 ************************                                                                                       IXORMOD    IXORMODA   IXORMODX   JUMP  	 JUMPLOCAL 
 JUMPSYMBOL LABEL  LAND   LANDC  LANDU  LBSET  LCVT   LENGTH	 LENGTHREF  LEQ    LEQP   LEQV   LITADDR    LITREF LNOT   LOG    LOG10  LOG2   LOR    LORC   LORU   LSBIT  LSS    LSSP   LVALUE LXOR   MACHOP1    MACHOP2    MAKEBP MAX    MEMBER MIN    MOD    MUL    MULH   MULMOD MULMODA    MULMODX    NEG    NEQ    NEQP   NONZERO    ORSKIP PALCALL    PAREN 	 PARMALLOC 
 PARMLENGTH PARMTEMP   PINDEX PMOD   POSTINCR  	 POSTINCRA 	 POSTINCRX  PREINCR    PREINCRA   PREINCRX   PWR    PWRO   PWRZ   REAL   REM    REMMOD REMMODA    REMMODX   	 REPLICATE 	 RESULTBUF 	 RESULTDYN 	 RESULTREG 	 RESULTSTK 	 RESULTTMP  RESULTTMPADR  
 RESULTTMPF RETURN	 RETURNDYN 	 RETURNREG 	 RETURNSTK  ROT    ROUND  SCALE  SCAST  SEARCH SEL    SELC   SELELSE    SELTHEN    SELU   SH SHL    SHLD   SHLMOD SHLMODA    SHLMODX    SHR    SHRA   SHRAMOD    SHRAMODA   SHRAMODX   SHRD   SHRMOD SHRMODA    SHRMODX    SIGNAL SIN    SIND   SINH   SIZE   SPLIT_FLUSH   
 SPLIT_LOAD SQRT   STKFRAME   STOP   STORE  STOREA STOREF STORES STOREV STOREX	 STOREX_IO  STOREZ SUB    SUBMOD SUBMODA    SUBMODX    SUBSCR SUBSET SUBSTR SUPERSET   SYMREF TAN    TAND   TANH   TEMPREF   	 TRANSLATE  TRUNC  UNSCALE    UNUSED_1  	 UNUSED_10 	 UNUSED_11 	 UNUSED_12 	 UNUSED_13 	 UNUSED_14 	 UNUSED_15 	 UNUSED_16 	 UNUSED_17 	 UNUSED_18 	 UNUSED_19  UNUSED_2  	 UNUSED_20 	 UNUSED_21 	 UNUSED_22 	 UNUSED_23 	 UNUSED_24 	 UNUSED_25 	 UNUSED_26 	 UNUSED_27 	 UNUSED_28 	 UNUSED_29  UNUSED_3  	 UNUSED_30  UNUSED_4   UNUSED_5   UNUSED_6   UNUSED_7   UNUSED_8   UNUSED_9   UPLINK USTRING    VBRANCH    VERIFY VLABEL VOID   VSTORE VSTOREA    VSTOREX    XCVT   ZEROBITS  N  (* 0   0* 1   8* 2   @* 3   H* 4   P* 5   X* 6   d* 7   p* 8   x* 9   * :   * ;   * <   * =   * >   * ?   * @   Ē* A   В* A   ܒ* B   * C   * D   * E   * F   * G   * H    * I   (* J   4* C   @* J   L* K   T* L   `* K   l* L   x* M   * N   * O   * P   * Q   * R   * S   * T   * U   ē* V   Г* W   ؓ* X   * Y   * Z   * [   * \   * ]   * ^   $* _   ,* `   4* a   <* b   D* c   L* d   X* e   `* f   h* g   t* h   |* i   * j   * k   * l   * m   * n   * o   * p   * q   Ȕ* r   Ԕ* s   * t   * u   * v   * w   * x   * y   * z   $* {   4* |   @* }   H* ~   P*    X*    `*    h*    p*    x*    *    *    *    *    *    *    *    ĕ*    ̕*    ԕ*    *    *    *    *    *     *    (*    4*    <*    D*    P*    \*    d*    l*    t*    |*    *    *    *    *    *    *    *    *    ̖*    ؖ*    *    *    *     *    *    *    *     *    ,*    4*    @*    L*    X*    `*    h*    p*    |*    *    *    *    *    *    *    *    ė*    ̗*    ؗ*    *    *    *    *    * 