1 INFO-VAX	Mon, 15 Dec 2003	Volume 2003 : Issue 692       Contents:% Difference in GETJPI item RIGHTS_SIZE  Re: Digital Divide Re: Digital Divide Re: Full or Partial file spec ?  Re: Full or Partial file spec ?  Re: Full or Partial file spec ?  Re: Full or Partial file spec ?  Re: Full or Partial file spec ?  Re: IO$GL_UBA_INT0 OT: The Powerpoint generation ! Re: OT: The Powerpoint generation  RE: Problems with 7.3 and 164LX  Re: Problems with 7.3 and 164LX  Re: Problems with 7.3 and 164LX  Re: Problems with 7.3 and 164LX  Re: Problems with 7.3 and 164LX  RE: Problems with 7.3 and 164LX  RE: Problems with 7.3 and 164LX  RE: Problems with 7.3 and 164LX  Re: question on SMTP queues  Re: TCPIP 5.3 VAX on Hobbyist / Re: Time for a community project? (SEARCH/KEY=)  Undocumented GETJPI UAF_FLAGS ? # Re: Undocumented GETJPI UAF_FLAGS ? # Re: Undocumented GETJPI UAF_FLAGS ? , Re: VAX 11/750 and RL02 - trying to boot VMS  F ----------------------------------------------------------------------  # Date: Sun, 14 Dec 2003 21:45:50 GMT 6 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER). Subject: Difference in GETJPI item RIGHTS_SIZE1 Message-ID: <iS4Db.68138$dt3.3370@news.chello.at>   > I just noted (yet) a(nother) difference between VAX and Alpha   	 The lines   & $ rs    = F$GETJPI ("", "RIGHTS_SIZE")8 $ say   "RIGHTS_SIZE = ", rs, " (", rs/8, " Identifier)"   gives on Alpha (V7.3-2)   " 	RIGHTS_SIZE = 184 (23 Identifier)  ! while on VAX (V7.3) the answer is   & 	RIGHTS_SIZE = 000000B8 (0 Identifier)  I It seems, that DCL on VAX does something wrong here (because also the doc E Table D CLI-7 on page DCLI-373 state the "Return Type" as "Integer").   ! Another task for Guy, I think ;-)    TIA    --   Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  # Date: Mon, 15 Dec 2003 01:42:05 GMT > From: Michael Austin <maustin@no-more-spam.firstdbasource.com> Subject: Re: Digital Divide @ Message-ID: <Nj8Db.549$F27.279426153@newssvr11.news.prodigy.com>   JF Mezei wrote:  <snip>  P > It doesn't take long for someone who has never had electricity to learn to useN > light switches etc. But it does take time to teach someone who has never hadP > electricity  how to use a computer, the internet etc. This is why the "digitalM > divide" is a problem because the gap between the poor and the rich has just M > gotten a hell of a lot wider and something must be done to give those folks < > who are not so fortunate some chance at bridging that gap. >   F And the bigger problem is that most of those people need other skills A long before they can learn to use a computer -- like reading and  H writing.  Once that is done then and only then can they even comprehend G what the computer might be able to do for them.  They need to learn to   walk before they can run.   @ You think the GreenPeace people have a problem with the current G industrialized countries generating electricity, just wait until every  I house in the world has a power line installed...  The fact of the matter  I is that there is not enough trees, coal, natural gas or oil in the world  F that could possibly sustain a world-wide power grid for any length of E time.  The only currrently available alternative is Nuclear.  Unless  I there are some significant advances in solar power (woefully inadequate)  H or wind-power(miles upon miles of unsightly windmills).  A state in the J US is fighting a wind-mill farm because it is just plain ugly - unsightly.  	 <snipage>    M.A.   ------------------------------  # Date: Mon, 15 Dec 2003 03:12:40 GMT 8 From: "Jerome H. Fine" <jhfineb9rv@b9rvnospamcompsys.to> Subject: Re: Digital Divide 4 Message-ID: <3FDD26D0.971130D3@b9rvnospamcompsys.to>   >Michael Austin wrote:  A > You think the GreenPeace people have a problem with the current H > industrialized countries generating electricity, just wait until everyJ > house in the world has a power line installed...  The fact of the matterJ > is that there is not enough trees, coal, natural gas or oil in the worldG > that could possibly sustain a world-wide power grid for any length of F > time.  The only currrently available alternative is Nuclear.  UnlessJ > there are some significant advances in solar power (woefully inadequate)I > or wind-power(miles upon miles of unsightly windmills).  A state in the L > US is fighting a wind-mill farm because it is just plain ugly - unsightly.   Jerome Fine replies:  0 I agree about the problem of using non-renewable/ methods of generating power except for nuclear.   4 If you go to Holland, they have a wind-mill on every3 property I am told.  And if I had to choose between 7 tearing down an old nuclear plant and an old wind-mill, 5 I am sure the cost of the former would be much higher  than the latter.  3 I am not saying that wind-mill power is better than 0 nuclear, but that given the overall compromises,1 it seems to me that wind-mills are easier to have 3 next door than nuclear power plants.  AND I realize 3 that the installed capacity probably needs to be at 5 least 3 times the expected load and still will not be 2 able to meet every demand.  Some of the time there1 will just not be enough wind.  However, I suspect 2 that if a minimum of 20% of the power was required3 to be from wind-mills so that a valid test could be . made, and people who lived within sight of the. wind-mills were given power at a reduced cost,3 there would soon be sufficient wind-mills to exceed 0 the 20% requirement.  Fortunately some countries0 in the EU will attempt to reach the 20% goal (or0 so I seem to have read somewhere) and it will be0 possible to know if wind-mills are actually cost1 effective.  BUT if Texas can have wind-mill farms 7 as well as Alberta (both areas with vast oil capacity), 1 then there must be something that is already cost 
 effective.  8 Until we are able to build a space elevator and transmit9 solar power to the surface of the earth or fusion becomes 6 possible that is even more economical or someone finds2 an even less expensive method to generate power, I: suggest that we at least attempt to find out if wind-mills/ are cost effective and make the NIMBY effort to 2 locate the wind-mills by offering reduced rates to2 anyone who can see the wind-mills.  I have nothing4 against nuclear power so long as any nuclear station3 that is built ALSO includes the plans and financing 3 to decommission the plant and store the spent fuel. 5 Otherwise, the actual cost is not apparent until many 5 decades after the plant is no longer being used.  The 3 same with any industrial product that costs to send 8 to a land fill, but was born by the user after the fact.   Sincerely yours,   Jerome Fine  --4 To obtain the original e-mail address, please remove5 the ten characters which immediately follow the 'at'. 8 If you attempted to send a reply and the original e-mail7 address has been discontinued due a high volume of junk 5 e-mail, then the semi-permanent e-mail address can be 7 obtained by replacing the four characters preceding the . 'at' with the four digits of the current year.   ------------------------------    Date: 14 Dec 2003 11:59:14 -0800. From: spamsink2001@yahoo.com (Alan E. Feldman)( Subject: Re: Full or Partial file spec ?< Message-ID: <b096a4ee.0312141159.2eb9409@posting.google.com>  [ JF Mezei <jfmezei.spamnot@istop.com> wrote in message news:<3FDC0C5B.6AC5126C@istop.com>...     F Well, first of all, you didn't answer my question about how adding one) to a gazillion would make any difference.      > "Alan E. Feldman" wrote:7 > > What is the nature of your "file selection dialog"?  > L > It is the standard vanilla decwindows file selection dialog. You give it aK > title, a file pattern to match. And then it returns the full file name as N > selected by the user. For instance, right now, I give it "SYS$LIBRARY:*.TLB"I > and that presents a list of .TLBs in SYS$LIBRARY, but the user can then E > navigate, change the file extention and the dialog may return to me & > sys$HELP:HELPLIB.HLB;2 for instance.    F Then what's the problem? You just wrote above that the DECwindows fileD selection dialog program gave you an actual file-spec, even though aE wildcard was initially specified. IOW, the user gave a wildcard spec, A DECwindows showed all matching files, then the user navigated and B found a particular file. So why do you need to deal with wildcards( when DECwindows already does it for you?  0 OK, going back to quote from your original post:  
 [begin quote] C Here is the context: upon application startup, if the argument is a 	 full file C spec, I proceed immediatly to processing that file. If it is just a 
 directory,F I add a "*.TLB" to it and call up a file selection dialogue, and if it is a? wildcard, I call the file selection dialogue without adding the  "*.TLB". [end quote]   < Ah. So I gather from this that the user is using a potentialB combination of typing a file-spec at a command prompt or somethingF other than the DECwindows File Selection Dialog Box (see how much moreD verbose GUI terms are compared to CLI terms?) and the DECwindows FSD% box. Well, that's very different! :-)   @ So you don't want to launch the DECwindows file-selection widgetC unless absolutely necesary. OK. Fair enough. Why should the user be = bothered with the DECwindows FSD box when he already uniquely > specified a file? (On the other hand, you can just not allow aC file-spec as a launch parameter and let the user type his file-spec D into the DECwindows FSD box and let that widget deal with it. BOTFH, maybe you don't want that.)    So how about using    % $   FILE_SPEC = F$PARSE(P1,"*.TLB")     B in a DCL procedure that launches the application? You can then use@ F$SEARCH() twice to see if you have unique match. If you have noF match, tell the user and ask again. If you have a unique match, launchC your app. If you have multiple matches, launch that DECwindows file C selection widget. And then you won't have to use (SYS)$PARSE to add - unwanted structures and the like to your app!   A I'd like to add here that what constitutes a wildcard spec can be " context sensitive. For exmaple, is       .TLB  D a "wildcard spec"? It is for DIRECTORY, but not for TYPE. It dependsC on what default-spec and what related spec, if any, are used in the C parse operation. So, the answer to your question in part depends on F what instructions you give to your users on how to specify file-specs.F If your user instructions are not strictly compatible with $parse, you4 have to write your own routine(s) to deal with that.   Disclaimer: JMHO Alan E. Feldman    ------------------------------  % Date: Mon, 15 Dec 2003 06:39:21 +0800 , From: Paul Repacholi <prep@prep.synonet.com>( Subject: Re: Full or Partial file spec ?- Message-ID: <87pter10ti.fsf@prep.synonet.com>   5 "Richard B. Gilbert" <rgilbert88@comcast.net> writes:   E > As a rule of thumb, ALWAYS use the $PARSE service or F$PARSE in DCL > > to parse a filespec!  The rules for what constitutes a validA > filespec are quite complex and include things many people never A > heard of.  If you break this rule you will regret it later.  If  > there IS a later!!!!  * And the device can be a search list, so...  . DISK:[DIR]FILE.NAME;1 can return many files...  > You can only discover this by opening and keeping count. ThereA is NOTHING in the syntax that even hints that it is a `wildcard'. $ For a different flavour of wildcard.   --   Paul Repacholi 1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076* comp.os.vms,- The Older, Grumpier Slashdot. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------  % Date: Sun, 14 Dec 2003 19:54:06 -0500 * From: JF Mezei <jfmezei.spamnot@istop.com>( Subject: Re: Full or Partial file spec ?) Message-ID: <3FDD0623.C32AC7C1@istop.com>    Paul Repacholi wrote: 0 > DISK:[DIR]FILE.NAME;1 can return many files...  L However, the default behaviour for most DCL applications is to use the firstL file in the above example. TPU however, will upon startup tell you that thisN represents multiple files and will want you to specify which one you want (forU instance, if same file exists in the specific and common directories in sys$manager:)   F I guess I'll have to do some bedtime reading of the FAB, NAM etc blockJ documentation from the RMS manual to see if there might be a simple way toN determine if SYS$PARSE has detected the possibility of multiple files matching or not.   I However, is there any chance (under special circumstances with the proper K alignement of the stars relative to the ratio of the share price of IBM and F MSFT) where a wildcard specification to SYS$PARSE would yield a singleL non-wildcard specification ? (for instance, if only one file were to match).   ------------------------------  % Date: Sun, 14 Dec 2003 22:36:42 -0500 * From: JF Mezei <jfmezei.spamnot@istop.com>( Subject: Re: Full or Partial file spec ?) Message-ID: <3FDD2C33.71C7A941@istop.com>    Graham Burley wrote:H > You need to provide a NAM block, then after the $PARSE check NAM$L_FNB! > to see if NAM$V_WILCARD is set.    Thanks.   A >  "To release this space, use a Parse service that specifies the B >   NAM$B_NOP field NAM$V_SYNCHK option and sets the FAB$B_DNS and >   NAM$L_RLF fields to zero."  H Does this mean I need to issue a second $PARSE or just include the above  settings in the initial $PARSE ?   ------------------------------  % Date: Sun, 14 Dec 2003 23:52:13 -0500 * From: JF Mezei <jfmezei.spamnot@istop.com>( Subject: Re: Full or Partial file spec ?) Message-ID: <3FDD3DE1.EEC23307@istop.com>    "Alan E. Feldman" wrote:B > So you don't want to launch the DECwindows file-selection widgetE > unless absolutely necesary. OK. Fair enough. Why should the user be ? > bothered with the DECwindows FSD box when he already uniquely  > specified a file?   L Exactly. Consider that a X app can be launched different ways. For instance,K from Fileview, the application can be launched with a specific file already N specificed. From the session manager, you can launch it without any arguments,N or specify an argument (which could be a specific file or a wildcard spec), orQ from the $ sign where you can supply no arguments, a specific file or a wildcard.   : So my app can't assume some DCL will have executed before.  J The reson I want to avoid the file selection dialogue whenever possible is$ just to make the application faster.   ------------------------------  % Date: Mon, 15 Dec 2003 06:18:04 +0800 , From: Paul Repacholi <prep@prep.synonet.com> Subject: Re: IO$GL_UBA_INT0 - Message-ID: <87u14311sz.fsf@prep.synonet.com>   . lukebrennan <lukebrennan@iinet.net.au> writes:  : > Looking at SDA for devices, I dump out vector 80 and see  $ > MCHK+005E8:  INCL @#IO$GL_UBA_INT0 > MCHK+005EE:  BRB  MCHK+005F0 > MCHK+005F0:  REI  5 > what the hey is this doing? What's IO$GL_UBA_INT0 ?   ; Counts interupts through 0, then branches in log the error.    --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076* comp.os.vms,- The Older, Grumpier Slashdot. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------  % Date: Sun, 14 Dec 2003 18:02:09 -0500 * From: JF Mezei <jfmezei.spamnot@istop.com>& Subject: OT: The Powerpoint generation) Message-ID: <3FDCEBEE.E02298C5@istop.com>   9 > http://www.nytimes.com/2003/12/14/magazine/14POWER.html   K has a most interesting article about how the use of Powerpoint is "dumbing" H down business decisions. Essentially it says that managers are forced toJ simplify everything to fit on a powerpoint slide that can contains limitedN amount of text in bullet point form instead of the precise information needed.  N Examples given of failures of Powerpoint is the shuttle columbia. After seeingK the launch video, the engineers had to cram all the information on possible L debris hit into powerpoint slides that did not make it possible for managersE to really understand the situation. Managers based their decisions on + powerpoint slides instead of the real data.    ------------------------------  # Date: Mon, 15 Dec 2003 00:39:00 GMT ) From: Steven Bitgood <steve@goodbits.com> * Subject: Re: OT: The Powerpoint generation+ Message-ID: <3FDD02BB.2090308@goodbits.com>   ` Anyone with an interest in the visual representation of data needs to review the work of Edward b Tufte. The September issue of Wired magazine has his summary of his opinions on PowerPoint, and I  highly recommend it.  2 http://www.wired.com/wired/archive/11.09/ppt2.html     JF Mezei wrote:   9 >>http://www.nytimes.com/2003/12/14/magazine/14POWER.html  >> > M > has a most interesting article about how the use of Powerpoint is "dumbing" J > down business decisions. Essentially it says that managers are forced toL > simplify everything to fit on a powerpoint slide that can contains limitedP > amount of text in bullet point form instead of the precise information needed. > P > Examples given of failures of Powerpoint is the shuttle columbia. After seeingM > the launch video, the engineers had to cram all the information on possible N > debris hit into powerpoint slides that did not make it possible for managersG > to really understand the situation. Managers based their decisions on - > powerpoint slides instead of the real data.  >    ------------------------------  # Date: Sun, 14 Dec 2003 19:02:32 GMT 6 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)( Subject: RE: Problems with 7.3 and 164LX2 Message-ID: <ct2Db.65534$dt3.42126@news.chello.at>  _ In article <CIEJLCMNHNNDLLOOGNJIMEJNIKAA.tom@kednos.com>, "Tom Linden" <tom@kednos.com> writes: * >Well the one that came with 7.3-1 was 6.2  D Check for yourself on http://ftp.digital.com/pub/DEC/Alpha/firmware/' Especically the "Firmware Not on CD"...  btw Current is V6.6   F >Now I believe that the 164LX was used in the Pelicans Dec 3000/300LX,E >of which I have two, one with Tru64 4.0d and the other with VMS7.3-1 G >and I believe I have the same firmware in both, but can only check the 	 >unix box   > No. The DEC 3000 are alltogether EV4 (and maybe EV45) systems.7 The 164LX is as the name already shows an EV5 system...    --   Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  % Date: Sun, 14 Dec 2003 13:18:46 -0600 ( From: Wayne Sewell <wayne@tachysoft.com>( Subject: Re: Problems with 7.3 and 164LX/ Message-ID: <00A2A5CD.447C62F3.5@tachysoft.com>   ' >From: Tor Arne Rein <tarein@online.no> L >User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b) Gecko/20031205 >            Thunderbird/0.4 >X-Accept-Language: en-us, en  >MIME-Version: 1.0 >X-Newsgroups: comp.os.vms) >Subject: Re: Problems with 7.3 and 164LX  >  >  > 	 >Tor Arne  >  >Wayne Sewell wrote: >>>Tom Linden wrote: >>> " >>>>Have you updated the firmware? >>> G >>>Yes, Tru64 came with a firmware CD, "show config" now reports: "SRM  ( >>>Console 5.8-1" . Is that the latest ? >>>  >>   >>  J >> No.  The latest CD I have, based on a very brief search, is FW CD V6.2. >>  9 >> According to the doc on that, 7.3 requires FW CD V5.9   >>   > I >Now I also have found some docs indicating that to run VMS 7.3 you need  I >firmware 5.9 . The sad thing for me is that I have firmware CD 6.3, and  J >for 164LX the latest version is still 5.8. No updated firmware have been ! >released for 164LX yet it seems.  > : >So I have to use VMS 7.2-1 or earlier it seems. Anybody ? >     M No, you don't have to do that.  7.3-1 *will* run on the 164LX.  Perhaps it is M the palcode.  There is more than one firmware component, with its own version ' number, included in the firmware kit.     1 1.21-2 is the palcode version that will run 7.3-1 O =============================================================================== N Wayne Sewell, Tachyon Software Consulting  (281)812-0738   wayne@tachysoft.com; http://www.tachysoft.com/www/tachyon.html and wayne.html    O =============================================================================== H Randolph Duke (in Trading Places): "Mother always said you were greedy."1    Mortimer Duke: "She meant it as a compliment!"    ------------------------------  % Date: Sun, 14 Dec 2003 14:34:26 -0500 3 From: "Richard B. Gilbert" <rgilbert88@comcast.net> ( Subject: Re: Problems with 7.3 and 164LX0 Message-ID: <rZOdnfTYDcjeJkGiRVn-ig@comcast.com>  D The "Very Latest Firmware CD" is labeled V6.5, it came with the VMS H V7.3-2 distribution I received a week or two ago.  This may not contain G updated firmware for very old machines and may not contain VMS PALCODE  @ or SRM console for machines that were never intended to run VMS.  H I believe that I've read of some unofficial and unsupported releases of G firmware for unsupported Alphas, courtesy of one of the VMS engineers,  > but the unsupported machines are still just that, unsupported!   Wayne Sewell wrote:   ( >>From: Tor Arne Rein <tarein@online.no> >>X-Newsgroups: comp.os.vms * >>Subject: Re: Problems with 7.3 and 164LX< >>In-Reply-To: <CIEJLCMNHNNDLLOOGNJIOEJLIKAA.tom@kednos.com> >> >>Hi,  >> >>Tom Linden wrote:  >>     >>! >>>Have you updated the firmware? 	 >>>        >>> F >>Yes, Tru64 came with a firmware CD, "show config" now reports: "SRM ' >>Console 5.8-1" . Is that the latest ?  >> >>     >> > H >No.  The latest CD I have, based on a very brief search, is FW CD V6.2. > 7 >According to the doc on that, 7.3 requires FW CD V5.9   >  > P >===============================================================================O >Wayne Sewell, Tachyon Software Consulting  (281)812-0738   wayne@tachysoft.com < >http://www.tachysoft.com/www/tachyon.html and wayne.html   P >===============================================================================I >Randolph Duke (in Trading Places): "Mother always said you were greedy." 2 >   Mortimer Duke: "She meant it as a compliment!" >    >    ------------------------------  % Date: Sun, 14 Dec 2003 20:59:39 +0100 & From: Tor Arne Rein <tarein@online.no>( Subject: Re: Problems with 7.3 and 164LX1 Message-ID: <Ik3Db.6085$Y06.98454@news4.e.nsc.no>    Hi,    Wayne Sewell wrote:  >>; >>So I have to use VMS 7.2-1 or earlier it seems. Anybody ?  >> >  >  > O > No, you don't have to do that.  7.3-1 *will* run on the 164LX.  Perhaps it is O > the palcode.  There is more than one firmware component, with its own version ) > number, included in the firmware kit.    > 3 > 1.21-2 is the palcode version that will run 7.3-1   5 I checked what I got with "show config" and it shows:   E   "SRM Console V5.8-1  OpenVMS PALcode V1.21-2, Digital UNIX PALcode   V1.23-2"  H Even though on the Firmware CD 6.3 that I have, said latest version was . 1.20 or something, this is what was installed.   Tor Arne   ------------------------------  % Date: Sun, 14 Dec 2003 21:04:15 +0100 & From: Tor Arne Rein <tarein@online.no>( Subject: Re: Problems with 7.3 and 164LX1 Message-ID: <%o3Db.5598$n31.96359@news2.e.nsc.no>    Hi,    Richard B. Gilbert wrote: F > The "Very Latest Firmware CD" is labeled V6.5, it came with the VMS J > V7.3-2 distribution I received a week or two ago.  This may not contain I > updated firmware for very old machines and may not contain VMS PALCODE  B > or SRM console for machines that were never intended to run VMS.L Yes, I have both 6.2 and 6.3, but the 164LX firmware was 5.8-1 on both CD's. > J > I believe that I've read of some unofficial and unsupported releases of I > firmware for unsupported Alphas, courtesy of one of the VMS engineers,  @ > but the unsupported machines are still just that, unsupported! > K Great. Unsupported ok, if I only can get it to work. Any pointers to that ?    Tor Arne   ------------------------------  % Date: Sun, 14 Dec 2003 14:49:44 -0800 # From: "Tom Linden" <tom@kednos.com> ( Subject: RE: Problems with 7.3 and 164LX9 Message-ID: <CIEJLCMNHNNDLLOOGNJIOEKCIKAA.tom@kednos.com>    >-----Original Message----- > >From: Peter 'EPLAN' LANGSTOEGER [mailto:peter@langstoeger.at]) >Sent: Sunday, December 14, 2003 11:03 AM  >To: Info-VAX@Mvb.Saic.Com) >Subject: RE: Problems with 7.3 and 164LX  >  > ? >In article <CIEJLCMNHNNDLLOOGNJIMEJNIKAA.tom@kednos.com>, "Tom ! >Linden" <tom@kednos.com> writes: + >>Well the one that came with 7.3-1 was 6.2  > E >Check for yourself on http://ftp.digital.com/pub/DEC/Alpha/firmware/ ( >Especically the "Firmware Not on CD"... >btw Current is V6.6 > G >>Now I believe that the 164LX was used in the Pelicans Dec 3000/300LX, F >>of which I have two, one with Tru64 4.0d and the other with VMS7.3-1H >>and I believe I have the same firmware in both, but can only check the
 >>unix box > ? >No. The DEC 3000 are alltogether EV4 (and maybe EV45) systems. 8 >The 164LX is as the name already shows an EV5 system...  H OK, but this then at least establishes that FW 6.0 will run on even this older  system.    >  >--  >Peter "EPLAN" LANGSTOEGER& >Network and OpenVMS system specialist >E-mail  peter@langstoeger.at G >A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist  >  >---' >Incoming mail is certified Virus Free. ; >Checked by AVG anti-virus system (http://www.grisoft.com). A >Version: 6.0.548 / Virus Database: 341 - Release Date: 12/5/2003  >  --- & Outgoing mail is certified Virus Free.: Checked by AVG anti-virus system (http://www.grisoft.com).@ Version: 6.0.548 / Virus Database: 341 - Release Date: 12/5/2003   ------------------------------  # Date: Sun, 14 Dec 2003 23:55:45 GMT 6 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)( Subject: RE: Problems with 7.3 and 164LX2 Message-ID: <5M6Db.69669$dt3.12973@news.chello.at>  _ In article <CIEJLCMNHNNDLLOOGNJIOEKCIKAA.tom@kednos.com>, "Tom Linden" <tom@kednos.com> writes: ? >>From: Peter 'EPLAN' LANGSTOEGER [mailto:peter@langstoeger.at] @ >>No. The DEC 3000 are alltogether EV4 (and maybe EV45) systems.9 >>The 164LX is as the name already shows an EV5 system...  > I >OK, but this then at least establishes that FW 6.0 will run on even this  >older system.  D It depends. What is FW 6.0 ? The version number of the Firmware CD ?I Or the version number of the most important firmware on the firmware CD ?   I Every machine has its own version of the firmware. And every file has its  own version number.   M The last (current ? Hah, it is many years old !) version for DEC 3000 systems   / 	V7.0	M300_V7_0.SYS	M400_V7_0.SYS	M500_V7_0.SYS   : The last (again some years old) version for PWS systems is   	V7.2-1	DIGITALPW_V72_1.SYS   < The last (of course some years old) version for a PC164LX is   	V5.8	LX164_V5_8.SYS  J The last (years old) version for a XP1000 is (below recommended version !)   	V5.9-1	XP1000_V59_1.SYS  1 The latest (it is very new) version for a DS10 is    	V6.6	DS10_V6_6.SYS    So, what V6.0 do you mean ?    --   Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  % Date: Sun, 14 Dec 2003 16:03:53 -0800 # From: "Tom Linden" <tom@kednos.com> ( Subject: RE: Problems with 7.3 and 164LX9 Message-ID: <CIEJLCMNHNNDLLOOGNJIKEKEIKAA.tom@kednos.com>    >-----Original Message----- > >From: Peter 'EPLAN' LANGSTOEGER [mailto:peter@langstoeger.at]( >Sent: Sunday, December 14, 2003 3:56 PM >To: Info-VAX@Mvb.Saic.Com) >Subject: RE: Problems with 7.3 and 164LX  >  > @ >In article <CIEJLCMNHNNDLLOOGNJIOEKCIKAA.tom@kednos.com>, "Tom ! >Linden" <tom@kednos.com> writes: @ >>>From: Peter 'EPLAN' LANGSTOEGER [mailto:peter@langstoeger.at]A >>>No. The DEC 3000 are alltogether EV4 (and maybe EV45) systems. : >>>The 164LX is as the name already shows an EV5 system... >>J >>OK, but this then at least establishes that FW 6.0 will run on even this >>older system.  > E >It depends. What is FW 6.0 ? The version number of the Firmware CD ? J >Or the version number of the most important firmware on the firmware CD ? > J >Every machine has its own version of the firmware. And every file has its >own version number. > B >The last (current ? Hah, it is many years old !) version for DEC 
 >3000 systems  > 0 >	V7.0	M300_V7_0.SYS	M400_V7_0.SYS	M500_V7_0.SYS > ; >The last (again some years old) version for PWS systems is  >  >	V7.2-1	DIGITALPW_V72_1.SYS > = >The last (of course some years old) version for a PC164LX is  >  >	V5.8	LX164_V5_8.SYS  > K >The last (years old) version for a XP1000 is (below recommended version !)  >  >	V5.9-1	XP1000_V59_1.SYS  > 2 >The latest (it is very new) version for a DS10 is >  >	V6.6	DS10_V6_6.SYS >  >So, what V6.0 do you mean ?  K Well, I guess it is what SRM is reporting.  From a Tru64 this is what I see    thor/tom 257 > consvar -l -v Firmware Rev: 6.0  system fam:7  cpu:2  smm:1069    >  >--  >Peter "EPLAN" LANGSTOEGER& >Network and OpenVMS system specialist >E-mail  peter@langstoeger.at G >A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist  >  >---' >Incoming mail is certified Virus Free. ; >Checked by AVG anti-virus system (http://www.grisoft.com). A >Version: 6.0.548 / Virus Database: 341 - Release Date: 12/5/2003  >  --- & Outgoing mail is certified Virus Free.: Checked by AVG anti-virus system (http://www.grisoft.com).@ Version: 6.0.548 / Virus Database: 341 - Release Date: 12/5/2003   ------------------------------  % Date: Sun, 14 Dec 2003 14:52:32 -0500 3 From: "Richard B. Gilbert" <rgilbert88@comcast.net> $ Subject: Re: question on SMTP queues0 Message-ID: <LoidnUlcFvEcIkGiRVn-tA@comcast.com>  H I seem to recall running a machine with two SMPT execution queues a few F years ago.  It was a VAX 8350 handling E-mail for some 2000 students, G facutlty, and staff at the then named Philadelphia College of Textiles  6 and Science.  It needed two queues to handle the load.  I You have to understand that this site started with VMS V5.4 and UCX 2.0E  F which didn't handle mail very well and frequently didn't handle it at E all.  Upgrading to VMS V5.5 and UCX 3.3 ECO Level 8 improved matters  E somewhat.  Having two queues enabled the system to keep sending mail  F while one queue was cleaning up after one job and starting the next.  L It's a wonder that the poor machine didn't melt into a puddle of silicon!!!!    % helbig@astro.multiNOSPAMvax.de wrote:   J >There was a thread on this a while back, but I don't recall a definitive  >answer. > I >I'm in the process of re-organising my queue database.  Batch and print  = >queues I understand, but the SMTP queues are a bit puzzling.  >  >Normally, things look like  > , >Generic server queue TCPIP$SMTP_NODENAME_00N >  /GENERIC=(TCPIP$SMTP_NODE_01) /OWNER=[SYSTEM] /PROTECTION=(S:M,O:D,G:R,W:S) >  /SCHEDULE=(NOSIZE)  > O >Server queue TCPIP$SMTP_NODENAME_01, idle, on NODENAME::, mounted form DEFAULT @ >  /BASE_PRIORITY=4 /DEFAULT=(FEED,FORM=DEFAULT) /OWNER=[SYSTEM]? >  /PROCESSOR=TCPIP$SMTP_SYMBIONT /PROTECTION=(S:M,O:D,G:R,W:S)  >  >This raises several questions:  > F >What is the point of a generic queue which points to just ONE server  >queue?  > 3 >What is the point of a generic queue on each node?  > J >Why not have the following setup: there is just one generic server queue , >which points to server queues on each node? >  >    >    ------------------------------  % Date: Sun, 14 Dec 2003 20:18:32 +0100 * From: Paul Sture <nospam@sture.homeip.net>& Subject: Re: TCPIP 5.3 VAX on Hobbyist0 Message-ID: <3FDCC598.19D52E5A@sture.homeip.net>   Michael Unger wrote: > * > On 2003-12-14 11:06, "Paul Sture" wrote: >  > > Michael Unger wrote: > >>
 > >> [...] > >>M > >> Are there *hobbyist* distribution kits? I've been told the "official" CD  > >> kits were quite expensive.  > > K > > I've just checked my email archives. When I registered for the Hobbyist < > > version of MultiNet, Process sent me a download address.; >                                          ^^^^^^^^^^^^^^^^  > > 	 > > [...]  > M > That's fine -- well, at least with a DSL line, sometimes next year perhaps.  >   > Please contact me offline then. I do have ADSL, and CD burning
 capabilities.0   -- u
 Paul Sture   ------------------------------  % Date: Sun, 14 Dec 2003 21:33:20 +0100  From: "KZ" <KZ@lido.com>8 Subject: Re: Time for a community project? (SEARCH/KEY=)4 Message-ID: <3fdcc90e$0$19286$626a54ce@news.free.fr>  I > > `Something I have always wanted was a way to limit SEARCH to specifico# > > `columns in the data such that:e > > `g& > > `$SEARCH/(POS:3,SIZ:5) file string > > 1 > > The FIND/REPLACE freeware for OpenVMS has it:  > >n: > > http://h71000.www7.hp.com/freeware/freeware60/find015/ >.I > But as someone pointed out in another thread, the SEARCH command has it6! > also, with the /KEY= qualifier.L  C True, but FIND looks like it includes everything SEARCH has, plus aiC /REPLACE mode, which is something missing in vanilla OpenVMS tools.L  G In the past, I used EDIT/EDT/COMMAND=REPLACE.EDT (generated on the fly)LI or slow DCL READ/WRITE to do global replaces in batch. With FIND/REPLACE,- it's way simpler.-  E It would be interesting to compare SEARCH and FIND and see if FIND isrG really a superset of the former -- I never bothered to look too hard...  I still use both daily.E   Slog   ------------------------------  # Date: Sun, 14 Dec 2003 20:17:10 GMTe6 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)( Subject: Undocumented GETJPI UAF_FLAGS ?2 Message-ID: <az3Db.66783$dt3.65636@news.chello.at>  @ Recently I did a GETJPI.COM where (part of it) is the following:  - $ uaf_flags = F$GETJPI ("''p1'", "UAF_FLAGS")I $ flaglist = ""IL $ IF (uaf_flags .AND. %X00000800) .NE. 0 THEN flaglist = flaglist + ",Audit"P $ IF (uaf_flags .AND. %X00004000) .NE. 0 THEN flaglist = flaglist + ",AutoLogin"N $ IF (uaf_flags .AND. %X00010000) .NE. 0 THEN flaglist = flaglist + ",Captive"M $ IF (uaf_flags .AND. %X00000002) .NE. 0 THEN flaglist = flaglist + ",DefCLI"0P $ IF (uaf_flags .AND. %X00100000) .NE. 0 THEN flaglist = flaglist + ",DefClsVal"N $ IF (uaf_flags .AND. %X00000010) .NE. 0 THEN flaglist = flaglist + ",DisAcnt"N $ IF (uaf_flags .AND. %X00000001) .NE. 0 THEN flaglist = flaglist + ",DisCtlY"Z $ IF (uaf_flags .AND. %X00008000) .NE. 0 THEN flaglist = flaglist + ",DisForce_Pwd_Change"O $ IF (uaf_flags .AND. %X00020000) .NE. 0 THEN flaglist = flaglist + ",DisImage"iN $ IF (uaf_flags .AND. %X00000080) .NE. 0 THEN flaglist = flaglist + ",DisMail"Q $ IF (uaf_flags .AND. %X00000040) .NE. 0 THEN flaglist = flaglist + ",DisNewMail"iP $ IF (uaf_flags .AND. %X00040000) .NE. 0 THEN flaglist = flaglist + ",DisPwdDic"P $ IF (uaf_flags .AND. %X00080000) .NE. 0 THEN flaglist = flaglist + ",DisPwdHis"R $ IF (uaf_flags .AND. %X01000000) .NE. 0 THEN flaglist = flaglist + ",DisPwdSynch"S $ IF (uaf_flags .AND. %X00002000) .NE. 0 THEN flaglist = flaglist + ",DisReconnect"pP $ IF (uaf_flags .AND. %X00001000) .NE. 0 THEN flaglist = flaglist + ",DisReport"Q $ IF (uaf_flags .AND. %X00000020) .NE. 0 THEN flaglist = flaglist + ",DisWelcome"eN $ IF (uaf_flags .AND. %X00200000) .NE. 0 THEN flaglist = flaglist + ",ExtAuth"M $ IF (uaf_flags .AND. %X00000100) .NE. 0 THEN flaglist = flaglist + ",GenPwd" N $ IF (uaf_flags .AND. %X00000004) .NE. 0 THEN flaglist = flaglist + ",LockPwd"Q $ IF (uaf_flags .AND. %X00400000) .NE. 0 THEN flaglist = flaglist + ",MigratePwd"wR $ IF (uaf_flags .AND. %X00000200) .NE. 0 THEN flaglist = flaglist + ",Pwd_Expired"S $ IF (uaf_flags .AND. %X00000400) .NE. 0 THEN flaglist = flaglist + ",Pwd2_Expired"gM $ IF (uaf_flags .AND. %X02000000) .NE. 0 THEN flaglist = flaglist + ",PwdMix"pQ $ IF (uaf_flags .AND. %X00000008) .NE. 0 THEN flaglist = flaglist + ",Restricted" N $ IF (uaf_flags .AND. %X00800000) .NE. 0 THEN flaglist = flaglist + ",VMSAuth"H $ IF (uaf_flags .AND. %X04000000) .NE. 0 THEN flaglist = flaglist + ",?"H $ IF (uaf_flags .AND. %X08000000) .NE. 0 THEN flaglist = flaglist + ",?"H $ IF (uaf_flags .AND. %X10000000) .NE. 0 THEN flaglist = flaglist + ",?"H $ IF (uaf_flags .AND. %X20000000) .NE. 0 THEN flaglist = flaglist + ",?"H $ IF (uaf_flags .AND. %X40000000) .NE. 0 THEN flaglist = flaglist + ",?"H $ IF (uaf_flags .AND. %X80000000) .NE. 0 THEN flaglist = flaglist + ",?" $ flaglist = flaglist - ","o0 $ say   "UAF_FLAGS = ''uaf_flags' (''flaglist')"  5 and it seems, that I see some of them not documented. D Where can I find something to "DisAcnt","DefClsVal","MigratePwd",...   TIA.   -- s Peter "EPLAN" LANGSTOEGERa% Network and OpenVMS system specialista E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  % Date: Sun, 14 Dec 2003 16:13:57 -0500 $ From: Hein <hein_cov@eps.zk.dec.com>, Subject: Re: Undocumented GETJPI UAF_FLAGS ?. Message-ID: <3FDCD295.738FD67F@eps.zk.dec.com>    Peter 'EPLAN' LANGSTOEGER wrote:  B > Recently I did a GETJPI.COM where (part of it) is the following:   <snip>  7 > and it seems, that I see some of them not documented.oF > Where can I find something to "DisAcnt","DefClsVal","MigratePwd",...  Q Not an answer, but if you were to do the bit-test in a loop it could look like...e (Snowy Sunday afternoon :-)e   $ uaf_flags = 0t- $ uaf_flags = F$GETJPI ("''p1'", "UAF_FLAGS")  $ list = ""sN $flags="DisCtlY,DefCLI,LockPwd,Restrict,DisAcnt,DisWelcom,DisNewMai,DisMail,"-M +"GenPwd,Pwd_Expir,Pwd2_Expi,Audit,DisReport,DisReconn,AutoLogin,DisForce_,"- M +"Captive,DisImage,DisPwdDic,DisPwdHis,DefClsVal,ExtAuth,MigratePw,VMSAuth,"- 1 +"DisPwdSyn,PwdMix,b26?,b27?,b28?,b29?,b30?,b31?"  $bit = 0	 $mask = 1 
 $bit_loop:N $if (uaf_flags .AND. mask).NE.0 then list = list + "," + f$elem(bit,",",flags) $mask = mask * 2 $bit = bit + 1" $if bit .lt. 32 then goto bit_loop $ list = list - ","c9 $ write sys$output   "UAF_FLAGS = ''uaf_flags' (''list')"    Hein.    ------------------------------  # Date: Sun, 14 Dec 2003 21:48:59 GMTe6 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER), Subject: Re: Undocumented GETJPI UAF_FLAGS ?1 Message-ID: <fV4Db.68181$dt3.8212@news.chello.at>g  U In article <3FDCD295.738FD67F@eps.zk.dec.com>, Hein <hein_cov@eps.zk.dec.com> writes:n! >Peter 'EPLAN' LANGSTOEGER wrote: C >> Recently I did a GETJPI.COM where (part of it) is the following:r >m ><snip>s >n8 >> and it seems, that I see some of them not documented.G >> Where can I find something to "DisAcnt","DefClsVal","MigratePwd",...d >kR >Not an answer, but if you were to do the bit-test in a loop it could look like... >(Snowy Sunday afternoon :-) >e >$ uaf_flags = 0. >$ uaf_flags = F$GETJPI ("''p1'", "UAF_FLAGS") >$ list = ""O >$flags="DisCtlY,DefCLI,LockPwd,Restrict,DisAcnt,DisWelcom,DisNewMai,DisMail,"-nN >+"GenPwd,Pwd_Expir,Pwd2_Expi,Audit,DisReport,DisReconn,AutoLogin,DisForce_,"-N >+"Captive,DisImage,DisPwdDic,DisPwdHis,DefClsVal,ExtAuth,MigratePw,VMSAuth,"-2 >+"DisPwdSyn,PwdMix,b26?,b27?,b28?,b29?,b30?,b31?"	 >$bit = 0t
 >$mask = 1 >$bit_loop:rO >$if (uaf_flags .AND. mask).NE.0 then list = list + "," + f$elem(bit,",",flags)  >$mask = mask * 2h >$bit = bit + 1o# >$if bit .lt. 32 then goto bit_loopd >$ list = list - ",": >$ write sys$output   "UAF_FLAGS = ''uaf_flags' (''list')"  ? Of course, but then the items are not sorted alphabetically ;-)b   -- b Peter "EPLAN" LANGSTOEGERt% Network and OpenVMS system specialistd E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  % Date: Mon, 15 Dec 2003 05:49:18 +0800l, From: Paul Repacholi <prep@prep.synonet.com>5 Subject: Re: VAX 11/750 and RL02 - trying to boot VMSs- Message-ID: <87y8tf134x.fsf@prep.synonet.com>6  , Paul Sture <nospam@sture.homeip.net> writes:  E > And in 750 days, an OEM was claiming that their version of 750s hadnE > some kind of performance boost. We never found out exactly how theyoF > intended to achieve that. I never did find another 750 quite as fast& > as the pair I was running however...   This wasn't Systime(?) was it?   --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076* comp.os.vms,- The Older, Grumpier Slashdot. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------   End of INFO-VAX 2003.692 ************************