INFO-VAX Mon, 25 Feb 2008 Volume 2008 : Issue 111 Contents: Re: Documentation Colors (was: Re: VMS 5.0 - VMS 5.5) Re: HP OpenVMS Tele-Marketing?!? Re: laboratory subroutines Re: LK-201 error question Re: Microsoft pro says OpenVMS best OS ever invented! Re: Microsoft pro says OpenVMS best OS ever invented! Re: Question about DFU Re: Question about DFU Re: Question about DFU Re: Samba and text files Re: Samba and text files Re: Samba and text files Re: Samba and text files Re: Unable to communicate with replacement ESL drive Uses for a MicroServer-SP? Re: Uses for a MicroServer-SP? Re: Uses for a MicroServer-SP? ---------------------------------------------------------------------- Date: Sun, 24 Feb 2008 23:00:07 GMT From: John Santos Subject: Re: Documentation Colors (was: Re: VMS 5.0 - VMS 5.5) Message-ID: In article <62bguuF22df2gU1@mid.individual.net>, billg999@cs.uofs.edu says... > In article , > Malcolm Dunnett writes: > > Bill Gunshannon wrote: > >> Just out of curiosity, I have Blue Binders for RT-11 and RSTS and Orange > >> binders for later versions of RSTS. Did the colors for all the OSes > >> tend to change at the same time? > > > > RSTS documentation in binders? What a new-fangled concept. > > > > The RSTS documentation I remember came with the books stapled > > together, with a "sunset" coloured cover that had a hole in it that you > > could read the title through. > > Yup. I have Version 7 in Blue and Version 9 in Orange. > > bill > > > The stapled manuals with the multicolored covers were from V4 (oldest I ever saw) and V5, IIRC. At some point, they switched to white covers with a stylize large lower case "dec", in multiple parallel colored stripes. At least I think that was what it was supposed to represent. This might have been V6A or just later reprinting of the older manuals. I've seen hardware manuals with the same colored covers. I think V6B and V6C were in light blue 3-ring binders, V7 in dark blue, V8 in gray, and V9-V10 in "Orange", which was officially "Chinese Red", but it sure looks orange to me, and to everyone else I ever discussed it with (except my friend who is color-blind; to him, it looks like a muddy shade of brown.) -- John ------------------------------ Date: Mon, 25 Feb 2008 03:57:11 GMT From: "Jay E. Morris" Subject: Re: HP OpenVMS Tele-Marketing?!? Message-ID: <47c23c97$0$22828$4c368faf@roadrunner.com> On 18-Feb-2008, billg999@cs.uofs.edu (Bill Gunshannon) wrote: > Stupid doesn't mean fast. That case probably took years. Just like the > "My CAT scan made me loose my psychic ability" case. Hey, at least they settled the "impacting the comet will screw up the harmony of the universe and ruin my astrology charts" case pretty fast. But then, they were under a deadline for that. -- The email fix is obvious. Help solve world hunger http:\\www.cropwalk.org Contribute to my walk https://www.kintera.org/faf/donorReg/donorPledge.asp?ievent=241032&lis=1&kntae241032=4564D14A56B14453B4882E5E35030784&supId=205315529 Or find someone in your neighborhood http://www.kintera.org/site/pp.asp?c=hsJPK0PEJpH&b=2892557 ------------------------------ Date: Sun, 24 Feb 2008 12:09:59 -0800 (PST) From: RiverRoadRambler@gmail.com Subject: Re: laboratory subroutines Message-ID: <4fa0b1d3-1820-4a4d-9248-153c2a52d914@n75g2000hsh.googlegroups.com> On Feb 24, 8:40=A0am, RiverRoadRamb...@gmail.com wrote: > On Feb 23, 12:18=A0pm, "John Wallace" > wrote: > > > > > > > wrote in message > > >news:143fc150-ef28-4663-aae8-468bcbbc02c8@p43g2000hsc.googlegroups.com...= > > > > I need some info on a subroutine from some VAX software > > > =A0 =A0the different names were VAXLAB, LABSTAR, Dec laboratory > > > subroutines DEC Real time integrator > > > > =A0 =A0In some software I called a signal processing filter =A0 -- =A0= LSP > > > $FILTER_NONREC > > > > =A0 =A0 The documentation as to what the filter code was has disappear= ed > > > from our lab over the years. =A0Does anyone have the documentation > > > DECrti was a fine product, but like many perfectly decent DEC products, = it > > was almost invisible in the market. VAXlab predates it but had similar > > challenges. > > > Both come from an era where DEC documentation mostly came either on pape= r or > > CD. A set of consolidated documentation CDs from the relevant era may > > contain the information you need, but there were exceptions which weren'= t on > > CD. Right now I can't remember the exact vintage we're looking for, perh= aps > > someone else can. I can't even find the SPD online otherwise the relevan= t > > era would be easily identifiable. It must be post 1988, based on where I= was > > working at the time; DECrti was probably early 1990s, but I can't curren= tly > > be more specific than that. (A quick search of newsgroups confirms this = but > > doesn't help be more specific). > > > As per Hein's suggestion not long ago in this ng, you can use the online= > > docs athttp://www.sysworks.com.au/odl.html-for each issue of VAX docs > > online there, look up the Online Documentation Library Contents and sear= ch > > it for your choice of VAXlab or DECrti (but I'm not 100% sure the > > VAXlab/DECrti docs would be on those CDs). Sysworks collection in the > > relevant era is far from complete, anyone interested in helping sysworks= > > fill their gaps ? > > > I'm away from my realtime resources for a couple of days, and they don't= > > include full VAXlab/DECrti docs anyways, but hopefully something will tu= rn > > up for you soon. > > > Today's "equivalent" product would probably be NI's Labview, which is ju= st > > as "proprietary"/closed as VAXlab/DECrti ever was, and for those doing r= eal > > realtime, or for those who care about data integrity or security, has th= e > > nontrivial snag of being Windows-based (or Linux if you prefer). But, li= ke > > Windows, Labview has huge market visibility and support. > > > Combine this with your need to reverse engineer some VAX assembly you po= sted > > elsewhere, and it sounds like you have "interesting times ahead". > > > Best of luck, > > John > > I have two people who have offered to take a look at converting the > vax macro code--so hopefully that part of my updating of an old system > will proceed. > > In the mid 1980s I wrote some software to process signals coming from > the digestive system using a PDP 11 23+ =A0 When the Microvax II came > out with a VAXLAB version (software package to run Q-Bus > instrumentation and lots of scientific routines), I moved the programs > from pdp to VAX and extensively used the DECWINDOWS graphing routines, > signal processing routines etc, but moved the data acquisition to > pcs. =A0Dec gave up on the VAXLAB stuff before Compaq bought it out. > They also never ported the software to run on the Alpha (the "real > time routines"). > =A0 =A0Anyway-- the analysis has been running on a VAXSTATION 90a since > 1994 or so and finally the users decided to have it replaced with a pc > version. =A0 I have been retired, and so am just coordinating some > efforts to duplicate the old analysis. > =A0 About the only parts that have to be exactly duplicated are the > macro peak finding code and the filters. =A0They were sort of blackbox > routines I called. =A0I have the source for the peaks, but no info for > the filters--which I believe are pretty much off the shelf > techniques. > > =A0 Sort of a stroll down memory lane, with a little pride that > something I originally wrote in 1985 on a pdp is still useful 24 years > later! > > Russ Hanson =A0 (I worked for a huge medical organization in Rochester > MN for 25 years--and this is some research stuff we did).- Hide quoted tex= t - > > - Show quoted text - Searching a little more on the internet led me to a site where I believe the filter routine may be located. The internet is pretty amazing! "DIGITAL_FILTER is adapted from the article "Digital Filters," by Robert Walraven, in Proceedings of the Digital Equipment User's Society, Fall 1984" fortran located at http://www.ibiblio.org/pub/academic/computer-science/history/pdp-11/rt/sig= tapes/11sp59/datfit/fltlib.for ------------------------------ Date: Sun, 24 Feb 2008 20:04:07 -0500 From: norm.raphael@metso.com Subject: Re: LK-201 error question Message-ID: This is a multipart message in MIME format. --=_alternative 0005E3A1852573FA_= Content-Type: text/plain; charset="US-ASCII" Doug Phillips wrote on 02/22/2008 04:46:15 PM: > On Feb 22, 3:25 pm, Forrest Kenney wrote: > > Keyboard Error 4 means the terminal could not talk to the keyboard. > > Could be the terminal or it could be the keyboard. > > > > Forrest > > Or the cable. and the answer is...the keyboard. Terminal works with another keyboard-cable. Keyboard does not work with that Terminal-cable. Thanks for all contributions. Remedy is to recycle the keyboard. --=_alternative 0005E3A1852573FA_= Content-Type: text/html; charset="US-ASCII"



