1 INFO-VAX	Wed, 27 Dec 2000	Volume 2000 : Issue 722       Contents: Re: "New" BA350 / Re: Any tips and/or tricks for VMS with HSG80s? / Re: Any tips and/or tricks for VMS with HSG80s? / Re: Any tips and/or tricks for VMS with HSG80s?  Re: Giving up on VMS( Re: Happy Holidays - From Rich Marcelllo( Re: Happy Holidays - From Rich Marcelllo IPROBE for VMS Re: IPROBE for VMS Minolta Dimage 2300 = Re: NLA0: the null device - can VMS have other default names? = Re: NLA0: the null device - can VMS have other default names? = Re: NLA0: the null device - can VMS have other default names?  Re: OpenVMS on Alpha XL? Re: OpenVMS SAN Integration  Re: OpenVMS SAN Integration ) Re: OpenVMS V5.5-2 VAX tailoring question ) Re: python telnet script for openvms host ) Re: python telnet script for openvms host $ Snapshot Requirements/Needs on HSG80( Re: Snapshot Requirements/Needs on HSG80  F ----------------------------------------------------------------------  # Date: Tue, 26 Dec 2000 20:57:11 GMT $ From: Gary Morin <gmm35@my-deja.com> Subject: Re: "New" BA350) Message-ID: <92b0n3$ue6$1@nnrp1.deja.com>   F Thanks for the suggestion but I already went down that road.  I pulledC everything out of the scsi bus except the 350 and I still can't see F anything.  Once I got the manual I could see that the power supply wasD reporting a fan out condition and in fact one of the fans is bad.  IE tried the 350 terminators both ways that it allows.  I put the box on E several other scsi machines I have around here, a Mac, a Linux PC and B still nothing. There may be more wrong with this box than just the fan.  C Thanks for your help and thanks to the person who pointed me to the  manual.   	   -- Gary   ( In article <3A4372EA.B16CAC36@mmaz.com>,.   "Barry Treahy, Jr." <treahy@mmaz.com> wrote:E > My first guess is that the BA350 you purchased may have been in the A > middle of a SCSI chain and it is no longer terminated properly.  > D > Pull the top rear fan out and confirm that the termination plug is still  > inserted.  >  > Barry  >  > gmm35@my-deja.com wrote: > 4 > > Well I have been of ebaying and got a used BA3504 > > and some SBB's with an eye to arraching it to my4 > > VAXserver 3100.  No manual (of course). I attach2 > > my miniscsi end inside the shelf (on the right2 > > side) plug the 50 pin standard scsi on my VAX.5 > > Install a drive in an open address slot (0 at the 4 > > top right?) power it up and do a show dev on the1 > > VAX console... no drive shows up on the list.  > >  > > I tried: > >  diferent drive  > >  all "Open" slots ' > >  moving the cable to the left side.  > > " > > THe VAX is addressed at SCSI 7 > > 3 > > I sure would appreciate any ideas you all might 	 > > have.  > > 
 > >   -- Gary  > >  > > Sent via Deja.com  > > http://www.deja.com/ >  > -- > A > Barry Treahy, Jr  *  Midwest Microwave  *  Vice President & CIO  > C > E-mail: Treahy@mmaz.com * Phone: 480/314-1320 * FAX: 480/661-7028  >  >      Sent via Deja.com  http://www.deja.com/   ------------------------------    Date: 26 Dec 2000 22:02:20 -0500* From: young_r@eisner.decus.org (Rob Young)8 Subject: Re: Any tips and/or tricks for VMS with HSG80s?+ Message-ID: <maPIHNsEbAYK@eisner.decus.org>   Q In article <920hsr$tnt$1@nnrp1.deja.com>, Uwe Zessin <zessin@my-deja.com> writes: - > In article <PFBvXZrZlrsI@eisner.decus.org>, / >   young_r@eisner.decus.org (Rob Young) wrote: 8 >> In article <3A42BB40.4737CBB0@wi.rr.com>, Scott Vieth > <svieth@wi.rr.com> writes: >> > Hi: >> >E >> > I've connected NT servers to our ESA12000s and even got a Novell D >> > server to talk to one of our Big StorageToys just to prove that@ >> > it would work but have not yet connected a VMS system to an >> > ESA12000. >> >F >> > Does anyone have any tips or tricks that they can pass along when8 >> > it comes to connecting a VMS system to an ESA12000? > D > The current version of the manual should be sufficient - the first% > one I found a little bit confusing. 3 > See: http://www.openvms.compaq.com/openvms/fibre/  > E >> > Has anyone done any dual-path stuff similar to SecurePath on NT? E >> > (Which is also similar to the dual-path setup I have with my CI-  >> > based storage networks.)  > G > Secure path is extra software for NT + Sun Solaris. OpenVMS V7.2+ and E > Tru64 Unix V5.0A+ have multi-path features built into the operating 	 > system.  > I > I am not responsible for any OpenVMS systems that use FC in production, H > however I am involved in a sale of a 4 node cluster and two EMA-12000sH > configuration that was handed to the customer some time ago. I've heldG > some training there and they are now trying to familiarize themselves  > with the hard- and software. > ! >> > Many thanks in advance.  :^)  >>A >> I'm going to get to do this someday soon, maybe ;-).  I sat in B >> on the one day ESA12000 pre-seminar at CETS2000 (Monday sessionA >> in Oct 2000).  I repeated a story yesterday from that session. H >> One of the CETS fellows told a sad story about a customer that didn't> >> quite have their HSG80s configured correctly (sorry, detail@ >> is sparse ;-) and when an NT server booted it was quite happyB >> to say hello to all the storage it saw including the productionD >> databases that were being served up to Sun servers.  Very painfulA >> restore of those databases resulted.  The key I came away from A >> there was to use zoning on the Brocade/Compaq switches.  It is C >> hardware based and so the NT or Novell or VMS , etc. servers can  >> only see their storage. > E > Ahem. Switch zoning only helps when the servers talk to _different_ E > storage systems, although it is useful to prevent HBAs from talking E > to each other, too. As the HSG80's connection table (with ACS V8.5) E > is only 64 entries big - zoning can/must also be used to reduce the  > number of connections. >   7 	I went back to my notes and picked up on a few things. 5 	under a slide titled "Look Out!!!"  this note rests:   1 		Solaris and NT must be on seperate fabrics when  		using multipath. 	 C 	SecurePath provides multipath functionality but to ensure separate @ 	fabrics zoning will have to come into play, right?  Also, splitA 	across two areas I wish to zone it such that VMS sees all HSG80s @ 	and NT would possibly replicate to another area, but that would 	come later.    C > On a storage system that is accessed by multiple systems which do F > not form a single cluster you need to set up SSP - selective storage& > presentation (a.k.a. 'LUN masking'). >   = 	Yes I see that and recognize that.  I was unsure what zoning ; 	would truly be used for.  In the OS support Matrix, I have = 	a note scribbled that you can't do VMS and Solaris together. = 	The reason is that Solaris must have the HSG80 set to SCSI-2 7 	for SCSI_VERSION and it must be set to SCSI-3 for VMS.   ; 	Anyone know when a Solaris platform kit will come about to 9 	talk SCSI-3?  Sure would make things a whole lot easier.      >>  Here is a bit about it:  >>@ >> http://www.nwfusion.com/archive/1999/69463_07-05-1999.html?nf >>6 >>  The 2400 and 2800 switches support hardware zoning5 >>  and IP addressing. Hardware zoning allows the SAN : >>  fabric to be partitioned securely into several virtual: >>               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^8 >>  private SANs to isolate different operating systems,7 >>  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^  >>  departments or policies. >>  ^^^^^^^^^^^^^^^^^^^^^^^  > > > It is sometimes also necessary when using one OS, as I wrote@ > above, to prevent the HBAs from talking to each other. In that? > case a storage subsystem can be in multiple zones at the same  > time (zones can overlap).  > = >>      "Zoning is an issue that is becoming important in the - >                                    ======== : >>      SAN environment. With hardware zoning, you have an8 >>      absolute lock on security. No one can change the= >>      security unless they know how the switch works," says = >>      Farid Neema, president of Strategic Research in Santa  >>      Barbara, Calif.  > = > Well, the article is old, now. Zoning _is_ important today!  >   >                            --- > < > Oh, and for those of you who have no experience with this:@ > Zoning and SSP are _not_ mutual exclusive. They have different" > purposes and you will need both. >   2 	But I am not seeing that.  Here is what the notes# 	say regarding Zoning Requirements.    		Switch zoning - Required  , 		SAN configuration where OS's not supported# 		in single fabric [NT and Solaris]   3 		WNT using SecurePath 2.2 and all 4 ports of HSG80  		pair are connected.   6 		SAN configuration where more than 64 connections can 		be created on HSG80   5 		SAN configuration where the HBA can see more active * 		controller ports than it has targets for  " 		Multiple Tru64 clusters in a SAN  % 		WNT or W2K in a SAN with Tru64 5.0a   = 	So it would be simple to create scenarios where zoning isn't ? 	required.  Also, several of these zone diagrams in front of me C 	show zones overlapping (friendly OSes I suppose).  What I believe  G 	happened in the disaster scenario above is the novice SAN manager had  F 	inadvertently relied on LUN masking and disaster struck on NT reboot.   				Rob    ------------------------------    Date: 26 Dec 2000 22:09:44 -0500* From: young_r@eisner.decus.org (Rob Young)8 Subject: Re: Any tips and/or tricks for VMS with HSG80s?+ Message-ID: <qQwl1k1LrbDq@eisner.decus.org>   H In article <3A45EF6B.6775C6FA@home.nl>, Dirk Munk <munk@home.nl> writes:   > F > And even the same port on that HSG80. ("Partitioned units can not be% > split accross ports" - page 2-29)    >   - 	Here is another note from that CETS session:   6 		[Partitions] Supported in "multi-bus failover" mode,4 		but all units for a partitioned storageset must be 		presented to the same host  A 	Sounds to me like , don't put different OSes on these partitions  	if in MBF.      			Rob   ------------------------------  # Date: Wed, 27 Dec 2000 06:04:01 GMT % From: Uwe Zessin <zessin@my-deja.com> 8 Subject: Re: Any tips and/or tricks for VMS with HSG80s?) Message-ID: <92c0og$ln1$1@nnrp1.deja.com>   + In article <qQwl1k1LrbDq@eisner.decus.org>, -   young_r@eisner.decus.org (Rob Young) wrote: B > In article <3A45EF6B.6775C6FA@home.nl>, Dirk Munk <munk@home.nl> writes:  > H > > And even the same port on that HSG80. ("Partitioned units can not be% > > split accross ports" - page 2-29)  > / > 	Here is another note from that CETS session:  > 8 > 		[Partitions] Supported in "multi-bus failover" mode,6 > 		but all units for a partitioned storageset must be > 		presented to the same host > C > 	Sounds to me like , don't put different OSes on these partitions 
 > 	if in MBF.    Rob,/ you wrote in '<maPIHNsEbAYK@eisner.decus.org>': 1     "NT would possibly replicate to another area"   F Are you planning to use DRM? Last time I checked, partitioned storage-0 sets were not supported in such a configuration.   --
 Uwe Zessin3 (If you want to send mail, please use user "zessin" / who lives at "decus.decus.de", not my-deja.com)      Sent via Deja.com  http://www.deja.com/   ------------------------------   Date: 27 Dec 2000 03:26:31 GMT& From: dsf@frontiernet.net (Dan Foster) Subject: Re: Giving up on VMS 8 Message-ID: <92bnh7$11rs$1@node17.cwnet.frontiernet.net>  > In article <hshubs-A5AE80.21201126122000@news.mindspring.com>,. Howard S Shubs  <hshubs@mindspring.com> wrote:> >In article <3A48BA34.AA30A534@mmaz.com>, "Barry Treahy, Jr."  ><treahy@mmaz.com> wrote:  > O >>VMS has never been a hopeless case, even when I could crash it with EDT, but   > - >How 'bout when you could crash it with STOP?   M Wasn't it priceless when you could crash a VMS 6.0 system with UCX installed, L by invoking HELP in some particular way? ;) Although, I imagine, 'priceless'N wasn't quite the right word to describe one's first reaction upon seeing it...   -Dan   ------------------------------  # Date: Sat, 23 Dec 2000 01:49:18 GMT 4 From: "Terry C. Shannon" <terryshannon@mediaone.net>1 Subject: Re: Happy Holidays - From Rich Marcelllo ; Message-ID: <ywT06.25276$1t.843409@typhoon.ne.mediaone.net>   . <Shane.F.Smith@Healthnet.com> wrote in message> news:OF31A66B16.99FE86D8-ON882569BD.00642358@foundation.com... > E > Sales should be addressed to the rest of the world, it's true. That G > postcard was a merry Christmas to the userbase, ie the VMS people, so  > should be available on VMS.   K Yep. Somewhere in the Matco Memorial Basement from Hell I have an old DECUS J tape with some cute .com files with VT-100 "graphics." Probably compatibleJ with the more modern VT-220 as well! I'll send the tape along to Rich if I find it.   ------------------------------  % Date: Fri, 22 Dec 2000 21:52:09 -0600 7 From: "David J. Dachtera" <djesys.nospam@earthlink.net> 1 Subject: Re: Happy Holidays - From Rich Marcelllo , Message-ID: <3A442169.E1567FE@earthlink.net>   Bill Todd wrote: > < > Dave Gudewicz <david.gudewicz@abbott.com> wrote in message4 > news:91vpgd$nb6$1@fizban.fizban.pprd.abbott.com...M > > We should put this thread in a time capsule and have someone open it in a N > > decade or 3 and observe their reaction to it.  If it were me reading theseJ > > words then, I would use the term BAH, HUMBUG to describe its contents. > How  > > about you? > H > Very likely - because by then, with high probability, the putative VMSN > renaissance will have been seen to be as inconsequential as this thread, andL > no one will care about VMS any more (save for those people happy to run itK > pretty much as-is forever, assuming Compaq holds to its COE commitments). N > So this thread will simply be seen, correctly, as just so much more bleatingK > by sheep unwilling or unable to summon up the courage to take more direct L > action to make Compaq take an unequivocal position (the same position bothL > inside and outside the VMS coterie) on its commitment (or lack thereof) to > VMS's future.   F Hi, Bill!! Long time, no see!! How are you doing? The Season's Best to you!!   C Now, since we've already beaten Compaq bloody both privately and in F public, what else would you recommend we do? We've shown them both theH error of their ways and where the profit potential *REALLY* is. However,D as the wise man said, "There are none so blind as those who will not( see" and Compaq is epitome of blindness.  F So, short of criminal action, violence and/or civil disobedience, what do you recommend?   F F.Y.I.: I've already begun pursuing my next career after EDP (I'm sureG some folks here are relieved to hear that!). "I'm not here just to make C a living, I'm here to make a difference." (That actually belongs to  someone else, not me.)   --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/   F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.    ------------------------------    Date: 27 Dec 2000 02:14:01 +0800, From: Paul Repacholi <prep@prep.synonet.com> Subject: IPROBE for VMS 0 Message-ID: <871yuvf3ti.fsf@k9.prep.synonet.com>  = On the current Linux Powertools for Alpha Linux, is a version ; of IPROBE. Any chance of the VMS version of this being made 
 available?   --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.   ------------------------------  % Date: Tue, 26 Dec 2000 13:25:06 -0600 ) From: "John E. Malmberg" <wb8tyw@qsl.net>  Subject: Re: IPROBE for VMS / Message-ID: <t4hs0j61q8181b@corp.supernews.com>   . "Paul Repacholi" <prep@prep.synonet.com> wrote5 in message news:871yuvf3ti.fsf@k9.prep.synonet.com...  > ? > On the current Linux Powertools for Alpha Linux, is a version = > of IPROBE. Any chance of the VMS version of this being made  > available?   What does IPROBE do?   -John  wb8tyw@qsl.network   ------------------------------  # Date: Tue, 26 Dec 2000 19:08:47 GMT ) From: "wzeijlmaker" <wzeijlmaker@home.nl>C Subject: Minolta Dimage 23003 Message-ID: <31626.26615$Es2.748927@zwoll1.home.nl>n  / Visit the New Minolta Dimage 2300 Digital Page: ! http://home.hetnet.nl/~zeylmaker/8   ------------------------------  # Date: Sat, 23 Dec 2000 01:54:31 GMT * From: Alan E. Feldman <alan48@my-deja.com>F Subject: Re: NLA0: the null device - can VMS have other default names?) Message-ID: <9210km$8o9$1@nnrp1.deja.com>   ) In article <920blm$oln$1@nnrp1.deja.com>,r-   Alan E. Feldman <alan48@my-deja.com> wrote:a) > In article <3a431bcb$1@cpns1.saic.com>,M2 >   "Scott Stark" <hayden.s.stark@saic.com> wrote: > > > David J. Dachtera wrote:# > > >> AH! I see the confusion now.e > > >>C > > >> In most cases, "NL:" is taken as being identical to "NLA0:".s > > ? > > Thank you for the abundant replies, the questions have been/ > answered.  TheH > > solution is to have the code look for NLA0 and not just "NL" as that > would,, > > bypass the intended NLPx (print) action. >3? > So, you're searching code for occurrences of the null device?$ >nF > You need to search for NL, NLA, NL0, NLA0, and all four with a colonG > attached. This is because the default controller is A and the defaultlG > number is 0, so either or both can be missing and it's still the same 	 > device.   E Oops, I just meant that there may or may not be a colon at the end ofeF the search string. Of course if you just search for NL you'll find allE the other cases, but you may get a lot of false positives (including,lD of course, NLP0)! I meant that any of the cases quoted above will beC interpreted as the null device when used in the context of a device  name.l   --F NOTE: If you wish to e-mail me, please do NOT use the deja address. ItE is broken. Instead, use one of the addresses below, removing the longp wrong part first. Thanks.h   Disclaimer: JMHO Alan E. Feldman  &-)+ w: afeldman@gfigroup.ButItSaidItPrinted.comt5 h: alan48@dellnet.YouCantBelieveEverythingYouRead.coms     Sent via Deja.com  http://www.deja.com/   ------------------------------  % Date: Fri, 22 Dec 2000 22:43:12 -0500B, From: Howard S Shubs <hshubs@mindspring.com>F Subject: Re: NLA0: the null device - can VMS have other default names?> Message-ID: <hshubs-84D4E9.22431222122000@news.mindspring.com>  J In article <jf+MDOY83EtA@eisner.decus.org>, briggs@eisner.decus.org wrote:  H >Or, as you appear to assume, does he want to identify references to the< >null device in the context of some form of static analysis?  O Yeah, I and others asked him for a better understanding of what he was asking, iO but he never came back with an explanation, so I'm going with the most obvious   (to me) answer.   L My answer can only be used after doing logical name translation all the way 3 down, and stripping out any leading "_" characters.     F >Note that an examination of the first two letters of a file or deviceD >specification is not a very robust technique.  NLP0 is not normally >the null device.j  M But it should be.  Given the standard nomenclature, the first two characters mM are the driver designation, the third is a controller letter, and the digits  K following are a unit number.  I would assume NLP0 is a strange null device <? unless shown otherwise.  I've not seen that designation so far.t  O Using some kind of CONNECT command in either SYSGEN (for VAXen) or SYSMAN (for (N Alphas), I'd think you could create an NLxn of whatever kind you liked, using # the NLDRIVER as the code behind it.  --   Howard S ShubsD "Run in circles, scream and shout!"  "I hope you have good backups!"   ------------------------------  % Date: Fri, 22 Dec 2000 22:45:45 -0500b, From: Howard S Shubs <hshubs@mindspring.com>F Subject: Re: NLA0: the null device - can VMS have other default names?> Message-ID: <hshubs-B0B28C.22454522122000@news.mindspring.com>  B In article <3A42E44C.D4982FB7@earthlink.net>, "David J. Dachtera" $ <djesys.nospam@earthlink.net> wrote:  = >In most cases, "NL:" is taken as being identical to "NLA0:".s  / IIRC, that's a hold-over from PDP-11 days, yes?u    D >I don't recall at this hour just where the reference is; but, checkI >through the docset (if you have it) for any references to the VMS deviceeE >naming conventions. In short, when you specify only the device class6C >name (such as "NL:", "TX:", etc.) the system will select the firsty/ >matching device spec ("NLA0:", "TXA0:", etc.).S  N Er, maybe.  I've used NL: and TT:, where NL: refers to -the- null device, and $ TT: is the current terminal, if any.    B >NLPxxxx: is an exception to this rule since it is supplied by theB >third-party IP stack known as Multinet (presumably, "Network LineI >Printer, unit xxxx"). That's as opposed to device class "NL", controller E >number 16 ("P"), unit number xxxx which it would otherwise describe.o  L -That- explains it.  I've never loaded Multinet.  That sounds like a broken  usage, anyway. -- y Howard S ShubsD "Run in circles, scream and shout!"  "I hope you have good backups!"   ------------------------------  # Date: Tue, 26 Dec 2000 20:48:38 GMT $ From: Gary Morin <gmm35@my-deja.com>! Subject: Re: OpenVMS on Alpha XL? ) Message-ID: <92b073$tvi$1@nnrp1.deja.com>n  G The XL series of Workstations runs the AlphaBIOS which only supports NTrE and Linux (with some tweaking, see www.alphalinux.org).  It was nevermD designed to support anything but NT.  Sorry, I also wish it ran VMS.  	   -- Gary>      / In article <t4d3e2ggr7p6f0@corp.supernews.com>,e6   "Walker Bennett" <Wabennett@gw.total-web.net> wrote:G > Does anyone know if OpenVMS (any version) will install on an Alpha XLt 366a > (21164 chip)?f >tC > I just inherited one which is loaded with NT, but I'd rather VMS.n >t	 > Thanks,w >  > Walker Bennett > w_bennett@msn.comz > wbennett@caldwellspartin.com >c >h     Sent via Deja.comi http://www.deja.com/   ------------------------------  # Date: Tue, 26 Dec 2000 19:50:19 GMTo From: Dirk Munk <munk@home.nl>$ Subject: Re: OpenVMS SAN Integration' Message-ID: <3A48F67B.22C59918@home.nl>c  
 fooguy wrote:m > I > We have Xiotech Fiberchannel Storage Area Network Solution, to which wemD > have attached several Netware, NT, and Solaris systems. We have onG > order, to replace our AS800, (2) DS20s (one with a Solid State Disk).eA > What we're wondering, is if anyone has had any luck with QLogictD > Fiberchannel HABs under OpenVMS. QLogic seems to make hardware andJ > drivers for every platform and OS (and DEC seems to use their stuff here
 > and there).  > 	 > Thanks,  > John >z    E Most unlikely that the Qlogics will work. Compaq uses the Emulex 8000pH cards, and unless Qlogic has a VMS driver, you can be quite sure nothing, else than a Emulex 8000 (or 7000) will work.  E And keep in mind that VMS uses fibrechannel just a bit different fromI# other platforms (identifiers etc.).o  E I would not like to experiment very much with this not so very maturei infrastructure.a   Regards,   Dirk i    i > --/ > *********************************************9* > "All I every wanted from life was to see. > Larry Wall give Bill Gates a Perl Necklace." >  > Sent via Deja.comr > http://www.deja.com/   ------------------------------  # Date: Tue, 26 Dec 2000 20:52:55 GMT " From: fooguy <jweisen@my-deja.com>$ Subject: Re: OpenVMS SAN Integration) Message-ID: <92b0f5$u36$1@nnrp1.deja.com>^  : I guess I'll stick to Storage Works spindles. Thanks Dirk.  ' In article <3A48F67B.22C59918@home.nl>, !   Dirk Munk <munk@home.nl> wrote:y >e >s > fooguy wrote:w > > H > > We have Xiotech Fiberchannel Storage Area Network Solution, to which weF > > have attached several Netware, NT, and Solaris systems. We have onB > > order, to replace our AS800, (2) DS20s (one with a Solid State Disk).C > > What we're wondering, is if anyone has had any luck with QLogicoF > > Fiberchannel HABs under OpenVMS. QLogic seems to make hardware andG > > drivers for every platform and OS (and DEC seems to use their stufft here > > and there).  > >i > > Thanks,i > > John > >i >eG > Most unlikely that the Qlogics will work. Compaq uses the Emulex 8000dB > cards, and unless Qlogic has a VMS driver, you can be quite sure nothing . > else than a Emulex 8000 (or 7000) will work. > G > And keep in mind that VMS uses fibrechannel just a bit different frome% > other platforms (identifiers etc.).  > G > I would not like to experiment very much with this not so very maturen > infrastructure.  >w
 > Regards, >e > Dirk >	 > > --1 > > *********************************************r, > > "All I every wanted from life was to see0 > > Larry Wall give Bill Gates a Perl Necklace." > >  > > Sent via Deja.comh > > http://www.deja.com/ >c   --- *********************************************r( "All I every wanted from life was to see, Larry Wall give Bill Gates a Perl Necklace."   /* John Eisenschmidt , fooguy AT AT AT eisenschmidt DOT DOT DOT org (you know the drill) */     Sent via Deja.comn http://www.deja.com/   ------------------------------  % Date: Tue, 26 Dec 2000 15:31:32 -0500p- From: JF Mezei <jfmezei.spamnot@videotron.ca> 2 Subject: Re: OpenVMS V5.5-2 VAX tailoring question, Message-ID: <3A49001E.EC8F5DF7@videotron.ca>   Richard Jordan wrote:eF > TK50s are dead/unreadable, though I have working V5.5-2H4 remasteredH > kits.  I do still have CD media, but no easy way to get a drive on the	 > system.:  J does 5.5-2 have the SYS$UPDATE:VMSTAILOR.EXE file ?  If so, your adding ofF components would be simplified and the -2H4 kit would still work sinceG VMSTAILOR.EXE would probably bypass the hardware checks that would maketB VMSINSTAL fail on the -2H4. Look at sys$update:tailor_on.template.  M Those *H* versions were targetted at specific VAX models released after 5.5-2 L and have code to prevent their install on other machines, and they contain aM full VMS kit but not upgrade procedures as I recall since they were generatedeT to load VMS on new virgin VAXes. So that kit should contain all the necessary files.  M From what I have seen. VMSTAILOR.EXE generates its own BACKUP commands (addedjN to the end of tailor_on.template). When you run VMSTAILOR.EXE, when it asks toN mount the media, you can look at your sys$login:BACKUP_TEMP.COM to see what it is about to do.   L It knows exactly which files are needed and they are specified in the backup command with a /SELECTL So it completely bypasses the procedures that are in the kit (at least as of	 VMS 7.2).t   ------------------------------  % Date: Tue, 26 Dec 2000 22:37:30 +0100 I From: =?iso-8859-1?Q?Jean=2DFran=E7ois=20PI=C9RONNE?= <jfp@altavista.net> 2 Subject: Re: python telnet script for openvms host- Message-ID: <3A490F9A.FB2EC59A@altavista.net>n  , The following script run fine on my station.  1 May be in your login you will have commands like r set term/inquire or/and
 set prompt   #python test script: import sys, telnetlibg host = 'hostname'i user = 'username\r'o password = 'mypasswd\r'o tn = telnetlib.Telnet(host)r # tn.set_debuglevel(1) tn.read_until('Username: ')p tn.write(user) tn.read_until('Password: '). tn.write(password)< # print tn.read_until('[c')    #last char of session hearder print tn.read_until('$ ')  tn.write('$ dir\r')3 print tn.read_until('$ ')i tn.write('$ sh sys\r') print tn.read_until('$ ')M tn.write('$ logout\r') print tn.read_all()r     Ennis Rosamond wrote:e > = > I am attempting to develop a Python telnet script to accesss > an OpenVMS host. > > > The script is partially successful in that it logs on to the> > target host. I know this because following acceptance of the@ > user password by the host, the host sends back the same header? > message as is received in an interactive telnet session.  ThesA > problem I am having is that the host doesn't seem to be sendingvA > back a '$ ' prompt after the session header; at least I haven'tsB > seen it.  Consequently, the host doesn't respond to any commands > sent by the script. 0 > (I have been trying a simple '$ dir' command.) > ! > My test script is listed below.  >  > #python test script: > import sys, telnetlibp > host = 'hostname'c > user = 'username\r'D > password = 'mypasswd\r'p > tn = telnetlib.Telnet(host)e > tn.read_until('Username: ')n > tn.write(user) > tn.read_until('Password: ')4 > tn.write(password)6 > tn.read_until('[c')    #last char of session hearder > tn.write('$ dir\r')  > / > #following this, I receive back the sequence:e > #recv '\377\373\001' > #IAC WILL 251n > #recv '\377\373\003' > #IAC WILL 251o > #recv '\003\\\033Z'  > #e' > #which I don't know how to interpret.f > < > Anyone have an idea about how to determine what I am doing9 > wrong?  Could the problem have something to do with the 4 > terminal type expected by the OpenVMS telnet host? > = > I am posting this to both the python and openvms discussiono( > groups.  Any help greatly appreciated. >  > Sent via Deja.coml > http://www.deja.com/   ------------------------------    Date: 27 Dec 2000 04:30:23 +0800, From: Paul Repacholi <prep@prep.synonet.com>2 Subject: Re: python telnet script for openvms host0 Message-ID: <87ofxzdixs.fsf@k9.prep.synonet.com>  + Ennis Rosamond <ennisr@my-deja.com> writes:n  / > #following this, I receive back the sequence:i > #recv '\377\373\001' > #IAC WILL 251  > #recv '\377\373\003' > #IAC WILL 251. > #recv '\003\\\033Z'? > # ' > #which I don't know how to interpret.h  * This is telnet protocol negotiation stuff.  6 Don't have TCPIP V5.0 on VMS by any chance? If so, run+ to the patch kits at Compaq and get V5.0a.     -- o< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.   ------------------------------    Date: 26 Dec 2000 22:15:14 -0500* From: young_r@eisner.decus.org (Rob Young)- Subject: Snapshot Requirements/Needs on HSG80i+ Message-ID: <FV+p8XW2KzUs@eisner.decus.org>   Q In article <925aie$5c7$1@nnrp1.deja.com>, Uwe Zessin <zessin@my-deja.com> writes:o  ' >> So the manual contradicts itself....  > A > There are many more (e.g. on memory requirements for snapshot).' >   $ 	From those CETS notes it says this:   		BCVSnap Limits in ACS 8.5S  0 		Can snap any type of storage volume (including 		partitioned containers)h  - 		4 snapshots per HSG80 pair / one per volumes  - 		Runs in both transparent and multi-bus modeo  ) 		Bitmap in cache uses 4MB for every Snap   = 		Can't snapshot same volume while previous snap still exists(  * >>>		Must have 512MB mirrored cache   <<<<   		Max unit size is 512 GBo  9 		Needs a TSS (temp storage set) same size or larger thanl 		the master volumen  3 		Can be used on the same host as the source volumey     		 			Rob   ------------------------------  # Date: Wed, 27 Dec 2000 06:01:00 GMTr% From: Uwe Zessin <zessin@my-deja.com> 1 Subject: Re: Snapshot Requirements/Needs on HSG80i) Message-ID: <92c0ir$lm8$1@nnrp1.deja.com>e  + In article <FV+p8XW2KzUs@eisner.decus.org>,a-   young_r@eisner.decus.org (Rob Young) wrote:vB > In article <925aie$5c7$1@nnrp1.deja.com>, Uwe Zessin <zessin@my- deja.com> writes:- >-) > >> So the manual contradicts itself....  > > C > > There are many more (e.g. on memory requirements for snapshot).s >-& > 	From those CETS notes it says this: >  > 		BCVSnap Limits in ACS 8.5S > 2 > 		Can snap any type of storage volume (including > 		partitioned containers)g >d/ > 		4 snapshots per HSG80 pair / one per volume  > / > 		Runs in both transparent and multi-bus mode1 > + > 		Bitmap in cache uses 4MB for every Snap  > 8 > 		Can't snapshot same volume while previous snap still >               exists>a, > >>>		Must have 512MB mirrored cache   <<<<  C A similar note is also in one if the HSG80's manuals - I'm too lazy< to check right now. But:  
 Release NotesM! RA8000/ESA1200 and MA8000/EMA1200p:   Solutions Software V8.5b for OpenVMS  ("= Platform kit") AA-RH4C-TE, Page 10w  ? "NOTE: It is strongly recommended that cache modules containingx         512 MB of memory be used"  8 Hm, English isn't my mother's language, but I think that   "must" <> "recommended".   > 		Max unit size is 512 GB    ACS V8.6 will have 1 TBytes.  ; > 		Needs a TSS (temp storage set) same size or larger than  > 		the master volumee >m5 > 		Can be used on the same host as the source volumeD >3 > 			Rob   --
 Uwe Zessin3 (If you want to send mail, please use user "zessin"a/ who lives at "decus.decus.de", not my-deja.com)-     Sent via Deja.com- http://www.deja.com/   ------------------------------   End of INFO-VAX 2000.722 ************************