1 INFO-VAX	Sat, 01 Apr 2000	Volume 2000 : Issue 182       Contents:2 Re: A proposed change to the Info-VAX mailing list2 Re: A proposed change to the Info-VAX mailing list? Re: Ancient Backup programs ( was Re: OpenVMS and IP Licensing) 3 Re: D.A.S.C. : Is this DEC product still available? " Dual Processor/program runs twice?& Re: Dual Processor/program runs twice?& Re: Dual Processor/program runs twice?, Re: First come first served: VAX 11/750 (UK), Re: First come first served: VAX 11/750 (UK), Re: First come first served: VAX 11/750 (UK)6 Re: Fw: A proposed change to the Info-VAX mailing list HSD05 / HSD10 DSSI Controller  Re: HSD05 DSSI Controller & Re: Identifying unfound target of GOTO( RE: Microvax 3100-96 4000-106A psychosis Re: Old vax  Re: Sign of the times. RE: Suggestion for authorize Re: Suggestion for authorize Re: Tuning Pathworks/MacIntosh( Re: usr sportster modem dialin vax cxy080 Re: VMS today: % users x-widnows vs VT terminals0 Re: VMS today: % users x-widnows vs VT terminals0 Re: VMS today: % users x-widnows vs VT terminals  F ----------------------------------------------------------------------   Date: 31 Mar 2000 19:52:58 GMT6 From: rickmnospam@oregon.uoregon.edu (Rick Millhollin); Subject: Re: A proposed change to the Info-VAX mailing list + Message-ID: <8c2vmq$i50$1@pith.uoregon.edu>   < > That means - newsgroup comp.os.vms must be also read-only.  O This would be undesirable for me.  I would much rather deal with a news group,  M which I can check when I want, than constant bombardment from a mailing list   of high volume.    --  < Rick Millhollin, Assistant Director for Computing FacilitiesA University of Oregon, Computing Center, Eugene, Oregon 97403-1212 ( Phone: (541)346-1730  FAX: (541)346-4397) E-mail: rickm123@oregon456.uoregon789.edu - <<<<< Remove digits from e-mail address >>>>>    ------------------------------  % Date: Fri, 31 Mar 2000 12:27:45 -0800 0 From: Mark Berryman <Mark.Berryman@Mvb.Saic.Com>; Subject: Re: A proposed change to the Info-VAX mailing list , Message-ID: <38E499C1.1207AA82@Mvb.Saic.Com>    Gotfryd Smolik, VMS lists wrote: > : >  Mark ! You get one little different message because the8 > differrence of info-Vax address (real and what I think > - see at end). > + > On Thu, 30 Mar 2000, Mark Berryman wrote:  > [...]  >  But the second wuestion:  > = >  That means - newsgroup comp.os.vms must be also read-only.   E No, no, a thousand times no.  Please don't make that assumption.  The H news<==>mail gateway is uneffected by this proposal.  There is already a- filter in place there that works pretty well.    > [...]  > 
 >  At end:5 >  In addition will report next problem: the official 1 > Info-Vax server address was for years @SRI.COM, # > what was a alias of MVB.SAIC.COM. - >  But my previous message was returned with: / > --------------------------------------------- = > This Message was undeliverable due to the following reason:  > @ > The following destination addresses were unknown (please check) > the addresses and re-mail the message):  >  > SMTP <Info-VAX@sri.com> / > ---------------------------------------------  > 8 >  The mvb.saic.com adress works. I misses the change of& > official Info-Vax listserv address ?  B The official change of the address took place when I took over the? mailing list from SRI several years ago.  MVB.SAIC.COM was even F registered as the home of the info-vax mailing list at that time.  The= relay at SRI.COM was left in place as a convience to existing H subscribers.  It was recently removed at my request due to the amount of spam being sent to that relay.  
 Mark Berryman    ------------------------------  % Date: Fri, 31 Mar 2000 16:25:04 -0500 ' From: "Bill Todd" <billtodd@foo.mv.com> H Subject: Re: Ancient Backup programs ( was Re: OpenVMS and IP Licensing)( Message-ID: <8c351h$fku$1@pyrite.mv.net>  6 Stephen Eickhoff <eick-hsr@jmusa.com> wrote in message# news:38E4EE76.CAC2C614@jmusa.com...  >  >  > Dan O'Reilly wrote:  > 5 > > At 07:53 AM 3/26/00 -0700, Malcolm Dunnett wrote: 2 > > >In article <8bkbcl$kvp$1@the-fly.zip.com.au>,< > > >    CSABA  HARANGOZO   <csabah@zipworld.com.au> writes: > > > > H > > > >>   [for the terminally pedantic, I realize VMS hasn't always hadD > > > >> BACKUP, but before that we had the RSX utility ( whose name< > > > >> escapes me) that would do the eqivalent of an image backup/restore.] > > > >   > > > >       Ah, memories...8-)H > > > >       Why, it was called BRU, of course. Backup/Restore Utility,5 > > > >       if my old brain recalls it correctly...  > > > > - > > > >       RSX-11M, those were the days... F > > > >                                               Cheers,    Csaba > > > I > > >    IIRC BRU was used to do backups of individual files or directory E > > >trees, but I don't think it could do an "image" backup of a disk B > > >(ie maintaining the same FIDs). The program that did that wasH > > >something different ( Disk Save/Compress perhaps? ). I know we usedH > > >to defragment our RM80 disks by using this program to copy the data fromE > > >one drive to another, then the old pack would be removed and the @ > > >newly created ( and defragmented ) one loaded in its place. > > > E > > >    BRU is still installed on our one remaining VAX, but the RSX 4 > > >emulator no longer works so I can't try it out. > > K > > RSX had 3 backup utilities in its life.  The first was PRESERVE, and it  was F > > really primitive.  It backed up everything, bad blocks, screwed up files,K > > whatever, and restored them the same way.  PRESERVE went away about the & > > time of RSX-11M V4 (or maybe 3.2).   A hollow voice says "rollin"...    - bill   > >  > K > Sounds like BACKUP /PHYSICAL. I used that by mistake when I was replacing  anC > RZ26 instead of /IMAGE. Copied all the bad parity information and 
 everything > 8^P  >  >    ------------------------------  % Date: Fri, 31 Mar 2000 20:25:19 +0100 0 From: "Martin Walker" <martin.walker@virgin.net>< Subject: Re: D.A.S.C. : Is this DEC product still available?< Message-ID: <000c01bf9b46$fb69e3a0$da08fc3e@LT-MW.csf.co.uk>  I I think you will find RCM (which I think replaces DASC / Propatch) on the C Compaq Tools CD in the quarterly CD distribution (recent releases).    -----Original Message-----C From: hoffman@xdelta.zko.dec.nospam <hoffman@xdelta.zko.dec.nospam> 1 To: Info-VAX@Mvb.Saic.Com <Info-VAX@Mvb.Saic.Com>  Date: 24 March 2000 17:53 < Subject: Re: D.A.S.C. : Is this DEC product still available?      > In article <8bff9q$bkn$2@the-fly.zip.com.au>, CSABA  HARANGOZO  <csabah@zipworld.com.au> writes:. : It is Digital A.... S....  C....  something.  ?   DASC (DIGITAL Automatic Systems Configuration, probably to be ?   renamed CASC in the near future) -- related to ProPatch -- is =   available via services.  Circa V5.4 is the current release.   A : ( I searched the net with AltaVista, but nothing was returned). 8 : The report this utility creates is very useful, nifty.  C   Yes, this tool is available as part of Compaq Services offerings.   ? : It lists all the hardware config info, with revision numbers, = : etc; also, I think, it does this for software as well ( not 	 : sure ).   B   On OpenVMS VAX and OpenVMS Alpha, CLUE CONFIG.  SDA> CLUE CONFIG'   on OpenVMS Alpha, and on OpenVMS VAX:        $ CLUE := $CLUE/DISPLAY 
     $ CLUE  D   On OpenVMS Alpha, PCSI (including ECOs on OpenVMS Alpha V7.1-2 andD   later) and VMSINSTAL.HISTORY (which includes ECOs on OpenVMS AlphaE   prior to V7.1-2).  This won't show you everything, but it will show 8   everything that was installed via standard mechanisms.  B   Though DASC/ProPatch does more than list the configuration -- it=   looks to see what patches you should have installed, too...   ) --------------------------- pure personal # opinion --------------------------- L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  # Date: Fri, 31 Mar 2000 23:43:49 GMT * From: "Daniel Bohner" <dbohner@uswest.net>+ Subject: Dual Processor/program runs twice? ? Message-ID: <VKaF4.122022$_G1.1055159@news1.sttls1.wa.home.com>   
 Greetings,  H Recently we migrated our VAXen to Alphas and have experienced one little@ glitch with one of our systems - and perhaps you folks can help.  J Because our Alphas are dual processor - we believe a process can be kickedD on and run twice - once on one processor and before it is complete a2 duplicate process be up and running on the second.  K What switch - either during compile or after - do I have to throw that will > keep the same process from running simultaneously on different  processors(within the same box).   ?? any takers ??  
 Daniel Bohner  Analyst/PublicSafety ADA County Sheriff's Office  Boise, ID  83704 isdan@ac1.co.ada.id.us dbohner@uswest.net   ------------------------------  % Date: Fri, 31 Mar 2000 17:57:18 -0700 5 From: "cstranslations" <cstranslations@email.msn.com> / Subject: Re: Dual Processor/program runs twice? ) Message-ID: <u#840U3m$GA.241@cpmsnbbsa03>   C Making use of the distributed lock manager is one possibility . . .   K Have the program call sys$getsyi to get the node name. Use the node name as J a prefix to some other string (say the program name). Pass that to sys$enqL and queue a system wide lock on that string (resource) before doing anythingG else. Specify no wait. If you don't get the lock then call sys$exit (or ? otherwise exit). Queuing system wide locks does require SYSLCK.   J Everything you need to know about the system services is documented in the system service manuals.    Joe   3 Daniel Bohner <dbohner@uswest.net> wrote in message 9 news:VKaF4.122022$_G1.1055159@news1.sttls1.wa.home.com...  > Greetings, > J > Recently we migrated our VAXen to Alphas and have experienced one littleB > glitch with one of our systems - and perhaps you folks can help. > L > Because our Alphas are dual processor - we believe a process can be kickedF > on and run twice - once on one processor and before it is complete a4 > duplicate process be up and running on the second. > H > What switch - either during compile or after - do I have to throw that will@ > keep the same process from running simultaneously on different" > processors(within the same box). >  > ?? any takers ?? >  > Daniel Bohner  > Analyst/PublicSafety > ADA County Sheriff's Office  > Boise, ID  83704 > isdan@ac1.co.ada.id.us > dbohner@uswest.net >  >  >    ------------------------------  # Date: Sat, 01 Apr 2000 05:19:52 GMT ! From: Ian Parker <parker@gol.com> / Subject: Re: Dual Processor/program runs twice? & Message-ID: <D4F5nCApbY54Ewzm@gol.com>  F In article <VKaF4.122022$_G1.1055159@news1.sttls1.wa.home.com>, Daniel" Bohner <dbohner@uswest.net> writes >Greetings,  > I >Recently we migrated our VAXen to Alphas and have experienced one little A >glitch with one of our systems - and perhaps you folks can help.  > K >Because our Alphas are dual processor - we believe a process can be kicked E >on and run twice - once on one processor and before it is complete a 3 >duplicate process be up and running on the second.  > L >What switch - either during compile or after - do I have to throw that will? >keep the same process from running simultaneously on different ! >processors(within the same box).  >  >?? any takers ??  >  >Daniel Bohner >Analyst/PublicSafety  >ADA County Sheriff's Office >Boise, ID  83704  >isdan@ac1.co.ada.id.us  >dbohner@uswest.net  >  >  >   B It sounds like you're worried about more than one incarnation of aH process running at the same time on the computer.  But it doesn't matterG how many cpus the computer has.  The same risk applies to a single cpu. F There's nothing to stop you running more than one copy of a process at the same time on a single cpu.  E It is within the application that you control whether multiple copies H can run, e.g. when the application starts it checks to see whether it is already running.  E You can do this trivially just by checking whether a specific file is A open, if it is then exit, otherwise open it and continue running.   G You can do this in a more sophisticated fashion by using locks directly  or with other methods.  = But surely you should be doing this already for this program?   F Of course, I've probably missed the point - should we be talking about( spinlocks or something similarly exotic?   Regards    Ian  --  
 Ian Parker   ------------------------------  % Date: Fri, 31 Mar 2000 13:39:38 -0500 + From: Stephen Eickhoff <eick-hsr@jmusa.com> 5 Subject: Re: First come first served: VAX 11/750 (UK) ) Message-ID: <38E4F0EA.1A3FA1E8@jmusa.com>    JF Mezei wrote:    > Bob Kaplow wrote: H > > > I guess you probably have already seen the pictures of the VAX bar7 > > > then, complete with ice tray and IIRC optic rack.  > > Q > > If you are looking, it's at http://www.lpl.arizona.edu/~vance/www/vaxbar.html  > K > Am I the only one here to have spotted a large problem with that VAXBAR ?  >  > $ show system M > BAR/VMS V1.0  on node VAXBAR  28-JUN-1997 18:11:08.82  Uptime 2190 17:43:42 O >   Pid    Process Name    State  Pri      I/O       CPU       Page flts  Pages O > 00001010 REFRIGERATOR    LEF      4     1212   0 00:10:12.23      4125    150 O > 00000800 LIGHTS          COM      6     9121   0 00:34:23.11      1231    343 O > 00000412 BLENDER         HIB      4     3412   0 00:23:49.32      1341    111 O > 00000169 SINK            LEF      3      211   0 00:01:12.66       231    222 
 > $ logout6 >   BARTENDER    logged out at 28-JUN-1997 18:11:23.75 > ' > 1- Where is the "BARTENDER" process ? V > 2- How come none of the processes are in CUR state ?  (yet, Lights in in COM state).M > 3- Shouldn't the REFRIGERATOR be in the undocumented KUL state, and SINK in  > WET states ?  T Screw that... that sucker has been up for six years! I want one! Actually, how about; two? Then I can cluster them and get loaded even faster ;-)    ------------------------------   Date: 31 Mar 2000 23:14:57 GMT, From: Alan Perry <esprit@shell7.ba.best.com>5 Subject: Re: First come first served: VAX 11/750 (UK) . Message-ID: <38e53171$0$206@nntp1.ba.best.com>  G If there is anyone with a Vax (preferably a 750), that they are looking G to get rid of and are not too many states from Washington state, let me E know.  I have been looking for a Vax or a Burroughs B1900 to go in my I machine room and don't even know where to start looking for such a thing.    alan  a In misc.forsale.computers.other.systems Jonathan Hunter <jonathan.hunter@stud.umist.ac.uk> wrote:  : Hi,   N : I have a vaguely complete VAX 11/750 system that I would like to get rid of.A : The notes I have made describing the collection are as follows:    : Cabinet containing:  : RA80 - hard disk drive% : RA60 - disk drive unit - removeable  : MODEL     RA80-CD    : DECserver 200/MC3 : "Software Product Description" - April 1988, "The 5 : DECserver 200 Terminal Server is a network terminal + : switch for Enternet Local Area networks." , : Ports - 8 serial ports; Ethernet AUI port.3 : Sticker with Ethernet address (08-00-2B-11-xx-xx)  : P/N       DSRVB-AB  : C.S. REV  B4        ECO  C0006 : MFG. Cloomel : ------------ : Model:    DSRVB-A   : : RM80. Built differently to rest, i.e. no seperable sides : etc.2 : Unit at top of cabinet; start/stop switches etc.5 : Controller unit underneath, slides out. Two massbus 8 : sockets - one unconnected; presumably for cable. Other7 : has an empty connector in it. Rack full of cards, and ) : ribbon cable going to drive unit above.  : MODEL     RM80-AD    : Tape drive : MODEL     TU81-CA    : 132-column Line Printer 
 : MODEL: LP25  : VARIATION: BA    : VAX itself (11/750)  : MODEL     SV-BXWAA-AD    : Plus miscellanous tapes etc.  I : There is also what appears to be a SCSI controller for the VAX, made by J : SUMMUS Computer Systems. I understand that this is quite a rare item and : might be worth something.   M : If anybody has a need for any of the above, I'm based in Manchester and you " : are welcome to come and collect.  M : If you don't want to make an offer for any of this, then I will allocate it K : on a "first come, first served" basis. However if you do email me with an N : offer (monetary, or offers of exchange for other interesting computer goods)K : then these offers will take precedence over people wanting bits for free.-  , : Let me know if any of this is of interest.  
 : Jonathan   ------------------------------  % Date: Fri, 31 Mar 2000 23:47:29 -0500e) From: Kurt B Mundinger <mslcglrh@fwi.com>l5 Subject: Re: First come first served: VAX 11/750 (UK)o' Message-ID: <38E57F61.A63DEAC1@fwi.com>e  F Like Alan, I would be interested in a free 11/750 or other 780/785 ... 8xxx  H somewhere in the midwest. I am in Northeast Indiana.  Had a working 750 > for many years.  Now have space and necessary Power available.   Thanks - Kurt        Alan Perry wrote:S > I > If there is anyone with a Vax (preferably a 750), that they are looking0I > to get rid of and are not too many states from Washington state, let meaG > know.  I have been looking for a Vax or a Burroughs B1900 to go in myeK > machine room and don't even know where to start looking for such a thing.T >  > alan > c > In misc.forsale.computers.other.systems Jonathan Hunter <jonathan.hunter@stud.umist.ac.uk> wrote:- > : Hi,- > P > : I have a vaguely complete VAX 11/750 system that I would like to get rid of.C > : The notes I have made describing the collection are as follows:: > " snip details of 11/750 hardware UK  O > : If anybody has a need for any of the above, I'm based in Manchester and youo$ > : are welcome to come and collect. > O > : If you don't want to make an offer for any of this, then I will allocate it M > : on a "first come, first served" basis. However if you do email me with an P > : offer (monetary, or offers of exchange for other interesting computer goods)M > : then these offers will take precedence over people wanting bits for free.: > . > : Let me know if any of this is of interest. >  > : Jonathan   ------------------------------  % Date: Fri, 31 Mar 2000 12:03:03 -0800-0 From: Mark Berryman <Mark.Berryman@Mvb.Saic.Com>? Subject: Re: Fw: A proposed change to the Info-VAX mailing list:, Message-ID: <38E493F7.36F541CD@Mvb.Saic.Com>    Gotfryd Smolik, VMS lists wrote: > + > On Fri, 31 Mar 2000, Mark Berryman wrote:t > [...] J > +The code has access to the envelope header (the value in the MAIL FROM:E > +command) and the contents of the From: header in the header of the K > +message itself, as well as the contents of the Reply-To: header.  It can / > +be told to compare against any or all three.l > @ >  Ach, yes, that answers my (seconds before getting the message' > have send the same question !) query.iA >  But: can the code allow checking with one user-settable header  > differrent that Reply-To: ?  >  Why ?; >  That is not important to me (because I have real "From:"e; > address) but can imagine, that one can require differrent 4 > Reply-To: (as I) and MUST have differrent "From:".7 >  The news (group comp.os.vms) problem still exists...-    C Yes, I can pick any header, or set of headers, to check.  So, if itl> turns out that folks have enough control over their mailers toH explicitly add a particular (but otherwise unused) header, then I see noG problem in supporting that as well.  In fact, if this turns out to be a C popular choice, it might even be sufficient to simply check for theiD presence of that header and not worry about the From: address(es) at all.  
 Mark Berrymanv   ------------------------------  % Date: Fri, 31 Mar 2000 12:49:48 -0800e3 From: "Wolf, Gerald J" <Gerald.Wolf@F22.Boeing.com>t& Subject: HSD05 / HSD10 DSSI ControllerQ Message-ID: <C16B19ADF2A3D111882C00805FE6C65004FF363E@xch-f22bh-01.ds.boeing.com>   L I have two systems I now support.  One uses an HSD05 controller the other an HSD10 controller.-L The one with the HSD05 controller already has 2 RZ40-VA(9GB narrow) drive in it.@. The HSD10 10 only has 4GB narrow drives in it.  I COMPAQ says 9GB narrow drives are not supported.  The one system with thee HSD05 controllerJ has had the 9GB narrow drives in it with no problems for as long as I have been here, 1.5 years.e  - What type of drives can each controller take?M HSD05? HSD10?   ------------------------------  % Date: Fri, 31 Mar 2000 14:30:51 -0600 * From: WILLIAM WEBB <WWEBB1@email.usps.gov>" Subject: Re: HSD05 DSSI Controller- Message-ID: <0033000020102620000002L002*@MHS>d  H =0AThere is a VAX4000-500a here with a BA350 shelf and HSD05 DSSI Contr= oller in it.)  H The disk shelf currently has (1) 2GB, (1) 4GB and (2) 9GB narrow drives=  in  it.   H The 2GB narrow drive keeps filling up with important development data, = so I want, to replace the 2GB narrow with a 9GB narrow.  H Do I have to configure the slot the 2GB disk is in to accept a larger 9= GB disk?    --- begin www response ---  	      Yes.   +      If memory serves me right, you have to         1.  delete the 2GB disk,       2.  insert the 9GB disk!      3.  and do an AUTOCONFIGURE.b   --- pause WWW response ---  : Will this shelf accept 9GB , 18GB and 32GB VW type drives?   --- resume WWW response ---C        350s only do narrow.   F      They'll FIT in there, but it'd be kinda like driving your Porsche      around in first gear.  H      Some of the BA356s do wide okay, but off the top of my head, I'll = betd)      you'd need an HSD10 to control them.         WWWebbU   --- end WWW response ---=e   ------------------------------  % Date: Fri, 31 Mar 2000 17:39:17 -0500i0 From: JF Mezei <jfmezei.spamnot@vl.videotron.ca>/ Subject: Re: Identifying unfound target of GOTO / Message-ID: <38E52912.540E53D1@vl.videotron.ca>    briggs@eisner.decus.org wrote:G > Easy fix.  Instead of directly invoking the problematic file from the I > batch job or captive command file, submit a jacket procedure (or direct ; > LGICMD to a jacket procedure) that calls the problem filea  L Ok, I am confused. How does executing TEST.COM which calls TEST2.COM cause aL different behaviour with regards to displaying the error message about GOTO & compared to executing TEST2 directly ?   ------------------------------  % Date: Fri, 31 Mar 2000 15:15:40 -0400R1 From: "Boyle, Darren" <boyledj@bankofbermuda.com> 1 Subject: RE: Microvax 3100-96 4000-106A psychosissK Message-ID: <F150836441C5D311A11700508B6FF01A5951F9@bdant024.bda.bobda.com>)   Hi,   E 	Yes I've seen this behaviour on a MV3100 in Australia, I also talked L to CSC and they said it was something imprinted on the board (can't rememberH what now) if it was Firmware or an actual chip.  It will not cause you a problem in my experience.u - Darren   > ----------2 > From: 	Jay T. McCanta[SMTP:jmccanta@immunex.com]' > Sent: 	Friday, March 31, 2000 2:52 PMH > To: 	Info-VAX@Mvb.Saic.Com0 > Subject: 	Microvax 3100-96 4000-106A psychosis > G > Recently we purchased a used MicroVax 3100-96.  That's what the order G > says, that's what the model number on the back of the unit describes,iF > but the HW_NAME says it's a VAX 4000-106A.  So what gives?  I talkedB > to a Compaq tech about it and he says there is a listing for theB > 3100-96 in the VMS hardware tables so he didn't know why the box > didn't identify correctly. >  > I am running OpenVMS 7.1 a > HW_NAME  VAX 4000-106A > HW_MODEL 487 > ) > Has anyone seen this?  Is it a problem?f > 
 > Jay Mccanta 
 > Immunex G > -===================================================================-F; > Jay McCanta              |  My opinions are barely my own = > System Administrator     |  My employer doesn't necessarilyn) > Immunex Corp.            |  share them.)G > -===================================================================-V >     F **********************************************************************C This message and any files transmitted with it are confidential andoJ may be privileged and/or subject to the provisions of privacy legislation.M They are intended solely for the use of the individual or entity to whom they L are addressed. If the reader of this message is not the intended recipient, B please notify the sender immediately and then delete this message.I You are notified that reliance on, disclosure of, distribution or copyinge of this message is prohibited.   Bank of BermudaeF **********************************************************************   ------------------------------  # Date: Fri, 31 Mar 2000 19:10:03 GMT 9 From: stu@c49395-a.wodhvn1.mi.home.com (Stuart R. Fuller)l Subject: Re: Old vax% Message-ID: <qsq2c8.ijf.ln@localhost>l  / Michael Austin (maustin@nc.prestige.net) wrote:cC : Actually you may not be able to use those drives in your PC.  TheuJ : firmware may be the VAX-Only variant.  Why not use VMS at home... with 4I : free web servers out there, it would make a great server.  If you don'ta : want them, send them to me.s  I Umm, exactly what "VAX-Only" variant of SCSI disk drives might they be?  a  K The systems in question likely have RZ23, RZ24, RZ25 and/or RZ26 disks, andbM each model of those disks have worked quite well in my PC running Windows and: Linux.           Stut   ------------------------------  # Date: Fri, 31 Mar 2000 23:43:54 GMT/( From: Terry Kennedy <terry@gate.tmk.com> Subject: Re: Sign of the times.u' Message-ID: <FsB8L6.9yr@spcuna.spc.edu>   > In comp.org.decus Tim Shoppa <shoppa@trailing-edge.com> wrote:A > I agree, it's good news (though a DS10 is probably overkill foryH > the simple task of serving up files - a lowly VS3100-30 can come closeE > to saturating a 10 Mbit/s Ethernet, and a DS10 has what, a thousand ! > times as much CPU horsepower?).s  D   Well, there was this "killer deal" on DS10's, and I wanted to haveF matching machines in a cluster for robustness, and I got carried away, and...   > Will the machine have a  > "*.decus.org" address?  E   I have no objection to the DECUS folks CNAME-ing a DECUS address to.G point at it, but there will be things on there (like the humor archive)nH that they may not consider appropriate. Of course, SPC never had a prob-G lem with Elf Sternberg's Tales of Pendor archive on ftp.spc.edu, thoughrH a few of the mirror sites asked "what's this porno doing on the server!"  + > Will it be publicly accessible or will itu< > require a password to access?  I was talking with Rochelle  I   Free to all. No passwords - either anonymous FTP or HTTP w/ no cookies,p no passwords, etc.  D > Lauer a while back and she was describing a similar project insideG > DECUS, but they were talking about requiring a password to get access 9 > (which I guess would limit access to US DECUS members).@  F   If they're funding something, they can set the policies. And if it'sD material only available from DECUS and charging for it helps support DECUS, that's a Good Thing.:  D   I think part of that may be waiting for the DECUServe migration to. the DS20, which is another one of my projects.  - 	Terry Kennedy             http://www.tmk.coms5         terry@tmk.com             Jersey City, NJ USAe   ------------------------------  # Date: Fri, 31 Mar 2000 19:44:23 GMTo* From: kuhrt@eisner.decus.org (Marty Kuhrt)% Subject: RE: Suggestion for authorizep' Message-ID: <2000Mar31.144423.1@eisner>c  k In article <D30A62ABC710D211AEE100A0C9D615EE316355@REAES2>, "POWERS, John" <John.POWERS@sema.co.uk> writes:iF > I have a much better (IMHO) suggestion for an amendment to authorizeG > that will cut through all these different customisation requirements.n > E > The run time interface to sysuaf is in desperate need (and has beensA > for YEARS) of the ability to add and delete records, as well asf > amending records.D > F > The absence of this facility makes a terrible mess of any controlled> > way of allowing departmental managers the ability to add andC > remove employees. It is particularly relevant, as the managerial,tC > people-oriented staff tend not to be the confident tecchie-types.e@ > These people need a nice captive environment that will ask theD > right questions and do all the work for them. This can do whateverA > the local requirements demand - add new UICs at end/fill in then9 > UIC blanks, auto-create/delete directories if required,e7 > delete/forward email - ensuring that the manager onlyg6 > creates/deletes users in their own group, etc. etc.. > ? > The best way to do this would be with a privileged installed  ? > image, that can check who's doing what, and ask all the righth
 > questions. e   [and so forth]  A My previous employer, Symark Software, was, at one point, sellinge? two such products.  One was HIS Software's XUAFMaestro, a Motifs? based account management package that could connect to any node-= in the network and diddle the UAF, RIGHTSLIST, mail profiles, ? diskquotas, etc.  You could set it up so that Joe Manager couldtA only affect accounts you wanted him to access, and narrow it down8? to specific fields, if you wanted.  Thus, it was easy to set up A help desk access to password field only, etc.  It could be set up @ to archive all activity and even roll back changes if you made a? big goof.  You could also have it trigger command procedures to/? launch pre and post processing for most actions.  When deletinge> accounts you could have it remove files, update rights, remove3 mail profile info, etc, all push button selectable.1  ? They also had a character cell product using SMG menus that hadC? the same functionality.  That one was maintained and updated in 8 house (by me for a while).  It was called UserManager.    @ I don't know if they're still in business.  If they are, I don't= know if they still sell the stuff.  Needless to say I have no ! involvement with them whatsoever.    ------------------------------  % Date: Fri, 31 Mar 2000 23:14:20 -0600 ) From: "John E. Malmberg" <wb8tyw@qsl.net>1% Subject: Re: Suggestion for authorizeE7 Message-ID: <17ef01bf9b99$26b59840$020a0a0a@xile.realm>   6 Mike Rechtman <michael.rechtman@digital.compaq> wrote:  > > At a previous employers site we had a nightly batch job that? > searched for free UICs according to the local specifications,i> > wrote them to a file (indexed file, using DCL) and the local? > version of adduser.com would pick from there. We never needed-+ > more than 50 new UICs on any given day...m  H It is relatively easy to set up a captive account that can use PathworksG Server to log into an NT domain.  You can hide the password in a RightsfH Identifier that is granted to the account, so that no command procedures0 need to be changed when you change the password.  L A batch job can then be used to inspect the list of NT groups with "VMS " asK their prefix and then create / update / disable VMS accounts based on theirh NT group membership.  J Or of course, if you have better account support people on the VMS side ofH the house, you can use these scripts to manage NT accounts based on what" attributes that a VMS account has.  G Coupled with external authentication, you can elimate those calls also.a  J It is a good way to trick your NT administration people into also managingJ the accounts for the VMS systems.  And this method removes having to train the account people.,   -John  wb8tyw@qsl.network   ------------------------------  % Date: Fri, 31 Mar 2000 20:33:59 -0500.% From: Bob Harris <harris@zk3.dec.com>A' Subject: Re: Tuning Pathworks/MacIntosh 3 Message-ID: <310320002033595623%harris@zk3.dec.com>V  / [[ This message was both posted and mailed: see-;    the "To," "Cc," and "Newsgroups" headers for details. ]],  D In article <5gTE4.1309$h81.23418@typhoon.aracnet.com>, Zane H. Healy# <healyzh@shell1.aracnet.com> wrote:n  K X Something I've noticed is that it looks like when you open the folder up,lN X pathworks not only looks at that folder, but every folder under it.  LookingM X from the VMS side in directories I *know* have never been opened on the Mac + X I'm seeing 'MSAF$RESOURCES' directories. O   Each Mac must disable the G Finder->Preferences->Views->Calculate_Folder_Sizes option.  This Mac OS C Finder feature causes the Mac to recursivily walk all the directoryr+ tree starting with the folder being opened..  uF X So unless I'm doing something stupid here, it looks like part of theK X question might be, is there a setting to only have it look at the currentn  X folder when you open a folder.  % On the Mac, yes.  The above mentionedn: Finder->Preferences->Views->Calculate_Folder_Sizes option.  G On the PATHWORKS for OpenVMS (Macintosh) DECshare file server, no.  The D DECshare server just does what the Mac asks it.  The DECshare serverE will not, on its own, walk a directory tree.  The most that it can do F is return information about all the files in 1 and only 1 directory atC a time (AFPEnumerate) at the request of the Mac.  DECshare does not0G have a [.dir...] style operation and there is not such operation in thei! AppleShare Filing Protocol (AFP).g  K X Looks like it's time to hit the books and see if there is such an option.e  = The operations that the Mac can ask the file server to do are G documented in the bootk "Inside AppleTalk, Second Edition", Chapter 13.p    M X > The speed when transferring files is all right in both directions though.  X K X I am noticing speed problems unfortunatly.  If my calculations are right,gP X I'm only getting about 160K/sec on writes, while if I FTP the file I get aboutL X 660K/sec.  However, I'm still on a 10Mbit interface.  I hope to upgrade toH X 100Mbit on Saturday assuming the cards arrive like they're supposed toK X tomorrow.  Note, this was a planned upgrade, not a brute force attempt atr X correcting the problem :^)  D FTP will use 1400 byte packets (ethernet max packet size), AppleTalkD will use a maximum of 600 byte packets (LocalTalk max packet size).   D Writes from the Mac to the server also require a setup request.  TheD Mac says I want to write 'n' bytes (AFPWrite).  The server allocatesE the buffer and sends an ASPWrtContinue call back to the Mac.  The MacmG then sends from 1 to 8 600 byte packets to the server (with overhead inoE each packet this results in around 4500 bytes of data more or less).  3 The server then acknowledges the completed write.  g  D The AppleTalk protocol is not as efficient as other protocols.  PlusD each message has some finite turn-around time at each end that slows things down.  @ This is one of the reasons Apple has started using TCP/IP in itsF server, but that all happen after Digital stopped developing DECshare.   ------------------------------  % Date: Fri, 31 Mar 2000 14:09:38 -0500 + From: Stephen Eickhoff <eick-hsr@jmusa.com>m1 Subject: Re: usr sportster modem dialin vax cxy08M) Message-ID: <38E4F7F2.D67055E8@jmusa.com>    PaulMac2@aol.com wrote:h  D > Finally got the modem to work, after turning on CD override (&C0),D > as well as modem-controlled DSR (&S1).  Could not get a high-speedB > connection though, and found that this particular model does notC > work real well with servers <http://support.microsoft.com/supporteD > /kb/articles/q139/4/70.asp>.  And it's not firmware upgradable :-( >t2 > Conclusion: in this case, I got what I paid for.  F I was about to suggest doing that. We have a Sportster x2 working fineH with a DECServer 300 to a VAX 4000-705a. Maximum port speed on the TS isD 19200, so we are limited by that. It's certainly sufficient for a VT session.   ------------------------------  # Date: Fri, 31 Mar 2000 19:29:12 GMTn* From: Gord Coulman <gcoulman@ccinet.ab.ca>9 Subject: Re: VMS today: % users x-widnows vs VT terminalse, Message-ID: <38E4F5B9.5D0970B5@ccinet.ab.ca>  _ I don't understand.  You kept the VT-500 series keyboard?  It plugs into your PC?  I have neveriU seen a VT-500, but the 420's we have around here don't have anything like an AT-styleh* keyboard.  I wonder where I could get one?   Gord.r   David A Froble wrote:   G > I can scrool back a thousand lines or more, I can cut/copy and paste,0M > and I have retained the VT-500 series keyboard.  A few function and numeric:Q > keypad keys are not mapped correctly, but I believe they could be, I'm just too3R > lazy.  For this purpose it's a better VT terminal.  Of course, if I had to use aQ > peecee keyboard you'd hear a different story.  (You got to wonder, watching alllI > the keyboard design advances through the 80s, just to revert to junk ona' > peecees!  One of my biggest bitches!)r   ------------------------------  % Date: Fri, 31 Mar 2000 15:12:26 -0500a[ From: jamese@beast.dtsw.army.mil (Ed James, TCS Inc, 410-295-1919, ed.james@telecomsys.com)s9 Subject: Re: VMS today: % users x-widnows vs VT terminals?0 Message-ID: <00033115122667@beast.dtsw.army.mil>  K Gord Coulman <gcoulman@ccinet.ab.ca> wrote on Fri, 31 Mar 2000 19:29:12 GMT $ in <38E4F5B9.5D0970B5@ccinet.ab.ca>:  P > I don't understand.  You kept the VT-500 series keyboard?  It plugs into your  PC?  I have neverHO > seen a VT-500, but the 420's we have around here don't have anything like an   AT-style, > keyboard.  I wonder where I could get one?  L My company bought me a LK46W-L2 keyboard for my NT box. We use eXcursion for6 NT to open DECWindows on an Alpha running VMS 7.1-1H1.  M It works like a champ, after a little fiddling with DECW$TERMINAL_DEFAULT.DAT C to get the escape, angle, comma, and period keys to work as I like.    > Gord.  >  > David A Froble wrote:  > I > > I can scrool back a thousand lines or more, I can cut/copy and paste, G > > and I have retained the VT-500 series keyboard.  A few function andiJ > > numeric keypad keys are not mapped correctly, but I believe they couldG > > be, I'm just too lazy.  For this purpose it's a better VT terminal.oG > > Of course, if I had to use a peecee keyboard you'd hear a differentoI > > story.  (You got to wonder, watching all the keyboard design advances J > > through the 80s, just to revert to junk on peecees!  One of my biggest
 > > bitches!)    Amen.1      : Ed James                           ed.james@telecomsys.com5 TeleCommunications Systems, Inc.   voice 410-295-1919g5 275 West Street, Suite 400         fax   410-280-1094s Annapolis, MD 21401-1740   ------------------------------  # Date: Fri, 31 Mar 2000 22:45:24 GMTa+ From: tom@automatedtech.com (Tom Hickerson)k9 Subject: Re: VMS today: % users x-widnows vs VT terminalsh2 Message-ID: <38e5298e.1372483@news.mindspring.com>  F On Fri, 31 Mar 2000 19:29:12 GMT, Gord Coulman <gcoulman@ccinet.ab.ca> wrote:  ` >I don't understand.  You kept the VT-500 series keyboard?  It plugs into your PC?  I have neverV >seen a VT-500, but the 420's we have around here don't have anything like an AT-style+ >keyboard.  I wonder where I could get one?M >o  D The current model is an LK461. It has all the DEC VT keys (Help, Do,E etc) and a PS/2 connector ( the LK450 had an AT connector). Its workse= great with the current version of Reflections.  It is sold bye8 Compaq but could be made by someone  else ( Boundless ?)   ------------------------------   End of INFO-VAX 2000.182 ************************