Doug Phillips <dphill46@netscape.net> wrote on 02/22/2008 04:46:15 PM:

> On Feb 22, 3:25 pm, Forrest Kenney <Forrest.Ken...@hp.com> wrote:
> >     Keyboard Error 4 means the terminal could not talk to the keyboard.
> > Could be the terminal or it could be the keyboard.
> >
> > Forrest
>
> Or the cable.
and the answer is...the keyboard.

Terminal works with another keyboard-cable.
Keyboard does not work with that Terminal-cable.
Thanks for all contributions.
Remedy is to recycle the keyboard. --=_alternative 0005E3A1852573FA_=-- ------------------------------ Date: Mon, 25 Feb 2008 00:24:24 -0000 From: "John Wallace" Subject: Re: Microsoft pro says OpenVMS best OS ever invented! Message-ID: <13s42ls9g93k202@corp.supernews.com> "Arne Vajhøj" wrote in message news:47be3660$0$90268$14726298@news.sunsite.dk... > ultradwc@gmail.com wrote: > > http://visualstudiomagazine.com/columns/article.aspx?editorialsid=2469 > > He actually knows VMS. A quick GG search reveals that he posted > to c.o.v/I-V a few times back in 1989. > > And he even has a point. The .NET CTS is many ways is the > object oriented equivalence of what VMS calling convention > etc. does for procedural programming. > > It allows you to use a common library and to mix multiple > languages in your app. > > Arne " It allows you to ... to mix multiple languages in your app" I'm not 100% sure mixing languages in one app is a common requirement, but common (language-independent) tools and interfaces surely should be. Anyway, surely all .NET allows you to do is to choose from a selection of Microsoft's current programming languages, of which there are not very many, and which are currently incompatible with what they were three years ago, and which history leads us to expect will be incompatibly different again three years from now? Where's the investment protection in that? Oh, I forgot, investment protection is out of fashion because version churn is the way the MS-centric ecosystem's players make much of their money, because once you are hooked it is very difficult to get clean again. Surely even gcc (and friends) does better in terms of language interoperability and compatibility and investment protection than .NET, and neither come close to the language interoperability ... in the VMS Calling Standard (and the rest) from day one? Whether .NET offers anything of value beyond language interoperability is a different discussion... Kudos to whoever Solak is/was (it would be inappropriate to summarise his comment on the magazine article, let's just say it's about "architecture"). Solak points out that architecture is something which VMS had from day 1, to which I'd just like to add that architecture is something Windows will never have, because you can't retrofit architecture (and elegance) when the underlying works are a collection of leftovers and kludges from DOS and thereafter (and even the better NT bits mostly came from VAXELN, rather than from VMS). ------------------------------ Date: Sun, 24 Feb 2008 21:05:29 -0500 From: =?ISO-8859-1?Q?Arne_Vajh=F8j?= Subject: Re: Microsoft pro says OpenVMS best OS ever invented! Message-ID: <47c22266$0$90272$14726298@news.sunsite.dk> John Wallace wrote: > "Arne Vajhøj" wrote in message > news:47be3660$0$90268$14726298@news.sunsite.dk... >> ultradwc@gmail.com wrote: >>> http://visualstudiomagazine.com/columns/article.aspx?editorialsid=2469 >> He actually knows VMS. A quick GG search reveals that he posted >> to c.o.v/I-V a few times back in 1989. >> >> And he even has a point. The .NET CTS is many ways is the >> object oriented equivalence of what VMS calling convention >> etc. does for procedural programming. >> >> It allows you to use a common library and to mix multiple >> languages in your app. > > " It allows you to ... to mix multiple languages in your app" > > I'm not 100% sure mixing languages in one app is a common requirement, but > common (language-independent) tools and interfaces surely should be. You can consider it a nice feature or just a positive side effect of what is necessary to provide the common library. I have mixed languages in VMS a few times (especially Pascal -> Fortran) and in .NET a few times (C# -> JScript). > Anyway, > surely all .NET allows you to do is to choose from a selection of > Microsoft's current programming languages, of which there are not very many, Not true. C# VB.NET C++/CLI JScript.NET (JavaScript) J# (Java) F# (ML) L# (Lisp) mgnat (Ada) Delphi.NET (Pascal) IronRuby IronPython Fujitsu NetCobol Lahey Fortran etc. I am not aware of any PL/I compiler though. > and which are currently incompatible with what they were three years ago, > and which history leads us to expect will be incompatibly different again > three years from now? None of the languages are incompatible with what they were 3 years ago (.NET 2.0 timeframe), but they are not compatible with the languages as they were 10 years ago (those that existed 10 years ago). The practical problem is not very big since .NET has several features for interoperability with the Win32 & COM worlds. > Where's the investment protection in that? Oh, I > forgot, investment protection is out of fashion So you think MS should have sticked to 16 bit DOS compilers to protect investments in that code ? I don't agree. The customers does not seem to agree. The world moves and vendors has to move with it. > because version churn is the > way the MS-centric ecosystem's players make much of their money, because > once you are hooked it is very difficult to get clean again. Hm. Everybody knows that it cost money to switch platform. That is not a MS specific problem. "get clean" sounds more as something from a religious speach than about programming languages and platforms. > Surely even gcc > (and friends) does better in terms of language interoperability Maybe. Speaking of: can you give me a good example of g++ and gcj interoperability ? I don't seem to be able to get anything working. Arne ------------------------------ Date: Sun, 24 Feb 2008 20:36:20 +0100 From: Jur van der Burg <"lddriver at digiater dot nl"> Subject: Re: Question about DFU Message-ID: <47c1c734$0$14345$e4fe514c@news.xs4all.nl> I was a member of VMS engineering when there was talk about including DFU in VMS. I had setup everything ready to go to have it included in the VMS build procedures, but management higher up the chain did not give the final word to do so, so we never included it. There was never a technical reason, it was purely political. Since I left HP I'm treating it as a private project. Jur. JF Mezei wrote: > Is there a reason why DFU was never included with VMS ? > > Seems to me like a key utility that should have been an official part of > VMS. > > I can understand its current status, along with the LDRIVER being > maintained by volunteers as freeware. (and many thanks are owed to Jur > for that). > > But before all the staff cuts and downsizing, was there some > technical/political/whatever reason that prevented DFU from being > included as part of VMS OS distribution ? ------------------------------ Date: Sun, 24 Feb 2008 20:43:50 -0500 From: JF Mezei Subject: Re: Question about DFU Message-ID: <47c21d96$0$10255$c3e8da3@news.astraweb.com> Jur van der Burg wrote: > build procedures, but management higher up the chain did not give the final > word to do so, so we never included it. There was never a technical reason, > it was purely political. Is it because management didn't see the value of this utility ? Some internal petty politics/turf wars ? Or budget constraints ? ------------------------------ Date: Mon, 25 Feb 2008 07:22:52 +0100 From: Jur van der Burg <"lddriver at digiater dot nl"> Subject: Re: Question about DFU Message-ID: <47c25ebc$0$14348$e4fe514c@news.xs4all.nl> Nobody wanted to be responsible from a management level, although I stepped up to be technicaly responsible. Jur. JF Mezei wrote: > Jur van der Burg wrote: > >> build procedures, but management higher up the chain did not give the final >> word to do so, so we never included it. There was never a technical reason, >> it was purely political. > > Is it because management didn't see the value of this utility ? > > Some internal petty politics/turf wars ? > > Or budget constraints ? ------------------------------ Date: Sun, 24 Feb 2008 21:50:03 +0000 (UTC) From: moroney@world.std.spaamtrap.com (Michael Moroney) Subject: Re: Samba and text files Message-ID: moroney@world.std.spaamtrap.com (Michael Moroney) writes: >"Gorazd Kikelj" writes: >>"Michael Moroney" wrote in message >>news:fpn019$m28$1@pcls4.std.com... >>>>vfs objects = varvfc >>> >>> Thanks, Paul, but quickly inserting that line in the [global] area of >>> smb.conf and restarting samba had no effect. I'll study the documentation >>> on that later. >>It's per share parameter. Just put it into share definition. >Still can't convince it to work, on two different systems. >[global] > server string = Samba %v running on %h (OpenVMS) > netbios name = %h > security = user > passdb backend = tdbsam > domain master = yes > guest account = SAMBA$GUEST > domain logons = Yes > log file = /samba$root/var/log_%h.%m > create mode = 0755 > load printers = no > printing = OpenVMS > vfs objects = varvfc >[homes] > comment = Home Directories > browseable = no > read only = no > create mode = 0750 > vfs objects = varvfc >[test1] > comment = test folder > path = /samba$root/tmp > read only = No > guest OK = Yes > vfs objects = varvfc This may actually not be an issue after all. I've been checking regular (created with EDT) text files with Notepad from a PC to see if things worked. I read that Notepad is rather brain damaged when working with Samba-served files so I opened a file with Wordpad, and it works correctly. Other tools seem to work as well. So there's something "funny" with Notepad. ------------------------------ Date: Sun, 24 Feb 2008 14:39:25 -0800 (PST) From: AEF Subject: Re: Samba and text files Message-ID: <68f9473d-22d5-44b8-a63d-4ecb6163751f@u72g2000hsf.googlegroups.com> On Feb 24, 4:50 pm, moro...@world.std.spaamtrap.com (Michael Moroney) wrote: > moro...@world.std.spaamtrap.com (Michael Moroney) writes: > >"Gorazd Kikelj" writes: > >>"Michael Moroney" wrote in message > >>news:fpn019$m28$1@pcls4.std.com... > >>>>vfs objects = varvfc > > >>> Thanks, Paul, but quickly inserting that line in the [global] area of > >>> smb.conf and restarting samba had no effect. I'll study the documentation > >>> on that later. > >>It's per share parameter. Just put it into share definition. > >Still can't convince it to work, on two different systems. > >[global] > > server string = Samba %v running on %h (OpenVMS) > > netbios name = %h > > security = user > > passdb backend = tdbsam > > domain master = yes > > guest account = SAMBA$GUEST > > domain logons = Yes > > log file = /samba$root/var/log_%h.%m > > create mode = 0755 > > load printers = no > > printing = OpenVMS > > vfs objects = varvfc > >[homes] > > comment = Home Directories > > browseable = no > > read only = no > > create mode = 0750 > > vfs objects = varvfc > >[test1] > > comment = test folder > > path = /samba$root/tmp > > read only = No > > guest OK = Yes > > vfs objects = varvfc > > This may actually not be an issue after all. I've been checking regular > (created with EDT) text files with Notepad from a PC to see if things > worked. I read that Notepad is rather brain damaged when working with > Samba-served files so I opened a file with Wordpad, and it works correctly. > Other tools seem to work as well. > > So there's something "funny" with Notepad. I have my notes about this at work, but IIRC, Notepad can only read files that are record-delimited by 's. The others can accept at least two different record delimiters. You can test this by using a recent enough version of Word to create files with different record delimiters. AEF ------------------------------ Date: 24 Feb 2008 22:50:58 GMT From: VAXman- @SendSpamHere.ORG Subject: Re: Samba and text files Message-ID: <47c1f4d2$0$25064$607ed4bc@cv.net> In article , moroney@world.std.spaamtrap.com (Michael Moroney) writes: >{...snip...} >This may actually not be an issue after all. I've been checking regular >(created with EDT) text files with Notepad from a PC to see if things >worked. I read that Notepad is rather brain damaged when working with >Samba-served files so I opened a file with Wordpad, and it works correctly. >Other tools seem to work as well. Something brain damaged in Weendoze? Who'd of thunk it? -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM "Well my son, life is like a beanstalk, isn't it?" http://tmesis.com/drat.html ------------------------------ Date: Sun, 24 Feb 2008 14:57:45 -0800 (PST) From: AEF Subject: Re: Samba and text files Message-ID: <85fc4078-a5cd-4086-a185-17a53d5ba0d4@i29g2000prf.googlegroups.com> On Feb 24, 6:39 pm, AEF wrote: > On Feb 24, 4:50 pm, moro...@world.std.spaamtrap.com (Michael Moroney) > wrote: > > > > > moro...@world.std.spaamtrap.com (Michael Moroney) writes: > > >"Gorazd Kikelj" writes: > > >>"Michael Moroney" wrote in message > > >>news:fpn019$m28$1@pcls4.std.com... > > >>>>vfs objects = varvfc > > > >>> Thanks, Paul, but quickly inserting that line in the [global] area of > > >>> smb.conf and restarting samba had no effect. I'll study the documentation > > >>> on that later. > > >>It's per share parameter. Just put it into share definition. > > >Still can't convince it to work, on two different systems. > > >[global] > > > server string = Samba %v running on %h (OpenVMS) > > > netbios name = %h > > > security = user > > > passdb backend = tdbsam > > > domain master = yes > > > guest account = SAMBA$GUEST > > > domain logons = Yes > > > log file = /samba$root/var/log_%h.%m > > > create mode = 0755 > > > load printers = no > > > printing = OpenVMS > > > vfs objects = varvfc > > >[homes] > > > comment = Home Directories > > > browseable = no > > > read only = no > > > create mode = 0750 > > > vfs objects = varvfc > > >[test1] > > > comment = test folder > > > path = /samba$root/tmp > > > read only = No > > > guest OK = Yes > > > vfs objects = varvfc > > > This may actually not be an issue after all. I've been checking regular > > (created with EDT) text files with Notepad from a PC to see if things > > worked. I read that Notepad is rather brain damaged when working with > > Samba-served files so I opened a file with Wordpad, and it works correctly. > > Other tools seem to work as well. > > > So there's something "funny" with Notepad. > > I have my notes about this at work, but IIRC, Notepad can only read > files that are record-delimited by 's. The others can accept > at least two different record delimiters. You can test this by using a > recent enough version of Word to create files with different record > delimiters. > > AEF I just logged into work. Yes, confirmed: Notepad can only read "CR- stream" files. Wordpad can read , , and properly. Word can read these three, too. But none of the three can read "properly". (I don't know what program requires that delimiter, but Word 2003 let's you create it!) I created test files using Word 2003. You simply save them in Plain Text mode and a dialog box comes up allowing you to pick your delimiter! (I don't have Word 2003 at home, so I had to log into work to try this.) AEF AEF ------------------------------ Date: Sun, 24 Feb 2008 20:15:54 -0500 From: norm.raphael@metso.com Subject: Re: Unable to communicate with replacement ESL drive Message-ID: This is a multipart message in MIME format. --=_alternative 0006F79B852573FA_= Content-Type: text/plain; charset="US-ASCII" David J Dachtera wrote on 02/23/2008 08:01:59 PM: > Lee Morgan wrote: > > > > Hi > > > > We have an AlphaServer GS1280 connected to an ESL322e Library > > containing 8 drives. > > > > About a week ago we had to have a drive replaced and now we are unable > > to talk to the drive. > > > > After the physical drive swapped, i ran SYSMAN> IO LIST_WWID but the > > new drive wasn't there. > > > > I then ran SYSMAN> IO FIND_WWID and this didn't find any new tape > > devices. > > > > As far as I'm aware, the FIND_WWID should see the new drive and then i > > run SYSMAN> IO REPLACE/DEVICE=/WWID= > > > > This system is in a cluster but doesn't share system disks, thus there > > is only 1 SYS$SYSTEM:SYS$DEVICES.DAT file. > > > > Has anyone experienced similar problems? > > > > HP are batting the problem to and fro between their OpenVMS team and > > the Storage Hardware team. > > Well, there's too many variables here to offer anything other than > suggestions. > > That said, make sure that the new drive is properly masked/mapped to the > FC interface which puts it onto the SAN. If it's an FC drive, check the > masking/mapping/zoning on the associated FC switch(es). > > Also, you don't mention your VMS version or ECO level. It's possible you > may need to take a reboot to clear out whatever is hosing this up. I've > seen that on V7.3-2 at various levels of FIBRE-SCSI ECOs. > > Dunno if this helps... > > David J Dachtera > (formerly dba) DJE Systems We've been replacing tape drives recently. We reboot the Fiber-to-SCSI bridge on the SAN, then do SYSMAN IO REPL $2$MGAn: (for the right n) and the new WWID gets into SYS$SYSTEM:SYS$DEVICES.DAT --=_alternative 0006F79B852573FA_= Content-Type: text/html; charset="US-ASCII"



