1 INFO-VAX	Wed, 26 May 2004	Volume 2004 : Issue 290       Contents: Re: 83x0 Re: 83x0' ACCOUNTING bug ! (long screen displays)  Re: Bind and stuffH RE: Carly responds to my email about advertising!  Yes, they will do it!H Re: Carly responds to my email about advertising!  Yes, they will do it! Re: CSWS 2.0 Source Code?  Re: CSWS 2.0 Source Code?  Re: CSWS 2.0 Source Code?  Re: CSWS 2.0 Source Code?  Re: CSWS 2.0 Source Code?  Re: Dave Cutler and VMS  Re: mc ncp show known link2 Re: Michael Voight of Cisco forging messages again2 Re: Michael Voight of Cisco forging messages again2 Re: Michael Voight of Cisco forging messages again2 Re: Michael Voight of Cisco forging messages again Re: OpenVMs Cluster  Re: OpenVMs Cluster 4 Re: Previous Post - Upgrading Cluster Communications! Re: Reboot forces Shadowset Merge ! RE: Reboot forces Shadowset Merge ! Re: Reboot forces Shadowset Merge  Re: SEARCH question  Re: SEARCH question  RE: SEARCH question 6 TCPIP Services for OpenVMS V5.4 ECO1 anti spam feature: Re: TCPIP Services for OpenVMS V5.4 ECO1 anti spam feature  F ----------------------------------------------------------------------  % Date: Wed, 26 May 2004 01:37:45 +0800 , From: Paul Repacholi <prep@prep.synonet.com> Subject: Re: 83x0 - Message-ID: <87vfik2ys6.fsf@prep.synonet.com>   4 Bob Willard <BobwBSGS@TrashThis.comcast.net> writes:   > Chris Scheers wrote:  >> "Roert G. Schaffrath" wrote: >>H >>>I had always wanted to try taking two CPU's from a spare 8350 and putF >>>them into another 8350 for a total of four CPU's and see what wouldI >>>happen.  Unfortunately, when I had access to that many 82xx CPU cards, I >>>VMS V5.0 was not available.  By the time VMS V5.0 came out, I was at a H >>>different job and did not have to ability to perform that experiment.I >>>Performance would have been lousy on the BI bus but it would have been  >>>an interesting machine.@ >> The early documentation for SMP support in VMS referenced two >> machines:5 >> an 8800 with two CPUs and an 8370 with seven CPUs. C >> It appears that any 8300 or 8350 with three or more CPUs will be   >> identified by VMS as an 8370. >>< > Sounds like a typo.  The Scorpio family of VAXen included: > ! > 8200: Original Single 5 MHz CPU  > 8300: Original Dual 5 MHz CPU % > 8300: Follow-on Single 6.25 MHz CPU # > 8350: Follow-on Dual 6.25 MHz CPU G > 8370: Follow-on Triple 6.25 MHz CPU (never announced or shipped IIRC)   I Plus the Vaxstation 8000, who's name has run off and hid at the moment...    --  < 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: Tue, 25 May 2004 19:50:29 +0100 ) From: Antonio Carlini <arcarlini@iee.org>  Subject: Re: 83x0 ; Message-ID: <1sNsc.200$a%4.139@newsfe5-gui.server.ntli.net>    Paul Repacholi wrote: K > Plus the Vaxstation 8000, who's name has run off and hid at the moment...   8 It's a little minx that name. No, hang on, I meant Lynx.   Antonio    --   --------------- - Antonio Carlini             arcarlini@iee.org    ------------------------------  # Date: Tue, 25 May 2004 19:10:09 GMT - From: JF Mezei <jfmezei.spamnot@teksavvy.com> 0 Subject: ACCOUNTING bug ! (long screen displays)@ Message-ID: <4e0e144f294a2e28c2fb43dbe675d218@news.teranews.com>   SET TERM/PAGE=51   (on a decterm)  P ACCOUNT/FULL/TYPE=USER   (to show the antispam logs from the TCPIP SMTP server).  I ACCOUNTING doesn't honour the page size fully. The "Press RETURN for Next N Record" is indeed placed at the bottom of the screen correctly. But the recordN information, including the "dump style" output for the final status text don'tM use the available page and leave most of the page unused, requiring one to go I to a next page to see the last few lines of output for that record (which 3 would have fit very comfortably on the first page).    ------------------------------  # Date: Tue, 25 May 2004 18:40:34 GMT 1 From: Michael Austin <maustin@firstdbasource.com>  Subject: Re: Bind and stuff 2 Message-ID: <40B39320.C4941AC9@firstdbasource.com>   Dan Allen wrote:   > <stuff snipped>    > G >         While all of the above is correct AD REQUIRES the underscores J > and you'll need to make sure all of the AD servers and clients use a DNSG > server that supports not only underscores in names but SRV records as I > well. This isn't the first time an RFC isn't followed to the letter and H > likely won't be the last. Running a DNS server that allows underscoresI > doesn't break anybody's apps - it just lets AD work and also happens to G > make lookups for the substantial number of DNS names owned by lots of F > non-AD sites to lookup as well. IMNSHO the RFC's should be tweaked -G > it's been done before when the need arose and there was no compelling  > technical argument otherwise.  >  > Dan    Dan,  K the technical argument to NOT tweak it is that there are more sites that do L not use AD and their client apps follow the RFC as they should... Looks likeJ MS is trying to re-write yet another RFC.  If you "need" to use names with= illegal characters, then add an alias that does not use it...    ------------------------------  % Date: Tue, 25 May 2004 15:14:36 -0400 ' From: "Main, Kerry" <kerry.main@hp.com> Q Subject: RE: Carly responds to my email about advertising!  Yes, they will do it! R Message-ID: <FD827B33AB0D9C4E92EACEEFEE2BA2FB355E3B@tayexc19.americas.cpqcorp.net>   > -----Original Message------ > From: John Smith [mailto:a@nonymous.com]=20  > Sent: May 25, 2004 11:53 AM  > To: Info-VAX@Mvb.Saic.Com ? > Subject: Re: Carly responds to my email about advertising!=20  > Yes, they will do it!  >=20< > Here's the next 'mention' of OpenVMS by HP in an ad (.pdf) >=20> >   May 24/2004 edition of eWeek, page 47 (not exactly your=20 > most high-profile  > location in the magazine). >=20: > It's virtually the same ad as before - same companies=20 > mentioned - same focus= > on IA64.  Bet they were choking while they told their ad=20  > agency to insert > the word 'OpenVMS'.  >=20   John,   * Go to www.eweek.com and click on HP ad.=20  5 When's the last time you saw OpenVMS in an online ad?    :-)    Regards   
 Kerry Main Senior Consultant  HP Services Canada Voice: 613-592-4660  Fax: 613-591-4477  Email: kerryDOTmainAThpDOTcom . (remove the DOT's and AT for email address)=20   ------------------------------  % Date: Tue, 25 May 2004 16:00:01 -0400 # From: "John Smith" <a@nonymous.com> Q Subject: Re: Carly responds to my email about advertising!  Yes, they will do it! , Message-ID: <986dnWLOj7lcOC7d4p2dnA@igs.net>  2 "Main, Kerry" <kerry.main@hp.com> wrote in messageL news:FD827B33AB0D9C4E92EACEEFEE2BA2FB355E3B@tayexc19.americas.cpqcorp.net...     > -----Original Message-----* > From: John Smith [mailto:a@nonymous.com] > Sent: May 25, 2004 11:53 AM  > To: Info-VAX@Mvb.Saic.Com < > Subject: Re: Carly responds to my email about advertising! > Yes, they will do it!  > < > Here's the next 'mention' of OpenVMS by HP in an ad (.pdf) > ; >   May 24/2004 edition of eWeek, page 47 (not exactly your  > most high-profile  > location in the magazine). > 7 > It's virtually the same ad as before - same companies  > mentioned - same focus: > on IA64.  Bet they were choking while they told their ad > agency to insert > the word 'OpenVMS'.  >    John,   ' Go to www.eweek.com and click on HP ad.   5 When's the last time you saw OpenVMS in an online ad?    --------------   Kerry,  B Like I said, I saw the noun 'OpenVMS' but I didn't see any OpenVMS advertising.  K I must have missed something in both the print ads and the on-line ones and I perhaps you can point out just which of these 'reference' success stories , for Integrity servers actually uses OpenVMS?    . I'll be interested to see the HP ad that says,  J  "Windows, Linux, HP-UX, Tru64 - these are all operating systems HP sells,= and each of them suck big time, though some less than others.   K The only operating systems HP offers that are any good happen to be the two L best operating systems on the planet, OpenVMS and NSK. Frankly we don't know0 why we even bother dealing with that other crap.  F If you want to avoid viruses, worms, downtime, reliability issues, and- scalability issues, then use OpenVMS and NSK.   5 Call 1-800-OpenVMS and tell them carly(tm) sent you."   * (c) 2004, John Smith. All Rights Reserved.   ------------------------------  # Date: Tue, 25 May 2004 17:48:06 GMT - From: JF Mezei <jfmezei.spamnot@teksavvy.com> " Subject: Re: CSWS 2.0 Source Code?@ Message-ID: <8db5bf72d586dbbb8ed133aee2930340@news.teranews.com>  
 re: file size   N My view is that there should be a field added, even to ODS-2 on VAX containingJ a file size. This field would be left blank (or some "out of range value")M until some application set a file size value through some RMS call. This file L size value would remain in place until the next write to the file , at which0 point it would return to its indeterminate size.  E It would be up to the applications de decide on what value to put in.   K The advantage of this is that it would either be real value, or no value at N all (no estimates). And for a web site, you,d need to calculate the value onlyK once and then once stored, it would be available without having to read the  file fully first.   H There are a LOT of applications that require file sizes (including IMAP,5 XMODEM, Y-MODEM, web servers, POP server etc etc etc.   K They could also provide super efficient RMS calls that would calculate file 2 size based on current open method (text, raw etc).   ------------------------------  % Date: Wed, 26 May 2004 01:29:55 +0800 , From: Paul Repacholi <prep@prep.synonet.com>" Subject: Re: CSWS 2.0 Source Code?- Message-ID: <87zn7w2z58.fsf@prep.synonet.com>   - David J Dachtera <djesys@comcast.net> writes:    > Rick Barry wrote:    6 >> The accurate determination of file size is just oneC >> issue. Meta-data in record formats such as variable-length cause C >> problems when Apache 2.0 maps the file in memory for performance F >> reasons. The meta-data get read as data which, of course, is wrong.@ >> We either figure out a way to filter the meta-data or not map >> certain record formats.  E > Wouldn't using RMS to read the file into memory solve that problem?   D Ha! You read a fixed length record file with the CRTL, and it adds aF freebe <LF> to every record. If you buffer is set to the length of the( file, much screaming in the distance...   < What about a Relative or Indexed file with deleted records?    --  < 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: 25 May 2004 13:48:50 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen) " Subject: Re: CSWS 2.0 Source Code?3 Message-ID: <vzg1pQWY0Qfm@eisner.encompasserve.org>   q In article <uiQ59p+UPPwM@eisner.encompasserve.org>, koehler@eisner.nospam.encompasserve.org (Bob Koehler) writes: e > In article <cere61r6agu4@eisner.encompasserve.org>, Kilgallen@SpamCop.net (Larry Kilgallen) writes: _ >> In article <dQosc.2140$gn.553@news.cpqcorp.net>, "Rick Barry" <richard.barry@hp.com> writes:  >>  K >>> The accurate determination of file size is just one issue. Meta-data in N >>> record formats such as variable-length cause problems when Apache 2.0 mapsN >>> the file in memory for performance reasons. The meta-data get read as dataI >>> which, of course, is wrong.  We either figure out a way to filter the 0 >>> meta-data or not map certain record formats. >>  E >> I was under the impression that VMS compilers for years had mapped D >> variable length record files and just skipped the count words and# >> fill bytes when interpreting it.  > A >    No.  The VMS compilers simply generate I/O calls to routines  >    built on top of RMS.   D No, I am not talking about what the compilers generate, I am talkingF about how they read the source files.  I know I have heard of at least@ one VMS compiler from DEC that mapped the files, and maybe more.   ------------------------------  # Date: Tue, 25 May 2004 19:12:16 GMT - From: JF Mezei <jfmezei.spamnot@teksavvy.com> " Subject: Re: CSWS 2.0 Source Code?@ Message-ID: <a8e1158c4f5998fdb6ea59bb26da6151@news.teranews.com>   Larry Kilgallen wrote:F > No, I am not talking about what the compilers generate, I am talkingH > about how they read the source files.  I know I have heard of at leastB > one VMS compiler from DEC that mapped the files, and maybe more.    L Since DEC-C (and predecessor VAX-C) allow you to specify a whole slew of RMSH attributes in the fopen, creat, open  C rtl routines, it is very safe to' presume that they make full use of RMS.   F Furthermore, since they allow one to open an indexed files and read itK sequentially (transparanetly to the program), it is also another indication - that the CRTL makes use of RMS to read files.    ------------------------------    Date: 25 May 2004 15:40:07 -0600; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) " Subject: Re: CSWS 2.0 Source Code?3 Message-ID: <i78GaLJ8AIqF@eisner.encompasserve.org>   c In article <vzg1pQWY0Qfm@eisner.encompasserve.org>, Kilgallen@SpamCop.net (Larry Kilgallen) writes:  > F > No, I am not talking about what the compilers generate, I am talkingH > about how they read the source files.  I know I have heard of at leastB > one VMS compiler from DEC that mapped the files, and maybe more.  F    I'll have to check out some compilers against some different record     formats and see if any choke.   ------------------------------  % Date: Tue, 25 May 2004 19:50:16 +0200 , From: "Hans Vlems" <hvlems.dotweg@zonnet.nl>  Subject: Re: Dave Cutler and VMS* Message-ID: <2hhffgFch8ppU1@uni-berlin.de>  A "Bob Willard" <BobwBSGS@TrashThis.comcast.net> schreef in bericht ) news:4k3sc.16339$JC5.1457137@attbi_s54...  > Hans Vlems wrote: E > > "Bob Willard" <BobwBSGS@TrashThis.comcast.net> schreef in bericht * > > news:gXHrc.22492$zw.16951@attbi_s01... > >  > >>Steve Lionel wrote:  > >> > >>I > >>>Cutler left VMS in 1980 before version 2.0 was released, and was not  > >  > > further  > > * > >>>involved with the VMS OS development. > >>> 
 > >>>Steve > >>I > >>While not part of the VMS group after ~1980, Dave did have some later A > >>and substantial influence on VMS when he was running DEC-West  > >>(ZSO, a/k/a DecWet). > >>I > >>When some of us were campaigning to get VMS to support SMP instead of  AMP,K > >>Dick H. was adamantly opposed.  Dave took a (huge) pile of VMS listings  toI > >>his office in ZSO, marked them up with changes needed to support SMP,  and L > >>had them delivered to ZKO to prove that SMP was feasible with VMS.  I doL > >>not know how much of Dave's changes were actually incorporated into VMS, > >  > > but  > > I > >>the SMP version of VMS was extremely valuable to DEC and, IMHO, would  not H > >>have happened (or not in time for the VAX 6K) without Dave's effort. > >>J > >>More opinion:  in the Hustvedt-dominated environment of the early-80'sK > >>VMS group, it was not fashionable to give credit to Cutler or, in fact, G > >>to any non-VMS person for contributions to VMS.  So, even if Dave's  > >  > > changes  > > L > >>to support SMP were used in toto, they may bear some initials other thanE > >>DNC.  While Dick H. and Dave C. were both extraordinary technical  people, K > >>their deep disagreement on VMS issues was well-known and was one of the K > >>reasons that Dave left VMS:  Dave pointed out that the Seattle area was 4 > >>about as far as he could get from the VMS group. > >>D > >>Caveat:  I was never part of the VMS group.  I was significantly involvedK > >>in the first MP VAX and the first good MP VAX; yeah, I know, those were  > >>different VAXen. > >>--   > >>Cheers, Bob  > >> > > J > > The first MP VAX being the 11/782? The first "good" MP one the 8350 or the  > > 62n0 series?L > > The reason that the later models behaved better was due to the fact that > > until VMS V5.0 one2 > > cpu was the primary cpu, and handled all IO's?I > > Lots of questions I know but if you'd care to elaborate somewhat... I  > > remember upgradingK > > from VMS V4.7 on an 8350 without the multi cpu license to V5.0 that had  dual > > cpu support 9 > > and was quite impressed with the scaling at the time.  > >  > > Hans > I > Yep, the VAX 11/782 (Code-named Atlas IIRC) was the first MP VAX; not a I > great design, and probably would have never been done if the 11/790 had H > not been woefully behind schedule.  I count the 8300 as the first goodI > MP VAX:  the 8800 and the 8300 were introduced on the same day, but the L > 8300 was ready first, and its intro was delayed a couple of months to haveI > a grand marketing splash with several new VAXen.  The 8250/8350 was the ; > 8200/8300 with a 25% faster CPU clock; same architecture.  > L > The 83x0 and 88x0 systems all shipped initially with AMP.  SMP came later,H > and was first shipped on the 62x0 systems.  SMP was mostly debugged onG > 8250/8350 systems, and on the (never-shipped) tri-CPU 8370 and on the 8 > (never-got-officially-numbered) quad-CPU 83x0 systems. > --  
 > Cheers, Bob  > J The 8350 may not have been a fast VAX but it surely was reliable. The only	 time I've J seen more than 1000 days up time was on a CI cluster with two  VAX  8350's and # two HSC50's. All disks were RA81's!  Hans   ------------------------------  % Date: Tue, 25 May 2004 20:21:24 -0400 . From: "Jim Mickalide" <mickalide@adelphia.net># Subject: Re: mc ncp show known link 1 Message-ID: <HbidnRb0U7eZfi7d4p2dnA@adelphia.com>   C In phase IV  it is either a Line or a Circuit.  In Phase V they use  different terms ; Line is the phsical  part and circuit is the logical piece.           C "Peter 'EPLAN' LANGSTOEGER" <peter@langstoeger.at> wrote in message + news:newscache$pt5ayh$l052$1@news.sil.at... ? > In article <93820504.0405242246.1d10dc14@posting.google.com>, / denis.fayaud@netspace.mc (Denis Fayaud) writes: I > >Is there a system service or any other function to retrieve the decnet / > >links as the "mc ncp show known link" does ? " > >(decnet IV & OpenVMS Alpha 7.3) > J > Don't think so. There isn't much of a DECnet API implemented/documented.D > But at least, you have the option to get the infos out (with NCP). > E > In DECnet Phase 5, I know of the X11 application NET$MGMT.EXE which C > (uses CML and) has a "Tasks" menu entry called "Show Known Links" F > (because there seems to be no direct way in DECnet-Plus utility NCL)+ > but I don't remember seeing it working...  >  > --   > Peter "EPLAN" LANGSTOEGER ' > Network and OpenVMS system specialist  > E-mail  peter@langstoeger.atH > A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  # Date: Tue, 25 May 2004 17:36:10 GMT  From: mrtravelkay <a@a.aa.a>; Subject: Re: Michael Voight of Cisco forging messages again > Message-ID: <euLsc.56835$Ow7.52353@newssvr29.news.prodigy.com>   Max Mustermann wrote:   K > Cisco troll/netkook/asshole Michael Voight mrtravelkay <a@a.aa.a> kooked:  >  >  >>Darrell Larose DID NOT wrote:  >> >>" >>>Still molesting children, Gary? >>> . >>>Still not allowed to go back to California? >>> 3 >>>How many years did you end up serving in prison?  >>>  >> >>Not even a good forgery. >  >  > Then why did you do it?    > IP address: 171.71.79.66  @ I didn't do it, it came via dizum, so I think I know who did it.   ------------------------------  # Date: Tue, 25 May 2004 17:35:36 GMT  From: mrtravelkay <a@a.aa.a>; Subject: Re: Michael Voight of Cisco forging messages again % Message-ID: <40B383E8.4080104@a.aa.a>    Gary L. Burnore wrote:  / > On 25 May 2004 18:37:10 +0200, Max Mustermann ) > <anonymous@remail.amessage.info> wrote:  >  > K >>Cisco troll/netkook/asshole Michael Voight mrtravelkay <a@a.aa.a> kooked:  >> >>  >>>Darrell Larose DID NOT wrote: >>>  >>> # >>>>Still molesting children, Gary?  >>>>/ >>>>Still not allowed to go back to California?  >>>>4 >>>>How many years did you end up serving in prison? >>>> >>>  >>>Not even a good forgery.  >> >>Then why did you do it?  >> >>IP address: 171.71.79.66& >>Host name: mvoight-w2k02-1.cisco.com >  > H > OOOOh, looks like an anonymous coward is jealous that someone can post) > from somewhere other than a remailer.    > ; > [SNIP a bunch of shit you're too cowardly to do yourself]    I didn't do it.    ------------------------------  % Date: Tue, 25 May 2004 14:06:01 -0400 . From: Gary L. Burnore <gburnore@databasix.com>; Subject: Re: Michael Voight of Cisco forging messages again 8 Message-ID: <c901pg$ejg$2@blackhelicopter.databasix.com>  ? On Tue, 25 May 2004 17:35:36 GMT, mrtravelkay <a@a.aa.a> wrote:    >  >  >Gary L. Burnore wrote:  > 0 >> On 25 May 2004 18:37:10 +0200, Max Mustermann* >> <anonymous@remail.amessage.info> wrote: >>   >>  L >>>Cisco troll/netkook/asshole Michael Voight mrtravelkay <a@a.aa.a> kooked: >>>  >>> ! >>>>Darrell Larose DID NOT wrote:  >>>> >>>>$ >>>>>Still molesting children, Gary? >>>>> 0 >>>>>Still not allowed to go back to California? >>>>> 5 >>>>>How many years did you end up serving in prison?  >>>>>  >>>> >>>>Not even a good forgery. >>>  >>>Then why did you do it? >>>  >>>IP address: 171.71.79.66 ' >>>Host name: mvoight-w2k02-1.cisco.com  >>   >>  I >> OOOOh, looks like an anonymous coward is jealous that someone can post * >> from somewhere other than a remailer.   >>  < >> [SNIP a bunch of shit you're too cowardly to do yourself] >  >I didn't do it.  C Didn't say you did, dip.  More likely the anonymous coward doing it 
 himself.     ------------------------------    Date: 25 May 2004 21:45:39 +02005 From: Max Mustermann <anonymous@remail.amessage.info> ; Subject: Re: Michael Voight of Cisco forging messages again C Message-ID: <0248c580e637f028b6883910a83d6c4e@remail.amessage.info>   I Cisco troll/asshole/netkook Michael Voight mrtravelkay <a@a.aa.a> kooked:    >  >  >Max Mustermann wrote: > L >> Cisco troll/netkook/asshole Michael Voight mrtravelkay <a@a.aa.a> kooked: >>   >>    >>>Darrell Larose DID NOT wrote: >>>  >>> # >>>>Still molesting children, Gary?  >>>>/ >>>>Still not allowed to go back to California?  >>>>4 >>>>How many years did you end up serving in prison? >>>> >>>  >>>Not even a good forgery.  >>   >>   >> Then why did you do it? >  >> IP address: 171.71.79.66  > A >I didn't do it, it came via dizum, so I think I know who did it.    Yep:  ; About rogue Cisco employee and netkook/troll/usenet flooder 5 Michael Voight, alias "mrtravel", "mrtravelkay", etc.   P "mrtavelkay" is the latest usenet handle of a brainless troll whose real name is+ Michael Voight, e-mail <mvoight@cisco.com>.    Michael D. Voight  111 Bean Creek Rd, No. 118 Scotts Valley,  CA  95066-4148 (831) 438-2485  = He is better known by his previous stupid handle, "mrtravel".   < The idiot works for Cisco in their Scotts Valley, California; Technical Assistance Center (TAC) and apparently they don't K keep him busy enough so he has to troll usenet newsgroups all day long from  work.   M ***WARNING:  THIS IDIOT HAS BEEN CAUGHT FORGING PEOPLE'S IDENTITIES ON USENET  AND CANCELLING THEIR POSTS.***  O If you are one of his victims, or are simply fed up with his trolling/newsgroup 0 flooding, forward his posts to abuse@cisco.com .  D He works in technical support, so forward them to tac@cisco.com too.  5 See further below for more Cisco contact information.   @ He often posts through sbcglobal and prodigy, so forward them to2 abuse@prodigy.net and abuse@sbcglobal.net as well.  H His main hangout is alt.visa.us.marriage-based, a sleazy newsgroup whereM foreigners wanting to immigrate to the US hook up with losers like Voight who P are willing to marry them for money so they can get their green card.  Voight isL a pro at this, handing out daily advice on how to be a sleazoid like him and sell green cards.   B When he isn't giving out advice on how to commit federal crimes onH alt.visa.us.marriage-based he is usually on rec.travel.air flooding thatP newsgroup with trolls and harassing posters and picking retarded fights with the regular posters there.  N He also tends to post a lot in the personals and penpals newsgroups as well asO the support groups for fat people, lonely folks, and for depression.  Obviously N after his Russian Internet brides get their green cards they flee, leaving himN lonely and desperate for company.  Maybe that's why he keeps a P.O. Box at the4 post office, so he can get his personals mail there:   Voight, Michael  P.O. Box 67016,  Scotts Valley, CA 95067  (408) 461-8707  > He also seems to frequent the teenage newsgroups.  Creepy.....  O The idiot is a two-time high school dropout and had to join the Marines because  even the Army rejected him!   F He's got a daughter in Orange County that one of his ex-wives had the D intelligence to take away from him.  Lord only knows what could haveN happened to her if she had continued to live with the kook.  The other kids heO has belong to his previous Russian sleazy brides, and since they come and go so L do the kids.  It wouldn't hurt to let Cisco know what kind of deviant sexual# pervert they have working for them.   P Many people have wondered how Cisco ever hired such a psycho.  It cheapens theirO image and credibility in the corporate world after all.  Well, they didn't hire O him directly, he came as baggage when they acquired the company he used to work J for, TGV Software.  His e-mail address there used to be <mvoight@tgv.com>.  O All intelligent members of the usenet community have killfiled him, so he takes P great pains to get past their killfiles by rubbing his only two cerebral neuronsK together and coming up with gems like: mrtrav <mrtrav@mtr.mrt.trm>, mrtrav3 H <mrtaa@aa.aa>, mrraveltay <mrraveltay@me.igpay.atinlay>, and mrtravelkayG <mrtravelkay@a.aa>, and mtravelkay <a.a.a@aaa.aaa> and <""a.a\"@a,a,a>.   3 Some of his other trolling aliases are Network Guy, K <starrystarrynight@sbcglobal.net>, sleepydoc <sleepdoc@verizon.net>, jlhunt M <jlhunt@huntbros.com>, and Lost 5 of 8 <seeme@loveme.fun>, mrt <mrt@mrt.com>, 1 news.sf.sbcglobal.net <none@none.none>, not-nomen 7 <none@none.none>,<uclaisthebest@ucla.edd>, David Tanner F <dtanner1256@dtanner.org>, Jeff Davies <test@test.test>, BobTheBuilderJ <noah@build.me.an.ark>.  The lastest product of his brain diarrhea is Bill$ Clarkj <bill@billclarkpresents.com>.  O It would be a good idea to call Cisco at 1-800-553-2447 and ask to speak with a P supervisor and explain that you are EXTREMELY unhappy that this idiot spends hisN whole day at work playing on the internet on company time.  THEY WILL NOT LIKE THAT.   L Then write to corporate headquarters explaining what this idiot is doing andL telling them HOW BAD IT IS FOR THEIR COMPANY IMAGE.  They will LOVE that you  brought this to their attention:   Cisco Systems, Inc.  170 West Tasman Dr.  San Jose, CA 95134 USA   M Then also call them.  You should always follow up email or letters with phone H calls.  Always ask for supervisors or managers.  Try to get as far up as	 possible.   
 (408)526-4000  (800)553-NETS or
 (800)553-6387   K Contact Investor Relations and tell them you are interested in investing in O their company but won't do so until they get rid of this asshole who is wasting  company resources:   Cisco Systems, Inc.  Investor Relations Department  170 West Tasman Drive  San Jose, CA 95134-1706  Phone: (408) 526-8890  Fax: (408) 526-4545 # Email: investor-relations@cisco.com   P Might as well contact customer service too, they LOVE to hear about this type of stuff:   USA 1 800 553 6387   ic-support-us@cisco.com  cs-support-us@cisco.com   C Then finally, send letters with copies of his nasty posts addressed ? personally to each one of the OFFICERS of the company using the I headquarters address.  Believe me, they READ your complaints and are VERY O INTERESTED in them, especially if it's about one of their employees.  They will F take a PERSONAL interest in rooting this ASSHOLE out of their company:   John Morgridge, Chairman John Chambers, President, CEO  Donald Valentine, Vice Chairman 9 Larry Carter, CFO, Sr. VP-Fin. and Admin., Sec., Director 3 Richard Justice, Sr. VP, Worldwide Field Operations   	 Have fun!    ------------------------------  % Date: Tue, 25 May 2004 22:07:38 +0200  From:  neale.hunt@hispeed.ch Subject: Re: OpenVMs Cluster) Message-ID: <c90926$apl$1@newshispeed.ch>   	 Hi Jutta,   H in the -flags the first parameter is the "system root" so that needs to F match with a directory on the boot server, is dka0:[sys11]  = root 11.  + You cannot boot 2 hosts from the same root.   H Is this host just a straight replacement for Alpha 255, or have you run F cluster_config to add it. If it's s straight replacement you will may I need to change the hardware address in the Decnet database, otherwise it   may not respond.  C VMS version is quite old, I will see if I can check the version of  E firmware needed, although that should not stop it booting, but would  < show a mesage on booting if the firmware revsion is too low.   The message     >boot ewa0.0.0.3.0 -flags 0,0  >Trying MOP boot   >.... bootstrap failure  A rather suggests the boot server does not accept the MOP request,  B although you should see this on the console (depending on what is > enabled by default) or from a priveledged account after doing D reply/ena=network (I think it is - you may want to verify the exact  options from the VMS help).   
   -- Neale   jutta wrote: > Hallo Neale, > ' > the os-version is : OpenVMS V.6.2.1H3  >  >  >> boot -flags 11,20000 9 >>    or	boot -flags 11,20001 (for a conversational boot)  > = > It is the same: I got the message:  .... bootstrap failure. 5 > On the other client: boot_osflags 0,0 and it works.  >  > D >>As regards firmware version, depends on the version of VMS, later G >>versions do need a minimum level of firmware.  It may be possible to  < >>email you a "CD image" if you are able to burn it onto CD. > $ > I'm able to burn something onto CD >  >  > Best of luck >         Jutta  >  > O >  neale.hunt@hispeed.ch wrote in message news:<c8tgl6$ili$1@newshispeed.ch>...  > K >>The personal workstation should not present a problem, I had one running  / >>VMS prior to swapping to an Alphastation 500.  >>D >>As regards firmware version, depends on the version of VMS, later G >>versions do need a minimum level of firmware.  It may be possible to  < >>email you a "CD image" if you are able to burn it onto CD. >>2 >>use "show sys /noproc" to determine the version. >> >>Part of the problem will be  >> >>  "boot_osflags 0,0",  >> >>  the hint here is >>1 >>Load Assist Parameter    = POALF2$DKA0:<SYS11.>  >>. >>So the root you need to boot is "11" not "0" >> >>so set boot_osflags 11,0 >>6 >>to see what is going on in detail try the following: >> >>	>  H >>You get a blow by blow account of the boot, but I'm not sure what you ( >>will see if you get bootstrap failure. >> >>Best of luck >>
 >>-- Neale >> >>	VMS System Specialist >> >>jutta wrote: >> >>>Thanks for the answer.  >>>  >>>I Think we have DECnet - >>>$ mc ncp list known node characteristics :  >>>   >>>Remote node =   2.32 (POALF4)/ >>>Hardware address         = 00-00-F8-75-6C-7F % >>>Load file                = APB.EXE 5 >>>Load Assist Agent        = SYS$SHARE:NISCS_LAA.EXE 2 >>>Load Assist Parameter    = POALF2$DKA0:<SYS11.> >>>   >>>Remote node =   2.33 (POALF5)/ >>>Hardware address         = 00-00-F8-21-E3-F4 % >>>Load file                = APB.EXE 5 >>>Load Assist Agent        = SYS$SHARE:NISCS_LAA.EXE 2 >>>Load Assist Parameter    = POALF2$DKA0:<SYS12.> >>>  >>>poalf4 is the new node. >>>  >>>$ mc lancp sho client *H >>>%LANCP-E-NORSPACP, No response from LANACP, LANACP process apparently >>>not running- >>>%LANCP-E-CMDERROR, Error executing command  >>> I >>>The new Client is a digital personal workstation 433au . Perhaps it is & >>>not the right hardware for OpenVMS? >>>  >>>Jutta >>> a >>>"Hans Vlems" <hvlems.dotweg@zonnet.nl> wrote in message news:<2h1q9oF853dlU1@uni-berlin.de>...  >>>  >>> 5 >>>>"jutta" <jutta.reichel@gmx.de> schreef in bericht : >>>>news:ec7e473.0405190622.77145268@posting.google.com... >>>> >>>>9 >>>>>We have a OpenVMS (Alpha) Cluster with 4 Satellites. H >>>>>One of them is defect. We took another Client with Operating SystemA >>>>>DEC UNIX. We changed the Hardware Address on the Server with  >>>>>Cluster_config.* >>>>>The boot parameter on the new Client: >>>>>  >>>>>  >>>>>>>>os_type OpenVMS  >>>>>>>>ew0_protocols MOP  >>>>>>>>boot_dev ewa0.0.0.14.0 >>>>>>>>boot_osflags 0,0 >>>>>>>>ewa0_inet_init  bootp   >>>>>>>>pal VMS PALcode V1.20-14 >>>>>>>>version V6-9-7 >>>>> : >>>>>We try to boot the new Client and we got the message: >>>>>  >>>>> 	 >>>>>>>>b  >>>>> ! >>>>>boot ewa0.0.0.3.0 -flags 0,0  >>>>>Trying MOP boot >>>>>.... bootstrap failure  >>>>>  >>>>>  >>>>>one of the other clients: >>>>>   >>>>>>>>pal  VMS PALcode V5.65.2 >>>>>>>>version V6.9-4 >>>>> 5 >>>>>Do we need to do somethings more on the server ? # >>>>>Is the firmware the wrong one?  >>>>>  >>>>>Who can help us?  >>>>> 
 >>>>>Jutta
 >>>>>Jutta >>>>< >>>>There are two ways to boot a satellite, DECnet or LANCP.N >>>>The MAC address of the satellite is used to figure out what SYS$SYSROOT is: >>>>used to boot from. The MAC address is either in LANCP:. >>>>Have a look at the output of this command: >>>> >>>>$ mc lancp sho client *  >>>>7 >>>>or in a DECnet database, for phase IV that would be  >>>>! >>>>$ mc ncp list known node char    ------------------------------  % Date: Tue, 25 May 2004 22:29:43 +0200  From:  neale.hunt@hispeed.ch Subject: Re: OpenVMs Cluster) Message-ID: <c90abj$cs7$1@newshispeed.ch>   	 Hi again,   0 additional info from the Cluster doucumentation:   Satellites LAN hardware address E Address has the form xx-xx-xx-xx-xx-xx. You must include the hyphens   when you/ specify a hardware address. Proceed as follows: L  On Alpha systems, enter the following command at the satellites console:  >>> SHOW NETWORK 3 Note that you can also use the SHOW CONFIG command.   F You can modify the address by running @sys$manager:cluster_config and < select option "3 CHANGE a cluster members characteristics.">   Then select option "9 Change <node> satellites Ethernet or  FDDI"hardware address.    < enter your nodename an dthe ethernet address as shown below.  * What is the nodes DECnet node name? ARIELG What is the new hardware address [XX-XX-XX-XX-XX-XX]? 08-00-3B-05-37-78  Updating network database...7 The configuration procedure has completed successfully.     * That hopefully will help with the booting.   For reference:  U http://h71000.www7.hp.com/doc/731FINAL/DOCUMENTATION/PDF/OVMS_731_CLUSTER_SYSTEMS.PDF   + principles are same for your version of VMS   H This is VMS 7.3-1 but Example 88 Sample Interactive CLUSTER_CONFIG.COM H Session to Change a Satellites Hardware Address should explain all you  need.   G Long time since I did booting over LAN, so maybe the flags will be 0,0  4 the system root is supplied by the network database.  0 section  9.4.1 Booting from a Single LAN Adapter   Hope this get's you further ...   
   -- Neale   __ Neale   jutta wrote:   > Hallo Neale, > ' > the os-version is : OpenVMS V.6.2.1H3  >  >  >> boot -flags 11,20000 9 >>    or	boot -flags 11,20001 (for a conversational boot)  > = > It is the same: I got the message:  .... bootstrap failure. 5 > On the other client: boot_osflags 0,0 and it works.  >  > D >>As regards firmware version, depends on the version of VMS, later G >>versions do need a minimum level of firmware.  It may be possible to  < >>email you a "CD image" if you are able to burn it onto CD. > $ > I'm able to burn something onto CD >  >  > Best of luck >         Jutta  >  > O >  neale.hunt@hispeed.ch wrote in message news:<c8tgl6$ili$1@newshispeed.ch>...  > K >>The personal workstation should not present a problem, I had one running  / >>VMS prior to swapping to an Alphastation 500.  >>D >>As regards firmware version, depends on the version of VMS, later G >>versions do need a minimum level of firmware.  It may be possible to  < >>email you a "CD image" if you are able to burn it onto CD. >>2 >>use "show sys /noproc" to determine the version. >> >>Part of the problem will be  >> >>  "boot_osflags 0,0",  >> >>  the hint here is >>1 >>Load Assist Parameter    = POALF2$DKA0:<SYS11.>  >>. >>So the root you need to boot is "11" not "0" >> >>so set boot_osflags 11,0 >>6 >>to see what is going on in detail try the following: >> >>	>  H >>You get a blow by blow account of the boot, but I'm not sure what you ( >>will see if you get bootstrap failure. >> >>Best of luck >>
 >>-- Neale >> >>	VMS System Specialist >> >>jutta wrote: >> >>>Thanks for the answer.  >>>  >>>I Think we have DECnet - >>>$ mc ncp list known node characteristics :  >>>   >>>Remote node =   2.32 (POALF4)/ >>>Hardware address         = 00-00-F8-75-6C-7F % >>>Load file                = APB.EXE 5 >>>Load Assist Agent        = SYS$SHARE:NISCS_LAA.EXE 2 >>>Load Assist Parameter    = POALF2$DKA0:<SYS11.> >>>   >>>Remote node =   2.33 (POALF5)/ >>>Hardware address         = 00-00-F8-21-E3-F4 % >>>Load file                = APB.EXE 5 >>>Load Assist Agent        = SYS$SHARE:NISCS_LAA.EXE 2 >>>Load Assist Parameter    = POALF2$DKA0:<SYS12.> >>>  >>>poalf4 is the new node. >>>  >>>$ mc lancp sho client *H >>>%LANCP-E-NORSPACP, No response from LANACP, LANACP process apparently >>>not running- >>>%LANCP-E-CMDERROR, Error executing command  >>> I >>>The new Client is a digital personal workstation 433au . Perhaps it is & >>>not the right hardware for OpenVMS? >>>  >>>Jutta >>> a >>>"Hans Vlems" <hvlems.dotweg@zonnet.nl> wrote in message news:<2h1q9oF853dlU1@uni-berlin.de>...  >>>  >>> 5 >>>>"jutta" <jutta.reichel@gmx.de> schreef in bericht : >>>>news:ec7e473.0405190622.77145268@posting.google.com... >>>> >>>>9 >>>>>We have a OpenVMS (Alpha) Cluster with 4 Satellites. H >>>>>One of them is defect. We took another Client with Operating SystemA >>>>>DEC UNIX. We changed the Hardware Address on the Server with  >>>>>Cluster_config.* >>>>>The boot parameter on the new Client: >>>>>  >>>>>  >>>>>>>>os_type OpenVMS  >>>>>>>>ew0_protocols MOP  >>>>>>>>boot_dev ewa0.0.0.14.0 >>>>>>>>boot_osflags 0,0 >>>>>>>>ewa0_inet_init  bootp   >>>>>>>>pal VMS PALcode V1.20-14 >>>>>>>>version V6-9-7 >>>>> : >>>>>We try to boot the new Client and we got the message: >>>>>  >>>>> 	 >>>>>>>>b  >>>>> ! >>>>>boot ewa0.0.0.3.0 -flags 0,0  >>>>>Trying MOP boot >>>>>.... bootstrap failure  >>>>>  >>>>>  >>>>>one of the other clients: >>>>>   >>>>>>>>pal  VMS PALcode V5.65.2 >>>>>>>>version V6.9-4 >>>>> 5 >>>>>Do we need to do somethings more on the server ? # >>>>>Is the firmware the wrong one?  >>>>>  >>>>>Who can help us?  >>>>> 
 >>>>>Jutta
 >>>>>Jutta >>>>< >>>>There are two ways to boot a satellite, DECnet or LANCP.N >>>>The MAC address of the satellite is used to figure out what SYS$SYSROOT is: >>>>used to boot from. The MAC address is either in LANCP:. >>>>Have a look at the output of this command: >>>> >>>>$ mc lancp sho client *  >>>>7 >>>>or in a DECnet database, for phase IV that would be  >>>>! >>>>$ mc ncp list known node char    ------------------------------  # Date: Tue, 25 May 2004 18:43:55 GMT 1 From: Michael Austin <maustin@firstdbasource.com> = Subject: Re: Previous Post - Upgrading Cluster Communications 2 Message-ID: <40B393E8.D7BC364B@firstdbasource.com>   Carl Karcher wrote:   L > In a previous article, mcaccavone@manfinancial.com (Mark Caccavone) wrote: > G > ->Therefore the cluster will always exist when changing communication G > ->channels so disks will not drop out of the Shadow Set when changing G > ->from FDDI to GIGABIT. I take it that to force whether or not to use H > ->FDDI or GIGABIT I just set the PRIORITY on the LAN DEVICE via SCACP. > H > I'd test that during a quiet time before assuming it's ok. Should someD > sort of packet loss issue be present (auto-negotiation failing forJ > example) you won't necessarily notice it until ALL SCS traffic goes overI > Gig-E. You'd want to test booting too - you may need to set environment 2 > variables for the line speed/duplex of the link. >  > --I > -- Carl Karcher, Waisman Computing Services, Waisman Center, UW-Madison 6 > --               karcher.nomorespxm@waisman.wisc.edu  L I concur . a very good rule of thumb -- especially with VMS and UNIX - NEVERA RELY ON NETWORK SWITCH AUTO-NEGOTIATE TO WORK THE WAY YOU EXPECT.    Michael Austin.    ------------------------------    Date: 25 May 2004 12:18:30 -07001 From: keithparris_NOSPAM@yahoo.com (Keith Parris) * Subject: Re: Reboot forces Shadowset Merge= Message-ID: <cf15391e.0405251118.7eb55075@posting.google.com>   ~ "David J. Dachtera" <djesys.nospam@NeOaSrPtAhMlNiOnWk.net> wrote in message news:<40A9713C.FDEE928E@NeOaSrPtAhMlNiOnWk.net>...> > does not mini-copy depend on the write bitmaps which are, of  > course, destroyed upon reboot?  B At the core of the suggestion was that if you reduce the shadowsetD down to 1 member during the shutdown, then a Merge will never occur.  D Given that, the next issue is to minimize the impact of this change.C Normally a Full Copy would be needed to bring the other member back C in, which can in itself be quite time-consuming. By dismounting the F member and creating a write bitmap (which must of necessity be createdF on the node which will stay up, not the node which will be shut down),F then the work required to bring the 2nd shadowset member back into theD shadowset is minimized, as you only have to copy the areas which theF surviving node changes during the period of the shutdown, which should* be minimal. This is a Mini-Copy operation.  E Acceptability of this solution depends, of course, on whether you can F take the risk of having a non-redundant 1-member shadowset for a short period of time.   ? I prefer a solution which allows the files to be cleanly closed  before/during shutdown.   ( > (The o.p. was asking about rebooting a> > node that might be the MSCP server for a shadow-set member.)  B I didn't get that impression from the o.p.  I might have if he had8 talked about a Copy, but he was concerned about a Merge.   ------------------------------  % Date: Tue, 25 May 2004 12:49:36 -0700 # From: "Tom Linden" <tom@kednos.com> * Subject: RE: Reboot forces Shadowset Merge9 Message-ID: <NDEMLKKEBOIFBMJLCECIKEOCDEAA.tom@kednos.com>      -----Original Message-----:   From: Keith Parris [mailto:keithparris_NOSPAM@yahoo.com]&   Sent: Tuesday, May 25, 2004 12:19 PM   To: Info-VAX@Mvb.Saic.Com ,   Subject: Re: Reboot forces Shadowset Merge    B   "David J. Dachtera" <djesys.nospam@NeOaSrPtAhMlNiOnWk.net> wrote?   in message news:<40A9713C.FDEE928E@NeOaSrPtAhMlNiOnWk.net>... @   > does not mini-copy depend on the write bitmaps which are, of"   > course, destroyed upon reboot?  D   At the core of the suggestion was that if you reduce the shadowsetF   down to 1 member during the shutdown, then a Merge will never occur.  F   Given that, the next issue is to minimize the impact of this change.E   Normally a Full Copy would be needed to bring the other member back E   in, which can in itself be quite time-consuming. By dismounting the H   member and creating a write bitmap (which must of necessity be createdH   on the node which will stay up, not the node which will be shut down),H   then the work required to bring the 2nd shadowset member back into theF   shadowset is minimized, as you only have to copy the areas which theH   surviving node changes during the period of the shutdown, which should,   be minimal. This is a Mini-Copy operation.  G   Acceptability of this solution depends, of course, on whether you can H   take the risk of having a non-redundant 1-member shadowset for a short   period of time.   A   I prefer a solution which allows the files to be cleanly closed    before/during shutdown.   *   > (The o.p. was asking about rebooting a@   > node that might be the MSCP server for a shadow-set member.)  D   I didn't get that impression from the o.p.  I might have if he had:   talked about a Copy, but he was concerned about a Merge.  G That is correct Keith, this was just a node in the cluster that was not G serving the shadow sets.  QMAN$MASTER.DAT is kept open by the node that E is being shutdown, even though the queue manager runs on another node  Here is the picture   +            ____________LAN_________________ +           |        |        |             | .        Node A   Node B   Node C  ...    Node K           |        |           |  SCSI  |       --------------------       |        |         |     SHDW X   SHDW Y    SHDW Z   J QUEUE MANAGER runs on Node A with Failover to B QMAN$MASTER.DAT resides on SHDW X  J Rebooting Node K cause the copy, unless I close the open file, which means shutting down the Queue manager.              --- (   Incoming mail is certified Virus Free.<   Checked by AVG anti-virus system (http://www.grisoft.com).A   Version: 6.0.680 / Virus Database: 442 - Release Date: 5/9/2004    --- & Outgoing mail is certified Virus Free.: Checked by AVG anti-virus system (http://www.grisoft.com).? Version: 6.0.680 / Virus Database: 442 - Release Date: 5/9/2004    ------------------------------    Date: 25 May 2004 22:31:31 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen) * Subject: Re: Reboot forces Shadowset Merge3 Message-ID: <YQrBNLlxXGcZ@eisner.encompasserve.org>   Y In article <40B3F000.32CB5A6B@comcast.net>, David J Dachtera <djesys@comcast.net> writes:  > Tom Linden wrote:   M >> Rebooting Node K cause the copy, unless I close the open file, which means  >> shutting  >> down the Queue manager. > 1 > ...or moving it to another node in the cluster.   D No, in the situation Tom is discussing, the queue manager is runningH on some other node.  But the Job Controller on _all_ nodes has a channelD open to QMAN$MASTER.DAT.  I talked with a real expert at last week'sF VMS Symposium and the consensus was to try shooting the Job Controller@ as part of the site specific shutdown.  Job Controller creates a8 successor, but that one would not have the channel open.   ------------------------------  % Date: Tue, 25 May 2004 12:21:36 -0700 + From: "Barry Treahy, Jr." <Treahy@MMaz.com>  Subject: Re: SEARCH question' Message-ID: <40B39CC0.8090604@MMaz.com>    Tom Linden wrote:    >  -----Original Message----- 3 >  From: Barry Treahy, Jr. [mailto:Treahy@MMaz.com] ' >  Sent: Tuesday, May 25, 2004 10:09 AM  >  To: Info-VAX@Mvb.Saic.Com >  Subject: Re: SEARCH question  >    >    >  Tom Linden wrote: >   $ >  >In my login I have the followingH >  >$ DEFINE/system/nolog HERMES$DISKS DISK$OPENVMS071:,DISK$HERMES_073:E >  >$ DEFINE/system/nolog NORNS$DISKS  DISK$AXPSYS2:,DISK$NORNS_0731: G >  >$ DEFINE/system/nolog ODIN$DISKS   DISK$ALPHA_0712:,DISK$ODIN_0731: K >  >$ DEFINE/system/nolog FREJA$DISKS  DISK$AXPVMS073:,DISK$USR:,DISK$FPLI: J >  >$ DEFINE/system/nolog SHADOW$DISKS DISK$COMMON:,DISK$PLI:,DISK$DECPLI:# >  >$ DEFINE/system/nolog ALL$DISKS @ >  >HERMES$DISKS,NORNS$DISKS,ODIN$DISKS,FREJA$DISKS,SHADOW$DISKS8 >  >$ LOCATE:=="SEARCH ALL$DISKS:[000000]DIRECTORY.LIS " >  > >  >so if I  >  >9 >  >$ LOCATE <name> 	it only searches on the HERMES$DISKS  >  >
 >  >but if >  >5 >  >$  dir  ALL$DISKS:[000000]DIRECTORY.LIS/version=1  >  > >  >it lists them all. >  >9 >  >why?  How do I get the search to look at all of them?  >  >   >  >G >  I'm speculating, but I suspect your problem is with the construct -  E >  specifically, the directory and filename are not specified at the  I >  'beginning but rather at the tail of the total search search so while  I >  SEARCH is running, it is prefixing your current default location with  H >  the disk drive, searching, not finding anything, and moving down the / >  list until the last device which has had the  >    >  [000000]DIRECTORY.LIS >    >   K >  suffixed. Now why HERMES is showing up rather than DECPLI, well I don't  
 >  know... >   2 >  Try this, on your LOCATE symbol, change it to : >   3 >  LOCATE:==SEARCH [000000]DIRECTORY.LIS,ALL$DISKS:  >    >  and see if that works...  > H >What that did is to search sys$sysdevice:[000000]directory.lis followed >by HERMES drives. >    >    > , Havne't a clue as it works just fine on 7.2:    V4100$ cre dka501:[000000]aa.com treahy  Exit * V4100$ def/sys aaa dka500:,dka501:,dka503:* V4100$ def/sys bbb dka500:,dka501:,dka503:* V4100$ def/sys ccc dka500:,dka501:,dka503: V4100$ reca sear V4100$ def/sys ddd aaa,bbb,ccc V4100$ reca sear$ V4100$ sear ddd:[000000]*.com treahy    ****************************** DKA501:[000000]AA.COM;1     treahy    ****************************** DKA501:[000000]AA.COM;1     treahy    ****************************** DKA501:[000000]AA.COM;1     treahy V4100$$ V4100$ eee:=search ddd:[000000]*.com V4100$ eee treahy     ****************************** DKA501:[000000]AA.COM;1     treahy    ****************************** DKA501:[000000]AA.COM;1     treahy    ****************************** DKA501:[000000]AA.COM;1     treahy V4100$   --    > Barry Treahy, Jr                       E-mail: Treahy@MMaz.com> Midwest Microwave                          Phone: 480/314-1320> Vice President & CIO                         FAX: 480/661-7028                            ------------------------------    Date: 25 May 2004 15:47:32 -0600; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler)  Subject: Re: SEARCH question3 Message-ID: <mBA39v2RUjZs@eisner.encompasserve.org>   _ In article <NDEMLKKEBOIFBMJLCECIKENJDEAA.tom@kednos.com>, "Tom Linden" <tom@kednos.com> writes:   A IIRC, the following will do it, assuming there's no more than one F version of the file on each disk, or that you're OK with searching all versions on each disk.  6 $ LOCATE:=="SEARCH ALL$DISKS:[000000]DIRECTORY.LIS;* "   ------------------------------  % Date: Tue, 25 May 2004 14:09:28 -0700 # From: "Tom Linden" <tom@kednos.com>  Subject: RE: SEARCH question9 Message-ID: <NDEMLKKEBOIFBMJLCECIKEOFDEAA.tom@kednos.com>   > That does work, but I had to purge first.  But why do you need0 to append the ;*  I don't see the logic of that?     -----Original Message-----D   From: Bob Koehler [mailto:koehler@eisner.nospam.encompasserve.org]%   Sent: Tuesday, May 25, 2004 2:48 PM    To: Info-VAX@Mvb.Saic.Com    Subject: Re: SEARCH question      A   In article <NDEMLKKEBOIFBMJLCECIKENJDEAA.tom@kednos.com>, "Tom  "   Linden" <tom@kednos.com> writes:   C   IIRC, the following will do it, assuming there's no more than one H   version of the file on each disk, or that you're OK with searching all   versions on each disk.   8   $ LOCATE:=="SEARCH ALL$DISKS:[000000]DIRECTORY.LIS;* "      --- (   Incoming mail is certified Virus Free.<   Checked by AVG anti-virus system (http://www.grisoft.com).A   Version: 6.0.680 / Virus Database: 442 - Release Date: 5/9/2004     --- & Outgoing mail is certified Virus Free.: Checked by AVG anti-virus system (http://www.grisoft.com).? Version: 6.0.680 / Virus Database: 442 - Release Date: 5/9/2004    ------------------------------  % Date: Tue, 25 May 2004 15:28:44 -0400 2 From: "Jonathan Boswell" <jsb.NOSP@M.cdrh.fda.gov>? Subject: TCPIP Services for OpenVMS V5.4 ECO1 anti spam feature 4 Message-ID: <O7Nsc.307$Ny6.1031@mencken.net.nih.gov>  L I am trying to configure TCPIP Services SMTP.CONFIG file to reject all email1 from 205.158.62.*.   So I entered a line like so:    Bad-Clients: 205.158.62.0/24  J and then restarted TCPIP services.  Spam still comes zinging right through@ from those addresses.  Any ideas on what I could be doing wrong?   ------------------------------  # Date: Tue, 25 May 2004 20:39:03 GMT - From: JF Mezei <jfmezei.spamnot@teksavvy.com> C Subject: Re: TCPIP Services for OpenVMS V5.4 ECO1 anti spam feature @ Message-ID: <a94539516017d19bf59d3dcea61cacbf@news.teranews.com>   Jonathan Boswell wrote:  > N > I am trying to configure TCPIP Services SMTP.CONFIG file to reject all email3 > from 205.158.62.*.   So I entered a line like so:  >  > Bad-Clients: 205.158.62.0/24  I Do you have a Good-Clients: definition which may encompass the bad client N specification ? The doc states that the one definition which is closest to the* IP address of the remote SMTP server wins.  M So if you had 205.158.62.128/23 in the good clients, it would allow .129 as a & good client, but .127 as a bad client.  H Also, you need to look at opcom or accounting to see if the receiver hasM emitted any messages with regards to that IP address when a message comes in.    ------------------------------   End of INFO-VAX 2004.290 ************************