0 INFO-VAX	Thu, 30 Jan 2003	Volume 2003 : Issue 59      Contents:D Re: Advanced Server question - client differences when reading files$ Alphaserver 4100 and Powerstorm 4D20 Andrew...Oh Andrew... = Re: Announcing a port of GnuPG V1.2 for OpenVMS Alpha and VAX  Re: automatic screensaver  RE: Clustered V6.2 and V7.3-1? Re: Clustered V6.2 and V7.3-1? RE: Clustered V6.2 and V7.3-1? RE: Clustered V6.2 and V7.3-1? Re: Clustered V6.2 and V7.3-1? Re: Clustered V6.2 and V7.3-1? Re: Clustered V6.2 and V7.3-1? Re: Clustered V6.2 and V7.3-1?' Re: cron in LINUX/UNIX, what in OpenVMS ' Re: cron in LINUX/UNIX, what in OpenVMS  Re: ds25# Re: EV7 / EV8 intellectual property 2 Re: EV7 hits, blows away Sun, IBM, 2-3x VMS gains!( GNU PATCH from OpenVMS freeware archives+ groups.google.com tip (Was: Re: memoryleak) ! Re: High hit rate VMS Web server? ! Re: High hit rate VMS Web server? 7 How To Turn Off HTML (Outlook, Outlook Express, et.al.) , HP has a chance to buy some software (rumor)+ Re: Installing second ethernet card (DE500)  Re: memoryleak Re: memoryleak Re: Moving CMS" My e-mail sucks and I owe you beer& Re: My e-mail sucks and I owe you beer& Re: My e-mail sucks and I owe you beer OpenVMS DCOM question ... A Re: OpenVMS.org: Marvel article and HP's press release for Marvel P Re: OpenVMS.org: Marvel article and HP's press release for Marvel and Alpha Reta! QL-XULA* licenses valid on Alpha? ! Re: Removing UCX from VMS system. ! Re: Removing UCX from VMS system. ) Re: Sending Escape Codes to a LPR Printer  Submit at end of month?  Re: Submit at end of month?  Re: Submit at end of month?  Re: Submit at end of month? # Re: Terminal server recommendations   Re: VAXstation 4000 cd-rom bezel Re: VMS source listings ?  Re: VMS source listings ?  Re: VMS source listings ?  Re: VMS source listings ?  Re: VMS source listings ?  Re: VMS source listings ?  Re: Was Doc's box cracked?& Re: [MSA1000] Support for/by OpenVMS ?  F ----------------------------------------------------------------------  % Date: Wed, 29 Jan 2003 21:01:22 -0500 5 From: "Brad McCusker" <brad.mccuskerNosp@Mcompaq.com> M Subject: Re: Advanced Server question - client differences when reading files / Message-ID: <v3h1rm6nl5lc44@corp.supernews.com>   E "Barratt, Chris (FMC)" <Chris.Barratt@fmc.sa.gov.au> wrote in message J news:07103702F27FD411ACA30000F8085452044FF190@sagemshs001.fmc.sa.gov.au...F > I have a share set up via Advanced Server which contains a number ofJ > sequential files which are of the format fixed length, 120 byte records. > F > When I connect to the share using an NT4 client and load a file into wordpad J > (or notepad), the file loads in such a way that it recognises the end of7 > each record and starts each new record on a new line.  > K > If I use a Windows 2000 or XP client connected to the same share and open J > the same file from Wordpad, the end of record is not recognised and many" > records appear on the same line. >   K I don't recognize this situation.  My first step in analyzing this would be K to capture a NETMON trace of each connection and read and look at the SMBs. K Chances are they are using different SMBs.  There in lies the direct answer E to your question.  But, me thinks you would then want to know why two H different SMBs reading the same data would present it to the applicationE differently.  Good question.  First step is to determine what the two  different SMBs are.   E There is also a chance that the SMBs are the same and in fact its the 3 application which is handling the data differently.   L Sorry I couldn't be more specific.  I was actually hoping someone else would( say they recognized what was going on...  
 Brad McCusker  OpenVMS Engineering    ------------------------------  % Date: Wed, 29 Jan 2003 21:38:27 +0100  From: Dirk Munk <munk@home.nl>- Subject: Alphaserver 4100 and Powerstorm 4D20 1 Message-ID: <dYWZ9.1715$Y9.237183@zwoll1.home.nl>   O I may be able to get a Alphaserver 4100. Don't know yet what type exactly, but  N I'm quite sure it does not have a decent graphics card. Just a simple one for  booting etc.  O Now I do have a PWS500 with a Powerstorm 4D20, and I was thinking about moving  I the 4D20 to the Alphaserver 4100. However it seems that the 4D20 is only  L supported in the 300 MHz version of the 4100, and not in the 533 or 600 MHz 	 versions.   P Can anyone tell me why that is, or has anyone had a 4D20 in a faster version of 
 the 4100 ?   ------------------------------  # Date: Wed, 29 Jan 2003 23:06:21 GMT # From: "John Smith" <a@nonymous.com>  Subject: Andrew...Oh Andrew...J Message-ID: <N7ZZ9.220639$pDv.218598@news04.bloor.is.net.cable.rogers.com>  2 http://www.eweek.com/article2/0,3959,840809,00.asp   January 22, 2003# Solaris Flaw Opens Door for Hackers  ....  C There is a serious vulnerability in several versions of the popular E Solaris operating system that enables a remote attacker to access any 8 file and obtain root privileges on a vulnerable machine.E The flaw affects Sun Microsystems Inc.'s Solaris 2.5.1, 2.6, 7, 8 and 6 9 running on Sparc-based or Intel Corp.-based servers.  E The vulnerability lies in a library service daemon known as the Kodak ; Color Management System. KCMS is a framework for developing C color-management systems. The KCMS server is used to enable library E functions to access profiles on remote machines. However, thanks to a C directory traversal condition in one of the server's procedures, an : attacker could retrieve any file on the vulnerable system.  B Specifically, the KCS_OPEN_PROFILE procedure is vulnerable to thisB attack, according to an advisory on the flaw released Wednesday byC Entercept Security Technologies, the San Jose, Calif., company that E discovered the problem. The CERT Coordination Center plans to release / a vulnerability note on the issue on Wednesday.   E Because the KCMS server runs with root privileges, an attacker who is E able to exploit this vulnerability would have complete control of the , machine and could access any file of choice.    F BTW...Nice to have you back...it was so quiet without you for so long, except for Bob C. ;-)    ------------------------------    Date: 29 Jan 2003 14:02:01 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen) F Subject: Re: Announcing a port of GnuPG V1.2 for OpenVMS Alpha and VAX3 Message-ID: <eefOAu7LrsQu@eisner.encompasserve.org>   b In article <3e38155a$1@news.si.com>, "Brian Tillman" <tillman_brian@notnoone.notnohow.com> writes:H >>        GnuPG for VAX and Alpha V1.2 is up and available for your use. > I > And another thing: if it's "open source", why the rigamarole of all the ( > registration crap and the secret URLs?  H Most Open Source licensing says they have to give you the source if theyI give you the binaries, and that they cannot restrict further distribution I by you. It does not restrict how they distribute the binary to you.  They D could choose to distribute only by CDROM and even charge a media and$ copying fee if they wanted to do so.  E I would presume they want to know to whom they have distributed, both K for statistical purposes and for letting recipients know of future changes.    ------------------------------  # Date: Thu, 30 Jan 2003 04:06:44 GMT 3 From: Vance Haemmerle <vance@toyvax.Glendale.CA.US> " Subject: Re: automatic screensaver5 Message-ID: <3E383459.4A4B30F1@toyvax.Glendale.CA.US>    Fred Kleinsorge wrote:   . > $def/sys/exec DECW$SCN_24PLANE_PSEUDOCOLOR 1 > K > This "should' get you the 8-bit pseudo color visual as the default (if my " > brain cells still are sparking).  ?   I wanted to let you know that this did indeed work.  Only the E default visual is pseudocolor, all the other visuals are still there.    -- Vance Haemmerle    ------------------------------  % Date: Wed, 29 Jan 2003 13:02:16 -0600 - From: John Brandon <John.Brandon@dalsemi.com> ' Subject: RE: Clustered V6.2 and V7.3-1? J Message-ID: <1809DA15308DD51180EE00508BCF21940DA165AA@misnts1.dalsemi.com>  J This message is in MIME format. Since your mail reader does not understand< this format, some or all of this message may not be legible.  ' ------_=_NextPart_001_01C2C7C8.F08C0510  Content-Type: text/plain;  	charset="iso-8859-1"   $ Am I still transmitting HTML format?  J 7) I disagree.  They are wanting to move the cluster applications from VAXB to Alpha.  No need to spend all this time in setting up a pristineL environment to have it whacked later - it is a waste of time and effort.  It@ also gives them incentive to get off the VAX and onto the Alpha.    K 10) I agree.  Nothing like scramble data.  Ask my other admin about that...        John Brandon VMS Systems Administrator  Dallas Semiconductor john.brandon@dalsemi.com 972.371.4172 wk  972.371.4003 fx        -----Original Message-----B From: young_r@encompasserve.org [mailto:young_r@encompasserve.org]* Sent: Wednesday, January 29, 2003 12:57 PM To: Info-VAX@Mvb.Saic.Com ' Subject: RE: Clustered V6.2 and V7.3-1?     J In article <1809DA15308DD51180EE00508BCF21940DA165A8@misnts1.dalsemi.com>,/ John Brandon <John.Brandon@dalsemi.com> writes:    > K > 7) I assume that you will not be sharing common files (SYSUAF, NETOBJECT, 6 > RIGHTSLIST, MAIL, etc.).  I suggest that you DO NOT. >   < 	This suggetion is not a good one.  Two separate SYSUAFs in 9 	a large user community can be a nightmare (passwords out A 	of synch, users change passwords on VAX but can't recall whether  they  B 	changed it on Alpha, find out it is in password history in Alpha, etc.  6 	There are hundreds of variations of nightmares here).  E 	Secondly, I did just that.  Shared SYS files VAX and Alpha, probably 9 	still that way (sizable cluster - 4 Alphas and 4 Vaxes).   ? 	I suggest just the opposite, share files - because you can and  	because it works well.    > F > 10) Force the Alpha Servers to serve the CI disk drives - forget the correct F > syntax, but will look for it.  Your file transfers will move faster. >   9 	He mentioned the Alphas are plugged into the same CI bus B 	as the VAXes.  This tells me two things.  The Alphas see the sameD 	disks the VAXes see, since that is the case ... they should be part: 	of the same cluster.  That or the intention is to see how8 	fast you can scramble a disk (of course, if not mounted3 	from the VAX I suppose you could mount them on the 4 	Alpha - and vice-versa).  Besides, the subject line 	says "Clustered."   				Rob   ' ------_=_NextPart_001_01C2C7C8.F08C0510  Content-Type: text/html; 	charset="iso-8859-1" + Content-Transfer-Encoding: quoted-printable   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">  <HTML> <HEAD>9 <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =  charset=3Diso-8859-1">@ <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
 5.5.2653.12"> - <TITLE>RE: Clustered V6.2 and V7.3-1?</TITLE>  </HEAD>  <BODY>  = <P><FONT SIZE=3D2>Am I still transmitting HTML format?</FONT>  </P>  E <P><FONT SIZE=3D2>7) I disagree.&nbsp; They are wanting to move the = I cluster applications from VAX to Alpha.&nbsp; No need to spend all this = I time in setting up a pristine environment to have it whacked later - it = F is a waste of time and effort.&nbsp; It also gives them incentive to =. get off the VAX and onto the Alpha.</FONT></P> <BR>  H <P><FONT SIZE=3D2>10) I agree.&nbsp; Nothing like scramble data.&nbsp; =' Ask my other admin about that...</FONT>  </P> <BR> <BR>  % <P><FONT SIZE=3D2>John Brandon</FONT> 3 <BR><FONT SIZE=3D2>VMS Systems Administrator</FONT> . <BR><FONT SIZE=3D2>Dallas Semiconductor</FONT>2 <BR><FONT SIZE=3D2>john.brandon@dalsemi.com</FONT>) <BR><FONT SIZE=3D2>972.371.4172 wk</FONT> ) <BR><FONT SIZE=3D2>972.371.4003 fx</FONT>  </P> <BR> <BR>  3 <P><FONT SIZE=3D2>-----Original Message-----</FONT> 8 <BR><FONT SIZE=3D2>From: young_r@encompasserve.org [<A =I HREF=3D"mailto:young_r@encompasserve.org">mailto:young_r@encompasserve.o=  rg</A>]</FONT>D <BR><FONT SIZE=3D2>Sent: Wednesday, January 29, 2003 12:57 PM</FONT>3 <BR><FONT SIZE=3D2>To: Info-VAX@Mvb.Saic.Com</FONT> A <BR><FONT SIZE=3D2>Subject: RE: Clustered V6.2 and V7.3-1?</FONT>  </P> <BR>   <P><FONT SIZE=3D2>In article =G &lt;1809DA15308DD51180EE00508BCF21940DA165A8@misnts1.dalsemi.com&gt;, = @ John Brandon &lt;John.Brandon@dalsemi.com&gt; writes:</FONT></P>   <P><FONT SIZE=3D2>&gt; </FONT>I <BR><FONT SIZE=3D2>&gt; 7) I assume that you will not be sharing common =   files (SYSUAF, NETOBJECT,</FONT>G <BR><FONT SIZE=3D2>&gt; RIGHTSLIST, MAIL, etc.).&nbsp; I suggest that =  you DO NOT.</FONT> <BR><FONT SIZE=3D2>&gt; </FONT>  </P>  C <P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>This = B suggetion is not a good one.&nbsp; Two separate SYSUAFs in </FONT>G <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>a large = 7 user community can be a nightmare (passwords out</FONT> I <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>of synch, = C users change passwords on VAX but can't recall whether they </FONT> G <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>changed = F it on Alpha, find out it is in password history in Alpha, etc.&nbsp; = </FONT> I <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>There are = 2 hundreds of variations of nightmares here).</FONT> </P>  H <P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>Secondly, =F I did just that.&nbsp; Shared SYS files VAX and Alpha, probably</FONT>E <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>still = 9 that way (sizable cluster - 4 Alphas and 4 Vaxes).</FONT>  </P>  H <P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>I suggest =; just the opposite, share files - because you can and</FONT> G <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>because =  it works well.</FONT>  </P>   <P><FONT SIZE=3D2>&gt; </FONT>E <BR><FONT SIZE=3D2>&gt; 10) Force the Alpha Servers to serve the CI = ' disk drives - forget the correct</FONT> G <BR><FONT SIZE=3D2>&gt; syntax, but will look for it.&nbsp; Your file = " transfers will move faster.</FONT> <BR><FONT SIZE=3D2>&gt; </FONT>  </P>  A <P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>He = < mentioned the Alphas are plugged into the same CI bus</FONT>F <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>as the =A VAXes.&nbsp; This tells me two things.&nbsp; The Alphas see the =  same</FONT> I <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>disks the = @ VAXes see, since that is the case ... they should be part</FONT>F <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>of the => same cluster.&nbsp; That or the intention is to see how</FONT>H <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>fast you =5 can scramble a disk (of course, if not mounted</FONT> H <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>from the =0 VAX I suppose you could mount them on the</FONT>G <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>Alpha - = 7 and vice-versa).&nbsp; Besides, the subject line</FONT> D <BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>says = &quot;Clustered.&quot;</FONT>  </P>  / <P>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = , &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =, &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =D &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>Rob</FONT> </P>   </BODY>  </HTML> ) ------_=_NextPart_001_01C2C7C8.F08C0510--    ------------------------------  # Date: Wed, 29 Jan 2003 19:04:31 GMT 3 From: hammond@not@peek.ssr.hp.com (Charlie Hammond) ' Subject: Re: Clustered V6.2 and V7.3-1? - Message-ID: <3BVZ9.56$8T1.2@news.cpqcorp.net>   5 In article <AVSZ9.1839$FS.130@twister.nyroc.rr.com>,  1 "Jeff Goodwin" <jgoodwin@maine.rrr-r.com> writes:   G >I'm working on a plan to migrate this cluster to Alpha systems running G >V7.3-1.  Due to the lack of support for many of the products currently J >running, I'd rather not try to upgrade the VAX systems to V7.3.  Instead,J >I'd rather cluster the OpenVMS VAX V6.2 and Alpha V7.3-1 systems and moveG >the older VAX packages to their newer Alpha counterparts/replacements.   K As I think you know, from HP's standpoint, the combination of OpenVMS V6.2  ? and V7.3-1 (Irrespective of VAX/Alpha issues) is not supported.   L What this means is that OpenVMS Engineering has NOT tested this combination.G Because of this, we simply do not know what problems you may encounter. G It is entirely possible that the OpenVMS cluster will form and "appear" E to be working O.K. -- only to have you find subtle problems some time ; later -- and these problems could include data corruptions.   H I would recommend that you DO NOT do this in a 24 x 7 production system.E Either upgrde the VAX systems to V7.3 or run two clusters -- one VAX   and one Alpha.   --  I       Charlie Hammond -- Hewlett-Packard Company -- Pompano Beach  FL USA H        (hammond@not@peek.ppb.cpqcorp.net -- remove "@not" when replying)J       All opinions expressed are my own and not necessarily my employer's.   ------------------------------    Date: 29 Jan 2003 13:14:18 -0600+ From: young_r@encompasserve.org (Rob Young) ' Subject: RE: Clustered V6.2 and V7.3-1? 3 Message-ID: <ZFvR7tnOb5Gg@eisner.encompasserve.org>   z In article <1809DA15308DD51180EE00508BCF21940DA165AA@misnts1.dalsemi.com>, John Brandon <John.Brandon@dalsemi.com> writes:L > This message is in MIME format. Since your mail reader does not understand> > this format, some or all of this message may not be legible. > ) > ------_=_NextPart_001_01C2C7C8.F08C0510  > Content-Type: text/plain;  > 	charset="iso-8859-1"  > & > Am I still transmitting HTML format?  C 	Yes.  Using Outhouse Express?  See groups.google.com , comp.os.vms  	on tips for turning it off.	    > L > 7) I disagree.  They are wanting to move the cluster applications from VAXD > to Alpha.  No need to spend all this time in setting up a pristineN > environment to have it whacked later - it is a waste of time and effort.  ItB > also gives them incentive to get off the VAX and onto the Alpha. >   ? 	Incentive?  They will be doing it.  Nothing pristine about it. A 	The migration will take a while.  Running both at the same time. > 	The example I gave... the only reason they were still running> 	VAXes is they didn't want to spend $60000 or so to upgrade anB 	application.  They eventually did.  They were/are running a mixedA 	architecture cluster for years.  This fella's migration may take $ 	many months (a good vacuous guess).  ; 	Running for several months is more incentive to use common 8 	SYS files.  It drastically cuts down on support issues.   				Rob    ------------------------------    Date: 29 Jan 2003 14:03:26 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen) ' Subject: RE: Clustered V6.2 and V7.3-1? 3 Message-ID: <oG$ZfHQyylar@eisner.encompasserve.org>   z In article <1809DA15308DD51180EE00508BCF21940DA165AA@misnts1.dalsemi.com>, John Brandon <John.Brandon@dalsemi.com> writes:L > This message is in MIME format. Since your mail reader does not understand> > this format, some or all of this message may not be legible. > ) > ------_=_NextPart_001_01C2C7C8.F08C0510  > Content-Type: text/plain;  > 	charset="iso-8859-1"  > & > Am I still transmitting HTML format?   Yes.   ------------------------------  % Date: Wed, 29 Jan 2003 17:58:03 -0400 0 From: JF Mezei <jfmezei.spamnot@vl.videotron.ca>' Subject: Re: Clustered V6.2 and V7.3-1? / Message-ID: <3E384E61.84D52DA1@vl.videotron.ca>    Jeff Goodwin wrote: H > V7.3-1.  Due to the lack of support for many of the products currentlyA > running, I'd rather not try to upgrade the VAX systems to V7.3.   L Depending on how long you intend to be keeping a mixed cluster, this may notK be a good idea. What happens when your Alpha moves to a version which is no 1 longer cluster-compatible with the old vax 6.2 ?    M For longer term coexistance, keeping both platforms at same versions may save , you a lot of mild headaches in the long run.    H What is the status of an old VAX in a cluster with a new alpha which mayM potentially have ODS-5 drives ? Would there be a different on whether the VAX  is at 7.2 or 6.2 ?  J One VERY quickly gets used to the features of 7.2 and above, such as pipe,J much more usable RECALL buffer etc. You'll find yourself constantly makingJ commands which won't work on 6.2 because you've gotten used to the 7.2 and above commands.     K If this is just for a transition period, then reading the release notes for N 7.3 (I think that the vms documentation web site has them) would probably give; you all the info you need to have for serious co-existance.    ------------------------------  % Date: Wed, 29 Jan 2003 18:00:22 -0500 , From: "Frank Sapienza" <sapienza@noesys.com>' Subject: Re: Clustered V6.2 and V7.3-1? , Message-ID: <b19mfc01t2t@enews3.newsguy.com>  I Why not bring in the new AlphaServer systems at V7.2-x, cluster that with J the VAX v6.2 systems (works fine), then when you're all happy and migrated upgrade the Alphas to v7.3?   : "Jeff Goodwin" <jgoodwin@maine.rrr-r.com> wrote in message. news:AVSZ9.1839$FS.130@twister.nyroc.rr.com... > K > The company I work for recently purchased a facility which has an OpenVMS B > VAX V6.2 CI cluster.  Some of the layered/3rd party products areG > discontinued.  Others that are still supported are vintage late 1980s  > versions.  > H > I'm working on a plan to migrate this cluster to Alpha systems runningH > V7.3-1.  Due to the lack of support for many of the products currentlyK > running, I'd rather not try to upgrade the VAX systems to V7.3.  Instead, K > I'd rather cluster the OpenVMS VAX V6.2 and Alpha V7.3-1 systems and move H > the older VAX packages to their newer Alpha counterparts/replacements. >  > Some other tidbits: 8 > - OpenVMS VAX systems are running all current VAX ECOsI > - No shadowing now, will want to MSCP serve some single member FC disks  from > Alpha to VAXJ > - The Alpha systems will have CIPCA cards and connect to the same CI bus as > the VAX systems  > - 7x24 operation > J > I'm looking for some input from people who may have some experience with( > these mixed versions running together. > 	 > Thanks,  > -Jeff  >  >  >    ------------------------------  # Date: Thu, 30 Jan 2003 00:21:53 GMT / From: "Jeff Goodwin" <jgoodwin@maine.rrr-r.com> ' Subject: Re: Clustered V6.2 and V7.3-1? : Message-ID: <Be_Z9.53744$7A4.6262785@twister.nyroc.rr.com>  F Thanks to every who's responded so far.  It appears that I didn't give$ enough information in my first post:  1 - I know that the configuration is not supported. B - The replacement systems will be ES45s, thus I need to run V7.3+.E - I've done multiple VAX to Alpha migrations.  I'm mainly looking for " someone who has the version match.L - The VAX systems are running, among other things, golden oldies such as RDBJ V4.2, Datatrieve V3.2, CDD V4.3, as well as the long obsolete ISIS messageL bus.  This in itself is not a supported configuration, thus my reluctance to upgrade OpenVMS.  7 "Frank Sapienza" <sapienza@noesys.com> wrote in message & news:b19mfc01t2t@enews3.newsguy.com...K > Why not bring in the new AlphaServer systems at V7.2-x, cluster that with L > the VAX v6.2 systems (works fine), then when you're all happy and migrated > upgrade the Alphas to v7.3?   > This would have been my first preference if not for the ES45s.   -Jeff    ------------------------------  % Date: Wed, 29 Jan 2003 21:59:05 -0500 2 From: rdeininger@mindspring.com (Robert Deininger)' Subject: Re: Clustered V6.2 and V7.3-1? L Message-ID: <rdeininger-2901032159070001@user-2ive10q.dialup.mindspring.com>  I In article <Be_Z9.53744$7A4.6262785@twister.nyroc.rr.com>, "Jeff Goodwin" ! <jgoodwin@maine.rrr-r.com> wrote:   G >Thanks to every who's responded so far.  It appears that I didn't give % >enough information in my first post:  > 2 >- I know that the configuration is not supported.C >- The replacement systems will be ES45s, thus I need to run V7.3+.   I I suspected something like that.  And if someone suggests trying pre-V7.3 ; on the ES45s, I can promise it won't work.  Save your time.   F >- I've done multiple VAX to Alpha migrations.  I'm mainly looking for# >someone who has the version match.   E There are many potential problems.  It might work, but it might not.  G Problems might only appear in certain configurations, so other people's ( experience might not be relevant to you.  J I don't think it is sane to try this on a production cluster.  You'll need? to dedicate some systems to a test environment before you start @ transitioning the production stuff.  That might mean you need toI temporarily deploy an extra VAX or two.  If you need additional VAXes for J testing, get them used and cheap (or free).  Try to negotiate a few monthsH of free temporary licenses for the VAXes as part of the ES45 purchase --. it wouldn't cost HP anything to provide these.  E To minimize run time needed for testing, read ALL the intervening VMS H release notes carefully, and read the notes for the ECO kits which mightI have anything to do with clustering and communications.  This is a lot of J research, but it is probably cheaper than "just trying it" on a production system.   I If most of the applications will end up on the alphas, do you really need E to include the Vaxes in the cluster?  DECnet, DFS (or NFS), DQS, etc. E would give you resource sharing beyond the boundary of a cluster, and I might be sufficient for the few applications that remain on the VAXes.  A I V6.2 VAX networked, but not clustered, with V7.3-1 alphas, does not offer / as many compatibility questions to worry about.    ------------------------------    Date: 29 Jan 2003 15:53:03 -0800. From: spamsink2001@yahoo.com (Alan E. Feldman)0 Subject: Re: cron in LINUX/UNIX, what in OpenVMS= Message-ID: <b096a4ee.0301291553.6c400a91@posting.google.com>   s spamsink2001@yahoo.com (Alan E. Feldman) wrote in message news:<b096a4ee.0301291005.7e1a602e@posting.google.com>...  [...] @ > Another thing to watch out for with SUBMIT/AFTER is if you use > something like > 0 >     $ SUBMIT/AFTER="''SOME_TIME_SYMBOL'"  .... > G > If that symbol happens to be null for some reason, the job will start E > right away! Probably not what you want, especially since this would G > most likely be caused by a bug in your DCL command procedure. So make  > sure that symbol isn't null."     - Of course! Why didn't I think of this before?   +     $ SUBMIT/AFTER=&SOME_TIME_SYMBOL .... !    Example:   $ SH SYM NOSUCH = %DCL-W-UNDSYM, undefined symbol - check validity and spelling # $ SUBMIT /AFTER=&NOSUCH NOTHING.COM > %DCL-W-VALREQ, missing qualifier or keyword value - supply all required values  $   + Yet another use for ampersand substitution!   C [Sorry for replying to myself. Some of you see that as bad form. It D never bothers me when others do it, though, and I don't see anything wrong with it.]    Disclaimer: JMHO   &-) Alan E. Feldman    ------------------------------  # Date: Thu, 30 Jan 2003 00:31:42 GMT L From: winston@SSRL.SLAC.STANFORD.EDU ("Alan Winston - SSRL Admin Cmptg Mgr")0 Subject: Re: cron in LINUX/UNIX, what in OpenVMS6 Message-ID: <00A1AB3C.5EEA3EAC@SSRL.SLAC.STANFORD.EDU>  h In article <CYSZ9.2591$c6.2671@bos-service2.ext.raytheon.com>, Chris Olive <nospam@raytheon.com> writes: >Rob Young wrote:  > J >I wonder if Kronos is what I was thinking of, though again, I could have F >sworn it was just called "CRON"...  Anyway, no way for me to know at  >this point.  F I have a C-language cron which goes down to 1-minute resolution.  BeenG using it for years.  It seems to have originated in an article in some  J HP-specific magazine, but it got ported to VMS.  When I first put it in I I needed to spend a couple of minutes thinking; the assumption seemed to be J that the cron$lib directory where everybody's cron entries would be placedJ were going to be world-writeable, which was wide open for anybody to writeK entries to be executed on their behalf by system.  So I ended up installing I the crontab program with privileges (subsystem identifiers not yet having J been invented at that time) and making the cron$lib directory not writable1 without privileges, which seemed reasonably safe.   H I'm not sure where I originally got the program, though.  It was called 3 mycron.  I hear KRONOS is good but haven't used it.    -- Alan   O =============================================================================== 0  Alan Winston --- WINSTON@SSRL.SLAC.STANFORD.EDUM  Disclaimer: I speak only for myself, not SLAC or SSRL   Phone:  650/926-3056 M  Paper mail to: SSRL -- SLAC BIN 99, 2575 Sand Hill Rd, Menlo Park CA   94025 O ===============================================================================    ------------------------------  % Date: Wed, 29 Jan 2003 21:21:57 -0500 2 From: rdeininger@mindspring.com (Robert Deininger) Subject: Re: ds25 L Message-ID: <rdeininger-2901032121590001@user-2ive10q.dialup.mindspring.com>  9 In article <3E380281.20008@ceris.purdue.edu>, Chuck Aaron   <caaron@ceris.purdue.edu> wrote:   >Hello,  > F >Is anyone running ds25's and could you provide me your comments about? >it service. I have some ds20e's now and thinking about a ds25.   F I have used some DS25 systems, and find them quite reliable and plentyD fast.  If you have particular I/O requirements, check the QuickSpecsH carefully; there are some slot restrictions, and some older adapters may not be officially supported.; IIRC, the minimum VMS version is V7.3-1 plus some ECO kits.   - The DS25 is in most respects half of an ES45.    ------------------------------  # Date: Wed, 29 Jan 2003 20:25:13 GMT # From: "John Smith" <a@nonymous.com> , Subject: Re: EV7 / EV8 intellectual propertyJ Message-ID: <JMWZ9.499786$F2h1.74692@news01.bloor.is.net.cable.rogers.com>  1 "Shane Smith" <ssmith@icius.com> wrote in message * news:01C2C77E.E22864E0@sulfer.icius.com...7 > >"Carl Perkins" <carl@gerg.tamu.edu> wrote in message * > >news:29JAN200303373999@gerg.tamu.edu..., > >> "John Smith" <a@nonymous.com> writes...7 > >> }http://www.theregister.co.uk/content/3/28947.html  > >> }E > >> }The EV7 runs at 1GHz and 1.15GHz and only includes one core per  > >chip.; > >> }It was designed by the old Digital Alpha chip team in  Shrewsbury, F > >> }Massachusetts, which will eventually be moved over to Intel. The > >chip @ > >> }maker last year bought the Alpha team and its intellectual property > >as A > >> }part of the Alpha sunsetting that Compaq announced prior to  being ! > >> }acquired by HP last spring.  > >> } > >> }6 > >> }So, what does HP own if this article is correct? > >>; > >> The article is not correct. Intel didn't buy the Alpha 
 "intellectual F > >> property" - they bought a non-exclusive license to all of it. So, in@ > >> essence, they bought the right to use all the Alpha related patents D > >> and all other information about it, but HP actually owns it and is > >free D > >> to use it themselves and to license it to anyone else that they feel > >like = > >> licensing it to (at the possible risk of anoying Intel).  > > F > >That's what I thought. So I suppose HP could tell Intel to choke on. > >Itanic II and partner with AMD/IBM instead. > E > Actually I think there might be an even more enjoyable (and just as B > unlikely) option. Wouldn't HP have inherited DEC's right to make Intel C > produce Alphas for them? I don't know the details of that ruling,  but ifB > it wasn't restricted to a single generation HP could really make Intel E > mad. Team up with IBM to finish the EV8 design, then force Intel to D > produce chips that left their beloved Itanic in the dust... Sorry, I'll > get back to reality now.    B I may be wrong on this, but isn't IBM's copper process better than what Intel currently has?    ------------------------------  % Date: Wed, 29 Jan 2003 14:18:13 +0000 ' From: Andrew Harrison SUNUK Consultancy ; Subject: Re: EV7 hits, blows away Sun, IBM, 2-3x VMS gains! . Message-ID: <3E37E2A5.7010805@nospamn.sun.com>    Well this all might be true but.  8 1.	Only if you think that SPECint and SPECfp are usefull8 	measures that will allow you to predict the performance 	of your application.   ; 	Sadly as we know that particularly when you happen to have 1 	an AlphaServer neither are likely to be usefull.   : 2.	Only if you don't understand how the omp NUMA directive6 	might make the STREAMS benchmark run on a NUMA system
 	like Marvel.    Regards      Bob Ceculski wrote: < > HP's AlphaServer GS1280 Launch: A MARVELous Development=20G > Posted by Terry Shannon (Sunday January 19 2003 @ 03:51PM EST) [ ]=20u > =20 ? > It's been a long time coming, but the enterprise server firsth@ > discussed a decade ago at Digital Equipment Corporation is nowD > reality. As predicted in SKHPC=97in which we've been writing aboutJ > Marvel for nearly two years now=97HP today opened a barrel of whoop-ass=  G > on competitive enterprise server vendors with the public debut of theaG > HP AlphaServer GS1280 "Marvel" system family. The first three members?F > of the Alpha EV78-inside follow-on to the AlphaServer GS320 WildfireD > enterprise server have been up and running in nearly 10 field testB > sites worldwide for nearly a year, and two through 16-way MarvelD > systems are now ready for prime time. Here's SKHPC's first take onJ > HP's evolutionary=97and some would argue revolutionary=97replacement fo= r  > the GS320 family.h >=20 > Evolution and Revolution=20r >=20? > In fact, the new HP AlphaServer GS1280 family represents bothsG > evolution and revolution. Indeed while these new systems represent aneB > evolutionary follow-on to the GS320 family, the AlphaServer 1280C > incorporates three major technology revolutions which will impose F > minimal customer disruption. First among these is "built-in SMP." InC > an effort to build a platform that delivers industry-leading appsrG > performance and far more scalable performance than its predecessor or D > competitive products, HP aggregated all the constituents of an SMPC > system onto a single Alpha EV78 CPU. These components include thetA > memory controller, the L2 cache controllers, and interprocessor " > communications and coordination. >=20C > Around the EV78 processor, HP developed an environment it calls alA > switch-less meshed architecture that dispenses with much of theoA > infrastructure, complexity, and expense of incumbent enterprisegC > servers. By interconnecting dual-processor modules with dedicatedA? > memory and I/O directly to one another, HP managed to deliver-H > virtually truly linear scalability because there's nothing between oneH > processor module and another except a cable. In addition, HP engineersE > did significant work on the switchless architecture to fault hardene; > the environment to make it even more robust and reliable.h >=20 > Simplicity =3D Stability >=20H > The "Lego Block" approach to GS1280 design provides a number of uniqueA > benefits to customers. System reliability dramatically improvedhB > through simplicity: since a single EV78 module contains multipleB > components that existed as discrete entities on GS320 systems, aE > GS1280 system contains fewer components than its predecessor. Fewer B > components translate to fewer opportunities for failure, hence a@ > GS1280 system provides a very significant increase in inherentH > single-system reliability. What's more, key components including CPUs,H > redundant power supplies, fans, and I/O modules are hot-swappable, andE > an advanced diagnostics subsystem not only monitors virtually everyiH > aspect of system performance, but provides prefailure information thatE > allows customers to take components offline and replace them beforef > they actually fail.l >=20? > The GS1280 family also sports optional RAID memory, a conceptnB > pioneered by HP's ISS group in IA-32-based systems. Based on theB > architectural simplicity of the AlphaServer GS1280 alone, HP hasF > experienced a 15 to 30 percent improvement in MTBF in the new system@ > when compared with the more complex AlphaServer GS320. The newF > instrumentation, console, and RAS features further contribute to the@ > stability and reliability of the GS1280 family. Additional RASA > features will be exploited by future versions of Tru64 UNIX and  > OpenVMS opating systems. >=20 > Fast and Frugal Scale-Up >=20D > Finally, HP is basing the AlphaServer 1280 family on several basicH > building block modules that provide a foundation for building scalable? > systems with reusable components. Significantly, these shared F > components mean that customers need not purchase more infrastructureG > than they need, nor will they confront daunting upgrade costs as theyeC > grow their GS1280 systems to meet growing demand. For instance, asD > customer can start with the smallest GS1280 system (and its modestF > entry price) and grow it to the largest supported configuration in aG > modular way that protects the vast majority of initial investments byvC > carrying all of the core products and modules and building blocks,A > forward. At the same time, the GS1280 is binary-compatible withuG > incumbent Alpha systems, rendering the system upgrade path smooth and. > free of pitfalls.g >=20 > Benchmarks Eclipse Sun, et ale >=20A > The new HP AlphaServer GS1280 systems have established industryaA > leadership in both the SPEC_rate2000 and the STREAM benchmarks,sC > demonstrating their outstanding "whole" systems performance and acJ > unique ability to scale linearly in performance=97and nearly linearly i= nhH > price as additional processor modules are added. While cache-intensiveG > apps will demonstrate little improvement over EV68-based systems (theiD > EV7 CPU uses the EV68 core and contains a 7-way associative 1.75MB> > cache while the latest EV68 sports a 32MB cache), real-world? > application performance benchmarks shine on the GS1280, as docD > SPEC_rate2000 and STREAMS numbers. In the STREAMS benchmark, whichD > measures sustainable memory bandwidth for computer systems, the HPA > AlphaServer GS1280 demonstrated five to 10 times greater memoryCG > bandwidth than comparable enterprise systems from IBM and Sun. Due todC > the new system architecture, memory bandwidth increases as GS1280gA > systems get larger: when compared with a 4-CPU GS320, a GS 1280hE > quadprocessor offers ~40 percent greater memory bandwidth. On 8-wayhB > systems, the GS1280 offers ~64 percent greater bandwidth, and onD > 16-way configurations, the GS1280 delivers ~70 percent more memory* > bandwidth than does an equivalent GS320. >=20 > Superlative SPEC_rate ResultsT >=20D > The GS1280's superlative SPEC_rate 2000 results go well beyond theH > leadership performance of today's AlphaServer systems, particularly inB > technical computing where the benefits of the systems' technicalB > innovations are well demonstrated with nearly 100 percent linearB > scalability from one to 32 processors. The vastly reduced memory@ > latency of the AlphaServer GS1280 is a key contributor to thisH > substantial improvement. As further proof points, HP plans to announceD > SAP and Oracle application benchmarks in the coming months. (SKHPC> > expects to see 35-50 percent performance gains on Tru64 UNIXD > applications.) Initial reports from field test sites indicate thatG > early adopters are absolutely delighted with the GS1280 system. Tru64rC > UNIX customers are extremely pleased. OpenVMS customers are blownbC > away: for example, Cerner Corporation saw a threefold increase ineG > OpenVMS performance during its Marvel field test; the Bank of AustriasF > saw VMS performance double on an HP AlphaServer GS1280 equipped withE > eight CPUs, and a 16-way system showed a performance gain of 150 to-4 > 200 percent over an equivalently-configured GS320. >=20 > Customer Assurance Ensured >=20H > The new HP AlphaServer GS1280 is one of the cornerstones of HP VP RichH > Marcello's RetainTrust Program. While previously reported in detail inH > SKHPC, the RetainTrust program was formally unveiled during today's HPH > AlphaServer GS1280 launch. With the initial eight to 16-way members ofF > the HP GS1280 family available today, smaller systems in March, thenG > 32-way systems in midyear and 64-way behemoths by the end of the yeariH > (with several per-processor memory capacity increases slated to appearH > this year), not to mention new releases of OpenVMS and Tru64 UNIX thatG > better exploit the GS1280, Alpha customers should feel confident that1D > HP will be with them for the long haul. In addition, HP is alreadyE > sampling prototype EV79 parts. EV79-Inside GS1280 systems should berF > available in late 2004, thus providing another performance boost forG > OpenVMS and Tru64 customers, and increasing the length of their Alpha1G > to IPF transition window. As things stand today, Alpha GS1280 systemsnF > will be sold through at least 2006 and supported for at least half aA > decade thereafter. Based on past experience with PDP-11 and VAXwB > systems, SKHPC wouldn't be surprised to see GS1280 systems stillG > available well into the second half of the decade. Accordingly, whilehF > OpenVMS and Tru64 users ultimately will migrate to OpenVMS-on-IPF orH > to the Consolidated Enterprise UNIX on IPF, the AlphaServer GS1280 andD > its EV79-based successor remain very safe bets, and should be moreG > than capable of meeting customer needs until such time as they chooserD > to migrate to HP's next-generation IPF systems. So yet again, HP'sG > "promises made are promises kept" strategy remains in play. As one HP0F > executive said, "If there's a problem with application compatibilityD > or functionality on the GS1280, it's HP's problem, not the ISV's." >=20" > Order Quick, They're Going Fast! >=20C > The high-end AlphaServer GS1280 is already shipping in eight- andgD > 16-way configurations sporting 1.15 GHz Alpha EV78 processor-basedF > systems. U.S. list prices for this highly-expandable system start atF > $117K for a two-CPU configuration. GS1280 systems with 32 processorsH > should be available by the middle of the year and 64-processor systems= > are slated to ship by the end of the year. AlphaServer ES80SG > departmental systems with up to eight 1GHz Alpha EV78 processors willr: > start shipping in March with prices starting at $81K forG > dual-processor configurations (by comparison, equivalently-configured H > incumbent GS80 systems cost about 20 percent more.) The ES47 workgroupD > systems also are available now and come in two and four 1GHz AlphaG > processor configurations with U.S. list prices starting at $39.7K for H > a two-processor tower system, just slightly higher than the price of aD > dual-processor DS25 system. An ES47 rackmount system with two CPUsA > goes for about $64.4K, similar to the price of a dual-processoraH > AlphaServer ES45. Quadprocessor ES47 rackmount systems cost from $133K > to $137K.  >=20( > Pricing Pressure... on the Competition >=20B > The price differential is even more significant in larger systemH > configurations, a marketing decision that should attract new customersD > while causing major headaches at IBM and Sun Microsystems. Case inH > point: when compared with an eight-processor GS320, an eight-processorB > GS1280 is priced 60 percent lower than its predecessor; a 16-CPUE > GS1280 is yours for 28 percent less than a 16-processor AlphaServerC > GS320. >=20! > An Enterprise Server Done Right> >=20C > SKHPC has been tracking high-end systems from DEC, Compaq, HP and H > their rivals since well before the October 1984 debut of the VAX 8600.F > In comparison with previous VAX and Alpha offerings ranging from theD > VAX 8800 and 9000 through the TurboLaser and Wildfire systems, the> > AlphaServer GS1280 represents a quantum leap forward in manyE > dimensions. In SKCHPC's opinion, the AlphaServer GS1280 is the best F > enterprise server to be fielded by any systems vendor, and we expectE > customer adoption rates will reflect the superiority of HP's latestTH > Alpha-Inside product offering for quite some time to come. In summary,F > HP's latest entry in the enterprise systems derby is sure to concern= > competitors while delighting customers. And as usual, SKHPC3> > subscribers will be provided with more details on the new HPG > AlphaServer GS1280 system in future issues of this subscription-based 
 > newsletter.3 >=20D > (c) 2003 by Terry C. Shannon, IT Consultant and Publisher, Shannon > Knows HPCo >=20H > Press Inquiries through 22 January: 505-400-8513 (cellular) 23 January! > and beyond 505-792-2324 (voice)B >=20E > Want ALL the details on Marvel and future AlphaServer and Superdomet6 > systems? Easy: subscribe to SKHPC. Drop me a line at5 > tshannon3@comcast.net for subscription information.E   ------------------------------  # Date: Thu, 30 Jan 2003 01:14:51 GMTr4 From: robert.sundstrom@upright.se (Robert Sundstrm)1 Subject: GNU PATCH from OpenVMS freeware archivesa. Message-ID: <b19u3g$925$1@yggdrasil.utfors.se>   Hello everybody.J A few years ago I downloaded the Gnu Patch port from the OpenVMS freeware L archives. It has been working well until my shop upgraded to VMS 7.3, it is 8 now frequently crashing in the quotearg_buffer routine.   O Unfortunately, quite a few of the source files of that archive are corrupt one ;L way or the other. Can anyone point me in a direction where I can find fresh . source files, and particularly a DESCRIP.MMS ?   ------------------------------    Date: 29 Jan 2003 14:25:32 -0600+ From: young_r@encompasserve.org (Rob Young)a4 Subject: groups.google.com tip (Was: Re: memoryleak)3 Message-ID: <3g35csDZqdPD@eisner.encompasserve.org>l  m In article <3e3823cc$0$83835$edfadb0f@dtext01.news.tele.dk>, "Jesper Naur" <jesper.naur@post.tele.dk> writes:;- > If you are programming in C, take a look at  > N > http://groups.google.com/groups?q=jesper+naur+memory+leak+group:comp.os.vms&E > hl=en&lr=&ie=UTF-8&selm=8hmfsc%24rt3%241%40news.inet.tele.dk&rnum=1  > 7 > The technique can also be adapted to other languages.n >   : 	Here is the tip, click on "Original Format" on the right. 	The URL then becomes:  W http://groups.google.com/groups?selm=8hmfsc%24rt3%241%40news.inet.tele.dk&output=gplaing      9 	Two things.. the format is sweet and the URL is shorter.T  2 	To see thread context, rip off the &output=gplain  I http://groups.google.com/groups?selm=8hmfsc%24rt3%241%40news.inet.tele.dk;  < 	Added bonus here is it fits in less than 80 columns and you& 	don't have to worry about line wraps.   				Rob/   ------------------------------    Date: 30 Jan 2003 05:48:56 +0800, From: Paul Repacholi <prep@prep.synonet.com>* Subject: Re: High hit rate VMS Web server?- Message-ID: <87lm13lj93.fsf@prep.synonet.com>F  % "John Smith" <a@nonymous.com> writes:a  ; > "Paul Repacholi" <prep@prep.synonet.com> wrote in messagen) > news:87d6mg3mtn.fsf@prep.synonet.com...e  > > > Sadly, ACMS et all is no longer `in the family' to be well' > > intergrated for this sort of thing.;  7 > What am I missing here vis. your comments about ACMS?   ,< > http://www.openvms.compaq.com/commercial/acms/44_info.html  < I know ACMS is still around. I was thinking of the extra run? around  that there would be getting Oricle and hp to coordinate = doing new stuff to make ACMS a good way to drive a web servera rather than terminals.  3 Seeing that stuff to Oricle was a huge mistake IMO.s   -- ;< Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.n@                                              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: Wed, 29 Jan 2003 23:10:12 GMT;# From: "John Smith" <a@nonymous.com>s* Subject: Re: High hit rate VMS Web server?J Message-ID: <obZZ9.220645$pDv.129133@news04.bloor.is.net.cable.rogers.com>  9 "Paul Repacholi" <prep@prep.synonet.com> wrote in message-' news:87lm13lj93.fsf@prep.synonet.com...3' > "John Smith" <a@nonymous.com> writes:r >.= > > "Paul Repacholi" <prep@prep.synonet.com> wrote in message + > > news:87d6mg3mtn.fsf@prep.synonet.com...t > @ > > > Sadly, ACMS et all is no longer `in the family' to be well) > > > intergrated for this sort of thing.  >I9 > > What am I missing here vis. your comments about ACMS?m >u> > > http://www.openvms.compaq.com/commercial/acms/44_info.html >t> > I know ACMS is still around. I was thinking of the extra runA > around  that there would be getting Oricle and hp to coordinatea? > doing new stuff to make ACMS a good way to drive a web serverr > rather than terminals.   That would be interesting.    5 > Seeing that stuff to Oricle was a huge mistake IMO.6  F No kidding. But Digital/Compaq had a habit of selling the crown jewels! at fire sale prices, didn't they?i   ------------------------------  # Date: Wed, 29 Jan 2003 21:20:40 GMTo1 From: LESLIE@JRLVAX.HOUSTON.RR.COM (Jerry Leslie)i@ Subject: How To Turn Off HTML (Outlook, Outlook Express, et.al.); Message-ID: <IAXZ9.43026$267.1596191@twister.austin.rr.com>e Keywords: turn,off,htmle  D This site has instructions for inactivating HTML in Outlook, Outlook3 Express, Outlook 2000, Netscape Communicator, etc.:r  ,      http://www.betips.net/etc/evilmail.html%      Why HTML in E-Mail is a Bad Idea   6 this site also contains reasons for inactivating HTML:  2      http://www.american.edu/cas/econ/htmlmail.htm      HTML Email: Turn It Off!p    C It's a hard job to get new internet users who say that nobody else pD complains about their HTML emails, and actually want to send emails  using all of the "goodies".p  D They need a worm that sets their modem speed to 1200 baud when their system downloads HTML emails.c      2 --Jerry Leslie   (my opinions are strictly my own)9   Note: leslie@jrlvax.houston.rr.com is invalid for emailn  =   "Outlook is a piece of software for giving remote access by 0    email to all the bugs in Internet Explorer !"   ------------------------------  # Date: Wed, 29 Jan 2003 23:01:26 GMTr# From: "John Smith" <a@nonymous.com>y5 Subject: HP has a chance to buy some software (rumor)sJ Message-ID: <a3ZZ9.220635$pDv.116259@news04.bloor.is.net.cable.rogers.com>  2 http://www.eweek.com/article2/0,3959,838444,00.asp  D Several tattlers told Spencer that BEA Systems may be putting itself> on the block-or is at least dropping hints to that effect. TheD tipsters assumed that the rumors are an effort by the infrastructureF software maker to raise its stock price or an attempt to see if anyone has an interest.    E HP can buy back the software Digital sold to BEA and control some keyuC software for VMS once again.  Maybe they'll buy Rdb from Oracle tooi ;-)    ------------------------------  # Date: Wed, 29 Jan 2003 23:15:04 GMT 9 From: Alan Adams <alan.adams@orchard-way.freeserve.co.uk>i4 Subject: Re: Installing second ethernet card (DE500)? Message-ID: <2a199fbc4b.Alan.Adams@orchard-way.freeserve.co.uk>m  ) In message <b18pmb$6nh$1@kermit.esat.net>.>           "Tom Wade" <t.wade@vms.eurokom.removespam.ie> wrote:   >  > Greetings, > G > I am trying to install a second ethernet card (DE500) into a PS 433au- > running OpenVMS 7.3. > . > I installed the card into a vacant PCI slot. > I > The SRM console sees the device as EWB0 in SHOW DEVICE and SHOW CONFIG.y > M > VMS sees the device as EWB0.  EWB2 (no owner) and EWB4 (DNS$ADVER) also are5' > visible. SHOW DEVICE shows no errors.h > 5 > The DNS$ADVER log file has a DEVINACT error logged.o > J > Starting DECnet line using create csma-cd station csmacd-2 communicationK > port = ewb seems to work, but the line shows "initializing" indefinitely.1  J Are these two cards on the same ethernet segment, and both running Decnet?H If so, and you are using PhaseIV compatible addressing, it won't work. II think it can be made to work if only PhaseV addressing is used (i.e. OSI,oK not Decnet area.node format). This is because with PhaseIV compatible mode,5L the ethernet address of the card is changed to AA-00-04-00-xx-yy, where yyxxI is the Hex version of the phaseIV address. Thus both cards try to use theo same Ethernet address.  L LAT and LAVC should both work on dual cards, provided Decnet hasn't set both to the same address.   > = > Multinet and LAT both report DEVINACT when trying to start.o > L > LEDs on both card and hub are normal (10BaseT mode set explicitly in SRM). > H > All of this points to a faulty card, but a packet sniffer detects LAVCM > packets coming from the card (only the sniffer and the host in question area? > on the hub, and the source address identifies the new DE500).d > K > Was I correct in assuming that there is no manual adjustment to SRM after I > installing the card ?  The DEC manual that came with the card describesrM > diagnostics and drivers for NT, but doesn't mention VMS (except in the listb5 > of trademarks).  Anything else I should have done ?s > 
 > Many thanksj > J > ------------------------------------------------------------------------K > Tom Wade    | EMail: tee dot wade at eurokom dot ie (all domain mailers). I > EuroKom     | X400:  g=tom;s=wade;o=eurokom;p=eurokom;a=eirmail400;c=ie-( > 30, Dale Rd | Tel:   +353 (1) 278-7878( > Stillorgan  | Fax:   +353 (1) 278-78795 > Co Dublin   | Disclaimer:  This is not a disclaimereB > Ireland     | Tip:         "Friends don't let friends do Unix !" >  >  >    -- e
 Alan Adams& alan.adams@orchard-way.freeserve.co.uk http://www.nckc.org.uk/n   ------------------------------    Date: 29 Jan 2003 14:09:52 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen)s Subject: Re: memoryleak13 Message-ID: <KIEv$FSKomun@eisner.encompasserve.org>f  g In article <c8a98246.0301291034.5ad98022@posting.google.com>, rallykarro@hotmail.com (karolina) writes:t > Hi,c > E > I have a problem with a program on VMS that are leaking memory. How9G > can I easy get hold of my leak. I tried lib$show_vm but realised thatoF > it doesn't give me anything. I read at compaq that this was obsolete
 > as well. > E > Is there any replacement for lib$show_vm or is there any thing like7! > "purifier" running on OpenVMS??r  . Presuming a relatively current version of VMS,  9 use the Heap Analyzer, documented in the Debugger manual.p   ------------------------------  % Date: Wed, 29 Jan 2003 21:34:57 -0500 2 From: rdeininger@mindspring.com (Robert Deininger) Subject: Re: memoryleakoL Message-ID: <rdeininger-2901032134580001@user-2ive10q.dialup.mindspring.com>  = In article <c8a98246.0301291034.5ad98022@posting.google.com>,t( rallykarro@hotmail.com (karolina) wrote:   >Hi, >iD >I have a problem with a program on VMS that are leaking memory. HowF >can I easy get hold of my leak. I tried lib$show_vm but realised thatE >it doesn't give me anything. I read at compaq that this was obsoleteJ	 >as well." >gD >Is there any replacement for lib$show_vm or is there any thing like  >"purifier" running on OpenVMS??  H Do you mean LIB$SHOW_VM_ZONE?  AFAIK, LIB$SHOW_VM_ZONE is not obsolete. J Public VMS components almost never go away.  Sometimes they are supersededJ by newer, more functional components, but the old stuff remains available.  J There is a chapter about memory management in the VMS programming concepts% manual.  It has a very good overview.   A There are some extensive hints available for debugging VMS memory,J management problems.  IIRC, these are either in the OpenVMS FAQ, or in theJ Ask the Wizard section at the VMS web site.  You should have the FAQ handy for reference in any case.  J And as someone else mentioned, there is the Heap Analyzer, part of the VMS	 debugger.f   ------------------------------  % Date: Wed, 29 Jan 2003 21:10:13 -0500s& From: Mickalide <mickalide@empire.net> Subject: Re: Moving CMSe) Message-ID: <3E388985.2080206@empire.net>   D The error you are getting has to do with ODS5  file structure.  The I library you are restoring  was created  before extended filename support eF was added to CMS.  You need to check to see  how CMS was installed on E the target system. I am not sure when you install CMS on an ODS5 diskrH if  extended filename support is automatically selected.  You can check  the release notes for 4.1@  about extended filename support.     -Jim-d         David Gray wrote:    >Greetings all,y >oK >Having problems with CMS libraries that have been moved from an Alpha 4000m >server (CMS Version V3.9-2) tot) >an Alpha Server ES45 (CMS Version V4.1).e >pJ >Using a VMS saveset backup the files have been moved to the new platform.% >Using the command $CMS SHOW LIB/FULLeL >I have verified CMS is looking in the correct place for the library but the$ >reference copy device is incorrect. >a
 >For example:' >a, >On the old server the reference copy was...9 >    REFERENCE_COPY directory is DISK$DRIVE2:[XPS_REFLIB]r >b4 >On the new server the reference copy needs to be...1 >    REFERENCE_COPY directory is JD4:[XPS_REFLIB]m >tG >The CMS command $CMS MOD LIB /REFERENCE=JD4:[XPS_REFLIB] throws up thed >following error.u# >CMS> mod lib /ref=JD4:[HLP_REFLIB]  >_Remark: New location: >%CMS-E-NOMODIFY, error modifying library JD4:[HLP_CMSLIB]I >-CMS-E-NOEXTENDEDREF, extended filenames are not available for referenced >copy directory  >eJ >How can I change the device for this reference copy lib without resorting >to... >r( >    $ Define/sys DISK$DRIVE2:      JD4: >5 >? >sM >$CMS VERIFY obviously throws up lots of errors regarding the reference_copy.e > > >Also tried modding the lib using the /extended_file qualifier$ >CMS> mod lib /extended_filenames "": >%CMS-E-NOMODIFY, error modifying library JD4:[HLP_CMSLIB]8 >-CMS-E-NOEXTENDED, extended filenames are not available >c >Thanks in advance,i
 >    Dave. >d >OpenVMS  is V7.3-1f >s >f# >Your CMS library list consists of:a >a >JD4:[HLP_CMSLIB]e >    and containsV >s >        868 elementst >          0 groupse >          1 class >          0 reservationse$ >          0 concurrent replacements >          0 reviews pending >o9 >    REFERENCE_COPY directory is DISK$DRIVE2:[HLP_REFLIB]o >l5 >    Library attributes are:  /Revision_time=Originalo) >                             /Concurrent-% >                             /Nokeep93 >                             /Noextended_filenamesm1 >                             /Long_variant_names, >a >n >  V >    ------------------------------  % Date: Wed, 29 Jan 2003 13:10:21 -06000- From: John Brandon <John.Brandon@dalsemi.com> + Subject: My e-mail sucks and I owe you beeroJ Message-ID: <1809DA15308DD51180EE00508BCF21940DA165AB@misnts1.dalsemi.com>  J This message is in MIME format. Since your mail reader does not understand< this format, some or all of this message may not be legible.  ' ------_=_NextPart_001_01C2C7CA.1207AF90y Content-Type: text/plain;l 	charset="iso-8859-1"   J I am having MS Exchange and client problems - I am sending as "Plain text"% and the server refuses to believe me.s My NT admins could care less.e1 So I will look for better ways to resolve this.     K I am told that it is working now and that does not get me out of buying thei beer.d  . I guess I am buying the beer (or coffee) then.   Londoner 14930 Midway Roadr Addison, TX  75001 u   This Friday at 5:15e   Find me if you can.s   John Brandon VMS Systems Administratorr Dallas Semiconductor john.brandon@dalsemi.com 972.371.4172 wk  972.371.4003 fxt      ' ------_=_NextPart_001_01C2C7CA.1207AF90r Content-Type: text/html; 	charset="iso-8859-1" + Content-Transfer-Encoding: quoted-printable   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">S <HTML> <HEAD>9 <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =c charset=3Diso-8859-1">@ <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
 5.5.2653.12"><1 <TITLE>My e-mail sucks and I owe you beer</TITLE>C </HEAD>e <BODY>  E <P><FONT SIZE=3D2 FACE=3D"Arial">I am having MS Exchange and client =aB problems - I am sending as &quot;Plain text&quot; and the server = refuses to believe me.</FONT>aF <BR><FONT SIZE=3D2 FACE=3D"Arial">My NT admins could care less.</FONT>E <BR><FONT SIZE=3D2 FACE=3D"Arial">So I will look for better ways to =h resolve this.&nbsp; </FONT>i </P>  G <P><FONT SIZE=3D2 FACE=3D"Arial">I am told that it is working now and = 3 that does not get me out of buying the beer.</FONT>  </P>  C <P><FONT SIZE=3D2 FACE=3D"Arial">I guess I am buying the beer (or =e coffee) then.</FONT> </P>  0 <P><FONT SIZE=3D2 FACE=3D"Arial">Londoner</FONT>: <BR><FONT SIZE=3D2 FACE=3D"Arial">14930 Midway Road</FONT>A <BR><FONT SIZE=3D2 FACE=3D"Arial">Addison, TX&nbsp; 75001 </FONT>i </P>  ; <P><FONT SIZE=3D2 FACE=3D"Arial">This Friday at 5:15</FONT>i </P>  ; <P><FONT SIZE=3D2 FACE=3D"Arial">Find me if you can.</FONT>s </P>  4 <P><FONT SIZE=3D2 FACE=3D"Arial">John Brandon</FONT>B <BR><FONT SIZE=3D2 FACE=3D"Arial">VMS Systems Administrator</FONT>= <BR><FONT SIZE=3D2 FACE=3D"Arial">Dallas Semiconductor</FONT>=A <BR><FONT SIZE=3D2 FACE=3D"Arial">john.brandon@dalsemi.com</FONT>A8 <BR><FONT SIZE=3D2 FACE=3D"Arial">972.371.4172 wk</FONT>8 <BR><FONT SIZE=3D2 FACE=3D"Arial">972.371.4003 fx</FONT> </P> <BR>   </BODY>  </HTML>-) ------_=_NextPart_001_01C2C7CA.1207AF90--k   ------------------------------    Date: 29 Jan 2003 15:11:55 -0600; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) / Subject: Re: My e-mail sucks and I owe you beeri3 Message-ID: <PKnUBfrc0qbT@eisner.encompasserve.org>:  z In article <1809DA15308DD51180EE00508BCF21940DA165AB@misnts1.dalsemi.com>, John Brandon <John.Brandon@dalsemi.com> writes:L > This message is in MIME format. Since your mail reader does not understand> > this format, some or all of this message may not be legible. > ) > ------_=_NextPart_001_01C2C7CA.1207AF90k > Content-Type: text/plain;u > 	charset="iso-8859-1"d > L > I am having MS Exchange and client problems - I am sending as "Plain text"' > and the server refuses to believe me.e > My NT admins could care less.s3 > So I will look for better ways to resolve this.     >   Right now you're sending in both, surounded by MIME headers.   ------------------------------  % Date: Wed, 29 Jan 2003 21:38:56 -0500-2 From: rdeininger@mindspring.com (Robert Deininger)/ Subject: Re: My e-mail sucks and I owe you beerEL Message-ID: <rdeininger-2901032138570001@user-2ive10q.dialup.mindspring.com>  J In article <1809DA15308DD51180EE00508BCF21940DA165AB@misnts1.dalsemi.com>,. John Brandon <John.Brandon@dalsemi.com> wrote:    K >I am having MS Exchange and client problems - I am sending as "Plain text"e& >and the server refuses to believe me. >My NT admins could care less.2 >So I will look for better ways to resolve this.   > L >I am told that it is working now and that does not get me out of buying the >beer. >t/ >I guess I am buying the beer (or coffee) then.i  I My help desk has been investigating this problem (they claim) for about 3 J weeks, and they have yet to offer a working way to get plain text messages from Outhouse/Expunge.  J Even if they succeed, I won't pay them the 100 Quatloos, since it is theirJ job to figure this stuff out.  They will have to ask management to pay the Quatloos as a bonus.   ------------------------------  % Date: Wed, 29 Jan 2003 18:17:25 -0500l, From: "Frank Sapienza" <sapienza@noesys.com>" Subject: OpenVMS DCOM question ..., Message-ID: <b19ne80203c@enews3.newsguy.com>  J Can an OpenVMS system act as a DCOM *client*?  Before I go and install the? DCOM kit and try to figure it out I thought I'd ask here first.t  G What I'd like to do is get the OpenVMS system to trigger an action in a>K particular piece of software on a Windows server.  Any other possibilities?h     Thanks in advance.   ------------------------------  % Date: Wed, 29 Jan 2003 19:45:11 -0500n* From: "Bill Todd" <billtodd@metrocast.net>J Subject: Re: OpenVMS.org: Marvel article and HP's press release for Marvel2 Message-ID: <c_mdnRUceJE46KWjXTWc2Q@metrocast.net>  8 "Rob Young" <young_r@encompasserve.org> wrote in message- news:fSiIgis3U5EB@eisner.encompasserve.org...t   ...c  $ > on-chip switches coming to Itanium  H Got a reference for that?  I certainly haven't seen any projected ItanicI that seems likely to support on-chip switches before 2006 at the earliestlK (and nothing specific there, either:  it's just that every version prior tohL that data seems explicitly to *exclude* the possibility).  Or on-chip memory: controllers, for that matter (SPARC has them today, IIRC).   - bill   ------------------------------  % Date: Wed, 29 Jan 2003 21:15:48 -0500 2 From: rdeininger@mindspring.com (Robert Deininger)Y Subject: Re: OpenVMS.org: Marvel article and HP's press release for Marvel and Alpha RetahL Message-ID: <rdeininger-2901032115490001@user-2ive10q.dialup.mindspring.com>  M In article <3E37E0D8.2060007@nospamn.sun.com>, Andrew.Harrison@Sun.COM wrote:r  A >Incedentally you really have to laugh over the other "benchmark"m7 >numbers used to justify the Marvel performance claims.n >N >STREAMS >l8 >16 CPU's do almost exactly 16 x 1 CPU streams perf. Not5 >suprising when you realise that Alpha benchmark used 9 >OpenMP and the NUMA omp directive which makes all memory ! >access local rather than remote.   H If these were VMS results, you should realize that VMS does not yet knowI anything about "near" and "far" memory on Marvel systems.  And AFAIK, VMS9G does not provide a way for applications to figure this out and optimizeP! memory allocation within the app.=   ------------------------------  % Date: Thu, 30 Jan 2003 06:11:47 +0100a? From: "Bo Hermanson" <informentor.hermanson@mailbox.swipnet.se> * Subject: QL-XULA* licenses valid on Alpha?3 Message-ID: <Qo2_9.574$CR2.487@nntpserver.swip.net>r  F The VAX user license (XUL) is, regarding to the current SPD, no longer
 available.4     "QL-XULA9-** OpenVMS VAX Individual User LicenseH     (No Longer Available...order the Concurrent Use License or Unlimited User License)"  G However, in the DBL it's still active (or has been reactivated) and thel# product marketing description says:f0     "OpenVMS VAX V5.5 Interactive 1 User License3     OpenVMS Operating System for Alpha & VAX (XUL)"e  I Can I reuse the old VAX XUL licenses (on contract) on the Alpha's withouth license transfer?    Regardst Bo     Ij   ------------------------------  # Date: Wed, 29 Jan 2003 22:39:32 GMTo. From: peter@langstoeger.at (Peter LANGSTOEGER)* Subject: Re: Removing UCX from VMS system.3 Message-ID: <EKYZ9.31735$xv1.443486@news.chello.at>a  k In article <57136ccc.0301290348.141d6c62@posting.google.com>, steve.spires@torex.com (Steve Spires) writes: F >I want [need?!?] to remove UCX from an existing system. It appears toD >be causing some conflict with TCPware, even though I can't see thatF >it's actually starting. We  have some other networking related issuesG >which I'm finding it difficult to resolve while this is the situation.t   No problem. C On my systems, TCPware and UCX/TCPIP coexist for over a decade now.e   >$ set watch file/class=allc >$ ftp >%XQP, Thread #0, FIB contents:i >e >[verbosity snippage...] > E >%XQP, Thread #0, Directory scan for: UCX$FTP.EXE;0, Status: 00000000i  G You obviously forgot, that TCPIP defines DCL verbs for their utilities,cE while TCPware does invoke the utilities via symbols. If you forgot towE define them ($ @TCPWARE:TCPWARE_COMMANDS) you implicitely use the UCXeE ones and they complain about missing logicals/config files/sockets...   " So, no need to deinstall anything.   -- o Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialistt E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  % Date: Wed, 29 Jan 2003 23:54:28 -0000 3 From: "Jefferson Humber" <matrix01@globalnet.co.uk> * Subject: Re: Removing UCX from VMS system.3 Message-ID: <YmOdnb6J9rIo9KWjXTWcow@brightview.com>v   Charlie,  / Would this be the same for removing DECnet too.t  = I tried to do this today and got a similar message from PCSI.   L Is PRODUCT REMOVE the right way to uninstall DECnet from and Alpha v.7.3 box ?u   Cheers,    Jeff    @ "Charlie Hammond" <hammond@not@peek.ssr.hp.com> wrote in message( news:QnSZ9.29$zB1.26@news.cpqcorp.net...? > In article <57136ccc.0301290348.141d6c62@posting.google.com>,a- steve.spires@torex.com (Steve Spires) writes:s > >Hi chaps and chapesses, > >c> > >I want [need?!?] to remove UCX from an existing system. ... > .. > >$ prod show prodi? > >----------------------------------- ----------- ------------ 8 > >PRODUCT                             KIT TYPE    STATE? > >----------------------------------- ----------- ------------ < > >DEC AXPVMS DECNET_PHASE_IV V7.3     Full LP     Installed< > >DEC AXPVMS DWMOTIF V1.2-6           Full LP     Installed< > >DEC AXPVMS OPENVMS V7.3             Platform    Installed< > >DEC AXPVMS UCX V4.2-21              Full LP     Installed< > >DEC AXPVMS VMS V7.3                 Oper System Installed? > >----------------------------------- ----------- ------------v > .. > >a > >$ prod remove ucx > > + > >The following product has been selected:n= > >    DEC AXPVMS UCX V4.2-21                 Layered Productu > >e! > >Do you want to continue? [YES]e > >oF > >%PCSI-W-OPTREF, product DEC AXPVMS UCX V4.2-21 is referenced by DEC > >AXPVMS OPENVMS V7.3A > >-PCSI-W-OPTRF1, this software dependency is expressed within aG > >configuration> > >-PCSI-W-OPTRF2,   option that is currently selected for the > >referencing productH > >-PCSI-W-OPTRF3, if you want to reconfigure the referencing product or	 > >reviewoE > >-PCSI-W-OPTRF4,   its configuration requirements, answer NO to the  > >followingE > >-PCSI-W-OPTRF5,   question to terminate this operation; if you areg > >sure you wantI > >-PCSI-W-OPTRF6,   to remove the referenced product, then answer YES tot
 > >proceed$ > >Do you want to continue? [YES] no > .. >t> > At this point, you should have answered "YES" (the default). >SG > You get this message because UCX V4.2-21 was installed as part of thefH > OpenVMS platform, along with the OpenVMS Operating System.  So not the5 > PCSI database show that the platform refrences UCX.o >eB > To see this, set your screen to 132 cols and execute the command >o% >     $ PRODUCT SHOW PRODUCT * / FULL  > F > This will add "MAINTENANCE" (patches) and "REFERENCED BY" columns toA > the display.  In the "REFRENCED BY" column for UCX you will seeo >e >     DEC AXPVMS OPENVMS V7.3h >SG > BTW, UCX versions of TCP/IP Services for OpenVMS are way out of date.rG > Consider the more recent versions, which call themselves TCPIP ratherh
 > than UCX >rI > One final thing.  Check your SYSTARTUP_VMS.COM.  If you have code therec+ > to start UCX, you will need to remove it.. >e > --K >       Charlie Hammond -- Hewlett-Packard Company -- Pompano Beach  FL USAmJ >        (hammond@not@peek.ppb.cpqcorp.net -- remove "@not" when replying)L >       All opinions expressed are my own and not necessarily my employer's. >e   ------------------------------  # Date: Wed, 29 Jan 2003 20:59:43 GMT1/ From: "Curtis Justus" <donotspamme@foo.bar.edu> 2 Subject: Re: Sending Escape Codes to a LPR Printer; Message-ID: <3hXZ9.66315$Gm2.1641754@twister.rdc-kc.rr.com>e   Hi!e  > I just wanted to say, "thank you," to everybody who responded.  
 Take care, cj  : "Curtis Justus" <donotspamme@foo.bar.edu> wrote in message5 news:YOlZ9.62222$Gm2.1499699@twister.rdc-kc.rr.com...e > Hello! > K > I have connected a printer from my OpenVMS server to a Windows 2000 printeL > server running Print Services for UNIX.  I need to send an escape sequenceL > at the beginning of every print job.  I'm guessing there is a file or someB > place in the configuration where I could set that... right?  ;-) >t > Thanks in advance, > cj >n >g   ------------------------------    Date: 29 Jan 2003 13:13:15 -0800' From: geff@excite.com (geff@excite.com)a  Subject: Submit at end of month?= Message-ID: <2119a17f.0301291313.2761b114@posting.google.com>M  D I need a job to run on the end of the month then resubmit itself forA the end of next month.  I found something in the newsgroup awhile E back.  Does this function look like it would handle it (including FEBS and DEC)?  Thanks for any info.h     $ end_of_month = -q f$cvtime("01-''f$cvtime("15--+30-","ABSOLUTE","MONTH")'-''f$cvtime("15--+30-","ABSOLUTE","YEAR")'-1-","ABSOLUTE")s   ------------------------------  % Date: Wed, 29 Jan 2003 22:25:20 +0100t9 From: Jan-Erik =?iso-8859-1?Q?S=F6derholm?= <aaa@aaa.com> $ Subject: Re: Submit at end of month?' Message-ID: <3E3846C0.510585BD@aaa.com>     What is "end-of-month" exactly ?( Would 00:00 the first of each month do ?" That's easier to make up, I think.   Jan-Erik Sderholm   "geff@excite.com" wrote: > F > I need a job to run on the end of the month then resubmit itself forC > the end of next month.  I found something in the newsgroup awhiledG > back.  Does this function look like it would handle it (including FEB4! > and DEC)?  Thanks for any info.1 >  > $ end_of_month = -s > f$cvtime("01-''f$cvtime("15--+30-","ABSOLUTE","MONTH")'-''f$cvtime("15--+30-","ABSOLUTE","YEAR")'-1-","ABSOLUTE")7   ------------------------------    Date: 29 Jan 2003 21:59:36 -0800' From: geff@excite.com (geff@excite.com)o$ Subject: Re: Submit at end of month?= Message-ID: <2119a17f.0301292159.201411cc@posting.google.com>   / I'm sorry - I mean 31-JAN, 28-FEB, 31-MAR, etc.n  U Jan-Erik Sderholm <aaa@aaa.com> wrote in message news:<3E3846C0.510585BD@aaa.com>...f" > What is "end-of-month" exactly ?* > Would 00:00 the first of each month do ?$ > That's easier to make up, I think. >  > Jan-Erik Sderholm >  > "geff@excite.com" wrote: > > H > > I need a job to run on the end of the month then resubmit itself forE > > the end of next month.  I found something in the newsgroup awhile I > > back.  Does this function look like it would handle it (including FEB # > > and DEC)?  Thanks for any info.m > >  > > $ end_of_month = -u > > f$cvtime("01-''f$cvtime("15--+30-","ABSOLUTE","MONTH")'-''f$cvtime("15--+30-","ABSOLUTE","YEAR")'-1-","ABSOLUTE")t   ------------------------------  % Date: Thu, 30 Jan 2003 07:09:31 +0100 9 From: Jan-Erik =?iso-8859-1?Q?S=F6derholm?= <aaa@aaa.com>S$ Subject: Re: Submit at end of month?' Message-ID: <3E38C19B.DFF5A08A@aaa.com>s  * OK, but then, in the beginning of 31-Jan ? Or at the end of 31-JAN ?  At lunch time ?n- Or just about anytime during the 24h period ?s   Jan-Erik Sderholm.S   "geff@excite.com" wrote: > 1 > I'm sorry - I mean 31-JAN, 28-FEB, 31-MAR, etc.f > W > Jan-Erik Sderholm <aaa@aaa.com> wrote in message news:<3E3846C0.510585BD@aaa.com>...    ------------------------------  # Date: Wed, 29 Jan 2003 23:22:16 GMTp9 From: Alan Adams <alan.adams@orchard-way.freeserve.co.uk>z, Subject: Re: Terminal server recommendations? Message-ID: <d6c19fbc4b.Alan.Adams@orchard-way.freeserve.co.uk>i  D In message <tomnews-EB3360.14231828012003@news.comcast.giganews.com>.           Tom Rymes <tomnews@rymes.net> wrote:   > One more thing:a > H > Am I correct to assume that the fact that the DECServer 90M has RJ-45 F > ports instead of MMJ ports will not be a problem, just so long as I  > adapt the plugs correctly?   Correct.   >  > Thank you, >  > Tom    --  
 Alan Adams& alan.adams@orchard-way.freeserve.co.uk http://www.nckc.org.uk/h   ------------------------------  # Date: Thu, 30 Jan 2003 04:30:25 GMTm3 From: Vance Haemmerle <vance@toyvax.Glendale.CA.US>r) Subject: Re: VAXstation 4000 cd-rom bezel 5 Message-ID: <3E3839E5.165374D6@toyvax.Glendale.CA.US>r   I wrote:  > > I recently purchased a field installable 32x SCSI CD-ROM for= > a VAXstation 4000 (RRD47-EN) from Compurex.  I was suprizedt= > that it didn't come with a front panel bezel to replace the3@ > blank one with the system.  MPRS says that spares for VAX 4000@ > are no longer for sale.  Does anyone have a spare one of these. > I can have or know of a place I can buy one?    ; I wanted to thank the group for their help, especially withn: the part number.  It allowed me to search various DEC part: websites.  Still didn't have any luck.  However, Dani Mora@ of Great Lakes Computer (www.glcomp.com) was able to get me one.> I also got a killer deal on a DEC 3000/900 Alpha from them sixA years ago -- the one I'm writing this on now.  I highly recommendi them.   > The RRD47-EN from Compurex couldn't have been the -EN variant.= The mounting bracket with it wasn't for a VAXstation 4000 anda? there were no clips on the bottom of the drive described in thei@ 4000/60 Options guide installation instructions.  With no way to@ secure the drive in place, I used tape.  Par for the course withA Compurex?  That 24-bit SPXgt (PV61G-AA) mentioned in another posts= I bought from Compurex in 1998.  They charged my card, sent at< wrong board twice and after 8 months I had to file an ethics> complaint with the DDA before I finally got the correct board.< Two transactions is a small sample but I don't think I'll be trying them again.   -- Vance Haemmerlee   ------------------------------    Date: 29 Jan 2003 14:07:17 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen)t" Subject: Re: VMS source listings ?3 Message-ID: <UtHiG37f$FN2@eisner.encompasserve.org>.  R In article <3s6g3vk37t6baapbvfjmeu85fcsfd77jpj@4ax.com>, Dan <dan@vrx.net> writes:H > if someone contracts me or sub-contracts or signs an agreement with me& > for this, why would it NOT be legal?  F Because the license for the source listings restricts them to using itE at a single location of theirs.  Whether doing work for hire on theirnH premises you could look at their copy is something on which I am unsure.  ' > I *HAVE* the source listings!!!!!!!!!S > B > Remember?? I have them! So, the only difference being the FORMAT' > in which the media that carries them.e > ? > I have microfiche, so I am already constrained by the licensee! > agreements for the source code.n  I There are no versions of VMS for which the source listings were available-L both on Microfiche and CDROM.  Therefore you have some other version covered by a different agreement.c  F Check your copy of the signed license agreement to see if they granted" you rights to use future versions.  E > you people are pathetically obtuse on this. there are always simplep > solutions to everything.  G And just as with programming, many of those simple solutions are wrong.g   ------------------------------  % Date: Wed, 29 Jan 2003 18:26:16 -0500U From: Dan <dan@vrx.net>1" Subject: Re: VMS source listings ?8 Message-ID: <biog3vo7hp83oeil2ic17am7jgvggmapr8@4ax.com>  F On 29 Jan 2003 14:07:17 -0600, Kilgallen@SpamCop.net (Larry Kilgallen) wrote:  S >In article <3s6g3vk37t6baapbvfjmeu85fcsfd77jpj@4ax.com>, Dan <dan@vrx.net> writes:tG >Because the license for the source listings restricts them to using itTF >at a single location of theirs.  Whether doing work for hire on theirI >premises you could look at their copy is something on which I am unsure.s  A wrong.. the agreement says NOTHING about the location. yes it mayy@ mention a single location, however, a cd set cannot exist in two, locations at once (not a single set anyhow).  B and what is meant by location? location of business? ok, many have( several locations, what then? and so on.  F You want to be obtuse, let's get completely carried away with just how< obtuse and silly this can be (and still be legit and legal!)  J >There are no versions of VMS for which the source listings were availableM >both on Microfiche and CDROM.  Therefore you have some other version coveredn >by a different agreement.  B that's not true either. completely not true. I checked with CompaqC already. When I first checked I could get it either on CD or fiche.n< Now maybe they made a mistake, but that's what they told me.. Of course, I could also get it on TK50. (ewww)  G >Check your copy of the signed license agreement to see if they granted # >you rights to use future versions.l  A yes, I do. but that doesn't help me, without a copy of the future5	 versions.   H >And just as with programming, many of those simple solutions are wrong.  D perhaps, but there are also many (correct) solutions to any problem.   Dan.   ------------------------------  # Date: Thu, 30 Jan 2003 01:04:54 GMT " From:   VAXman-  @SendSpamHere.ORG" Subject: Re: VMS source listings ?0 Message-ID: <00A1AB5A.2A40BA0E@SendSpamHere.ORG>  R In article <biog3vo7hp83oeil2ic17am7jgvggmapr8@4ax.com>, Dan <dan@vrx.net> writes:G >On 29 Jan 2003 14:07:17 -0600, Kilgallen@SpamCop.net (Larry Kilgallen)l >wrote:p >.T >>In article <3s6g3vk37t6baapbvfjmeu85fcsfd77jpj@4ax.com>, Dan <dan@vrx.net> writes:H >>Because the license for the source listings restricts them to using itG >>at a single location of theirs.  Whether doing work for hire on their J >>premises you could look at their copy is something on which I am unsure. >aB >wrong.. the agreement says NOTHING about the location. yes it mayA >mention a single location, however, a cd set cannot exist in twom- >locations at once (not a single set anyhow).s >lC >and what is meant by location? location of business? ok, many haveb) >several locations, what then? and so on.o  J Well Dan, the verbage of the contract reads as follow (...and my copy has ( yellowed but I'm sure it's still valid):  
 4. LICENSE    :    :K    4.3 Except as provided in Paragraph 4.4 below, CUSTOMER or a thrid partyoK        acting as a CUSTOMER's agent and on CUSTOMER's behalf shall have the-N        right to use at the designated facility or campus specified in Section 1        14 below each Source licensed hereunder...n    K So, yes, the agreement does restrict the source listings to a location.  In1K my case, section 14 describes that place as the home office of yours truly.o  K I am not a lawyer -- and I'm thankful for that as I would hate to loathe myoK fellow man and worship the root of all evil -- but I am pretty sure that inHL the realm of the lust for litigation types that the possession of the sourceE listings does not imply any rights to them or any rights to use them.M   --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COMd            p5   "Well my son, life is like a beanstalk, isn't it?" d   ------------------------------    Date: 29 Jan 2003 21:51:50 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen)m" Subject: Re: VMS source listings ?3 Message-ID: <jMlt8aVEX0w9@eisner.encompasserve.org>e  R In article <biog3vo7hp83oeil2ic17am7jgvggmapr8@4ax.com>, Dan <dan@vrx.net> writes:H > On 29 Jan 2003 14:07:17 -0600, Kilgallen@SpamCop.net (Larry Kilgallen) > wrote: > T >>In article <3s6g3vk37t6baapbvfjmeu85fcsfd77jpj@4ax.com>, Dan <dan@vrx.net> writes:H >>Because the license for the source listings restricts them to using itG >>at a single location of theirs.  Whether doing work for hire on their.J >>premises you could look at their copy is something on which I am unsure. > C > wrong.. the agreement says NOTHING about the location. yes it maysB > mention a single location, however, a cd set cannot exist in two. > locations at once (not a single set anyhow). > D > and what is meant by location? location of business? ok, many have* > several locations, what then? and so on.  A The agreement my company signed with HP restricts use to a single . location and required us to name the location.   <ad hominem attack snipped>-  K >>There are no versions of VMS for which the source listings were availablecN >>both on Microfiche and CDROM.  Therefore you have some other version covered >>by a different agreement.n > D > that's not true either. completely not true. I checked with CompaqE > already. When I first checked I could get it either on CD or fiche.:> > Now maybe they made a mistake, but that's what they told me.0 > Of course, I could also get it on TK50. (ewww)  8 Please provide order numbers for those various versions.  H >>Check your copy of the signed license agreement to see if they granted$ >>you rights to use future versions. >  > yes, I do.  G Then you have quite a unique source license agreement (remember, we are ? _not_ talking about an ordinary HP software license agreement).    ------------------------------  % Date: Thu, 30 Jan 2003 00:52:51 -0500  From: Dan <dan@vrx.net> " Subject: Re: VMS source listings ?8 Message-ID: <pafh3vom0n5qs4q7efi6t5ipsc70cuvlfb@4ax.com>  F On 29 Jan 2003 21:51:50 -0600, Kilgallen@SpamCop.net (Larry Kilgallen) wrote:B >The agreement my company signed with HP restricts use to a single/ >location and required us to name the location..   who said anything about HP?i# I dont have an agreement with HP...e but that's fine.  F so what happens if you move ? you then can't legally use the software?  H >Then you have quite a unique source license agreement (remember, we are@ >_not_ talking about an ordinary HP software license agreement).   I never signed a thing with HP..   Dan.   ------------------------------  % Date: Thu, 30 Jan 2003 00:56:17 -0500o From: Dan <dan@vrx.net>o" Subject: Re: VMS source listings ?8 Message-ID: <uefh3voefi75oh8s4m3e49f4ljstcr7fsn@4ax.com>  C On Thu, 30 Jan 2003 01:04:54 GMT, VAXman-  @SendSpamHere.ORG wrote:iK >Well Dan, the verbage of the contract reads as follow (...and my copy has t) >yellowed but I'm sure it's still valid):  >aL >So, yes, the agreement does restrict the source listings to a location.  InL >my case, section 14 describes that place as the home office of yours truly.   oh for gods sakes.F this is EXACTLY what was wrong with VMS 28 years ago, and it's EXACTLY# what is still wrong with VMS today.j  E the overstuffed, pigheaded, pompous, self-righteous, holier than thou- snobbish, stuck-up, elitism...  D I despise that crap. and its entirely what the open-source community is designed to get rid of.  L >I am not a lawyer -- and I'm thankful for that as I would hate to loathe myL >fellow man and worship the root of all evil -- but I am pretty sure that inM >the realm of the lust for litigation types that the possession of the source F >listings does not imply any rights to them or any rights to use them.  9 define "use". is "reading" therefore "use" ? but whatever   D ok so what yer saying is, in order for me to even LOOK at the stupidE CDs, I have to travel to someone who has them and look at them there?c   that's dumb, but whatever.   Dan.   ------------------------------  # Date: Thu, 30 Jan 2003 00:43:35 GMTi1 From: Michael Austin <maustin@firstdbasource.com> # Subject: Re: Was Doc's box cracked?y2 Message-ID: <3E387497.2C9AB6BD@firstdbasource.com>   "Doc.Cypher" wrote:t > F > On Tue, 28 Jan 2003, "Mr. Gunfun Knee" <gunfunny@hotmail.com> wrote:H > >Did a port scan of the subnet, and my mistake... the ip of the user I= > >accessed was 213.193.176.107, sorry for jumping the gun...  > J > Not really a good idea - doing the port scan. I hope you were "discreet"E > about it and only checking a single port on each IP with reasonableaI > intervals between them. Otherwise you might have upset one of my online 
 > neighbours.m > G > OTOH, if they're like me, and have been running services for a while,r@ > they'll be used to odd traffic following an IP address change. >  > Doc. > --< > Time and money, the psychotropics of the business world...M > ~ VAXman                                             https://vmsbox.cjb.nety  F Just curious, what DDNS service are you using and how are you updatingH the DDNS with your new IP address?  I am using ZONEEDIT and have a linux" box monitoring the Linksys router.   --   Regards,  6 Michael Austin            OpenVMS User since June 19847 First DBA Source, Inc.    Registered Linux User #261163l7 Sr. Consultant            http://www.firstdbasource.comr   ------------------------------    Date: 29 Jan 2003 11:16:30 -08001 From: keithparris_NOSPAM@yahoo.com (Keith Parris)r/ Subject: Re: [MSA1000] Support for/by OpenVMS ?u= Message-ID: <cf15391e.0301291116.2ac6da06@posting.google.com>h  j peter@langstoeger.at (Peter LANGSTOEGER) wrote in message news:<93hZ9.246726$TY.2592125@news.chello.at>...L > Last winter I heard that the VMS support for the then new MSA1000 Mini-SAN> > is coming in the not so far distance ("probably fall 2002").  > Appears to be slated for Q1 of 2003, according to the info at:B http://www.openvms.compaq.com/openvms/roadmap/openvms_roadmaps.htm   ------------------------------   End of INFO-VAX 2003.059 ************************