David J Dachtera <djesys.no@spam.comcast.net> wrote on 02/23/2008 08:01:59 PM:

> Lee Morgan wrote:
> >
> > Hi
> >
> > We have an AlphaServer GS1280 connected to an ESL322e Library
> > containing 8 drives.
> >
> > About a week ago we had to have a drive replaced and now we are unable
> > to talk to the drive.
> >
> > After the physical drive swapped, i ran SYSMAN> IO LIST_WWID but the
> > new drive wasn't there.
> >
> > I then ran SYSMAN> IO FIND_WWID and this didn't find any new tape
> > devices.
> >
> > As far as I'm aware, the FIND_WWID should see the new drive and then i
> > run SYSMAN> IO REPLACE/DEVICE=/WWID=
> >
> > This system is in a cluster but doesn't share system disks, thus there
> > is only 1 SYS$SYSTEM:SYS$DEVICES.DAT file.
> >
> > Has anyone experienced similar problems?
> >
> > HP are batting the problem to and fro between their OpenVMS team and
> > the Storage Hardware team.
>
> Well, there's too many variables here to offer anything other than
> suggestions.
>
> That said, make sure that the new drive is properly masked/mapped to the
> FC interface which puts it onto the SAN. If it's an FC drive, check the
> masking/mapping/zoning on the associated FC switch(es).
>
> Also, you don't mention your VMS version or ECO level. It's possible you
> may need to take a reboot to clear out whatever is hosing this up. I've
> seen that on V7.3-2 at various levels of FIBRE-SCSI ECOs.
>
> Dunno if this helps...
>
> David J Dachtera
> (formerly dba) DJE Systems

