1 INFO-VAX	Sat, 26 Mar 2005	Volume 2005 : Issue 170       Contents:P Re: Announcing Availability of HP OpenVMS Migration Software for Alpha to IntegrP Re: Announcing Availability of HP OpenVMS Migration Software for Alpha to IntegrP Re: Announcing Availability of HP OpenVMS Migration Software for Alpha to Integr$ Re: Carly's Way - article retracted?$ Re: Carly's Way - article retracted? decnet for linux problem5 Re: DS15 RADEON 7500 hang solved (at least partially) 5 Re: DS15 RADEON 7500 hang solved (at least partially) 5 Re: DS15 RADEON 7500 hang solved (at least partially)  Re: History of the VMS shark2 Re: New Customer Benchmark Brochure Info Available# Re: Question on DCL f<dollar>string # Re: Question on DCL f<dollar>string  shadow minicopy  The Greatest News Ever!  Re: VAX 4000 battery  F ----------------------------------------------------------------------  % Date: Sat, 26 Mar 2005 04:38:36 -0500 # From: "John Smith" <a@nonymous.com> Y Subject: Re: Announcing Availability of HP OpenVMS Migration Software for Alpha to Integr , Message-ID: <zqudnb_VIPg_sNjfRVn-oQ@igs.net>   Rob Young wrote:E > In article <3agv68F6akvkgU1@individual.net>, bill@cs.uofs.edu (Bill  > Gunshannon) writes: / >> In article <424338f9$1@news.langstoeger.at>, ; >> peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) writes: A >>> In article <uNE0e.2216$yq1.1658@news.cpqcorp.net>, "Bob Lail"   >>> <Robert.Lail@hp.com> writes:F >>>>  Why do you say that?  OpenVMS V8.2 for AlphaServers is available? >>>> and shipping. The AlphaServer 1200 is one of the supported E >>>> platforms. Future versions will continue to support AlphaServers  >>>> until at least 2010.  >>> E >>> Maybe because he might not order it, because his boss never heard  >>> of VMS, % >>> or heard it died many years ago ?  >>> D >>> Why do you think, he himself believes that VMS (Alpha) is dead ? >>>  >>B >> So I'm sitting in a class on computer security and in the frontB >> of the room the instructor is talkiing about how VMS died aboutC >> the same time Digital did.  The company was bought by Compaq but F >> VMS was already dead.  And then it was bought by some other companyE >> who's name he couldn't recall.  So I piped in that the company was C >> HP and that VMS was still going strong.  "Oh no." he said.  "VMS H >> is dead.  Used for nothing but a few legacy (there's that word again)? >> applications.  You never see it mentioned in the trade press C >> anymore." So I said what about things like JStars?  And he said, / >> "Yeah, JStars and other legacy application."  >> > = > You could have mentioned that a good deal of cellular phone @ > billing back-ends are VMS based, pointed out that is a rapidlyB > growing niche VMS is in.  On one hand, I would have acknowledged> > VMS lives in niches but I would have also pointed out it was? > quite strong in those niches (health care, cell phones, funds  > transfers, manufacturing).     Blowing sunshine again Rob?   F Bill should not have had to say anything about the viability of VMS inE today's marketplace.....that's what HP's advertising of VMS should be I doing....no advertising, no perception of viability. Bill's instructor in J that courcse is but one of hundreds of thousands of people in positions ofL (some) influence who should hear about VMS today but don't - courtesy of the HP/Microsoft alliance.     --F OpenVMS - The never advertised operating system with the dwindling ISV base.    ------------------------------  % Date: Sat, 26 Mar 2005 04:42:13 -0500 # From: "John Smith" <a@nonymous.com> Y Subject: Re: Announcing Availability of HP OpenVMS Migration Software for Alpha to Integr , Message-ID: <krGdnbDuvv3hs9jfRVn-qA@igs.net>   Larry Kilgallen wrote:E > In article <3aharnF69bs4pU1@individual.net>, bill@cs.uofs.edu (Bill  > Gunshannon) writes:  > E >> There is nothing controversial about it at all.  He stated it as a H >> fact and the majority will accept it as such and go on to make futureF >> decisions based on that information.  Note, that one of the reasons@ >> given for this was that VMS never gets mentioned in the tradeE >> journals. Whre have we heard this before?  And who is the only one ' >> capable of doing something about it?  >  > VMS customers.    L We, for the most part, have day jobs which require us to do productive work.I Pushing on a rope for a corporation that does not care one iota about our , suggestions and pleas is not my idea of fun.   --L OpenVMS - The never advertised operating system with the dwindling ISV base.   ------------------------------  % Date: Sat, 26 Mar 2005 09:24:21 -0500 " From: Glenn Everhart <gce@gce.com>Y Subject: Re: Announcing Availability of HP OpenVMS Migration Software for Alpha to Integr , Message-ID: <BpKdnYZfVLac79jfRVn-rA@rcn.net>   Main, Kerry wrote: >>-----Original Message-----" >>From: bill@triangle.cs.uofs.edu A >>[mailto:bill@triangle.cs.uofs.edu] On Behalf Of Bill Gunshannon  >>Sent: March 24, 2005 6:01 PM >>To: Info-VAX@Mvb.Saic.Com ? >>Subject: Re: Announcing Availability of HP OpenVMS Migration  ) >>Software for Alpha to Integrity Servers  >>. >>In article <424338f9$1@news.langstoeger.at>,; >>	peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) writes:  >>; >>>In article <uNE0e.2216$yq1.1658@news.cpqcorp.net>, "Bob   >>$ >>Lail" <Robert.Lail@hp.com> writes: >>< >>>> Why do you say that?  OpenVMS V8.2 for AlphaServers is  >> >>available and  >>; >>>>shipping. The AlphaServer 1200 is one of the supported   >> >>platforms. Future  >>G >>>>versions will continue to support AlphaServers until at least 2010.  >>> ? >>>Maybe because he might not order it, because his boss never   >> >>heard of VMS,  >>$ >>>or heard it died many years ago ? >>> C >>>Why do you think, he himself believes that VMS (Alpha) is dead ?  >>>  >>A >>So I'm sitting in a class on computer security and in the front A >>of the room the instructor is talkiing about how VMS died about B >>the same time Digital did.  The company was bought by Compaq butE >>VMS was already dead.  And then it was bought by some other company D >>who's name he couldn't recall.  So I piped in that the company wasB >>HP and that VMS was still going strong.  "Oh no." he said.  "VMSG >>is dead.  Used for nothing but a few legacy (there's that word again) H >>applications.  You never see it mentioned in the trade press anymore."F >>So I said what about things like JStars?  And he said, "Yeah, JStars  >>and other legacy application." >>@ >>So what does this mean in the real world?  The instructor alsoB >>said at another point in the class that he does this class about? >>50 times a year.  Let's see, 50 classes, 20 people per class. B >>Senior NCO's, Warrant Officers, Lieutenants, Captains, Colonels.> >>And then there are the Allied Officers from other countries.D >>What was it someone said not so long ago about DOD still being one? >>of those major VMS customers?  How long do you expect that to A >>continue when the decision makers all learn about it like this? E >>(No, I am n ot going to fight with the instructor to try and change , >>his mind.  I'm just another student here.) >> >>bill >> >  > G > Next time you meet an instructor like that, ask him how many years of H > real IT experience he has had outside of his narrow little cube. Don'tD > just sit back and not say anything - that will only encourage thisH > person to continue spouting crap when he needs to be put in his place.H > At the very least ensure his Mgmt knows via feedback that his personalG > beliefs should not be preached to Customers who might take offence at  > his soapboxing.  > E > Any instructor who says controversial things like that in any class J > *about any OS* is obviously an instructor who has not spent much time inI > the real world of IT. If the instructor had spent any time in real life G > IT, they would know how controversial making statements like that can  > be.  > B > Microsoft now refers to its own Windows 2000 *and* Windows NT asI > "legacy" versions, so does this instructor think Microsoft is legacy as  > well?  > G > Let me guess, the instructor was about 25, had a pocket protector and , > wore black rimmed glasses as well - right? > 
 > ROTFL... > I > Bottom line is that like Microsoft, all platforms have legacy versions, F > but that does not make the entire platform "legacy". Mainframes haveB > legacy versions but some of their other capabilities can only beE > considered very leading edge. Same goes for Solaris, HP-UX and yes,  > OpenVMS as well.   > I > OS popularity rises and falls. A few years ago, some Customers believed G > Solaris was the way to go because that was what Oracle was saying and I > they invested lots of $'s to get their. Now these same Cust's are being B > told by Oracle "no. no .. You should go to Linux..." - so shouldH > Customers blindly follow again or should they think for themselves and. > do whats right for their companies business? > G > Next time you meet an instructor like that point him to the following < > testimonial benchmark article which just became available: > A > http://h71028.www7.hp.com/enterprise/cache/79977-0-0-0-121.html = > (click on HP ISE article on right side "HP ISE White Paper: : > International Securities Exchange scales off the chart") > 	 > Regards  >  > Kerry Main > Senior Consultant  > HP Services Canada > Voice: 613-592-4660  > Fax: 613-591-4477  > kerryDOTmainAThpDOTcom > (remove the DOT's and AT)  > & > "OpenVMS has always had integrity ..  > Now, Integrity has OpenVMS .." >  >  >  >  > K Sometimes I find that asking the simple question "what have you contributed B to the info security field?" serves to surface shallow opinions...   ------------------------------  % Date: Sat, 26 Mar 2005 05:14:59 -0500 # From: "John Smith" <a@nonymous.com> - Subject: Re: Carly's Way - article retracted? , Message-ID: <7Y-dnZDD3_y3q9jfRVn-pA@igs.net>   Bob Kaplow wrote:  > In articleJ > <OFFD9D36DA.1A18AF4B-ON85256FCD.0053EA53-85256FCD.0054D18A@cca-int.com>,! > Tym_Stegner@cca-int.com writes: D >> Technology Review, Inc. cannot vouch for the accuracy of "Carly'sF >> Way," by Michelle Delio, published online on March 4, 2005. Nor canF >> we stand by "Carly's Gone. HP Celebrates," also by Delio, publishedA >> online on February 10, 2005. We regret publishing the stories.  > C > Did this article ever make it in the printed edition? If so, what  > issue?     No, it did not.   L http://story.news.yahoo.com/news?tmpl=story&cid=562&ncid=738&e=4&u=/ap/20050 326/ap_on_hi_te/tech_reporter   ( Writer of Retracted Stories Faces Review   Fri Mar 25, 7:13 PM ET Technology - AP     " By MARK JEWELL, AP Business Writer  J BOSTON - A freelance journalist who authored two online news articles thatG Technology Review magazine retracted over questions of veracity is also : facing review of stories she wrote for other publications.  H The journalist, Michelle Delio, is a 37-year-old New York City freelance" writer specializing in technology.  H Delio said Friday that Technology Review's online version was correct inI retracting the two stories because they were based on an anonymous source " who misrepresented himself to her.  F But she defended the rest of the work she has written over her 15-year career as truthful.   K WiredNews.com, for whom Delio has long been a contributor, published a note F to readers citing this month's retractions by TechnologyReview.com andK saying it had assigned a journalism professor to review articles written by  Delio.  G The online publication has not, however, removed any of the hundreds of H stories Delio has written for it, said Wired News' managing editor Marty	 Cortinas.   G Adam Penenberg, a New York University professor who also writes a media , column for Wired News, was to do the review.  J Paul Calento, a spokesman for InfoWorld, said that publication's editorialI staff also was reviewing Delio's work. "We currently stand by Ms. Delio's  work with InfoWorld," he said.  K Delio told The Associated Press she was confident reviews would not turn up 4 further evidence of problems with her other stories.  L The retracted Technology Review articles concerned last month's dismissal of7 Carly Fiorina as chief executive of Hewlett-Packard Co.   F "I got scammed by a source who told me he worked for Hewlett-Packard,"K Delios said in a telephone interview. "He misrepresented himself to me, and  I have no idea why he did it."  J "I should have checked it out further ... I feel absolutely horrible aboutJ this. I feel horrible I gave out information that turned out to be false,"	 she said.   G Technology Review's editor-in-chief, Jason Pontin, on March 7 retracted I articles by Delio that had been posted in February and on March 4, saying L the publication could not verify the anonymous source cited in both stories.  K Pontin began reviewing the stories - which did not appear in the magazine's F print version - after HP officials complained that they were unable toK verify the existence of an employee fitting the description of the one that  Delio quoted anonymously.   * The stories were both critical of Fiorina.  K In the first one, the anonymous source was identified as an HP engineer. In G the second, he was described as a Hungarian immigrant with the initials J G.S., and as "an electrical engineer who worked as a research scientist atH the Hewlett-Packard Imaging Systems Laboratory starting in 1975 until he resigned in 2003."  H Pontin, whose magazine is affiliated with the Massachusetts Institute ofJ Technology, said he had repeatedly asked Delio to provide more information) about the source but that she was unable.   I "We regret having published the stories," Pontin said Friday. "They never H could have been published in the print magazine," which he said has more= rigorous fact-checking standards than the online publication.   I "But the hard truth of online publishing is that we trust to the accuracy ' and honesty of reporters," Pontin said.   L Delio said she had met the source that was the basis for her Hewlett-PackardL stories several years ago at a technology conference and had come to believe: what he told her about his background and knowledge of HP.  I "I know I should have checked it out further - my name was on the piece," 	 she said.    ------------------------------  # Date: Sat, 26 Mar 2005 14:48:37 GMT * From: "FredK" <fred.nospam@nospam.dec.com>- Subject: Re: Carly's Way - article retracted? 1 Message-ID: <9De1e.2329$pP2.813@news.cpqcorp.net>    > > > Delio said she had met the source that was the basis for her Hewlett-Packard F > stories several years ago at a technology conference and had come to believe < > what he told her about his background and knowledge of HP. > K > "I know I should have checked it out further - my name was on the piece,"  > she said.  >   G I've seen this a number of times over the years.  My wife was at a bank  doing F some work, and they have a consultant who claimed to have written someH SCSI and Graphics code for Tru64 - since I knew pretty much everyone whoJ was doing graphics, she asked me about him - I never heard of him.  I evenL sent mail to the guy who I knew was the actual author of the graphics code -I who also didn't know him.  Nor did anyone doing SCSI - although they said K he might have been there for a short time.  But 99.9% of the time, this guy K (who I still see occasionally post in other forums) will get away with this G unchallenged.  Maybe he had a contract in a qual group, or worked there G just long enough to do little, but know enough names to be able to make I claims that are, uh, less than the truth - but look good on a resume when   trying to land contracting jobs.   ------------------------------  + Date: Sat, 26 Mar 2005 12:25:11 +0000 (UTC) 6 From: John F <john@PleaseSeeSigForAddress.invalid.com>! Subject: decnet for linux problem , Message-ID: <d23kb7$231$1@reader1.panix.com>  = I've downloaded dnprogs-2.29.tar.gz and latd-1.23.tar.gz from : http://linux-decnet.sourceforge.net, and installed them on8 a PC running Linux/Slackware 10.1 with a 10Mbps thinwire6 card on a lan that also contains a DECserver90L+ and a6 VS4000/90 running VMS 7.3 off the new VAX hobbyist cd.7 The VS is running DECnet-Plus, with telnet and ftp also  configured.   ; Almost everything seems to work okay.  I can telnet and ftp > between the PC and the VS.  And VT's plugged into the 90L+ can> connect to the PC and to the VS.  I can also sethost to the VS0 from the PC, and set host to the PC from the VS.A      But, while copy login.com psi3"username password"::login.com B works fine in the VS to PC direction, the reverse PC to VS command8 dncopy file.txt 'vs90n2"system manager"::file.txt' fails  with a "no route to host" error.@      Moreover, I can phone vs90n2::system from the PC and answer> on the VS.  However, if I phone psi3::root from the VS, the PC< displays "system is calling you" messages on the PC, but theA phone utility says "no one is calling you" when I answer -- while 7 it continues emitting "system is calling you" messages.   3 The PC is configured with /etc/latd.conf containing       /usr/local/sbin/latcp -j 0      /usr/local/sbin/latcp -x 100 -s -a psi3star and /etc/decnet.conf containing A      executor        1.13    name    psi3star        line    eth0 +      node            1.2     name    vs90n2 ; On startup, the MAC address is changed to AA:00:04:00:0D:04 C (corresponding to 1.13), latcp -s is issued okay, and the rc.decnet  script contains       /sbin/modprobe decnet4      echo "1.13" > /proc/sys/net/decnet/node_address1      echo "psi3" > /proc/sys/net/decnet/node_name 6      echo "eth0" > /proc/sys/net/decnet/default_device8 as well as a loop to start the decnet-for-linux daemons.  3 DECnet-Plus on the VS was configured by running the 1 $ @sys$manager:net$configure basic script, with a 8 PhaseIV address of 1.2, and running $ mc decnet_register- to register all the node names and addresses. 7      One possible little inconsistency is that the full 7 Linux hostname of the PC is psi3star, which I shortened 7 to psi3 in decnet_register (and in the rc.decnet script 6 on the PC side).  Telnet and ftp on the VS call the PC3 psi3star (likewise, the 90L+ connects to psi3star), ) but set host on the VS calls the PC psi3.   2 I didn't always understand everything I was doing,. but tried to carefully configure it all as per1 instructions.  Guess I missed at least one thing. ( But, besides checking that both machines0 seem to be configured as intended,  I'm clueless) about how to further debug the situation.  Thanks for any sugegstions,  --  > John Forkosh  ( mailto:  j@f.com  where j=john and f=forkosh )   ------------------------------    Date: 26 Mar 2005 13:03:41 +0100K From: pmoreau@ath.cena.fr (Patrick MOREAU, CENA Athis, Tel: 01.69.57.68.40) > Subject: Re: DS15 RADEON 7500 hang solved (at least partially)! Message-ID: <yYmdO5kSnXcn@sinead>   : In article <42434808$0$3714$39cecf19@news.twtelecom.net>, 5 Dan Holm <danholm@googlesfreemailservice.com> writes:  [...] H > Crazy.  Just this week I bought a new monitor so I could get a little K > more real-estate than the maximum 1024x768 the previous monitor afforded  F > me, and immediately after increasing the resolution to 1280x1024 my G > DS10L with a Radeon 7500 started hanging every couple hours whenever  E > there were a lot of updates on the display.  I did a little Google  K > searching but didn't find anything, so I assumed it had to be a hardware  J > issue and called my vendor to begin the replacement procedure.  Now I'm 8 > seeing it could actually be a software/driver problem. > F > I, also, wanted to upgrade to 8.2 just to see if that would fix the D > problem, but being a mere hobbyist without access to media at the E > workplace, I would have to shell out the full price for new media.  G > Fortunately, from the reply from the DEC employee, at least it seems  4 > like this is a known issue with a fix coming soon.  - The HP guy tells me there is an interim patch L (dec-axpvms-vms732_graphics-f0227--4.pcsi) but I was not able to find it via ITRC.   M OTOH I never had such problems with the Elsa Gloria. I use it on a DS10 since K Near 5 years with very high graphic usage and no problem at all (In 16 bits  mode).     Patrick  --O =============================================================================== N pmoreau@ath.cena.fr  (CENA/SDER) ______      ___   _          (Patrick MOREAU)4 moreau_p@decus.fr (DECUS)       / /   /     / /|  /|J CENA/SDER/Athis-Mons France    / /___/     / / | / |   __   __   __   __  N BP 205                        / /         / /  |/  |  |  | |__| |__  |__| |  |N 94542 ORLY AEROGARE CEDEX    / /   ::    / /       |  |__| | \  |__  |  | |__|N http://www.ath.cena.fr/~pmoreau/              http://membres.lycos.fr/pmoreau/O ===============================================================================    ------------------------------  % Date: Sat, 26 Mar 2005 13:49:37 +0100  From: Dirk Munk <munk@home.nl>> Subject: Re: DS15 RADEON 7500 hang solved (at least partially)2 Message-ID: <d23lpg$nfk$1@news6.zwoll1.ov.home.nl>  6 Patrick MOREAU, CENA Athis, Tel: 01.69.57.68.40 wrote:  ; >In article <42434808$0$3714$39cecf19@news.twtelecom.net>,  6 >Dan Holm <danholm@googlesfreemailservice.com> writes: >[...]   >    > H >>Crazy.  Just this week I bought a new monitor so I could get a little K >>more real-estate than the maximum 1024x768 the previous monitor afforded  F >>me, and immediately after increasing the resolution to 1280x1024 my G >>DS10L with a Radeon 7500 started hanging every couple hours whenever  E >>there were a lot of updates on the display.  I did a little Google  K >>searching but didn't find anything, so I assumed it had to be a hardware  J >>issue and called my vendor to begin the replacement procedure.  Now I'm 8 >>seeing it could actually be a software/driver problem. >>F >>I, also, wanted to upgrade to 8.2 just to see if that would fix the D >>problem, but being a mere hobbyist without access to media at the E >>workplace, I would have to shell out the full price for new media.  G >>Fortunately, from the reply from the DEC employee, at least it seems  4 >>like this is a known issue with a fix coming soon. >>     >> > . >The HP guy tells me there is an interim patchM >(dec-axpvms-vms732_graphics-f0227--4.pcsi) but I was not able to find it via  >ITRC. >    > F Interim patches never are published on ITRC. These are usualy patches I for specific problems that occured with some customers. If there is such  H a patch for your problem, you can obtain it through HP software support.  D Interim patches later find their way into 'normal' patches or patch # bundels that are published on ITRC.   N >OTOH I never had such problems with the Elsa Gloria. I use it on a DS10 sinceL >Near 5 years with very high graphic usage and no problem at all (In 16 bits >mode).  >  >Patrick >-- P >===============================================================================O >pmoreau@ath.cena.fr  (CENA/SDER) ______      ___   _          (Patrick MOREAU) 5 >moreau_p@decus.fr (DECUS)       / /   /     / /|  /| K >CENA/SDER/Athis-Mons France    / /___/     / / | / |   __   __   __   __   O >BP 205                        / /         / /  |/  |  |  | |__| |__  |__| |  | O >94542 ORLY AEROGARE CEDEX    / /   ::    / /       |  |__| | \  |__  |  | |__| O >http://www.ath.cena.fr/~pmoreau/              http://membres.lycos.fr/pmoreau/ P >=============================================================================== >    >    ------------------------------  # Date: Sat, 26 Mar 2005 14:34:42 GMT * From: "FredK" <fred.nospam@nospam.dec.com>> Subject: Re: DS15 RADEON 7500 hang solved (at least partially)1 Message-ID: <6qe1e.2328$FO2.382@news.cpqcorp.net>    > J > >OTOH I never had such problems with the Elsa Gloria. I use it on a DS10 since I > >Near 5 years with very high graphic usage and no problem at all (In 16  bits	 > >mode).  > >    Apples, pears, and oranges.   G The ELSA Gloria DDX started life as a hastly written, poor quality, low  performance L piece of "code" running on a fairly slow device (3DLabs P2).  I re-wrote the DDX I after VMS acquired responsibility for it, and after some time shaking out  bugs it H has been fairly stable.  I did the primary development of the Oxygen VX1 DDX, andF once again got involved later on to help clean up and optimize the DMA version K of the code.  It too is now failry stable.  But like any complex code, both  of these> were not bug-free from the start, but became stable over time.  J The Radeon 7500 code started life as the xFree86 code (you know where this isJ headed).  It was "adapted" to a MIT based server, and extensively modified and F enhanced by the Tru64 group and ported to OpenVMS.  The code was IMHO,L more buggy than the initial ELSA code by a long shot, and unevenly optimizedK at best - and very complex as it is also does direct rendering 3D.  OpenVMS I has been working hard to try to both get the performance up to acceptable  levels, J as well and nail down some very subtle bugs in the way synchronization was done.   L We have been planning a set of patch kits for a while, but each time we comeI close to nirvana, we stumbled over additional problems.  We have supplied  someL intermediate side-built kits to customers who reported problems.  We are nowJ busy building a set of ECO kits for V7.3-1, 7.3-2 and 8.2 (IPF/Alpha) that isE still somewhat of a compromise with workarounds that fix hangs at the D expense of performance in certain circumstances (but there is a userK control that can re-enable the performance at the cost of reliabilty - just L like a PC!).  We think we may be close to solving these intractable problemsA and still get the higher performance, but we need to do some more K exhastive testing of it before we do another ECO on it (there are also some I additional slow paths in the 3D code that we are looking to fix as well).   I "Most" customers running just 2D, without the Open3D license have not had I problems, and the 2D performance is adequate.  I use the shipping version I of the DDX for my own system, and have never had it fail - so your milage 	 may vary.   K There are also bugs that are being attributed to the Radeon, that sometimes F are really not Radeon bugs - don't try to draw a *very* wide image for example,H because XPutImage in Xlib has a infinite recursion (this is fixed in the Motif I ECO for V7.3-1 (Motif V1.3-1), and is fixed in V8.2) - and will crash the  image  (not the server).    ------------------------------  % Date: Sat, 26 Mar 2005 09:34:39 -0600 / From: Clay M. Denton <denton@orison.dsserv.com> % Subject: Re: History of the VMS shark 8 Message-ID: <k60b41peokhsgp0962rdovpgs5vcj77m96@4ax.com>  U IIRC, the shark used by VMS was pulled from a royalty-free clipart database included  V with whatever vintage Corel Draw would have been current in the 1995-1996 timeframe...   Clay  R On Thu, 10 Mar 2005 11:15:34 -0500, JF Mezei <jfmezei.spamnot@teksavvy.com> wrote:  A >A while ago, I mentioned providing the VMS shark logo in various G >formats. A software problem on a mac resulted in that area of the disk + >drive to be zapped. (Thanks RealPlayer !).  > I >But I have re-begun work on this. The original artwork on the clipart CD H >is really rough, and was probably simply automatically generated from aI >analog drawing that was scanned in. (automatic contouring of images). So C >I have spent a few minutes every day redrawing it over itself with  >simpler, smoother curves. > E >I even decided to take a peek at pictures of sharks to try to see if H >that drawing was anatomically correct. This seems to be the great whiteD >shark. Perhaps fitting since that species is an endangered species.H >(just like VMS), yet it is extremely powerful and smart. based on thoseD >images, I'll have to make a few changes to the shark (proportion ofF >ventral fins, lack of anal fin, and proportion of second dorsal fin).G >This beast is a complex hydrodynamic animal. The "glitch" in the upper I >tail fin on the original artwork happens to be a real notch in the fin , E >not some artifact of the vectorizing of that picture. (Note that the H >great white is perhaps ne of the ugliest sharks, especially compared toV >the sleeker white tipped shark. But the great white has the raw power to cempensate). >  > E >So, when I am done, I plan to setup a small web page where folks can L >download the logo in various formats , and probably generate a few "icons". >  >I have 2 questions here:  > = >For the sake of documentation in that page, does anyone know I >when/where/how/whom the first use of the shark was made (in reference to  >VMS, of course) ? > C >And if one wanted to put a small icon on web pages, should it read F >"Powered by VMS", "Powered by OpenVMS" , "VMS rocks" or what ???? Any >suggestions ? >  > D >Now, considering that sharks eat and destroy stuff, wouldn't "Intel/ >inside" be truly fitting ????? :-) :-) :-) :-)  > @ >In hindsight, the shark really should have been the Alpha logo.   ------------------------------  % Date: Sat, 26 Mar 2005 04:31:05 -0500 # From: "John Smith" <a@nonymous.com> ; Subject: Re: New Customer Benchmark Brochure Info Available , Message-ID: <E76dnZZNnYN9ttjfRVn-vA@igs.net>   Main, Kerry wrote: > All, > ? > The readers of this list might be interested in the following D > HP-ISE-OM Technlogies Financial Services brochure that just became > available: > A > http://h71028.www7.hp.com/enterprise/cache/79977-0-0-0-121.html = > (click on HP ISE article on right side "HP ISE White Paper: : > International Securities Exchange scales off the chart") >  > Extract from the attached:G > "When the results of the benchmark began to come in, there was a long C > moment of stunned silence in the benchmark center; the ISE system E > configuration was able to scale to 1 million quotes per second. The F > benchmark results had important implications for ISE in terms of itsD > ability to handle the steadily increasing volume levels in optionsG > trading transactions that have marked ISE's phenomenal success in the  > finance industry." >  > [snip...]  > ? > All of this with ultra-high security and no viruses .. what a 
 > concept....     F It *would* indeed be a concept IF it were advertised in WSJ, Financial> Times, The Economist, Business Week, Forture, Forbes, Barrons,H Computerworld, Information Week, eWeek, hell...even PC Magazine. Without' that, it's just preaching to the choir.   I Why does Blatz & Co. even waste the money producing this crap if it isn't H going to be seen beyond the magic 660 accounts.....I have customers withK 60,000+ employees where I can't even mention VMS because they don't believe H HP has any committment to it because HP don't advertise it, and that theJ 3rd-party application portfolio is pretty thin, and because a lot of 'openI source' doesn't have a ready VMS version. I guess the University of Turin J will single-handedly take care of that....correct? or will they be gettingI help from other academic institutions with 1 or 2 students porting one or : two modules of some 'open source' as an academic exercise?  K You know what would be worth crowing about....when HP sells in one year the L same number of Wintel servers it sells in one week. But that'll never happen without advertising for VMS.   --F OpenVMS - The never advertised operating system with the dwindling ISV base.    ------------------------------  % Date: Sat, 26 Mar 2005 09:44:11 +0100  From: Dirk Munk <munk@home.nl>, Subject: Re: Question on DCL f<dollar>string2 Message-ID: <d237ct$rq0$1@news6.zwoll1.ov.home.nl>  P All these examples are not the best way to accomplish the desired result, since 0 you need special coding for the months 10 to 12.  H For this purpose you should use the F$Fao lexical, like in this example:   $! $ last=2 $! $ last =  F$Fao("!2ZL",last) $! $ show symbol last    LAST = "02" $! $! ========================= $!	 $ last=12  $! $ last =  F$Fao("!2ZL",last) $! $ show symbol last    LAST = "12" $! $! ========================= $!	 $ last=12  $! $ last =  F$Fao("!4ZL",last) $! $ show symbol last    LAST = "0012" $! $ exit  L The F$Fao("!#ZL",<symbol>) lexical will take the numeric symbol <symbol> as P input, and return a ascii string of # bytes wide with added extra zeroes to the  left if necessary.  Q The problem with this lexical is that there are not many examples in the manual,  K which makes it a bit hard to understand how to use it. However it is a lot  % easier than it looks at first glance.	     norm.raphael@metso.com wrote:e > 3 > I found this in a DCL procedure (last is actually 6 > calculated as a month-related single-digit integer): > 
 > $ last=2 > $ last = f$string("0"'last') > $ sho sym last >   LAST = "02"  > $!===n! > Now I would have expected this:  > 
 > $ last=2 > $ last="0''last'"r > $ sho sym last >   LAST = "02"e > $!===  > or maybe this: > 
 > $ last=2 > $ last = f$string("0''last'")t > $ sho sym last > $!  LAST = "02"n > ===d* > but what exactly is the first one doing?- > Is there any advantage or difference in the  > result from them?  >  > 6 > $HELP LEXICALS  F$STRING    Argument      expression > < >          The integer or string expression to be evaluated. > F >          If you specify an integer expression, the F$STRING functionF >          evaluates the expression, converts the resulting integer toD >          a string, and returns the result. If you specify a stringI >          expression, the F$STRING function evaluates the expression and  >          returns the result. > H >          When converting an integer to a string, the F$STRING functionD >          uses decimal representation and omits leading zeros. WhenH >          converting a negative integer, the F$STRING function places aL >          minus sign at the beginning string representation of the integer.   ------------------------------    Date: 26 Mar 2005 10:26:58 -0800( From: "Hein" <hein_news@eps.zko.dec.com>, Subject: Re: Question on DCL f<dollar>stringB Message-ID: <1111861618.202524.63580@l41g2000cwc.googlegroups.com>   Dirk Munk wrote:C > All these examples are not the best way to accomplish the desireds
 result, sinceo2 > you need special coding for the months 10 to 12. >>A > For this purpose you should use the F$Fao lexical, like in thise example:   And you should.l; But if you like to be 'cute' and obscure, you can also use:p   $ last=2 $ last=f$ext(1,2,100+last) $ show symb last
   LAST = "02"    gag! :-)    Hein.t   ------------------------------  % Date: Sat, 26 Mar 2005 07:25:50 -0800V# From: "Tom Linden" <tom@kednos.com>  Subject: shadow minicopy( Message-ID: <opsn83tczvzgicya@hyrrokkin>  < Have three shadow sets in a cluster containing nodes running? 7.3, 7.3-1, 7.3-2 and 8.2 on alpha and VAX.  Had to replace theh? CD drives in one 7.3 AXP and one 7.3-1.  The shadow sets are on < a shared scsi bus with those two and yet a third 7.3-2 node.D The shadow sets are each 74GB.  A merge operation was thus initiatedB One of the sets hosts hosts WASD, MX HGFTP and QUEUE Manager. ThisH one took 7 days to merge!  (the sets are in a BA356 so only 40MB/sec Tx)E the others completed in two days.  So I thought I would implement the,	 minicopy.v  / Upon startup, the sets are currently mounted asa
 $     MOUNT   J DSA0:/CLUSTER/NOASSIST/INCLUDE/NOCOPY/SHADOW=($42$DKA1200:,$42$DKA1300:)   COMMONI and at shutdown a command procedure is called to dismount the disks which I tests for and skips system disk this is called from syshutdwn.com which  . exemptss shadow masters, i.e.  0 $       if f$getdvi(device,"shdw_master") then -          goto loop  E So in the the dismount procedure after determining this_disk we issueo $	dismount 'this_disk'    H So here is the question, to implement minicopy is the following correct?  E $     MOUNT DSA0:/CLUSTER/NOASSIST/INCLUDE/POLICY=MINICOPY=OPTIONAL -g+ 	/SHADOW=($42$DKA1200:,$42$DKA1300:) COMMON-   and for dismount  + $       If f$getdvi(this_disk,"shdw_member)  $       then= $               dismount/policy=minicopy=optional 'this_disk'o $       else$ $               dismount 'this_disk'
 $       endifk  J I ask because I note a posting by Ken Fairfield, (reproduced in the .com   file)U "n0 $ ! From: Ken Fairfield <My.Full.Name@intel.com> $ ! Newsgroups: comp.os.vms 1 $ ! Subject: Re: Creating a wide area VMS Clustert) $ ! Date: Thu, 18 Sep 2003 12:00:24 -0700t# $ ! Organization: Intel Corporation - $ ! Message-ID: <3F6A00C8.7E0EEAF7@intel.com>t $ !n; $ !         I've said this before in the newsgroup and I'lle8 $ ! say it again: the ONLY SAFE WAY to mount shadow sets> $ ! (unassisted during startup) is with /INCLUDE/NOCOPY.  ThisB $ ! will assure that you don't overwrite a good member of a shadowD $ ! set with a out-of-date one that, for any of a number of reasons,C $ ! might otherwise be used as the shadow master during a copy (notn $ ! merge) initiated on mount. "-  K which may predate the appearance of minicopy.  I couldn't find in the docs, ; but isn't /NOCOPY exclusive with /POLICY=MINICOPY=OPTIONAL?:  I Finally, since these sets are mounted on all the nodes, I guess they haveiF to be dismounted first from all and then mount with minicopy to create. the bit maps, one at a time.  Is that correct?   TIAt Tom>   ------------------------------    Date: 26 Mar 2005 07:47:24 -0800 From: Ron_Grossi_038@yahoo.com  Subject: The Greatest News Ever!C Message-ID: <1111852044.684358.133740@f14g2000cwb.googlegroups.com>R  7 http://www.jcil.blogspot.com << The Greatest News Ever!t   ------------------------------    Date: 26 Mar 2005 03:55:43 -0800" From: chris_doran@postmaster.co.uk Subject: Re: VAX 4000 batteryGC Message-ID: <1111838143.768201.196380@f14g2000cwb.googlegroups.com>>   JF Mezei wrote:l > Chris wrote:G > > that seem to have similar characteristics and connector.  Not beinge much of>D > > an electrical type, what would be the worst thing to happen if I replacedF > > the 180mAh pack with one of same voltage, but rated at say 320mAh? > > Combustion? Smell of Death?0   Only the voltage matters.   C > A long time ago, I replaced my All Mighty Microvax II's batteries  with 3B > AAA purchased from Radio Shack which I soldered in series to the > original connector.a  G You were luckier than I have been with soldering nicads. Whenever I trydG it, one or more of them dies shortly afterwise. I guess they just can'teG take the heat. Low temperature solder and/or cooling them quickly afterbE the act is probably required. It's safer to just buy a ready-solderednE battery of the right voltage and change to the connector from the oldsG battery (getting it the right way round!). Wireless 'phones use(d?) thesD same size battery and over here are readily available on the surplus market.t  2 >  In a month or two, my all mighty MV II turns 18E > (which means I technically can start storing porn on it and feed ith
 > alchool :-)  >eF > Inside the plastic wrapper, you'll find conventional AAA or AA nicad
 batteries.   Agreed.>   Chrisn   ------------------------------   End of INFO-VAX 2005.170 ************************