0 INFO-VAX	Sun, 18 Feb 2001	Volume 2001 : Issue 97      Contents: ****SPECIAL REPORT**** Classic VMS Games - restoration  Re: CONINTERR and friends & Re: Future outlook for OpenVMS admins?& Re: Future outlook for OpenVMS admins?, Re: heads up - OpenVMS Technical update days, Re: heads up - OpenVMS Technical update days, Re: heads up - OpenVMS Technical update days Re: History of VAX releases  Re: Interesting feature... Re: Interesting feature...$ Re: Multitasking via telnet sessions$ Re: Multitasking via telnet sessions
 Re: newbie
 Re: newbie# Re: Now BYPASS doesn't allow DELETE 5 RE: Passing PCL codes to printer via VMS printer form   Re: Possible security hole in... Re: TFT > 18.1" with 1280x1024 Re: TFT > 18.1" with 1280x1024 Re: UNIX write vs VMS ?  Re: version numbers.C Re: Was Renaming directories. Now: Suitable privileges for a SYSMGR ! Re: which shadow patch do I need? ! Re: which shadow patch do I need? ! Re: which shadow patch do I need?  Re: www.openvms.compaq.com  F ----------------------------------------------------------------------  # Date: Sat, 17 Feb 2001 21:54:07 GMT  From: wilsoncredit@email.com Subject: ****SPECIAL REPORT**** 8 Message-ID: <3qCj6.191812$9v2.2064501@quark.idirect.com>  + --_NextPart_0000904B-000018B5-0470A50B-0F11  Content-Type: text/plain Content-Transfer-Encoding: 7bit    Get a brand new, clean, ! credit file in 15 days or less...  Get the credit you deserve...  For more info, send a email to wilsoncredit@email.com" with "INFO" in the subject line...- --_NextPart_0000904B-000018B5-0470A50B-0F11--    ------------------------------  % Date: Sat, 17 Feb 2001 15:07:35 -0500 ! From: Beyonder <beyonder@vrx.net> ( Subject: Classic VMS Games - restoration8 Message-ID: <ehlt8t8qstcj6db7urcfp73riq891fjv7c@4ax.com>  8 Ok, I posted a bit before, but now for the real deal. :)C Here's some of the stuff I have collected, and still have, and some  stuff I'm looking for....   ) These all date back to roughly 1976-1979-   D 1. Colossal Cave (Adventure) - I have a copy of the Vax BASIC source code for this in a printout   E 2. Zork - I have the Vax Fortran source code for this. The one I have E has "self-correcting" code, that is, you make a typo on a line, it'll > tell you the line # and what the mistake is. regardless of the9 mistake. The printout for this is something like 6" thick   D 3. Rogue - someplace I have the Vax Fortran source printout for this one   ? 4. Empire - I have the Vax Fortran source printout for this one   E 5. Trek5 - I believe this may be Vax Basic, possibly Fortran. this is , the age-old single-user Star Trek - classic.  D 6. Castle - I only have a painstakingly converted version for the PCC written in Borland Turbo Pascal - could easily be converted to Free , Pascal (FPC or Gnu). The PC executable is at# http://nexus.vrx.net/mp3/castle.zip   B 7. Trek7 - The holy terror - In my opinion the BEST Star Trek game; ever made in the history of computer games. Full multi user D capability, made the way classic Star Trek was meant to be. Full Vax3 Fortran sources. This restoration project lives at:  http://nexus.vrx.net/trek7  E 8. Wumpus - I have the Vax source printout for this one. Who can live  without this one? :)  ? 9. The Hidden Crown - Vax source code printout for this old one   < 10. Conquest - I have a Vax backup set of this one. requires9 backup/restore to retrieve. Have binary file image on PC.   D 11. SpaceWar - the FIRST game ever made. This PDP Classic is truly aC collectors item. Thankfully I also have a PC (Dos) emulator for the  PDP so you can play it :)    -----------------------------   A Most of these are printouts from a Vax from no more recently than D 1984. and I still have the paper printouts, which I will need to OCRF scan (and then clean up for mistakes). Some of them I could simply put online if people wanted.  D My ultimate goal will be to put all of these online in a Vax archiveB (first my own, and possibly later, others).  I wanted to see whichD ones people would like to see, and if anyone out there wants to help& clean up the stuff so it'll run again.  D For example - my empire printout has water stains. about 20 lines of= code (out of a 1-1.5" printout) were obliterated or partially  obliterated.  C Yes I know some of these have been converted to the PC, but I don't F really care. I'd like to see working Vax versions again (running under3 the new VMS versions), or ported to Linux. or both!   > So suggestions, comments, requests, and lots of help, would be appreciated.  C I'm going to build a new URL for all this, http://nexus.vrx.net/vms < and stuff everything under there. so trek7 will get moved to> http://nexus.vrx.net/vms/trek7 castle will be similarly moved.  ? I'll throw Spacewar and conquest up as soon as I can get to it.    B.   ------------------------------    Date: 17 Feb 2001 14:10:43 -0500: From: malmberg@eisner.encompasserve.org (John E. Malmberg)" Subject: Re: CONINTERR and friends3 Message-ID: <a8$pm2rWKHQD@eisner.encompasserve.org>   - In article <87pughpn6h.fsf@prep.synonet.com>, . Paul Repacholi <prep@prep.synonet.com> writes: > C > OK, I was looking through the docs, and it seems to have vanished A > for Alpha VMS. How do I do a Connect to Interupt? Specifically, > > I want to get the interupt from the *chip* console port. Not# > the system console, the chip one.  > C > Anyone delved into this area on Alphas? Or is this stuff Vax only 
 > nowdays?  @ IIRC: The Connect to Interrrupt IO functions, IO$_CONINTREAD andB IO$_CONINTWRITE were only documented for the Laboratory Peripheral
 Excellerator.    -John  wb8tyw@qsl.network Personal Opinion Only    ------------------------------    Date: 17 Feb 2001 15:34:23 -05002 From: young_r@eisner.encompasserve.org (Rob Young)/ Subject: Re: Future outlook for OpenVMS admins? 3 Message-ID: <7ticHyDx3qnF@eisner.encompasserve.org>    In article <rdeininger-1602012153450001@user-2ive7k1.dialup.mindspring.com>, rdeininger@mindspring.com (Robert Deininger) writes: 5 > In article <kPbh9WrW+T$9@eisner.encompasserve.org>, 5 > young_r@eisner.encompasserve.org (Rob Young) wrote:  >  >   E >>         This kind of search took two minutes, Dell sells a 1.5 GHz  >>         P4: > F > Since I've never dealt with Dell, this may be a silly question.  AreH > "selling" and "shipping" pretty much the same for them, or is there an  > indefinite "pre-order" period? >   = 	The other search I performed was out at SpecBench... this is : 	a good view too.  Keep in mind, you can "sell" futures at> 	SpecBench but you have to hardware availability date and Dell; 	has November 2000 as availability date.  Today I am taking E 	a different tack and focusing on IBM.  IBM shipped 1.5 GHz Pentium 4  	since November:  D http://www.zdnet.com/products/stories/reviews/0,4161,2655575,00.html  F 	I checked and IBM is indeed today selling a 1.5 GHz Pentium 4 desktop 	box for $2666.00   = 	I also check and noted that mindspring.com is an ISP through < 	earthlink.net ... so I am assuming you yourself can do this9 	same sort of "magic"  (i.e. search the Internet and find 0 	information).  You may wish to start at Google: 		   		http://www.google.com/   	and type:  Pentium 4   ! 	feel free to refine your search.    				Rob    ------------------------------  % Date: Sat, 17 Feb 2001 15:51:05 -0800 ! From: Koloth <koloth@tmisnet.com> / Subject: Re: Future outlook for OpenVMS admins? + Message-ID: <3A8F0E69.C3512B9C@tmisnet.com>   M I remember going to an Intel presentation many, many moons ago.  Their saying @ was, "There are lies, damn lies, and then there are benchmarks!"  G One thing I want to know is if the SPECint2000 measure 32 bit or 64 bit M calculations.  Some problems these days like encryption work much better with O larger bit size.  Only having 32 bit calculations in the benchmark can skew the > results away from showing the true power of 64 bit processors.   Cass   "Main, Kerry" wrote:  K > While one could split hairs and point out that the 1.5Ghz x86 is actually I > slower than the 833Mhz Alpha when looking at the optimized SPECint 2000 : > result, (A=544 vs I=536) essentially, it is a dead heat.? > http://ideasinternational.com/benchmark/spec/specint2000.html  > N > And as always, one should also consider other benchmarks and reviews as well > e.g.; > <http://www4.tomshardware.com/cpu/00q4/001122/p4-04.html> ; > <http://www4.tomshardware.com/cpu/00q4/001122/p4-03.html>  > 
 > Regards, >  > Kerry Main > Senior Consultant  > Compaq Canada Inc. > Professional Services  > Voice: 613-592-4660  > Fax  :  819-772-7036 > Email: Kerry.Main@Compaq.com >  > -----Original Message-----6 > From: tsm@palindrome.org [mailto:tsm@palindrome.org]" > Sent: February 16, 2001 11:23 AM > To: Info-VAX@Mvb.Saic.Com 1 > Subject: Re: Future outlook for OpenVMS admins?  > 0 > On 16 Feb 2001 10:30:38 +0100, Jan Vorbrueggen: > <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de> wrote:$ > >"rocko" <rocko1@home.com> writes: > > L > >> We are waiting on a couple Compaq AlphaServer ES40's to arrive.  How do > they
 > >> rate? > > G > >If they're the 833 MHz variety, they're the fastest processor on the 	 > planet.  >  > Not true.  > K > The Pentium 4 is faster than the 833 MHz EV6, at least at integer, and is 5 > faster than anything but the 833 at floating point.  > 
 > SpecInt2000 
 > -----------  > 1.5 GHz Pentium 4 - 524  > 833 MHz EV6 (in ES40) - 518  > 1.2 GHz Athlon - 443 > 1 GHz Pentium III - 438  > 731 MHz EV6 (in ES40) - 352  >  > SpecFP2000 > ---------- > 833 MHz EV6 - 590  > 1.5 GHz Pentium 4 - 549  > 731 MHz EV6 - 405  > 1.2 GHz Athlon - 359 > 1 GHz Pentium III - 327    ------------------------------   Date: 17 Feb 2001 12:32:22 CDT= From: wayne@tachysoft.xxx.522739.killspam.00bb (Wayne Sewell) 5 Subject: Re: heads up - OpenVMS Technical update days . Message-ID: <AG$dd8$2h1vf@tachxxsoftxxconsult>  j In article <yJbj6.8$fY5.281@gazette.loc1.tandem.com>, "Sue Skonetski" <susan.skonetski@compaq.com> writes: > Dear Newsgroup,  > M > I wanted you to be aware that we currently have 3 OpenVMS Technical Updates J > scheduled.  One is Washington DC, one in Dallas Texas and one in London,I > England.  OpenVMS Engineers will be doing the sessions at these events.  > ( > Washington DC is scheduled March 27&28 > " > The 2-day event will be held at: > 2 > University of Maryland Inn and Conference Center > & > University Boulevard at Adelphi Road > # > College Park, Maryland 20742-1610  > K > Location directions, registration logistics and agenda details are on the # > registration website shown below.  >  > www.compaq-signup.com  > L > Dallas Texas is scheduled for April 18-20th at the Sheraton Grand Hotel atD > Dallas/FT. Worth Airport. More details when they become available. > # > London, England will be May 15-17  >  > Warm Regards,  >     N I cannot get to this page using a vms browser.  netscape displays a blank pageN and mozilla dies a horrible death.  Is this yet another case of a vms-oriented: web page that can only be displayed on a billybox browser?       --  O =============================================================================== M Wayne Sewell, Tachyon Software Consulting  (281)812-0738  wayne@tachysoft.xxx : http://www.tachysoft.xxx/www/tachyon.html and wayne.html  K change .xxx to .com in addresses above, assuming you are not a spambot  :-) O =============================================================================== B Cute Girl, to Curly: "Oh, what a beautiful head of bone you have!"   ------------------------------  % Date: Sat, 17 Feb 2001 17:51:16 -0500 % From: "John Vottero" <John@mvpsi.com> 5 Subject: Re: heads up - OpenVMS Technical update days / Message-ID: <t8u049qatjnp0c@news.supernews.com>   J "Wayne Sewell" <wayne@tachysoft.xxx.522739.killspam.00bb> wrote in message( news:AG$dd8$2h1vf@tachxxsoftxxconsult...G > In article <yJbj6.8$fY5.281@gazette.loc1.tandem.com>, "Sue Skonetski" $ <susan.skonetski@compaq.com> writes: > > Dear Newsgroup,  > > G > > I wanted you to be aware that we currently have 3 OpenVMS Technical  Updates L > > scheduled.  One is Washington DC, one in Dallas Texas and one in London,K > > England.  OpenVMS Engineers will be doing the sessions at these events.  > > * > > Washington DC is scheduled March 27&28 > > $ > > The 2-day event will be held at: > > 4 > > University of Maryland Inn and Conference Center > > ( > > University Boulevard at Adelphi Road > > % > > College Park, Maryland 20742-1610  > > I > > Location directions, registration logistics and agenda details are on  the % > > registration website shown below.  > >  > > www.compaq-signup.com  > > K > > Dallas Texas is scheduled for April 18-20th at the Sheraton Grand Hotel  atF > > Dallas/FT. Worth Airport. More details when they become available. > > % > > London, England will be May 15-17  > >  > > Warm Regards,  > >  >  > K > I cannot get to this page using a vms browser.  netscape displays a blank  pageC > and mozilla dies a horrible death.  Is this yet another case of a  vms-oriented< > web page that can only be displayed on a billybox browser? >   6 The page contains nothing but a Shockwave Flash movie.  J I don't know why anyone would support or use proprietary extensions to the web.  L I especially don't understand why Compaq would require the use of MacromediaC products when Macromedia doesn't support OpenVMS or Tru64 or Alpha.   I And before anyone starts whining about me burying my head in the sand and I pretending that VMS is a desktop O/S, I'm typing this on an Intel machine D running Windows 2000 and IE 5.5.  But, I still have ActiveX controls8 disabled and I refuse to use proprietary web extensions.   ------------------------------  % Date: Sun, 18 Feb 2001 00:06:20 +0000 ) From: Christof Brass <brass@infopuls.com> 5 Subject: Re: heads up - OpenVMS Technical update days , Message-ID: <3A8F11FC.33AE45F3@infopuls.com>   John Vottero wrote:  > L > "Wayne Sewell" <wayne@tachysoft.xxx.522739.killspam.00bb> wrote in message* > news:AG$dd8$2h1vf@tachxxsoftxxconsult...I > > In article <yJbj6.8$fY5.281@gazette.loc1.tandem.com>, "Sue Skonetski" & > <susan.skonetski@compaq.com> writes: > > > Dear Newsgroup,  > > > Q > > > I wanted you to be aware that we currently have 3 OpenVMS Technical Updates N > > > scheduled.  One is Washington DC, one in Dallas Texas and one in London,M > > > England.  OpenVMS Engineers will be doing the sessions at these events.  > > > , > > > Washington DC is scheduled March 27&28 > > > & > > > The 2-day event will be held at: > > > 6 > > > University of Maryland Inn and Conference Center > > > * > > > University Boulevard at Adelphi Road > > > ' > > > College Park, Maryland 20742-1610  > > > O > > > Location directions, registration logistics and agenda details are on the ' > > > registration website shown below.  > > >  > > > www.compaq-signup.com  > > > P > > > Dallas Texas is scheduled for April 18-20th at the Sheraton Grand Hotel atH > > > Dallas/FT. Worth Airport. More details when they become available. > > > ' > > > London, England will be May 15-17  > > >  > > > Warm Regards,  > > >  > >  > > R > > I cannot get to this page using a vms browser.  netscape displays a blank pageR > > and mozilla dies a horrible death.  Is this yet another case of a vms-oriented> > > web page that can only be displayed on a billybox browser? > >  > 8 > The page contains nothing but a Shockwave Flash movie. > L > I don't know why anyone would support or use proprietary extensions to the > web. > N > I especially don't understand why Compaq would require the use of MacromediaE > products when Macromedia doesn't support OpenVMS or Tru64 or Alpha.  > K > And before anyone starts whining about me burying my head in the sand and K > pretending that VMS is a desktop O/S, I'm typing this on an Intel machine F > running Windows 2000 and IE 5.5.  But, I still have ActiveX controls: > disabled and I refuse to use proprietary web extensions.  @ I vote for standardised and open formats. XHTML/XML and a proper@ semantics not only for the Web but also for office documents and> other. There is of course the problem of hindering innovation.= But the first step should always be an RFC and an open source 0 implementation for at least three different OSs.  : OTH I think the form and technique of a Web page should be= appropriate to its content. If it should be fancy and impressn< some business or marketing folks use whatever you want, fine8 with me, I won't look at it. If you want to present some; important information make the information as easy (fast ins7 terms of download time) and (e.g. no fat files) quicklyr? accessible as possible. Don't use fancy stuff which detracts mee; from reading and recepting this information. At least therei> should be a text only version alternatively available. I don't? want to waste bandwidth if I only want to know which curses arei offered.   ------------------------------  % Date: Sat, 17 Feb 2001 20:20:24 +0000 + From: "antonio.carlini" <arcarlini@iee.org> $ Subject: Re: History of VAX releases' Message-ID: <3A8EDD08.96C58DA8@iee.org>s   "Mark D. Jilson" wrote:h > D > Release dates may be obtainable but what do you mean by withdrawal > date?? >  > Nick Ogbourne wrote: > >qF > > Can anyone point me to information that lists the release date andJ > > withdrawal dates of VAX and Alpha machines in the period 1995 to 2000? > >j > > Nick OgbourneP  4 Withdrawl date could be either "last order date" or 4 "last ship date" for any given machine. Getting hold of them can sometimes be fun.   4 Release date is similarly fuzzy given that there are4 "announcement" dates and "first revenue ship" dates.  6 Go back far enough and you can split these dates up by3 geography (products were sometimes announced in the 4 US and then announced a few months later in Europe).  / Then again he may want a list of machines first1( supported by a given release (of a given) operating system) or the same list but ofs# releases which last supported givenb	 hardware.8  $ The Digital timeline might be a good general place to start.a   Antonio    ---------------s- Antonio Carlini             arcarlini@iee.org    ------------------------------  % Date: Sat, 17 Feb 2001 20:03:55 +0000   From: steven.reece@quintiles.com# Subject: Re: Interesting feature... H Message-ID: <OFBB8ABA57.D7B364E4-ON802569F6.006E049A@qedi.quintiles.com>  H I don't think that's strictly true.  I don't believe my two 8400s (whichA are still up for sale if someone wants them.  Buyer collects fromi+ Bracknell, UK) have RCM units in them......o  8 Paul Repacholi (prep at prep dot synonet dot com) wrote:D >>>The 'top end' stuff does all of this, as can the 4100. Hell, even( my old Prioris can have it as an option.  A Generally in a RSM, Remote System MAnagment, unit in the smalllerr? systems. The larger ones have a more integrated on standard.<<<C   ------------------------------  % Date: Sat, 17 Feb 2001 14:45:18 -0600n% From: Keith Brown <kbrown780@isd.net> # Subject: Re: Interesting feature...u' Message-ID: <3A8EE2DE.3A6A8C24@isd.net>v   Dean Woodward wrote: > E > One of the guys from the other side of the building (Internet Svcs)mC > just got a new toy from that company named after our nearest staraG > (Not mentioning names lest I awaken AH).  He showed me a feature thatT > I found most interesting.  > E > This is a little 1u rackmount box.  It's console runs even when theoE > system itself is powered down- in fact, one of the commands you canrC > issue is 'poweron', and suddenly all the fans and drives wake up.h > D > Forgiving my ignorance of high-end Alphas, but do any of them knowC > how to do this, and if so, is it a feature likely to migrate downdD > to low end boxes that might compete with this? (Say, the rackmount > DS10 series)?a > G > (Of course, and OTOH, it's a feature for when your box isn't running, 1 > so maybe not of much interest to VMS users. ;-)   + IIRC my old VAX 8650 did this 10 years ago.r   -- u Keith Browni kbrown780@isd.netn   ------------------------------   Date: 17 Feb 2001 17:25:08 GMT3 From: gartmann@immunbio.mpg.de (Christoph Gartmann)t- Subject: Re: Multitasking via telnet sessionsr0 Message-ID: <96mc5k$pl6$1@n.ruf.uni-freiburg.de>  W In article <3a8eb910.5456371@news.earthlink.net>, alexlong@earthlink.net (Alex) writes:pG >I connect to a VMS server through Telnet to do various tasks, and somet@ >of those taks take a considerable amount of time to run.  Is itC >possible to multi-taks through a telnet session with just a singleh >login?c  M You could use batch-jobs or detached processes. Refer to the docs for furthern information.   Regards,    Christoph Gartmann   H -- --------------------------------------------------------------------+H | Max-Planck-Institut fuer      Phone   : +49-761-5108-464   Fax: -452 |H | Immunbiologie                                                        |H | Postfach 1169                 Internet: gartmann@immunbio.mpg.de     |H | D-79011  Freiburg, FRG                                               |H +--------- http://www.immunbio.mpg.de/home/english/menue.html ---------+   ------------------------------  % Date: Sat, 17 Feb 2001 15:27:51 -0500:- From: JF Mezei <jfmezei.spamnot@videotron.ca>Q- Subject: Re: Multitasking via telnet sessionsu, Message-ID: <3A8EDEC5.BD457A70@videotron.ca>  ' There are many ways to accomplish this.   L You can use your TELNET software to open multiple windows, each with its ownM unique telnet session to the target host. (NCSA telnet on a MAC allows this).tL The target system must have the licenses to allow multiple logins since eachL window will be considered a separate interactive user. (if the target systemE is a single user system you will only be allowed one telnet session).   9 You can also use the SPAWN command from a single session.h  K It becomes easy to maintain various contexts at the same time and switching- from one to the other:   $CD SYS$LOGIN: $SET PROC/name=JOB10   $SPAWN $SET PROC/NAME=JOB2s $CD disk$:[GHOSTSCRIPT]j$ $GS :== "$DISK$:[GHOSTSCRIPT]GS.EXE" $DEFINE CHOCOLATE "GOOD"   $ATTACH JOB1  F You are now back in the first process, where your default directory is2 SYS$LOGIN, and "GS" and "CHOCOLATE" are undefined.   $ATTACH JOB2  J You're back in the second process in the ghostscript directory with the GS& symbol and CHOCOLATE logicals defined.  N Of course, if one of the two processes is curently executing a very long task,M you don't have the opportunity to type the ATTACH command and must wait untill it is done.A   From JOB1, you could :  : SPAWN/NOWAIT/PROC=JOB3 @command_that_takes_a_long_time.COM  L This will make JOB3 run concurrently and you remain in JOB1. The above won'tM work very well if JOB3 requires input. And if JOB3 generates a lot of output,BG it gets sent to your terminal, mixed with whatever output JOB1 would be0N generating. You can alleviate this with /OUTPUT=JOB3.LOG in the SPAWN command.3  (HELP SPAWN will give you a lot more information).:  G Another method would be to turn your PC into an X terminal (with some X N terminal software), and then have multiple independant DECterm windows runningM on your PC, each attached to an independant process on the target VMS system.e   ------------------------------  % Date: Sat, 17 Feb 2001 20:11:10 +0000m# From: Matt London <matt@knm.yi.org>f Subject: Re: newbie E Message-ID: <Pine.LNX.4.20.0102171956200.28318-100000@coffeepot.matt>d   Hi,   
 > Andy wrote:e > > I > > I just started a position where i will be using open VMS extensively,aL > > and am wondering if this NG has any recommendations on books that covers1 > > a broad range,...intro, commands, admin, etc.g > > K > > Any ideas appreciated,....local bookstores were not much help,..nothing  > > in stock > ? > While the others recommendations are all valid there could berB > something we might take into account: what is your experience so? > far, what do you know? What will you do with the system? Willy, > you be a sysadmin, a programmer or a user?   I'm also a newbie :&)   B I've just aquired a microvax 3100 m10e with VAX/VMS-5.4 and NetBSDG installed on it - and while I'm nice and at home with *BSD, I'd love totI get into VMS. My first thought was "let's check out the online VMS docs",tD but I'm so much more at home with stuff on paper :&/ I did wonder ifE anyone knew any resoure, be it online, book, whatever that introduced.G admining/using VMS from a unix user's perspective. If not, then I'll be ! attacking the online VMS docs :&)i  I What would be useful is a list of important things to read to start with..  ( Well any ideas would be appreciated :&)    -- Mattr   ---oH PGP Key fingerprint = 00BF 19FE D5F5 8EAD 2FD5  D102 260E 8BA7 EEE4 8D7F' PGP Key http://knm.yi.org/matt-pgp.htmlf   ------------------------------    Date: 18 Feb 2001 05:00:06 +0800, From: Paul Repacholi <prep@prep.synonet.com> Subject: Re: newbier- Message-ID: <87vgq9nhyh.fsf@prep.synonet.com>r  % Matt London <matt@knm.yi.org> writes:   D > I've just aquired a microvax 3100 m10e with VAX/VMS-5.4 and NetBSDI > installed on it - and while I'm nice and at home with *BSD, I'd love tosK > get into VMS. My first thought was "let's check out the online VMS docs",iF > but I'm so much more at home with stuff on paper :&/ I did wonder ifG > anyone knew any resoure, be it online, book, whatever that introducediI > admining/using VMS from a unix user's perspective. If not, then I'll be # > attacking the online VMS docs :&)8 > K > What would be useful is a list of important things to read to start with.l > * > Well any ideas would be appreciated :&)   D I suspect if you posted where you are, and said "old doc set wanted,C will collect...", you will soon have an offer. To take ALL of them. > The help file is a pretty good start, and Hoffs excellent FAQ.   -- e< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.-@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.   ------------------------------  % Date: Sat, 17 Feb 2001 18:12:50 -0500x% From: "John Vottero" <John@mvpsi.com>Y, Subject: Re: Now BYPASS doesn't allow DELETE/ Message-ID: <t8u1chb8fnskce@news.supernews.com>w  ? "Hoff Hoffman" <hoffman@xdelta.zko.dec.nospam> wrote in messagep1 news:OpWi6.669$cu.2814@gazette.loc1.tandem.com...iH > In article <VA.000002a5.45845c7e@sture.ch>, Paul Sture <paul@sture.ch> writes:lK > :In article <y4d7cm3h9p.fsf@mailhost.neuroinformatik.ruhr-uni-bochum.de>,r Jan& > :Vorbrueggen wrote:nL > :> From: Jan Vorbrueggen <jan@mailhost.neuroinformatik.ruhr-uni-bochum.de> > :> Newsgroups: comp.os.vms, > :> Subject: Re: Another missed opportunity% > :> Date: 13 Feb 2001 13:21:38 +0100s > :>' > :> Paul Sture <paul@sture.ch> writes:  > :>J > :> > I once heard a tale of Pathworks files which couldn't be deleted by thes= > :> > SYTEM account - solution - reinitialize the disk. Yuk.  > :>$ > :> I thought BYPASS bypasses that? > :>K > :Well before I heard the tale, I thought so too. But this story came fromr a K > :System Manager who is one of the best I have worked with. Let's check it 	 > :out...  > K >   The system manager was wrong, or there was something else going on thateJ >   was mimicking a OpenVMS protection check (incorrectly).  BYPASS grants6 >   all access to everything, even in an SEVMS system. >=  I This is probably a result of calling sys$chkpro and assuming that successnL grants access and failure denies access.  If an object gets a corrupt ACL on> it then sys$chkpro returns SS$_INVACL even if you have BYPASS.  I > :Looking at section 4.3 of the Guide to System Security, BYPASS doesn't=+ > :really _bypass_ access checking anymore.h >aI >   The flow chart has a bug.  The READALL "no" path in HH should lead toeF >   the BYPASS check, and only then to "grant" or to section II.  I've logged, >   a problem report against the flow chart. > , >  --------------------------- pure personal# opinion ---------------------------f1 >    Hoff (Stephen) Hoffman   OpenVMS EngineeringA hoffman#xdelta.zko.dec.com >.   ------------------------------  % Date: Sat, 17 Feb 2001 16:05:56 -0500 1 From: "Forster, Michael " <MFORSTER@PARTNERS.ORG>w> Subject: RE: Passing PCL codes to printer via VMS printer formP Message-ID: <709CDBE6CA13D311B4DF0008C7EAD0C604443959@phsexch13.mgh.harvard.edu>  O Thanks everyone! I've tested this out on our development system and then on theeM live production boxes, using three different HP printers. Everyone's help has  been fantastic.v  E Now's the fun part of doing the fine-tuning to align the print on the  pre-printed forms.   mi     > -----Original Message-----3 > From:	Olson, Ingemar [SMTP:IOlson@dairyworld.com]o) > Sent:	Friday, February 16, 2001 7:59 PMn > To:	Info-VAX@Mvb.Saic.Com @ > Subject:	RE: Passing PCL codes to printer via VMS printer form > P > If ALL your printers are guaranteed to be compatible now and forevermore, that > 8 > naming scheme might be ok. If not, here's what we do:  > H > 1) Create a separate library for each "type" of printer (eg: HP laser, > DecWriter, ...) P > where the "type" really is a group that can understand the same set of escape 9 > sequences. And name them to describe the printer type. e > P > 2) Populate each of those libraries with modules for each FORM you are using. P > Different printers will require different escape sequences to do the same job. > N > Even if that means the module sometimes contains nothing at all, since some B > printers won't support all the features of every other printer.  > P > Eg: If you have two printers & two libraries and you want to print "portrait" N > on both of them, then each library gets a "portrait" module, but the actual E > escape sequences you define to accomplish that might be different. i > G > 3) Create the FORM definition to reference the module name you need. f > C > 4) Start each queue with the appropriate /library=<library name>   > L > You are now in a position where you can print to any queue using the same J > FORM name. The print symbiont will look in the queue's library and pull  > out the appropriate module.  > P > Granted that there will be instances where using a FORM which is intended for P > an HP but printing it on your DecWriter won't give your users the result they A > wanted, but at least it won't crap out on the print statement. o > It _will_ do _something_.  >  > Ingemar Olson  >  >  > -----Original Message----- t; > From: Forster, Michael [ <mailto:MFORSTER@PARTNERS.ORG>] e > Sent: February 15, 2001 6:39   > To: Info-VAX@Mvb.Saic.Com A > Subject: RE: Passing PCL codes to printer via VMS printer form a >  > K > Yes, I was planning on using DCL to inject the escape sequences into the  G > file, especially since I'm not adept at EDIT/EVE or TPU. The code is n > appreciated. e > H > I have a few more questions, so I hope you'll continue to be patient. M > Libraries and modules for printers is something totally new for me since I oD > normally pass the PCL through applications and not the VMS queue.  > O > I'm going to make a library, which will contain numerous modules for each of uN > the pre-printed paper forms we have. So I'll have to have a separate module M > for each of those forms, and have the VMS form attached to the appropriate i > module. Am I correct?  > O > I'm not going to use the default module, and will make a new module. Did the rO > LIBRARY command create the TLB file I'm copying to SYS$LIBRARY in the second sK > command? Also what naming convention would I use for my_module_name - is a > that an alias? r > E > I was thinking of naming the "my_library"  and "my_library.TLB" as   > HP_PCL_CLAIMFORMS. a > 	 > Steps: pJ > Create PCL file using DCL to insert escape sequences, name it MMIS5.TXT F > LIBRARY/INSERT/TEXT SYS$LIBRARY:my_library MMIS5.TXT/my_module_name : > COPY SYS$LIBRARY:my_library.TLB SYS$COMMON:[SYSLIB]/LOG  >  > Am I still on track? w >  > m  >  > > -----Original Message-----  E > > From: rdeininger@mindspring.com [SMTP:rdeininger@mindspring.com] a/ > > Sent: Thursday, February 15, 2001 12:37 AM I  > > To:   Info-VAX@Mvb.Saic.Com H > > Subject:      Re: Passing PCL codes to printer via VMS printer form  > >  > > In article sJ > > <709CDBE6CA13D311B4DF0008C7EAD0C604443923@phsexch13.mgh.harvard.edu>, 7 > > "Forster, Michael " <MFORSTER@PARTNERS.ORG> wrote: h > >  > > M > > > One PCL string example of what I have to pass to the printer is (In my m
 > > example,  O > > > *27 indicates the <ESC>, don't know what the library control uses as the o > > code): p > > > @ > > *27,"&l0L",*27,"&l6D",*27,"&l0E",*27,"&l125Z",*27,"&l-233U"  > > >  > > One suggestion:  > > N > > Files that contain escape sequences are a pain to work with. Editors tend K > > to suppress special characters in various ways (which is good) and the  G > > TYPE on such a file is likely to do nasty things to your terminal. f > > N > > I prefer to build up such files in DCL command files, and let the command L > > file insert the module in a library, and then delete the raw text file. - > > Something like this, using your example: i > >  > > $ ESC[0,8] == %X1B -I > > $ pcl_string = esc + "&l0L" + esc + "&l6D" + esc + ""&l0E" + esc + - i  > >  "&l125Z" + esc + "&l-233U"  > > $  > > $ open/write temp temp.txt   > > $ write temp pcl_string  > > $ close temp w > > $ 3 > > $ library/text/replace <library file> temp.txt   > > $ ' > > $ delete/nolog/noconfirm temp.txt;   > > L > > This kind of file is easy to edit, print, type, etc, but it creates the 6 > > module you need with embedded special characters.  > >  > > -- 2 > > Robert Deininger b > > rdeininger@mindspring.com  >    ------------------------------  % Date: Sat, 17 Feb 2001 18:47:06 -0500 2 From: "Richard B. Gilbert" <DRAGON@compuserve.com>) Subject: Re: Possible security hole in...a7 Message-ID: <200102171847_MC2-C5F9-95A2@compuserve.com>b  > Message text written by INTERNET:hoffman@xdelta.zko.dec.nospamG >In article <t8ok8kjcv0j822@news.supernews.com>, wspencer@ap.nospam.orgs (Warren Spencer) writes:  I :I understand the concern about not broadcasting security/crash issues. =f   But =   H :once Q has received (and verified) a report, how do the rest of us find out =a   :about it?  Thanks.   .   Each report of a security problem is unique.  J   The approach chosen for remediation depends on the results of the gener= alJ   investigation, on the level of severity of and risk of an exposure to t= he  F   problem, and on the potential for disruption from the fix itself.  =    G   Sometimes the remediation will simply be incorporated into an ECO kit E   currently under development (potentially raising the installation =t  I   priority of the particular ECO kit), and sometimes the required fixes =h  =   will mandate a specific ECO kit be created and distributed.s  H   I will assume you are familiar with DSNlink and the support databases,3   and with the various ECO notification mechanisms.t <.  C         I think that, perhaps, Warren was asking about those not on J support.  I've been there myself.  It's not a happy situation but sometim= es4 there's nothing you can do but cope as best you can!   ------------------------------  % Date: Sat, 17 Feb 2001 17:30:07 -0500a% From: "John Vottero" <John@mvpsi.com>4' Subject: Re: TFT > 18.1" with 1280x1024 / Message-ID: <t8tusfqm55dj05@news.supernews.com>n  6 "Christof Brass" <brass@infopuls.com> wrote in message& news:3A8DC3DE.8E147FF3@infopuls.com... > John Vottero wrote:a > > 2 > > > Question1: is the pixel size of TFT's fixed? > >s > > Yes. > >hC > > > Question2: is the quality reduced if the native resolution is 9 > > > 1600x1200 (19.6" TFT) but I'm using only 1280x1024?  > >a> > > Yes.  Don't pay for 1600x1200 unless that's what you want. > >pI > > What is the actual display size with your 20" monitor?  An 18.1" flatw panel H > > is really 18.1".  My 21" monitor only has about 19" of usable space. >b > Thanks for your advice.h >i@ > Calculating/measuring the real display size is not that simple  > as I haven't done this before.? > The width is 49.7 cm (should be 19.6"), the height is 29.8 cm A > (should be 11.7) and I calculated the diagonal with the formula > > sqrt(width*width + height*height) as 58 cm (should be 22.8")A > which seems a little bit too much. But I don't know where I didi= > the mistake. I used a 30 cm (should be 11.8") solid measurer3 > stick. The monitor is a SAMSUNG SyncMaster 1000p.   G Are you sure about the width?  49.7 cm sounds about 10 cm too wide.  AtlG least it's 10 cm wider than either of my 20"/21" monitors.  The 29.8 cmkH height is about the same as mine but your width is different.  This alsoJ would mean that your pixels are about 33% wider than they are tall.  (.388 mm x .291 mm).   ------------------------------  % Date: Sat, 17 Feb 2001 23:54:43 +0000 ) From: Christof Brass <brass@infopuls.com>m' Subject: Re: TFT > 18.1" with 1280x1024-+ Message-ID: <3A8F0F43.1690C1F@infopuls.com>-   John Vottero wrote:  > 8 > "Christof Brass" <brass@infopuls.com> wrote in message( > news:3A8DC3DE.8E147FF3@infopuls.com... > > John Vottero wrote:1 > > > 4 > > > > Question1: is the pixel size of TFT's fixed? > > >1
 > > > Yes. > > > E > > > > Question2: is the quality reduced if the native resolution isu; > > > > 1600x1200 (19.6" TFT) but I'm using only 1280x1024?- > > >-@ > > > Yes.  Don't pay for 1600x1200 unless that's what you want. > > >eK > > > What is the actual display size with your 20" monitor?  An 18.1" flate > panel J > > > is really 18.1".  My 21" monitor only has about 19" of usable space. > >o > > Thanks for your advice.e > >pB > > Calculating/measuring the real display size is not that simple" > > as I haven't done this before.A > > The width is 49.7 cm (should be 19.6"), the height is 29.8 cmuC > > (should be 11.7) and I calculated the diagonal with the formulac@ > > sqrt(width*width + height*height) as 58 cm (should be 22.8")C > > which seems a little bit too much. But I don't know where I didc? > > the mistake. I used a 30 cm (should be 11.8") solid measurei5 > > stick. The monitor is a SAMSUNG SyncMaster 1000p.t > I > Are you sure about the width?  49.7 cm sounds about 10 cm too wide.  AtJI > least it's 10 cm wider than either of my 20"/21" monitors.  The 29.8 cmNJ > height is about the same as mine but your width is different.  This alsoL > would mean that your pixels are about 33% wider than they are tall.  (.388 > mm x .291 mm).  ; You are perfectly right. The width is in fact only 39.7 cm,r9 yielding a diagonal of only 49.6 cm - 19.5". I got a very ? interesting mail directly about a NEC LCD with 20.1" and nativev9 1280x1024 res. The last condition I'm searching for is anA@ additional digital interface. My observation is that screens are: much longer in use than computers. So I want to be able to5 attach this screen later to a digital only interface.y   ------------------------------  % Date: Sat, 17 Feb 2001 21:51:42 +0000A) From: Christof Brass <brass@infopuls.com>g  Subject: Re: UNIX write vs VMS ?, Message-ID: <3A8EF26E.4F126AF1@infopuls.com>   Paul Repacholi wrote:w > - > Christof Brass <brass@infopuls.com> writes:S >  > > Jan Vorbrueggen wrote: > G > > > In Unix, write() is a syscall. In VMS, it is done by the C RTL, IiE > > > presume. In any case, VMS doesn't do such stupid things, so youeH > > > don't have to worry. OTOH, you can keep the loop if properly coded, > > > - it will execute once, and that's it. > H > > Thanks, but I will throw out the loop because on that level the codeD > > can't be the same and I think it clutters the source if I have a > > superflous loop. > E > FOr various reasons, unix systems can 'interupt' a syscall. This istH > not an error in any normal sense of meaning, nothing is broken, exceptH > unix ;), it just throws the problem back into userland and declares it > 'your problem' > F > VMS can do this ( or did... ) in a few odd cases. But it just pushedC > back to PC, and tried again when the process was rescheduled, butt > you will never see it. > E > There is one case you must deal with, and that is quotas. If you dooD > a write that excedes you quota, it fails with EXQUOTA. redoing the8 > write, if can have the overdraft quota!, will succeed. >  > --> > Paul Repacholi                               1 Crescent Rd.,9 > +61 (08) 9257-1001                           Kalamunda.tB >                                              West Australia 60760 > Raw, Cooked or Well-done, it's all half baked.  < Your explanation is in synch with what my colleague told me.@ Typical reasons for UNIX to interrupt a syscall according to him8 are kernel cannot handle the amount of data in one write= operation or signals sent to the process like a user pressingf ctrl-C.i  = I regard this as broken because this should either be handledw= completely by the kernel or at least handled with a differentn@ architecture. To delegate this to the local code which calls the' syscall write() isn't a clean solution.-  = Is it common practice in VMS to handle this EXQUOTA case with < the process having the overdraft quota? I tend to not handle? this and regard this as fatal error not beeing able to write tot a file.o   ------------------------------  % Date: Sun, 18 Feb 2001 04:36:01 +0100n2 From: martin@radiogaga.harz.de (Martin Vorlaender) Subject: Re: version numbers.s; Message-ID: <3a8f4321.524144494f47414741@radiogaga.harz.de>n   I wrote:6 > how about the following procedure that I just wrote?  M One should really never publish a V1.0 version... I put a more robust versiontL of RESEQ.COM on the web at http://www.pdv-systeme.de/users/martinv/reseq.com   cu,b   Martin --J One OS to rule them all       | Martin Vorlaender  |  VMS & WNT programmer7 One OS to find them           | work: mv@pdv-systeme.deuJ One OS to bring them all      |   http://www.pdv-systeme.de/users/martinv/> And in the Darkness bind them.| home: martin@radiogaga.harz.de   ------------------------------  % Date: Sat, 17 Feb 2001 22:42:11 -0600x7 From: "David J. Dachtera" <djesys.nospam@earthlink.net> L Subject: Re: Was Renaming directories. Now: Suitable privileges for a SYSMGR- Message-ID: <3A8F52A3.DA414615@earthlink.net>    Paul Sture wrote:6 > H > In article <3A8DE930.92527852@earthlink.net>, David J. Dachtera wrote:; > > From: "David J. Dachtera" <djesys.nospam@earthlink.net>o > > Newsgroups: comp.os.vmsj+ > > Subject: Re: Renaming directories. How?s) > > Date: Fri, 16 Feb 2001 21:00:00 -0600w > >H > > "Richard D. Piccard" wrote:d > > >aL > > > Glad I could help.  I think comp.os.vms is heavily populated by systemM > > > managers, who may well spend a large fraction of their life with BYPASS  > > > turned on! > >9L > > Actually, I have OPER by default and SETPRV as an authorized priv. Then,I > > in my LOGIN.COM processing, I do SET PROC/PRIV=(ALL,NOBYPASS). I onlyhH > > enable BYPASS to delete directories/trees or (do anything) with DFO. > >i) > Sorry but that's being extremely lazy,    G The results, however, are helpful to maintain security, especially when C users *DON'T* (or can't) enable other privileges during their loginT scripts.  . As for laziness, well, let me put it this way:  A My career-long philosophy has been, and will continue to be, "theeH machine works for me, not the other way around". I only fix things once.D If I fix it, and it doesn't stay fixed, then I made the wrong fix to begin with.   H Some folks enjoy having pagers go off at all hours of the day and night.2 I prefer to sleep and have a life outside of work.   -- S David J. Dachterac dba DJE Systemsg http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/c  F This *IS* an OpenVMS-related newsgroup. So, a certain bias in postings is to be expected.  @ Feel free to exercise your rights of free speech and expression.  F However, attacks against individual posters, or groups of posters, are strongly discouraged.    ------------------------------  % Date: Sun, 18 Feb 2001 07:10:50 +1300 6 From: "antony wardle" <antony.wardle@nospam.met.co.nz>* Subject: Re: which shadow patch do I need?0 Message-ID: <a3zj6.1139$v4.53174@ozemail.com.au>   Thanks but I don't have DSN.  ' Maybe I can get CSC to ring me at home.S   cheers   antony        1 "Scott Vieth" <svieth@wi.rr.com> wrote in message-  news:3A8E9E5C.50406@wi.rr.com...
 > Anthony: >1
 > DO THIS: > 	 > $  mailr >r > MAIL> send/editE > To:     dsn%storagecD > Subj:   pr3: problems with shadowing in mixed-architecture cluster >98 > [describe your exact problem here and then hit CTRL+Z] >d > Get cup of coffee. >v > Wait for response from CSC.p >tJ > Use DSN ITS (or ftp over the Internet) to retrieve the patches mentioned > in the reply from the CSC. >n > -Scott :^) >o > antony wardle wrote: >h- > > what patch do I need to fix this problem?r > > 8 > > The machines that mounted the disk is ds20e 7-2-11h1 > >I/ > > the machines that can't mount the disks ared > >e# > > 7.1 axp machines and a 6.2 vax.V > >b
 > > cheers > >j
 > > antony > >P > >d > > $ > > JET$ mount/cluster dsa70: data_7/ > > %MOUNT-I-MOUNTED, DATA_7 mounted on _DSA70:eF > > %MOUNT-I-ISAMBR, _$1$DGA70: (METJET) is a member of the shadow set? > > %MOUNT-W-RMTMNTFAIL, _DSA70: failed to mount on node METMINp9 > > -MOUNT-F-FILESTRUCT, unsupported file structure levelh? > > %MOUNT-W-RMTMNTFAIL, _DSA70: failed to mount on node METSATc9 > > -MOUNT-F-FILESTRUCT, unsupported file structure levelp? > > %MOUNT-W-RMTMNTFAIL, _DSA70: failed to mount on node METTSTe9 > > -MOUNT-F-FILESTRUCT, unsupported file structure level ? > > %MOUNT-W-RMTMNTFAIL, _DSA70: failed to mount on node METMAXt9 > > -MOUNT-F-FILESTRUCT, unsupported file structure levels? > > %MOUNT-W-RMTMNTFAIL, _DSA70: failed to mount on node METC01i9 > > -MOUNT-F-FILESTRUCT, unsupported file structure levela > > Jw > >o > >t >o   ------------------------------  % Date: Sun, 18 Feb 2001 07:15:19 +1300t6 From: "antony wardle" <antony.wardle@nospam.met.co.nz>* Subject: Re: which shadow patch do I need?0 Message-ID: <o7zj6.1140$v4.53706@ozemail.com.au>  ; Pretty close. They are 18gb disks with a cluster size of 5.i  9 At the moment, I am trying to turn them into non shadowed < disks, as the quorum disk isn't shadowed and can be accessed by the other nodes.o  J Its cluster size is 35. Its a bit annoying this, as I have said that I canD have the new machines installed and running in production by 1-MarchG and, while I have had a few problems, I am on the home straight, having + just introduced these nodes to the cluster.    oh well,   back to  mill then.      antony     <e  K         If, as appears likely from these messages, the disk was initialized I as ODS-5, then only a VMS upgrade on the failing nodes is likely to help.2  H         VMS V7.2 made some changes to the file system; I think the majorH change was a larger BITMAP.SYS so that really big disks could have smallE cluster sizes.   If the disk in question is, say, an 18Gb disk with aIJ cluster size of three, again the only solution may be to upgrade the other nodes to VMS V7.2.  F         You could, as Mark Jilson suggested, apply the appropriate VMSH Shadow patches with all their pre, co, and post requisites to all of theH systems involved.  Depending on the actual cause of the problem it mightI help and is a good idea anyway as I think that most or all of the patchesnG involved are rated "Install_1" which could be translated as manadatory.a   ------------------------------  % Date: Sat, 17 Feb 2001 18:45:37 -0500o2 From: "Richard B. Gilbert" <DRAGON@compuserve.com>* Subject: Re: which shadow patch do I need?7 Message-ID: <200102171845_MC2-C5F6-CD60@compuserve.com>y  J         The other solution us to reinitialize the disks with a clustersiz= eIF that is supported on the lower versions.  This will cost you some diskE space if you have lots of small files but it may be a more acceptableO/ solution than upgrading all your other systems.C  D         I suspect that shadowing, per se, has nothing to do with theJ problem!   Under the old rules the minimum cluster size is something like=   36!!!Y   $ SAY  :=3D WRITE SYS$OUTPUT3 $ SAY F$GETDVI(<DISK>, "MAXBLOCKS") /(255*4096) + 1 J Whatever this calculation gives you is the minimum cluster size for pre V= MS V7.2!   ' Message text written by "antony wardle"  >I  ; Pretty close. They are 18gb disks with a cluster size of 5.n  9 At the moment, I am trying to turn them into non shadowedt< disks, as the quorum disk isn't shadowed and can be accessed by the other nodes.   J Its cluster size is 35. Its a bit annoying this, as I have said that I ca= nCD have the new machines installed and running in production by 1-MarchG and, while I have had a few problems, I am on the home straight, havingc+ just introduced these nodes to the cluster.    oh well,   back to  mill then.*     antony     <-  J         If, as appears likely from these messages, the disk was initializ= edJ as ODS-5, then only a VMS upgrade on the failing nodes is likely to help.=    H         VMS V7.2 made some changes to the file system; I think the majorH change was a larger BITMAP.SYS so that really big disks could have smallE cluster sizes.   If the disk in question is, say, an 18Gb disk with a J cluster size of three, again the only solution may be to upgrade the othe= ri nodes to VMS V7.2.  F         You could, as Mark Jilson suggested, apply the appropriate VMSH Shadow patches with all their pre, co, and post requisites to all of theH systems involved.  Depending on the actual cause of the problem it mightJ help and is a good idea anyway as I think that most or all of the patches=  G involved are rated "Install_1" which could be translated as manadatory.f <l   ------------------------------  % Date: Sat, 17 Feb 2001 17:53:37 -0500e% From: "John Vottero" <John@mvpsi.com> # Subject: Re: www.openvms.compaq.com / Message-ID: <t8u08g1mddbh42@news.supernews.com>-  < "Chris Scheers" <chris@applied-synergy.com> wrote in message- news:3A8DD5D7.B7BC82C6@applied-synergy.com...> > JF Mezei wrote:i > >eJ > > > > return a negative version (in the sense that -32767 to -1 could beI > > > > represented as 32768 - 65535 (or vice versus at a binary level)).i Making* > > > > the version unsigned should be ok. > >aK > > On the other hand, allowing signed version numbers would have some mostc > > interesting features.s > > I > > How about a file system where the current version number is always 1,f andi. > > subsequent files are give -1, -2, -3 etc ? > >fL > > This way, you wouldn't have to worry about ever growing version numbers. An1 > > purge would always get you back to version 1.  > G > What do I do when my job aborts because version -32767 is already outo > there? >a   $ PURGE/KEEP=31000   ------------------------------   End of INFO-VAX 2001.097 ************************