We've been replacing tape drives recently.  We reboot the Fiber-to-SCSI
bridge on the SAN, then do SYSMAN IO REPL $2$MGAn: (for the right n)
and the new WWID gets into SYS$SYSTEM:SYS$DEVICES.DAT
--=_alternative 0006F79B852573FA_=-- ------------------------------ Date: Sun, 24 Feb 2008 18:09:38 -0600 From: Slor Subject: Uses for a MicroServer-SP? Message-ID: I recently ended up with a DecServer 3100, VT1300, a couple storage expansion units, and a MicroServer-SP. That last device is the one I'm trying to found out more about. Based on my web searches, the only documented use for it I've found is as a gateway to connect a DECnet or TCP/IP network to an SNA network. Is that pretty much it? Is it useless to me unless I'm trying to get my VMS boxes to talk to something like an IBM 360? Any pointers to further information would be most welcome. Thanks! -- James http://www.e-host-direct.com Reliable web hosting from $12/year. ------------------------------ Date: Sun, 24 Feb 2008 21:20:44 -0500 From: "Stanley F. Quayle" Subject: Re: Uses for a MicroServer-SP? Message-ID: <47C1DFAC.28030.20844B8@infovax.stanq.com> On 24 Feb 2008 at 18:09, Slor wrote: > [...] MicroServer-SP. [...] a gateway to connect a DECnet or TCP/IP network > to an SNA network. You probably have a DESNB device. I used a couple of these a ways back to communicate with an IBM mainframe which didn't have an IP stack. Once the mainframe's stack was installed and reliable, it wasn't meaningful anymore... I also used a DEMSA, which converts X.25 traffic to DECnet. Another device whose time has mostly passed. Whenever we needed support on it, the call would be routed to Australia, so there might be some use for them down there. Both devices were called "MicroServer"s, IIRC. --Stan Quayle Quayle Consulting Inc. ---------- Stanley F. Quayle, P.E. N8SQ Toll free: 1-888-I-LUV-VAX 8572 North Spring Ct., Pickerington, OH 43147 USA stan-at-stanq-dot-com http://www.stanq.com/charon-vax.html "OpenVMS, when downtime is not an option" ------------------------------ Date: Sun, 24 Feb 2008 19:23:53 -0800 (PST) From: Bob Gezelter Subject: Re: Uses for a MicroServer-SP? Message-ID: On Feb 24, 7:09 pm, Slor wrote: > I recently ended up with a DecServer 3100, VT1300, a couple storage > expansion units, and a MicroServer-SP. That last device is the one I'm > trying to found out more about. Based on my web searches, the only > documented use for it I've found is as a gateway to connect a DECnet or > TCP/IP network to an SNA network. Is that pretty much it? Is it useless > to me unless I'm trying to get my VMS boxes to talk to something like an > IBM 360? Any pointers to further information would be most welcome. > > Thanks! > > -- > Jameshttp://www.e-host-direct.com > Reliable web hosting from $12/year. Stan, Do you remember the details of what processors etc. that those systems contained? - Bob Gezelter, http://www.rlgsc.com ------------------------------ End of INFO-VAX 2008.111 ************************