1 INFO-VAX	Sat, 14 Aug 2004	Volume 2004 : Issue 448       Contents:0 RE: How to block many IP#s with Bad-Client list?+ Re: HP - Other heads on the chopping block? + Re: HP servers management shakeup happening + Re: HP servers management shakeup happening + Re: HP servers management shakeup happening + Re: HP servers management shakeup happening + Re: HP servers management shakeup happening + Re: HP servers management shakeup happening + Re: HP servers management shakeup happening # Re: Looking for VMS experts opinion # Re: Looking for VMS experts opinion # Re: Looking for VMS experts opinion  Re: MPlayer is a DVD player 0 Re: NONSHRADR and NONRES messages at end of boot0 Re: NONSHRADR and NONRES messages at end of boot' Re: Rejecting network access to service  Re: Samba on OpenVMS' TCP Server  SYSTEM-F-DUPLNAM on restart : Unknown OPCOM message: "clm privilege violation" More info  F ----------------------------------------------------------------------  % Date: Fri, 13 Aug 2004 16:56:53 -0700 # From: "Tom Linden" <tom@kednos.com> 9 Subject: RE: How to block many IP#s with Bad-Client list? 9 Message-ID: <NDEMLKKEBOIFBMJLCECIKEJFDKAA.tom@kednos.com>    < -----Original Message-----3 < From: Lawrence Bleau [mailto:bleau@UMTOF.UMD.EDU] ( < Sent: Friday, August 13, 2004 10:09 AM < To: Info-VAX@Mvb.Saic.Com 7 < Subject: How to block many IP#s with Bad-Client list?  <  < C < Hello, I have a question about an anti-spam feature of TCPIP: the L < Bad-Client list.  Here's my version: TCPIP V5.4 - ECO 1 on OpenVMS V7.3-2. < I < We are blocking a lot of sites because we're getting so much spam.  The I < Bad-Client list is quite long.  Btw, I noticed that it has to be all on K < one line, else subsequent lines are ignored.  Maybe this can get fixed in 
 < the future.  < L < Anyway, the problem is that, once the Bad-Client line gets over 512 chars,K < it ignores that line altogether, and treats it like we don't have any bad  < clients declared.  < 3 < Does anyone know of a fix or workaround for this?    Yes, switch to MX5.3   <  < Lawrence Bleau < University of Maryland$ < Physics Dept., Space Physics Group < 301-405-6223 < bleau@umtof.umd.edu  <  < --- ( < Incoming mail is certified Virus Free.< < Checked by AVG anti-virus system (http://www.grisoft.com).A < Version: 6.0.735 / Virus Database: 489 - Release Date: 8/6/2004  <  --- & Outgoing mail is certified Virus Free.: Checked by AVG anti-virus system (http://www.grisoft.com).? Version: 6.0.735 / Virus Database: 489 - Release Date: 8/6/2004    ------------------------------  % Date: Fri, 13 Aug 2004 18:46:50 -0400 % From: "Chris" <mc.moore@sympatico.ca> 4 Subject: Re: HP - Other heads on the chopping block?; Message-ID: <HxbTc.33144$Mq1.1922890@news20.bellglobal.com>   > "Michael Austin" <maustin@firstdbasource.com> wrote in message0 news:FX3Tc.7$Rx5.2@newssvr22.news.prodigy.com... > John Smith wrote:  >  > > I http://www.informationweek.com/story/showArticle.jhtml?articleID=28700191  > >  > >  > > 2 > > HP Shakes Up Execs After Disappointing Results > >  > > Aug. 12, 2004  > > K > > Three key executives in the company's top enterprise server and storage  unitJ > > were replaced after the division posted a $208 million operating loss. > > By Darrell Dunn  > >  > >  > > J > > Hewlett-Packard fired three top managers Thursday after reporting that its K > > Enterprise Servers and Storage Group experienced a sales decline in the  > > third quarter. > > L > > Following the earnings announcement, chairman and CEO Carly Fiorina saidD > > Mike Winkler will replace Peter Blackmore as executive VP of the CustomerF > > Solutions Group; Jack Novia will replace Jim Milton as the group's	 senior VP I > > and managing director for the Americas region; and Bernard Meric will L > > replace Kasper Rorsted as the group's senior VP and managing director of > > Europe.  > > L > > Winkler has served as chief marketing officer and will retain that role.J > > Novia was senior VP and general manager of the HP Technology SolutionsH > > Group. Meric was senior VP of the Imaging and Printing Group for the Europe, K > > Middle East, and Africa region. An HP spokesman said he wasn't aware of  any  > > other planned changes. > > F > > "It's pretty clear that heads will roll," says Jonathon Eunice, an analyst @ > > with Illuminata. "If you're a customer with certain personal
 relationships L > > with some of the people inside that organization, you'd better brace forL > > change. Anyone with responsibility within that organization is at risk." > > K > > Executives on the hot seat could include Ann Livermore, an executive VP  who F > > earlier this year was placed in charge of the Technology Solutions Group,L > > which includes Enterprise Servers and Storage, and Bob Shultz, senior VP and J > > general manager of the Network Storage Solutions business unit, Eunice says.  > > D > > "Execution issues cost us, and we are therefore making immediate
 management, > > changes," Fiorina said in the statement. > > C > > Solid results by the company overall "were overshadowed" by the 
 EnterpriseK > > Servers and Storage Group's performance, where revenue was down 5% year  toK > > year and down about 15% compared with the second quarter, she said. The E > > segment suffered an operating loss of $208 million, after revenue  declinesL > > of 8% year over year in its Business Critical Server business and 15% in its  > > storage business.  > > F > > Fiorina pointed to three issues that led to problems, resulting inG > > shortfalls in revenue of about $400 million and operating profit of  about I > > $270 million. The company "executed poorly" on the migration to a new G > > order-processing and supply-chain system, which led to missing some  sales I > > opportunities. The problems also required the company to take special J > > measures to ensure deliveries, including fulfilling some direct orders byK > > its channel partners and expediting orders with air shipment, which led  to > > erosion of gross margins.  > > L > > Second, there were channel-management issues in Europe, including overlyJ > > aggressive discounting and a transition to centralized claims process. The ; > > channel claims process has been resolved, Fiorina said.  > > J > > The company also experienced declines in average selling prices in its > > storage business.  > > K > > New introductions within HP's storage business in May, as well as those L > > planned for September, are expected to strengthen the company's position in  > > that business, Fiorina said. > > E > > Overall, the Enterprise Servers and Storage unit should return to 2 > > profitability in the fourth quarter, she said. > > L > > The company reported earnings of $586 million, or 19 cents per share, onH > > revenue of $18.9 billion in the quarter ended July 31. That compares withH > > earnings of $884 million, or 29 cents per share, on revenue of $20.1 billion J > > in the previous quarter, and earnings of $297 million, or 10 cents perB > > share, on revenue of $17.3 billion in same quarter a year ago. > >  > >  >  >  > from the Interex clip: > H > "Enterprise Servers and Storage reported revenue of $3.4 billion, down fiveK > percent from the same quarter last year. Business Critical Server revenue F > dropped eight percent to $828 million; Alpha fell by 32 percent, and NonStop G > declined by 25 percent. UNIX revenue, however, rose eight percent and  Industry- > Standard Server revenue grew two percent. "  >  >  > H > it is little wonder that Alpha slipped 32% when there was virtually no	 marketing ) > of the products... what do they expect?  >   K In a quote from the James Bond archive, "No, Mr. Bond, I expect you to DIE"      > --   > Michael Austin.  > Consultant - Available. B > Donations welcomed. Http://www.firstdbasource.com/donations.html > :)   ------------------------------  % Date: Fri, 13 Aug 2004 17:50:17 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> 4 Subject: Re: HP servers management shakeup happening, Message-ID: <411D3797.7944F7D0@teksavvy.com>   Bob Koehler wrote:H >    Many of us looking at new VMS systems are looking at IA64.  We have4 >    no trouble understanding a drop in Alpha sales.  I Many more are not looking at IA64 because they can't be bothered with the L conversion, especially of they feel that VMS is no longer viable in the longI term. In such cases, sticking with Alpha systems is the logical solution.   L What is important to note and monitor is the percentage of enterprise serverJ reevenus which are IA64 based. Last I had heard (I think it was may), IA64" accounted for only 16% of revenus.  N So a 35% drop in Alpha, with an overall reduction in total enterprise systems,H means that IA64 is not taking up the slack from the drop in Alpha sales.   ------------------------------  % Date: Fri, 13 Aug 2004 18:11:16 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> 4 Subject: Re: HP servers management shakeup happening, Message-ID: <411D3C80.5925AB34@teksavvy.com>  % There are 2 key points to this event:   K When a CEO, instead of fixing problems,  starts to play musical chairs as a L knee jerk reaction to the announcement of disapointing results, it generallyL means that the company is going down. The goal of such reorgs is to fool theH wall street casino analysts into thinking the CEO is strong, asserts her2 leadership role and knows how to fix the problems.  H Secondly, from a VMS perspective, it is not good news when a guy such asN Winkler who is known to be windows centric and thus against VMS is promoted to! gain even more rtesponsabilities.   K If Marcello is the only one who is mildly pro VMS in the place, his lack of " promotion isn't good news for VMS.  I There should have been only one change at HP: carly.  She pushed for IA64 M instead of aborting that failed chip before Merced was released. As a result, K HP's server linup is in a mess and continues to be in a mess due to lack of N confidence in the future of that chip, and the premature death of the previous= proven chips that still pack more punch than that IA64 thing.   I It is no surprise that their enterprise division is faltering. Either the N number of systems sold goes down, or HP must give hefty discounts to customersV to convince them to risk going to that IA64 thing. Either way, it means lower profits.  L Palmer killed Digital by sabotaging his profit generator. HP will be able toN survive longer since it real profit centre are ink cartridges. So it will takeN much longer for HP to fail, unless of course shareholders start to demand that! the printer division be spun off.    ------------------------------  % Date: Fri, 13 Aug 2004 19:40:49 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> 4 Subject: Re: HP servers management shakeup happening, Message-ID: <411D5178.37E83273@teksavvy.com>   Paul Sture wrote: G > Yeowch! 6 weeks production downtime! That's inexcusable for a company I > selling high availablity solutions. I don't think much of the planned 3  > weeks downtime either.  M After 9-11, Bombardier claimed it had not lost any sales of its regional jets J and that production was rolling along. Airbus cancelled planned productionL increases. Boeing immediately announced cutbacks and 30,000 layoffs. (BoeingI had already upped production rates, Airbus hadn't yet, which explains the  different reactions).     M What Bombardier did is to cause one union to strike, shutting down production I for a few weeks.  How convenient. Blame lower yearly output on the union, G instead of admiting that your customers have cancelled and/or postponed M deliveries. But you can only do this for so long, and eventually, the cat got J out of the bag, the president was sacked, major re-org, and Bombardier wasH short of cash and it had to sell off its original business (skidoos) and/ layoff lots of people. Its stock went way down.   N My take on this SAP thing at HP is that it was a similar ploy to hide the factN that HP's production rates were too optimistic and this problem allowed a drop& of production by blaming someone else.  M However, SAP's costs notwidthstanding, HP's now public implementation failure J of SAP, is a huge stain on its consulting reputation. 3 weeks "planned" isN unacceptable to begin with.  It also reflects poorly on HP's ability to chooseM the right product. Seems to be that they chose SAP because it is "trendy" and 1 it backfired with such an implementation failure.   N Offline for 6 weeks is absolutely silly. You'd think that they would have keptB the old system up and running until the SAP one was really ready ?   ------------------------------  % Date: Fri, 13 Aug 2004 22:53:19 -0400 * From: "Bill Todd" <billtodd@metrocast.net>4 Subject: Re: HP servers management shakeup happening2 Message-ID: <nLGdnbpmx4TK44DcRVn-qQ@metrocast.net>  7 "Paul Sture" <nospam@sture.homeip.net> wrote in message $ news:2o3m0uF69bvlU1@uni-berlin.de... > Bill Todd wrote: > ? > > http://www.theregister.co.uk/2004/08/12/hp_blackmore_fired/  > >  > > : > > http://www.byteandswitch.com/document.asp?doc_id=57677 > >  > G > "Fiorena blamed the problems in part on the divisions migration to a I > new SAP system that shut down production for six weeks instead of three F > weeks as planned. She also cited problems with channel management inH > Europe. But she acknowledged that HPs storage products aren't meeting > expectations." > G > Yeowch! 6 weeks production downtime! That's inexcusable for a company I > selling high availablity solutions. I don't think much of the planned 3  > weeks downtime either. > J > Perhaps they should have employed some of their customers as consultants > for this.   D Well, this shaky storage situation is not exactly unique to the last- quarter - see this article from 3 months ago:   L http://searchstorage.techtarget.com/originalContent/0,289142,sid5_gci966137, 00.html    - bill   ------------------------------  % Date: Fri, 13 Aug 2004 23:03:38 -0400 ( From: David Froble <davef@tsoft-inc.com>4 Subject: Re: HP servers management shakeup happening, Message-ID: <411D810A.6090605@tsoft-inc.com>   JF Mezei wrote:    > Bob Koehler wrote: > H >>   Many of us looking at new VMS systems are looking at IA64.  We have4 >>   no trouble understanding a drop in Alpha sales. >> > K > Many more are not looking at IA64 because they can't be bothered with the N > conversion, especially of they feel that VMS is no longer viable in the longK > term. In such cases, sticking with Alpha systems is the logical solution.     Q We're both on the same side of this issue, but the reality is that Alpha is dead  P and if one needs to  install any new VMS systems in the next several years, the Q itanic is the only game in town.  So just hope that the piece of shit is halfway  N usable and that Intel themselves doesn't sink it as part of their response to  being flogged by AMD.     N > What is important to note and monitor is the percentage of enterprise serverL > reevenus which are IA64 based. Last I had heard (I think it was may), IA64$ > accounted for only 16% of revenus.    % I'd be surprised if it was that high.     P > So a 35% drop in Alpha, with an overall reduction in total enterprise systems,J > means that IA64 is not taking up the slack from the drop in Alpha sales.    M Did you ever have any illusion that it would do so?  The idiots burned their  Q bridges with the knowledge that they would lose some portion of their customers.  Q   They didn't care.  Hell of a way to run a company, but that's what we're stuck   with.      Dave     --  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, 13 Aug 2004 23:24:56 -0400 ( From: David Froble <davef@tsoft-inc.com>4 Subject: Re: HP servers management shakeup happening, Message-ID: <411D8608.4020109@tsoft-inc.com>   JF Mezei wrote:   ' > There are 2 key points to this event:  > M > When a CEO, instead of fixing problems,  starts to play musical chairs as a N > knee jerk reaction to the announcement of disapointing results, it generallyN > means that the company is going down. The goal of such reorgs is to fool theJ > wall street casino analysts into thinking the CEO is strong, asserts her4 > leadership role and knows how to fix the problems.    J You must be remembering the re-orgs at DEC when things weren't going well.    J > Secondly, from a VMS perspective, it is not good news when a guy such asP > Winkler who is known to be windows centric and thus against VMS is promoted to# > gain even more rtesponsabilities.      Depends, see below.     M > If Marcello is the only one who is mildly pro VMS in the place, his lack of $ > promotion isn't good news for VMS.    L Maybe we don't want Rich to get too high.  At some point, you become cannon M fodder to be blamed when the next quarter also is disappointing.  Now, if we  L only have to put up with Winkler for another quarter, I got no problem with 
 that.  :-)    K > There should have been only one change at HP: carly.  She pushed for IA64 O > instead of aborting that failed chip before Merced was released. As a result, M > HP's server linup is in a mess and continues to be in a mess due to lack of P > confidence in the future of that chip, and the premature death of the previous? > proven chips that still pack more punch than that IA64 thing.     Q For an unbiased outside observer, HP must appear to be a circus, made up only of  Q clowns.  Killing off good products in favor of vaporware that already has a poor  N track record makes no sense.  I can understand some having 'hopes' for IA-64. M But confidence, no way.  People make buying decisions based upon confidence.  L Looking at it's entire lifespan, only those with a vested interest in IA-64 Q could claim to have confidence, and I think most of them are lying to themselves.     K > It is no surprise that their enterprise division is faltering. Either the P > number of systems sold goes down, or HP must give hefty discounts to customersX > to convince them to risk going to that IA64 thing. Either way, it means lower profits.    Q You'll always sway some beancounters by making the numbers look too good to pass  N up.  Problem is, how often are beancounters concerned with something actually  working?    N > Palmer killed Digital by sabotaging his profit generator. HP will be able toP > survive longer since it real profit centre are ink cartridges. So it will takeP > much longer for HP to fail, unless of course shareholders start to demand that# > the printer division be spun off.   L If it wasn't for printing, and we're talking ink cartridges as you suggest, H after some of the management blunders HP would be on the rocks.  IBM is M confidence with a capitol 'C', and they're not doing anything to change that  Q perception.  I think that Sun porting Solaris to Power just might be hugh in the  N future.  The Sun customer base (existing users) is large, and presenting them L with the capability of using the worlds fastest CPU just might be a winner. P That's the type of action that instills CONFIDENCE in buyers/customers, even if Q they don't need Power and continue buying SPARC.  Killing a product that current  ! customers have depended on isn't.    Dave   --  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, 13 Aug 2004 23:28:41 -0400 ( From: David Froble <davef@tsoft-inc.com>4 Subject: Re: HP servers management shakeup happening, Message-ID: <411D86E9.9030507@tsoft-inc.com>   JF Mezei wrote:    > Paul Sture wrote:  > G >>Yeowch! 6 weeks production downtime! That's inexcusable for a company I >>selling high availablity solutions. I don't think much of the planned 3  >>weeks downtime either. >> > O > After 9-11, Bombardier claimed it had not lost any sales of its regional jets L > and that production was rolling along. Airbus cancelled planned productionN > increases. Boeing immediately announced cutbacks and 30,000 layoffs. (BoeingK > had already upped production rates, Airbus hadn't yet, which explains the  > different reactions).  >  > O > What Bombardier did is to cause one union to strike, shutting down production K > for a few weeks.  How convenient. Blame lower yearly output on the union, I > instead of admiting that your customers have cancelled and/or postponed O > deliveries. But you can only do this for so long, and eventually, the cat got L > out of the bag, the president was sacked, major re-org, and Bombardier wasJ > short of cash and it had to sell off its original business (skidoos) and1 > layoff lots of people. Its stock went way down.  > P > My take on this SAP thing at HP is that it was a similar ploy to hide the factP > that HP's production rates were too optimistic and this problem allowed a drop( > of production by blaming someone else. > O > However, SAP's costs notwidthstanding, HP's now public implementation failure L > of SAP, is a huge stain on its consulting reputation. 3 weeks "planned" isP > unacceptable to begin with.  It also reflects poorly on HP's ability to chooseO > the right product. Seems to be that they chose SAP because it is "trendy" and 3 > it backfired with such an implementation failure.  > P > Offline for 6 weeks is absolutely silly. You'd think that they would have keptD > the old system up and running until the SAP one was really ready ? >   P HP wants to grow the services business, (read that as consulting and such).  Is Q this the company that you'd choose to run your SAP implementation?  Well, maybe,  Q since choosing SAP is a bad decision in the first place, so you might as well be   consistant.    Dave   --  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: 13 Aug 2004 14:47:16 -0500. From: frey@encompasserve.org (Lurker at Large), Subject: Re: Looking for VMS experts opinion3 Message-ID: <CBQ6rClxutpm@eisner.encompasserve.org>   a In article <44d1cf8d.0408130811.555b4bbe@posting.google.com>, a.samorezov@volcanomail.com writes:  > Dear VMS experts,  > + > Thus, may I ask for your kind assistance. ) > Would you send me web-links to positive 6 > experience explanation and successful stories of the# > VMS implementation known for you.   O Sure, here's mine.  This response isn't approved by or known to my management,  I it's only my experience and point of view.  For that reason I have to be  ) nonspecific about company names and such.   P I work for a company that sells software for E911 dispatching in the U.S.A.  As I you know, E911 dispatching is a 24x7, 365 day a year, critical, real-time  application.  P The software was originally developed on DEC's PDP machines using RSTS.  It was O later ported to Vaxes running VMS.  We still have customers on Vaxes, although  P most have been ported to Alphas - still using VMS.  We're beginning to port our K software to Itanium - still using VMS.  At the height of our business, the  F early 1980's, we had something like 80% market share and a tremendous  reputation with our customers.  P For about 10 years between the 1980's and 1990's our management decided that VMSO was archaic and developed a Windows/unix version of our software.  Even though  L we continued to support our VMS customers, management dictated that we stop M selling the VMS version to new customers.  We had terrible problems with the  P Windows version of our software (for various reasons that I won't go into here) O and it got us a huge black eye with customers and lost us alot of market share.   O This past year, on the verge of calling it quits, management decided to try to  P start selling the VMS product to new customers as a last-ditch effort to regain P our lost market share and stay in business.  We dumped the windows/unix version G (although it's our policy to support existing customers, no matter the  
 platform).  D I was on the teams that did our latest (and first two) new customer N installations of the software and can report that we didn't have the problems M that our windows software installations had.  Both projects "went live" with  P zero downtime and only minor issues.  Both continue to run with zero downtime.  O All of our customers are encouraged and we have new customers again looking at  O us as a potential vendor.  Management has noticed this, and although it hasn't  H been decided (or announced at least) yet, I'm sure we'll continue to do % business and regain our market share.   K There are many reasons why the VMS version is better than the Windows/unix  O version, and I won't use this followup to blast the other two platforms.  It's  6 my opinion that the VMS version is unbeatable because:  - * strong built-in security and data integrity 2 * good clustering and strong file locking features * easy to program     - Sharon, lurker at Large   ------------------------------  # Date: Sat, 14 Aug 2004 02:56:46 GMT 1 From: Michael Austin <maustin@firstdbasource.com> , Subject: Re: Looking for VMS experts opinion: Message-ID: <ObfTc.165$oc1.103@newssvr22.news.prodigy.com>   Lurker at Large wrote: <snip>  Q > All of our customers are encouraged and we have new customers again looking at  Q > us as a potential vendor.  Management has noticed this, and although it hasn't  J > been decided (or announced at least) yet, I'm sure we'll continue to do ' > business and regain our market share.  > M > There are many reasons why the VMS version is better than the Windows/unix  Q > version, and I won't use this followup to blast the other two platforms.  It's  8 > my opinion that the VMS version is unbeatable because: > / > * strong built-in security and data integrity 4 > * good clustering and strong file locking features > * easy to program  >  >  - Sharon, lurker at Large   HP Are you listening????   --   Michael Austin.  Consultant - Available. @ Donations welcomed. Http://www.firstdbasource.com/donations.html :)   ------------------------------  % Date: Fri, 13 Aug 2004 22:27:17 -0600 " From: GreyCloud <mist@cumulus.com>, Subject: Re: Looking for VMS experts opinion0 Message-ID: <DbadnUomlcSpCYDcRVn-uA@bresnan.com>   Lurker at Large wrote:  c > In article <44d1cf8d.0408130811.555b4bbe@posting.google.com>, a.samorezov@volcanomail.com writes:  >  >>Dear VMS experts,  >>+ >>Thus, may I ask for your kind assistance. ) >>Would you send me web-links to positive 6 >>experience explanation and successful stories of the# >>VMS implementation known for you.  >  > Q > Sure, here's mine.  This response isn't approved by or known to my management,  K > it's only my experience and point of view.  For that reason I have to be  + > nonspecific about company names and such.  > R > I work for a company that sells software for E911 dispatching in the U.S.A.  As K > you know, E911 dispatching is a 24x7, 365 day a year, critical, real-time  > application. > R > The software was originally developed on DEC's PDP machines using RSTS.  It was Q > later ported to Vaxes running VMS.  We still have customers on Vaxes, although  R > most have been ported to Alphas - still using VMS.  We're beginning to port our M > software to Itanium - still using VMS.  At the height of our business, the  H > early 1980's, we had something like 80% market share and a tremendous   > reputation with our customers. > R > For about 10 years between the 1980's and 1990's our management decided that VMSQ > was archaic and developed a Windows/unix version of our software.  Even though  N > we continued to support our VMS customers, management dictated that we stop O > selling the VMS version to new customers.  We had terrible problems with the  R > Windows version of our software (for various reasons that I won't go into here) Q > and it got us a huge black eye with customers and lost us alot of market share.  > Q > This past year, on the verge of calling it quits, management decided to try to  R > start selling the VMS product to new customers as a last-ditch effort to regain R > our lost market share and stay in business.  We dumped the windows/unix version I > (although it's our policy to support existing customers, no matter the   > platform). > F > I was on the teams that did our latest (and first two) new customer P > installations of the software and can report that we didn't have the problems O > that our windows software installations had.  Both projects "went live" with  R > zero downtime and only minor issues.  Both continue to run with zero downtime.  Q > All of our customers are encouraged and we have new customers again looking at  Q > us as a potential vendor.  Management has noticed this, and although it hasn't  J > been decided (or announced at least) yet, I'm sure we'll continue to do ' > business and regain our market share.  > M > There are many reasons why the VMS version is better than the Windows/unix  Q > version, and I won't use this followup to blast the other two platforms.  It's  8 > my opinion that the VMS version is unbeatable because: > / > * strong built-in security and data integrity 4 > * good clustering and strong file locking features > * easy to program  >   H The easy to program part is the best part.  I've found that the old DEC E docs were the best in the industry in the 1980's and helped a lot in  F understanding their APIs.  Things worked as advertised and I found no , surprises with VMS or the development tools.   --  ! ---------------------------------  The Golden Years Sux.    ------------------------------  + Date: Sat, 14 Aug 2004 00:05:55 +0000 (UTC) , From: lewis@PROBE.MITRE.ORG (Keith A. Lewis)$ Subject: Re: MPlayer is a DVD player. Message-ID: <cfjl13$l7e$1@newslocal.mitre.org>   Nigel Barker <nigel@hp.com> writes in article <k3roh0ttvngtuljsd0dvl90isqc4i5pjt8@4ax.com> dated Fri, 13 Aug 2004 07:25:42 GMT: D >On Thu, 12 Aug 2004 22:46:29 +0200, Dirk Munk <munk@home.nl> wrote: > P >>I have a DS10 with a Radeon card. I suppose I need some kind of sound card as S >>well? I tried to buy one some time ago, but it seems the supported sound card is  . >>so ancient that it belongs in a museum :-) . > O >I bought an Ensoniq Audio PCI soundcard on Ebay for 10 Euros. Works great. You Q >need to check that the card is the version that has a large chip labelled either  >ES1371/ES1373 or CT5880.   E So ES1370 won't work?  There seem to be a lot of those available.  :(   I Does anybody know how many sound cards you can put in a 500au?  I've been K using the unsupported built-in audio, but it restricts me to 1-in and 1-out B at a time (stereo of course), same sampling frequency, and there'sJ noticeable crosstalk between the in and the out.  I'd love to get a couple> of cheap cards so I could do 2-in and 1-out with no bleedover.  0 --Keith Lewis              klewis {at} mitre.org> The above may not (yet) represent the opinions of my employer.   ------------------------------  % Date: Fri, 13 Aug 2004 13:36:24 -0400 ( From: David Froble <davef@tsoft-inc.com>9 Subject: Re: NONSHRADR and NONRES messages at end of boot , Message-ID: <411CFC18.6040205@tsoft-inc.com>  	 JG wrote:   H > My 7.2-2 Alphas always output these messages on the console at the endD > of a boot.  I know it's not causing a problem, but I was wondering- > what I could do to get rid of the messages.  > : > %INSTALL-I-NOTSHRADR, DECW$XLIBSHR is not installed with > shareable address data > A > %INSTALL-I-NONSHRADR, image installed ignoring '/SHARE=ADDRESS' 5 > DISK$SYS:<SYS0.SYSCOMMON.SYSLIB>DECW$XTLIBSHRR5.EXE = > %INSTALL-I-NOTSHRADR, DECW$XTLIBSHRR5 is not installed with  > shareable address data > A > %INSTALL-I-NONSHRADR, image installed ignoring '/SHARE=ADDRESS' 5 > DISK$SYS:<SYS0.SYSCOMMON.SYSLIB>DECW$XMLIBSHR12.EXE = > %INSTALL-I-NOTSHRADR, DECW$XMLIBSHR12 is not installed with  > shareable address data > 9 > %INSTALL-I-NONRES, image installed ignoring '/RESIDENT' 6 > DISK$SYS:<SYS0.SYSCOMMON.SYSLIB>DECW$MRMLIBSHR12.EXE= > -INSTALL-E-NOGHREG, insufficient memory in the code or data  > granularity hint region  > A > %INSTALL-I-NONSHRADR, image installed ignoring '/SHARE=ADDRESS' 6 > DISK$SYS:<SYS0.SYSCOMMON.SYSLIB>DECW$MRMLIBSHR12.EXE> > %INSTALL-I-NOTSHRADR, DECW$MRMLIBSHR12 is not installed with > shareable address data > 9 > %INSTALL-I-NONRES, image installed ignoring '/RESIDENT' 6 > DISK$SYS:<SYS0.SYSCOMMON.SYSLIB>DECW$DXMLIBSHR12.EXE) > -INSTALL-E-NOGHREG, insufficient memoryP >   ( Not that I recommend the following, but:  & set message /nofac /noid /notex /nosev  & See HELP SET MESSAGE for more details.   Dave   -- m4 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 Roade Vanderbilt, PA  15486e   ------------------------------    Date: 13 Aug 2004 15:27:49 -0700& From: chessmaster1010@hotmail.com (JG)9 Subject: Re: NONSHRADR and NONRES messages at end of bootC= Message-ID: <dd3f0cb7.0408131427.6637edbc@posting.google.com>"  v koehler@eisner.nospam.encompasserve.org (Bob Koehler) wrote in message news:<4n6oTU2L++yN@eisner.encompasserve.org>...h > In article <dd3f0cb7.0408120949.2547cc1a@posting.google.com>, chessmaster1010@hotmail.com (JG) writes:J > > My 7.2-2 Alphas always output these messages on the console at the endF > > of a boot.  I know it's not causing a problem, but I was wondering/ > > what I could do to get rid of the messages.0 > > < > > %INSTALL-I-NOTSHRADR, DECW$XLIBSHR is not installed with > > shareable address data > >  > " >    Sounds like time for autogen.  C Autogen has been run many times on these systems since the messageso started coming out.    ------------------------------   Date: 13 Aug 2004 18:42:47 GMT6 From: DAVISM@er6.eng.ohio-state.edu (Michael T. Davis)0 Subject: Re: Rejecting network access to service: Message-ID: <cfj237$t89$1@charm.magnus.acs.ohio-state.edu>  < In article <cfino0$inc@newton.cc.rl.ac.uk>, "Richard Brodie" <R.Brodie@rl.ac.uk> writes:n   >sD >"Michael T. Davis" <DAVISM@er6.eng.ohio-state.edu> wrote in message5 >news:cfimhr$s0i$1@charm.magnus.acs.ohio-state.edu...o >a6 >> In essence, I want to accept queries from any host,G >> except those on the NTP service's reject list.  What else might I be  >> missing?P >iH >The service reject list is like old-fashioned TCP wrappers; better thanL >nothing but essentially useless for a permanently running server like NTPD. >oD >However, you can put access controls in the NTP configuration file, >or with NTPDC.  >g >g  E 	Thanks for this.  While the version of TCP/IP Services we're runningwM (V5.3 - ECO 2) doesn't seem to have documentation on this feature, the online0G documentation for v5.4 does.  What's more, the "restrict" option in the0C configuration file works just fine under the version we're running.   
 Much obliged,p Mike --I              Michael T. Davis            |    Systems Specialist: ChE,MSEAL     E-mail: davism@ecr6.ohio-state.edu   | Departmental Networking/ComputingH            -or- DAVISM+@osu.edu          |     The Ohio State UniversityH  http://www.ecr6.ohio-state.edu/~davism/ |     197 Watts, (614) 292-6928   ------------------------------  # Date: Sat, 14 Aug 2004 05:05:17 GMT,/ From: "Richard L. Dyson" <rick-dyson@uiowa.edu>p Subject: Re: Samba on OpenVMS + Message-ID: <h4hTc.5100$TI1.1494@attbi_s52>i   Michael Clark wrote:M > Currently we are running a dated version of PATHWORKS 6.0C on our VMS 7.2-1rG > installation.  I was wondering how a samba installation would comparepG > functionality wise.  I have used samba before on *BSD/Linux operatingh
 > systems.  L I have Samba v2.2.8 for OpenVMS installed.  I have not seen a newer release.F I believe the official Samba is now v3.x and prior versions were going  to be dropped from updates, etc.  G I have tested it VERY little.  It is a little hard to figure out how toaH setup.  I don't have any experience with it elsewhere.  Pathworks wasn't' easy to setup/configure either, though.   B I have been able to map shares from my Win2k and WinXP boxes to myI OpenVMS v7.3-1 servers.  I have not tried with any other combo.  Nor haveV I pushed on it at all.   Here is the URL I have for it:  , 	http://www.pi-net.dyndns.org/anonymous/jyc/   Regards, Rick   ------------------------------    Date: 13 Aug 2004 22:31:37 -07001 From: dugaldpeacock@yahoo.com.au (Dugald Peacock)e0 Subject: TCP Server  SYSTEM-F-DUPLNAM on restart= Message-ID: <df7a3cf2.0408132131.28d07960@posting.google.com>"   Dear Group,t  , I am writing a TCP server on Open VMS using:6 "Compaq TCP/IP Services for OpenVMS Alpha Version V5.3> on a COMPAQ AlphaServer DS20E 666 MHzP running OpenVMS V7.3-1"  E I have a question about restarting my server.  I am currently runningdC my server using the OpenVMS debugger and stopping it with control-Y F and entering stop at DCL.  In the long run I will run it as a detached process.  @ When I have no clients attached I can stop and restart my serverB immediately.  However if there is one or more clients and I try toF restart my server as described above I get SYSTEM-F-DUPLNAM when I tryF to set the server options.  After one minute it is possible to restart my server without any errors.m  E When I look at the TPCIP devices immediately after stopping my serverr+ I cannot see the device I was listening on.w  F What is the cause of this?  Is it the linger timer or some thing else?4  I have tried to disable linger but with no success.  : Is there any timer I can change so I can restart my server immediately?  ? I have provided my setup code (FORTRAN 77) below my signature.     Thanks   Dugald           PROGRAM TCPIP_LISTENER       IMPLICIT NONE          INCLUDE '($IODEF)'       INCLUDE '($SSDEF)'       INCLUDE '($DVIDEF)'t       INCLUDE '($LNMDEF)'i       INCLUDE '($SYSSRVNAM)'       INCLUDE '(LIB$ROUTINES)'-       INCLUDE 'SYS$LIBRARY:TCPIP$INETDEF.FOR'h         INTEGER*2 SERVER_BACKLOG       INTEGER*2 LISTEN_CHANNEL!       INTEGER*2 UCX_INET_HTONS_I2p       INTEGER*2 SERVER_PORTNUM       INTEGER*4 STATUS         INTEGER*4 PROBE_TIMER        INTEGER*4 DROP_TIMER       INTEGER*4 TIMER_LENGTH       INTEGER*4 REUSEADDR  !s.       PARAMETER INET_DEVNAME = 'TCPIP$DEVICE:''       PARAMETER connect_event_flag = 10  !l+ !     IOSBLK structure used with $QIO callsa !a       STRUCTURE /IOSBLK/          INTEGER*2 STATUSn          INTEGER*2 BYTCNT           INTEGER*4 DETAILS       END STRUCTUREl !e4 !     UCX Item List 2 structure used with $QIO calls !        STRUCTURE /ITEM_LIST_2/e          INTEGER*2 LENGTH           INTEGER*2 TYPEa          INTEGER*4 ADDRESS       END STRUCTUREe !c4 !     UCX Item List 3 structure used with $QIO calls !s       STRUCTURE /ITEM_LIST_3/           INTEGER*2 LENGTHv          INTEGER*2 TYPEl          INTEGER*4 ADDRESS          INTEGER*4 RETLENs       END STRUCTUREh !o1 !     UCX sockchar structure used with $QIO callss !r       STRUCTURE /SOCKCHAR/          INTEGER*2 PROTe          BYTE      TYPEp          BYTE      AFs       END STRUCTURE2         STRUCTURE /TRNITM/          INTEGER*2   BUFLENt          INTEGER*2   ITMCDEi          INTEGER*4   BUFADDn          INTEGER*4   LENADD        END STRUCTUREa         STRUCTURE /LINGER/          INTEGER*4 ENABLED          INTEGER*4 TIMEr       END STRUCTUREr       RECORD /LINGER/ LINGER  !       RECORD /IOSBLK/ LISTEN_IOSBe  '       RECORD /SOCKCHAR/ LISTEN_SOCKCHARS  )       RECORD /SOCKADDRIN/  SERVER_ADDRESS2)       RECORD /ITEM_LIST_2/ SERVER_ITEMLSTo  -       RECORD /ITEM_LIST_2/ REUSEADDR_ITEMDSCRo-       RECORD /ITEM_LIST_2/ REUSEADDR_ITEMLISTn  *       RECORD /ITEM_LIST_2/ LINGER_ITEMDSCR*       RECORD /ITEM_LIST_2/ LINGER_ITEMLIST  )       RECORD /ITEM_LIST_2/ SENSE_ITEMDSCRn)       RECORD /ITEM_LIST_3/ SENSE_ITEMLISTt  !       RECORD /TRNITM/ TRNLNM_ITEMo  $       COMMON /LISTEN/ LISTEN_CHANNEL         SERVER_PORTNUM = 5000  !t< !     Set server so it can reuse the address again and again !w       REUSEADDR = 1o !i# !     Disable linger on this socket- !-       LINGER.ENABLED = 0       LINGER.TIME = 0  !m? !     Set the server backlog - look at UCX doco for this value.r !a       SERVER_BACKLOG = 1 !e% !     Set up a generic listener port.o ! ;       STATUS = SYS$ASSIGN(INET_DEVNAME, LISTEN_CHANNEL, , )e  &       IF (STATUS .EQ. ss$_normal) THEN !u* !     Set the socket characteristics. - P1 !y+          LISTEN_SOCKCHAR.PROT = TCPIP$C_TCPn.          LISTEN_SOCKCHAR.TYPE = TCPIP$C_STREAM/          LISTEN_SOCKCHAR.AF   = TCPIP$C_AF_INET  !g> !     Setup the socket name - the local port to listen on - P3 !o6          SERVER_ADDRESS.SIN$W_FAMILY = TCPIP$C_AF_INET&          SERVER_ADDRESS.SIN$W_PORT   =! UCX_INET_HTONS_I2(SERVER_PORTNUM) 9          SERVER_ADDRESS.SIN$L_ADDR   = TCPIP$C_INADDR_ANY  !e=          SERVER_ITEMLST.LENGTH       = SIZEOF(SERVER_ADDRESS)t8          SERVER_ITEMLST.TYPE         = TCPIP$C_SOCK_NAME=          SERVER_ITEMLST.ADDRESS      = %LOC  (SERVER_ADDRESS)- !-+ !    Set the port to reuse the same address  !r8          REUSEADDR_ITEMLIST.LENGTH   = SIZEOF(REUSEADDR)8          REUSEADDR_ITEMLIST.TYPE     = TCPIP$C_REUSEADDR7          REUSEADDR_ITEMLIST.ADDRESS  = %LOC (REUSEADDR)  !sA          REUSEADDR_ITEMDSCR.LENGTH   = SIZEOF(REUSEADDR_ITEMLIST) 6          REUSEADDR_ITEMDSCR.TYPE     = TCPIP$C_SOCKOPT@          REUSEADDR_ITEMDSCR.ADDRESS  = %LOC (REUSEADDR_ITEMLIST) ! 4          STATUS = SYS$QIOW(%VAL(CONNECT_EVENT_FLAG),0      -                     %VAL(LISTEN_CHANNEL),-      -                     %VAL(IO$_SETMODE), B      -                     LISTEN_IOSB,          ! IO Status BlockA      -                     ,                     ! AST Completions Routinea@      -                     ,                     ! AST Paramater5      -                     LISTEN_SOCKCHAR,      ! P1M5      -                     ,                     ! P2 6      -                     SERVER_ITEMLST,       ! P3 5      -                     %VAL(server_backlog), ! P4t5      -                     REUSEADDR_ITEMDSCR,   ! P5 5      -                     )                     ! P6  !sA          IF (STATUS .EQ. ss$_normal) THEN   ! Need to check codese8             IF (LISTEN_IOSB.STATUS .EQ. ss$_normal) THEN8                LINGER_ITEMLIST.LENGTH   = SIZEOF(LINGER)8                LINGER_ITEMLIST.TYPE     = TCPIP$C_LINGER7                LINGER_ITEMLIST.ADDRESS  = %LOC (LINGER)c !tA                LINGER_ITEMDSCR.LENGTH   = SIZEOF(LINGER_ITEMLIST)E9                LINGER_ITEMDSCR.TYPE     = TCPIP$C_SOCKOPT @                LINGER_ITEMDSCR.ADDRESS  = %LOC (LINGER_ITEMLIST)  :                STATUS = SYS$QIOW(%VAL(CONNECT_EVENT_FLAG),0      -                     %VAL(LISTEN_CHANNEL),-      -                     %VAL(IO$_SETMODE),eB      -                     LISTEN_IOSB,          ! IO Status BlockA      -                     ,                     ! AST Completione Routinem@      -                     ,                     ! AST Paramater5      -                     ,                     ! P1e5      -                     ,                     ! P2u7      -                     ,                     ! P3  s7      -                     ,                     ! P4  e8      -                     LINGER_ITEMDSCR,      ! P5   5      -                     )                     ! P6   A                IF (STATUS .EQ. ss$_normal) THEN   ! Need to check  codest>                   IF (LISTEN_IOSB.STATUS .EQ. ss$_normal) THEN,                      CALL LIB$WAIT (100000.)                   ELSE8                     write (*,*) 'IOSB on setting Linger'>                     CALL LIB$SIGNAL (%VAL(LISTEN_IOSB.STATUS))                   ENDIF                 ELSEu7                  write (*,*) 'Status on setting Linger'e/                  CALL LIB$SIGNAL (%VAL(STATUS))n               ENDIFg             ELSE+                 write (*,*) 'IOSB on setup'a:                 CALL LIB$SIGNAL (%VAL(LISTEN_IOSB.STATUS))             ENDIFf
          ELSEu*              write (*,*) 'Status on setup'+              CALL LIB$SIGNAL (%VAL(STATUS))           ENDIF
       ELSE,          write (*,*) 'Unable to assign port'       END IF
       STOP	       ENDa !t !  !b0       INTEGER*2 FUNCTION UCX_INET_HTONS_I2(HOST)       IMPLICIT NONES       INCLUDE '($FORIOSDEF)'              STRUCTURE /WORD/          UNION             MAPn                INTEGER*2 WORDe             END MAPc             MAP                 BYTE BYTE_1                BYTE BYTE_2             END MAPS          END UNION       END STRUCTURE       n       INTEGER*2 HOST       RECORD /WORD/ WORD_1       RECORD /WORD/ WORD_2      s       WORD_1.WORD = HOST#       WORD_2.BYTE_1 = WORD_1.BYTE_2l#       WORD_2.BYTE_2 = WORD_1.BYTE_1   %       UCX_INET_HTONS_I2 = WORD_2.WORD-         RETURN	       END,   ------------------------------  # Date: Sat, 14 Aug 2004 02:14:35 GMT 4 From: Kent Behrends <kent.at.bci.com@nospam.invalid>C Subject: Unknown OPCOM message: "clm privilege violation" More infoo? Message-ID: <130820041914341457%kent.at.bci.com@nospam.invalid>-  9 I am getting the following opcom messages on all 5 of my t  OpenVMS Alpha 7.2 cluster nodes:  G %%%%%%%%%%%  OPCOM   9-AUG-2004 10:55:08.26  %%%%%%%%%%%  DUMP_LOG_FILE6  F OPCOM has noticed a condition which might be due to an internal error.J It might also be explained by normal events, especially if nodes have justL crashed or rebooted in a VAXcluster.  Please bring this message to Digital'sG attention only if you are having problems with operator communications.m  ; Buffer is   219 (%X00DB) bytes -- "clm privilege violation"tn  6174733C 20202020 20204D45 54535953 00010004 FFFFFFFF 5FFFFFFF 00000008 ......._........SYSTEM      <sta 0000n  00000001 0094000A 4D40000A 47200001 000D0000 00B50902 0413130C 203E7472 rt> ............. G..@M........ 0020n  00080000 00010000 00000000 00000000 0407000A 47C00001 000D0000 00000000 ..........G.................... 0040n  4D455453 59532020 20202020 4D455453 59530001 0004FFFF FFFFFFFF FFFF0000 ..............SYSTEM      SYSTEM 0060n  00000001 00040000 00010000 000000FF F9FF0000 00020000 0000010A 00042020   ............................. 0080n  00000000 00000000 00000000 00000000 000D0000 00010006 00060000 00000000 ................................ 00A0n  00000000 003A3041 504F2431 30565245 535F6961 67612067 6E690000 00000000 ......ing agai_SERV01$OPA0:..... 00C0     Anyone have any ideas?   -- a --- 
 Kent Behrends  BEHR Consulting International  http://www.bci.com   ------------------------------   End of INFO-VAX 2004.448 ************************s no longer viable in the longK > term. In such cases, sticking with Alpha systems is the logical solution.     Q We're both on the same side of this issue, but the reality is that Alpha is dead  P and if one needs to  install any new VMS systems in the next several years, the Q itanic is the only game in town.Yno&f*ofr~MP+zlr۱6Yj̈́[:"T*
