1 INFO-VAX	Thu, 02 May 2002	Volume 2002 : Issue 241       Contents:# Re: 6.2/7.3 Cluster - Advice Sought  RE: Adding drives to an HSZ80  RE: Adding drives to an HSZ80 
 Re: AIM HACK? 
 Re: AIM HACK?  Re: BACKUP Question   Re: DCPS Help Required..........  Re: DCPS Help Required..........: Re: DECUS/EncompassUS Survey -- no longer assuming Windows  Re: Fix for EDT emulation in EVE Re: Gold key, Re: GUI VMS application on Linux workstation Re: HP vote cleared  Re: HP vote cleared  RE: HP vote cleared  RE: HP vote cleared  Re: HP vote cleared  Re: HP vote cleared  Re: HP vote cleared  Re: HP vote cleared ) HP vote now official. Compaq dead May 7th  IBM announcement RE: IBM announcement Re: info-zip VMS executable? Re: Itanium troubles Re: license question7 Re: New HPS Times - You ARE the weakest link, Good bye! 9 Re: Reducing size of incremental backup - will this work? 9 Re: Reducing size of incremental backup - will this work? 9 Re: Reducing size of incremental backup - will this work? / RMS equiv of F$FILE_ATTR( filename, "EOF" ) ??? 3 Re: RMS equiv of F$FILE_ATTR( filename, "EOF" ) ??? % Re: Running CSWS 1.2 on Alpha VMS 7.2 ' Re: SKC Morphs Again... We're Now SKHPC ' Re: SKC Morphs Again... We're Now SKHPC ' Re: SKC Morphs Again... We're Now SKHPC ' Re: SKC Morphs Again... We're Now SKHPC ' Re: SKC Morphs Again... We're Now SKHPC ' Re: SKC Morphs Again... We're Now SKHPC ' Re: SKC Morphs Again... We're Now SKHPC  Re: TCPIP$C_SHARE % Re: virtual i/o cache v7.2-1 and v7.3 ( Re: VMS Bigots Unite To Form New Company( Re: VMS Bigots Unite To Form New Company( Re: VMS Bigots Unite To Form New Company( Re: VMS Bigots Unite To Form New Company( Re: VMS Bigots Unite To Form New Company( Re: VMS Bigots Unite To Form New Company( Re: VMS Bigots Unite To Form New Company Re: VMS SCAN product Re: VMS SCAN product Re: VMS SCAN product Re: VMS SCAN product VMSTAR Re: Whining about HPS Times  You can't beat the price... 6 Re: ZIP strangeness (search list as part of file spec) ZTDRIVER.EXE Re: ZTDRIVER.EXE Re: ZTDRIVER.EXE RE: ZTDRIVER.EXE RE: ZTDRIVER.EXE  F ----------------------------------------------------------------------  % Date: Wed, 01 May 2002 22:00:01 -0400 2 From: rdeininger@mindspring.com (Robert Deininger), Subject: Re: 6.2/7.3 Cluster - Advice SoughtK Message-ID: <rdeininger-0105022200010001@1cust124.tnt1.nashua.nh.da.uu.net>   = In article <c113b52c.0204300757.2656ddb6@posting.google.com>, ( jbecker@ui.urban.org (Jim Becker) wrote:  D >I'm looking for sage advice, useful warnings, etc. on the following >situation.    ...   # >However, here's the basic problem: 5 >- A 6.2/7.3 mix doesn't even have migration support. - >- The minimum OS version for an ES45 is 7.3.   I Note the ES45 will come with V7.3 plus a bunch of patches pre-installed.  H Don't try to run it with plain V7.3.  (I'm not sure it would even boot.)  I For some reason, the new ES45's I've seen in the last few weeks came with H somewhat stale Factory-Installed Software disks.  I guess the disks wereD loaded some time ago and then stocked in a warehouse somewhere.  YouG should probably plan a little time to put the latest patches on the new D system.  (Of course, it's a good excuse to update your existing V7.3 systems if they need it.)    ------------------------------  $ Date: Wed, 1 May 2002 14:26:44 -0400> From: "Koska, John C. (LNG-MBC)" <John.C.Koska@lexisnexis.com>& Subject: RE: Adding drives to an HSZ80M Message-ID: <3D35AD137AAAD411A6BA0008C7B1B12D032C387D@MBCALBEXC03.BENDER.COM>   I I would not do hot-swap, unless absolutely necessary.  Instead, I would =  do4 warm-swap.  It appears to be much safer thing to do.   Take a look at: I http://wwss1pro.compaq.com/support/reference_library/viewdocument.asp?so=  urce =3DOD011115_CW01.xml&dt=3D3    :) jck
 John Koska Matthew Bender & Co., Inc. -"   A Member of the LexisNexis Group
 1275 Broadway  Albany, NY  12204  USA  518-487-3255 John.C.Koska@lexisnexis.com   ) I post personal opinion only, and all the * disclaimers one could imagine apply.  That( includes, I speak for myself only and my) views in no way represent my employer(s). + One should also take note of the Electronic ) Communications Privacy Act of 1986, which + imposes civil and criminal liability on any ( person who intentionally intercepts "any( wire, oral or electronic communication."   -----Original Message-----5 From: John Welsh [mailto:johnW@digitalexpress.com.au] & Sent: Tuesday, April 30, 2002 10:30 PM To: Info-VAX@Mvb.Saic.Com & Subject: RE: Adding drives to an HSZ80     John, 2 	No buttons to press ....  just plug the drives in: 	one at a time. Its a good idea to wait for each drive you6 	plug in to finish its spin-up although not necessary.  1 	Once the drives are in place just " RUN CONFIG " . 	and the drives will be added into the config.  2 	Then you should be able to "SHOW DEVICE " and the4 	drives will be seen but not assigned to any logical
 	"container".   - 	You can then stripe, raid or "jbod" them and  	create a suitable unit #.   Regards, John Welsh. I =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= I =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=3D=3D=3D     -----Original Message-----/ From: Jan-Erik S=F6derholm [mailto:aaa@aaa.com] & Sent: Wednesday, May 01, 2002 11:36 AM To: Info-VAX@Mvb.Saic.Com & Subject: Re: Adding drives to an HSZ80    = AFAIK, there should be this "add/remove" buttons on the HS*80 @ series also. One for each SCSI bus. I setup a HSZ80 about a year= ago, and I'm positive there is a button to press to remove or : add disks. Shouldn't be hard to find just by loking at it.   Jan-Erik S=F6derholm.    John Santos wrote: >=20 > Hi, all -  >=20@ > (On HSJ40/50's, you were supposed to press the port button forC > the bus and it would blink for about 30 seconds, while suspending C > all activity, and you could safely install, remove, or swap disks & > while the light continued blinking.) >    ------------------------------  $ Date: Wed, 1 May 2002 17:17:55 -0400  From: John Santos <JOHN@egh.com>& Subject: RE: Adding drives to an HSZ804 Message-ID: <1020501171132.334A-100000@Ives.egh.com>  3 On Wed, 1 May 2002, Koska, John C. (LNG-MBC) wrote:   L > I would not do hot-swap, unless absolutely necessary.  Instead, I would do6 > warm-swap.  It appears to be much safer thing to do. >  > Take a look at: N > http://wwss1pro.compaq.com/support/reference_library/viewdocument.asp?source > =OD011115_CW01.xml&dt=3  >  > :) jck   John -  D Thanks for the pointer.  This seems to be the most detailed and bestE info so far, and exactly what I was looking for.  I think for what we A are doing, adding new drives rather than swapping or removing, we D would be fairly safe with a hot-swap, but a warm-swap (warm install) would be safer.   B The key I think to finding this page would be to search for HSx80,B rather than HSZ80, since it seems to apply equally to HSZ/G/J80's,$ and the title is expressed that way.  
 Thanks again.    --   John Santos  Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------   Date: 1 May 2002 19:17:32 -0700 3 From: BaltimorePlayboy@yahoo.com (BaltimorePlayboy)  Subject: Re: AIM HACK?= Message-ID: <9113a9f4.0205011817.32bc5b88@posting.google.com>   E I looked up Doc Cypher and all I saw in ever newsgroup was "How can I = effectively suck a cock?" But dont worry Doc, you do it well.    ------------------------------  # Date: Thu, 02 May 2002 03:31:41 GMT ( From: "Mark E. Levy" <mlevy70@attbi.com> Subject: Re: AIM HACK?/ Message-ID: <wq2A8.208355$CH1.141646@sccrnsc02>   @ "BaltimorePlayboy" <BaltimorePlayboy@yahoo.com> wrote in message7 news:9113a9f4.0205011817.32bc5b88@posting.google.com... G > I looked up Doc Cypher and all I saw in ever newsgroup was "How can I ? > effectively suck a cock?" But dont worry Doc, you do it well.    And you would certainly know.    ------------------------------   Date: 1 May 2002 16:55:38 -0700 . From: SPAMSINK2001@YAHOO.COM (Alan E. Feldman) Subject: Re: BACKUP Question= Message-ID: <343f30ae.0205011555.2dd43565@posting.google.com>   Y briggs@encompasserve.org wrote in message news:<aP5qxxmPeELS@eisner.encompasserve.org>... p > In article <343f30ae.0204301739.6bcdc724@posting.google.com>, SPAMSINK2001@YAHOO.COM (Alan E. Feldman) writes:f > > lewis@PROBE.mitre.org (Keith A. Lewis) wrote in message news:<aan3et$lqd$1@newslocal.mitre.org>...Q > >> I had a similar problem once.  Something about normal BACKUP not setting the O > >> modification date on the top level directory [000000]000000.DIR.  Try this  > >> one time: > > H > > This appears to be exactly the problem. The backup date field in theA > > problem directory is <No backup recorded>. This directory was B > > apparently copied to the disk after the last image backup, andI > > apparently the incremental backups don't update the backup date field  > > on the .DIR file.  > D > The incremental backup command in this case (which I snipped) used% > a file specification of [*...]*.*;*  > < > That file specification does not match [000000]problem.dir    , Of course! I missed it. Oh well. Good catch!    C > Because the problem directory was not mentioned explicitly in the F > source file specification, it does not get its backup date recorded. > C > That's one reason that a lot of folks use [000000...] as a source K > file specification.  It matches the top level directory files themselves.     F I think another reason is that file protections, ACLs, and the like onF top level directories don't get saved with [*...] whereas they do withE [000000...]. (I didn't test this, but it is true IIRC.) The V5 manual = actually recommends [*...], but I believe more recent manuals  recommend [000000...].      > 	John Briggs   Disclaimer: JMHO Alan E. Feldman " afeldman atski gfigroup dotski com   ------------------------------   Date: 1 May 2002 23:58 CDT' From: carl@gerg.tamu.edu (Carl Perkins) ) Subject: Re: DCPS Help Required.......... , Message-ID: <1MAY200223582615@gerg.tamu.edu>  : MGATTAURA@COLLINS-STEWART.COM (Mandeep Gattaura) writes...E }I have managed to solve that problem - I had a "showpage" at the end E }of the form. I am still having a problem printing multiple page data E }files. The first page is overlayed onto the form, but the subsequent  }pages come out with no form. D }Not sure if the is a way of telling the print (or queue), to retain@ }the form until the end of the job. Does anyone know the answer? }  }Thanks  }Mandeep  ; As has been indicated, you can redefine "showpage" for your ? job so that the showpage command itself draws the form for you.   A Alternatively, you can use your PS module that now works once and > apply it to every page. In the DEFINE/FORM command you can use? /PAGE_SETUP instead of /SETUP. This applies the module from the A device control library to the start of every page instead of just  the start of the file.   --- Carl   ------------------------------  % Date: Thu, 02 May 2002 01:35:18 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca> ) Subject: Re: DCPS Help Required.......... , Message-ID: <3CD0D005.8C90C35D@videotron.ca>   Carl Perkins wrote: C > Alternatively, you can use your PS module that now works once and @ > apply it to every page. In the DEFINE/FORM command you can useA > /PAGE_SETUP instead of /SETUP. This applies the module from the C > device control library to the start of every page instead of just  > the start of the file.  ' How would this be implemented by DCPS ?   N While the text symbiont has a fairly easy way to find the start of a new page,N the postscript one doesn't. It is very hard to figure out when postscript codeI actually generates a new page. (That is why DCPS interrogates the printer K before and after a job to figure out how many pages were spewed out because ; there is no way to tell by looking at the postscript code).   L The only way DCPS could emulate the /PAGE_SETUP is to wrap the module into aK routine and redefine showpage to do a normal showpage and then execute that 9 routine that contains the code of the /PAGE_SETUP module.    ------------------------------   Date: 1 May 2002 23:36 CDT' From: carl@gerg.tamu.edu (Carl Perkins) C Subject: Re: DECUS/EncompassUS Survey -- no longer assuming Windows , Message-ID: <1MAY200223363466@gerg.tamu.edu>  $ Steve.Spires@yellgroup.com writes...C }carl@gergl1.gerg.tamu.edu (Carl Perkins) on 05/01/2002 02:04:00 AM  } ! }To:        Info-VAX@Mvb.Saic.Com  }cc:K }From:      carl@gergl1.gerg.tamu.edu (Carl Perkins), 1 May 2002, 2:04 a.m.  } ; }Re: DECUS/EncompassUS Survey -- no longer assuming Windows  } 	 }[cut...]  } H }If as few as something like 23 people with one postal code answer, oddsB }are better than 50% that two of them will have the same birthday. } 	 }--- Carl  }  }Why's that then?  }  }Steve S   Statistics.    Let p = 1 - (1/365.25)  B Probability that there is no shared birthday in a group of people:*  2 people: p2  = p          (0.9972621492)*  3 people: p3  = p^2 * p2   (0.9918089146)*  4 people: p4  = p^3 * p3   (0.9836849231)*  5 people: p5  = p^4 * p4   (0.9729563534)*  6 people: p6  = p^5 * p5   (0.9597100385)*  7 people: p7  = p^6 * p6   (0.9440522954)*  8 people: p8  = p^7 * p7   (0.9261075045)*  9 people: p9  = p^8 * p8   (0.9060164648)* 10 people: p10 = p^9 * p9   (0.8839345567)* 11 people: p11 = p^10 * p10 (0.8600297429)* 12 people: p12 = p^11 * p11 (0.8344804472)* 13 people: p13 = p^12 * p12 (0.8074733453)* 14 people: p14 = p^13 * p13 (0.7792011073)* 15 people: p15 = p^14 * p14 (0.7498601299)* 16 people: p16 = p^15 * p15 (0.7196482942)* 17 people: p17 = p^16 * p16 (0.6887627854)* 18 people: p18 = p^17 * p17 (0.6573980066)* 19 people: p19 = p^18 * p18 (0.6257436166)* 20 people: p20 = p^19 * p19 (0.5939827173)* 21 people: p21 = p^20 * p20 (0.5622902144)* 22 people: p22 = p^21 * p21 (0.5308313676)* 23 people: p23 = p^22 * p22 (0.4997605449)  @ So at 23 people there is only about a 49.976% chance that no twoC of them will share a birthday, or about a 50.024% chance that there  will be at least one match.   D This does assume an even distribution of birthdays in the populationD in question, which probably isn't quite true. The difference is withB reality is probably fairly small. It also ignores 1900 not being aC leap year even though there are still a few people alive from then. ? This should also not skew the statistics much - especially when C considering how likely it is that someone who is at least 102 years  old will respond to the poll.   = But really, I just remembered the answer. This was why I said B "something like" since I couldn't remember if it was 23 you needed= or more than 23 you needed to top the 50% mark - as the above ? calculations indicate, it is in "the number you need to top 50%  probability" category.  ? People tend to find this number surprisingly small - most would @ guess that it was more like 365/2 rounded up = 183 people to getB over 50% chance of two sharing a birthday. But this is math, whichC is not a democracy, and "most people" are often wrong when it comes " to things involving probabilities.   --- Carl   ------------------------------  # Date: Thu, 02 May 2002 01:51:23 GMT 1 From: "David J. Dachtera" <djesys.nospam@fsi.net> ) Subject: Re: Fix for EDT emulation in EVE ' Message-ID: <3CD09E8B.948F0A49@fsi.net>    Peter Weaver wrote:  > M > Below is the reply I sent to David through private e-mail, I'm not going to N > post the attachments here, if anyone wants to look at any of the attachments? > I sent David then let me know and I will send them privately.  > [snip]  @ Peter's reply sort of underscored what I discovered when first IG reviewed the feasibility of doinga complete re-write of EDTINI.EDT into  TPU/EVE.  ! Let just take one simple example:   
 In EDT, it's: ! DEFINE KEY GOLD  C AS "D+CCUNDC."    In TPU, it's something like:   PROCEDURE transpose_char 	eve$edt_delete_char;  	eve_move_right; 	eve_restore_character;  endprocedure  3 Tons more code: five lines in TPU, one line in EDT.   9 Rather like BASIC (PRINT "Hello, world!") versus COBOL...   H I suppose someday I may have to give up on EDT, but that day is not yet.  E EDT is still useful. For those needs that require TPU, it's there for0 me.u   Good enough for me.    -- e David J. Dachteral dba DJE Systemsu http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------   Date: 1 May 2002 22:28 CDT' From: carl@gerg.tamu.edu (Carl Perkins)p Subject: Re: Gold keye, Message-ID: <1MAY200222284268@gerg.tamu.edu>  , Nic Clews <sendspamhere@127.0.0.1> writes... }warren sander wrote: K }> The reason it's called 'gold key' was that at one point Digital actuallya4 }> manufactured keyboards with a 'gold key' on them. }> t }> I still have one..  } I }I have several. Also I used to use a VT52 which also had red and blue as  }well as gold keys.o } B }It allows you to use the little publicized DCL define/key and use }  }/SET_STATE=colour }  }then DEFINE/KEY }  }/IF_STATE=GOLD... }/IF_STATE-RED...u }/IF_STATE=BLUE... } - }So one keypad key could have four functions.i }-- ) }Regards, Nic Clews CSC Computer Sciences   D This also lets you pick which key you want to be each of the colors.  / I actually use this, more or less. In my login:   @ $ define/key pf1 "show "/echo/noterminate/set_state="gold"/nolog< $ define/key pf1 "time"/terminate/nolog/echo/if_state="gold"> $ define/key pf2 "monitor system/int=1"/terminate/noecho/nologF $ define/key pf2 "device/full "/noterminate/echo/if_state="gold"/nolog? $ define/key pf3 "monitor process/int=5"/terminate/noecho/nolog > $ define/key pf3 "log "/noterminate/echo/if_state="gold"/nologF $ define/key pf4 "monitor process/int=1/topcpu"/terminate/noecho/nologA $ define/key pf4 "symbol "/noterminate/echo/if_state="gold"/nologU  E So PF2 through PF4 each has two functions, a MONITOR related functionMF in the normal state, or a function that completes the SHOW for variousG things after PF1 has been pressed to do the SHOW part and put the statee to GOLD.  G On the other hand, it turns out that the only one of the gold functions @ that I actually use on anything resembling a regular basis is toB just hit PF1 twice to get a SHOW TIME. I usualy can't even remeber= which of the others is which - it's just easier to type stuff-A in than remember the key. Typing in "sh log whatever" is not that A many more keystrokes than "PF1 PF3 whatever", and I don't need toC< move my hand off the regular keyboard section to the keypad.A Oh well. It seemed like a good idea at the time I put it in there3? (which was probably sometime around 1990, give or take). On thee> other other hand, I do use the direct, non gold-state, monitor
 functions.   --- Carl   ------------------------------  % Date: Thu, 02 May 2002 16:40:35 +1200x From: Kevin <waugh@met.co.nz>p5 Subject: Re: GUI VMS application on Linux workstation ( Message-ID: <3CD0C343.1030806@met.co.nz>   Sandeep Yelwatkar wrote: > Hi, M >     I run applications from VMS server on NT workstation (helped by EXCEED,  > Xsession or else...),'; > but I don't know how to do this on a Linux workstation :(F > Please help me !!! > 	 > Sandeepu >  >  >   $ If you telnet to the VMS system then  3 $ set display/create/node=10.10.192.142/trans=tcpipl $ r sys$system:decw$notepada  8 where node is your linux workstation address or hostname  F if you put this in a command procedure called notepad.com for example 7 you can invoke it from the linux command line like this-  B rexec -l yourlogon -p yourpassword hostname.met.co.nz '@notepad' &  F bearing in mind you are sending your username and password across the A network. This may or may not be a problem depending on your site.s   ------------------------------  % Date: Wed, 01 May 2002 14:16:28 -0400a- From: JF Mezei <jfmezei.spamnot@videotron.ca>l Subject: Re: HP vote cleared, Message-ID: <3CD030F4.FD0DF9FB@videotron.ca>   "Terry C. Shannon" wrote:WN > Word has it this will happen once the acquisition is a done deal. The PowersD > That Be did not have the guts to come forth with same prior to the > consummation of the deal.e  J please define "done deal" ? At what point will Carly run out of excuses to avoid talking about VMS ?d   Let me see: * she declared a win on the day of election.* she declared semi-official tally as a win.5 she kicked out her only opposition from the HP board.64 she won in court against said (former) board member.  H Will she wait until all "Compaq" logos have disapeared from letterheads,M buildings, products etc before declaring that it is time to speak about VMS ?x  M Once she signs the papers with her new husband Curly, will she wait until the J lawyers and accountants have done all the background paperwork and the SECH officially removed the name "Compaq" from its database of corporations ?  K Will she wait until every Compaq branded PC has been thrown away due to old  age ?v  L Hint: of the VMS engineers do not announce immediatly that they have begun aN rebranding efford to change all copyrights, are we to assume that VMS will notL survive ? At what point would the continued use of the word "Compaq" for VMSF stuff signal that HP does not intend to really integrate VMS into HP ?  N The longer Carly waits, the easier it becomes for customers to see some "HP is killilng VMS" spin into it.3  K If Carly is aware that she needs to keep VMS to keep the company afloat and N subsidize her wintel follies, then she would be aware that she needs to send a. strong signal to the remaining customers ASAP.   ------------------------------  # Date: Wed, 01 May 2002 18:39:13 GMTe# From: "John Smith" <a@nonymous.com>o Subject: Re: HP vote clearedH Message-ID: <lDWz8.63195$Il1.16817@news02.bloor.is.net.cable.rogers.com>  K Given the Curly memo presented into evidence during the Delaware trial, yousK know - "At current course and speed we will fail.", want to lay any bets asiF to how long before Curly gets the golden handshake and shown the door?      < "Terry C. Shannon" <terryshannon@attbi.com> wrote in message5 news:49Uz8.60333$%s3.23768939@typhoon.ne.ipsvc.net...l >e> > "Dave Gudewicz" <david.gudewicz@abbott.com> wrote in message4 > news:aaoqh2$s0e$1@fizban.fizban.pprd.abbott.com.../ > > I liked the reach and frequency phrase btw.. > >  > > Dave...A > > E > >  what's to become of VMS. No, I don't think it'll die off. I just>
 > > > want toaG > > >     see some sort of statement made LOUD and CLEAR with reach andl > > frequency. > > >y >IG > Word has it this will happen once the acquisition is a done deal. The. PowersD > That Be did not have the guts to come forth with same prior to the > consummation of the deal.  >0L > Fortunately for the Windoze and NSK contingent, statements regarding their# > products were not embargoed. Doh.t >n >s   ------------------------------  $ Date: Wed, 1 May 2002 11:54:01 -0700# From: "Tom Linden" <tom@kednos.com>p Subject: RE: HP vote cleared9 Message-ID: <CIEJLCMNHNNDLLOOGNJIMEBPEOAA.tom@kednos.com>)  H As you may recall from previous posts, it wasn't just a golden handshake it was a chest of gold   >-----Original Message-----y) >From: John Smith [mailto:a@nonymous.com]e' >Sent: Wednesday, May 01, 2002 11:39 AM- >To: Info-VAX@Mvb.Saic.Com >Subject: Re: HP vote cleared0 >t >9L >Given the Curly memo presented into evidence during the Delaware trial, youL >know - "At current course and speed we will fail.", want to lay any bets asG >to how long before Curly gets the golden handshake and shown the door?o >y >r >d= >"Terry C. Shannon" <terryshannon@attbi.com> wrote in messagea6 >news:49Uz8.60333$%s3.23768939@typhoon.ne.ipsvc.net... >>? >> "Dave Gudewicz" <david.gudewicz@abbott.com> wrote in message 5 >> news:aaoqh2$s0e$1@fizban.fizban.pprd.abbott.com...C0 >> > I liked the reach and frequency phrase btw. >> > >> > Dave... >> >F >> >  what's to become of VMS. No, I don't think it'll die off. I just >> > > want toH >> > >     see some sort of statement made LOUD and CLEAR with reach and >> > frequency.  >> > > >>H >> Word has it this will happen once the acquisition is a done deal. The >Powers E >> That Be did not have the guts to come forth with same prior to the  >> consummation of the deal. >>= >> Fortunately for the Windoze and NSK contingent, statementsa >regarding their$ >> products were not embargoed. Doh. >> >> >o >w >---' >Incoming mail is certified Virus Free.p; >Checked by AVG anti-virus system (http://www.grisoft.com).pA >Version: 6.0.351 / Virus Database: 197 - Release Date: 4/19/2002: >  ---i& Outgoing mail is certified Virus Free.: Checked by AVG anti-virus system (http://www.grisoft.com).@ Version: 6.0.351 / Virus Database: 197 - Release Date: 4/19/2002   ------------------------------  $ Date: Wed, 1 May 2002 14:24:25 -0500/ From: "Stuart, Ed" <Ed.Stuart@austinenergy.com>h Subject: RE: HP vote clearedT Message-ID: <92EFB80E551BD511B39500D0B7B0CDCC0642C3BD@ohms.electric.ci.austin.tx.us>  5 I thought I read that the "Curly memo" was a forgery?e   EdE **Please apply a generous amount of all the usual disclaimers here.**d     -----Original Message-----( From: John Smith [mailto:a@nonymous.com]% Sent: Wednesday, May 01, 2002 1:39 PMi To: Info-VAX@Mvb.Saic.Comi Subject: Re: HP vote cleared    K Given the Curly memo presented into evidence during the Delaware trial, youeK know - "At current course and speed we will fail.", want to lay any bets asoF to how long before Curly gets the golden handshake and shown the door?      < "Terry C. Shannon" <terryshannon@attbi.com> wrote in message5 news:49Uz8.60333$%s3.23768939@typhoon.ne.ipsvc.net...  >c> > "Dave Gudewicz" <david.gudewicz@abbott.com> wrote in message4 > news:aaoqh2$s0e$1@fizban.fizban.pprd.abbott.com.../ > > I liked the reach and frequency phrase btw.[ > >  > > Dave...d > >hE > >  what's to become of VMS. No, I don't think it'll die off. I just 
 > > > want tomG > > >     see some sort of statement made LOUD and CLEAR with reach and  > > frequency. > > >  >cG > Word has it this will happen once the acquisition is a done deal. The- PowersD > That Be did not have the guts to come forth with same prior to the > consummation of the deal.: >:L > Fortunately for the Windoze and NSK contingent, statements regarding their# > products were not embargoed. Doh.e >G >a   ------------------------------  # Date: Wed, 01 May 2002 20:40:42 GMT"* From: "Bill Todd" <billtodd@metrocast.net> Subject: Re: HP vote clearedA Message-ID: <epYz8.16735$Ii2.1498089@bin2.nnrp.aus1.giganews.com>t  : "Stuart, Ed" <Ed.Stuart@austinenergy.com> wrote in messageL news:92EFB80E551BD511B39500D0B7B0CDCC0642C3BD@ohms.electric.ci.austin.tx.us. ..7 > I thought I read that the "Curly memo" was a forgery?n  H I believe what you read was that a purported Curly email to Walter was aI forgery.  The 'current course and speed' (one might call it the 'vector'),H reference was supposedly in Curly's diary (wonder who dug *that* up) or,1 possibly, in some statement he made at a meeting.E   - bill   ------------------------------  % Date: Wed, 01 May 2002 17:50:36 -0400h- From: JF Mezei <jfmezei.spamnot@videotron.ca>r Subject: Re: HP vote cleared, Message-ID: <3CD0632A.77657A0D@videotron.ca>   John Smith wrote:0 > M > Given the Curly memo presented into evidence during the Delaware trial, youeM > know - "At current course and speed we will fail.", want to lay any bets aseH > to how long before Curly gets the golden handshake and shown the door?  J She will stay on long enough to cause enough damage. By the time the boardM decides to kick her out, it will be too late. Besides, she has eliminated heryK opposition so now she has a board slate that will be good dogs and sit when  Carly tells them to sit.   ------------------------------  % Date: Wed, 01 May 2002 21:24:42 -0400r2 From: rdeininger@mindspring.com (Robert Deininger) Subject: Re: HP vote clearedK Message-ID: <rdeininger-0105022124420001@1cust124.tnt1.nashua.nh.da.uu.net>   5 In article <3CD030F4.FD0DF9FB@videotron.ca>, JF Mezein% <jfmezei.spamnot@videotron.ca> wrote:     M >Hint: of the VMS engineers do not announce immediatly that they have begun amO >rebranding efford to change all copyrights, are we to assume that VMS will not M >survive ? At what point would the continued use of the word "Compaq" for VMSoG >stuff signal that HP does not intend to really integrate VMS into HP ?a  I This is a perfectly useless indicator.  A module would not get re-brandedSH and re-lawyered unless/until someone actually modifies it for some otherH reason.  There are lots of places in the current listings kit that still  have Digital copyright notices.   I In any case, I suspect VMS 7.3-1 is way too far along for anyone to spend: time rebranding it.g  N Besides, they have to use up the existing stock of Sun-branded VMS wrappers.   :-)n   ------------------------------  % Date: Thu, 02 May 2002 01:19:42 -0400e( From: David Froble <davef@tsoft-inc.com> Subject: Re: HP vote cleared* Message-ID: <3CD0CC6E.60601@tsoft-inc.com>   Robert Deininger wrote:a    P > Besides, they have to use up the existing stock of Sun-branded VMS wrappers.   > :-)  >     Q It's really too bad that those weren't HP systems in the wrappers.  Think of the oC fun we could have with that.  Someone knew of the merger years ago?9   Dave   ------------------------------  % Date: Wed, 01 May 2002 21:18:52 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca>92 Subject: HP vote now official. Compaq dead May 7th+ Message-ID: <3CD093FB.BB61FDC@videotron.ca>)  4 http://www.hp.com/hpinfo/newsroom/press/01may02b.htm  ; HP Announces Certified Vote Tally on Compaq Merger Proposal0#  New HP Expected to Launch on May 7    PALO ALTO, Calif., May 1, 2002     H  Hewlett-Packard Company (NYSE:HWP) today announced that the independentL Inspectors of Election, representatives of IVS Associates, Inc., have issuedM their final Inspectors of Election report with respect to the special meeting0' of shareowners held on March 19, 2002.    J  According to the report, there were 838,401,376 shares of HP common stockL voted for the proposal to approve the issuance of shares of HP common stock J in connection with the merger transaction with Compaq Computer CorporationH (NYSE:CPQ), 793,094,105 shares voted against the proposal and 13,950,651I shares abstained. Based on this report, HP confirms that the proposal hasa@ passed in accordance with New York Stock Exchange requirements.   M   HP expects to close the deal on May 3, 2002. The launch of the new HP will p take place on May 7, 2002.   ------------------------------  $ Date: Wed, 1 May 2002 11:17:34 -0700# From: "Tom Linden" <tom@kednos.com>r Subject: IBM announcemento9 Message-ID: <CIEJLCMNHNNDLLOOGNJIGEBOEOAA.tom@kednos.com>o  + http://www.ibm.com/news/us/2002/04/293.htmlrL http://www-916.ibm.com/press/prnews.nsf/jan/CB61AC5EAFBD69BB85256BAB0051F477L http://www-916.ibm.com/press/prnews.nsf/jan/6EB4F3FD32371B3785256BAA004912A2  4 Interesting.  Not all the apps that run on the i890. ---0& Outgoing mail is certified Virus Free.: Checked by AVG anti-virus system (http://www.grisoft.com).@ Version: 6.0.351 / Virus Database: 197 - Release Date: 4/19/2002   ------------------------------  $ Date: Wed, 1 May 2002 11:28:26 -0700# From: "Tom Linden" <tom@kednos.com>  Subject: RE: IBM announcement 9 Message-ID: <CIEJLCMNHNNDLLOOGNJIAEBPEOAA.tom@kednos.com>-   >-----Original Message----- ) >From: Tom Linden [mailto:tom@kednos.com]a' >Sent: Wednesday, May 01, 2002 11:18 AMF >To: Info-VAX@Mvb.Saic.Com >Subject: IBM announcement >9 >i, >http://www.ibm.com/news/us/2002/04/293.htmlD >http://www-916.ibm.com/press/prnews.nsf/jan/CB61AC5EAFBD69BB85256BA
 >B0051F477D >http://www-916.ibm.com/press/prnews.nsf/jan/6EB4F3FD32371B3785256BA
 >A004912A2 >e5 >Interesting.  Not all the apps that run on the i890.] Meant to say,  Notet >---' >Outgoing mail is certified Virus Free. ; >Checked by AVG anti-virus system (http://www.grisoft.com).IA >Version: 6.0.351 / Virus Database: 197 - Release Date: 4/19/2002T >t >---' >Incoming mail is certified Virus Free.T; >Checked by AVG anti-virus system (http://www.grisoft.com).tA >Version: 6.0.351 / Virus Database: 197 - Release Date: 4/19/2002e >e ---o& Outgoing mail is certified Virus Free.: Checked by AVG anti-virus system (http://www.grisoft.com).@ Version: 6.0.351 / Virus Database: 197 - Release Date: 4/19/2002   ------------------------------  # Date: Wed, 01 May 2002 21:46:37 GMTr2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)% Subject: Re: info-zip VMS executable?y9 Message-ID: <1nZz8.28$k_1.457818@cacnews.cac.cpqcorp.net>n  u In article <SNJz8.6363$N8.744968@bin5.nnrp.aus1.giganews.com>, "Peter A. Stoll" <archae86_unspam@comcast.net> writes:aM :Unfortunately the non-Alpha version I have on Info-zip is quite old (version2E :1.9), and does not handle at least two real situations arising in my C :accounts well enough for me to get any use of it for this purpose.  :oK :The distribution sites I have found offer the unzip side in VMS executableeG :form, but only source for the zip side.  (you guessed it, a c compiler K :license is not active on the nodes for which I have accounts, and I am tooy# :ignorant to use one quickly also).e :eK :Perchance could a kind soul point me to a non-alpha executable for the ZIPL  :side of an up-to-date info-zip?    G   As part of your preparations, please download the OpenVMS Frequently sJ   Asked Questions (FAQ).  Lots of useful information.  Yes, even pointers H   to current zip tools are included in the FAQ.  Oh, and zip is also on !   the current Freeware, too.  :-)"    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: Thu, 02 May 2002 01:17:10 GMT 1 From: "David J. Dachtera" <djesys.nospam@fsi.net>i Subject: Re: Itanium troublese' Message-ID: <3CD09682.FC73599C@fsi.net>r   Peter da Silva wrote:c > ) > In article <3CCF49D3.D874B30B@fsi.net>,a2 > David J. Dachtera <djesys.nospam@fsi.net> wrote:K > > No one wants to "enforce" anything on anyone. Don't read it if it's nott
 > > there. > K > "Reading books on usability should be a requirement for all programmers."t > H > If it's a requirement you don't enforce it's not a requirement, is it?  + Check your quoting. That's not what I said.b   I said:f  3 > > I took that to mean that Sander apparently sees G > > neither the necessity nor importance of usability as having as muchmI > > weight as the other issues involved in the development of open-sourceo
 > > software.k  B As evidenced by other threads in the group, neither importance norH necessity constitutes a mandate in the eyes of many. The original posterB implied a mandate. I implied something more along the lines of the5 difference between doing something and doing "right".-  L > > > Now you may read *that* as usability not "having as much weight as theH > > > other issues involved in the development of open-source software", > K > > You and I can bandy it about until Bill Gates goes belly-up. The bottom I > > line is this: if you want people to use your software, give them whats > > they want - usability. > M > You can bandy it about all you want. The bottom line is this, talking about N > what should be a requirement for a developer isn't going to get any software
 > developed, .  H You really need to get that "requirement" bit. They can choose to ignoreH advice indicating that certain actions on their part would help garner aD larger audience - that's up to them. I'm still REQUIRING anything ofE anyone - other than of myself, regarding what I will and won't pursuee for my own needs.&  ' Take it as a "statement by the market".e  B > and it's not going to get any documentation written. If you haveM > something to contribute, then you know where the CVS tree is. If you're not M > a coder, then write documentation. That's what I mostly did for the FreeBSDcN > Project when I was more closely involved with it... I was one of the FreeBSDM > Handbook maintainers. Yes, I did coding as well, but I do that for a livingnN > and I need to do something ELSE to relax these days (it's hell getting old).   I'm hip.  J > If you're as good as you seem to be, they'll be happy to give you commitJ > privileges. It's not that they don't want to make the system more usableE > or better suited to end users, it's that they're up to their ass inyK > alligators and Microsoft and Intel and a hundred frantic hardware vendorsnJ > struggling to stay ahead of the pack are busily pumping toxic waste into > the swamp.  F Well, "RTFM" has become the industry-standard joke these days. I doubtF documentation will have as much of an impact as something that the endC user can easily relate to with regard to getting more code into the  hands of more M$ expatriates.p   -- a David J. Dachteral dba DJE Systemsm http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/n   ------------------------------  % Date: Wed, 01 May 2002 21:38:12 -0400n2 From: rdeininger@mindspring.com (Robert Deininger) Subject: Re: license questionrK Message-ID: <rdeininger-0105022138130001@1cust124.tnt1.nashua.nh.da.uu.net>   H In article <MZSz8.154549$nc.21286476@typhoon.tampabay.rr.com>, "John N." <JNixon@cfl.rr.com> wrote:  M >I have four Alpha departmental class machines.  One of them has an unlimitedsJ >user license, but could get by with a 16 user license.  Two of the AlhpasK >have 32 user licenses.  One of them needs more licensed user seats. One ofu >them Icould actuallyeC >get rid of.  One has a four user license, and will soon need more.- >-M >Can I move these licenses around as I see fit, or do I need to notify Compaq" >and/or pay any sort of fees.:  A You'll have to consult your specific license terms to be certain.n  D Generally speaking, alpha user licenses of recent vintage are prettyI portable amoung machines that you own.  Just don't register and load morea units than you are entitled to.o  G The unlimited license can probably only be used on 1 machine at a time, I but I never had one so I'm not certain.  (I'd guess that an unlimited PAK3C is NO_SHARE, so that it can only be loaded on 1 node in a cluster.)d   ------------------------------    Date: 02 May 2002 06:35:37 +0800, From: Paul Repacholi <prep@prep.synonet.com>@ Subject: Re: New HPS Times - You ARE the weakest link, Good bye!0 Message-ID: <87d6wfsdhi.fsf@k9.prep.synonet.com>  * "C.W.Holeman II" <cwhii5@ACM5.org> writes:    ! > In that light, who owns VAXELN?t  0 Cumpuke I guess, it is still on the Vax CONDIST.   -- s< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------   Date: 1 May 2002 16:45:40 -0700m. From: SPAMSINK2001@YAHOO.COM (Alan E. Feldman)B Subject: Re: Reducing size of incremental backup - will this work?= Message-ID: <343f30ae.0205011545.1a27713b@posting.google.com>d  h tadamsmar@aol.com (Tom Adams) wrote in message news:<793af3df.0204300858.7baf1b61@posting.google.com>...E > I want to try to do backup/record on a directory to keep the entireC5 > contents from being backuped.  Something like this:C > ( > !Backup to force record of backup date- > $BACKUP/RECORD  DSA0:[FOO]BAR.DIR DUMMY.TMPa > $DELETE DUMMY.TMP.*,' > !Proceed with real incremental backupf: > $BACKUP/SINCE=BACKUP DSA0{000000...]  TAPEDRIVE:BLAHBLAH > D > This directory will never be renamed.  It is a large direcory withK > some file creates and deletes happening in it every day, but only a small": > portion of the files in it are changed on a daily basis. > H > Is there any problem with this?  I am not sure of all the reasons thatE > VMS was revised in the first place to backup all the contents of a .5 > directory when the directory's modify date changed.o    & This is fine. But I would change it to  C     $ BACKUP/RECORD DSA0:[FOO]BAR.DIR NL:A.B/SAVE_SET/NOCRC/GROUP=0a4     $ BACKUP/VERIFY DSA0:[000000...]/SINCE=BACKUP  -            TAPEDRIVE:BLAHBLAH.BCK  * and use a block size no larger than 32256.  C This way you'll get the old incremental behavior for that directoryn/ but the new behavior for all other directories.t  D The incremental behavior was changed so that renamed directories areF restored properly. Under the old scheme, you could end up with a mess:D BACKUP/INCREMENTAL would restore files saved under the old directoryC name under the old directory name and restore files saved under theeB new directory name under the new directory name. The result: FilesD that were modified after the directory name was changed would appearF in both and in general not be identical. Files that were deleted afterD the directory name change would still appear under the old directoryD name. According to the release notes, some files would not come back@ at all, though I don't see how that would happen unless the disk= filled up, in which case you could just re-apply the relevantsB incrementals. Back when all this was started, one poster showed anC example using SET FILE/ENTER how one could lose a file with the oldiD incremental scheme, so maybe that's how you'd lose data. I could try to dig it up if you like.t  E The new incremental method eliminates the above problems, I believe.    F The problem is that directory modification dates are updated too oftenF in some circumstances, due to XQP (?) bugs, or MacIntosh Pathworks, or@ the like, or the unlike, whatever, resulting in huge incremental backups.   Disclaimer: JMHO Alan E. Feldmane" afeldman atski gfigroup dotski com   ------------------------------  % Date: Wed, 01 May 2002 21:29:57 -0400 2 From: rdeininger@mindspring.com (Robert Deininger)B Subject: Re: Reducing size of incremental backup - will this work?K Message-ID: <rdeininger-0105022129580001@1cust124.tnt1.nashua.nh.da.uu.net>d  9 In article <fm0A8.31$n_1.460867@cacnews.cac.cpqcorp.net>, $ hoffman@xdelta.zko.dec.nospam wrote:     >:E >:    $ BACKUP/RECORD DSA0:[FOO]BAR.DIR NL:A.B/SAVE_SET/NOCRC/GROUP=0c6 >:    $ BACKUP/VERIFY DSA0:[000000...]/SINCE=BACKUP  -" >:          TAPEDRIVE:BLAHBLAH.BCK >: >nH >  /NOCRC and /GROUP=0 mean you really trust your tape hardware to work.  J Um, this example uses the null device.  I think it takes a special kind of* paranoia to CRC writes to the null device.   :-).   ------------------------------  # Date: Thu, 02 May 2002 01:10:35 GMTb2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)B Subject: Re: Reducing size of incremental backup - will this work?9 Message-ID: <fm0A8.31$n_1.460867@cacnews.cac.cpqcorp.net>h  n In article <343f30ae.0205011545.1a27713b@posting.google.com>, SPAMSINK2001@YAHOO.COM (Alan E. Feldman) writes:i :tadamsmar@aol.com (Tom Adams) wrote in message news:<793af3df.0204300858.7baf1b61@posting.google.com>...pF :> I want to try to do backup/record on a directory to keep the entire6 :> contents from being backuped.  Something like this: :> -) :> !Backup to force record of backup date1. :> $BACKUP/RECORD  DSA0:[FOO]BAR.DIR DUMMY.TMP :> $DELETE DUMMY.TMP.*( :> !Proceed with real incremental backup; :> $BACKUP/SINCE=BACKUP DSA0{000000...]  TAPEDRIVE:BLAHBLAHh  A   You can set the dates -- including the BACKUP date -- using the @   Freeware DFU tool.  It's rather easier than the proposed, and    a much more direct solution.  E :> This directory will never be renamed.  It is a large direcory withnG :> some file creates and deletes happening in it every day, but only a cA :> small portion of the files in it are changed on a daily basis.p :> iI :> Is there any problem with this?  I am not sure of all the reasons that F :> VMS was revised in the first place to backup all the contents of a 6 :> directory when the directory's modify date changed.  @   BACKUP/RECORD is intended to be used with /IMAGE, and then the>   backups are run incremental (and restored with /INCREMENTAL)A   to rebuild the disk.  If you are interested in this, you reallynA   will want to review the examples of performing full BACKUP and nD   subsequent incremental operations, as listed in the BACKUP manual. :l' :This is fine. But I would change it tol :oD :    $ BACKUP/RECORD DSA0:[FOO]BAR.DIR NL:A.B/SAVE_SET/NOCRC/GROUP=05 :    $ BACKUP/VERIFY DSA0:[000000...]/SINCE=BACKUP  -r! :          TAPEDRIVE:BLAHBLAH.BCKh :i  G   /NOCRC and /GROUP=0 mean you really trust your tape hardware to work.e  D   Given you have shadowsets, I'd look seriously at quescing the disk4   activity briefly, and then splitting off a volume.  D :This way you'll get the old incremental behavior for that directory0 :but the new behavior for all other directories.  E   /NOINCREMENTAL (and the current BACKUP ECO kit) is a better way to t/   get the old behaviour, if you really want it.-    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: Wed,  1 May 2002 16:08:08 -0400 . From: "Chris Olive" <colive@technologease.com>8 Subject: RMS equiv of F$FILE_ATTR( filename, "EOF" ) ???> Message-ID: <200205011608.AA1605959898@mail.technologease.com>  W Me again.  Needing ticklers on stuff I know I used to know inside and out...  Anyway...-  What is the RMS structure equivalent to the DCL lexical F$FILE_ATTR( filename, "EOF" ) operation on a file (returns the actual blocks in use by a file).  I found the $FAB structure FAB$L_ALQ field, which returns the allocation quantity, but I do recall that you can have blocks allocated to a file but still have nothing in the file.  So what's the F$FILE "EOF" equiv in RMS?  I looked through all the $FAB and $XABxxx blocks/fields, but nothing is ringing a bell.   I guess I could have whipped up a quick routine to LIB$FIND_FILE a file, used the context field (which again if I recall is a FAB pointer), and dumped the FAB fields, but I thought I would just ask.   Chrisi -----m Chris Olivet colive@NOSPAM.technologEase.comi   ------------------------------  # Date: Wed, 01 May 2002 20:50:29 GMT6* From: "Bill Todd" <billtodd@metrocast.net>< Subject: Re: RMS equiv of F$FILE_ATTR( filename, "EOF" ) ???@ Message-ID: <pyYz8.16631$q8.2416409@bin3.nnrp.aus1.giganews.com>  9 "Chris Olive" <colive@technologease.com> wrote in messagep8 news:200205011608.AA1605959898@mail.technologease.com...G > Me again.  Needing ticklers on stuff I know I used to know inside andr out...  Anyway...u >m9 > What is the RMS structure equivalent to the DCL lexicalcL $FILE_ATTR( filename, "EOF" ) operation on a file (returns the actual blocksE in use by a file).  I found the $FAB structure FAB$L_ALQ field, whichmI returns the allocation quantity, but I do recall that you can have blocks F allocated to a file but still have nothing in the file.  So what's theE F$FILE "EOF" equiv in RMS?  I looked through all the $FAB and $XABxxx.- blocks/fields, but nothing is ringing a bell.a  H Well, in at least one sense the ALQ value really is the actual amount ofG space in use by a file, even if there's nothing yet in it.  But I thinkaJ you'll find what you want in two fields of the File Header CharacteristicsG XAB (highest-addressed valid byte in the file, plus 1 - though it won't 7 account for any 'sparseness' if VMS now supports that).v   - bill   ------------------------------  # Date: Wed, 01 May 2002 22:48:55 GMT/# From: "Dan" <io_crater@hotmail.com>s. Subject: Re: Running CSWS 1.2 on Alpha VMS 7.29 Message-ID: <rh_z8.4182$uE2.276765@news2.calgary.shaw.ca>3  D I installed CSWS 1.2 on a VMS 7.2 hobbyist system. No changes to theI downloaded kit were required.  I had been running the beta 1.2 and it wasu/ nicely removed during the released 1.2 install.:  @ I have also installed without modifications CSWS_PHP T1.0, V1.0,; CSWS_PHP10_UPDATE and CSWB T1.0 on the same VMS 7.2 system.i  G All have run fine with the exception of CSWB T1.0 (the Mozilla browser)VK which has died a couple of times. But A) it is beta and; B) I am not at theuA requisite OS release, so I shouldn't be complaining and I am not!t  J I haven't put any kind of a load on this system but any web scripts I have; run, particularly PHP, have performed better than expected.e  J As Rick Barry mentions, VMS 7.2-1 is the recommended/supported version forE these products so I wouldn't rush to put this on a VMS 7.2 production5I system. But you probably have a hobbyist VMS system so you can try thingsp> and experiment, here is another opportunity. Indulge yourself.  & As always, YMMV and make good backups!   Dan Henigman    6 "Rick Barry" <barry@star.zko.dec.com> wrote in message2 news:XTQz8.4$lS1.175237@cacnews.cac.cpqcorp.net...L > You may be able to get it working, but not guranteed. Even with 7.2-1 it'sD > helpful to have the latest ECO installed for the most up-to-date C run-time
 > library. >rI > But the CSWS installation requires 7.2-1 as a minimum, so you'd need tohH > unpackage the PCSI kit, change the software requirement statement, and5 > repackage. (No, that's not a supported operation :)  >aI > You're really better off going to 7.2-1, if you can, to avoid problems.  >p > Rick Barry* > Compaq Secure Web Server Deveopment Team  > OpenVMS Systems Software Group > Compaq Computer CorporationY > Nashua, NH > I > "Simon Clubley" <clubley@remove_me.eisner.decus.org-Earth.UFP> wrote in 7 > message news:9lFRb$IHKYcg@eisner.encompasserve.org...-J > > The installation guide for the latest version of Apache (IE: CSWS 1.2)I > > states that at least VMS 7.2-1 is required. Can it be made to work on-. > > VMS 7.2 (the version on the hobbyist CD) ? > >- > > Thanks for any information,  > >a
 > > Simon. > >eK > > PS: In order to head off what is currently a standard response to these E > > types of postings, I would like to declare in advance that I havem > preciselyuF > > _zero_ interest in running Purveyor, nor do I have any interest in
 > debatingK > > the merits of that webserver versus the rest of the VMS webservers. :-)t > >d > > --? > > Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFPn/ > > Microsoft: The Lada of the computing world.  >R >i   ------------------------------  $ Date: Wed, 1 May 2002 20:17:25 +0100* From: Roy Brown <roy@acanthus.demon.co.uk>0 Subject: Re: SKC Morphs Again... We're Now SKHPC3 Message-ID: <vv6uNcSF9D08Ew+C@acanthus.demon.co.uk>t  E In message <L6Tz8.60193$%s3.23734634@typhoon.ne.ipsvc.net>, Terry C. m' Shannon <terryshannon@attbi.com> writes J >Another year, another name change. We at Shannon Knows DEC, Shannon KnowsH >Distributed Enterprise Computing, Shannon Knows Compaq, and now ShannonK >Knows HPC are getting used to the good old name game. And we hope that you H >Constant Readers will take the latest name change in stride. Here's theM >deal: Shannon Knows Compaq has withstood the rigors of two name changes pluseF >the economic angst of the thermonuclear winter incited by a wholesaleI >dot-com bombing. Acting on the news yesterday that the Delaware Chancery L >Court has given Hewlett-Packard's acquisition of Compaq a go-ahead, SKC hasM >changed its name to Shannon Knows High Performance Computing. HP, of course, @ >can be construed as High Performance or Hewlett-Packard, which,G >post-acquisition, will be Numero Uno in the High Performance ComputingpJ >arena. In the interest of brevity-plus a desire to coin a new five-letterI >acronym-we'll now operate under the SKHPC name. Extended "dance version"cM >five-letter acronym aside, we'll continue to provide the same coverage we'veoK >been dishing out for the last nine years, plus even more. And for those ofiJ >you who wonder why we didn't opt for Shannon Knows HPS, it turns out thatK >HPS is the acronym for Hewlett Packard Services! Thanks to a senior Compaq.5 >manager for pointing out this potential gaffe to us!w  @ Please excuse my confusion, but don't you have to 'Learn About'  something before you 'Know' it?o  F As you weren't, to my knowledge, 'Shannon Knows HP' before yesterday, : how has the mere fact of the merger equipped you so to be?  F Or should it be 'Shannon Knows That Bit of HewCom Paqard (Or Whatever H They Are Going To Call Themselves) Which Used To Be DEC, And Is Rapidly - Trying To Get Up To Speed On the Rest Of It'?g  G Anyway, if they do think up a new name (the last bit of HP to be hived tI off was named after an anagram of 'Genital'), you'll only have to change e it yet again :-(  D PS - you might want to add comp.sys.hp.hpux to your newsgroup list. C Seems a shame to leave them out, even if it is a minority interest   OS.....h -- mH Roy Brown        'Have nothing in your houses that you do not know to beE Kelmscott Ltd     useful, or believe to be beautiful'  William Morrise   ------------------------------  $ Date: Wed, 1 May 2002 16:43:46 -0400  From: norm.raphael@jamesbury.com0 Subject: Re: SKC Morphs Again... We're Now SKHPC4 Message-ID: <C2256BAC.0070E0EA.00@jklh22.valmet.com>  H Well, Roy, Terry doesn't need me to defend him - he can very well defend himself,P but there are things I, myself, know that I do not advertise that I know or tell everyoneO that I know, but I still know them, and when it is appropriate I may then claims
 truthfullyL to know them, so Shannon may very well know HP and know it well and have hadN continuing knowledge of HP for some time, but have chosen not to tell you that untileP now, so you should not be 'confused', you should rather be 'embarrassed.'  Let's9 see what he knows before we castigate him for his claims.n -Normr        2 roy@acanthus.demon.co.uk on 05/01/2002 03:17:25 PM  * Please respond to roy@acanthus.demon.co.uk   To:   Info-VAX@mvb.saic.comm cc:h1 Subject:  Re: SKC Morphs Again... We're Now SKHPCo      D In message <L6Tz8.60193$%s3.23734634@typhoon.ne.ipsvc.net>, Terry C.' Shannon <terryshannon@attbi.com> writes J >Another year, another name change. We at Shannon Knows DEC, Shannon KnowsH >Distributed Enterprise Computing, Shannon Knows Compaq, and now ShannonK >Knows HPC are getting used to the good old name game. And we hope that youeH >Constant Readers will take the latest name change in stride. Here's theM >deal: Shannon Knows Compaq has withstood the rigors of two name changes plusoF >the economic angst of the thermonuclear winter incited by a wholesaleI >dot-com bombing. Acting on the news yesterday that the Delaware Chancery:L >Court has given Hewlett-Packard's acquisition of Compaq a go-ahead, SKC hasM >changed its name to Shannon Knows High Performance Computing. HP, of course,n@ >can be construed as High Performance or Hewlett-Packard, which,G >post-acquisition, will be Numero Uno in the High Performance ComputingCJ >arena. In the interest of brevity-plus a desire to coin a new five-letterI >acronym-we'll now operate under the SKHPC name. Extended "dance version"rM >five-letter acronym aside, we'll continue to provide the same coverage we'vehK >been dishing out for the last nine years, plus even more. And for those of2J >you who wonder why we didn't opt for Shannon Knows HPS, it turns out thatK >HPS is the acronym for Hewlett Packard Services! Thanks to a senior Compaqa5 >manager for pointing out this potential gaffe to us!@  ? Please excuse my confusion, but don't you have to 'Learn About'1 something before you 'Know' it?a  E As you weren't, to my knowledge, 'Shannon Knows HP' before yesterday,n: how has the mere fact of the merger equipped you so to be?  E Or should it be 'Shannon Knows That Bit of HewCom Paqard (Or WhateverMG They Are Going To Call Themselves) Which Used To Be DEC, And Is Rapidly - Trying To Get Up To Speed On the Rest Of It'?V  F Anyway, if they do think up a new name (the last bit of HP to be hivedH off was named after an anagram of 'Genital'), you'll only have to change it yet again :-(  C PS - you might want to add comp.sys.hp.hpux to your newsgroup list.eB Seems a shame to leave them out, even if it is a minority interest OS.....i --H Roy Brown        'Have nothing in your houses that you do not know to beE Kelmscott Ltd     useful, or believe to be beautiful'  William Morrise   ------------------------------  # Date: Wed, 01 May 2002 17:17:16 GMTU1 From: "Terry C. Shannon" <terryshannon@attbi.com>C0 Subject: Re: SKC Morphs Again... We're Now SKHPC; Message-ID: <wqVz8.60342$%s3.23812479@typhoon.ne.ipsvc.net>h  + <david20@alpha2.mdx.ac.uk> wrote in message % news:aap647$k1k$1@aquila.mdx.ac.uk...cG > In article <L6Tz8.60193$%s3.23734634@typhoon.ne.ipsvc.net>, "Terry C.i) Shannon" <terryshannon@attbi.com> writes:h > .y > .u > .d; > > Acting on the news yesterday that the Delaware ChancerydJ > >Court has given Hewlett-Packard's acquisition of Compaq a go-ahead, SKC haseG > >changed its name to Shannon Knows High Performance Computing. HP, of: course,hB > >can be construed as High Performance or Hewlett-Packard, which,I > >post-acquisition, will be Numero Uno in the High Performance Computing 	 > >arena.a >cJ > I doubt they'll be  "Numero Uno in the High Performance Computing arena"J > if they persist in their plans to force all their customers onto Itanic.  J Not being an Overpaid Armani Analyst, I can't tell those folks what to do! ;-}t   ------------------------------  # Date: Wed, 01 May 2002 17:16:29 GMTo1 From: "Terry C. Shannon" <terryshannon@attbi.com>l0 Subject: Re: SKC Morphs Again... We're Now SKHPC; Message-ID: <NpVz8.60341$%s3.23812221@typhoon.ne.ipsvc.net>   - <norm.raphael@jamesbury.com> wrote in messagee. news:C2256BAC.005A940E.00@jklh22.valmet.com... >s >a3 > Interesting Sig file in the light of the message. 7 > When exactly are you going to complete this morph...?P > ->4 > Web (info on SKC):  www.openvms.org, www.tru64.org > <-  K I continue to host SKWhatever moldy oldies at the aforementioned Ken Farmeri$ sites. This may change soon, though!   ------------------------------  # Date: Wed, 01 May 2002 17:15:25 GMTm1 From: "Terry C. Shannon" <terryshannon@attbi.com>c0 Subject: Re: SKC Morphs Again... We're Now SKHPC; Message-ID: <NoVz8.60340$%s3.23811689@typhoon.ne.ipsvc.net>.  8 "Rob Young" <young_r@encompasserve.org> wrote in message- news:vVZS78ztr3Xq@eisner.encompasserve.org... G > In article <L6Tz8.60193$%s3.23734634@typhoon.ne.ipsvc.net>, "Terry C.O) Shannon" <terryshannon@attbi.com> writes:0 >0F > > In the interest of brevity-plus a desire to coin a new five-letterL > > acronym-we'll now operate under the SKHPC name. Extended "dance version"J > > five-letter acronym aside, we'll continue to provide the same coverage we've = > > been dishing out for the last nine years, plus even more.- >-E > Oh boy!  Does this mean you will soon be coming up your own versionnE > of the "five-note siren song of the Intel Xylophone Orchestra" ????- >l  D No, but I gave serious thought to hiring some 13-year old kid with aJ backward baseball cap (actually, sans cap, as the backward cap reduces theK IQ by 23 points) to come up with a 10 or 11-note "Death March" tune for useiI as the IPF jingle. Twice the number of bits requires an arpeggio at leastw, twice as long as the current Intel standard.   ------------------------------  % Date: Wed, 01 May 2002 14:14:57 -0700   From: Jon <jsmyth69@hotmail.com>0 Subject: Re: SKC Morphs Again... We're Now SKHPC8 Message-ID: <glm0dusdvegv9kbiskjd71tedpc3ickkul@4ax.com>  = Just to save time, Can't you just call it "Shannon knows... "P      2 "Terry C. Shannon" <terryshannon@attbi.com> wrote:  J >Another year, another name change. We at Shannon Knows DEC, Shannon KnowsH >Distributed Enterprise Computing, Shannon Knows Compaq, and now ShannonK >Knows HPC are getting used to the good old name game. And we hope that youlH >Constant Readers will take the latest name change in stride. Here's theM >deal: Shannon Knows Compaq has withstood the rigors of two name changes plus?F >the economic angst of the thermonuclear winter incited by a wholesaleI >dot-com bombing. Acting on the news yesterday that the Delaware Chancery L >Court has given Hewlett-Packard's acquisition of Compaq a go-ahead, SKC hasM >changed its name to Shannon Knows High Performance Computing. HP, of course,o@ >can be construed as High Performance or Hewlett-Packard, which,G >post-acquisition, will be Numero Uno in the High Performance ComputingqJ >arena. In the interest of brevity-plus a desire to coin a new five-letterI >acronym-we'll now operate under the SKHPC name. Extended "dance version"NM >five-letter acronym aside, we'll continue to provide the same coverage we'vePK >been dishing out for the last nine years, plus even more. And for those ofuJ >you who wonder why we didn't opt for Shannon Knows HPS, it turns out thatK >HPS is the acronym for Hewlett Packard Services! Thanks to a senior Compaqg5 >manager for pointing out this potential gaffe to us!t   ------------------------------  # Date: Thu, 02 May 2002 01:22:47 GMTt' From: ben_myers@charter.net (Ben Myers)n0 Subject: Re: SKC Morphs Again... We're Now SKHPC0 Message-ID: <3cd0937b.38291605@news.charter.net>  K "Shannon knows best"?  Reminds me of a TV show of days gone by... Ben Myers   E On Wed, 01 May 2002 14:14:57 -0700, Jon <jsmyth69@hotmail.com> wrote:   > >Just to save time, Can't you just call it "Shannon knows... " >- >- >-3 >"Terry C. Shannon" <terryshannon@attbi.com> wrote:o >aK >>Another year, another name change. We at Shannon Knows DEC, Shannon Knows0I >>Distributed Enterprise Computing, Shannon Knows Compaq, and now Shannon:L >>Knows HPC are getting used to the good old name game. And we hope that youI >>Constant Readers will take the latest name change in stride. Here's theIN >>deal: Shannon Knows Compaq has withstood the rigors of two name changes plusG >>the economic angst of the thermonuclear winter incited by a wholesale J >>dot-com bombing. Acting on the news yesterday that the Delaware ChanceryM >>Court has given Hewlett-Packard's acquisition of Compaq a go-ahead, SKC hasaN >>changed its name to Shannon Knows High Performance Computing. HP, of course,A >>can be construed as High Performance or Hewlett-Packard, which,FH >>post-acquisition, will be Numero Uno in the High Performance ComputingK >>arena. In the interest of brevity-plus a desire to coin a new five-letterxJ >>acronym-we'll now operate under the SKHPC name. Extended "dance version"N >>five-letter acronym aside, we'll continue to provide the same coverage we'veL >>been dishing out for the last nine years, plus even more. And for those ofK >>you who wonder why we didn't opt for Shannon Knows HPS, it turns out thatSL >>HPS is the acronym for Hewlett Packard Services! Thanks to a senior Compaq6 >>manager for pointing out this potential gaffe to us! >e   ------------------------------  % Date: Thu, 02 May 2002 13:33:25 +0930h/ From: Mark Daniel <Mark.Daniel@wasd.vsm.com.au>n Subject: Re: TCPIP$C_SHARE/ Message-ID: <3CD0BA8D.CDF68324@wasd.vsm.com.au>h  C I recently started to use this approach to share a listening socketEH between processes.  The principle is much the same.  There are currentlyH some problems with this under load with Compaq TCP/IP Services and I putH together some code to demonstrate this issue (an ECO should be availableH this quarter apparently).  You can find this code and it's use of _SHARE at  #   http://wasd.vsm.com.au/wasd/mgd.cB  @ The currently implementation using this approach can be found at  3   https://wasd.vsm.com.au/ht_root/src/httpd80/net.cn  G look for functions NetCreateSocket(), NetGetBgDevice(), NetAccept() andnF NetAcceptAst().  Although this is not precisely the same functionalityC as what you want, it does illustrate use of the _SHARE behaviour tohE allow multiple processes to use the same BG: device and may provide a  few more clues.-  
 Joe wrote: >  > OpenVMS 7.1-1H20 > C V6.2-003 > TCPIP 5.0A - ECO 3 > D > What exactly does the IO$_SETMODE option TCPIP$C_SHARE do? Maybe I$ > should be asking how it is used... > C > Basic idea: a server will be listening on a port for connections.eC > "Clients" connect to the port and then send information on one ofnB > several possible "services" that they want to request. After theD > server listening on the port has this information it decides if itE > wants to pass the request off to a worker capable of processing the H > request (if not it drops the connection). The docs and what I've found- > on the net seem to indicate this is doable.b > E > The server specifies TCPIP$C_SHARE on the IO$_ACCESS | IO$M_ACCEPT.aE > The worker does the same specifying P1/P3/P5 (with no joy) with its @ > IO$_SETMODE call when it attepts to bind to the resulting port( > (SS$_DUPLNAM is returned in the IOSB). > C > The only way I can get the "worker" to "connect" to the resultingsF > socket is to enable SHARE, use $GETDVI to get the underlying BG unit? > number, call $ASSIGN and the use $QIO... I saw something that H > indicated this was kind of a bad thing to do (something in relation toD > unit numbers north of 9999) although at the moment I can't seem to > find that reference. > E > Any ideas on what I'm doing wrong here or code samples appreciated.a >  > As always TIA, > Joet   ------------------------------   Date: 01 May 2002 21:50:01 GMT- From: "Jim Strehlow" <jimSnoSpam@data911.com> . Subject: Re: virtual i/o cache v7.2-1 and v7.30 Message-ID: <aapnu9$7ro@dispatch.concentric.net>   Thanks for the warning.e I will change to VCC_FLAGS = 1   $mcr sysgen show vcc_flagsG Parameter Name           Current    Default     Min.      Max.     Unit. DynamicoL --------------           -------    -------    -------   -------   ----  ---2 VCC_FLAGS                       2          2   ...  
 Thank you.   Jim Strehlow, Data911 SystemsS  4 "Carl Perkins" <carl@gerg.tamu.edu> wrote in message' news:30APR200222472931@gerg.tamu.edu...c3 > "Jim Strehlow" <jimSnoSpam@data911.com> writes...gC > }What is the best source of reading material for me to read up on D > }the new Extended File Cache in v7.3 and how the virtual i/o cache > }is affected?  > }o1 > }Jim Strehlow, OpenVMS Systems Manager, Data911  > }jimS@data911.com  > }Alameda, CA, USAt > }d4 > }$show memory/all/full      !on OpenVMS Alpha v7.3C > }              System Memory Resources on 29-APR-2002 09:14:46.64m > }rC > }Physical Memory Usage (pages):     Total        Free      In Usei ModifiedC > }  Main Memory (1024.00Mb)         131072       25496       97991  7585 > }eE > }Extended File Cache  (Time of last reset: 17-APR-2002 07:33:33.29)uB > }    Allocated (Mbytes)          474.65    Maximum size (Mbytes)	 > }512.00- >-K > The system this is running on is not using the VIOC, it is using the XFC.r6 > The are two completely different file cache systems. >i4 > *** You should IMMEDIATELY stop using the XFC. *** >h; > The XFC is buggy. Using it can result in data corruption.o> > DO NOT USE IT. Switch to the VIOC (and then it may be a good> > idea to check your data to make sure it is good). You really@ > should not wait until normally scheduled down time. Do it now. >CB > Which disk cache type you use is controlled by a sytem parameterG > (I don't have a 7.3 system to look it up on - it may be the VCC_FLAGSn@ > parameter). You should set this in MODPARAMS.DAT (and probablyC > increase the max size of the VIOC to a reasonable value while youfC > are in there - a factor of 10 increase over the default would notcE > be a bad conservative guess with the amount of memory you have, andnE > you might go higher if you want) and do an AUTOGEN, preferably withiB > REBOOT as the final stage so as to get rid of the XFC as quickly > as possible. > 
 > --- Carl   ------------------------------   Date: 1 May 2002 12:27:57 -0700 / From: chinachowchow@mailcity.com (Rick Nickles)n1 Subject: Re: VMS Bigots Unite To Form New Companyw= Message-ID: <ac4e3b24.0205011127.2faa8b08@posting.google.com>E  B I surely agree that Compaq needs to think about small businesses.  This is = a market that they aren't even looking at really right now.  e  D The idea is that if HPQ doesn't care about VMS, then let's see it go? to somebody who does care and will do what it takes to push theo product and make itvC a part of the mainstream.  If they really decide that they do care,n= then let's make it a part of the mainstream by making it more E affordable and available to more people.   Let's put a nice gui on itnD and put it on PC's everywhere, make it an OS that blow's Microsoft's! socks off.  We can do that right?y   ------------------------------   Date: 1 May 2002 19:45:02 -0000a= From: Doc.Cypher <Use-Author-Supplied-Address-Header@[127.1]> 1 Subject: Re: VMS Bigots Unite To Form New Companye6 Message-ID: <20020501194502.14118.qmail@gacracker.org>  ? On 1 May 2002, chinachowchow@mailcity.com (Rick Nickles) wrote:aC >I surely agree that Compaq needs to think about small businesses.   >This is> >a market that they aren't even looking at really right now.   > E >The idea is that if HPQ doesn't care about VMS, then let's see it goh@ >to somebody who does care and will do what it takes to push the >product and make itD >a part of the mainstream.  If they really decide that they do care,> >then let's make it a part of the mainstream by making it moreF >affordable and available to more people.   Let's put a nice gui on itE >and put it on PC's everywhere, make it an OS that blow's Microsoft's " >socks off.  We can do that right?  F VMS already has "a nice GUI", and the problem with trying to put it onA "PC's everywhere" is that the hardware simply doesn't support it.   K FWIW I don't think there is any need to make compromises or changes to makesJ the OS a genuinely viable product, just a need to market it appropriately.     Doc. --  6 The bigger the humbug, the better people will like it.K ~ Phineas Taylor Barnum.                             https://vmsbox.cjb.netu   ------------------------------   Date: 1 May 2002 19:42:07 -0000g4 From: Doc.Cypher <Use-Author-Address-Header@[127.1]>1 Subject: Re: VMS Bigots Unite To Form New Companys6 Message-ID: <20020501194207.13975.qmail@gacracker.org>  @ On Wed, 01 May 2002, "Bill Todd" <billtodd@metrocast.net> wrote:K >"Doc.Cypher" <Use-Author-Supplied-Address-Header@[127.1]> wrote in messageh0 >news:20020501150338.4663.qmail@gacracker.org...B >> On Wed, 1 May 2002, WILLIAM WEBB <WWEBB1@email.usps.gov> wrote: >> > >> Doc:r >> > >> >re:  your last paragraph >> > >> >Please send address. >> >Cigar to be forthcoming. >>M >> Thanks, I'll pass on the cigar - the Belgian postal service would probablyn
 >> mangle it.e >>K >> It was just a less sensationalist rework of my "Free The OpenVMS 7" posts >> which can be found atE >> http://groups.google.com/groups?selm=FreeThe.OpenVMS_7@nowhere.nil  >iJ >Which (not to in any way detract from the above) was also very much alongI >the lines of the entry-level system suggestions we included in our groupoJ >letter to Curly two years ago.  And we know how well *that* got received.  K The fact that separate people, or groups of people, keep coming to the samemC conclusions regarding the targetted marketing of VMS certainly saysfI something. Perhaps anyone who comes to these conclusions within the wallseH of Compaq (and has been foolish enough to mention them) has been quickly disposed of.     Doc. --  6 The bigger the humbug, the better people will like it.K ~ Phineas Taylor Barnum.                             https://vmsbox.cjb.net    ------------------------------  % Date: Wed, 01 May 2002 17:53:39 -0400t- From: JF Mezei <jfmezei.spamnot@videotron.ca> 1 Subject: Re: VMS Bigots Unite To Form New Companys+ Message-ID: <3CD063E1.583D896@videotron.ca>o   Rick Nickles wrote:1 > C > I surely agree that Compaq needs to think about small businesses.h	 > This is = > a market that they aren't even looking at really right now.i  N Jesus Murphy, have you looked at all of Compaq's advertising ? It is all aimedJ at small business. Just because Compaq doesn't pitch VMS to anyone doesn'tM mean that they don't go after small business. They have plenty of wintel craptK to sell to small business. After all, small business can afford to go down,aL can afford to spend mega time fixing abnd patching microsoft faulty productsT etc and it is only the largest of the large businesses that really need reliability.   ------------------------------  # Date: Wed, 01 May 2002 23:17:07 GMT'( From: spam@devnull.com (Russell Wallace)1 Subject: Re: VMS Bigots Unite To Form New Companyt1 Message-ID: <3cd0751e.1155449644@news.eircom.net>-  , On Wed, 01 May 2002 17:53:39 -0400, JF Mezei% <jfmezei.spamnot@videotron.ca> wrote:s  O >Jesus Murphy, have you looked at all of Compaq's advertising ? It is all aimedwK >at small business. Just because Compaq doesn't pitch VMS to anyone doesn'twN >mean that they don't go after small business. They have plenty of wintel crapL >to sell to small business. After all, small business can afford to go down,M >can afford to spend mega time fixing abnd patching microsoft faulty productseU >etc and it is only the largest of the large businesses that really need reliability.,  C And in fact, for the individual and small business market, Compaq'st+ strategy is overwhelmingly the correct one.s  B The landscape is littered with the bones of companies who tried toF push proprietary desktop machines and refused to listen when customers? said no. People _don't want_ proprietary solutions. They want arA standard, so they can buy a computer, buy a program, and have the B latter run on the former. Who that standard is from doesn't reallyE matter; Microsoft happened to be the first (in 1990) to come out with C a marketable GUI-based operating system that would run on commoditynE hardware. Apple, Commodore, Atari, any number of companies could have-> done the same; they didn't, as a result Apple had a near-deathE experience and all the others went to the great stock exchange in the2 sky.  A For big business who have their own IT departments, write much of F their own software and pay a huge price for every hour their server isC down, it's different. In that market, reliability is more important  than standardization.l  B Compaq's mistake has been to take the strategy that served them soC well in the mass market (and it did serve them well, they got to be:D one of the biggest companies in the computer industry by being amongC the first to get the clue that people wanted PC compability without%C any ifs, ands or buts) and apply it to the high-end market where itr doesn't work so well.e  F That's why Compaq, rather than merging with HP, should have been split> in two - the strategies really require fundamentally different corporate cultures.r   Oh well.   -- t3 "Mercy to the guilty is treachery to the innocent."v! http://www.esatclear.ie/~rwallacer mail:rw(at)eircom(dot)netx   ------------------------------  # Date: Thu, 02 May 2002 01:38:28 GMTp1 From: "David J. Dachtera" <djesys.nospam@fsi.net>o1 Subject: Re: VMS Bigots Unite To Form New Company ' Message-ID: <3CD09B88.DD73D9FB@fsi.net>c   Charlie Hammond wrote: > ) > In article <3CCF4F4E.D7F77FC5@fsi.net>,y5 > "David J. Dachtera" <djesys.nospam@fsi.net> writes:t >  > >Charlie Hammond wrote:l > ..C > >> Please let us know where we can download your business plan...p > .cH > >Not sure why when everything you need has already been spelled out in, > >this thread and countless others like it. > I > Is there specifc, valid market research that shows higher total revenuea/ > could be achieved by making OpenVMS "cheap"?    G Ever heard of a little company in Redmond, Washington (U.S.) that sells: a GUI o.s. for Intel PCs?'   > Or giving it away?  * Ever heard of an outfit called, "Red Hat"?   -- t David J. Dachterat dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/h   ------------------------------  # Date: Thu, 02 May 2002 01:36:21 GMTr1 From: "David J. Dachtera" <djesys.nospam@fsi.net>n1 Subject: Re: VMS Bigots Unite To Form New Companye' Message-ID: <3CD09B06.1005BA2C@fsi.net>e   Robert Deininger wrote:n > = > In article <3CCF4F4E.D7F77FC5@fsi.net>, "David J. Dachtera"i  > <djesys.nospam@fsi.net> wrote: >  > >> [snip]eC > >> Please let us know where we can download your business plan...t > >>@ > >>     ...said Charlie, with tongue firmly planted in cheek... > >tH > >Discussions such as this frequently precipitate exactly that comment. > >dG > >I suppose you're looking for a multi-hundred page Word document withcI > >charts and graphs and biographies of high-powered executives sought bysA > >the Fortune 10 of the world and page after page of figures anda > >calculations or something.u > >eH > >Not sure why when everything you need has already been spelled out in, > >this thread and countless others like it. > >nJ > >For the benefit of those who've never been to business school (and most= > >of those who have), the business plan is extremely simple:  > >wF > >1. Provide wanted products and services at prices the customers can
 > >afford. > > 2 > >2. Sell them what they can't get anywhere else. > > 9 > >3. Sell them what no one else is willing to sell them.- > >-3 > >4. Remember these two rules of customer service:2& > >   I. The Customer is Always Right!/ > >  II. If the customer is wrong, see rule #1.e > >SJ > >5. Remember this precept of profit: if you can't satisfy the customer'sJ > >need, help them find someone who can! Next time they need help, they'll > >remember YOU! > >oG > >If there's anything there that you can't (or won't) understand, yourl3 > >efforts and dollars are best invested elsewhere.n > >t8 > >This is no different from any other business venture. > J > David, your comments on this topic include a lot of good ideas.  1-4 areH > right on the money, and little more than "common" sense.  (Why do theyJ > call it "common" sense, when it seems to be so rare?)  DigiPaq has often4 > lost sight of the customer's needs over the years. > J > But your 5th point is important also.  VMS has to make a profit for it'sF > owner, and since it's not trendy, it's expected to help prop up more@ > faddish, less profitable enterprises.  (I think this is calledK > "strategy".)  So the reality is that VMS has a limited amount of money toa > spend on all its projects.  E Nothing in that list requires additional outlays, though perhaps moree2 effective use of the available dollars is implied.   > [snip]J > I think there are folks in VMS-land who are genuinely trying to make VMS@ > grow.  But they need ideas that are either cheap to implement,  F What does it cost to produce additional media kits? ...process orders?E ...ship product? As long as income offsets costs and leaves a profit,  where's the problem?  
 > or at leasttK > have a pretty clear path from expenditure to added revenue.  "Port VMS to . > everything" was not a realistic suggestion.   > Nor was it mine. My bad for including it in the text I quoted.   > Much of the effort would not > add revenue.  E Well, that's a matter of considerable debate. Let's not go there just, now.  L > When folks talk about a "business plan", they don't mean a bunch of glossyJ > powerpoint fluff.  But a grand scheme that fails to yield an expectationI > of some revenue is destined to get little attention from the people who  > make decisions.n  F What part of the five steps I listed "fails to yield an expectation of some revenue"?  J > If anyone has proposals to boost VMS in specific ways that are likely toK > lead to additional $$$, he should start a serious discussion with Compaq.n  G That's been tried. They're not interested. Perhaps TCFKAHP (the companyrF formerly known as HP) will be more receptive. We should give them someF time to settle in once the dust settles from the 1200 staff cuts, then- consider a new strategy for approaching them.e  L > If a VMS enhancement would help you sell more VMS stuff to your customers,L > or make VMS more useful to your own organization, you should make sure VMSJ > management knows about it.  (I don't claim Compaq makes this easy.)  "WeL > would install xx more systems if you gave us feature yy" IS of interest to > these folks. h  F For "xx", substitute 500,000 (that would double VMS's estimated market? penetration), and for "feature yy", substitute "affordability".t  F "But David, doesn't that significantly reduce the margin and therefore profit?"   Margin? Yes. Profit? No. v   "How can that be?"  H Ever heard of a support contract? ...training? That's where the money isG nowadays - just ask Red Hat, Caldera, and others. Sell the systems, andoE users will want support and training. THAT is where the money is now.w9 But, to get it, ya gotta sacrifice margin on the product.e  : > I suspect incremental enhancements are more likely to goE > forward in the present climate, since VMS has enough major projectsnJ > underway these days.  If you can't figure out who to contact, find a VMSL > ambassador, or contact Mark Gorham directly.  I expect reasonable, seriousB > proposals would at least get routed to the appropriate folks for > consideration.  H With the state VMS is in, and with the corporate carnage we are about to; witness, "consideration" is much too little, much too late.l  : Realistically, of course, it's probably all we can expect.   -- e David J. Dachterae dba DJE Systemsg http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/r   ------------------------------  # Date: Wed, 01 May 2002 20:09:54 GMTo? From: Jim.Johnson@software-exploration.nospam.com (Jim Johnson)o Subject: Re: VMS SCAN product 0 Message-ID: <3cd04b6b.49991984@news.demon.co.uk>  B No offence John, but really ---  the last thing we need is a MACRO compiler with AI...9   :) Jim.  F On Wed, 01 May 2002 16:17:05 GMT, John Reagan <john.reagan@compaq.com> wrote:   >Larry Kilgallen wrote:t >, >> n >> Try the command:u >> v >> 	HELP LINK/VAXt >  >nC >Has anybody actually used this?  You would still need all the VAX  G >shareables, VAX object libraries (STARLET.OLB), etc. to link against. vI >You don't want Alpha GSMATCH values to be in your VAX .EXE (even if you g >just turn around and VEST it).e >sG >I don't think documenting the "cross-linker" was a good idea.  It has hD >limited value.  I can't imagine this being carried over to Itanium. >a >--  >John Reagan( >Compaq Pascal/{A|I}MACRO Project Leader >w   Jim Johnsono Software Exploration, Ltd.) (remove '.nospam' from the reply address)o   ------------------------------  # Date: Wed, 01 May 2002 20:23:15 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) Subject: Re: VMS SCAN products9 Message-ID: <T8Yz8.25$J%1.506980@cacnews.cac.cpqcorp.net>   i In article <338eb8f7.0204300724.3d1ce16b@posting.google.com>, GARY.MORIN@EMERGIS.COM (Gary Morin) writes: h :"Lock Horsburgh" <lock@lohmacs.fsnet.co.uk> wrote in message news:<aalnvg$7s7$1@news7.svr.pol.co.uk>...M :> Once upon a time we had a DEC product called SCAN, which was used to parse0H :> input text and generate different outputs - like code generation, and) :> language translations from Basic to C.e :> p+ :> We understand this product is long dead.c :> hM :> Does anyone remember the package, and does anyone have any recommendationsJJ :> for other tools to do this kind of thing, whether on VMS or UNIX or PC? :> . :> > :> Lock. :sG :The SCAN programing language has been put on the VMS Freeware CD so it C :is available to anybody for just the cost of the CD (or download).e :a5 :SCAN was very cool in its day and still usefull now.a     VAX SCAN is dead.t  A   Please take the time to review the previous discussions of thisc<   topic, using the INFO-VAX Archives or the Google Archives.  2   Convert to Perl or Python or Ruby, or otherwise.  6   Perl can be embedded.  (Donno about Python or Ruby.)  D   Time to add this topic to the OpenVMS FAQ.  I will add a synopsis C   of the VAX SCAN discussions into the next edition of the FAQ, as .E   this question has certainly reached a frequency which warrants its 0   inclusion into the FAQ.v      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: Thu, 02 May 2002 01:55:18 GMT 1 From: "David J. Dachtera" <djesys.nospam@fsi.net>c Subject: Re: VMS SCAN producte' Message-ID: <3CD09F7A.794D402D@fsi.net>e   David Froble wrote:u >  > ualski wrote:  > A > > My favorite is PCCTS (Perdue Compiler Construction Tool Set).e5 > > I didn't check this link but it might still work:p* > > http://www.ece.purdue.edu/~hankd/PCCTS > >r > > Hope this helps. > >s > > -- Aaron Sliwinski > >e > > Lock Horsburgh wrote:  > >nN > >>Once upon a time we had a DEC product called SCAN, which was used to parseI > >>input text and generate different outputs - like code generation, ande* > >>language translations from Basic to C. > L > This product would be more helpful if the translation was from C to Basic. > , > Let the religous language wars begin.  :-)  9 Actually, I think both would be useful. BASIC is at leasto) comprehensible, but C is more ubiquitous.o  G Then again, C to MACRO32 would be well received in the OpenVMS freewareI9 arena, I think. Not optimal, but perhaps at least usable.e   -- i David J. Dachtera: dba DJE Systemsi http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/m   ------------------------------   Date: 1 May 2002 21:06:39 -0500'- From: Kilgallen@SpamCop.net (Larry Kilgallen)e Subject: Re: VMS SCAN productt3 Message-ID: <mXNGL3EVSSvB@eisner.encompasserve.org>t  r In article <3cd04b6b.49991984@news.demon.co.uk>, Jim.Johnson@software-exploration.nospam.com (Jim Johnson) writes:D > No offence John, but really ---  the last thing we need is a MACRO > compiler with AI...r >  > :) > Jim.  ; Ah, so you want them to rewrite VMS rather than port it :-)    ------------------------------  $ Date: Thu, 2 May 2002 07:45:47 +02004 From: "Bernard Schluep" <bernard.schluep@azisoft.ch> Subject: VMSTARe* Message-ID: <aaqkb8$h6d$1@rex.ip-plus.net>  ? Periodically, I receive a TAR file generated on an Unix system.h+ It contains a text file and some TIF files.aL When I try to decompress it with VMSTAR 3.4-1, I receive only the text file, the others are not extracted.t  J If I open this TAR on a PC with PowerArchiver and I save it as ZIP file, IL could extract all files on OpenVMS with unzip, but this way is not clean for me.i  , Did somebody have the same kind of problem ?. Do exist another "untar" program for OpenVMS ?   Thanks for your help Regards, Bernarde   ------------------------------  # Date: Thu, 02 May 2002 02:04:32 GMT 1 From: "David J. Dachtera" <djesys.nospam@fsi.net>r$ Subject: Re: Whining about HPS Times' Message-ID: <3CD0A1A4.ECA54544@fsi.net>a   Jim Agnew wrote: >  > "David J. Dachtera" wrote: > > 4 > > John@helferlein.net, Jones@helferlein.net wrote: > C > > > I got mine.  Too bad you didn't get yours.  Maybe bad karhma?  > >h; > > Maybe folks should stop whining about people whining...h > >l >  > Qua'Pla!!!!!!!!  Amen, Bro!!  H He'll likely post again whining about me whining about him whining about) people whining about (fill in the blank).   3 ...which might also be classified as "whining", no?i  ) WTF ever happened to free speech, anyway?r   -- ? David J. Dachtera  dba DJE Systemst http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/i   ------------------------------  % Date: Wed, 01 May 2002 15:20:27 -0700A' From: David Mathog <mathog@caltech.edu>i$ Subject: You can't beat the price...+ Message-ID: <3CD06A2B.61A960CA@caltech.edu>t  ; We have some old DEC equipment and a pile of 8mm media that . we're giving away.  If you want any of it see:  0   http://saf.bio.caltech.edu/www/decmachines.txt   Regards,   David Mathog mathog@caltech.edu   ------------------------------  # Date: Thu, 02 May 2002 01:59:33 GMTm1 From: "David J. Dachtera" <djesys.nospam@fsi.net>m? Subject: Re: ZIP strangeness (search list as part of file spec) ' Message-ID: <3CD0A078.99DB4F95@fsi.net>(   "David J. Dachtera" wrote: >  > Phillip Helbig wrote:  > >f# > > ZIP zip-file name zip-file list" > >  > > Used it for years. > >iL > > Assume that the zip-file name (name of the file zip creates) is given asL > > LOGICAL:ZIP.FILE, where LOGICAL is a search list.  (The list of files toI > > be zipped in my test case was also in (the same) search list; in thiseH > > case as expected it picks up files from the directories in the orderI > > defined by the search list).  ZIP.FILE ends up in the SECOND, not thet> > > FIRST, directory specified by the search list.  This seemsL > > counter-intuitive (i.e. different than what happens normally with search > > lists).d > >  > > Why? > F > When I tested this, it always goes to the last element of the searchF > list. That said, I didn't test it with a search list which points to > non-existant paths.t   O.K. Here's the test log...I   $ sh log user$exeg.    "USER$EXE" = "USER$IMG:" (LNM$JOB_85585A00) 	= "USER$COM:" 	= "SYS$SPECIFIC:[SYSEXE]" 	= "SYS$COMMON:[SYSEXE]": 1  "USER$IMG" = "USER$ROOT:[EXE.ALPHA]" (LNM$JOB_85585A00)4 1  "USER$COM" = "USER$ROOT:[EXE]" (LNM$JOB_85585A00)$ $ zip/level=9/vms user$exe:ts t*.com   adding: TEST.COM  (deflated 20%)p   adding: TIME_DIFF.COMy  (deflated 60%)  $ dir user$exe:ts.zip-   Directory SYS$COMMON:[SYSEXE]:  ? TS.ZIP;1                    5/18         1-MAY-2002 09:26:37.45:   Total of 1 file, 5/18 blocks.3 $ del/lo user$exe:ts.zip;iA %DELETE-I-FILDEL, SYS$COMMON:[SYSEXE]TS.ZIP;1 deleted (18 blocks)o $! $ sh log all_disks5    "ALL_DISKS" = "SYS$SYSDEVICE:" (LNM$PROCESS_TABLE)  	= "DISK1:"  	= "DISK51:" 	= "DISK52:" 	= "DISK53:" 	= "DISK54:" 	= "DISK55:" 	= "DISK56:" 	= "DISK57:" 	= "DISK58:" 	= "DISK59:"
 	= "$1$DKA0:"  	= "DISK4:"  	= "DISK14:" 	= "DISK15:" 	= "DISK16:" 	= "DISK17:" 	= "DISK18:" 	= "DISK19:"/ 1  "SYS$SYSDEVICE" = "DSA0:" (LNM$SYSTEM_TABLE)9' 1  "DISK1" = "DSA1:" (LNM$SYSTEM_TABLE)i) 1  "DISK51" = "DSA51:" (LNM$SYSTEM_TABLE)s) 1  "DISK52" = "DSA52:" (LNM$SYSTEM_TABLE) ) 1  "DISK53" = "DSA53:" (LNM$SYSTEM_TABLE)c) 1  "DISK54" = "DSA54:" (LNM$SYSTEM_TABLE) ) 1  "DISK55" = "DSA55:" (LNM$SYSTEM_TABLE)V) 1  "DISK56" = "DSA56:" (LNM$SYSTEM_TABLE)1) 1  "DISK57" = "DSA57:" (LNM$SYSTEM_TABLE)w) 1  "DISK58" = "DSA58:" (LNM$SYSTEM_TABLE)3) 1  "DISK59" = "DSA59:" (LNM$SYSTEM_TABLE)o* 1  "DISK4" = "$1$DUA4:" (LNM$SYSTEM_TABLE), 1  "DISK14" = "$1$DUA14:" (LNM$SYSTEM_TABLE), 1  "DISK15" = "$1$DUA15:" (LNM$SYSTEM_TABLE), 1  "DISK16" = "$1$DUA16:" (LNM$SYSTEM_TABLE), 1  "DISK17" = "$1$DUA17:" (LNM$SYSTEM_TABLE), 1  "DISK18" = "$1$DUA18:" (LNM$SYSTEM_TABLE), 1  "DISK19" = "$1$DUA19:" (LNM$SYSTEM_TABLE) $!% $! The following path spec is invalidm& $! (lacks a directory name). Note that $! ZIP fails quietly.r% $ zip/level=9/vms all_disks:ts t*.coml   adding: TEST.COM  (deflated 20%)d   adding: TIME_DIFF.COMh  (deflated 60%)  $ show symbol $status    $STATUS == "%X00000001"p $ dir all_disks:ts.zip> %DIRECT-E-OPENIN, error opening DISK19:[WORK]TS.ZIP;* as input -RMS-E-DNF, directory not found)" -SYSTEM-W-NOSUCHFILE, no such file $ del/lo all_disks:ts.zip;> %DELETE-W-SEARCHFAIL, error searching for DISK19:[WORK]TS.ZIP; -RMS-E-DNF, directory not foundt" -SYSTEM-W-NOSUCHFILE, no such file
 $ dir z*.;   Directory USER$ROOT:[WORK]  ? ZI517538.;1                 5/9          1-MAY-2002 09:26:37.88m   Total of 1 file, 5/9 blocks.
 $ del/lo z*.; @ %DELETE-I-FILDEL, USER$ROOT:[WORK]ZI517538.;1 deleted (9 blocks) $!- $ zip/level=9/vms all_disks:[000000]ts t*.como updating: TEST.COM  (deflated 20%)i updating: TIME_DIFF.COM)  (deflated 60%)N $ dir all_disks:[000000]ts.zip   Directory DISK19:[000000]r  ? TS.ZIP;1                    5/9          1-MAY-2002 09:26:38.59-   Total of 1 file, 5/9 blocks." $ del/lo all_disks:[000000]ts.zip;< %DELETE-I-FILDEL, DISK19:[000000]TS.ZIP;1 deleted (9 blocks) $! $ exit  > You can tell by the time stamps - I ran that on a QUICK Alpha!   -- g David J. Dachteray dba DJE Systemsq http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/r   ------------------------------  $ Date: Wed, 1 May 2002 15:08:14 -04000 From: "Syltrem" <syltremspammenot@videotron.com> Subject: ZTDRIVER.EXEh5 Message-ID: <W0Xz8.10867$a04.49004@tor-nn1.netcom.ca>   " Anyone knows what ZTDRIVER.EXE is?  K I have a client that says he gets a "file not found" on this one when doingd SYSGEN> AUTOCONFIGURE ALL   L We're at a minimum boot right now. All the devices we need configure ok, and2 we are in the process of restoring a damaged disk.   Thanks   --   Syltrem-I http://pages.infinit.net/syltrem (OpenVMS related web site - en franais)S> To reply to myself directly, remove .spammenot from my address   ------------------------------  % Date: Wed, 01 May 2002 16:19:41 -0400>1 From: Michael Austin <maustin@firstdbasource.com>  Subject: Re: ZTDRIVER.EXE 2 Message-ID: <3CD04DDD.50F2DBD4@firstdbasource.com>   Syltrem wrote: > $ > Anyone knows what ZTDRIVER.EXE is? > M > I have a client that says he gets a "file not found" on this one when doing' > SYSGEN> AUTOCONFIGURE ALLo > N > We're at a minimum boot right now. All the devices we need configure ok, and4 > we are in the process of restoring a damaged disk. >  > Thanks >  > -- > 	 > SyltremaK > http://pages.infinit.net/syltrem (OpenVMS related web site - en franais) @ > To reply to myself directly, remove .spammenot from my address   What version? what system? c
 look here:I >>http://www.decus.org/encompass/libcatalog/document_html/vs0174_173.htmly -- o Regards,  7 Michael Austin            Registered Linux User #261163p7 First DBA Source, Inc.    http://www.firstdbasource.comc Sr. Consultant 704-947-1089 (Office)a 704-236-4377 (Mobile)c   ------------------------------  # Date: Wed, 01 May 2002 22:12:37 GMTe2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) Subject: Re: ZTDRIVER.EXE 9 Message-ID: <pLZz8.29$412.540708@cacnews.cac.cpqcorp.net>-  h In article <W0Xz8.10867$a04.49004@tor-nn1.netcom.ca>, "Syltrem" <syltremspammenot@videotron.com> writes:# :Anyone knows what ZTDRIVER.EXE is?   
   Guessing...-  L   MicroVAX 3100 series DSW-series widget.  If so, ZTDRIVER is the wide-area L   network device driver for the DSW-series widgets.  On OpenVMS VAX releasesG   prior to V6.0, install the WANDD kit.  On V6.0 and later OpenVMS VAX cM   releases, load DECnet-Plus and use the optionally-configured WANDD support.   M   Please see the OpenVMS FAQ for the details that can be useful to the folks .K   that might know the answer to your question.  Versions, platforms, etc.  eB   Including these details can help get you an answer more quickly.  E   Without details, the above details are a GUESS at the problem here.i    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: Wed, 1 May 2002 17:09:00 -0500+ From: Christopher Smith <csmith@amdocs.com>a Subject: RE: ZTDRIVER.EXEyJ Message-ID: <7E008308CD77154485FEF878168D078E01784514@CMIMAIL1.amdocs.com>   --=_IS_MIME_Boundary Content-Type: text/plain;o 	charset="iso-8859-1"y   > -----Original Message-----% > From: hoffman@xdelta.zko.dec.nospame  ; >   Please see the OpenVMS FAQ for the details that can be   > useful to the folks < >   that might know the answer to your question.  Versions,  > platforms, etc.  rD >   Including these details can help get you an answer more quickly.  D This is the second time today I've seen you make that suggestion. :)  2 >  ---------------------------- #include <rtfaq.h>  " Maybe it's the choice of language?   Could change that to:a     ok require FAQ    Chrisi      ! Christopher Smith, Perl Developer  Amdocs - Champaign, IL   /usr/bin/perl -e '? print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n");t 't  V --=_IS_MIME_Boundary) Content-Type: text/plain;charset=us-asciis Content-Transfer-Encoding: 7bitt Content-Disposition: inlineA  U -------------------------------------------------------------------------------------n  C The information contained in this message is proprietary of Amdocs, 1 protected from disclosure, and may be privileged. N The information is intended to be conveyed only to the designated recipient(s)L of the message. If the reader of this message is not the intended recipient,P you are hereby notified that any dissemination, use, distribution or copying of ? this communication is strictly prohibited and may be unlawful. sN If you have received this communication in error, please notify us immediately> by replying to the message and deleting it from your computer.
 Thank you.  U -------------------------------------------------------------------------------------,   --=_IS_MIME_Boundary--   ------------------------------  # Date: Wed, 01 May 2002 22:58:34 GMTi2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) Subject: RE: ZTDRIVER.EXE,9 Message-ID: <uq_z8.30$u%1.495729@cacnews.cac.cpqcorp.net>l  x In article <7E008308CD77154485FEF878168D078E01784514@CMIMAIL1.amdocs.com>, Christopher Smith <csmith@amdocs.com> writes:  < :>   Please see the OpenVMS FAQ for the details that can be < :>   useful to the folks that might know the answer to your ; :>   question.  Versions, platforms, etc.  Including these a5 :>   details can help get you an answer more quickly.r :cE :This is the second time today I've seen you make that suggestion. :),  G   It very likely will not be the last time that you see me make this or G   a similar suggestion, nor will it be the last time that you will see m!   a reference to the OpenVMS FAQ.n  G   What you (and some of the questioners) did not see were the questions F   that I skimmed, and that I didn't post replies to -- simply because E   of the lack of details in the original posting, this in particular  9   consideration of my current level of schedule loading.    &   ps: Your mailer is adding MIME tags.  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   ------------------------------   End of INFO-VAX 2002.241 ************************