1 INFO-VAX	Fri, 14 Dec 2001	Volume 2001 : Issue 694       Contents:> 2000           Your Vacation Winning !                  9250184 ALPHA strategy (was: RE: Inquirer: OpenVMS on DS20L)P Chase Visa Card, Verisign Thawte Certificate, Rapid Traffic and Eif Services forP Re: Chase Visa Card, Verisign Thawte Certificate, Rapid Traffic and Eif Services Re: Compaq without the merger  Re: Compaq without the merger  Re: Compaq without the merger   Re: Crash (SYSDUMP.DMP) question" Re: DEC Alpha 255 - 300 Mhz wanted" Re: DEC Alpha 255 - 300 Mhz wanted" RE: DEC Alpha 255 - 300 Mhz wanted" Re: DEC Alpha 255 - 300 Mhz wanted" RE: DEC Alpha 255 - 300 Mhz wanted" RE: DEC Alpha 255 - 300 Mhz wanted" Re: DEC Alpha 255 - 300 Mhz wanted" Re: DEC Alpha 255 - 300 Mhz wanted" RE: DEC Alpha 255 - 300 Mhz wanted Re: DECC$TIME multiply defined Re: DECC$TIME multiply defined& Disposing of: DS10L for less then 2900E Re: From within a CGI: sending an https method=post request elsewhere  Re: FTP Servers 3 Gartner again suggests it expects VMS to be dropped  Re: global foreign command Re: global foreing command Re: help [[  MCR NCP ]] " Re: HP Foundations - let them know# Huge file compression - help needed ' Re: Huge file compression - help needed ' Re: Huge file compression - help needed ' Re: Huge file compression - help needed  Re: Inquirer: OpenVMS on DS20L Re: Inquirer: OpenVMS on DS20L Re: Inquirer: OpenVMS on DS20L RE: Inquirer: OpenVMS on DS20L# Re: More about Alpha and the merger # Re: More about Alpha and the merger # Re: More about Alpha and the merger  More on Google archive2 Re: Move to an HP OS, most folks would rather not.2 Re: Move to an HP OS, most folks would rather not.2 Re: Move to an HP OS, most folks would rather not.2 Re: Move to an HP OS, most folks would rather not.. Re: nova (was: RE: Inquirer: OpenVMS on DS20L). Re: nova (was: RE: Inquirer: OpenVMS on DS20L)* nova (was: RE: Inquirer: OpenVMS on DS20L). Re: nova (was: RE: Inquirer: OpenVMS on DS20L). Re: nova (was: RE: Inquirer: OpenVMS on DS20L). Re: nova (was: RE: Inquirer: OpenVMS on DS20L). Re: nova (was: RE: Inquirer: OpenVMS on DS20L) Old VAX Documentation " OT: Startrek, Borgs and the HHGTTG& Re: OT: Startrek, Borgs and the HHGTTGA Press Release SyntheSys Secure Technologies - JabCast  on OpenVMS ! Reloading device drivers on Alpha % Re: Reloading device drivers on Alpha # Re: remote connection and pathworks  RMSdef.stb linking ... Re: RMSdef.stb linking ... Re: RMSdef.stb linking ...P SPAM Reporting - was Re: Chase Visa Card, Verisign Thawte Certificate, Rapid TraP Re: SPAM Reporting - was Re: Chase Visa Card, Verisign Thawte Certificate, Rapid( Summary "Unknown VAXstation 4000-90 ???" sys$getdvi and socket  Re: sys$getdvi and socket  Re: sys$getdvi and socket  Re: sys$getdvi and socket  Re: The demise of compaq Re: The demise of compaq Re: The demise of compaq Re: The demise of compaq Re: The demise of compaq Re: The demise of compaq Re: The demise of compaq Re: The demise of compaq Re: vms 3.x question Re: VMS file hex editor?? Re: Writing a device driver: virtual/physical address questions ? Re: Writing a device driver: virtual/physical address questions  WSSIZE and AWSA   F ----------------------------------------------------------------------   Date: Fri, 14 Dec 2001 21:18:09 $ From: 189250travelincentives@aol.comG Subject: 2000           Your Vacation Winning !                  925018 8 Message-ID: <iss.66a.3c1a0cb0.b8f65.1@mx2.west.saic.com>  > You have been specially selected to qualify for the following:  0 Premium Vacation Package and Pentium PC Giveaway6 To review the details of the please click on the link # with the confirmation number below:    http://vacation.81832.com    Confirmation Number#Lh340 J Please confirm your entry within 24 hours of receipt of this confirmation.  " Wishing you a fun filled vacation!J If you should have any additional questions or cann't connect to the site % do not hesitate to contact me direct: , mailto:vacation@btamail.net.cn?subject=Help!   ------------------------------  + Date: Fri, 14 Dec 2001 19:38:30 +0100 (MET) 9 From: Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com> = Subject: ALPHA strategy (was: RE: Inquirer: OpenVMS on DS20L) ; Message-ID: <01KBVBG11KKO9138XQ@sysdev.deutsche-boerse.com>   K > Well.  I suppose it is because it is the Alpha Server business that makes  > the money.    E I know the comparison is not spot-on, but isn't that like saying "we  F stopped fitting our cars with tyres since engines were making most of H the profit" or, a bit closer to home, "we stopped fitting our computers I with hard disks since memory was making most of the profit"?  I know I'm  E being A BIT cynical, but you get the point: there needs to be a full  I range of ALPHA hardware.  My guess would be that high-performance places  I regularly upgrade their production machines, but upgrade the development  H machines less often (not as necessary: after all, a programmer can only @ type so fast; also, some used production machines might move to I development).  In other words, terminating the low-end (yes, I do have a  C "letter of commitment" to VMS workstations somewhere) won't impact  G customers as quickly, so it would be wrong to think that if the newest  H machines are high-end and no-one complains right away, then all is well.  N > EV7 has no other purpose that to provide high-performance, and scale to veryI > large systems.  It is not focused on the uniprocessor market.  You want J > something on the desktop, think EV68, but not EV7 or EV8, or EV9, or any! > other processor on the roadmap.  > L > From I think a non-VMS perspective, anything small enough to be on or next2 > to a desktop, is something for a Intel solution. > E > Do I agree with that?  Not from a VMS, or Tru64 perspective.  While L > certainly big systems is where we make our money, you still need the small. > form factor ones to sell the whole solution. > L > Itanium has the potential of providing us a lower-cost platform than where > Alpha was heading.  I As I see it, the move to Itanium will allow the full range, from low-end  F desk-top workstations to high-end high-performance servers.  It seems D strange to me that this strategy will be possible with Itanium, but E wasn't possible with ALPHA.  Unless, of course, the hope is that the  C high volume of NON-VMS low-end machines will make it worthwhile to  & support VMS on the low-end machines.     ------------------------------  % Date: Fri, 14 Dec 2001 09:10:35 -0800 O From: "Paul Mac Arthur (Rapid Internet Marketing Newsletter)" <info@1edeal.com> Y Subject: Chase Visa Card, Verisign Thawte Certificate, Rapid Traffic and Eif Services for 9 Message-ID: <iss.342c.3c19c2c0.798af.1@mx2.east.saic.com>   I Chase Visa Card, Verisign Certificate, Rapid Traffic and Eif Services for  all the readers.  I At 20% better conditions: follow the links email your requests, fill your  forms   
 And enjoy.   http://www.eif.net/    http://www.eif.net/chase.htm  # Rapid Internet Marketing Newsletter       = =============================================================   
 IN THIS ISSUE    1. Search Engine News Flash ) 2. Reach 75% of the Internet with one buy > 3. SPONSOR # 1 Maximize your keyword bids for "Pay-Per-Clicks"3 4. Three Steps To Overture(former Goto.com) Success : 5. SPONSOR # 2 DRIVE MORE TRAFFIC TO YOUR WEBSITE FOR FREE" 6. How to Subscribe or Unsubscribe    > ==============================================================   1. Search Engine News Flash   H 1). Both Yahoo and LookSmart have recently increased the price of their . Express submission service to $299 last month.  L 2). AltaVista followed Inktomi's lead in offering a paid inclusion program. F FAST is expected to bring out its own program shortly. (More details: 3 http://www.altavista.com/sites/search/express_incl)   L 3). LookSmart Adds Paid Listings Option For Small Businesses. A new program D called "Site Promote" from LookSmart has made it possible for small J businesses and others with low publicity budgets to get listed within the G paid placement area of its search results. The new program allows site  F owners pay a monthly fee of $20 or $30 to appear within the "Featured 	 Listings" H area of the LookSmart search results page. These are paid listings that = appear above LookSmart's editorial results. (More details at   http://listings.looksmart.com)  L 4). Overture(the former Goto.com) has signed an agreement to provide search C results to Yahoo!'s millions of users last month. Users who conduct 	 searches  K at www.yahoo.com will see search results that include Overture's top three  F search listings in a section called "Sponsor Matches." Two additional J Overture listings will be featured at the bottom of the page in a section L called "More Sponsor Matches." When users click on the "Next 20" link, they K will also see five additional Overture listings in the same configuration.  L All listings displayed in the Yahoo! implementation will feature a one line G description and URL with full title mouse-over as a part of the search   results.A =================================================================   ) 2. Reach 75% of the Internet with one buy   I Overture is the one online advertising buy that will drive more targeted  K customers to your site. With Overture, you only pay when someone clicks on  G your search listing. And because their search results reach 75% of all  F Internet users, you can be sure to get tons of high-quality, targeted  customer traffic!   % Advertising with Overture gives you:     TREMENDOUS REACH-   F Expand your customer reach to 75% of all Internet users with just one H advertising buy. Overture can put you in the search listings on Yahoo!, I America Online, Lycos, AltaVista, Hotbot, Netscape, CNET and many others.    TARGETED LEADS-   G Get your site in front of users right when they are searching for your  $ products, services and information.    COST EFFECTIVE-   8 Pay only when targeted leads click through to your site.   !!! $10 BONUS CREDIT !!!  D Earn a special $10 bonus credit if you become a new active Overture H advertiser* between now and March 31, 2002. This offer is only valid for new F Overture advertisers, and if you've received this message, that's you!  I Click on http://www.overture.com/d/advertisers/p/bjump/?o=RR-13590&b=10   - learn more and list your site with Overture.        A =================================================================   > 3. Sponsor # 1 Maximize your keyword bids for "Pay-Per-Clicks"  I Dynamic KeywordBid Maximizer is an ultimate search engine promotion tool  J helps you manage your keywords and bids at ALL major pay-per-click search J engines. You can use it to build your keyword list, manage your keywords, I monitor your keyword bids and URL positions at all major "Pay-per-click"  E search engines such as Overure, Overture(UK), FintWhat, 7Search, and  K Sprinks. It will update your keyword bids, analyze your ranking positions,  > closing bid gaps and bit to the TOP 3 piosition AUTOMATICALLY:  G    - Save you hundreds of hours per day to maintains and monitors your  # keyword bids if checking manually.  I    - Saves up to 85% of bid cost by eliminate bid gaps and maintain your  G current position automatically.(don't over pay for clicks where is not   necessary)  H    - Stay on top of your competitors 24 hours a day, 365 days a year by < improve your position to the TOP 3 positions automatically. J    - Automatically monitors your keyword bids once per day or every hour. J    - Automatically maintains your desired position to get more traffic to  your web site.  L    - Saves money by allowing you to set maximum bid parameters so you don't  overpay for clicks. H    - Fully automated and run in the background when you are doing other  work. C    - No monthly fee or other charges, pay once and use it forever.  #    - 30 days money back guarantee.           A =================================================================   4 4. Three Steps To Overture(former Goto.com) Successs  9 Following a mention in my free newsletter 'Success Lines' : that I was having some success generating traffic from the9 pay-per-click search engine Goto.com, I received an email < from a subscriber asking for a blow by blow account of how I9 did it. So, for the benefit of a wider audience here's my 	 response.   6 I should first point out that I like to keep things as/ simple as possible, so I'll limit this to three  straightforward steps.   Step 1 - Find your keywords   < Goto provide a useful tool for identifying the most commonly: searched keywords for the previous month. There's no guess< work here. If a search term has received hundreds of hits in< a month, it's safe to assume that it'll continue to do so in the future.   8 First you need to visit the page where Goto provides its advertising tools. This is:   % https://secure.goto.com/s/dtc/center/   < Then click on "Search Term Suggestion Tool". This will bring< up a search box in which you type your main keyword. In this: example I'll use the keyword "ebook". The result is a list9 of search terms from "free ebook" at 13944 hits to "ebook  publish" at 49 hits.   Step 2 - Find the cost to bid   < Having selected your search terms from the list, you need to8 determine whether you can afford to bid for them. You're; aiming to get in the top 3 slots, as this means you will be < featured on many other search engines rather than just Goto.  < Using the same URL as above click on "Get Current Bid Tool".; This will open a search box in which you type your selected : search term. I'm going to use "free ebook downloads" which< appeared towards the middle of the previous list with around	 900 hits.   ; The results tell me there are only 3 competitors bidding on : this term at $0.06, $0.05, $0.05. So, to get a top 3 place: as cheap as possible I need to bid $0.06 to get 2nd place," as a $0.05 bid would place me 4th.  ; Do this for all your search times, listing the ones you can 9 get cheaply. You'll find some will be very expensive. The 9 price you bid is what you pay for every click through, so 1 don't get carried away. The minimum bid is $0.05.    Step 3 - Make your bids   ' First visit the account set-up page at:   % https://signup.goto.com/s/dtc/signup/   8 Complete a separate section of the form for every search9 term you're bidding for. You'll need to list search term, 8 title of entry, description of entry, page URL, and bid.  4 Try to include the search term in both the title and< description and you'll get a much better response. There are full instructions on the page.  9 You pay a minimum monthly fee of $20, whether you receive ; $20 of clickthroughs or not. So make sure you bid on enough 5 terms. You'll hear back from Goto.com in about 5 days * whether or not each bid has been accepted.  < You need to check back from time to time to make sure no one; has outbid you, in which case you need to decide whether to 8 up the bid. You also receive a monthly traffic report by' email listing the hits on each keyword.   < That's basically all there is to it. Remember to be creative6 with your search terms. For example, a term containing2 "online" may be out of your price bracket, but one containing "on line" may not.    Be successful!      < ------------------------------------------------------------      A =================================================================   : 5. Sponsor # 2 Drive More Traffic to Your Website for Free  K Dynamic Submission 2000 - "ALL-IN-ONE", 5-star, Award-Winning,web-promotion K software that drives Internet traffic to websites for FREE. It includes ALL L the tools needed to promote websites on the Internet in one package and willG submit websites to 1000+ major search engines automatically, check your H website ranking with search engines, analyze keywords, optimize your webG page and will get your website to the TOP positions of ALL major search  engines.  	 Features:   * Auto Engine Database Update,   * Search Engine Submitter,   * Meta Tag Generator,  * Web Site Optimizer,  * Web Ranking, ?  * Customise Submission to Yahoo and Open Directory (dmoz.org), 2  * URL Verification and Links Population checking,  * Doorway Page Generator,  * Keyword Builder,   * FTP Upload,2  * Client Engine Builder (Enterprise Edition Only)        A =================================================================0  # 6. How to subscribe and unsubscribeO   We need your feedbacki ____________________  E We hope you find this information useful. If you have any interestingVJ articles about tips, tricks, or comment on marketing promotion issues that5 you want to share with others, please simply send to:p$ mailto:info@1edeal.com?subject=Share  K Do you want to contribute an article in exchange for some free exposure? If G so, send us your contribution, with your brief, promotional byline, to:h$ info@1edeal.com?subject=Contribution    " About InternetMarketing Newsletter% _____________________________________   J Your FREE subscription to Rapid Internet Marketing ezine is brought to you< by EIF, a division of Hyksos Eif Ltd, the creator of DynamicJ Submission 2000 - award winning web promotion software that drives traffic to your web site.   - To download a FREE trial of EIF, please goto:s http://www.eif.net  B Don't hesitate to forward a copy of this newsletter to friends andK associates, but please ask for permission before reproducing the content ine. any form -- we would like to know who you are.   To subscribe or unsubscribeo _______________________       = To unsubscribe, send a blank email from the above address to:2 mailto:remove@1edeal.com  < To subscribe to this newsletter, just send a blank email to: mailto:info@1edeal.com  @ Rapid Internet Marketing Newsletter is powered by Dynamic Opt-InJ Emailer -- the choice of professional email marketing software that allowsD you to send "personalized" bulk email messages to your customers andL subscribers. Let Dynamic Opt-In Emailer save you time and money by improving- your marketing effectiveness. More details ata http://www.eif.net   Privacy Policy: J This is a private mailing list and it will never be sold or given away for any reason.)> If you do not wish to receive future issues of info@1edeal.com( Newsletter, simply send a blank email to2 mailto:remove@1edeal.com with "unsubscribe" as the subject.     Copyright 2001 Dynamic  I Chase Visa Card, Verisign Certificate, Rapid Traffic and Eif Services foro all the readers.  I At 20% better conditions: follow the links email your requests, fill yourn formse  
 And enjoy.   http://www.eif.net/i   http://www.eif.net/chase.htm   ------------------------------  % Date: Fri, 14 Dec 2001 13:29:33 +0100.1 From: Franz-Josef Fornefeld <jo.fornefeld@gmx.de>sY Subject: Re: Chase Visa Card, Verisign Thawte Certificate, Rapid Traffic and Eif ServicesC' Message-ID: <9vcurt.c5.1@jo.dyndns.org>t   [posted&mailed]U  < Paul Mac Arthur (Rapid Internet Marketing Newsletter) wrote:  Q > From: "Paul Mac Arthur (Rapid Internet Marketing Newsletter)" <info@1edeal.com>e/ > Organization: Info-VAX<==>comp.os.vms Gateway l > Subject: Chase Visa Card, Verisign Thawte Certificate, Rapid Traffic and Eif Services for all the readers.' > Date: Fri, 14 Dec 2001 09:10:35 -0800 ; > Message-ID: <iss.342c.3c19c2c0.798af.1@mx2.east.saic.com>i  & Sheesh, SPAM via the Info-VAX-Gateway.   HTML and wrong Date/Time.i  + Mark, would you please cancel this account?E   regards    FollowUp-To poster   ------------------------------  % Date: Fri, 14 Dec 2001 02:57:59 -05001  From: John Santos <JOHN@egh.com>& Subject: Re: Compaq without the merger4 Message-ID: <1011214024741.418B-100000@Ives.egh.com>  , On Fri, 14 Dec 2001, Terry C. Shannon wrote:   > B > "Ken and Kelley Coleman" <knkcoleman@attbi.com> wrote in message) > news:9NVR7.44504$Yy.491844@rwcrnsc53...e > > C > > "Terry C. Shannon" <terryshannon@mediaone.net> wrote in messagei+ > > news:3ZNR7.41519$Yy.463296@rwcrnsc53...3 > > > H > > > All the more reason why Compaq needs to continue selling corporate > > desktopsK > > > (as opposed to consumer peecees, which appear to be more trouble thany > they > > > are worth!). > > >n > >oN > > I don't know. They'll have to do a better job on that from my perspective.J > > We're a Compaq shop at my facility and the last shipment of 65 desktopM > > workstations came up with 9 dead-out-of-the-box units - two of which weremN > > shipped without power supplies, some had power supplies but wires were notN > > connected, and several had no memory chips at all (we paid for 256Mb RAM). > M > This obviously is not acceptable and is not in keeping with the "COMPAtiblea > Quality" name. > N > > That's a very poor percentage. (Brought to mind my old Packard Bell days!)L > > That along with the more than two-month delay in other shipments (thingsM > > from DLT tapes to universal hard drives) make me think there's more amisstL > > than Compaq will let on. But I admit that I could be letting the currentI > > "political" situation of Compaq Corporate color my thinking about itsc > > operations.a > >p > M > Well, I've had a couple of Presarios and was very dissatisfied with them. I K > was thermonuclearly PO'd when the Imitation SuperDisk failed and both CPQeL > and Best Buy (from whom I purchased a service contract) blew me off 'cos IK > had installed a real OS (Win2K) over the squatulent Win98 virus. Best BuytK > said that the software change invalidated the purchase contract. CPQ said I > that the Presario was a consumer product and Win2K was a commercial OS,t+ > hence they refused to remedy the problem.r  E Terry - there are 2 things you could have tried: 1) painful - back uptK your W2K system, install W98, bring it back and say "It's broken.  Fix it."nB 2) Much easier - lie.  When they ask you what O/S you are running,F say "Windows 98, which came with it."  What are the chances they could tell the difference?  B Every PC warrantee I've ever seen says you have a right to install@ new software and add new hardware without voiding the warrantee.A (Of course the new stuff isn't covered by the warrantee, just thetB original equipment.)  However, they often seem to say that you mayE have to restore the system to the original config (including originalhA O/S) before they will attempt to diagnose the problem.  But for aw? purely hardware problem, they should be able to diagnose from ao@ bootable floppy or CD and shouldn't care if the installed O/S is( M$ or Linux or the mythical OpenVMS x86.  @ Which leads to alternative 3) Yank your hard drive and install aC replacement, freshly formatted, otherwise empty drive and tell themr "It won't boot anymore." ;-)   > J > The ultimate solution to the Presario Problem was quite soul-satisfying.L > Remember the old "Second City TV" show (a SNL knock-off) which opened each? > episode with folks hurling teevees out of skyscraper windows?e > J > My Presario was hurled from my second floor porch. It was an interesting3 > exercise in qualitative functional decomposition.g > N > My roommate's Presario also got weird and crufty on me. I replaced it with aJ > Dell PC as I could not in good conscience recomend a Presario to anyone. > J > I also have a Compaq DeskPro 600Mhz running Win2k. The floppy drive wentL > South the second week I had the system. Rather than futz with it, I use my: > CD burner or flash memory card reader for file transfer. > N > I also had an Armada 6500 which went teats-up early on. It was replaced withG > an Armada M700 which ended up being "rebricked." Replaced the CPU andmK > motherboard, re-inited the disk, and replaced Win98 virus with Win2K. ThewK > Armada is now down due to a loose connection between the body and the TFT=	 > screen.= > M > Current portable is an EVO N600c which is absolutely a superb system that Iy > would recommend to anyone. > I > I don't know how CPQ compares with rivals in the commercial desktop andoI > portable realm, but I know that I had infinitely more problems with the & > Apple garbage I used five years ago.   -- t John Santosv Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  # Date: Fri, 14 Dec 2001 13:54:40 GMT"4 From: "Terry C. Shannon" <terryshannon@mediaone.net>& Subject: Re: Compaq without the merger= Message-ID: <AwnS7.12467$Sj1.7085361@typhoon.ne.mediaone.net>   @ "Ken and Kelley Coleman" <knkcoleman@attbi.com> wrote in message' news:FrgS7.22459$7y.275161@rwcrnsc54...  > A > "Terry C. Shannon" <terryshannon@mediaone.net> wrote in messageT9 > news:yEeS7.12350$Sj1.6866329@typhoon.ne.mediaone.net...o >l > >lG > > Well, I've had a couple of Presarios and was very dissatisfied withe them.  > IcI > > was thermonuclearly PO'd when the Imitation SuperDisk failed and boths CPQsL > > and Best Buy (from whom I purchased a service contract) blew me off 'cos IrI > > had installed a real OS (Win2K) over the squatulent Win98 virus. Bestl BuySH > > said that the software change invalidated the purchase contract. CPQ saidK > > that the Presario was a consumer product and Win2K was a commercial OS, - > > hence they refused to remedy the problem.e >dJ > That's terrible. Actually, I would think that any company that could getL > their systems to work with Win98 would be grateful that a customer *could* > switch to 2K.o  K Compaq support copped out. Perhaps they have a point that's defensible in a=H court of law, but what they ended up with was a customer who would neverE even consider purchasing a Presario again. The plot thickens... I had J another Presario kicking around. It went all crufty, so I took it to TexasL and let the DFWCUG Adepts take a look at it. Impossible to fix the thing, so$ it too is destined for the junkyard.  @ > I can't stand 98, but I'm too uninterested - or maybe just tooJ > lazy - to upgrade. I've never used Presarios, but had always bought into therL > idea that Compaq was a pretty good home machine. I have an HP Pavilion andJ > I'm pretty happy with it - except for that Win98 thing. But I'm a fairly low L > end home user. I work on computers all day at work and my enthusiasm wanesL > and waxes once I get home. A fine meal and a couch are all I long for most > evenings.  :-) > L > > My Presario was hurled from my second floor porch. It was an interesting5 > > exercise in qualitative functional decomposition.c >iI > I've never had the cajones to do something like that. Then again, being1I > female, I've never had cajones at all. But that's beside the point now,u > isn't it?t  B Presario-throwing is a fine, all-American sport. It's fun for all,F regardless of their sex, sexual orientation, race, creed, religion, orK political persuasion. Presarios aren't very heavy, so not even OSHA can get=" in the way of this good clean fun.   >oK > > I also had an Armada 6500 which went teats-up early on. It was replacede > withI > > an Armada M700 which ended up being "rebricked." Replaced the CPU andpI > > motherboard, re-inited the disk, and replaced Win98 virus with Win2K.a TheyI > > Armada is now down due to a loose connection between the body and thea TFT- > > screen.r >eL > I have an Armada M700 also and only use it on those rare occassions when IJ > have to check in from home. I usually just end up going in. It's runningK > Win98 and again, it's a pain in the butt just for that reason. I can takeo itE > into work and get it upgraded to 2K but that requires an element ofm' > motivation I seem to lack these days.o >bH > > Current portable is an EVO N600c which is absolutely a superb system that > Ip > > would recommend to anyone. >s1 > Haven't heard of it. What do you like about it?r  K First the bad news. The price is about $2.5K. But you get what you pay for.mI 1.2GHz processor (way more than you need for a notebook, but it makes forvI outstanding DVD playback), up to 1GB memory (I have about 750MB in mine),tK excellent 14" screen, sturdy magnesium case, 3+ hour battery life (and over D 2 hours when running a DVD, enough for a complete movie), integratedJ Ethernet, nice, responsive keyboard. Really nice graphics. And, of course, Windows 2000 support.s  K My only real gripe involves the cheesy plastic inserts in the PCMCIA slots. K Hinged doors would be nicer. And the little tabs that are used to eject ther PC cards can be a pain as well.c  J But all things considered, I regard the Evo N600c to be the BMW of desktopI replacement notebooks and would recommend the system to anyone. ReviewersrJ from the trade press seem to agree. If you're looking at the Evo N150/N160I econobox, think again. The N600c is well worth the additional investment.    cheers,    terry s    ------------------------------  # Date: Fri, 14 Dec 2001 13:59:55 GMTb4 From: "Terry C. Shannon" <terryshannon@mediaone.net>& Subject: Re: Compaq without the merger= Message-ID: <vBnS7.12469$Sj1.7087642@typhoon.ne.mediaone.net>r  - "John Santos" <JOHN@egh.com> wrote in messageg. news:1011214024741.418B-100000@Ives.egh.com.... > On Fri, 14 Dec 2001, Terry C. Shannon wrote: >a > >lD > > "Ken and Kelley Coleman" <knkcoleman@attbi.com> wrote in message+ > > news:9NVR7.44504$Yy.491844@rwcrnsc53.... > > >sE > > > "Terry C. Shannon" <terryshannon@mediaone.net> wrote in messagee- > > > news:3ZNR7.41519$Yy.463296@rwcrnsc53...c > > > >wJ > > > > All the more reason why Compaq needs to continue selling corporate > > > desktopsH > > > > (as opposed to consumer peecees, which appear to be more trouble than > > they > > > > are worth!). > > > >i > > >aC > > > I don't know. They'll have to do a better job on that from my  perspective.L > > > We're a Compaq shop at my facility and the last shipment of 65 desktopJ > > > workstations came up with 9 dead-out-of-the-box units - two of which wereL > > > shipped without power supplies, some had power supplies but wires were notcJ > > > connected, and several had no memory chips at all (we paid for 256Mb RAM).o > >dC > > This obviously is not acceptable and is not in keeping with thed "COMPAtible  > > Quality" name. > >rI > > > That's a very poor percentage. (Brought to mind my old Packard Bell  days!)F > > > That along with the more than two-month delay in other shipments (things.I > > > from DLT tapes to universal hard drives) make me think there's moree amissoF > > > than Compaq will let on. But I admit that I could be letting the current K > > > "political" situation of Compaq Corporate color my thinking about itsi > > > operations.  > > >3 > >kG > > Well, I've had a couple of Presarios and was very dissatisfied withp them. I/I > > was thermonuclearly PO'd when the Imitation SuperDisk failed and both  CPQyL > > and Best Buy (from whom I purchased a service contract) blew me off 'cos I I > > had installed a real OS (Win2K) over the squatulent Win98 virus. Bestt BuyaH > > said that the software change invalidated the purchase contract. CPQ saidK > > that the Presario was a consumer product and Win2K was a commercial OS, - > > hence they refused to remedy the problem.   J This would have been kinda tough to do *after* I waltzed into Best Buy andI asked 'em to fix the peecee. They no doubt would have remembered me had I F returned a week later with the same system downgraded to Win98. That'sI assuming that I could have accomplished the downgrade in the absence of am
 floppy drive.   I Point is, I learned my lesson about Best Buy and the $150 3-Year Enhanced L Warranty they offer (and of course try to ram down your throat when you makeE a purchase). I no longer patronize Best Buy and I urge my friends and I clients to consider my experience when they select a consumer electronics- vendor. ;-}    ------------------------------  % Date: Fri, 14 Dec 2001 11:47:08 -0700S* From: "Lorin Ricker" <Lorin@LockTrack.com>) Subject: Re: Crash (SYSDUMP.DMP) questionLC Message-ID: <FKrS7.106022$lV4.16226474@e420r-atl1.usenetserver.com>I   Mark D. Jilson wrote:eK > If you have access to DSNLink there are 2 articles to help you with this.e  A > [OpenVMS] Managing Dumpfiles on VAX & Alpha Systems or ClustersnB > [OpenVMS] How To Check That the Dumpfile Was Mapped at Boot Time  J No, I don't have access to DSNLink, but these two articles sound just like what I need.  ;-(L) Any other way I can access them?  Thanks!A   -- Lorin Ricker   Lorin@LockTrack.comi   ------------------------------  % Date: Fri, 14 Dec 2001 11:58:39 +0100i0 From: Thomas Hahnemann <Thomas.Hahnemann@s-t.de>+ Subject: Re: DEC Alpha 255 - 300 Mhz wanted & Message-ID: <3C19DB5F.380FD75A@s-t.de>  = If the hardware keeps up, you can run a VMS-system for years.nC I would not try to run 365 days/24 hours applications on a Windows = box. =     Jan-Erik Sderholm wrote:= > 7 > Gosh, someone's going to develope *new* SW for VMS !!f< > But wait, you can run Tru64 on that box also, can't you... >  > :-)l >  > Jan-Erik Sderholm.n >  > Thomas Hahnemann wrote:, > >o? > > don't know if these is the right group, but I'm looking foroA > > a DEC Alpha 255 - 300 Mhz or bigger for software develpement.e4 > > It should have a TGA2 or better graphics module. > >m* > > Thanks in advance for hints and offers > >o > > Thomas Hahnemann   ------------------------------  % Date: Fri, 14 Dec 2001 11:59:19 +0100e0 From: Thomas Hahnemann <Thomas.Hahnemann@s-t.de>+ Subject: Re: DEC Alpha 255 - 300 Mhz wanteda& Message-ID: <3C19DB87.148A77CD@s-t.de>  
 good address.    Thanks.    ------------------------------  % Date: Fri, 14 Dec 2001 11:24:51 -0000 8 From: John Macallister <J.Macallister1@physics.ox.ac.uk>+ Subject: RE: DEC Alpha 255 - 300 Mhz wantedoN Message-ID: <35666012DF4CD411BE940090279FA240010BF170@ppnt41.physics.ox.ac.uk>  > >If the hardware keeps up, you can run a VMS-system for years.D >I would not try to run 365 days/24 hours applications on a Windows  >box.   J If the hardware keeps up you can probably run any type of system for yearsC provided the configuration is stable. We have VMS systems which runcJ uninterrupted for very long periods and we have VMS systems which crash or% have to be rebooted fairly regularly.i  K I don't remember my desktop Windows system, which runs continuously becauseaK it hosts long-running applications in addition to normal "office" activity, L ever crashing since August 1997 when it was installed. It has been rebooted,J infrequently, for software installation, hardware upgrades, the occasionalE "problem", etc but that is also my experience with "actively used andi changing" VMS systems.  L By all means praise the good points of VMS but keep an open mind about otherJ options. This news group/mailing list is probably the principal VMS windowD to the computing world. We need to give the impression that we're anI outgoing and forward looking community if we're to promote VMS to others.i   John  B Name: John B. Macallister  E-mail: j.macallister1@physics.ox.ac.uk= Post: Denys Wilkinson Building, Keble Road, Oxford OX1 3RH,UKeA Phone: +44-1865-273388 (direct)  273333 (reception)  273418 (Fax)-   ------------------------------  % Date: Fri, 14 Dec 2001 12:48:39 +0000l% From: Alan Greig <a.greig@virgin.net>C+ Subject: Re: DEC Alpha 255 - 300 Mhz wantedR8 Message-ID: <c1tj1uoru6t7lpjpje3c2a50cml26oambf@4ax.com>  4 On Fri, 14 Dec 2001 11:24:51 -0000, John Macallister( <J.Macallister1@physics.ox.ac.uk> wrote:  K >If the hardware keeps up you can probably run any type of system for yearslD >provided the configuration is stable. We have VMS systems which runK >uninterrupted for very long periods and we have VMS systems which crash oro& >have to be rebooted fairly regularly.  E I have never seen a VMS system crash or need rebooted regularly whereaE the problem was not already fixed by an ECO or could not be diagnosedtD and worked around by Compaq (admittedly Pathworks 5.0 and UCX pushed, this to the limit). This is VMS not Windows.  D If you need to regularly reboot VMS systems or they crash frequentlyA then my first suggestion is that whoever is responsible for their1A system management (sorry if it is you) is not doing their job. IfyD Compaq or your other suppliers cannot fix the problem please post up some more details. > L >I don't remember my desktop Windows system, which runs continuously becauseL >it hosts long-running applications in addition to normal "office" activity,M >ever crashing since August 1997 when it was installed. It has been rebooted,gK >infrequently, for software installation, hardware upgrades, the occasional F >"problem", etc but that is also my experience with "actively used and >changing" VMS systems.e > M >By all means praise the good points of VMS but keep an open mind about otheriK >options. This news group/mailing list is probably the principal VMS windowdE >to the computing world. We need to give the impression that we're anuJ >outgoing and forward looking community if we're to promote VMS to others. >h >Johne >yC >Name: John B. Macallister  E-mail: j.macallister1@physics.ox.ac.ukc> >Post: Denys Wilkinson Building, Keble Road, Oxford OX1 3RH,UKB >Phone: +44-1865-273388 (direct)  273333 (reception)  273418 (Fax) >P >a >B   -- Alan   ------------------------------  % Date: Fri, 14 Dec 2001 14:28:35 -0000s8 From: John Macallister <J.Macallister1@physics.ox.ac.uk>+ Subject: RE: DEC Alpha 255 - 300 Mhz wantedlN Message-ID: <35666012DF4CD411BE940090279FA240010BF171@ppnt41.physics.ox.ac.uk>  F >I have never seen a VMS system crash or need rebooted regularly whereF >the problem was not already fixed by an ECO or could not be diagnosedE >and worked around by Compaq (admittedly Pathworks 5.0 and UCX pusheda- >this to the limit). This is VMS not Windows.   E Since around 1992 we've had the following scenario on many occasions.O   Running VMS x.y .u Using package P ..K P (hardware or software) causes VMS system crashes or "hangs". P is a third. party product." DEQ claim the problem lies with P.. P's supplier claims the problem lies with DEQ.< DEQ may investigate if VMS is brought up to version x+n.y+m.0 P doesn't work at all under VMS version x+n.y+m.: Many other packages do not work with VMS version x+n.y+m .I We have to stay with VMS x.y until all required software "works" with VMSnJ x+n.y+m or, as is normally the case now, we have found a non-VMS solution.   John  B Name: John B. Macallister  E-mail: j.macallister1@physics.ox.ac.uk= Post: Denys Wilkinson Building, Keble Road, Oxford OX1 3RH,UKnA Phone: +44-1865-273388 (direct)  273333 (reception)  273418 (Fax)r   ------------------------------  + Date: Fri, 14 Dec 2001 15:34:33 +0000 (UTC)m From: david20@alpha1.mdx.ac.uk+ Subject: RE: DEC Alpha 255 - 300 Mhz wanted/+ Message-ID: <9vd669$dt7$1@aquila.mdx.ac.uk>r   In article <35666012DF4CD411BE940090279FA240010BF171@ppnt41.physics.ox.ac.uk>, John Macallister <J.Macallister1@physics.ox.ac.uk> writes:eG >>I have never seen a VMS system crash or need rebooted regularly whererG >>the problem was not already fixed by an ECO or could not be diagnosedtF >>and worked around by Compaq (admittedly Pathworks 5.0 and UCX pushed. >>this to the limit). This is VMS not Windows. >eF >Since around 1992 we've had the following scenario on many occasions. >N >Running VMS x.y . >Using package P .L >P (hardware or software) causes VMS system crashes or "hangs". P is a third >party product.s# >DEQ claim the problem lies with P.i/ >P's supplier claims the problem lies with DEQ.i= >DEQ may investigate if VMS is brought up to version x+n.y+m.o1 >P doesn't work at all under VMS version x+n.y+m.t; >Many other packages do not work with VMS version x+n.y+m .lJ >We have to stay with VMS x.y until all required software "works" with VMSK >x+n.y+m or, as is normally the case now, we have found a non-VMS solution.b >e  K This is a potential problem with any system running thirdparty software or 0$ having attached thirdparty hardware.@ In my experience it is best solved by getting out of the middle.K Get the VMS engineers talking directly to the thirdparty product engineers. J The VMS engineers are usually quite happy to do this. So long as you have E maintenance / prior version support then I would not expect DEQ to beN forcing you to upgrade.a  
 David Webb VMS and Unix team leader CCSS Middlesex University n   ------------------------------    Date: 14 Dec 2001 17:03:10 +0100G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de>p+ Subject: Re: DEC Alpha 255 - 300 Mhz wantedoH Message-ID: <y4n10lkcw1.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  : John Macallister <J.Macallister1@physics.ox.ac.uk> writes:   > Running VMS x.y .o > Using package P .aM > P (hardware or software) causes VMS system crashes or "hangs". P is a third7 > party product.$ > DEQ claim the problem lies with P.  J As long as P does not contain non-user-mode code, DEQ has no reason at all! to put the blame on anybody else.<   	Jan   ------------------------------  % Date: Fri, 14 Dec 2001 15:42:32 +0000n% From: Alan Greig <a.greig@virgin.net>l+ Subject: Re: DEC Alpha 255 - 300 Mhz wanted 8 Message-ID: <ir6k1uofmnmnj7q7odo7rnhl5jvi1nrut2@4ax.com>  4 On Fri, 14 Dec 2001 14:28:35 -0000, John Macallister( <J.Macallister1@physics.ox.ac.uk> wrote:    F >Since around 1992 we've had the following scenario on many occasions. >v >Running VMS x.y . >Using package P .L >P (hardware or software) causes VMS system crashes or "hangs". P is a third >party product.e# >DEQ claim the problem lies with P.W/ >P's supplier claims the problem lies with DEQ.d= >DEQ may investigate if VMS is brought up to version x+n.y+m.u1 >P doesn't work at all under VMS version x+n.y+m.y; >Many other packages do not work with VMS version x+n.y+m .o  = Given the date of 1992 I'll assume this is probably a VAX and E DEC/Compaq have done everything they can to avoid breaking older apps 6 under later versions of VAX/VMS. You might need to runC register_privileged_image.com (if I have the name right) but that'sr@ normally about it. Unless the app tries to check the VMS version@ itself of course. Until we turned off our production VAX systemsF (moved to Alpha) we ran several products under VMS 7.1 (for DEC/CompaqF support purposes) which were qualified for 5.5-2. I realize this mightD not apply to you but have you actually checked to see if P might run& under a current supported VAX release?  B If you must run an old unsupported version of VMS with unsupportedE third party software then that understandably puts you in a less thanlC ideal position but it's a bit much to then post to c.o.v that VAXesf@ regularly crash and Compaq can't fix it without giving the extra details you have nw provided.o  J >We have to stay with VMS x.y until all required software "works" with VMSK >x+n.y+m or, as is normally the case now, we have found a non-VMS solution.k  0 The latter unfortunately all too often the case/   >n >Johnl >BC >Name: John B. Macallister  E-mail: j.macallister1@physics.ox.ac.uks> >Post: Denys Wilkinson Building, Keble Road, Oxford OX1 3RH,UKB >Phone: +44-1865-273388 (direct)  273333 (reception)  273418 (Fax) >a >n   -- Alan   ------------------------------  % Date: Fri, 14 Dec 2001 16:24:05 -0000 8 From: John Macallister <J.Macallister1@physics.ox.ac.uk>+ Subject: RE: DEC Alpha 255 - 300 Mhz wantednN Message-ID: <35666012DF4CD411BE940090279FA240010BF173@ppnt41.physics.ox.ac.uk>  ; >Given the date of 1992 I'll assume this is probably a VAX a  L Just to clarify. I am not referring to one system but to many of the systemsH we've had from 1992 until the present day. The comments refer to VAX andK Alpha. I've also bypassed the version checks in installation procedures andeK sometimes things work well but the insurmountable problems to which I refer K usually involve device drivers and other system-linked components for whichh* the necessary build code is not available.  2 >If you must run an old unsupported version of VMS  J Yes, we have to run certain versions of software in order to be compatibleI with colleagues and compatible over a time span which may be a few years.i   John    B Name: John B. Macallister  E-mail: j.macallister1@physics.ox.ac.uk= Post: Denys Wilkinson Building, Keble Road, Oxford OX1 3RH,UKeA Phone: +44-1865-273388 (direct)  273333 (reception)  273418 (Fax)5   ------------------------------  % Date: Fri, 14 Dec 2001 10:16:30 +0100y, From: Theo Jakobus <Theo.Jakobus@iaf.fhg.de>' Subject: Re: DECC$TIME multiply defined ) Message-ID: <3C19C36E.9000904@iaf.fhg.de>    Craig A. Berry wrote:u  4 > In article <gk5S7.553$BK1.14958@news.cpqcorp.net>,6 >  hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) wrote: >  > 9 >>In article <3C185C64.6010003@iaf.fhg.de>, Theo Jakobus c# >><Theo.Jakobus@iaf.fhg.de> writes:l6 >>:I started to build GNU WGET and got a LINK warning: >>..5 >>:%LINK-W-MULDEF, symbol DECC$UTIME multiply definedoE >>:         in module DECC$SHR file SYS$COMMON:[SYSLIB]DECC$SHR.EXE;1r >>..5 >>:I'm using: Compaq C V6.4-008 on OpenVMS Alpha V7.3g >>D >>  And the compiler believes your code is defining a "time" symbol.E >>  Either don't do that (usually best), or use the /PREFIX "except" 9B >>  mechanism to resolve the time symbol against the local symbol. >> > I > Actually (and contrary to the subject line) it looks like your code is .I > defining a "utime" symbol, which was not available in the C RTL before 2G > VMS 7.3.  Thus the same code probably worked fine until recently but nE > now gets the collision you are seeing.  I'm not familiar with WGET mD > specifically, but it probably has a homegrown utime() for VMS (or G > perhaps just a stub that says no-can-do).  You can modify the prefix eJ > list but the change should be version specific so prior versions of VMS  > still see the utime symbol.  > I > The principle of multiple version support still holds if you choose to cC > modify the code rather than the compile command.  An incantation t5 > similar to the following (untested) one might work:e > 5 > #if !defined(__CRTL_VER) || (__CRTL_VER < 70300000)e > # > [ home-made utime() replacement ]l >  > #endif >     ; I included the if/endif and no warnings no error showed up.n   Thanks to all of you !!!  * To Steven M. Schweda: I got the WGET from 5 http://nucwww.chem.sunysb.edu/info/software.htmlx#Topd     -- h  ; *********************************************************** ; *                                                         *h; *  Theo Jakobus                                           *r; *  Fraunhofer-Institut fuer Angewandte Festkoerperphysik  *s; *  Tullastr. 72                                           *h; *  D-79108 Freiburg                                       *d; *  Germany                                                *a; *  Phone:   +49-(0)761-5159-325                           *n; *  FAX :    +49-(0)761-5159-200                           *t; *  e-mail:  Theo.Jakobus@iaf.fhg.de                       *l; *  http://www.iaf.fhg.de                                  *t; *                                                         * ; ***********************************************************    ------------------------------  % Date: Fri, 14 Dec 2001 10:15:19 +0100e, From: Theo Jakobus <Theo.Jakobus@iaf.fhg.de>' Subject: Re: DECC$TIME multiply definedc) Message-ID: <3C19C327.7080902@iaf.fhg.de>Q   Craig A. Berry wrote:a  4 > In article <gk5S7.553$BK1.14958@news.cpqcorp.net>,6 >  hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) wrote: >  > 9 >>In article <3C185C64.6010003@iaf.fhg.de>, Theo Jakobus y# >><Theo.Jakobus@iaf.fhg.de> writes:e6 >>:I started to build GNU WGET and got a LINK warning: >>..5 >>:%LINK-W-MULDEF, symbol DECC$UTIME multiply definedsE >>:         in module DECC$SHR file SYS$COMMON:[SYSLIB]DECC$SHR.EXE;1m >>..5 >>:I'm using: Compaq C V6.4-008 on OpenVMS Alpha V7.3B >>D >>  And the compiler believes your code is defining a "time" symbol.E >>  Either don't do that (usually best), or use the /PREFIX "except" eB >>  mechanism to resolve the time symbol against the local symbol. >> > I > Actually (and contrary to the subject line) it looks like your code is -I > defining a "utime" symbol, which was not available in the C RTL before oG > VMS 7.3.  Thus the same code probably worked fine until recently but DE > now gets the collision you are seeing.  I'm not familiar with WGET iD > specifically, but it probably has a homegrown utime() for VMS (or G > perhaps just a stub that says no-can-do).  You can modify the prefix tJ > list but the change should be version specific so prior versions of VMS  > still see the utime symbol.c > I > The principle of multiple version support still holds if you choose to  C > modify the code rather than the compile command.  An incantation o5 > similar to the following (untested) one might work:  > 5 > #if !defined(__CRTL_VER) || (__CRTL_VER < 70300000)h > # > [ home-made utime() replacement ]A >  > #endif >     ; I included the if/endif and no warnings no error showed up.r   Thanks to all of you !!!  * To Steven M. Schweda: I got the WGET from 5 http://nucwww.chem.sunysb.edu/info/software.htmlx#Top      -- k  ; ***********************************************************w; *                                                         *l; *  Theo Jakobus                                           * ; *  Fraunhofer-Institut fuer Angewandte Festkoerperphysik  *t; *  Tullastr. 72                                           *0; *  D-79108 Freiburg                                       *e; *  Germany                                                *c; *  Phone:   +49-(0)761-5159-325                           *-; *  FAX :    +49-(0)761-5159-200                           *0; *  e-mail:  Theo.Jakobus@iaf.fhg.de                       *:; *  http://www.iaf.fhg.de                                  *4; *                                                         *-; ***********************************************************r   ------------------------------  % Date: Fri, 14 Dec 2001 09:07:01 -0500p- From: "www.islandco.com" <sales@islandco.com>D/ Subject: Disposing of: DS10L for less then 2900./ Message-ID: <u1k1qrbsep2fff@news.supernews.com>a   DS10Le
 EV6 466MHZ 128MB MEMORY 9GB ULTRA 2 SCSI DISK  UW SCSI CONTROLLER
 DUAL ETHERNETb2 IN ALMOST NEW CONDITION WITH OVER 1.5YRS OF COMPAQ ON SITE SERVICEt   PRICE IS $2850  	 Sales Dpti Island Computers US Corporationy 2700 Gregory Streetn	 Suite 180o Savannah GA 31404  Tel: 912 447 6622t Fax: 912 201 0096  sales@islandco.com www.islandco.com' http://www.islandco.com/legal-email.htmy   ------------------------------   Date: 14 Dec 2001 15:07:03 GMT= From: jlw@psulias.psu.edu (j.lance wilkinson, (814) 865-1818) N Subject: Re: From within a CGI: sending an https method=post request elsewhere, Message-ID: <9vd4in$1ccm@r02n01.cac.psu.edu>  U In article <3C19946B.7DB1ECD4@gmx.ch>, Didier Morandi <Didier.Morandi@gmx.ch> writes:n+ >"j.lance wilkinson, (814) 865-1818" wrote:  >> pI >> I have a protected (via https) script that needs to change a password.i  * >You did not say which WEB server you run. >oQ >I think that WASD does HTTPS very well, and of course WASD is THE WEB server forr >(advanced :-) DCL programmers.o    @ 	I don't see how the server that I run is relevant to the issue.F         I'm running CSWS, but the problem is how to establish an HTTPSI         connection *from within the DCL CGI script to ANOTHER web server*n  ? 	The server running MY script should be irrelevant.  The server B 	running the target script on the other machine, the one expectingA 	HTTPS as the protocol to receive the POST method script data, istB 	running on some AIX platform.  WASD isn't relevant there, either.  M +-"Never Underestimate the bandwidth of a station wagon full of mag tapes"--+eN | J.Lance Wilkinson ("Lance")            InterNet:  Lance.Wilkinson@psu.edu | M | Systems Design Specialist - Lead       AT&T:      (814) 865-1818          |gM | Library Computing Services             FAX:       (814) 863-3560          |eM | E3 Paterno Library                     "I'd rather be dancing..."         |rM | Penn State University         A host is a host from coast to coast,       | M | University Park, PA 16802     And no one will talk to a host that's close |iM | <postmaster@psulias.psu.edu>  Unless the host that isn't close            |rM | VMS GopherMeister             Is busy, hung or dead.                      | M +------"He's dead, Jim. I'll get his tricorder. You take his wallet."-------+ 9                 [apologies to DeForest Kelley, 1920-1999]e3 <A Href="http://perdita.lcs.psu.edu">home page</a> yJ <a Href="http://perdita.lcs.psu.edu/junkdec.htm">junk mail declaration</a>   --	       /"\ #       \ /     ASCII RIBBON CAMPAIGNt!        X        AGAINST HTML MAIL7	       / \s   ------------------------------  # Date: Fri, 14 Dec 2001 16:28:16 GMTi+ From: "Andy Proctor" <aproctor@hotmail.com>b Subject: Re: FTP Servers5 Message-ID: <1008347345.441905@ananke.eclipse.net.uk>s  ? "Hoff Hoffman" <hoffman@xdelta.zko.dec.nospam> wrote in messagea, news:CkcS7.572$BK1.15464@news.cpqcorp.net...F > In article <1008291635.862391@ananke.eclipse.net.uk>, "Andy Proctor" <aproctor@hotmail.com> writes: > :Net: 4 or 5 PC's, 2 Alphaso > :Alpha with problem: > :255/233, VMS 7.1, UCX 4.10 > :Other Alpha is a new DS10, runs like a dream. >iK >   The AlphaServer DS10 is probably running V5.0A or V5.1 with ECO, right?n >KL > :The problem is that the FTP server takes about 90 seconds to respond to a > :connection request. > I >   Is there a chance you can get to V5.1 with ECO?  (V4.1 is really old,1I >   and the typical minimum release for OpenVMS V7.* is V5.0 -- V5.1 withu  >   ECO is the current release.) >nH >   Also check the turn-around for a DNS/bind look-up, as the FTP serverK >   tries to find out who is connecting into it.  Check the DNS/bind servery< >   throughput, and consider entering the host name locally: > ( >     set host NAME /address=ww.xx.yy.zz  L I'll try this, thanks Hoff, yes there is a BIND server and this makes sense.D I'll try over the next week or so to help the customer through this.   Cheers   Andy   ------------------------------  % Date: Fri, 14 Dec 2001 11:54:26 +0000 % From: Alan Greig <a.greig@virgin.net>.< Subject: Gartner again suggests it expects VMS to be dropped8 Message-ID: <eqpj1u04fr9ij742mbo8000vjd9pr4f366@4ax.com>  : http://www3.gartner.com/resources/103100/103104/103104.pdf  = "Our advice for customers of both companies remains the same:iC  Tactical purchases and upgrades remain sound. Long-term strategici commitments, however,tC should be confined to those products that Gartner has identified asV strategic, including: 
 - HP printersa) - Compaq Proliant servers.- HP/UX serversx. - Compaq StorageWorks storage for the midrange  - HP XP storage for the high-endA  Investments in PCs and PDAs from either vendor are safe (due to- minor technical differentiationr( and rapid product cycles, respectively).<  Services are unaffected by the status of the acquisition." -- Alan   ------------------------------  + Date: Fri, 14 Dec 2001 12:41:25 +0100 (MET)49 From: Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com>s# Subject: Re: global foreign command ; Message-ID: <01KBUX7MAL9Q9138XQ@sysdev.deutsche-boerse.com>o  . > nitpick   command :== "$full:[spec]file.exe"  I Nitpick:  one needs EITHER the : OR the ".  Both don't hurt, but are not aE necessary.  (Leaving out the quotes will automatically uppercase it, ME which is probably better since otherwise it will get uppercased when   parsed anyway.).   ------------------------------  # Date: Fri, 14 Dec 2001 11:53:58 GMTa= From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)t# Subject: Re: global foreing commandP0 Message-ID: <00A067F4.918E9F27@SendSpamHere.ORG>  ` In article <u1iularnugk657@corp.supernews.com>, Phillip <nntpmouse@prism.datastacks.com> writes:B >I have figured out how to set up foreing commands with the cmd :=J >full:[spec]file.exe at the DCL command line, but I have yet to figure outJ >how to figure out how to add it globaly for all users. I saw something toF >the effect of using a `CLD' file, but am at a lose on how to do that. >Help from anyone? >r >-Phillip (the newbie)   Create CMD.CLD:n   DEFINE VERB cmds   IMAGE full:[spec]file.exef   CLIFLAGS (FOREIGN)    6 $ SET COMMAND/TABLE=SYS$COMMON:[SYSLIB]DCLTABLES.EXE -2   /OUTPUT=SYS$COMMON:[SYSLIB]DCLTABLES.EXE CMD.CLD2 $ INSTALL REPLACE SYS$COMMON:[SYSLIB]DCLTABLES.EXE     --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COMe            nJ   "And of course, I'm a genius, so people are naturally drawn to my fiery I   intellect.  Their admiration overwhelms their envy!" -- Calvin & Hobbes.   ------------------------------  + Date: Fri, 14 Dec 2001 08:15:38 +0100 (MET)o& From: Rudolf Wingert <win@fom.fgan.de>  Subject: Re: help [[  MCR NCP ]]6 Message-ID: <200112140715.IAA11300@sinet1.fom.fgan.de>   Hello,  = you have to configure your network. The best way to do so is:wB execute the NET$CONFIG (or is it called NTCONFIG I don't remember)@ command procedure. This procedure looks for all existend networkB adapters and creates the specific entries within the NCP database.   Best regards Rudolf Wingertn   ------------------------------  % Date: Fri, 14 Dec 2001 12:19:56 -0500n5 From: "Fred Kleinsorge" <kleinsorge@star.zko.dec.com>D+ Subject: Re: HP Foundations - let them knowi2 Message-ID: <qAqS7.604$BK1.15866@news.cpqcorp.net>  A David J. Dachtera wrote in message <3C18381E.29876608@fsi.net>...c >Rob Young wrote: 	 >> [snip]aI >>         Don't be too alarmed by "sightings" on a Dead chip... it meansg >>         nothing.c >eG >Did I miss something, or were these "sightings" not on the current IPFs3 >porting platforms in the possession of OVMS Engr.?e >i    J The problem (and frankly, I don't know what it was) has been fixed in PAL.J Want to know how many things on Alpha were fixed in PAL (if not permanent,
 temporarily)?y  K Making chips is like making sausage... you might not want to know what doese into it.   ------------------------------  % Date: Fri, 14 Dec 2001 14:42:11 +0100y( From: "Pawe Grecki" <gorpa@kki.net.pl>, Subject: Huge file compression - help needed( Message-ID: <9vcvk3$jla$1@leo.gazeta.pl>   Hi all.   D I have some AXP servers (AS4100's and ES40), OpenVMS 7.2-1h1 and Rdb Database 7.06.G I have a problem with ziping a big files (rdb databases backups *.rbf). K I used for it  Zip 2.3 with -9 parameter but when the output temporary files< took over 2 GB of space (over 4 100 000 blocks) zip crashed.K It means that probably zip is an 32-bit compiled program and cannot addressn more than 2GB.  " Is there anybody who can help me ?J Maybe someone knows something about 64-bit zip or other compress program ?< Or about program that can cut big file and glue it back ???.   Regardst  
 Pawel Goreckio OpenVMS and Rdb admin.   ------------------------------  % Date: Fri, 14 Dec 2001 16:08:53 +0100n= From: Jan-Erik =?iso-8859-1?Q?S=F6derholm?= <noone@dummy.com>d0 Subject: Re: Huge file compression - help needed) Message-ID: <3C1A1605.CF96CFA3@dummy.com>   5 No help with ZIP'ing files > 2GB, but just would likec; to note that ZIP'ing Rdb Backups isn't supported by Oracle..: Having sad that, I myself hav never had *any* problem with ZIP'ed RBF's...O   Jan-Erik Sderholm.e   ------------------------------  + Date: Fri, 14 Dec 2001 16:22:31 +0100 (MET) 9 From: Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com>10 Subject: Re: Huge file compression - help needed; Message-ID: <01KBV4XPEX8Y9138XQ@sysdev.deutsche-boerse.com>w  $ > No help with ZIP'ing files > 2GB,   - Right, an internal (documented) limit of ZIP.    > but just would like'= > to note that ZIP'ing Rdb Backups isn't supported by Oracle.   D How could they?  ZIP is a freeware (or whatever) package over which  Oracle has no direct control.e  < > Having sad that, I myself hav never had *any* problem with > ZIP'ed RBF's...p   I'm also a satisfied ZIP user.   ------------------------------  % Date: Fri, 14 Dec 2001 16:39:29 +0100 = From: Jan-Erik =?iso-8859-1?Q?S=F6derholm?= <noone@dummy.com>h0 Subject: Re: Huge file compression - help needed( Message-ID: <3C1A1D31.7C0EAE2@dummy.com>  = Well, I ment that *if* you call Oracle and they find out thato7 you have put your Rdb backup files throught a ZIP/UNZIPe8 cycle, that *could* be a problem with there ability/will5 to help. I didn't ment the ZIP/UNZIP process as such. < That's probably also true for any file-mangling tool such as8 VMSTAR. It's up to you to verify that whatever you do to= your Rdb backup's (that's outside of what Oracle can support)e is actualy working.y  @ Now, for the original problem. Creating multiple RBF files (from/ different storage areas) could be one solution.0  = I'd actualy take a major re-think of the whole backup/restore5
 strategy !   Jan-Erik Sderholm.        Phillip Helbig wrote:( > % > > No help with ZIP'ing files > 2GB,< > / > Right, an internal (documented) limit of ZIP.. >  > > but just would like ? > > to note that ZIP'ing Rdb Backups isn't supported by Oracle.% > E > How could they?  ZIP is a freeware (or whatever) package over whichE > Oracle has no direct control.C > > > > Having sad that, I myself hav never had *any* problem with > > ZIP'ed RBF's...h >   > I'm also a satisfied ZIP user.   ------------------------------  % Date: Fri, 14 Dec 2001 12:30:08 -0500P5 From: "Fred Kleinsorge" <kleinsorge@star.zko.dec.com>b' Subject: Re: Inquirer: OpenVMS on DS20Lc2 Message-ID: <_JqS7.606$BK1.15878@news.cpqcorp.net>  @ David Mathog wrote in message <3C18DBCA.E524D276@caltech.edu>... >"Terry C. Shannon" wrote: >MH >> The biggest problem VMS faces right now (IMHO) is the availability of" >> low-cost development platforms. >'= >Right now???  That makes it sound like a new development but = >it's been a huge problem for at last 15 years!!!  The nearlyy9 >total obliteration of OpenVMS in academia and most otherc7 >computing arenas was (and still is) a direct result of 9 >OpenVMS software and hardware always costing (much) morel >than the competition. >     L And guess what.  There were no plans for any new small Alphas you might haveK considered for a desktop or even a desk side.  The smallest EV7 platform isi@ a dual processor server.  The EV8 would have had 64kb pages onlyI (translation: ~2GB minimum memory configurations are what we envisioned).nJ Do you know what *my* personal WS is today?  A DS20E.  A bit too noisy forC anyone that hasn't already lost a fair percentage of their hearing.s  L At least Itanium provides the possibility of something smaller, and cheaper.  @ >> assuming IPF achieves the exalted "industry standard" status. > : >And that's an increasingly dubious assumption given AMD's7 >increasing market share against Intel in the x86 spaceh8 >and the advent in the near future of the Hammer series.: >Also, is it realistic to expect that Intel will sell IA648 >cpus without the price markup that it applies to Xeons?= >The only way that I see IA64 becoming price attractive is if > >AMD pushes Intel so hard that they have no choice but to sell@ >this CPU for less.  Kind of like what happened with the regular >(non Xeon) PIII and PIV.a >h    J Nobody has presented a credible case for how Hammer gets beyond IA32 mode,& besides some niche Linux applications.   ------------------------------  + Date: Fri, 14 Dec 2001 18:41:55 +0100 (MET) 9 From: Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com><' Subject: Re: Inquirer: OpenVMS on DS20LC; Message-ID: <01KBV9MUZL029138XQ@sysdev.deutsche-boerse.com>h  I > And guess what.  There were no plans for any new small Alphas you mightqF > have considered for a desktop or even a desk side.  The smallest EV7I > platform is a dual processor server.  The EV8 would have had 64kb pagesoC > only (translation: ~2GB minimum memory configurations are what weNG > envisioned). Do you know what *my* personal WS is today?  A DS20E.  A H > bit too noisy for anyone that hasn't already lost a fair percentage of > their hearing. o > E > At least Itanium provides the possibility of something smaller, ando > cheaper. f  G Presumably, this was the plan before talk of the merger, and before the G death of ALPHA.  What was the reasoning behind it?  I always consideredlF it a strength of VMS that it ran on everything from very small to veryG large machines.  For various reasons (purchase price, loudness, runninglE costs), many people don't develop on really big systems.  Also, therekH are some applications which could make use of a fast CPU but which don't need a lot of memory.   F Of course, one could develop on an older, slower ALPHA, but this still> might have the disadvantage of being slightly different if theE development machine is also used to compile, with no compilers on thes production machine.    ------------------------------  % Date: Fri, 14 Dec 2001 13:19:43 -0500l5 From: "Fred Kleinsorge" <kleinsorge@star.zko.dec.com>a' Subject: Re: Inquirer: OpenVMS on DS20L 2 Message-ID: <ssrS7.614$BK1.16039@news.cpqcorp.net>   Phillip Helbig wrote in message|2 <01KBV9MUZL029138XQ@sysdev.deutsche-boerse.com>...J >> And guess what.  There were no plans for any new small Alphas you mightG >> have considered for a desktop or even a desk side.  The smallest EV7eJ >> platform is a dual processor server.  The EV8 would have had 64kb pagesD >> only (translation: ~2GB minimum memory configurations are what weH >> envisioned). Do you know what *my* personal WS is today?  A DS20E.  AI >> bit too noisy for anyone that hasn't already lost a fair percentage ofn >> their hearing.d >>F >> At least Itanium provides the possibility of something smaller, and >> cheaper.  >7H >Presumably, this was the plan before talk of the merger, and before theH >death of ALPHA.  What was the reasoning behind it?  I always consideredG >it a strength of VMS that it ran on everything from very small to very H >large machines.  For various reasons (purchase price, loudness, runningF >costs), many people don't develop on really big systems.  Also, thereI >are some applications which could make use of a fast CPU but which don't* >need a lot of memory. >*    I Well.  I suppose it is because it is the Alpha Server business that makes:E the money.  The Alpha workstation business effectively folded.  AlphaD? Servers itself is focused on 1) performance, 2) performance, 3)fL scaleability, 4) performance, 5) reliability.  Why?  Because performance was Alpha's differentiation.  L EV7 has no other purpose that to provide high-performance, and scale to veryG large systems.  It is not focused on the uniprocessor market.  You want7H something on the desktop, think EV68, but not EV7 or EV8, or EV9, or any other processor on the roadmap.c  J From I think a non-VMS perspective, anything small enough to be on or next0 to a desktop, is something for a Intel solution.  C Do I agree with that?  Not from a VMS, or Tru64 perspective.  WhilejJ certainly big systems is where we make our money, you still need the small, form factor ones to sell the whole solution.  J Itanium has the potential of providing us a lower-cost platform than where Alpha was heading.   ------------------------------  % Date: Fri, 14 Dec 2001 10:43:40 -0800s# From: "Tom Linden" <tom@kednos.com>o' Subject: RE: Inquirer: OpenVMS on DS20L 9 Message-ID: <CIEJLCMNHNNDLLOOGNJIAEOIDLAA.tom@kednos.com>o   > -----Original Message-----< > From: Fred Kleinsorge [mailto:kleinsorge@star.zko.dec.com]* > Sent: Friday, December 14, 2001 10:20 AM > To: Info-VAX@Mvb.Saic.Com ) > Subject: Re: Inquirer: OpenVMS on DS20LS >  > ! > Phillip Helbig wrote in messageG4 > <01KBV9MUZL029138XQ@sysdev.deutsche-boerse.com>...L > >> And guess what.  There were no plans for any new small Alphas you mightI > >> have considered for a desktop or even a desk side.  The smallest EV7 L > >> platform is a dual processor server.  The EV8 would have had 64kb pagesF > >> only (translation: ~2GB minimum memory configurations are what weJ > >> envisioned). Do you know what *my* personal WS is today?  A DS20E.  AK > >> bit too noisy for anyone that hasn't already lost a fair percentage of& > >> their hearing.8 > >>H > >> At least Itanium provides the possibility of something smaller, and
 > >> cheaper.  > >tJ > >Presumably, this was the plan before talk of the merger, and before theJ > >death of ALPHA.  What was the reasoning behind it?  I always consideredI > >it a strength of VMS that it ran on everything from very small to very J > >large machines.  For various reasons (purchase price, loudness, runningH > >costs), many people don't develop on really big systems.  Also, thereK > >are some applications which could make use of a fast CPU but which don'tl > >need a lot of memory. > >  >o >iK > Well.  I suppose it is because it is the Alpha Server business that makes G > the money.  The Alpha workstation business effectively folded.  AlphacA > Servers itself is focused on 1) performance, 2) performance, 3)t> > scaleability, 4) performance, 5) reliability.  Why?  Because > performance was  > Alpha's differentiation. >1@ > EV7 has no other purpose that to provide high-performance, and > scale to verysI > large systems.  It is not focused on the uniprocessor market.  You wantaJ > something on the desktop, think EV68, but not EV7 or EV8, or EV9, or any! > other processor on the roadmap.6  K So if you are going to continuing producing desktops based on EV68, why not:J EV7, it is only a chip and the incremental cost to produce a new board for itG (if it is even required) is small indeed.  It occurs to me that Digitalh alwaysK had a difficulty with the concept of modular, reusable components.  I mean,i thinktI back to the VAXes, almost every one had a different memory module, not to. mention  all the other pieces.a >eL > From I think a non-VMS perspective, anything small enough to be on or next2 > to a desktop, is something for a Intel solution.  L There certainly are advantages to this approach,  but you will in that event needE to build a fair amount of software (granted some can be acquired from  others, even free,E like putty, which works OK from W2K) to provide good connectivity and  integration.1 And what about security?  Lots of backdoors here.f >eE > Do I agree with that?  Not from a VMS, or Tru64 perspective.  WhilewL > certainly big systems is where we make our money, you still need the small. > form factor ones to sell the whole solution. >2L > Itanium has the potential of providing us a lower-cost platform than where > Alpha was heading. >d >p >  >s   ------------------------------  % Date: Fri, 14 Dec 2001 10:59:55 +0000.% From: Alan Greig <a.greig@virgin.net> , Subject: Re: More about Alpha and the merger8 Message-ID: <12kj1ucjup8d9j2bkt1q2ecqiqepqpd54m@4ax.com>  . On Fri, 14 Dec 2001 06:32:15 GMT, "Duane Sand"" <Duane.Sand@mindspring.com> wrote:     >t: >I believe the axe was already falling on Alpha before the@ >merger was contemplated, not vice versa.  Others will doubtless >prefer grander conspiracies.r  E Carly said in a recent interview that she first floated the idea of amA merger with Compaq internally within HP a couple of years ago ( a F search of  The Register or The Inquirer should find the reference) andD Curly confirms that he has had ongoing wide ranging discussions with? Carly since 1999 with them just getting closer and closer. ThisiF suggests that almost from the day  Capellas took over as CEO he was inF bed with Carly. It was also around this period he took the decision to cancel Alpha/NT. o  D What I find compelling is the repeated statements by Carly and CurlyD at the merger announcement that they could not recall exactly when aA merger was first suggested. They know they have something to hides4 from, at least, a PR perspective if not a legal one.  F The closer you get to  the Alpha/Intel/HP business the more it smells.A The day Compaq EOLd Alpha/NT was also just a couple of days afteraB Microsoft and Intel first publicly demonstrated Windows booting onF IA64. Not conclusive but again (to me) hints that Capellas had decided( IA64 was the way forward and not Alpha.   C Also around  the time Compaq killed Alpha/NT it had been  announced C that Tru64 was to be ported to IA64. I posted up at the time that ItB thought the announcements could add up to the end of Alpha and theD eventual end of VMS: Windows was safe on Intel; Tru64 was to be safeF on Intel. So I asked Compaq (formally) why, of the three current AlphaD operating systems, only VMS would not be on IA64 - which would leaveC VMS stranded should Alpha be dropped. In response Compaq wrote me aAE letter saying they were terminating the Tru64 port  which should showLA me they had faith in Alpha. On the strength of this statement and D phone calls from Marcello I released a PO for $250,000 for Alpha VMSF hardware and software. I currently have quotes in for over one millionC dollars of Alpha/VMS  hardware and software and am awaiting project-E approval (or otherwise...) Although I am vocally anti current  Compaqe- management I continue to push VMS internally.e  D So yes, in my opinion,  the real decision to kill Alpha preceded the? HP merger announcement by some time but Carly, Curly and Wintelo5 pre-programmed the destination at least two years agot  9 >-- Duane Sand, not speaking for past or future companies     D Eckhard Pfeiffer would be interesting to talk to. Terry, any chance?  > After note: Just as I was about to post this the spell-checker? suggested I replace Eckhard with "Packard". It's all clear now!e   -- Alan   ------------------------------  # Date: Fri, 14 Dec 2001 14:20:12 GMTc4 From: "Terry C. Shannon" <terryshannon@mediaone.net>, Subject: Re: More about Alpha and the merger= Message-ID: <wUnS7.12473$Sj1.7098273@typhoon.ne.mediaone.net>.  > "John McLean" <mcleanj@swissonline.delete.ch> wrote in message/ news:3C199ADC.368AB2BC@swissonline.delete.ch...g >> >  > "Terry C. Shannon" wrote:s > >eB > > "John McLean" <mcleanj@swissonline.delete.ch> wrote in message3 > > news:3C191AC3.8A5AE685@swissonline.delete.ch...h > >bH > > So, now which looks the more plausible reason for Alpha's departure?J > > Compaq's stated justifications .or the hypothesis that it was done for > > the merger ? > >sJ > > Based on the information available in the public domain it's difficultL > > (well, in my opinion, it's difficult) to determine whether the merger orH > > Compaq's financial analysis was the proximate cause of the decision. > >eL > > And if, the latter, what are your impressions of the integrity of Compaq > > ?? > >0J > > If the latter, my impression of the integrity of Compaq will adopt the glidegL > > characteristics of a rock. I'm reluctant to make such an assertion since ImH > > simply don't have enough information on what actually went on in the > > boardrooms.i >rG > Agreed.  We certainly don't know and my theory is only a theory untiloJ > proven otherwise ... and besides the CPQ board didn't approve the mergerG > for several weeks, apparently because they were dissatisfied with thet) > original terms that C & C put together.b > G > And according a recent source (which I must check), HP held its first-J > merger discussions with Compaq on June 22 ... and the announcement about > Alpha was on June 25th.?  H Interesting timing... the Alpha announcement was 25 June, I daresay thatL less than 5 percent of the folks at CPQ were aware of the Trees announcement on 22 June.l   > H > I somehow don't believe that HP simply knocked on the door one day andF > said "We want to talk about a merger and we want to talk right now".B > These things would be arranged at least 4 to 6 weeks in advance.D > Agendas and topics for discussion would arranged, just so that theJ > principals could have the facts to hand at the meeting.  I would be veryI > surprised if the issue of two unixes and future of Alpha - as a pair ofZ3 > major stumbling blocks - were not on that agenda.d >i >  >Z
 > John McLeanu   ------------------------------  % Date: Fri, 14 Dec 2001 08:50:43 -0800e' From: David Mathog <mathog@caltech.edu>(, Subject: Re: More about Alpha and the merger+ Message-ID: <3C1A2DE3.6F682F88@caltech.edu>s  E > In this posting I probably under-estimated the benefits to Compaq'stJ > bottom line because from documents filed in 1998 by Compaq at the SEC (*G > see note below) we find that Compaq's estimated expenditure on all ofyJ > the in-process technology that it obtained from Digital was $630 millionB > this year (2001), $520 million in 2002, $400 million in 2003 andE > thereafter falling away.  With Alpha being a major component of the/D > in-progress technology, transferring Alpha to Intel would save the > better part of $1 billion.  @ To paraphrase a famous quote, "There's lies, damn lies, and then< there's accounting."  Just look at Enron.  We have no way ofF knowing what the Q lumped into this category.  But yes, there was someE expenditure, because usually you have to invest money to make money. t UnlikeC the Q's PC business, where putting the same money in Treasury notes  would + have been a far better investment strategy.t  G Q management (sic) decided that they could eject the motor out of their G corporate airplane and just glide a while.  After all, gas costs money,t andi? if there's less weight in the aircraft (no motor) it will glidei
 farther.  TheiF problem with this scenario is that the plane eventually plows into the ground.)H Q management (sic) evidently plan on borrowing a more efficient motor on the,D way to the ground. Even the sleepiest of customers can see the crash coming@ (there's this guy Gartner standing in the aisle with a megaphone shoutingE "Get Out! Get Out! GET OUT!!!  THERE'S THE DOOOOOOOORRRRRR!!!!!") anddD all things considered they have a heck of a lot of incentive to jumpE  out.  Luckily for those passengers who are customers Sun and IBM areDE flying alongside with a big net to pick them up. The other passengersgA (the employees) are not nearly so fortunate - but that concerns QlB management not at all since their own parachutes are at the ready.  F Ironically enough, all this is being done nominally in the name of the
 shareholders,aD and while customers can find other vendors, employees can find other jobs, shareholdersG are probably just going to lose most of their money.  Ask the folks whoo invested in SGIl how that goes.   Regards,   David Mathog mathog@caltech.edu   ------------------------------  % Date: Fri, 14 Dec 2001 13:45:56 +0000 % From: Alan Greig <a.greig@virgin.net>t Subject: More on Google archive.8 Message-ID: <q00k1u8mtk43blr5hnvcqd38vk9uhgpkm0@4ax.com>  F If you're looking for posts prior to 1987 they are in fa.info-vax backF to November 1981. Here's the first post. Note that external field test@ sites were attacking what was to become VAXC RTL even before its release.  F I still can't find a single post to *any* newgroup from myself between@ 1987 and 1991 but can find them some before and many after theseD years. All would have been via one provider. Prior to 1987 I doubt IA posted to info-vax but did read it on and off - still primarily anD TOPS-20 fan at that time and have not ben able to locate archives ofB the TOPS-20 mailing list (which unlike info-vax was never gated to news) yet.    & First info-vax  post in Google archive  a' From: ucbvax!info-vax (ucbvax!info-vax)r Subject: VMS C compiler  Newsgroups: fa.info-vaxoB View: (This is the only article in this thread) | Original Format  Date: 1981-11-16 13:18:00 PST   e  * >From mo@LBL-UNIX Mon Nov 16 12:35:44 1981F The DEC C compiler is NOT free!!!  It is a product being funded by the> Unix engineering group inside DEC.  We are a test site for the compilerD and the current reactions are mixed.  The code generation is nothingF to brag about, in fact, often worse than the Unix compiler for routineB expressions (in spite of much optimizer screwing around).  What is worse,A the run-time system is horrid.  It will also be broken by VMS 3.0.C (which we are also a test-site for).  When it is finally announced,o< it will cost MONEY.  We will talk more about the compiler as
 experience accumulates. 	-Mike    P --------------------------------------------------------------------------------   -- Alan   ------------------------------    Date: 14 Dec 2001 05:47:24 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen) ; Subject: Re: Move to an HP OS, most folks would rather not.w3 Message-ID: <H8iVZyIF$VAq@eisner.encompasserve.org>   j In article <qveS7.574$BK1.15448@news.cpqcorp.net>, "Fred Kleinsorge" <kleinsorge@star.zko.dec.com> writes:J > It also appears on its face to be about moving Tru64 customers to HP-UX.  L But at least it mentioned VMS and indicated there might be VMS customers :-)   ------------------------------  # Date: Fri, 14 Dec 2001 14:15:10 GMT * From: "Bill Todd" <billtodd@metrocast.net>; Subject: Re: Move to an HP OS, most folks would rather not.PC Message-ID: <OPnS7.179315$tf5.10778136@bin5.nnrp.aus1.giganews.com>f  : "JF Mezei" <jfmezei.spamnot@videotron.ca> wrote in message& news:3C199651.FF940430@videotron.ca... > Bill Todd wrote:B > > 'Facing the proposed merger, 45 percent of the Alpha customers interviewedrH > > by Warburg believed it was "less likely" that they would stay with aJ > > combined HP/Compaq company, while 55 percent said their feelings about0 > > remaining a Compaq customer were "unchanged" >oL > What is important to consider is whether there are significant differences8 > between the 45% and 55% in terms of customer profiles.  H It was easy to skim over the fact that not all of the 55% whose feelingsE were unchanged intended to stick with cHomPaq if the merger occurred:o  K "Of those that indicated unchanged, the majority required more knowledge oftG HP's product road map or had already made the decision to leave Compaq,a Young said."  H Would have been interesting to know why those who had already decided to defect did so.   - bill   ------------------------------  % Date: Fri, 14 Dec 2001 12:49:07 -0500r5 From: "Fred Kleinsorge" <kleinsorge@star.zko.dec.com>i; Subject: Re: Move to an HP OS, most folks would rather not.t2 Message-ID: <N%qS7.607$BK1.15808@news.cpqcorp.net>   Bill Todd wrote in message ... >r >sG >I'm sure Fred will be delighted that someone has actually gone out andbJ >polled Alpha customers to find out how they feel, but, again, the resultsE >seem less consistent with his optimistic view of the world than witho	 >others':c >e   ...t >A: >Admittedly, the poll here was merger-specific rather thanG >Alpha-to-Itanic-specific, but it still indicates significant sentimentnL >toward defection that Fred's radar does not appear to have detected (thoughG >one could understand why it might be much more heavily weighted toward  Tru64rH >customers).  And without attempting to quantify defection potential theI >article does mention the discomfort Alpha customers reportedly have witht >Itanic as a replacement.  >     I On its face, this thing puports to relay the effects on "Alpha" customersnL and their probability of moving to HP-UX.  This, I would submit, has nothingI to do with OpenVMS.  You want to be able to eat your cake here by lumping F "Alpha" bad news together to make it "VMS" bad news.  To my knowledge,D nobody here is suggesting migrating VMS users to HP-UX, otherwise we, wouldn't need to do the VMS port to Itanium.  H Give me the specific breakout of the number of VMS customers polled, theE number of Tru64 customers polled, the titles of those polled, and theL1 number/value of the system assets they represent.e  L I have never denied that any serious attempt to move VMS customers to NT (inL the past) or HP-UX (which is what you imply - due to the lack of the numbers5 behind the conclusions) would be anything but doomed.   L It would also strike me that without the specific advantages Tru64 provides,L HP-UX would also be problematic for a migration.  It would be the job of theH new company to import those features into HP-UX to make it attractive to* Tru64 users.  But THIS is not a VMS issue.   ------------------------------  % Date: Fri, 14 Dec 2001 12:52:32 -0500r5 From: "Fred Kleinsorge" <kleinsorge@star.zko.dec.com>>; Subject: Re: Move to an HP OS, most folks would rather not.a2 Message-ID: <_2rS7.608$BK1.15719@news.cpqcorp.net>  = JF Mezei wrote in message <3C199651.FF940430@videotron.ca>...h >Bill Todd wrote:aA >> 'Facing the proposed merger, 45 percent of the Alpha customersn interviewedtG >> by Warburg believed it was "less likely" that they would stay with aaI >> combined HP/Compaq company, while 55 percent said their feelings abouto/ >> remaining a Compaq customer were "unchanged"w > K >What is important to consider is whether there are significant differences 7 >between the 45% and 55% in terms of customer profiles.s >r    5 Yeah, like 45% were Tru64 customers and 55% were VMS.p  J >Compaq would be glad to lose me as a customer since I don't generate much >profits to Compaq.u  K Bzzzt.  We will not be glad to lose you.  There may come a time that we do,s! but there won't be any rejoicing.i  < >But Compaq wouldn't want to lose an outfit like Bombardierr> >who has a big VMS cluster. (and some Tru64 unix running SAP). >rG >So if the 45% of customers are mostly small customers, and the 55% arey mostlyH >large customers, then Compaq would actually see this as a positive move sincepH >it would keep the "creme de la creme" and dump the smaller unprofitable pesky customers. >u  K Or if most of those staying with Compaq are VMS, and those leaving would beV Tru64...  F >With the niches ever so smaller for VMS, it will need fewer and fewerI >applications to satisfy the smaller remaining customer base. Essentially,D >Compaq is downsizing VMS to a very small niche that might not be so	 differentt >than what Cray used to have.e  E I don't see this acellerating any downsizing.  I see VMS shrinking incJ certain areas, and growing in others - something that has been ongoing for at least a decade.   ------------------------------  % Date: Fri, 14 Dec 2001 10:51:23 -0000 * From: "Richard Brodie" <R.Brodie@rl.ac.uk>7 Subject: Re: nova (was: RE: Inquirer: OpenVMS on DS20L)i+ Message-ID: <9vcljb$vrs@newton.cc.rl.ac.uk>r  : "Jonathan Boswell" <jsb@ost.cdrh.fda.gov> wrote in message* news:3C18F19D.90A3F33D@ost.cdrh.fda.gov...  J > See http://www.snopes2.com/business/misxlate/nova.htm which seems pretty
 > definitive.r  L Curious. The two examples of unfortunate car names I've heard in the UK wereL the (GM) Vauxhall Nova and the Triumph Acclaim. It appears that the VauxhallG Nova was actually made in Spain but not marketed under that name there.l   ------------------------------  + Date: Fri, 14 Dec 2001 12:36:05 +0100 (MET)a9 From: Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com>w7 Subject: Re: nova (was: RE: Inquirer: OpenVMS on DS20L)-; Message-ID: <01KBUWZLEIW89138XQ@sysdev.deutsche-boerse.com>   L > > See http://www.snopes2.com/business/misxlate/nova.htm which seems pretty > > definitive.  > N > Curious. The two examples of unfortunate car names I've heard in the UK wereN > the (GM) Vauxhall Nova and the Triumph Acclaim. It appears that the VauxhallI > Nova was actually made in Spain but not marketed under that name there.a  D There are, of course, many OTHER reasons why cars are marketed with E different names in different countries (not that I always understand  G them).  For instance, the Audi 100 was (at least at one time) marketed gG as the Audi 5000 in the States, the VW Golf used to be the Rabbit, the  A Passat the Dasher etc.  The Opel (a German company from the 19th wE century, initially a maker of sewing machines, bought by GM in 1929) oD Kadett was, at least some of the time, essentially identical to the F Vauxhall (also owned by GM) Astra.  Why not Kadett or Cadet in the UK?. (Now, it is called Opel Astra in Germany too.)   ------------------------------  + Date: Fri, 14 Dec 2001 12:49:06 +0100 (MET)l9 From: Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com>o3 Subject: nova (was: RE: Inquirer: OpenVMS on DS20L) ; Message-ID: <01KBUXCSHUKK9138XQ@sysdev.deutsche-boerse.com>   L > }Ah yes. Advanced RISC Architecture. I believe "ara" is a Very Bad Word inM > }Arabic, Farsi, or some other middle eastern language. Same mistake GM madenN > }with the Chevy Nova. Since "no va" translates into "doesn't go" in Spanish,5 > }GM didn't sell a heck of a lot of Novas in Mexico!t > 4 > This is an urban legend, i.e. not really the case. > D > "Nova" in Spanish means the same thing it does in English - a starD > that has exploded. (Which may not be the best thing to name a car,7 > but it is no worse in Spanish than it is in English.)a  C True, but this comes from the Latin word for "new".  The usage was pF introduced by Tycho Brahe (once described by, I think, Herbert S. Zim ? (writer of popular-science books, mostly about animals etc but mH occasionally, as here, other topics as well) as "a somewhat disoriented G cross between W. C. Fields and Carl Sagan") in his book DE NOVA STELLA hD ("concerning the new star").  Novae, exploding stars, were formerly G thought to be new stars, since they were too dim to be seen before the l> explosion.  (In modern times, one has actually identified the @ progenitors of some novae on images taken before the explosion.)  F The Spanish word for "new" is "nueva".  I don't know if, as a result, E Spanish-speaking people would associate "nova" with "new" more than, e# say, English-speaking people would.d   ------------------------------  % Date: Fri, 14 Dec 2001 13:04:55 +0100n= From: Jan-Erik =?iso-8859-1?Q?S=F6derholm?= <noone@dummy.com> 7 Subject: Re: nova (was: RE: Inquirer: OpenVMS on DS20L)c) Message-ID: <3C19EAE7.CD04291E@dummy.com>s  7 The astronomical "nova" is actualy an exploding star at": the end of it's (normal) life. Depending on it's size, the: nova can end in just nothing or in a white small, very hot star.r   Jan-Erik Sderholm   ------------------------------   Date: 14 Dec 2001 06:26:09 CDT= From: wayne@tachysoft.xxx.524703.killspam.00bd (Wayne Sewell) 7 Subject: Re: nova (was: RE: Inquirer: OpenVMS on DS20L)m. Message-ID: <MmDRAObT0$Ku@tachxxsoftxxconsult>  t In article <9BfS7.12421$Sj1.6912779@typhoon.ne.mediaone.net>, "Terry C. Shannon" <terryshannon@mediaone.net> writes:< > "Jonathan Boswell" <jsb@ost.cdrh.fda.gov> wrote in message, > news:3C18F19D.90A3F33D@ost.cdrh.fda.gov... >> Phillip Helbig wrote:I >> > > Same mistake GM made with the Chevy Nova. Since "no va" translatesr > intoJ >> > > "doesn't go" in Spanish, GM didn't sell a heck of a lot of Novas in >> > > Mexico! >> >K >> > I'm pretty sure this is an urban legend (if not, it is an urban legend & >> > that it is an urban legend :-) ). >>K >> See http://www.snopes2.com/business/misxlate/nova.htm which seems prettyi >> definitive. >> >>  - JB > G > Thanks for the definitive info. I can see how, as per the info at theiK > aforementioned site,  the phrase "no va" (literally "doesn't go") and thecM > word "nova" are distinct entities with different pronunciations in Spanish.a; > Still, close enuff to provide fodder for an Urban Legend.i > H > Meanwhile, I must get back to my new job: taking a census of all thoseH > alligators that are hanging out in the New York City sewer system. ;-}  O I applied for a job as a Kentucky Fried Chicken food inspector so I can protect & the public from those deep-fried rats.   --  O ===============================================================================eM Wayne Sewell, Tachyon Software Consulting  (281)812-0738  wayne@tachysoft.xxxi: http://www.tachysoft.xxx/www/tachyon.html and wayne.html  K change .xxx to .com in addresses above, assuming you are not a spambot  :-) O ===============================================================================oN Sparky (from Bring It On): "In cheerleading, we throw people in the air.  Fat  	people don't go as high."   ------------------------------  # Date: Fri, 14 Dec 2001 17:59:01 GMTu4 From: "Terry C. Shannon" <terryshannon@mediaone.net>7 Subject: Re: nova (was: RE: Inquirer: OpenVMS on DS20L)e= Message-ID: <F5rS7.12702$Sj1.7186394@typhoon.ne.mediaone.net>-  J "Wayne Sewell" <wayne@tachysoft.xxx.524703.killspam.00bd> wrote in message( news:MmDRAObT0$Ku@tachxxsoftxxconsult...I > In article <9BfS7.12421$Sj1.6912779@typhoon.ne.mediaone.net>, "Terry C.a, Shannon" <terryshannon@mediaone.net> writes:> > > "Jonathan Boswell" <jsb@ost.cdrh.fda.gov> wrote in message. > > news:3C18F19D.90A3F33D@ost.cdrh.fda.gov... > >> Phillip Helbig wrote:K > >> > > Same mistake GM made with the Chevy Nova. Since "no va" translates  > > intoL > >> > > "doesn't go" in Spanish, GM didn't sell a heck of a lot of Novas in > >> > > Mexico! > >> >F > >> > I'm pretty sure this is an urban legend (if not, it is an urban legend( > >> > that it is an urban legend :-) ). > >>F > >> See http://www.snopes2.com/business/misxlate/nova.htm which seems pretty > >> definitive. > >>
 > >>  - JB > >tI > > Thanks for the definitive info. I can see how, as per the info at the I > > aforementioned site,  the phrase "no va" (literally "doesn't go") andf thewF > > word "nova" are distinct entities with different pronunciations in Spanish.= > > Still, close enuff to provide fodder for an Urban Legend.e > > J > > Meanwhile, I must get back to my new job: taking a census of all thoseJ > > alligators that are hanging out in the New York City sewer system. ;-} >hI > I applied for a job as a Kentucky Fried Chicken food inspector so I can  protectf( > the public from those deep-fried rats. >l  L But deep-fried rat goes so nicely with a dessert of Bubble Yum... gotta love? the black widow spider eggs that come with the chewing gum. ;-}u   ------------------------------    Date: 14 Dec 2001 10:38:17 -08003 From: Eric Smith <eric-no-spam-for-me@brouhaha.com> 7 Subject: Re: nova (was: RE: Inquirer: OpenVMS on DS20L) 0 Message-ID: <qhzo4lve92.fsf@ruckus.brouhaha.com>  , Jan-Erik Sderholm <noone@dummy.com> writes:9 > The astronomical "nova" is actualy an exploding star ath< > the end of it's (normal) life. Depending on it's size, the< > nova can end in just nothing or in a white small, very hot > star.t   It can't end in "just nothing".h   ------------------------------  % Date: Fri, 14 Dec 2001 08:21:57 -0500e' From: Ken Robinson <kenrbnsn@rbnsn.com>  Subject: Old VAX DocumentationA Message-ID: <5.1.0.14.2.20011214081331.0504ab40@mail.eclipse.net>   K A co-worked of my wife's found some old VAX documentation and knowing that a" I am a VMS guy, gave them to me...  	 They are:s  M 1) The 1981 VAX Architecture Handbook (Sub-titled "Architecture for the 80's"h  L 2) VAX Technical Summary from 1982. This covers the 11/780, 11/782, 11/750,  and the 11/730.e   Ken Robinson kenrbnsn@rbnsn.com   ------------------------------  % Date: Fri, 14 Dec 2001 12:34:16 +0100e( From: Paul Sture <paul.sture@bluewin.ch>+ Subject: OT: Startrek, Borgs and the HHGTTGr- Message-ID: <VA.000004eb.f772c81b@bluewin.ch>v  K In article <QD7S7.60404$xS6.99329@www.newsranger.com>, Simon Clubley wrote:t  M > Those Star Trek fans who are not fans of Microsoft tend to make comparisonsd% > between the Borg and Microsoft. :-)y > H Chuckle. I'm just re-reading the HHGTTG, and I'm realising how propheticG Douglas Adams was with his vision of the Sirius Cybernetic Corporation.oF Substitute M$ for that name as you read, and smile :-) ... or weep :-(  E Compare the irritating Eddie, the Shipboard Computer, with the Office2F paperclip. See how a drinks machine can issue a DoS attack on the mainJ system (embedded NT anyone?). Doors that are smug; the tunes Windows playsG on startup, and tons more. One almost wonders if BG used the books as ai model for M$...i  I In a perhaps vain attempt to bring this back on topic, my introduction to D the HHGTTG came from my habit of taking a radio into work on Sundays  when tending my first PDP-11 :-) ___y
 Paul Sture Switzerlando   ------------------------------  % Date: Fri, 14 Dec 2001 14:21:50 +0000i( From: Nic Clews <sendspamhere@127.0.0.1>/ Subject: Re: OT: Startrek, Borgs and the HHGTTGe) Message-ID: <3C1A0AFE.D0E3F6B7@127.0.0.1>    Paul Sture wrote:e > M > In article <QD7S7.60404$xS6.99329@www.newsranger.com>, Simon Clubley wrote:b > O > > Those Star Trek fans who are not fans of Microsoft tend to make comparisonsc' > > between the Borg and Microsoft. :-)o > >oJ > Chuckle. I'm just re-reading the HHGTTG, and I'm realising how propheticI > Douglas Adams was with his vision of the Sirius Cybernetic Corporation. H > Substitute M$ for that name as you read, and smile :-) ... or weep :-(  B And that "[the Earth] was being run for the benefit of a few white mice".  oG > Compare the irritating Eddie, the Shipboard Computer, with the OfficegH > paperclip. See how a drinks machine can issue a DoS attack on the mainL > system (embedded NT anyone?). Doors that are smug; the tunes Windows playsI > on startup, and tons more. One almost wonders if BG used the books as an > model for M$...   3 Doesn't the man in the shack remind you of BG ? :-)   E Just the other week I picked up a copy of Marvin the Paranoid AndroidcE and "Reasons to be miserable", the double B side on Depressive Discs.    -- -( Regards, Nic Clews CSC Computer Sciences nclews at csc dot comJ   ------------------------------  % Date: Fri, 14 Dec 2001 09:42:55 -050042 From: "Sue Skonetski" <susan.skonetski@compaq.com>J Subject: Press Release SyntheSys Secure Technologies - JabCast  on OpenVMS2 Message-ID: <BcoS7.600$BK1.15974@news.cpqcorp.net>   They also have a surveyn   Sueo   http://www.prnewswire.comt  H BOCA RATON, Fla., Dec. 12 /PRNewswire/ -- SyntheSys Secure Technologies,H Inc. announces the release of the JabCast Secure Realtime Communications (SRC)sG system on Compaq Computer Corporation's AlphaServer systems running the I OpenVMS operating system.  SyntheSys developed the product for JabCast, ad Newn York-based software company.L     JabCast SRC is the first technology that allows for realtime interactiveJ text, file, and document exchange in a secure environment via the InternetL across multiple operating systems including Windows NT, Windows 2000, Linux,	 and UNIX.aH     "Many companies and government agencies have been unable to maximize their G productivity and communications with the use of realtime communicationso acrossJ the Internet because of significant security concerns and the inability ofJ different operating systems to 'talk' to one another," said Craig Woolven, CEOeG of JabCast, Inc.  "With JabCast, Compaq's OpenVMS provides the inherentgK security and the uptime needed in critical real-time situations, as well ast@ the scalability to grow with our customers as demand increases."J     JabCast SRC also provides absolute security of transmitted informationK from point of origination and destination.  Moreover, it offers path hidinge by9 encrypting the sender's address from outside observation.oG     "With the addition of JabCast, Compaq OpenVMS users have additionaltG options to share data and converse in realtime across the Internet in a  secureL environment," said Mark Gorham, Vice President of the OpenVMS Systems Group.F "JabCast's capabilities, combined with the performance and security ofF OpenVMS, will allow companies to increase productivity by facilitatingJ complete and secure, realtime online meetings that take minutes versus the< traditional exchange of e-mails over several hours or days."  '     About SyntheSys Secure TechnologiestK     SyntheSys Secure Technologies, Inc., a global secure solutions company,iI develops and markets a variety of innovative security-based products thattE function on various operating systems including OpenVMS, UNIX, Linux,e Windows,F NT, Windows 2000 and AS400.  The company is structured around five keyK business segments that addresses all elements of IT security: (1) BiometriceH crypto-controlling smart cards, (2) full public key infrastructure (PKI) withI digital signatures and trust centers, (3) secure realtime communications,sJ (4) systems integration and training, and (5) transponder tags.  SyntheSys isK headquartered in Boca Raton, Florida and has been providing authentication,iJ network security software, and IT security solutions since 1992.  For moreI information on SyntheSys and JabCast, visit http://www.synthesysusa.com .u   ------------------------------  # Date: Fri, 14 Dec 2001 13:04:42 GMT0G From: Simon Clubley <simon_clubley@remove_me.altavista.co.uk-Earth.UFP>:* Subject: Reloading device drivers on Alpha7 Message-ID: <KNmS7.61313$xS6.100278@www.newsranger.com>   C I am aware that reloading of device drivers on Alpha as such is not E possible, but I am interested in hearing what techniques other driveruE writers use to avoid having to continually reboot the system when aret developing new drivers.   I As far as I can see you have to play games with the driver's filename and>G attach it to another unit. Attaching it to another unit is not an issue G in my case, but is there any way to avoid having to play with filenamesaA in order to force VMS to load the latest version of your driver ?    Thanks for any information,S   Simon.   -- l@ Simon Clubley, simon_clubley@remove_me.altavista.co.uk-Earth.UFPK In the task of removing Microsoft from the marketplace, I have discovered aeE truly remarkable plan, but this signature is too small to contain it.    ------------------------------  % Date: Fri, 14 Dec 2001 12:55:34 -0500r5 From: "Fred Kleinsorge" <kleinsorge@star.zko.dec.com>%. Subject: Re: Reloading device drivers on Alpha2 Message-ID: <P5rS7.609$BK1.16022@news.cpqcorp.net>  H Nope.  I agree it's a pain in the ass, and I disagreed with the decisionB when it was made.  But the only really safe thing to do is reboot.    " Simon Clubley wrote in message ...D >I am aware that reloading of device drivers on Alpha as such is notF >possible, but I am interested in hearing what techniques other driverF >writers use to avoid having to continually reboot the system when are >developing new drivers. > J >As far as I can see you have to play games with the driver's filename andH >attach it to another unit. Attaching it to another unit is not an issueH >in my case, but is there any way to avoid having to play with filenamesB >in order to force VMS to load the latest version of your driver ? >  >Thanks for any information, >a >Simon." >. >--eA >Simon Clubley, simon_clubley@remove_me.altavista.co.uk-Earth.UFPiL >In the task of removing Microsoft from the marketplace, I have discovered aF >truly remarkable plan, but this signature is too small to contain it.   ------------------------------  % Date: Fri, 14 Dec 2001 11:30:11 -0500r; From: "Brian Tillman" <tillman_brian@notnoone.notnohow.com>a, Subject: Re: remote connection and pathworks$ Message-ID: <3c1a2920$1@news.si.com>   >Are you sure on that ?x( >Can you prove this with SDA> SHOW LAN ?  ( It's running on only one interface here:  
 SDA> show lan-   LAN Data Structures1 -------------------0=                 -- LAN Device Summary 14-DEC-2001 11:28:14 --e  + LAN block address  = C1554480  (2 stations)p LAN flags:  0002 LAN_initD   LSB address  = C1566500v$ Device state = 4013 Inited,Run,Timer  <                  -- FXA Unit Summary 14-DEC-2001 11:28:14 --  8 UCB     UCB Addr  Fmt   Value           Client     State; ---     --------  ---   -----           ------  -----------l FXA0    C1566140I FXA1    C1580700  Eth   60-07           SCA     0017 Strtn,Len,Uniq,StrtdiI FXA3    C17711C0  Eth   60-03           DECNET  0017 Strtn,Len,Uniq,StrtdH4 FXA4    C1770000  Eth   60-01           MOPDL   001F Strtn,Len,Uniq,Share,StrtdK FXA5    C1613F80  Eth   90-00           LOOP    001D Strtn,Uniq,Share,StrtdtE FXA6    C17AD5C0  Eth   08-00           IP      0015 Strtn,Uniq,StrtdsE FXA7    C17ADB80  Eth   08-06           ARP     0015 Strtn,Uniq,StrtdcE FXA8    C17AE140  Eth   86-DD                   0015 Strtn,Uniq,StrtdbE FXA9    C17DA480  Eth   60-04           LAT     0015 Strtn,Uniq,StrtdlE FXA13   C180E100  Eth   80-41           LAST    0015 Strtn,Uniq,StrtdtI FXA15   C18099C0  Eth   81-2B                   0017 Strtn,Len,Uniq,Strtd-E FXA16   C180D980  Eth   80-40           BIOS    0015 Strtn,Uniq,StrtdTE FXA17   C19075C0  802   F0              PATHWRK 0015 Strtn,Uniq,Strtd:    LAN Data Structures -------------------  LSB address  = C1571A409, Device state = 001B Inited,Run,Ctl_Rdy,Timer  <                  -- EXA Unit Summary 14-DEC-2001 11:28:19 --  8 UCB     UCB Addr  Fmt   Value           Client     State; ---     --------  ---   -----           ------  -----------a EXA0    C15712C0I EXA1    C15716C0  Eth   60-07           SCA     0017 Strtn,Len,Uniq,StrtdiE EXA4    C17F1F00  Eth   80-41           LAST    0015 Strtn,Uniq,StrtdN --A Brian Tillman                   Internet: tillman_brian at si.comtA Smiths Aerospace                          tillman at swdev.si.comu= 3290 Patterson Ave. SE, MS      Addresses modified to preventu< Grand Rapids, MI 49512-1991     SPAM.  Replace "at" with "@"8        This opinion doesn't represent that of my company   ------------------------------  % Date: Fri, 14 Dec 2001 11:25:19 -0000t4 From: "Chris Sharman" <chris.sharman@ccagroup.co.uk> Subject: RMSdef.stb linking ...wB Message-ID: <1008328954.21817.0.nnrp-08.9e989e7e@news.demon.co.uk>  H I've a module which goes fishing in RMS, to discover which processes areI blocking RMS locks - it's invoked from many places when an RMS lock error J (such as rms$_rnl) is detected. It's been unchanged (& forgotten) for some years.  K Since installing 7.3, we've been experiencing odd process exits - typicallyo	 RMS bugs.,E I've just (after months) traced it to this piece of code, which linkswL against sys$loadable_images:rmsdef.stb, as well as /sysexe=selective_search, for the symbols:& %LINK-I-UDFSYM,         IFB$L_SFSB_PTR& %LINK-I-UDFSYM,         IRB$L_IFAB_LNK% %LINK-I-UDFSYM,         IRB$L_RFA_VBNs$ %LINK-I-UDFSYM,         IRB$W_RFA_ID& %LINK-I-UDFSYM,         PIO$GW_IIOIMPA& %LINK-I-UDFSYM,         SFSB$L_LOCK_ID  K The question is, how should I be building this thing, so that it will causeeH an error at activation time if RMS has changed, rather than causing exec mode accvios at runtime ?-   Thanks,-
 Chris Sharmana   ------------------------------  # Date: Fri, 14 Dec 2001 12:25:29 GMT0= From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)M# Subject: Re: RMSdef.stb linking ...K0 Message-ID: <00A067F8.F8799BD8@SendSpamHere.ORG>  y In article <1008328954.21817.0.nnrp-08.9e989e7e@news.demon.co.uk>, "Chris Sharman" <chris.sharman@ccagroup.co.uk> writes:dI >I've a module which goes fishing in RMS, to discover which processes are J >blocking RMS locks - it's invoked from many places when an RMS lock errorK >(such as rms$_rnl) is detected. It's been unchanged (& forgotten) for somee >years.  >aL >Since installing 7.3, we've been experiencing odd process exits - typically
 >RMS bugs.F >I've just (after months) traced it to this piece of code, which linksM >against sys$loadable_images:rmsdef.stb, as well as /sysexe=selective_search,> >for the symbols:>' >%LINK-I-UDFSYM,         IFB$L_SFSB_PTRn' >%LINK-I-UDFSYM,         IRB$L_IFAB_LNKi& >%LINK-I-UDFSYM,         IRB$L_RFA_VBN% >%LINK-I-UDFSYM,         IRB$W_RFA_ID ' >%LINK-I-UDFSYM,         PIO$GW_IIOIMPAd' >%LINK-I-UDFSYM,         SFSB$L_LOCK_IDt >,6 >The question is, how should I be building this thing,   Correctly!  ;)   > so that it will cause I >an error at activation time if RMS has changed, rather than causing execY >mode accvios at runtime ? >  >Thanks, >Chris Sharman  L Each and every one of the symbols you have listed is available under V7.3.  J PIO$GW_IIOIMPA is defined in the base image which tend to have be questionI your build procedure.  You shouldn't need to have to do anything specific)I as these symbols/locations/offset exist in V7.3.  At least they do on thenK Alpha.  I doubt that they were removed on VAX but I haven't checked it out.a  K How are these various symbols used and/or defined in your program?  And how=< do you specify the LINK command and/or .OPTion linking deck?   --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM-            aJ   "And of course, I'm a genius, so people are naturally drawn to my fiery I   intellect.  Their admiration overwhelms their envy!" -- Calvin & Hobbess   ------------------------------  % Date: Fri, 14 Dec 2001 12:56:32 -0000"4 From: "Chris Sharman" <chris.sharman@ccagroup.co.uk># Subject: Re: RMSdef.stb linking ...xB Message-ID: <1008334415.24428.0.nnrp-08.9e989e7e@news.demon.co.uk>  8 > >The question is, how should I be building this thing, >: > Correctly!  ;)  # Yes, right, and when it needs it ;)m    $link/share/notrace ss_getblock,- sys$loadable_images:rmsdef.stb/sel/sysexe=sel   L To clarify: the problem is not how to build it, but how to remember to build it !  K Linking with /sysexe=sel will cause an activation error if there's a change  to pio$gw_iioimpa L Can I link it so that I get a similar activation time version check done forE the RMS symbols, since they're what bit me, and it's taken a while to/G identify the offender (particularly since with RMS & XFC problems & thenJ like, I wasn't even sure I had a problem - just install the latest patch & hope it doesn't recur).    ------------------------------  % Date: Fri, 14 Dec 2001 08:59:41 -0500 4 From: John Malmberg <Malmberg@dskwld.zko.dec.compaq>Y Subject: SPAM Reporting - was Re: Chase Visa Card, Verisign Thawte Certificate, Rapid Traa4 Message-ID: <3C1A05CD.5080706@dskwld.zko.dec.compaq>   Franz-Josef Fornefeld wrote:   > [posted&mailed]s  a   Someone claiming to be  > > Paul Mac Arthur (Rapid Internet Marketing Newsletter) wrote:    B You can not believe any of the human settable headers from a SPAM G message.  This is a known trick of spammers to get false reports filed.d    ( > Sheesh, SPAM via the Info-VAX-Gateway.    H It happens.  This one hit several mailing lists that are cross gated to  newsgroups.      > HTML and wrong Date/Time.     F Actually not really HTML.  It was plain text, the bad HTML tag at the E beginning prevented http://www.spamcop.net from decoding the spam to b identify the true senders.  v Correcting the content type line before SpamCop processing allowed finding the correct abuse reporting mail addresses.    G Note that spamcop (the last time I checked) would not handle newsgroup eH postings, and there are too many ways for spammers to forge the headers.  I But the service will handle spam from mailing lists.  Sometimes deleting oC the line about the x-newsgroups will allow it to decode the e-mail -1 headers to determine the true source of the spam.e    - > Mark, would you please cancel this account?A    H There is no account to cancel.  Anyone can inject a posting from either H a news group, or directly sending to the mailing list.  info-vax is not  closed to just subscribers.n  F While Mark has indicated that he has some spam filters in place, this  obviously got by them.  C Please review the info-vax section of the OpenVMS Frequently Asked  I Questions at http://www.openvms.compaq.com/ for information on this list : and newsgroup.      > FollowUp-To poster    F This confirms that the your e-mail address is valid, and further spam  will not bounce.  H You probably have just signed your self up to get tons of spam, as this D usually just adds your e-mail address to the lists that the spammer F sells.  [You may actually get dropped from the one you requested, but . you will likely get added to a few dozen more]   -John  wb8tyw@qsl.network   Personal Opinion Onlyh; Not affiliated with spamcop, just using their free service.    ------------------------------    Date: 14 Dec 2001 08:46:31 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen)tY Subject: Re: SPAM Reporting - was Re: Chase Visa Card, Verisign Thawte Certificate, Rapids3 Message-ID: <RyaatgVeaE2t@eisner.encompasserve.org>   k In article <3C1A05CD.5080706@dskwld.zko.dec.compaq>, John Malmberg <Malmberg@dskwld.zko.dec.compaq> writes:n  H > Actually not really HTML.  It was plain text, the bad HTML tag at the G > beginning prevented http://www.spamcop.net from decoding the spam to - > identify the true senders.  : On a mail (not newsgroup) message I received this morning,4 the SpamCop parse put up a red notice about bad HTML6 but did parse the message correctly.  I had never seen7 that red notice before, so perhaps it is a new feature..  I > Note that spamcop (the last time I checked) would not handle newsgroup sJ > postings, and there are too many ways for spammers to forge the headers.  C I find that pasting newsgroup posts into the SpamCop window results,B in a proper parse most of the time, and I do use that to complain.? Messages posted by the email gateway into comp.os.vms, however,t, cannot be parsed by SpamCop for some reason.   ------------------------------  # Date: Fri, 14 Dec 2001 12:28:19 GMT ' From: "Hans Vlems" <hvlems@zfree.co.nz>e1 Subject: Summary "Unknown VAXstation 4000-90 ???"c$ Message-ID: <3c19f060$1@zfree.co.nz>  ? Hoff is right, as usual. I checked again the hardware and foundhA that there was dust in the Turbochannel connector that drives theO: LCSPX. I cleaned that out and rebooted the system. VMS now8 correctly identifies the system as a VS 4000 model 90-A.> The SHO LIC/CHAR command lists expected values for the various license types (D, E and F). < Next I connected it to a Digital monitor, and that worked asD well. So it seems that the LCSPX is still working, unless it has got two modes, ASCII and graphics.  ? Thank you all for helping me out. Hoff, my apologies for tryings$ a second channel with this question.  
 Hans Vlems  3 hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) wrote:g >:Hans Vlems wrote:1L >:> - VMS 7.3 still reports that it found an invalid processor configuration >rH >  I'll paraphrase my email response here -- I'll be posting any furtherJ >  comments and any discussions here in comp.os.vms as needed, rather than  H >  trying to replicate my answers across all the various communications 6 >  channels where this question is currently active... >dD >  Short answer: please get somebody to look at the hardware of this? >                VAXstation 4000 model 90 system.  It's busted.r >iL >  Long answer: Now that the console firmware has been reloaded, the OpenVMSH >  licensing errors are indicative of misconfigured or busted hardware.  Most nJ >  likely, this is a problem with the graphics controller -- either failed or eH >  missing, though this could potentially also be a hardware or firmware  ! >  problem with the motherboard. e > J >  Based on the hardware model code, this box appears to believe it shouldJ >  have the LCSPX graphics controller, but the motherboard or the graphicsL >  or a related component is either non-functional or is otherwise returning   >  an invalid response.i >sK >  This does not appear to be an OpenVMS software licensing problem -- onceiK >  the hardware is correctly configured and functional, OpenVMS should workf >  correctly here. >  >gO > ---------------------------- #include <rtfaq.h> -----------------------------nK >      For additional, please see the OpenVMS FAQ -- www.openvms.compaq.comC     O > --------------------------- pure personal opinion ---------------------------rM >   Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.como >h       http://www.zfree.co.nz   ------------------------------  % Date: Fri, 14 Dec 2001 10:14:03 -0500,  From: Binh Nguyen <binh@egh.com> Subject: sys$getdvi and socket& Message-ID: <3C1A173B.87F95A9@egh.com>   Help!   6 I have a socket that I've created using socket(), then6 bind() and listen().  After the connect() call returns< I create a new socket to accept the connection via accept().  : Now I want to find the VMS device name for this socket.  I> thought I could get sys$getdvi but am not successful.  What am I doing wrong ?m   Here's the code snipet:L   char devnam_string[64];w$ $DESCRIPTOR(devnam, devnam_string);    struct ilist {k         short int buf_len;         short int item;I         char *buf_addr;e         int *ret_len;a }; r struct ilist item_list;n   item_list.buf_len = 64;i item_list.item = DVI$_DEVNAM;e, item_list.buf_addr = (char *)&devnam_string;0 item_list.ret_len = (int *)&devnam.dsc$w_length;  6 sts = SYS$GETDVIW(0, sock, 0, &item_list, 0, 0, 0, 0);       sts is 8740r $:: help/message/status=8740    $  IVIDENT,  invalid identifier format  '   Facility:     SYSTEM, System Servicesn  D   Explanation:  This message can occur under either of the following                 conditions:e  F                 o The specified identifier is not formatted correctly.  F                 o A system call to the $QIO system service specified aA                   channel number that is outside the valid range.m    L   User Action:  Take the appropriate action, depending on the circumstances:  J                 o Use one of the valid identifier formats described in theI                   OpenVMS Guide to System Security and retry the command.   H                 o Modify the code to specify a channel number within the                   valid range.   ------------------------------   Date: 14 Dec 2001 17:09:52 GMT1 From: JONESD@er6.eng.ohio-state.edu (David Jones)n" Subject: Re: sys$getdvi and socket: Message-ID: <9vdbp0$8b3$1@charm.magnus.acs.ohio-state.edu>  I In message <3C1A173B.87F95A9@egh.com>, Binh Nguyen <binh@egh.com> writes:r; >Now I want to find the VMS device name for this socket.  Ie? >thought I could get sys$getdvi but am not successful.  What am  >I doing wrong ?  D A socket descriptor is not a VMS channel number.  You get the actual; channel number that the C RTL is using for a socket via thed function vaxc$get_sdc().  - >item_list.buf_addr = (char *)&devnam_string;7  . Change to: item_list.buf_addr = devnam_string;  7 >sts = SYS$GETDVIW(0, sock, 0, &item_list, 0, 0, 0, 0);   O Change to: sts = SYS$GETDVIW(0, vaxc$get_sdc(sock), 0, &item_list, 0, 0, 0, 0);e    < David L. Jones               |      Phone:    (614) 292-6929- Ohio State University        |      Internet: L 140 W. 19th St. Rm. 231a     |               jonesd@er6s1.eng.ohio-state.edu: Columbus, OH 43210           |               vman+@osu.edu  1 Disclaimer: I'm looking for marbles all day long.    ------------------------------  % Date: Fri, 14 Dec 2001 12:31:34 -0500   From: Binh Nguyen <binh@egh.com>" Subject: Re: sys$getdvi and socket' Message-ID: <3C1A3776.91FAD474@egh.com>i   David,   Thanks so much.  It works!     Binh   David Jones wrote: > K > In message <3C1A173B.87F95A9@egh.com>, Binh Nguyen <binh@egh.com> writes:@= > >Now I want to find the VMS device name for this socket.  IMA > >thought I could get sys$getdvi but am not successful.  What aml > >I doing wrong ? > F > A socket descriptor is not a VMS channel number.  You get the actual= > channel number that the C RTL is using for a socket via them > function vaxc$get_sdc(). > / > >item_list.buf_addr = (char *)&devnam_string;e > 0 > Change to: item_list.buf_addr = devnam_string; > 9 > >sts = SYS$GETDVIW(0, sock, 0, &item_list, 0, 0, 0, 0);i > Q > Change to: sts = SYS$GETDVIW(0, vaxc$get_sdc(sock), 0, &item_list, 0, 0, 0, 0);- > > > David L. Jones               |      Phone:    (614) 292-6929/ > Ohio State University        |      Internet:pN > 140 W. 19th St. Rm. 231a     |               jonesd@er6s1.eng.ohio-state.edu< > Columbus, OH 43210           |               vman+@osu.edu > 3 > Disclaimer: I'm looking for marbles all day long.    --   ------------------------------  % Date: Fri, 14 Dec 2001 13:48:54 -0500 % From: "John Vottero" <John@mvpsi.com> " Subject: Re: sys$getdvi and socket/ Message-ID: <u1kid46mvva79e@news.supernews.com>   H It only works because you're lucky.  Item lists must be terminated by anK item list entry that's all zeros.  You only have a single item in your item0I list, you're just lucky that the stuff following that happens to be zero.8  K Make your item list an array and set all the members of the last element to  zero.R  - "Binh Nguyen" <binh@egh.com> wrote in messaget! news:3C1A3776.91FAD474@egh.com...r > David, >b > Thanks so much.  It works! >  > Binh >  > David Jones wrote: > > E > > In message <3C1A173B.87F95A9@egh.com>, Binh Nguyen <binh@egh.com>  writes:1? > > >Now I want to find the VMS device name for this socket.  I C > > >thought I could get sys$getdvi but am not successful.  What amT > > >I doing wrong ? > >0H > > A socket descriptor is not a VMS channel number.  You get the actual? > > channel number that the C RTL is using for a socket via then > > function vaxc$get_sdc(). > > 1 > > >item_list.buf_addr = (char *)&devnam_string;  > > 2 > > Change to: item_list.buf_addr = devnam_string; > > ; > > >sts = SYS$GETDVIW(0, sock, 0, &item_list, 0, 0, 0, 0);0 > >1L > > Change to: sts = SYS$GETDVIW(0, vaxc$get_sdc(sock), 0, &item_list, 0, 0, 0, 0); > > @ > > David L. Jones               |      Phone:    (614) 292-69291 > > Ohio State University        |      Internet:_" > > 140 W. 19th St. Rm. 231a     | jonesd@er6s1.eng.ohio-state.edut> > > Columbus, OH 43210           |               vman+@osu.edu > > 5 > > Disclaimer: I'm looking for marbles all day long.e >t > --   ------------------------------   Date: 14 Dec 2001 09:17:02 GMT( From: nmm1@cus.cam.ac.uk (Nick Maclaren)! Subject: Re: The demise of compaq 0 Message-ID: <9vcg2e$h4o$1@pegasus.csx.cam.ac.uk>  1 In article <LAcS7.131$f9.5941@eagle.america.net>,5# del cecchi <dcecchi@msn.com> wrote:. >uG >Ah, the story of the 1 line program by IBM that ended up with 7 or wass? >it 9 APARs being written against it.  The program was IEFBR14.R >lD >Perhaps it is just a blue urban legend, but I have seen accounts on9 >internal groups that included the APARs and the results.n  0 It wasn't.  We were responsible for two of them.     Regards, Nick Maclaren,* University of Cambridge Computing Service,> New Museums Site, Pembroke Street, Cambridge CB2 3QH, England. Email:  nmm1@cam.ac.uk/ Tel.:  +44 1223 334761    Fax:  +44 1223 334679R   ------------------------------  % Date: Fri, 14 Dec 2001 10:29:44 +0000_- From: Roy Omond <Roy.Omond@BlueBubble.UK.Com>N! Subject: Re: The demise of compaq 1 Message-ID: <3C19D497.BD11C0D8@BlueBubble.UK.Com>i   Nick Maclaren wrote:  3 > In article <LAcS7.131$f9.5941@eagle.america.net>, % > del cecchi <dcecchi@msn.com> wrote:h > >aI > >Ah, the story of the 1 line program by IBM that ended up with 7 or was-A > >it 9 APARs being written against it.  The program was IEFBR14.0 > >mF > >Perhaps it is just a blue urban legend, but I have seen accounts on; > >internal groups that included the APARs and the results.S >H2 > It wasn't.  We were responsible for two of them.  6 Nick, would you care to reveal what these APARs were ?  6 It's beyond me to contemplate what could be wrong with the one liner:    BR 14cF unless, of course, register 14 were not to be the true return address.  	 Roy Omondk Blue Bubble Ltd.   ------------------------------   Date: 14 Dec 2001 11:14:05 GMT( From: nmm1@cus.cam.ac.uk (Nick Maclaren)! Subject: Re: The demise of compaqs0 Message-ID: <9vcmtt$m8t$1@pegasus.csx.cam.ac.uk>  1 In article <3C19D497.BD11C0D8@BlueBubble.UK.Com>,n/ Roy Omond <Roy.Omond@BlueBubble.UK.Com> writes:s |> Nick Maclaren wrote:f6 |> > In article <LAcS7.131$f9.5941@eagle.america.net>,( |> > del cecchi <dcecchi@msn.com> wrote: |> > >L |> > >Ah, the story of the 1 line program by IBM that ended up with 7 or wasD |> > >it 9 APARs being written against it.  The program was IEFBR14. |> > >I |> > >Perhaps it is just a blue urban legend, but I have seen accounts on!> |> > >internal groups that included the APARs and the results. |> >5 |> > It wasn't.  We were responsible for two of them.t |> i9 |> Nick, would you care to reveal what these APARs were ?  |> y9 |> It's beyond me to contemplate what could be wrong withO |> the one liner:    BR 14I |> unless, of course, register 14 were not to be the true return address.n  8 In MVT, the return code was the bottom 8 bits of R15 :-)  > [ For those who didn't use it, R15 was also the address of the program on entry. ]m  D I can't remember the second APAR, but it was on the 'fixed' version.D IBM's eventual solution was about 1K bytes long, mostly of copyright? notices.  We had a IEFBR14A, with extra function, from c. 1973.      Regards, Nick Maclaren,* University of Cambridge Computing Service,> New Museums Site, Pembroke Street, Cambridge CB2 3QH, England. Email:  nmm1@cam.ac.uk/ Tel.:  +44 1223 334761    Fax:  +44 1223 334679-   ------------------------------  # Date: Fri, 14 Dec 2001 17:10:43 GMT + From: Anne & Lynn Wheeler <lynn@garlic.com>c! Subject: Re: The demise of compaqc) Message-ID: <ubsh1pw4c.fsf@earthlink.net>   * nmm1@cus.cam.ac.uk (Nick Maclaren) writes: > : > In MVT, the return code was the bottom 8 bits of R15 :-) > @ > [ For those who didn't use it, R15 was also the address of the > program on entry. ]g > F > I can't remember the second APAR, but it was on the 'fixed' version.F > IBM's eventual solution was about 1K bytes long, mostly of copyrightA > notices.  We had a IEFBR14A, with extra function, from c. 1973.c  ; there was also link-edit apars about specifying re-entrant,a? serial-reusable, etc options to bind the code into load librarytC ... affecting could it be executed directly from shared, R/O memory  (i.e. BLDL list).   B In a multiple step batch program ... there might be specific stepsF that effectively only created or destroyed files (datasets) but didn'tC actually need to execute any code (aka "DD" statements) ... but jobr6 step semantics required an EXEC statement specifying a@ program. IEFBR14 as a dummy program could be specified. However,D subsequent job steps could test the condition code from the previousD job step (which would be the aggregate of the condition from each ofE the DD statements and the EXEC statement). Subsequent job steps couldeE check for aggregate succesful (each zeros) condition code (the return A code from the EXEC program execution plus the condition code froml each DD statement).    random past iefbr14 postings3 http://www.garlic.com/~lynn/99.html#81 Perfect Codel3 http://www.garlic.com/~lynn/99.html#85 Perfect Code F http://www.garlic.com/~lynn/99.html#96 IEFBR14 cookie from www.ibm.com? http://www.garlic.com/~lynn/2001e.html#60 Estimate JCL overheads   -- nH Anne & Lynn Wheeler   | lynn@garlic.com -  http://www.garlic.com/~lynn/    ------------------------------   Date: 14 Dec 2001 17:40:23 GMT( From: nmm1@cus.cam.ac.uk (Nick Maclaren)! Subject: Re: The demise of compaqI0 Message-ID: <9vddi7$bpj$1@pegasus.csx.cam.ac.uk>  ) In article <ubsh1pw4c.fsf@earthlink.net>,o- Anne & Lynn Wheeler <lynn@garlic.com> writes:  |> f> |> there was also link-edit apars about specifying re-entrant,B |> serial-reusable, etc options to bind the code into load libraryF |> ... affecting could it be executed directly from shared, R/O memory |> (i.e. BLDL list).   It's coming back to me now ....n  = Did you know that there have also been bugs in quite a few of  the versions of /bin/true? :-)     Regards, Nick Maclaren,* University of Cambridge Computing Service,> New Museums Site, Pembroke Street, Cambridge CB2 3QH, England. Email:  nmm1@cam.ac.uk/ Tel.:  +44 1223 334761    Fax:  +44 1223 334679s   ------------------------------  % Date: Fri, 14 Dec 2001 12:59:08 -0500 5 From: "Fred Kleinsorge" <kleinsorge@star.zko.dec.com>m! Subject: Re: The demise of compaqa2 Message-ID: <a9rS7.610$BK1.15808@news.cpqcorp.net>  G Sander Vesik wrote in message <1008250583.37922@haldjas.folklore.ee>...u< >In comp.arch Robert Harley <harley@estephe.inria.fr> wrote: >.: >> "Fred Kleinsorge" <kleinsorge@star.zko.dec.com> writes:H >>>But I have never shipped code that I could reasonable conclude had no? >>>bugs, unless it was small enough to fit on a couple screens.j > A >> That small?  I've shipped code up to a few thousand lines (100eG >> screens or so) for which I could reasonably conclude it had no bugs.n > G >Well, see, the problem seems to be that the size Fred talks about is arK >codebase of many millions of lines, also known as the Tru64 kernel (unlessa5 >I got my memory wrong and irts some other kernel)...a >e    5 Well, I have worked in the VMS kernel, but not Tru64.n  K I've shipped application code which has never had a bug reported on it, yetnI I still would not go as far as saying it is bug free.  Only that any bugs - that might be in it, have not yet been found.    ------------------------------  % Date: Fri, 14 Dec 2001 13:04:14 -0500L5 From: "Fred Kleinsorge" <kleinsorge@star.zko.dec.com>n! Subject: Re: The demise of compaqs2 Message-ID: <YdrS7.611$BK1.15894@news.cpqcorp.net>  K Strangely enough, the code that I wrote that customers/users seemed to have F the highest satisfaction with, was the terminal emulator I wrote for aJ defunct window system on VMS.  This code was *far* from bug free (heck, itE ran in kernel mode at IPL 2, and was many thousands of lines of C andwK Macro-32).  However, I worked in a continuous feedback loop with it's users L fixing bugs and adding features.  Most people were not upset when they found< a bug, as it usually was fixed in a few days or a few weeks.    E Franz-Josef Fornefeld wrote in message <9v9veq.ml.1@jo.dyndns.org>...  >Goran Larsson wrote:k >a0 >> My conclusion was that software should have aF >> software quality that is balanced. Not too bad as your customers goH >> elsewhere. Not too good as your customers don't need your help fixing >> bugs. >9B >We had the same experience. Our customers cancelled their service >contracts in the 90's.  > G >A well configured VMS system runs practically with no attention[1] andiE >so does our software[2]. It was more economic to call for service onA >demand. >h: >[1] our record holder is a VAX8250 with ~1500 days uptime. >[2] not bug free of course, but fairly robust   ------------------------------  % Date: Fri, 14 Dec 2001 19:43:48 +0100:3 From: Terje Mathisen <terje.mathisen@hda.hydro.com>i! Subject: Re: The demise of compaqu- Message-ID: <3C1A4864.BE5DBC29@hda.hydro.com>e   del cecchi wrote:iH > Ah, the story of the 1 line program by IBM that ended up with 7 or was@ > it 9 APARs being written against it.  The program was IEFBR14. > E > Perhaps it is just a blue urban legend, but I have seen accounts ont: > internal groups that included the APARs and the results.   Ah, Yes! :-)  F I'll try to explain IEFBR14, just in case there's someone young enough  here to not have heard about it!  @ This was IBM's kludgy workaround for a job control language that? couldn't handle files on it's own, it needed a dummy program tok associate them with.  H An immediate Branch to the value stored in register 14 would terminate aB program, so IEFBR14 was effectively identical to a MSDOS .COM file5 consisting of a single 0xC3 byte, the opcode for RET.l  E (The two-byte sequence CD 20 (INT 20h) would also do the same thing.)c  E Also equivalent to IEFBR14, those two programs both share the failing * that they don't set a proper return value.  5 On MSDOS the fix is to make a full program like this:a     mov ax,4c00h	   int 21hr  G (I just checked, the scary part was that I still remember those opcodesu and hex function codes. :-()  F This sets the return value (Errorlevel) in AL to 0, and then calls the ExitProgram (AH=4Ch) function.  E Afaik, IEFBR14 needed the same fix, i.e. zeroing out the return valuem	 register.   * BTW, these programs proves the old adage:   H "All programs contain at least one bug, and can be shortened by at least one instruction.G Therefore, all programs can be shortened to a single instruction, which- will be wrong."-   Terje    --    - <Terje.Mathisen@hda.hydro.com>@ "almost all programming can be viewed as an exercise in caching"   ------------------------------  % Date: Fri, 14 Dec 2001 09:55:23 +0000e- From: Roy Omond <Roy.Omond@BlueBubble.UK.Com>f Subject: Re: vms 3.x question 0 Message-ID: <3C19CC8B.2AEB4B0@BlueBubble.UK.Com>   mckinneyj@cpva.saic.com wrote:  Q > In article <3C190B38.923BA6C0@iee.org>, "a.carlini" <arcarlini@iee.org> writes:c > >l > >a > > Andy Burns wrote: G > >> If there are any .EXE files around you could try ANAL/IMAG/FULL onm
 > >> them ...) > > * > > If there aren't any .EXE files around,& > > then it's unlikely to be a VAX/VMS > > system disk :-)  > >r% > > I'd go for making an image backupn# > > of the disk and finding someones( > > with a suitable machine (VAX-11/7xx) > > to try it on!s > >; > > Antonioe > > 6 >         If there's a dump file present you might try >,& >         $ dump/blo=cou:1 sysdump.dmp >8D >         depending upon what state it was left in you might see theF >         VMS version, nodename, and hardware platform stored there...  N Similarly, look at the error log.  It should at least contain some timestamps.1 And the version of VMS will be recorded in there.   	 Roy Omondr Blue Bubble Ltd.   ------------------------------  # Date: Fri, 14 Dec 2001 18:10:13 GMT ' From: Don Sykes <anonymous@pacbell.net>e! Subject: Re: VMS file hex editor? + Message-ID: <3C1A4119.908B32E8@pacbell.net>   H You can also use TPU. It will avoid the record length problems with EDT.H While it's not a hex editor per se, I created a TPU section file w/ alotD of EDT type key assigns and if you press <ctrl>D on any character itE will display the decimal value in the message area. Then, like in EDT-; just press PF1+KP3 and you can enter the new decimal value.OF If your interested you can download this & other custom VMS tools from  http://alphase.com/VMSTools.html   Dona   frank brown wrote: > N > Is there a hex editor available for VAX/VMS?  I want to change some bytes in > a binary file. >  > http://www.inwa.net/~frog/   ------------------------------  % Date: Fri, 14 Dec 2001 13:07:35 -0500I5 From: "Fred Kleinsorge" <kleinsorge@star.zko.dec.com>nH Subject: Re: Writing a device driver: virtual/physical address questions2 Message-ID: <7hrS7.612$BK1.16007@news.cpqcorp.net>  $ Jan Vorbrueggen wrote in message ...8 >"Fred Kleinsorge" <kleinsorge@star.zko.dec.com> writes: >=G >> Well, I wouldn't say that it is a good practice for a device to knowS aboutWH >> page table formats.  Makes it platform, and perhaps even OS specific. > < >I would agree in principle. However, I would think that any high-performanceJ >device contains a processor executing a stored program anyway. So all the OSK >has to do is to download the routine(s) that walk the page tables into them% >device - say, in Java byte code 8-)?g >     & You are a sick puppy.  Java byte code.   ------------------------------  % Date: Fri, 14 Dec 2001 13:08:59 -0500R5 From: "Fred Kleinsorge" <kleinsorge@star.zko.dec.com>4H Subject: Re: Writing a device driver: virtual/physical address questions2 Message-ID: <pirS7.613$BK1.16026@news.cpqcorp.net>  $ Jan Vorbrueggen wrote in message ...8 >"Fred Kleinsorge" <kleinsorge@star.zko.dec.com> writes: >MG >> Well, I wouldn't say that it is a good practice for a device to knowI aboutwH >> page table formats.  Makes it platform, and perhaps even OS specific. >c< >I would agree in principle. However, I would think that any high-performanceJ >device contains a processor executing a stored program anyway. So all the OSK >has to do is to download the routine(s) that walk the page tables into thek% >device - say, in Java byte code 8-)?h >e    D To be specific, I've seen all kinds of twisted, sick things done forD performance.  But once you bring Java into it... you've defeated any& performance you were trying to get ;-)   ------------------------------  % Date: Fri, 14 Dec 2001 19:44:52 +0100h, From: "Sjaak Bosman @ BBI.nl" <Sjaak@BBI.nl> Subject: WSSIZE and AWSA4 Message-ID: <3c1a46cd$0$218$4d4ebb8e@news.nl.uu.net>  , This is a multi-part message in MIME format.  + ------=_NextPart_000_000F_01C184D7.CC7354B0  Content-Type: text/plain;c 	charset="iso-8859-1"g+ Content-Transfer-Encoding: quoted-printable@   Hi All,e  I Ever wanted to visualize the Working Set Size behaviour? Check out this =dI example (WSSIZE.COM) and an example to quickly use it (RUN_WSSIZE.COM). =oD It's really nice to see how AWSA works when invoking or quiting an = image.  J You can modify RUN_WSSIZE to view only processes from a specific user or =I processes running a particular image etc. Lexical-freaks know how to do =1 it, else just send me a mail.a    Please let me know your comment.  ; Be aware that the PIPE command is being used in WSSIZE.COM!<   Sjaak@BBI.nl     --- cut here ---   $ ! =hJ *************************************************************************= **J $ ! *                                                                    =      *J $ ! * (c) RUN_WSSIZE.COM                                                 =      *J $ ! *                                                                    =      * $ ! =$J *************************************************************************= ** $ !e $ ! =eJ ------------------------------------------------------------*************= ** $ !,; $ ! Copyright    : Barendse & Bosman Office Automation B.V.c: $ !                C. Kouwenbergzoom 221     -------------; $ !                3065 GK  ROTTERDAM       | Info@BBI.nl | : $ !                The Netherlands           ------------- $ !tH $ ! Description  : See WSSIZE.COM for details. This procedure shows an = example ) $ !                how to use WSSIZE.COM.iE $ !                Specify (a part of) the process-name you want to =- display-< $ !                in P1, the scale (Kb/chr) in P2 and the = refresh-interval# $ !                (seconds) in P3.m $ !  $ ! =-J ------------------------------------------------------------*************= ** $ !cA $ main:                                                       ! =o MAINROUTINEp $    ! $    prcnam  =3D "''P1'" $    scale   =3D P2  $    refresh =3D P3  $    !+ $    IF scale   .EQ. 0 THEN scale   =3D 100s+ $    IF refresh .EQ. 0 THEN refresh =3D   3t $    !  $    prv =3D F$SETPRV( "WORLD" ) $    @WSSIZE      -n         'scale'   -r         'refresh' - G         " F$LOCATE( ""''prcnam'"", F$GETJPI( pid, ""PRCNAM"" ) ) .NE. = ) F$LENGTH( F$GETJPI( pid, ""PRCNAM"" ) ) ", $    ! $    prv =3D F$SETPRV( prv ) $    !A $ EXIT                                                        ! =- ENDMAINROUTINE $ !- $ ! =eJ ------------------------------------------------------------*************= ** =20u --- cut here ---   $ ! =mJ *************************************************************************= **J $ ! *                                                                    =      *J $ ! * (c) WSSIZE.COM                                                     =      *J $ ! *                                                                    =      * $ ! =rJ *************************************************************************= ** $ !t $ ! =lJ ------------------------------------------------------------*************= ** $ !e; $ ! Copyright    : Barendse & Bosman Office Automation B.V. : $ !                C. Kouwenbergzoom 221     -------------; $ !                3065 GK  ROTTERDAM       | Info@BBI.nl |o: $ !                The Netherlands           ------------- $ ! H $ ! Version      : V5.0.03 - 15 November 2001 (originaly build in 1989!) $ !cF $ ! Description  : This procedure shows a dynamic display of working = sets oncJ $ !                your OpenVMS-system. The following characters will be = used:> $ !o( $ !                chr | from    | until( $ !                ----+---------+------* $ !                 .  | 0       | DEFAULT( $ !                 -  | DEFAULT | QUOTA) $ !                 +  | QUOTA   | EXTENT / $ !                 P  | number of pages in use>0 $ !                 S  | actual working set size $ !E/ $ ! Parameters   : input  P1 > Scale in Kb/Chr.r@ $ !                            Default is a scale of 100 Kb/Chr.; $ !                       P2 > Refresh interval in seconds. C $ !                            Default is an interval of 5 seconds. I $ !                       P3 > Match condition. Use 'pid' to refer to a =w process ? $ !                            when including F$GETJPI in the =  condition-string.tD $ !                            Default is all interactive processes.H $ !                output    > Dynamic display showing working set size. $ !sG $ ! Example      : $ @WSSIZE "20" "3" "" ! Focus on WSDEF (small scale)t $ !o- $ ! Remarks      : o This procedures assumes: C $ !                  W.S.-DEFAULT <=3D W.S.-QUOTA <=3D W.S.-EXTENT.RH $ !                o When specifying a match-condition in P3, no syntax-0 $ !                  validation will take place.H $ !                o This procedure uses the PIPE-command. Please modifyB $ !                  if your OpenVMS-system doesn't support this = command.G $ !                o Use this procedure as you like, but please don't =e removeF $ !                  this header and copyright-note. Send an e-mail to4 $ !                  Info@BBI.nl with your comments. $ !)% $ ! Changed      : by      : +author; / $ !                version : +release; - +date;s* $ !                reason  : +description; $ !t $ ! =rJ ------------------------------------------------------------*************= ** $ ! A $ main:                                                       ! =  MAINROUTINE  $    ! $    GOSUB initializew $    ! $    CALL  wssize  $    ! $    GOSUB finishn $    !A $ EXIT                                                        ! =  ENDMAINROUTINE $ !a $ ! =rJ ------------------------------------------------------------*************= **   $ ! =)J ------------------------------------------------------------*************= ** $ !i
 $ initialize:e $    !( $    PIPE esc =3D "" ; esc[0,8] =3D %X1B( $    PIPE csi =3D "" ; csi[0,8] =3D %X9B $    !G $    ! Clear display, set cursor off, define scroll area and terminal =g width. $    ! =E ---------------------------------------------------------------------t $    !0 $    WRITE SYS$OUTPUT "''csi'r''csi'J''csi'?25l" $    ! $    bgn_line  =3D  2o $    end_line  =3D 24h $    ! $    SET TERMINAL /WIDTH=3D132 $    ! $    ! Set input-parameters. $    ! --------------------- $    !# $    IF P1 .EQS. "" THEN P1 =3D 100h! $    IF P2 .EQS. "" THEN P2 =3D 5oC $    IF P3 .EQS. "" THEN P3 =3D " F$GETJPI( pid, ""MODE"" ) .EQS. =n ""INTERACTIVE"" "i $    ! $    scale    =3D P1 $    interval =3D P2 $    match    =3D P3 $    ! $ RETURN $ !/ $ ! =rJ ------------------------------------------------------------*************= **   $ ! =1J ------------------------------------------------------------*************= ** $ !hA $ wssize:                                                       =a
 SUBROUTINE $    ! $    ! Set exit-condition. $    ! ------------------- $    !( $    ctrl =3D F$ENVIRONMENT( "CONTROL" ) $    SET CONTROL=3DY) $    ON  CONTROL_Y THEN GOTO exit_handlerl $    ! $    !1 $    ! Write header, display first screen normal.>1 $    ! ------------------------------------------- $    !H $    WRITE SYS$OUTPUT F$FAO( "''csi'H''csi'7m!14AS''csi'27m  >!8* 1!9* =D 2!9* 3!9* 4!9* 5!9* 6!9* 7!9* 8!9* 9!9* 0!9* 1", "''scale' Kb/chr" ) $    toggle_bold =3D "''csi'1m"  $    ! $    repeat:	 $       !n $       ! Start at first line. $       ! --------------------	 $       !t $       line =3D bgn_linek	 $       ! 1 $       ! Toggle display between normal and bold.e1 $       ! ---------------------------------------n	 $       ! ' $       IF toggle_bold .EQS. "''csi'1m"  $       THEN& $          toggle_bold =3D "''csi'22m"% $          inverse     =3D "''csi'1m"0 $       ELSE% $          toggle_bold =3D "''csi'1m"c& $          inverse     =3D "''csi'22m"
 $       ENDIF 	 $       !B $       ! First process. $       ! --------------	 $       !0  $       pid =3D F$PID( context ): $       while: IF .NOT. (pid .NES. "") THEN GOTO end_while $          ! $          IF 'match'i $          THENe $             !>0 $             ! Determine and Set diplay-values.0 $             ! -------------------------------- $             ! 2 $             prcnam =3D F$GETJPI( pid, "PRCNAM" ) $             ! D $             g1 =3D (F$GETJPI( pid, "DFWSCNT"  ) / 2 / 'scale') ! = WSDEFAULT or PQL_DWSDEFAULT D $             g2 =3D (F$GETJPI( pid, "WSQUOTA"  ) / 2 / 'scale') ! = WSQUOTA or PQL_DWSQUOTAlD $             g3 =3D (F$GETJPI( pid, "WSEXTENT" ) / 2 / 'scale') ! = WSEXTENT or PQL_DWSEXTENTr $             g3 =3D g3 - g2 $             g2 =3D g2 - g1I $             IF g1 .GT. 132 THEN PIPE g1 =3D 132 ; g2 =3D 132 ; g3 =3D =  132t> $             IF g2 .GT. 132 THEN PIPE g2 =3D 132 ; g3 =3D 1321 $             IF g3 .GT. 132 THEN PIPE g3 =3D 132v $             !uJ $             p  =3D F$GETJPI( pid, "PPGCNT" ) + F$GETJPI( pid, "GPGCNT" = )L. $             s  =3D F$GETJPI( pid, "WSSIZE" )) $             p  =3D p / 2 / 'scale' + 15s) $             s  =3D s / 2 / 'scale' + 15c $             !g* $             IF p .GT. 132 THEN p =3D 132 $             sign =3D "S"0 $             IF s .GT. 132 THEN PIPE sign =3D =7 "''inverse'''esc'(0`''esc'(B''toggle_bold'" ; s =3D 132  $             !o& $             ! Construct output-line.& $             ! ---------------------- $             !r. $             fixed  =3D F$FAO( "!2ZL", line )I $             string =3D F$FAO( "!136AS", F$FAO( "''csi'''fixed'H!14AS: =e- !''g1'*.!''g2'*-!''g3'*+''csi'K", prcnam  ) )y $             !e $             ! Write line.r $             ! -----------m $             !.8 $             WRITE SYS$OUTPUT "''toggle_bold'" + string4 $             WRITE SYS$OUTPUT "''csi'A''csi'''p'CP": $             WRITE SYS$OUTPUT "''csi'A''csi'''s'C''sign'" $             ! G $             ! Set for next line. Wait if this was the last line for =  this $             ! display. $             ! =e: ---------------------------------------------------------- $             !p $             line =3D line + 1nG $             IF line .EQ. end_line THEN PIPE WAIT 00:00:'interval' ; =A line =3D bgn_line] $             !r $          ENDIF $          ! $          ! Next process. $          ! ------------- $          !# $          pid =3D F$PID( Context )  $          ! $          GOTO whileh $       end_while:	 $       !c) $       ! Clear display beyond last line.e) $       ! -------------------------------e	 $       !c $       IF line .EQ. bgn_linet $       THEN4 $          WRITE SYS$OUTPUT "''csi'2H''csi'J''csi'A" $       ELSE, $          WRITE SYS$OUTPUT "''csi'J''csi'A"
 $       ENDIFt	 $       !a( $       ! Wait before starting again.=20% $       ! --------------------------- 	 $       !u $       WAIT 00:00:'interval'y	 $       !  $    GOTO repeat $    ! $ EXIT   $ exit_handler:e $    !  $    ! Restore process settings.  $    ! ------------------------- $    != $    PIPE SET NOCONTROL=3D(Y,T) ; IF ctrl .NES. "" THEN SET =d CONTROL=3D('ctrl') $    SET TERMINAL /WIDTH=3D80a9 $    WRITE SYS$OUTPUT "''csi'r''csi'J''csi'?25h''csi'22m"e $    ! $ EXITA $                                                               =o
 ENDSUBROUTINE  $ !  $ ! =oJ ------------------------------------------------------------*************= **   $ ! = J ------------------------------------------------------------*************= ** $ !'A $ finish:                                                       =p
 SUBROUTINE $    !# $    ! Clear screen. Set cursor on.s# $    ! ----------------------------s $    !: $    WRITE SYS$OUTPUT "''csi'r''csi'2J''csi'?25h''csi'22m" $    ! $ EXITA $                                                               =C
 ENDSUBROUTINE  $ !, $ ! =4J ------------------------------------------------------------*************= **    + ------=_NextPart_000_000F_01C184D7.CC7354B0m Content-Type: text/html; 	charset="iso-8859-1"b+ Content-Transfer-Encoding: quoted-printablep  > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD>3 <META content=3D"text/html; charset=3Diso-8859-1" =s http-equiv=3DContent-Type>6 <META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR> <STYLE></STYLE>  </HEAD>e <BODY bgColor=3D#ffffff>J <DIV><FONT face=3DArial size=3D2>Hi All,<BR><BR>Ever wanted to visualize = the Working=20H Set Size behaviour? Check out this example (WSSIZE.COM) and an example = to=20cI quickly use it (RUN_WSSIZE.COM). It's really nice to see how AWSA works =  when=20 * invoking or quiting an image.</FONT></DIV>4 <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>I <DIV><FONT face=3DArial size=3D2>You can modify RUN_WSSIZE to view only =i processes=20C from a specific user or processes running a particular image etc. =i Lexical-freaks=20f9 know how to do it, else just send me a mail.</FONT></DIV> 4 <DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>: <DIV><FONT face=3DArial size=3D2>Please let me know your = comment.<BR><BR>Be aware=20uF that the PIPE command is being used in WSSIZE.COM!<BR><BR></FONT><A=202 href=3D"mailto:Sjaak@BBI.nl"><FONT face=3DArial=20. size=3D2>Sjaak@BBI.nl</FONT></A><BR><BR></DIV>J <DIV><FONT face=3DArial size=3D2><FONT face=3D"Courier New" size=3D2>--- = cut here=20f ---</FONT></FONT></DIV>t3 <DIV><BR><FONT face=3D"Courier New" size=3D2>$ !=20-J *************************************************************************=
 **<BR>$=20 !=20J *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=J &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=J nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=J bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=J sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=G p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20n *<BR>$ ! * (c)=20wJ RUN_WSSIZE.COM&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=J ;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=J &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=J nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=+ bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20o *<BR>$ !=20dJ *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=J &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=J nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=J bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=J sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=G p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20t *<BR>$ !=20rJ *************************************************************************=
 **<BR>$=20 !<BR>$ !=20iJ ------------------------------------------------------------*************=
 **<BR>$=20E !<BR>$ ! Copyright&nbsp;&nbsp;&nbsp; : Barendse &amp; Bosman Office =-
 Automation=20- B.V.<BR>$=20J !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;=20jC C. Kouwenbergzoom 221&nbsp;&nbsp;&nbsp;&nbsp; -------------<BR>$=20 J !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;=20KJ 3065 GK&nbsp; ROTTERDAM&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | </FONT><A=209 href=3D"mailto:Info@BBI.nl"><FONT face=3D"Courier New"=20 E size=3D2>Info@BBI.nl</FONT></A><FONT face=3D"Courier New" size=3D2> =.	 |<BR>$=20uJ !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;=20s The =uJ Netherlands&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20D -------------<BR>$ !<BR>$ ! Description&nbsp; : See WSSIZE.COM for = details. This=20" procedure shows an example<BR>$=20J !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;=20e how to use WSSIZE.COM.<BR>$=20J !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;=20m@ Specify (a part of) the process-name you want to display<BR>$=20J !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;=20a@ in P1, the scale (Kb/chr) in P2 and the refresh-interval<BR>$=20J !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;=20v! (seconds) in P3.<BR>$ !<BR>$ !=20SJ ------------------------------------------------------------*************=
 **<BR>$=20	 !<BR>$=20SJ main:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=J bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=J sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=J p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=( ;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20? ! MAINROUTINE<BR>$&nbsp;&nbsp;&nbsp; !<BR>$&nbsp;&nbsp;&nbsp; =- prcnam&nbsp; =3D=20*6 "''P1'"<BR>$&nbsp;&nbsp;&nbsp; scale&nbsp;&nbsp; =3D = P2<BR>$&nbsp;&nbsp;&nbsp;=20D refresh =3D P3<BR>$&nbsp;&nbsp;&nbsp; !<BR>$&nbsp;&nbsp;&nbsp; IF=205 scale&nbsp;&nbsp; .EQ. 0 THEN scale&nbsp;&nbsp; =3D =   100<BR>$&nbsp;&nbsp;&nbsp; IF=20G refresh .EQ. 0 THEN refresh =3D&nbsp;&nbsp; 3<BR>$&nbsp;&nbsp;&nbsp;=20 4 !<BR>$&nbsp;&nbsp;&nbsp; prv =3D F$SETPRV( "WORLD" = )<BR>$&nbsp;&nbsp;&nbsp;=20*( @WSSIZE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20F -<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 'scale'&nbsp;&nbsp;=20< -<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 'refresh'=20= -<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; " F$LOCATE( =  ""''prcnam'"",=20OJ F$GETJPI( pid, ""PRCNAM"" ) ) .NE. F$LENGTH( F$GETJPI( pid, ""PRCNAM"" ) = )=20J "<BR>$&nbsp;&nbsp;&nbsp; !<BR>$&nbsp;&nbsp;&nbsp; prv =3D F$SETPRV( prv=20" )<BR>$&nbsp;&nbsp;&nbsp; !<BR>$=20J EXIT&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=J sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=J p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=J ;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 ! ! ENDMAINROUTINE<BR>$ !<BR>$ !=20 J ------------------------------------------------------------*************= **</FONT></DIV>h< <DIV><FONT face=3D"Courier New" size=3D2></FONT>&nbsp;</DIV>7 <DIV><FONT face=3D"Courier New" size=3D2>--- cut here =  ---<BR></DIV></FONT>5 <DIV><FONT size=3D2><FONT face=3D"Courier New">$ !=20 J *************************************************************************=
 **<BR>$=20 !=20J *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=J &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=J nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=J bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=J sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=G p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20  *<BR>$ ! * (c)=20cJ WSSIZE.COM&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=J sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=J p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=J ;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=? &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20r *<BR>$ !=20nJ *&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=J &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=J nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=J bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=J sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=G p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20s *<BR>$ !=20 J *************************************************************************=
 **<BR>$=20 !<BR>$ !=20 J ------------------------------------------------------------*************=
 **<BR>$=20E !<BR>$ ! Copyright&nbsp;&nbsp;&nbsp; : Barendse &amp; Bosman Office = 
 Automation=20  B.V.<BR>$=20J !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;=20 C C. Kouwenbergzoom 221&nbsp;&nbsp;&nbsp;&nbsp; -------------<BR>$=202J !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;=20sJ 3065 GK&nbsp; ROTTERDAM&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | </FONT><A=203 href=3D"mailto:Info@BBI.nl"><FONT face=3D"Courier =l# New">Info@BBI.nl</FONT></A><FONT=20t face=3D"Courier New"> |<BR>$=20 J !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;=20w The =sJ Netherlands&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20E -------------<BR>$ !<BR>$ ! Version&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : =  V5.0.03 - 15=20WJ November 2001 (originaly build in 1989!)<BR>$ !<BR>$ ! Description&nbsp; =	 : This=20m< procedure shows a dynamic display of working sets on<BR>$=20J !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;=20 J your OpenVMS-system. The following characters will be used:<BR>$ !<BR>$=20J !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;=20 , chr | from&nbsp;&nbsp;&nbsp; | until<BR>$=20J !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;=20h ----+---------+------<BR>$=20nJ !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;&nbsp;=20-A .&nbsp; | 0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | DEFAULT<BR>$=20nJ !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;&nbsp;=20w! -&nbsp; | DEFAULT | QUOTA<BR>$=20!J !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;&nbsp;=20R, +&nbsp; | QUOTA&nbsp;&nbsp; | EXTENT<BR>$=20J !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;&nbsp;=20-( P&nbsp; | number of pages in use<BR>$=20J !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;&nbsp;=20 J S&nbsp; | actual working set size<BR>$ !<BR>$ ! Parameters&nbsp;&nbsp; : =  , input&nbsp; P1 &gt; Scale in Kb/Chr.<BR>$=20J !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=J &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= nbsp;&nbsp;&nbsp;=20) Default is a scale of 100 Kb/Chr.<BR>$=20 J !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=? &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 , P2 &gt; Refresh interval in seconds.<BR>$=20J !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=J &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= nbsp;&nbsp;&nbsp;=20, Default is an interval of 5 seconds.<BR>$=20J !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=? &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 @ P3 &gt; Match condition. Use 'pid' to refer to a process<BR>$=20J !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=J &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= nbsp;&nbsp;&nbsp;=208 when including F$GETJPI in the condition-string.<BR>$=20J !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=J &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= nbsp;&nbsp;&nbsp;=20- Default is all interactive processes.<BR>$=20sJ !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;=20-C output&nbsp;&nbsp;&nbsp; &gt; Dynamic display showing working set =o
 size.<BR>$=20tJ !<BR>$ ! Example&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : $ @WSSIZE "20" "3" "" ! = Focus=20& on WSDEF (small scale)<BR>$ !<BR>$ ! =, Remarks&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : o=20  This procedures assumes:<BR>$=20J !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=! &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 < W.S.-DEFAULT &lt;=3D W.S.-QUOTA &lt;=3D W.S.-EXTENT.<BR>$=20J !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;=20"= o When specifying a match-condition in P3, no syntax-<BR>$=20 J !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=! &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20-# validation will take place.<BR>$=20 J !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;=20J= o This procedure uses the PIPE-command. Please modify<BR>$=20EJ !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=! &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 < if your OpenVMS-system doesn't support this command.<BR>$=20J !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;=20 A o Use this procedure as you like, but please don't remove<BR>$=20tJ !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=! &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 9 this header and copyright-note. Send an e-mail to<BR>$=20 J !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=! &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20D. </FONT><A href=3D"mailto:Info@BBI.nl"><FONT=20H face=3D"Courier New">Info@BBI.nl</FONT></A><FONT face=3D"Courier New"> = with your=20B comments.<BR>$ !<BR>$ ! Changed&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :=203 by&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : +author;<BR>$=203J !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;=20-$ version : +release; - +date;<BR>$=20J !&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;=20!- reason&nbsp; : +description;<BR>$ !<BR>$ !=20nJ ------------------------------------------------------------*************=
 **<BR>$=20	 !<BR>$=20 J main:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=J bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=J sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=J p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=( ;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20F ! MAINROUTINE<BR>$&nbsp;&nbsp;&nbsp; !<BR>$&nbsp;&nbsp;&nbsp; GOSUB=20H initialize<BR>$&nbsp;&nbsp;&nbsp; !<BR>$&nbsp;&nbsp;&nbsp; CALL&nbsp;=20? wssize<BR>$&nbsp;&nbsp;&nbsp; !<BR>$&nbsp;&nbsp;&nbsp; GOSUB=20E' finish<BR>$&nbsp;&nbsp;&nbsp; !<BR>$=20cJ EXIT&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=J sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=J p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=J ;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=- &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20'! ! ENDMAINROUTINE<BR>$ !<BR>$ !=20SJ ------------------------------------------------------------*************= **</FONT></FONT></DIV> <DIV>&nbsp;</DIV>-/ <DIV><FONT face=3D"Courier New" size=3D2>$ !=20'J ------------------------------------------------------------*************=
 **<BR>$=20I !<BR>$ initialize:<BR>$&nbsp;&nbsp;&nbsp; !<BR>$&nbsp;&nbsp;&nbsp; PIPE = 
 esc =3D ""=20OG ; esc[0,8] =3D %X1B<BR>$&nbsp;&nbsp;&nbsp; PIPE csi =3D "" ; csi[0,8] =T =3D=20G %X9B<BR>$&nbsp;&nbsp;&nbsp; !<BR>$&nbsp;&nbsp;&nbsp; ! Clear display, =e
 set cursor=20TG off, define scroll area and terminal width.<BR>$&nbsp;&nbsp;&nbsp; !=20SJ ---------------------------------------------------------------------<BR>= $&nbsp;&nbsp;&nbsp;=20, !<BR>$&nbsp;&nbsp;&nbsp; WRITE SYS$OUTPUT=203 "''csi'r''csi'J''csi'?25l"<BR>$&nbsp;&nbsp;&nbsp; =' !<BR>$&nbsp;&nbsp;&nbsp;=20 G bgn_line&nbsp; =3D&nbsp; 2<BR>$&nbsp;&nbsp;&nbsp; end_line&nbsp; =3D=20sB 24<BR>$&nbsp;&nbsp;&nbsp; !<BR>$&nbsp;&nbsp;&nbsp; SET TERMINAL=20E /WIDTH=3D132<BR>$&nbsp;&nbsp;&nbsp; !<BR>$&nbsp;&nbsp;&nbsp; ! Set=20 - input-parameters.<BR>$&nbsp;&nbsp;&nbsp; !=20 J ---------------------<BR>$&nbsp;&nbsp;&nbsp; !<BR>$&nbsp;&nbsp;&nbsp; IF = P1=20-H .EQS. "" THEN P1 =3D 100<BR>$&nbsp;&nbsp;&nbsp; IF P2 .EQS. "" THEN P2 = =3D=20F 5<BR>$&nbsp;&nbsp;&nbsp; IF P3 .EQS. "" THEN P3 =3D " F$GETJPI( pid, =
 ""MODE"" )=20EJ .EQS. ""INTERACTIVE"" "<BR>$&nbsp;&nbsp;&nbsp; !<BR>$&nbsp;&nbsp;&nbsp;=20E scale&nbsp;&nbsp;&nbsp; =3D P1<BR>$&nbsp;&nbsp;&nbsp; interval =3D=20s7 P2<BR>$&nbsp;&nbsp;&nbsp; match&nbsp;&nbsp;&nbsp; =3D =D P3<BR>$&nbsp;&nbsp;&nbsp;=20 !<BR>$ RETURN<BR>$ !<BR>$ !=20J ------------------------------------------------------------*************= **</FONT></DIV>o <DIV>&nbsp;</DIV>o/ <DIV><FONT face=3D"Courier New" size=3D2>$ !=20pJ ------------------------------------------------------------*************=
 **<BR>$=20	 !<BR>$=20hJ wssize:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=J &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=J nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=J bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=* sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20C SUBROUTINE<BR>$&nbsp;&nbsp;&nbsp; !<BR>$&nbsp;&nbsp;&nbsp; ! Set=20>+ exit-condition.<BR>$&nbsp;&nbsp;&nbsp; !=20 J -------------------<BR>$&nbsp;&nbsp;&nbsp; !<BR>$&nbsp;&nbsp;&nbsp; ctrl = =3D=208 F$ENVIRONMENT( "CONTROL" )<BR>$&nbsp;&nbsp;&nbsp; SET=20B CONTROL=3DY<BR>$&nbsp;&nbsp;&nbsp; ON&nbsp; CONTROL_Y THEN GOTO=20? exit_handler<BR>$&nbsp;&nbsp;&nbsp; !<BR>$&nbsp;&nbsp;&nbsp;=20w@ !<BR>$&nbsp;&nbsp;&nbsp; ! Write header, display first screen=20# normal.<BR>$&nbsp;&nbsp;&nbsp; !=20$D ------------------------------------------<BR>$&nbsp;&nbsp;&nbsp;=203 !<BR>$&nbsp;&nbsp;&nbsp; WRITE SYS$OUTPUT F$FAO(=20bG "''csi'H''csi'7m!14AS''csi'27m&nbsp; &gt;!8* 1!9* 2!9* 3!9* 4!9* 5!9* =n 6!9* 7!9*=20? 8!9* 9!9* 0!9* 1", "''scale' Kb/chr" )<BR>$&nbsp;&nbsp;&nbsp; =& toggle_bold =3D=20= "''csi'1m"<BR>$&nbsp;&nbsp;&nbsp; !<BR>$&nbsp;&nbsp;&nbsp;=20s3 repeat:<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20&> !<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ! Start at first=203 line.<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; !=20n@ --------------------<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=206 !<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; line =3D=204 bgn_line<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20E !<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ! Toggle display between =;
 normal and=20s3 bold.<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; !=20&J ---------------------------------------<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
 ;&nbsp;=20B !<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IF toggle_bold .EQS.=206 "''csi'1m"<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20A THEN<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =p toggle_bold =3D=20I "''csi'22m"<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20n& inverse&nbsp;&nbsp;&nbsp;&nbsp; =3D=206 "''csi'1m"<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20A ELSE<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =t toggle_bold =3D=20H "''csi'1m"<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20& inverse&nbsp;&nbsp;&nbsp;&nbsp; =3D=207 "''csi'22m"<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20=1 ENDIF<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20:5 !<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ! First=20B6 process.<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; !=20: --------------<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20D !<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pid =3D F$PID( context=20G )<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; while: IF .NOT. (pid .NES. =; "") THEN=202 GOTO =G end_while<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20rB !<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IF=20E 'match'<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20uJ THEN<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs= p;&nbsp;=20;J !<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
 nbsp; !=20 Determine and Set=20J diplay-values.<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;=20e !=20J --------------------------------<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=' &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20SJ !<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= nbsp;=20% prcnam =3D F$GETJPI( pid, "PRCNAM"=20 J )<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= nbsp;=20J !<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= nbsp;=20I g1 =3D (F$GETJPI( pid, "DFWSCNT"&nbsp; ) / 2 / 'scale') ! WSDEFAULT or=20pJ PQL_DWSDEFAULT<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;&nbsp;=20<G g2 =3D (F$GETJPI( pid, "WSQUOTA"&nbsp; ) / 2 / 'scale') ! WSQUOTA or=20*J PQL_DWSQUOTA<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n= bsp;&nbsp;&nbsp;=20&C g3 =3D (F$GETJPI( pid, "WSEXTENT" ) / 2 / 'scale') ! WSEXTENT or=20nJ PQL_DWSEXTENT<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= nbsp;&nbsp;&nbsp;=20 g3 =3D g3 -=20J g2<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=	 &nbsp;=20b g2 =3D g2 -=20J g1<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=	 &nbsp;=20'< IF g1 .GT. 132 THEN PIPE g1 =3D 132 ; g2 =3D 132 ; g3 =3D=20J 132<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
 ;&nbsp;=20/ IF g2 .GT. 132 THEN PIPE g2 =3D 132 ; g3 =3D=20pJ 132<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
 ;&nbsp;=20" IF g3 .GT. 132 THEN PIPE g3 =3D=20J 132<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
 ;&nbsp;=20J !<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= nbsp;=20B p&nbsp; =3D F$GETJPI( pid, "PPGCNT" ) + F$GETJPI( pid, "GPGCNT"=20J )<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= nbsp;=20& s&nbsp; =3D F$GETJPI( pid, "WSSIZE"=20J )<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= nbsp;=20  p&nbsp; =3D p / 2 / 'scale' +=20J 15<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=	 &nbsp;=20s  s&nbsp; =3D s / 2 / 'scale' +=20J 15<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=	 &nbsp;=20;J !<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= nbsp;=20 IF p .GT. 132 THEN p =3D=20pJ 132<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
 ;&nbsp;=20 sign =3D=202J "S"<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
 ;&nbsp;=20" IF s .GT. 132 THEN PIPE sign =3D =6 "''inverse'''esc'(0`''esc'(B''toggle_bold'" ; s =3D=20J 132<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
 ;&nbsp;=20J !<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
 nbsp; !=20 Construct=20J output-line.<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n= bsp;&nbsp;&nbsp;=20n !=20J ----------------------<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs= p;&nbsp;&nbsp;&nbsp;&nbsp;=20pJ !<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= nbsp;=20& fixed&nbsp; =3D F$FAO( "!2ZL", line=20J )<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= nbsp;=20< string =3D F$FAO( "!136AS", F$FAO( "''csi'''fixed'H!14AS:=203 !''g1'*.!''g2'*-!''g3'*+''csi'K", prcnam&nbsp; )=20;J )<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= nbsp;=20J !<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
 nbsp; !=20 Write=20J line.<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb= sp;&nbsp;=20 !=20J -----------<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb= sp;&nbsp;&nbsp;=20J !<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= nbsp;=20& WRITE SYS$OUTPUT "''toggle_bold'" +=20J string<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
 bsp;&nbsp;=20; WRITE SYS$OUTPUT=20sJ "''csi'A''csi'''p'CP"<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp= ;&nbsp;&nbsp;&nbsp;&nbsp;=20 WRITE SYS$OUTPUT=20;J "''csi'A''csi'''s'C''sign'"<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=" ;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20J !<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
 nbsp; !=208 Set for next line. Wait if this was the last line for=20J this<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs= p;&nbsp;=20> !=20J display.<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;=20; !=20J ----------------------------------------------------------<BR>$&nbsp;&nbs=A p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20=J !<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= nbsp;=20 line =3D line +=20J 1<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&= nbsp;=20C IF line .EQ. end_line THEN PIPE WAIT 00:00:'interval' ; line =3D=20bJ bgn_line<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;= &nbsp;&nbsp;=20b? !<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20-C ENDIF<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20 F !<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ! Next=20H process.<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; !=20J -------------<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =  F !<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pid =3D =	 F$PID(=20iG Context )<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20bD !<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; GOTO=201 while<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20b6 end_while:<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20I !<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ! Clear display beyond last=20b3 line.<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; !=20 J -------------------------------<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =  : !<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IF line .EQ.=204 bgn_line<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20G THEN<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; WRITE =&
 SYS$OUTPUT=20pD "''csi'2H''csi'J''csi'A"<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20G ELSE<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; WRITE =b
 SYS$OUTPUT=20&< "''csi'J''csi'A"<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=201 ENDIF<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20bJ !<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ! Wait before starting again. =  . <BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; !=20G ---------------------------<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20/2 !<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; WAIT=20< 00:00:'interval'<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20E !<BR>$&nbsp;&nbsp;&nbsp; GOTO repeat<BR>$&nbsp;&nbsp;&nbsp; !<BR>$=200 EXIT</FONT></DIV>e <DIV>&nbsp;</DIV>$, <DIV><FONT face=3D"Courier New" size=3D2>$ =' exit_handler:<BR>$&nbsp;&nbsp;&nbsp;=20;, !<BR>$&nbsp;&nbsp;&nbsp; ! Restore process =% settings.<BR>$&nbsp;&nbsp;&nbsp; !=20i2 -------------------------<BR>$&nbsp;&nbsp;&nbsp; =  !<BR>$&nbsp;&nbsp;&nbsp; PIPE=204 SET NOCONTROL=3D(Y,T) ; IF ctrl .NES. "" THEN SET=209 CONTROL=3D('ctrl')<BR>$&nbsp;&nbsp;&nbsp; SET TERMINAL=20l6 /WIDTH=3D80<BR>$&nbsp;&nbsp;&nbsp; WRITE SYS$OUTPUT=20D "''csi'r''csi'J''csi'?25h''csi'22m"<BR>$&nbsp;&nbsp;&nbsp; !<BR>$=20J EXIT<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=J p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=J ;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=J &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=J nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n= bsp;&nbsp;&nbsp;=20p ENDSUBROUTINE<BR>$ !<BR>$ !=20J ------------------------------------------------------------*************= **</FONT></DIV>  <DIV>&nbsp;</DIV>r5 <DIV><FONT size=3D2><FONT face=3D"Courier New">$ !=20bJ ------------------------------------------------------------*************=
 **<BR>$=20	 !<BR>$=20tJ finish:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=J &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=J nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=J bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=* sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20D SUBROUTINE<BR>$&nbsp;&nbsp;&nbsp; !<BR>$&nbsp;&nbsp;&nbsp; ! Clear = screen. Set=20& cursor on.<BR>$&nbsp;&nbsp;&nbsp; !=205 ----------------------------<BR>$&nbsp;&nbsp;&nbsp; =s !<BR>$&nbsp;&nbsp;&nbsp;=20a WRITE SYS$OUTPUT => "''csi'r''csi'2J''csi'?25h''csi'22m"<BR>$&nbsp;&nbsp;&nbsp;=20	 !<BR>$=20pJ EXIT<BR>$&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=J p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=J ;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=J &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=J nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n= bsp;&nbsp;&nbsp;=20t ENDSUBROUTINE<BR>$ !<BR>$ !=20J ------------------------------------------------------------*************=( **<BR></FONT></DIV></FONT></BODY></HTML>  - ------=_NextPart_000_000F_01C184D7.CC7354B0--    ------------------------------   End of INFO-VAX 2001.694 ************************