1 INFO-VAX	Tue, 03 Jul 2001	Volume 2001 : Issue 365       Contents:0 AMD Supercomputer - The Phantom "growing" Menace& Re: Compaq replace AES/DSN with NT box Re: How to lock a kernel mutex Re: How to lock a kernel mutex RE: KZMSA support on VAX 7710 : Problems Creating ODBC Connections to RDB databases on vms  QBus TK50 controller -- got one?
 Server up? Some Questions About Backup  Re: The Alpha/IA64 Hybrid  Re: The Alpha/IA64 Hybrid  Re: The Alpha/IA64 Hybrid  Re: The Alpha/IA64 Hybrid  to 7.3 from 6.2  RE: VMS 7.3 experiences? Re: VMS V7.3 SPD Error  F ----------------------------------------------------------------------  % Date: Mon, 02 Jul 2001 14:24:17 -0300 ) From: fabio_compaq@ep-bc.petrobras.com.br 9 Subject: AMD Supercomputer - The Phantom "growing" Menace L Message-ID: <OFEE187D79.837EA101-ON03256A7D.005F8B42@ep-bc.petrobras.com.br>   Click at  2 http://www.theregister.co.uk/content/53/20117.html   Regards    FC   ------------------------------  * Date: Mon, 2 Jul 2001 11:43:51 +0000 (UTC)' From: david20@alpha1.mdx.ac.uk (D.Webb) / Subject: Re: Compaq replace AES/DSN with NT box + Message-ID: <9hpmpn$ffk$1@aquila.mdx.ac.uk>   _ In article <200107020636.IAA09029@sinet1.fom.fgan.de>, Rudolf Wingert <win@fom.fgan.de> writes:  >Hello,  > L >our security politic is, that there is no way from the inner net (intranet)L >to the outer net (internet). How will Compaq satisfy us? With an NT bridge?L >No, because we do not allow to bridge the two nets. So Compaq must look forH >an other way, or do Compaq say we stop service for you? The way via ex-K >changable media is mostly unpossible (there is no media between Wintel and  >Alpha for files >2.4 MB).   >  >TIA and regards Rudolf Wingert  >   O I have just spoken to someone from Compaq about this AES replacement and raised  the same issues of Security.  K The idea of an Internet connected NT box having access to our admin systems M is rather unsettling. This looks like Compaq once again not understanding the  Enterprise.   
 David Webb VMs and unix team leader CCSS Middlesex University   ------------------------------  # Date: Mon, 02 Jul 2001 11:11:38 GMT = From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-) ' Subject: Re: How to lock a kernel mutex 0 Message-ID: <009FE64E.B33810F0@SendSpamHere.ORG>  X In article <3b403336.2317221@news.force9.net>, mark@*NO*SPAM*techop.co.uk (Mark) writes:A >On Fri, 29 Jun 2001 13:48:38 GMT, system@SendSpamHere.ORG (Brian   >Schenkenberger, VAXman-) wrote: >  >Hi, >  >Thanks for the reply. > G >>SCH$LOCK{R/W}{_QUAD} has always done the trick for me.  If you intend H >>to use C, you'll want the call based routines SCH_STD$LOCK{R/W}{_QUAD}- >>and don't forget the SCH_STD$UNLOCK{_QUAD}.  > G >I can't find any documentation for these functions.  Do you know where ? >it can be found. It's not even mentioned in my "master index"!   I Master index?  I suspect you're reading the VMS documentation set.  These H are routines in the kernel and are not documented in the VMS doc. set.    I You can find these "documented" in the "OpenVMS Internals and Data Struc- F tures" manual -- a book orderable separate from the doc. set.  DigitalH Press (Butterworth Heineman) is the publisher.  I don't see anything butH the "Scheduling and Process Control" addendum/update available on the BHE web site.  This addendum/update, however, should cover what you need.   I Short of having the I&DS, the OpenVMS source listings CDs are the defini- G tive source for such routines and how to invoke them.  You also may get J some mileage out of searching the web for packages with use these routines- to learn how to invoke and use them properly.   H If you still find you need some pointers, drop me a private email.  See  the .sig for the address.  --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM              O city, n., 1. a place where trees are cut down and streets are named after them.    ------------------------------  # Date: Mon, 02 Jul 2001 11:25:21 GMT = From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-) ' Subject: Re: How to lock a kernel mutex 0 Message-ID: <009FE650.9DB90060@SendSpamHere.ORG>  o In article <3pMO1CXEqXx8@eisner.encompasserve.org>, Kilgallen@eisner.decus.org.nospam (Larry Kilgallen) writes: Y >In article <3b403336.2317221@news.force9.net>, mark@*NO*SPAM*techop.co.uk (Mark) writes: C >> On Fri, 29 Jun 2001 13:48:38 GMT, system@SendSpamHere.ORG (Brian " >> Schenkenberger, VAXman-) wrote: >>   >> Hi, >>   >> Thanks for the reply. >>  H >>>SCH$LOCK{R/W}{_QUAD} has always done the trick for me.  If you intendI >>>to use C, you'll want the call based routines SCH_STD$LOCK{R/W}{_QUAD} . >>>and don't forget the SCH_STD$UNLOCK{_QUAD}. >>  I >> I can't find any documentation for these functions.  Do you know where A >> it can be found. It's not even mentioned in my "master index"!  > 9 >Your master index covers only the VMS documentation set.  > H >For internals like this, you need the VMS Internals and Data StructuresI >book from Digital Press.  I believe the latest version comes in separate 	 >volumes.  > < >	http://www.openvms.compaq.com/openvms/books_internals.html > > >It can be purchased at your local corner technical bookstore.    > Sadly, this page contains a short blurb titled "What's Coming"  E       We've begun planning the next volume, which will consist of the F       Version 1.5 memory management chapters updated to the next majorG       release. We plan to add information on 64-bit addressing and very G       large memory support, as well as Galaxy-related memory management G       changes. Please send any suggestions for this volume and feedback .       on the V1.5 memory management chapters.   H I have been awaiting this addendum/update for some time now; however, inH the light of the top-level mismanagement decision to throw the baby out I with the bath water, I doubt much that this manual will even come to fru- H ition.  :(  This may be good for Ruth -- allowing her to spend more time, at her vacation (retirement?) home in Maine.   --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM              O city, n., 1. a place where trees are cut down and streets are named after them.    ------------------------------  % Date: Mon, 02 Jul 2001 23:16:20 +0100 5 From: "Steeples, Oliver" <Oliver.Steeples@compaq.com> & Subject: RE: KZMSA support on VAX 7710N Message-ID: <F498D199EDB12D468CD2C66680D308018B154A@reoexc04.emea.cpqcorp.net>   Hi,  	my sources say:  H "XMI to Narrow Single Ended/Differential SCSI-1/SCSI-2 Adapter for DEC = 7000< AXP or DEC 10000 AXP, AlphaServer 8400 and GS140 systems.=20  H The KZMSA I/O adapter is used in the XMI plug=ADin unit (PIU) of a DEC = 7000F AXP or DEC 10000 AXP system. The KZMSA allows I/O to tapes and disks = using G the SCSI (Small Computer Systems Interface) protocol. Compaq supplies =  the E BA655 SCSI disk and tape PIU for SCSI I/O devices in the system and =  expanderF cabinets of the DEC 7000 AXP and DEC 10000 AXP systems. Also used on = the & AlphaServer 8400 and GS140 XMI buses."  E So it looks like AXP only, not VAX.  My VAX 7700 SOC shows CI based =  storage B as the only option with no scsi HSx controllers allowed   As for = striping on " an HSZ40, yes a license is needed.   Regards, 	Oliver    -----Original Message-----C From: Jean-Francois Marchal [mailto:jean-francois.marchal@x9000.fr] $ Sent: Monday, July 02, 2001 10:44 AM To: Info-VAX@Mvb.Saic.Com " Subject: KZMSA support on VAX 7710     Hi all !  G I need no know if the KZMSA is supported on a VAX 7710 running VMS 6.2. G I can't find the info in the latest SOC I've found (they only reference 8 a KFMSA adapter). I it is supported, are two supported ?  I Will I need a license to use striping on a HSZ40 connected to the KZMSA =  ?    Cheers Jean-Fran=E7ois Marchal  X9000    ------------------------------  % Date: Tue, 03 Jul 2001 10:03:22 +1200 . From: Nivlesh Chandra <NChandra001@itc.gov.fj>C Subject: Problems Creating ODBC Connections to RDB databases on vms M Message-ID: <084681714A1BD511970B0002A560015F2D742B@exchange01.govnet.gov.fj>   F I had posted this question sometime earlier but I guess I was not very$ coherent. here is the question again  I I have rdb databases on VMS Alpha Machines. The version of rdb is DEC Rdb & V6.1-04 and the version of VMS is V6.0D Now what I want to do is to connect to the rdb database using a odbcL connection from a windows machine. Before this used to work but now for someL reason it does not. I do not have any manuals to work by and the person thatE had setup the odbc stuff previously has long gone without leaving any J documentation. This is of urgency since I have to get the ODBC connectionsK up as soon as possible. Would really appreciate it if someone could help me K figure out what is going on or better still point me to documentation which + I can follow to troubleshoot the problem...   + Your urgent help would be most appreciated.    Niv    ------------------------------  % Date: Mon, 02 Jul 2001 10:23:15 -0500 + From: Christopher Smith <csmith@amdocs.com> ) Subject: QBus TK50 controller -- got one? L Message-ID: <3B55D7F383B0D31197D9009027541CBF0D9D2028@cmiexch1.cmi.itds.com>   Hi guys.  I Single, Grey, Almighty MicroVAX II seeks working QBus TK50 controller for 6 long boot procedures, and the occasional image backup.  L I've actually just adopted this one.  Her name is Candy (really, she used toK work at a confectioner's ;).  Her hobbies are running MicroVMS 4.something, ( and talking to character cell terminals.  J Anyway, it seems that the tk50 controller that came with this one is shot,I and I'd like to find a working one.  Does anyone have one they could part  with?  Please let me know.   Regards,   Chris   ! Christopher Smith, Perl Developer  Amdocs - Champaign, IL   /usr/bin/perl -e '? print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n");  '       ------------------------------  % Date: Mon, 02 Jul 2001 09:53:01 -0700 ! From: Tom Linden <tom@kednos.com>  Subject: Server up? 9 Message-ID: <CIEJLCMNHNNDLLOOGNJIAEGNCOAA.tom@kednos.com>   = Haven't gotten any mail since early this morning.  Are we up?    ------------------------------  % Date: Mon, 02 Jul 2001 12:11:17 -0400 + From: John Eisenschmidt <jeisensc@aaas.org> $ Subject: Some Questions About Backup# Message-ID: <sb4064f5.072@aaas.org>   L During the short week I'm working on a system slated to go into production =C this summer. Today I'm working on backup, and I have some general = ( questions I'd like to throw out there...  K 1) I've read several places that when backing up a Shadow Set, one should = D dismount the Shadow Set, remount it with one disk, mount the other =L privately, and then take a backup. We're a 9 to 5 shop, and aside from the =F hypothetical problems of backing up a Shadow Set (it might not be in =L sync), is there any real prevailing reason against just backing it up like =L a stand alone disk? (BACKUP/MEDIA_FORMAT=3DCOMPACT/RECORD/VERIFY/IGNORE=3D(=? INTERLOCK,LABEL) DSA100:[000000...]*.*;* MKA600:DSA100.BCK/LOG)   G 2) This may sound stupider than my usual fare, but does anyone backup = I their System disk every night? I shut the system down and take an Image = H backup once a month - my thinking is that a running system has so many =+ open files you'll never get a clean backup.   H 3) ::SIGH:: Oracle. Now that my Oracle tablespaces are spread across a =K bunch of disks, let's pretend I want all of a single instance in a single = C save set. For a database called DB_FOO I have the following layout:    DSA100:[DB_FOO]  DSA200:[DB_FOO]  DSA300:[DB_FOO]  DSA400:[DB_FOO]  DSA500:[DB_FOO]  DSA600:[DB_FOO]   J Is there a way to create one saveset on tape called DB_FOO that contains = [DB_FOO...] from each disk?     L I did manage to create a BACKUP account with the recommended quotas. It is = much faster.   Thanks in Advance, John   ------------------------------   Date: 2 Jul 2001 11:07:19 GMT N From: Casper.Dik@Holland.Sun.Com (Casper H.S. Dik - Network Security Engineer)" Subject: Re: The Alpha/IA64 Hybrid0 Message-ID: <9hpkl7$5cj$1@new-usenet.uk.sun.com>  3 [[ PLEASE DON'T SEND ME EMAIL COPIES OF POSTINGS ]]   % Paul DeMone <pdemone@igs.net> writes:   @ >  Indeed, what kind of oafs can't market the fastest 64 bit MPU >  after 8 years in the market?     C People not realizing that there's more to hardware than a fast CPU.   G EV7 and the systems designed for EV7 may put this right, but isn't that  just a little bit late?    Casper --F Expressed in this posting are my opinions.  They are in no way related2 to opinions held by my employer, Sun Microsystems.? Statements on Sun products included here are not gospel and may  be fiction rather than truth.    ------------------------------  $ Date: Mon, 2 Jul 2001 13:25:20 +02005 From: "Werner Brockhoven" <werner.brockhoven@no.spam> " Subject: Re: The Alpha/IA64 Hybrid1 Message-ID: <BSY%6.321$rc5.8506@news.cpqcorp.net>   2 "Bill Todd" <billtodd@foo.mv.com> wrote in message" news:9hpk9f$e0j$1@pyrite.mv.net... > B > "Werner Brockhoven" <werner.brockhoven@no.spam> wrote in message- > news:hdY%6.319$rc5.8531@news.cpqcorp.net... 6 > > "Bill Todd" <billtodd@foo.mv.com> wrote in message& > > news:9hlsnc$om2$1@pyrite.mv.net...H > > > In an attempt to climb out of the hole it jumped into last Monday, > CompaqK > > > has apparently been energetically leaking information (from employees J > > > purporting to speak on their behalf) about Intel's having internallyL > > > perceived the error of its ways and now wishing to fix the problems in > the J > > > IA64 architecture by enlisting much or all of the Alpha architecture in > > the H > > > service of the IA64 instruction set.  Particularly explicit quotes > > include: > > > K > > > From a Compaq employee in comp.os.linux.alpha (6/26 4:48 A.M. EDT and  > 6/28 > > > 4:03 A.M. EDT):  > > ! > > Wow thanks for quoting me. :)  > > < > > But next time have the balls to also include the source. > F > I did (see the times above, which more than adequately identify it).K > Leaving off your name was a matter of tact:  I thought you might not wish  toE > be thought an idiot by people who didn't bother following up on the  > reference. >  > - bill  I Well people who follow this ng would have figured it out anyway.  BTW the K contents of both quotes is publicly available information.  Since when does % that count as "leaking information" ?    Regards,   Werner   > >  > > Regards, > > 
 > > Werner > > 
 > > <snip> > >  > >  >  >    ------------------------------  $ Date: Mon, 2 Jul 2001 16:20:31 -0400' From: "Bill Todd" <billtodd@foo.mv.com> " Subject: Re: The Alpha/IA64 Hybrid( Message-ID: <9hqkrl$e9j$1@pyrite.mv.net>  J "Casper H.S. Dik - Network Security Engineer" <Casper.Dik@Holland.Sun.Com>; wrote in message news:9hpkl7$5cj$1@new-usenet.uk.sun.com... 5 > [[ PLEASE DON'T SEND ME EMAIL COPIES OF POSTINGS ]]  > ' > Paul DeMone <pdemone@igs.net> writes:  > B > >  Indeed, what kind of oafs can't market the fastest 64 bit MPU! > >  after 8 years in the market?  >  > E > People not realizing that there's more to hardware than a fast CPU.  > I > EV7 and the systems designed for EV7 may put this right, but isn't that  > just a little bit late?   K Actually, no.  Wildfire systems aren't pigs, you know, they're just not the I be-all and end-all that some proponents had hoped they would be.  Sort of  like USIII.   L The mid-range-and-up market is still up for grabs:  if it weren't, Intel and HP wouldn't have created IA64.   - bill   >  > Casper > --H > Expressed in this posting are my opinions.  They are in no way related4 > to opinions held by my employer, Sun Microsystems.A > Statements on Sun products included here are not gospel and may  > be fiction rather than truth.    ------------------------------  $ Date: Tue, 3 Jul 2001 01:15:49 -0400' From: "Bill Todd" <billtodd@foo.mv.com> " Subject: Re: The Alpha/IA64 Hybrid( Message-ID: <9hrk76$he9$1@pyrite.mv.net>  ; "Yousuf Khan" <ykhan@nospam.home.com.spam> wrote in message 8 news:ZFb07.398996$eK2.81072129@news4.rdc1.on.home.com...A > "Terry C. Shannon" <terryshannon@mediaone.net> wrote in message 6 > news:_lb07.709$tH1.512983@typhoon.ne.mediaone.net...; > > > In which specific categories did Tru64 surpass HP-UX?  > >o > > Clustering, for one. >qB > Now, there are two separate meanings for clustering. There's theC > load-balancing type clustering, where multiple nodes run the sameeH > applications and share tasks with each other simultaneously to work onH > bigger workloads. Then there is the failover type clustering, where it= > simply a high-availability option. Which one is cited here?   J There are a great many more than 2 meanings of 'clustering'.  Greg PfisterE wrote the book 'In Search of Clusters' on the subject (get the second-C edition if you look it up - unless he's gotten a third out by now)._  J My guess is that the kind of clustering Terry's referring to involves bothH high-availability and scalability, since that's what TruClusters tend toJ support.  Though HP/UX may offer some form of clustering as well, possibly based on the Veritas software.   - bill   >- >     Yousuf Khan    ------------------------------  % Date: Mon, 02 Jul 2001 17:28:11 -0700b- From: "Mark W. Ripley" <markr@millerslab.com>  Subject: to 7.3 from 6.2. Message-ID: <3B41119B.2A0F85D1@millerslab.com>  @ I've looked through the FAQ, but couldn't find exactly what I am@ looking for which is information on what to look out for when we5 upgrade our AlphaServer 4100 from VMS 6.2-1H3 to 7.3.iC I am especially looking for information on gotcha's with UCX$/TCP$ e> and any other advice/warnings you think would be helpful.  Of @ course we RTFM, but I really would appreciate any info on things to be aware of.b   TIA -i   Mark W. Ripley Miller's Professional Imagingn   ------------------------------  % Date: Mon, 02 Jul 2001 15:12:36 -0400 + From: "Main, Kerry" <Kerry.Main@compaq.com>m! Subject: RE: VMS 7.3 experiences?rR Message-ID: <BE56C50EA024184DAF48F0B9A47F5CF4AD7ED2@kaoexc01.americas.cpqcorp.net>   John,s  > http://www.openvms.compaq.com/openvms/brochures/Bank-Austria/   L Fyi - as indicated in the brochure, these folks have been using VMS V7.3 for some time now.   Regards,  
 Kerry Main Senior Consultant- Compaq Canada Inc. Professional Services3 Voice: 613-592-4660S Fax  :  819-772-7036 Email: Kerry.Main@Compaq.com     -----Original Message-----) From: John Nebel [mailto:nebel@csdco.com]S Sent: July 1, 2001 10:53 AMb To: Info-VAX@Mvb.Saic.Comn Subject: VMS 7.3 experiences?       I What experiences have people had with V7.3?  Is it too early to use it in F a mixed-architecture and wide area production cluster, or can one just forge ahead?   Thanks.A  
 John Nebel   ------------------------------  % Date: Mon, 02 Jul 2001 10:18:27 -0600s4 From: Wayne Johnson <wayne.johnson@metc.state.mn.us> Subject: Re: VMS V7.3 SPD Error 0 Message-ID: <sb404a89.076@thor.metc.state.mn.us>   For What It's Worth:  F We are running 2 MicroVAX II's with 64 MB each.  (still running 5.5-2)    
 Wayne Johnsont! Metropolitan Council, Minneapoliso! wayne.johnson@metc.state.mn.us=20       2 >>> <dittman@dittman.net> 7/1/2001 11:34:50 AM >>>3 Robert Deininger <rdeininger@mindspring.com> wrote:lC : In article <Pfa%6.154244$Mq.4633135@e420r-sjo3.usenetserver.com>,h : dittman@dittman.net wrote:  C :> The VMS V7.3 SPD lists the MicroVAX II in both the supported andS0 :> unsupported hardware list.  Which is correct?  H : I think we'd heard rumors about that system going off support.  Is theJ : minimum memory listed?  I think it's more than the maximum a MicroVAX IIK : can have, using DEC-standard parts.  That would be enough to desupport, =s Ia : think.  : The MicroVAX II CPU can have 16MB with DEC-standard parts.  I : It's also possible a 3rd party came up with a way to put more memory innI : the system, and then VMS would work.  But it probably still wouldn't bea : supported.  B The MicroVAX II can't have more than 16MB, even with a third-party	 solution.  --=20  Eric Dittman dittman@dittman.net=20   ------------------------------   End of INFO-VAX 2001.365 ************************