1 INFO-VAX	Sun, 06 Oct 2002	Volume 2002 : Issue 551       Contents:C Re: "Intel's Huge Bet Turns Iffy":  Doubts hit the mainstream (NYT) ! Re: Announcing WHOIS V1.5 for VMS  Bug in time zone files Re: Bug in time zone files! Re: e-mail web client (SilkyMail) ! Re: e-mail web client (SilkyMail) ! Re: e-mail web client (SilkyMail) ! Re: e-mail web client (SilkyMail) ! Re: e-mail web client (SilkyMail) ! Re: e-mail web client (SilkyMail)   Re: First 7.3-1 problem detected  Re: First 7.3-1 problem detected FS: Some DEC books...  Re: Merger - smerger Merger - smerger Re: mouning floppy drive Re: Mount ISO Image  Re: Mount ISO Image  Re: NETPrint 1000  Re: OpenVMS is strategic Re: OpenVMS is strategic Re: OpenVMS is strategic Re: OpenVMS is strategic Re: OpenVMS is strategic Re: OpenVMS is strategic Re: OpenVMS is strategic+ Re: Originator of detached process from DCL  Re: tcp/ip == UCX  Re: The perils of reusable code  VMS pages update  Re: Volume shadowing performance! Re: WASD Security Advisory Issued ! Re: WASD Security Advisory Issued   F ----------------------------------------------------------------------  " Date: Sat, 5 Oct 2002 23:32:03 GMT- From: bdc@world.std.com (Brian 'Jarai' Chase) L Subject: Re: "Intel's Huge Bet Turns Iffy":  Doubts hit the mainstream (NYT)& Message-ID: <H3J81F.DG6@world.std.com>  - In article <87u1k4enma.fsf@prep.synonet.com>, . Paul Repacholi  <prep@prep.synonet.com> wrote:1 > bdc@world.std.com (Brian 'Jarai' Chase) writes:  > ' > > C.O.V: The older grumpier Slashdot.  > 4 > Can I steal this for my .sig? It is a real keeper!   Sure, be my guest.   -brian.  --  F --- Brian Chase | bdc@world.std.com | http://world.std.com/~bdc/ -----H This counter is [6,177,399,753] times as pointless as a real one.  -- K.   ------------------------------  % Date: Sat, 05 Oct 2002 23:31:36 +0200 2 From: martin@radiogaga.harz.de (Martin Vorlaender)* Subject: Re: Announcing WHOIS V1.5 for VMS; Message-ID: <3d9f5a38.524144494f47414741@radiogaga.harz.de>   . JF Mezei (jfmezei.spamnot@videotron.ca) wrote: > Martin Vorlaender wrote:M > > It's probably the compiler version. With Compaq C v6.x you get the effect   > > when using /STANDARD=ANSI89. > N > The alpha version compled cleanly on an alpha with 7.3-1 and CC 6.5 compiled9 > with CC/INSIGNED WHOIS.C and it didn't complain at all.  > 0 > On my vax, I have 6.0 and again no complaints.  H David Smith said he has DEC C 5.6. The message was probably just shiftedD from the RELAXED_ANSI89 group to the ANSI89 group in the v6.x frame.   cu,    Martin --  F                           | Martin Vorlaender  |  VMS & WNT programmer3  Cetero censeo            | work: mv@pdv-systeme.de F  Redmondem delendam esse. |   http://www.pdv-systeme.de/users/martinv/:                           | home: martin@radiogaga.harz.de   ------------------------------  % Date: Sat, 05 Oct 2002 23:44:20 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca>  Subject: Bug in time zone files , Message-ID: <3D9FB18F.E042FAB5@videotron.ca>   VAX VMS 7.3   7 SYS$SYSROOT:[SYS$ZONEINFO.system.sources]northamerica.;   	 contains:   7 # CANADA   PACIFIC    7 H  BEHIND UTC    APR 3 - OCT 29 / # CANADA   YUKON      SAME AS PACIFIC    DAWSON    <...>   - # From Arthur David Olson (January 21, 1989): O # April 3 fell on a Sunday in 1988; October 29 fell on a Sunday in 1989.  Ahem. J # Note claim that there's double DST in Newfoundland and that Yukon shouldO # be same as Pacific.  Stick with rules posted in 1988 until more authoritative  # information is available.   P # Rule  NAME    FROM    TO      TYPE    IN      ON      AT      SAVE    LETTER/SI Rule Canada     1969    max     -       Oct     lastSun 2:00    0       S I Rule Canada     1969    1986    -       Apr     lastSun 2:00    1:00    D I Rule Canada     1987    max     -       Apr     Sun>=1  2:00    1:00    D   ? # Zone  NAME             GMTOFF RULES/SAVE      FORMAT  [UNTIL] 8 # Bob Devine says that DST *is* observed in Newfoundland4 Zone Canada/Newfoundland -3:30  Canada          N%sT4 Zone Canada/Atlantic     -4:00  Canada          A%sT4 Zone Canada/Eastern      -5:00  Canada          E%sT4 Zone Canada/Central      -6:00  Canada          C%sTG Zone Canada/East-Saskatchewan   -6:00   -       CST # No DST as of 1987 4 Zone Canada/Mountain     -7:00  Canada          M%sT4 Zone Canada/Pacific      -8:00  Canada          P%sT4 Zone Canada/Yukon        -9:00  Canada          Y%sT         ###   N From my bike trips to Yukon and Alaska in 1989, 1990, 1991, I can confirm thatK Yukon observes the same time as Pacific time ( GMT-8, with daylight savings J during summer).  The above has text that corrpborates, but then the "Zone"9 statement provides a different time offsent from Pacific.    Hawaii is -10, Alaska (except aleutians) is -9  Pacific (including Yukon) is -8   J Note that in 1994, on a CP flight from Hong Kong to Vancouver, the airshowK still had Alaska with the same offset as Hawaii and Yukon with its own time K zone. (and I knew that was dead wrong). So VMS isn't alone with this error.   H Yukon tends to do business with british Columbia and wants the same timeN zones. Northwest Territories do business with Edmonton (mountain time) and use their time zone.  K Not sure what Nunavut decided. They had a rererendum to decide whether they H should all be in the same time zone or not. (they span at least eastern,L central, and possibly mountain). But they do not have their onw time zone so) it is moot for that particular subsystem.    ------------------------------  % Date: Sun, 06 Oct 2002 01:31:19 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca> # Subject: Re: Bug in time zone files , Message-ID: <3D9FCA9D.E1FC3EB8@videotron.ca>  ' Tu further support my previous message: / http://www.worldtimezone.net/time-canada12.html   1 Clearly shows that yukon is in pacific time zone.   & http://www.yukonsite.com/yukon_map.htm  > Also has text that confirms Yukon is in the Pacific time zone.   ------------------------------  % Date: Sat, 05 Oct 2002 21:41:14 +0200 @ From: Arne =?ISO-8859-1?Q?Vajh=F8j?= <arne.vajhoej@mail.tele.dk>* Subject: Re: e-mail web client (SilkyMail)) Message-ID: <3D9F405A.30905@mail.tele.dk>    JF Mezei wrote:    > Francesco Gennai wrote: H >>There are also service providers that offer the access to a remote POPE >>mailbox from their remote web site. All of them use CGI the work as . >>IMP, SilkyMail, Mailman, AnyEmail, etc.....!    O > But don't they first move the email from the remote server via pop to a local D > mailbox before serving that local mailbox to the client via http ?     No.   1 They just get it via the POP protocol (using UIDL  or "leave on server").  1 They have to do it this way, because often people ! will get the email via POP later.   H > There is an issue of message integrity here. You can't download pop toM > temporrary files and serve them to the customer during his current session. H > What happens when the customer hangs-up just after the pop process hasK > retreived remote mail but before they have been displayed to the client ?     4 Because the email is not deletede on the POP server,( then it can retried over and over again.   No integrity problem.    Arne   ------------------------------  % Date: Sat, 05 Oct 2002 22:22:03 +0200 6 From: Arne =?ISO-8859-1?Q?Vajh=F8j?= <arne@vajhoej.dk>* Subject: Re: e-mail web client (SilkyMail)) Message-ID: <3D9F49EB.4070108@vajhoej.dk>    JF Mezei wrote:    > Arne Vajhj wrote:3 >>They just get it via the POP protocol (using UIDL  >>or "leave on server"). > M > But then you cannot really delete/manage your messages. Once they have been O > transfered (without deleting them), I do not think that the order of messages N > (and hence their numbering with regards to pop commands) is garanteed across > POP sessions.  > J > i.e. client is shown messages 1 to 5 that were retreived from remote POPO > server. Client takes an hour to read them, then decides to delete message #3. M > Meanwhile someone else accessed his POP mail and delete all messages, and 3 O > more messages arrived. When the command is made to delete message #3, the web H > interface will send a DELE 3 command which will delete the 3rd message< > currently in the mailbox which would be an unread message.    ' There are several way of handling that: ;    - the webmail interface could verify if #3 mail actually 1      is what it should be before doing the delete 6    - the webmail could explicit only allow one session,      access to one email account at the time    8 There are probably some webmail interface out there that does not handle it.   9 But is is a very common feature - I would expect it to be 5 used by *millions* of people world-wide. And it seems  to work.  0 BTW, how does VMS MAIL handle the same problem ?   Arne   ------------------------------  * Date: Sat, 5 Oct 2002 16:28:24 +0000 (UTC)+ From: david20@alpha2.mdx.ac.uk (David Webb) * Subject: Re: e-mail web client (SilkyMail)+ Message-ID: <ann3v8$hca$1@aquila.mdx.ac.uk>   Y In article <anmrjk$ep4$1@aquila.mdx.ac.uk>, david20@alpha1.mdx.ac.uk (David Webb) writes: t >In article <72f5654.0210042345.570287dc@posting.google.com>, francesco.gennai@iat.cnr.it (Francesco Gennai) writes:r >>jlw@psulias.psu.edu (j.lance wilkinson, (814) 865-1818) wrote in message news:<anktaf$ddk@r02n01.cac.psu.edu>...] >>> In article <aneq66$o4g$1@aquila.mdx.ac.uk>, david20@alpha1.mdx.ac.uk (David Webb) writes: x >>> >In article <72f5654.0210011225.4934b40b@posting.google.com>, francesco.gennai@iat.cnr.it (Francesco Gennai) writes:k >>> >>Mike Rechtman <michael.rechtman@digital.com> wrote in message news:<3D996314.3C585889@digital.com>...  >>>  >>> 	 >>(David) + >>I tried mailman from Endymion on OSU/VMS. @ >>It worked, but there were problems in downloading attachments. >>They appeared corrupted.& >>I didn't investigate on the problem. >> > P >I did download mailman but didn't get around to configuring it before I'd heardI >about Yahmail. My recollection was that I'd found out about mailman when O >someone had posted in a newsgroup about using it on VMS - I think with the OSU  >webserver. K >Did you check that the Mime types of the attachments were set correctly in  >the webserver ? >   N Sorry forget that last question. The Mime type should be being set by the Perl CGI not by the webserver.   
 David Webb VMS and Unix team leader CCSS Middlesex University   >  >  >David Webb  >VMS and Unix team leader  >CCSS  >Middlesex University  >  >>(Mike)C >>I'm interested in a solution that will permit me to run a webmail 
 >>on OpenVMS. C >>I would avoid to manage an unix box just to have a webmail access - >>to my PMDF (POP (otionally) IMAP) accounts. @ >>I pointed the attention of this newsgroup to Silkymail because2 >>I think that it should be a good solution (PHP).@ >>Maybe it is not difficult for some of you to investigate about3 >>the possibility to run it on OpenVMS environment. K >>The folks at Cyrusoft  ( http://www.cyrusoft.com ) said me that it should  >>run on any PHP platform.L >>There shouldn't need any porting, but currently I haven't time to test it. >>K >>Silkymail is derived from IMP that is considered one of the best webmail  ' >>(please visit http://www.horde.org ).  >>M >>I think that HP or Process Software (or other...) should look at porting a  7 >>good webmail client like Silkymail or IMP to OpenVMS.  >># >>Hp... Process..... any comments ?  >> >>Francesco  >>   >>> (David?)S >>> >Try MAILMAN from ENDYMION see http://www.endymion.com/  this uses PERL and I'm R >>> >pretty sure others have run it on VMS in the past. It uses POP to access the  >>> >user's mailboxes. >>> J >>> 	I tried, without success, to get this to work on OpenVMS with CSWS.  H >>> 	There's just too many local assumptions made by Endymion it seemed. >>> G >>> 	I wound up using Netwin's WEBMAIL on a Tru64 box to access my PMDF = >>> 	POPStore and VMS MAIL.MAI files using PMDF on OpenVMS.    >>> K >>> 	The Netwin folks DID indicate a willingness to work with me on porting J >>> 	their CGI script, webmail.cgi, to OpenVMS.  I just haven't taken themC >>> 	up on it yet.  For an educational site like me, it's less than H >>> 	$500/year as it is, and neither Tru64 or OpenVMS is going away here >>> 	for a while.  >>>  >>> T >>> +----"Never Underestimate the bandwidth of a station wagon full of mag tapes"--+F >>> | J.Lance Wilkinson ("Lance")		InterNet:  Lance.Wilkinson@psu.edu @ >>> | Systems Design Specialist - Lead	AT&T:      (814) 865-1818= >>> | Digital Library Technologies		FAX:       (814) 863-3560 6 >>> | 3 Paterno Library				"I'd rather be dancing..." F >>> | Penn State University		    A host is a host from coast to coast,O >>> | University Park, PA 16802	    And no one will talk to a host that's close G >>> | <postmaster@psulias.psu.edu>	    Unless the host that isn't close > >>> | EMail Professional since 1978	    Is busy, hung or dead.T >>> +---------"He's dead, Jim. I'll get his tricorder. You take his wallet."-------+= >>>                 [apologies to DeForest Kelley, 1920-1999] 7 >>> <A Href="http://perdita.lcs.psu.edu">home page</a>  N >>> <a Href="http://perdita.lcs.psu.edu/junkdec.htm">junk mail declaration</a>
 >>> --	/"\ >>> 	\ /	ASCII RIBBON CAMPAIGN >>> 	 X	AGAINST HTML MAIL  >>> 	/ \   ------------------------------  % Date: Sat, 05 Oct 2002 18:35:39 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca> * Subject: Re: e-mail web client (SilkyMail)* Message-ID: <3D9F6933.563F69@videotron.ca>   Arne Vajhj wrote:2 > BTW, how does VMS MAIL handle the same problem ?  ? The same way because this is a limitation of the POP protocol.    K However, if you use POP to transfer all mail from the remote pop account to I your VMS mail account, then the web interface can make smarter use of the ) VMSmailbox  due to the locking mechanisms    ------------------------------  % Date: Sat, 05 Oct 2002 15:27:58 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca> * Subject: Re: e-mail web client (SilkyMail), Message-ID: <3D9F3D3D.2BBF8E4E@videotron.ca>   Francesco Gennai wrote: H > There are also service providers that offer the access to a remote POPE > mailbox from their remote web site. All of them use CGI the work as . > IMP, SilkyMail, Mailman, AnyEmail, etc.....! >   M But don't they first move the email from the remote server via pop to a local B mailbox before serving that local mailbox to the client via http ?  F There is an issue of message integrity here. You can't download pop toK temporrary files and serve them to the customer during his current session. F What happens when the customer hangs-up just after the pop process hasI retreived remote mail but before they have been displayed to the client ?    ------------------------------  % Date: Sat, 05 Oct 2002 16:07:08 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca> * Subject: Re: e-mail web client (SilkyMail), Message-ID: <3D9F4669.593A8BA1@videotron.ca>   Arne Vajhj wrote:3 > They just get it via the POP protocol (using UIDL  > or "leave on server").  K But then you cannot really delete/manage your messages. Once they have been M transfered (without deleting them), I do not think that the order of messages L (and hence their numbering with regards to pop commands) is garanteed across
 POP sessions.   H i.e. client is shown messages 1 to 5 that were retreived from remote POPM server. Client takes an hour to read them, then decides to delete message #3. K Meanwhile someone else accessed his POP mail and delete all messages, and 3 M more messages arrived. When the command is made to delete message #3, the web F interface will send a DELE 3 command which will delete the 3rd message: currently in the mailbox which would be an unread message.   ------------------------------  % Date: Sat, 05 Oct 2002 19:49:10 +0200  From: Dirk Munk <munk@home.nl>) Subject: Re: First 7.3-1 problem detected 2 Message-ID: <eCFn9.3659$gD2.288978@zwoll1.home.nl>   Gib Copeland wrote:  > Dirk Munk wrote: >  >> Well, my first problem :-)  >>I >> I was trying to startup Apache T1.3 (which worked fine in 7.3) and it  ! >> stopped with an error message.  >>D >> This is what is happening now in the Apache startup command file: >>K >> $       create /name_table/nolog/executive/parent=lnm$system_directory - G >>               /protection=(system:rwed,owner:rwed,group:r,world:r) - % >>               apache$logical_names > >> $       set acl /nolog/new/object_type=logical_name_table -C >>               /acl=(identifier=[apache$www],access=read+write) - % >>               apache$logical_names 7 >> %SYSTEM-F-NOLOGTAB, no logical name table name match  >>. >> The table is there, so what is wrong here ? >> > ? > Set your DCL parse style back to "traditional" and try again. < > Or, in the SET ACL command, change apache$logical_names to > uppercase. > C > I'm not sure why the SET ACL command is treating it as lowercase, C > while the CREATE/NAME creates the table in uppercase.  Perhaps we B > need a DCL case/parsing flow chart similar to the one for object > security?  >  > Gib  > Q You're right, changing name of the table to uppercase did the trick. This is new  C beheaviour, I already had the extended parse style in use with 7.3.   Q The name of the table is always in uppercase (at present), so something is wrong  O   in the way the ACL commands (set & edit) work with logical name tables. They  G should always work, no matter if the name of the table is specified in  M uppercase, lowercase or any combination of the two. This beheaviour would be  * consistent with the way files are treated.   Regards,   Dirk   ------------------------------  % Date: Sat, 05 Oct 2002 12:07:15 -0500 1 From: "David J. Dachtera" <djesys.nospam@fsi.net> ) Subject: Re: First 7.3-1 problem detected ' Message-ID: <3D9F1C43.67447E97@fsi.net>    Gib Copeland wrote:  >  > Dirk Munk wrote: > > Well, my first problem :-) > > I > > I was trying to startup Apache T1.3 (which worked fine in 7.3) and it " > > stopped with an error message. > > E > > This is what is happening now in the Apache startup command file:  > > L > > $       create /name_table/nolog/executive/parent=lnm$system_directory -H > >               /protection=(system:rwed,owner:rwed,group:r,world:r) -& > >               apache$logical_names? > > $       set acl /nolog/new/object_type=logical_name_table - D > >               /acl=(identifier=[apache$www],access=read+write) -& > >               apache$logical_names8 > > %SYSTEM-F-NOLOGTAB, no logical name table name match > > / > > The table is there, so what is wrong here ?  > >  > ? > Set your DCL parse style back to "traditional" and try again. < > Or, in the SET ACL command, change apache$logical_names to > uppercase. > C > I'm not sure why the SET ACL command is treating it as lowercase, C > while the CREATE/NAME creates the table in uppercase.  Perhaps we B > need a DCL case/parsing flow chart similar to the one for object > security?   G I would expect case use/sensitivity to now be relegated to the programs G invoked by the commands (for external commands, internal commands would F be another question), and not for that to be within DCL itself. Dunno, tho...   --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  # Date: Sat, 05 Oct 2002 11:42:55 GMT 1 From: CSABA  HARANGOZO   <csabah@zipworld.com.au>  Subject: FS: Some DEC books...3 Message-ID: <3fAn9.26$O5.5170@nasal.pacific.net.au>   ; 	I have the following DEC books for sale. Postage is extra.     6 1.  VAX Rdb/VMS	Guide to using SQL	AA-JM33E-TE	1991	$5/ 2.  VMS V5.2	User's Manual		AA-LA98B-TE	1989	$5 4 3.  VMS V5.2	System Manager's M.	AA-LA00B-TE	1989	$56 4.  VMS V5.0	License Management U.	AA-LA33A-TE	1988	$28 5.  RRD42 Disc Drive	Owner's Manual	EK-RRD42-003	1991	$24 6.  DEC C	User's Guide for OVMS	AA-PUNZD-TK	1995	$104 7.  DEC C	Run-Time Lib. Ref. M.	AA-PUNED-TK	1995	$15B 8.  WordPerfect for VAX/VMS Systems  V5.0  MNUSVWP50-3/90 1990	$157 9.  VAX Fortran	Vol 1. User Manual	AA-D035E-TE	1988	$10 < 9.  VAX Fortran	Vol 2. Language Ref. M. AA-D034E-TE	1988	$10- 10. TCP/IP Jumpstart	Internet Protocol Basics  		by Andrew G. Blank		2000		$15  11. POLYCENTER Solutions Guide8 	Managing Today's Open Client/Server Environment	1995	$5- 12. Writing OpenVMS Alpha Device Drivers in C * 	Developer's Guide and Reference Manual	by8 	Margie Sherlock & Leonard SZubowicz  750 pages	1996	$306 13. DECthreads	Guide to DECthreads	AA-PV6NA-TK	1993	$5/ 14. OpenVMS System and Network Node Managem. II & 		Student Workbook + Exercise Book		$5> 15. VMS Internals and Data Structures Version 5 Update Express9 	by Ruth Goldenberg & Lawrence J. Kenah, 5 vols.	1989	$40  16. DECUSERVE	Australia 1993, 	Proceedings of the D.E.C. User Society			$58 17. DECUS	Software Library  1992/93 International ed.	$2; 18. Managing the Oracle RDB Database,  course book	1994	$10    					Cheers,    Csaba   I    ---------------------------------------------------------------------- E    * Csaba I. Harangozo     |    'To err is human', said the hedgehog E    * csabah@zipworld.com.au |           as he dismounted a wirebrush. I    ---------------------------------------------------------------------- ;    EARTH::AUSTRALIA:[SYDNEY]HARANGOZO.CSABA;1, delete? [N]:    ------------------------------  % Date: Sat, 05 Oct 2002 18:39:12 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca>  Subject: Re: Merger - smerger , Message-ID: <3D9F6A07.D4824028@videotron.ca>   Neil Rieck wrote: N > "Compaq Computer Corporation is a wholly-owned subsidiary of Hewlett-Packard > Company."   K I think it has always been quite clear that it was HP buying Compaq with HP K making the big decisions. They may have worded it as a merger so that Curly H and Winkler wouldn't be seen as such losers but the fact remains that HP7 bought Compaq to eliminate Compaq from the marketplace.    ------------------------------  $ Date: Sat, 5 Oct 2002 16:33:10 -0400) From: "Neil Rieck" <n.rieck@sympatico.ca>  Subject: Merger - smerger 9 Message-ID: <d0In9.5458$sB3.308863@news20.bellglobal.com>    Check out this link:L http://www.compaq.com/support/asktima/operating_systems/009F6DF1-BC7EC4E1-1C	 02A1.html  The bottom line reads:L "Compaq Computer Corporation is a wholly-owned subsidiary of Hewlett-Packard	 Company."   H So there you have it. Merger - smerger. This is no different than CompaqH buying Digital back in 1998 (except that HP may know how to run a non-PC company)  
 Neil Rieck Kitchener/Waterloo/Cambridge,  Ontario, Canada.! http://www3.sympatico.ca/n.rieck/    ------------------------------  $ Date: Sun, 6 Oct 2002 07:41:39 +0200* From: DWParsons@T-Online.de (Dave Parsons)! Subject: Re: mouning floppy drive P Message-ID: <Ej0w7lFo08Zw-pn2-Ih5zwg8JKCrX@jupiter.dwparsons.dialin.t-online.de>  N On Fri, 4 Oct 2002 13:56:12 UTC, "Hamid Bourchi" <hbourchi@hotmail.com> wrote:  & > By 'normal' i mean MS-DOS format ... >   & Then what you probably want is mtools.  @ I can't remember the URL exactly, but try Google or www.tux.org.   --   Dave      ------------------------------  % Date: Sat, 05 Oct 2002 12:04:09 -0500 1 From: "David J. Dachtera" <djesys.nospam@fsi.net>  Subject: Re: Mount ISO Image& Message-ID: <3D9F1B89.EDB55A5@fsi.net>   Larry Kilgallen wrote: > ] > In article <3D9E68D9.F8998089@fsi.net>, "David J. Dachtera" <djesys.nospam@fsi.net> writes:  > > rob@netcarrier.net wrote:  > >> > >>         Hi  > >>2 > >>  Is there a tool to mount ISO images for VMS?6 > >>  I'm using the VCD tool on Windows to Test Images7 > >>  But it would be neat to test right on the VMS box  > > L > > From my hobbyist machine, MOUNTing one of the CDs I'll be passing out atB > > the pre-symposium seminar I'm giving come Monday in St. Louis: > > + > > DJAS01::DDACHTERA$ mount/over=id dka400 . > > %MOUNT-I-WRITELOCK, volume is write lockedA > > %MOUNT-I-CDROM_ISO, HPETS2002:HPETS2002 (1 of 1) , mounted on  > > _DJAS01$DKA400:  > > C > > The disk was written using Gear for Windows in ISO-9660 format.  > L > On earlier versions of VMS one must explicitly specify /MEDIA_FORMAT=CDROMK > for mounting an ISO9660 CDROM.  In my experience, one must still add that K > if mounting an ISO-9660 volume other than on a genuine CDROM drive.  That I > is, when I mount an Infoserver partition on VMS I must specify it, so I L > presume the same might be true using the software driver someone mentionedI > earlier in this thread for mounting an image without committing it to a  > CDROM.  ( DJAS01::DDACHTERA$ mou/noassi/for dka400- %MOUNT-I-MOUNTED,  mounted on _DJAS01$DKA400: - DJAS01::DDACHTERA$ copy dka400: hpets2002.iso 1 %COPY-W-INCOMPAT, _DJAS01$DKA400:[].; (input) and E DKA0:[DDACHTERA]HPETS2002.ISO;1 (output) have incompatible attributes  DJAS01::DDACHTERA$ dir *.iso   Directory DKA0:[DDACHTERA]  > DK2.ISO;1             629336/629336   25-MAR-2002 21:45:59.94  (RWED,RWED,RE,)  ELX-PRE1-RC2-UPDATED-CD1.ISO;1>                          567/568      23-MAR-2002 21:46:17.37  (RWED,RWED,RE,) > HPETS2002.ISO;1        41552/41552     5-OCT-2002 11:37:03.52  (RWED,RWED,RE,)   ' Total of 3 files, 671455/671456 blocks. # DJAS01::DDACHTERA$ say 4155200/2048  2028 DJAS01::DDACHTERA$ sh dev ld  F Device                  Device           Error    Volume         Free 	 Trans Mnt F  Name                   Status           Count     Label        Blocks	 Count Cnt . DJAS01$LDA0:            Online               0- DJAS01::DDACHTERA$ ld conn hpets2002.iso lda1 $ DJAS01::DDACHTERA$ moun/over=id lda1* %MOUNT-I-WRITELOCK, volume is write locked> %MOUNT-I-CDROM_ISO, HPETS2002:HPETS2002 (1 of 1) , mounted on 
 _DJAS01$LDA1:  DJAS01::DDACHTERA$    B Sorry 'bout the text wrap. That's kinda ugly in places, ain't it?!  / Anyway, that's using LD V6.2 on OpenVMS V7.1-2.   D Funny part is, the Toshiba CD-ROM I have in this machine is so slow,? it's actually faster to FTP the disk image from the Gear Images  directory on the PC.   --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------   Date: 5 Oct 2002 17:37:17 -0600 - From: Kilgallen@SpamCop.net (Larry Kilgallen)  Subject: Re: Mount ISO Image3 Message-ID: <nFhmtHnhrEEQ@eisner.encompasserve.org>   Z In article <3D9F1B89.EDB55A5@fsi.net>, "David J. Dachtera" <djesys.nospam@fsi.net> writes: > Larry Kilgallen wrote:  M >> On earlier versions of VMS one must explicitly specify /MEDIA_FORMAT=CDROM L >> for mounting an ISO9660 CDROM.  In my experience, one must still add thatL >> if mounting an ISO-9660 volume other than on a genuine CDROM drive.  ThatJ >> is, when I mount an Infoserver partition on VMS I must specify it, so IM >> presume the same might be true using the software driver someone mentioned J >> earlier in this thread for mounting an image without committing it to a	 >> CDROM.    > DJAS01::DDACHTERA$ sh dev ld > H > Device                  Device           Error    Volume         Free  > Trans Mnt H >  Name                   Status           Count     Label        Blocks > Count Cnt 0 > DJAS01$LDA0:            Online               0/ > DJAS01::DDACHTERA$ ld conn hpets2002.iso lda1 & > DJAS01::DDACHTERA$ moun/over=id lda1, > %MOUNT-I-WRITELOCK, volume is write locked@ > %MOUNT-I-CDROM_ISO, HPETS2002:HPETS2002 (1 of 1) , mounted on  > _DJAS01$LDA1:  > DJAS01::DDACHTERA$   > D > Sorry 'bout the text wrap. That's kinda ugly in places, ain't it?! > 1 > Anyway, that's using LD V6.2 on OpenVMS V7.1-2.   9 Hmmm.  Does the LDA0: device tell VMS it is CDROM drive ?    ------------------------------  $ Date: Sat, 5 Oct 2002 19:49:18 +0200$ From: "Georg Howen" <georg@howen.de> Subject: Re: NETPrint 1000/ Message-ID: <ann8n1$3fi$07$1@news.t-online.com>   A "Fabio Cardoso" <fabiopenvms@yahoo.com.br> schrieb im Newsbeitrag : news:20020906123919.63058.qmail@web20203.mail.yahoo.com...2 > I discovered an old NetPrint 1000 in my network. > 3 > Anyone knows how can I configure TCPIP address in , > this dinossaur ? I searched www.osicom.com >  site 3 > which purchased this Digital hardware but I didnt  > discover anything. >   J I just found one myself and even got it to work with W2K/XP - that's how I found your post.   1. Set the IP address with:  arp -s IP-Address MAC-Address    2. Then ping the IP-Adress  G The Netprint will then read the IP-Address from the ping packets, reset H itself and after a few minutes should have the new address. Then you canL telnet to the machine and configure the rest. Standard username and password is sysadm/sysadm.   F If you know the current IP you can obviously telnet directly to it and change the IP.   Georg    ------------------------------  % Date: Sat, 05 Oct 2002 15:06:05 -0700 " From: GreyCloud <cumulus@mist.com>! Subject: Re: OpenVMS is strategic ( Message-ID: <3D9F624D.A94CD50C@mist.com>   Jerry Leslie wrote:  > H > Lorraine Profeta (profetal@greaterbaynet.com@greaterbaynet.com) wrote: > : ! > : Who's still running EXEC 8...  > : I > Unisys customers who are running its descendent, OS 2200, per the posts < > of Peter DeSilva, and what's available on web pages, e.g.: > N >    http://www.tek-tips.com/gviewthread.cfm/lev2/4/lev3/27/pid/302/qid/274565- >    Unisys DBMS solutions - unisys 1100/2200  > H >   "Home > Forums > Programmers > DBMS Packages > Unisys DBMS solutions >    unisys 1100/2200  >  >    thread302-274565  > % >    rtamma (Programmer) May 16, 2002  > A >    what are the differences between the unisys1100/2200 and the B >    other  machines like A- series or NX series for that matter ? >  >    MBaker (MIS) May 20, 2002 > J >    The OS 2200 based machines and the MCP based machines have nothing in* >    common, except being Unisys machines. > I >    The OS 2200 based machines (11xx, 1100/xx, 2200/xxx, IX4800, IX5600, F >    IX5800, IX6600, IX6800, IX7802, IX7840) are all desendents of theG >    Sperry (formerly Univac) line.  These machines are based on 36-bit  >    one's complement hardware.  > G >    OS 2200 itself is a desendent of EXEC 8.  The operating system has " >    evolved since the early 60's. > ? >    Perhaps someone else will describe the MCP based systems."  > B > Old timers who worked on Univacs may want to "SLJ" to this site: > 8 >    http://www.fourmilab.ch/documents/univac/index.html >    UNIVAC Memories  5 Ah yes!  The 1107s.  Repaired so many of those at the 	 shipyard.    ------------------------------  " Date: Sat, 5 Oct 2002 13:08:00 GMT- From: bdc@world.std.com (Brian 'Jarai' Chase) ! Subject: Re: OpenVMS is strategic & Message-ID: <H3IF5C.Dn2@world.std.com>  3 In article <YtjzdKBUxi6J@eisner.encompasserve.org>, : Bob Koehler <koehler@eisner.aspm.encompasserve.org> wrote:F > In article <3D9D76AF.1010000@nospamn.sun.com>, Andrew Harrison SUNUK > Consultancy writes:   G > > 3.	Can you think of any reason why this kind of offer will be of no M > > interest to Sun/IBM customers except if they are also OpenVMS customers ?  > > O > > I hope so. If they arn't OpenVMS customers already then the chances of them L > > making their minds up for a change of platform and doing it plus issuingM > > the order in a timeframe that will fall inside the offer period is almost  > > nil. > @ >    So Sun has no hopes of attracting existing IBM, HP, or Dell< >    customers, each of which would have to change platform?  A I'd be more inclined to say that Sun has a fair amount of hope in ? attracting existing IBM AIX, HP HPUX, and HP Tru64 customers.   D Equivalently, IBM and HP have just as much as hope in attracting SunH Solaris customers to their Unix offerings.  All of them would be able toD attract Dell Windows customers who needed to move to a more scalableB platform, though that's a tougher migration, it's one that has theI necessity of moving to a more scalable platform behind it.  And certainly D I could see Windows users moving to an OpenVMS solution for the sameC reasons--as long as OpenVMS supported the applications they wanted.   D I could see Unix customers moving to OpenVMS for things like processJ control or some financial systems where 24x7x365 availablity and near 100%H system uptime is either critical or highly advantageous to the business.   -brian.  --  F --- Brian Chase | bdc@world.std.com | http://world.std.com/~bdc/ -----H This counter is [6,177,399,753] times as pointless as a real one.  -- K.   ------------------------------  " Date: Sat, 5 Oct 2002 12:17:18 GMT- From: bdc@world.std.com (Brian 'Jarai' Chase) ! Subject: Re: OpenVMS is strategic & Message-ID: <H3ICsu.CKw@world.std.com>  5 In article <ank9e6$f8hqo$1@ID-135708.news.dfncis.de>,n) Bill Gunshannon <bill@cs.uofs.edu> wrote:f( > In article <H3FqIo.Kr0@world.std.com>,2 > 	bdc@world.std.com (Brian 'Jarai' Chase) writes:   > > M > >                       It's about as likely as a company running primarily ) > >     on OpenVMS changing over to Unix.w > >  > F > I don't know how to break this to you, but not only does this happenH > all the time, the current owners of VMS are pushing it.  Or do you see2 > the forced migration to HPUX as something else??  G Admittedly, I was trying to be polite.  The main difference between the H Unix and OpenVMS world is that there are several large vendors which allG provide Unix.  Most of the major applications that people would want to E run under Unix tend to be supported across at least Solaris, AIX, andeJ HPUX, and increasingly on Linux or even Apple's OS-X.  If any one of thoseI vendors would tell their customers, "We're sorry, you're going to have to-J migrate to our new non-Unix XYZ operating system," most of those customersJ would maintain their legacy systems and, over the long term, bail and moveF to one of the other roughly equivalent Unix operating systems that are available elsewhere.  G OpenVMS customers don't have that sort of option.  When the only vendor J of OpenVMS is telling its customers, "You have to use HPUX," you're pretty
 much screwed.   % So I'll modify my original statement:e  G    A company wanting to change from Unix to OpenVMS is about as likely u7    as a company wanting to change from OpenVMS to Unix.@   Rambling on...  J Reflecting on the brochure which is being discussed in the thread, the oneG stating that "OpenVMS is Strategic", I have to wonder about that claim.,A It's certainly a strategic choice if HP has outlined some sort ofnJ easy/inexpensive upgrade path from OpenVMS/Alpha to OpenVMS/IA64.  Are theG latest Alpha servers designed so that they can be upgraded to IA64 withiH board swaps?  I remember Digital doing this for some of their last largeI VAX systems.  If so, I can see it as being strategic for existing OpenVMSA& customers to remain OpenVMS customers.  G As for it being a strategic move for Unix shops, I hardly could imagineWA any place running primarily Unix wanting to give up the strategic H advantage they have of being able move between different vendors of UnixI OSes.  Technical weaknesses aside (in comparision to OpenVMS), Unix has auE lot of practical advantages.  I've administered quite a few different F types of Unix systems, ranging from Solaris, AIX, IRIX, Linux, NetBSD,I OpenBSD, FreeBSD, NeXTSTEP, and now OS-X; they're all similar enough thatsF it's been easy for my sysadmin skillset to be useful from the junkiestG Linux/Intel box to the largest multi-processor SGI, Sun and IBM systems:  I've supported for my employers.  I Unix shops also have lots of options when they looks for a new systems.  9I This gives us leverage to make deals.  Lets say I'm primarily a Sun shop;yG I can pit the sales guy from IBM, Sun, SGI, and HP against eachother toBF drive the price of my servers down in a bidding war--even if I alreadyJ know on day-1 that I'm going to buy a Sun at the end of this.  It may takeG a month or two to let the bidding run its course, but at the end of it, L you can bet I'll have a better price on the Sun equipment I wanted to buy.  J In the case with OpenVMS, there's only one supplier of your OS and they'reH also the only supplier of equipment which runs that OS.  Your ability to. negotiate pricing is pretty much non-existant.  F I'd be willing to agree that OpenVMS is a far better operating system,B technically speaking, than any of the Unix operating systems beingH offered.  But moving to OpenVMS means that my business--or as a sysadminE in my case--my livelihood, is in the hands of a single company.  Or ILG guess with OpenVMS, in the hands of single companies; all of which have/H shown questionable competence in their handling of OpenVMS as a product.  I Particularly, in the case of HP, you've got a company which is now actingoI schizophrenic about OpenVMS.  On one hand, it sounds like they're pushingcC HPUX as a migration path away from OpenVMS; while at the same time,nF they're saying the OpenVMS is strategic and are offering Sun/IBM usersH discounts to move to OpenVMS.  What the hell?  Why wouldn't HP /also/ beE targeting HPUX for these people?  It sounds to me like there are some J major communication issues within the company and that they don't have anyC sort of coherent vision yet.  They're still spinning in post-mergero
 confusion.  G If I'm an IBM or Sun customer, I'm going to stay /far/ away from all of F HPUX, Tru64, OpenVMS, Alpha, and Itanium until HP figures out what theI hell it is they're trying to do.  I'll probably still buy their printers,e though.r   -brian.  -- lF --- Brian Chase | bdc@world.std.com | http://world.std.com/~bdc/ -----H This counter is [6,177,399,753] times as pointless as a real one.  -- K.   ------------------------------  % Date: Sat, 05 Oct 2002 20:54:01 -0400o- From: JF Mezei <jfmezei.spamnot@videotron.ca>o! Subject: Re: OpenVMS is strategic , Message-ID: <3D9F8999.4D4B56B0@videotron.ca>   Bill Todd wrote:M > That couldn't have happened at the time, because DEC simply didn't know hownK > to build hardware that cheaply:  if it had sold its products at the priceiM > IBM charged for its PC, it would have lost quite a bit of money on each one-  > (well, maybe not the DECmate).   Horse radish.   N If IBM was able to compate against Apple and Commodore, there is no reason DECJ ,which was able to build cheaper hardware than IBM, couldn't have competed+ too. Where there is a will, there is a way.e  F DEC has consistently shown that it was unwilling to compete against itW competitors, perhaps because it refused to wake-up to the existence of new competitors.s   ------------------------------  % Date: Sat, 05 Oct 2002 15:48:21 -04000- From: JF Mezei <jfmezei.spamnot@videotron.ca>5! Subject: Re: OpenVMS is strategic.+ Message-ID: <3D9F4203.982F3E0@videotron.ca>k   Bill Todd wrote:I > The real beginning happened well before KO's departure in 1992.  It wasoK > certainly as early as the 1988 cancellation of the PRISM DECwest project,PM > which I've been told was itself due to continuing internal friction between, > the VMS and Unix factions.  L I'd say that the real beginning was when DEC refused to commercialise/marketM its PDP11-in-a-VT100 as a viable personal computer. Commodore had the vision. G Apple had the vision, and IBM got the vision (rather late in the game).r0 Digital had it now, but *chose* not to push it.   0 (Perhaps because it wanted to push VAX instead).  J And sometimes between 1987 and 1990, Olsen started to bring in some ex-IBMJ folks and, whether coincidence or not, Digital became arrogant , kept highM prices saying that its products were so much better that they deserved highers prices etc etc etc.o  J RE: VMS can't run on RISC. At the time he said that, remember that DEC hadJ started to sell MIPS based Unix workstations, and it is very possible thatK MIPS lacked the required stuff to run VMS. Recall that Alpha had many hooks  added to support VMS.2  I Yes, one could argue that Digital could have paid MIPS to incorporate thecL required features into MIPS and then migrate VMS to MIPS. (today's landscapeK might be totally different had DEC done that - no Alpha, DEC might still beP2 alive, and MIPS might be the "industry standard".)  H The 1980s were just the foundations for the disaster. The 1990s were the= execution of the disaster instead of correcting the problems.   K DEC had great products, poor prices/marketing in the 1980s. When Palmer wasdN brought in, it was expected that he would fix the prices and marketing. He notN only didn't fix those, but he decimated the company with his quarterly reorgs,I and tore down the software products and sent strong singlas about lack ofeM future for VMS. When you discard the software products that made VMS popular,hK you should give strong incentive for ISVs to replace your onw products withEM theirs. But if you tell the iSVs "don't bother porting tol VMS, we're killingw+ VMS", then those products don't get ported.e   ------------------------------  # Date: Sat, 05 Oct 2002 20:11:32 GMT 1 From: LESLIE@JRLVAX.HOUSTON.RR.COM (Jerry Leslie)i! Subject: Re: OpenVMS is strategicu; Message-ID: <UHHn9.73208$Fw2.2175371@twister.austin.rr.com>a  F Lorraine Profeta (profetal@greaterbaynet.com@greaterbaynet.com) wrote: :h : Who's still running EXEC 8...s : G Unisys customers who are running its descendent, OS 2200, per the postse: of Peter DeSilva, and what's available on web pages, e.g.:  L    http://www.tek-tips.com/gviewthread.cfm/lev2/4/lev3/27/pid/302/qid/274565+    Unisys DBMS solutions - unisys 1100/2200m  F   "Home > Forums > Programmers > DBMS Packages > Unisys DBMS solutions    unisys 1100/2200D      thread302-274565m  #    rtamma (Programmer) May 16, 2002a  ?    what are the differences between the unisys1100/2200 and theI@    other  machines like A- series or NX series for that matter ?      MBaker (MIS) May 20, 2002  H    The OS 2200 based machines and the MCP based machines have nothing in(    common, except being Unisys machines.  G    The OS 2200 based machines (11xx, 1100/xx, 2200/xxx, IX4800, IX5600,hD    IX5800, IX6600, IX6800, IX7802, IX7840) are all desendents of theE    Sperry (formerly Univac) line.  These machines are based on 36-bitG    one's complement hardware.t  E    OS 2200 itself is a desendent of EXEC 8.  The operating system has8     evolved since the early 60's.  =    Perhaps someone else will describe the MCP based systems."e  @ Old timers who worked on Univacs may want to "SLJ" to this site:  6    http://www.fourmilab.ch/documents/univac/index.html    UNIVAC Memories  2 --Jerry Leslie   (my opinions are strictly my own)9   Note: leslie@jrlvax.houston.rr.com is invalid for emailf   ------------------------------  $ Date: Sat, 5 Oct 2002 14:55:25 -0400* From: "Bill Todd" <billtodd@metrocast.net>! Subject: Re: OpenVMS is strategice6 Message-ID: <DeOdndjQotcTqAKgXTWc3A@News.GigaNews.Com>  J "Lorraine Profeta" <profetal@greaterbaynet.com@greaterbaynet.com> wrote in. message news:ann15h$sa4$1@news.chatlink.com...G > It seems to me that there are a lot of "young people" in this NG, and I > everywhere else in life.  I think I should share my elderly experience:   I And that's a Good Thing (at least IMO).  But I think some of what you saye- indicates confusion about what makes VMS VMS.g   >uJ > (1) When asked about implementing RISC architecture in VMS systems (thatJ > meant VAX back then) Ken Olsen replied that VMS required a CISC computer so' > it would never be put on a RISC chip.   L Well, you have to remember that Ken's technical contributions to VAX were inL the area of the early power supplies (IIRC), and that software was never hisK forte at all.  Though even some reasonably experienced software people were>/ confused about exactly what RISC was back then.    >'F > (2) In 1987 DEC offers the OSF group, DECWindows as the standard guiI > interface to OSF Unix.  The committee agrees on X-Windows and Motif (as  youhK > should already know).  DEC also fight to have DEC Unix used as the kerneloJ > for OSF Unix; the committee agrees on AIX (you should already know this, > too).m  J That's interesting, since my impression was that OSF/1 was more Mach-based9 than anything else.  But I'm no expert on its provenance.    >tI > (3) In 1989 (give or take 1 year) Ken Olsen states that, "Unix is snake> oil.K > If you believe in Unix then you believe in snake oil.".  The shareholderspI > committee fires Ken Olsen for his "lack of vision".  This really markedd the  > beginning of the end for VMS.   G The real beginning happened well before KO's departure in 1992.  It was I certainly as early as the 1988 cancellation of the PRISM DECwest project,IK which I've been told was itself due to continuing internal friction betweenw the VMS and Unix factions.   >aJ > (4) The plan for OpenVMS was (I read this before the Alpha was released)K > was to become completely compatible with OSF1 Unix (DEC Unix, later to beaK > called Tru64); i.e., you could create programs on OpenVMS and run them ondJ > OSF1 Unix, or vice-versa.  Ultimately, OpenVMS would be the standard for OSF	H > Unix.  Lofty goals that were never realized, but it was a statement of > direction by DEC.6  G And might have made a huge difference if it had been followed through - B though given the amount of disdain in which the VMS/RSX people hadJ traditionally held Unix (and RSTS, and TOPS...) I'm not too surprised thatI this goal (which I can't remember ever having heard of formally, though IsA wasn't following DEC closely back then) was not strongly pursued.M   ...f  C > OpenVMS is Posix compliant, just like any good Unix OS should be.d  I Well, it was for a while, and reportedly will be again soon.  And the COE E work should markedly improve upon it - which is a good thing, becausedJ POSIX-compliance is not worth as much as some non-Unix people might think.     E.g.,jI > compare Files-11 to the AIX jfs.  Obviously OpenVMS uses dot delimiters  forIL > directory names and everything below the disk name has to be surrounded inK > [], and OpenVMS uses different directory names.  Past that the details ofc) > jfs and Files-11 are extremely similar.g  L Actually, they are less similar underneath the covers than they are in their interfaces and syntax.  %   Both file systems have a disk indexlK > in the "root" directory ([000000] for OpenVMS) and those indexes point toaJ > dir files that contain the names of files and other dir files that point toG > more files and more dir files that point to ..., etc.  The difference  being-/ > that in jfs those dir files are called inodes0  I No:  a Unix 'inode' is roughly equivalent to an entry in an ODS-1/2 indexRL file (i.e., to a 'file header').  IIRC jfs directories are b-tree-structuredH while ODS-1/2 directories are linear lists (though ordered lists, in the case of ODS-2).   A ODS-2 directories are themselves files, but I'm not sure that JFS J directories are:  they may be a special-purpose entity that isn't based on an underlying file.    ...r  L > I actually have a point to all of this.  Going back to item (1); VMS neverK > was put on a RISC chip.  Alpha systems have a MACRO-32 compiler, so AlphaYF > systems have an interface to the low level code of VAX computers; so OpenVMSh* > became middleware for the Alpha systems.  E No.  While a significant amount of MACRO-32 was compiled in early VMSuJ releases on Alpha, a fair amount of VMS code even back then was written inG higher-level languages (primarily C, I think) and simply recompiled foreE Alpha.  And over time a great deal of the remaining MACRO-32 code goteH re-written (again, mostly in C) - not that there's that much substantiveI difference between compiling VAX assembler code into Alpha assembler codeu) and compiling some higher-level language.       Today the OpenVMS interface is > just that; an interface.  C Well, I'd have to agree that an interface is an interface.  But theiJ statement doesn't mean what I suspect you think it does:  VMS is every bit- as much VMS running on Alpha as it is on VAX.e  4   Try to cluster a VAX running VMS 5.5 with an Alpha1 > running OpenVMS 6.2 or higher; it doesn't work!h  K Backward-compatibility sometimes must be sacrificed at some point.  It doessL surprise me that it would have been broken between one major release and the+ next, but presumably there was good reason.e  I And it would also be a bit surprising if you couldn't cluster an Alpha in.L that situation but could cluster a VAX running the same release as the Alpha was.     When you do run a newer OSL > version on the VAX you can loosely couple, but only if you are using ODS-2 > on both the VAX and Alpha.  K ODS-2 is fundamental to VMS itself, so that's hardly surprising.  If you'renA not running ODS-2 (or perhaps now ODS-5 as an alternative, or theoK now-defunct Spiralog storage underpinnings which ODS-2 remained on top of),cF I don't know that you can cluster at all (though perhaps a stand-alone0 system could have run ODS-1 up to some release).  -   Now that VAX systems have been discontinuedrK > ODS-2 will eventually disappear, and nobody will be able to cluster theireJ > VAXStation (or any other VAX) to their Alpha cluster.  I sincerely doubt/ > you'll see ODS-2 on the new Itanium machines.a  K I will be flabberghasted if you don't (assuming you see VMS at all there) ->H unless ODS-5 (which is itself ODS-2 with some enhancements) replaces it.   >sI > This in itself is no big deal.  OSes stick around while they are usefulh andaG > then fade away.  Who's still running EXEC 8, or RSTS (OK, some peoplec stilliD > are running RSTS, but it's a tiny group that is becoming extinct)? However,K > There is still a "link" between the original VMS and OpenVMS. even thoughoI > it's becoming more and more nebulous.  When OpenVMS sits on top of EPICtF > architecture I doubt that there will be anything left of the old VMS exceptI > the use of a Files-11 looking file structure and a DCL interface to it.u  I Again, you're confused.  While there may already be no remaining VMS V1.0 @ code, VMS is every bit as much VMS as it ever was - plus all the! enhancements added along the way.t  3 And if/when it appears on Itanic, it still will be.b  L > Does anybody think that today's Mustang is anything like the 1965 Mustang?K > I drove a 2001 Mustang last year and the way you sit in it is reminiscent, ofI > the original Mustang.  Today's Mustang gives you a "pony car" feel that  wasjL > missing in Mustangs of the 70s and 80s. So if you miss the old Mustang youJ > could get some of the feeling of it in today's car of the same name, but you)F > would be aware that it was a completely different implementation and > architecture.t  C Well, as I said above, the implementation may already be completelynG different if you define that as having no remaining VMS V1 code.  And InK rather doubt that V7.3 will run in 256 KB of memory off a pair of RK06s (ifs you could find any).  D But your analogy is otherwise a poor one.  Unlike the Mustang, VMS'sL fundamentals have not been replaced over time but merely (actually, greatly)I enhanced (that, in fact, is occasionally a weakness:  a few items such ascJ the file system and RMS could have benefited from a more complete upgrade,I but the one real attempt at the former - Spiralog - fell short and wasn'tr, completed; XFC will help, though - finally).  E VMS's drawbacks are that it has not evolved enough (to be more widelysH acceptable) rather than that it has evolved too much, and that its ownerD isn't interested in it (so its future is dubious, and its present isL hampered by its availability only on a declared-dying platform plus a future4 platform that's inferior to the one it's replacing).  L But for anything you bought VMS V1, or V2, or V3, or V4, or V5, or V6 to do,F VMS V7 (and V8, if and when) should do at least as well and often muchI better (though possibly requiring more hardware resources in some cases). L VAX is indeed gone, but Alpha was a worthy replacement.  Alpha is on its wayI out, and *that's* a major mistake - but it doesn't affect VMS's VMS-ness, H just its commercial viability (and the pain customers must eventually go$ through to migrate to new hardware).   - bill   ------------------------------   Date: 5 Oct 2002 13:21:06 -0700o From: tironef@yahoo.come4 Subject: Re: Originator of detached process from DCL= Message-ID: <a159f330.0210051221.7e7c851d@posting.google.com>   G I can't modify abatmgr.  It is a purchased job scheduler.  Great ideas!M   Thanks,.   Frank-  a JF Mezei <jfmezei.spamnot@videotron.ca> wrote in message news:<3D9DF5EA.9FE73534@videotron.ca>...	 > tironef@yahoo.com wrote:D > > I'm trying to determine which process or application created theE > > detached process.  This job can be just submitted or created as aeJ > > detached process from a process named ABATEMGR.  If my job is run from0 > > ABATEMGR, I need to do additional procssing. >  > ouch.  > O > Can ABATEMGR be modified ? If so, then ABATEMGR could "pass a message" to the O > detacted process to indicate it should do the extra processing. One way to doi" > this is to use the process name. > I > I.E. when ABATEMGR creates the detached process, it specifies a specialtL > process name. And when the detached process starts , it checks its processK > name to see if it is the special keyword and if so, then does the special @ > processing and then renames itself to a standard process name. > L > I am not really sure it is possible for a detached process to know who its > parent is.   ------------------------------  $ Date: Sat, 5 Oct 2002 18:50:33 -05002 From: "Stuart Johnson" <ssj152 AT charter DOT net> Subject: Re: tcp/ip == UCX/ Message-ID: <upuunbr09c9t98@corp.supernews.com>-   Thanks for the correction!  J "Lorraine Profeta" <profetal@greaterbaynet.com@greaterbaynet.com> wrote in. message news:anmsbg$p6k$1@news.chatlink.com...  > Ultrix Compatibility Executive >-   ------------------------------  # Date: Sat, 05 Oct 2002 21:27:31 GMTH  From: cjt <cheljuba@prodigy.net>( Subject: Re: The perils of reusable code+ Message-ID: <3D9F5983.65DF30F0@prodigy.net>   $ "Webb, William W Raleigh, NC" wrote: >  <snip>< > Eager to demonstrate their flying skills for some visiting; > American pilots, the hotshot Aussies "buzzed" the virtualC< > kangaroos in low flight during a simulation. The kangaroos< > scattered, as predicted, and the visiting Americans nodded; > appreciatively... then did a double-take as the kangaroosm9 > reappeared from behind a hill and launched a barrage ofo= > Stinger missiles at the hapless helicopter. (Apparently theg6 > programmers had forgotten to remove that part of the > infantry coding.)- <snip>  4 C'mon, now.  I saw that scene in "Crocodile Dundee."   ------------------------------  % Date: Sat, 05 Oct 2002 22:24:09 +020096 From: Arne =?ISO-8859-1?Q?Vajh=F8j?= <arne@vajhoej.dk> Subject: VMS pages update.) Message-ID: <3D9F4A69.5060100@vajhoej.dk>D   Just some link fixing.   New main site:"    http://www.vajhoej.dk/arne/vms/  2 (http://www.levitte.org/~ava/ is still working and will be updated)   Arne   ------------------------------  $ Date: Sat, 5 Oct 2002 19:52:06 +0200+ From: Roland Barmettler <rob@bbp.ch.remove>u) Subject: Re: Volume shadowing performancee7 Message-ID: <20021005195206.126f42b1.rob@bbp.ch.remove>p   JF Mezei wrote:  > "Bradford J. Hamilton" wrote:  > > D > > I ran a quick test, FTP'ing a 50Meg file to a single disk, and aB > > dual-member shadow-set (9Gig, 10KRPM in each case).  I ran theE > > test three times for each disk, and saw no appreciable differencec3 > > to either disk (4.8 to 5.4Mb for each transfer)l >   C This is what I'd expect. I wouldn't even mind half the performance!  But 1/10....  C > IS it possible that the target drive is badly fragmented and thusu > writes are slower ?    No, this is not the case.-  -C > Are the shadowset members linked via MSCP on the ethernet ?  That C > would essentially halve the ethernet throughput since each packet3C > sent by the FTP client would be "echoed" on the ethernet as it is<. > transmitted to all members of the shadowset.  B No it's a standalone machine. I has two KZPBA-CX (Qlogic 1040B) UWA controllers four disks on one, three on the other controller. The B fourth disk is alone, the rest has an equivalent shadow partner on the other controller.t   C > A better measure might be to use COPY to send a large file to thei? > shadowset or to a non-shadow drive and then use tools such ase< > MONITOR DISK to see what the maximum/average throughput is  C Good idea. The results were a bit inconclusive (thanks to XFC, as ItE found out later). But generally, copying a 20M file from disk to diskd= yielded better results for the shadow sets as FTPing on them.gE After disabling XFC, the performance was improved by about 40% in allS( cases.   Im getting puzzled even more...  C I got an IO operation rate of 120 when copying from the single diskiB to the shadow set and 90 the other way around. This I would expectF since the disks of the shadow set are faster. But why its only getting' 40-80 over the network... I don't know.    Greetings, Rolandi  F --------------- bbp - Biveroni Batschelet Partners AG ----------------:              Bahnhofstrasse 28, CH-5401 Baden, SwitzerlandF ----------------------------------------------------------------------   ------------------------------   Date: 6 Oct 2002 00:49:56 GMT-, From: bill@gw5.cs.uofs.edu (Bill Gunshannon)* Subject: Re: WASD Security Advisory Issued5 Message-ID: <ano1be$fhqe2$1@ID-135708.news.dfncis.de>o  ) In article <2zru26hpTRY4@elias.decus.ch>, , 	p_sture@elias.decus.ch (Paul Sture) writes: > ) > Attack reproduced, on my username file:1 >  > $ dir sysuaf/da/siz=all  >  > Directory SYS$COMMON:[SYSEXE]  > ? > SYSUAF.DAT;2               4/18        5-OCT-2002 10:51:13.20 ? > SYSUAF.DAT;1              54/54       27-OCT-2000 17:35:16.22  > ! > Total of 2 files, 58/72 blocks.0 > $ set host 0 > ? >  Welcome to OpenVMS (TM) Alpha Operating System, Version V7.3  >  > Username: test+ > Error accessing system authorization file  > Invalid record size 5 > %REM-S-END, control returned to node LOCAL:.MYBOX::  > $n > G > Yes, a denial of service, but easy to fix, as it hasn't destroyed the: > original version.i >    Question. (seriously)o  A UI do not know exactly what this exploit is all about as I don't)1 have a VMS machine available to play with but....   E Once the UAF has been overwritten can the exploit be repeated or does 8 it immediately prevent any further access to the system?H Assuming it can be repeated, could the attacker not just run the exploitE a few dozen times in rapid succession until the real UAF file (or anyeH other important system file) ran out of allowed versions and deleted the important file.f   bill   --  J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>   o   ------------------------------   Date: 6 Oct 2002 02:06:43 GMT<, From: bill@gw5.cs.uofs.edu (Bill Gunshannon)* Subject: Re: WASD Security Advisory Issued5 Message-ID: <ano5rj$g4abc$1@ID-135708.news.dfncis.de>r  8 In article <00A15022.2CF3BC0A@ssrl04.slac.stanford.edu>,' 	winston@SSRL.SLAC.STANFORD.EDU writes:l > P > That only works if you have version limits set on your important system files, > which you typically don't.   > M > If version limits aren't set, the oldest version doesn't go away by itself; O > RMS just declines to create version 32768.  (So you'd have to run the exploitC7 > more than a few dozen times to cause that to happen.)    Thank you for the explanation.   bill     --  J Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolvesD bill@cs.scranton.edu     |  and a sheep voting on what's for dinner. University of Scranton   |A Scranton, Pennsylvania   |         #include <std.disclaimer.h>   r   ------------------------------   End of INFO-VAX 2002.551 ************************