1 INFO-VAX	Sat, 22 Apr 2006	Volume 2006 : Issue 222       Contents: Boot Camp Update April 21  Re: Even lower DS10 pricing * Re: HP Storageworks Arrays are Bulletproof* Re: HP Storageworks Arrays are Bulletproof* Re: HP Storageworks Arrays are Bulletproof* Re: HP Storageworks Arrays are Bulletproof* Re: HP Storageworks Arrays are Bulletproof* Re: HP Storageworks Arrays are Bulletproof* Re: HP Storageworks Arrays are Bulletproof' Re: OpenVMS is the worlds best desktop! . Re: Opinion: I was just trying to sell OpenVMS Re: OT: Sparc not dead yet Re: OT: Sparc not dead yet Re: OT: Sparc not dead yet: Re: Overland Data neo 2000/MSL series drive + OpenVMS 8.2>: Re: Overland Data neo 2000/MSL series drive + OpenVMS 8.2>: Re: Overland Data neo 2000/MSL series drive + OpenVMS 8.2>P Point Secure Press Release - announcing OpenVMS System Detective, has now been p* Re: Quorum, locks and application question Re: Replacing drives in bricks Re: Replacing drives in bricks Re: Replacing drives in bricks Re: Replacing drives in bricks Re: Replacing drives in bricks Re: Replacing drives in bricks Re: Replacing drives in bricks Re: Replacing drives in bricks Re: Replacing drives in bricks Re: Replacing drives in bricks Re: Replacing drives in bricks Re: Replacing drives in bricks Re: Replacing drives in bricks Re: Strange disk device state  Re: Strange disk device state  Re: Strange disk device state  Re: Strange disk device state  Re: Strange disk device state  Re: The Undocumented OpenVMS Re: The Undocumented OpenVMS Re: The Undocumented OpenVMS" Updated VMS information - April 21 Re: VAX Q-bus and SCSI Disks?  Re: VAX Q-bus and SCSI Disks?  Re: VAX Q-bus and SCSI Disks?  Re: VAX Q-bus and SCSI Disks?  VMS news from France  F ----------------------------------------------------------------------    Date: 21 Apr 2006 15:14:57 -0700) From: "Sue" <susan_skonetski@hotmail.com> " Subject: Boot Camp Update April 21B Message-ID: <1145657697.691145.64410@z34g2000cwc.googlegroups.com>   Dear Newsgroup  C Here is this weeks OpenVMS Advanced technical Boot Camp Update. You A will notice some changes in this weeks update.  First we have had C several cancellations and second there are on three seats committed ? instead of ten.  I have returned or used all the other seats as 
 scholarships.   G Please note: If you are planning on registering for this event you need A to do so quickly mainly because the hotel is running out of hotel  rooms.     Registration Goal 200  Seats Committed =  163
 % full =  82%  Seats available =  37  Registered = 160! % of new attendees =  37% (aprox) # % of repeat attendees = 63% (aprox)  Weeks until Boot Camp 4 % Folks from out side the US = 67 (45%)  Countries represented = 19 Germany  England  Netherlands  Switzerland  Sweden Belgium  Canada Ireland  Austria  France	 Australia  Belgium  India  New Zealand  Spain  US China  Japan  Scotland    . http://h71000.www7.hp.com/symposium/index.html    @ Warm Regards as always and thank you for your continued support.   Sue    ------------------------------  % Date: Fri, 21 Apr 2006 21:30:29 -0500 @ From: "David J. Dachtera" <djesys.nospam@NeOaSrPtAhMlNiOnWk.net>$ Subject: Re: Even lower DS10 pricing6 Message-ID: <44499545.BC57F47E@NeOaSrPtAhMlNiOnWk.net>  / "David Turner, Island Computers US Corp" wrote:  > " > Go to www.islandco.com/ds10.html >  > We have a large qty  > B > DS10 466 with 512MB memory and 30GB IDE disk for only $1895 !!!!  > The ffort is appreciated, Dave. However, that's still circa. aF half-months take-home pay for some folks (hobbyists), and rather a bit  to speculate for an ISV/OEM/VAR.   --   David J Dachtera dba DJE Systems  http://www.djesys.com/  & Unofficial OpenVMS Marketing Home Page! http://www.djesys.com/vms/market/   ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/   ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/   ------------------------------  % Date: Fri, 21 Apr 2006 14:10:46 -0400 C From: "David Turner, Island Computers US Corp" <dbturner@icusc.com> 3 Subject: Re: HP Storageworks Arrays are Bulletproof : Message-ID: <Bd92g.25891$Kh5.18401@bignews8.bellsouth.net>  I I wonder if I used a Glock 10mm with hollowtips would the EVA do so well?    :0)    --     David B Turner Island Computers US Corp 2700 Gregory St, Suite 180 Savannah GA 31404  Tel: 912 447 6622 X201 Cell: 912 447 6622 X251  Fax: 912 201 0402  Email: dbturner@icusc.com  Web: http://www.islandco.com% ===================================== < All orders are subject to the following terms and conditions. of sale. These should be read before ordering.% http://www.islandco.com/warranty.html   " <sean@obanion.us> wrote in message= news:1145639645.322076.237470@u72g2000cwu.googlegroups.com... , > Just don't let them do a firmware upgrade. > G > The first one they did, and assured us we could leave all of our HPUX I > systems running, had a bug that disabled all the FC ports on the array. - >  Not surprisingly, all the systems crashed.  >  >  > Sean >  > Alan Greig wrote: - > > http://www.theinquirer.net/?article=31165  > > Which begins:  > > K > > HP HAS A TENDENCY to use gun metaphors when talking about their storage 3 > > solutions, and the newest one is 'bulletproof'.  > > H > > Instead of the wussy technical term for it, they went out and shot aH > > hole clean through a half-million dollar Storageworks XP12000 server > > while it was running.  > > L > > The bullet went right through it, but only half way through the fishtankH > > on the other side. That is what you get with .308 rounds, not enough: > > stopping power vs high-end arrays backed by fishtanks. > > H > > In either case, they literally proved that their Storageworks arraysD > > will take a bullet while streaming video, never missing a frame.	 > > .....  > >  > >  > > --   > > Alan Greig >    ------------------------------  % Date: Fri, 21 Apr 2006 14:23:18 -0400 + From: Chuck Aaron <caaron@ceris.purdue.edu> 3 Subject: Re: HP Storageworks Arrays are Bulletproof 5 Message-ID: <e2b7um$1bs$1@mailhub227.itcs.purdue.edu>   , This is a multi-part message in MIME format.& --------------0906020002060400030607089 Content-Type: text/plain; charset=us-ascii; format=flowed  Content-Transfer-Encoding: 7bit   & Perhaps the Glock .40 will do the job.   Chuck   - David Turner, Island Computers US Corp wrote:   J >I wonder if I used a Glock 10mm with hollowtips would the EVA do so well? >  >:0) >  >    >   & --------------090602000206040003060708) Content-Type: text/html; charset=us-ascii  Content-Transfer-Encoding: 7bit   ? <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">  <html> <head>I   <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">    <title></title>  </head> ' <body bgcolor="#339999" text="#ffffff"> * Perhaps the Glock .40 will do the job.<br> <br>	 Chuck<br>  <br>- David Turner, Island Computers US Corp wrote: B <blockquote cite="midBd92g.25891$Kh5.18401@bignews8.bellsouth.net"
  type="cite"> X   <pre wrap="">I wonder if I used a Glock 10mm with hollowtips would the EVA do so well?   :0)      </pre>
 </blockquote>  </body>  </html>   ( --------------090602000206040003060708--   ------------------------------  % Date: Fri, 21 Apr 2006 15:57:35 -0400 ' From: Dave Froble <davef@tsoft-inc.com> 3 Subject: Re: HP Storageworks Arrays are Bulletproof / Message-ID: <ZpednVcydp00pdTZRVn-hg@libcom.com>    Chuck Aaron wrote:* >   Perhaps the Glock .40 will do the job. >  > Chuck  > / > David Turner, Island Computers US Corp wrote:  > K >>I wonder if I used a Glock 10mm with hollowtips would the EVA do so well?  >> >>:0)  >> >>   >>  K I'm sure the aiming was appropriate so that a really vital part was missed.   C Now if they want a real challenge, find out if any of the old WWII  H battleships are still intact, and try one of their 16 inch guns.  If it & survuves that, then I'll be impressed.   --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com 170 Grimplin Road  Vanderbilt, PA  15486    ------------------------------  % Date: Fri, 21 Apr 2006 12:37:54 -0700  From: Z <Z@ids.net> 3 Subject: Re: HP Storageworks Arrays are Bulletproof ' Message-ID: <hwa2g.174$oo1.41@fe04.lga>    Alan Greig wrote: + > http://www.theinquirer.net/?article=31165  > Which begins:  > J > HP HAS A TENDENCY to use gun metaphors when talking about their storage 1 > solutions, and the newest one is 'bulletproof'.  > G > Instead of the wussy technical term for it, they went out and shot a  G > hole clean through a half-million dollar Storageworks XP12000 server   > while it was running.  > K > The bullet went right through it, but only half way through the fishtank  G > on the other side. That is what you get with .308 rounds, not enough  8 > stopping power vs high-end arrays backed by fishtanks. > G > In either case, they literally proved that their Storageworks arrays  B > will take a bullet while streaming video, never missing a frame. > .....   H Interesting but the placement of the bullet was deliberate and while it F penetrated a circuit board, it's clear that this wasn't really a good E test. Heck, I could shoot a bullet through my Windows desktop PC (no  H RAID) and one of its circuit boards (and even the secondary or external F disk) and it would still run just fine streaming video. It's not even 2 clear that any disks were penetrated by the round.   ------------------------------  % Date: Fri, 21 Apr 2006 16:54:27 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> 3 Subject: Re: HP Storageworks Arrays are Bulletproof , Message-ID: <4449467C.E3E7DBCA@teksavvy.com>  G If the bullet goes through the storage array with enough energy left to C still penetrate another object, can it really be considered "bullet  proof" ?  H If a bullet goes through your torso without injuring critical organs and, you survive, does it make you bullet proof ?   ------------------------------   Date: 22 Apr 2006 00:38:17 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)3 Subject: Re: HP Storageworks Arrays are Bulletproof + Message-ID: <4atc7pFu045hU2@individual.net>   / In article <ZpednVcydp00pdTZRVn-hg@libcom.com>, * 	Dave Froble <davef@tsoft-inc.com> writes: > Chuck Aaron wrote:+ >>   Perhaps the Glock .40 will do the job.  >>   >> Chuck >>  0 >> David Turner, Island Computers US Corp wrote: >>  L >>>I wonder if I used a Glock 10mm with hollowtips would the EVA do so well? >>>  >>>:0) >>>  >>>    >>>  > M > I'm sure the aiming was appropriate so that a really vital part was missed.  >   D You mean like the Masterlock commercial where a lock I can dismantleC with a fingernail file survives being shot by a high-powered rifle?    bill   --  J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>       ------------------------------  % Date: Fri, 21 Apr 2006 21:08:18 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> 3 Subject: Re: HP Storageworks Arrays are Bulletproof , Message-ID: <444981FD.90FB8CF8@teksavvy.com>  K For real bulletproofness, nothing beats the RA82 drives in the Q5 cabinets.   D At least 3 layers of thick steel before you get to the HDA which was3 thick cast iron. The motor itself was a 1/3hpmotor.   J Maybe the belt between the motor and the HDA might have been destructible.  B The power supply was itself encased in yet another layer of steel.    G (in fairness though the front panels didn't afford as much protection.)    ------------------------------   Date: 22 Apr 2006 00:26:30 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)0 Subject: Re: OpenVMS is the worlds best desktop!+ Message-ID: <4atbhmFu045hU1@individual.net>   2 In article <V%72g.6661$v74.2498@news.cpqcorp.net>,4 	Keith Parris <keithparris_NOSPAM@yahoo.com> writes: > Bill Gunshannon wrote:D >> How does that apply tp HP?  They killed Alpha.  They no longer doH >> hardware.  They sell other people's hardware.  At razor thin margins. > F > HP has chosen to move to using microprocessors from the leading two K > companies in the industry (Intel and AMD) rather than continuing to make  ) > its own, incompatible processor chips.      E OK, just what was it that Alpha was incompatible with that Itanium is  now compatable with?   bill   --  J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>       ------------------------------  % Date: Fri, 21 Apr 2006 18:09:25 -0400 % From: BRAD <bradhamilton@comcast.net> 7 Subject: Re: Opinion: I was just trying to sell OpenVMS * Message-ID: <44495815.3080702@comcast.net>   Keith Parris wrote:  > Bill Gunshannon wrote: >  >> It's not like forF >> every hospital that migrates away another one migrates towards VMS. >  > K > Not true. There is still a steady stream of hospitals installing VMS for  D > the first time, driven by applications. If they choose a software K > package from Cerner, IDX, or SMS, it's very likely they'll be running it  D > on VMS, even if that means setting up a brand-new VMS environment.  < At the physician's practice where I currently work, the IDX G character-cell interface application (running on AIX) will be upgraded  A to a newer IDX with a GUI front-end, running on...AIX!.  The two  I hospitals that we are closely affiliated run IDX and Meditech on...well,  
 *not* VMS!  G There are IDX Rad and IDX Scheduling products at one of the affiliated  E hospitals which are VMS-based, but as far as anyone can tell me, the  G apps are no longer in use (indeed, I get the VMS banner when TELNETing  I to each machine, rather than an IDX application).  Sorry, but I'm seeing  H this over and over again in the healthcare shops in my area.  I know of G only two major "shops" in my area (Eastern/Central Massachusetts) that  = use VMS, and VMS is only one (small?) part of the overall IT  H infrastructure.  Sad, especially since we are talking about "DEC"'s own  "backyard"!   C > Same is true for stock (and other) exchanges. If they choose OMX  : > software, it's almost certain they'll be running on VMS. >   E Can't speak for stack exchanges, but at a mutual-fund company (think  @ "900-lb. gorilla") VMS was but a small corner of the overall IT E infrastructure, and the internal IT organization was doing its level  I best to rid itself of such "legacy" equipment (as of 2001).  I can't say  I if that is still the case (perhaps someone else can comment anonymously).    ------------------------------  % Date: Fri, 21 Apr 2006 15:44:01 -0400 ' From: Dave Froble <davef@tsoft-inc.com> # Subject: Re: OT: Sparc not dead yet / Message-ID: <ZpednVQydp3iqNTZRVn-hg@libcom.com>    Doug Phillips wrote: > Dave Froble wrote: >  >>JF Mezei wrote:  >  > <...>  > I >>>Neother do I.  But if the market and the 8086 develops to a point that I >>>the 8086 can take on the vast majority of configurations now done only I >>>in Sparc, and the 8086 is cheaper, then Sun will also be responsive to - >>>cutsomer demands for lower priced systems.  >>> B >>>Sparc competes against power and 8086. Both Sparc and Power are? >>>essentially proprietary chips without competition within the F >>>architectures. (yes, I know sparc has multiple sources, but do they >>>really *compete* ? )  >>J >>What you're ignoring is that AMD at least doesn't give a rat's ass aboutJ >>the top end.  The desktop (say volumn) is just getting to dual core, andD >>the majority of servers is in the 4-8 core size.  That's where the. >>volume is.  Volume is where the money is at. >> >  > D > Are you kidding? AMD and Intel *covet* the top end. AMD is pushing. > Intel & x86 upward like noone else ever has.  H No, I'm not kidding.  What some may 'covet', isn't what brought them to  where they are now.   F Are AMD and Intel pushing for more capabilities?  Sure they are.  But I the main reason is to try to out-do each other, not to replace Sparc and   Power.  D Answer me this, when did Intel decide to again push ahead with x86? G When Sparc and Power out-did them?  Or perhaps when AMD started eating    their bread and butter business?  F Now, Intel does (or did) covet the top end.  That was the itanic.  We F see just how much coveting occured when AMD ate into the x86 business.  G > To anyone paying attention it's obvious that x86 (AMD64 / EM64T) will F > keep advancing upward. Anyone willing to "do the math" will see thatG > the R&D $ pushing the x86 advancement is greater than other competing I > chips. Okay, forget the money. Consider inertia. There is more software H > running on x86 than any other instruction set. There are tools alreadyE > developed for x86 that must be ported or re-written for development E > under another set. Plus, the Alpha folks are working in both camps. + > Some competitive feelings there, perhaps?   I All true.  But the motive is to beat each other in the x86 world, not to  I replace Sparc and Power.  They may indeed do so in time, but not because   that was their primary thrust.  E > Plot it out. SUN will reach a point where they can't afford to keep G > dumping money into SPARC when x86 does the job faster and cheaper and H > doesn't put such a strain on their budget. Intel will reach that pointI > with Itanium because the x86 is one business Intel doesn't want to lose I > and AMD will keep on eating into market share if Intel doesn't keep up. G > And IBM? Well, I don't see them pouring tons of money into Power just B > for pride. At some point it's wiser to stop swimming against the$ > current and climb aboard the raft.  A Well, there are those who thought that time had already arrived.  E Surprise, Sun has just come out with a product that very nicely fits  F what their customers are doing.  Not a general purpose product, but a H targetted product.  I don't think Power is aimed at the desktop and x86  market either.  E So you seem to adher to JF's 'inevitable' theory also?  Doesn't make   either of you right.   --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com 170 Grimplin Road  Vanderbilt, PA  15486    ------------------------------  % Date: Fri, 21 Apr 2006 16:24:57 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> # Subject: Re: OT: Sparc not dead yet , Message-ID: <44493F94.8191E19B@teksavvy.com>   etmsreec@yahoo.co.uk wrote: C > interested in selling x86 systems and their customer base who are H > probably as loyal as VMS people would buy them.  Why would Sun want to" > compete in BillyBox land though?  D There are quite a few examples (apple being the latest) of companiesC building fairly serous systems not designed to run windows and with P serious features in the systems, despite running the 8086 64 bit toy controller.  E What makes a "Superdome" isn't that IA64 thing, it is all the support ? chips, interconnects, power supplies, IO busses etc around it.    G If HP wanted, they could probably build an 8086 based superdome  with 8 C core modules (4 cpus) and some interconnect that worked. In fact, I L wouldn't be surprised if it had already been done in some lab in Kalifornia.  D > margin in high end reliable systems.  There's bugger all margin inC > low-end x86 servers since HP and Dell have them sliced and diced.     , Not all 8086s need to be low end low margin.   ------------------------------    Date: 21 Apr 2006 14:02:38 -0700- From: "Doug Phillips" <dphill46@netscape.net> # Subject: Re: OT: Sparc not dead yet C Message-ID: <1145653358.282526.136900@v46g2000cwv.googlegroups.com>    Dave Froble wrote: > Doug Phillips wrote: > > Dave Froble wrote: > >  > >>JF Mezei wrote:  > > 	 > > <...>  > > K > >>>Neother do I.  But if the market and the 8086 develops to a point that K > >>>the 8086 can take on the vast majority of configurations now done only K > >>>in Sparc, and the 8086 is cheaper, then Sun will also be responsive to / > >>>cutsomer demands for lower priced systems.  > >>> D > >>>Sparc competes against power and 8086. Both Sparc and Power areA > >>>essentially proprietary chips without competition within the H > >>>architectures. (yes, I know sparc has multiple sources, but do they > >>>really *compete* ? )  > >>L > >>What you're ignoring is that AMD at least doesn't give a rat's ass aboutL > >>the top end.  The desktop (say volumn) is just getting to dual core, andF > >>the majority of servers is in the 4-8 core size.  That's where the0 > >>volume is.  Volume is where the money is at. > >> > >  > > F > > Are you kidding? AMD and Intel *covet* the top end. AMD is pushing0 > > Intel & x86 upward like noone else ever has. > I > No, I'm not kidding.  What some may 'covet', isn't what brought them to  > where they are now.  >   G No, Microsoft brought them to where they are. You don't think Microsoft B wants to take over the top-end? Forget where they started, look atD where they are and the direction they're heading. Is each release ofC Windows server better than the last? Absolutely. Is each release of D AMD64/EM64T better than the last? Absolutely. Where is the big money$ being spent, and who is spending it?  G > Are AMD and Intel pushing for more capabilities?  Sure they are.  But J > the main reason is to try to out-do each other, not to replace Sparc and > Power. > E > Answer me this, when did Intel decide to again push ahead with x86? H > When Sparc and Power out-did them?  Or perhaps when AMD started eating" > their bread and butter business? >   A What got Intel's attention was when AMD started eating into their A higher-end business. As long as AMD were playing in the commodity D desk-top market they really weren't hurting Intel, and in fact, they2 were helping keep Intel out of anti-trust trouble.  G > Now, Intel does (or did) covet the top end.  That was the itanic.  We H > see just how much coveting occured when AMD ate into the x86 business. >   E AMD set a direction that Intel recognized as a threat to not only x86 & but IA64. It's a simple chart to draw.  I > > To anyone paying attention it's obvious that x86 (AMD64 / EM64T) will H > > keep advancing upward. Anyone willing to "do the math" will see thatI > > the R&D $ pushing the x86 advancement is greater than other competing K > > chips. Okay, forget the money. Consider inertia. There is more software J > > running on x86 than any other instruction set. There are tools alreadyG > > developed for x86 that must be ported or re-written for development G > > under another set. Plus, the Alpha folks are working in both camps. - > > Some competitive feelings there, perhaps?  > J > All true.  But the motive is to beat each other in the x86 world, not toJ > replace Sparc and Power.  They may indeed do so in time, but not because  > that was their primary thrust. >   > Well, I think their primary thrust is to dominate the world ofA computing, and that means "from the desk-top to the data-center". D (Sorry to bring that up again). x86 is the vehicle they've chosen toC drive. Take another look at the numbers, draw a trend and see where 
 it's heading.   G Like the old saying; You can't change how you got here. What matters is  where you're going.     G > > Plot it out. SUN will reach a point where they can't afford to keep I > > dumping money into SPARC when x86 does the job faster and cheaper and J > > doesn't put such a strain on their budget. Intel will reach that pointK > > with Itanium because the x86 is one business Intel doesn't want to lose K > > and AMD will keep on eating into market share if Intel doesn't keep up. I > > And IBM? Well, I don't see them pouring tons of money into Power just D > > for pride. At some point it's wiser to stop swimming against the& > > current and climb aboard the raft. > B > Well, there are those who thought that time had already arrived.F > Surprise, Sun has just come out with a product that very nicely fitsG > what their customers are doing.  Not a general purpose product, but a I > targetted product.  I don't think Power is aimed at the desktop and x86  > market either. > F > So you seem to adher to JF's 'inevitable' theory also?  Doesn't make > either of you right. >   D I don't know about JF's theory, but Stephen King said: "Everything's% Eventual". That sounds about right;-)   C As the chip guys around here point out, it takes a long time to get D from design to production. One would expect to see new SPARC & PowerE releases for awhile. Whatever is going on in the design labs, though,  I'm afraid we can only guess.   D IBM is the only company I see with enough capital resource to battleA x86 and it looks to me like they're not that interested. In fact, G they're moving more into x86. SUN doesn't look strong enough to keep up B the pace. Maybe some of the non-U.S. companies will jump in to theF fight; but I see them jumping on the x86 bandwagon. Maybe someone willG actually buy SUN and pump them up. Anything could happen, but given the E state of finance and technology today and the small glimpse we get of " tomorrow, x86 looks like a winner.   ------------------------------  % Date: Fri, 21 Apr 2006 16:27:29 -0400 ' From: Dave Froble <davef@tsoft-inc.com> C Subject: Re: Overland Data neo 2000/MSL series drive + OpenVMS 8.2> / Message-ID: <TaidnVz-KI0xotTZRVn-tA@libcom.com>   - David Turner, Island Computers US Corp wrote: M > We have a customer to whom we shipped an Overland Data Neo 2000 series tape 0 > library (same as MSL from HP) with two DLT8000> > DLT Tape drives installed. Cabling and termination included. > L > before shipping we tested it on an Alphaserver DS10 617Mhz running OpenVMS > 7.3-2 M > We backed up to each drive of the library and then did a backup back to the % > hard drive to ensure data integrity  >  >  > Everything worked beautifully  > @ > Now it is at a customer site and they cannot even get past the > $mount/foreign commandM > It hangs their system (which is an Itanium II RX2620 with U3 SCSI interface  > runninng 8.2+ patches  >  > Anyone got any ideas?  > K > One HP tech said that support in VMS for "older" tape drives is no longer 0 > there and customer should have something newer >  > David  >   I Nothing useful to add, but I will comment that that "HP tech" is full of  E shit.  This is probably not a VMS support issue.  It may be an issue  F with the itanic version.  Drivers not moved to the itanic version and > such, but they did indicate there would be a common code base.  H With the exception of very old hardware, MVI and such, VMS doesn't take H out support for devices.  Even the older stuff will work, it's just not 
 supported.   --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com 170 Grimplin Road  Vanderbilt, PA  15486    ------------------------------  % Date: Fri, 21 Apr 2006 15:25:22 -0700 # From: "Tom Linden" <tom@kednos.com> C Subject: Re: Overland Data neo 2000/MSL series drive + OpenVMS 8.2> ) Message-ID: <op.s8dpwkjezgicya@hyrrokkin>   L On Fri, 21 Apr 2006 10:07:07 -0700, David Turner, Island Computers US Corp   <dbturner@icusc.com> wrote:   J > We have a customer to whom we shipped an Overland Data Neo 2000 series   > tape0 > library (same as MSL from HP) with two DLT8000> > DLT Tape drives installed. Cabling and termination included. > F > before shipping we tested it on an Alphaserver DS10 617Mhz running  	 > OpenVMS  > 7.3-2 K > We backed up to each drive of the library and then did a backup back to    > the % > hard drive to ensure data integrity  >  >  > Everything worked beautifully  > @ > Now it is at a customer site and they cannot even get past the > $mount/foreign commandE > It hangs their system (which is an Itanium II RX2620 with U3 SCSI    > interface  > runninng 8.2+ patches  >  > Anyone got any ideas?  > K > One HP tech said that support in VMS for "older" tape drives is no longer 0 > there and customer should have something newer >  > David  >   6 Was the device recognized at the console?  did you try SYSMAN> IO AUTO/LOG   9 If that doesn't work, maybe you can sell them an Alpha:-)    ------------------------------  # Date: Fri, 21 Apr 2006 22:56:39 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com>C Subject: Re: Overland Data neo 2000/MSL series drive + OpenVMS 8.2> 2 Message-ID: <Hqd2g.6699$ig4.2771@news.cpqcorp.net>   Tom Linden wrote:   8 > Was the device recognized at the console?  did you try > SYSMAN> IO AUTO/LOG   E    There'd be nothing to mention to MOUNT, if a device driver hadn't  2 been connected to a device that had been detected.  L    Now as to whether or not it was correctly detected, that's another issue.  I    And whether or not the SCSI bus is appropriately configured or if the  G tape driver recognizes this tape device within this context, those too   are discussions.  F    I'd expect that HP could offer integration services, if that is of  interest here.   ------------------------------    Date: 21 Apr 2006 15:18:59 -0700) From: "Sue" <susan_skonetski@hotmail.com> Y Subject: Point Secure Press Release - announcing OpenVMS System Detective, has now been p C Message-ID: <1145657939.700637.277480@i40g2000cwc.googlegroups.com>   F If you need a better copy (logo/.doc) please send email to my hp email which is my name @ hp.com.  ! Also available on www.openvms.org    For immediate release   ? PointSecure helps to secure corporate data and enforce security   policies on HP Integrity serversE System Detective version 8.2 provides host-based intrusion detection, G real-time security monitoring and access control for HP OpenVMS running  on HP Integrity servers   C HOUSTON, Texas, April 18, 2006 - PointSecure, a leading provider of E security and auditing solutions for  OpenVMS systems, today announced F the availability of System Detective version 8.2, providing host-basedE intrusion detection, real-time security monitoring and access control  for HP Integrity servers.   D PointSecure's System Detective helps to protect OpenVMS systems fromC internal and external threats by proactively enforcing and ensuring @ compliance with corporate security policies and/or industry best= practices. System Detective facilitates a more secure OpenVMS G environment by recording session activity, managing unattended inactive G terminal sessions, restricting access to sensitive files or images, and G interactively monitoring, assisting, or taking control of selected user 	 sessions.   F PointSecure has worked closely with HP to support the Integrity serverF platform, which is designed to meet the most demanding performance and scalability requirements.   E "Sprint/Nextel focuses on delivering innovative, reliable -- and most = importantly, secure -- wireless communications to millions of G customers," said Don Nutt, Manager of OpenVMS Systems at Sprint/Nextel. G "PointSecure's System Detective has become an indispensable part of our D corporate security plan, helping us control access to sensitive dataA and keep security policies enforced. We're moving to HP Integrity D servers now. We are really looking forward to PointSecure supporting* the platform and making the move with us."  > "OpenVMS is playing an ever-increasing role in IT environments: worldwide where performance, availability and security areE mission-critical," said Rick Pleczko, President & CEO of PointSecure. > "We're excited to support this new generation of HP OpenVMS onD Integrity servers, which enables us to continue to provide customersC with an indispensable solution for proactively protecting corporate  data."  B "We are delighted that PointSecure has decided to strengthen theirC commitment to HP OpenVMS." said Ann McQuaid, general manager of the B OpenVMS group, Business Critical Servers, HP.  "With PointSecure'sG support for OpenVMS on HP Integrity servers, our customers can continue > to take advantage of the high-availability of their HP OpenVMSC environments with solutions that streamline security management and  data protection."    AvailabilityD PointSecure System Detective version 8.2 is available now.  For more@ information, to upgrade, or to request a demonstration of System- Detective, please visit: www.pointsecure.com.    About PointSecure F PointSecure is the leading provider of security and auditing solutions@ for OpenVMS systems. Our solutions have been declared "virtuallyF unhackable" and were banned from Defcon. Our solutions protect OpenVMSG systems from both external and internal security threats while ensuring < compliance with corporate security policies and governmentalE regulations such as HIPAA, GLBA, and BS779. Headquartered in Houston, E TX, our intrusion detection, real-time monitoring, and access control = solutions protect and secure mission critical OpenVMS systems 
 worldwide.   ###   D PointSecure is a division of BBS Technologies, Inc. System Detective= and PointAudit are trademarks or registered trademarks of BBS E Technologies, Inc. or its subsidiaries in the United States and other E jurisdictions.  All other company and product names may be trademarks 7 or registered trademarks of their respective companies.    ------------------------------  # Date: Sat, 22 Apr 2006 00:04:47 GMT   From: John Santos <john@egh.com>3 Subject: Re: Quorum, locks and application question ( Message-ID: <zqe2g.438$bU6.109@trnddc06>   Dave Froble wrote: > Keith Parris wrote:  >  >> Richard Maher wrote:  >> >>> Consider this conundrum: - >>> K >>> Q. How does a Rdb Monitor process faithfully implement it's FREEZE lock A >>> mechanism so as to protect the ACID properties of a database   >>> transaction? >>> L >>> A. Stuffed if I know. (There was a discussion in ITRC about this a while	 >>> back)  >>> G >>> 1) Process A on Node X has entered a Cayman Island transaction for   >>> $1B and J >>> will have to rollback 'cos a commit-time constraint will stop it going >>> through.I >>> 2) Process B on Node Y has a lock pending on this Account record and  	 >>> wants / >>> to transfer the balance to the Isle of Man. G >>> 3) Node Z is thrashing away sending tree re-mastering requests all  
 >>> around, >>> the cluster and being a general nuisance >>> 4) Node X dies >>> : H >>> : From this point on I imagine the possibility of a race-condition.  >>> That is,F >>> what *right-now* is stopping Process B from seeing the dodgy data? >> >> >>I >> If I understand your question, the basic issue is that when a lock is  I >> being used to protect updates to some shared resource, you may really  J >> need to know if the reason you are now being granted your lock request  >> is because:J >> 1) the prior user is now done with it, having left the shared resource 4 >> (like a database block) in a consistent state, orJ >> 2) the prior user got interrupted in mid-update by a node failure, and E >> the resource has been left in an indeterminate state and probably   >> needs to be fixed up  >>H >> In the early '90s Rdb asked for and received new capabilities in VMS H >> to handle this possibility. The $SETCLUEVT system service allows one B >> to ask for notification of events like loss of a node from the F >> cluster, and VMS guarantees that the AST notifying you of the node E >> loss will always be delivered before any AST (or mainline process  I >> execution) notifying you that a has lock granted because the old lock  G >> on a failed node has been freed as a result of the state transition.  >  > G > So if a lock is granted because the node holding the lock exited the  C > cluster, the process acquiring the lock must be testing for this  H > condition by having such an AST queued every time a lock is requested?  E I think you can do this using lock value blocks.  Put a flag in there G that says "the transaction was successfully completed".  Clear the flag A on acquiring the lock.  Set the flag when you exit.  If, when you : acquire the lock, the flag is already clear, or if you getC SS$_VALNOTVALID, then you need to back out whatever transaction was  in progress first.  E But probably of more practical use, since the information to back out F a partial transaction has to be stored somewhere (e.g. RMS journaling,G a database, or roll-your-own), the "transaction in progress" flag could H be stored in the same place.  This may involve some disk I/O, but on theA plus side, it will also survive a complete cluster crash.  If you E acquire the lock cleanly, (valid lock value block that says there was H no transaction in progress) just do your thing.  If the lock value blockA is invalid, either it was held by a process on another node which @ crashed, or you are the first process up after a system boot or F application restart, so you need to check for in-progress transactionsD and back them out before continuing.  If there is a valid lock valueD block, but it indicates an in-progress transaction, then the processC which held the lock (but not the node it was running on), must have  crashed, so same thing.   C You may need to have two resources, one which is used for exclusive B access to the database (or whatever), and a 2nd one which can onlyG be held by the current holder of an exclusive lock on the 1st resource. B The 2nd lock records the current state of the transaction, and hasG its value set to "in progress" *after* a process acquires the 1st lock, E and then is set to "done" after finishing the transaction, but before B releasing the 1st lock.  Then use invalidity of the value block orB an "in progress" value (for the 2nd resource), to decide whether a? back-out is needed.  The reason for this, ISTR, is that you can C only modify the contents of a lock value block when you release the F lock, so you need a lock you can release without losing your exclusive? access to the database.  (For this to work well, all interested @ processes need to take out "null" locks on both the resources atA startup, and then use lock conversions on them, rather than using A $enq/$deq each time they need the lock.  Otherwise, when the last B holder does its $deq, the lock value block will evaporate, and theH app will do a lot of unnecessary checking for in-progress transactions.)     > K > Does RDB queue an AST and test for the condition.  (I'm guessing that it  I > does since your post is in reply to such an event.)  In the case where  I > the condition exists, what does RDB do?  It's like "hey buddy, you now  > > have the resource, but the last guy never finished with it".         --   John Santos  Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------    Date: 21 Apr 2006 12:19:37 -07001 From: nothome@spammers.are.scum (Malcolm Dunnett) ' Subject: Re: Replacing drives in bricks , Message-ID: <AdYHhVEnfe+9@malvm9.mala.bc.ca>  D In article <Pine.LNX.4.61.0604211057130.6747@localhost.localdomain>,+     Rob Brown <mylastname@gmcl.com> writes:   F > This sounds attractive.  Now here is a hypothetical.  I get a BA350 I > and some rz28s in storageworks bricks.  n years down the road an rz28s  F > dies.  What is the wisdom of opening up the bricks in replacing the ? > dead drive with a modern drive (with appropriate cabling and  H > terminators etc.) so that I can continue to use the slot in the BA350? > "    Isn't the BA350 a narrow shelf?  D    You may have trouble finding a "modern drive" that will work on aA narrow SCSI bus. I've seen some that do, some that only do with a ? special jumper setting and some that I could never get to work.   F    On the more general question of opening up the bricks and replacing@ drives - physically it's a piece of cake, just make sure you getB a compatible drive ( eg 68 pin vs 80 pin - DEC has used both kindsF over the years ). If you're more modern drive is faster ( eg 15K rpm )D you might have to watch out for heat dissipation issues. I generallyD wouldn't put anything faster than 7200RPM in one of the blue plastic bricks.   : > Would you do it as a hobbyist?  Would you do it at work? >   B   I have replaced drives in a Raid Array 8000 with generic SeagateB disks. There's no guarantees but I've had some in fairly heavy useD for years with no problems - so I would rate the risk as low. OTOH I@ have had some with weird firmware that didn't work properly in aG RA8000 - in that case the problem was pretty obvious, their performance D was really terrible. I guess the bottom line is yes, I'd do it - but8 I'd test it carefully before putting it into production.   ------------------------------  % Date: Fri, 21 Apr 2006 15:30:41 -0400 ' From: Dave Froble <davef@tsoft-inc.com> ' Subject: Re: Replacing drives in bricks / Message-ID: <BsmdnfZOFsXGr9TZRVn-iA@libcom.com>    Rob Brown wrote:% > On Thu, 20 Apr 2006, syslost wrote:  > G >> But wait there's more.. I also have 48 ba350-sb shelves.  Some have  F >> 150 watt power supplys, and all have two fans.  Same deal, you pay  >> only the shipping.  >  > J > This sounds attractive.  Now here is a hypothetical.  I get a BA350 and E > some rz28s in storageworks bricks.  n years down the road an rz28s  K > dies.  What is the wisdom of opening up the bricks in replacing the dead  F > drive with a modern drive (with appropriate cabling and terminators < > etc.) so that I can continue to use the slot in the BA350? > : > Would you do it as a hobbyist?  Would you do it at work? > 	 > Thanks.  >  > - Rob   > The correct reply to this, which you'll hate, is "it depends".  F BA350 shelves are, I believe, narrow SCSI.  Wide, and the even faster I follow-ups need not apply.  It's getting hard to find narrow SSCSI disks.   I The enclosures for the disks are "wired" for specific drives.  They have  C a plug, and if the pins in the dirves do not match, it's not good.  B Doesn't help to have the parity pin connected to one of the drive 
 address pins.   H If you can find drives where the pins match what the drive enclosure is - set up for, then yes, you can replace drives.   I It was a bit tough for me.  While I'd appriciate some more RZ26 and RZ28  C drives, I already have some spares.  Better to leave the available  G drives for other hobbyists.  I also have an unused BA350 and an unused  6 BA356.  Stupid to get more when others could use them.   --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com 170 Grimplin Road  Vanderbilt, PA  15486    ------------------------------  # Date: Fri, 21 Apr 2006 19:44:52 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com>' Subject: Re: Replacing drives in bricks 2 Message-ID: <UCa2g.6686$W64.4883@news.cpqcorp.net>   Rob Brown wrote:  J > This sounds attractive.  Now here is a hypothetical.  I get a BA350 and E > some rz28s in storageworks bricks.  n years down the road an rz28s  K > dies.  What is the wisdom of opening up the bricks in replacing the dead  F > drive with a modern drive (with appropriate cabling and terminators < > etc.) so that I can continue to use the slot in the BA350?  ?    Now here's another hypothetical: how comfortable are you in  F performing SCSI device integration and testing, and hardware surgery? H (Without intending offense, if you have to ask this sort of a question, ? well, then you are clearly headed for a bit of a, um, learning  G experience.  If that's interesting to you or if that's your real goal,   of course, do have at.)   C    The older boxes don't provide Ultra or Wide or such, as a start.   E    Is the transplant you suggest possible?  Sure.  Will you alway be  F able to integrate an arbitrary widget into an arbitrary enclosure and I get it to work with an arbitrary system?  Probably not.  (And don't take  B that or the rest of this reply personally, BTW, as I'm not at all G certain I could manage an "arbitrary integration" task -- lately, I've  I been having way too much "fun" with I/O bridge chips (southbridges), and  H with the interactions of the southbridge with certain of the common I/O 1 peripherals, to sign up for that particular bet.)   : > Would you do it as a hobbyist?  Would you do it at work?  I    Various used RZ bricks in this series have been regularly selling for  H US$10 to US$20, or so.  In a few years, what are now current bricks and F storage will be selling at similar prices.  When you get to the point G that you need or want to perform a transplant, then look around and/or   have at.  G    I'd buy a couple of "duds" first, too, and practice -- and BTW, the  F brick-internal cables will also need to match up reasonably well with $ your transplant-candidate disk, too.  =    General third-party device integration discussions are an  H ever-popular fodder here in the newsgroups, and there is also a related E section on this same topic available within the OpenVMS FAQ, as well.    ------------------------------    Date: 21 Apr 2006 13:05:39 -0700( From: "Rich Jordan" <jordan@ccs4vms.com>' Subject: Re: Replacing drives in bricks C Message-ID: <1145649939.062759.113360@i39g2000cwa.googlegroups.com>   C I would never do this for production work.  However if you pull the E drive (carefully) from the container and ID it, you may find that the D manufacturer made different capacities in the same model; same modelF means almost certainly the same connectors and DIP pin connections, so the internal cable will work.   D I had an Ebay blue container 9GB/7200RPM drive that would work for aD few hours then die.  When I disassembled it I found it was a SeagateE 80-pin unit; when I visited the Seagate site I found its model number E was the smallest member of a set of disks that topped out at 50GB.  A E bit of froogle and pricewatch searches found one of those 50GB models D (cheaper than the 18 and 36!) for around $35 (and this was in 2004).F That disk installed perfectly and has been working just fine, 24x7, in4 the same SBB container in my BA364 tower since then.  C If you are careful you may be able to pop the top off the container D without hurting the cable or causing any harm.  You can then confirmD the drive model and brand, and do some searching for other models in> the same series.  You can probably still find that info at theA manufacturer (or successor) sites even for the old narrow 5400RPM  drives.   ? Not for production because the drives you find will probably be E generic/peecee, and without DEC firmware.  However we've been running D error free for years at home and work doing that, with recent enough versions of VMS.   Rich   ------------------------------  % Date: Fri, 21 Apr 2006 18:23:02 -0400 % From: BRAD <bradhamilton@comcast.net> ' Subject: Re: Replacing drives in bricks * Message-ID: <44495B46.5000702@comcast.net>   Rob Brown wrote:% > On Thu, 20 Apr 2006, syslost wrote:  [...] J > This sounds attractive.  Now here is a hypothetical.  I get a BA350 and E > some rz28s in storageworks bricks.  n years down the road an rz28s  K > dies.  What is the wisdom of opening up the bricks in replacing the dead  F > drive with a modern drive (with appropriate cabling and terminators < > etc.) so that I can continue to use the slot in the BA350? > : > Would you do it as a hobbyist?  Would you do it at work?  F I've done UW bricks in a BA356 as a hobbyist.  I received a number of H "bad" 18G bricks; rather than bothering with shipping them back, I took I the drives out of them, and replaced them with 36/72G Seagate drives.  I  H took care to get the "thin" (1-inch?) drives, since the bricks had foam F inserts in them to "cradle" the thin drives in the "relatively" thick  bricks.  Work like a charm!   E In my previous job, I replaced drives inside RZ28 narrow bricks with  I similar, good, working drives purchased from e-bay.  The drives were not  B under any kind of HW warranty, so no worries (!).  Of course, the B previous discussion assumes that you do not have/will not need HW I warranty service for any drives you replace.  I imagine that third-party  G vendors will service such equipment, for an (appropriately) large fee,  H but if you're going that route, you might as well let the vendor do the  whole job, soup-to-nuts.  F The toughest part(s) of the operation are remembering to remove all 4 = screws from the "base" of the bricks, and (carefully) prying  H off/re-inserting the "ribbon" cable that supplies LED-signaling and pin E connectivity to the "backplane".  I've wrecked at least two of those  H jobbies in the several years' experience I've had with manipulating the  bricks.    ------------------------------  % Date: Fri, 21 Apr 2006 18:21:48 -0400 / From: "William Webb" <william.w.webb@gmail.com> ' Subject: Re: Replacing drives in bricks I Message-ID: <8660a3a10604211521s36c7a851wf5470ec65b54925d@mail.gmail.com>   2 On 4/21/06, Rob Brown <mylastname@gmcl.com> wrote:% > On Thu, 20 Apr 2006, syslost wrote:  > G > > But wait there's more.. I also have 48 ba350-sb shelves.  Some have F > > 150 watt power supplys, and all have two fans.  Same deal, you pay > > only the shipping. > E > This sounds attractive.  Now here is a hypothetical.  I get a BA350 H > and some rz28s in storageworks bricks.  n years down the road an rz28sE > dies.  What is the wisdom of opening up the bricks in replacing the > > dead drive with a modern drive (with appropriate cabling andH > terminators etc.) so that I can continue to use the slot in the BA350? >   > Would you do it as a hobbyist?  4 Not for 28s at this point as they're a dime a dozen.  9 Generally speaking, though, would do so and have done so.    Would you do it at work?    Depends upon the type of "work".  D There are those little breakaway foil labels over some of the screws0 and  joints which say "Warranty Void If Removed.  F And in some situations that's a little more serious than those "Do NotC Remove This Tag Under Penalty Of Law" tags that come on mattresses.    WWWebb > 	 > Thanks.  >  > - Rob  >  >  > -- > D > Rob Brown                        b r o w n a t g m c l d o t c o mC > G. Michaels Consulting Ltd.      (866)438-2101 (voice) toll free! 8 > Edmonton                         (780)438-9343 (voice)8 >                                    (780)437-3367 (FAX)5 >                                    http://gmcl.com/  >  >      --C NOTE: This email address is only used for noncommerical VMS-related  correspondence. C All unsolicited commercial email will be deemed to be a request for 8 services pursuant to the terms and conditions located at# http://bellsouthpwp.net/w/e/webbww/    ------------------------------  % Date: Fri, 21 Apr 2006 15:32:18 -0700 # From: "Tom Linden" <tom@kednos.com> ' Subject: Re: Replacing drives in bricks ) Message-ID: <op.s8dp74x5zgicya@hyrrokkin>   J On Fri, 21 Apr 2006 10:02:58 -0700, Rob Brown <mylastname@gmcl.com> wrote:  % > On Thu, 20 Apr 2006, syslost wrote:  > L >> But wait there's more.. I also have 48 ba350-sb shelves.  Some have 150  L >> watt power supplys, and all have two fans.  Same deal, you pay only the   >> shipping. > K > This sounds attractive.  Now here is a hypothetical.  I get a BA350 and   F > some rz28s in storageworks bricks.  n years down the road an rz28s  L > dies.  What is the wisdom of opening up the bricks in replacing the dead  G > drive with a modern drive (with appropriate cabling and terminators   < > etc.) so that I can continue to use the slot in the BA350? > : > Would you do it as a hobbyist?  Would you do it at work? > 	 > Thanks.  >  > - Rob  > K I have a BA356 in which I replaced all the 4.3GB drives in the cannisters    withD device type SEAGATE ST373405LC, and the answer is yes to both your  
 questions.J Of course, this somewhat overkill since the BA356 transfer rate is 1/4th   thatG of the drives.  Have a spare which IO  can pop in if needed.  I would   	 guess you + could get such drives today for about $200@    ------------------------------  % Date: Fri, 21 Apr 2006 16:06:43 -0700 # From: "Tom Linden" <tom@kednos.com> ' Subject: Re: Replacing drives in bricks ) Message-ID: <op.s8drthdbzgicya@hyrrokkin>   J On Fri, 21 Apr 2006 15:23:02 -0700, BRAD <bradhamilton@comcast.net> wrote:  I > The toughest part(s) of the operation are remembering to remove all 4   @ > screws from the "base" of the bricks, and (carefully) prying  K > off/re-inserting the "ribbon" cable that supplies LED-signaling and pin   H > connectivity to the "backplane".  I've wrecked at least two of those  K > jobbies in the several years' experience I've had with manipulating the   	 > bricks.   D Remove the face plate first by depressing the two tabs on each side.E If you are doing this with a slotted screw driver, a strong thumbnail E helps to keep one unlatched while you work on the other, and yes, the G tabs can break.  Next use a similar technique to remove upper half from F lower.  The 4 mounting screws are concealed by the adhesive label, butE you can readily find them.  You don't need to remove the label simply F ream it out where the screws are.  Remove the thin film cable form the@ drive is obvious as is the attachment to the DIN41612 connector.   ------------------------------   Date: 21 Apr 2006 22:26:01 GMT From: healyzh@aracnet.com ' Subject: Re: Replacing drives in bricks , Message-ID: <e2bm5p01pnq@enews4.newsguy.com>  & Rob Brown <mylastname@gmcl.com> wrote:% > On Thu, 20 Apr 2006, syslost wrote:   H > > But wait there's more.. I also have 48 ba350-sb shelves.  Some have G > > 150 watt power supplys, and all have two fans.  Same deal, you pay   > > only the shipping.  F > This sounds attractive.  Now here is a hypothetical.  I get a BA350 I > and some rz28s in storageworks bricks.  n years down the road an rz28s  F > dies.  What is the wisdom of opening up the bricks in replacing the ? > dead drive with a modern drive (with appropriate cabling and  H > terminators etc.) so that I can continue to use the slot in the BA350?  : > Would you do it as a hobbyist?  Would you do it at work?  E I'm not sure which BA350 varient the -SB is, but be aware that to run I 7200RPM disks the shelves need 2x speed fans.  All my single shelves came J with the old 1x fans, which I then replaced with the 2x fans from a couple
 arrays I got.   L I ran a shelf of the RZ28's for at least a couple years before I upgraded toE RZ29's, which I ran for several years.  I've since moved to a pair of K Andataco 3 disk JBOD units.  The Andataco canistors easily take both the 1" L and 1.6" SCA hard drives, no fiddling required.  Plus they can easily handle8 cooling 10k drives, and probably the 15k drives as well.  J I do still use the RZ29-VA's and the BA350's.  They're great to hook up toI something with Narrow SCSI such as a VAXstation 4000 or AlphaStation 200.   L As a Hobbyist I'd consider replacing the newer Blue cannistor disks if I hadK a working shelf, for the older Narrow SCSI, I don't consider it to be worth I the effort (but then it doesn't help that I have more RZ29-VA's than I do  loose narrow SCSI drives.   L For work, it would depend on how tight the budget was.  Years ago we used toK do this with another storage solution that we used.  I'd just as soon stick 0 with strictly supported configurations for work.   		Zane   ------------------------------  % Date: Fri, 21 Apr 2006 17:10:21 -0700 # From: "Tom Linden" <tom@kednos.com> ' Subject: Re: Replacing drives in bricks ) Message-ID: <op.s8durjapzgicya@hyrrokkin>   . On Fri, 21 Apr 2006 16:48:21 -0700, JF Mezei  % <jfmezei.spamnot@teksavvy.com> wrote:    > Malcolm Dunnett wrote:J >>    I mostly work with the wide bricks and they generally use 80 PIN SCAG >> connectors. In that system the SCSI ID pins are part of the 80 pin    >> connectorG >> and there's no chance to get it wrong - they're just "plug and play"  > F > Does the brick leave enough room to put in some SCA adaptor or 50 toF > 68pin adaptor etc ? Or is the mechanical fitting so tight that it is( > really difficult to add such a gizmo ?   No room.  Its 80 pin.    ------------------------------  % Date: Fri, 21 Apr 2006 19:48:21 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> ' Subject: Re: Replacing drives in bricks , Message-ID: <44496F44.716DEB23@teksavvy.com>   Malcolm Dunnett wrote:I >    I mostly work with the wide bricks and they generally use 80 PIN SCA N > connectors. In that system the SCSI ID pins are part of the 80 pin connectorF > and there's no chance to get it wrong - they're just "plug and play"  D Does the brick leave enough room to put in some SCA adaptor or 50 toD 68pin adaptor etc ? Or is the mechanical fitting so tight that it is& really difficult to add such a gizmo ?   ------------------------------  % Date: Fri, 21 Apr 2006 21:35:52 -0500 @ From: "David J. Dachtera" <djesys.nospam@NeOaSrPtAhMlNiOnWk.net>' Subject: Re: Replacing drives in bricks 6 Message-ID: <44499688.E56F70B7@NeOaSrPtAhMlNiOnWk.net>   BRAD wrote:  >  > Rob Brown wrote:' > > On Thu, 20 Apr 2006, syslost wrote:  > [...] K > > This sounds attractive.  Now here is a hypothetical.  I get a BA350 and F > > some rz28s in storageworks bricks.  n years down the road an rz28sL > > dies.  What is the wisdom of opening up the bricks in replacing the deadG > > drive with a modern drive (with appropriate cabling and terminators > > > etc.) so that I can continue to use the slot in the BA350? > > < > > Would you do it as a hobbyist?  Would you do it at work? > G > I've done UW bricks in a BA356 as a hobbyist.  I received a number of I > "bad" 18G bricks; rather than bothering with shipping them back, I took J > the drives out of them, and replaced them with 36/72G Seagate drives.  II > took care to get the "thin" (1-inch?) drives, since the bricks had foam G > inserts in them to "cradle" the thin drives in the "relatively" thick  > bricks.  Work like a charm!   H I'd be interested to know which 36/72GB drives you've used and where youH got them, and if anything bigger than a 9GB drive is available that willD work/fit the -VA variants. Specifically, I'm looking for RZ40/equiv. type drives.   > [snip]G > The toughest part(s) of the operation are remembering to remove all 4 > > screws from the "base" of the bricks, and (carefully) pryingI > off/re-inserting the "ribbon" cable that supplies LED-signaling and pin F > connectivity to the "backplane".  I've wrecked at least two of thoseI > jobbies in the several years' experience I've had with manipulating the 	 > bricks.    Yeah - those are a bit fragile.    --   David J Dachtera dba DJE Systems  http://www.djesys.com/  & Unofficial OpenVMS Marketing Home Page! http://www.djesys.com/vms/market/   ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/   ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/   ------------------------------  % Date: Sat, 22 Apr 2006 01:32:19 -0400 ' From: Dave Froble <davef@tsoft-inc.com> ' Subject: Re: Replacing drives in bricks 9 Message-ID: <t-ednRWp693AItTZnZ2dneKdnZydnZ2d@libcom.com>    JF Mezei wrote:  > Malcolm Dunnett wrote: > I >>   I mostly work with the wide bricks and they generally use 80 PIN SCA N >>connectors. In that system the SCSI ID pins are part of the 80 pin connectorF >>and there's no chance to get it wrong - they're just "plug and play" >  > F > Does the brick leave enough room to put in some SCA adaptor or 50 toF > 68pin adaptor etc ? Or is the mechanical fitting so tight that it is( > really difficult to add such a gizmo ?  G No way!  For any of them, things are real tight.  I've got 50, 68, and  # 80 pin types.  Real tight in there.    --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com 170 Grimplin Road  Vanderbilt, PA  15486    ------------------------------  % Date: Fri, 21 Apr 2006 19:31:51 +0200 , From: Albrecht Schlosser <ajs567@tiscali.de>& Subject: Re: Strange disk device state, Message-ID: <fu4b2e.i78.ln@news.hus-soft.de>   Rob Brooks wrote: 0 > Albrecht Schlosser <ajs567@tiscali.de> writes: >> Hoff Hoffman wrote:J >>>   This appears to be an erroneously decremented reference count, most * >>> likely.  A kernel bug, in other words. > P > Yup; I just checked with the engineer who deals with MOUNT, and he's not awareP > of any outstanding problem in this area.  That, of course, doesn't absolve us,9 > but there is no known patch kit to address this issue.   > M >>>   Short of patching the kernel, I don't know a way to clear this without  
 >>> a reboot. L >> We'll leave the system in this state at least until monday, just in case " >> someone would have another idea >  > There is no other idea.   @ I didn't really expect one to solve the problem, but maybe some @ VMS/developer person who would like me to gather some more info.  B > You'll need to reboot, unless you want to patch the longword at Q > ucb->ucb$l_refc to be 0, instead of FFFFFFFF.  This is, of course, unsupported, & > and may lead to further instability.   I understand ;-)  Q > Having said that, I've done it with seemingly good results, but I'm not running G > any production systems, and picking through crash dumps are a way of   > life for me :-)   G Well, it _is_ a production system, and it must (or it should at least)  G run 24 hours, 7 days. But before I start patching kernel structures, I  1 think that we _will_ reboot the system next week.    Albrecht   ------------------------------  # Date: Fri, 21 Apr 2006 19:58:04 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com>& Subject: Re: Strange disk device state2 Message-ID: <gPa2g.6691$p54.4347@news.cpqcorp.net>   Albrecht Schlosser wrote:  > Rob Brooks wrote: 1 >> Albrecht Schlosser <ajs567@tiscali.de> writes:  >>> Hoff Hoffman wrote: F >>>>   This appears to be an erroneously decremented reference count, 0 >>>> most likely.  A kernel bug, in other words. >> ... B > I didn't really expect one to solve the problem, but maybe some B > VMS/developer person who would like me to gather some more info.    D    Unless you happen to know how you got into this particular state G and/or unless you can reproduce it, there's probably not much that the  H running system or the carcass can likely tell us.  The "fun" here isn't C the current state, it's how the system and the device got into the   particular state.   F    35000 errors implies rather serious problems with the SCSI bus, or F with at least one of the devices present on the bus, too.  Obviously, G the disk itself is the first and most obvious candidate for a hardware  H problem.  (And devices that are not responding appropriately can end up F wedged in all manner of odd states -- unstable hardware can and often   does produce unstable software.)  B    I don't know that the disks on an rx2600 series are considered G hot-swap; it's been my experience that controllers and storage devices  D that support this sort of thing have a way to quiesce the SCSI bus. D Traditional SCSI devices can see a bus transient when the device is C swapped in or out, and whether or not this matters depends on what  % happens to be "in flight" on the bus.   I > Well, it _is_ a production system, and it must (or it should at least)  I > run 24 hours, 7 days. But before I start patching kernel structures, I  3 > think that we _will_ reboot the system next week.   G    I might force a crash (and generate a carcass, err, crashdump), but  H other than that, I'd get the system rebooted and get it all back online.   ------------------------------  % Date: Fri, 21 Apr 2006 16:07:18 -0400 ' From: Dave Froble <davef@tsoft-inc.com> & Subject: Re: Strange disk device state/ Message-ID: <mdKdnbvGiohsp9TZRVn-vw@libcom.com>    Albrecht Schlosser wrote:  > Rob Brooks wrote:  > 1 >> Albrecht Schlosser <ajs567@tiscali.de> writes:  >> >>> Hoff Hoffman wrote:  >>> F >>>>   This appears to be an erroneously decremented reference count, 0 >>>> most likely.  A kernel bug, in other words. >> >>H >> Yup; I just checked with the engineer who deals with MOUNT, and he's  >> not awareF >> of any outstanding problem in this area.  That, of course, doesn't  >> absolve us,9 >> but there is no known patch kit to address this issue.  >>F >>>>   Short of patching the kernel, I don't know a way to clear this  >>>> without a reboot. >>> H >>> We'll leave the system in this state at least until monday, just in ( >>> case someone would have another idea >> >> >> There is no other idea. >  > B > I didn't really expect one to solve the problem, but maybe some B > VMS/developer person who would like me to gather some more info. > C >> You'll need to reboot, unless you want to patch the longword at  F >> ucb->ucb$l_refc to be 0, instead of FFFFFFFF.  This is, of course,  >> unsupported, ' >> and may lead to further instability.  >  >  > I understand ;-) > G >> Having said that, I've done it with seemingly good results, but I'm   >> not runningH >> any production systems, and picking through crash dumps are a way of  >> life for me :-) >  > I > Well, it _is_ a production system, and it must (or it should at least)  I > run 24 hours, 7 days. But before I start patching kernel structures, I  3 > think that we _will_ reboot the system next week.  > 
 > Albrecht  I Steve and Rob will definitely be closer to understanding this than I am,  D but a thought.  If the disk is truly dead, perhaps the system never I received something it needed to dismount the disk.  I'd expect some type  F of timeout to resolve this.  The reference count seems to be at least  some part of the problem.   F I believe you mentioned that the disk was hot-swapable?  Why not just G pull the bugger and insert a hopefully good disk.  Could be wrong, and  D Steve and Rob seem to indicate that this may not work, but VMS just G might surprise you once it can get the disk to respond.  I would be at  G the stage of ready to re-boot the system, just in case the action does   the re-boot for you.  E It would be very interesting to see if VMS recovers with a good disk.    --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com 170 Grimplin Road  Vanderbilt, PA  15486    ------------------------------  % Date: Fri, 21 Apr 2006 16:18:08 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> & Subject: Re: Strange disk device state, Message-ID: <44493DFB.8DFFB2D8@teksavvy.com>   re: reference count of -1   ( Have you tried SHOW DEV /FILES dka100: ?   If you do :   ? $INSTALL LIST , does it show any installed files on that disk ?     E From the SYSTEM account will all privileges, what happens if you try:    DISMOUNT dka100: DISMOUNT/ABORT dka100:  G I was think of some program that does a direct DISK $QIO. It would then E increment the reference count, possibly set it to 0, which would then F allow you to manipulate the drive. IF you could get the drive mounted,G you can then install a few files to raise the reference count, and then E exit from that QIO program (which would decrease the reference count, G but due to the installed files, the reference count would still be > 0.   G The real screw up would happen when the devide is next dismounted since - the reference count would again go down to -1      Reboot would be safer.   ------------------------------  % Date: Fri, 21 Apr 2006 16:30:28 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> & Subject: Re: Strange disk device state, Message-ID: <444940DE.9DA50A24@teksavvy.com>   Albrecht Schlosser wrote: H > Well, it _is_ a production system, and it must (or it should at least)H > run 24 hours, 7 days. But before I start patching kernel structures, I3 > think that we _will_ reboot the system next week.    No, you should have said:   G But before rebooting the system next week, I'll try patching the kernel * structures to see if it would have worked.  H Once you know the system will go down anyways, you may as well try it toB see if it could save the day. Just make sure your applications areH shutdown so that if the system does crash, it con't cause any damage and you can reboot right away.   ------------------------------  % Date: Fri, 21 Apr 2006 21:23:40 -0500 @ From: "David J. Dachtera" <djesys.nospam@NeOaSrPtAhMlNiOnWk.net>% Subject: Re: The Undocumented OpenVMS 6 Message-ID: <444993AC.3E1B625A@NeOaSrPtAhMlNiOnWk.net>   JF Mezei wrote:  > 1 > Phillip Helbig---remove CLOTHES to reply wrote: > > > > Think: multicast powerpoint, with audio and a chat line.! > >   ^^^^^            ^^^^^^^^^^  > > Isn't that a contradiction?  > E > No. It simply means that I won't even bother checking that web site ? > because it is very unlikely I can view that prorietary thing.   G Depends on whether you allow javascript (Hi, Larry!). PowerPoint is not ) required, I just used that as an analogy.    --   David J Dachtera dba DJE Systems  http://www.djesys.com/  & Unofficial OpenVMS Marketing Home Page! http://www.djesys.com/vms/market/   ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/   ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/   ------------------------------  % Date: Fri, 21 Apr 2006 21:25:55 -0500 @ From: "David J. Dachtera" <djesys.nospam@NeOaSrPtAhMlNiOnWk.net>% Subject: Re: The Undocumented OpenVMS 6 Message-ID: <44499433.A063A17F@NeOaSrPtAhMlNiOnWk.net>   Neil Rieck wrote:  > . > <VAXman- @SendSpamHere.ORG> wrote in message, > news:00A548B0.DBC1E71A@SendSpamHere.ORG...N > > In article <4448449B.EA101E7A@NeOaSrPtAhMlNiOnWk.net>, "David J. Dachtera"2 > > <djesys.nospam@NeOaSrPtAhMlNiOnWk.net> writes: > >  > >  > > Is it really powerpuke?  > > N > > I know HPs webinars that they keep excluding me from attending require the > > use F > > of Billzebub-warez Infernonet Exploiter but I was able to pass the > > requirementsN > > for Parsec's webinar using my Safari borwser on my Powerbook running OS X. > > I K > > didn't get to attend the last seminar tho.  I'm looking forward to this  > > next= > > one  only to see what's actually involved in a "webinar".  > >  > > --4 > > VAXman- A Bored Certified VMS Kernel Mode Hacker > > VAXman(at)TMESIS(dot)COM > >  > M > Like you, I am not a fan of MS apps and OSs but will endure both to have my   > OVMS knowledge base increased.  H I tolerate WhineBloze and Interhose Exploder as a necessary evil. I even= have an iPaq that I won for submitting session evaluations at 
 HPworld-2004.    --   David J Dachtera dba DJE Systems  http://www.djesys.com/  & Unofficial OpenVMS Marketing Home Page! http://www.djesys.com/vms/market/   ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/   ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/   ------------------------------  % Date: Fri, 21 Apr 2006 21:24:17 -0500 @ From: "David J. Dachtera" <djesys.nospam@NeOaSrPtAhMlNiOnWk.net>% Subject: Re: The Undocumented OpenVMS 4 Message-ID: <444993D1.521852@NeOaSrPtAhMlNiOnWk.net>  ! VAXman-, @SendSpamHere.ORG wrote:  > { > In article <4448449B.EA101E7A@NeOaSrPtAhMlNiOnWk.net>, "David J. Dachtera" <djesys.nospam@NeOaSrPtAhMlNiOnWk.net> writes:  > >  > >  > >JF Mezei wrote: > >> > >> Laura wrote: D > >> > This one-hour Webinar will cover the undocumented features ofL > >> > OpenVMS--some humorous, some useful, and some you might already know. > >>M > >> Sounds interesting. But what exactly is a "one hour webinar". A bunch fo / > >> web pages availabel only during one hour ?  > >>L > >> A Flash movie ? and Windows media stream ? Some JAVA chat application ? > > ; > >Think: multicast powerpoint, with audio and a chat line.  >  > Is it really powerpuke?   / Probably not, but probably requires javascript.    --   David J Dachtera dba DJE Systems  http://www.djesys.com/  & Unofficial OpenVMS Marketing Home Page! http://www.djesys.com/vms/market/   ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/   ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/   ------------------------------    Date: 21 Apr 2006 15:16:31 -0700) From: "Sue" <susan_skonetski@hotmail.com> + Subject: Updated VMS information - April 21 C Message-ID: <1145657791.084446.141240@e56g2000cwe.googlegroups.com>    Dear Newsgroup  E Here is the latest VMS Updated Information.  As you know as soon as I D send this out, something will come in ;').  Have a wonderful weekend# and thank you for all your support.   
 Warm Regards,  Sue  ___________________________  1. Time Sensitive: 2. In the Press: 3. Sue's Fav's:  4. Partner Information:    1. Time Sensitive:  8 ONE MORE WEEK TO REGISTER FOR MONTREAL TECHNICAL SEMINARC There is less than one week remaining to register for the technical C seminar in Montreal. A few spots are still available and seating is E very limited so, if you are still planning to attend, it is advisable E to reserve your seat right away to avoid disappointment. To register, E please go to: http://www.encompasscanada.com/seminar-registration.htm    Mark your calendar now!  HP Technology Forum 2006 September 17-21, 2006 . George R. Brown Convention Center, Houston, TX   ____________________   2. In the Press   B http://biz.yahoo.com/prnews/060418/sftu075.html?.v=48  PointSecureB Helps to Secure Corporate Data and Enforce Security Policies on HP Integrity Servers   N http://sev.prnewswire.com/computer-electronics/20060307/SFTU03807032006-1.htmlG Oracle Unveils Oracle(R) Rdb 7.2 for HP OpenVMS on HP Integrity Servers  and AlphaServer Systems   D http://home.nestor.minsk.by/computers/news/2006/04/0411.html AppWorx5 Announces Enhanced Functionality in AppWorx Version 7   L http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=10193912 - Cluster with 9 year up time ____________________   3. Sue's Fav's:   B HP set the 'gold standard' for reliability and now brings you more http://tinyurl.com/l7nrk or    http://h71028.www7.hp.com/erc/library/GetPage.aspx?pageid=313885&audienceid=0&statusid=0&ccid=0&langid=121&ERL=true&pageTitle=Enterprise%20library:%20HP%20set%20the%20'gold%20standard'%20for%20reliability%20and%20now%20brings%20you%20more   HP StorageWorks for OpenVMS 0 http://h18006.www1.hp.com/storage/osopenvms.html  , www.sciinc.com - Great Partner, Great People  F A Person had this question -  Do you know if a PDF of the DEC DEMSA-AA( manual exists.  Then provided the answerL http://www.sysworks.com.au/disk$vaxdocmar962/decw$book/d3euaaa3.p9.decw$book  - <http://vt100.net/mirror/antonio/usv-rep.pdf>   / Improved event logging for background processes C A Synergy program running in the background (as a scheduled task or F service) can write errors and information to the event log on Windows,B to syslog on Unix, or to the operator log on OpenVMS. This is most- beneficial to services and detached programs. 3 http://www.synergex.com/solutions/synergy/SDE83.asp    ________________________   4. Partner Information:   D 2006 series of HP-Intel Developer Forums - don't miss this chance to3 port your software and get an  HP Integrity server:     L http://h21007.www2.hp.com/dspp/bus/bus_BusDetailPage_IDX/1,1252,6045,00.html  C WIN2WIN contest - report your wins and enter to win an HP Integrity  server :    P http://h21007.www2.hp.com/dspp/OnlineForm/form_OnlineForm_IDX/1,2914,170,00.html  C OpenVMS Bootcamp Partner Roundhouse - Tuesday, May 23, Nashua, NH - . sign up now for your free table at this event:    : http://h71000.www7.hp.com/symposium/roundhouse_signup.html   ------------------------------  # Date: Fri, 21 Apr 2006 23:00:10 GMT   From: John Santos <john@egh.com>& Subject: Re: VAX Q-bus and SCSI Disks?( Message-ID: <_td2g.430$bU6.345@trnddc06>   JF Mezei wrote:  > Hoff Hoffman wrote:  > I >>   nb: The KFQSA was an interesting widget to configure, as the numbers I >>of DSSI ISEs (disks) connected onto the DSSI bus changed the numbers of A >>emulations presented to the hosts and changes to the numbers of H >>emulations could cause a cascading series of CSR and vector changes on$ >>other lower-ranked Q-bus modules.  >  >  > Interesting. > C > For my Dilog SQ 739, this is not the case. Itr generates RA drive I > devices (DUAx) and appears as a single controller with a single slot on > > the QBUS no matter how many SCSI devices are attached to it. > J > I find it interesting that for Q-BUS to SCSI adaptors, the "competition"I > were able to design something which was truly superior in functionality C > to the DEC products.  I take it Digital was interested in locking D > costomers to RD54 drives at $9000 a piece and preventing them from@ > connecting $200 drives with greater capacity to their systems.  H I think you are wrong about the motive.  I think DEC was more interestedC in selling you a new CPU with DSSI or SCSI drives (depending on the F the time period) than in selling you a new controller so you could putE spiffy new (3rd-party?) SCSI drives on your obsolete, puny little [1] C MV-II.  (BTW, I don't think SCSI drives cost $200 at the time, more 8 like $1000, which was still much cheaper than new RD's.)    G [1] Even without its glasses, dressed in a blue and red cape with a big G "S", and bathed by the rays of a yellow sun, I don't see how anyone can  call an MV-II "all mighty" :-)  G P.S.  The Dilog controller sounds pretty cool.  I bet it also uses much  less power than my KDA50's...    --   John Santos  Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  % Date: Fri, 21 Apr 2006 20:02:41 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> & Subject: Re: VAX Q-bus and SCSI Disks?, Message-ID: <444972A0.34F534E5@teksavvy.com>   John Santos wrote:G > spiffy new (3rd-party?) SCSI drives on your obsolete, puny little [1] 	 > MV-II.    , DON'T EVER INSULT MY ALL MIGHTY MICROVAX II.    E  And it was anything but "little" (mine was in the large Q5 cabinet).    ------------------------------  # Date: Sat, 22 Apr 2006 00:47:36 GMT   From: John Santos <john@egh.com>& Subject: Re: VAX Q-bus and SCSI Disks?' Message-ID: <I2f2g.442$bU6.39@trnddc06>    JF Mezei wrote:  > John Santos wrote: > G >>spiffy new (3rd-party?) SCSI drives on your obsolete, puny little [1] 	 >>MV-II.   >  > . > DON'T EVER INSULT MY ALL MIGHTY MICROVAX II. >  > G >  And it was anything but "little" (mine was in the large Q5 cabinet).   H So is mine, but the insides were replaced (many years ago) by a VAX 3600A CPU and memory.  Only two slots capable of holding memory boards, E though, so I only have 24MB (16MB+8MB).  A real s-box would allow for E more memory.  (Q22 slots?, QCD slots?, I forget the terminology, need  to google for "serpentine"!)  G Since I now have my Vax 4300 up and running, I'll soon brain-transplant G my 11/73 into the MVII box.  Now there's a real *ALL MIGHTY* system :-)   D (Getting the Q5 cab into the basement was fun.  Even the SA7XX box IC replaced the RA81 with is fairly hefty - loads of thick gauge sheet 1 metal.  I bet a Glock 9mm would just bounce off.)    --   John Santos  Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  % Date: Sat, 22 Apr 2006 01:25:55 -0400 ' From: Dave Froble <davef@tsoft-inc.com> & Subject: Re: VAX Q-bus and SCSI Disks?9 Message-ID: <t-ednRqp691DINTZnZ2dneKdnZydnZ2d@libcom.com>    JF Mezei wrote:  > John Santos wrote: > G >>spiffy new (3rd-party?) SCSI drives on your obsolete, puny little [1] 	 >>MV-II.   >  > . > DON'T EVER INSULT MY ALL MIGHTY MICROVAX II. >  > G >  And it was anything but "little" (mine was in the large Q5 cabinet).   E Sorry, one of my VAXstation 4000 model 90A systems, capable of being  @ carried under one arm, makes that MVII an oversize paper weight.  I Compared to everything prior to them, the last N-VAX systems were a real  G marvel (no pun (or otherwise) intended).  They got the clock up to 100  7 MHz, and we're talking mid 90s and a CISC architecture.    --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com 170 Grimplin Road  Vanderbilt, PA  15486    ------------------------------    Date: 21 Apr 2006 18:02:29 -0700) From: "Sue" <susan_skonetski@hotmail.com>  Subject: VMS news from France C Message-ID: <1145667749.140052.262470@i39g2000cwa.googlegroups.com>    Dear Distribution Lists,  D The following announcement is in French.  However the translation is> fairly obvious but just in case I have done a somewhat amateur0 translation for you, please forgive my mistakes.  C SysGroup announces the availability of MySQL 5.1.7-beta for OpenVMS  Alpha and IA64 .  D The Alpha version has been used for a few days on a site without any particular problems.  A SysGroup currently seeks more sites and additional testers. (Beta G sites) If you are interested, please let us know it by sending email to   sysgroup@sysgroup.fr   D SysGroup has  worked for several years in the support and porting of MySQL to OpenVMS  ' Jean-Francois will be at the boot camp.   
 Warm Regards,  Sue      -----Original Message----- From: Skonetski, Susan$ Sent: Friday, April 21, 2006 1:51 PM To: OpenVMS Direct! Subject: FW: VMS news from France     F I think that even if you do not read French you will find the attached  interesting as well as exciting.   Sue      -----Original Message-----0 From: remi jolin [mailto:remi.jolin@sysgroup.fr]% Sent: Friday, April 21, 2006 12:47 PM  To: Skonetski, Susan Subject: VMS news from France      Hi Sue, how are you ?   4 As I know you read french, you should have a look toG http://www.sysgroup.fr/news.htm where Jean-Francois Pieronne has made a    great announcement.        Amicalement, Remi.    ------------------------------   End of INFO-VAX 2006.222 ************************