1 INFO-VAX	Sat, 26 Oct 2002	Volume 2002 : Issue 592       Contents:3 Re: 6 free RA81 disks near philly (for pickup only) 3 Re: 6 free RA81 disks near philly (for pickup only)  Re: backup saveset( Re: Fiorina Gets Feisty at Gartner Event5 Re: How can I determine the device of the system disk  Re: Immutable laws of the PC Re: Immutable laws of the PC# Re: Makefile to call a command file  Re: OpenVMS 7.3-1 and CSWING Re: OpenVMS 7.3-1 and CSWING Re: page or pagelet  Re: page or pagelet  Re: page or pagelet ( Re: Quorum disk appears to not be voting( Re: Quorum disk appears to not be voting( Re: Quorum disk appears to not be voting  Re: So I went to the HP IT forum  Re: So I went to the HP IT forum  Re: So I went to the HP IT forum  Re: So I went to the HP IT forum  Re: So I went to the HP IT forum  Re: So I went to the HP IT forum  Re: So I went to the HP IT forum Re: TSM on the Freeware disk  F ----------------------------------------------------------------------  % Date: Sat, 26 Oct 2002 16:18:29 +0200 " From: "Hans Vlems" <hvlems@iae.nl>< Subject: Re: 6 free RA81 disks near philly (for pickup only)4 Message-ID: <ape88b$o5qb$1@ID-143435.news.dfncis.de>  9 "Brian Hechinger" <wonko@4amlunch.net> schreef in bericht 3 news:20021025050822.A1728947@marvin.4amlunch.net... J > Dave McGuire and I had the good fortune of being able to rescue that lot ofI > PDP-11/70 kit from Williamsport, PA.  in there was a pile of stuff that  noneL > of us really want or need.  one of those things is 6 RA81 disks.  they are* > currently arranged in 3 DEC short racks. > G > come take them, they are under a tarp in my driveway.  come before it  snows. > J What is the problem with snow? Power these beasts up and you won't need to. remove snow from your driveway all winter ....   ------------------------------   Date: 26 Oct 2002 14:48:21 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)< Subject: Re: 6 free RA81 disks near philly (for pickup only)4 Message-ID: <ape9vj$p3vv$1@ID-135708.news.dfncis.de>     :  "Brian Hechinger" <wonko@4amlunch.net> schreef in bericht4  news:20021025050822.A1728947@marvin.4amlunch.net...J > Dave McGuire and I had the good fortune of being able to rescue that lot  of I > PDP-11/70 kit from Williamsport, PA.  in there was a pile of stuff that   none L > of us really want or need.  one of those things is 6 RA81 disks.  they are* > currently arranged in 3 DEC short racks. > G > come take them, they are under a tarp in my driveway.  come before it   snows.  >   ? It's just too bad you didn't say anything before the trip.  You @ could have dropped them off here and not hauled them all the wayC to Philly in the first place.   I still use RA8x disks on the PDP's C at the University (where I don't have to pay for the electricity or  the air conditioning.  :-)   bill   --  J 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>       ------------------------------   Date: 26 Oct 2002 01:26 CDT ' From: carl@gerg.tamu.edu (Carl Perkins)  Subject: Re: backup saveset - Message-ID: <26OCT200201260796@gerg.tamu.edu>   5 "David J. Dachtera" <djesys.nospam@fsi.net> writes...  }Brian Tillman wrote:  }>  L }> >Thank you for your suggestion. I tried that but the size of the original2 }> >save set is approx 303k blocks and when I copy= }> >it to disk it goes to over 1.8 mill. It does not stay the  }> >same size. }>  0 }> The default block size on tape is 8192 bytes. } F }Is that the default for BACKUP or is that stated as the default block/ }size in the ANSI labelled tape specifications?  }  }--  }David J. Dachtera  G If you allow BACKUP to mount the tape, it defaults to 8192 byte blocks. F If you manually MOUNT a labeled tape, it defaults to 2048 byte blocks.  I The former has a /BLOCK_SIZE=n qualifer and the latter has a /BLOCKSIZE=n I qualifier (one of those fairly rare small inconsitenceis in DCL, although I the can both be specified as just /BLOCK=n). BACKUP's has a minimum value ! of 2048, MOUNT can go much lower.    --- Carl   ------------------------------  # Date: Sat, 26 Oct 2002 13:58:26 GMT & From: Bob Willard <BobwBSGS@attbi.com>1 Subject: Re: Fiorina Gets Feisty at Gartner Event ) Message-ID: <3DBA9FAA.E41B4D27@attbi.com>    Dave Weatherall wrote: > % > Reading this thread  made me wonder  > G > Has the downturn in the (IT) economy been a good thing or a bad thing  > for the merger?  > 9 > Has it masked any fundamental flaws or made them worse?  >  > Sugar! OT again - sorry. >  > -- > Cheers - Dave.  @ In the highly unlikely but theoretically possible event that the= merger is ever so slightly less successful than Carly'n'Curly < had predicted, then a general downturn in IT spending offers? a defendable excuse behind which the dynamic duo can hide while / continuing to inhale their lofty remunerations.  --   Cheers, Bob    ------------------------------  % Date: Sat, 26 Oct 2002 10:01:57 +0200 ) From: Bart Zorn <B.Zorn@xs4all.nospam.nl> > Subject: Re: How can I determine the device of the system disk* Message-ID: <apdi5l$a7n$1@news1.xs4all.nl>   rok@nuk.uni-lj.si wrote:@ > In Article <OF641887E1.62603D0E-ON85256C5C.006EB209@metso.com>  > norm.raphael@metso.com writes: > 7 >>Is there any easier way than capturing the output of:  >>$ RUN SYS$SYSTEM:SYSMAN ! >>SYSMAN> SET ENVIRONMENT/CLUSTER - >>%SYSMAN-I-ENV, current command environment: " >>    Clusterwide on local cluster" >>    Clusterwide on local cluster: >>    Username MASTER       will be used on nonlocal nodes >>' >>SYSMAN> DO SHOW LOGICAL SYS$SYSDEVICE 3 >>%SYSMAN-I-OUTPUT, command execution on node NODEA 2 >>  "SYS$SYSDEVICE" = "DSA100:" (LNM$SYSTEM_TABLE)3 >>%SYSMAN-I-OUTPUT, command execution on node NODEB 1 >>  "SYS$SYSDEVICE" = "DSA11:" (LNM$SYSTEM_TABLE) 3 >>%SYSMAN-I-OUTPUT, command execution on node NODEC 2 >>  "SYS$SYSDEVICE" = "DSA150:" (LNM$SYSTEM_TABLE) >>SYSMAN> EXIT >>$  >>8 >>so that I know for each node the system disk device on >>each of the other nodes? >  > > > $ define/system/executive/nolog/table=lnm$syscluster_table -2 >    'f$getsyi("SCSSYSTEMID")'$SYSDEVICE 'sysdev': >  > in SYSTARTUP_VMS.COM. > >  I miss item SYSDEVICE in f$getsyi too. I even wouldn't mind) > having it functional in SYLOGICALS.COM.  > 
 > Regards, > F > Rok Vidmar                       Internet:  rok.vidmar@nuk.uni-lj.si= > National and University Library  Phone:     +386 1 421 5461 = > Turjaska 1, SI-1000 Ljubljana    Fax:       +386 1 421 5464 
 > Slovenia  1 Good idea! But may I suggest a small improvement:   * $ define/exec/nolog/table=lnm$syscluster -@     'f$getsyi("nodename")'_SYSDEVICE 'f$trnlnm("sys$sysdevice")'  E - /system conflicts with /table=lnm$syscluster_table and is overruled     by the latter? - use 'nodename' in stead of 'scssystemid': easier to recognize A - use an underscore in stead of a dollar for 'user' logical names    Regards,  	 Bart Zorn    ------------------------------  % Date: Sat, 26 Oct 2002 15:42:44 +0300 1 From: "mariuz pop andy" <mariuz@stop.spamming.us> % Subject: Re: Immutable laws of the PC = Message-ID: <pan.2002.10.26.12.42.44.343629@stop.spamming.us>   : http://news.com.com/2100-1001-963447.html?tag=fd_lede1_hed  I Torvalds also griped about Intel's decision to push its high-end Itanium  D "IA-64" processors over its current Pentium and Xeon "IA-32" lines. 7 The Itanium processor, codeveloped by Hewlett-Packard,  > is a 64-bit chip built to accommodate vast amounts of memory, ? but the commands it understands are drastically different from  > those understood by the 32-bit Pentium line. Torvalds said he I preferred AMD's approach to 64-bit computers, keeping the same commands,  2 or "instruction set," but adding 64-bit abilities.  : "I really dislike IA-64. I think it's a losing strategy," @ Torvalds said. "My personal hope is that IA-64 withers and dies < because there's no point. It performs badly; it's expensive;"  it's an all-new instruction set."  9 "The reason Intel was so hugely successful was they went  9 for the mass market, for normal users. They went for all  2 the things that Intel stands for today," he said. 2 AMD is staying truer to that philosophy, he said. 4 I find AMD's approach a lot more interesting, which 5 is to replace a 32-bit Athlon with a 64-bit Athlon... H They come from below and eat up all the high-performance big computers."  ; Intel and HP don't dispute that Itanium is very different,  9 but argue that a radical revamp was required to create a  * new architecture that would last decades. 6 In addition, they argue, the chip comes with features 7 for protecting data integrity, pumping data on and off  2 the chip more rapidly and working better in large # computers with multiple processors.   7 On Fri, 25 Oct 2002 08:12:23 +0000, David Mathog wrote:    > In this article: > , >   http://www.theinquirer.net/?article=5894 >  > 4 > - New product must cost less while providing equal; >     functionality/performance to previous generation, or, > > - New product must provide greater functionality/performance7 >     at a cost comparable to previous generation, and, 2 > - New product must maintain legacy compatibilityI > - New product replaces existing product of monopolist, who discontinues , >     previous product.  (Forced migration). >    ------------------------------  % Date: Sat, 26 Oct 2002 13:56:33 -0400 * From: "Bill Todd" <billtodd@metrocast.net>% Subject: Re: Immutable laws of the PC 2 Message-ID: <7a2dnfcGboaiSiegXTWcpw@metrocast.net>  8 "Rob Young" <young_r@encompasserve.org> wrote in message- news:kGbNNgX+hCte@eisner.encompasserve.org...    ...   K > If Intel's desktop chips will get a 1MB L2 cache, what about their server I > solutions? It has been well known that Intel's Madison processor (third L > generation derivative of Itanium) would have a massive 6MB on-die L3 cache on aH > 0.13-micron process, but armed with Intel's 90nm process the Montecito coreK > (fourth generation Itanium) will boast an incredible 12MB on-die L3 cache  using 1 > close to 800 million of these 90nm transistors.  >  > > > Opteron is a wonderful CPU, but certainly won't compete with6 > Itanium and a 800 million transistor/12 MByte cache.  E It occurred to me that perhaps the reason you were inclined to go all E slack-jawed over the 6 MB / 12 MB of cache in future Itanics might be J because you don't understand that with main-memory latency held relativelyL constant (at least through Montecito:  it takes an architectural change suchG as Hammer's on-chip controller reduce it any faster than the relatively K leisurely rate of latency improvement the basic DRAM manufacturers achieve) H you *need* to double the amount of cache in the chip for every 40% or soL increase in clock rate just to keep performance increases fairly linear withL clock frequency.  So if Montecito clocks at about 2 GHz (compared with 1 GHzL for McKinley and 1.4 GHz or so for Madison) it will *need* all that 12 GB ofK cache in 2004 just to achieve twice the performance of McKinley (1600 or so K SPECint) - and if you're optimistic that Montecito will clock faster than 2 I GHz, then even 12 MB won't be sufficient to keep the performance increase G linear (i.e., at 2.25 GHz a SPECint score of 1800 would start to become < difficult to attain with 'only' 12 MB of cache on the chip).  J Of course, a 2004 90 nm. Opteron will also need twice as much cache as theJ initial Opteron to achieve SPECint scores in the area of 2000 at about 2.8H GHz (given that 20% improvement for 64-bit code that Fred Weber expects,K which would put the initial Opteron a bit over 1400 in 64-bit mode).  But a J mere 2 MB of cache on that Opteron will satisfy that requirement, yieldingK superior performance on a single-core chip 1/6 the size of Montecito's that G would use less than half Montecito's power.  If they do go to dual-core J Opterons in 2004 (presumably with a 4 MB on-chip shared cache), that wouldE still keep the overall chip size at about 1/3 that of the single-core K Montecito chip size while offering more performance *per core* - i.e., over < twice the performance per chip while using less total power.  I So the 800 M transistors and 12 MB cache in Montecito, impressive as they L may seem, will not result in any dramatic speed improvement:  they're merelyI continuing the brute-force tradition this architecture has established of H being fatter, hotter, and more expensive while struggling to achieve theK commercial performance of its slimmer, cooler, less expensive competition - 6 of which Hammer is about to become the prime exemplar.   - bill   ------------------------------    Date: 25 Oct 2002 23:17:46 -0700) From: P.Young@unsw.EDU.AU (Patrick Young) , Subject: Re: Makefile to call a command file= Message-ID: <55f85d77.0210252217.459de06d@posting.google.com>   v "Christian Zander" <czander@crazypag.de> wrote in message news:<apatev$mvc$2@newsreader2.lb-lan.ka.de.kpnqwest.net>...  < > I'd like to compile and link under OpenVMS using gnu-make.D > Within that process, I'd like to start a batch file (aselink.com).  
 H t makefile.  makefile1: makefile          \@test H t test.com  $ write sys$output "hello world"   H make -f makefile \@test hello world  H    ------------------------------  # Date: Sat, 26 Oct 2002 08:08:35 GMT ! From: Carlos Costa <calo@shaw.ca> % Subject: Re: OpenVMS 7.3-1 and CSWING ( Message-ID: <B9DF9B92.1DCF%calo@shaw.ca>   On 10/25/02 7:34 PM, in article F rdeininger-2510022234130001@1cust118.tnt2.nashua.nh.da.uu.net, "Robert- Deininger" <rdeininger@mindspring.com> wrote:    > A >> Yes, that is true. That is why they added the statement "If an F >> application compatibility problem is discovered, Compaq will assignI >> the problem a high priority and commit to providing a fix.". They know G >> that that may happen, and guess what? It did. No surprise there. The A >> only surprise is why people are opposed to finding a solution.  > G > I think several folks _here_ have offered pointers toward a solution.  >   L Yes, you are right. My sincere apologies if I sounded like I was disparagingJ the group. I didn't mean to. 99% of the postings have been very helpful. IJ just got riled by the particular poster's tone. Not like me, actually, I'mE usually meek and mild... My only excuse is that I'm going through CWS   (CSWING Withdrawal Syndrome. :-)     L > The first part of the solution is to remove any latent bugs in CSWING thatL > might be the cause of the symptom.  If bugs remain that are due to V7.3-1,4 > then it's time to beat HP over the head with them. > K > IMHO, Compaq's compatibility statement is far too strong to be realistic. H > It was probably written by a marketing person.  I can't picture a saneL > engineer making this statement with a straight face.  HP will have to sort	 > it out.  >   H It does seem strong to me too. I was not trying to say that it was true,I only that that's what HP said. But there are several types of updates and F this one is supposed to be the mildest sort (Enhancement Release) so IK really think that they expected most, if not all, code to be compatible. It L just looks like something slipped between the cracks. And really, it mattersK little to me whether it is a VMS or a CSWING bug or a combination. I'd just ! like to get CSWING working again.    >>  # >> Actually, I did. What I got was:  >>  $ >> Searching, root = SHODAN:[000000]% >> %SYSTEM-W-NOSUCHFILE, no such file  > J > Ah!  This is useful.  "No such file" means we asked for a file spec that > isn't there. > I > Might be worth looking at whether the program deals with this condition  > properly.   L Actually, it does. The next little bit of code checks for this condition. ItB looks to me that NOSUCHFILE and the NOMOREFILES seem to be the two conditions checked for.    > H > The traceback is useful if you are trying to debug with a link map andI > compiler listings.  It shows each level in the call chain of functions. L > The addresses given here can be matched up with specific lines of code andJ > specific machine instructions.  The traceback answers the question, "how > did we get here".  > J > But this isn't a very fun way to debug.  It's much easier to use the VMSL > debugger.  There's a fair learning curve for that, but the debugger manual > is quite good.     2 >> %TRACE-W-TRACEBACK, symbolic stack dump follows >  > <snip> > ' >> %SYSTEM-W-NOMOREFILES, no more files  > 1 > This is a different condition, "no more files".  > % >> %SYSTEM-W-NOSUCHFILE, no such file  >  > And another "no such file"...  >  > etc. >  > H >> It means absolutely nothing to me. Told you I was weak in VMS systems >> programming.  > J > I given one or two hints above.  I don't have the program in front of meL > to do more investigating.  See the C documentation and the debugger manualJ > if you are interested in gaining debugging skills, and feel free to post > questions here.   L Thanks for your hints. I have also been reading the stuff that was suggestedF earlier (VMS Answer Man articles, etc). The debugger manual is BIG andF daunting, but I think that will be my next go at trying to see what isL happening. I guess one must start somewhere, but I suspect that someone will get CSWING working before I do.      Carlos   ------------------------------    Date: 26 Oct 2002 07:56:07 -0700: From: craig.berry@SignalTreeSolutions.com (Craig A. Berry)% Subject: Re: OpenVMS 7.3-1 and CSWING = Message-ID: <7f15589f.0210260656.2e947aa0@posting.google.com>   
 In article    B <rdeininger-2510022234130001@1cust118.tnt2.nashua.nh.da.uu.net>,  6  rdeininger@mindspring.com (Robert Deininger) wrote:        & > >Searching, root = SHODAN:[000000]  ' > >%SYSTEM-W-NOSUCHFILE, no such file    >   L > Ah!  This is useful.  "No such file" means we asked for a file spec that   > isn't there.   >   K > Might be worth looking at whether the program deals with this condition   
 > properly.      3 From get_dirs in swing.c after an IO$_ACCESS qio:               /*  ,         **  file in dir but not indexf.sys           */  (         if (iosb[0] == SS$_NOSUCHFILE)           {                fib.fib$l_wcc++;               continue;            }      B Isn't the "wild card context" of the file information block one ofD those opaque longword values that one should not depend on coming inE sequence, much less increment oneself and hope that doing so will not E get you in trouble?  I certainly don't see anything in the I/O User's F Guide that suggests I could predict or should attempt to influence theF value of the wcc.  I have a strong suspicion that the code I've quotedA is the source of the looping problem.  Section 1.3.1.2 of the I/O  User's Guide says:   D "On the first lookup, FIB$L_WCC should contain zero entries. On eachC lookup, the ACP returns a nonzero value in FIB$L_WCC, which must be C passed back on the next lookup call. In addition, you must pass the B resultant name string returned by the previous lookup using the P4B result string buffer, and its length in the P3 result length word.D This string is used together with FIB$L_WCC to continue the wildcard1 search at the correct position in the directory."    D The code in question, in addition to depending on what appears to beE undocumented (and apparently obsolete) behavior of the context value, C also does not pass the previous result name on subsequent calls (it F zeros the first byte of the name string before each QIO and also zeros the length).   C John Malmberg's approach of following the compiler warnings will no @ doubt bring great improvement to the package, but there are alsoD things that should be rethought and possibly reimplemented.  I wouldC expect that lib$find_file (or even readdir() for that matter) would E offer a more maintainable method for getting a directory listing than  the QIO method.    ------------------------------  % Date: Sat, 26 Oct 2002 08:53:54 -0400 * From: "Bill Todd" <billtodd@metrocast.net> Subject: Re: page or pagelet2 Message-ID: <6XmdnfJta9nNDSegXTWcpA@metrocast.net>  , <VAXman- @SendSpamHere.ORG> wrote in message* news:00A1604A.671C97D4@SendSpamHere.ORG...@ > In article <n6ycnW6ZZaXZdCSgXTWcrg@metrocast.net>, "Bill Todd"  <billtodd@metrocast.net> writes: > > G > >"Daryl Jones" <jones.computer.srv@worldnet.att.net> wrote in message : > >news:8a646952.0210251344.705a9554@posting.google.com...   ...   I > >> To estimate the resources needed for an Alpha migration environment,  > >> consider the following:/ > >>  Greater image size on the Alpha systems"  > > I > >No shit.  However, no one in any way suggested that image sizes didn't  growD > >somewhat in the migration to RISC:  we just pointed out that your
 contention3 > >that they grew by a factor of 5 - 6 was rubbish.  > K > I objected to the image size increase being the impetus for larger pages.   ? So did I, but that wasn't the particular point addressed above.    - bill   ------------------------------  # Date: Sat, 26 Oct 2002 11:31:15 GMT " From:   VAXman-  @SendSpamHere.ORG Subject: Re: page or pagelet0 Message-ID: <00A1604A.20082F5B@SendSpamHere.ORG>  w In article <8a646952.0210251344.705a9554@posting.google.com>, jones.computer.srv@worldnet.att.net (Daryl Jones) writes: e >"Tom Linden" <tom@kednos.com> wrote in message news:<CIEJLCMNHNNDLLOOGNJIKEIAFPAA.tom@kednos.com>...  >> >-----Original Message-----F >> >From: VAXman- @SendSpamHere.ORG [mailto:VAXman- @SendSpamHere.ORG], >> >Sent: Thursday, October 24, 2002 2:21 PM >> >To: Info-VAX@Mvb.Saic.Com   >> >Subject: Re: page or pagelet >> > >> >@ >> >In article <8a646952.0210241256.296d1d1@posting.google.com>,= >> >jones.computer.srv@worldnet.att.net (Daryl Jones) writes: 0 >> >>VAXman-  @SendSpamHere.ORG wrote in message0 >>  news:<00A15D65.98CDBFDF@SendSpamHere.ORG>...; >> >>> In article <ap41pv$t0g1@rain.i-cable.com>, "Kenneth" ' >>  <yeung_kenneth@hotmail.com> writes: B >> >>> >In VMS 7.2-1, Alpha 8400. Does any on know when I do a mon >>  page, the freeD >> >>> >page list and the modified page list shown is in the unit of >>  page (8KB) or  >> >>> >pagelet (512K)?  >> >>> > >> >>> > >> >>> >> >>> Hmm.  Let's see.  >> >>>( >> >>> When I do it on my system, I see: >> >>> >> >>> $ MONITOR PAGE : >> >>>                             OpenVMS Monitor Utility= >> >>>                            PAGE MANAGEMENT STATISTIICS 
 >> >>>   :I >>                                   CUR        AVE        MIN        MAX 
 >> >>>   :< >> >>>     Free List Size               237273.00  237273.59 >>  237273.00  237276.00< >> >>>     Modified List Size              350.00     350.00 >>  350.00     350.00  >> >>> >> >>> >> >>> Then, if I issue: >> >>> >> >>> $ SHOW MEMORY/PHYSICAL G >> >>>               System Memory Resources on 22-OCT-2002 15:05:49.40  >> >>>C >> >>> Physical Memory Usage (pages):     Total        Free      In  >>  Use    Modified ; >> >>>   Main Memory (2048.00Mb)         262144      237442  >>  24353         349  >> >>>? >> >>> Of the physical pages in use, 5523 pages are permanently  >>  allocated to OpenVMS.  >> >>> >> >>> >> >>>8 >> >>> It would look to me to be a page of 8K.  (2GB/8K) >> >>> >> >>>, >> >>> FYI, a pagelet is 512 bytes not 512K. >> >> G >> >>A page on an Alpha VMS machine is 8192 bytes per page and on a VAX G >> >>machine it is 512 bytes per page. This is due to RISC vs CISC chip G >> >>technology where the image sizes grew to be 5-6 time larger on the  >> >>RISC chip.  >> >$ >> >No it's not!  Who told you this? >>  F >> I think it is probably close to true.  When you write compilers youJ >> have occassion to to look at things like this and I think it is obviousH >> to anyone who has coded assembly on VAX and Alpha that it takes a lotE >> more instructions to accomplish the same task.  In the case of our K >> PL/I compiler, on Alpha it is more than 7 times larger.  Of course, this I >> uses the GEM backend versus VCG, so I think the 5-6 figure is probably K >> fairly accurate.  If you compare the sizes of DECC you will find about a L >> 9:1 ratio, but again, part of that may be due to the much larger backend. >>   >> > >> >@ >> >> A pagelet on an Alpha VMS processor is 512 bytes. It takesI >> >>16 pagelets (16*512=8192) to equal to a page on a Alpha VMS machine.  >> >; >> >Unless your particular Alpha has 16K, 32K or 64K pages.  >> >--6 >> >VAXman- OpenVMS APE certification number: AAA-0001 >> >VAXman(at)TMESIS(dot)COM >> >8 >> >  "Well my son, life is like a beanstalk, isn't it?" >> > >> >--- * >> >Incoming mail is certified Virus Free.> >> >Checked by AVG anti-virus system (http://www.grisoft.com).E >> >Version: 6.0.404 / Virus Database: 228 - Release Date: 10/15/2002  >> > >> ---) >> Outgoing mail is certified Virus Free. = >> Checked by AVG anti-virus system (http://www.grisoft.com). D >> Version: 6.0.404 / Virus Database: 228 - Release Date: 10/15/2002 > 
 >To Everyone:  > E >From Alpha Architecture Reference Manual, Digital Press, 1992, pages 
 >vii-viii. > E >"Alpha is designed to handle the largest computing problems of today = >and tomorrow. When the Alpha architecture is compared to its = >predecessor, the VAX architecture, two differences stand out D >immediately. First, Alpha is a 64-bit architecture; VAX is a 32-bitC >architecture. This means that the Alpha virtual address extends to A >64-bit linear range of bytes in memory. Supporting this extended E >virtual address space are an extended maximum physical address range A >(up to 48 bits) and larger pages (8KB to 64KB). Alpha's extended B >virtual address range allows direct manipulation of gigabytes andF >terabytes produced in electrical and mechanical design, database, and$ >transaction processing, and imaging  G I have the preliminary Alpha ARM and not this issue; however, what does H this say to support your hypothesis that the page size was increased be-- cause of an increased instruction population?     C >Second, Alpha is a RISC architecture; VAX is a CISC architecture." I >________________________________________________________________________  > B >From: Migrating an Application from OpenVMS VAX to OpenVMS Alpha,D >Software Version: OpenVMS Alpha Version 7.0 and OpenVMS VAX Version( >7.0, DEC, 1995, Page 4-1, section 4.1.1 > F >"There are several issues to consider when planning what hardware youD >will need for your migration. To begin, consider what resources are5 >required in your normal VAX development environment:  >	CPU >	Disks	 >	Memory  > E >To estimate the resources needed for an Alpha migration environment,  >consider the following:+ >	Greater image size on the Alpha systems"  > I >________________________________________________________________________  >  > > >Image size on the Alpha is bigger than on a VAX, again due toA >difference in RISC and CISC architecture. How big the image size F >growth will be may be dependent upon whether the full VAX instructionC >set used by the VAX 9000 or the Reduce instruction set used by the % >6000-7000 VAXes are being converted.   E The VAX 9000 implemented the full VAX instruction set?  Hmm.  Time to + scan through the emulation source listings.     G >By increasing the page size, you will be able to map larger amounts of  >physical memory.   E This document actuallstates this?  What does the page size have to do F with how much physical memory can be mapped.  With an approriate sized# PTE, any amount should be mappable.       --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM              5   "Well my son, life is like a beanstalk, isn't it?"     ------------------------------  # Date: Sat, 26 Oct 2002 11:33:11 GMT " From:   VAXman-  @SendSpamHere.ORG Subject: Re: page or pagelet0 Message-ID: <00A1604A.671C97D4@SendSpamHere.ORG>  _ In article <n6ycnW6ZZaXZdCSgXTWcrg@metrocast.net>, "Bill Todd" <billtodd@metrocast.net> writes:  > E >"Daryl Jones" <jones.computer.srv@worldnet.att.net> wrote in message 8 >news:8a646952.0210251344.705a9554@posting.google.com... >  >....  >  >> To Everyone:  >>G >> From Alpha Architecture Reference Manual, Digital Press, 1992, pages  >> vii-viii. >>G >> "Alpha is designed to handle the largest computing problems of today ? >> and tomorrow. When the Alpha architecture is compared to its ? >> predecessor, the VAX architecture, two differences stand out F >> immediately. First, Alpha is a 64-bit architecture; VAX is a 32-bitE >> architecture. This means that the Alpha virtual address extends to C >> 64-bit linear range of bytes in memory. Supporting this extended G >> virtual address space are an extended maximum physical address range C >> (up to 48 bits) and larger pages (8KB to 64KB). Alpha's extended D >> virtual address range allows direct manipulation of gigabytes andH >> terabytes produced in electrical and mechanical design, database, and& >> transaction processing, and imaging >>E >> Second, Alpha is a RISC architecture; VAX is a CISC architecture."  > F >I'm not sure why you felt compelled to quote the above, since it adds" >exactly nothing to your argument. > K >> ________________________________________________________________________  >>D >> From: Migrating an Application from OpenVMS VAX to OpenVMS Alpha,F >> Software Version: OpenVMS Alpha Version 7.0 and OpenVMS VAX Version* >> 7.0, DEC, 1995, Page 4-1, section 4.1.1 >>H >> "There are several issues to consider when planning what hardware youF >> will need for your migration. To begin, consider what resources are7 >> required in your normal VAX development environment:  >>  CPU
 >>  Disks >>  Memory  >>G >> To estimate the resources needed for an Alpha migration environment,  >> consider the following:- >>  Greater image size on the Alpha systems"  > L >No shit.  However, no one in any way suggested that image sizes didn't growM >somewhat in the migration to RISC:  we just pointed out that your contention 1 >that they grew by a factor of 5 - 6 was rubbish.   I I objected to the image size increase being the impetus for larger pages.    --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM              5   "Well my son, life is like a beanstalk, isn't it?"     ------------------------------  # Date: Sat, 26 Oct 2002 09:38:47 GMT = From: "Colin Butcher" <colinDOT.butcherAT@xdeltaDOT.coDOT.uk> 1 Subject: Re: Quorum disk appears to not be voting = Message-ID: <Hotu9.2237$pk3.13849703@news-text.cableinet.net>   F If DKA1: is a 'normal' SCSI disc then shouldn't it appear as DKA100: ?L The quorum disc is generally best specified as the full device name returnedJ by f$getsyi("dka100:","fulldevnam") since this stuff happens very early onK in the boot sequence and an awful lot of the logical names and other things - you'd like to see aren't there at that stage.   F You also need to ensure that the specified quorum disc is visible by aK direct path from all systems attempting to use the quorum disc. It needs to = be visible at the hardware level >>> prompt from all systems.   G If the system can't find the specified quorum disc (due to an incorrect J name) then you won't get a vote from it, which would produce the behaviour you've described.    -- Hope this helps. Cheers, Colin. ' (colinDOT.butcherAT@xdeltaDOT.coDOT.uk)     D "Stephen McElduff" <stephen.mcelduff@transcore.com> wrote in message7 news:1a941731.0210251401.2e518336@posting.google.com... F > I am trying to configure a 2 Node DecNet based cluster with a quorumG > disk. As best I can tell, I have set all of the sysgen parameters (in F > the modprarams.dat) files on each system such that DKA1 should be my > quorum disk. > F > I have configured it to give each node a single vote and to give theA > quorum disk a single vote, so that if any single node dies, the G > cluster will transition but remain available (after a transition) for 
 > my apps....  >  > G > I believe that my quorum disk is not contributing a vote (see details  > below) >  > = > A cut/paste from my modparams.dat file follows: (the votes, C > expected_votes, disk_quorum values are the same on both machines)  > 	 > VOTES=1  > EXPECTED_VOTES=3< > AGEN$INCLUDE_PARAMS SYS$MANAGER:AGEN$NEW_NODE_DEFAULTS.DAT > SCSNODE="MCTMC1" > SCSSYSTEMID=1536 > NISCS_LOAD_PEA0=1  > VAXCLUSTER=2 > DISK_QUORUM="DKA1"
 > QDSKVOTES=1  > ALLOCLASS=200  > INTERCONNECT="NI"  > BOOTNODE="N" >  > @ > When I either shutdown or disconnect one of the nodes from theC > network, the other system "hangs" and doesn't come back until the2! > other system gets booted again.C >eH > I use the Show Cluster Utility to show me the current contents of someH > values relating to this. Most intriguing is the fact that the value of4 > the QF_VOTE parameter is "NO" for the Quorum disk. >eG > I don't understand what I am missing or have wrong that's not lettings
 > the disk > contribute a vote ?c >aC > Also strange is the value of the parameter named QF_SAME. For one E > system it is listed with a value of YES, for the other it is listedu > with a value of NO.t > D > When both systems are online the value of CL_VOTES is 2 (one wouldD > expect it to be 3). The value of CL_EXP is 3, as one would expect. >t >H >T >r >  >  >I@ > In each systartup_vms.com file, I mark the disk on as follows: >w > , > mount/system/cluster $2000$DKA1: LABELNAME >r >  > A > I believe I followed the instructions exactly as in the OpenVMS-F > Cluster Systems Manual relating to how to get a disk to have a vote. >aH > I checked for and found a quorum.dat file in the root directory of the  > disk drive in question (dka1). >( > 2 > Any help would be greatly appreciated..thanks...   ------------------------------  % Date: Sat, 26 Oct 2002 11:39:14 +0200 * From: Mike Rechtman <rechtman@tzora.co.il>1 Subject: Re: Quorum disk appears to not be votingn* Message-ID: <3DBA62C2.8020307@tzora.co.il>  : And you *did* run autogen from SAVPARAMS through REBOOT...% (and checked the AGEN$PARAMS.REPORT?)n Mike   Stephen McElduff wrote:8  F > I am trying to configure a 2 Node DecNet based cluster with a quorumG > disk. As best I can tell, I have set all of the sysgen parameters (in.F > the modprarams.dat) files on each system such that DKA1 should be my > quorum disk. > F > I have configured it to give each node a single vote and to give theA > quorum disk a single vote, so that if any single node dies, thehG > cluster will transition but remain available (after a transition) fors
 > my apps....$ >  > G > I believe that my quorum disk is not contributing a vote (see detailsc > below) >  > = > A cut/paste from my modparams.dat file follows: (the votes,GC > expected_votes, disk_quorum values are the same on both machines)  > 	 > VOTES=1i > EXPECTED_VOTES=3< > AGEN$INCLUDE_PARAMS SYS$MANAGER:AGEN$NEW_NODE_DEFAULTS.DAT > SCSNODE="MCTMC1" > SCSSYSTEMID=1536 > NISCS_LOAD_PEA0=1a > VAXCLUSTER=2 > DISK_QUORUM="DKA1"
 > QDSKVOTES=1  > ALLOCLASS=200h > INTERCONNECT="NI"n > BOOTNODE="N" >  > @ > When I either shutdown or disconnect one of the nodes from theC > network, the other system "hangs" and doesn't come back until thee! > other system gets booted again.e > H > I use the Show Cluster Utility to show me the current contents of someH > values relating to this. Most intriguing is the fact that the value of4 > the QF_VOTE parameter is "NO" for the Quorum disk. > G > I don't understand what I am missing or have wrong that's not letting 
 > the disk > contribute a vote ?r > C > Also strange is the value of the parameter named QF_SAME. For onesE > system it is listed with a value of YES, for the other it is listed1 > with a value of NO.r > D > When both systems are online the value of CL_VOTES is 2 (one wouldD > expect it to be 3). The value of CL_EXP is 3, as one would expect. >  t >  >  >  >  >  > @ > In each systartup_vms.com file, I mark the disk on as follows: >  > , > mount/system/cluster $2000$DKA1: LABELNAME >  >  > A > I believe I followed the instructions exactly as in the OpenVMSnF > Cluster Systems Manual relating to how to get a disk to have a vote. > H > I checked for and found a quorum.dat file in the root directory of the  > disk drive in question (dka1). >  > 2 > Any help would be greatly appreciated..thanks... >      -- B  & New to c.o.vms? allow me to recommend:6 http://eisner.encompasserve.org/~rechtman/post_hlp.htm= Other useful links at http://eisner.decusserve.org/~rechtman/EE --------------------------------------------------------------------- E Usual disclaimer: All opinions are mine alone, perhaps not even that.c? Mike Rechtman                            *rechtman@tzora.co.il*ME Kibbutz Tzor'a.                          Voice (home):(972)-2-9908337 C    "20% of a job takes 80% of the time, the rest takes another 80%"tE ---------------------------------------------------------------------D   ------------------------------  % Date: Sat, 26 Oct 2002 15:54:22 +0200h" From: "Hans Vlems" <hvlems@iae.nl>1 Subject: Re: Quorum disk appears to not be votingg4 Message-ID: <ape6qu$pcg0$1@ID-143435.news.dfncis.de>  K The SYSGEN data suggests that you're trying to build a two node NI cluster.  Two things about them:(  1) the DECnet address is coded as 1.512"  2) the quorum disk is set to DKA1B If you have SCSI disks then DKA1 ought to be DKA100, shouldn't it?  L If you have two separate systems, connected only by ethernet (i.e. no sharedJ SCSI) then only one system can have a quorum disk according to the manual.K That would be similar to giving that system two votes and forget the quorum,H disk. If you want to have redundancy, one system stays up no matter whatL system is shut down then you have one supported option: add a quorum VAX and give it one vote too.l   Hans  F "Stephen McElduff" <stephen.mcelduff@transcore.com> schreef in bericht7 news:1a941731.0210251401.2e518336@posting.google.com...>F > I am trying to configure a 2 Node DecNet based cluster with a quorumG > disk. As best I can tell, I have set all of the sysgen parameters (incF > the modprarams.dat) files on each system such that DKA1 should be my > quorum disk. >rF > I have configured it to give each node a single vote and to give theA > quorum disk a single vote, so that if any single node dies, thecG > cluster will transition but remain available (after a transition) for 
 > my apps....P >  >mG > I believe that my quorum disk is not contributing a vote (see detailsT > below) >S >-= > A cut/paste from my modparams.dat file follows: (the votes, C > expected_votes, disk_quorum values are the same on both machines)  >w	 > VOTES=1o > EXPECTED_VOTES=3< > AGEN$INCLUDE_PARAMS SYS$MANAGER:AGEN$NEW_NODE_DEFAULTS.DAT > SCSNODE="MCTMC1" > SCSSYSTEMID=1536 > NISCS_LOAD_PEA0=1i > VAXCLUSTER=2 > DISK_QUORUM="DKA1"
 > QDSKVOTES=1T > ALLOCLASS=200I > INTERCONNECT="NI"i > BOOTNODE="N" >v >w@ > When I either shutdown or disconnect one of the nodes from theC > network, the other system "hangs" and doesn't come back until then! > other system gets booted again.s > H > I use the Show Cluster Utility to show me the current contents of someH > values relating to this. Most intriguing is the fact that the value of4 > the QF_VOTE parameter is "NO" for the Quorum disk. >uG > I don't understand what I am missing or have wrong that's not letting 
 > the disk > contribute a vote ?n >yC > Also strange is the value of the parameter named QF_SAME. For oneiE > system it is listed with a value of YES, for the other it is listeds > with a value of NO.s > D > When both systems are online the value of CL_VOTES is 2 (one wouldD > expect it to be 3). The value of CL_EXP is 3, as one would expect. >m >u >t >s >m >. > @ > In each systartup_vms.com file, I mark the disk on as follows: >. >4, > mount/system/cluster $2000$DKA1: LABELNAME >. >/ >0A > I believe I followed the instructions exactly as in the OpenVMStF > Cluster Systems Manual relating to how to get a disk to have a vote. >uH > I checked for and found a quorum.dat file in the root directory of the  > disk drive in question (dka1). >h >b2 > Any help would be greatly appreciated..thanks...   ------------------------------    Date: 26 Oct 2002 00:49:34 -0700) From: P.Young@unsw.EDU.AU (Patrick Young) ) Subject: Re: So I went to the HP IT forumt= Message-ID: <55f85d77.0210252349.6bfdc614@posting.google.com>   d winston@SSRL.SLAC.STANFORD.EDU wrote in message news:<00A15FB4.6EB8DC2D@SSRL04.SLAC.STANFORD.EDU>...N > David Mathog may or may not be interested to know that I brought up what areO > basically his objections about the EDU license (vs. the OPENVMSEDU FAQ, whicha  3 OK, I'll bite. What exactly are the issues du jour?   F We have been on CSLG for longer than I can remember. The program is soI excellent I have my home alpha licensed under it, and pay the fee (ratherh than free hobby license).o  H YES!, you do need to install a new license each year - so what??? - thisI is a good thing. Lets HP know you want to (and are using) their products.g   ------------------------------  # Date: Sat, 26 Oct 2002 10:11:24 GMT,$ From: winston@SSRL.SLAC.STANFORD.EDU) Subject: Re: So I went to the HP IT forumt8 Message-ID: <00A16025.D49BA4AA@SSRL04.SLAC.STANFORD.EDU>  i In article <55f85d77.0210252349.6bfdc614@posting.google.com>, P.Young@unsw.EDU.AU (Patrick Young) writes:oe >winston@SSRL.SLAC.STANFORD.EDU wrote in message news:<00A15FB4.6EB8DC2D@SSRL04.SLAC.STANFORD.EDU>...iO >> David Mathog may or may not be interested to know that I brought up what arelP >> basically his objections about the EDU license (vs. the OPENVMSEDU FAQ, which >l4 >OK, I'll bite. What exactly are the issues du jour?  L The FAQ on the OPENVMSEDU site says you can run multiple users, that you canO put CSLG licenses on systems where the BASE license comes from the EDU program,i etc.  L The actual text of the license (last time I looked, when it appeared to haveL been cut and pasted from the hobbyist license text) didn't support this, and2 even said it was specifically for single-user use.  ? It would be nice for the license to reflect what the FAQ says. e  
 License says:   P  Upon agreement to these terms Compaq Computer Corporation ("COMPAQ") grants youO  a limited right to use the Software Program Version (the "Software") specifiedtL  above by a single individual. The Software may be used on a single computerN  solely for individual and personal "technology enthusiast" purposes, personalI  education and study, or administrative use in support of the educational.P  institution. It may not be used for any commercial or business purpose, whetherP  "for profit" or "not for profit." Any work performed or produced as a result ofN  use of this Software cannot be performed or produced for the benefit of otherL  parties for a fee, compensation or any other reimbursement or remuneration.P  This license is granted to a named individual at an educational institution andO  not to any public, private or governmental institution or entity. However, the J  Software may be copied and used on multiple computers that are under yourP  control in a classroom environment, including use by multiple students who haveB  agreed to these License Terms solely for instructional purposes.   K So it would appear that you can't have multiple users, even students, on a  O single machine, which doesn't really make it too useful for teach multitasking.aL (However, the "administrative use in support of the educational institution"F clause made me feel much better about my using it as the license for aF departmental server I bought "Linux-ready" at 2/3ds the price with VMS	 license.)   H The FAQ repeatedly says you can get multi-user licenses from CSLG, whichK strongly implies that it's permitted to do that.  It would be nice for the , license text to say that.u   >eG >We have been on CSLG for longer than I can remember. The program is so J >excellent I have my home alpha licensed under it, and pay the fee (rather >than free hobby license). >u  I CSLG is excellent if you have enough machines to spread the cost around.  M Diminishing returns are reached when you have low numbers - which acceleratestL the departure of VMS from schoools, and slows the uptake if someone wants toH bring it back.  (Or at least this was true the last time I looked at theB pricing.)  Luckily for me, there's still over 50 VMS systems here.  I >YES!, you do need to install a new license each year - so what??? - thislJ >is a good thing. Lets HP know you want to (and are using) their products.  E I have no complaints about that, and I didn't think David did either.l   -- Alano   ------------------------------    Date: 26 Oct 2002 06:47:59 -0700( From: bob@instantwhip.com (Bob Ceculski)) Subject: Re: So I went to the HP IT forum = Message-ID: <d7791aa1.0210260547.1aa3a36c@posting.google.com>o  g "James Gessling" <jgessling@yahoo.com> wrote in message news:<apbkvn$5441$1@ID-46415.news.dfncis.de>...vB > Yesterday, October 24, Pleasanton, CA. (San Francisco Bay area). > F > I came away quite pleased.  Maybe this VMS stuff has a future.  Mary@ > Jane Vasquez, who works for Mark Gorham as VMS product managerH > gave a very upbeat talk and we had plenty of time for discussion.  SheC > seemed very open to comments and suggestions about what direction ) > VMS should take.  That was after lunch.o > E > Lowlight was the Intel guy before lunch.  Trying to make the 8 yeariE > process of getting Itanium out the door a good thing.  And slammingC= > AMD's hammer chip with snide comments about itanium being ap2 > whole new thing vs. an evolutionary development. > ; > My main comment was that HP needs to get the whole tcp/ip = > software thing figured out.  Having three competing stacks,cB > with different features is just a mess.  Especially when two are8 > owned by the same company, process software.  Maybe HP@ > should give their tcp services to process and let them work it' > out, they seem to do a very good job.r >  > JimC  > TCPware is still superior to ucx,multinet and it runs the best= because it is still vms kernel based, not unix like the other  two ...    ------------------------------  # Date: Sat, 26 Oct 2002 14:07:56 GMTe# From: "John Smith" <a@nonymous.com>w) Subject: Re: So I went to the HP IT forum H Message-ID: <0lxu9.81580$Q3S.36232@news01.bloor.is.net.cable.rogers.com>  8 "Sean O'Banion" <seanobanion@attbi.com> wrote in message7 news:f883d5a4.0210251609.704cfd51@posting.google.com...a4 > I have to agree about May Jane, and the Intel Guy. >eH > I congratulated them on moving the COE work that was talked about lastF > year at the IT Forum into UNIX Portability.  I pointed out that UNIXH > Portability needs a "killer app", something major that would show whatG > it took to port an application, and I proposed Oracle Applications as F > a possible example: Mary Jane responded that they are always talkingD > to Oracle.  Since she didn't even write this comment down (she didC > write down the other comments), I took this to mean that this has @ > occurred to them (well, duh), but she could not comment on it.    K In an email to Mark Gorham last year it was suggested that, "... your group.J author or sponsor the authorship of a practical guide for unix/NT softwareD developers detailing the techniques they need to know in order writeD software for OpenVMS. Perhaps this will enable OpenVMS to again haveI 3rd-party software released at the same time as unix and NT variants withtD version parity. Practical experience over the years has shown me howD important this is in having IT departments view OpenVMS favourably."  L To which he replied, "Great idea, thanks for the mail.    We'll include this
 in our plans.    Regardsy   Mark"a     Guess we are still waiting.    ------------------------------   Date: 26 Oct 2002 14:14:25 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)) Subject: Re: So I went to the HP IT forumg4 Message-ID: <ape800$phoj$1@ID-135708.news.dfncis.de>  K In article <rdeininger-2510022248450001@1cust118.tnt2.nashua.nh.da.uu.net>,o5 	rdeininger@mindspring.com (Robert Deininger) writes:fN > In article <apcoef$fkvk$1@ID-135708.news.dfncis.de>, bill@cs.uofs.edu wrote: > : >>In article <00A15FB4.6EB8DC2D@ssrl04.slac.stanford.edu>,0 >>        winston@SSRL.SLAC.STANFORD.EDU writes: >>> P >>> David Mathog may or may not be interested to know that I brought up what areQ >>> basically his objections about the EDU license (vs. the OPENVMSEDU FAQ, whichrM >>> says the license is to be interpreted in ways not supported by the actualaQ >>> words) and the default speed of stuff in RMS (coupled with a suggestion abouthJ >>> changing to less-safe defaults on a per-process basis, although other O >>> system managers in the room said I should just be using XFC).  Anyway, MaryeJ >>> Jane (maryjane.vazquez@hp.you-know-what) says the EDU thing is now her
 > baby andK >>> she'd love to hear any suggestions for getting VMS back in the schools.a >>>  >>P >>Well, I'm all for keeping it as simple as possible (for both sides concerned). >>G >>Should I email her suggesting that they write up something that says oG >>you can use Hobbyist PAKS and use the systems for anything related to 
 >>academics,   > K > Yes, it sounds like a good time to explain your objections to the currentdI > scheme, and toss in any suggestions you have for improving the program.h > J > IIRC, you had your campus lawyer look at the license terms, and he had aL > number of objections.  I you still have that discussion at hand, you mightJ > as well send it along.  Or maybe my memory is playing tricks, and you're > someone else.  :-)  F Wrong person.  It never got that far.  The department faculty (who areG not overly keen on returning to VMS anymore anyway) took one look at ithE and said no.  They are willing to use VMS, but only if it involves nomA additional labor on their part.  Anything that can not be totallyrI administered by me (after all, I am The Department Systems Administrator)6H is not going acceptable.  It would be different if everyone was fightingG to get VMS back in the classroom, but the schools really don't care and.J that means an uphill battle. Any program has to be as flexible as possibleC and easy to implement and maintain.  As soon as strings start to bep> attached the easiest thing for schools to do is "just say no".   bill   -- 0J 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>   r   ------------------------------   Date: 26 Oct 2002 14:20:03 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)) Subject: Re: So I went to the HP IT forumf4 Message-ID: <ape8aj$phoj$2@ID-135708.news.dfncis.de>  = In article <55f85d77.0210252349.6bfdc614@posting.google.com>, , 	P.Young@unsw.EDU.AU (Patrick Young) writes:f > winston@SSRL.SLAC.STANFORD.EDU wrote in message news:<00A15FB4.6EB8DC2D@SSRL04.SLAC.STANFORD.EDU>...O >> David Mathog may or may not be interested to know that I brought up what are P >> basically his objections about the EDU license (vs. the OPENVMSEDU FAQ, which > 5 > OK, I'll bite. What exactly are the issues du jour?  >   I CSLG is something totally different from the dreaded Educational Program.g  H > We have been on CSLG for longer than I can remember. The program is soK > excellent I have my home alpha licensed under it, and pay the fee (ratheru > than free hobby license).W  K Having a home machine on the University's CSLG License seems rather dubiouspH legally to me, but then, I am not a lawyer (and I don't play one on TV).   > J > YES!, you do need to install a new license each year - so what??? - thisK > is a good thing. Lets HP know you want to (and are using) their products.r  K It also costs money.  Not an insignificant amount either.  Considering thatnG the Univeristy and my Department see no true advantage in using VMS foroF anything, why would they consider paying anything for the priveledge??J As far as they are concerned, they don't need it.  It is to HP's advantage to change this opinion.  g   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>   r   ------------------------------   Date: 26 Oct 2002 14:23:22 GMT, From: bill@gw5.cs.uofs.edu (Bill Gunshannon)) Subject: Re: So I went to the HP IT forume4 Message-ID: <ape8gp$phoj$3@ID-135708.news.dfncis.de>  = In article <857e9e41.0210251832.16f24298@posting.google.com>,D4 	susan_skonetski@hotmail.com (Sue Skonetski) writes: > Jim, > N > Thank you for your feedback on this event.  I have forwarded to Mark and MJ.   Sue,H    Maybe you should consider forwarding the whole discussion to them.  I5 doubt it is likely they will be reading it otherwise.e   bill   -- eJ 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>       ------------------------------  % Date: Fri, 25 Oct 2002 22:20:51 -0600'$ From: Lee Y T Mah <lytmah@cha.ab.ca>% Subject: Re: TSM on the Freeware diskr) Message-ID: <3DBA1823.820AE551@cha.ab.ca>   N TSM can be used to automate the configuration of any of the following terminal servers:4     DS100, DS200, DS700, DS900, Emulex P4000, Xyplex  G There may be others but these are the only ones I have run TSM against.a     "kenrbnsn1@rcn.com" wrote:  H > I'm doing a short term contract installing a VAX 3100/85 to eventuallyK > replace a VAX 3100/20. They have a decserver 700 currently attached. It's.G > been a long time since I've played with a decserver (any model), so IJG > thought I would try to use the TSM from the Freeware (CD & Web area).JH > Downloading from the Web or using the files off the CD, gives the same
 > results: >A > $ r tsm021.dcx_vaxexem >tM >                 FTSV DCX auto-extractible compressed file for OpenVMS (VAX)>8 >                 FTSV V3.0 -- FTSV$DCX_VAX_AUTO_EXTRACT< >                 Copyright (c) Digital Equipment Corp. 1993 >nA > Options: [output_file_specification [input_file_specification]]s >r> > The decompressor  needs to know  the filename to use for the> > decompressed file. If you don't specify any, it will use the> > original name  of the  file before it  was  compressed,  and> > create  it in  the  current  directory.  If  you  specify  a= > directory name, the file will be created in that directory.n >h' > Decompress into (file specification): 1 >         Opening and checking compressed file...>8 > Decompressing (press Ctrl-T to watch the evolution)...' >         Creating decompressed file...:G >         Original file specification: SYS$SYSROOT:[SYSMGR]TSM021.SAV;1V* >         Decompressed file specification:' > DKA100:[KSROPR.DOWNLOADS]TSM021.SAV;1>2 > %FTSV-W-COMP_DECOMPERR, fatal decompressor errorM > -DCX-E-INVDATA, invalid data presented for expansion or bounded compression  > J > Is there a different place I could get a good copy? (or hints on getting > into the decserver manually?)0 >> > Thanks > Ken0 > F > --------------------------------------------------------------------- > mail2web - Check your email from the web ats > http://mail2web.com/ .   -- Lee>  ; Lee Y T Mah                        Capital Health Authoritye   ------------------------------   End of INFO-VAX 2002.592 ************************