&DR|wT#7JX%Wy>W?gzşB
@Uu<_/J
ҚL8Z5fJp]-}g	Wz/Z{~ɹ硹zg#a4Cتe!Krˬi[ZFel52YlFQ1639m`cDGSkZ-yyF5r2*La{@4`ܶSLkPgT#׀L1`;"g&fCl3ə#xrOKzY?z}O3RȻ	VNAN	VG-kf&Gm؀mbq639x0`?6SL+<R`&Gk_걍nJ`vQy$m̀ϥ۸	vՀLn#6ǽ6#c3۟
XٽvLv2=639ZzmnUM9)d639msĀmHnC`ЕiH&)[̓5f4`3YKۅۘ&X6yvr=639Z՗nUef&GkelYom&%
hi;mb;h?lG[րL6]3޳&fʽc*כ!lzlgvr#yle;ؔoyF5rTnfr'\0`6Ǖgu*63b3c3s~n1UT(!=?"d2O*M37 4^̀g˘`zlfr[3hV!w¶&HmZ#_63l3c3CJdJ=ܞ'׭I3LGZ6Or،<9I639Z͟Z|=6*3<639ڵ`V/gZU&fZ.639Z5n+n*3>OYǦ|kƛGy0]Y	=:	:0`i2ŉl3"G6
gbJgR5IEWUjx2g RG>ҧ\s}t<9clfr[SmVҶj[حZM^gT##D7`+Ta2Gν&r5zlfl^639̀Mnϔ&fo1639.k1Ә5+ƬěZ}M>
GVO>_'j^^;oN஽;{V[<OSKkӽoy~%?mMk>!^{;5={~]D(X8|֝Oƶzfū&OOVuT{mѳc6N3O#*o3+&S!U6o޲so=6~zPl߱ݎ