1 INFO-VAX	Fri, 07 Apr 2006	Volume 2006 : Issue 193       Contents:$ Re: "Mount Verify" messages in OPCOM Re: Anyone for CORAL? # Re: CI Path Errors (was Re: Errors) # Re: CI Path Errors (was Re: Errors) # Re: CI Path Errors (was Re: Errors)  Re: DECWindows not starting  Re: DECWindows not starting  Errors.  Re: old uVAX needs a home ' Re: OpenVMS is the worlds best desktop! . RE: Opinion: I was just trying to sell OpenVMS" Recall /all oddness on Alpha 7.3-1& Re: Recall /all oddness on Alpha 7.3-1& Re: Recall /all oddness on Alpha 7.3-1& RE: Recall /all oddness on Alpha 7.3-1& Re: Recall /all oddness on Alpha 7.3-1@ Star Coupler failures (was: Re: CI Path Errors (was Re: Errors))D Re: Star Coupler failures (was: Re: CI Path Errors (was Re: Errors))D Re: Star Coupler failures (was: Re: CI Path Errors (was Re: Errors))D Re: Star Coupler failures (was: Re: CI Path Errors (was Re: Errors)) Re: Using the Serial Terminal  VMS-BASIC + RMS + HTML (demo)   F ----------------------------------------------------------------------   Date: 7 Apr 2006 10:15:19 -0500 . From: brooks@cuebid.zko.hp.nospam (Rob Brooks)- Subject: Re: "Mount Verify" messages in OPCOM , Message-ID: <oq7bC0trethx@cuebid.zko.hp.com>  B "David J. Dachtera" <djesys.nospam@NeOaSrPtAhMlNiOnWk.net> writes:
 > I wrote:  N >> Overloaded HSG80's will apply backpressure to the fibre channel port driverK >> if it's getting more I/O than it can handle  (the notorious "queue full" O >> problem).  That'll also cause mount verifications that are not indicative of : >> failing hardware.  Underconfigured yes, but broken, no. > J > We're seeing the same kind of OPCOM messages as Dave, but when I look onJ > the console of the HSG associated with the underlying volume I'm gettingI > tremendous numbers of "command aborted" messages, much faster than 9600 @ > baud can accommodate - the screen scrolls constantly at times. > 8 > Any ideas where to start looking for a possible cause?  H Please log a support call; these HSG80 backpressure issues can be ratherL twisted, and I'm not directly involved with the port driver work that's beenD done to mitigate it, so I'm not the right person to troubleshoot it.  L I *thought* that relatively recent FIBRE_SCSI kits solved this problem; it's: possible that this is a slightly different manifestation.    --    H Rob Brooks    VMS Engineering -- Exec Group     brooks!cuebid.zko.hp.com   ------------------------------   Date: 7 Apr 2006 07:11:55 -0700 ) From: "Jon Lockett" <jon.lockett@eds.com>  Subject: Re: Anyone for CORAL?C Message-ID: <1144419115.544344.188140@e56g2000cwe.googlegroups.com>    Tom Linden wrote: 0 > On Thu, 06 Apr 2006 08:18:01 -0700, TriumphMan, > <triumphman@karibuni.fsworld.co.uk> wrote: > G > > We used CORAL-66 first on a Honeywell DDP-516 (Honeywell compiler), K > > then on a PDP-11/45 and later on various MicroPDP-11s (RMCS compiler by I > > Robert Firth), then on the VAX under VMS (a completely different RMCS F > > compiler by John Hunter). The application was flight data recorderK > > replay and analysis (still doing that today, but m$ and C++ - sigh). We J > > started to use CORAL because it was a viable alternative to FORTRAN on> > > the DDP-516. We found the code quality much improved (moreI > > maintainable, lower bug density) when we made the change. And somehow E > > we stuck with it until the late 1990's. Now it seems much of that E > > system software is lost. I have heard that a copy the RMCS PDP-11 J > > compiler has been found but I don't hold out much hope for the others.J > > Pity; how am I going to compile my source code now there are emulators > > available? ;-) > > H > I thought the CORAL-66 compiler on the VAX used the PL/I backend, VCG.H > Have a vague recollection of speaking with someonefrom Reading 1981 at > the Systems show in Munich.   C The OpenVMS CORAL compilers from EDS don't use the PL/I backend. In D 1981, DEC had their own CORAL compiler and presumably this used VCG.F The EDS compiler generates VAX code and, on Alpha/Itanium, uses the HP? AMACRO/IMACRO compilers to generate the appropiate object code.    ------------------------------  # Date: Fri, 07 Apr 2006 14:29:41 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com>, Subject: Re: CI Path Errors (was Re: Errors)1 Message-ID: <pHuZf.6029$BG.5821@news.cpqcorp.net>    Leigh wrote:  G > The VAX has whinged a couple of times over a month about device PAA0: I > and says that it has gone from GOOD to BAD once for node 6 and once for 	 > node 7.   I    The CI is a dual-path device, so this implies one of the two paths is  H having at least transient communications problems.  The CI cluster will G operate on the other path, until either the failed path starts working  ' or until the remaining path also fails.   @ > Does this indicate a real problem or is it an occasional blip.  I    This could be a cabling problem or a controller failure, or incorrect  G termination.  Cables can be bent into a a radius a little too tightly,  E or dinged, and this can damage the coax.  Check the cable radii, the  E connections and termination and the cables themselves, and check the  F error log for the specific error(s) being reported.  The star coupler < itself is entirely passive and unpowered, and tends to be a $ correspondingly low risk of failure.  ) > I can probably get more info if needed.   3    The error log may (will?) have more information.   H    I will assume you are aware that this is very old VAX 6000 model 610 G series box, and CI and HSJ/HSC storage iron, and that old iron can and  H does tend to have an increasing likelihood of failures, it does tend to F drift toward the margins of the tolerances and specifications, and it I can and does become far more difficult to acquire spares and replacement  H parts.  (An Integrity rx2620 series box would run rings around this old E VAX 6000 series box, too, in terms of speed and storage capacity and  , physical size and power requirements and...)   ------------------------------   Date: 7 Apr 2006 07:56:09 -0700 1 From: "Leigh" <LGBowden@bowdenfamily.fsnet.co.uk> , Subject: Re: CI Path Errors (was Re: Errors)B Message-ID: <1144421769.663423.17070@i40g2000cwc.googlegroups.com>   Thanks,   D The cables are tight. One controller is on the light blue thin stuffG and the other is on the thick dark blue stuff. They're as straight as I > can make them but the thick stuff is mostly still on the reel.  A Both controllers aren't showing any error lights on the front and G aren't displaying any error messages either (hence link lights/activity  lights).  @ I've asked the customer to increase the disk usage to see if the= frequency goes up. Twice in a month could be just transitory?   G As for fixing it - the HSJ's I've found to be the worst. The VAX, HSC90 F and Star coupler are OK. I've only had one RA92 failure in nearly fourA years and one RA72. I appreciate that they're old but it has been F pretty good. Certainly better than some stuff half the age. Also thereG was a blower failure in it as well. That's about one fault a year. I've D tried to get the customer interested in the Charon VAX 6610 emulator8 but whilst it remains "reliable" they're not interested.   ------------------------------  $ Date: Fri, 7 Apr 2006 12:05:01 -0400 From: norm.raphael@metso.com, Subject: Re: CI Path Errors (was Re: Errors)Q Message-ID: <OF83D50C4D.DAC66905-ON85257149.0057B265-85257149.0058595A@metso.com>   D bill@wcschmidt.com meant to reply to this on 04/07/2006 11:34:04 AM:  G During heavy loads, the keep alive timer complains and will log errors, A have you logged into the HSJ's to make sure there isn't a problem - there, check out the last error message code.     G Hoff Hoffman <hoff-remove-this@hp.com> wrote on 04/07/2006 10:29:41 AM:    > Leigh wrote: > I > > The VAX has whinged a couple of times over a month about device PAA0: K > > and says that it has gone from GOOD to BAD once for node 6 and once for  > > node 7.  > J >    The CI is a dual-path device, so this implies one of the two paths isI > having at least transient communications problems.  The CI cluster will H > operate on the other path, until either the failed path starts working) > or until the remaining path also fails.  > B > > Does this indicate a real problem or is it an occasional blip. > J >    This could be a cabling problem or a controller failure, or incorrectH > termination.  Cables can be bent into a a radius a little too tightly,F > or dinged, and this can damage the coax.  Check the cable radii, theF > connections and termination and the cables themselves, and check theG > error log for the specific error(s) being reported.  The star coupler = > itself is entirely passive and unpowered, and tends to be a & > correspondingly low risk of failure. > + > > I can probably get more info if needed.  > 5 >    The error log may (will?) have more information.  > I >    I will assume you are aware that this is very old VAX 6000 model 610 H > series box, and CI and HSJ/HSC storage iron, and that old iron can andI > does tend to have an increasing likelihood of failures, it does tend to G > drift toward the margins of the tolerances and specifications, and it J > can and does become far more difficult to acquire spares and replacementI > parts.  (An Integrity rx2620 series box would run rings around this old F > VAX 6000 series box, too, in terms of speed and storage capacity and. > physical size and power requirements and...)   ------------------------------  % Date: Fri, 07 Apr 2006 02:05:47 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> $ Subject: Re: DECWindows not starting, Message-ID: <4436010D.DDB4DC2D@teksavvy.com>   FredK wrote:L > Uh, a server needs hardware?  So why would you expect it to start a server > if you have no graphics?  A The confusion comes because on VMS, the server startup and client A startup are not separate. I too was bitten by this some time ago.   P There should have been a DECW$SERVER_STARTUP.COM   and a DECW$CLIENT_STARTUP.COM  G And in SYSGEN, perhaps a new value to WINDOW_SYSTEM tell the system you  want client only software.   ------------------------------  $ Date: Fri, 7 Apr 2006 08:59:33 -0400* From: "FredK" <fred.nospam@nospam.dec.com>$ Subject: Re: DECWindows not starting* Message-ID: <44366236@usenet01.boi.hp.com>  : "JF Mezei" <jfmezei.spamnot@teksavvy.com> wrote in message& news:4436010D.DDB4DC2D@teksavvy.com... > FredK wrote:G > > Uh, a server needs hardware?  So why would you expect it to start a  server > > if you have no graphics? > C > The confusion comes because on VMS, the server startup and client C > startup are not separate. I too was bitten by this some time ago.  > : > There should have been a DECW$SERVER_STARTUP.COM   and a DECW$CLIENT_STARTUP.COM  > I > And in SYSGEN, perhaps a new value to WINDOW_SYSTEM tell the system you  > want client only software.  H Why?  To avoid an informational message?  The logical name to not try toK start the workstation software does what a new SYSGEN value would do (don't I get me started with WINDOW_SYSTEM - it has been turned into a meaningless  mess).   ------------------------------   Date: 7 Apr 2006 03:52:16 -0700 1 From: "Leigh" <LGBowden@bowdenfamily.fsnet.co.uk>  Subject: Errors.C Message-ID: <1144407136.439510.175720@z34g2000cwc.googlegroups.com>   @ This is a VAX 6610 with star coupler leading too a HSC90 and twoE HSJ40's in dual redundant mode which, all in all, equates too 4 nodes + on a CI cluster. The two HSJ's are 6 and 7.   E The VAX has whinged a couple of times over a month about device PAA0: G and says that it has gone from GOOD to BAD once for node 6 and once for  node 7.   > Does this indicate a real problem or is it an occasional blip.F Performance doesn't seem to have been affected but I do wish the HSJ's@ had link and activity lights on them. Make life a little easier.  ' I can probably get more info if needed.    ------------------------------  $ Date: Fri, 7 Apr 2006 09:12:30 -0400& From: "John Allain" <allain@panix.com>" Subject: Re: old uVAX needs a home, Message-ID: <e15ofn$a15$1@reader1.panix.com>  2 William <william.bader@gmail.com> wrote in messageD > A few people have inquired about the uVAXen, but we don't have any > takers so far.  It's sad.    Thanks for posting here.K For the record, we made an effort to get a truck down to you and found that J the machines had been disposed too soon.  Thanks for making the effort; if? you could've waited until 03-April things would've been better. ' Others out there: Don't be discouraged.    John A.  MARCH at the infoAge Museum    ------------------------------  $ Date: Fri, 7 Apr 2006 08:55:31 -0400* From: "FredK" <fred.nospam@nospam.dec.com>0 Subject: Re: OpenVMS is the worlds best desktop!* Message-ID: <44366144@usenet01.boi.hp.com>  / "GreyCloud" <mist@cumulus.com> wrote in message 4 news:9IqdnUaAQ5BDd6jZnZ2dnUVZ_vGdnZ2d@bresnan.com... > Bill Gunshannon wrote: >    > > F > > So, how would you propose paying VMS Engineering?  With the excessH > > profits HP gets for selling Wintel hardware?  (Sure sounds like more! > > creeping Stallmanism to me!!)  > C > The same way that Sun and the others are doing it... thru support  > service contracts.H > I'm not exactly for Stalls methods, but at least a bit of common senseG > wouldn't hurt.  But as soon as a new trend starts, like free software J > and such, then unfortunately the rate of innovation will be slown down aG > bit.  For example, I can't see paying over a $1000 for a good fortran < > compiler as a hobbyist.  As a professional I could see it. >   G I'll point out here that the sucessful example of this is Linux - where J aisde from a handful of deveopers - the labor is free.  The business modelJ for it that has worked doesn't really give it away free but includes it asL part of a subscription service (Red Hat).  They can do it because they don'tK have to have a huge engineering budget for either hardware or software.  So 4 they can afford to still give away Fedora downloads.  L The SUN model hasn't helped their bottom line - they still are losing money.D Despite the large number of downloads they claim, it hasn't led to aH groundswell of new users to rival Windows (which while it may be bundledK with a new PC - isn't "free") or Linux.  Nor can they do away with or slash J their engineering budgets.  I think the SUN experiment was a great idea toK try to stem the tide of users leaving Solaris for Linux - but it is hard to  argue that it worked.    ------------------------------  $ Date: Fri, 7 Apr 2006 10:13:37 -0400' From: "Main, Kerry" <Kerry.Main@hp.com> 7 Subject: RE: Opinion: I was just trying to sell OpenVMS T Message-ID: <FA60F2C4B72A584DBFC6091F6A2B8684011FA3A6@tayexc19.americas.cpqcorp.net>   > -----Original Message-----$ > From: bill@triangle.cs.uofs.edu=20A > [mailto:bill@triangle.cs.uofs.edu] On Behalf Of Bill Gunshannon  > Sent: April 6, 2006 8:06 AM  > To: Info-VAX@Mvb.Saic.Com 9 > Subject: Re: Opinion: I was just trying to sell OpenVMS  >=20  
 [big snip ..]   G > > Thnx much.  It won't be long till M$ usurps that particular market.  >=20< > Where have you been hiding?  MS replaced VMS in all the=20 > hospitals around" > here more than a decade ago. =20 >=20 > bill >=20 > --=20 B > Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n. =20 > Three wolvesF > bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. > University of Scranton   |E > Scranton, Pennsylvania   |         #include <std.disclaimer.h>  =20  >=20   Bill,   H You obviously have not been involved to much in the hospital scene. JustG because your local hospital has some Windows based app's, that does not ( mean the entire world has gone that way.  F Cerner is one of the biggies in health care and are very much involvedG with deploying OpenVMS (and very big GS1280's to use as an example).=20   D Bottom line is that many companies can not afford the QA and testingD required for other platforms monthly security patches (e.g. Windows, Linux etc).   C Course, companies can always choose not not test their applications H before rolling out monthly OS security patches (which typically requiresC a reboot), but then they likely do not really have mission critical 
 applications.    Regards   
 Kerry Main Senior Consultant  HP Services Canada Voice: 613-592-4660  Fax: 613-591-4477  kerryDOTmainAThpDOTcom (remove the DOT's and AT)=20  4 OpenVMS - the secure, multi-site OS that just works.   ------------------------------   Date: 7 Apr 2006 07:01:09 GMT 2 From: "Dave Weatherall" <djw-nothere@nospam.nohow>+ Subject: Recall /all oddness on Alpha 7.3-1 ? Message-ID: <DTiotGxQ0bj6-pn2-Ek8vLnC7xs2Q@dave2_os2.home.ours>    One for Guy E                         this may have been seen and already resolved,    Yesterday I tried    	reca /all sub  F to recover a submit command. I didn't find the one I wanted because it@ had been stored in the recall buffer with a leading space...e.g.   recall /all    dir 	 sub job_a  dir 
  sub job_b dir 	 sub job_x 	 sub job_x    I never got ' sub job_b' back.     --   Cheers - Dave W.   ------------------------------  % Date: Fri, 07 Apr 2006 10:24:50 +0100 0 From: Chris Sharman <chris.sharman@sorry.nospam>/ Subject: Re: Recall /all oddness on Alpha 7.3-1 4 Message-ID: <e15b53$1v3$1$8302bc10@news.demon.co.uk>   Dave Weatherall wrote: > Yesterday I tried  > 	reca /all subH > to recover a submit command. I didn't find the one I wanted because itB > had been stored in the recall buffer with a leading space...e.g. > 
 > recall /all  >  > dir  > sub job_a  > dir  >  sub job_b > dir  > sub job_x  > sub job_x  > ! > I never got ' sub job_b' back.    F I don't think you can - I wondered if quoting, or extended parsing and/ "recall ^ sub" would do it, but no, it doesn't. E Some later version of vms added recall/search, which would provide a  ? workaround. 7.3-1 is unsupported, so I guess it will stay bust.    Chris    ------------------------------  % Date: Fri, 07 Apr 2006 13:31:09 +0200 ( From: Paul Sture <paul.sture@bluewin.ch>/ Subject: Re: Recall /all oddness on Alpha 7.3-1 + Message-ID: <49n0ruFpcuf6U1@individual.net>    Dave Weatherall wrote:
 > One for Guy G >                         this may have been seen and already resolved,  >  > Yesterday I tried  >  > 	reca /all sub > H > to recover a submit command. I didn't find the one I wanted because itB > had been stored in the recall buffer with a leading space...e.g. > 
 > recall /all  >  > dir  > sub job_a  > dir  >  sub job_b > dir  > sub job_x  > sub job_x  > ! > I never got ' sub job_b' back.   >   5 Tested on V8.2, where it appears this has been fixed.   H Here's a workaround from V7.2 days (and maybe before that) which allows F you to search the recall commands, even if the string you are looking * for isn't at the beginning of the command.   $ sh sym recI    REC == "pipe recall/all > sys$login:recall.out ; @sys$login:searchbuf"    $! sys$login:searchbuf.com $! ----------------------- $!8 $ if f$search("sys$login:recall.out") .eqs. "" then exit, $ search/match=and sys$login:recall.out 'p1'% $ delete/nolog sys$login:recall.out;*    ------------------------------  $ Date: Fri, 7 Apr 2006 08:57:50 -0400' From: "Main, Kerry" <Kerry.Main@hp.com> / Subject: RE: Recall /all oddness on Alpha 7.3-1 T Message-ID: <FA60F2C4B72A584DBFC6091F6A2B8684011FA334@tayexc19.americas.cpqcorp.net>   > -----Original Message-----< > From: Dave Weatherall [mailto:djw-nothere@nospam.nohow]=20 > Sent: April 7, 2006 3:01 AM  > To: Info-VAX@Mvb.Saic.Com - > Subject: Recall /all oddness on Alpha 7.3-1  >=20
 > One for Guy G >                         this may have been seen and already resolved,  >=20 > Yesterday I tried  >=20 > 	reca /all sub >=20H > to recover a submit command. I didn't find the one I wanted because itB > had been stored in the recall buffer with a leading space...e.g. >=20
 > recall /all  >=20 > dir  > sub job_a  > dir  >  sub job_b > dir  > sub job_x  > sub job_x  >=20# > I never got ' sub job_b' back.=20  >=20 > --=20  > Cheers - Dave W. >=20  G Dave, try the following instead: (the /search qual came in around 7.3-1  timeframe via ECO as I recall)   $ recall/search sub    Regards   
 Kerry Main Senior Consultant  HP Services Canada Voice: 613-592-4660  Fax: 613-591-4477  kerryDOTmainAThpDOTcom (remove the DOT's and AT)=20  4 OpenVMS - the secure, multi-site OS that just works.   ------------------------------  # Date: Fri, 07 Apr 2006 14:35:43 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com>/ Subject: Re: Recall /all oddness on Alpha 7.3-1 1 Message-ID: <3NuZf.6030$lH.5375@news.cpqcorp.net>    Dave Weatherall wrote: ... G >                         this may have been seen and already resolved,  ...  > Yesterday I tried  >  > 	reca /all sub  E    Known, reported, and already fixed.  There was an ECO kit out for  H this and a few other DCL bugs for the supported OpenVMS releases, IIRC, I but I don't know that the kit made it as far back as this V7.3-1 release.    ------------------------------  $ Date: Fri, 7 Apr 2006 11:08:06 -0400 From: norm.raphael@metso.comI Subject: Star Coupler failures (was: Re: CI Path Errors (was Re: Errors)) Q Message-ID: <OF1EBA2CBE.D14B9798-ON85257149.0052DC16-85257149.0053239C@metso.com>   G Hoff Hoffman <hoff-remove-this@hp.com> wrote on 04/07/2006 10:29:41 AM:    > Leigh wrote: > I > > The VAX has whinged a couple of times over a month about device PAA0: K > > and says that it has gone from GOOD to BAD once for node 6 and once for  > > node 7.  > J >    The CI is a dual-path device, so this implies one of the two paths isI > having at least transient communications problems.  The CI cluster will H > operate on the other path, until either the failed path starts working) > or until the remaining path also fails.  > B > > Does this indicate a real problem or is it an occasional blip. > J >    This could be a cabling problem or a controller failure, or incorrectH > termination.  Cables can be bent into a a radius a little too tightly,F > or dinged, and this can damage the coax.  Check the cable radii, theF > connections and termination and the cables themselves, and check the5 > error log for the specific error(s) being reported.    > The star coupler= > itself is entirely passive and unpowered, and tends to be a & > correspondingly low risk of failure.  G Hoff, Has anyone actually logged a start coupler failure in the history H of Field Service?  Short of someone or something physically damaging theI beast (Fire, Flood, Dropping a save on it, maybe) what can possibly fail?    > + > > I can probably get more info if needed.  > 5 >    The error log may (will?) have more information.  > I >    I will assume you are aware that this is very old VAX 6000 model 610 H > series box, and CI and HSJ/HSC storage iron, and that old iron can andI > does tend to have an increasing likelihood of failures, it does tend to G > drift toward the margins of the tolerances and specifications, and it J > can and does become far more difficult to acquire spares and replacementI > parts.  (An Integrity rx2620 series box would run rings around this old F > VAX 6000 series box, too, in terms of speed and storage capacity and. > physical size and power requirements and...)   ------------------------------   Date: 7 Apr 2006 08:34:04 -0700  From: bill@wcschmidt.comM Subject: Re: Star Coupler failures (was: Re: CI Path Errors (was Re: Errors)) C Message-ID: <1144424044.184209.238750@j33g2000cwa.googlegroups.com>   G During heavy loads, the keep alive timer complains and will log errors, A have you logged into the HSJ's to make sure there isn't a problem - there, check out the last error message code.    norm.raphael@metso.com wrote: I > Hoff Hoffman <hoff-remove-this@hp.com> wrote on 04/07/2006 10:29:41 AM:  >  > > Leigh wrote: > > K > > > The VAX has whinged a couple of times over a month about device PAA0: M > > > and says that it has gone from GOOD to BAD once for node 6 and once for 
 > > > node 7.  > > L > >    The CI is a dual-path device, so this implies one of the two paths isK > > having at least transient communications problems.  The CI cluster will J > > operate on the other path, until either the failed path starts working+ > > or until the remaining path also fails.  > > D > > > Does this indicate a real problem or is it an occasional blip. > > L > >    This could be a cabling problem or a controller failure, or incorrectJ > > termination.  Cables can be bent into a a radius a little too tightly,H > > or dinged, and this can damage the coax.  Check the cable radii, theH > > connections and termination and the cables themselves, and check the7 > > error log for the specific error(s) being reported.  >  > > The star coupler? > > itself is entirely passive and unpowered, and tends to be a ( > > correspondingly low risk of failure. > I > Hoff, Has anyone actually logged a start coupler failure in the history J > of Field Service?  Short of someone or something physically damaging theK > beast (Fire, Flood, Dropping a save on it, maybe) what can possibly fail?  >  > > - > > > I can probably get more info if needed.  > > 7 > >    The error log may (will?) have more information.  > > K > >    I will assume you are aware that this is very old VAX 6000 model 610 J > > series box, and CI and HSJ/HSC storage iron, and that old iron can andK > > does tend to have an increasing likelihood of failures, it does tend to I > > drift toward the margins of the tolerances and specifications, and it L > > can and does become far more difficult to acquire spares and replacementK > > parts.  (An Integrity rx2620 series box would run rings around this old H > > VAX 6000 series box, too, in terms of speed and storage capacity and0 > > physical size and power requirements and...)   ------------------------------  $ Date: Fri, 7 Apr 2006 11:43:45 -0400) From: "Ken Robinson" <kenrbnsn@gmail.com> M Subject: Re: Star Coupler failures (was: Re: CI Path Errors (was Re: Errors)) G Message-ID: <7dd80f60604070843ib975158l76a4fc872a957334@mail.gmail.com>   A On 4/7/06, norm.raphael@metso.com <norm.raphael@metso.com> wrote: I > Hoff, Has anyone actually logged a start coupler failure in the history J > of Field Service?  Short of someone or something physically damaging theK > beast (Fire, Flood, Dropping a save on it, maybe) what can possibly fail?  >   F I believe the Star Coupler was a passive device (no electricity neededE for it to operate). Back in the 1980's when I was at Bellcore, an air D conditioning water pipe broke in the ceiling above our Star Coupler.A The Star Coupler didn't fail, even with the water pouring through D it... The machines had to be powered down due to the water under the- raised floors, but the Star Coupler was fine.    Ken    ------------------------------  $ Date: Fri, 7 Apr 2006 12:04:03 -0400 From: norm.raphael@metso.comM Subject: Re: Star Coupler failures (was: Re: CI Path Errors (was Re: Errors)) Q Message-ID: <OF0749EF7A.ECB1A912-ON85257149.00582136-85257149.005842CB@metso.com>   D "Ken Robinson" <kenrbnsn@gmail.com> wrote on 04/07/2006 11:43:45 AM:  C > On 4/7/06, norm.raphael@metso.com <norm.raphael@metso.com> wrote: K > > Hoff, Has anyone actually logged a start coupler failure in the history H > > of Field Service?  Short of someone or something physically damaging the G > > beast (Fire, Flood, Dropping a save on it, maybe) what can possibly  fail?  > >  > H > I believe the Star Coupler was a passive device (no electricity neededG > for it to operate). Back in the 1980's when I was at Bellcore, an air F > conditioning water pipe broke in the ceiling above our Star Coupler.C > The Star Coupler didn't fail, even with the water pouring through F > it... The machines had to be powered down due to the water under the/ > raised floors, but the Star Coupler was fine.  >  > Ken   K That's what I thought.  Maintenance was $8 or $10 per month during the 80's > and 90's.  I could never understand what was actually covered.   ------------------------------   Date: 7 Apr 2006 07:46:17 -0700 $ From: "Wilm" <w4.boerhout@planet.nl>& Subject: Re: Using the Serial TerminalC Message-ID: <1144421177.424407.252490@g10g2000cwb.googlegroups.com>   ? One of my customer users serial comms on (VAX-)VMS in two ways:   C 1. A user uses a PC to connect to a VMS application with a terminal E emulator. The application uses FMS forms. Input from a weighing scale F is routed to the FMS form via a terminal emulator script. The scale isE connected to the COM-port of the PC that hosts the terminal emulator. G >From a VMS point of view, this input is "as if typed on the keyboard". G No special provisions are taken in the application. The user just types 6 in the weight, as far as the application is concerned.  G 2. That same application environment drives a nummer of pallet devices, F to place large pallets full of books into a warehouse. The device thatD actually moves the pallets and drives the cranes is a PC. This PC isC connected to VMS via two serial lines, a "send line" and a "receive F Line". VMS allocates two serial lines, say TXC0: and TXC1: on startup.F The application on the PC and the VMS application have a protocol thatC allows datagrams to be sent back and forth, and acted upon. The low @ level protcocol is "transparent binary" on the VMS serial lines.  G The command used to set the line characteristics for these lines on VMS  startup is:    $SET TERM TXcn:  /PERMANENT-
 /NOBROADCAST- 	 /NOWRAP -  /SPEED=(9600)- /DEVICE_TYPE(unknown)-
 /NOAUTOBAUD -  /NOFORM-	 /PASTHRU-  /NOECHO- /PARITY=ODD /NOEIGHT_BIT - /TYPEAHEAD- 
 /NOTTSYNC-
 /SYSPASSWORD-  /DISMISS   HTH, /Wilm    ------------------------------  $ Date: Fri, 7 Apr 2006 12:05:06 -0400) From: "Neil Rieck" <n.rieck@sympatico.ca> & Subject: VMS-BASIC + RMS + HTML (demo)9 Message-ID: <B4wZf.3129$sh3.221675@news20.bellglobal.com>    Mark,   F I've received a few requests this week regarding BASIC + RMS + HTML soL (since I was on vacation) I decided to do a stand-alone demo. Here is a stub" from my "free VMS demos" web page.  ? http://www3.sympatico.ca/n.rieck/demo_vms/basic_apache_demo.zip   	     ##### B Click download a quick hack demo program that shows how to extractL information from a web page submitted to Apache for OpenVMS (CSWS) using CGII (Common Gateway Interface). This program can run in four different modes: G CRT (green screen), WEB=GET, WEB=POST and WEB=GET+POST. It shows how to C submit forms. It contains a small amount of RMS code to show how to E interface RMS to the WEB. It also shows how to do a JAVASCRIPT pop-up  window. 	     #####   L p.s. This was cobbled together from other programs so forgive the mess. I'llG try to clean it up and add a few more Apache-2 features in the next few  weeks   
 Neil Rieck Kitchener/Waterloo/Cambridge,  Ontario, Canada.8 http://www3.sympatico.ca/n.rieck/links/cool_openvms.html9 http://www3.sympatico.ca/n.rieck/links/openvms_demos.html    ------------------------------   End of INFO-VAX 2006.193 ************************                                                                                                                                                                                                                                                                                                                                                                                                                                                             .endm $$rms_xaset  w w      	      _lm,  .macro $$rms_rvset p0 p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15 p16 p17 p18 p19 p20 p21 p22 p23 p24 p25 p26 p27 p28 p29 p30 p31 p32 p33 p34 p35 p36 p37 p38 p39 p40 p41 p42 p43 p44 p45 p46 p47 p48 p49C 		.error "Macro $$RMS_RVSET is not supported for use with MACRO-64"  .endm $$rms_rvset  w w         _lm,  .macro $$rms_rset p0 p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15 p16 p17 p18 p19 p20 p21 p22 p23 p24 p25 p26 p27 p28 p29 p30 p31 p32 p33 p34 p35 p36 p37 p38 p39  
  p40 p41 p42 p43 p44 p45 p46 p47 p48 p49 B 		.error "Macro $$RMS_RSET is not supported for use with MACRO-64" .endm $$rms_rset w w         _lm,  .macro $$rms_rcset p0 p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15 p16 p17 p                                                                                                                                                                                                                                               