1 INFO-VAX	Fri, 17 Dec 2004	Volume 2004 : Issue 698       Contents:4 %BACKUP-I-BTCTIMESTAMP, interrupt 06:58, PC=000000008 Re: %BACKUP-I-BTCTIMESTAMP, interrupt 06:58, PC=000000008 Re: %BACKUP-I-BTCTIMESTAMP, interrupt 06:58, PC=00000000  Building OpenSSL 0.9.7e on a VAX$ Re: Building OpenSSL 0.9.7e on a VAX$ Re: Building OpenSSL 0.9.7e on a VAX Re: HP exodus to Intel Re: HP exodus to Intel Re: HP exodus to Intel Re: HP exodus to Intel Re: HP exodus to Intel Re: HP exodus to Intel) Re: HP pulls out of IA64 chip development ) Re: HP pulls out of IA64 chip development ) Re: HP pulls out of IA64 chip development  Re: More on Tru64   Re: OpenVMS V7.3-2 License issue Re: SIMH Questions Re: SIMH Questions Re: TCPIP Printer Library  Re: TCPIP Printer Library  Re: Time to revive Emerald?  Re: Time to revive Emerald?  Re: Time to revive Emerald?  Re: Time to revive Emerald?  Re: Time to revive Emerald?  Re: Time to revive Emerald?  Re: Time to revive Emerald?   F ----------------------------------------------------------------------   Date: 16 Dec 2004 22:34:15 GMT7 From: yehavi@vms.huji.ac.il (Yehavi Bourvine (58-4279)) = Subject: %BACKUP-I-BTCTIMESTAMP, interrupt 06:58, PC=00000000 % Message-ID: <2004Dec16.223415@hujicc>    Hello,  N  A week ago I've upgraded a system from VMS-7.3-1 to 7.3-2; I've noticed todayN in the weekly backup logs (done with /IMAGE on a live system) that I get a new message:  5 %BACKUP-I-BTCTIMESTAMP, interrupt 06:58, PC=00000000    E This message appears after the command (and before any other messages ) from Backup) and is repeated three times.   A Any idea what it might be? A search in Google revealed nothing...   F BTW, on other systems  I've done the upgrade I don't get this message.  5                                    Thanks!  __Yehavi:    ------------------------------    Date: 16 Dec 2004 12:56:49 -0800) From: "Ken Robinson" <kenrbnsn@rbnsn.com> A Subject: Re: %BACKUP-I-BTCTIMESTAMP, interrupt 06:58, PC=00000000 B Message-ID: <1103230609.738030.71660@f14g2000cwb.googlegroups.com>   Yehavi Bourvine 58-4279 wrote: > Hello, > B >  A week ago I've upgraded a system from VMS-7.3-1 to 7.3-2; I've
 noticed today F > in the weekly backup logs (done with /IMAGE on a live system) that I	 get a new 
 > message: > 6 > %BACKUP-I-BTCTIMESTAMP, interrupt 06:58, PC=00000000 > G > This message appears after the command (and before any other messages + > from Backup) and is repeated three times.  > C > Any idea what it might be? A search in Google revealed nothing...  > ? > BTW, on other systems  I've done the upgrade I don't get this  message.  D I guess you didn't see this post from Guy Pelig on Dec 13 to another% person asking about the same problem:   ( "James" <h...@shsu.edu> wrote in message< news:1102952797.685571.73190@z14g2000cwz.googlegroups.com...      B > After applying the update-v0300 patches, when I use BACKUP/IMAGE3 > command on the Operator account, I get a message:     D > $ BACKUP/IMAGE/label=002182 TAPEDRIVE:$5$DKC300WKLY.BCK $5$DKA300:* > %NONAME-W-NOMSG, Message number 00000000  F > and the backup does not work. When I run it under the system account8 > the same backup works fine. I am seeing some messages:      6 > %BACKUP-I-BTCTIMESTAMP, interrupt 05:57, PC=00000000= > If anyone can be of some assistance, I would appreciate it.     @ You are doing nothing wrong and there is nothing wrong with yourB system. The kit introduced a problem with the message file. PleaseB escalate to your local support center or wait for the next kit.... Guy      Ken Robinson   ------------------------------    Date: 16 Dec 2004 22:43:31 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen) A Subject: Re: %BACKUP-I-BTCTIMESTAMP, interrupt 06:58, PC=00000000 3 Message-ID: <Q60BEJuYCISF@eisner.encompasserve.org>   _ In article <2004Dec16.223415@hujicc>, yehavi@vms.huji.ac.il (Yehavi Bourvine (58-4279)) writes:  > Hello, > P >  A week ago I've upgraded a system from VMS-7.3-1 to 7.3-2; I've noticed todayP > in the weekly backup logs (done with /IMAGE on a live system) that I get a new
 > message: > 7 > %BACKUP-I-BTCTIMESTAMP, interrupt 06:58, PC=00000000   > G > This message appears after the command (and before any other messages + > from Backup) and is repeated three times.  > C > Any idea what it might be? A search in Google revealed nothing...   ( To me Googling for BTCTIMESTAMP yielded:  D http://groups-beta.google.com/group/comp.os.vms/msg/ef8d51ec1beaeebb   ------------------------------    Date: 16 Dec 2004 15:18:12 -06004 From: kuhrt@nospammy.encompasserve.org (Marty Kuhrt)) Subject: Building OpenSSL 0.9.7e on a VAX 3 Message-ID: <HYUYmJ5SncMF@eisner.encompasserve.org>   D Has anyone built OpenSSL 0.9.7e on a VAX successfully?  I downloadedD the latest from http://www.openssl.org/source/ and tried to compile @ it on a VAX running V7.2, and DECC 6.4, with the latest patches.   Using the...  / $ @MAKEVMS.COM all ignore nodebug decc multinet   C invocation, I received several of the following errors (reduced to   one instance for brevity)...  . Compiling The DES Library Files. (LIBRARY,LIB)         set_key.c O         OPENSSL_IMPLEMENT_GLOBAL(int,DES_check_key);    /* defaults to false */ 	         ^ M %CC-W-MIXLINKAGE, In this declaration, "_hide_DES_check_key" is declared with O  both internal and external linkage.  The previous declaration is at line 70 in 3  $44$DKA200:[OPENSSL-0_9_7E.CRYPTO.DES]SET_KEY.C;1. G  At line number 70 in$44$DKA200:[OPENSSL-0_9_7E.CRYPTO.DES]SET_KEY.C;1.   < %VCG-I-SUMMARY, Completed with 0 error(s), 1 warning(s), and  0 informational messages.I  At line number 411 in $44$DKA200:[OPENSSL-0_9_7E.CRYPTO.DES]SET_KEY.C;1.   = %LIBRAR-W-COMCOD, compilation warnings in module SET_KEY file 7 $44$DKA200:[OPENSSL-0_9_7E.VAX.OBJ.CRYPTO]SET_KEY.OBJ;1   H Before I start the forensic work necessary to figure this out, I thought9 I'd bounce a "did you get it work" message off the group.    ------------------------------  % Date: Thu, 16 Dec 2004 19:37:15 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> - Subject: Re: Building OpenSSL 0.9.7e on a VAX , Message-ID: <41C22A38.B56F25EA@teksavvy.com>   Marty Kuhrt wrote: > : > Has anyone built OpenSSL 0.9.7e on a VAX successfully?    I I did 0.97c  succesfully some time ago ( as a prelude to compiling mosaic M 3.8). Took about 24 hours to compile the whole kit. But it was clean compile. E Sorry, I don't remember when I got the kit. DEC-C 6.0 is my compiler.    ------------------------------   Date: 16 Dec 2004 19:35:06 EST) From: cook@wvnvms.wvnet.edu (George Cook) - Subject: Re: Building OpenSSL 0.9.7e on a VAX ! Message-ID: <zZWM2L1lDUbl@wvnvms>   j In article <HYUYmJ5SncMF@eisner.encompasserve.org>, kuhrt@nospammy.encompasserve.org (Marty Kuhrt) writes:F > Has anyone built OpenSSL 0.9.7e on a VAX successfully?  I downloadedF > the latest from http://www.openssl.org/source/ and tried to compile B > it on a VAX running V7.2, and DECC 6.4, with the latest patches. >  > Using the... > 1 > $ @MAKEVMS.COM all ignore nodebug decc multinet  > E > invocation, I received several of the following errors (reduced to   > one instance for brevity)... > 0 > Compiling The DES Library Files. (LIBRARY,LIB) >         set_key.c Q >         OPENSSL_IMPLEMENT_GLOBAL(int,DES_check_key);    /* defaults to false */  >         ^ O > %CC-W-MIXLINKAGE, In this declaration, "_hide_DES_check_key" is declared with Q >  both internal and external linkage.  The previous declaration is at line 70 in 5 >  $44$DKA200:[OPENSSL-0_9_7E.CRYPTO.DES]SET_KEY.C;1. I >  At line number 70 in$44$DKA200:[OPENSSL-0_9_7E.CRYPTO.DES]SET_KEY.C;1.  > > > %VCG-I-SUMMARY, Completed with 0 error(s), 1 warning(s), and >  0 informational messages.K >  At line number 411 in $44$DKA200:[OPENSSL-0_9_7E.CRYPTO.DES]SET_KEY.C;1.  > ? > %LIBRAR-W-COMCOD, compilation warnings in module SET_KEY file 9 > $44$DKA200:[OPENSSL-0_9_7E.VAX.OBJ.CRYPTO]SET_KEY.OBJ;1  > J > Before I start the forensic work necessary to figure this out, I thought; > I'd bounce a "did you get it work" message off the group.   @ I tried the following build of 0.9.7e on VAX V7.3 with DECC 6.4:  /         @MAKEVMS BUILDINF NORSAREF NODEBUG DECC 0         @MAKEVMS SOFTLINKS NORSAREF NODEBUG DECC-         @MAKEVMS CONFIG NORSAREF NODEBUG DECC -         @MAKEVMS CRYPTO NORSAREF NODEBUG DECC   ? and SET_KEY.C compiled fine.  I don't do a full build because I 5 only use it with VMS Mosaic.  Our TCP/IP is Multinet.      George Cook  WVNET    ------------------------------   Date: 17 Dec 2004 01:33:06 GMT! From: Lee Witten <lw99@yahoo.com>  Subject: Re: HP exodus to Intel / Message-ID: <Xns95C2D12DC59CCnn48@199.125.85.9>   ( "John Vottero" <John@mvpsi.com> wrote in3 news:v_jwd.907$1o1.791@newssvr19.news.prodigy.com:  1 > "Lee Witten" <lw99@yahoo.com> wrote in message  * > news:Xns95C280F78DE7nn48@199.125.85.9...F >> >http://www.theregister.co.uk/2004/12/15/hp_sends_itanium_to_intel/H >>>Intel's CEO-to-be Paul Otellini recently said Itanium has no place inD >>>workstations or low-end servers. This comment, according to an HP? >>>insider, came as quite the shock at HP where low-end Itanium  >>>shipments are key.  >>. >> There goes any chance at a VMS revival, no? >> >  > Why?  G Well, the theory in this news group was the move from Alpha to Itanium  @ would spark a revivial due to the move from 'niche' hardware to A 'mainstream' hardware, which would put the advanced features and  I unparalleled reliability of VMS into the hands of the masses.  Sorry for  J the exaggeration, and even more sorry it didn't happen.  It seems that if J Itanium is only for medium and large scale servers, then VMS will at best H retain its current installed base.  It's real hard to grow from the top  down, you know...    --lw--   ------------------------------  % Date: Thu, 16 Dec 2004 17:50:19 -0800 # From: "Tom Linden" <tom@kednos.com>  Subject: Re: HP exodus to Intel ( Message-ID: <opsi4p15xpzgicya@hyrrokkin>  ? On 17 Dec 2004 01:33:06 GMT, Lee Witten <lw99@yahoo.com> wrote:   H > Well, the theory in this news group was the move from Alpha to ItaniumA > would spark a revivial due to the move from 'niche' hardware to B > 'mainstream' hardware, which would put the advanced features andJ > unparalleled reliability of VMS into the hands of the masses.  Sorry forK > the exaggeration, and even more sorry it didn't happen.  It seems that if K > Itanium is only for medium and large scale servers, then VMS will at best I > retain its current installed base.  It's real hard to grow from the top  > down, you know...   J Introducing incompatible architecture when you have a large installed baseG is reckless at best, and is a good way to shed customers.  You make the I assumption that Alpha based customers will willy-nilly jump to Itanium. I G think that is an unproven assertion and is likely false considering the E lack of success (we may have different measures for this quantity) in G migrating from VAX to Alpha.  The IBM model for how this is done is the K only sound way to execute, z-series can execute code compiled 40 years ago!    --  C Using Opera's revolutionary e-mail client: http://www.opera.com/m2/    ------------------------------  % Date: Thu, 16 Dec 2004 19:13:31 -0800 # From: "Tom Linden" <tom@kednos.com>  Subject: Re: HP exodus to Intel ( Message-ID: <opsi4twtwuzgicya@hyrrokkin>  H On Thu, 16 Dec 2004 19:08:18 -0800, Jack Peacock <peacock@simconv.com>   wrote:  L > The Register makes a point that only 10% of Itaniums are sold without an   > OSC > (we'll assume all are VMS bound for argument's sake).  Article at @ > http://www.theregister.co.uk/2004/12/16/hp_intel_itanic_shift/  J I think that is a reasonable assumption.  I can't imagine why anybody elseD would want them.  I remember a few who bought the Intel 4/32.  	HUH!  J Actually, reconsidering the recent news I can't imagine why a VMS customer
 might buy it.    --  C Using Opera's revolutionary e-mail client: http://www.opera.com/m2/    ------------------------------  % Date: Thu, 16 Dec 2004 19:08:18 -0800 * From: "Jack Peacock" <peacock@simconv.com> Subject: Re: HP exodus to Intel 2 Message-ID: <1oWdneWVdJE-0F_cRVn-gA@mpowercom.net>  / "Tom Linden" <tom@kednos.com> wrote in message  " news:opsi4p15xpzgicya@hyrrokkin...L > Introducing incompatible architecture when you have a large installed baseI > is reckless at best, and is a good way to shed customers.  You make the K > assumption that Alpha based customers will willy-nilly jump to Itanium. I I > think that is an unproven assertion and is likely false considering the G > lack of success (we may have different measures for this quantity) in  > migrating from VAX to Alpha.L The Register makes a point that only 10% of Itaniums are sold without an OS B (we'll assume all are VMS bound for argument's sake).  Article at > http://www.theregister.co.uk/2004/12/16/hp_intel_itanic_shift/  L This would be the upper limit of early adopters.  Given the small number of J chips made HP may have a hard time keeping enough customer base to do any M more than life support past VMS 8.  I expect VMS to be sold or spun off, not  + right away, bad form, but in a year or two.   K And if HP thinks customers aren't paying attention, I just took their name  I off the prospective vendor list for a high reliability system at a major  K airport.  VMS would have been an excellent fit, and at one time would have  I been the only choice, but in good faith I can't recommend it anymore.  I  ; cited the activities of the last few days as justification.    Jack Peacock     ------------------------------  % Date: Thu, 16 Dec 2004 23:35:17 -0500 - From: JF Mezei <jfmezei.spamnot@teksavvy.com>  Subject: Re: HP exodus to Intel , Message-ID: <41C261FB.ECA78CA1@teksavvy.com>   Jack Peacock wrote: L > airport.  VMS would have been an excellent fit, and at one time would haveJ > been the only choice, but in good faith I can't recommend it anymore.  I= > cited the activities of the last few days as justification.   N Actually, the activities in the last few days are encouraging. The IA64 zit isN growing and is getting an infection. It will have to burst soon. The sooner it2 bursts, the sooner we'll know where VMS is going.   1 Uncertainty leads to speculation, leads to fear.    L If HP doesn't port VMS to a thriving platform, or get Intel to dump IA64 and. restart Alpha, then I hope HP sinks big time.   J Maybe after 3 companies have sunk due to mistreatment of VMS, history will+ recall how stupid management can really be.    ------------------------------    Date: 16 Dec 2004 23:33:35 -0600+ From: young_r@encompasserve.org (Rob Young)  Subject: Re: HP exodus to Intel 3 Message-ID: <cJ3TlpJupT04@eisner.encompasserve.org>   _ In article <1oWdneWVdJE-0F_cRVn-gA@mpowercom.net>, "Jack Peacock" <peacock@simconv.com> writes:   N > This would be the upper limit of early adopters.  Given the small number of L > chips made HP may have a hard time keeping enough customer base to do any O > more than life support past VMS 8.  I expect VMS to be sold or spun off, not  - > right away, bad form, but in a year or two.    	Ha...  ; 	How many years of "the future of VMS", "who will buy VMS", C 	blah blah blah pointless debates.  From a 1993 post in comp.os.vms   # > The future of VMS .. what future?   E You're opinion and you're entitled to it, just don't try to sell that C too hard to customers who bet their businesses on OpenVMS everyday, 3 you're likely to get into a religious arguement;-)     ---    	Or better yet...   Q http://groups-beta.google.com/group/comp.os.vms/msg/2581845e26d26b59?dmode=source   * From: "Jack Peacock" <peac...@simconv.com> Newsgroups: comp.os.vms % Date: Fri, 13 Apr 2001 12:19:50 -0700   K Market realities are that VMS has a precarious existence and a dim future.    Q http://groups-beta.google.com/group/comp.os.vms/msg/d954db3b3bd0b9a0?dmode=source   * From: "Jack Peacock" <peac...@simconv.com> Subject: Re: alpha longevity Date: 1999/11/02    J If MS gets a good version of NT out the door then Compaq will abandon VMS N because their customers will.  No one really knows what will happen, but basedO on past DEC history (i.e. DEC-10/20 and TOPS) the demise of VMS will be sudden,  without any real warning.   Q http://groups-beta.google.com/group/comp.os.vms/msg/960bdd83f123a046?dmode=source   * From: "Jack Peacock" <peac...@simconv.com>, Subject: Re: Another OpenVMS customer letter Date: 1999/08/07  B Zealous defense of VMS aside, how is it going to survive against a# stable and robust NT in the future?   F Fluff pieces from transient CEOs aside, where is Compaq explaining how6 they will be able to keep VMS afloat 5 years from now?   ---    	etc. etc. etc.  	 B 	So maybe in 5 more years you come back with a similar prediction?  M > And if HP thinks customers aren't paying attention, I just took their name  K > off the prospective vendor list for a high reliability system at a major  M > airport.  VMS would have been an excellent fit, and at one time would have  K > been the only choice, but in good faith I can't recommend it anymore.  I  = > cited the activities of the last few days as justification.     F 	Please spare us - Jack.  You've been trying to bury VMS for years andC 	you make it sound as if "recent events" made you decide something.  	 + 	Sorry Jack, but Google is not your friend!    				Rob    ------------------------------  % Date: Fri, 17 Dec 2004 04:47:15 +0800  From: prep@prep.synonet.com 2 Subject: Re: HP pulls out of IA64 chip development- Message-ID: <87zn0eq8bw.fsf@prep.synonet.com>   % "Tom Linden" <tom@kednos.com> writes:   E > On Thu, 16 Dec 2004 06:54:11 GMT, CJT <abujlehc@prodigy.net> wrote:   C >>   SO, why is HP giving Intel $3B?  I don't think they are.  As I F >> understand it, they're going to spend $3B on things like developing+ >> and marketing their own Itanium servers.   D > December 16, 2004. (FinancialWire) Intel Corp. (NASDAQ: INTC) willA > acquire Hewlett-Packard?s (NYSE: HPQ) titanium chip engineering  > team.   E > December 16, 2004.  (FinancialWire) Intel Corp. (NASDAQ: INTC) will A > acquire Hewlett-Packard?s (NYSE: HPQ) titanium chip engineering B > team.  The deal ends a decade-long partnership for the two.  TheD > titanium development group in Colorado will transfer to Intel, butD > Hewlett-Packard will continue to use the chips in its servers.  ItA > will also put about $3 billion into development of titanium for $ > high-end servers, according to HP.   > --- end story  ---  D > Aside from the foray into metallurgy, I read this as money from HPE > to Intel to keep the program alive.  It seems fairly obvious (to me E > anyway) that without such payment, Intel would drop the program, as # > financially inattractive for them   G untel is not getting $3B, the money is the dosh that has been there for E years for ISVs to port, etc. There is NO new money. Anf the engineers : may give intel the bird and walk to more plesent climes...      --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda. @                                              West Australia 6076* comp.os.vms,- The Older, Grumpier Slashdot. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------    Date: 16 Dec 2004 15:58:48 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen) 2 Subject: Re: HP pulls out of IA64 chip development3 Message-ID: <K2xMdYm74HWg@eisner.encompasserve.org>   ` In article <41C0E7CF.C7DF427A@comcast.net>, David J Dachtera <djesys.nospam@comcast.net> writes:  F > If the Alpha FABs have been dismantled, then RIP Alpha. Even if they5 > haven't, the ramp-back-up time will be significant.   F The Alpha FAB (Hudson) was for early Alphas.  Later Alphas were fabbedE by Intel (EV6 ?) and IBM (EV7 ?).  Neither of those companies devoted 7 an entire FAB to Alpha (nor had DEC done so in Hudson).    ------------------------------  % Date: Thu, 16 Dec 2004 21:07:55 -0500 ' From: Dave Froble <davef@tsoft-inc.com> 2 Subject: Re: HP pulls out of IA64 chip development, Message-ID: <41C23F7B.2060108@tsoft-inc.com>   Larry Kilgallen wrote:  b > In article <41C0E7CF.C7DF427A@comcast.net>, David J Dachtera <djesys.nospam@comcast.net> writes: >  > F >>If the Alpha FABs have been dismantled, then RIP Alpha. Even if they5 >>haven't, the ramp-back-up time will be significant.  >> > H > The Alpha FAB (Hudson) was for early Alphas.  Later Alphas were fabbedG > by Intel (EV6 ?) and IBM (EV7 ?).  Neither of those companies devoted 9 > an entire FAB to Alpha (nor had DEC done so in Hudson).  >   J Quite right!  And, if IBM is building EV7s, I'm sure that they are making M whatever profit they feel they need to do so.  As long as they're happy with  Q that profit, they'll be happy to make them as long as the orders continue.  When  O you have a cash cow, you milk it.  Changing to anything would cost them money,  N not make them money.  And it's not as if the EV7s were being build with a FAB ' process anywhere near state of the art.   F Wonder how easily they could build NVAX chips?  Cheaper than Pentiums?   ------------------------------  # Date: Fri, 17 Dec 2004 03:51:52 GMT 5 From: rdeininger@mindspringdot.com (Robert Deininger)  Subject: Re: More on Tru64L Message-ID: <rdeininger-1612042251500001@user-uinj0qe.dialup.mindspring.com>  H In article <ifjwd.24219$%p1.1513797@news20.bellglobal.com>, "Neil Rieck" <n.rieck@sympatico.ca> wrote:   M >HP said existing Tru64 customers should move over to HP-UX and just licence  B >third party software from Veritas to make up for the differences. > K >Well, it looks like Symatec just bought Veritas and you know what usually  H >happens during mergers. (hint: stuff that's not a real big money maker  >usually gets the chop)   I HP-UX has shipped with the Veritas file system for a number of years.  As H I understand it, the file system is well integrated with the rest of the OS.   & So I guess HP-UX is doomed too, right?   ------------------------------  # Date: Thu, 16 Dec 2004 18:50:36 GMT ( From: "John Hayes" <hayes1966@yahoo.com>) Subject: Re: OpenVMS V7.3-2 License issue > Message-ID: <0Okwd.47680$Qv5.42015@newssvr33.news.prodigy.com>   Mark,   C It is a license issue and we have bought some more paks to resolve.   J We run a two node Alpha DS20 cluster system. We have another DS20 that we I hope to get our web site up on but I am having some issues with Apache &  M Tomcat on that.  We currently use a Windows 2000 server for our web site and   it is nothing but trouble.   John  A "Mark Buda" <buda@SP_AMTripleBreakProducts.com> wrote in message  + news:muudnfLyTOkt_FzcRVn-uA@adelphia.com...  > I > For each user who logs in, it requires 100 units of OPENVMS-ALPHA-ADL.  F > Subprocesses are par of parent process and do not require any units. > H > If you wan to get more users on the system, you will have to buy more  > units. > % > What type of system is it?  Galaxy?  >  > mark >  > 6 > "John Hayes" <hayes1966@yahoo.com> wrote in message 9 > news:qP1td.29192$Rf1.5488@newssvr19.news.prodigy.com...  >> Hi Peter, >>= >> I hope that this sheds a little more light on the problem.  >> >> $ show us >>9 >>      OpenVMS User Processes at  6-DEC-2004 13:42:31.63 ; >>    Total number of users = 22,  number of processes = 67  >>7 >> Username    Node     Interactive  Subprocess   Batch + >> CATHY      ALPHA1            1         1 + >> CHERI      ALPHA2            2         2 + >> DAN        ALPHA1            2         2 + >> DYAN       ALPHA1            1         1 + >> ERIK       ALPHA1            1         1 + >> GARY       ALPHA2            1         1 + >> GEOFF      ALPHA2            1         1 + >> GRAZIA     ALPHA2            1         1 + >> JENNIFER   ALPHA2            2         2 ! >> JOHN       ALPHA1            2 + >> KAREN      ALPHA2            1         1 + >> KARYN      ALPHA2            1         1 + >> LORI       ALPHA1            3         3 + >> NAIOMI     ALPHA1            2         2 + >> PAULA      ALPHA1            2         2 + >> PHIL       ALPHA1            1         1 + >> PHIL       ALPHA2            1         1 + >> RICK       ALPHA2            2         2 + >> ROY        ALPHA2            2         2 5 >> SYSTEM     ALPHA1            1         -         1 ! >> SYSTEM     ALPHA2            1 + >> TARA       ALPHA1            1         1 + >> TARA       ALPHA2            1         1 + >> WAREHOUSE  ALPHA1            1         1 + >> WOODIE     ALPHA2            1         1  >> >>! >> $show license/usage/full *vms*  >>) >> [ALPHA1] show license/usage/full *vms*  >>G >> View of loaded licenses from node ALPHA1                 6-DEC-2004   >> 13:43:26.52 >>8 >> ACTIVITY license DEC OPENVMS-ALPHA usage information: >>        Availability: 0  >>        Activity: A  >>        Version:  0.0  >>        Release Date: (none)" >>        Termination Date: (none) >>        NO_SHARE@ >>    Pid        Process Name      Units   Username         NodeB >>    20202576   WAREHOUSE            75   WAREHOUSE        ALPHA1C >>    Units loaded: 75    Units allocated: 75    Units available: 0  >>< >> ACTIVITY license DEC OPENVMS-ALPHA-ADL usage information: >>        Availability: 0  >>        Activity: 100  >>        Version:  0.0  >>        Release Date: (none)" >>        Termination Date: (none)@ >>    Pid        Process Name      Units   Username         NodeB >>    2020095C   _OPA0:              100   SYSTEM           ALPHA1B >>    204002AD   _OPA0:              100   SYSTEM           ALPHA2B >>    2020256A   JOHN                100   JOHN             ALPHA1B >>    20400F63   KAREN               100   KAREN            ALPHA2B >>    20400F65   GRAZIA              100   GRAZIA           ALPHA2B >>    20202879   PAULA               100   PAULA            ALPHA1B >>    20202E7B   _TNA371:            100   PAULA            ALPHA1B >>    20400F67   RICK                100   RICK             ALPHA2B >>    20401069   _TNA455:            100   RICK             ALPHA2B >>    20400E6B   JENNIFER            100   JENNIFER         ALPHA2B >>    2040106C   _TNA457:            100   JENNIFER         ALPHA2B >>    2020267E   NAIOMI              100   NAIOMI           ALPHA1B >>    2040106F   ROY                 100   ROY              ALPHA2B >>    20401071   _TNA459:            100   ROY              ALPHA2B >>    20202A80   CATHY               100   CATHY            ALPHA1B >>    20202B81   DYAN                100   DYAN             ALPHA1B >>    20202603   LORI                100   LORI             ALPHA1B >>    20202805   _TNA376:            100   LORI             ALPHA1B >>    2020241D   _TNA377:            100   NAIOMI           ALPHA1B >>    20202426   _TNA378:            100   LORI             ALPHA1B >>    20400D73   CHERI               100   CHERI            ALPHA2B >>    20400E75   _TNA461:            100   CHERI            ALPHA2B >>    20202233   _TNA381:            100   JOHN             ALPHA1B >>    20400F7B   KARYN               100   KARYN            ALPHA2B >>    20401080   GEOFF               100   GEOFF            ALPHA2B >>    20401082   WOODIE              100   WOODIE           ALPHA2B >>    20202861   PHIL                100   PHIL             ALPHA1B >>    20401088   GARY                100   GARY             ALPHA2B >>    20400E8F   TARA                100   TARA             ALPHA2B >>    20202765   TARA                100   TARA             ALPHA1B >>    20202D84   DAN                 100   DAN              ALPHA1B >>    20202102   _LTA5059:           100   DAN              ALPHA1B >>    20202456   ERIK                100   ERIK             ALPHA1I >>    Units loaded: 4000    Units allocated: 3300    Units available: 700  >>9 >> AVAILABILITY license DEC VMSCLUSTER usage information:  >>        Availability: H  >>        Activity: 0  >>        Version:  0.0  >>        Release Date: (none)" >>        Termination Date: (none) >>    Units   Node >>     1050   ALPHA1 >>     1050   ALPHA2G >>    Units loaded: 2100    Units allocated: 2100    Units available: 0  >> >>5 >> [ALPHA1] show proces/rights/subprocess/id=20202585  >>I >> 6-DEC-2004 13:44:58.72   User: DAN              Process ID:   20202585 J >>                          Node: ALPHA1           Process name: "DAN_158" >> >> Process rights:- >> DAN                               resource  >> INTERACTIVE >> LOCAL >> >> System rights:  >> SYS$NODE_ALPHA1 >> >> Soft CPU Affinity: off  >>% >> There are 2 processes in this job:  >> >>  DAN  >>    DAN_158 (*)  >> >> >> My program does a" >> xcall lib$spawn("$RUN "+prgram) >> >> John  >>K >> "Peter Weaver" <WeaverConsultingServices@sympatico.ca> wrote in message  ) >> news:31jn8rF3abs0pU1@individual.net...  >>> John Hayes wrote:  >>>> Hi, >>>>F >>>> Recently (not sure when it started happening) our system has beenF >>>> grabbing an openvms license for each process the user creates. WeA >>>> have an application that spawns a new process as part of the I >>>> application and each of these seperate processes grab a license. Any  >>>>...  >>> I >>> Haven't seen it myself, I do not have a 7.3-2 system that I can reach D >>> right now to test, but I'm sure I would have noticed if this was >>> happening. >>> A >>> Just to be sure that these are subprocesses try doing a "show  >>> license/usage/full *vms*"  >>> 0 >>> Then for every process ID you see do a "show' >>> process/rights/subprocesses/id=pid"  >>> L >>> If you do have sub-processes requesting licenses then post an example ofK >>> how the spawn is happening, is it a DCL spawn or a system service call?  >>>  >>> --   >>> Peter Weaver# >>> Weaver Consulting Services Inc.  >>> Canadian VAR for CHARON-VAX  >>> www.weaverconsulting.ca  >>>  >>>  >> >> >  >    ------------------------------    Date: 16 Dec 2004 11:44:53 -0800) From: "Vladimir" <vershinin-vk@tochka.ru>  Subject: Re: SIMH Questions C Message-ID: <1103226293.086482.145380@z14g2000cwz.googlegroups.com>   # pa@it.singer-friedlander.com wrote:  > Hello, > C > Could someone tell me how I can switch the SIMH hardware settings  fromF > a VAXServer to a MicroVAX. I have tried the instructions in the FAQ,G > but I get a "non-existing device" error. I have checked show conf and  > PTR does not exist.  > D > Also, how do I enable extended addressing so that I can use larger > disks? > 	 > Thanks,  >  > Piyush   Hello!   Read 4.6 in simh_faq.txt   Vladimir   ------------------------------  # Date: Thu, 16 Dec 2004 23:02:54 GMT  From: <sethmuce@retronet.net>  Subject: Re: SIMH Questions 5 Message-ID: <yuowd.12575$_3.138675@typhoon.sonic.net>   ( Vladimir <vershinin-vk@tochka.ru> wrote: > % > pa@it.singer-friedlander.com wrote: 	 >> Hello,  >>D >> Could someone tell me how I can switch the SIMH hardware settings > fromG >> a VAXServer to a MicroVAX. I have tried the instructions in the FAQ, H >> but I get a "non-existing device" error. I have checked show conf and >> PTR does not exist. >>E >> Also, how do I enable extended addressing so that I can use larger 	 >> disks?  >>  
 >> Thanks, >>  	 >> Piyush  >  > Hello! >  > Read 4.6 in simh_faq.txt > 
 > Vladimir  3 The PTR device seems to be missing from SIMH 3.3-0!   = Piyush, you should be able to build an older version of SIMH, > for example 3.2-3, and follow the instructions in simh_faq.txt? to patch the boot rom.  Make sure both ka655.bin and ka655x.bin = are in the same directory when you do this.  You only need to . do this once, then use the new boot ROM image.   -Seth    --  
 Seth Morabito E sethmuce at retronet.net - To reply: remove the 'uce' from my address    ------------------------------    Date: 16 Dec 2004 11:06:20 -0800 From: denny.rich@swagelok.com " Subject: Re: TCPIP Printer LibraryC Message-ID: <1103222699.115672.187580@f14g2000cwb.googlegroups.com>    $ init/que/start-  /processor=tcpip$tlenetsym-  /library=<your_devctl_lib> - <your_queue>  C If this doesn't do it, please describe the error you are receiving.    thanks   denny    Hal Kuff wrote: @ > I'm likely missing something... how does one add an HP Printer library specE > to an HP/TCPIP printer queue...? I'm used to the old way of putting  it on  > the init/start/queue line...   ------------------------------  # Date: Thu, 16 Dec 2004 19:15:04 GMT # From: hoff@hp.nospam (Hoff Hoffman) " Subject: Re: TCPIP Printer Library2 Message-ID: <Y8lwd.4649$fq4.2536@news.cpqcorp.net>  S In article <cpqhqj$t3c@library2.airnews.net>, "Hal Kuff" <kuff@comcast.net> writes:cM :I'm likely missing something... how does one add an HP Printer library spec pK :to an HP/TCPIP printer queue...? I'm used to the old way of putting it on 0 :the init/start/queue line...   =   Which OpenVMS version, TCP/IP Services version, HP Printer, ?   and printer access method are in use here?  These details cana@   help me understand your question, and tailor the answer to theA   question you had intended -- I am not entirely certain what youe7   are asking for here, and the following are guesses...   ?   DCPS is the usual approach for accessing Postscript printers.A  ?   For device control libraries, the usual approach involves thee>   /LIBRARY qualifier.  I'm not at all certain that is what you   mean here.  ?   For setting up DCPS options, the DCPS startups typically will >   provide the defaults, and sets up various logical names with?   the queue-specific settings -- once the queues are configurede   and started, of course.E  A   For more than you ever wanted to know about IP printing, please-B   see topic (1020) in the Ask The Wizard (ATW) area.  Topic (5104)@   has some details on adding information for DCPS printing, and >   for various of the so-called "unrecognized" printer logical B   names that can be configured; the DCPS documentation has details   on this topic.     The ATW area:n  (     http://www.hp.com/go/openvms/wizard/  C   Again, I am guessing at the intended question here, and providingn7   a variety of related or potentially-related pointers.r  N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq N  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.com-   ------------------------------    Date: 16 Dec 2004 15:55:01 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen)B$ Subject: Re: Time to revive Emerald?3 Message-ID: <3Mic9gumjZJ+@eisner.encompasserve.org>b  g In article <XG7wd.18737$%p1.1380898@news20.bellglobal.com>, "Neil Rieck" <n.rieck@sympatico.ca> writes:o  L > I'm aware of these VAX emulators but that's not what I had in mind. I wantK > to see OpenVMS run in native mode on other hardware platforms. Whether weTM > like it or not, the computer industry appears to have produced some defactocK > hardware standard platforms and son-of-PC is one of them. I would like totG > see HP direct their OpenVMS engineering team to port OpenVMS to otheriJ > AMD/Intel chips (while there is still a team available to do so). UnlikeG > LINUX, I don't think HP should ever give OpenVMS (for IA32) away, butoK > charging something like $100 (to $500) per site license and an additionalrM > $20 for every subsequent user license would allow this wonderful OS to fend  > for itself in the real world.0  A I don't think those are the pricing levels at which VMS is aimed.n> The level of reliability that goes into VMS is really aimed at< those for whom the price of buying the box is not paramount.   ------------------------------  % Date: Thu, 16 Dec 2004 19:47:37 -0500t) From: "Neil Rieck" <n.rieck@sympatico.ca> $ Subject: Re: Time to revive Emerald?; Message-ID: <E0qwd.26586$%p1.1623864@news20.bellglobal.com>   ; "Larry Kilgallen" <Kilgallen@SpamCop.net> wrote in message  - news:3Mic9gumjZJ+@eisner.encompasserve.org...wK > In article <XG7wd.18737$%p1.1380898@news20.bellglobal.com>, "Neil Rieck"    > <n.rieck@sympatico.ca> writes: >  [...snip...]H >> LINUX, I don't think HP should ever give OpenVMS (for IA32) away, butL >> charging something like $100 (to $500) per site license and an additionalJ >> $20 for every subsequent user license would allow this wonderful OS to  >> fend   >> for itself in the real world. >gC > I don't think those are the pricing levels at which VMS is aimed.h@ > The level of reliability that goes into VMS is really aimed at> > those for whom the price of buying the box is not paramount.  K I couldn't agree more. However, we're talking about OpenVMS (an ultra-high wL quality OS) on non-Itanium Intel platforms competing with some high quality I operating systems (LINUX and Solaris spring to mind) which are currently  M available for free. Compaq used to sell a Tru64 hobbyist kit for $100.00 and AL that was in my mind when I threw out the previous numbers. (BTW, I was in a L system attendant role for a 5-node Tru64-based Alpha cluster and this, too,  was a very high quality OS).  L On the flip side, if HP got more people using OpenVMS, they would make much H more money licensing the development tools. I think this is Microsoft's H model an it's something that HP should understand since they seem to be 5 morphing from an engineering company to a PC company.p  
 Neil Rieck Kitchener/Waterloo/Cambridge,l Ontario, Canada.! http://www3.sympatico.ca/n.rieck/l   ------------------------------  % Date: Thu, 16 Dec 2004 19:31:54 -0600l2 From: David J Dachtera <djesys.nospam@comcast.net>$ Subject: Re: Time to revive Emerald?+ Message-ID: <41C2370A.6FD67628@comcast.net>r   DAVID TURNER wrote:  >  > Hang on a minute...  >  > www.softresint.com > , > I wonder if they are on any stock exchange( > My bet would be to buy a load of that. > Openvms DOES run on PC's4 > (as long as you give billy your $100.00 as well !)  H ...and therein lies the rub. So long as the x86-based systems need a VAXC emulation layer, they will remain limited as VAX replacements. When9G OpenVMS-IA32 runs natively on IA32, and OpenVMS-x86/64 runs natively on,B x86/64, *THEN* we'll see an opportunity for the market to take off again.   -- O David J Dachtera dba DJE Systems1 http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/t  " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/g   ------------------------------  % Date: Thu, 16 Dec 2004 17:52:31 -0800 # From: "Tom Linden" <tom@kednos.com>o$ Subject: Re: Time to revive Emerald?( Message-ID: <opsi4p5te1zgicya@hyrrokkin>  6 On Thu, 16 Dec 2004 19:31:54 -0600, David J Dachtera  " <djesys.nospam@comcast.net> wrote:   > DAVID TURNER wrote:  >> >> Hang on a minute... >> >> www.softresint.como >>- >> I wonder if they are on any stock exchangem) >> My bet would be to buy a load of that.e >> Openvms DOES run on PC'sh5 >> (as long as you give billy your $100.00 as well !)- >-J > ...and therein lies the rub. So long as the x86-based systems need a VAXE > emulation layer, they will remain limited as VAX replacements. WheneI > OpenVMS-IA32 runs natively on IA32, and OpenVMS-x86/64 runs natively onsD > x86/64, *THEN* we'll see an opportunity for the market to take off > again. >iK Of course, all modern processors emulate some prior design on an underlyingp; core, the difference is how the emulation code is executed.A       -- 7C Using Opera's revolutionary e-mail client: http://www.opera.com/m2/    ------------------------------  % Date: Thu, 16 Dec 2004 21:18:17 -0500v' From: Dave Froble <davef@tsoft-inc.com>e$ Subject: Re: Time to revive Emerald?* Message-ID: <41C241E9.70406@tsoft-inc.com>   Larry Kilgallen wrote:  i > In article <XG7wd.18737$%p1.1380898@news20.bellglobal.com>, "Neil Rieck" <n.rieck@sympatico.ca> writes:C >  > L >>I'm aware of these VAX emulators but that's not what I had in mind. I wantK >>to see OpenVMS run in native mode on other hardware platforms. Whether we M >>like it or not, the computer industry appears to have produced some defacto4K >>hardware standard platforms and son-of-PC is one of them. I would like toeG >>see HP direct their OpenVMS engineering team to port OpenVMS to otherAJ >>AMD/Intel chips (while there is still a team available to do so). UnlikeG >>LINUX, I don't think HP should ever give OpenVMS (for IA32) away, but$K >>charging something like $100 (to $500) per site license and an additionaleM >>$20 for every subsequent user license would allow this wonderful OS to fend  >>for itself in the real world.p >> > C > I don't think those are the pricing levels at which VMS is aimed. @ > The level of reliability that goes into VMS is really aimed at> > those for whom the price of buying the box is not paramount. >   9 That's a very valid perception.  Not a bad place for VMS.n  O But the robust environment VMS provides also makes it a good fit in many other S5 areas.  Is there any reason to avoid smaller markets?V   Dave   ------------------------------  % Date: Thu, 16 Dec 2004 21:27:05 -0500 ' From: Dave Froble <davef@tsoft-inc.com> $ Subject: Re: Time to revive Emerald?, Message-ID: <41C243F9.9010305@tsoft-inc.com>   David J Dachtera wrote:    > DAVID TURNER wrote:w >  >>Hang on a minute...  >> >>www.softresint.com >>, >>I wonder if they are on any stock exchange( >>My bet would be to buy a load of that. >>Openvms DOES run on PC's4 >>(as long as you give billy your $100.00 as well !) >> > J > ...and therein lies the rub. So long as the x86-based systems need a VAX@ > emulation layer, they will remain limited as VAX replacements.    O Why?  What rule makes this so?  What do you care how you get to an environment  Q that will run VMS?  For that matter, VMS doesn't run on Alpha, or NVAX.  It runs eP on the environment made up of those products plus firmware, microcode, PALcode, I whatever.  VAX emulation code is just another example of what I've named.    > WhenI > OpenVMS-IA32 runs natively on IA32, and OpenVMS-x86/64 runs natively ongD > x86/64, *THEN* we'll see an opportunity for the market to take off > again.    O Well, there is no more IA32 hardware available.  Intel and AMD have gotten the sL speed from hardware that is no longer x86, and provided an x86 environment, 1 again, using firmware/microcode/PALcode/whatever.1  N To the people building CPUs today, 'NATIVE' no longer has the same meaning as Q when CPUS were a collection of boards, and a MOVL truly was a hardware operation.0   ------------------------------  % Date: Thu, 16 Dec 2004 23:23:54 -0500w- From: JF Mezei <jfmezei.spamnot@teksavvy.com>o$ Subject: Re: Time to revive Emerald?, Message-ID: <41C25F50.828C09CA@teksavvy.com>   David J Dachtera wrote:vJ > ...and therein lies the rub. So long as the x86-based systems need a VAX@ > emulation layer, they will remain limited as VAX replacements.  L Lets not forget that there is really no roadmap for VAX-VMS, so with VAX-VMSL all but declared mature, nobody would really want to jump into VMS. Only old exsiting customers would.   M In terms of the comments made about price not being important for the type ofgM VMS customer still on VMS, this is the very attitude that had killed Digital,u Compaq and will kill HP.  M When you have competition from other vendors, and when the competition offerspF similar products with a feature set, which wile a subset of VMS, stillI fulfills the needs of the vast majority, then you either get a very small D narrow custoemr base with a high price, or you compete head to head.  L The problem with just expecting rich customer for whom price isn't importantI is that the second your competitors get the one feature VMS had that they-U didn't, you're toast because customers will migrate to the competition to save money.s  J Meanwhile, when you let the message out that you will price VMS out of theL market and allow only a small number of customers for whom budgets aren't soK important, developpers and software vendors will read this as: a market not L worth pursuing because it won't grow. So you get less and less software. AndI when you don't even market the thing, people get the message even faster./  L For christ's sake, two companies failed because of the thinking that VMS canN command a huge premium.  I can't understand how anyone still involved with VMS" would still hold such convictions.   ------------------------------   End of INFO-VAX 2004.698 ************************