1 INFO-VAX	Sun, 22 May 2005	Volume 2005 : Issue 283       Contents:# Re: AUTOGEN and page and swap files # Re: AUTOGEN and page and swap files * Re: Cluster question - which interconnect? Re: FMS Runtime Installation0 Re: How to filter spam based on message content?0 Re: How to filter spam based on message content?0 Re: How to filter spam based on message content?P http://www.tbn.org/films/videos/To_Hell_And_Back.ram << GREAT VIDEO! Just click P Re: http://www.tbn.org/films/videos/To_Hell_And_Back.ram << GREAT VIDEO! Just cl LAT problems. Re: Networking problem concerning a DEC TS 90L. Re: Networking problem concerning a DEC TS 90LD Re: Newbie Questio.. Getting a Virtual address space full and globalP Newbie Questio.. Getting a Virtual address space full and global page table fullP Re: Newbie Questio.. Getting a Virtual address space full and global page table $ Re: Newbie with command file problem Re: upgrade 7.3-1 --> 7.3-2  Re: upgrade 7.3-1 --> 7.3-2  Re: upgrade 7.3-1 --> 7.3-2  Re: upgrade 7.3-1 --> 7.3-2  Re: upgrade 7.3-1 --> 7.3-2  Re: upgrade 7.3-1 --> 7.3-2 ' Re: VAXstation 3100 free to a good home ' Re: VAXstation 3100 free to a good home ' Re: VAXstation 3100 free to a good home ' Re: VAXstation 3100 free to a good home ' Re: VAXstation 3100 free to a good home ' Re: VAXstation 3100 free to a good home   F ----------------------------------------------------------------------  + Date: Sat, 21 May 2005 18:35:26 +0000 (UTC) P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply), Subject: Re: AUTOGEN and page and swap files$ Message-ID: <d6nv1e$imn$1@online.de>  C In article <1116693153.219505.236160@g47g2000cwa.googlegroups.com>, ' "AEF" <spamsink2001@yahoo.com> writes:    G > > Yes, but normally if one modifies something in MODPARAMS.DAT, which  > isG > > also in PARAMS.DAT, say, EXPECTED_VOTES, then in future versions of - > > PARAMS.DAT only the new value will exist.  > G > But if you go back to the old version of MODPARAMS.DAT you should get E > back the old version of PARAMS.DAT, no? PARAMS.DAT is the output of I > GETDATA. Does it not depend only on the inputs? And these inputs do not F > include PARAMS.DAT. This reminds me of the effects of the hysteresisG > property of ferromagnetic materials. In such effects the value of one G > variable depends upon not only the current value of another variable, G > but also upon the history of that other variable. I don't think there I > are any hysteresis effects in which PARAMS.DAT depends upon the history I > of MODPARAMS.DAT. If there are, can someone please explain how? Thanks.   I I'm pretty sure that my problem won't be solved by any number of AUTOGEN  C repeats.  The file names are sort of like other parameters in that  G AUTOGEN works with them, but on the other hand they are not parameters   for SYSGEN or SYSMAN.    ------------------------------  # Date: Sun, 22 May 2005 01:02:25 GMT # From: Beach Runner <bob@nospam.com> , Subject: Re: AUTOGEN and page and swap files; Message-ID: <BSQje.33002$VH2.16969@tornado.tampabay.rr.com>   B Excuse the top posting.    In my real life I talk to customers and; I always recommend setting pagefile to 0.  You can look in  E agen$feedback.dat and see pagefile peak usage.  Set it manually.  If  G autogen thinks you need a larger page file, it will try and create it,  G but if your disk is badly fragmented, instead it will create a tiny one  and you are really in trouble.  D After the initial setting of autogen create page files, primary and  secondary manually.   0 $show mem/file will show current pagefile usage.    / Phillip Helbig---remove CLOTHES to reply wrote:   K > Note: This post is rather long, and there are several questions, even at  G > the bottom, but since they are all related, I think one long post is  ! > better than several short ones.  > G > I am really confused about AUTOGEN's handling of page and swap files.  > H > I know that AUTOGEN can be told to leave them alone completely, but I J > want to understand what is going on.  Also, the information provided by D > AUTOGEN's calculations can be interesting.  (Also, in my case, it J > doesn't modify them anyway, at least not with my current configuration.) > F > Sidebar question: Is there anyway to have AUTOGEN calculate and set F > parameters but NOT change the page and swap files?  TESTFILES stops G > before the parameters are set.  If I tell AUTOGEN not to bother with  E > page and swap files at all, then I can't even see the results with   > TESTFILES. > J > Here's my setup: I have primary page and swap files on the system disk, J > and secondary on another disk.  In MODPARAMS.DAT, I refer to the former K > by {PAGE|SWAP}FILE1 and the latter by {PAGE|SWAP}FILE2.  The problem is,  B > AUTOGEN is getting confused as to which is which.  Consider the 1 > following typical output in AGEN$PARAMS.REPORT:  > 6 > AUTOGEN Parameter Calculation Report on node: GLADIA= >   This information was generated at 19-MAY-2005 10:53:11.50 M >   AUTOGEN was run from SAVPARAMS to SETPARAMS - default execution specified  > ! > Processing Parameter Data files ! > -------------------------------  > 5 > Including parameters from: SYS$SYSTEM:MODPARAMS.DAT  > ; > The following problems were detected within MODPARAMS.DAT 3 >    These problems should be reviewed immediately.  > ; > ** WARNING ** - Duplicate value for PAGEFILE1_NAME found. I > 	This overrides preceding requirements for this parameter in PARAMS.DAT L > 	Please review the parameter setting and if possible use MIN, MAX, or ADD.9 > ****	Ignoring previously specified PAGEFILE1_NAME value  > ; > ** WARNING ** - Duplicate value for PAGEFILE2_NAME found. I > 	This overrides preceding requirements for this parameter in PARAMS.DAT L > 	Please review the parameter setting and if possible use MIN, MAX, or ADD.9 > ****	Ignoring previously specified PAGEFILE2_NAME value  > ; > ** WARNING ** - Duplicate value for SWAPFILE2_NAME found. I > 	This overrides preceding requirements for this parameter in PARAMS.DAT L > 	Please review the parameter setting and if possible use MIN, MAX, or ADD.9 > ****	Ignoring previously specified SWAPFILE2_NAME value  > / >  Calculations for page, swap, and dump files. / >  --------------------------------------------  >  >     Page file calculations:  > S >         PAGEFILE1_SIZE information (for DISK$SWAPPAGE_3:[GLADIA]PAGEFILE2.SYS;1):  > 	Feedback information./ > 	   Old value was 400000, New value is 200000 , > 	   Maximum observed usage (blocks): 37120D > 	Override Information - parameter calculation has been overridden.? > 	   The calculated value was 55700.  The new value is 200000. ; > 	   PAGEFILE1_SIZE is not allowed to be less than 200000. ; > 	   PAGEFILE1_SIZE will be modified to hold 200000 blocks  > C >         PAGEFILE2_SIZE information (for SYS$SYSTEM:PAGEFILE.SYS):  > 	Feedback information./ > 	   Old value was 200700, New value is 400000 , > 	   Maximum observed usage (blocks): 36864D > 	Override Information - parameter calculation has been overridden.? > 	   The calculated value was 55300.  The new value is 400000. D > 	   PAGEFILE2_SIZE has been set to the hard-coded value of 400000.; > 	   PAGEFILE2_SIZE will be modified to hold 400000 blocks  > B > 	** NOTE ** Unable to change the size of PAGEFILE1 since current> > 	   disk block utilization is 95%.  However, if enough spaceM > 	   were available, DISK$SWAPPAGE_3:[GLADIA]PAGEFILE2.SYS;1, would contain  F > 	   200000 blocks.  Instead, PAGEFILE1 will remain at 400000 blocks. >  >     Swap file calculations:  > C >         SWAPFILE1_SIZE information (for SYS$SYSTEM:SWAPFILE.SYS):  > 	Feedback information.- > 	   Old value was 50000, New value is 50000 , > 	   Maximum observed usage (blocks): 21504D > 	Override Information - parameter calculation has been overridden.> > 	   The calculated value was 32300.  The new value is 50000.: > 	   SWAPFILE1_SIZE is not allowed to be less than 50000.A > 	   SWAPFILE1 will not be modified. The file size is within 10%  > S >         SWAPFILE2_SIZE information (for DISK$SWAPPAGE_3:[GLADIA]SWAPFILE2.SYS;1):  > 	Feedback information./ > 	   Old value was 100000, New value is 100000 ( > 	   Maximum observed usage (blocks): 0D > 	Override Information - parameter calculation has been overridden.> > 	   The calculated value was 6400.  The new value is 100000.D > 	   SWAPFILE2_SIZE has been set to the hard-coded value of 100000.A > 	   SWAPFILE2 will not be modified. The file size is within 10%  > K > Note that it gives 2 warnings about page files, corresponding to the two  K > wrong file names further down.  It gives 1 warning about swap files, but  " > actually both names are correct. > F > It says there is a conflict with PARAMS.DAT.  However, no number of G > repeats of AUTOGEN will solve the problem.  It seems the only way to  G > solve the problem is to edit PARAMS.DAT by hand, although ONE IS NOT  # > SUPPOSED TO EVER NEED TO DO THIS.  > K > Presumably, even if I screw up I can just restore the current version of  J > PARAMS.DAT, in which case I won't be any worse off than I am now, right? > J > I think the problem was probably caused by me using the wrong values in I > MODPARAMS.DAT at some stage.  However, I would have hoped that AUTOGEN  < > could correct this.  Do I have to edit PARAMS.DAT by hand? > > > MAIL>  spa sea disk$alphasys_3:[sys0.sysexe]params.dat _name, > SWAPFILE1_NAME = "SYS$SYSTEM:SWAPFILE.SYS"< > SWAPFILE2_NAME = "DISK$SWAPPAGE_3:[GLADIA]SWAPFILE2.SYS;1"< > PAGEFILE1_NAME = "DISK$SWAPPAGE_3:[GLADIA]PAGEFILE2.SYS;1", > PAGEFILE2_NAME = "SYS$SYSTEM:PAGEFILE.SYS"@ > PAGEFILE1_NAME="SYS$SYSTEM:PAGEFILE.SYS" ! WHY DO I NEED THIS?8 > PAGEFILE2_NAME="DISK$SWAPPAGE_3:[GLADIA]PAGEFILE2.SYS"H > SWAPFILE1_NAME="SYS$SYSTEM:SWAPFILE.SYS" ! MAYBE NOT NEEDED; SEE ABOVE8 > SWAPFILE2_NAME="DISK$SWAPPAGE_3:[GLADIA]SWAPFILE2.SYS" > / > Here's the relevant portion of MODPARAMS.DAT:  > @ > PAGEFILE1_NAME="SYS$SYSTEM:PAGEFILE.SYS" ! why do I need this? > MIN_PAGEFILE1_SIZE=200000 8 > PAGEFILE2_NAME="DISK$SWAPPAGE_3:[GLADIA]PAGEFILE2.SYS" > PAGEFILE2_SIZE=400000 H > SWAPFILE1_NAME="SYS$SYSTEM:SWAPFILE.SYS" ! maybe not needed; see above > MIN_SWAPFILE1_SIZE=500008 > SWAPFILE2_NAME="DISK$SWAPPAGE_3:[GLADIA]SWAPFILE2.SYS" > SWAPFILE2_SIZE=100000  > J > During an upgrade, I booted the node without the disk for the secondary G > files.  After that, the AUTOGEN reports looked OK, but the old error  K > returned after I booted it with the secondary files.  Here's what one of  J > these good reports looks like.  I don't understand why it gets confused 7 > with the names if the secondary files are accessible.  > 6 > AUTOGEN Parameter Calculation Report on node: GLADIA= >   This information was generated at 19-MAY-2005 02:37:44.22 > >   AUTOGEN was run from SAVPARAMS to SETPARAMS using FEEDBACK > / >  Calculations for page, swap, and dump files. / >  --------------------------------------------  >  >     Page file calculations:  > C >         PAGEFILE1_SIZE information (for SYS$SYSTEM:PAGEFILE.SYS):  > 	Feedback information./ > 	   Old value was 200700, New value is 200700 ( > 	   Maximum observed usage (blocks): 0A > 	   PAGEFILE1 will not be modified. The file size is within 10%  > Q >         PAGEFILE2_SIZE information (for DISK$SWAPPAGE_3:[GLADIA]PAGEFILE2.SYS):  > 	Feedback information.* > 	   Old value was 0, New value is 400000& > 	   No usage recorded for this file.D > 	Override Information - parameter calculation has been overridden.@ > 	   The calculated value was 200700.  The new value is 400000.D > 	   PAGEFILE2_SIZE has been set to the hard-coded value of 400000. > Q >         PAGEFILE2_SIZE information (for DISK$SWAPPAGE_3:[GLADIA]PAGEFILE2.SYS): I > 	  PAGEFILE2 will not be modified: access problems on DISK$SWAPPAGE_3:. A > 	    (Please check file DISK$SWAPPAGE_3:[GLADIA]PAGEFILE2.SYS.)  >  >     Swap file calculations:  > C >         SWAPFILE1_SIZE information (for SYS$SYSTEM:SWAPFILE.SYS):  > 	Feedback information.- > 	   Old value was 50000, New value is 50000 ( > 	   Maximum observed usage (blocks): 0D > 	Override Information - parameter calculation has been overridden.= > 	   The calculated value was 6400.  The new value is 50000. : > 	   SWAPFILE1_SIZE is not allowed to be less than 50000.A > 	   SWAPFILE1 will not be modified. The file size is within 10%  > Q >         SWAPFILE2_SIZE information (for DISK$SWAPPAGE_3:[GLADIA]SWAPFILE2.SYS):  > 	Feedback information.* > 	   Old value was 0, New value is 100000& > 	   No usage recorded for this file.D > 	Override Information - parameter calculation has been overridden.> > 	   The calculated value was 6400.  The new value is 100000.D > 	   SWAPFILE2_SIZE has been set to the hard-coded value of 100000. > Q >         SWAPFILE2_SIZE information (for DISK$SWAPPAGE_3:[GLADIA]SWAPFILE2.SYS): I > 	  SWAPFILE2 will not be modified: access problems on DISK$SWAPPAGE_3:. A > 	    (Please check file DISK$SWAPPAGE_3:[GLADIA]SWAPFILE2.SYS.)  > H > Another question: Can I somehow tell the system to preferentially use F > the secondary page and swap files, and only use the primary ones if H > needed?  The idea behind this is that the primary page and swap files H > are on a faster disk (a solid-state--disk shadow set) and I also have G > room for much larger files there.  I would want to keep those on the  K > system disk primarily for use when the secondary files are not available  / > (and IIRC they are required to exist anyway).  > H > (At the moment, this node is a DEC 3000/300 LX with 48 MB RAM.  It hadD > been running 7.3-1 for about 18 months, but a couple of days ago II > upgraded it to 7.3-2.  7.3-2 officially requires 64 MB (though it's not I > 100% clear to me that this is required for running 7.3-2, as opposed to I > installing it; I actually did the upgrade on a DEC 3000/600 with 192 MB C > RAM which otherwise has the same hardware configuration (ethernet F > controller etc) so one can just swap the disks with no configurationH > changes (though I immediately run AUTOGEN so that it realises how muchE > memory it really has)).  Performance seems fine, but the startup is E > slower than before.  I realise that 48 MB is starving (perhaps even G > 7.3-1 officially required more; the 300 LX appeared when VMS 6.x was  C > current (it is a first-generation ALPHA), so presumably then the  H > supported minimum was not more than 48 MB), but the solid-state disks G > for the swap/page shadow set probably helps things.  (I realise that  C > more memory would be easier, even in this slow machine, but as a  K > hobbyist I have to make do with what I have; I put enough money into the  F > electricity bill so I only buy hardware when absolutely necessary.)) >    ------------------------------    Date: 21 May 2005 15:02:44 -07001 From: "Bart.Zorn@xs4all.nl" <Bart.Zorn@xs4all.nl> 3 Subject: Re: Cluster question - which interconnect? C Message-ID: <1116712964.801399.105690@g44g2000cwa.googlegroups.com>   A An other tool to get info on your cluster interconnects is SCACP.   E MCR SCACP SHOW CHANNEL gives you quite a lot of interesting info. And  of course, there is HELP too!    Regards,  	 Bart Zorn    ------------------------------  % Date: Sat, 21 May 2005 17:30:54 -0400  From: norm.raphael@metso.com% Subject: Re: FMS Runtime Installation Q Message-ID: <OFCC1DD5F8.1D73405A-ON85257008.0075E4FD-85257008.00768EDD@metso.com>   + This is a multipart message in MIME format. " --=_alternative 00768ED785257008_=, Content-Type: text/plain; charset="US-ASCII"  J David J Dachtera <djesys.nospam@comcast.net> wrote on 05/20/2005 10:43:20  PM:    > John Vottero wrote:  > > - > > <norm.raphael@metso.com> wrote in message  > > K news:OF5A7D1D55.32520B91-ON85257007.00538088-85257007.00536481@metso.com...  > > >  > > >  > > >  > > > / > > > By the way - Score:  VMSINSTAL 1, PCSI 0.  > > > J > > > If this had been a PCSI kit, fixing it would have been doable, but a > > > narrower group > > > would have known how.  > > >  > > J > > I'm no PCSI expert but, I don't think you could build a PCSI kit that  tried I > > to install a file that wasn't in the kit so maybe the score should be  > > VMSINSTAL 0, PCSI 1? >    Is that a fact?  If it is, the score would be   VMSINTALL      1 Kit Developer  DNF PCSI           Still Champion    > I'd say more like: > 
 > PCSI      1  > Kit Developer    0 >  > --   > David J Dachtera > dba DJE Systems  > http://www.djesys.com/ > + > Unofficial OpenVMS Hobbyist Support Page: $ > http://www.djesys.com/vms/support/ > * > Unofficial Affordable OpenVMS Home Page:! > http://www.djesys.com/vms/soho/  > $ > Unofficial OpenVMS-IA32 Home Page:! > http://www.djesys.com/vms/ia32/  >  > Coming soon:( > Unofficial OpenVMS Marketing Home Page  " --=_alternative 00768ED785257008_=+ Content-Type: text/html; charset="US-ASCII"      <br>G <br><font size=2><tt>David J Dachtera &lt;djesys.nospam@comcast.net&gt; $ wrote on 05/20/2005 10:43:20 PM:<br> <br> &gt; John Vottero wrote:<br> &gt; &gt; <br>= &gt; &gt; &lt;norm.raphael@metso.com&gt; wrote in message<br> Y &gt; &gt; news:OF5A7D1D55.32520B91-ON85257007.00538088-85257007.00536481@metso.com...<br>  &gt; &gt; &gt;<br> &gt; &gt; &gt;<br> &gt; &gt; &gt;<br> &gt; &gt; &gt;<br>A &gt; &gt; &gt; By the way - Score: &nbsp;VMSINSTAL 1, PCSI 0.<br>  &gt; &gt; &gt;<br>M &gt; &gt; &gt; If this had been a PCSI kit, fixing it would have been doable, 	 but a<br> ! &gt; &gt; &gt; narrower group<br> ( &gt; &gt; &gt; would have known how.<br> &gt; &gt; &gt;<br> &gt; &gt; <br>F &gt; &gt; I'm no PCSI expert but, I don't think you could build a PCSI kit that tried<br>L &gt; &gt; to install a file that wasn't in the kit so maybe the score should be<br>" &gt; &gt; VMSINSTAL 0, PCSI 1?<br> &gt; </tt></font>  <br>0 <br><font size=2><tt>Is that a fact?</tt></font>= <br><font size=2><tt>If it is, the score would be</tt></font>  <br>@ <br><font size=2><tt>VMSINTALL &nbsp; &nbsp; &nbsp;1</tt></font>8 <br><font size=2><tt>Kit Developer &nbsp;DNF</tt></font>O <br><font size=2><tt>PCSI &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Still Champion<br>  </tt></font>0 <br><font size=2><tt>&gt; I'd say more like:<br>	 &gt; <br> # &gt; PCSI &nbsp; &nbsp; &nbsp;1<br> % &gt; Kit Developer &nbsp; &nbsp;0<br> 	 &gt; <br>  &gt; -- <br> &gt; David J Dachtera<br>  &gt; dba DJE Systems<br> &gt; http://www.djesys.com/<br> 	 &gt; <br> 2 &gt; Unofficial OpenVMS Hobbyist Support Page:<br>+ &gt; http://www.djesys.com/vms/support/<br> 	 &gt; <br> 1 &gt; Unofficial Affordable OpenVMS Home Page:<br> ( &gt; http://www.djesys.com/vms/soho/<br>	 &gt; <br> + &gt; Unofficial OpenVMS-IA32 Home Page:<br> ( &gt; http://www.djesys.com/vms/ia32/<br>	 &gt; <br>  &gt; Coming soon:<br> / &gt; Unofficial OpenVMS Marketing Home Page<br>  </tt></font>$ --=_alternative 00768ED785257008_=--   ------------------------------  % Date: Sat, 21 May 2005 17:47:19 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> 9 Subject: Re: How to filter spam based on message content? , Message-ID: <428FAC60.1E6C5E13@teksavvy.com>   "John E. Malmberg" wrote:   I > If someone knows of a mail server with the ability to do custom content B > checks before the SMTP transaction is over that is available forI > OpenVMS, either commercial or ported OpenSource, it would be useful for   > them to post that information.  F It is called Postfix. It benefits from much community contributions toF keep spam filters and logic up-to-date.  But because the VMS engineersG have not documented the TCPIP$ routines to interface to the SMTP queues E directly, it is pointless to attempt a port of the receiver portion.    F VMS was succesful because of its complete documentation. Unfortunatly,E in the case of SMTP, the lack of the documentation to the proprietary  interfaces is now a hindrance.  C Granted, I know the VMS engineers will respond that this would cost D money and that there is no business case etc etc. They might as wellH respond "well, there is no real business case to compinue to improve VMSB since customers are all running legacy applications and not really! willing to pay for new features".    ------------------------------  % Date: Sat, 21 May 2005 17:25:09 -0500 - From: Hunter Goatley <goathunter@goatley.com> 9 Subject: Re: How to filter spam based on message content? 8 Message-ID: <9xOje.4842$6k7.1149@bignews4.bellsouth.net>   John E. Malmberg wrote:  > K > I am not aware of any product on OpenVMS that will SMTP reject after the  : > initial acceptance of the start of the SMTP transaction.  @ Martin has already mentioned the product that does.  PreciseMailF Anti-Spam Gateway's proxy SMTP server will let you do this.  DependingC on a message's score and the site-configurable thresholds, messages B can be rejected during the SMTP session, preventing them from ever entering your system.   J > It likely will require replacing the basic TCPIP$SMTP_RECEIVER.EXE with  > a full featured mail server.  B PreciseMail's proxy server can be run in front of any SMTP server,B including the servers provided by PMDF, MultiNet, TCPware, MX, and TCP/IP Services.  J > If someone knows of a mail server with the ability to do custom content C > checks before the SMTP transaction is over that is available for  J > OpenVMS, either commercial or ported OpenSource, it would be useful for   > them to post that information. > < More information on PreciseMail Anti-Spam can be found here.  0 http://www.process.com/precisemail/antispam.html  = Disclaimer: I not only work for Process Software, PreciseMail  Anti-Spam Gateway is my baby.    Hunter ------9 Hunter Goatley, Process Software, http://www.process.com/ : goathunter@goatley.com      http://www.goatley.com/hunter/   ------------------------------  % Date: Sat, 21 May 2005 23:38:05 -0400 0 From: "Jeff Morgan" <vmswiz@geonospamcities.com>9 Subject: Re: How to filter spam based on message content? - Message-ID: <d6our0$26tu$1@news3.infoave.net>   J I'm fairly pleased with the results of my SMTP Email Content Filter. It's L been running for many years now. You just have to be careful not to get too L overzealous looking for specific words or you might throw away good emails. H If you ever email me, don't mention financing or mortgages. It won't go  through!   :)  M I haven't updated the source on www.geocities.com/vmswiz in quite some time.  F If anyone wants a copy of the latest DCL with all of my current "spam E phrase" filters, just let me know. Email me at vmswiz@yanospamhoo.com   F TEC is entirely written in DCL so it is easy to customize and add new M filters. There are no modifications to VMS or TCP/IP other than stopping the   normal SMTP incoming job que.   K I use TEC to block all executable files, zip files, everything from China,  F Poland, etc. You can easily block all audio and video files. Anything , "Received from: Unknown.hostname" is tossed.  I Any email with a cyrillic or chinese character gets tossed. I don't know  # anybody in eastern europe or China.   G You can even put emails on hold that are coming in to your kids' email  H address and check them for content before manually letting them through.  K I have a filter so the "To:" address must specifically contain valid email  I addresses on my internal network, otherwise they get put on hold. Then I  K also have specific permission searches for listservs that use distribution   lists.  M You can pretty much create any filter rules you can devise based on the text  9 content of the email and the power of the search utility.   J I get a status email every few hours showing all the filtered emails, the D main smtp headers and which phrase filter caught it. That way I can A fine-tune the filters and keep an eye on what is going through...   L If the VMS developers could improve the search utility and allow me to pass G parameters by external file or SYS$INPUT, I can cut out a lot of image  J activations. Right now, I can only search about 30 junk mail phrases in a L single DCL command string. Every single email message requires up to 60 DCL F search utility commands to pass all the tests. Options for Wildcards, L "discard all special characters" and "discard all spaces and tabs" would be  helpful as well.  H It's not the most efficient way to take care of a problem, but it works.  I If you want to try out the technique without harming your system, follow  L these steps to stop the que, pick out an email message and show the text of  the message body:   )        $ STOP/NEXT TCPIP$SMTP_nodename_00 /        $ sh que/all/file TCPIP$SMTP_nodename_00   L        Wait for messages to build up in the stopped que and then pick out a J filename from the entries in the que, for example, it will look something 
 like this:          $ type C sys$sysdevice:[SYS0.TCPIP$SMTP]05052119300771_TCPIP$SMTP-D2B8.*TEXT   I The message text is stored in a file of the same name as the file in the  * que, but with *TEXT as the file extension.  H The jobs in the SMTP que are just like print jobs. You can delete them, 7 reque them or put them on hold just like any other que.   A If you try the test above, don't forget to restart your SMTP que!   , The same technique also works with Multinet.  H Suggestions and improvements to my code are most welcome and encouraged!  #                                Jeff     @ "Peter Weaver" <newsgroup@weaverconsulting.ca> wrote in message % news:3f6vs2F699c2U1@individual.net...  > Lawrence Bleau wrote:  >>... A >> What I want to be able to do is filter based on content of the D >> message, rather than just IP address, host name, or subject line.C >> I'd like to reject the message while it is still being received, I >> rather than letting it get queued and delivered to my users' inbox and 7 >> having them to deal with the messages one at a time.  >>...  >  > Check out the message I > http://groups.google.ca/group/comp.os.vms/msg/e03d20ee60be5173?hl=en by H > Jeff Morgan last year.  It looks like it will do what you want. I haveG > been thinking about following his lead but modifying it so I can have C > VMS send my phone a SMS text message if an e-mail comes in with a 7 > certain phrase in the body or from certain customers.  >  > --   > Peter Weaver! > Weaver Consulting Services Inc.  > Canadian VAR for CHARON-VAX  > www.weaverconsulting.ca  >  >    ------------------------------    Date: 21 May 2005 11:01:01 -0700 From: AOLfan250106@yahoo.comY Subject: http://www.tbn.org/films/videos/To_Hell_And_Back.ram << GREAT VIDEO! Just click  C Message-ID: <1116698461.759634.171430@g49g2000cwa.googlegroups.com>   D http://www.tbn.org/films/videos/To_Hell_And_Back.ram << GREAT VIDEO! Just click on link to view.    ------------------------------  # Date: Sat, 21 May 2005 22:20:29 GMT " From:   VAXman-  @SendSpamHere.ORGY Subject: Re: http://www.tbn.org/films/videos/To_Hell_And_Back.ram << GREAT VIDEO! Just cl 0 Message-ID: <00A441BA.3B0169CB@SendSpamHere.ORG>  b In article <1116698461.759634.171430@g49g2000cwa.googlegroups.com>, AOLfan250106@yahoo.com writes:E >http://www.tbn.org/films/videos/To_Hell_And_Back.ram << GREAT VIDEO!  >Just click on link to view.  % Safari downloads 58 bytes of garbage.  --  K VAXman- A Bored Certified VMS Kernel Mode Hacker   VAXman(at)TMESIS(dot)COM              5   "Well my son, life is like a beanstalk, isn't it?"     ------------------------------    Date: 21 May 2005 12:11:01 -0700 From: tomarsin2015@comcast.net Subject: LAT problems B Message-ID: <1116702661.387892.51690@g43g2000cwa.googlegroups.com>   Hello 9 I am beginning to get the following error messages on LAT 3 %LAT-W-CMDERROR, error reported by command executor ' -SYSTEM-F-BADPARAM, bad parameter value  When I start LAT I get this 3 %LAT-W-CMDERROR, error reported by command executor / -LAT-F-NOMORESVCS, no more services in database G It seems like the LAT service is bombing out when the lat$systartup.com  comes to the line : $ lcp set node nodename (where nodename is the name of the node)/connections=both  1 The only thing I did was a reboot on a few nodes.  thanks phillip    ------------------------------  % Date: Sat, 21 May 2005 17:05:21 -0500 2 From: David J Dachtera <djesys.nospam@comcast.net>7 Subject: Re: Networking problem concerning a DEC TS 90L + Message-ID: <428FB0A0.53ACF2A7@comcast.net>    The Eighth Doctor wrote: > G > In article <428EA2B7.FF27F7C3@comcast.net>, djesys.nospam@comcast.net 	 > says...  > >  > >The Eighth Doctor wrote:  > >>! > >> Hello from the Eighth Doctor G > >> Basically I need to connect a DEC TS 90L who has a COAX port, to a  > customer'sP > >> UTP based network. It seems they seem need that gizmo for some work they doQ > >> based at the other end of their network. I did explain that there is a whole  > backplane P > >> for doing just that, but they refuse to spend the extra money to obtain the > backplane. > >>T > >> I just finished using a Google based search engines for the DELNI. I would have, > >> better luck wiring something of a sort. > >>S > >> Does anyone on the NG have just such an item roosting in their equipment room, Q > >> that they obviously do not need, and would be willing to part with, I'll pay 
 > shippingY > >> charges? And if your located in the tri-state area, (NY, NJ, CT), I'll take anything S > >> medium sized that's not needed as well, physically. Please e-mail for physical 
 > >> address.  > >  > >DELNI doesn't sound right.  > > E > >You're looking for a 10BaseT <-> 10Base2 transceiver of some sort.  > > D > >Push comes to shove, look for a DESPR (10Base5 to 10Base2, sinpleJ > >10Base2 port) or a DEMPR (multiple 10Base2 ports), and a DESTA (10Base5I > >to 10BaseT), at least I think those are the models. Not sure about the  > >-xx suffix for each, though.  > > I > >...though there's likely a smaller single-unit device that will do the ' > >same thing. Have you tried BlackBox?  > >  > >--  > >David J Dachtera  > >dba DJE Systems > >http://www.djesys.com/  > > , > >Unofficial OpenVMS Hobbyist Support Page:% > >http://www.djesys.com/vms/support/  > > + > >Unofficial Affordable OpenVMS Home Page: " > >http://www.djesys.com/vms/soho/ > > % > >Unofficial OpenVMS-IA32 Home Page: " > >http://www.djesys.com/vms/ia32/ > >  > >Coming soon: ) > >Unofficial OpenVMS Marketing Home Page  > Hello from the Eighth DoctorQ > Yes. What they have is too expensive, and poorly suited to my needs. I've got a P > four port AUI hub that Inmac made about twenty years ago, plus a good count ofR > DESTA units, and an equal number of AUIs that are UTP output. I figured I'd wire> > my own adapter, if I could not scare up a BNC<-->UTP device. > K > Problem is the first place that Google showed me that might have had them Q > for sale, had discontinued them three years ago. And the first sales 'droid who R > answered my e-mail, has reached the limits of his programming. I might visit theU > CDW website, or just keep digging. What I really need is one of the backplanes that  > the TS plugs into.  B Well, that alone won't help you unless you also find the DEChub-90E attached unit that provides multiple UTP ports (DECrepeater-90, don't + know the five-character code for that one).    --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/    Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------  % Date: Sat, 21 May 2005 18:27:35 -0500 2 From: David J Dachtera <djesys.nospam@comcast.net>7 Subject: Re: Networking problem concerning a DEC TS 90L + Message-ID: <428FC3E7.E4D5ACB3@comcast.net>    David J Dachtera wrote:  >  > The Eighth Doctor wrote: > > I > > In article <428EA2B7.FF27F7C3@comcast.net>, djesys.nospam@comcast.net  > > says...  > > >  > > >The Eighth Doctor wrote:  > > >># > > >> Hello from the Eighth Doctor I > > >> Basically I need to connect a DEC TS 90L who has a COAX port, to a  > > customer'sR > > >> UTP based network. It seems they seem need that gizmo for some work they doS > > >> based at the other end of their network. I did explain that there is a whole 
 > > backplane R > > >> for doing just that, but they refuse to spend the extra money to obtain the > > backplane. > > >>V > > >> I just finished using a Google based search engines for the DELNI. I would have. > > >> better luck wiring something of a sort. > > >>U > > >> Does anyone on the NG have just such an item roosting in their equipment room,OS > > >> that they obviously do not need, and would be willing to part with, I'll paya > > shipping[ > > >> charges? And if your located in the tri-state area, (NY, NJ, CT), I'll take anythinguU > > >> medium sized that's not needed as well, physically. Please e-mail for physical  > > >> address.s > > >t > > >DELNI doesn't sound right.d > > >sG > > >You're looking for a 10BaseT <-> 10Base2 transceiver of some sort.A > > >!F > > >Push comes to shove, look for a DESPR (10Base5 to 10Base2, sinpleL > > >10Base2 port) or a DEMPR (multiple 10Base2 ports), and a DESTA (10Base5K > > >to 10BaseT), at least I think those are the models. Not sure about theG! > > >-xx suffix for each, though.  > > >bK > > >...though there's likely a smaller single-unit device that will do thel) > > >same thing. Have you tried BlackBox?u > > >e > > >--f > > >David J Dachteral > > >dba DJE Systems > > >http://www.djesys.com/d > > > . > > >Unofficial OpenVMS Hobbyist Support Page:' > > >http://www.djesys.com/vms/support/  > > >-- > > >Unofficial Affordable OpenVMS Home Page:.$ > > >http://www.djesys.com/vms/soho/ > > > ' > > >Unofficial OpenVMS-IA32 Home Page: $ > > >http://www.djesys.com/vms/ia32/ > > >d > > >Coming soon:i+ > > >Unofficial OpenVMS Marketing Home Page3  > > Hello from the Eighth DoctorS > > Yes. What they have is too expensive, and poorly suited to my needs. I've got a-R > > four port AUI hub that Inmac made about twenty years ago, plus a good count ofT > > DESTA units, and an equal number of AUIs that are UTP output. I figured I'd wire@ > > my own adapter, if I could not scare up a BNC<-->UTP device. > >aM > > Problem is the first place that Google showed me that might have had themnS > > for sale, had discontinued them three years ago. And the first sales 'droid whoAT > > answered my e-mail, has reached the limits of his programming. I might visit theW > > CDW website, or just keep digging. What I really need is one of the backplanes thath > > the TS plugs into. > D > Well, that alone won't help you unless you also find the DEChub-90G > attached unit that provides multiple UTP ports (DECrepeater-90, don'tn- > know the five-character code for that one).h  F I think it might be a DETPR that you'd need, but not sure what variantH as I believe there was originally a stand-alone/rack-mount unit that was also called DETPR.   --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page:y" http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/a  " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/l   Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------  % Date: Sat, 21 May 2005 19:26:49 -0500o( From: Wayne Sewell <wayne@tachysoft.com>M Subject: Re: Newbie Questio.. Getting a Virtual address space full and global / Message-ID: <00A441C3.7FCF3BD0.1@tachysoft.com>m  , >Message-ID: <428FC1E4.8B9E07BE@comcast.net>& >Date: Sat, 21 May 2005 18:19:00 -05003 >From: David J Dachtera <djesys.nospam@comcast.net> & >Reply-To: djesysno@spam.earthlink.netN >Subject: Re: Newbie Questio.. Getting a Virtual address space full and globalN >         page table full error.. How to  repair.? page table full error.. How? >         to  repair.? page table full error.. How to  repair.?i+ >Content-Type: text/plain; charset=us-asciie  >Content-Transfer-Encoding: 7bit
 >Lines: 58     >Bruce Cooke wrote:n >> a >> HicH >> I have a Vaxstation 4000 60, vms 5.5 , 2 rz23l hard drives , and when     >>>> b/r5:1g >l >   2..1..0  >l >SYSBOOT>  SET STARTUP_P1 "MIN"p >w >SYSBOOT>  SET WRITESYSPARAMS 0t  M Was WRITESYSPARAMS available that far back?  vms 5.5 is kind of from the DawnyO of Man, or earlier.  I can't check, tossed all 5.5 media and documentation last 
 millenium.    O ===============================================================================UN Wayne Sewell, Tachyon Software Consulting  (281)812-0738   wayne@tachysoft.com; http://www.tachysoft.com/www/tachyon.html and wayne.html   EO ===============================================================================eP Jake Blues:"You traded the Caddy for a microphone? ...... Okay, I can buy that."   ------------------------------  # Date: Sat, 21 May 2005 20:44:51 GMTa+ From: "Bruce Cooke" <bruce.a.cooke@shaw.ca> Y Subject: Newbie Questio.. Getting a Virtual address space full and global page table full . Message-ID: <75Nje.1429037$Xk.312577@pd7tw3no>   HiF I have a Vaxstation 4000 60, vms 5.5 , 2 rz23l hard drives , and when K booting get the subject messages. The computer wont boot into dec windows,  G so the only way in is thru the DCL sysboot menu.I know there are spare FH blocks on the boot drive but have no idea how to fix no virtual address  space error Any one  here know how to solve this? TIAR   ------------------------------  % Date: Sat, 21 May 2005 18:19:00 -0500 2 From: David J Dachtera <djesys.nospam@comcast.net>Y Subject: Re: Newbie Questio.. Getting a Virtual address space full and global page table  + Message-ID: <428FC1E4.8B9E07BE@comcast.net>-   Bruce Cooke wrote: >  > HiG > I have a Vaxstation 4000 60, vms 5.5 , 2 rz23l hard drives , and whennL > booting get the subject messages. The computer wont boot into dec windows,H > so the only way in is thru the DCL sysboot menu.I know there are spareI > blocks on the boot drive but have no idea how to fix no virtual address  > space error Any ones > here know how to solve this?  B Well, Peter suggested AUTOGEN. If you don't know what that is, I'dG recommend a read through the on-line OpenVMS documentation which can beE found via this URL:     http://www.hp.com/go/openvms/doc  ; Look down the left-hand column for OpenVMS Operating Systemm? documentation, go that page, and have a read through the SystemnE Manager's Manual. The current version is quite far removed from V5.5,l" but many of the basics will apply.  H SInce you're having trouble booting, you may need to do a conversational@ boot and do a minimal startup. The sequence would look like this$ (assuming your boot root is 0(zero):  
 >>> b/r5:1  
    2..1..0   SYSBOOT>  SET STARTUP_P1 "MIN"   SYSBOOT>  SET WRITESYSPARAMS 0   SYSBOOT>  CONT  C Then, if it boots up o.k. in minimum mode, run AUTOGEN from GETDATA  through REBOOT:I  $ $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT   ...and see how it goes.F   --   David J Dachtera dba DJE Systems0 http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page:1" http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/T  " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/s   Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------  % Date: Sat, 21 May 2005 17:00:47 -0500T2 From: David J Dachtera <djesys.nospam@comcast.net>- Subject: Re: Newbie with command file problem + Message-ID: <428FAF8F.2AE4A3C8@comcast.net>O   brucedodds@comcast.net wrote:a > H > Yes, I've seen the VMS help command.   I do  use it, but it might haveF > been kind of tough to get an answer to the question I posed here via > HELP.4   How so?   E ...or did you see some other piece of code and just model the boolean* operators in use there?z  A (Another poster provided the help path to the boolean operators.)o   -- i David J Dachtera dba DJE Systemse http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page:0" http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/W  " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/n   Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------    Date: 21 May 2005 22:37:15 +01006 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)$ Subject: Re: upgrade 7.3-1 --> 7.3-2, Message-ID: <428fb81b$1@news.langstoeger.at>  w In article <d6ni24$vhv$1@online.de>, helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes:EG >Some related questions:  After the upgrade, I immediately applied all e9 >patches (the latest UPDATE and all patches not in that).s  F I hope you started with the VMS732_PCSI patch, then the VMS732_UPDATE, then the rest...  H >                                                          (It would be B >nice if PRODUCT INSTALL were supported within the restricted DCL  >environment!)  2 There are only two things to note when doing this:B 1) You need /REMOTE for all PRODUCT commands (which means you have? to define the PCSI$SYSDEVICE and PCSI$SPECIFIC logicals before) ? 2) You can't UNDO patches because pure V7.3-2 had a bug in PCSI G (which is fixed in VMS732_PCSI) and you probably don't find a VMS 7.3-2," installation CD with ECOs applied.  = btw: Has anyone tried/succeeded making an VMS installation CD J with cumulated ECOs ? (I always get VERIFY errors after burning the CD...)  D >               I first applied the PCSI patch, and it said I could D >either log out and log back in or do a "SET COMMAND".  I chose the 	 >latter. e  H I always do a SET HOST/LOG for every installation (after defining 3 moreE PCSI logicals - PCSI$LOG, PCSI$TRACE and PCSI$$SAVE_RECOVERY_DATA) to,J get a useful set of infos where which file came from and which kit deleted6 which (sometimes foreign) file is saved for later use.  E Sideeffect of this is a new process with a new command table as well..  A >          The next installation complained about "BLOCK_SIZE".   I >Apparently the installation went OK though.  To me, this looks like the E7 >SET COMMAND didn't take effect.  Has anyone seen this?M  @ It probably comes from the VMS732_COPY V1.0 which is now part of- VMS732_UPDATE V4.0 and no, I haven't seen it.Y  = Did you really do a $ SET COMMAND/TABLE=SYS$SHARE:DCLTABLES ?_  P btw: Why is COPY/BLOCK_SIZE not entered in VMSHELP ? Is the ECO suboptimal ? ;-)  I >Since I was installing from a different account than the one I normally dI >use for installation, the installation of the UPDATE kit crashed due to A >too low quota."  ? Installations are a very important task for the SYSTEM account.YM How could that happen not using SYSTEM ? This is obvious for >20 years now..."  H >               I then modified the account, logged out and logged back # >in, and repeated the installation.o  , Does PRODUCT SHOW HISTORY now reflect this ?  H >                                   It apparently went through OK (here D >and in the above case if PRODUCT tells me it has been successfully E >installed, I'm hoping that that is in fact the case), but gave some hE >strange "kitnotsame" messages, though of course it was the same kit.e  L What is the exact message ? I don't know a "kitnotsame". Do you perhaps mean^ %PCSI-I-RETAIN, file file was not replaced because file from kit has lower generation number# Don't think so, but I don't know...f  E >I also noticed in the ACRTL patch it sometimes says in the text filefE >that it is for 8.2 rather than 7.3-2, but in other cases talks aboutYE >7.3-2, which is apparently correct.  Probably a cut-and-paste error.7  E Not during my kit installtion. Do you have more detailed info ? Or do I you mean the VMS732_ACRTL-V0100.RELEASE_NOTES, which have only one error:   A      2.3  Version(s) of OpenVMS to which this kit may be applied:)        OpenVMS Alpha V8.2.   or did you misread the umpteen:i  D                a.b.c.d  Release Version of OpenVMS that will contain$                         this change:                  V8.2c  C >I'm also confused about the PCSI messages regarding the saving of EF >recovery data.  Normally, I apply a few patches one after the other, H >then reboot once when I am done (then usually again after an AUTOGEN a C >day or two later).  One is advised to save recovery data, but the  G >messages make it sound like one can undo only the last patch applied,  J >though based on other messages this is not completely clear.  Can anyone  >explain this in detail?  K *) Save recovery data is a method to store the original files of the system G disk in an extra area (SYS$SYSDEVICE:[PCSI$UNDO*]) to allow the UNDOinga< of an (VMS, DECnet, TCPIP, MOTIF, ...) ECO (!) installation.  E *) It requires a version of PCSI which is still not available on VAX.b  L *) /SAVE_RECOVERY_DATA (or setting the undocumented PCSI$$SAVE_RECOVERY_DATAB logical to YES) has only a meaning for the installation of an ECO.  E *) An installation of an full kit invalidates the stored files in the I PCSI$UNDO* directories and therefor PRODUCT does REMOVE the RECOVERY_DATA > automatically (all recovery data = you can't UNDO afterwards).  G *) PRODUCT UNDO is for ECO kits only (full kit installations are undoneID with a PRODUCT REMOVE of course) and requires the VMS732_PCSI patch.  C *) Every (ECO) installation makes an SYS$SYSDEVICE:[PCSI$UNDO_001]. J If this already exists, it is renamed to PCSI$UNDO_002.DIR If this already5 exists, it is renamed to PCSI$UNDO_003.DIR and so on.E  H *) If you UNDO an ECO installation where more than one ECO was installed2 at once, all of them are deinstalled at once also.  lG >                         If one can only undo the last patch, I don't rF >see much benefit from this, but I also don't see any reason for this ) >restriction.  Or am I missing something?c  N You can UNDO the latest ECO installation. And then the ECO installation beforeN becomes the latest and this you can undo again. You can UNDO all installationsL as long as you have recovery data for them (usually up to the last full PCSI kit installation).  B NOTE: VMSINSTAL invalidates the PCSI$UNDO* directories as well butC without deleting them automatically. UNDOing after an VMSINSTAL mayhE restore wrong files and is dangerous. (a quick fix would be a PRODUCT D DELETE RECOVERY_DATA line at the start of SYS$UPDATE:VMSINSTAL.COM).     So my way (and suggestion) is:H 1) Do not install every single kit you find immediately (on a testsystemF of course, in production things are different ;-). Wait for a handfull of them before you start.oF 2) Always make installations of one kit at a time and always make&keep a logfile of it.D 3) Avoid VMSINSTAL kits (they can't be deinstalled easily) as far as possible# 4) Group all the kits to install inh 	a) VMSINSTAL kits 	b) full PCSI kits 	c) ECO PCSI kitsrC 5) Define the PCSI logicals to reduce type work during installationaJ (and prevent forgetting important switches like /LOG) which means at least+   "PCSI$$SAVE_RECOVERY_DATA" [exec] = "YES"t   "PCSI$LOG" [exec] = "TRUE"%   "PCSI$SOURCE" [exec] = "disk:[dir]"a   "PCSI$TRACE" [exec] = "TRUE"$ 6) Make a backup of your system disk, 7) Do a PRODUCT DELETE RECOVERY_DATA by handF (the VMSINSTAL or the full PCSI kits delete them anyway, but then they. will fill your installation logfile unrelated)+ 8) Begin the installation of 4a, 4b and 4c.u   Is this enough ?   --   Peter "EPLAN" LANGSTOEGERs% Network and OpenVMS system specialist0 E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------   Date: 21 May 05 16:47:00 EDT) From: cook@wvnvms.wvnet.edu (George Cook),$ Subject: Re: upgrade 7.3-1 --> 7.3-2! Message-ID: <lt0kntwpxxoY@wvnvms>5  w In article <d6ni24$vhv$1@online.de>, helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes:8= > I have a few questions regarding a 7.3-1 --> 7.3-2 upgrade.t > I > First, though, I'm happy to say that it went well, and I now have a DECeE > 3000/300LX with 48 MB RAM (yes, I know that the official minimum iscH > more) running 7.3-2 (I did the upgrade on a 3000/600 with 192 MB RAM, G > though) and apparently all is OK.  (I also have TCPIP 5.4 ECO 4 now.). > E > I've done fresh installs with 7.1 (ALPHA), 7.2 (VAX), 7.3 (VAX) and D > upgrades 7.1 --> 7.2-1 (ALPHA), 7.2 --> 7.3 (VAX), 7.2-1 --> 7.3-1J > (ALPHA) and now 7.3-1 --> 7.3-2 (ALPHA).  Only in this most recent case H > did I see these problems; previously, everything went without a hitch.  ' ... H > Some related questions:  After the upgrade, I immediately applied all I > patches (the latest UPDATE and all patches not in that).  (It would be  C > nice if PRODUCT INSTALL were supported within the restricted DCL oE > environment!)  I first applied the PCSI patch, and it said I could aE > either log out and log back in or do a "SET COMMAND".  I chose the 0A > latter.  The next installation complained about "BLOCK_SIZE".  dJ > Apparently the installation went OK though.  To me, this looks like the 8 > SET COMMAND didn't take effect.  Has anyone seen this?  G Was it the UPDATE-V0400 patch which complained?  If so, we had the sameIJ problem.  Apparently V0400 needs the COPY command CLD to have been updatedE by a previous patch (a bug since V0400 should only need PCSI-V0100 to8C have previously been installed).  The only supported way to get the I CLD updated is to first install COPY-V0100, but it unfortunately requires/J UPDATE-V0300.  To avoid a bunch of installs we manually extracted COPY.CLDG from COPY-V0100 and placed it in DCLTABLES.EXE (with an INSTALL/REPLACEtG DCLTABLES.EXE and logout/login afterward), after which UPDATE-V0400 ranm without error.  ? FWIW, HP support said it was safe to ignore the BLOCK_SIZE copy;B command failures.  We never determined what didn't get copied when the commands failed.  J > Since I was installing from a different account than the one I normally J > use for installation, the installation of the UPDATE kit crashed due to J > too low quota.  I then modified the account, logged out and logged back J > in, and repeated the installation.  It apparently went through OK (here E > and in the above case if PRODUCT tells me it has been successfully dF > installed, I'm hoping that that is in fact the case), but gave some F > strange "kitnotsame" messages, though of course it was the same kit.  E The failed install probably updated the COPY CLD prior to failing, soNB the second install used the correct CLD.  I have no idea about the "kitnotsame" messages.     George Cooki WVNETt   ------------------------------   Date: 21 May 05 17:45:08 EDT) From: cook@wvnvms.wvnet.edu (George Cook) $ Subject: Re: upgrade 7.3-1 --> 7.3-2! Message-ID: <iTL+QMjixNY6@wvnvms>t  e In article <428fc369$1@news.langstoeger.at>, peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) writes:sO > In article <lt0kntwpxxoY@wvnvms>, cook@wvnvms.wvnet.edu (George Cook) writes:iA >>FWIW, HP support said it was safe to ignore the BLOCK_SIZE copy D >>command failures.  We never determined what didn't get copied when >>the commands failed. > N > If you have a detailed installation log of the failed and of the successfullK > installation, there should be a hint in the differences found. Or what isa > the problem ?n  D We did not have a detailed log.  We were in a hurry, so we undid theD install, got the right CLD in DCLTABLES, and reinstalled (I guess we2 should have created a detailed log at that point).     George Cookt WVNETr   ------------------------------  + Date: Sat, 21 May 2005 22:50:01 +0000 (UTC) P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)$ Subject: Re: upgrade 7.3-1 --> 7.3-2$ Message-ID: <d6oduo$74o$1@online.de>  H In article <428fb81b$1@news.langstoeger.at>, peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) writes: t  y > In article <d6ni24$vhv$1@online.de>, helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) writes:-I > >Some related questions:  After the upgrade, I immediately applied all e; > >patches (the latest UPDATE and all patches not in that).  > H > I hope you started with the VMS732_PCSI patch, then the VMS732_UPDATE, > then the rest...  
 Yes, exactly.l  ? > Did you really do a $ SET COMMAND/TABLE=SYS$SHARE:DCLTABLES ?i  ? I entered the command as the installation procedure told me to.n  K > >Since I was installing from a different account than the one I normally  K > >use for installation, the installation of the UPDATE kit crashed due to s > >too low quota.p > A > Installations are a very important task for the SYSTEM account.eO > How could that happen not using SYSTEM ? This is obvious for >20 years now...e  B I installed the patches using SYSTEM, which had too low quotas.  ID normally install patches from another account (with all privs turnedI on), whose quotas were high enough, so I updated SYSTEM to have the same m quotas.e  J > >               I then modified the account, logged out and logged back % > >in, and repeated the installation.r > . > Does PRODUCT SHOW HISTORY now reflect this ?   No.t  I PRODUCT                             KIT TYPE    OPERATION   DATE AND TIMElP ----------------------------------- ----------- ----------- --------------------P DEC AXPVMS VMS732_VERIFY V1.0       Patch       Install     19-MAY-2005 02:03:41P DEC AXPVMS VMS732_LAN V3.0          Patch       Install     19-MAY-2005 02:02:43P DEC AXPVMS VMS732_GRAPHICS V3.0     Patch       Install     19-MAY-2005 02:01:06P DEC AXPVMS VMS732_FIBRE_SCSI V4.0   Patch       Install     19-MAY-2005 01:57:03P DEC AXPVMS VMS732_SYS V7.0          Patch       Install     19-MAY-2005 01:55:35P DEC AXPVMS VMS732_DRIVER V2.0       Patch       Install     19-MAY-2005 01:52:59P DEC AXPVMS VMS732_DCL V3.0          Patch       Install     19-MAY-2005 01:51:44P DEC AXPVMS VMS732_ACRTL V1.0        Patch       Install     19-MAY-2005 01:50:39P DEC AXPVMS TCPIP_ECO V5.4-154       Patch       Install     19-MAY-2005 01:34:54P DEC AXPVMS DWMOTIF_ECO01 V1.3-1     Patch       Install     19-MAY-2005 01:29:10P DEC AXPVMS VMS732_UPDATE V4.0       Patch       Install     19-MAY-2005 01:19:46P DEC AXPVMS VMS732_PCSI V1.0         Patch       Install     19-MAY-2005 01:10:04P CPQ AXPVMS CDSA V2.0-109            Full LP     Install     19-MAY-2005 00:00:13P DEC AXPVMS DECNET_PHASE_IV V7.3-2   Full LP     Install     19-MAY-2005 00:00:13P DEC AXPVMS DWMOTIF V1.3-1           Full LP     Install     19-MAY-2005 00:00:13P DEC AXPVMS OPENVMS V7.3-2           Platform    Install     19-MAY-2005 00:00:13P DEC AXPVMS TCPIP V5.4-15            Full LP     Install     19-MAY-2005 00:00:13P DEC AXPVMS VMS V7.3-2               Oper System Install     19-MAY-2005 00:00:13P HP AXPVMS KERBEROS V2.0-6           Full LP     Install     19-MAY-2005 00:00:13  F Prior to these are removals of old stuff done by the installation.  SoH the failed UPDATE install doesn't show up.  (Do failed installs show up ? in PRODUCT SHOW HISTORY?  I know they do in VMSINSTAL.HISTORY.)   J > >                                   It apparently went through OK (here F > >and in the above case if PRODUCT tells me it has been successfully G > >installed, I'm hoping that that is in fact the case), but gave some iG > >strange "kitnotsame" messages, though of course it was the same kit.c > N > What is the exact message ? I don't know a "kitnotsame". Do you perhaps mean` > %PCSI-I-RETAIN, file file was not replaced because file from kit has lower generation number  F No.  That's a harmless message which I saw many times, mainly because I the 7.3-1 patches were current and the 7.3-2 CD a couple of years old by t? now.  I didn't note the whole message, but it was "kitnotsame".p  G > >I also noticed in the ACRTL patch it sometimes says in the text filesG > >that it is for 8.2 rather than 7.3-2, but in other cases talks aboutfG > >7.3-2, which is apparently correct.  Probably a cut-and-paste error.e > G > Not during my kit installtion. Do you have more detailed info ? Or dodK > you mean the VMS732_ACRTL-V0100.RELEASE_NOTES, which have only one error:o > C >      2.3  Version(s) of OpenVMS to which this kit may be applied:l >  >      OpenVMS Alpha V8.2    Yes, that's what I mean.  M > *) Save recovery data is a method to store the original files of the system I > disk in an extra area (SYS$SYSDEVICE:[PCSI$UNDO*]) to allow the UNDOingP> > of an (VMS, DECnet, TCPIP, MOTIF, ...) ECO (!) installation.   OK.s  G > *) It requires a version of PCSI which is still not available on VAX.n   OK.i  N > *) /SAVE_RECOVERY_DATA (or setting the undocumented PCSI$$SAVE_RECOVERY_DATAD > logical to YES) has only a meaning for the installation of an ECO.   OK.c  G > *) An installation of an full kit invalidates the stored files in the K > PCSI$UNDO* directories and therefor PRODUCT does REMOVE the RECOVERY_DATAq@ > automatically (all recovery data = you can't UNDO afterwards).  E Is it obvious which, if any, of the patches at ITRC (see the list of  ; patches I installed after the upgrade above) are full kits./  I > *) PRODUCT UNDO is for ECO kits only (full kit installations are undonehF > with a PRODUCT REMOVE of course) and requires the VMS732_PCSI patch.  ! That was the first one I applied.   E > *) Every (ECO) installation makes an SYS$SYSDEVICE:[PCSI$UNDO_001].0L > If this already exists, it is renamed to PCSI$UNDO_002.DIR If this already7 > exists, it is renamed to PCSI$UNDO_003.DIR and so on.l > J > *) If you UNDO an ECO installation where more than one ECO was installed4 > at once, all of them are deinstalled at once also.  C Do you mean selecting more than one thing with PRODUCT INSTALL?  I   always select one at a time.  I > >                         If one can only undo the last patch, I don't oH > >see much benefit from this, but I also don't see any reason for this + > >restriction.  Or am I missing something?w > P > You can UNDO the latest ECO installation. And then the ECO installation beforeP > becomes the latest and this you can undo again. You can UNDO all installationsN > as long as you have recovery data for them (usually up to the last full PCSI > kit installation).  H Most of the patches I install say that if I save recovery data for this F patch, it will remove that for the previous patch.  It also says that C things not involved in the current installation are not affected.  .
 Confusing.    > So my way (and suggestion) is:J > 1) Do not install every single kit you find immediately (on a testsystemH > of course, in production things are different ;-). Wait for a handfull > of them before you start. H > 2) Always make installations of one kit at a time and always make&keep > a logfile of it.F > 3) Avoid VMSINSTAL kits (they can't be deinstalled easily) as far as
 > possible  I I always do all of these (except the log file; should get into the habit - of SET HOST/LAT/LOG).e  % > 4) Group all the kits to install inn > 	a) VMSINSTAL kits > 	b) full PCSI kits > 	c) ECO PCSI kitsl  I Are any of the "patches" at ITRC "full kits"?  I saw the messages during 1* the installation of the stuff shown above.  E > 5) Define the PCSI logicals to reduce type work during installationkL > (and prevent forgetting important switches like /LOG) which means at least- >   "PCSI$$SAVE_RECOVERY_DATA" [exec] = "YES"O >   "PCSI$LOG" [exec] = "TRUE"' >   "PCSI$SOURCE" [exec] = "disk:[dir]"G  >   "PCSI$TRACE" [exec] = "TRUE"  B I'll have to look into this, but I think I answer the interactive  questions appropriately.  & > 6) Make a backup of your system disk  ; I generally break a shadow set and restore it if all is OK.T   ------------------------------    Date: 21 May 2005 15:46:42 -0700# From: "itjck01" <JKoska@bender.com>t$ Subject: Re: upgrade 7.3-1 --> 7.3-2B Message-ID: <1116715602.360936.38250@g44g2000cwa.googlegroups.com>  & See OpenVMS Alpha 8.2 Release Notes...? http://h71000.www7.hp.com/doc/82FINAL/6674/6674pro_install.html0  G Namely, section 1.9.3 Error on upgrade from version 7.3-1, which speaks0 to the STARLET_C.TLB error.>  * "1.9.3 Error on Upgrade from Version 7.3-1 V8.2  D When you upgrade an OpenVMS Alpha Version 7.3-1 system disk to Alpha@ Version 8.2, the following error message might appear during the execution phase:  A %PCSI-E-PARUDF, file [SYSLIB]SYS$STARLET_C.TLB was not previouslye	 installedn5 or is present but out of scope; module update skippedtE Terminating is strongly recommended.  Do you want to terminate? [YES]m  ? This error message is not appropriate for the circumstances. It ? incorrectly states that the SYS$STARLET_C.TLB library cannot be E updated. The cause of this problem is that a patch kit applied to the0B Alpha Version 7.3-1 system disk improperly updated a module in the library.  G Disregard the recommendation to terminate the upgrade. Answer NO to thenB prompt Do you want to terminate? [YES] . The upgrade will continue successfully. "j  s :) jck   ------------------------------  + Date: Sat, 21 May 2005 22:52:03 +0000 (UTC)oP From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)$ Subject: Re: upgrade 7.3-1 --> 7.3-2$ Message-ID: <d6oe2j$74o$2@online.de>  E In article <lt0kntwpxxoY@wvnvms>, cook@wvnvms.wvnet.edu (George Cook)t writes:   J > > Some related questions:  After the upgrade, I immediately applied all K > > patches (the latest UPDATE and all patches not in that).  (It would be IE > > nice if PRODUCT INSTALL were supported within the restricted DCL lG > > environment!)  I first applied the PCSI patch, and it said I could oG > > either log out and log back in or do a "SET COMMAND".  I chose the  C > > latter.  The next installation complained about "BLOCK_SIZE".  ,L > > Apparently the installation went OK though.  To me, this looks like the : > > SET COMMAND didn't take effect.  Has anyone seen this? > 3 > Was it the UPDATE-V0400 patch which complained?  i   Yes.   > If so, we had the sameL > problem.  Apparently V0400 needs the COPY command CLD to have been updatedG > by a previous patch (a bug since V0400 should only need PCSI-V0100 to0E > have previously been installed).  The only supported way to get the K > CLD updated is to first install COPY-V0100, but it unfortunately requiresmL > UPDATE-V0300.  To avoid a bunch of installs we manually extracted COPY.CLDI > from COPY-V0100 and placed it in DCLTABLES.EXE (with an INSTALL/REPLACEhI > DCLTABLES.EXE and logout/login afterward), after which UPDATE-V0400 ranD > without error.  & This is an obvious bug in the patches.  A > FWIW, HP support said it was safe to ignore the BLOCK_SIZE copy D > command failures.  We never determined what didn't get copied when > the commands failed.  H I ignored them, and haven't noticed any problems (then again, I haven't  done any serious testing).   ------------------------------  % Date: Sat, 21 May 2005 14:04:05 -0400 $ From: "Chris" <an.other@not_here.ca>0 Subject: Re: VAXstation 3100 free to a good home8 Message-ID: <nKKje.6718$Wp.856446@news20.bellglobal.com>  L Not a bad little toy, but hardly worth all the angst demonstrated here. SortJ of like agonizing over giving away a well-used 1963 Plymouth 4 door with 6G cyl and 3 spd manual.   Might be worth something to someone, but if YOUh don't want it, why care?  B Not horribly fast, needs much more memory than the 12 Mb indicatedH (especially when DECwindows hits), required a memory daughter card iirc,L 3-button DEC "puck" mouse was a royal pain, and is pretty specific about itsL video requirements.  Running PWRK on one would indicate that response on the: desktop isn't needed, and with so little disk, why bother?  G (had 4 of them with 24Mb end up in the crusher a year or so ago -- more ) trouble than they were worth, ultimately)e  + <tomarsin2015@comcast.net> wrote in message = news:1116646960.463149.236090@f14g2000cwb.googlegroups.com...oI > I surplus a VAXstation 3100 with 2 1 gig drives and 12megs of memory. Iy: > would like to give this system to someone that could useD > it. VMS 7.3 is already installed, so the only thing you would needI > to do is install a license. The system is a VAX model 10 in a BA42 box.1D > What I would like is a e-mail stating why you would like this VAX. >  There are a few rules thruoB > 1. NO EBAY - IF YOU WANT THE SYSTEM TO SALE ON EBAY OR ANY OTHER5 >    ONLINE AUCTION SERVICE THEN LOOK SOMEPLACE ELSE.rB >    YOU WILL SIGN A AGREEMENT TO THE FACT - IF THE SYSTEM APPEARSH >    ON EBAY OR ANY OTHER SERVICE THEN YOU OWN ME 5000.00 (FIVE THOUSAND" > DOLLARS) (AND YES THIS IS LEGAL)8 > 2. YOU MUST KEEP THE SYSTEM FOR AT LEAST 1 (ONE) YEAR.B > 3. THE SYSTEM WILL BE USED FOR A NON-PROFIT USE IE HOME USE ONLYF > 4. YOU MAY TRANSFER/GIVE THE SYSTEM TO SOMEONE ELSE, BUT IF IT FALLSI > WITHIN THAT 1 YEAR I MUST BE NOTIFIED, AND THE PERSON MUST AGREE TO THE  > THESE TERMS.I > ANY VOLIATION OF THESE RULES WILL RESULT IN COURT ACTION - I HAVE GIVENnH > STUFF AWAY ONLY TO SEE IT APPEAR ON EBAY. SO THATS WHY I AM GETTING SOG > STRICK. I AM NOT GIVING STUFF AWAY JUST TO SEE IT ON EBAY!!! IF THATSe( > THE CHOICE THEN I WILL DO IT MYSELF!!!A > I will be putting the system on the net so anybody can log intomH > the system and see what it is like. You may telnet to the system using@ > the address 68.35.167.136 port 99 (make sure you spec port 99) > USERNAME FREEVAX > NO PASSWORD NEEDED< > The system will be up on the net within the next 24 hours.E > LOCAL PICKUP IS PREFER, BUT WILL SHIP IT. YOU PICK UP THE CHARGES - , > THIS ALSO INCLUDES INTERNATIONAL SHIPPING. > thanks > ps= > I may have a Alphastation 200/233 going to the dumps soon!!P	 > phillipo >o   ------------------------------    Date: 21 May 2005 11:58:42 -0700 From: tomarsin2015@comcast.net0 Subject: Re: VAXstation 3100 free to a good homeC Message-ID: <1116701922.075726.326490@g44g2000cwa.googlegroups.com>   F To tell the truth I could care less what you do with the silly thing -G put it up on ebay and  get 10 million for it  more power to you. As foru8 disk a 1 gig is good for the system disk, but if someone@ is serious about the thing I will throw in a few  9s  or 18s forF storage. I also have a TKZ30 or a TKZ10 that would go with the system.6 I thought I had a 16meg module to get the system up toG 32megs but I cannot find the board(s). Yes the VAXserver with PathworksHB is used by about 5 people maybe 10 at the most, but they are loyal9 Pathworks customers, they would rather fight then switch.  phillipm   ------------------------------  % Date: Sat, 21 May 2005 17:57:31 -0400i- From: JF Mezei <jfmezei.spamnot@teksavvy.com> 0 Subject: Re: VAXstation 3100 free to a good home+ Message-ID: <428FAEC4.1133AE3@teksavvy.com>   E What is the difference between  a VAXstation 3100-10 and a Vaxstationr	 3100-30 ?d  E I know that a Microvax 3100-10 and -30 go from 2.4 to 3.5 VUPS. But It0 also know that Microvax 3100 != Vaxstation 3100.  < This puppy might be interesting in a cluster as a 3rd node.   / I might also be interested in the disk drives. c   But transport...   ------------------------------  % Date: Sat, 21 May 2005 18:22:34 -0500a2 From: David J Dachtera <djesys.nospam@comcast.net>0 Subject: Re: VAXstation 3100 free to a good home+ Message-ID: <428FC2B9.24C98DDB@comcast.net>    tomarsin2015@comcast.net wrote:e > I > I surplus a VAXstation 3100 with 2 1 gig drives and 12megs of memory. I): > would like to give this system to someone that could use > it.t   Um, Guy?  E I can understand your not wanting to give away something that someonel7 else could potentially make money off of, but consider:m  G o Shipping charges easily eat up any potential profit unless one passestF them along to the buyer, which - of course - discourages some bidders.  G o If you don't want others to profit rather than you, sell it yourself.:   -- / David J Dachtera dba DJE Systemsg http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page:-" http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/i  " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/D   Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------  % Date: Sat, 21 May 2005 23:24:08 -0400o' From: Dave Froble <davef@tsoft-inc.com>t0 Subject: Re: VAXstation 3100 free to a good home0 Message-ID: <118vup68mqujt0f@corp.supernews.com>   tomarsin2015@comcast.net wrote: H > To tell the truth I could care less what you do with the silly thing -I > put it up on ebay and  get 10 million for it  more power to you. As forp: > disk a 1 gig is good for the system disk, but if someoneB > is serious about the thing I will throw in a few  9s  or 18s for
 > storage.  H If you're offering some 9 or 18 GB disks, I could use a couple.  50 pin G or 68 pin SCSI?  I use such to backup my VMS systems.  (You can tell I I don't have much data.)   -- A4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com 170 Grimplin Road= Vanderbilt, PA  15486=   ------------------------------  % Date: Sat, 21 May 2005 23:21:22 -04008' From: Dave Froble <davef@tsoft-inc.com>w0 Subject: Re: VAXstation 3100 free to a good home0 Message-ID: <118vuk0hmphee43@corp.supernews.com>   Chris wrote:N > Not a bad little toy, but hardly worth all the angst demonstrated here. SortL > of like agonizing over giving away a well-used 1963 Plymouth 4 door with 6I > cyl and 3 spd manual.   Might be worth something to someone, but if YOUw > don't want it, why care?  I When you're trying to help some hobbyist, you can get a bit upset seeing 7) it on Ebay the next week.  I can, anyway.t   -- 04 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com 170 Grimplin Roads Vanderbilt, PA  15486o   ------------------------------   End of INFO-VAX 2005.283 ************************