1 INFO-VAX	Mon, 21 Aug 2006	Volume 2006 : Issue 465       Contents: Re: Alpha remembrance day  Re: Alpha remembrance day  Re: Alpha remembrance day % Re: ANN: DynDNS update client for VMS % Re: ANN: DynDNS update client for VMS ) Re: DEC is alive, in the pejorative sense  Dibol programmers ! Re: Difference between VM and VMS . SEPPUCLU bugcheck introducing new cluster node2 Re: SEPPUCLU bugcheck introducing new cluster node2 Re: SEPPUCLU bugcheck introducing new cluster node2 Re: SEPPUCLU bugcheck introducing new cluster node2 Re: SEPPUCLU bugcheck introducing new cluster node2 Re: SEPPUCLU bugcheck introducing new cluster node2 Re: SEPPUCLU bugcheck introducing new cluster node. VGA video adapter for Vaxstation 4000 model 602 Re: VGA video adapter for Vaxstation 4000 model 60 Re: Wireless handhelds Re: Wireless handhelds Re: Wireless handhelds Re: Wireless handhelds  F ----------------------------------------------------------------------    Date: 21 Aug 2006 03:45:38 -0700- From: "Andrew" <andrew_harrison@symantec.com> " Subject: Re: Alpha remembrance dayC Message-ID: <1156157138.766417.270840@h48g2000cwc.googlegroups.com>    Bill Todd wrote: > Andrew wrote:  > > Bill Todd wrote: > >> Andrew wrote: > >> > >> ... > >>N > >>>>> The whole discussion has now become extremely boring and so I will notK > >>>>> be responding to any more of your posts on this subject unless they M > >>>>> contain well thought out and relevant points which don't descend into  > >>>>> abuse. > >>>> Good riddance, asshole.I > >>> Let me spell it out for you since you seem to have missed the point  > >>> again. > >  > >> Exactly what part of  > >>L > >> "The whole discussion has now become extremely boring and so I will notH > >> be responding to any more of your posts on this subject unless theyQ > >> contain well thought out and relevant points which don't descend into abuse"  > >>J > >> (still right up there above) would you suggest that I misinterpreted,K > >> asshole?  I was deliberately and pointedly abusive at least in part to L > >> see whether you'd hold to your expressed resolve - but, of course, your: > >> words there were as empty as most of your others are. > > K > > Since we are obviously no longer discussing Alpha's apparent demise let  > > me offer you some advice.  > ; > While yet again making a mockery of your own words above.  >  > > 5 > > Being rude is not a means to winning an argument.  > G > Being rude is a last resort when dealing with persistent incompetents I > who won't either wise up or shut up.  The alternative is ignoring them, 1 > and in some cases that's the right thing to do.  > C > With people like you, however, that just encourages them (as your H > history here bears out:  it's hardly a snap-judgment on my part).  AndJ > when the matter is an issue of some importance (as I already observed inF > borrowing from Santayana's observation about learning from history),$ > that's not a good idea in my book. > C > So, as I also already observed, get used to it if you're going to D > continue being persistently incompetent.  I'm no longer making anyI > attempt to 'win an argument' (though I do continue to present the facts G > just in case any casual on-lookers might be confused by your drivel): ? > I'm just attempting to exterminate a pest with whatever blunt  > instruments may come to hand.   G Well reading back through the last six posts you made on this thread we  get.  	 Rudeness.   $ Introduction of an irrelevant point.  	 Rudeness.   ; Stating the absolutely obvious (some people don't upgrade).    Rudeness  ' Introduction of more irrelevant points.    Rudeness  : Refusal to restate aledgedly relevant and coherant points.   Rudeness  B Now this would be ok ish if there had been any content between theE rudeness, the irrelevance or the statements of the absolutely obvious  but there wasn't.   G If that is what passes for you putting down the consitently incompetent ) then you really need to try a bit harder.    Regards  Andrew Harrison    ------------------------------    Date: 21 Aug 2006 04:52:01 -0700- From: "Andrew" <andrew_harrison@symantec.com> " Subject: Re: Alpha remembrance dayC Message-ID: <1156161121.049466.318940@h48g2000cwc.googlegroups.com>    JF Mezei wrote:  > Michael Kraemer wrote:> > > yeah, promise, and that's it. Technical merits are nothing9 > > if the time window for broad introduction has closed.  > H > Well, considering it was the first "mainstream" 64 bit architecture, IJ > wouldn't say that Alpha was late. If at all, it was early to the market.D >  DEC was late only in lowering prices for its VAX lines to stay in" > business until Alpha came along. >   C No it wasn't MIPS was 64 bit before Alpha and MIPS was a mainstream 7 processor. The R4000 was released in 1991 before Alpha.   G In any case for much of the market it was a complete re-herring because G Digital didn't build boxes which were big enough support decent amounts > of memory, I/O and CPU's in the same package at the same time.  - > > > The FABs were at the time, a good idea,  > > 8 > > No it wasn't. It was another example of DECs hybris:7 > > "we are so great, we can do everything on our own".  > D > At the time, intel was still just a toy controller maker and thereI > weren't that many high tech FABs that were commercially available.  For H > DEC, having its own FAB was a way to be to market before any others byI > building a next generation FAB now.  Had DEC succesfully commercialised H > its FAB business, it may have had enough business to pay for upgrades.J > In the end, DEC didn't commercialise that business and it lost big moneyD > and certaintly coudn,t afford to build a next generation FAB.  DEC@ > vacating that market left the door opened for IBM and Intel toF > commerciallise their FAB business. And because of the extremely highH > costs of FABs, fewer and fewer FABs can be built, and those who stayed4 > in teh business now get everybody else's business. >   D Again not true, Sun never had a FAB using instead using TI and otherF vendors to FAB their SPARC processors, this model was in use from 1985F onwards clearly establishing that you could develop an build a complexB RISC chip without having a FAB.  MIPS also never had a FAB insteadC using NEC, IDT and other to FAB their processors and MIPS goes back  further than Sun.   E Nor was Intel a toy controller vendor. In 1992 the 486 came in at 1.4 G million transistors nor far short of the 1.6 million transistors in the A first Alpha. By marh 1993 this had jumped to 3.1 million with the ; Pentium which at its core was a superscalar RISC processor.   F > Only the fittest survive. DEC didn't exercise its FAB enough and was > eliminated from the race.  > . > > IIRC that happened when DEC still existed.@ > > And too me (and most others) was another sign of DEC heading > > for their final collapse.  > H > In the 3 years prior to the official announcement of the Compaq buyingJ > DEC, Palmer was acting on the requests of Pfeiffer to scale down DigitalG > and get rid of parts that Compaq wasn't interested in. Palmer proudly < > announced that on CNN on the day the merger was announced. >   A Like the FAB which as you point out was doomed before Palmer even  started talking to Compaq.   > J > > IBM had big losses in 1992/1993, but they also still had deep pockets. > F > Read Lou Gerstner's book. When he got in, IBM had already contractedE > with merhant banks to find buyers to sell IBM off to raise money to F > survive. The state of IBM was far worse than people had been lead to. > believe. It no longer had such deep pockets. >  > < > > But IBM already had at least some strategy when Gerstner > > took over, > H > Again, read his book. The strategy was to break the company up. It wasJ > Gerstner that immediatly  cancelled this and set the company on a course3 > where it woudl have its own strategy and compete.  > L > > Now this is hard to imagine. At that time Compaq was already three times1 > > bigger than DEC. A dwarf swallowing a giant ?  > E > Digital was #2 computer maker for a very long time, and I believ it F > still was at the time Palmer took the helm. DEC was downsized out ofA > existance uder Palmer, partly due to "suggestions" by Pfeiffer.  >   G How is that possible, Digital and Compaq started talking about a merger D in 1996. The decisions which led to Digitals downsizing were made inG some cases a decade or more earlier when it would have been unthinkable A for DEC to be taking to Compaq about anything except Compaq being  aquired.  E You seem to be mistaking cause with effect. Compaq didn't want to buy C Digital with the Hudson FAB because it was bleeding Digital dry and C would have done the same thing to Compaq. The decisions that led to G this state happened years earlier. Pfeiffer just said quite reasonably, G come back when you have done something with your FAB. The Intel IP case C came up and Palmer was handed the one decent card he had had in the 
 last 5 years.    Regards  Andrew Harrison    ------------------------------    Date: 21 Aug 2006 08:55:12 -0700- From: "Andrew" <andrew_harrison@symantec.com> " Subject: Re: Alpha remembrance dayC Message-ID: <1156175711.980664.222230@m79g2000cwm.googlegroups.com>    JF Mezei wrote:  > Michael Kraemer wrote:> > > yeah, promise, and that's it. Technical merits are nothing9 > > if the time window for broad introduction has closed.  > H > Well, considering it was the first "mainstream" 64 bit architecture, IJ > wouldn't say that Alpha was late. If at all, it was early to the market.D >  DEC was late only in lowering prices for its VAX lines to stay in" > business until Alpha came along. > - > > > The FABs were at the time, a good idea,  > > 8 > > No it wasn't. It was another example of DECs hybris:7 > > "we are so great, we can do everything on our own".  > D > At the time, intel was still just a toy controller maker and thereI > weren't that many high tech FABs that were commercially available.  For H > DEC, having its own FAB was a way to be to market before any others byI > building a next generation FAB now.  Had DEC succesfully commercialised H > its FAB business, it may have had enough business to pay for upgrades.J > In the end, DEC didn't commercialise that business and it lost big moneyD > and certaintly coudn,t afford to build a next generation FAB.  DEC@ > vacating that market left the door opened for IBM and Intel toF > commerciallise their FAB business. And because of the extremely highH > costs of FABs, fewer and fewer FABs can be built, and those who stayed4 > in teh business now get everybody else's business. > F > Only the fittest survive. DEC didn't exercise its FAB enough and was > eliminated from the race.  > . > > IIRC that happened when DEC still existed.@ > > And too me (and most others) was another sign of DEC heading > > for their final collapse.  > H > In the 3 years prior to the official announcement of the Compaq buyingJ > DEC, Palmer was acting on the requests of Pfeiffer to scale down DigitalG > and get rid of parts that Compaq wasn't interested in. Palmer proudly < > announced that on CNN on the day the merger was announced. >  > J > > IBM had big losses in 1992/1993, but they also still had deep pockets. > F > Read Lou Gerstner's book. When he got in, IBM had already contractedE > with merhant banks to find buyers to sell IBM off to raise money to F > survive. The state of IBM was far worse than people had been lead to. > believe. It no longer had such deep pockets. > F The difference is size, IBM could have sold off the mainframe divisionF as an entity and it would have been as large as Digital. Ditto for the S36/AS400 division.  > < > > But IBM already had at least some strategy when Gerstner > > took over, > H > Again, read his book. The strategy was to break the company up. It wasJ > Gerstner that immediatly  cancelled this and set the company on a course3 > where it woudl have its own strategy and compete.  >   ? Gerstner's vision was an end to end company supported by a huge B services business that helped customers integrate the PC's the AIXC boxes, the AS400's and the mainframes along with all IBM's software A products and he had the core of that when he took over the reins.   D Unlike at DEC despite being the problem rather than the solution IBMG hadn't missed the UNIX/Open Systems wave nor had it missed the PC wave. D IBM had bet on POWER and delivered early compared with Alpha, so the@ key product in their mid range arsenal was actually in OK shape.  A IBM wasn't seing large errosions in market share and it had loyal < customers for its mainframes and for its S36/AS400 platform.  > So Gersner did rather what Marc Hurd has done at HP he cut, heF streamlined etc because IBM had become big unwieldy and complacent. HeB took out layers of managment and cancelled intelligently projects.  G Palmer had a different problem, DEC had missed the PC wave, it had also > missed the mid-range and later high end systems wave driven byF UNIX/Open Systems platforms. It had no low end to speak of and its midE range was anything but secure. Most of the projects had allready been ? cancelled and Digital was in bed with Microsoft with inevitable  consequences for All In One.   Regards  Andrew Harrison    ------------------------------  % Date: Mon, 21 Aug 2006 14:27:29 +0930 * From: Mark Daniel <mark.daniel@vsm.com.au>. Subject: Re: ANN: DynDNS update client for VMS0 Message-ID: <12eiirl7emdat26@corp.supernews.com>   bradhamilton wrote:  > Mark Daniel wrote: > . >> Recent discussion of a DynDNS update client >>/ >>   http://www.dyndns.com/services/dns/dyndns/  >>E >> in this forum prompted me to do something I'd been meaning to for  E >> years - put together a native version for VMS and move the update  I >> duties from my PC to my VMS system.  It has now been running for some  I >> four weeks without too many hiccoughs so you are welcome to give it a  H >> go as well. It requires the HP [Open]SSL product to be installed and  >> started.  >>H >> A complementary application included, DynDNSrpt, is a CGI Web server H >> application that can be used as a basic reporting tool for the above G >> application (should be suitable for Apache, OSU, Purveyor and WASD).  >>G >> Setup, build instructions and revision log for each may be found in  E >> the source code each of the respective applications once restored.  >>< >> A ZIPed source-code kit (it is assumed users will be VMS C >> enthusiasts/hobbiests with their own compiler) is available from  >>! >>   http://wasd.vsm.com.au/wasd/  >> >> Hope it's useful. >> > F > Thanks, Mark.  Where would be a good "place" to ask questions, etc?  > Here, or INFO-WASD?   F It's of no specific application to info-WASD Brad so here would be of  more general value.    ------------------------------  % Date: Mon, 21 Aug 2006 15:00:42 +0930 * From: Mark Daniel <mark.daniel@vsm.com.au>. Subject: Re: ANN: DynDNS update client for VMS0 Message-ID: <12eikpu6m255vbc@corp.supernews.com>   David J. Dachtera wrote: > Mark Daniel wrote: > - >>Recent discussion of a DynDNS update client  >>/ >>   http://www.dyndns.com/services/dns/dyndns/  >>I >>in this forum prompted me to do something I'd been meaning to for years I >>- put together a native version for VMS and move the update duties from F >>my PC to my VMS system.  It has now been running for some four weeksH >>without too many hiccoughs so you are welcome to give it a go as well.C >>It requires the HP [Open]SSL product to be installed and started.  >>F >>A complementary application included, DynDNSrpt, is a CGI Web serverF >>application that can be used as a basic reporting tool for the aboveF >>application (should be suitable for Apache, OSU, Purveyor and WASD). >>I >>Setup, build instructions and revision log for each may be found in the @ >>source code each of the respective applications once restored. >>: >>A ZIPed source-code kit (it is assumed users will be VMSB >>enthusiasts/hobbiests with their own compiler) is available from >>! >>   http://wasd.vsm.com.au/wasd/  >> >>Hope it's useful.  >  > B > Just wondering if this has any advantage over the WGET approach?  E Don't know David.  I'm aware of the DCL-based utility that uses WGET  G because of the recent discussion here that mentioned it.  I didn't use  E it as a reference when putting together my own though and so I'm not  # aware of what it can (or can't do).   E When I first started to use DynDNS DDNS for my domestic network some  C time ago I looked around for a VMS update client but only remember  C finding Perl and DCL based utilities that would have been suitable  A (perhaps I quit searching too quickly).  I decided then to write  H something 'native' (i.e. an executable) sometime and fell back to using I a pre-packaged WIN32 client on my Windows-based desktop in the meantime.  F   Well, I put it off and put it off until the recent enquiry during a ( period with some spare time reminded me.  F Why use this new one?  No big reason I suppose.  If something else is G working working for you well and good.  I can't make a comparison with  D the WGET approach because I haven't used it.  However, the original E announcement might have been a bit thin so I'll list some of the new   offering's attributes:      o  C code,    o  single image in a RUN/DETACHED process'    o  light-weight process and activity 6    o  uses SSL to secure the credentials of the update2    o  logs activity through file and logical names=    o  neat little reporting utility available as a CGI script     Also (but not public attributes)  >    o  provided me some exercise writing BSD sockets based codeB    o  provided me some exercise writing BSD sockets based SSL code  I Profit margins are minimal so if you don't need it I probably won't miss   you not buying it :-)    ------------------------------    Date: 21 Aug 2006 06:09:50 -0700' From: "bclaremont" <msi1@earthlink.net> 2 Subject: Re: DEC is alive, in the pejorative senseA Message-ID: <1156165790.682571.37770@i3g2000cwc.googlegroups.com>   H > > So either VMS is truly being wond down and a very specific policy ofI > > paliative care for the remaining customer base and no attempt to grow 
 > > out of it  > G > That's the situation - no need for any 'or' clause later.  In fact, I J > think I even recall an explicit statement from HP to the effect that VMS< > was concentrating only on its existing established niches.  G I've seen this statement broadcast too, several times.  Bottom line for G HP has to be that VMS makes enough money to keep around (not to mention E contractual commitments that must be served).  However, there must be ? some pretty interesting internal strife, given that HP competed F directly against VMS for decades.  I am sure there are many misguided,> but dedicated souls within HP that would like to see VMS dead.  B As to Digital management history, I dealt directly with senior DECD staff and two senior VP's in the early 90's on a competitive programD designed to lure IBM midrange ISV's into the VMS fold.  I had one ofG the VP's say to my face: "Bruce, I'm not interested in what the program D can do for DEC, I want to know what the program can do for me."  TheF funnest job I every had was working for Digital and the fun went rightB out of it at that  point.  The subsequent demise of Digital was no	 surprise.   D I am sure some of the same attitudes exist in HP, as they do in most@ organizations.  People that act for the common good seem to grow= increasing rare as one works their way up the authority tree.    Bruce Claremont    Improved with Age  - Wine - Wisdom	 - OpenVMS    ------------------------------    Date: 21 Aug 2006 08:32:57 -0700 From: sandeep_brion@yahoo.com  Subject: Dibol programmersB Message-ID: <1156174377.254416.142930@74g2000cwt.googlegroups.com>  E We are looking for dibol programmers/consultants/full-time employees. = We are located in Wisconsin. Pls. send resume to hr@isgwi.com    Thanks   ------------------------------  % Date: Mon, 21 Aug 2006 11:03:43 -0400 , From: Hoff Hoffman <hoff-remove-this@hp.com>* Subject: Re: Difference between VM and VMS* Message-ID: <44e9cb4c@usenet01.boi.hp.com>   Babu_Ram wrote: F > In my work it is VM, Mainframe I believe VAX/VMS or OS 390, is there  > difference between VM and VMS? > B > Where can I find document to brush up my knowledge or VM or VMS?  N    I'd wager you're probably (mis)recalling the VM/CMS stack, which is an IBM M operating system environment comprised of an IBM CMS guest running on IBM VM. O If that guess is correct, you're posting in a newsgroup targeting a completely  H different operating system from a completely different vendor for three ( completely different hardware platforms.  O    As for finding documentation for most anything these days, there are always  M the available web search engines -- though you'll need to acquire additional  Q knowledge around specifically what product(s), platform(s) or environment(s) you    are looking for here, obviously.   ------------------------------  % Date: Mon, 21 Aug 2006 09:36:13 +0100 ) From: Tom Wade <nospam@picard.eurokom.ie> 7 Subject: SEPPUCLU bugcheck introducing new cluster node . Message-ID: <44E9707D.70604@picard.eurokom.ie>  
 Greetings,  ? Cluster of OpenVMS Alpha 7.3-1 machines sharing a common system E disk on a fiber array (several patches installed including UPDATE 4.0  and FIBER_SCSCI 3.0).   7 When introducing a new node, it crashes out as follows:   P ** Bugcheck code = 00000AB4: SEPPUCLU, Remote crash request / execution honoredy< ** Crash CPU: 00    Primary CPU: 00    Active CPUs: 0000000F ** Current Process = NULL  ** Current PSB ID = 00000001 ** Image Name =   S One of the other nodes (not always the same one) also crashes out with a LOCKMGRERR 	 bugcheck.   H A google search of SEPPUCLU showed up one hit: a PDF document describingJ undocumented VMS features.  SEPPUCLU only appears as a one-liner followingI the phrase "we engineers will have our fun".  It looks like this crash is  induced by the other one.   H Searches for LOCKMGRERR show up suggestions that it is a network problemI (the switch reports no errors on the port), or an issue with insufficient 3 LOCKIDTBL triggering a problem expanding the table.   F Has anyone else seen this problem ?  Should I ensure that LOCKIDTBL isI set to 4 times the number of locks in MONITOR LOCK and RESHASHTBL 4 times  the number of resources ?   9 --------------------------------------------------------- @ Tom Wade                 | EMail: tee dot wade at eurokom dot ie3 EuroKom                  | Tel:   +353 (1) 296-9696 3 A2, Nutgrove Office Park | Fax:   +353 (1) 296-9697 L Rathfarnham              | Disclaimer:  This is not a disclaimer            G Dublin 14                | Tip:   "Friends don't let friends do Unix !"  Ireland    ------------------------------    Date: 21 Aug 2006 02:27:56 -0700/ From: "Volker Halle" <volker_halle@hotmail.com> ; Subject: Re: SEPPUCLU bugcheck introducing new cluster node C Message-ID: <1156152476.571621.159790@m79g2000cwm.googlegroups.com>    Tom,  F you need to first analyze the LOCKMGRERR crash. The SEPPUCLU crash hasE most likely been induced by the node crashing with LOCKMGRERR to also A force a crash on the node, from which a possibly bad lock manager F message has been received. This should allow a comparision between theF contents of the sent and received message to determine, where it mightF have been corrupted (if the problem was actually caused by a corrupted lock message).  F Without understanding the reason for that LOCKMGRERR crash, no further> advice can be given. If you suspect data corruption on the LANE communication path, you could enable PEDRIVER checksumming by setting  NISCS_PORT_SERV=3.   Volker.    ------------------------------  % Date: Mon, 21 Aug 2006 11:34:24 -0400 / From: "William Webb" <william.w.webb@gmail.com> ; Subject: Re: SEPPUCLU bugcheck introducing new cluster node I Message-ID: <8660a3a10608210834u192d2983y2e9cd55ca8aa7ab7@mail.gmail.com>   6 On 8/21/06, Tom Wade <nospam@picard.eurokom.ie> wrote: > Greetings, > A > Cluster of OpenVMS Alpha 7.3-1 machines sharing a common system G > disk on a fiber array (several patches installed including UPDATE 4.0  > and FIBER_SCSCI 3.0).  > 9 > When introducing a new node, it crashes out as follows:  > R > ** Bugcheck code = 00000AB4: SEPPUCLU, Remote crash request / execution honoredy> > ** Crash CPU: 00    Primary CPU: 00    Active CPUs: 0000000F > ** Current Process = NULL  > ** Current PSB ID = 00000001 > ** Image Name =  > U > One of the other nodes (not always the same one) also crashes out with a LOCKMGRERR  > bugcheck.  > J > A google search of SEPPUCLU showed up one hit: a PDF document describingL > undocumented VMS features.  SEPPUCLU only appears as a one-liner followingK > the phrase "we engineers will have our fun".  It looks like this crash is  > induced by the other one.  > J > Searches for LOCKMGRERR show up suggestions that it is a network problemK > (the switch reports no errors on the port), or an issue with insufficient 5 > LOCKIDTBL triggering a problem expanding the table.  > H > Has anyone else seen this problem ?  Should I ensure that LOCKIDTBL isK > set to 4 times the number of locks in MONITOR LOCK and RESHASHTBL 4 times  > the number of resources ?  > ; > --------------------------------------------------------- B > Tom Wade                 | EMail: tee dot wade at eurokom dot ie5 > EuroKom                  | Tel:   +353 (1) 296-9696 5 > A2, Nutgrove Office Park | Fax:   +353 (1) 296-9697 B > Rathfarnham              | Disclaimer:  This is not a disclaimerI > Dublin 14                | Tip:   "Friends don't let friends do Unix !" 	 > Ireland  >   @ Am I the only one who notices the resemblance of SEPPUCLU to the Japanese word "seppuku"?  P I suspect that some engineer had tongue firmly implanted in cheek with this one.   WWWebb   --   I'm job-hunting, folks. < Any leads or referrals would be most gratefully appreciated.1 Unsolicited commercial email, however, would not.    ------------------------------  % Date: Mon, 21 Aug 2006 11:11:48 -0400 , From: Hoff Hoffman <hoff-remove-this@hp.com>; Subject: Re: SEPPUCLU bugcheck introducing new cluster node * Message-ID: <44e9cd31@usenet01.boi.hp.com>   Tom Wade wrote:   J > A google search of SEPPUCLU showed up one hit: a PDF document describingL > undocumented VMS features.  SEPPUCLU only appears as a one-liner followingK > the phrase "we engineers will have our fun".  It looks like this crash is  > induced by the other one.   O    What the bugcheck refers to isn't exactly "fun", and there are words around  M that slide that aren't included in the text of the presentation you've found.   N    This bugcheck is issued where the particular cluster node self-exits in an G attempt to allow and to preserve the continued operations of the whole   configuration.  C    I'd be looking at the communications, connectivity, and at such  F considerations as the allocation classes, and at mis-matched SCS node  identification settings.   ------------------------------  % Date: Mon, 21 Aug 2006 16:40:51 +0100 * From: "Richard Brodie" <R.Brodie@rl.ac.uk>; Subject: Re: SEPPUCLU bugcheck introducing new cluster node , Message-ID: <ecck63$5kj$1@south.jnrs.ja.net>  ; "William Webb" <william.w.webb@gmail.com> wrote in message  C news:8660a3a10608210834u192d2983y2e9cd55ca8aa7ab7@mail.gmail.com...   B > Am I the only one who notices the resemblance of SEPPUCLU to the > Japanese word "seppuku"?  . I doubt it. Google spots the resemblance too.    ------------------------------  % Date: Mon, 21 Aug 2006 18:35:27 +0100 ) From: Tom Wade <nospam@picard.eurokom.ie> ; Subject: Re: SEPPUCLU bugcheck introducing new cluster node 0 Message-ID: <44E9EEDF.6060606@picard.eurokom.ie>  I >   What the bugcheck refers to isn't exactly "fun", and there are words  I > around that slide that aren't included in the text of the presentation   > you've found.   G Sorry, I didn't mean to suggest that VMS engineering introduced a booby ' trap :-)  I understand the name chosen.   D >   I'd be looking at the communications, connectivity, and at such H > considerations as the allocation classes, and at mis-matched SCS node  > identification settings.  ? The SCSNODE and SCSSYSTEMID parameters are unique to each node.   G The machines in the cluster use different alloclasses (this was because H the DEVICE_NAMING took care of shared SCSI buses, and the different nodeE alloclasses prevented multiple IDE DQA0 devices being confused).  The A only shared bus now is the fiber array, which is always $1$DGAxxx   G An oddity is the output of the >>> SHOW DEVICE command.  Apart from the E DGA101, the other DGAs don't exist (they also have $0$DGA which looks E wrong).  Would these be causing confusion, or is this a red herring ?      P00>>>show device D dga101.1001.0.3.1          $1$DGA101                     HSG80  V87FD dga101.1002.0.3.1          $1$DGA101                     HSG80  V87FD dga12409.1.0.3.1           $0$DGA12409                   HSG80  V87FD dga12409.2.0.3.1           $0$DGA12409                   HSG80  V87FD dga12601.1.0.3.1           $0$DGA12601                   HSG80  V87FD dga12601.2.0.3.1           $0$DGA12601                   HSG80  V87FD dga14585.1.0.3.1           $0$DGA14585                   HSG80  V87FD dga14585.2.0.3.1           $0$DGA14585                   HSG80  V87FD dga14777.1.0.3.1           $0$DGA14777                   HSG80  V87FD dga14777.2.0.3.1           $0$DGA14777                   HSG80  V87FD dga15963.1.0.3.1           $0$DGA15963                   HSG80  V87FD dga15963.2.0.3.1           $0$DGA15963                   HSG80  V87FD dga25784.1.0.3.1           $0$DGA25784                   HSG80  V87FD dga25784.2.0.3.1           $0$DGA25784                   HSG80  V87FD dga26104.1.0.3.1           $0$DGA26104                   HSG80  V87FD dga26104.2.0.3.1           $0$DGA26104                   HSG80  V87FD dga26168.1.0.3.1           $0$DGA26168                   HSG80  V87FD dga26168.2.0.3.1           $0$DGA26168                   HSG80  V87FD dga28856.1.0.3.1           $0$DGA28856                   HSG80  V87FD dga28856.2.0.3.1           $0$DGA28856                   HSG80  V87FD dga29176.1.0.3.1           $0$DGA29176                   HSG80  V87FD dga29176.2.0.3.1           $0$DGA29176                   HSG80  V87FD dga29240.1.0.3.1           $0$DGA29240                   HSG80  V87FD dga29240.2.0.3.1           $0$DGA29240                   HSG80  V87FD dga31096.1.0.3.1           $0$DGA31096                   HSG80  V87FD dga31096.2.0.3.1           $0$DGA31096                   HSG80  V87FD dga9337.1.0.3.1            $0$DGA9337                    HSG80  V87FD dga9337.2.0.3.1            $0$DGA9337                    HSG80  V87FD dqa0.0.0.15.0              DQA0             Compaq   CRD-8402B  1.03 dva0.0.0.1000.0            DVA0 > eia0.0.0.6.1               EIA0              00-50-8B-69-DD-3D> pga0.0.0.3.1               PGA0        WWN 1000-0000-c930-d745 P00>>> --  9 --------------------------------------------------------- @ Tom Wade                 | EMail: tee dot wade at eurokom dot ie3 EuroKom                  | Tel:   +353 (1) 296-9696 3 A2, Nutgrove Office Park | Fax:   +353 (1) 296-9697 L Rathfarnham              | Disclaimer:  This is not a disclaimer            G Dublin 14                | Tip:   "Friends don't let friends do Unix !"  Ireland    ------------------------------    Date: 21 Aug 2006 10:41:36 -0700/ From: "Volker Halle" <volker_halle@hotmail.com> ; Subject: Re: SEPPUCLU bugcheck introducing new cluster node C Message-ID: <1156182096.269574.211400@i42g2000cwa.googlegroups.com>    Tom,  ; the SEPPUCLU crash is clearly a lock-manager related crash.   F After receiving a fatal lock message, the local node takes this crash.( R12 points to the lock message received:   SDA> FORMAT @R12/TYPE=LKMSG    shows the received message.    SDA> CLUE REGISTER  A will show the sender node (the one that crashed with LOCKMGRERR).   A If you provide the SDA> CLUE REGISTER output from the other node, $ additional analysis may be possible.   Volker.    ------------------------------    Date: 21 Aug 2006 09:08:53 -0700 From: intensifi@earthlink.net 7 Subject: VGA video adapter for Vaxstation 4000 model 60 B Message-ID: <1156176533.145459.190780@i3g2000cwc.googlegroups.com>   Hello,  G I heard such an adapter existed.  Does anyone know where I can get one?   D 29-32549-01 is a part # I found while searching, but no luck finding one to buy.    Thanks in advance!   ------------------------------    Date: 21 Aug 2006 10:23:06 -0700 From: etmsreec@yahoo.co.uk; Subject: Re: VGA video adapter for Vaxstation 4000 model 60 B Message-ID: <1156180986.397791.296080@75g2000cwc.googlegroups.com>  C The FAQ suggests that this is a BNC to SVGA adapter so requires the ) VS<->BNC cable to be daisy chained to it:   G "The DIGITAL (classic 2-5-2-style) part number 29-32549-01 converts the E output from the RGB cable (3 BNC, synch-on-green) that comes with the = VAXstation 3100 and VAXstation 4000 series to a female SVGA D E connector. You may be able to find third-party converters or adapters D (3 BNCs with synch-on-green signaling to 5 BNCs with VGA/SVGA, or to 15-pin VGA/SVGA. "   Steve    intensifi@earthlink.net wrote: > Hello, > I > I heard such an adapter existed.  Does anyone know where I can get one?  > F > 29-32549-01 is a part # I found while searching, but no luck finding
 > one to buy.  >  > Thanks in advance!   ------------------------------    Date: 21 Aug 2006 08:24:59 -0700- From: "Doug Phillips" <dphill46@netscape.net>  Subject: Re: Wireless handhelds B Message-ID: <1156173899.565876.241480@i3g2000cwc.googlegroups.com>   Bill Gunshannon wrote:D > In article <1155924518.357237.320180@75g2000cwc.googlegroups.com>,2 > 	"Doug Phillips" <dphill46@netscape.net> writes: > > H > > All this really isn't as hard as you think, David. You might as wellK > > ask: "can an application running on OpenVMS communicate via TELNET with + > > a VT terminal that has a small screen?"  > 3 > Actually, it is a bit more complicated than that.    Only if you make it so.    >  You also need to knowH > if the telnet session will survive when the hand-held moves from AP to% > AP as you move about the warehouse.   > Transparent. Just buy the right equipment for the application.  & >  Most connectionless functions (likeF > using a web browser) will do this, but connection oriented protocolsJ > may not survive the transition.  Especially if you are looking at things& > like WPA without the pre-shared key. >   D We're talking about an industrial application. I have a few of theseC running now. They aren't that hard to set up unless you try to save F money and buy equipment that is *not* made to perform in an industrial environment.   ------------------------------  % Date: Mon, 21 Aug 2006 11:47:30 -0400  From: norm.raphael@metso.com Subject: Re: Wireless handhelds Q Message-ID: <OFBE99A982.092CD8B1-ON852571D1.005680EB-852571D1.0056BF4A@metso.com>   I We are using WindowsCE on the handhelds and talking through AttachmateWRQ C Verastream Middleware to our OpenVMS system.  This allows us to use J existing screens and not write separate handheld interfaces to the OpenVMS< application.  It is neither simple nor inexpensive, however.   ------------------------------    Date: 21 Aug 2006 09:03:54 -0700- From: "Andrew" <andrew_harrison@symantec.com>  Subject: Re: Wireless handhelds @ Message-ID: <1156176234.441098.8230@74g2000cwt.googlegroups.com>   bob@instantwhip.com wrote:6 > you can save money by buying ipaqs and buying an app@ > to run on it, then just ftp the flat files to and from vms ...  C It rather depends on what the environment is. Warehouses tend to be E rather hostile and in addition you need a handhold that has a minimum  of a bar code reader.   C Symbol do Palm, Linux and Windows based devices. They are generally C very rugged and things like the bar code reader are built in rather = than being an external device that will just get trashed in a 
 warehouse.  A FTP would not be a good choice. The device users are not remotely E computer literate they need a system generated picking list, they may E need to interact with the server while they are picking and the whole  mechanism needs to be quick.   regards  Andrew Harrison    ------------------------------    Date: 21 Aug 2006 10:27:00 -0700- From: "Doug Phillips" <dphill46@netscape.net>  Subject: Re: Wireless handhelds A Message-ID: <1156181220.388596.18540@i3g2000cwc.googlegroups.com>    norm.raphael@metso.com wrote: K > We are using WindowsCE on the handhelds and talking through AttachmateWRQ E > Verastream Middleware to our OpenVMS system.  This allows us to use L > existing screens and not write separate handheld interfaces to the OpenVMS> > application.  It is neither simple nor inexpensive, however.  = I'd like to hear more about what makes it "neither simple nor D inexpensive". My experience is that the job is easier to do with theF right tools, and buying & building the right tools might cost a little3 more up front but overall will save time and money.   ; Maybe the OP David Gray will come back with his experience.    ------------------------------   End of INFO-VAX 2006.465 ************************