0 INFO-VAX	Tue, 09 Jan 2001	Volume 2001 : Issue 17      Contents: Adding link libraries to DECC ! Re: Adding link libraries to DECC ! Re: Adding link libraries to DECC ! Re: Adding link libraries to DECC ! Re: Adding link libraries to DECC 6 Re: Asking an app to temporarily relinquish a resource6 Re: Asking an app to temporarily relinquish a resource6 Re: Asking an app to temporarily relinquish a resource6 Re: Asking an app to temporarily relinquish a resource6 Re: Asking an app to temporarily relinquish a resource( Re: Compaq stockholders affecting policy( Re: Compaq stockholders affecting policy4 Re: Compaq: A simple, affordable clustering solution4 Re: Compaq: A simple, affordable clustering solution4 Re: Compaq: A simple, affordable clustering solution4 Re: Compaq: A simple, affordable clustering solution4 Re: Compaq: A simple, affordable clustering solution4 Re: Compaq: A simple, affordable clustering solution4 Re: Compaq: A simple, affordable clustering solution4 Re: Compaq: A simple, affordable clustering solution4 Re: Compaq: A simple, affordable clustering solution4 Re: Compaq: A simple, affordable clustering solution4 Re: Compaq: A simple, affordable clustering solution4 Re: Compaq: A simple, affordable clustering solution4 Re: Compaq: A simple, affordable clustering solution4 Re: Compaq: A simple, affordable clustering solution4 Re: Compaq: A simple, affordable clustering solution4 Re: Compaq: A simple, affordable clustering solution$ CSWS (Apache) update 1.0-1 available( Re: CSWS (Apache) update 1.0-1 available( Re: CSWS (Apache) update 1.0-1 available Re: DEC 3000 model 300 Re: DEC 3000 model 300 Re: DEC 3000 model 300 Re: DEC 3000 model 300" Re: DEC-AXPVMS-VMS712_SYS-V0200--4 Re: Decserver 700 ! Re: Flackey fibre channel support ! Re: Flackey fibre channel support  FreeVMS  Re: FreeVMS  Re: FreeVMS  Re: FreeVMS " FS: Digital AlphaStation 600 5/266  Re: FW: start/que/search problem Re: Happy New Years  Re: How many..J HW/SW for Chip Fabs (was: Compaq: A simple, affordable clusteringsolution) Re: Microsoft Message Queue * Re: Need KZTSA information / documentation Re: OpenVMS opportunities  Re: OpenVMS opportunities  Re: OpenVMS opportunities  Re: OpenVMS opportunities  Re: OpenVMS opportunities  Re: OpenVMS opportunities 	 Re: samba 	 Re: samba  Software beta testers required; Re: vax basic - can someone remind me how this works again? 6 Re: [Q] Which model Exabyte in TKZ09 and TKZ15 drives?6 Re: [Q] Which model Exabyte in TKZ09 and TKZ15 drives?+ Re: [TCPIP V5.0A ECO1] BIND Server errors ? + Re: [TCPIP V5.0A ECO1] BIND Server errors ? + Re: [TCPIP V5.0A ECO1] BIND Server errors ? P Re: [Update] APACHE (CSWS) + MOD_PERL = No private process logicals definablein P Re: [Update] APACHE (CSWS) + MOD_PERL = No private process logicals definablein   F ----------------------------------------------------------------------  $ Date: Mon, 8 Jan 2001 19:40:19 -05009 From: "Steven Shamlian" <not dot an at earthling dot net> & Subject: Adding link libraries to DECC2 Message-ID: <93dmn4$9ap$1@slb7.atl.mindspring.net>   Hello,I I'm running DEC C V6.0-001 on a MicroVAX 3100/40 running OpenVMS V7.2 and K would like this code to compile very, very much.  I need to use VMSLIB, and F found that the package contains an .OLB file and a (familiar) .H file.K Noting that many of the same were in SYS$LIBRARY: , I placed VMSLIB.OLB and  VMSLIB.H there and triedA $ link /exe=plredt.exe [.obj]bitvectors, [.obj]edit, [.obj]plredt 4 (all these files have a #include <vmslib.h> in them)  I This caused link errors regarding not being able to find CLEAR_SCREEN and K CURSOR functions from VMSLIB, as if the file was not found by the compiler.   % No luck.  I then tried the following: B $ link /exe=plredt.exe [.obj]bitvectors, [.obj]edit, [.obj]plredt,1 DISK$SYSTEM:[VMS$COMMON.SYSLIB]vmslib.olb/library   K This produced a lot of link errors whining about various functions found in K stdlib.h and string.h that vmslib wanted.  There must be a better way.  I'd E like the compiler to be as aware of VMSLIB.H as it is, say, STDIO.H .   < I hope someone can tell me how to get this thing to compile. Thanks in advance, =+=Steven Shamlian=+=    ------------------------------  $ Date: Mon, 8 Jan 2001 20:08:38 -0500% From: "John Vottero" <John@mvpsi.com> * Subject: Re: Adding link libraries to DECC/ Message-ID: <t5kp60fop54b81@news.supernews.com>   D "Steven Shamlian" <not dot an at earthling dot net> wrote in message, news:93dmn4$9ap$1@slb7.atl.mindspring.net... > Hello,K > I'm running DEC C V6.0-001 on a MicroVAX 3100/40 running OpenVMS V7.2 and I > would like this code to compile very, very much.  I need to use VMSLIB,  and H > found that the package contains an .OLB file and a (familiar) .H file.I > Noting that many of the same were in SYS$LIBRARY: , I placed VMSLIB.OLB  and  > VMSLIB.H there and triedC > $ link /exe=plredt.exe [.obj]bitvectors, [.obj]edit, [.obj]plredt 6 > (all these files have a #include <vmslib.h> in them) > K > This caused link errors regarding not being able to find CLEAR_SCREEN and C > CURSOR functions from VMSLIB, as if the file was not found by the 	 compiler.  > ' > No luck.  I then tried the following: D > $ link /exe=plredt.exe [.obj]bitvectors, [.obj]edit, [.obj]plredt,3 > DISK$SYSTEM:[VMS$COMMON.SYSLIB]vmslib.olb/library  >   , You're on the right track with that command.  J > This produced a lot of link errors whining about various functions found inH > stdlib.h and string.h that vmslib wanted.  There must be a better way. I'd G > like the compiler to be as aware of VMSLIB.H as it is, say, STDIO.H .  >   K "whining about various functions" isn't good enough.  Post the errors or at & least a closer representation of them.  : My guess is that VMSLIB was compiled with /NOPREFIX.  See:   $ HELP CC /PREFIX  $ HELP CC LINK_LIBRARIES   ------------------------------  $ Date: Mon, 8 Jan 2001 21:21:07 -05009 From: "Steven Shamlian" <not dot an at earthling dot net> * Subject: Re: Adding link libraries to DECC2 Message-ID: <93dslj$7of$1@slb1.atl.mindspring.net>   [snip]L > > This produced a lot of link errors whining about various functions found inJ > > stdlib.h and string.h that vmslib wanted.  There must be a better way. I'd I > > like the compiler to be as aware of VMSLIB.H as it is, say, STDIO.H .  > >  > J > "whining about various functions" isn't good enough.  Post the errors or at( > least a closer representation of them.  L Ok, you asked for it.  This is long, but mostly because of all the instances of the functions called.) Note that DISK$HOBBES is the system disk.   B $ link /exe=plredt.exe [.obj]bitvectors, [.obj]edit, [.obj]plredt,1 DISK$HOBBES:[VMS$COMMON.SYSLIB]vmslib.olb/library   & %LINK-W-NUDFSYMS, 4 undefined symbols: %LINK-I-UDFSYM,  FFLUSH  %LINK-I-UDFSYM,  PRINTF  %LINK-I-UDFSYM,  STRLEN  %LINK-I-UDFSYM,  TOLOWER5 %LINK-W-USEUNDEF, undefined symbol TOLOWER referenced !  in psect $CODE offset %X0000018C B  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;15 %LINK-W-USEUNDEF, undefined symbol TOLOWER referenced !  in psect $CODE offset %X000001A9 B  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;14 %LINK-W-USEUNDEF, undefined symbol STRLEN referenced!  in psect $CODE offset %X000001F2 B  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;14 %LINK-W-USEUNDEF, undefined symbol PRINTF referenced!  in psect $CODE offset %X00000281 B  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;14 %LINK-W-USEUNDEF, undefined symbol FFLUSH referenced!  in psect $CODE offset %X0000028E B  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;14 %LINK-W-USEUNDEF, undefined symbol PRINTF referenced!  in psect $CODE offset %X000002A5 B  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;14 %LINK-W-USEUNDEF, undefined symbol FFLUSH referenced!  in psect $CODE offset %X000002B2 B  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;14 %LINK-W-USEUNDEF, undefined symbol PRINTF referenced!  in psect $CODE offset %X000002C9 B  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;14 %LINK-W-USEUNDEF, undefined symbol FFLUSH referenced!  in psect $CODE offset %X000002D6 B  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;14 %LINK-W-USEUNDEF, undefined symbol PRINTF referenced!  in psect $CODE offset %X000002ED B  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;14 %LINK-W-USEUNDEF, undefined symbol FFLUSH referenced!  in psect $CODE offset %X000002FA B  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;14 %LINK-W-USEUNDEF, undefined symbol PRINTF referenced!  in psect $CODE offset %X00000311 B  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;14 %LINK-W-USEUNDEF, undefined symbol FFLUSH referenced!  in psect $CODE offset %X0000031E B  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;14 %LINK-W-USEUNDEF, undefined symbol PRINTF referenced!  in psect $CODE offset %X00000335 B  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;14 %LINK-W-USEUNDEF, undefined symbol FFLUSH referenced!  in psect $CODE offset %X00000342 B  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;14 %LINK-W-USEUNDEF, undefined symbol PRINTF referenced!  in psect $CODE offset %X00000365 B  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;14 %LINK-W-USEUNDEF, undefined symbol FFLUSH referenced!  in psect $CODE offset %X00000372 B  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;14 %LINK-W-USEUNDEF, undefined symbol PRINTF referenced!  in psect $CODE offset %X00000389 B  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;14 %LINK-W-USEUNDEF, undefined symbol FFLUSH referenced!  in psect $CODE offset %X00000396 B  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;14 %LINK-W-USEUNDEF, undefined symbol PRINTF referenced!  in psect $CODE offset %X000003AD B  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;14 %LINK-W-USEUNDEF, undefined symbol FFLUSH referenced!  in psect $CODE offset %X000003BA B  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;14 %LINK-W-USEUNDEF, undefined symbol PRINTF referenced!  in psect $CODE offset %X000003D1 B  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;14 %LINK-W-USEUNDEF, undefined symbol FFLUSH referenced!  in psect $CODE offset %X000003DE B  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;14 %LINK-W-USEUNDEF, undefined symbol PRINTF referenced!  in psect $CODE offset %X000003F5 B  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;14 %LINK-W-USEUNDEF, undefined symbol FFLUSH referenced!  in psect $CODE offset %X00000402 B  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;14 %LINK-W-USEUNDEF, undefined symbol PRINTF referenced!  in psect $CODE offset %X00000419 B  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;14 %LINK-W-USEUNDEF, undefined symbol FFLUSH referenced!  in psect $CODE offset %X00000426 B  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;14 %LINK-W-USEUNDEF, undefined symbol PRINTF referenced!  in psect $CODE offset %X0000043D B  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;14 %LINK-W-USEUNDEF, undefined symbol FFLUSH referenced!  in psect $CODE offset %X0000044A B  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;14 %LINK-W-USEUNDEF, undefined symbol PRINTF referenced!  in psect $CODE offset %X00000461 B  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;14 %LINK-W-USEUNDEF, undefined symbol FFLUSH referenced!  in psect $CODE offset %X0000046E B  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;1   ------------------------------   Date: 8 Jan 2001 22:13:24 -0500 2 From: malmberg@eisner.decus.org (John E. Malmberg)* Subject: Re: Adding link libraries to DECC+ Message-ID: <qqYZjr8iHUZv@eisner.decus.org>   2 In article <93dmn4$9ap$1@slb7.atl.mindspring.net>,; "Steven Shamlian" <not dot an at earthling dot net> writes:  > Hello,: > I'm running DEC C V6.0-001 on a MicroVAX 3100/40 running8 > OpenVMS V7.2 and would like this code to compile very,6 > very much.  I need to use VMSLIB, and found that the9 > package contains an .OLB file and a (familiar) .H file.   = > Noting that many of the same were in SYS$LIBRARY:, I placed ) > VMSLIB.OLB and VMSLIB.H there and tried C > $ link /exe=plredt.exe [.obj]bitvectors, [.obj]edit, [.obj]plredt 6 > (all these files have a #include <vmslib.h> in them) >  <snip>' > No luck.  I then tried the following: D > $ link /exe=plredt.exe [.obj]bitvectors, [.obj]edit, [.obj]plredt,3 > DISK$SYSTEM:[VMS$COMMON.SYSLIB]vmslib.olb/library  > D > This produced a lot of link errors whining about various functionsC > found in stdlib.h and string.h that vmslib wanted.  There must be D > a better way.  I'd like the compiler to be as aware of VMSLIB.H as > it is, say, STDIO.H .  > > > I hope someone can tell me how to get this thing to compile. > Thanks in advance,  ; Please reference the DEC C compiler documentation available 
 online at:  7 http://www.openvms.compaq.com/commercial/c/c_index.html   ; Also of interest would be the command $HELP CC/DECC/INCLUDE   > When you are compiling, the complier is not concerned with theD location of any OLB files that are used with the linking.  The DEC C? compiler will follow the rules given in the references above to  locate the header files.  A I do not recognize either VMSLIB or the PLREDT.EXE package names.   < If they are older packages, you may need to compile with the /STANDARD=VAXC option.    B Now do you really need to recompile this, or is this just a matterB of linking some files that are supplied in object files and object libraries only?   D The linker messages (that you did not supply the exact text of) thatE you describe imply that the VMSLIB.OLB was built with the older VAX C J compiler, and that it needs to be linked with the SYS$LIBRARY:VAXCRTL.EXE.  = For this, a linker option file must be specified, you can use 1 sys$input from the DCL prompt as a quick compile.   3 $link/exe=plredt.exe [.obj]plredt,edit,bitvectors,- $ sys$library:vmslib.olb,sys$input/opt sys$library:vaxcrtl.exe/share  ^z $   F For more on linker option files, see the documentation for the LINKER.  > If you do decide to recompile your application with DEC C, youE probably will want to recompile the source for the vmslib.olb library C and build it back into a new library.  I would recommend giving the B resulting library a slightly different name, to prevent getting it' confused with the one build with VAX C.   C If the VMSLIB routines (built with VAX C) pass a pointer to a *FILE A structure as part of their parameters, then they can only be used ( with object modules compiled with VAX C.   -John  wb8tyw@qsl.network! representing only my own opinion.    ------------------------------  % Date: Mon, 08 Jan 2001 23:19:14 -0500 - From: JF Mezei <jfmezei.spamnot@videotron.ca> * Subject: Re: Adding link libraries to DECC, Message-ID: <3A5A9141.6D6877CB@videotron.ca>   Steven Shamlian wrote:7 > %LINK-W-USEUNDEF, undefined symbol TOLOWER referenced # >  in psect $CODE offset %X000001A9 D >  in module VMSLIB file DISK$HOBBES:[VMS$COMMON.SYSLIB]VMSLIB.OLB;1  N Sounds like whomever generated VMSLIB.OLB did it in a way not quite compatible$ with the rest of your  object files.  I Are you on VAX ? Is it possible that VMSLIB was created with VAXC but you F compiled the rest with DECC ? If so, you will need to also link in the VAXCRTL.EXE    for instance: 4 $LINK mymain.obj,mylib.olb/library,sys$input/options SYS$LIBRARY:VAXCRTL.EXE/SHARE  $    ------------------------------  " Date: Mon, 8 Jan 2001 19:19:48 GMT7 From: moroney@world.std.spaamtrap.com (Michael Moroney) ? Subject: Re: Asking an app to temporarily relinquish a resource & Message-ID: <G6uz10.App@world.std.com>  I The usual way to do this is to have the first application take out a lock K with a blocking AST.  This AST fires when another process requests the lock E in an incompatible mode.  The AST cleans up in some way (in this case G deallocating the port) and releases the lock, then requeues the lock in K some method that grants the lock when the second process releases the lock.O  J This requires cooperation by the first process, that is you can change theF source of the fax program.  If not, you'll have to do some brute forceK method like issuing a $FORCEX to the fax program, running your application, H and restarting the fax program (possibly in an exit handler in case your program encounters an error)   -Mikee   ------------------------------  $ Date: Mon, 8 Jan 2001 14:33:20 -0500% From: "John Vottero" <John@mvpsi.com>o? Subject: Re: Asking an app to temporarily relinquish a resource . Message-ID: <t5k5haa5k9a6c@news.supernews.com>  : "JF Mezei" <jfmezei.spamnot@videotron.ca> wrote in message& news:3A59F0A8.BEFE2844@videotron.ca...K > I have a fax reception application that constantly has a channel assignedr to1 > the serial port, listening to an incoming call.n >oJ > What I want to do is to allow any application to send a "message" to the faxeJ > application asking it to relinquish control of the serial port until the% > second application is done with it.d >e7 > For the second part of the problem it is fairly easy:u >r= > second-app takes a lock to indicate it has the serial port.i > L > fax-app tries to take the same lock and asks that an AST be delivered when thebG > first app relinquishes the lock (app terminates, process killed etc).i > . > But the first part doesn't seem so obvious : >nI > However, is there a way for the fax-app to be notified whenever someonee else' > is asking for a lock it already has ?  >a >1J > Or is the only way for the fax-app to have a mailbox to which the second appe. > sends a request whenever it needs the port ? >0F > In another I had acheined that functionality with DECnet. You open a decnetD > channel to the application's object and for as long as the channel remained > opened, you had the resource.e > B > What I definitely require is 100% assurance that when the second applicationeL > ends, dies or its process is killed, that the fax-app is notified that the! > serial port is again available.   K The fax-app takes out a lock and specifies a blocking AST.  When the secondfK app requests the same lock, the fax-app will receive a blocking AST and caneJ release the lock.  After releasing the lock (converting to NL) the fax-app6 re-acquires the lock specifying the LCK$M_QUECVT flag.   ------------------------------  % Date: Mon, 08 Jan 2001 15:09:01 -0500m- From: JF Mezei <jfmezei.spamnot@videotron.ca>x? Subject: Re: Asking an app to temporarily relinquish a resourceT, Message-ID: <3A5A1E4F.85688B20@videotron.ca>   Michael Moroney wrote: > K > The usual way to do this is to have the first application take out a lockrM > with a blocking AST.  This AST fires when another process requests the locki > in an incompatible mode.    S Thanks. exactly what I was looking for. Will look for "blocking AST" in the docset.-   ------------------------------    Date: 09 Jan 2001 04:37:41 +0800, From: Paul Repacholi <prep@prep.synonet.com>? Subject: Re: Asking an app to temporarily relinquish a resource 0 Message-ID: <87y9wlvkyy.fsf@k9.prep.synonet.com>  / JF Mezei <jfmezei.spamnot@videotron.ca> writes:i  N > However, is there a way for the fax-app to be notified whenever someone else' > is asking for a lock it already has ?n  I Use the lock manager. Set up a blocking ast in the first app. When somoneaI else goes for the lock, the blocking ast fires. Convert down to NUL, thenHM reque to a write lock. When the second exits, for any reason, your conversionr@ completes, and you grab the port and re-enable the blocking ast.     -- i< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.d@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.   ------------------------------  % Date: Mon, 08 Jan 2001 23:42:23 -0500p2 From: rdeininger@mindspring.com (Robert Deininger)? Subject: Re: Asking an app to temporarily relinquish a resourceeL Message-ID: <rdeininger-0801012342230001@user-2ive6as.dialup.mindspring.com>  ^ In article <87y9wlvkyy.fsf@k9.prep.synonet.com>, Paul Repacholi <prep@prep.synonet.com> wrote:  K > Use the lock manager. Set up a blocking ast in the first app. When somoneoK > else goes for the lock, the blocking ast fires. Convert down to NUL, then:O > reque to a write lock. When the second exits, for any reason, your conversionmB > completes, and you grab the port and re-enable the blocking ast.    l Aren't VMS locks wunnerful!?  The original problem statement made this sound like a really hard problem. :-)  4 For extra credit, solve the same problem in oonix...   -- e Robert Deininger rdeininger@mindspring.com    ------------------------------  % Date: Mon, 08 Jan 2001 13:05:00 -0800 + From: "richard n. frank" <rnfrank@llnl.gov>A1 Subject: Re: Compaq stockholders affecting policya> Message-ID: <4.2.0.58.20010108125452.00b0ad00@poptop.llnl.gov>  I Someone in this thread said,"... buy as many shares of Compaq ...We will   then exert whateC  >leverage we can muster and force Capellas and the others to beginnJ  >proactively marketing VMS or face ouster by demand of the stockholders."  K There are 1,700,000,000 shares of common stock outstanding.  Get a grip on rI reality. People who own stock .and. people who understand VMS will never i have an impact on Compaq Corp.            rich   @ DISCLAIMER: This is not the opinion of the U.S. Government, DOE,2 UC, or LLNL. It may not even really be my opinion.M ---------------------------------------------------------------------------- s ------------------------------- 2 At 08:00 PM 1/8/01 +0100, Peter LANGSTOEGER wrote:C >In article <3A59103D.6C44E836@earthlink.net>, "David J. Dachtera" t& ><djesys.nospam@earthlink.net> writes: > >Peter LANGSTOEGER wrote:  > >> > >> In article F > <910612C07BCAD1119AF40000F86AF0D805284B97@kaoexc3.kao.cpqcorp.net>, / > "Main, Kerry" <Kerry.Main@compaq.com> writes:mI > >> >>>> If CPQ had intended to outswap VMS into hibernation mode, they s
 > wouldn'tL > >> >have bothered with V7.3, or with the Oracle partnership. I don't thinkK > >> >they'd be hiring developers, either. (If you're a Compaqtian and you a > bring.7 > >> >in a qualified VMS hire, you get a $5K bounty)<<<  > >> >M > >> >Yep, and likely the openVMS Engineering group would not be aggressively I > >> >hiring college graduates either ie. focus on long term, new idea's t > and goingl > >> >after youth. > >> > > >> >Reference:G > >> ><http://www.compaq.com/inFORM/issues/issue32/human-int-29-b.html>n > >> > >> Come on, Kerry.@ > >> We all know that OpenVMS engineering was never the problem.C > >> The marketing, ads and sales were and unfortunately still are.s > >>G > >> Yes, the Q top management might have changed their mind about VMS,L? > >> but what we still see here is, that VMS is on its way out.- > >MF > >So, then - the answer to the perennial question, "what can *WE* do"J > >would seem to be as Terry and others have suggested: every one who can,H > >buy as many shares of Compaq as your finances will responsibly allow.K > >Remember that the stock certificates must be in *YOUR* name, not that of[J > >your retirement account or its management firm. We will then exert whatD > >leverage we can muster and force Capellas and the others to beginJ > >proactively marketing VMS or face ouster by demand of the stockholders. > >IH > >This seems the only effective recourse available. I urge everyone who. > >can to participate actively in this effort. >-9 >Sigh. This is of course possible, even from my location.C@ >But I would have lost half of my money over the last 9 weeks... >N >--I= >Peter "EPLAN" LANGSTOEGER           Tel.    +43 1 81111-2651e< >Network and OpenVMS system manager  Fax.    +43 1 81111-888= ><<< KAPSCH AG  Wagenseilgasse 1     E-mail  eplan@kapsch.netFI >A-1121 VIENNA  AUSTRIA              "I'm not a pessimist, I'm a realist"i   ------------------------------  % Date: Mon, 08 Jan 2001 21:14:48 -0600S7 From: "David J. Dachtera" <djesys.nospam@earthlink.net>D1 Subject: Re: Compaq stockholders affecting policyO- Message-ID: <3A5A8228.A444856D@earthlink.net>S   "richard n. frank" wrote:S > J > Someone in this thread said,"... buy as many shares of Compaq ...We will > then exert whatSE >  >leverage we can muster and force Capellas and the others to begin L >  >proactively marketing VMS or face ouster by demand of the stockholders." > L > There are 1,700,000,000 shares of common stock outstanding.  Get a grip onJ > reality. People who own stock .and. people who understand VMS will never  > have an impact on Compaq Corp.   Ever heard of a class action?    -- c David J. Dachtera  dba DJE Systems  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.O   ------------------------------   Date: 8 Jan 2001 20:00:17 +0100 * From: eplan@kapsch.net (Peter LANGSTOEGER)= Subject: Re: Compaq: A simple, affordable clustering solutionD* Message-ID: <3a5a0e41$1@news.kapsch.co.at>  g In article <3A59103D.6C44E836@earthlink.net>, "David J. Dachtera" <djesys.nospam@earthlink.net> writes:- >Peter LANGSTOEGER wrote:F >>   >> In article <910612C07BCAD1119AF40000F86AF0D805284B97@kaoexc3.kao.cpqcorp.net>, "Main, Kerry" <Kerry.Main@compaq.com> writes:DO >> >>>> If CPQ had intended to outswap VMS into hibernation mode, they wouldn'toJ >> >have bothered with V7.3, or with the Oracle partnership. I don't thinkN >> >they'd be hiring developers, either. (If you're a Compaqtian and you bring5 >> >in a qualified VMS hire, you get a $5K bounty)<<<B >> >K >> >Yep, and likely the openVMS Engineering group would not be aggressivelytP >> >hiring college graduates either ie. focus on long term, new idea's and going >> >after youth. >> > >> >Reference:E >> ><http://www.compaq.com/inFORM/issues/issue32/human-int-29-b.html>e >> $ >> Come on, Kerry.> >> We all know that OpenVMS engineering was never the problem.A >> The marketing, ads and sales were and unfortunately still are.e >> $E >> Yes, the Q top management might have changed their mind about VMS,b= >> but what we still see here is, that VMS is on its way out.o >eD >So, then - the answer to the perennial question, "what can *WE* do"H >would seem to be as Terry and others have suggested: every one who can,F >buy as many shares of Compaq as your finances will responsibly allow.I >Remember that the stock certificates must be in *YOUR* name, not that oftH >your retirement account or its management firm. We will then exert whatB >leverage we can muster and force Capellas and the others to beginH >proactively marketing VMS or face ouster by demand of the stockholders. >SF >This seems the only effective recourse available. I urge everyone who, >can to participate actively in this effort.  8 Sigh. This is of course possible, even from my location.? But I would have lost half of my money over the last 9 weeks...C   -- s< Peter "EPLAN" LANGSTOEGER           Tel.    +43 1 81111-2651; Network and OpenVMS system manager  Fax.    +43 1 81111-888S< <<< KAPSCH AG  Wagenseilgasse 1     E-mail  eplan@kapsch.netH A-1121 VIENNA  AUSTRIA              "I'm not a pessimist, I'm a realist"   ------------------------------   Date: 8 Jan 2001 20:11:14 +0100 * From: eplan@kapsch.net (Peter LANGSTOEGER)= Subject: Re: Compaq: A simple, affordable clustering solutionL* Message-ID: <3a5a10d2$1@news.kapsch.co.at>  k In article <OF7DF1ACF8.F6A1302F-ON802569CE.004F42D7@qedi.quintiles.com>, steven.reece@quintiles.com writes: L >I definitely go with Terry on this one.  The DII-COE work is very importantI >to the future of VMS and future application support.  I could easily seeZJ >Oracle making a great deal of use of it since they would not have as much9 >work to do in generating the VMS port of their products.   0 Hopefully, the waves comes soon across the pond.N Here, the local ORACLE branch still asks "What is VMS ? This old/dead Opsys ?"J And even when they know about VMS, nobody of them would suggest VMS to theL customers. They suggest UNIX (which means SOLARIS, AIX and HP/UX and nothing else)...  J I Q USA is serious about VMS (which is still uncertain from my view), thenK someone must force the rest of Q and the other companies in US and the rest G of the other companies worldwide to believe it and be serious about VMSl? themselves, too. And this takes time, while there is no more...[   -- r< Peter "EPLAN" LANGSTOEGER           Tel.    +43 1 81111-2651; Network and OpenVMS system manager  Fax.    +43 1 81111-888f< <<< KAPSCH AG  Wagenseilgasse 1     E-mail  eplan@kapsch.netH A-1121 VIENNA  AUSTRIA              "I'm not a pessimist, I'm a realist"   ------------------------------  # Date: Mon, 08 Jan 2001 19:28:53 GMTh4 From: "Terry C. Shannon" <terryshannon@mediaone.net>= Subject: Re: Compaq: A simple, affordable clustering solution < Message-ID: <Vxo66.37261$1M.8539351@typhoon.ne.mediaone.net>  7 "Peter LANGSTOEGER" <eplan@kapsch.net> wrote in messageC$ news:3a5a0e41$1@news.kapsch.co.at... <snip> > >iF > >So, then - the answer to the perennial question, "what can *WE* do"J > >would seem to be as Terry and others have suggested: every one who can,H > >buy as many shares of Compaq as your finances will responsibly allow.K > >Remember that the stock certificates must be in *YOUR* name, not that of J > >your retirement account or its management firm. We will then exert whatD > >leverage we can muster and force Capellas and the others to beginJ > >proactively marketing VMS or face ouster by demand of the stockholders. > >eH > >This seems the only effective recourse available. I urge everyone who. > >can to participate actively in this effort. >o: > Sigh. This is of course possible, even from my location.A > But I would have lost half of my money over the last 9 weeks...o  J But you didn't buy it nine weeks ago, and at $16 and change, it's a steal.J Depending on what's announced on January 23 (4FQ00 earnings) it may not be such a steal thereafter.  = Things could be worse. You coulda bought CMGI nine weeks ago!m   ------------------------------   Date: 8 Jan 2001 12:05:23 PSTiT From: Fairfield@SLAC.Stanford.EDU (Ken Fairfield; SLAC: 650-926-2924; FAX: 926-3515)= Subject: Re: Compaq: A simple, affordable clustering solutione3 Message-ID: <5Ro7GnmEIgLJ@mccdev.slac.stanford.edu>t  - In article <937h30$2j88$1@info.cs.uofs.edu>, n8     	bill@triangle.cs.uofs.edu (Bill Gunshannon) writes:( > In article <G6q4BH.Ju8@world.std.com>,< >  moroney@world.std.spaamtrap.com (Michael Moroney) writes: [...]jA > |> There's another reason - VMS runs all of Intel's fab plants!r > ? > Yes, but not on Alphas and undoubtedly not a current release.a  H         This is no longer true.  (1) There  are Alphas as members of theH     VMS  clusters  running some of the fabs.  (2) The newest fab,  beingH     built in the Northwest, is using an Alpha/VMS cluster.  The fab willH     be doing 12" wafers (current  size  is  8").   (3)  In  a  _factory_H     environment,  you  do  _not_  change  the software willy-nilly.  YouH     _prove_ a certain release  and  _stay_  there  as  long as possible.H     IIRC,  current fabs are at VMS 7.1 (VAX), not _that_ far behind  the     release schedule.e  H         So with, as Terry would say, "the recent unpleasantness" betweenH     Digital and Intel "behind us",  and  with the immenent demise of VMSC     not realized, the Intel fabs have moved forward with Alpha/VMS.-  H         Note, however, that currents within  Intel continue to think "weH     should  be  building  our chips with our own chips", and  there  areH     always plans to run the "next fab" on Intel processors.   It  didn'tH     work  out  that  way  for  the  12"  fab.  And (as readers here willH     understand) it's probably much less  an  issue of Intel versus AlphaH     procesors than an issue of VMS versus _any_ other o/s, let alone one     which runs on Intel.  5         -Ken, who's-probably-said-more-than-he-shouldi -- oM  Kenneth H. Fairfield            |  Internet: Fairfield@SLC.Slac.Stanford.Eduh:  SLAC, 2575 Sand Hill Rd, MS 46  |  Voice:    650-926-2924:  Menlo Park, CA  94025           |  FAX:      650-926-3515N  -----------------------------------------------------------------------------B  These opinions are mine, not SLAC's, Stanford's, nor the DOE's...   ------------------------------   Date: 8 Jan 2001 22:23:49 +0100 * From: eplan@kapsch.net (Peter LANGSTOEGER)= Subject: Re: Compaq: A simple, affordable clustering solutionc* Message-ID: <3a5a2fe5$1@news.kapsch.co.at>  s In article <Vxo66.37261$1M.8539351@typhoon.ne.mediaone.net>, "Terry C. Shannon" <terryshannon@mediaone.net> writes: ] >"Peter LANGSTOEGER" <eplan@kapsch.net> wrote in message news:3a5a0e41$1@news.kapsch.co.at...t; >> Sigh. This is of course possible, even from my location.,B >> But I would have lost half of my money over the last 9 weeks... >nK >But you didn't buy it nine weeks ago, and at $16 and change, it's a steal.lK >Depending on what's announced on January 23 (4FQ00 earnings) it may not bet >such a steal thereafter.d  F Remember the DEC stock. I could have trippled my money with DEC sharesG in about 16months and later double my money in about 19months. But alaslD I didn't do it. And DEC is gone also. And what do we learn by that ?  J Other IT companies stock rate did tend to grow (with a little flickering),M DEC (and now Q also) did tend to keep the same (also with some up and downs). ; But the last months didn't do good things to all of them...l  G And, if I would buy Q shares now (in Dollar), earnings of an eventuallyxD growing Q stock rate would probably be eaten by a growing Euro rate.K It would be better, if I bought Dollars years ago, and you buy Euros now...n  G So, no thanks, I don't think that I will buy (Q or other) shares in theaH near future at all. Or asked the other way, how much shares would I haveF to buy to get an influence ? Millions ? For so much money, I will quit: immediately and forget VMS and the business alltogether...   --  < Peter "EPLAN" LANGSTOEGER           Tel.    +43 1 81111-2651; Network and OpenVMS system manager  Fax.    +43 1 81111-888u< <<< KAPSCH AG  Wagenseilgasse 1     E-mail  eplan@kapsch.netH A-1121 VIENNA  AUSTRIA              "I'm not a pessimist, I'm a realist"   ------------------------------    Date: 09 Jan 2001 04:08:19 +0800, From: Paul Repacholi <prep@prep.synonet.com>= Subject: Re: Compaq: A simple, affordable clustering solutiont0 Message-ID: <87r92dx0wc.fsf@k9.prep.synonet.com>  / JF Mezei <jfmezei.spamnot@videotron.ca> writes:8  P > For crying out loud, why is so goddam impossible for Compaq to take just a bitK > of VMS's profits and make some public advertising so that at least we arefO > given the impression that Compaq isn't affraid to publicly admit it has VMS ?nN > Right now, I get the feeling that Compaq feels that VMS is a disease that is; > socially unacceptable so it won't talk about it publicly.:  H I could hardly give a rats arse for ads. By the time they get done, they are turned to pap.  H Now soon, another vendor is goning to have to start comming up with SPEC> numbers on the 'worlds fastest' earth shattering 64-bit CPU...  @ It would be SO nice to see the Q drop a little bit bigger number@ 5 min later. And anounce that xxxxx is NOT the fastest. Remember; the Mig-25 vs SR-71 world speed records? +25 MPH 3 times...g  + Don't even bother to hide the sand-bagging.r  ? Oh, and re-run the API(?) 'waiting' adds, only at feeding time.   B In fact, I'd be more extreme. I'd find a 780, cut a deal to get itI back under HW and SW support, and get ready to have a 25th b'day party :)   , Oh, and stick it to Sun on clusters, loudly.   --  < 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: 09 Jan 2001 04:12:52 +0800, From: Paul Repacholi <prep@prep.synonet.com>= Subject: Re: Compaq: A simple, affordable clustering solution 0 Message-ID: <87n1d1x0or.fsf@k9.prep.synonet.com>  4 mathog@seqaxp.bio.caltech.edu (David Mathog) writes:  K > Nobody reads inFORM other than the Compaq installed base of Tru64 an VMS g
 > users.    B And they only read it if they have a PC or some crap so that it is READABLE...W   --  < 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: Mon, 08 Jan 2001 17:49:59 -0600r7 From: "David J. Dachtera" <djesys.nospam@earthlink.net>-= Subject: Re: Compaq: A simple, affordable clustering solutionn- Message-ID: <3A5A5227.615D0151@earthlink.net>a   Peter LANGSTOEGER wrote: > [snip]I > So, no thanks, I don't think that I will buy (Q or other) shares in theiJ > near future at all. Or asked the other way, how much shares would I haveH > to buy to get an influence ? Millions ? For so much money, I will quit< > immediately and forget VMS and the business alltogether...  H How 'bout if 10,000 (are there that many of use out here?) of us buy 100H shares each (can you rob the butter-and-egg kitty of $1600?), that's one million shares total, no?   G Does anyone have access to the numbers (how many shares total of CompaqnH stock)? What percentage of the total would one million shares be? Enough) to exert some leverage in a class-action?-   -- - David J. Dachtera- dba DJE Systemss http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/e  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: Mon, 08 Jan 2001 17:54:04 -0600l7 From: "David J. Dachtera" <djesys.nospam@earthlink.net>a= Subject: Re: Compaq: A simple, affordable clustering solutiont- Message-ID: <3A5A531C.FDF3A2FE@earthlink.net>.   Paul Repacholi wrote:S > 1 > JF Mezei <jfmezei.spamnot@videotron.ca> writes:d > R > > For crying out loud, why is so goddam impossible for Compaq to take just a bitM > > of VMS's profits and make some public advertising so that at least we are Q > > given the impression that Compaq isn't affraid to publicly admit it has VMS ?2P > > Right now, I get the feeling that Compaq feels that VMS is a disease that is= > > socially unacceptable so it won't talk about it publicly.  > J > I could hardly give a rats arse for ads. By the time they get done, they > are turned to pap.  / Well, I understand "arse", but "pap" eludes me.    J > Now soon, another vendor is goning to have to start comming up with SPEC@ > numbers on the 'worlds fastest' earth shattering 64-bit CPU...  G Never mind the speed nonesense! The fastest CPU in the world is uselesssF if the only dominant o.s. available for it won't stay running for more than a few hours!*  A > Oh, and re-run the API(?) 'waiting' adds, only at feeding time.t   Which ads are those?  D > In fact, I'd be more extreme. I'd find a 780, cut a deal to get itK > back under HW and SW support, and get ready to have a 25th b'day party :)r   Yes!  . > Oh, and stick it to Sun on clusters, loudly.  	 Fer sure!v   -- w David J. Dachterac dba DJE Systems  http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/v  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: 9 Jan 2001 01:23:18 +0100-* From: eplan@kapsch.net (Peter LANGSTOEGER)= Subject: Re: Compaq: A simple, affordable clustering solutionj* Message-ID: <3a5a59f6$1@news.kapsch.co.at>  g In article <3A5A5227.615D0151@earthlink.net>, "David J. Dachtera" <djesys.nospam@earthlink.net> writes:e >Peter LANGSTOEGER wrote:a	 >> [snip]aJ >> So, no thanks, I don't think that I will buy (Q or other) shares in theK >> near future at all. Or asked the other way, how much shares would I have I >> to buy to get an influence ? Millions ? For so much money, I will quitn= >> immediately and forget VMS and the business alltogether...t > I >How 'bout if 10,000 (are there that many of use out here?) of us buy 100.I >shares each (can you rob the butter-and-egg kitty of $1600?), that's onet >million shares total, no?  M If you got the first 1000 (ok, let's be fair, 100) participiants, I'll join..F You end probably by umpteen. Ooops, is that pessimistic or realistic ?7 $1600 ? That's about a month's salary for many of us...cM If this ever get realistic, I join with 2-3 months salary, but wait, I dream.v btw. Do you own Q shares ?  H >Does anyone have access to the numbers (how many shares total of CompaqI >stock)? What percentage of the total would one million shares be? Enough * >to exert some leverage in a class-action?  H Well below 1%. I heard of 1.7 billions recently. Don't know if its true.6 Don't know how much is required for anything either...   -- .< Peter "EPLAN" LANGSTOEGER           Tel.    +43 1 81111-2651; Network and OpenVMS system manager  Fax.    +43 1 81111-888a< <<< KAPSCH AG  Wagenseilgasse 1     E-mail  eplan@kapsch.netH A-1121 VIENNA  AUSTRIA              "I'm not a pessimist, I'm a realist"   ------------------------------   Date: 8 Jan 2001 19:55:48 -0500t* From: young_r@eisner.decus.org (Rob Young)= Subject: Re: Compaq: A simple, affordable clustering solution>+ Message-ID: <pS2OzKskbRrQ@eisner.decus.org>)  _ In article <87r92dx0wc.fsf@k9.prep.synonet.com>, Paul Repacholi <prep@prep.synonet.com> writes:g   > J > Now soon, another vendor is goning to have to start comming up with SPEC@ > numbers on the 'worlds fastest' earth shattering 64-bit CPU... > 8 	I suppose you are referring to Itanium?  If so, you may: 	have missed where Intel declared SPEC numbers for Itanium@ 	"unimportant" or not a good measure.  So the de facto benchmark6 	for a workstation, Itanium won't be participating in.   				Robi   ------------------------------    Date: 09 Jan 2001 06:43:33 +0800, From: Paul Repacholi <prep@prep.synonet.com>= Subject: Re: Compaq: A simple, affordable clustering solutiony0 Message-ID: <87vgrpu0kq.fsf@k9.prep.synonet.com>  V Fairfield@SLAC.Stanford.EDU (Ken Fairfield; SLAC: 650-926-2924; FAX: 926-3515) writes:  J >         This is no longer true.  (1) There  are Alphas as members of theJ >     VMS  clusters  running some of the fabs.  (2) The newest fab,  beingJ >     built in the Northwest, is using an Alpha/VMS cluster.  The fab willJ >     be doing 12" wafers (current  size  is  8").   (3)  In  a  _factory_J >     environment,  you  do  _not_  change  the software willy-nilly.  YouJ >     _prove_ a certain release  and  _stay_  there  as  long as possible.J >     IIRC,  current fabs are at VMS 7.1 (VAX), not _that_ far behind  the >     release schedule.   E In about 79-80 Moto did a double page add in EE times or one of them. * "Why out processor quality is the best..."  : We counted about 20 PDP-11s in the photo! All 34s I think.   ROTFL.   -- t< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.n@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.   ------------------------------  % Date: Mon, 08 Jan 2001 20:51:35 -0500i- From: JF Mezei <jfmezei.spamnot@videotron.ca>t= Subject: Re: Compaq: A simple, affordable clustering solutionk, Message-ID: <3A5A6EA0.A876F4FA@videotron.ca>  H The first clustering system witrh a single file system at its root, onlyH TrueCluster V.5 provides a single system image, which greatly simplifies, management and lowers the cost of ownership.    > Source: Canadian version of Inform, Winter 2000/2001, page 38.  R From pages 0 to 47, VMS is mentioned twice in passing (such as also supports _VMS)    : On page 48, there is an article about OpenVMS and DII COE:  F "Open VMS has been the longtime operating system of choice for defenseN contractors". The end of the article points one to http://diicoe.disa.mil/coe/  M So it seems that the former 6 niche markets Compaq was willing to push VMS inr. has narrowed down to just defense contractors.  L  The next page has 2 columns about Heroix which does VMS software (but beingD very careful to ensure that their software also runs on Unix and NT.  M Of the 73 pages, only 1.66 pages are devoted to VMS, and 2 pages to Himalaya.nJ The upside is that Alpha is more prominant than I would have expected, but' always talking about TruCluster/True64.   " Oh, and I forgot about how SABRE : ##M The partnership with Compaq has roots in the early dats of Sabre reservationseB system, when VAX computers anchored the front end of its mainframeJ environment, more than 20 years later, these workhorses still serve as theW processing engines that distribute queries and messages in and out of the core systems.> ##, Is that a subtle way to spell "LEGACY" ?????  L The rest of the article talks about how Sabre is deploying Proliants and NT,2 as well as clustered Compaq proliant 6500 servers.    K There is an article about how Lockheed Martin chose MS Exchange as a singleiJ corporate-wide platform with immunity against viruses being one of the bigN advantages. Yes, Kerry, that is what your employer is telling customers behind
 your back.    I The conclusion: a whole lot more people should check "Defense contractor"t+ checkboxes when filling out Compaq surveys.y  L If Compaq ever calls me for a survey, I will state that I am a self employedG defense contractor. I make neutron bombs in my basement and use VMS....l   ------------------------------  % Date: Mon, 08 Jan 2001 20:51:05 -0600o7 From: "David J. Dachtera" <djesys.nospam@earthlink.net>c= Subject: Re: Compaq: A simple, affordable clustering solution2- Message-ID: <3A5A7C99.5CA8D724@earthlink.net>t   JF Mezei wrote:s > # > steven.reece@quintiles.com wrote:i > >eO > > I definitely go with Terry on this one.  The DII-COE work is very importantm8 > > to the future of VMS and future application support. > O > When I see these "DII-CEO" commitments, the first thing that comes to mind iseM > that famous long term commitment to ensure that VMS will exist x years from8M > now. And this is the part that bears no credibility because even Palmer hadeO > made similar promises. OS2 still exists and is still supported, and owners of(O > Commodore PETs can still operate their machines with the 8k of ram they have.nL > The way I see it, it just means that Compaq is willing to pay for the life5 > support equipment once VMS enters a comatose state.e > V > If DII-CEO included instead a marketing commitment, I woudl be far more comfortable. > O > I have to agree tough that it is true that the unix-system-services aspect oflO > the program is a big positive. It is a foundation that will give VMS a betternO > chance. However, even with DII-COE, lack of marketing will still leave VMS in B > a semi comatose state and remain totally unkown in the industry.  C Remember, also, that this is an effort to make VMS competitive on aeD feature basis when there remains no guarantee that VMS will actuallyF capture any of those DII-COE opportunities. The whole thing could just7 be as elaborate a smoke-screen as WhineBloze is a hoax.s  % Without promotion, VMS is truly dead!    -- o David J. Dachterau dba DJE Systemst http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/   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: 09 Jan 2001 10:53:58 +0800, From: Paul Repacholi <prep@prep.synonet.com>= Subject: Re: Compaq: A simple, affordable clustering solution.0 Message-ID: <877l45saex.fsf@k9.prep.synonet.com>  , young_r@eisner.decus.org (Rob Young) writes:  a > In article <87r92dx0wc.fsf@k9.prep.synonet.com>, Paul Repacholi <prep@prep.synonet.com> writes:- >  > > L > > Now soon, another vendor is goning to have to start comming up with SPECB > > numbers on the 'worlds fastest' earth shattering 64-bit CPU... > > : > 	I suppose you are referring to Itanium?  If so, you may< > 	have missed where Intel declared SPEC numbers for ItaniumB > 	"unimportant" or not a good measure.  So the de facto benchmark8 > 	for a workstation, Itanium won't be participating in.  G Well, one way or the other, bring-out-your-dead-time is getting closer.1  * Hey, Compaq is in SPEC, they could test...   -- p< 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: Tue, 09 Jan 2001 04:18:18 GMTC4 From: "Terry C. Shannon" <terryshannon@mediaone.net>= Subject: Re: Compaq: A simple, affordable clustering solution.< Message-ID: <eiw66.37714$1M.8709794@typhoon.ne.mediaone.net>  B "David J. Dachtera" <djesys.nospam@earthlink.net> wrote in message' news:3A5A7C99.5CA8D724@earthlink.net...Q   >)E > Remember, also, that this is an effort to make VMS competitive on atF > feature basis when there remains no guarantee that VMS will actuallyH > capture any of those DII-COE opportunities. The whole thing could just9 > be as elaborate a smoke-screen as WhineBloze is a hoax.b >e' > Without promotion, VMS is truly dead!y  H On one level, DII-COE is a checkoff item, just like VMS Integrated PosixL was. (Gotta support the FIPS, ya know!) On another level, DII-COE might leadJ to incremental opportunities IF ISVs begin porting their apps. No porting, no new apps, no gain.l  B And you are absolutely right. The marketing department needs to be@ proactive, not passive. But that's my opinion, I could be wrong.  
 charlie matcor   ------------------------------  # Date: Mon, 08 Jan 2001 21:17:45 GMTp+ From: rjordan@mars.mcs.net (Richard Jordan) - Subject: CSWS (Apache) update 1.0-1 available-2 Message-ID: <Z7q66.710$8S4.62930@news.goodnet.com>  I Noted while browsing CSWS docs on the Q website today; CSWS V1.0-1 updateaI dates January 5, 2001, is available for download with updated docs.  I've9E not had time to review it yet so I don't know what changes were made.    FYI...  C http://www.openvms.compaq.com/openvms/products/ips/apache/csws.htmlt   Rich Jordano rjordan@mcs.nete   ------------------------------  % Date: Mon, 08 Jan 2001 14:38:30 -0700o% From: Dean Woodward <deanw@rdrop.com> 1 Subject: Re: CSWS (Apache) update 1.0-1 availablep) Message-ID: <3A5A3356.A71D8D94@rdrop.com>o   Richard Jordan wrote:  > K > Noted while browsing CSWS docs on the Q website today; CSWS V1.0-1 update K > dates January 5, 2001, is available for download with updated docs.  I'veoG > not had time to review it yet so I don't know what changes were made.t >  > FYI... > E > http://www.openvms.compaq.com/openvms/products/ips/apache/csws.htmlg  D The new feature is authentication agains SYSUAF.  To whoever finally? implemented this:  THANK YOU!  It's what I've been waiting for.g  - 'Scuse me, I have to go download something...    ------------------------------  % Date: Mon, 08 Jan 2001 17:52:03 -0500c" From: Dan Sugalski <dan@sidhe.org>1 Subject: Re: CSWS (Apache) update 1.0-1 availableo: Message-ID: <5.0.2.1.0.20010108174816.01f99670@24.8.96.48>  . At 02:38 PM 1/8/01 -0700, Dean Woodward wrote: >Richard Jordan wrote: > > M > > Noted while browsing CSWS docs on the Q website today; CSWS V1.0-1 updatenM > > dates January 5, 2001, is available for download with updated docs.  I'veoI > > not had time to review it yet so I don't know what changes were made.  > > 
 > > FYI... > >:G > > http://www.openvms.compaq.com/openvms/products/ips/apache/csws.htmla >AE >The new feature is authentication agains SYSUAF.  To whoever finally9@ >implemented this:  THANK YOU!  It's what I've been waiting for.  J Just do be aware you should *not* use this for pages where one end of the F web conversation, or the net in the middle, is insecure. Using SYSUAF F validation means that for *every* page secured this way, a browser is L sending a username and _unencrypted_ password for an account on your system.  L If the account has no login privs (basically a web-access-only account), or E the pages are served via secure http, or you trust both ends and the -@ middle, then you're fine. If you're not sure, be really careful.  J You probably really, *really* do not want to access pages with an account K that has one of the ALL class privs (sysprv or world, say), since a simple  9 packet sniffer will give someone the keys to your system.n   					Dan  I --------------------------------------"it's like this"-------------------o2 Dan Sugalski                          even samurai? dan@sidhe.org                         have teddy bears and evenm;                                       teddy bears get drunko   ------------------------------   Date: 8 Jan 2001 19:47:05 GMT12 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) Subject: Re: DEC 3000 model 300 6 Message-ID: <93d5fp$nvl$1@mailint03.im.hou.compaq.com>  O In article <3A5A0905.4B33DDC4@chello.nl>, Mark Sterk <strong@chello.nl> writes:o :m :m_stanifer@my-deja.com wrote: :sG :> I wonder if I am having the same type problem? I have a DEC 2000 300tF :> AXP (jensen) I have tried loading Open VMS on it and when it startsI :> booting it gets to the same point everytime and the screen goes black.S  F   The subject says DEC 3000 model 300, which is a completely differentF   (TURBOchannel) system than the DEC 2000 model 300 (EISA) system thatG   is referenced in the text.  I will here assume DEC 2000, based on thegG   Jensen reference (and not Pelican or related bird) found in the text.0  I :Replace the card for one with a S3 trio64, trio64+ or S3-Virge chip they J :are supported under OSF,TRU64,NT,Linux and VMS and are a lot faster and a! :lot more stable than the Mach64.   G   From the perspective of OpenVMS, the reported symptoms are indicativet*   of an unsupported graphics controller...  E   I would not encourage alterations to the base configuration of the d!   DEC 2000 model 300 series box. a  E   I would not encourage trying to extend the internal SCSI controller F   outside of the DEC 2000 model 300 series box, or (if so configured) 6   extending the external SCSI controller into the box.  H   I would not encourage trying to an ISA graphics controller other than =   the Qvision.  I would not encourage use of the S3 series.  d  I   I would encourage using only the qualified EISA controllers, and using  +   the correct revisions of the controllers.m  F   If you want to try a ISA Mach64 on the DEC 2000 model 300, you will H   likely have to run it configured in VGA mode.  (You might get that to G   work.  Or you might not.)  Higher resolutions would require a linear  F   address window of at least four megabytes in size, and this address E   space must be aligned on a four megabyte boundary within the first  G   sixteen megabytes of ISA memory.  On the DEC 2000 model 300, the ISA WD   memory and the system memory space are not separable; there is no E   graphics memory hole.  You cannot DMA into any memory in that four  H   megabyte window, meaning that you would somehow need to create a four G   megabyte logical memory hole in the right portion of system physical oB   memory, and somehow convincing OpenVMS not to use this memory...  J   The DEC 2000 model 300 and model 500 are the only OpenVMS Alpha systems F   with (only) the EISA/ISA bus.  All later Alpha systems have and use F   either integrated graphics or a PCI controller for graphics support.K   Various of the PCI graphics controllers mentioned will work with OpenVMS.G  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------    Date: 09 Jan 2001 04:24:39 +0800, From: Paul Repacholi <prep@prep.synonet.com> Subject: Re: DEC 3000 model 300 0 Message-ID: <87ae91x054.fsf@k9.prep.synonet.com>  4 rdeininger@mindspring.com (Robert Deininger) writes:   > This is from the DEC 3000 Model 300/300L AXP Harware Reference Guide, part number EK-PELCN-OG.B01.  Chances are, the same applies to the models 300X and 300LX.  But I make no promises.  F From memory, the 300 and the 300X are 1280x1024 on board, the 300LX is  only 1024x8??... The other one!!   -- i< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.y@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.   ------------------------------   Date: 8 Jan 2001 23:16:35 +0100I* From: eplan@kapsch.net (Peter LANGSTOEGER) Subject: Re: DEC 3000 model 300r* Message-ID: <3a5a3c43$1@news.kapsch.co.at>  _ In article <87ae91x054.fsf@k9.prep.synonet.com>, Paul Repacholi <prep@prep.synonet.com> writes:a5 >rdeininger@mindspring.com (Robert Deininger) writes:c >l >> This is from the DEC 3000 Model 300/300L AXP Harware Reference Guide, part number EK-PELCN-OG.B01.  Chances are, the same applies to the models 300X and 300LX.  But I make no promises.  >.G >From memory, the 300 and the 300X are 1280x1024 on board, the 300LX isa! >only 1024x8??... The other one!!    ??   It is 1280x1024x72x8.    What did you mean ?-   -- -< Peter "EPLAN" LANGSTOEGER           Tel.    +43 1 81111-2651; Network and OpenVMS system manager  Fax.    +43 1 81111-888m< <<< KAPSCH AG  Wagenseilgasse 1     E-mail  eplan@kapsch.netH A-1121 VIENNA  AUSTRIA              "I'm not a pessimist, I'm a realist"   ------------------------------  % Date: Mon, 08 Jan 2001 22:22:16 -0500e2 From: rdeininger@mindspring.com (Robert Deininger) Subject: Re: DEC 3000 model 300tL Message-ID: <rdeininger-0801012222170001@user-2ive6as.dialup.mindspring.com>  ^ In article <87ae91x054.fsf@k9.prep.synonet.com>, Paul Repacholi <prep@prep.synonet.com> wrote:  6 > rdeininger@mindspring.com (Robert Deininger) writes: >  > > This is from the DEC 3000 Model 300/300L AXP Harware Reference Guide, part number EK-PELCN-OG.B01.  Chances are, the same applies to the models 300X and 300LX.  But I make no promises. > H > From memory, the 300 and the 300X are 1280x1024 on board, the 300LX is" > only 1024x8??... The other one!!     You are on the right track.  I was lumping them all together from the point of view of setting the alternate console ... and I was guessing.   For built-in graphics, the 300L has 1024x 768 @ 72 Hz, and the 300, 300X, and 300LX have 1280 x 1024 @ 72 Hz.  These are all 8-plane, 2D graphics systems.O (Source: section 1.1 of the the DEC 3000 300/400/500/600/700/800/900 AXP ModelsoM System Programmer's Manual, order number EK-D3SYS-PM.B01, revised July 1994.)   8 There are some possibly interesting manuals linked here:<     ftp://ftp.netbsd.org/pub/NetBSD/misc/dec-docs/index.html" including the programmer's manual:E       ftp://ftp.netbsd.org/pub/NetBSD/misc/dec-docs/ek-d3sys-pm.ps.gzh   Hope that helps.   -- a Robert Deininger rdeininger@mindspring.comD   ------------------------------  % Date: Mon, 08 Jan 2001 22:41:16 -0500 2 From: rdeininger@mindspring.com (Robert Deininger)+ Subject: Re: DEC-AXPVMS-VMS712_SYS-V0200--4nL Message-ID: <rdeininger-0801012241160001@user-2ive6as.dialup.mindspring.com>  [ In article <9327pi$rft$3@mailint03.im.hou.compaq.com>, hoffman@xdelta.zko.dec.nospam wrote:1  M > In article <931tnd$6fp$1@nnrp1.deja.com>, karlrohwedder@my-deja.com writes:mG > :After installing the patch (DEC-AXPVMS-VMS712_SYS-V0200--4.PCSI) and6 > :rebooting the system, iss$ > :announces itself as VMS V7.2-1... >  >   Workaround:  > & >     $ RUN SYS$LOADABLE_IMAGES:SYSVER >     REPLACE V7.1-2 >     WRITE  >     $ EXIT  G Hoff, I don't much care for this workaround.  First, it doesn't (work):t   $ set def sys$manager   / This is the our usual default directory, right?n    $ RUN SYS$LOADABLE_IMAGES:SYSVERC >>> SYS$BASE_IMAGE.EXE can not be opened: no such file or directoryM  E So this little SYSVER program isn't smart enough to find the image itrF wants to modify.  Then unsuspecting upgrader (me) tries something like this:e  ! $ set default sys$loadable_imageso  $ RUN SYS$LOADABLE_IMAGES:SYSVER SYSVERSION> replace V7.1-2 SYSVERSION> write  SYSVERSION> exit $2  F That appeared to work.  The version number was correct (but only after rebooting).  Unsuspecting upgrader then proceeds to rolling-reboot some satellites, but they come up with the version set to V7.2-1 !!  7 Closer inspection reveales the old familiar booby-trap:e   $ dir/date sys$base_image.exe*   Directory SYS$SYSROOT:[SYS$LDR]    SYS$BASE_IMAGE.EXE;1,                       8-JAN-2001 15:25:58.26   Total of 1 file.   Directory SYS$COMMON:[SYS$LDR]   SYS$BASE_IMAGE.EXE;2,                       8-JAN-2001 15:08:47.28 SYS$BASE_IMAGE.EXE;1,                       4-DEC-2000 18:54:22.68 SYS$BASE_IMAGE.EXE_OLD;2,                       5-MAY-2000 03:54:22.86 SYS$BASE_IMAGE.EXE_OLD;1,                       3-DEC-1998 16:01:06.41   Total of 4 files.b  & Grand total of 2 directories, 5 files.  J So the SYSVER program has read the SYS$BASE_IMAGE.EXE from SYS$COMMON, andI written the corrected version in the system-specific directory, where thep satellites don't see it.  ! So I suggest this method instead:a  0 $ set default disk$whatever:[vms$common.sys$ldr]  $ RUN SYS$LOADABLE_IMAGES:SYSVER SYSVERSION> replace V7.1-2 SYSVERSION> writeh SYSVERSION> exit $o    L Or, as you say in a later post, just wait for the corrected ECO to come out.    P I hope someone hurries up and finishes V7.2-3, so we can have all this fun again when V7.3-2 comes out  :-)   -- M Robert Deininger rdeininger@mindspring.coma   ------------------------------  + Date: Mon, 08 Jan 2001 16:12:08 -0700 (MST)r" From: John Nebel <nebel@csdco.com> Subject: Re: Decserver 700G Message-ID: <Pine.OSF.4.21.0101081607130.19581-100000@athena.csdco.com>w  " Sounds like you want to use bootp.  = Specifying the host is the router's job, not the DECserver's.e   If it's a Cisco router:    interface Ethernet0 :  ip address x.240.0.97 255.255.255.0   <<< gateway address<  ip helper-address x.181.152.50        <<< bootp/tftp server  
 John Nebel    ) On Thu, 14 Dec 2000, Robert Greene wrote:l  N > Is this is a good place to ask a question about configuring a decserver 700? >  > K > How do I configure the decserver 700 to request it's load (WWENG2) from a  > specific IP node?m > N > I just bought the thing a couple of months ago and now the network admin hasJ > put it behind a router that only transfers IP. It requests a load from aI > node (IP) but the decserver never gets the load file... the LED display K > cycles from 4-2 over and over and the decserver just keeps trying to loade > the file from the same node. >  > < > If I could specify what node contains the load file,  then > maybe I could get it to load.  >  > I > If I hook the server up to another router (bad me, not allowed) then iti > works fine.... > N > I am fairly familiar with decserver in a MOP or LAT environment but not sure > how to handle this one...a >  >  >  >  >  >  >    ------------------------------  # Date: Tue, 09 Jan 2001 01:06:46 GMTr From: kparris@my-deja.comr* Subject: Re: Flackey fibre channel support) Message-ID: <93do72$l5j$1@nnrp1.deja.com>   + young_r@eisner.decus.org (Rob Young) wrote:  > 	With 7.3, the; > 	very painful merges after backup go away with mini-copy.i  C I think you're confusing merges with full-copy operations, and thus. Mini-Copy with Mini-Merge.  G Mini-Copy makes shadow full-copy operations faster, and is intended forcF use when a shadowset member has been removed but then is re-added to aE shadowset later (as one might want to do for "snapshot"-style backupsa- in the absence of a Snapshot Driver product).-  C A Merge operation is triggered by the crash of a VMS node which has<E shadowset(s) mounted.  In order to do a Mini-Merge, a record of writeeG operations must be kept somewhere outside of a VMS node itself (e.g. in_F the controller), so that after a VMS node crashes, the other VMS nodesB in the cluster can determine what areas on the shadowset disks theE departed node was writing to recently, so that you only have to mergemD the contents of those few areas, instead of scanning the entire diskD contents as you have to do for a full merge.  As of today, only MSCPD controllers (HSJ, HSD) have the Volume Shadowing Assist called Write) History Logging which allows Mini-Merges.   D I'm told that mini-merge support for the HSG80 is under development.A (This will presumably require both ACS firmware and HBVS softwareeG enhancements).  I was cautioned at the time that if this capability wasp? provided in the HSG80, that wouldn't guarantee support for this6= capability in the next follow-on HSG controller.  But perhaps & circumstances have changed since then.G ------------------------------------------------------------------------G Keith Parris|Integrity Computing,Inc.|parris@decuserve.decus.org-nospamTF VMS Consulting: Clusters, Perf., Alpha porting, Storage&I/O, Internals     Sent via Deja.comi http://www.deja.com/   ------------------------------   Date: 8 Jan 2001 23:27:02 -0500h* From: young_r@eisner.decus.org (Rob Young)* Subject: Re: Flackey fibre channel support+ Message-ID: <jRDyH83MUtUF@eisner.decus.org>a  E In article <93do72$l5j$1@nnrp1.deja.com>, kparris@my-deja.com writes:s- > young_r@eisner.decus.org (Rob Young) wrote:  >> 	With 7.3, theE< >> 	very painful merges after backup go away with mini-copy. > E > I think you're confusing merges with full-copy operations, and thusr > Mini-Copy with Mini-Merge. >   8 	Yes.  My poor choice of words there.  Copy after backup- 	as you point out and as mini-copy describes.v   				Rob    ------------------------------  # Date: Tue, 09 Jan 2001 00:18:17 GMT. From: circuitz@my-deja.com Subject: FreeVMS) Message-ID: <93dlc2$ipg$1@nnrp1.deja.com>t  B I heard about this OS abit, anyone tried it? Is it very similar to OpenVMS?0 Is it any good, supports other VMS software etc?     Sent via Deja.coma http://www.deja.com/   ------------------------------  % Date: Mon, 08 Jan 2001 21:32:01 -0600 7 From: "David J. Dachtera" <djesys.nospam@earthlink.net>o Subject: Re: FreeVMS- Message-ID: <3A5A8631.3FD88F0F@earthlink.net>C   circuitz@my-deja.com wrote:r > D > I heard about this OS abit, anyone tried it? Is it very similar to
 > OpenVMS?2 > Is it any good, supports other VMS software etc?  " FreeVMS is a dream that never was.   -- m David J. Dachterah dba DJE Systemsi http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/o  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.v   ------------------------------  % Date: Tue, 09 Jan 2001 00:36:04 -0500 ' From: Randy Hawley <rhawley@iquest.net>e Subject: Re: FreeVMS* Message-ID: <3A5AA344.A07E32E1@iquest.net>   circuitz@my-deja.com wrote:h > D > I heard about this OS abit, anyone tried it? Is it very similar to
 > OpenVMS?2 > Is it any good, supports other VMS software etc? >  > Sent via Deja.comn > http://www.deja.com/  F If you are wanting to try out VMS for free, and you have the hardware,B there is a program for "Hobbyists" that Compaq offers through the ) user group (what is that new name again?)0  B Older hardware can be had for a song (or if you can't sing, I see @ stuff all the time for the simple act of coming and getting it).  @ Of course, the license is only available for non-commercial use.   Randy,   ------------------------------  % Date: Tue, 09 Jan 2001 07:26:31 +0000e7 From: Lothar Geyer <Lothar.Geyer@EDV-Berater-Online.de>  Subject: Re: FreeVMS5 Message-ID: <3A5ABD27.1A5417DB@EDV-Berater-Online.de>i   Look at www.Free-VMS.org   Lothar Geyer   circuitz@my-deja.com schrieb:T > D > I heard about this OS abit, anyone tried it? Is it very similar to
 > OpenVMS?2 > Is it any good, supports other VMS software etc? >  > Sent via Deja.com  > http://www.deja.com/   ------------------------------   Date: 8 Jan 2001 20:28:13 GMTa& From: UCL Workstations <havoc@apk.net>+ Subject: FS: Digital AlphaStation 600 5/266e( Message-ID: <93d7st$2lm$3@plonk.apk.net>  1 Digital AlphaStation 600 for sale, last one left.bF Basic config below, more details, including spare parts, available at:  ) http://junior.apk.net/~havoc/decgear.htmlr  ! Discounts to local/pickup buyers!    Config:  -------b  5 AlphaStation 600 5/266 (Tru64 5.0/5.1 Configuration):c  	 256MB RAMh+ DEC RZ-28VW 2 GB Fast/Wide SCSI-2 Hard Diskd5 DEC RZ-29VW 4 GB Fast/Wide SCSI-2 Hard Disk (7200RPM)o DEC RRD46 6X SCSI CD-ROM Drive9 2-channel Fast/Wide SCSI & 10Base Combo Ethernet Adapter e, High-end PowerStorm 4D50T 3D PCI Framebuffer'   (ZLXp-L1 available for OpenVMS users)h Keyboard, mouse, power cables E Tru64 5.0 pre-loaded (non-commercial/commercial Tru64 license reqd.) e Tru64 5.1 available also.-   $1095.00 + Shipping    ----  C DEC 3000 series Alphas and Digital Personal Workstation 600aus alsoaI available, ck. http://junior.apk.net/~havoc/decgear.html for more detailsm and pricing.   -- n$ UCL Workstations, Servers & Networks3 A member of the auctions.workstations.org communityi Email: havoc@apk.netJ Auctions: http://auctions.workstations.org/com/plsql/usersearch?id=ucl_wsn   ------------------------------  % Date: Mon, 08 Jan 2001 21:02:13 -0600 7 From: "David J. Dachtera" <djesys.nospam@earthlink.net>r) Subject: Re: FW: start/que/search problem3- Message-ID: <3A5A7F35.AC36EF7B@earthlink.net>    Ray Phelan wrote:e >  > All, > D > We have a DCL menu facility for our clients, to restart printing a< > report from a string, using the START/QUE/SEARCH commands. > J > This was working fine, until recently we have moved our clients to AlphaA > DS10, running VMS 7.2-1.  The print queue is a LAT print queue.r > @ > When the users now use this facility, it puts the queue into aJ > "RESUMING" state, and brings the box to a grinding halt.  Usually beforeJ > this happens, we reboot the box, this also clears the state of the print > queue. > D > Is there a patch fix or bug fix for this problem, or is it a known! > problem with a work around.????o  
 I believe:   $ HELP START /QUE   < ...contains an important caveat about the /SEARCH qualifier.   -- f David J. Dachtera  dba DJE Systemse http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/v  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.e   ------------------------------  # Date: Tue, 09 Jan 2001 04:56:09 GMTk* From: martin.hunt@nbnz.co.nz (Martin Hunt) Subject: Re: Happy New Years/ Message-ID: <3a5a992a.89497079@news.xtra.co.nz>d  E On Sat, 06 Jan 2001 09:34:03 +0100, Paul Sture <paul@sture.ch> wrote:n  = >In article <3A53489F.66B256B8@videotron.ca>, JF Mezei wrote:  > Q >> According to another encyclopedia, it is defined as a scale having 180 degreesnM >> between the point of freezing and boiling of water. (degrees, angles.....)e >> >The answer I dug out from oB >http://www.school-for-champions.com/science/temperature.htmn was  >hG >"Fahrenheit used his body temperature as 100 degrees and the freezing eQ >temperature of saturated salt water as 0 degrees. He marked those levels on his lB >thermometer and divided the scale into 100 parts for each degree. >pF I read (many years ago) that the 100 degrees was the blood temperature	 of an ox.h@ And many people grew up believing that he deliberately chose the) bioling point of water to be 212 degrees!- -- Martin Hunt  Technical Specialist National Bank of New Zealand   ------------------------------    Date: 09 Jan 2001 06:13:26 +0800, From: Paul Repacholi <prep@prep.synonet.com> Subject: Re: How many.. 0 Message-ID: <878zolvgjd.fsf@k9.prep.synonet.com>   k_knutson@my-deja.com writes:s  B > I have recently been tasked to come up with a number of how manyB > techi's does it take to support our network.  We are growing and= > accounting would like to know when we need to add Techi's..0 > ? Get them to agree to being last to get help. That way they WILLI! know if you don't have enough. ;)t  6 Well, 7 days a week? 24 hour? How amny users? How many2 come/leave per week. Printers? Special print runs?  2 > So here is the question..  and Where do I look.. > - > How may systems manager per Alpha systems..a@ >          (we currently have 2 to 3 for  about 8 Alpha systems)  ! 1. for all. Subject to the above.l  4 > How may network admin per systems on the network..  8 VMS, none. Others, well... If you net is extensive, have> one person running it. Use DECnet LAT etc as much as possible.= They keep working. If you need 'network printing', point thems at the LAT queues on VMS.     & > and do say to much like it or not... > 5 > How may NT administrators per NT systems are neededs >                   as well as2 > How may NT administrators per Desktop/PC users..  B 5-8 NT boxes per person. If you are blessed with Pathworks, 1 in 5= of the PC weenies should be charged eith PW. Pick good ones!!X    E Then, add ops staff to suit hours and work load. If you do any amount ? of security printing, add another to account for that, minimum.e   -- L< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.A@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.   ------------------------------  % Date: Thu, 11 Jan 2001 21:53:20 +00002) From: Christof Brass <brass@infopuls.com>.S Subject: HW/SW for Chip Fabs (was: Compaq: A simple, affordable clusteringsolution)1, Message-ID: <3A5E2B50.B392C3FB@infopuls.com>  9 "Ken Fairfield; SLAC: 650-926-2924; FAX: 926-3515" wrote:e > . > In article <937h30$2j88$1@info.cs.uofs.edu>,= >         bill@triangle.cs.uofs.edu (Bill Gunshannon) writes:r* > > In article <G6q4BH.Ju8@world.std.com>,> > >  moroney@world.std.spaamtrap.com (Michael Moroney) writes: > [...]eC > > |> There's another reason - VMS runs all of Intel's fab plants!m > >,A > > Yes, but not on Alphas and undoubtedly not a current release.1 > J >         This is no longer true.  (1) There  are Alphas as members of theJ >     VMS  clusters  running some of the fabs.  (2) The newest fab,  beingJ >     built in the Northwest, is using an Alpha/VMS cluster.  The fab willJ >     be doing 12" wafers (current  size  is  8").   (3)  In  a  _factory_J >     environment,  you  do  _not_  change  the software willy-nilly.  YouJ >     _prove_ a certain release  and  _stay_  there  as  long as possible.J >     IIRC,  current fabs are at VMS 7.1 (VAX), not _that_ far behind  the >     release schedule.: > J >         So with, as Terry would say, "the recent unpleasantness" betweenJ >     Digital and Intel "behind us",  and  with the immenent demise of VMSE >     not realized, the Intel fabs have moved forward with Alpha/VMS.n > J >         Note, however, that currents within  Intel continue to think "weJ >     should  be  building  our chips with our own chips", and  there  areJ >     always plans to run the "next fab" on Intel processors.   It  didn'tJ >     work  out  that  way  for  the  12"  fab.  And (as readers here willJ >     understand) it's probably much less  an  issue of Intel versus AlphaJ >     procesors than an issue of VMS versus _any_ other o/s, let alone one >     which runs on Intel. > 7 >         -Ken, who's-probably-said-more-than-he-shouldu > --O >  Kenneth H. Fairfield            |  Internet: Fairfield@SLC.Slac.Stanford.Edu:< >  SLAC, 2575 Sand Hill Rd, MS 46  |  Voice:    650-926-2924< >  Menlo Park, CA  94025           |  FAX:      650-926-3515P >  -----------------------------------------------------------------------------D >  These opinions are mine, not SLAC's, Stanford's, nor the DOE's...  @ As there are new fabs every year but no new VAXen Intel has only two choices:9 change to another HW/SW system or migrate to Alpha. If wes
 consider the d? tremendous costs of a new fab the risk in screwing something upe with a new U HW/SW system seems pretty high.V< Does anybody know which HS/SW systems are being used by IBM, Motorola or AMD?> I don't consider the OS the problem. Intel is much less biased in the OS area.t> The Alpha chip is produced by Intel's fabs IIRC, but it hasn't been designed > by Intel's engineers. If VMS ran on Intel it probably wouldn't be any problem o> for Intel continuing that way. Replacing VMS might not be very
 easy because  > I expect that some realtime features of VMS are in use and not many  1 full scale OSs offer realtime features right now.]   ------------------------------  % Date: Mon, 08 Jan 2001 21:05:39 +0000$7 From: Lothar Geyer <Lothar.Geyer@EDV-Berater-Online.de>2$ Subject: Re: Microsoft Message Queue5 Message-ID: <3A5A2BA3.F4C3C1BC@EDV-Berater-Online.de>E  G You may look for BEA MessageQ (formerly DECmessageQ) available from BEAb (www.bea.com).G It is running on more than 13 platforms. And of course on VMS and NT. A_ W95 client is also available.    Lothar Geyer   Andrew Jones schrieb:e >  > Hi,d< > Is there an OpenVMS equivalent to Microsoft Message Queue? > N > I think the requirement is for an OpenVMS app to access a SQLserver database > on an NT box...Y >  > Cheers >  > Aj   ------------------------------  % Date: Mon, 08 Jan 2001 23:37:01 -0500 2 From: rdeininger@mindspring.com (Robert Deininger)3 Subject: Re: Need KZTSA information / documentation-L Message-ID: <rdeininger-0801012337010001@user-2ive6as.dialup.mindspring.com>   In article <rdeininger-0801010219320001@user-2iveal5.dialup.mindspring.com>, rdeininger@mindspring.com (Robert Deininger) wrote:    F > The KZTSA is a turbochannel option that provides a single fast wide H > differential SCSI-2 port.  It was current in 1994 or 1995, and enjoys I > living inside DEC 3000 boxes.  It's the only turbochannel option that'sv, > supported in VMS for multihost SCSI buses.  6 I've learned a little more, but I'm still pretty lost.  ) Here's a URL with some KZTSA information:5I http://www.tru64unix.compaq.com/faqs/publications/cluster_doc/cluster_15/r TCR_HWCFG/CHCNFGRN.HTM  J It gives a few more console commands than the module itself reports, tells how to change the SCSI ID and switch between fast and slow SCSI, and explains the LED and jumpers on the board.  But it's clear that there's still a lotO of info missing, so I'm still hoping someone has a real manual for the KZTSA.  I  N This tru64unix FAQ also describes some some interesting storage configurations% in more detail than I've seen before.-  J One annoying point comes out of the FAQ:  Unix clusters can have multihostSCSI busses using the PMAZC controller, as well as the KZTSA.  In turbochannel, VMS only supports the KZTSA, which is quite a bit harder to find.  Why do we get shortchanged in VMS?  Any chance the PMAZC would work in a VMS SCSI cluster, even though not supported?    P! > Some specific questions so far:  > L > 1.  Do we need to fiddle with a jumper on the board in order to enable the > firmware upgrade?0  + Apparently not, according to the above FAQ..     > 2.  >>> "test TCn ?" lists various on-board tests and utilities.  How can I change the SCSI ID of the KZTSA?  In a multi-host configuration, I'll need to 2 > change one of the modules from the default of 7.   The FAQ explains this.   >  Does anyone know how to: > interpret the on-board error logs ( >>> test TCn logs) ?  # Still no idea about the error logs.a    A > 3.  We have some modules that seem very sick.  The test reportsd > "startup failed...7 > err-mips rom object "pst-t" reported a severe error."hE > (I don't know the exact context here, since I'm relaying this part  F > second-hand.)  Is there a fix for this, short of sending the modulesF > to Compaq?  If we get the firmware upgrader going, will the "repair"H > option have a chance to fix this?  Or is this a totally different ROM?   Still stuck on this too.  I > 4.  Slightly related:  Any good sources for "Y" cables for differentiala > SCSI, to allow external termination of the bus instead of the on-board KZTSA terminators?  This would allow a multi-host bus to be unplugged from one  > KZTSA while the other KZTSA kept the bus active.  I think the DEC part number for this Y cable was BN21W, but an off-brand equivalent would do.  I've never L > seen a cable like this, but they sure look purdy in the clustering manual.E > This is a hobbyist project, so cheap is an important consideration.A  M Sorry for adding to my previous post, but I thougt the new info was worth it.i   -- c Robert Deininger rdeininger@mindspring.como   ------------------------------    Date: 09 Jan 2001 04:15:38 +0800, From: Paul Repacholi <prep@prep.synonet.com>" Subject: Re: OpenVMS opportunities0 Message-ID: <87elydx0k5.fsf@k9.prep.synonet.com>  3 "Mark D. Jilson" <jilly@clarityconnect.com> writes:s  H > Well that may be an option.  I forget what teams Laurie may be workingI > with but I know our team is willing to hire full time telecommuters and-H > may even do so shortly as I have been involved in some interviews.  IfJ > you want to telecommute and would like to work for the US CSC please seeI > the OpenVMS Jobs link and look at the jobs listed for Colorado Springs,1- > CO as some of them may allow telecommuting.   < I wonder how far their definition of telecomputing extends?    -- 	< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.n@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.   ------------------------------   Date: 8 Jan 2001 22:06:57 GMT-2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)" Subject: Re: OpenVMS opportunities6 Message-ID: <93ddm1$qcu$1@mailint03.im.hou.compaq.com>  _ In article <87elydx0k5.fsf@k9.prep.synonet.com>, Paul Repacholi <prep@prep.synonet.com> writes:d= :I wonder how far their definition of telecomputing extends? p  G   I'd expect that this would be at the discretion of the hiring manager1I   and the candidate, and -- the specific job and supervision allowing --  H   probably limited only by the availability of scheduled commercial air E   (aerospace :-) transportation and communications with the region.  iH   Australia would likely not be out of the question for some positions, I   given management support and the right candidate...  For various jobs, D/   working from Australia would be infeasible.../  E   Taken literally, Low Earth Orbit (LEO) would likely be outside the wG   telecomputing limit, if for no other reason than the transportation, e?   housing, and communications costs that would be involved. :-)s  N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Mon, 08 Jan 2001 19:27:23 -0500l- From: JF Mezei <jfmezei.spamnot@videotron.ca> " Subject: Re: OpenVMS opportunities, Message-ID: <3A5A5AE9.C0A24CA4@videotron.ca>   Hoff Hoffman wrote:bF >   Taken literally, Low Earth Orbit (LEO) would likely be outside theH >   telecomputing limit, if for no other reason than the transportation,A >   housing, and communications costs that would be involved. :-)a  J Well, LEO would be out of question not because it is far (only about 250kmI away), but because it can't answer phohnes 7*24 due to areas of its orbit  without communications.   I Also, they have some hefty firewalls which make it hard for the worker tonG access systems outside of NASA. But the view can't be beaten I am told..   ------------------------------  % Date: Mon, 08 Jan 2001 18:10:06 -07006% From: Dean Woodward <deanw@rdrop.com>G" Subject: Re: OpenVMS opportunities( Message-ID: <3A5A64EE.2943600@rdrop.com>   Hoff Hoffman wrote:. > a > In article <87elydx0k5.fsf@k9.prep.synonet.com>, Paul Repacholi <prep@prep.synonet.com> writes: > > :I wonder how far their definition of telecomputing extends? > F >   Taken literally, Low Earth Orbit (LEO) would likely be outside theH >   telecomputing limit, if for no other reason than the transportation,A >   housing, and communications costs that would be involved. :-)c  A Housing- I'd think housing costs for a telecommuter are up to thenB worker, not the company, unless the company needs an employee in aH certain location some reason.  If my relationship with my company allows@ me to live wherever I want, and I want to live on the Riveria, I1 wouldn't expect them to pay me any more to do it.6  G Communications- wireless is line-of-sight with enough watts behind it. sG Just make sure you've got a TELSAT in your neighborhood before you buy,0* or sign up for StarBand satellite service.  E Transportation- only expensive going up.  Getting down again is easy.rA (shedding excess heat and velocity is left as an exercise for theh reader.)  0 All that said, GeoSynch orbit might be better...   ------------------------------  % Date: Mon, 08 Jan 2001 17:53:45 -08001! From: Shane.F.Smith@Healthnet.com0" Subject: Re: OpenVMS opportunitiesD Message-ID: <OFC20B8E70.83C09F9D-ON882569CF.000A2DBF@foundation.com>  K LEO plus a decent knowledge of orbital mechanics, a reasonable computer andrK some kind of fine-tunable launching system should allow you to drop a largev, rock on Redmond and solve a lot of problems.  @ Maybe we should organize a fund, so we can all chip in...... ;-)   Shane           9 Dean Woodward <deanw@rdrop.com> on 01/08/2001 05:10:06 PMe   To:   Info-VAX@Mvb.Saic.Comj cc:R  # Subject:  Re: OpenVMS opportunitiesg     Hoff Hoffman wrote:e >hA > In article <87elydx0k5.fsf@k9.prep.synonet.com>, Paul Repacholie <prep@prep.synonet.com> writes:e> > :I wonder how far their definition of telecomputing extends? >HF >   Taken literally, Low Earth Orbit (LEO) would likely be outside theH >   telecomputing limit, if for no other reason than the transportation,A >   housing, and communications costs that would be involved. :-)h  A Housing- I'd think housing costs for a telecommuter are up to thehB worker, not the company, unless the company needs an employee in aH certain location some reason.  If my relationship with my company allows@ me to live wherever I want, and I want to live on the Riveria, I1 wouldn't expect them to pay me any more to do it.c  F Communications- wireless is line-of-sight with enough watts behind it.G Just make sure you've got a TELSAT in your neighborhood before you buy,a* or sign up for StarBand satellite service.  E Transportation- only expensive going up.  Getting down again is easy. A (shedding excess heat and velocity is left as an exercise for thee reader.)  0 All that said, GeoSynch orbit might be better...   ------------------------------   Date: 9 Jan 2001 02:32:40 GMTo1 From: bill@triangle.cs.uofs.edu (Bill Gunshannon)-" Subject: Re: OpenVMS opportunities, Message-ID: <93dt88$2lrc$1@info.cs.uofs.edu>  ( In article <3A5A64EE.2943600@rdrop.com>,(  Dean Woodward <deanw@rdrop.com> writes: |>3 |> All that said, GeoSynch orbit might be better...e  - Maybe, but then the view gets kind of boring.d   bill   -- MJ Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>   a   ------------------------------   Date: 8 Jan 2001 17:01:32 -0500o2 From: malmberg@eisner.decus.org (John E. Malmberg) Subject: Re: samba+ Message-ID: <0Kz0Xx6PRy1y@eisner.decus.org>l  7 In article <93c74r$96a6@eccws12.dearborn.ford.company>, 3 "Carlo Mussche" <vec.60730CM@memo.volvo.se> writes:h > hello, >g9 > I have installed samba version 2.0.3 on a Alpha VMS 7.1 > > but everytime I want to map (from my NT-station) to a drive,; > I get the message (after supplying the correct password :c >i$ > "the network name cannot be found"  2 That message can indicate many different problems.   > how can I solve this?c  < Samba 2.0.3 for OpenVMS does not support encrytped passwords? clients connecting to it.  There is a registry patch that if it = is not with your distribution kit can be obtained from one ofb$ the mirrors of http://www.samba.org.  A If you need to run with encryted passwords, then you must convert ! to using SAMBA 2.0.6 for OpenVMS..  < In my observations on using Windows NT clients to connect toC SAMBA 2.0.6 shares, the NT client would attempt to log into the VMS2= system through an special pipe that SAMBA seems to map to the?@ SAMBA GUEST account.  If the SAMBA GUEST account does not exist,D then SAMBA server will request that the NT client ask for a password for that special pipe.  C Only after it gets the password, will it attempt to find it special & pipe name in the VMS account database.  @ Since there is no corresponding VMS account when the SAMBA GUESTG account does not exist, there is no correct password for you to supply.h  A The result will be that the NT client will have failed validationL4 and not be allowed to see a list of "network names".  E As I have never actually run SAMBA 2.0.3 for OpenVMS, I would have to @ refer you to the documentation that was with it for creating the SAMBA guest account for it.p  I For SAMBA 2.0.6 for OpenVMS, the name of the SAMBA Guest account defaultsd4 to "SAMBA__GUEST" (two underscores preceding GUEST).  J SAMBA 2.0.6 for VMS seems to currently require OpenVMS 7.x because of someF issues with the FRONTPORT library.  The download locations for it are:  9 http:\\eisner.decus.org\~malmberg\samba\ and it requires:-, http:\\eisner.decus.org\~malmberg\frontport\  G Because of differences in the way that the two ports were done, and the E differences in capabilities, some of the setup and configurations are > different.  Read the installation and release notes carefully.   -Johnu wb8tyw@qsl.network  Representing only my own opinion   ------------------------------   Date: 8 Jan 2001 23:20:33 +01003* From: eplan@kapsch.net (Peter LANGSTOEGER) Subject: Re: samba* Message-ID: <3a5a3d31$1@news.kapsch.co.at>  ` In article <0Kz0Xx6PRy1y@eisner.decus.org>, malmberg@eisner.decus.org (John E. Malmberg) writes:: >http:\\eisner.decus.org\~malmberg\samba\ and it requires:- >http:\\eisner.decus.org\~malmberg\frontport\   2 Should be slashes (and not backslashes) of course.  9 http://eisner.decus.org/~malmberg/samba/ and it requires:y, http://eisner.decus.org/~malmberg/frontport/   -- n< Peter "EPLAN" LANGSTOEGER           Tel.    +43 1 81111-2651; Network and OpenVMS system manager  Fax.    +43 1 81111-888i< <<< KAPSCH AG  Wagenseilgasse 1     E-mail  eplan@kapsch.netH A-1121 VIENNA  AUSTRIA              "I'm not a pessimist, I'm a realist"   ------------------------------  # Date: Mon, 08 Jan 2001 20:41:55 GMTa From: Recruitment@KSM2000.como' Subject: Software beta testers required / Message-ID: <nCp66.19475$nu5.127887@NewsReader>    SOFTWARE BETA TESTERS REQUIRED  N Welcome to KSM2000, we are the fulfilment agents for our clients MicroService.   Our client is actively seeking to recruit 1000 beta software testers throughout Europe and we have been placed with the challenge of locating them.h  g So where better than here in your newsgroup, will we find possible candidates. This is not a SPAM mail.i   If you thing that this type of opportunity would be of interest to you, we would be grateful if you would use the link below to mail us your interest.  3 The subject line should contain:  Beta MicroserviceA   And the contents: Your full name, address, postcode and of course your E-mail address. On receipt of this mail we will forward you full details of the positions available.e    ; Please note this is not a full time employment opportunity.s    Mailto: Microservice.Ksm2000.com   ------------------------------   Date: 8 Jan 2001 18:49 CST' From: carl@gerg.tamu.edu (Carl Perkins) D Subject: Re: vax basic - can someone remind me how this works again?, Message-ID: <8JAN200118493855@gerg.tamu.edu>  % Beyonder <beyonder@vrx.net> writes...-/ }>After 25 years of programming in DEC flavoredo0 }>BASIC, I've never encountered the need to read2 }>only one byte from a file, unless perhaps I knew/ }>the record was only one byte.  BASIC likes tom/ }>process records rather than individual bytes.m } 3 }never? that's amazing. what if you need to processu8 }a "binary" file? what about file encryption/decryption?; }what about a million other uses where the file isn't text?o: }I even play with manipulating EXE files on a daily basis.6 }then there's graphic images, raw files, and so forth.  B The answer to this is trivial: you don't read one byte and processB one byte, you read in a whole record and then process it a byte at a time.e  7 }that won't work at all. there are no "records" in purey5 }binary files. ie: EXEs, or encrypted files, or other < }types, like graphic images, and so forth. the list goes on.  > These all have records in the RMS sense. EXE files for example= are fixed length 512 byte record files. It is irrelevant thatVA this isn't the real record structure of the data in this sense - -C you just read a full 512 byte record from the disk into your bufferA@ and process it however you want from there. Likewise for all the= other files. The only ones you may have trouble with are someMA oddball formats (that can be essentially recordless as far as RMSrA is concerned, but those are rare and not generally intended to be A accessed via RMS) and stream formats that try to use rediculouslyp
 long records.c   --- Carl   ------------------------------   Date: 8 Jan 2001 16:05:25 PST-T From: Fairfield@SLAC.Stanford.EDU (Ken Fairfield; SLAC: 650-926-2924; FAX: 926-3515)? Subject: Re: [Q] Which model Exabyte in TKZ09 and TKZ15 drives?o3 Message-ID: <OStLxIkams09@mccdev.slac.stanford.edu>7  G In article <3A5785AD.F7EB78ED@usa.com>, guppy <guppy99@usa.com> writes:0G > The TKZ09 is an 8500S (5 gig - no compression).  The TKZ15 is an 8505(L > which, I believe, writes only in compressed mode (10 gig), but will read 5I > gig tapes written on the 8500's as well as the 10 gig compressed tapes.   F         OK, that's helpful.  But I'm still confused.  The drive in theF     problematic TKZ9E shows up on an AlphaServer 4100's console and at'     VMS (7.2-1) in SHOW DEVICE/FULL as,   !         EXABYTE EXB-85058SQAANXR1e  H     Is this an "8505" or an  "85058"  or an "85058S" or what?  Again, myH     problem is that, _supposedly_, the TKZ15 is supported on an HSC-95'sH     k.scsi  requestor under HSC Software 8.6, but a TKZ9E is not listed.H     From what you've posted, an "8500" would server my needs, but if theH     "8505" in the TKZ9E is the same  as  in  the  TKZ15,  then  I've  noH     confidence  in  the HSC documentation on this matter since the TKZ9E     "doesn't work".i           Thanks, Kenn --M  Kenneth H. Fairfield            |  Internet: Fairfield@SLC.Slac.Stanford.Edui:  SLAC, 2575 Sand Hill Rd, MS 46  |  Voice:    650-926-2924:  Menlo Park, CA  94025           |  FAX:      650-926-3515N  -----------------------------------------------------------------------------B  These opinions are mine, not SLAC's, Stanford's, nor the DOE's...   ------------------------------    Date: 09 Jan 2001 10:57:07 +0800, From: Paul Repacholi <prep@prep.synonet.com>? Subject: Re: [Q] Which model Exabyte in TKZ09 and TKZ15 drives? 0 Message-ID: <873detsa9o.fsf@k9.prep.synonet.com>  V Fairfield@SLAC.Stanford.EDU (Ken Fairfield; SLAC: 650-926-2924; FAX: 926-3515) writes:  I > In article <3A5785AD.F7EB78ED@usa.com>, guppy <guppy99@usa.com> writes:II > > The TKZ09 is an 8500S (5 gig - no compression).  The TKZ15 is an 8505 N > > which, I believe, writes only in compressed mode (10 gig), but will read 5K > > gig tapes written on the 8500's as well as the 10 gig compressed tapes.e > H >         OK, that's helpful.  But I'm still confused.  The drive in theH >     problematic TKZ9E shows up on an AlphaServer 4100's console and at) >     VMS (7.2-1) in SHOW DEVICE/FULL as,i > $ >         EXABYTE EXB-8505 8SQAANXR1:                 model     ^ FW rev, sort of. FW signature? Upgrade the FW, it changes.e   -- ,< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.i@                                              West Australia 6076. Raw, Cooked or Well-done, it's all half baked.   ------------------------------   Date: 8 Jan 2001 21:52:52 +0100n* From: eplan@kapsch.net (Peter LANGSTOEGER)4 Subject: Re: [TCPIP V5.0A ECO1] BIND Server errors ?* Message-ID: <3a5a28a4$1@news.kapsch.co.at>  ] In article <3A59E7F1.80FF17C2@compaq.com>, Jason Fountain <Jason.Fountain@compaq.com> writes:oM >The 'zone dump failed' message is nothing to be worried about.  All it means K >is that you have not specified the TCPIP$BIND_SERVER_MERGE_DYNAMIC_UPDATEStN >logical.  This logical tells the bind server, when receiving dynamic updates,J >to write the database to disk (once per hour).  The problem with definingI >this logical is that when the db is written, all formatting and comments  >of your db are lost.u  J I didn't find this in the management manual, and so I didn't notice (it isD documented in the concepts manual). Thanks, this is indeed the case.F So, this is an ERROR I should ignore. Why not change it to a WARNING ?  I btw: once per hour doesn't seem to be exact as you can see in the logs...     ' What about the other problem with W2K ?n     TIAe   -- G< Peter "EPLAN" LANGSTOEGER           Tel.    +43 1 81111-2651; Network and OpenVMS system manager  Fax.    +43 1 81111-888i< <<< KAPSCH AG  Wagenseilgasse 1     E-mail  eplan@kapsch.netH A-1121 VIENNA  AUSTRIA              "I'm not a pessimist, I'm a realist"   ------------------------------  % Date: Mon, 08 Jan 2001 14:20:35 -0700 % From: Dean Woodward <deanw@rdrop.com>t4 Subject: Re: [TCPIP V5.0A ECO1] BIND Server errors ?) Message-ID: <3A5A2F23.8CB6AF99@rdrop.com>i   Peter LANGSTOEGER wrote:  ) > What about the other problem with W2K ?   G "other" problem?  I'm afraid you'll have to be more specific than that.- ;-)-   ------------------------------   Date: 8 Jan 2001 23:13:55 +0100h* From: eplan@kapsch.net (Peter LANGSTOEGER)4 Subject: Re: [TCPIP V5.0A ECO1] BIND Server errors ?* Message-ID: <3a5a3ba3$1@news.kapsch.co.at>  Q In article <3A5A2F23.8CB6AF99@rdrop.com>, Dean Woodward <deanw@rdrop.com> writes:m >Peter LANGSTOEGER wrote:: >i* >> What about the other problem with W2K ? >bH >"other" problem?  I'm afraid you'll have to be more specific than that.  G My original posting had 2 problems mentioned and only one was referred./ Read again.e  J btw. In a private email I got an answer that the problem is currenly under investigation...   -- 4< Peter "EPLAN" LANGSTOEGER           Tel.    +43 1 81111-2651; Network and OpenVMS system manager  Fax.    +43 1 81111-888a< <<< KAPSCH AG  Wagenseilgasse 1     E-mail  eplan@kapsch.netH A-1121 VIENNA  AUSTRIA              "I'm not a pessimist, I'm a realist"   ------------------------------  # Date: Mon, 08 Jan 2001 20:04:46 GMT8+ From: Craig A. Berry <calepine@my-deja.com>RY Subject: Re: [Update] APACHE (CSWS) + MOD_PERL = No private process logicals definablein  ) Message-ID: <93d6go$5fg$1@nnrp1.deja.com>b   Andy,a  > I'm not that familiar with mod_perl, but the Perl source has a8 suspicious-sounding comment in its getenv() replacement:   /* my_getenvB * Translate a logical name.  Substitute for CRTL getenv() to avoidB * memory leak, and to keep my_getenv() and my_setenv() in the sameA * domain (mostly - my_getenv() need not return a translation fromi! * the process logical name table)  *t    D Isn't the process table the one that goes AWOL?  my_getenv() depends< on my_trnlnm(), which as far as I can tell only looks at theE LNM$FILE_DEV table.  All this would only be relevant if Perl is beingl@ used to create the subprocess, and I have no idea whether that'sA true.  Have you tried populating LNM$FILE_DEV and seeing if thosea logicals survive?9        9 In article <Ick66.208582$DG3.5008301@news2.giganews.com>,s-   "Andy Stoffel" <acs@fcgnetworks.net> wrote:?E > I've experimented a little with this this weekend on another systemx runningtB > the same version of VMS, TCPIP, Apache, etc that I can reboot at	 will.....nA > and now I understand it even less %-).... changing CHANNELCNT &h > CTLPAGES had no effect.s >l	 > Anyway:  >S? > For the sub-process APACHE$WWW_4 with mod_perl enabled I get: < > (This is generated using a SHOW LOG * in TEST-CGI-VMS.COM) >y" > (LNM$PROCESS_TABLE)     [kernel]5 >                         [no protection information]f > 4 >   "APACHE$CGI_USE_DCLCOM_FOR_IMAGES" [super] = "1"* >   "APACHE$INPUT" [super] = "SYS$COMMAND"E >   "APACHE_SCRIPT" [super] = "APACHE$ROOT:[000000]APACHE_SCRIPT.COM"n/ >   "APACHE_SHARED_SOCKET" [super] = "_BG3881:"i >         = "_BG3880:", >   "PERL5LIB" [super] = "/apache$root/perl"8 >   "SYS$COMMAND" [super,confine] = "_BG3887" [terminal]. >   "SYS$COMMAND" [exec] = "_NLA0:" [terminal]' >   "SYS$DISK" [super] = "APACHE$ROOT:"t& >   "SYS$DISK" [exec] = "APACHE$ROOT:"6 >   "SYS$ERROR" [super,confine] = "_BG3892" [terminal]. >   "SYS$ERROR" [exec] = "_BG3889:" [terminal]F >   "SYS$INPUT" [super,confine] = "_HLDRNS$DKA0:" [concealed,terminal], >   "SYS$INPUT" [exec] = "_NLA0:" [terminal]B >   "SYS$OUTPUT" [super,confine] = "_BG3889:" [concealed,terminal]/ >   "SYS$OUTPUT" [exec] = "_BG3889:" [terminal]y >   "TT" [exec] = "_NLA0:" >m9 > But if I put a SHOW LOG * in the APACHE$WWW LOGIN.COM If > get:B > (It looks like my logicals defined in that LOGIN.COM ( CC$TEST )A > and SYLOGIN.COM (EVE$INIT) are being created on initial startupl? > but aren't being created in any APACHE sub-process afterward.  >a; > IF I define APACHE$CGI_MODE to be 2 those APACHE specificDE > process logicals DO appear in the process logicals, as they should.W >h > (LNM$PROCESS_TABLE)  >  >   "CC$TEST" = "Testing..."% >   "EVE$INIT" = "SYS$LOGIN:EVE.INIT" # >   "SYS$COMMAND" = "_HLDRNS$DKA0:"o >   "SYS$DISK" = "APACHE$ROOT:"s! >   "SYS$ERROR" = "_HLDRNS$DKA0:"-+ >   "SYS$INPUT" [super] = "_HLDRNS$DKA200:"h( >   "SYS$INPUT" [exec] = "_HLDRNS$DKA0:" >   "SYS$NET" = "NL:" * >   "SYS$OUTPUT" [super] = "_HLDRNS$DKA0:") >   "SYS$OUTPUT" [exec] = "_HLDRNS$DKA0:" 2 >   "TT" = "APACHE$ROOT:[000000]APACHE$SERVER.COM" > E > Unless there is something different in how a sub-process is createdoF > by Apache when mod-Perl is enabled I'm at a loss..... and if that IS5 > what is happening I don't know enough to fix it....5 >" > Ideas/suggestions welcome. >  > -Andy- >e >s     Sent via Deja.come http://www.deja.com/   ------------------------------  # Date: Mon, 08 Jan 2001 21:31:53 GMTs* From: "Andy Stoffel" <acs@fcgnetworks.net>Y Subject: Re: [Update] APACHE (CSWS) + MOD_PERL = No private process logicals definablein e9 Message-ID: <dlq66.179423$IP1.6505454@news1.giganews.com>e  = Rick Barry (Compaq) was kind enough to check into this and to  paraphrase/shorten what he told me:  F      In CSWS, mod_perl is currently reinitializing the process logicalE     name table for EVERY http request so defining process logicals in0+     LOGIN.COM or  SYLOGIN.COM doesn't work.-  D In my case, defining the logicals I need for the web application I'm? dealing with later on in a CGI script (one of several suggested.; work-arounds) is possible but cumbersome. Hopefully, a less5C "scorched-earth"  approach to dealing with the process logical name:- table by mod_perl  + CSWS will be worked out.v   -Andy-   ------------------------------   End of INFO-VAX 2001.017 ************************