1 INFO-VAX	Fri, 06 Apr 2001	Volume 2001 : Issue 193       Contents:' Re: - OpenVMS ever to be on Intel chip? ' Re: - OpenVMS ever to be on Intel chip?  Re: Another Win for OpenVMS  Re: Another Win for OpenVMS  Re: Another Win for OpenVMS  Re: Another Win for OpenVMS & Re: booting a 3300 for the first time.& Re: booting a 3300 for the first time.& Re: booting a 3300 for the first time.+ Re: CI based cluster for max I/O perf. How? / Compaq quitting with Alpha Workstations ??????? 3 RE: Compaq quitting with Alpha Workstations ??????? 3 Re: Compaq quitting with Alpha Workstations ??????? 3 Re: Compaq quitting with Alpha Workstations ??????? 3 Re: Compaq quitting with Alpha Workstations ??????? 3 Re: Compaq quitting with Alpha Workstations ??????? 3 Re: Compaq quitting with Alpha Workstations ??????? 3 Re: Compaq quitting with Alpha Workstations ??????? 3 Re: Compaq quitting with Alpha Workstations ??????? 3 Re: Compaq quitting with Alpha Workstations ??????? 3 Re: Compaq quitting with Alpha Workstations ??????? 3 Re: Compaq quitting with Alpha Workstations ???????   Re: DCL question: piping command  Re: DCL question: piping command  Re: DCL question: piping command  Re: DCL question: piping command> Re: EV7 and EV8 for the low end (was: VMS-Related: Affordable)A RE: How do I redefine the alias between SYSCOMMON and VMS$COMMON? A RE: How do I redefine the alias between SYSCOMMON and VMS$COMMON? A Re: How do I redefine the alias between SYSCOMMON and VMS$COMMON? A Re: How do I redefine the alias between SYSCOMMON and VMS$COMMON? A Re: How do I redefine the alias between SYSCOMMON and VMS$COMMON? A Re: How do I redefine the alias between SYSCOMMON and VMS$COMMON? A Re: How do I redefine the alias between SYSCOMMON and VMS$COMMON? # LINK-I-DATMISMCH since some patch ? ' Re: LINK-I-DATMISMCH since some patch ?  Local Domain *Mismatch*  Re: Local Domain *Mismatch*  Re: Local Domain *Mismatch*  Re: Local Domain *Mismatch* & Login problem on Alpha 400 running 6.2* Re: Login problem on Alpha 400 running 6.2* Re: Login problem on Alpha 400 running 6.2 Re: Missing QMAN$MASTER.DAT ! Object protection on tcp sockets? % Re: Object protection on tcp sockets? 0 Re: OVMS Tech Update Presentations [and Mozilla]0 Re: OVMS Tech Update Presentations [and Mozilla]0 Re: OVMS Tech Update Presentations [and Mozilla]0 Re: OVMS Tech Update Presentations [and Mozilla]* Re: Problems with threads on VMS AXP 7.1-2* Re: Problems with threads on VMS AXP 7.1-2 Re: pthreads + printf  Re: pthreads + printf  Q: Unmapping global section  Re: Q: Unmapping global section  Re: Q: Unmapping global section  Re: Q: Unmapping global section  Re: Q: Unmapping global section  Re: Q: Unmapping global section  Re: Q: Unmapping global section  Ramdisk for AXP OpenVMS  Re: Ramdisk for AXP OpenVMS  Re: Ramdisk for AXP OpenVMS  Re: Restart TCP/IP Services  Re: Restart TCP/IP Services  Re: Restart TCP/IP Services $ Seeking CD-R/CD-RW SCSI INQUIRY data( Re: Seeking CD-R/CD-RW SCSI INQUIRY data( Re: Seeking CD-R/CD-RW SCSI INQUIRY dataD Re: Support for CD-R (was: Re: Seeking CD-R/CD-RW SCSI INQUIRY data) Re: TSM and terminal servers?  Re: TSM and terminal servers?  Re: UCX .DAT Files - Path? Re: UCX .DAT Files - Path? UCX 5.1 BG device problem  Re: Updated information  VMS ad in another UK trade mag" Re: VMS ad in another UK trade mag" VMS equivalent of Unix wc command? Re: VMS-Related: Affordable  Re: VMS-Related: Affordable  Re: VMS-Related: Affordable  Re: ZXLp-L2 bugcheck analysis  Re: ZXLp-L2 bugcheck analysis $ [ANNOUNCE] Release of OpenSSL 0.9.6a  F ----------------------------------------------------------------------  $ Date: Fri, 6 Apr 2001 09:08:26 -0700- From: "Bill Pedersen" <pedersen@ccsscorp.com> 0 Subject: Re: - OpenVMS ever to be on Intel chip?9 Message-ID: <3acde9fa$0$838$8eec23a@newsreader.tycho.net>   , ELN has been run on the Charon-VAX emulator.  I Am currently working with a couple customers with the emulator on OpenVMS G Alpha for support of OpenVMS VAX applications which they do not wish to  migrate (or can not) to Alpha.  B Newest version (MV3500/3600) which supports 64MB is still in beta.   Looks JUST LIKE A VAX.  J Issues are, of course, the extra network adapter and a console device.  OnF workstation console can be another x-window.  On server have developedE technique of using a LAT device is applicaiton mode as the "console".    --
 Bill Pedersen  CCSS Corporation www.CCSScorp.com 831-336-2708  : "Dave Weatherall" <djweath@attglobal.net> wrote in message/ news:DTiotGxQ0bj6-pn2-dO13EFYdIgvz@localhost... F > On Tue, 13 Mar 2001 19:06:23, kaplow_r@eisner.encompasserve.org.mars > (Bob Kaplow) wrote:  > A > > In article <QUtr6.8$na.430@news.enterprise.net>, "NewsReader" & <NewsReader@NotOnYourLife.Com> writes:K > > > I read the tech .pdfs for Charon & it says for PC memory emulation is  16Mb, > > > max. Surely this is a little limiting? > > I > > The current version emulates a MicroVAX-II. The MV2 was limited to 16  MB. So4 > > it's as limiting as the hardware it's emulating. > > L > > An MV3000 is supposed to be in the works. And some folks probably need aJ > > 6000 or 7000 class emulator. I wonder if they can do SMP emulation :-) > # > Could one run ELN on it I wonder.  >  > -- > Cheers - Dave.   ------------------------------   Date: 6 Apr 2001 17:17:12 GMT & From: davidsen@tmr.com (bill davidsen)0 Subject: Re: - OpenVMS ever to be on Intel chip?: Message-ID: <9aktmn$2nkq$1@newssvr05-en0.news.prodigy.com>  9 In article <3acde9fa$0$838$8eec23a@newsreader.tycho.net>, , Bill Pedersen <pedersen@ccsscorp.com> wrote:. | ELN has been run on the Charon-VAX emulator. | K | Am currently working with a couple customers with the emulator on OpenVMS I | Alpha for support of OpenVMS VAX applications which they do not wish to   | migrate (or can not) to Alpha. | D | Newest version (MV3500/3600) which supports 64MB is still in beta. |  | Looks JUST LIKE A VAX. | L | Issues are, of course, the extra network adapter and a console device.  OnH | workstation console can be another x-window.  On server have developedG | technique of using a LAT device is applicaiton mode as the "console".   >   I'd re-ask the previous question, can SMP be used to improveE performance? And given the relative price and performance of ia86 vs. F Alpha, isn't the market limited to people who need to run VAX softwareD (VMS? OpenUNIX?) but can't or won't use a real VAX? If the markey isF people who can't afford a VAX, I would guess the price of the softwareD is going to have to be pretty low or they can't afford that, either.  G   Those are questions, not comments or anything, I'm just curious about " the implementation and motivation.   --  <   bill davidsen <davidsen@tmr.com>  CTO, TMR Associates, IncG "I am lost. I am out looking for myself. If I should come back before I ; return, please ask me to wait."  -seen in a doctor's office    ------------------------------   Date: 6 Apr 2001 06:18:34 GMT 2 From: mathog@seqaxp.bio.caltech.edu (David Mathog)$ Subject: Re: Another Win for OpenVMS, Message-ID: <9ajn3q$n0s@gap.cco.caltech.edu>  a In article <9ajjsn$lk1@gap.cco.caltech.edu>, mathog@seqaxp.bio.caltech.edu (David Mathog) writes: t >In article <oWLy6.34229$Wz.9323509@typhoon.ne.mediaone.net>, "Terry C. Shannon" <terryshannon@mediaone.net> writes: >>M >>E*Trade (unlike another online entity whose name begins with "E") relies on H >>OpenVMS to ensure that mission-critical apps are up 24x7. Which is why6 >>Charlie Matco relies on E*Trade for his IRA account. >> > C >I wonder if Chuck could log into his E*trade account at 22:00 PST  5 >05-APR-2001, because I sure couldn't get into mine.     <SNIP>  F Oh heck, this seems to be a symptom of old browser syndrome.  NetscapeD 4.03 had an expired Verisign certificate, which caused a warning butC usually allows a connection after that.  Not this time, apparently. F Probably the redirect goes straight to 443 and the server/browser justI won't set up a connection with the bad certificate.  Too bad it failed by K hanging though.  Lynx -head http://trading.etrade.com/ from another machine I would fail too because the port is wrong and there's no server running on H port 80, but it would work to the www.etrade.com machine running its web browser on port 80.   C In the words of the immortal Roseanne Roseanna-Danna: "Never mind."    David Mathog mathog@seqaxp.bio.caltech.edu ? Manager, sequence analysis facility, biology division, Caltech     ------------------------------  # Date: Fri, 06 Apr 2001 14:42:52 GMT 4 From: "Terry C. Shannon" <terryshannon@mediaone.net>$ Subject: Re: Another Win for OpenVMS= Message-ID: <MBkz6.43700$Wz.10513299@typhoon.ne.mediaone.net>   ? "David Mathog" <mathog@seqaxp.bio.caltech.edu> wrote in message & news:9ajn3q$n0s@gap.cco.caltech.edu...L > In article <9ajjsn$lk1@gap.cco.caltech.edu>, mathog@seqaxp.bio.caltech.edu (David Mathog) writes:I > >In article <oWLy6.34229$Wz.9323509@typhoon.ne.mediaone.net>, "Terry C. , Shannon" <terryshannon@mediaone.net> writes: > >>L > >>E*Trade (unlike another online entity whose name begins with "E") relies onJ > >>OpenVMS to ensure that mission-critical apps are up 24x7. Which is why8 > >>Charlie Matco relies on E*Trade for his IRA account. > >> > > D > >I wonder if Chuck could log into his E*trade account at 22:00 PST6 > >05-APR-2001, because I sure couldn't get into mine. >  > <SNIP> > H > Oh heck, this seems to be a symptom of old browser syndrome.  NetscapeF > 4.03 had an expired Verisign certificate, which caused a warning but) > usually allows a connection after that.   G Ah, Netscape... the browser for crash test dummies. I used to use it on L Windoze, but got sick of the multiple daily browser crashes and went over to> Internet Exploder. At least it is more reliable than Netscape.   ------------------------------  % Date: Fri, 06 Apr 2001 11:07:01 -0400 # From: Jim Agnew <Agnew@hsc.vcu.edu> $ Subject: Re: Another Win for OpenVMS+ Message-ID: <3ACDDB95.A8437865@hsc.vcu.edu>    and are you sure that your hard disk has not been read by every one on the web????  ;-)  (i use netscape, and encrypt my checkbook..P i figure that's where they can do the most damage, and not be totally paranoid.)   jim    "Terry C. Shannon" wrote:  > A > "David Mathog" <mathog@seqaxp.bio.caltech.edu> wrote in message ( > news:9ajn3q$n0s@gap.cco.caltech.edu...N > > In article <9ajjsn$lk1@gap.cco.caltech.edu>, mathog@seqaxp.bio.caltech.edu > (David Mathog) writes:K > > >In article <oWLy6.34229$Wz.9323509@typhoon.ne.mediaone.net>, "Terry C. . > Shannon" <terryshannon@mediaone.net> writes: > > >>N > > >>E*Trade (unlike another online entity whose name begins with "E") relies > onL > > >>OpenVMS to ensure that mission-critical apps are up 24x7. Which is why: > > >>Charlie Matco relies on E*Trade for his IRA account. > > >> > > > F > > >I wonder if Chuck could log into his E*trade account at 22:00 PST8 > > >05-APR-2001, because I sure couldn't get into mine. > > 
 > > <SNIP> > > J > > Oh heck, this seems to be a symptom of old browser syndrome.  NetscapeH > > 4.03 had an expired Verisign certificate, which caused a warning but+ > > usually allows a connection after that.  > I > Ah, Netscape... the browser for crash test dummies. I used to use it on N > Windoze, but got sick of the multiple daily browser crashes and went over to@ > Internet Exploder. At least it is more reliable than Netscape.   ------------------------------  % Date: Fri, 06 Apr 2001 16:19:46 +0100 - From: Tim Llewellyn <tim.llewellyn@bbc.co.uk> $ Subject: Re: Another Win for OpenVMS) Message-ID: <3ACDDE91.66FA21B7@bbc.co.uk>    "Terry C. Shannon" wrote:    > J > > Oh heck, this seems to be a symptom of old browser syndrome.  NetscapeH > > 4.03 had an expired Verisign certificate, which caused a warning but+ > > usually allows a connection after that.  > I > Ah, Netscape... the browser for crash test dummies. I used to use it on N > Windoze, but got sick of the multiple daily browser crashes and went over to@ > Internet Exploder. At least it is more reliable than Netscape.  N yes, but netscape is at least somewhat orthogonal to other applications on the sameK platform. When I had DSL installed the engineer had installed IE 5 before I  could P stop him. Guess when I discovered that my accounting application no longer works  M due to ActiveX incompatibility. Yes, when I really need to get those year end  accounts done yesterday :-(.     --6 Tim Llewellyn, OpenVMS Infrastructure, Remarcs Project0 MedAS at the BBC, Whiteladies Road, Bristol, UK.A Email tim.llewellyn@bbc.co.uk. Home tim.llewellyn@cableinet.co.uk   A I speak for myself only and my views in no way represent those of  MedAS or the BBC.    ------------------------------  % Date: Fri, 06 Apr 2001 11:24:30 +0100   From: steven.reece@quintiles.com/ Subject: Re: booting a 3300 for the first time. H Message-ID: <OF3C57CC3B.3FAFF4FA-ON80256A26.0037C1DC@qedi.quintiles.com>   I don't fully agree.G If Eric wants to use the VAX 3300 then he could either get a Q-Bus SCSI D adapter (like the CMD CQD220 series, although I wouldn't necessarilyE recommend this) or he could get a Storageworks shelf like a BA350, an < RZ28-VA, an HSD05 and an RRD40 or similar in a desktop case.K Connect the HSD05 up to the DSSI bus, shove it in the top-slot of the BA350 K and then chain the RRD40 off the SCSI connector on the shelf backplane (not 5 forgetting to adjust the termination as appropriate).   C Taking prices from the Prodec web site (www.prodec.co.uk) they have  RRD40          75 pounds RZ28-VA   75 pounds  HSD05          50 pounds  - They don't show a BA350 at the moment though.   9 Alternatively, one could try a KZQSA with an RRD40 on it.   C n.b. I've not dealt with Prodec and have no idea what they or their  equipment is like.   Steve.   John E. Malmberg wrote:  >>> F > Failing that, can someone point me to a list of cheap SCSI CD Drives" > known to work with the microvax?  7 Ok, first what bootable SCSI adaptor do you have in it?   B That little plug with an LED on it is not a SCSI terminator, it isD DSSI.  It is not electrically compatible with SCSI, even if you find% some of the internal cables will fit.   G If you look on the used market, you will probably find faster ALPHA and G VAX systems with SCSI busses built in for less than what a SCSI adaptor ' for either DSSI or a Q-BUS will go for.  <<<    ------------------------------   Date: 6 Apr 2001 09:22:16 -0500 3 From: malmberg@encompasserve.org (John E. Malmberg) / Subject: Re: booting a 3300 for the first time. 3 Message-ID: <BIycWn7JU9Yy@eisner.encompasserve.org>   H In article <OF3C57CC3B.3FAFF4FA-ON80256A26.0037C1DC@qedi.quintiles.com>,& steven.reece@quintiles.company writes: >  > I don't fully agree.I > If Eric wants to use the VAX 3300 then he could either get a Q-Bus SCSI F > adapter (like the CMD CQD220 series, although I wouldn't necessarily > recommend this)   D I do not know how to translate pounds to U.S.D., but I regularly see7 posts that things are more expensive outside the U.S.A.   J Used CMD controllers generally sell between $500.00 and $1000.00 depending3 on board options, warrantee and such. (U.S Dollars)   H As a contrast, I picked up a VAX 4000-500 advertised on comp.os.vms lastH fall that included a bootable SCSI adaptor for quite a bit less than theI minimum I have seen for just a SCSI adaptor.  And that included shipping.   J I also do not have that much invested in my Multia system either, and that includes it's CD-ROM.   F It is very possible to find used equipment with desired components for, much less than what the components sell for.   A hobbyist must look carefully.   D Note that the cheapest source of used 16MB or 32MB true parity SIMMS@ I have found are old commercial use 486 PC Servers and Desktops.  B They are often discarded (free) with memory intact.  A single usedA true parity SIMM from a reseller or an auction site usually sells 2 for far more than a PC containing a bunch of them.C (Of course do you really know what is in the PC before you buy it?)   7 > or he could get a Storageworks shelf like a BA350, an > > RZ28-VA, an HSD05 and an RRD40 or similar in a desktop case.M > Connect the HSD05 up to the DSSI bus, shove it in the top-slot of the BA350 M > and then chain the RRD40 off the SCSI connector on the shelf backplane (notM7 > forgetting to adjust the termination as appropriate).  >eE > Taking prices from the Prodec web site (www.prodec.co.uk) they havee > RRD40          75 pounds > RZ28-VA   75 poundsn > HSD05          50 pounds  I That configuration will work, and is probably supported.  I supposed thatfH someone will translate this to U.S. Dollars for a comparative reference.  K Do not forget to include the prices for the correct DSSI cables.  There area two styles of connectors.q  G Prices can and do vary wildly for the same compents on the used market.r  H I have seend used CD-ROMS that may work with OpenVMS from $50.00 (U.S.D)4 on up.  Finding one of them should not be a problem.  / > They don't show a BA350 at the moment though.  > ; > Alternatively, one could try a KZQSA with an RRD40 on it.q  E Unfortuately the console of a VAX 3300 has no idea on what to do withW a KZQSA.  ? After you get OpenVMS 5.3 (and possibly a SCSI patch) installedeI on the system by some other method, it will be happy with ODS-2 formattedg CD-ROMs and a KZQSA.  E > n.b. I've not dealt with Prodec and have no idea what they or their  > equipment is like. > Steve. >  > John E. Malmberg wrote:e >>>>G >> Failing that, can someone point me to a list of cheap SCSI CD DrivesN# >> known to work with the microvax?e >e9 > Ok, first what bootable SCSI adaptor do you have in it?a >eD > That little plug with an LED on it is not a SCSI terminator, it isF > DSSI.  It is not electrically compatible with SCSI, even if you find' > some of the internal cables will fit.r >fI > If you look on the used market, you will probably find faster ALPHA and I > VAX systems with SCSI busses built in for less than what a SCSI adaptor ) > for either DSSI or a Q-BUS will go for.  > <<<  -John* wb8tyw@qsl.network Personal Opinion Onlye   ------------------------------  % Date: Fri, 06 Apr 2001 15:16:18 +0100A% From: Alan Greig <a.greig@virgin.net> / Subject: Re: booting a 3300 for the first time.p8 Message-ID: <pljrct4rahgv2mc367sfu61v6ihr60tf5h@4ax.com>  A On 6 Apr 2001 09:22:16 -0500, malmberg@encompasserve.org (John E.e Malmberg) wrote:    E >I do not know how to translate pounds to U.S.D., but I regularly seel8 >posts that things are more expensive outside the U.S.A.  E Very roughly 1UK Pound = 1.5 USD (varies a bit obviously but the raten0 has been between 1.4 and 1.6 for several years).    F >> Taking prices from the Prodec web site (www.prodec.co.uk) they have >> RRD40          75 poundsg >> RZ28-VA   75 pounds >> HSD05          50 pounds J >That configuration will work, and is probably supported.  I supposed thatI >someone will translate this to U.S. Dollars for a comparative reference.n  - Roughly 110 dollars, 110 dollars,  75 dollarso     -- Alan   ------------------------------  # Date: Fri, 06 Apr 2001 14:46:06 GMT 3 From: Dave Harrold <DRHarrold.nospam@earthlink.net>a4 Subject: Re: CI based cluster for max I/O perf. How?8 Message-ID: <7hkrctglv5igqjhhgroqcuqeeiu040fm09@4ax.com>  
 Hi Lyndon,  2 On Wed, 04 Apr 2001 10:09:48 -0500, Lyndon Bartels  <lbartels@pressenter.com> wrote:   >Good Morning, >lF >I'd like to start a discussion on how to configure a CI based cluster? >for maximum I/O performance, redundancy, and availability. Buti >Performance is the key goal.i >eC >Why? The application I have on this cluster is more I/O and memory:? >intensive, not CPU intensive. Memory and CPU don't seem to be a$ >limiting factors. But I/O might be. > H >Anyway. I've been reading the cluster configuration part of the manualsH >and I'm thinking of using multiple CI (Star couplers). Each node member> >will have two(2) CIPCAs. And the HSJs will be dual-redundant.  D Let me start with a description of our environment.  We have 5 nodes= in our cluster, 3 8400s and 2 GS60Es.  Each node has 2 CIPCAseC installed.  We have 2 16 node Star Couplers (labeled A and B).  OnelE CIPCA (both paths) in a node is connected to the A star and the otherh! CIPCA is connected to the B star.   > All of our production data is served from dual-redundant HSJ50E controllers.  The HSJ50 only has one CI connection, so one controllertD from the pair is connected to the A star and the other controller to the B star.h   >wI >For CI, should I split the paths between couplers, or split by node? HowaI >should the nodes be numbered? I didn't get a clear understanding of thatC >from my reading.- >8  D I don't know if you can split the paths between stars or not.  We doF not.  You'll probably have to open a support call to determine if thatA is a legal configuration. (I would think it would work, however).   E The only advise I have gotten about numbering the nodes is to put thewE systems at the high numbers and the controllers at the lower numbers.rE We keep the node numbers the same on both stars (e.g. the node numberi" for an 8400 is 14 on both CIPCAs.)   >nG >For disks, considering the discussion on loosing pagedisks. Giving I'm G >using the same disks would it be better to have it connected to a hostsG >based SCSI bus, or run it through the CI? Should I be running disks in0K >a controller based RAID scenario? RAID 0+1? How many members of the Stripe G >set should I have. HOw should I have the disks arranged amoung the six- >SCSI shelves? >e  D I run all of my page and swap disks and dump disks off of local SCSIF busses on the node.  My opinion is that this is better performing thanB going across the CI for this task.  Also keeps the paging activity+ from interfering with the application data.d  A On the disk config, (stripes vs. RAID5 vs. RAID1, etc.) it reallyaC depends on your application use.  For example, RAID5 is good if youl7 have primarily reads, bad if you have lots of writes.  i  E A couple of pointers, though.  Make sure your RAID sets (of any type) E are spread across the SCSI busses of the controller.  We use 3 member B stripe sets for our database (then shadow at VMS across controllerC pairs), so each drive is on a bus.  Also, make sure that you defineeB the PREFERRED_PATH on a unit on the HSJ50.  We have run into timesF when all of the units were served by one controller in the pair.  ThenA you are not using the other I/O path to your systems.  Could be an. bottleneck in your performance, it was for us.  B The other thing to do is run VTDPY on your controllers.  This willA tell you how much of the controller cache you are actually using.e   > D >Also for disks, what would the best disk layout be. How should I beP >laying these disks out amoungst the controller shelves for optimum performance? > I >Almost nothing is out of the realm of possible discussion here. Fibre isaJ >out.  This is conceptual in nature only. And the concept is limited to CI >based storage only. >tC >I will of course continue my reading of both manuals and any whiten >papers I can find.i >  >Thanks in advance,o >c >Lyndon-   Hope that helped,-   Dave Harrold      V ======================================================================================V Dave Harrold                                          E-Mail: David_Harrold@Aurora.orgL Sr. Software Systems Engineer                         Phone : (414) 647-6204L Aurora Health Care                                    FAX   : (414) 647-4999I 3031 W. Montana Street                                Milwaukee, WI 53234i  X "A common mistake people make when trying to design something completely foolproof is to/ underestimate the ingenuity of complete fools."e   ------------------------------  $ Date: Fri, 6 Apr 2001 09:08:47 -04008 From: "Island Computers US Corp" <dbturner@islandco.com>8 Subject: Compaq quitting with Alpha Workstations ???????/ Message-ID: <tcrfuek7i39a50@news.supernews.com>r  H I heard a rumour about Compaq stating they were going to discontinue the" manufacture of Alpha workstations.  K Is this true - in a way I hope so... all the more business for us, but what  a stupid move by Compaq.H Or are they just trying to squeeze more billy boxen in there where there were AStations  K Or - maybe concentrating on Tru64 servers and Linux desktops.... hmmm not a 	 bad idea.c  E After all, Tru64 is a far superior product to VMS, right !?!?!?   ;0)      DT -- Island Computers US Corporationi 2700 Gregory Streetn	 Suite 150  Savannah GA 31404h Tel: 912 447 6622  Fax: 912 201 0096v sales@islandco.com www.islandco.com  C This message and any files transmitted with it are confidential andsJ may be privileged and/or subject to the provisions of privacy legislation.H They are intended solely for the use of the individual or entity to whomE they are addressed. If the reader of this message is not the intendedp
 recipient,G please notify Island Computers US Corp immediately and then delete thiss message.I You are notified that reliance on, disclosure of, distribution or copyingh of this message is prohibited.   ------------------------------  % Date: Fri, 06 Apr 2001 09:06:00 -0500.+ From: Christopher Smith <csmith@amdocs.com>s< Subject: RE: Compaq quitting with Alpha Workstations ???????L Message-ID: <3B55D7F383B0D31197D9009027541CBF0D9D1D20@cmiexch1.cmi.itds.com>   > -----Original Message-----? > From: Island Computers US Corp [mailto:dbturner@islandco.com]   6 > Or - maybe concentrating on Tru64 servers and Linux  > desktops.... hmmm not a2 > bad idea.0  G > After all, Tru64 is a far superior product to VMS, right !?!?!?   ;0)h  I If by "superior," you mean "newer," and "similar to something designed bydI AT&T thirty-some years ago."  And, I suppose, "it doesn't bother you witho' all of those confusing permissions." :)a   Regards,   Chris   ! Christopher Smith, Perl Developero Amdocs - Champaign, IL   /usr/bin/perl -e '? print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n");t '    ------------------------------  % Date: Fri, 06 Apr 2001 14:39:59 +0100,% From: Alan Greig <a.greig@virgin.net> < Subject: Re: Compaq quitting with Alpha Workstations ???????8 Message-ID: <r6hrctoc2rdhf7r3l2orrubt8efl005j1o@4ax.com>  = On Fri, 6 Apr 2001 09:08:47 -0400, "Island Computers US Corp"t <dbturner@islandco.com> wrote:  I >I heard a rumour about Compaq stating they were going to discontinue theg# >manufacture of Alpha workstations.i  E I suppose the question is what's the difference between a workstation.D and a server these days? Not sure how Compaq could stop making AlphaE workstations without also discontinuing low end servers. I'd be happycA for Compaq to sell me a GS320 based workstation at typical marketW" workstation pricing for example :)  E Btw, that Island PC164LX533V I just bought is performing nicely. I've>0 loaded VMS 7.3 EFT2 on it and everything is fine     -- Alan   ------------------------------  $ Date: Fri, 6 Apr 2001 10:48:34 -04005 From: "Fred Kleinsorge" <kleinsorge@star.zko.dec.com>d< Subject: Re: Compaq quitting with Alpha Workstations ???????2 Message-ID: <TGkz6.625$fB6.16807@news.cpqcorp.net>  H What's a workstation?  IMHO the last "true" workstation we built was theE VaxStation 4000.  I say that because it is the last platform where weeJ actually did something to the platform itself specific to graphics (we putC the graphics in the memory controller - the LCG).  Other than that,eL workstations have pretty much been servers without some of the RAS features.   The XP900 is a DS10.  H The workstation group itself long ago was disbanded, and the function ofH building workstations is part of AlphaServers.  The difference between aA Server and a Workstation is then how it's packaged, and licensed.b   _Fred   - Island Computers US Corp wrote in message ...DI >I heard a rumour about Compaq stating they were going to discontinue theh# >manufacture of Alpha workstations.o >bL >Is this true - in a way I hope so... all the more business for us, but what >a stupid move by Compaq. I >Or are they just trying to squeeze more billy boxen in there where there  >were AStationsm >sL >Or - maybe concentrating on Tru64 servers and Linux desktops.... hmmm not a
 >bad idea. >tF >After all, Tru64 is a far superior product to VMS, right !?!?!?   ;0) >  >e >DTt >--c  >Island Computers US Corporation >2700 Gregory Street
 >Suite 150 >Savannah GA 31404 >Tel: 912 447 6622 >Fax: 912 201 0096 >sales@islandco.com  >www.islandco.comu > D >This message and any files transmitted with it are confidential andK >may be privileged and/or subject to the provisions of privacy legislation. I >They are intended solely for the use of the individual or entity to whom,F >they are addressed. If the reader of this message is not the intended >recipient,yH >please notify Island Computers US Corp immediately and then delete this	 >message.eJ >You are notified that reliance on, disclosure of, distribution or copying >of this message is prohibited.0 >1 >4 >  >0   ------------------------------  % Date: Fri, 06 Apr 2001 16:00:35 +0100i- From: Tim Llewellyn <tim.llewellyn@bbc.co.uk>8< Subject: Re: Compaq quitting with Alpha Workstations ???????) Message-ID: <3ACDDA13.F5948443@bbc.co.uk>o   Alan Greig wrote:s  ? > On Fri, 6 Apr 2001 09:08:47 -0400, "Island Computers US Corp"c  > <dbturner@islandco.com> wrote: > K > >I heard a rumour about Compaq stating they were going to discontinue the % > >manufacture of Alpha workstations.  >0G > I suppose the question is what's the difference between a workstationa > and a server these days?  H Qualification of graphics controllers to work on the particular hardware platform seems to be the
 major factor.e    H > vBtw, that Island PC164LX533V I just bought is performing nicely. I've2 > loaded VMS 7.3 EFT2 on it and everything is fine >t  < ah, what made you go for that rather than the 433 au system?   Tim, still thinking about it.  --6 Tim Llewellyn, OpenVMS Infrastructure, Remarcs Project0 MedAS at the BBC, Whiteladies Road, Bristol, UK.A Email tim.llewellyn@bbc.co.uk. Home tim.llewellyn@cableinet.co.uk   A I speak for myself only and my views in no way represent those of  MedAS or the BBC.a   ------------------------------  $ Date: Fri, 6 Apr 2001 11:11:03 -04008 From: "Island Computers US Corp" <dbturner@islandco.com>< Subject: Re: Compaq quitting with Alpha Workstations ???????/ Message-ID: <tcrn3m2agem2b7@news.supernews.com>   H So Compaq will continue to  manufacture "desktop" Alpha servers that are? affordable by the average IT manager to stuff on his desktop?!?rG Especially when Compaq's added value licenses on a server compared to a ' Workstation bump up the price threefolde  K Oh... well they are such good machines it's worth paying $10K for a desktop ; Alpha, and those licenses will make great drawer liners !!!    Hmmm DT   -- Island Computers US CorporationD 2700 Gregory Street,	 Suite 150e Savannah GA 31404y Tel: 912 447 6622o Fax: 912 201 0096  sales@islandco.com www.islandco.com  C This message and any files transmitted with it are confidential andeJ may be privileged and/or subject to the provisions of privacy legislation.H They are intended solely for the use of the individual or entity to whomE they are addressed. If the reader of this message is not the intendedl
 recipient,G please notify Island Computers US Corp immediately and then delete thisD message.I You are notified that reliance on, disclosure of, distribution or copying  of this message is prohibited.    @ "Fred Kleinsorge" <kleinsorge@star.zko.dec.com> wrote in message, news:TGkz6.625$fB6.16807@news.cpqcorp.net...J > What's a workstation?  IMHO the last "true" workstation we built was theG > VaxStation 4000.  I say that because it is the last platform where wewL > actually did something to the platform itself specific to graphics (we putE > the graphics in the memory controller - the LCG).  Other than that, D > workstations have pretty much been servers without some of the RAS	 features.s >d > The XP900 is a DS10. >nJ > The workstation group itself long ago was disbanded, and the function ofJ > building workstations is part of AlphaServers.  The difference between aC > Server and a Workstation is then how it's packaged, and licensed.  >o > _Fredy >?/ > Island Computers US Corp wrote in message ... K > >I heard a rumour about Compaq stating they were going to discontinue the % > >manufacture of Alpha workstations.  > > I > >Is this true - in a way I hope so... all the more business for us, buto what > >a stupid move by Compaq.MK > >Or are they just trying to squeeze more billy boxen in there where theree > >were AStationse > >eL > >Or - maybe concentrating on Tru64 servers and Linux desktops.... hmmm not an > >bad idea. > >5H > >After all, Tru64 is a far superior product to VMS, right !?!?!?   ;0) > >d > >f > >DTn > >--t" > >Island Computers US Corporation > >2700 Gregory Street > >Suite 150 > >Savannah GA 31404 > >Tel: 912 447 6622 > >Fax: 912 201 0096 > >sales@islandco.coms > >www.islandco.comd > >yF > >This message and any files transmitted with it are confidential and@ > >may be privileged and/or subject to the provisions of privacy legislation.K > >They are intended solely for the use of the individual or entity to whomhH > >they are addressed. If the reader of this message is not the intended
 > >recipient,cJ > >please notify Island Computers US Corp immediately and then delete this > >message..L > >You are notified that reliance on, disclosure of, distribution or copying! > >of this message is prohibited.e > >D > >  > >  > >. >  >.   ------------------------------  $ Date: Fri, 6 Apr 2001 12:18:55 -04005 From: "Fred Kleinsorge" <kleinsorge@star.zko.dec.com>e< Subject: Re: Compaq quitting with Alpha Workstations ???????2 Message-ID: <A%lz6.633$fB6.17002@news.cpqcorp.net>  K The DS10 and the XP900 are the same hardware.  You can get it packaged as atD workstation or as a Server.   Licensed as a Server or a Workstation.  - Island Computers US Corp wrote in message ...vI >So Compaq will continue to  manufacture "desktop" Alpha servers that are @ >affordable by the average IT manager to stuff on his desktop?!?H >Especially when Compaq's added value licenses on a server compared to a( >Workstation bump up the price threefold ><L >Oh... well they are such good machines it's worth paying $10K for a desktop< >Alpha, and those licenses will make great drawer liners !!! >G >Hmmm. >DT@ >g >--t  >Island Computers US Corporation >2700 Gregory Street
 >Suite 150 >Savannah GA 31404 >Tel: 912 447 6622 >Fax: 912 201 0096 >sales@islandco.come >www.islandco.comg >oD >This message and any files transmitted with it are confidential andK >may be privileged and/or subject to the provisions of privacy legislation. I >They are intended solely for the use of the individual or entity to whomtF >they are addressed. If the reader of this message is not the intended >recipient, H >please notify Island Computers US Corp immediately and then delete this	 >message.2J >You are notified that reliance on, disclosure of, distribution or copying >of this message is prohibited.s >o > A >"Fred Kleinsorge" <kleinsorge@star.zko.dec.com> wrote in messagee- >news:TGkz6.625$fB6.16807@news.cpqcorp.net...sK >> What's a workstation?  IMHO the last "true" workstation we built was the0H >> VaxStation 4000.  I say that because it is the last platform where weI >> actually did something to the platform itself specific to graphics (wek putvF >> the graphics in the memory controller - the LCG).  Other than that,E >> workstations have pretty much been servers without some of the RASo
 >features. >> >> The XP900 is a DS10.u >>K >> The workstation group itself long ago was disbanded, and the function ofdK >> building workstations is part of AlphaServers.  The difference between apD >> Server and a Workstation is then how it's packaged, and licensed. >> >> _Fred >>0 >> Island Computers US Corp wrote in message ...L >> >I heard a rumour about Compaq stating they were going to discontinue the& >> >manufacture of Alpha workstations. >> >J >> >Is this true - in a way I hope so... all the more business for us, but >whath >> >a stupid move by Compaq.L >> >Or are they just trying to squeeze more billy boxen in there where there >> >were AStations >> >I >> >Or - maybe concentrating on Tru64 servers and Linux desktops.... hmmmr notb >a
 >> >bad idea.l >> >I >> >After all, Tru64 is a far superior product to VMS, right !?!?!?   ;0)s >> > >> > >> >DT >> >--# >> >Island Computers US Corporationd >> >2700 Gregory Street0
 >> >Suite 150  >> >Savannah GA 31404C >> >Tel: 912 447 6622n >> >Fax: 912 201 0096  >> >sales@islandco.com >> >www.islandco.com >> >G >> >This message and any files transmitted with it are confidential andsA >> >may be privileged and/or subject to the provisions of privacye
 >legislation.sL >> >They are intended solely for the use of the individual or entity to whomI >> >they are addressed. If the reader of this message is not the intendedp >> >recipient,K >> >please notify Island Computers US Corp immediately and then delete thise >> >message.E >> >You are notified that reliance on, disclosure of, distribution orm copyingh" >> >of this message is prohibited. >> > >> > >> > >> > >> >> >e >m   ------------------------------   Date: 6 Apr 2001 16:40:16 GMT12 From: mathog@seqaxp.bio.caltech.edu (David Mathog)< Subject: Re: Compaq quitting with Alpha Workstations ???????, Message-ID: <9akrhg$63h@gap.cco.caltech.edu>  j In article <tcrfuek7i39a50@news.supernews.com>, "Island Computers US Corp" <dbturner@islandco.com> writes:I >I heard a rumour about Compaq stating they were going to discontinue the # >manufacture of Alpha workstations.a  - I'm also really dubious about API's future.  f  I Samsung, seems to have woken up enough to produce their own motherboard.  F The UP1500 mobo is supposed to show up in July 2001. (Thanks Terry forK sending me off to look for this, otherwise I'd never have heard of it.)  TolG find it, go to www.samsung.com and enter "up1500" in the search field.  L It's based on the AMD 761 chipset and looks a heck of a lot like many of theK high end Athlon boards - except for the 800Mhz 21264 in it.  Why isn't it aoH 1Ghz part? Well, note that it uses an ATX power supply, but a 400W one. I Add up the currents and you'll find that this beast uses 4x as much power I as your average PC mobo!  It may well be that they can build a 1Ghz 21264 I but that it draws so much power that it can't be used with an ATX supply,hH so they went for the lower speed.  (Or maybe they just can't get to 1GhzI reliably.)  The UP1500 will hold 4Gb of memory - should have been >4Gb torI differentiate it from the PC crowd.  Again, what use is 64 bits if you'vehK only got 32 bits of memory to work with???  Anyway, they only list Linux aswL an OS, but it uses SRM, and since there's no evidence of anything else this < size in the pipeline, perhaps the VMS team will support it.   L The thing is, since this is otherwise identical to a bunch of Athlon boards I which cost less than $500 with the CPU, and since it's darn near certain oK that this beast will cost at least 4 times that much (if API/Compaq pricingsI is any guide), it would have to be 4X faster than a 1.3 Gz Athlon to make C it a winner on price/performance.  And that simply isn't possible. L  J The situation kind of reminds me of the Wankel engine cars that Mazda usedH to sell.  They were quite quick but burned a lot of gas - and the energyF crisis of the 70's killed them.  Given the current energy situation inF California (and maybe elsewhere in the US) this does not seem like theI ideal time to be trying to sell hardware that's at most 20-40% faster but4K uses 4X as much power.  I'm not sure there was _ever_ a good time to try toWP sell hardware that was 20-40% faster and cost 4X as much.  But at least they'll * probably sell a bunch to the weapons labs.   Regards,   David Mathog mathog@seqaxp.bio.caltech.edu ? Manager, sequence analysis facility, biology division, Caltech SJ **************************************************************************J *                                RIP VMS                                 *J **************************************************************************   ------------------------------  % Date: Fri, 06 Apr 2001 16:51:18 +0100 % From: Alan Greig <a.greig@virgin.net>v< Subject: Re: Compaq quitting with Alpha Workstations ???????8 Message-ID: <7rorctg8tfrjcf4k55r2b8sgk566nmm3pv@4ax.com>  1 On Fri, 06 Apr 2001 16:00:35 +0100, Tim Llewellynm  <tim.llewellyn@bbc.co.uk> wrote:    I >> vBtw, that Island PC164LX533V I just bought is performing nicely. I'ved3 >> loaded VMS 7.3 EFT2 on it and everything is finet >> > = >ah, what made you go for that rather than the 433 au system?e  D Speed really 533Mhz as opposed to 433Mhz. I strongly suspect that itD will run at 600Mhz as well if I just alter the jumpers but let's notD fry it just yet! Seems to run fine under VMS  (7.2-1 and 7.3 EFT2 at? any rate) . Ordered from Island 28/3/01. First delivery attemptfC 30/03/01 (FedEx screwed up but that's no Island's fault). Even camen@ with a UK power cord.  Sealed Digital PC164LX motherboard manual	 included.o  E I went for 256MB, extra Compaq 18G fast disk, Permedia graphics, Fast B Ethernet, LK411 style keyboard, CD-ROM, floppy and 3 button mouse.   >  >Tim, still thinking about it.   -- Alan   ------------------------------    Date: 07 Apr 2001 00:32:35 +0800, From: Paul Repacholi <prep@prep.synonet.com>< Subject: Re: Compaq quitting with Alpha Workstations ???????- Message-ID: <87elv6c7ks.fsf@prep.synonet.com>m  : "Island Computers US Corp" <dbturner@islandco.com> writes:  F > I heard a rumour about Compaq stating they were going to discontinue( > the manufacture of Alpha workstations.  D > Is this true - in a way I hope so... all the more business for us,? > but what a stupid move by Compaq.  Or are they just trying too> > squeeze more billy boxen in there where there were AStations  5 > Or - maybe concentrating on Tru64 servers and Linuxi# > desktops.... hmmm not a bad idea.e  B Well one word around the traps is that Samsung and API are pulling& the plug on Alpha. Just a rumour mind.  E As to you 164 LXs Dave, are the Q still making them? I doubt it. What9C you have is stock from near day one of the 164. What do you do whena it runs out.  F I heard a 'official Q line' explanation of how you run a small SW shop< where you need to give a developer a machine for testing....  ) You get a GS80, and give him a partition!t  : This was told with a very straight 'offical speek' face :(     -- i< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda..@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.   ------------------------------  $ Date: Fri, 6 Apr 2001 13:30:24 -04008 From: "Island Computers US Corp" <dbturner@islandco.com>< Subject: Re: Compaq quitting with Alpha Workstations ???????/ Message-ID: <tcrv8vm5m2fkc2@news.supernews.com>t  2 PC164LX....No they aren't making them any longer..  J But we do have a lot in stock - if I can sell all of the ones we have here" then I could theoretically retire.   :0)a     -- Island Computers US Corporation? 2700 Gregory Street6	 Suite 1507 Savannah GA 31404  Tel: 912 447 6622i Fax: 912 201 0096" sales@islandco.com www.islandco.com  C This message and any files transmitted with it are confidential andcJ may be privileged and/or subject to the provisions of privacy legislation.H They are intended solely for the use of the individual or entity to whomE they are addressed. If the reader of this message is not the intended 
 recipient,G please notify Island Computers US Corp immediately and then delete thise message.I You are notified that reliance on, disclosure of, distribution or copyinga of this message is prohibited.    9 "Paul Repacholi" <prep@prep.synonet.com> wrote in messagee' news:87elv6c7ks.fsf@prep.synonet.com...d< > "Island Computers US Corp" <dbturner@islandco.com> writes: >hH > > I heard a rumour about Compaq stating they were going to discontinue* > > the manufacture of Alpha workstations. > F > > Is this true - in a way I hope so... all the more business for us,A > > but what a stupid move by Compaq.  Or are they just trying too@ > > squeeze more billy boxen in there where there were AStations >i7 > > Or - maybe concentrating on Tru64 servers and LinuxV% > > desktops.... hmmm not a bad idea.- > D > Well one word around the traps is that Samsung and API are pulling( > the plug on Alpha. Just a rumour mind. >1G > As to you 164 LXs Dave, are the Q still making them? I doubt it. WhatnE > you have is stock from near day one of the 164. What do you do whend > it runs out. >tH > I heard a 'official Q line' explanation of how you run a small SW shop> > where you need to give a developer a machine for testing.... >h+ > You get a GS80, and give him a partition!  >c< > This was told with a very straight 'offical speek' face :( >  >n > --> > Paul Repacholi                               1 Crescent Rd.,9 > +61 (08) 9257-1001                           Kalamunda.tB >                                              West Australia 60760 > Raw, Cooked or Well-done, it's all half baked.   ------------------------------  # Date: Fri, 06 Apr 2001 17:48:23 GMTt= From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)l< Subject: Re: Compaq quitting with Alpha Workstations ???????0 Message-ID: <009FA228.B5D7B432@SendSpamHere.ORG>  j In article <tcrv8vm5m2fkc2@news.supernews.com>, "Island Computers US Corp" <dbturner@islandco.com> writes:3 >PC164LX....No they aren't making them any longer..h >sK >But we do have a lot in stock - if I can sell all of the ones we have herec# >then I could theoretically retire.  >t >:0)  H Hmm.  I'll be willing to test one out for you for the same price as that	 modem! :)6     --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COMi            tO city, n., 1. a place where trees are cut down and streets are named after them.i   ------------------------------  # Date: Fri, 06 Apr 2001 11:06:30 GMTe= From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-).) Subject: Re: DCL question: piping commandl0 Message-ID: <009FA1F0.916964F4@SendSpamHere.ORG>  I In article <3ACD4B43.2E1A2B4F@home.com>, Andy <kicsi2l8@home.com> writes:-E >dont see brian's answer, ecpet what you quoted,...but thanks Ill tryr >that tomorrow  G Where does Andy read his news?  I am curious and would like to find out?8 why my posts are not getting through to his news server.   --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM             TO city, n., 1. a place where trees are cut down and streets are named after them.e   ------------------------------  # Date: Fri, 06 Apr 2001 11:52:21 GMT 1 From: CSABA  HARANGOZO   <csabah@zipworld.com.au>a) Subject: Re: DCL question: piping commandl9 Message-ID: <V5iz6.1208$CN.202303@nostril.pacific.net.au>-   Andy <kicsi2l8@home.com> wrote: ; > I'm pretty new at this, so forgive me if I mess up terms.2  F > I want to create a shortcut in my login.com that does the following:H >    find all the batch queues (and print queues) that are STOPPED , put5 > it in a new file (retain.tmp), and print that file.    > My approach:E >   $ pipe show queue | search sys$input stopped /output=retain.tmp |h2 > close retain.tmp | print/que=whatever retain.tmp  ; 	Use "show queue/output=queues.lis" , then search that file 9 	"search queues.lis stopped /output=retain.tmp" . No needo! 	for the "close retain.tmp" line. 7 	As written later in this thread, you might want to usee5 	";"-s instead of "|". Please see $HELP PIPE as well.  	Hope this helps...s 					Cheers,		Csaban  I    ---------------------------------------------------------------------- E    * Csaba I. Harangozo     |    'To err is human', said the hedgehog E    * csabah@zipworld.com.au |           as he dismounted a wirebrush.cI    ----------------------------------------------------------------------);    EARTH::AUSTRALIA:[SYDNEY]HARANGOZO.CSABA;1, delete? [N]:r   ------------------------------  $ Date: Fri, 6 Apr 2001 13:56:35 -0400, From: "J. Scott Greig" <jsgreig@geminaq.com>) Subject: Re: DCL question: piping commandr1 Message-ID: <pqnz6.220$cS3.744@quark.idirect.com>b  / I believe it will work if you do the following:'  @ $ pipe show queue | search sys$input stopped/output=retain.tmp ; print/que=whatever retain.tmpI  K The magic is in the semi-colon instead of the vertical bar after the searchn command.   Scotto    + "Andy" <kicsi2l8@home.com> wrote in messageh" news:3ACD1328.5C864B53@home.com...; > I'm pretty new at this, so forgive me if I mess up terms.j > F > I want to create a shortcut in my login.com that does the following:H >    find all the batch queues (and print queues) that are STOPPED , put5 > it in a new file (retain.tmp), and print that file.r >  > My approach:E >   $ pipe show queue | search sys$input stopped /output=retain.tmp |l2 > close retain.tmp | print/que=whatever retain.tmp > I > Am I on the right track? First I tried it w/o the close command, and it6D > said locked by another user. when i run it this way it creates andD > prints the file, but for some reason only gets about 3 or 4 of theF > queues in question, when in reality I know there are about 50 queues > that are stopped.  > I > If i take it apart and take off everything after /output=retain.tmp, it H > creates the file with ALL the queues that are stopped, which is what i > need.  >p > Thanks in advance. >  > andy >l   ------------------------------  # Date: Fri, 06 Apr 2001 17:57:18 GMTo2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)) Subject: Re: DCL question: piping command 2 Message-ID: <2snz6.639$fB6.17003@news.cpqcorp.net>  I In article <3ACD1328.5C864B53@home.com>, Andy <kicsi2l8@home.com> writes:   E :I want to create a shortcut in my login.com that does the following: G :   find all the batch queues (and print queues) that are STOPPED , puts4 :it in a new file (retain.tmp), and print that file.  L   Use a simple DCL procedure and the f$getqui lexical function.  Not PIPE.    J   Your approach will fail if the text string "stopped" is found elsewhere    in the input, for instance...f  G   Related OpenVMS Ask The Wizard topics include (813), (1240), (3951), h   (4568), (4903) and (5188).  N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  $ Date: Fri, 6 Apr 2001 10:17:03 +0100' From: "LJEB" <LJEB@somewhere.out.there> G Subject: Re: EV7 and EV8 for the low end (was: VMS-Related: Affordable)d) Message-ID: <9ak1id$l02$1@soap.pipex.net>g  / I'm probably well out of my depth here, but,...f; is the cache to memory not mapped using physical addresses?h  I If it is, the process context becomes irrelevant, in fact is you have twolE threads/processes communicating via shared memory this would be a biguH advantage as the receiving process will have the data cached waiting for it.s  J I seem to remember that EV8 has the memory controller embedded in with the8 CPU (using RDRAM?), perhaps this is the reason for that?  	 Laurence.   I "Jan Vorbrueggen" <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de> wrote 
 in messageB news:y4vgojh319.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de...= > Kilgallen@eisner.decus.org.nospam (Larry Kilgallen) writes:  >kJ > > > At the simplest level, EV8 can be treated by the OS as 4 independent CPUs.w9 > > > With each "thread" appearing as an independent CPU.hE > > But wouldn't such use suffer from the various threads not sharingn@ > > an address space (tromping on cache in different fashions) ? >nJ > Yes. I suppose the rationale is that a thread that suffers a cache miss,K > especially all the way out to memory, is stalled (give or take hit-under->I > miss and out-of-order processing) for at least a hundred cycles anyway,o soJ > that doesn't matter so much. It does introduce some interesting code for > the thread scheduler...t >  > Jani   ------------------------------  % Date: Fri, 06 Apr 2001 07:57:43 -0400d2 From: "Kent, Philip  JW1811" <kent@jwfc.jfcom.mil>J Subject: RE: How do I redefine the alias between SYSCOMMON and VMS$COMMON?H Message-ID: <5B57189920E7D41190B500606D210686011A69D8@mailsvr.jfcom.mil>  F > From: Steve.Spires@yellgroup.com [mailto:Steve.Spires@yellgroup.com]) > Sent: Thursday, April 05, 2001 12:37 PM> > To: Info-VAX@Mvb.Saic.ComuH > Subject: How do I redefine the alias between SYSCOMMON and VMS$COMMON?  G I once had a System Administrator who was trying to clean up disk spacea start deleting [VMS$COMMON...].>  ; Then they selectively restored the data from a backup tape.i  K We had to use the following command to restore the relationship between thee+ [SYS0.SYSCOMMON] directory and [VMS$COMMON]y  3 $ SET FILE/ENTER=SYSTEM_DISK:[000000]VMS$COMMON.DIRh SYSTEM_DISK:[SYS0]SYSCOMMON.DIRf  9 Phil Kent (kent@jwfc.jfcom.mil    philip.kent@compaq.com)e   ------------------------------  % Date: Fri, 06 Apr 2001 13:24:35 +0100s  From: steven.reece@quintiles.comJ Subject: RE: How do I redefine the alias between SYSCOMMON and VMS$COMMON?H Message-ID: <OF872152D5.E5C96211-ON80256A26.0043B5A6@qedi.quintiles.com>  @ This could be a grey-cell problem but I think that the directory- specifications are the wrong way around here.m. $ SET FILE/ENTER=alias-filespec  file_to_alias  G The files should have been restored to [vms$common...] and then aliasedw4 into [sysn.syscommon...] using the set file command. IIRC.c Steve.   Phil Kent wrote:> >>>Then they selectively restored the data from a backup tape.  K We had to use the following command to restore the relationship between theu+ [SYS0.SYSCOMMON] directory and [VMS$COMMON]u  3 $ SET FILE/ENTER=SYSTEM_DISK:[000000]VMS$COMMON.DIR  SYSTEM_DISK:[SYS0]SYSCOMMON.DIR0 <<<h   ------------------------------    Date: 06 Apr 2001 05:34:02 +0800, From: Paul Repacholi <prep@prep.synonet.com>J Subject: Re: How do I redefine the alias between SYSCOMMON and VMS$COMMON?- Message-ID: <87r8z7116d.fsf@prep.synonet.com>f  . "Bart Zorn" <B.Zorn@TrueBit.n0spam.nl> writes:  E > I wonder, does your system run without the proposed corrections? InTF > other words, without any [VMS$COMMON] directory?  You mentioned it'sC > not clustered. In my cluster there is NO logical name pointing toyD > [VMS$COMMON...] and everything just works fine.  OTH, I didn't tryB > SET FILE/REMOVE SYS$SYSDEVICE:[000000]VMS$COMMON.DIR; However, I3 > wouldn't be surprised if I could live without it!z  A I think there was some comment that PCSI does use [vms$common...]4 rather than sys$common:[...]   -- c< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.a@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.   ------------------------------  # Date: Fri, 06 Apr 2001 16:13:16 GMTn8 From: hammond@not@peek.ppb.cpqcorp.net (Charlie Hammond)J Subject: Re: How do I redefine the alias between SYSCOMMON and VMS$COMMON?2 Message-ID: <wWlz6.632$fB6.17001@news.cpqcorp.net>  R In article <00256A25.005B3D70.00@quegw01.btyp>, Steve.Spires@yellgroup.com writes:  > >How do I redefine the alias between SYSCOMMON and VMS$COMMON?  7 I assume you mean SYS$SYSDEVICE:[SYSx]SYSCOMMON.DIR andt7                   SYS$SYSDEVICE:[000000]VMS$COMMON.DIR.d  F The answer is, if these already exist as separate files (directories),? then there is no direct way to make them aliases of each other.t  H SYSCOMMON.DIR is normaly created by a SET FILE /ENTER command similar to the following:  9     $ SET FILE /ENTER=SYS$SYSDEVICE:[SYS0]SYSCOMMON.DIR -e,         SYS$SYSDEVICE:[000000]VMS$COMMON.DIR  I But if SYS$SYSDEVICE:[SYS0]SYSCOMMON.DIR already exists, this won't work.b  N >I had a node for which I had restored the system disk from LEGATO backup ontoP >another node [the reasons aren't important in the context of the question], andQ >found that the OPS guys had incorrectly set a switch on the backup command which J >meant that [SYS0.SYSCOMMON...] wasn't backup up. I restored this from theO >original disk, but now I wonder, do I need to have a VMS$COMMON structure [via-Q >an alias] - the node isn't clustered - and if so, how do I do this using the SETr >FILE/ENTER command?  B Reading *EXACTLY* what you say, you  *MIGHT* be able to (1) DeleteE SYS$SYSDEVICE:[SYS0.SYSCOMMON...]*.*;*, then (2) execute the SET FILE08 command shown above, and then (3) restore the backup of " SYS$SYSDEVICE:[SYS0.SYSCOMMON...].  A I say "MIGHT" because I do not know exactly how you got into this2D situation -- in fact, I am not entirely clear on just what situation you actually have.  D In general, if you backup and restore an OpenVMS System disk WITHOUTE using /IMAGE on both the backup and restore, you are likely to end uptE with missing and/or duplicate files and/or directories.  Fixing this 3G can be a real problem -- many have failed.  Even if your system appearsfD to run O.K., there is a really good chance that the next time you do- an OpenVMS Upgrade it will not work properly.   C If it is at all possilbe, go back and get a good, /IMAGE backup andsJ restore it -- with /IMAGE.  In the long run, this will likely be far less 4 work and bother than trying to fix up what you have.  F If no good, /IMAGE backup can be had, I seriously suggest you considerE re-building your system disk from a new OpenVMS intallation.  If this:E is a production system, that is about the only way to ensure that youv8 are not creating major problems somewhere in the future.   -- nK     Charlie Hammond -- Compaq Computer Corporation -- Pompano Beach  FL USA H        (hammond@not@peek.ppb.cpqcorp.net -- remove "@not" when replying)J       All opinions expressed are my own and not necessarily my employer's.   ------------------------------  % Date: Fri, 06 Apr 2001 12:41:37 -0400x  From: norm.raphael@jamesbury.comJ Subject: Re: How do I redefine the alias between SYSCOMMON and VMS$COMMON?4 Message-ID: <C2256A26.005AD0D9.00@jklh21.valmet.com>  O If you have been "running" from this corrupted system disk after you "restored"  it, N then I agree with Charlie that you are almost surely in an "unresolved" state. Your& need to start from a known good point.  O The "correct" structure for a system disk is documented, however, and there aresP articles on how to fix the backlinks once the directory entries are in place, so if youO do, in fact, have multiple [sysn.syscommon] directories which are all the same,e youcP should be able to rename one of them, delete the others, and the fix everything, but9F only IF THE DISK IS MOUNTED PRIVATELY and NOT the RUNNING SYSTEM DISK.C So if your system is usable as is, and you have a spare spindle....t  4 Of course, in any case, be careful, be very careful.        % hammond@not on 04/06/2001 12:13:16 PMl   Please respond to hammond@noti   To:   Info-VAX@mvb.saic.coma cc:tK Subject:  Re: How do I redefine the alias between SYSCOMMON and VMS$COMMON?e        J In article <00256A25.005B3D70.00@quegw01.btyp>, Steve.Spires@yellgroup.com writes:c  > >How do I redefine the alias between SYSCOMMON and VMS$COMMON?  7 I assume you mean SYS$SYSDEVICE:[SYSx]SYSCOMMON.DIR andr7                   SYS$SYSDEVICE:[000000]VMS$COMMON.DIR.0  F The answer is, if these already exist as separate files (directories),? then there is no direct way to make them aliases of each other.i  H SYSCOMMON.DIR is normaly created by a SET FILE /ENTER command similar to the following:  9     $ SET FILE /ENTER=SYS$SYSDEVICE:[SYS0]SYSCOMMON.DIR -y,         SYS$SYSDEVICE:[000000]VMS$COMMON.DIR  I But if SYS$SYSDEVICE:[SYS0]SYSCOMMON.DIR already exists, this won't work.s  N >I had a node for which I had restored the system disk from LEGATO backup ontoP >another node [the reasons aren't important in the context of the question], andK >found that the OPS guys had incorrectly set a switch on the backup command. whichpJ >meant that [SYS0.SYSCOMMON...] wasn't backup up. I restored this from theO >original disk, but now I wonder, do I need to have a VMS$COMMON structure [via M >an alias] - the node isn't clustered - and if so, how do I do this using theo SET. >FILE/ENTER command?  B Reading *EXACTLY* what you say, you  *MIGHT* be able to (1) DeleteE SYS$SYSDEVICE:[SYS0.SYSCOMMON...]*.*;*, then (2) execute the SET FILEo7 command shown above, and then (3) restore the backup of " SYS$SYSDEVICE:[SYS0.SYSCOMMON...].  A I say "MIGHT" because I do not know exactly how you got into thisAD situation -- in fact, I am not entirely clear on just what situation you actually have.  D In general, if you backup and restore an OpenVMS System disk WITHOUTE using /IMAGE on both the backup and restore, you are likely to end upeD with missing and/or duplicate files and/or directories.  Fixing thisG can be a real problem -- many have failed.  Even if your system appearseD to run O.K., there is a really good chance that the next time you do- an OpenVMS Upgrade it will not work properly.   C If it is at all possilbe, go back and get a good, /IMAGE backup and0I restore it -- with /IMAGE.  In the long run, this will likely be far less 4 work and bother than trying to fix up what you have.  F If no good, /IMAGE backup can be had, I seriously suggest you considerE re-building your system disk from a new OpenVMS intallation.  If thisBE is a production system, that is about the only way to ensure that you 8 are not creating major problems somewhere in the future.   --K     Charlie Hammond -- Compaq Computer Corporation -- Pompano Beach  FL USASH        (hammond@not@peek.ppb.cpqcorp.net -- remove "@not" when replying)J       All opinions expressed are my own and not necessarily my employer's.   ------------------------------    Date: 07 Apr 2001 00:21:42 +0800, From: Paul Repacholi <prep@prep.synonet.com>J Subject: Re: How do I redefine the alias between SYSCOMMON and VMS$COMMON?- Message-ID: <87itkic82x.fsf@prep.synonet.com>I  4 rdeininger@mindspring.com (Robert Deininger) writes:  J > I don't remember all the icky little details any more.  I sort of recallJ > than VMS$COMMON was an alias, and was a subdirectory of [000000.SYSE] or > some such.  A That is the sign of a VMS update than did not complete correctly.s8 Seems for some reason, it got part way through, then????  D Sys$common is put into syse, a new sys$common built then all syse isA nuked after a boot into the new standard root. But this one seemst8 to have been interupted, or the roots resored from syse.   -- w< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.o@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.   ------------------------------  % Date: Fri, 06 Apr 2001 13:35:40 -0400r  From: norm.raphael@jamesbury.comJ Subject: Re: How do I redefine the alias between SYSCOMMON and VMS$COMMON?4 Message-ID: <C2256A26.005FC2F6.00@jklh21.valmet.com>   Paul,i   It must be late for you.  2 SYSE is the on-system-disk standalone backup root.+ SYSF is the OpenVMS upgrade temporary root.a   -Normt        / prep@prep.synonet.com on 04/06/2001 12:21:42 PMl  ' Please respond to prep@prep.synonet.coma   To:   Info-VAX@mvb.saic.com  cc:(K Subject:  Re: How do I redefine the alias between SYSCOMMON and VMS$COMMON?         4 rdeininger@mindspring.com (Robert Deininger) writes:  J > I don't remember all the icky little details any more.  I sort of recallJ > than VMS$COMMON was an alias, and was a subdirectory of [000000.SYSE] or > some such.  A That is the sign of a VMS update than did not complete correctly.i8 Seems for some reason, it got part way through, then????  D Sys$common is put into syse, a new sys$common built then all syse isA nuked after a boot into the new standard root. But this one seems 8 to have been interupted, or the roots resored from syse.   --< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.-@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.   ------------------------------  $ Date: Fri, 6 Apr 2001 09:02:03 +0200> From: "Jean-Francois Marchal" <jean-francois.marchal@x9000.fr>, Subject: LINK-I-DATMISMCH since some patch ?. Message-ID: <9ajpeu$4dg$1@reader1.imaginet.fr>   Bonjour  tous !  + I'm using 7.2-1 with the latest patches ...t  - Hadn't have to link new apps for a long time.  Now for a RDB installation,l  I get the following messages ...  5 %LINK-I-DATMISMCH, creation date of 31-AUG-2000 14:45h4 in shareable image SYS$COMMON:[SYSLIB]DECC$SHR.EXE;1& differs from date of 29-DEC-1999 03:56: in shareable image library VMI$ROOT:[SYSLIB]IMAGELIB.OLB;15 %LINK-I-DATMISMCH, creation date of 26-OCT-2000 00:49n2 in shareable image SYS$COMMON:[SYSLIB]LIBRTL.EXE;1& differs from date of 29-DEC-1999 03:53: in shareable image library VMI$ROOT:[SYSLIB]IMAGELIB.OLB;1  4 Same messages occur for all languages I tested with.* I updated ALL languages from the MARCH CD.  5 As these are information, I shouldn't be worried, BUTd9 RDB has declared my installation failed, probably becauser/ the IVP output does not match the expected one,r due to embedded messages.   5 Would anybody know what (patch ?) has caused the daten+ mismatch, and what should I do to fix this?u   Cordialement Jean-Francois Marchalt X9000 - LYON (FR)k   ------------------------------  $ Date: Fri, 6 Apr 2001 13:09:40 +02000 From: "Peter Flunger\(News/gmx\)" <p-i-b@gmx.at>0 Subject: Re: LINK-I-DATMISMCH since some patch ?0 Message-ID: <9ak839$qmu$1@rohrpostix.uta4you.at>  C "Jean-Francois Marchal" <jean-francois.marchal@x9000.fr> schrieb ima4 Newsbeitrag news:9ajpeu$4dg$1@reader1.imaginet.fr... > Bonjour  tous ! >0- > I'm using 7.2-1 with the latest patches ...8 >5/ > Hadn't have to link new apps for a long time.  > Now for a RDB installation, " > I get the following messages ... > 7 > %LINK-I-DATMISMCH, creation date of 31-AUG-2000 14:45 6 > in shareable image SYS$COMMON:[SYSLIB]DECC$SHR.EXE;1( > differs from date of 29-DEC-1999 03:56< > in shareable image library VMI$ROOT:[SYSLIB]IMAGELIB.OLB;17 > %LINK-I-DATMISMCH, creation date of 26-OCT-2000 00:49l4 > in shareable image SYS$COMMON:[SYSLIB]LIBRTL.EXE;1( > differs from date of 29-DEC-1999 03:53< > in shareable image library VMI$ROOT:[SYSLIB]IMAGELIB.OLB;1 >-6 > Same messages occur for all languages I tested with., > I updated ALL languages from the MARCH CD. >e7 > As these are information, I shouldn't be worried, BUT-; > RDB has declared my installation failed, probably because-1 > the IVP output does not match the expected one,  > due to embedded messages.  >-7 > Would anybody know what (patch ?) has caused the date1- > mismatch, and what should I do to fix this?e >  > Cordialement > Jean-Francois Marchald > X9000 - LYON (FR)f >d >e >   J Obviously at least on of the VMS patches you installed 'forgot' to replace the updated images in IMAGLIB.F That was a 'bug' formerly known from OpenVMS 7.1-1Hxx patches, I never" saw that happen on 7.1-2 or above.K The thing i find quite interesting is the path specified for IMAGLIB, whichd is VMI$ROOT:[SYSLIB]s Try ac< $ LIBRARY /REPLACE SYS$SHARE:IMAGELIB SYS$SHARE:DECC$SHR.EXE and at: $ LIBRARY /REPLACE SYS$SHARE:IMAGELIB SYS$SHARE:LIBRTL.EXE2 ( sys$share = sys$library = sys$sysroot:[SYSLIB] =1   sys$specific:[syslib] and sys$common:[syslib] )n and then install RDB   Hope that helps, Petert   ------------------------------  % Date: Fri, 06 Apr 2001 10:46:20 -0300m) From: fabio_compaq@ep-bc.petrobras.com.br   Subject: Local Domain *Mismatch*L Message-ID: <OF575D2B54.65C01A74-ON03256A26.004B17DE@ep-bc.petrobras.com.br>  : I have the following BIND Resolver configuration (UCX 4.2)   BIND Resolver Parameters     Local domain: * Mismatch *  (1)    System      State:     Started, Enableda     Transport: UDP   Domain:    my.domain.com   Retry:     4   Timeout:   4   Servers:   PIRARUCU, RUBI     Process     State:     Enabled     Transport:   Domain:    my.domain.com (2)   Retry:
   Timeout:
   Servers:    c I lost my Local Domain   (1) (my.domain.com)  and it appeared in the Process /Domain paragraph (2). < I am not a full specialist in UCX, so what I did wrong ?????   Regards-   FC   ------------------------------  % Date: Fri, 06 Apr 2001 16:23:14 +0200<5 From: Oswald Knoppers <Oswald.Knoppers@whitehouse.nl>e$ Subject: Re: Local Domain *Mismatch*- Message-ID: <3ACDD152.4198F29A@whitehouse.nl>8  * fabio_compaq@ep-bc.petrobras.com.br wrote: > < > I have the following BIND Resolver configuration (UCX 4.2) >  > BIND Resolver Parameters > " >  Local domain: * Mismatch *  (1) > 	 >  Systeme >  >   State:     Started, Enabledd >  >   Transport: UDP >   Domain:    my.domain.com  > Can you show the output of 'show comm' and 'show config comm'?  e > I lost my Local Domain   (1) (my.domain.com)  and it appeared in the Process /Domain paragraph (2). > > I am not a full specialist in UCX, so what I did wrong ?????  G If you issue a 'set name' command without using the '/system' qualifierI$ it will affect the process settings.   Regards,   Oswald   ------------------------------  % Date: Fri, 06 Apr 2001 16:24:09 +0200 2 From: "Thomas H. Pauli" <thomaspauli@arcormail.de>$ Subject: Re: Local Domain *Mismatch*+ Message-ID: <3ACDD189.9020300@arcormail.de>d  @ What does UCX SHOW COMM show ? If there is another domain noted,1 run SYS$MANAGER:UCX$CONFIG.COM, Core, Interfaces.b   Thomas  * fabio_compaq@ep-bc.petrobras.com.br wrote:  < > I have the following BIND Resolver configuration (UCX 4.2) >  > BIND Resolver Parameters > " >  Local domain: * Mismatch *  (1) > 	 >  System  >  >   State:     Started, Enabledt >  >   Transport: UDP >   Domain:    my.domain.com >   Retry:     4 >   Timeout:   4 >   Servers:   PIRARUCU, RUBIh > 
 >  Process >  >   State:     Enabled >  >   Transport:  >   Domain:    my.domain.com (2)
 >   Retry: >   Timeout: >   Servers: >  > e > I lost my Local Domain   (1) (my.domain.com)  and it appeared in the Process /Domain paragraph (2). > > I am not a full specialist in UCX, so what I did wrong ????? > 	 > Regards> >  > FC     -- d9 Thomas H. Pauli, Hammersteinstr.19, 14199 Berlin, Germanye   ------------------------------  % Date: Fri, 06 Apr 2001 12:06:30 -0300.) From: fabio_compaq@ep-bc.petrobras.com.br $ Subject: Re: Local Domain *Mismatch*L Message-ID: <OFE32ECDCB.F09ACE3F-ON03256A26.0052DC85@ep-bc.petrobras.com.br>  E I solved this problem with the shutdown of UCX. After the restart they parameters returned OK.vK I believe the NAME SERVICE was lost because I stopped it with STOP NAME and: tried to* reconfigure some parameters by UCX$CONFIG.   Regardsc   FC        C "Thomas H. Pauli" <thomaspauli@arcormail.de> em 06/04/2001 11:24:09m  > Favor responder a "Thomas H. Pauli" <thomaspauli@arcormail.de>             Info-VAX@Mvb.Saic.Comn      $ Assunto: Re: Local Domain *Mismatch*    @ What does UCX SHOW COMM show ? If there is another domain noted,1 run SYS$MANAGER:UCX$CONFIG.COM, Core, Interfaces.l   Thomas  * fabio_compaq@ep-bc.petrobras.com.br wrote:  < > I have the following BIND Resolver configuration (UCX 4.2) >n > BIND Resolver Parameters >R" >  Local domain: * Mismatch *  (1) >S	 >  Systemd >S >   State:     Started, Enabledf >1 >   Transport: UDP >   Domain:    my.domain.com >   Retry:     4 >   Timeout:   4 >   Servers:   PIRARUCU, RUBId > 
 >  Process >i >   State:     Enabled >S >   Transport:  >   Domain:    my.domain.com (2)
 >   Retry: >   Timeout: >   Servers: >Y >VF > I lost my Local Domain   (1) (my.domain.com)  and it appeared in the Process /Domain paragraph (2).> > I am not a full specialist in UCX, so what I did wrong ????? > 	 > RegardsI >s > FC     --9 Thomas H. Pauli, Hammersteinstr.19, 14199 Berlin, Germany    ------------------------------   Date: 6 Apr 2001 14:43:40 GMT   From: robert.harrison@ch.abb.com/ Subject: Login problem on Alpha 400 running 6.2a* Message-ID: <9akkms$n2k$1@news.netmar.com>   Hi,o   Can anyone help me?t  J We have a customer who cannot log in on any account. We had a DEC engineer who 7 tried, even he couldn't log in using the field account.   F I even talked the enduser through doing a minimal boot, set deffing toK SYS$SYSTEM and running authorize to set the pwd back to something sensible.iJ He set the password, rebooted in normal mode, tried to log in and couldn't& log in with this newly reset password.  J I got him to take down the details from the system account using authorize andt' everything looks OK - nothing disabled.e  < if anyone can help can they either post or email me. Please.   Many TIA   Rob       O  -----  Posted via NewsOne.Net: Free (anonymous) Usenet News via the Web  ----- M   http://newsone.net/ -- Free reading and anonymous posting to 60,000+ groups-I    NewsOne.Net prohibits users from posting spam.  If this or other posts.L made through NewsOne.Net violate posting guidelines, email abuse@newsone.net   ------------------------------  % Date: Fri, 06 Apr 2001 16:49:52 +0100s  From: steven.reece@quintiles.com3 Subject: Re: Login problem on Alpha 400 running 6.2-H Message-ID: <OF4F693689.F1EC1ADF-ON80256A26.00566F4E@qedi.quintiles.com>   Robert, C I think there may be an alternate SYSUAF configured when you booted B minimum.  This would mean that the password did get reset but in a different UAF file.r  J My first step would be to take the system down, boot it minimum, login andJ take a look at the startups for anything that defines SYSUAF either in the/ minimum environment or in the full environment.i  K You could also break in to the machine by rebooting it as documented in theo0 FAQ (MGMT 5- I've forgotten the system password)  B Robert Harrison (robert dot harrison at ch dot abb dot cob) wrote: >>>Can anyone help me?  J We have a customer who cannot log in on any account. We had a DEC engineer whop7 tried, even he couldn't log in using the field account.  <trim> <<<e   ------------------------------    Date: 06 Apr 2001 18:05:37 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de>a3 Subject: Re: Login problem on Alpha 400 running 6.2aH Message-ID: <y4ae5uui7i.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>   Possibilities:  # - SYSGEN parameter SYSUAFALT is setsH - startup defines logical name SYSUAF to an unexpected value, so you are6   looking at a UAF file that isn't actually being used   	Jan   ------------------------------  $ Date: Fri, 6 Apr 2001 07:36:48 -0400, From: "J. Scott Greig" <jsgreig@geminaq.com>$ Subject: Re: Missing QMAN$MASTER.DAT2 Message-ID: <nShz6.35$nC3.20218@quark.idirect.com>   I think you want tou  4 $ START/QUEUE/MANAGER DSA0:[SYS0.SYSQUE]/NEW_VERSION  2 This hosuld create the new queue manager database.   Scotth      8 "John Eisenschmidt" <jeisensc@aaas.org> wrote in message news:sacc82a4.070@aaas.org...Y= I'm having trouble with a new install on a DS10 running 7.2-1p  ( I added the below line to SYLOGICALS.COM= $ DEFINE/SYSTEM/EXECUTIVE_MODE QMAN$MASTER DSA0:[SYS0.SYSQUE]    And then did the following( $ START/QUEUE/MANAGER DSA0:[SYS0.SYSQUE]8 %%%%%%%%%%%  OPCOM   5-APR-2001 13:32:38.75  %%%%%%%%%%%" Message from user SYSTEM on BARIUM@ %JBC-E-OPENERR, error opening DSA0:[SYS0.SYSQUE]QMAN$MASTER.DAT;  8 %%%%%%%%%%%  OPCOM   5-APR-2001 13:32:38.75  %%%%%%%%%%%" Message from user SYSTEM on BARIUM -RMS-E-FNF, file not found  9 %JBC-E-QMANNOTSTARTED, queue manager could not be started0  G I did a search of the system disk, and there is no QMAN$MASTER.DAT file * anywhere. This server is not in a cluster.   Did I miss a step someplace?   Thanks,  John  3 ___________________________________________________n        John Eisenschmidt      Systems Analyst<      The American Association for the Advancement of Science"      Office of Technology Services      1200 New York Avenue, NWD      Washington, DC 20005'      Telephone: 202-326-7039      Facsimile: 202-289-8440'      Electronic Mail: jeisensc@aaas.orgn3 ___________________________________________________h   ------------------------------  % Date: Fri, 06 Apr 2001 06:56:31 -0400t0 From: Jim Jennis <jjennis@discovery.fuentez.com>* Subject: Object protection on tcp sockets?D Message-ID: <3.0.5.32.20010406065631.009123b0@discovery.fuentez.com>   Hi VMS Colleagues...  E I have a strange problem when non-priviledged users (just std NETMBX,h) TMPMBX privs) run tcpip programs such as E   sys$system:tcpip$ping.exeI sys$system:tcpip$traceroute.exeY  " OpenVMS 7.2-1 and tcp services 5.0  I When attempting to use the programs, the users get back a message such ask this...Y
 $ping vms1 ping: socket: permission deniedGG %SYSTEM-F-NOPRIV, insufficient privilege or object protection violation   ? Priviledge users have no problems with any of these programs...h  G A dir/sec on the images themselves shows that everyone has read/executeTN priviledges. Other tcpip programs such as nslookup, telnet, ftp, etc are fine.  K What objects (other than the programs themselves) need to be accessable forr  users to execute these programs?  ' Thanks in advance for your help/advice!i  
 Best regards,h  
 Jim Jennis8 --------------------------------------------------------7 FSC - Building Better Information Technology Solutions-d7       from the Production Floor to the Customer's Door.l8 -------------------------------------------------------- Jim Jennis, Technical Director Fuentez Systems Concepts, Inc. 211 Discovery Road, Suite 2s Martinsburg, WV. 25401-0824o USAs  # Phone: +001 (304) 263-0163 ext. 235. Fax:   +001 (304) 263-0702% Email: jjennis@discovery.fuentez.com n        jhjennis@shentel.neti& WEB: http://www.discovery.fuentez.com/   ------------------------------  % Date: Fri, 06 Apr 2001 15:06:29 +0200c5 From: Oswald Knoppers <Oswald.Knoppers@whitehouse.nl> . Subject: Re: Object protection on tcp sockets?- Message-ID: <3ACDBF55.17F5F435@whitehouse.nl>p   Jim Jennis wrote:-  G > I have a strange problem when non-priviledged users (just std NETMBX,o* > TMPMBX privs) run tcpip programs such as >  > sys$system:tcpip$ping.exeS! > sys$system:tcpip$traceroute.exeD > $ > OpenVMS 7.2-1 and tcp services 5.0 > K > When attempting to use the programs, the users get back a message such asi	 > this...d > $ping vms1! > ping: socket: permission deniedMI > %SYSTEM-F-NOPRIV, insufficient privilege or object protection violation   E You need to have OPER privilege in order to ping (see tcpip help pingm restrictions).  1 You can also install these images with OPER priv.    Regards,   Oswald   ------------------------------  % Date: Fri, 06 Apr 2001 09:53:57 -0400r  From: norm.raphael@jamesbury.com9 Subject: Re: OVMS Tech Update Presentations [and Mozilla]a4 Message-ID: <C2256A26.004B793B.00@jklh21.valmet.com>  : Shame on me.  I should have looked there first, of course.        7 hoffman@xdelta.zko.dec.nospam on 04/05/2001 04:37:34 PM6  / Please respond to hoffman@xdelta.zko.dec.nospam    To:   Info-VAX@mvb.saic.com  cc:e: Subject:  Re: OVMS Tech Update Presentations [and Mozilla]        O In article <C2256A25.005CF674.00@jklh21.valmet.com>, norm.raphael@jamesbury.coms writes:C  I :Rich's slides say Mozilla is the default browser for OpenVMS for Q12001.  :Is this so?  Where is it?     The FAQ has the pointers.i  N  ---------------------------- #include <rtfaq.h> -----------------------------J       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.comN  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Fri, 06 Apr 2001 10:41:39 -0400   From: norm.raphael@jamesbury.com9 Subject: Re: OVMS Tech Update Presentations [and Mozilla] 4 Message-ID: <C2256A26.004FD4AE.00@jklh21.valmet.com>  
 Hoff (et al).r  / (This is a bit long, but I wanted it all here.)r (Consult the FAQ, get more Q's)u  ; The FAQ gives this (stuff between >>> and <<< added by me):e   [Start of SOFT3 of FAQ]a   SOFT3.? Where can I get the Netscape Navigator Mozilla.org Web Browser?   H Mozilla.org is the open source organization providing Netscape and otherM interested parties with a browser. Netscape is expected to commercialize this K mozilla.org browser, add additional proprietary features, and release it assK Netscape Communicator (version number TBD). This Netscape Communicator will9L contain the features that the Internet community expected to see in Netscape Communicator V5.  O OpenVMS Engineering is currently porting Mozilla.org's web browser to OpenVMS -uG OpenVMS baselevels of the browser are currently available for download.   1 The mozilla.org browser schedule is available at:t  !   http://www.mozilla.org/project/g   >>> ; Clicking this gives me a "The page cannot  be found" error.s <<<b  > The latest information and current downloads are available at:5   http://www.openvms.compaq.com/openvms/products/ips/S   >>>M Clicking this throws me into:,2 http://www.openvms.compaq.com/ebusiness/index.html where I have to click: OpenVMS Technology then Mozilla2 to get to this: H http://www.openvms.compaq.com/openvms/products/ips/register_mozilla.html" where I find the information below <<< M See section SOFT9 for information on various certificates for V3.003 Netscaped4 Navigator; certificates that have presently expired.  4                                         [Sue Denham]9                                         [Stephen Hoffman]n   [End of SOFT3 of FAQ]   	 [Start ofeI http://www.openvms.compaq.com/openvms/products/ips/register_mozilla.html]F  M New Mozilla Technology Demonstration Release for OpenVMS Alpha now available!r March 28, 2001  J Compaq is pleased to announce the availability of a thirteenth "technologyJ demonstration" version of Mozilla for OpenVMS Alpha. The Mozilla Milestone= 0.8.1 (M0.8.1) release is based on the final Netscape 6 code.0  - Mozilla M0.8.1 for OpenVMS includes security!e      M Currently, Mozilla is neither release nor field test (beta) quality software.eI The M0.8.1 kit is made available here as a Technology Demonstration only.DI Do not use Mozilla in a production environment. Over the coming weeks andCK months, we will make more reliable Mozilla baselevels available on OpenVMS.I   [snip]   [End ofiI http://www.openvms.compaq.com/openvms/products/ips/register_mozilla.html]:  C This means (pointer confusion in the FAQ aside) that the statement:0K ":Rich's slides say Mozilla is the default browser for OpenVMS for Q12001."mF from the slides is not correct, as I read English, and that it will beB "weeks and months" before Mozilla will be supported in production.  M Would anyone who knows, please comment or correct me if I've gotten it wrong.a   -Normh        7 hoffman@xdelta.zko.dec.nospam on 04/05/2001 04:37:34 PMe  / Please respond to hoffman@xdelta.zko.dec.nospamc   To:   Info-VAX@mvb.saic.come cc:e: Subject:  Re: OVMS Tech Update Presentations [and Mozilla]        O In article <C2256A25.005CF674.00@jklh21.valmet.com>, norm.raphael@jamesbury.comn writes:   I :Rich's slides say Mozilla is the default browser for OpenVMS for Q12001.S :Is this so?  Where is it?     The FAQ has the pointers.g  N  ---------------------------- #include <rtfaq.h> -----------------------------J       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.comN  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  $ Date: Fri, 6 Apr 2001 15:56:02 +0100* From: "Richard Brodie" <R.Brodie@rl.ac.uk>9 Subject: Re: OVMS Tech Update Presentations [and Mozilla]o, Message-ID: <9aklej$160u@newton.cc.rl.ac.uk>  \ <norm.raphael@jamesbury.com> wrote in message news:C2256A26.004FD4AE.00@jklh21.valmet.com...  E > This means (pointer confusion in the FAQ aside) that the statement:2M > ":Rich's slides say Mozilla is the default browser for OpenVMS for Q12001."nH > from the slides is not correct, as I read English, and that it will beD > "weeks and months" before Mozilla will be supported in production. >UO > Would anyone who knows, please comment or correct me if I've gotten it wrong.R  J I don't know for sure but the Mozilla roadmap gives the *earliest* releaseN date for Mozilla 1.0 as Q3 2001. I strongly doubt the Q will bless any version earlier than that.   ------------------------------  % Date: Fri, 06 Apr 2001 11:27:33 -0400p  From: norm.raphael@jamesbury.com9 Subject: Re: OVMS Tech Update Presentations [and Mozilla]-4 Message-ID: <C2256A26.005408B6.00@jklh21.valmet.com>  B Perhaps the slide should have read:  Q12002 (no sarcasm intended).        + R.Brodie@rl.ac.uk on 04/06/2001 10:56:02 AMs  # Please respond to R.Brodie@rl.ac.ukc   To:   Info-VAX@mvb.saic.comf cc:i: Subject:  Re: OVMS Tech Update Presentations [and Mozilla]          - <norm.raphael@jamesbury.com> wrote in message . news:C2256A26.004FD4AE.00@jklh21.valmet.com...  E > This means (pointer confusion in the FAQ aside) that the statement:eM > ":Rich's slides say Mozilla is the default browser for OpenVMS for Q12001.")H > from the slides is not correct, as I read English, and that it will beD > "weeks and months" before Mozilla will be supported in production. >iO > Would anyone who knows, please comment or correct me if I've gotten it wrong.t  J I don't know for sure but the Mozilla roadmap gives the *earliest* releaseN date for Mozilla 1.0 as Q3 2001. I strongly doubt the Q will bless any version earlier than that.   ------------------------------   Date: 6 Apr 2001 07:35:53 GMTm- From: djweath@attglobal.net (Dave Weatherall)h3 Subject: Re: Problems with threads on VMS AXP 7.1-2F5 Message-ID: <DTiotGxQ0bj6-pn2-IxSMddwbOcgx@localhost>-  E On Thu, 5 Apr 2001 22:26:25, dashw459@aol.comeatspam (Doug W.) wrote:u   > Jakob Erber wrote  > O > << Our Applikation using Compaq Ada and multi Tasking (based on DEC pthreads) M > at some point just sleeps. Meaning, it stops working, going into HIB state.a >  >> N > Interesting.  Have you got the pthreads patches installed?  ASTs and threadsO > just don't like each other.  Perhaps you can use another thread instead of an( > AST?   Jakob E              I've never properly tested my DecThreads Application on mF VMS 7-1, only on 5.5 and 6.2. The application built under 6.2 does run= under 7.1 as far as I can tell. I simply haven't stressed it.   A However, 7.1 DecThreads supports Upcalls which enable the Thread 9E scheduler and VMS scheduler to play together in  a more co-operative pC way. If you call code that would put the process into a wait (LEF) uF state, e.g. $QIOW,  then the system works out whether there is anotherD thread that could be run. Without Upcalls enabled, the process will F become blocked until the wait is satisfied rather than the thread that
 caused it.  E In non-upcall environments, one needs to play some tricks with AST's oB etc to ensure that threads use thread-wait states and not process B waits, if you want to maintain performance and/or avoid deadlocks.  B In summary, check out DecThread Upcalls, if you're not using them  already<G>.    -- X Cheers - Dave.   ------------------------------  $ Date: Fri, 6 Apr 2001 15:11:49 +0200$ From: "Jakob Erber" <erberj@post.ch>3 Subject: Re: Problems with threads on VMS AXP 7.1-2  Message-ID: <3acdc096$1@hcwe67>t   Thanks for the replies so far.   best regards   Jakobr    5 "Jakob Erber" <erberj@post.ch> schrieb im NewsbeitragR news:3acc82c4$1@hcwe67...c > Hello, > 8 > for too long now, we fight with the following problem: >nL > Our Applikation using Compaq Ada and multi Tasking (based on DEC pthreads)F > at some point just sleeps. Meaning, it stops working, going into HIB state. > I > If we apply the system service $wake on it, it awakes and works normaly  from  > then on, never sleeping again. > I > Our guess ist, that the problem is related to the use of ASTs and Tasks.  > (threads) in the same process. >,L > As it looks, tasks suddenly are put to sleep for exactly the time, a timerK > (with AST)  was set up for in a complety different, unrelated part of the 
 > program. >0& > Compaq is responding very very slow. >a, > Has anybody experienced something similar? >n > best regards >  > Jakob2 >@ >s   ------------------------------  # Date: Fri, 06 Apr 2001 14:31:59 GMTn2 From: seibel_r@localhost.localdomain (Rich Seibel) Subject: Re: pthreads + printf; Message-ID: <slrn9crkq2.9ke.seibel_r@localhost.localdomain>o  E On 05 Apr 2001 22:35:33 GMT, Doug W. <dashw459@aol.comeatspam> wrote:e >Seibel wrote: >kG ><< printf is not thread-safe in POSIX usage.  You might try using yourr? >own lock around it.  A thread mutex should be sufficient.  See.> >pthread_mutex_init, pthread_mutex_lock, pthread_mutex_unlock. > >> >oL >This was correct at one time.  But I don't think you have to protect printf >anymore under DECTHREADS.  F That puts VMS ahead of other implementations.  I've created some very . interesting looking output from other systems.  L >If I am wrong on this jump on me.  In any case I use printf without problem? >running multiple threads across multiple CPUs under VMS 7.3.     ' I didn't think 7.3 was available yet?  sJ It is said to have some feature that I am interested in (additional POSIX / compatibility) for the porting that I am doing.t   >If I had to? >protect it with a mutex debugging would never get completed.  e   I am curious, why is this so?8J The package I am porting uses a lock around its printf-like capability and: I haven't notices any performance or debugging issues yet.   >Think it was okG >under VMS 7.2-1 with pthreads patches installed.  Believe it had to bel- >protected under earlier versions of threads.l >nI I am using 7.2-1 with the latest patches.  It's good to know that I won'tn have printf problems.n   --  D --------------------------------------------------------------------D Rich Seibel, Software Engineer                 (314)579-0066 ext 220D Object Computing, Inc.                           seibel_r@ociweb.comD Need ACE training?                      See http://www.theaceorb.comD --------------------------------------------------------------------   ------------------------------  % Date: Fri, 06 Apr 2001 16:23:15 +0100-% From: Alan Greig <a.greig@virgin.net>7 Subject: Re: pthreads + printf8 Message-ID: <ninrct40labu027rn3kmj1sb5ivu46dnbl@4ax.com>  F On Fri, 06 Apr 2001 14:31:59 GMT, seibel_r@localhost.localdomain (Rich Seibel) wrote:    ( >I didn't think 7.3 was available yet?  K >It is said to have some feature that I am interested in (additional POSIX A0 >compatibility) for the porting that I am doing.  E Not released yet but external field test kits for early adopters have-C been available to order from Compaq (price around $50) for the lastrC few months. If you've never used a VMS external field test kit theysA usually close to final ship quality and suitable for early accesst development use.  F You can order directly from the OpenVMS web site (OpenVMS Portal link) if you live in the US.   >h
 >>If I had toi@ >>protect it with a mutex debugging would never get completed.   >a >I am curious, why is this so?K >The package I am porting uses a lock around its printf-like capability andI; >I haven't notices any performance or debugging issues yet.S >Y >>Think it was okdH >>under VMS 7.2-1 with pthreads patches installed.  Believe it had to be. >>protected under earlier versions of threads. >>J >I am using 7.2-1 with the latest patches.  It's good to know that I won't >have printf problems.   -- Alan   ------------------------------  # Date: Fri, 06 Apr 2001 15:56:25 GMTI$ From: mark@NOSPAMtechop.co.uk (Mark)$ Subject: Q: Unmapping global section0 Message-ID: <3acde6e7.117174347@news.force9.net>   Hi,d  C I am mapping a global section with sys$mgblsc.  How can I unmap it?l   TIA    ------------------------------    Date: 06 Apr 2001 18:12:20 +0200G From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de>s( Subject: Re: Q: Unmapping global sectionH Message-ID: <y47l0yuhwb.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>  & mark@NOSPAMtechop.co.uk (Mark) writes:  E > I am mapping a global section with sys$mgblsc.  How can I unmap it?    With $DELVA, I suppose...a   	Jan   ------------------------------  # Date: Fri, 06 Apr 2001 16:17:44 GMT-= From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)i( Subject: Re: Q: Unmapping global section0 Message-ID: <009FA21C.0C520038@SendSpamHere.ORG>  W In article <3acde6e7.117174347@news.force9.net>, mark@NOSPAMtechop.co.uk (Mark) writes:  >Hi, >rD >I am mapping a global section with sys$mgblsc.  How can I unmap it? >  >TIA >     
 SYS$DGBLSC   --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM             5O city, n., 1. a place where trees are cut down and streets are named after them.    ------------------------------  # Date: Fri, 06 Apr 2001 16:21:37 GMT = From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)l( Subject: Re: Q: Unmapping global section0 Message-ID: <009FA21C.97587EA9@SendSpamHere.ORG>  W In article <3acde6e7.117174347@news.force9.net>, mark@NOSPAMtechop.co.uk (Mark) writes:k >Hi, >tD >I am mapping a global section with sys$mgblsc.  How can I unmap it? >  >TIA >e  ' You might also have look at SYS$DELTVA.o --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM-            -O city, n., 1. a place where trees are cut down and streets are named after them.o   ------------------------------  % Date: Fri, 06 Apr 2001 17:21:15 +0100 - From: Tim Llewellyn <tim.llewellyn@bbc.co.uk>-( Subject: Re: Q: Unmapping global section) Message-ID: <3ACDECFB.E6516365@bbc.co.uk>r   Jan Vorbrueggen wrote:  ( > mark@NOSPAMtechop.co.uk (Mark) writes: > G > > I am mapping a global section with sys$mgblsc.  How can I unmap it?f >t > With $DELVA, I suppose...n  C OK, so you won't be able to write to it any more from that process,-G but will this reduce the reference count on the global section? Its notr apparent that it will.    I feel a test program coming on.    --o6 Tim Llewellyn, OpenVMS Infrastructure, Remarcs Project0 MedAS at the BBC, Whiteladies Road, Bristol, UK.A Email tim.llewellyn@bbc.co.uk. Home tim.llewellyn@cableinet.co.uki  A I speak for myself only and my views in no way represent those ofy MedAS or the BBC.e   ------------------------------  % Date: Fri, 06 Apr 2001 17:28:59 +0100 - From: Tim Llewellyn <tim.llewellyn@bbc.co.uk>g( Subject: Re: Q: Unmapping global section) Message-ID: <3ACDEECB.25C2E5B5@bbc.co.uk>-  & "Brian Schenkenberger, VAXman-" wrote:  Y > In article <3acde6e7.117174347@news.force9.net>, mark@NOSPAMtechop.co.uk (Mark) writes:m > >Hi, > >sF > >I am mapping a global section with sys$mgblsc.  How can I unmap it? > >d > >TIA > >- >- > SYS$DGBLSC  X Thats what I thought at first, however given that Mark is using $MGBLSEC, it is apparentX that some other process or program is creating the section and he may not want to deleteM the section or mark it for deletion. From system services reference, VMS 7.2.   [ The $DGBLSC service does not unmap a global section from a process's virtual address space.zP To do this, the process should call the Delete Virtual Address Space ($DELTVA orQ      $DELTVA_64) service, which deletes the pages to which the section is mapped.m      --n6 Tim Llewellyn, OpenVMS Infrastructure, Remarcs Project0 MedAS at the BBC, Whiteladies Road, Bristol, UK.A Email tim.llewellyn@bbc.co.uk. Home tim.llewellyn@cableinet.co.uki  A I speak for myself only and my views in no way represent those of- MedAS or the BBC.    ------------------------------  # Date: Fri, 06 Apr 2001 17:46:34 GMT-= From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)-( Subject: Re: Q: Unmapping global section0 Message-ID: <009FA228.74F8450B@SendSpamHere.ORG>  Y In article <3ACDEECB.25C2E5B5@bbc.co.uk>, Tim Llewellyn <tim.llewellyn@bbc.co.uk> writes:j >s >y' >"Brian Schenkenberger, VAXman-" wrote:n >iZ >> In article <3acde6e7.117174347@news.force9.net>, mark@NOSPAMtechop.co.uk (Mark) writes: >> >Hi,s >> >G >> >I am mapping a global section with sys$mgblsc.  How can I unmap it?h >> > >> >TIAs >> > >>
 >> SYS$DGBLSC< >dY >Thats what I thought at first, however given that Mark is using $MGBLSEC, it is apparentMY >that some other process or program is creating the section and he may not want to deleteaN >the section or mark it for deletion. From system services reference, VMS 7.2. >t\ >The $DGBLSC service does not unmap a global section from a process's virtual address space.Q >To do this, the process should call the Delete Virtual Address Space ($DELTVA ortR >     $DELTVA_64) service, which deletes the pages to which the section is mapped. >M >n > --7 >Tim Llewellyn, OpenVMS Infrastructure, Remarcs Projectn1 >MedAS at the BBC, Whiteladies Road, Bristol, UK.nB >Email tim.llewellyn@bbc.co.uk. Home tim.llewellyn@cableinet.co.uk >iB >I speak for myself only and my views in no way represent those of >MedAS or the BBC.    F What would be nice is if Mark would better explain what he's doing andG perhaps RTFM.  If he was able to figure out how to use $MGBLSC, I wouldc3 have to think him capable if figuring out the rest.p     --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COMy            lO city, n., 1. a place where trees are cut down and streets are named after them._   ------------------------------  $ Date: Fri, 6 Apr 2001 15:42:06 +0200( From: "Pawe Grecki" <gorpa@kki.net.pl>  Subject: Ramdisk for AXP OpenVMS( Message-ID: <9akh3p$avu$1@leo.gazeta.pl>   Hi,   > Is there anybody who knows how to create Ramdisk under OpenVMS3 (relative cheap alternative to solid state disks) ?T Is it possible at all ???t     Regardsv Pawela   ------------------------------   Date: 6 Apr 2001 10:12:06 -0500h9 From: Kilgallen@eisner.decus.org.nospam (Larry Kilgallen)e$ Subject: Re: Ramdisk for AXP OpenVMS3 Message-ID: <G+bnCZrPF10X@eisner.encompasserve.org>o  S In article <9akh3p$avu$1@leo.gazeta.pl>, "Pawe Grecki" <gorpa@kki.net.pl> writes:   @ > Is there anybody who knows how to create Ramdisk under OpenVMS5 > (relative cheap alternative to solid state disks) ?,  / DECram for OpenVMS Version 2.3 is described at:u  / 	http://www.compaq.com/info/SP3426/SP3426PF.PDFh  ) I believe a newer version is coming soon.n  N ==============================================================================N Great Inventors of our time: Al Gore -> Internet; Sun Microsystems -> ClustersN ==============================================================================   ------------------------------  % Date: Fri, 06 Apr 2001 10:21:33 -040002 From: rdeininger@mindspring.com (Robert Deininger)$ Subject: Re: Ramdisk for AXP OpenVMSL Message-ID: <rdeininger-0604011021330001@user-2iveadr.dialup.mindspring.com>  8 In article <9akh3p$avu$1@leo.gazeta.pl>, "Pawe Grecki" <gorpa@kki.net.pl> wrote:m   > Hi,o > @ > Is there anybody who knows how to create Ramdisk under OpenVMS5 > (relative cheap alternative to solid state disks) ?o > Is it possible at all ???n  J There's the DECram product from OVMS engineering.  The license is includedD in the hobbyist program, for non-commercial use.  Or you can buy theG regular license.  These disks can be served across a cluster, shadowed,s made into volume sets, etc.r  I There may be other RAMdisk products around, perhaps on the freeware CD orh in DECUS libraries.-  H Remember that solid state disks typically have battery backup, somethingD RAM disks DON'T have.  A RAM disk may survive a reboot, but it won't survive a power failure.   -- p Robert Deininger rdeininger@mindspring.com-   ------------------------------  % Date: Fri, 06 Apr 2001 12:10:54 +0100c  From: steven.reece@quintiles.com$ Subject: Re: Restart TCP/IP ServicesH Message-ID: <OF0DD58182.29D803E6-ON80256A26.003D4746@qedi.quintiles.com>  C It can be done with UCX 4.2 in a batch job.  Been there, done that.cI The biggest problem is what happens if, for whatever reason, the shutdown0* or the startup fail to complete correctly? Steve.   Zane H. Healy wrote: >>>eI You know I was actually thinking about this a little while ago.  Is thererJ any reason why you can't do this by submitting a batch job to shut it downC and start it back up?  Guess I'll have to try it one of these days.   ? Since telnet is my normal method of access this could be handy.e <<<    ------------------------------  % Date: Fri, 06 Apr 2001 13:44:14 +0100l- From: Tim Llewellyn <tim.llewellyn@bbc.co.uk>r$ Subject: Re: Restart TCP/IP Services) Message-ID: <3ACDBA1E.67FDB01B@bbc.co.uk>h   "Zane H. Healy" wrote:  & > Jim Agnew <Agnew@hsc.vcu.edu> wrote:W > >> Can be helpful not to restart telnet if you are making the changes via telnet :-).a >n) > > Awwww.... why not??????????????   ;-D4 > >0; > > (p.s., have seen someone actually do just this... ;-P )Q >0K > You know I was actually thinking about this a little while ago.  Is theresL > any reason why you can't do this by submitting a batch job to shut it downE > and start it back up?  Guess I'll have to try it one of these days.  >r   Yup, it can be made to work.   >sA > Since telnet is my normal method of access this could be handy.s >o& >                                 Zane   --6 Tim Llewellyn, OpenVMS Infrastructure, Remarcs Project0 MedAS at the BBC, Whiteladies Road, Bristol, UK.A Email tim.llewellyn@bbc.co.uk. Home tim.llewellyn@cableinet.co.uka  A I speak for myself only and my views in no way represent those ofl MedAS or the BBC.    ------------------------------  % Date: Fri, 06 Apr 2001 13:55:50 +0100s- From: Tim Llewellyn <tim.llewellyn@bbc.co.uk>*$ Subject: Re: Restart TCP/IP Services) Message-ID: <3ACDBCD6.DCDC5ACA@bbc.co.uk>v  ! steven.reece@quintiles.com wrote:-  E > It can be done with UCX 4.2 in a batch job.  Been there, done that.tK > The biggest problem is what happens if, for whatever reason, the shutdown , > or the startup fail to complete correctly?  K Agreed, very important to test before using on production server in anotherW city.e  H Hey, I even coded a batch to install ECO's to UCX 4.1, including reboot.L Never did any more than test that though. A bit to scary and no real need to use it.r  -- 6 Tim Llewellyn, OpenVMS Infrastructure, Remarcs Project0 MedAS at the BBC, Whiteladies Road, Bristol, UK.A Email tim.llewellyn@bbc.co.uk. Home tim.llewellyn@cableinet.co.ukr  A I speak for myself only and my views in no way represent those ofy MedAS or the BBC.d   ------------------------------  % Date: Fri, 06 Apr 2001 11:27:11 +0200e$ From: Michael Unger <unger@decus.de>- Subject: Seeking CD-R/CD-RW SCSI INQUIRY datae* Message-ID: <009FA214.FC81160B.5@decus.de>  $ > Date: Tue, 3 Apr 2001 16:44:49 GMT4 > From: Hoff Hoffman <hoffman@XDELTA.ZKO.DEC.NOSPAM>O > Subject: Re: Support for CD-R (was: Re: Seeking CD-R/CD-RW SCSI INQUIRY data)Q >   S > In article <009F9FAC.F51F1C83.5@decus.de>, Michael Unger <unger@decus.de> writes:  >   D > :(No standards? Devices manufactured not compliant with standards?E > :Standards as defined can be interpreted in different ways? I heardsG > :years ago that "the standards" for recordable CD media are describeduH > :in the "orange book". - I _do_ know that neither "S" in "SCSI" is the& > :abbreviation for "Standard" ... ;-) >   C >   You have clearly not yet reached a fully visceral understanding C >   of that which is politely known as SCSI.  When you can create arC >   working SCSI driver implementation for an arbitrary SCSI widgetuD >   from scratch, it will be time for you to leave, Grasshopper. :-)  ' I didn't claim I could do that, did I ?   B >   Put another way, there are currently three major familities ofD >   SCSI CD-R drives around, and various CD-R drive models even from? >   a particular vendor are not necessarily command-compatible.l  F I suppose some vendors never have heard the expression "compatibility" :-)o  C I definitely didn't request that any CD-R drive model that could be D bought anywhere had to be supported; I thought of a (small) range ofF models qualified and supported -- there are a few "Compaq branded" andE "OpenVMS qualified" and "fully supported" CD-ROM drives, "RRD-4x". (IeF never disassembled a drive to see what is really in it; I guess CompaqE and formerly Digital selected a specific vendor and a specific model,fD tested it, requested bug fixes to be made to the firmware, qualifiedC it again and if it had passed all tests successfully it was labeledn
 "Compaq".)  0 > :"formal support not added anytime soon": Why?G > :CD-Rs are an established medium for backup and software distributiontC > :which can not be overwritten (i.e., files can not be modified orDB > :deleted later on) and with a life expectancy of about 30 years. >   : >   This has nothing to do with the media lifetime itself. >   H >   The complexity here involves tracking and supporting the CD-R drives. >   and fielding the inevitable support calls.  F That's the reason why I requested just "a small range of models" to be
 supported.  I > :Maybe you can tell us the reason the OpenVMS management has decided totH > :keep this on the "wish list" forever? I guess it has been there for a > :rather long time now ...o >   H >   Why?  Simple: Resources (engineers, time), and scheduling priorities/ >   (DII COE, other high(er)-profile projects).p  C Reading of tens of thousands of programmers being fired by Internet D companies right now in the newspapers Compaq should be able to get a< few of them <rant> if Compaq is really interested in furtherB developments of VMS according to customer suggestions and requests? <grumble> and if Compaq is really willing to spend a few of theoA multi-billion dollars it gets from VMS sales (hardware, software,t& support contracts). </grumble> </rant>  F And scheduling priorities can be changed, too. (Not requesting DII COE& or other projects have to be stopped.)  ' No personal offence intended of course.d@ (You, Hoff, are "not in a position ..." -- I do know of that :-)  E I read on the WWW page of U.S.Design (Inc?) that the "optical storage D department" was sold to them by DEC many years ago. Is the fact thatG DEC sold this division the reason Compaq is not allowed to manufacture/0 sell optical storage solutions?    Michael    ------------------------------  % Date: Fri, 06 Apr 2001 11:33:04 +0200/C From: Eberhard Heuser-Hofmann <vaxinf@chclu.chemie.uni-konstanz.de>-1 Subject: Re: Seeking CD-R/CD-RW SCSI INQUIRY data-> Message-ID: <009FA215.CEFA4021.1@CHCLU.CHEMIE.UNI-KONSTANZ.DE>  I >"Eberhard Heuser-Hofmann" <vaxinf@chclu.chemie.uni-konstanz.de> wrote in00 >message news:3ac99071.0@news.uni-konstanz.de...  N >> CD-writing nowadays is standardized: All newer drives (since 1999!) use the >> same E >> commands to produce a CD-R. DVD-R-drives behave the same. Even thet >> interfaceK >> is not of that importance, if one can send "raw"-commands. So what's thee
 >> problem???t  H >A good friend of mine is the author of a well known CD-R product on theF >market.  He has MANY CD-R's for testing and receives new ones all theA >time.  The number of 'standard' exceptions is surprisingly high. I >Hanging the bus, going out to la-la land, etc, is not that uncommon wheni! >adding support for a new device.p  G Not the drives are the problem, but the OS (guess which one I mean...). I You see this if you switch to linux and the drive runs nicely on the samew	 hardware.s  H >The question is, if this happens on VMS, who debugs it and supports it?I >There are limited cycles available to do all the work that is requested.h  G So why people like Joerg Schilling, the author of cdrecord, is able to  I write a program for many platforms and a huge amount of different drives?nE He owns only about five drives, but due to the linux idea many people  share their knowledge.  ! The following sentences are true:-  L Since OpenVMS 6.x it is possible to burn CDROMs on VMS without the need of aJ PC-software. BTW. you economize the transfer of the virtual disk onto yourQ PC. If your virtual drive has a size of 650 MB you need about 30 min to transfer aH this file. This argument is never been mentioned in the discussion about cdburning for VMS.  F For OpenVMS/Alpha > V6.2  CD-Rewriting is possible. IDE drive usage + ? burn-proof-technology runs nicely (Tested with TEAC CD-W512EB).l  " Here is my "supported" drive list:   Yamaha 6420s Philips CDD2000r HP 6020: TEAC CD-R58S TEAC CD-W512EB   Eberhard   ------------------------------  % Date: Fri, 06 Apr 2001 11:26:56 +0100-% From: Alan Greig <a.greig@virgin.net>r1 Subject: Re: Seeking CD-R/CD-RW SCSI INQUIRY dataH8 Message-ID: <c66rcto6stv6hf9aabi9ennbid6ha2due4@4ax.com>  ; On Fri, 06 Apr 2001 11:33:04 +0200, Eberhard Heuser-Hofmanna, <vaxinf@chclu.chemie.uni-konstanz.de> wrote:   >oH >So why people like Joerg Schilling, the author of cdrecord, is able to J >write a program for many platforms and a huge amount of different drives?F >He owns only about five drives, but due to the linux idea many people >share their knowledge.   A From my limited look at Linux source code and docs in the area ofeD arbitrary SCSI device handling it is clear that the Linux developersD have run into all these problems but far more extensive distributionA has provided feedback on actual drive capabilities. It would seem D possible to parse Linux header file details of drive capabilities toE create a generic driver for VMS which would have a better idea of how @ to handle foreign drives. No VMS need not formally support these. devices but it sounds at least possible to me.   >k" >The following sentences are true: >PM >Since OpenVMS 6.x it is possible to burn CDROMs on VMS without the need of aiK >PC-software. BTW. you economize the transfer of the virtual disk onto youroR >PC. If your virtual drive has a size of 650 MB you need about 30 min to transfer I >this file. This argument is never been mentioned in the discussion abouts >cdburning for VMS.3 >EG >For OpenVMS/Alpha > V6.2  CD-Rewriting is possible. IDE drive usage + .@ >burn-proof-technology runs nicely (Tested with TEAC CD-W512EB). >m# >Here is my "supported" drive list:i >$
 >Yamaha 6420se >Philips CDD2000 >HP 6020
 >TEAC CD-R58So >TEAC CD-W512EB  >t	 >Eberhard  >    -- Alan   ------------------------------  # Date: Fri, 06 Apr 2001 14:57:16 GMTtF From: lederman@star.enet.dec.DISABLE-JUNK-EMAIL.com (Bart Z. Lederman)M Subject: Re: Support for CD-R (was: Re: Seeking CD-R/CD-RW SCSI INQUIRY data),2 Message-ID: <gPkz6.626$fB6.16552@news.cpqcorp.net>   In article <y4hf038jyy.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>, Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de> writes: > I >In that case, the priorities aren't right. Supporting CD-R(W) is a must-.J >have, nowadays, and I suppose DVD-R wil be soon. It's the cheapest way of2 >exchanging data in a robust and standardized way. >: >	Jann  ? The problem is where the 'standard' is, if any.  There was some.B standardization of CD formats: there was never any standardization= of CD drive command sets (beyond basic read functions) as far < as I know, and there still isn't.  If anyone can point to a 8 "real" standard (ANSI, EIA, DIN, ISO, NIST, or any other= industry standard) I'm sure a lot of us would like to see it.t  C From the looks of things so far, I think it likely that DVD-R(x) iseC going to be better than CD-R(x) was in terms of drive capabilities.oA It may well turn out to be easier to support DVD-x drives than it ? was to support CD-x drives.  Of course, things in this industryE1 are subject to change at any time without notice.t   -- i(  B. Z. Lederman   Personal Opinions Only  8  Posting to a News group does NOT give anyone permission8  to send me advertising by E-mail or put me on a mailing  list of any kind.  5  Please remove the "DISABLE-JUNK-EMAIL" if you have as5  legitimate reason to E-mail a response to this post.-   ------------------------------  % Date: Fri, 06 Apr 2001 10:45:29 +0100   From: steven.reece@quintiles.com& Subject: Re: TSM and terminal servers?H Message-ID: <OF8624756C.EEA9C1E1-ON80256A26.00354BFE@qedi.quintiles.com>  G Probably true, but in the quick test I did with a DECserver 700 runningbJ wweng1.sys it worked in as much as it reconnected to the preferred service from just pressing return.    Scott Vieth commented / quoted :4 >>>Not *preferred* service, but *dedicated* service.  A Set those terminal server ports to "dedicated" and they'll always>9 be connected to the service in question.  Your users will 2 never see the local prompt on the terminal server. <trim>
 > How about : ' > DEF PORT n PREFER SERVICE servicename  > DEF PORT n AUTOCONNECT ENABLEo > LOGOUT PORT nc <<<o   ------------------------------    Date: 07 Apr 2001 01:03:04 +0800, From: Paul Repacholi <prep@prep.synonet.com>& Subject: Re: TSM and terminal servers?- Message-ID: <871yr6c65z.fsf@prep.synonet.com>e  . Howard S Shubs <hshubs@mindspring.com> writes:  I > In article <3ACC7631.7C48BFFB@unh.edu>, Bob Kenney <rmk@unh.edu> wrote:   < > >	Not that I've seen.  The future does not lie that way, I
 > >	guess.  9 > Of course not.  It's hard to find a dumb terminal, too.e  E > > You can set the server prompt, but AFAIK none of the DEC terminalsJ > > servers(or Xyplexes, either) allow for a port-specific prompt setting.  @ > Just bought new terminal servers from Lantronix.  They're veryD > DECserver-like.  Perhaps their web site (http://www.lantronix.com/ > would be useful?  C I have found the Lantronix folks to be very good and helpfull. Nicee; gear too. Thay are about the only one who know what LAT is!   ) I got an EPS-1 the other day. Nice bonus!a   -- d< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.   ------------------------------  % Date: Fri, 06 Apr 2001 13:46:51 +0100l  From: steven.reece@quintiles.com# Subject: Re: UCX .DAT Files - Path? H Message-ID: <OFD9F0133C.1524FF5A-ON80256A26.00454602@qedi.quintiles.com>   David,H I'd suspect that UCX a.k.a. Compaq TCP/IP Services manages to use commonF files.  The cluster I have here only has the .DAT files in SYS$COMMON.J Host IP addresses only need to be typed in on one node in the cluster whenJ the systems shared a system disk so I'd expect other items to be in shared
 files too.   David Dachtera wrote:hH >>>I have a challenge at work to combine two Alphas onto a common system3 disk. Each currently runs from its own system disk.4  H I've got most everything else worked out. What I don't know is about the' UCX$*.DAT files in the SYS$SYSTEM path.=  A When nodes share a common system disk, do they share a common UCXn database also?  = Should the UCX$*.DAT files be in the SYS$COMMON branch or the= SYS$SPECIFIC branch?  C Since you'll probably want to know, we're talking OVMS V7.1-2 + UCX1D V4.2, not sure what ECO level and no, I don't (think I) have the UCXF doc.'s. If these matter to anyone, one Alpha is a 4100, the other is aF 2100, the interconnect is currently DSSI (yes - you read that right!),A and each machine will have it's own local SCSI disk for secondaryo pagefiles and such.o  ! What does anyone know 'bout this?d <<<e   ------------------------------    Date: 07 Apr 2001 00:36:40 +0800, From: Paul Repacholi <prep@prep.synonet.com># Subject: Re: UCX .DAT Files - Path?n- Message-ID: <87ae5uc7dz.fsf@prep.synonet.com>n  4 rdeininger@mindspring.com (Robert Deininger) writes:  = > In article <3ACD10F9.65B9D1AF@fsi.net>, "David J. Dachtera"   > <djesys.nospam@fsi.net> wrote: >  > > Hi, Folks, > > I > > I have a challenge at work to combine two Alphas onto a common system 7 > > disk. Each currently runs from its own system disk.g > > L > > I've got most everything else worked out. What I don't know is about the+ > > UCX$*.DAT files in the SYS$SYSTEM path.i > > E > > When nodes share a common system disk, do they share a common UCX0 > > database also? > > A > > Should the UCX$*.DAT files be in the SYS$COMMON branch or thee > > SYS$SPECIFIC branch? > > G > > Since you'll probably want to know, we're talking OVMS V7.1-2 + UCXaH > > V4.2, not sure what ECO level and no, I don't (think I) have the UCXJ > > doc.'s. If these matter to anyone, one Alpha is a 4100, the other is aJ > > 2100, the interconnect is currently DSSI (yes - you read that right!),E > > and each machine will have it's own local SCSI disk for secondaryd > > pagefiles and such.t > > % > > What does anyone know 'bout this?  >  > B > On a system disk with one locally-connected alpha and a bunch of> > satellites, OVMS V7.1-2 + UCX V4.2, I find UCX*.DAT files in: > SYS$COMMON:[SYSEXE] and SYS$COMMON:[SYSMGR], but none in. > SYS$SYSROOT:[SYSEXE] or SYS$SYSROOT:[SYSMGR] > J > So I guess you need to put the files into the same common directory.  If= > they are different, you'll need to make them match somehow.t  E At least on a Vax, you *can* have the UCX files is sys$specific. DoneeB that, it works well if you need to run a machine on a 'non-normal'* network. I have NOT tried it with TCP yet.  E For combining, I drop a rock on all the .dats and re-run the configs.    -- e< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.c@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.   ------------------------------  $ Date: Fri, 6 Apr 2001 09:06:44 -0400. From: "Ted Medenblik" <ted.medenblik@duke.edu>" Subject: UCX 5.1 BG device problem( Message-ID: <9akf02$lrd$1@news.duke.edu>  H FYI, I upgraded to TCPIP/UCX 5.1 (VMS 7.2-1) Wednesday night.  We have aF client server app that the BG device's are not closing properly on andI causing me to disconnect bg devices for users to get back in or flush the1K service by disabling and re-enabling.  I also had a crash.  Both issues areRL known problems per phone support and an ECO is due out some time this month.  K    I added some DCL to disconnect the BG device in the command file, but iteI doesn't seem to release the active connection count in the service.  Doesr anyone have something better than:t   $ pid=f$getjpi ("", "PID") $ sho proc /out=aes:'pid'.oute@ $ search aes:'pid'.out "Devices allocated:" /out= aes:'pid'.out2! $ open/read infile aes:'pid'.out2s $ read infile record" $ bg =f$element (1, ":", record  ) $ close infile $ sho sym bg $ delete aes:'pid'.out*;*t
 $ sh sym x $ ucx disc dev 'bg': $ logout   ------------------------------  % Date: Fri, 06 Apr 2001 11:41:28 +0100i  From: steven.reece@quintiles.com  Subject: Re: Updated informationH Message-ID: <OFEAA785B3.CA095943-ON80256A26.003AA355@qedi.quintiles.com>   But were they DC or AC?  :-)   Sue wrote : K >>>The question you have to ask your self is "Will Sue throw anything at me  orG just the lighting fixtures?" If you were in DC you would know what thisB	 means.<<<>   ------------------------------  % Date: Fri, 06 Apr 2001 11:12:22 +0100L% From: Alan Greig <a.greig@virgin.net>o' Subject: VMS ad in another UK trade magS8 Message-ID: <vn3rct8d29jn2pe8nouig1os6acu695jbi@4ax.com>   News just in...l  E A second flock of winged pigs has been spotted in the skies above thetD United Kingdom. Experts believe this particular breed of pig (Latin:D Pigus VMSus) has a genetic advantage which has enabled it to rapidlyE evolve and escape the Foot In Mouth epidemic which is devastating the_	 industry.a  B  Insiders claim that further advances will be made following a topD secret military project which aims to crossbreed these pigs with theA more primitive Pigus Unixus to further enhance their evolutionaryc@ ability to live in environments previously considered hostile. AF previous project to cross-breed with the industry dimwit (Pigus, PigusE Maximus Windus) only resulted in gains for the evil cloners at markete leader MicroPig.  E Said top breeders ComPig: "We know we've got it wrong in the past buto> that was the result of mistakes inherited from our predecessorC DigiPig. In future we intend to further enhance our pigs until they F fly all the way to the (J)stars and beyond. Just wait till you see ourD InterGalactic Pigs combine to form a major stellar cluster eclipsing our local Sun.  C Disbelievers are invited to consider the evidence for themselves on 2 Page 5 of VNU's Network News dated 4th April 2001. -- Alan   ------------------------------  % Date: Fri, 06 Apr 2001 14:46:17 -0000t- From: wspencer@ap.nospam.org (Warren Spencer)D+ Subject: Re: VMS ad in another UK trade magf/ Message-ID: <tcrllp2al5m642@news.supernews.com>m  ) a.greig@virgin.net (Alan Greig) wrote in i- <vn3rct8d29jn2pe8nouig1os6acu695jbi@4ax.com>:a   >News just in... > F >A second flock of winged pigs has been spotted in the skies above the  
 -- snip --   Well done Alan!e   ws   -- t1 << Marriage is Grand.  Divorce is Fifty Grand. >>n   Warren Spencer Senior Software Engineer The Associated Press  ? ** My employer does not necessarily agree with my statements **i   ------------------------------  $ Date: Fri, 6 Apr 2001 11:01:14 -06000 From: "Greg Zymbaluk" <greg.zymbaluk@compaq.com>+ Subject: VMS equivalent of Unix wc command?h2 Message-ID: <ADmz6.636$fB6.16968@news.cpqcorp.net>   Hi,e  K Is there a VMS equivalent of the Unix wc -l command to count the lines in at file?e   Thanks,h   Greg   ------------------------------  % Date: Fri, 06 Apr 2001 10:56:51 +0100o  From: steven.reece@quintiles.com$ Subject: Re: VMS-Related: AffordableH Message-ID: <OFF05286E4.BAB0DD32-ON80256A26.00365DC4@qedi.quintiles.com>   It's a unix-ism Tim  :-)J If you want the write to complete before the completion status is returnedD then use VMS.  If you want to think that it's been written but don'tH actually care then use Unix.  If you don't even want to be bothered with2 what a write is then use a Microsoft product.  :-) Steve.   Tim Llewellyn wrote/quoted:o >>>  Jan Vorbrueggen wrote:  - > Christof Brass <brass@infopuls.com> writes:l ><) > > Is there any chance to fix the C RTL?c >gE >  The other things is that VMS insists in writes actually completing) beforeI > calling the I/O complete - the C RTL could work around that, and XFC V2. > should help here.t  J Why would one WANT to code an application where one was not confident thatF when the OS said the I/O had completed that it HAD actually completed?  A Is this the way they teach people to program these days ? Sheesh.e <<<e   ------------------------------  % Date: Fri, 06 Apr 2001 13:52:26 +0100-- From: Tim Llewellyn <tim.llewellyn@bbc.co.uk>m$ Subject: Re: VMS-Related: Affordable) Message-ID: <3ACDBC0A.B2E3BA80@bbc.co.uk>e  ! steven.reece@quintiles.com wrote:e   > It's a unix-ism Tim  :-)   Tell that to Bill Todd.D   > L > If you want the write to complete before the completion status is returnedF > then use VMS.  If you want to think that it's been written but don'tJ > actually care then use Unix.  If you don't even want to be bothered with4 > what a write is then use a Microsoft product.  :-) > Steve.  M  Thats what I thought too but apparently I have been deluded all these years.a --6 Tim Llewellyn, OpenVMS Infrastructure, Remarcs Project0 MedAS at the BBC, Whiteladies Road, Bristol, UK.A Email tim.llewellyn@bbc.co.uk. Home tim.llewellyn@cableinet.co.ukm  A I speak for myself only and my views in no way represent those ofi MedAS or the BBC.u   ------------------------------   Date: 6 Apr 2001 09:17:31 -0700 1 From: nothome@spammers.are.scum (Malcolm Dunnett)u$ Subject: Re: VMS-Related: Affordable, Message-ID: <7LEm389Vfl8O@malvm1.mala.bc.ca>  I In article <OFF05286E4.BAB0DD32-ON80256A26.00365DC4@qedi.quintiles.com>, n&     steven.reece@quintiles.com writes: >  >  > It's a unix-ism Tim  :-)L > If you want the write to complete before the completion status is returnedF > then use VMS.  If you want to think that it's been written but don't > actually care then use Unix.  H     I'm no Unix expert, but it appears that ( at least with Tru64 Unix )/ there's an option on mount ( sync ) which says:e     syncK       Causes all writes to be written immediately to disk as well as to thee       buffer cache.r  !    This option is off by default.   C    It appears the default is to synchronously write all file system  metadata updates thought.   H   From the above it would seem that getting the VMS behaviour on Unix is4 a lot easier than getting the Unix behaviour on VMS.   ------------------------------  $ Date: Fri, 6 Apr 2001 09:06:52 -04005 From: "Fred Kleinsorge" <kleinsorge@star.zko.dec.com>"& Subject: Re: ZXLp-L2 bugcheck analysis2 Message-ID: <Ibjz6.623$fB6.16346@news.cpqcorp.net>   This brings up a favorite line:-    B                         If it hurts when you do that, don't do it.    J You will also find that the ZLXp-L2 may not work on an SMP platform.  OnlyJ count on it working on platforms it was qualified on - and for this option( that pretty much means the workstations.  D Remember also that the 32mb is being shifted left 5 places.  Not allH platforms were created equal, and not all of them have a sparse space as1 large as dense space, or even overlap the spaces.i  J Just because the comment says 16, doesn't mean that the code is wrong.  It+ could be the comment that is wrong.  Dunno.o   _Fredu  . Brian Schenkenberger, VAXman- wrote in message' <009FA087.24FB95FF@SendSpamHere.ORG>...  >OK, >e1 >Here's what I've found in my ZXLp-L2 crash dump.r >xH >The system crashes with a DECWINDOWS bugcheck which corresponds to lineI >14191 in the V7-2.1 listing of DUBDRIVER.  The reason it crashes is thatl! >IOC$MAP_IO returns SS$_BADPARAM.o >MF >I computed the address of UCB$L_GUB_BASE_ADDRESS(R5) and examined itsE >contents and it has: 07000000(16).  The driver called the IOC$MAP_IOi@ >requesting:  #<1024*1024*16*2>   ; Map 16Mbytes in sparse space= >(This looks like 32 Meg to me)  and #IOC$K_BUS_MEM_BYTE_GRANd > D >The MAP_IO routine in IO_SUPPORT_1605 checks the following for this >attribute:P >I3 >3   40220         case IOC$K_BUS_MEM_BYTE_GRAN : {o
 >3   40221D >3   40222             /* Sparse Memory Space is from 0 to 128 MB */
 >3   40223L >3   40224             if ((bus_address + num_bytes) > ONE_TWENTY_EIGHT_MB )3 >3   40225                     return SS$_BADPARAM;n >i >So, let me see... >CF >1024*1024*16*2 is 02000000(16)  plus 07000000(16) yields 09000000(16)@ >or 01000000(16) more than ONE_TWENTY_EIGHT_MB 08000000(16).  :( >E >The question now is WHY???- >- >---3 >VAXman- OpenVMS APE certification number: AAA-0001  VAXman(at)TMESIS(dot)COM >tJ >city, n., 1. a place where trees are cut down and streets are named after them.    ------------------------------  # Date: Fri, 06 Apr 2001 13:57:05 GMT5= From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)r& Subject: Re: ZXLp-L2 bugcheck analysis0 Message-ID: <009FA208.666DBCC7@SendSpamHere.ORG>  j In article <Ibjz6.623$fB6.16346@news.cpqcorp.net>, "Fred Kleinsorge" <kleinsorge@star.zko.dec.com> writes:  >This brings up a favorite line: >  >sC >                        If it hurts when you do that, don't do it.a  * Practicing medicine without a license?  ;)    K >You will also find that the ZLXp-L2 may not work on an SMP platform.  OnlyvK >count on it working on platforms it was qualified on - and for this option)) >that pretty much means the workstations.  > E >Remember also that the 32mb is being shifted left 5 places.  Not allaI >platforms were created equal, and not all of them have a sparse space as 2 >large as dense space, or even overlap the spaces. > K >Just because the comment says 16, doesn't mean that the code is wrong.  Iti, >could be the comment that is wrong.  Dunno.  G The comment is likely wrong.  The *-L2 has 32MB of memory.  Without thei. piggyback card, it becomes the *-L1 with 16MB.   --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM             eO city, n., 1. a place where trees are cut down and streets are named after them.i   ------------------------------  % Date: Fri, 06 Apr 2001 12:03:39 +0200h+ From: Richard Levitte <levitte@openssl.org>s- Subject: [ANNOUNCE] Release of OpenSSL 0.9.6a-- Message-ID: <20010406120338.L438@openssl.org>r  !   OpenSSL version 0.9.6a releasedcB   =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D  /   OpenSSL - The Open Source toolkit for SSL/TLSd   http://www.openssl.org/n  F   The OpenSSL project team is pleased to announce the release of vers= ion F   0.9.6a of our open source toolkit for SSL/TLS.  This new OpenSSL ve= rsioneF   is mostly a bugfix release and incorporates at least 55 changes to = theeF   toolkit (for a complete list see http://www.openssl.org/source/exp/=	 CHANGES).w  #   The most significant changes are:   =     o Security fix: change behavior of OpenSSL to avoid usingV1       environment variables when running as root. =     o Security fix: check the result of RSA-CRT to reduce theeA       possibility of deducing the private key from an incorrectlye       calculated signature.t8     o Security fix: prevent Bleichenbacher's DSA attack.@     o Security fix: Zero the premaster secret after deriving the'       master secret in DH ciphersuites.e9     o Reimplement SSL_peek(), which had various problems.f>     o Compatibility fix: the function des_encrypt() renamed to<       des_encrypt1() to avoid clashes with some Unixen libc.*     o Bug fixes for Win32, HP/UX and Irix.@     o Bug fixes in BIGNUM, SSL, PKCS#7, PKCS#12, X.509, CONF and       memory checking routines.h;     o Bug fixes for RSA operations in threaded enviroments.r.     o Bug fixes in misc. openssl applications.*     o Remove a few potential memory leaks.,     o Add tighter checks of BIGNUM routines.>     o Shared library support has been reworked for generality.     o More documentation.S#     o New function BN_rand_range().d:     o Add "-rand" option to openssl s_client and s_server.  F   We consider OpenSSL 0.9.6a to be the best version of OpenSSL availa=
 ble and weF   strongly recommend that users of older versions, especially of old = SSLeayF   versions, upgrade as soon as possible.  OpenSSL 0.9.6a is available=  forF   download via HTTP and FTP from the following master locations (you = can findF   the various FTP mirrors under http://www.openssl.org/source/mirror.= html):  $     o http://www.openssl.org/source/#     o ftp://ftp.openssl.org/source/i  F   [1] OpenSSL comes in the form of two distributions this time as wel= l.F   The reasons for this is that we want to deploy the external crypto = deviceF   support but don't want to have it part of the "normal" distribution=  justaF   yet.  The distribution containing the external crypto device suppor= t isF   popularly called "engine", and is considered experimental.  It's be= enF   fairly well tested on Unix and flavors thereof.  If run on a system=  withAF   no external crypto device, it will work just like the "normal" dist=	 ribution.s  "   The distribution file names are:  &       o openssl-0.9.6a.tar.gz [normal]-       o openssl-engine-0.9.6a.tar.gz [engine]i     Yours,!   The OpenSSL Project Team... =20   <     Mark J. Cox             Richard Levitte    Andy Polyakov<     Ralf S. Engelschall     Bodo M=F6ller        Holger Reif=     Dr. Stephen Henson      Ulf M=F6ller         Geoff Thorpeu*     Ben Laurie              Lutz J=E4nicke   ------------------------------   End of INFO-VAX 2001.193 ************************