1 INFO-VAX	Tue, 18 Oct 2005	Volume 2005 : Issue 582       Contents: Re: Alpha last order date 6 Re: Announcing the proVMS Computer Experts Association% OT: Is your HP printer spying on you?  Re: Porting VMS back to VAX ?  Re: Porting VMS back to VAX ?  Re: Porting VMS back to VAX ?  Re: set time on Itanium OpenVMS  Re: TCP/IP NFS-mount Re: [CSWS V2.1] When expected ?  Re: [CSWS V2.1] When expected ? ! [TCPIP V5.5 ECO1] When expected ? % Re: [TCPIP V5.5 ECO1] When expected ? % Re: [TCPIP V5.5 ECO1] When expected ? % Re: [TCPIP V5.5 ECO1] When expected ?  [TCPIP V5.5] X11 over SSH   F ----------------------------------------------------------------------  + Date: Tue, 18 Oct 2005 13:35:30 +0000 (UTC)  From: david20@alpha2.mdx.ac.uk" Subject: Re: Alpha last order date) Message-ID: <dj2tn0$d73$1@news.mdx.ac.uk>   f In article <_bB3f.23947$U9.4632@fe3.news.blueyonder.co.uk>, Alan Greig <greigaln@netscape.net> writes: >  >  >Dave Froble wrote: 8 >> Just got some stuff from HP, e-mail newsletter stuff. >>  J >> VMS was rather prominent, mentioned in multiple locations.  Some stuff F >> on Alpha also.  One item was October 27, 2006 as a last order date. > F >That date has been on the HP Alphaserver page for some time now. Not % >sure exactly when it first appeared.  > L >> Some were worried that 2006 meant Jan 1.  Not so.  Got a year to see how I >> things work out.  If the itanic survives, that's good for VMS.  If it   > E >I've been under the impression it was end 2006 but I can't remember  G >where I saw that. A last order date of Oct 27 probably implies a last  D >ship around December 2006 (excepting some special cases I suppose). >   ? The OpenVMS 8.2 release notes had the following in section A.10   E Product                    Final Order date           Final ship date E =======                    ================           ===============   G Alpha Systems              September 30, 2006         December 30, 2006   G CPU upgrades               September 30, 2007         December 30, 2007     M So if they've extended the Final order date by a month it's possible the last ) ship date might extend into January 2007.   ' Still much much too soon in my opinion.   
 David Webb Security team leader CCSS Middlesex University       >Six years previously... >  >--- >Newsgroups: comp.os.vms1 >From: Andreas Strahm <andreas.str...@siemens.ch>  >Date: 2000/08/08 * >Subject: Last order dates for VAX systems >  >Just for information: >  >  <$ >   Last order dates for VAX systems > 3 >   VAX 4000, MicroVAX 3100 - 88 and 3100-98 models  > < >   VAX 4000, MicroVAX 3100-88, and MicroVAX 3100-98 systems1 >   and all associated options are being retired. 5 >   Limited supply will be supported on a first come,  >   first serve basis. > ' >   Last order date: September 30, 2000  > % >   Last ship date: December 31, 2000  >  > > = >Source: http://www.compaq.com/alphaserver/vax/vax_dates.html  > 	 >Regards,  >  >Andreas Strahm, >Software Engineer >--- > K >> has problems, well, they're accepting orders for another year, and last  J >> ship date is probably some reasonable time after that.  Still possible - >> at that time to extend Alpha if necessary.  >>  G >> I'm feeling that in another year, the 'writing on the wall' for the  J >> itanic will be much clearer.  Not saying that it will be bad, could go 0 >> either way.  I'm hoping it finds some future. >>  L >> If the newsletter is any indication, HP is not hiding VMS.  That's good. F >>  Then again, I may be a targeted reader, getting a special version. >>  # >> Black helicopters and such.  :-)  >>   >  >--  >Alan Greig    ------------------------------  % Date: Tue, 18 Oct 2005 08:24:53 +0100 % From: "issinoho" <issinoho@gmail.com> ? Subject: Re: Announcing the proVMS Computer Experts Association 4 Message-ID: <dj27ut$7mf$1$8302bc10@news.demon.co.uk>  * <thierry.uso@wanadoo.fr> wrote in message = news:1129587539.811245.288240@g43g2000cwa.googlegroups.com... C > We have tested some CMS on OpenVMS (spip, mambo and guppy) before H > choosing TextPattern. spip and co needed modification of the PHP code, > rename of files... > E > TextPattern 1.0rc3 works out-of-the-box on OpenVMS. We have not yet ! > tested the last stable version.  > ' > We choosed TextPattern also because : @ >  - it has a strict separation between presentation and content >  - it generates a clean XHTML ' >  - it has powerfull publish functions  >  > Weakness :4 >  - it needs a good understanding in CSS stylesheet >  - not enough documentation  > F > When we built the website, PHP was not supported by WASD on Itanium. > So, we choosed Apache. > 8 > I will document soon all the stuff on your VAMP board. >    Thank-you. Excellent.    ------------------------------  # Date: Tue, 18 Oct 2005 17:06:01 GMT ( From: Alan Greig <greigaln@netscape.net>. Subject: OT: Is your HP printer spying on you?< Message-ID: <ZX95f.47089$U9.10746@fe3.news.blueyonder.co.uk>  F Did you know your colour printer might be encoding the date, time and C printer serial number in every print? Researchers for the EFF have  I broken the code on some printers which allows them to identify the date,  4 time and printer serial number of each print page...  ) http://www.theinquirer.net/?article=27027 H "RESEARCHERS hired by the Electronic Frontier Foundation (EFF) say they H were able to break a code hidden in tiny tracking dots that some colour 5 laser printers secrete in every document they print."   < And a list of HP printers known to encode information from: , http://www.eff.org/Privacy/printers/list.phpJ List of HP printers which encode tracking information in every print page: HP Color LaserJet yes         * 1500l [exp]      * 2500 [exp]       * 2500n [exp]      * 2550l [exp]      * 2550n [exp]      * 2600n [exp]      * 2680 [exp]       * 2840 [exp]       * 3500 [exp]       * 3500n [exp]      * 3600dn [exp]       * 3700 [exp]       * 3700dn [exp]       * 3700n [exp]      * 4600 [exp]       * 4600dn [exp]       * 4600hdn [exp]      * 4600n [exp]      * 4650 [exp]       * 4650dn [exp]       * 4650dtn [exp]      * 5100cn [exp]       * 5500 [exp]       * 5500atn [exp]      * 5500dn [exp]       * 5500hdn [exp]      * 5550 [exp]       * 5550dtn [exp]      * 9500 [exp]       * 9500hdn [exp]  G Other HP printers might encode - these are just the ones known so far.  F Full instructions for searching for the dots in your own printouts at 3 http://www.eff.org/news/archives/2005_10.php#004063    --  
 Alan Greig   ------------------------------  # Date: Tue, 18 Oct 2005 11:07:56 GMT 5 From: rdeininger@mindspringdot.com (Robert Deininger) & Subject: Re: Porting VMS back to VAX ?L Message-ID: <rdeininger-1810050708180001@user-uinj4cc.dialup.mindspring.com>  5 In article <43543A04.4D3EE1C1@teksavvy.com>, JF Mezei % <jfmezei.spamnot@teksavvy.com> wrote:    >Hoff Hoffman wrote:G >>   As we stated some eons ago, the VAX kernel and its environment is, G >>   are, and will remain stable -- we'd have to overhaul it as part of D >>   any down-port, causing most any drivers or other kernel-code to$ >>   require relinks or more rework. > @ >In terms of drivers, wouldn't the Alpha and IA64 drivers differH >substantially ? Or do they share some core structure which is radically( >different from those designed for VAX ?  H For most devices, the Alpha and I64 drivers are nearly identical.  ThereH are bits of conditional code, and macros and system routines that behaveF differently on different architectures.  But the same source code gets4 compiled for both architectures in every case AFAIK.  I All the I64 device drivers supported on V8.2 were written and/or debugged F on Alpha systems, usually before the developers had easy access to I64E systems.  These days, new driver development is main on I64, for I64.    ------------------------------    Date: 18 Oct 2005 07:56:06 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) & Subject: Re: Porting VMS back to VAX ?3 Message-ID: <elwl5+UcT+r5@eisner.encompasserve.org>   ] In article <uAO4f.14715$1o3.12741@news.cpqcorp.net>, John Reagan <john.reagan@hp.com> writes:  > F > Also, much of the Macro-32 code over the years has evolved to using J > various EVAX_ builtins and referencing the additional R16-R24 registers I > for increased performance.  Plus most of the Macro-32 code was touched  I > when moving from VAX to Alpha to add things like .CALL_ENTRY, etc. and  I > recoding to not use features that the Macro compiler couldn't support.    F    The last time I tried this, the VAX Macro-32 assembler accepted the:    Alpha Macro-32 compiler directorives like .CALL_ENTRY .  E    I don't recall which version of VMS I tried that on, but I'm quite F    sure it was fairly old.  Only one of the VAXen I have access to is     anywhere near up to date.   ------------------------------  # Date: Tue, 18 Oct 2005 14:06:42 GMT & From: John Reagan <john.reagan@hp.com>& Subject: Re: Porting VMS back to VAX ?3 Message-ID: <Sj75f.14824$Ma4.8934@news.cpqcorp.net>    Bob Koehler wrote:_ > In article <uAO4f.14715$1o3.12741@news.cpqcorp.net>, John Reagan <john.reagan@hp.com> writes:  > F >>Also, much of the Macro-32 code over the years has evolved to using J >>various EVAX_ builtins and referencing the additional R16-R24 registers I >>for increased performance.  Plus most of the Macro-32 code was touched  I >>when moving from VAX to Alpha to add things like .CALL_ENTRY, etc. and  I >>recoding to not use features that the Macro compiler couldn't support.   >  > H >    The last time I tried this, the VAX Macro-32 assembler accepted the< >    Alpha Macro-32 compiler directorives like .CALL_ENTRY . > G >    I don't recall which version of VMS I tried that on, but I'm quite H >    sure it was fairly old.  Only one of the VAXen I have access to is  >    anywhere near up to date. >   D Yep, I think I mentioned that in a later message.  Those directives @ (which actually are just macros) are ignored on VAX (except for F .CALL_ENTRY which does know how to make the register save mask on the I entry point).  All the interesting directives like HOME_ARGS, QUAD_ARGS,  E etc. are all ignored.  I'm guessing the code would notice if we just   ignored the option.   H In addition, a significant amount of Macro-32 code has become dependent B on what I call "autopreseving".  The Alpha and I64 compilers will I autopreserve any register written in a .CALL_ENTRY or .JSB_ENTRY routine  H that isn't marked as OUTPUT or SCRATCH.  So a routine that just needs a I quick temp can just use, lets say, R3, and the compiler will preserve it  I at the top of the routine and restore it at the bottom.  That code won't  H work on VAX as-is since the modified R3 would be visible to the outside I world.  Either the code would have to be modified to explicitly list the  G registers in the PRESERVE clause or the VAX assembler would have to be  I extended to process the directives, analyze the flow of the routine, and  I compute the autopreserving.  The VAX assembler is in no shape to perform  H that task.  The amount of work would be enormous.  It would essentially H mean that we'd have to turn the VAX *ASSEMBLER* into a *COMPILER*.  The C "easiest" solution is to turn on the infos that have the Alpha/I64  D compiler list the autopreserved registers for each routine and have C somebody modify each module in the system to explicit preserve the  E register.  And, again, I don't know how to specify the preserving of  ! registers larger than R16 on VAX.    --   John Reagan / HP Pascal/{A|I}MACRO for OpenVMS Project Leader  Hewlett-Packard Company    ------------------------------    Date: 18 Oct 2005 02:00:35 -0700/ From: "Volker Halle" <volker_halle@hotmail.com> ( Subject: Re: set time on Itanium OpenVMSC Message-ID: <1129626035.327261.208810@f14g2000cwb.googlegroups.com>    Don,  E consider to enable TIME auditing with SET AUDIT/ALARM/ENA=TIME to see ? what's happening to the system time. Then watch the OPCOM AUDIT  messages after RPLEY/ENABLE.   Volker.    ------------------------------    Date: 18 Oct 2005 09:17:07 +0200. From: huber@NOBODY-mppmu.mpg.de (Joseph Huber) Subject: Re: TCP/IP NFS-mount + Message-ID: <H4V9BaBN5$sw@vms.mppmu.mpg.de>   c In article <1129143133.326479.189620@g14g2000cwa.googlegroups.com>, "Bendix" <br@b-riis.dk> writes: = > I'm trying to nfs-mount in tcpip with the following result.    >  > TCPIP> sh proxy  > = > VMS User_name     Type      User_ID    Group_ID   Host_name  > 5 > NOBODY            ON             -2          -2   * 2 > TCPIP> mount dnfs: /host=vax1 /path="/test/data"> > %TCPIP$DNFSMOUNT-E-MOUNTFAIL, error mounting _DNFS5:[000000]> > -SYSTEM-F-INVLOGIN, login information invalid at remote node  = If not just not shown in Your posting, the necessary PROXY is  TCPIP$NOBODY, not just NOBODY.  ( To update proxies to the OND state, use   $  tcpip set tcp/signal    2 (if not the maximum number of proxies is reached).   --  @    Joseph Huber , Muenchen,Germany:  http://www.huber-joseph.de/   ------------------------------  % Date: Tue, 18 Oct 2005 11:01:05 +0200 3 From: "Gorazd Kikelj" <gorazd.kikelj@nospam.hp.com> ( Subject: Re: [CSWS V2.1] When expected ?* Message-ID: <4354b9d3@usenet01.boi.hp.com>  D "Peter 'EPLAN' LANGSTOEGER" <peter@langstoeger.at> wrote in message & news:4353f696$1@news.langstoeger.at...4 >I wanted to upgrade a CSWS V2.0 system to VMS V8.2,7 > but CSWS V2.1 with support for V8.2 is not yet there.  > On  L I just test beta T2.1. It works very vell, but have a problem with mod_perl H and backticks that logical names from parent process don't propagate to  subprocess.   
 Best, Gorazd     ------------------------------    Date: 18 Oct 2005 14:37:56 -02006 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)( Subject: Re: [CSWS V2.1] When expected ?* Message-ID: <435508c4@news.langstoeger.at>  Z In article <11l8apro3ukik8d@corp.supernews.com>, Dave Froble <davef@tsoft-inc.com> writes: >Rick Barry wrote:N >> We now expect a mid-November availability for SWS 2.1 on Alpha and Itanium. >>  - >> SWS 2.1 removes the stream-lf restriction.  > + >Me thinks you will be a hero to many.  :-)    I second this...   --   Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------    Date: 18 Oct 2005 16:08:51 -02006 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)* Subject: [TCPIP V5.5 ECO1] When expected ?* Message-ID: <43551e13@news.langstoeger.at>  @ Does perhaps anybody know when TCPIP V5.5 ECO1 is expected now ?  F And will it fix the "$ in username" SSH problem (which V5.4 ECO 4 or 5% already fixed some/many months ago) ?   J And will it fix the "no intrusion records" SSH problem (which AFAIK wasn't there in V5.4) ?   Many TIA   --   Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------    Date: 18 Oct 2005 16:22:46 -02006 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER). Subject: Re: [TCPIP V5.5 ECO1] When expected ?, Message-ID: <43552156$1@news.langstoeger.at>  _ In article <dj2vv0$t1e$1@blackmamba.itd.rl.ac.uk>, "Richard Brodie" <R.Brodie@rl.ac.uk> writes: D >"Peter 'EPLAN' LANGSTOEGER" <peter@langstoeger.at> wrote in message% >news:43551e13@news.langstoeger.at...  > C >> Does perhaps anybody know when TCPIP V5.5 ECO1 is expected now ?  >  >Two or three weeks ago ;)   Shame on me I overlooked it :-( 4 Because I checked FTP.ITRC.HP.COM before I posted...  > And does it fix the "VMS username in lowercase" SFTP Problem ?   Ok, I look for myself...   --   Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  % Date: Tue, 18 Oct 2005 15:13:51 +0100 * From: "Richard Brodie" <R.Brodie@rl.ac.uk>. Subject: Re: [TCPIP V5.5 ECO1] When expected ?2 Message-ID: <dj2vv0$t1e$1@blackmamba.itd.rl.ac.uk>  C "Peter 'EPLAN' LANGSTOEGER" <peter@langstoeger.at> wrote in message $ news:43551e13@news.langstoeger.at...  B > Does perhaps anybody know when TCPIP V5.5 ECO1 is expected now ?   Two or three weeks ago ;)    ------------------------------  % Date: Tue, 18 Oct 2005 14:33:13 +0000 - From: David B Sneddon <dbsneddon@bigpond.com> . Subject: Re: [TCPIP V5.5 ECO1] When expected ?* Message-ID: <435507A9.5000704@bigpond.com>  / Peter 'EPLAN' LANGSTOEGER was overheard to say: B > Does perhaps anybody know when TCPIP V5.5 ECO1 is expected now ? > H > And will it fix the "$ in username" SSH problem (which V5.4 ECO 4 or 5' > already fixed some/many months ago) ?  > L > And will it fix the "no intrusion records" SSH problem (which AFAIK wasn't > there in V5.4) ? > 
 > Many TIA >   4 That has been available from itrc since October 3...   Regards, Dave.  --  D David B Sneddon (dbs)  VMS Systems Programmer  dbsneddon@bigpond.comD Sneddo's quick guide ...     http://www.users.bigpond.com/dbsneddon/D DBS freeware     http://www.users.bigpond.com/dbsneddon/software.htm   ------------------------------    Date: 18 Oct 2005 15:17:23 -02006 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)" Subject: [TCPIP V5.5] X11 over SSH, Message-ID: <43551203$1@news.langstoeger.at>  < I just tried to do X11 over SSH in TCPIP V5.5 and it worked.5 But I think in TCPIP V5.4 (ECO 5) it looks like this:    $ SHOW DISPLAY       Device:    WSA4:  [super] $     Node:      mechta.langstoeger.at     Transport: TCPIP     Server:    10      Screen:    0  ! while in V5.5 it looks like this:    $ SHOW DISPLAY= %DECW-W-OPENIN, error opening ns.langstoeger.at:10.0 as input ' -SYSTEM-F-IVDEVNAM, invalid device name   $ SHOW LOGICAL/FULL DECW$DISPLAYF    "DECW$DISPLAY" [user] = "ns.langstoeger.at:10.0" (LNM$JOB_82006900)    F Any good reason for this change ?? I'm quite sure it works for most ifG not all the X11 applications, but it is different to V5.4 (and uglier).    Many TIA   --   Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------   End of INFO-VAX 2005.582 ************************