1 INFO-VAX	Tue, 10 Dec 2002	Volume 2002 : Issue 682       Contents:1 Re: "VMS will be around long after we retire" ... 1 Re: "VMS will be around long after we retire" ... 1 RE: "VMS will be around long after we retire" ... 1 Re: "VMS will be around long after we retire" ... 1 RE: "VMS will be around long after we retire" ... 1 Re: "VMS will be around long after we retire" ... 1 Re: "VMS will be around long after we retire" ... C (Very) Affordable VMS on older gear (was: "VMS will be around ...") G Re: (Very) Affordable VMS on older gear (was: "VMS will be around ...") , Re: Alternatives to "DEC LMF PAK GEN V1.3" ? Re: Another Porting Problem  Re: Another Porting Problem  Re: Another Porting Problem  File update notification* How many messages/second can a CI rail do?M Re: Info-VAX only access (was: "VMS will be around long after we retire" ...) M Re: Info-VAX only access (was: "VMS will be around long after we retire" ...)  my recent posts...P Re: number of fiber connections from alpha to switch and from switch to symmetri- Re: OT: Whoa! Is Sun aiming at VMS's jugular? - Re: OT: Whoa! Is Sun aiming at VMS's jugular? - Re: OT: Whoa! Is Sun aiming at VMS's jugular? - Re: OT: Whoa! Is Sun aiming at VMS's jugular? 2 Re: Performance of atomic instructions and locking2 Re: Performance of atomic instructions and locking2 Re: Performance of atomic instructions and locking Porting from Sun to OpenVMS  RE: Porting from Sun to OpenVMS  Re: Porting from Sun to OpenVMS  RE: Porting from Sun to OpenVMS B Re: Request for Discussion, make comp.os.vms a moderated newsgroup RE: UPS maxicode and OpenVMS...  RE: UPS maxicode and OpenVMS...  Re: UPS maxicode and OpenVMS...  Re: Using old VRT19-HA Monitor Re: Vest Re: Vest Vest+ [search] looking for 1986 DECcies in France   F ----------------------------------------------------------------------  $ Date: Mon, 9 Dec 2002 21:22:31 +01005 From: "Chris Clifford" <chris.clifford@openvms.co.uk> : Subject: Re: "VMS will be around long after we retire" ...* Message-ID: <3df4fb8a@news.swissonline.ch>  . "Roy Omond" <Roy@Omond.net> wrote in message >< > Hmmm... interesting e-mail address Chris (@openvms.co.uk). > > > http://www.openvms.co.uk lands you in www.openvms.compaq.com > F > Does that mean you work for HP/Compaq/DEC ?  And you still can't get > good VMS people ?  >   K No I've worked for any of them. I have intended for some time to start up a J VMS related website but with 9-month old twins it's proving impossible :-)B So I'm doing my bit by redirecting the domain to HP's VMS website.  K If someone wants to give it a go then please contact me and you can happily 2 have some webspace and the loan of the domain....!   - Chris.   ------------------------------  % Date: Tue, 10 Dec 2002 02:32:06 -0500 0 From: JF Mezei <jfmezei.spamnot@vl.videotron.ca>: Subject: Re: "VMS will be around long after we retire" .../ Message-ID: <3DF59871.93F28481@vl.videotron.ca>    Robert Deininger wrote: I > What if VMS licensing was made FREE on older, less capable systems, VAX J > and/or Alpha?  No hobbyist restrictions.  Regular production quality VMSL > licenses for free, but only on old hardware.  Would this be worthwhile for	 > anyone?   ' YES YES YES , at least at first glance.   I Allowing VMS to be used at very low cost on second hand hardware would be F great as a way to get VMS into the door. And once there, it MAY grow.   L The problem I see however is that if a potential customer takes advantage ofN this, gets VMS inside the shop, and wants to grow it because it works so well,L he shouldn't be given a heart attack when he decides to upgrade and then pay the full amount.  N But having essentially free VMS and layered producs on old machines would be a> great way to push VMS inside some shops for demos, pilots etc.   ------------------------------    Date: 10 Dec 2002 03:51:28 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen) : Subject: RE: "VMS will be around long after we retire" ...3 Message-ID: <ST5m$aMmtDVE@eisner.encompasserve.org>   ~ In article <BE56C50EA024184DAF48F0B9A47F5CF402660BEE@kaoexc01.americas.cpqcorp.net>, "Main, Kerry" <Kerry.Main@hp.com> writes: >  > H >>>> Yes, yes. Important, and VMS is generally ignored by the developersA > of virii and exploits due to them being interested in as wide a  > distribution as possible.<<  > J > Course, the fact that there are no known OpenVMS virus's in the wild (toI > my knowledge anyway) may also have something to do with it as well. For J > anti-virus makers, how can you sell a solution when there is no problem? >  > I > Perhaps we should introduce some weakness's into the OS architecture to D > make it easier to introduce Virus's to keep the masses busy and so) > anti-virus companies can make a living?   G I do resent the notion that Microsoft provides nourishment to all those  anti-virus companies.    ------------------------------  % Date: Tue, 10 Dec 2002 12:30:30 +0100 5 From: "Chris Clifford" <chris.clifford@openvms.co.uk> : Subject: Re: "VMS will be around long after we retire" ..., Message-ID: <3df5d059$1@news.swissonline.ch>  4 "Howard S Shubs" <howard@shubs.net> wrote in message6 news:howard-E92A5C.21291409122002@enews.newsguy.com...  H > I believe that you believe that.  I believe that HP -might- want us toI > believe that.  I, however, don't believe that.  VMS is dead.  Tru64 was C > murdered.  DEC is completely gone, and I'm moving on in my career " > because I have to pay the bills.  J Well, not strictly true. There's a lot less VMS around nowadays but in theK environment I work in, there's three mission-critical VMS clusters although B admittedly one will disappear during 2003. At another location, myH employer's actually expanding the VMS environment. So "VMS is dead" is a little extreme.   L I hope you're happy moving on in your career. I'm doing the same and will doK my Solaris Certification in early 2003. To me, achieving this will be a bit L like getting a gold starred badge for 2 years' service in MacDonalds... i.e.& not exactly the high point of my life.   > H > Once a thing gets beyond a certain point, there's no reviving it.  VMSH > is and was a very good OS.  Doesn't matter.  Quality is of limited useD > if you can't market it.  Ask Xerox or Sony (Beta!) or many others. > I > The people working on VMS now, and those who try to push it, are one or H > more of very very cynical, doing it because it pays the bills, or live4 > in some world I've not yet found a way to achieve.  L Maybe true, but how many times has a similar thread popped up here in c.o.v.G and still VMS refuses to dip its head below the surface and stay under.    ------------------------------  % Date: Tue, 10 Dec 2002 07:04:27 -0500 ' From: "Main, Kerry" <Kerry.Main@hp.com> : Subject: RE: "VMS will be around long after we retire" ...T Message-ID: <BE56C50EA024184DAF48F0B9A47F5CF402660BF1@kaoexc01.americas.cpqcorp.net>   Doc -=20  % <<<This - at least with my newsreader H - results in your posts appearing at the bottom of the thread and out of context.<<<   D I did not realize that. Mmmm... My laptop browser is Opera (fast andF does not support Activex or Vbscript which the virus kiddies like) and? it also has a newsreader, so perhaps I will look into using its  newsreader as well.=20  ! Old habits are hard to change :-)    Thx for the feedback.    Regards   
 Kerry Main Senior Consultant  Hewlett-Packard (Canada) Co.! Consulting & Integration Services  Voice: 613-592-4660  Fax   : 613-591-4477 Email: kerryDOTmain@hpDOTcom-     (remove the DOT's and replace with "."'s)      -----Original Message-----> From: Doc.Cypher [mailto:Use-Author-Address-Header@[127.1]]=20 Sent: December 10, 2002 1:00 AM  To: Info-VAX@Mvb.Saic.Com # Cc: mail2news@freedom.gmsociety.org : Subject: RE: "VMS will be around long after we retire" ...    < On Mon, 9 Dec 2002, "Main, Kerry" <Kerry.Main@hp.com> wrote:  H >Perhaps we should introduce some weakness's into the OS architecture to  F >make it easier to introduce Virus's to keep the masses busy and so=20( >anti-virus companies can make a living?   I don't think so.   C >>>>I think you (deliberately?) ignore the point David is trying to 	 >make.<<<  > H >Nope. I already stated I thought OpenVMS marketing could be better. You  H >won't find many knowledgeable people internal or external to HP that=20 >will argue that point.   G I didn't think you were against wider - or as I and others would prefer D - unrestricted marketing of VMS. The conclusion drawn by many in theH newsgroup is that the fault lies with those above you (how high above, I don't know).  J >And the merits of back-porting a full 64bit OS like OpenVMS to a 32bit=20H >HW architecture on cheap hardware in the hope that this will somehow=20G >automatically attract a huge number of new ISV's has been debated a=20 " >thousand times before in this NG.  G As far as I am concerned, it's about 10 years too late to try something B like that. My suspicion is the Hammer will gradually take over theD market currently served by smaller x86 systems. Consequently I wouldG like to see HP hedging their bets rather than putting all their eggs in  one basket.   H >Granted, I have access to information like OpenVMS Customer win reports  I >that most readers here do not have, so when some readers (albeit long=20 E >time OpenVMS promoters) start to get discouraged, I simply try to=20 B >remind them that OpenVMS is getting new Customers and existing=20F >Customers and ISV's are doing interesting stuff with OpenVMS these=20 >days.  E I know, I think we touched on this in the past. Many customers aren't E willing to have you publically announce large sales. I can appreciate , you probably find that frustrating at times.  I >The OpenVMS market is not as good as it could be, but it is certainly=20 ; >not as bad as some participants on this NG believe either.  > I >In addition to the previous pointers, check out Mike's previous reply=20 1 >on the big OpenVMS SAN stuff as another example.   & Yes, nice stuff. Can I borrow some? :)  G >>>> [On a completely unrelated point... Won't Hoff and the rest of the C >engineering folks share their newsfeed with you? Trust me, it is a + >*much* better way to access the group.]<<<  > C >I have a large number of different information sources and this=20 H >newsgroup is only one, but perhaps you can expand on what it is that=20" >bothers you in an offline email ?  G You're a fairly frequent contributor, but because you post via Info-VAX D the References header is lost on your posts. This - at least with my
 newsreaderH - results in your posts appearing at the bottom of the thread and out of context.  E I know there are some contributors who can only access c.o.v. via the H list, whereas there are news servers available within HP. I also believeD you would find it takes less time to go through all the posts in theD group via a newsreader. It certainly wasn't intended as a criticism.     Doc. --=20 6 The bigger the humbug, the better people will like it. ~ Phineas Taylor Barnum. https://vmsbox.cjb.net   ------------------------------  % Date: Tue, 10 Dec 2002 08:24:10 -0800 ' From: David Mathog <mathog@caltech.edu> : Subject: Re: "VMS will be around long after we retire" ...8 Message-ID: <20021210082410.3b36b78a.mathog@caltech.edu>  ! On Mon, 9 Dec 2002 11:03:11 -0600 - "Tony Scandora" <Scandora@cmt.anl.gov> wrote:     F > Itanium is espensive today.  So was Pentium when 486 was king.  Like2 > everything else, Itanium's price will come down,  D Your argument is flawed - the x86 processors have a mass market, butI the Itanium will not.  The classic example is the Alpha, which was always H very expensive when the equipment was new.  I suspect a huge fraction ofC new Alphas were actually only sold when Digital/Compaq dropped them I to close out prices.  That is, closer to what real end users were willing  to pay.      > and Opteron might make it ' > happen sooner than Intel would like.    @ Probably not even then.  What that might do is to force Intel toA produce its own x86-64 variant.  Which wouldn't be Itanium.  Such < a result would drive the cost of Itanium up, not down, since1 it would further restrict Itanium's market niche.    Regards,   David Mathog mathog@caltech.edu> Manager, Sequence Analysis Facility, Biology Division, Caltech   ------------------------------  % Date: Tue, 10 Dec 2002 08:42:03 -0800 ' From: David Mathog <mathog@caltech.edu> : Subject: Re: "VMS will be around long after we retire" ...8 Message-ID: <20021210084203.3d874b70.mathog@caltech.edu>  " On Tue, 10 Dec 2002 12:30:30 +01006 "Chris Clifford" <chris.clifford@openvms.co.uk> wrote:  N > Maybe true, but how many times has a similar thread popped up here in c.o.v.I > and still VMS refuses to dip its head below the surface and stay under.   A Carly and Winkler are standing on its head - VMS will stay under.   K HP's enterprise strategy is beyond mortal comprehension.  With VMS drowned, K Tru64 murdered, and HPUX forced to undergo both a heart xenotransplant (the F donor apparently being a cross between a  pig and a sloth) and massiveG grafts from Tru64, the only thing that should be on the mind of most HP D enterprise customers is "Who's our IBM sales rep?"  The Tandem folksF must be praying that Carly will remain too busy preening for the media/ to notice, and destroy, their platform as well.      Regards,   David Mathog mathog@caltech.edu> Manager, Sequence Analysis Facility, Biology Division, Caltech   ------------------------------    Date: 10 Dec 2002 04:05:08 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen) L Subject: (Very) Affordable VMS on older gear (was: "VMS will be around ...")3 Message-ID: <$tym8Z5sl3b$@eisner.encompasserve.org>    In article <rdeininger-1012020043110001@user-2ive3t1.dialup.mindspring.com>, rdeininger@mindspring.com (Robert Deininger) writes:   I > What if VMS licensing was made FREE on older, less capable systems, VAX J > and/or Alpha?  No hobbyist restrictions.  Regular production quality VMSL > licenses for free, but only on old hardware.  Would this be worthwhile for	 > anyone?   C It would certainly fill the gap caused by the unwillingness of eBay E vendors to sell machines with a license transfer.  That would benefit  the eBay sellers and buyers.  D It would not harm HP revenues, since their income from people buyingB fresh licenses for older gear is minimal.  They do make a good bitF of income from selling hardware and software _support_ for older gear,B but the appetite of customers for _support_ on older gear would inA no way be affected by the (non-)cost of _licenses_ for that gear.   F But the people not currently covered by the hobbyist program are thoseG who would use the machine for business.  The one aspect of the hobbyist D program (aside from eligibility) that is unacceptable for even smallE businesses is the yearly renewal.  One cannot base a business on some - permission that might be withdrawn in a year.   D If HP were intent on getting a yearly "survey of interest" (which isG the benefit they get from the Hobbyist renewals), conceivably VMS could H be doctored to run only on older gear under a new kind of PAK.  That PAKD could be issued without a termination date but version-limited. SomeD small businesses would be willing to accept the need to get new PAKsG for new versions of VMS (always with the possibility, like the hobbyist A program, that HP could stop giving away such PAKs in the future).   G On the other hand, HP could save a lot of overhead by just skipping the I survey capability and trading lack of information for increased adoption.   G The customers for used DEC 3000 machines on eBay are really a different 4 population than the customers for new ES45 machines.   ------------------------------  % Date: Tue, 10 Dec 2002 08:12:25 -0500 ( From: David Froble <davef@tsoft-inc.com>P Subject: Re: (Very) Affordable VMS on older gear (was: "VMS will be around ..."), Message-ID: <3DF5E839.9080607@tsoft-inc.com>   Larry Kilgallen wrote:   > In article <rdeininger-1012020043110001@user-2ive3t1.dialup.mindspring.com>, rdeininger@mindspring.com (Robert Deininger) writes:  >  > I >>What if VMS licensing was made FREE on older, less capable systems, VAX J >>and/or Alpha?  No hobbyist restrictions.  Regular production quality VMSL >>licenses for free, but only on old hardware.  Would this be worthwhile for	 >>anyone?  >> > E > It would certainly fill the gap caused by the unwillingness of eBay G > vendors to sell machines with a license transfer.  That would benefit  > the eBay sellers and buyers. > F > It would not harm HP revenues, since their income from people buyingD > fresh licenses for older gear is minimal.  They do make a good bitH > of income from selling hardware and software _support_ for older gear,D > but the appetite of customers for _support_ on older gear would inC > no way be affected by the (non-)cost of _licenses_ for that gear.  > H > But the people not currently covered by the hobbyist program are thoseI > who would use the machine for business.  The one aspect of the hobbyist F > program (aside from eligibility) that is unacceptable for even smallG > businesses is the yearly renewal.  One cannot base a business on some / > permission that might be withdrawn in a year.  > F > If HP were intent on getting a yearly "survey of interest" (which isI > the benefit they get from the Hobbyist renewals), conceivably VMS could J > be doctored to run only on older gear under a new kind of PAK.  That PAKF > could be issued without a termination date but version-limited. SomeF > small businesses would be willing to accept the need to get new PAKsI > for new versions of VMS (always with the possibility, like the hobbyist C > program, that HP could stop giving away such PAKs in the future).  > I > On the other hand, HP could save a lot of overhead by just skipping the K > survey capability and trading lack of information for increased adoption.  > I > The customers for used DEC 3000 machines on eBay are really a different 6 > population than the customers for new ES45 machines. >     P The question is valid, and Larry has presented some good arguments.  However, I Q wonder where this is coming from.  Several years ago a proposal was submitted to  J VMS management that suggested that license costs for older be modified to P reflect the capabilities of the systems.  Continuing to charge enterprise class M license fees for an old VAX 6000 system just isn't reasonable.  The argument  Q that DEC/Compaq would rather 'push' such people into a new system is just poorly  Q masqueraded greed.  The license fees had been received on such systems when they  K were sold.  As Larry has indicated, these are different types of customers.   F The proposal mentioned disappeared into the bottomless pit called VMS P management, never to be seen again, not even a rejection.  Is the appearance of M this question an indicator that VMS management might be looking at proposals  C from customers a bit differently these days?  More than a bit late.    Dave   ------------------------------  $ Date: Mon, 9 Dec 2002 19:26:50 -05004 From: "Mark Buda" <buda@tabasco.zko.dec.no.spam.com>5 Subject: Re: Alternatives to "DEC LMF PAK GEN V1.3" ? 3 Message-ID: <RyaJ9.52$%_1.2935875@news.cpqcorp.net>   2 Here is an ASCII copy of the PAKGEN documentation.     --  
 Sincerely,	 Mark Buda  Hewlett-Packard Company  VMS Engineering  110 Spitbrook Road
 MS: ZK3-4/X57  Nashua, NH 03062 Voice: (603) 884-1969  FAX: (603) 884-3451   + VMS Home Page http://www.openvms.compaq.com > OpenVMS Portal http://www.openvms.compaq.com/portal/index.html      H ------------------------------------------------------------------------
 ----------   Mark Schafer+ January 18, 2002, updated November 9, 2002.   F DSPP program. If you meet a partner, please ask them to contact the hp% developer & solution partner program.  800 249 3294 www.hp.com/dspp      Introduction  E PAKGEN produces LMF PAKs for software.  Digital Equipment Corporation G developed LMF licensing technology for its OpenVMS operating system and G layered products in the late 1980s.  Later, LMF was extended to Digital E UNIX (now Tru64 UNIX).  A central tenet of LMF is the security of the D generator, PAKGEN.  PAKGEN was offered as a product, but Digital wasE restrictive and not many companies purchased the software.  Some ISVs C asked for it, but it never was the mainstream.  Still, it's used to E license the OpenVMS operating system and planned to be in the Itanium H port of OpenVMS.  For this reason, I proposed to offer PAKGEN to ISVs as a service of the CSA program. " Responsible Organizations & People  # Leo Demers, OpenVMS product manager 7 Responsible for the PAKGEN technology and documentation    Mark Buda, OpenVMS engineer A Maintains LMF and PAKGEN software in the OpenVMS operating system    Mark Schafer, CSA TechSupport ; Provides technical support to ISVs through the CSA program.   E Susan Mill, License Key manager High Performance Server business unit 4 Issues and tracks LMF keys, including the PAKGEN key$ CSA Service Offering PAKGEN for ISVs  D Members of Compaq's CSA program may request PAKGEN.  They make theirH request by logging into the Members Only website and filling out a form,H "Request for Technical Support" by following the links, "Request PortingF or Technical Support" for AlphaServer systems, "Development or PortingB Question."  In their request, the partner should put PAKGEN in theF Subject field and the requested TOKEN string in the textbox area "YourF request or concern."  CSA TechSupport will open a case for the requestG and forward it to the License Key manager.  The manager issues a PAKGEN H key with the requested TOKEN string, and emails the key file to the ISV. Scope   C Worldwide.  CSA members must use the Members Only website to make a H request and to download documentation.  The PAKGEN key file will be sent to them by email.  Cost   There is no cost to the member.  Prerequisite Software   H Support for PAKGEN is integrated into OpenVMS Version 7.2 and later.  No, additional product installation is required. Support   E PAKGEN software is not warranted.  CSA TechSupport will provide "best B effort" support for ISVs that requested and received a PAKGEN key.D Backup support will come from OpenVMS engineering for questions thatB cannot be answered or for bugs that are entered in the PTR system.
 Documentation   < General LMF documentation is provided in the OpenVMS product documentation. http://www.openvms.compaq.com/) OpenVMS License Management Utility Manual  Order Number: AA--PVXUF--TK   G An API for software programs that use LMF is documented in "DEC VMS/LMF E System Services Reference Manual", available as a PDF file on the CSA  Members Only website.   E PAKGEN user documentation is provided on the CSA Members Only website * for members to download and is here below: Generating License PAKs   B The License Management Facility (LMF) is an OpenVMS component thatF provides system managers and product developers with a means to manageH and track software PAKs that have been issued to customers. Users of LMFE use the LMF Product Authorization Keys (PAKs) and the LMF database to F register and manage license PAKs.  Product developers use LMF to checkH for valid product licenses.  Product developers and product vendors must use LMF to generate new keys.   F Each PAK includes a variety of fields that supply specific informationF about a product.  The most relevant fields for generating and trackingD license keys are the product name, product issuer, product producer,A product authorization, and product token. The product name is the H designation for the particular product; that is, the specific product orF product group that is authorized by the key.  The producer is the nameH of the organization that produced or created the product.  Together, theG producer and the product name uniquely identify a product license.  The C issuer identifies the organization that generated the license; this = organization may or may not be the same as the producer.  The G authorization field is an arbitrary alphanumeric string that the issuer C can use as a key serial number or a customer-order tracking number.   G The product token is an alphanumeric string.  It cannot be more than 31 E characters.  Don't associate the string with a specific product name. E The convention has historically been to refer to your Company name so H that the licenses are "identifiable" in an audit situation.  Please note that you cannot change it.  F Each product producer can have multiple product issuers; however, each@ issuer is individually authorized to generate license keys for aA particular producer.  The ability to generate keys is specific to G individual producer/issuer pairs; the producer/issuer pair can generate E keys for only that pair. An issuer who needs to generate licenses for F multiple producers requires individual and separate authorizations for each producer.  G The run-time product license check is based on the product name and the F product producer.  The ability to generate product licenses is enabledF by a license key -- the product authorization key generation key.  TheF key generator key name is PAKGEN, and the producer and issuer are both: DEC.  The PAKGEN key uses the product token to declare theE producer/issuer pair that is authorized by the particular PAKGEN key.   F Each PAKGEN PAK authorizes a code for a particular producer/issue pairF and for no others.  Although multiple PAKGEN PAKs can be registered inG parallel in the LMF database, a maximum of one PAKGEN PAK can be loaded  and active at a time.   G Support for PAKGEN is integrated into OpenVMS (VAX & Alpha) Version 7.2 ; and later.  No additional product installation is required.   C The following sections describe how to use PAKGEN. The descriptions E assume basic familiarity with PAKS and with the DCL commands commonly  used with LMF.# Step 1: Register the PAKGEN License   C The first step involved in the use of PAKGEN is registration of the @ PAKGEN key.  To enable the PAKGEN key, use either the VMSLICENSEE procedure or the DCL commands LICENSE REGISTER and LICENSE LOAD.  You F must fill in each field of the PAKGEN license exactly as listed on the product license document.   H The following example shows how to register and load the PAKGEN license:   $ LICENSE CREATE -- /DATABASE=device:[directory]localdatabase.ldb    $ LICENSE REGISTER PAKGEN - / /DATABASE=device:[directory]localdatabase.ldb - 
 /ISSUER=DEC -  /PRODUCER=DEC - % /AUTHORIZATION=authorization-string -  /UNITS=license-units - /RELEASE=release-date  - /ACTIVITY=activity-code - " /TOKEN=producer-name~issuer-name - /CHECKSUM=checksum $ LICENSE LOAD PAKGEN - - /DATABASE=device:[directory]localdatabase.ldb     E If licenses for multiple producer/issuer pairs are required, you must G first register the individual PAKGEN keys and then unload and load keys & for the specific producer/issuer pair.  D The following example shows how to display a currently loaded PAKGEN license:   $ SHOW LICENSE PAKGEN/FULL   Active licenses on node XDELTA:    PAKGEN         Producer: DEC          Units: 100         Version: 0.0!         Release Date: 21-JAN-2000           Termination Date: (none)         Availability: 100          Activity: 0          VAX_ALPHA          Product Token: FOO~BAR  C Only the PAKGEN key that is issued by Compaq is honored for license F generation.  The only producer string that is valid for PAKGEN is DEC.$ Step 2: Generate the Product License  E To generate a license PAK, you must first use the DCL command PRODUCT E REGISTER with the /GENERATE qualifier. Then, to generate the PAK, you F must input specific product information by using the REGISTER/GENERATE# command with additional qualifiers.   F It is strongly suggested that you register PAKGEN paks into a separateB database than the OpenVMS standard one.  This keeps the system LMFE database separate and untouched by anyone registering PAKGEN paks and @ creating PAK's. Use the /DATABASE=device:[directory]database.ldb qualifier to accomplish this.   F Once the particular license is registered in the LMF database, you useE the PRODUCT ISSUE command to produce the completed license key in the  desired format.   B The /GENERATE qualifier is valid only when the producer and issuerF specified on the license PAK match a valid, loaded PAKGEN key.  If youG need to issue licenses for another producer/issuer pair, you must first E unload the PAKGEN license and then reload the license associated with  that producer/issuer pair.  E The following example shows how to generate a license and to create a 8 DCL procedure that contains the newly generated license:  * $ LICENSE REGISTER/GENERATE product-name -/ /DATABASE=device:[directory]localdatabase.ldb -  /PRODUCER=producer - /ISSUER=issuer -% /AUTHORIZATION=authorization-string - 
 /UNITS=0 -% /TERMINATION_DATE=termination-date  -  /ACTIVITY=activity-code -  /TOKEN=product-token-code ( $ LICENSE ISSUE/PROCEDURE product-name -/ /DATABASE=device:[directory]localdatabase.ldb - ' /OUTPUT=SYS$SCRATCH:PAK_PROCEDURE.COM - # /AUTHORIZATION=authorization-string     A The following example shows the contents of the PAK_PROCEDURE.COM 4 procedure that was created by the preceding command:  - $! Software Product Authorization Key Replica  $! Issued by BUDA  $! Issued on  7-JAN-2002 06:49% $!----------------------------------- ! $ LICENSE REGISTER product-name -  /PRODUCER=producer - /ISSUER=issuer -% /AUTHORIZATION=authorization-string - 
 /UNITS=0 -% /TERMINATION_DATE=termination-date  -  /ACTIVITY=activity-code -  /TOKEN=product-token - /CHECKSUM=2-xxxx-xxxx-xxxx-xxxx & Using the Product Authorization String  ? You can use the product authorization string to track licenses, G customers, the person or system that generated the license, as a serial E number, and so on.  You should use a string format that allows all of E this information to be parsed easily; in particular, you should use a H format that permits you to identify the format used as changes are made.  B For example, you can include an application-specific authorization? format identifier, a customer code, a unique serial number, and @ information about when and where this particular license key was
 generated:   1-CUSTCODE-1234-2000021-SITE  B If the authorization format needs to be changed or enhanced in theE future, you can alter the value that you stored in the first field to B identify the particular format.  For example, in the authorizationF string of the preceding example, you could change the leading 1 to a 24 when the format of the authorization string changes.& Securing the Product Authorization Key  H Be careful to avoid both the release of the PAKGEN authorization key andF unintentional access to the OpenVMS system enabled for key generation.H Failure to maintain the security of the PAKGEN key or failure to controlB access to the generator can result in the creation of unauthorized
 license keys.   D In particular, do not register the PAKGEN key in an untrusted systemE environment; register and load the PAKGEN key only during use, and do " not release the PAKGEN key itself.   End of PAKGEN documentation  Frequently Asked Questions  4 Q: Where are the system services for LMF documented?: A:  Contact DSPP for the LMF System Service documentation.   ------------------------------  # Date: Mon, 09 Dec 2002 20:40:45 GMT " From:   VAXman-  @SendSpamHere.ORG$ Subject: Re: Another Porting Problem0 Message-ID: <00A18321.D2050FAF@SendSpamHere.ORG>  q In article <Hn$VmidjDWli@eisner.encompasserve.org>, koehler@eisner.nospam.encompasserve.org (Bob Koehler) writes: V >In article <00A18318.059B0768@SendSpamHere.ORG>,   VAXman-  @SendSpamHere.ORG writes: > F >> If the above is truly representative of the code, I fail to see howD >> the VAX didn't puke when the call to 1$ returned to a code streamD >> with 0 (a HALT on VAX and would require KERNEL mode to execute it  >> without returning an OPCDEC). > B >   You been away too long?  The target of a CALLG/CALLS is a word, >   mask for register saves and PSL changes. >    Huh?  # Look at that pseudo code snippet...         .entry $unit_name	      .... 	      .... A      calls #0,1$	; call routine 1$ and return to next instruction  1$:  .word 0	      .... 	      ....       blss Return  & What have I been away from TOO LONG?     Ne'er question my macro.   --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COM              5   "Well my son, life is like a beanstalk, isn't it?"     ------------------------------    Date: 10 Dec 2002 06:01:30 -0800& From: aaron.d.mullens@lmco.com (Aaron)$ Subject: Re: Another Porting Problem= Message-ID: <99c3a525.0212100601.15c7662d@posting.google.com>e  , VAXman-  @SendSpamHere.ORG wrote in message  > 4 > Perhaps a larger snippet of the code would help.   >   E OK, I'll give you a large code segment.  I in no way expect you to golA over it all, but you may be interested in seeing it.  I have beenfE struggling with this section of code for weeks now.  If you believe ItE need to learn Macro64 after reviewing it, then break it to me gently,t and again thanks for your time.   F I listed two .sbttl here, the first function gets the Initial_FP and IB have been able to do this in C and Ada and pass it into a assembly< routine on an Alpha.  The functions are called by Ada units.    " 	.sbttl Initialize Tasking Routine  C ; This routine searches back through stack frames for the second towF last FP. ; This FP is needed for task stack initialization to keep AdaD & the debugger ; happy. ; ; INPUTS:  Offset of the stack top pointer for the currently runningg ;          VMS version ;n ; OUTPUTS: Nonej    < STACK_TOP = ^X4		; stack lower limit (VAX stacks grow down.)0 			; We change this to be the bottom of P0 space1 			; instead of P1 space. The offset is differento 			; between 4.x and 5.x.   * 	.psect	$DATA,long,noexe,pic,rel,noshr,wrt     Initial_FP: .long	0   ( 	.psect	$CODE,long,exe,pic,rel,shr,nowrt    ' 	.entry	$Initialize_Tasking,^m<R10,R11>w  + 	movl 	FP,R11			; start with the current FPP  4 0$:	movl	SF$L_SAVE_FP(R11),R10	; Get the previous FP5 	tstl	SF$L_SAVE_FP(R10)	; is the FP before that = 0 ?t$ 	beql	1$			; if so, remember this FP  $ 	movl 	R10,R11			; else keep looking  	brb	0$  2 1$:	movl	R11,Initial_FP		; record the last FP with 					; a nonzero previous FP  . ; Initialize Ada stack limit to prevent errors5 	tstl	-(SP)			; make room for a longword on the stack"3 	pushab	(SP)			; record the address of the argumentR; 	calls	#1,G^Ada$Current_Task 	; get the main task's Ada TCBe 	addl3	(sp)+,STACK_TOP(ap),r0e5 	clrl	(R0)			; change the lower task stack bound to 0i- 					;   (bottom of P0) to prevent Ada errorsy 4$:	ret				P   a    % 	.sbttl	Initialize Task Stack RoutineS  C ; This routine initializes the new task stack for ease of switchingo    1 	.entry	$INITIALIZE_STACK,^m<R2,R3,R4,R5,R10,R11>m  5 	movl 	4(AP),R10		; get the TCB passed as an argumentm   .if equal <Debugging-Enabled>o 	Debug_Stats	#3,#0,r10 .endce  1 ; Create an initial stack frame on the new stack:   5 	pushl   FP			; save the creator task's Frame Pointeri6 	movl	SP,R11			; save the creator task's Stack Pointer? 	movl 	Initial_SP(R10),SP	; get the initial SP for the new taskp  ; 	movl 	Initial_FP,FP		; set the initial FP for the new taskf7 	calls	#0,1$			; create a stack frame on the new stack,e4 1$:	.word	0			; ...filling in FP with the current SP    F ; Initial condition handler is passed in the Saved_SP field of the TCB  @ 	movl	Saved_SP(R10),(FP)	; put Condition Handler on top of stack= 	clrl	SF$L_SAVE_PC(FP)	; clear the return PC for the new taski    1 ; Create a second stack frame with AST arguments:l  5 	subl	#ArgsLen,SP		; make room for the argument list.o% 	movc3	#ArgsLen,@SF$L_SAVE_AP(FP), - w5 		    (SP) 		; copy creator's arg list onto the stackw 	movl	Initial_PC(R10), - e9 		    Return_PC(SP)	; make the AST return to the new tasks9 	addl	#2,Return_PC(SP)	; adjust the PC for the entry mask   < 	subl	#SF$L_SAVE_REGS,SP	; adjust the SP for remaining frame  A 	movc3	#SF$L_SAVE_REGS,4(R11),- ; copy the rest of the creator's l" 		    (SP) 		; current stack frame  ? 	insv	#0,#SF$V_SAVE_MASK, - 	; indicate no registers were saved $ 		#SF$S_SAVE_MASK,SF$W_SAVE_MASK(SP)  ; 	movl	FP,SF$L_SAVE_FP(SP)	; update the saved FP to indicatel+ 					;   the initial frame on the new stackR  / 	pushl   SP			; record the current SP as the FPe5 	movl 	SP,Saved_SP(R10)	; for when we get rescheduledn  D 	moval   $SCHED_DATA + PQLen,R0	; get the address of scheduling data= 	movl	Priority(R10),R2	; get the priority of the current task>  1 	bbss	R2,Queue_Info(R0),2$	; mark queue non-emptybC 2$:	insqhi	(R10),PQueue(R0)[R2]	; put current task at head of Queued  % 	movl	R11,SP			; restore creator's SPe! 	popl	FP			; restore creator's FPh  $ 	movl	TCB(R0),R1		; get current taskC 	cmpl	Priority(R1),Priority(R10) ; if current task higher priority,t+ 	blss    Return			; that's all - we're doney  0 	$CANTIM_S -			; if new task is higher priority,' 		REQIDT=#-1		; cancel any time-slicingn& 	calls	#0,$SCHEDULE		; and reschedule  Return:i 	ret				; & return to creator   3 ; $Initialize_Stack yields new task stack contents: D ; The address of Frame 1 is saved as the SP for the task to use when7 it is ; first scheduled. ; ; Task Frame 1 (AST Frame) :-, ;		Condition_Handler		=   (Copied & Ignored). ;		Frame Flags			= Copied PSL & no saved regs $ ;		Saved AP			=   (Copied & Ignored)" ;		Saved FP			= Address of Frame 0$ ;		Saved PC			=   (Copied & Ignored)! ;	Args:	Arg Count			= 5  (Copied)<$ ;		AST Arg				=   (Copied & Ignored)$ ;		Saved R0			=   (Copied & Ignored)$ ;		Saved R1			=   (Copied & Ignored)/ ;		Return PC			= Task address+2 (passed in TCB)  ;		Saved PSL			=   (Copied)e ;d% ; Task Frame 0 (Initial Task Frame) : 6 ;		Condition_Handler		= Passed in TCB's saved FP field# ;		Frame Flags			= Created by CALLSt* ;		Saved AP			= Created by CALLS & Ignored- ;		Saved FP			= Initial FP for Ada & Debuggert ;Initial_SP: 	Saved PC			= 0   ------------------------------  % Date: Tue, 10 Dec 2002 10:58:02 -0500a& From: John Reagan <john.reagan@hp.com>$ Subject: Re: Another Porting Problem3 Message-ID: <_5pJ9.38$Dw2.1055916@news.cpqcorp.net>e   Aaron wrote:  G > OK, I'll give you a large code segment.  I in no way expect you to gorC > over it all, but you may be interested in seeing it.  I have been   D Hmmm...  This is very similar to another question asked in the last  couple of months...   G 1) Read the OpenVMS Alpha Calling Standard to learn more than you want h& to know about stack frames on OpenVMS.  F Then read it again, repeat until an expert, write some Macro-64 code,  and expect to debug it.o   Or  H 2) use the LIB$GET_INVO_CONTEXT and friends routines which are designed 9 to walk the stack frames and get the information you wantd  E BTW, Be prepared to rip it all apart for Itanium (which has no frame f pointer at all).     -- a John Reagan ' Compaq Pascal/{A|I}MACRO Project Leaderd Hewlett-Packard Companyt   ------------------------------  % Date: Tue, 10 Dec 2002 11:38:39 -0600-0 From: Earl Lakia <Lakia_n_o__s_p_a_m_@ipact.com>! Subject: File update notificationy1 Message-ID: <_lWdnXSINcW5u2ugXTWcrg@netnitco.net>r  G I have a keyed RMS file that is updated by an Easysoft ODBC server.  I FH have an application that I would like to be notified when an update has H been done to the file (e.g., modified).  Other than digging through RMS H locks, I thought I saw something posted before addressing this problem. H   Obviously, I could poll the file, but this seems to be a bad solution.  H Someone had mentioned ACLs on a directory for determing when a file was D placed in a directory, could something like this work?  Is the last E modified date stored in the directory file and maybe an AST could be r triggered off the ACL?  
 Any thoughts?.   Thanks
 Earl Lakia   ------------------------------  % Date: Tue, 10 Dec 2002 06:30:51 -0800m, From: "James Gessling" <jgessling@yahoo.com>3 Subject: How many messages/second can a CI rail do? 5 Message-ID: <at4tqt$10m4hi$1@ID-46415.news.dfncis.de>0  G I'm investigating a performance issue that occured in our cluster.  Onew morning,K access to a certain file was really slow.  So I looked in the decps data in  theMK performance evaluation display/CI statistics and see that one rail (of six)dL was doing 15,000+ messages per second.  This was (I suppose) due to the lockJ requests between other nodes reading the file.  There are no credit waits. SoI management asked the obvious question, is that too high a rate?  How manye! messages/second can a CI rail do?k   Can anyone help with this?   Jim   J p.s. this is one of those time when I wish Usenet was not so public.  In a forumlL where I knew who was listening, I could give more detail that I am afraid toG give here for fear of getting in trouble for violating confidentiality.t Coulde# www.openvms.org offer such a place?m   ------------------------------  % Date: Tue, 10 Dec 2002 19:47:57 +1100 1 From: Paddy O'Brien <paddy.o'brien@tg.nsw.gov.au>oV Subject: Re: Info-VAX only access (was: "VMS will be around long after we retire" ...), Message-ID: <3DF5AA3D.7060906@tg.nsw.gov.au>  - Doc.Cypher wrote (in response to Kerry Main):d   [snips]   M > You're a fairly frequent contributor, but because you post via Info-VAX theeM > References header is lost on your posts. This - at least with my newsreaderuJ > - results in your posts appearing at the bottom of the thread and out of
 > context. > M > I know there are some contributors who can only access c.o.v. via the list,kH > whereas there are news servers available within HP. I also believe youL > would find it takes less time to go through all the posts in the group via< > a newsreader. It certainly wasn't intended as a criticism.  A Interesting, I'm one of those too (can only access via Info-VAX).a  H Since corporate believe that Gartner, Gates and Unix are the gods (used I to be total VMS), I have lost all access to the world except via Mozilla cF to an Outhouse account.  No ftp, http, etc., which I used to have via G Netscape.  They've installed MS authentication stuff which only allows e< Exploder/Exploiter (so much for MS tap on the wrist by DoJ).  G But why is the context lost?  Out of interest, if I originate a thread  H and people reply via newsreaders, does my original post still appear at  the bottom of said thread?   Regards, Paddy                G ***********************************************************************W  C "This electronic message and any attachments may contain privileged > and confidential information intended only for the use of the B addressees named above.  If you are not the intended recipient of C this email, please delete the message and any attachment and adviseoB the sender.  You are hereby notified that any use, dissemination, 7 distribution, reproduction of this email is prohibited.f  A If you have received the email in error, please notify TransGrid wA immediately.  Any views expressed in this email are those of the  = individual sender except where the sender expressly and with tC authority states them to be the views of TransGrid.  TransGrid uses > virus scanning software but excludes any liability for viruses contained in any attachment.  < Please note the email address for TransGrid personnel is now$ firstname.lastname@transgrid.com.au"  G ***********************************************************************a   ------------------------------    Date: 10 Dec 2002 09:10:18 -0000- From: "Doc.Cypher" <doc_cypher@nym.alias.net> V Subject: Re: Info-VAX only access (was: "VMS will be around long after we retire" ...)5 Message-ID: <20021210091018.5206.qmail@nym.alias.net>o  5 NOTE: This message was sent thru a mail2news gateway.n8 No effort was made to verify the identity of the sender.8 --------------------------------------------------------  G On Tue, 10 Dec 2002, Paddy O'Brien <paddy.o'brien@tg.nsw.gov.au> wrote:f. >Doc.Cypher wrote (in response to Kerry Main):  B >Interesting, I'm one of those too (can only access via Info-VAX). >wI >Since corporate believe that Gartner, Gates and Unix are the gods (used  J >to be total VMS), I have lost all access to the world except via Mozilla G >to an Outhouse account.  No ftp, http, etc., which I used to have via  H >Netscape.  They've installed MS authentication stuff which only allows = >Exploder/Exploiter (so much for MS tap on the wrist by DoJ).  >cH >But why is the context lost?  Out of interest, if I originate a thread I >and people reply via newsreaders, does my original post still appear at d >the bottom of said thread?a  E Okay, I use a Windows client called X-News. Whenever a new message isqI posted it first examines the References: header in an effort to determine-K where in the thread to place the message. If it can't do this, then it willgJ examine the Subject: header and try and use this as a basis for threading.  G You changed the subject, and as there was no References: header in your2J post, my newsreader figures it had better start a new thread. This appearsH to be exactly the same way Google handles things, so if you can bear theE thought of using a PC for a few minutes you can look and see how it'stH handled. You can also go through the "View this article only" then on toK "Original Format" and you'll see the messages where a References: header isd	 provided.r  J Because of the client I use for posting via an account on nym.alias.net, IJ can see exactly what its done to ensure proper threading. This message has the following in the headers:t  , References: <3DF5AA3D.7060906@tg.nsw.gov.au>  K When a news client sees this it places my message under yours, but indentedCJ to indicate that it is a followup. As a discussion continues, it starts toF look like what you see on the left, if someone replies via Info-VAX to7 *any* article it changes to what is shown on the right.C  (       O                   O             (       |                   |             (       +-O                 +-O           (         |                 | |           (         +---O             | +---O       (         |   |             | |   |       (         +-O +-O           | +-O +-O     >                           X               <- Info-VAX posting.  K Now, I assume that the Info-VAX list behaves itself, that means that if yourI examine the headers on this message you should see the References: headereI (as well as a few others). IIRC, the header is permitted in mail, but the.F vast majority of mail clients just discard it when you reply. Ideally,H there would be some way to mark an email address as being a mailing listI thus making the mail client handle the References: header in the same waytJ as a news client. I can imagine that such behaviour would also make life aH whole lot simpler for people developing software for archives of mailing lists.     Doc. -- o6 The bigger the humbug, the better people will like it.K ~ Phineas Taylor Barnum.                             https://vmsbox.cjb.net)   ------------------------------  % Date: Tue, 10 Dec 2002 11:45:22 -0500bB From: "John C. Koska, x-3255, 1-800-209-8352" <itjck01@bender.com> Subject: my recent posts...h= Message-ID: <02121011452276.14260.25112683@alaxp2.bender.com>   8 Well, I guess I have to read and post from OpenVMS MAIL.  E Sorry for all the MIME stuff from Micros__t Outnot and Exhume mailer.   : I have put in a subscribe request from an OpenVMS account.  - Sorry again, and thank you for your patience.t   :) jck
 John Koska Matthew Bender & Co., Inc.   ------------------------------  # Date: Tue, 10 Dec 2002 18:06:50 GMTe" From: Jim McDonald <Jim@mcdee.net>Y Subject: Re: number of fiber connections from alpha to switch and from switch to symmetrio& Message-ID: <3DF62D3A.10306@mcdee.net>   Jesper Monsted wrote:y6 > charles.durfee@bassett.org (charlie durfee) wrote in8 > news:358dbcab.0212041323.3db1436c@posting.google.com:  >  >  >>Thanks for the confirmation!H >>We'll continue cables from each server to both switches, and from each" >>switch to the Symmetrix cabinet. >>             S 1 >>             W >>___          I         ______   >>A1 |-------- T        |      |  >>___|\   ____ C -------|  S   |  >>     \ /     H        |  Y   |  >>      \               |  M   |  >>___  / \____ S 2      |  M   |  >>A2 |/        W -------|      |  >>___|-------- I        |______| >>             T >>             C   >>             H   >  > I > That the way to do it. You could consider interlinking the switches to nM > safeguard against A1's link to switch1 and switch2's link to the symmetrix   > going down simultaneously... >e  I I wouldn't recommend interlinking the switches, it would create a single nD fabric == single point of failure.  Problems with the name service, G routing, or zone changes could take down the entire fabric and both of a! your connections to your storage.a     Cheers,  Jim. -- h Jim McDonald - Jim@mcdee.net   ------------------------------  % Date: Tue, 10 Dec 2002 09:43:49 +0000r' From: Andrew Harrison SUNUK Consultancyo6 Subject: Re: OT: Whoa! Is Sun aiming at VMS's jugular?. Message-ID: <3DF5B755.1080306@nospamn.sun.com>   Bob Ceculski wrote:e > Andrew Harrison SUNUK Consultancy <Andrew_No.Harrison_No@nospamn.sun.com> wrote in message news:<3DF46C65.9090401@nospamn.sun.com>...o >  >>Bob Ceculski wrote:  >>c >>>"David J. Dachtera" <djesys.nospam@fsi.net> wrote in message news:<3DF15610.C34D0025@fsi.net>...n >>>  >>>eD >>>>In InfoWorld on-line today... Opponents of both OpenVMS-IA32 andH >>>>Affordable OpenVMS should note the number and price of downloads forG >>>>Solaris Intel, given that availability was announced only recently.a >>>>$ >>>>Are there any further questions? >>>> >>>>The defense rests. >>>" >>>cA >>>and your point is what?  Slowaris is in the same boat as otherl> >>>unix/linux garbage ... VMS is superior to all them ... they> >>>can give it away and I will still pay for VMS because it is@ >>>the best hands down ... "if its free, there must be a reason,? >>>and 99.9% of the time the reason is no one would buy it" ...  >>3 >>How is OpenVMS superior ? A factual justificationa
 >>please Bob.d >>6 >>You will need to do better than your Alpha is faster6 >>claims which you will remember you completely failed
 >>to justify.v >>	 >>Regardsn >>Andrew Harrisonn >  > @ > clustering, security, reliability, real-time, uptime, 31 certs? > in 13 years while over 500 in 5 years for slowaris ... do youu > want me to continue?   Real-Time ????  3 Really describe how OpenVMS's support for real timea differs from say Solaris's.r  	 Security.s  4 If your evidence for OpenVMS's security pre-eminence2 is its Cert advisory count then you just blew your	 argument.d  0 Repeat after me Cert is not a source of reliable& information on OpenVMS vunerabilities.   The things you forgot:  7 Scalability or rather you were right not to mention it.t Performance ditto  Price ditto' Available applications ditto. Support for current programming and deployment platforms dittob  2 You also forgot the soft things or rather you were right not to mention them:  . Job prospects for people who think like you do$ and don't skill up in something else0 Vendor support or indifference depending on your perspective 0 Close vs open, I don't mean the old open systems/ argument but a vendor who is open to input fromo2 customers about the direction in which they should be going with the OS.a  3 Like it or not the OS is only as good as its parts,-2 OpenVMS has some very good parts, it also has some2 terrible parts and overall you would have to judge it as being adequate.E   RegardsE Andrew Harrisong   ------------------------------   Date: 10 Dec 2002 13:19:30 GMT( From: bill@cs.uofs.edu (Bill Gunshannon)6 Subject: Re: OT: Whoa! Is Sun aiming at VMS's jugular?6 Message-ID: <at4pl1$10id41$1@ID-135708.news.dfncis.de>  . In article <3DF5B755.1080306@nospamn.sun.com>,T 	Andrew Harrison SUNUK Consultancy   <Andrew_No.Harrison_No@nospamn.sun.com> writes: >  >  > Bob Ceculski wrote:l >> Andrew Harrison SUNUK Consultancy <Andrew_No.Harrison_No@nospamn.sun.com> wrote in message news:<3DF46C65.9090401@nospamn.sun.com>... >> rA >> clustering, security, reliability, real-time, uptime, 31 certst@ >> in 13 years while over 500 in 5 years for slowaris ... do you >> want me to continue?  >  > Security.  > 6 > If your evidence for OpenVMS's security pre-eminence4 > is its Cert advisory count then you just blew your > argument.a > 2 > Repeat after me Cert is not a source of reliable( > information on OpenVMS vunerabilities. >   G But Andrew, I love it when he points out CERT as the proof of security.KC I can then remind people that there are even less (maybe none) CERTn announcements for:
   a) RT-11   b) RSTS/E    c) RSX-11M   d) Ultrix-11 and, last but not leasta   e) Primos'  1 For the humor impaired......                  :-)p   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>   u   ------------------------------  % Date: Tue, 10 Dec 2002 12:54:14 +0000r' From: Andrew Harrison SUNUK Consultancyk6 Subject: Re: OT: Whoa! Is Sun aiming at VMS's jugular?. Message-ID: <3DF5E3F6.7070401@nospamn.sun.com>   David Webb wrote:id > In article <3DF4EB57.37E9F9F3@vl.videotron.ca>, JF Mezei <jfmezei.spamnot@vl.videotron.ca> writes: >  >>David Webb wrote:s >>L >>>IA32 is as much on death row as ALPHA. VMS is being ported to Intel's new >>>architecture IA64.b >> >>P >>IA64 is not intel's "new" architecture and it looks like it will never become.L >>It is HP's proprietary architecture with a few others bending to the IntelH >>blackmail and stating that they might make a few IA643 boxes later on. >>I >>Intel has admitted that IA64 woN't be a desktop chip. They have already"" >>downsized their dream big time.  >> > N > Which just means Intel is in real trouble if Hammer lives up to its promise.@ > They may well end up with no commercially viable desktop chip. >   ? They are in real trouble anyway. For desktop also read very lowu@ end server as well. IA-64 is currently too hot and too expensive/ to put in a blade server or a 1U sub 2K server.t  ; So the Intel/HP proposition is that for the desktop and the ; highest volume sector of the server market there will be ant9 entirly different CPU architecture to the mid to high ends
 server range.q  A For HP that means no low end HP-UX/Tru64/OpenVMS servers based ont@ IA-64 instead they have to rely on HP-PA or give up that segmentH of the market to Win2000 on IA32 which is in turn in effect incompatible? with Win2000 on IA64. Currently HP do product price competitivee 1U HP-PA based servers.u  A For Intel that means entirely segmenting their product range intooD two incompatible product sets IA32 and IA64 with the costs of having" to support 2 ISV programs etc etc.  @ This doesn't only look broken it is broken. In addition with theA exception of Alpha which gave up on the low end years ago this isa? strategy does not compete well with the other 64 bit processorsN@ SPARC and Power both of which have binary compatible, no massiveG performance hit between models ranges for low cost to high performance.h  C AMD have clearly seen the glaring hole in the IA64 strategy and aredA intending to make hay at Intel and HP's expense, if they are moren> sucessfull at capturing ISV's which looks like it could be the2 case then the IA64 experiment may well be history.   RegardsM Andrew Harrisone   ------------------------------    Date: 10 Dec 2002 09:35:30 -0800( From: bob@instantwhip.com (Bob Ceculski)6 Subject: Re: OT: Whoa! Is Sun aiming at VMS's jugular?= Message-ID: <d7791aa1.0212100935.6a1e2afd@posting.google.com>c   Andrew Harrison SUNUK Consultancy <Andrew_No.Harrison_No@nospamn.sun.com> wrote in message news:<3DF5B755.1080306@nospamn.sun.com>...e > Bob Ceculski wrote:r > > Andrew Harrison SUNUK Consultancy <Andrew_No.Harrison_No@nospamn.sun.com> wrote in message news:<3DF46C65.9090401@nospamn.sun.com>...  > > B > > clustering, security, reliability, real-time, uptime, 31 certsA > > in 13 years while over 500 in 5 years for slowaris ... do yout > > want me to continue? >  > Real-Time ???? > 5 > Really describe how OpenVMS's support for real timea > differs from say Solaris's.;  ; VMS is the best real time os out there, period, esp. pitted. againset unix/linux ...l   >  > Security.l > 6 > If your evidence for OpenVMS's security pre-eminence4 > is its Cert advisory count then you just blew your > argument.s > 2 > Repeat after me Cert is not a source of reliable( > information on OpenVMS vunerabilities.  8 repeat after me ... cert is a reliable source of finding; out how bad security is on an os ... just ask Micro$oft ... 6 another source is user experience ... I am going on 185 years now on VMS with "NO" security problems and "NO"e4 os crashes ... it just runs and runs like the little* bunny on the battery commercial on tv ...    >  > The things you forgot: > 9 > Scalability or rather you were right not to mention it.e  9 VMS scales just fine, and soon EV7 will take that word tof  new heights ... then itanium ...   > Performance dittoe  7 alpha blows sun away, any day ... EV7 will do more than 5 blow sparky away, it will destroy it in both floatingu point and integer tests ...t  
 > Price ditton  : VMS wins the price contest every time ... has a tco no one else can touch ...   > Available applications ditto  ; plenty currently and many more coming on, esp. with itaniumA around the corner ...a  0 > Support for current programming and deployment  5 as far as hiring programming support, that's easy ...a2 plenty of people available, and if they don't know0 vms, we train them ... vms isn't like unix/linux1 were it takes 2 years to learn all the convuluted . commands and file system and os in general ...2 vms commands make sense and are easily tailored to ones taste ...   > 4 > You also forgot the soft things or rather you were > right not to mention them: > 0 > Job prospects for people who think like you do& > and don't skill up in something else  8 I took AS400 OS400 training and actually tried that junk8 system 9 years ago ... 1 month on it about killed me ...8 had 2 os crashes in 1 month and support had no idea what8 caused them ... no thanks, I don't need to rush the gray5 hairs and blood pressure medication ... unfortunately 3 besides vms, there are no other superior high level  os's out there to go to ...o  2 > Vendor support or indifference depending on your
 > perspectiven  5 we get wonderful support for $700 (bronze) a year ...   5 > Like it or not the OS is only as good as its parts,I4 > OpenVMS has some very good parts, it also has some4 > terrible parts and overall you would have to judge > it as being adequate.b  7 that's your opinion, but of course you willn't tell theN2 truth because you work for sun, stuck selling that6 garbage sparky and the garbage slowaris to go with it,2 of course, having to sell 80,000 sparkys to one or4 two alphas probably earns you a lot more commission,4 which your brain dead customers are paying, thinking! they are getting a great deal ...m   ------------------------------  % Date: Tue, 10 Dec 2002 13:07:10 -0500y5 From: "Fred Kleinsorge" <kleinsorge@star.zko.dec.com>w; Subject: Re: Performance of atomic instructions and lockingi. Message-ID: <3df62dfd$1_2@hpb10302.boi.hp.com>  $ Larry Kilgallen wrote in message ...I >In article <3DEFE1B3.2020905@telocity.com>, Koloth <koloth@telocity.com>s writes:1 >NH >> When the Wildfire was introduced they found that using spinlocks in aK >> NUMA architecture was a problem for heavily used spinlocks.  The CPUs intF >> the same QBB where the memory was was able to get the spinlock moreK >> often than a CPU on a different QBB.  I think to solve this problem theyaB >> had to come up with a queueing mechanism instead of a spinlock. > F >Whereas I thought they adjusted the fairness by changing the spinlockD >counts for local vs. remote memory.  Of course that is harder to doD >for EV7, but I thought a queueing mechanism was bound to be way too5 >slow for the performance one expect from a spinlock.t  H Actually, the change had to do with some RAD awareness, and detection ofH lock "abuse".   So we have a hybrid simple spinlock.  Tru64 injects someB randomness into a backoff time when trying to aquire a spinlock to breakthrough contention.  H We did however, look at a number of other alternatives which might be ofD interest.  I suggest doing a web search with the keywords "cray fairI spinlock".  This should find you some interesting research on fair locks.pL MCS locks, ticket locks, etc.  The general idea is that simple spinlocks canL fail under load with high CPU counts and/or unfairness in access to the lock (such as NUMA).t  L To be brief about it - spinlocks are the most efficient lock mechanism.  ButD if there is any "unfairness" in the system - such as NUMA memory, orJ different speed CPUs, or very high CPU counts - then they can have failureG modes where CPUs can be starved and never aquire the lock.  Most "fair"oK locks use a mechanism that guarantees forward progress of a CPU if all CPUstL are well behavied - but they all have higher overhead than simple spinlocks.H The main differences (IMHO) between the types of fair locks is where the1 cost is paid - in the aquisition, or the release.a  L I think I coded up a MCS (named after the guys who invented it) lock between% two processes once.  Wasn't too hard.m   ------------------------------  % Date: Tue, 10 Dec 2002 13:14:42 -0500d5 From: "Fred Kleinsorge" <kleinsorge@star.zko.dec.com>r; Subject: Re: Performance of atomic instructions and locking-, Message-ID: <3df62fc0_2@hpb10302.boi.hp.com>  % Steve Bainbridge wrote in message ... 2 >Per Schrder <pesc@bredband.net> wrote in message/ news:<XETH9.20320$Y2.719@news2.bredband.com>...I
 >> > Also,H >> > because an area of memory either side of a lock is also locked downG >> > (by the processor/OS) when the lock is locked this may slow thingso >> > down un-expectedly. >>F >> Not quite. The process or OS does not "lock down" memory cells when >> you take a spinlock.a >>H >> First you have the granularity for atomic operations which I think isG >> 4 bytes (I don't have the Alpha architecture manual right now so you F >> should check this.) If all four bytes in a word is protected by the >> same lock, you are OK.i >u& >Not quite. From the OpenVMS Wizard... >oD >  "In regard to topic (6984), the granularity of memory affected byF >   the hardware interlock is implementation-specific, and can involveE >   anything from the smallest grain of memory (a longword) to all ofbG >   system physical memory, and can also potentially be discontiguous."o > G >I'm trying to find a more precise value for the granularity in my casetE >(OpenVMS v7.3-1 and ES40/45 hardware). I seem to recall that placing G >an unused 128 byte array before and after the lock variable was enoughe2 >to ensure that only the lock variable was locked.  G This is chip specific.  Each generation has had larger requirements for L performance reasons.  You should put the lock in a 128 byte aligned block ofJ 128 bytes or more, so that it does not share the cache line with any other data.e  H EV6 and EV7 use cache state as part of the locking protocol.  So the CPUL trying to write the lock can do this if A) the store conditional succeeds inK the cache, and B) if no interrupt occured between the load locked and store.F conditional that read or wrote *any* memory location on the local CPU.  L On earlier CPU designs, there was a global "lock" state, so there was not asL much sensitivity to the cache system - but it also doesn't hurt to make sure( that you allocate a cache line per lock.   ------------------------------  % Date: Tue, 10 Dec 2002 18:57:42 -0000.- From: wspencer@ap.nospam.org (Warren Spencer)i; Subject: Re: Performance of atomic instructions and lockingp5 Message-ID: <92E08BB21warrenspencer1977@216.168.3.30>1  : stephen_bainbridge@yahoo.co.uk (Steve Bainbridge) wrote in3 <a48f6f51.0212061238.7955a785@posting.google.com>: t  2 >Per Schrder <pesc@bredband.net> wrote in message1 >news:<XETH9.20320$Y2.719@news2.bredband.com>...  
 >> > Also,H >> > because an area of memory either side of a lock is also locked downG >> > (by the processor/OS) when the lock is locked this may slow things  >> > down un-expectedly. >> aG >> Not quite. The process or OS does not "lock down" memory cells when   >> you take a spinlock.  >> .I >> First you have the granularity for atomic operations which I think is tH >> 4 bytes (I don't have the Alpha architecture manual right now so you G >> should check this.) If all four bytes in a word is protected by the n >> same lock, you are OK.  >b& >Not quite. From the OpenVMS Wizard... > D >  "In regard to topic (6984), the granularity of memory affected byF >   the hardware interlock is implementation-specific, and can involveE >   anything from the smallest grain of memory (a longword) to all oflG >   system physical memory, and can also potentially be discontiguous."m > G >I'm trying to find a more precise value for the granularity in my casehE >(OpenVMS v7.3-1 and ES40/45 hardware). I seem to recall that placingiG >an unused 128 byte array before and after the lock variable was enoughi2 >to ensure that only the lock variable was locked.  H Perhaps I'm off base here, but I'd consider getting out of the spinlock F business altogether and try the OpenVMS lock manager.  It can deliver I asynchronous notification when your lock becomes available, or pause the aJ asking process until the lock becomes available.  Before trying this, you L may wish to insert counters in your locking code to determine just how much  spinning is going on.r   ws   -- e   Warren Spencer' Senior Software Engineer (not a writer)T The Associated Press  + ** What's brown and sticky?    A stick.  **u   ------------------------------    Date: 10 Dec 2002 08:32:52 -0800- From: jodonnell@hrblock.com (Jason O'Donnell) $ Subject: Porting from Sun to OpenVMS= Message-ID: <9059bf6b.0212100832.7277674c@posting.google.com>    All,  D We are considering porting an application environment from a Solaris! platform to our OpenVMS platform.s  9 Has anybody done a something of this nature and have some	. tips/warnings/suggestions they care to impart?   ------------------------------  % Date: Tue, 10 Dec 2002 08:43:57 -0800h$ From: Shane Smith <ssmith@icius.com>( Subject: RE: Porting from Sun to OpenVMS0 Message-ID: <01C2A028.6272C560@sulfer.icius.com>  F I suggest you provide some idea of the construction of the applicationG environment. What language, any networking, is there a GUI, a database,;; etc. Each flavour of app has a different set of challenges.v   Shanes   -----Original Message-----: From: jodonnell@hrblock.com [mailto:jodonnell@hrblock.com]( Sent: Tuesday, December 10, 2002 8:33 AM To: Info-VAX@Mvb.Saic.Coms$ Subject: Porting from Sun to OpenVMS     All,  D We are considering porting an application environment from a Solaris! platform to our OpenVMS platform.e  9 Has anybody done a something of this nature and have some . tips/warnings/suggestions they care to impart?   ------------------------------    Date: 10 Dec 2002 10:12:21 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen)a( Subject: Re: Porting from Sun to OpenVMS3 Message-ID: <LNq+9eka849f@eisner.encompasserve.org>   m In article <9059bf6b.0212100832.7277674c@posting.google.com>, jodonnell@hrblock.com (Jason O'Donnell) writes:;  F > We are considering porting an application environment from a Solaris# > platform to our OpenVMS platform.v > ; > Has anybody done a something of this nature and have some#0 > tips/warnings/suggestions they care to impart?  F VMS Development has done that (or had a subcontractor do it) since theD DII-COE software (the stuff you will _not_ get when VMS releases its/ enhancements) is basically a port from Solaris.a  D VMS Development regularly gives information about the latest methodsF in this area, including presentations at HPETS (DECUS) in St. Louis in> October and at the VMS Symposium in New Hampshire in November.  E Stand by for January when rumor has it the date for the next US DECUSv4 Symposium (whatever they call it) will be announced.   ------------------------------  % Date: Tue, 10 Dec 2002 12:41:11 -0500e' From: "Main, Kerry" <Kerry.Main@hp.com>;( Subject: RE: Porting from Sun to OpenVMST Message-ID: <BE56C50EA024184DAF48F0B9A47F5CF402660BF3@kaoexc01.americas.cpqcorp.net>   Jason,  G <<<We are considering porting an application environment from a SolarisS$ platform to our OpenVMS platform.<<<  H A few miscellaneous pointers that may be of assistance: (file 13 if seen already)  ? http://www.openvms.compaq.com/openvms/products/ips/porting.htmlFA (OpenVMS Porting Library Routines for moving UNIX applications tol OpenVMS)  0 https://vmsbox.cjb.net/VMS/UNIX_TO_VMS_NOTES.TXT5 (Doc Cyphers tips-n-hints on porting UNIX to OpenVMS)e  B http://www.openvms.compaq.com/openvms/products/ips/netbeans/ (IDE)C "OpenVMS Engineering is pleased to provide NetBeans Version 3.4 forvF OpenVMS Alpha. This is the latest release of NetBeans and is available, on the OpenVMS platform for free download. "  $ http://sourceforge.net/projects/gnv/% http://gnv.sourceforge.net/readme.htm	F (The goal is to port Open Source software to VMS with primary focus on. infrastructure to make porting to VMS easier.)  ; http://www.openvms.compaq.com/openvms/products/ips/gtk.html A "Compaq is pleased to provide an updated (A2) release of GTK+ foroA OpenVMS Alpha, an open source, free software library for creatingt graphical user interfaces."e  3 http://nchrem.tnw.tudelft.nl/openvms/software2.htmlnF "This page gives an overview of the packages I'm running on my OpenVMS. system. for several of them I did some porting> work to get them working on OpenVMS. Please send your comments tojoukj@hrem.stm.tudelft.nl"  1 http://www-pi.physics.uiowa.edu/~dyson/webalizer/SG "The Webalizer is a fast, free web server log file analysis program. It	C produces highly detailed, easily configurable usage reports in HTMLo1 format, for viewing with a standard web browser."      RegardsH  
 Kerry Main Senior ConsultantP Hewlett-Packard (Canada) Co.! Consulting & Integration Servicesa Voice: 613-592-4660d Fax   : 613-591-4477 Email: kerryDOTmain@hpDOTcom-     (remove the DOT's and replace with "."'s)-       -----Original Message-----7 From: Jason O'Donnell [mailto:jodonnell@hrblock.com]=20o  Sent: December 10, 2002 11:33 AM To: Info-VAX@Mvb.Saic.Com3$ Subject: Porting from Sun to OpenVMS     All,  D We are considering porting an application environment from a Solaris! platform to our OpenVMS platform.   9 Has anybody done a something of this nature and have somer. tips/warnings/suggestions they care to impart?   ------------------------------  # Date: Tue, 10 Dec 2002 13:58:31 GMTe( From: "Jay E. Morris" <jem@epsilon3.com>K Subject: Re: Request for Discussion, make comp.os.vms a moderated newsgroupo; Message-ID: <bqmJ9.151766$8D.4260459@twister.austin.rr.com>t  ; In message <3DF3925A.49FB5DEA@fsi.net>, "David J. Dachtera"  <djesys.nospam@fsi.net> wrote: .....iF > Best advice I can give is, if you don't want people prying into your& > private info, don't do it to others. >  > Do unto others, y'know...P >  and then split.e -- a
 Jay E. Morrisa@ Posted with Ink Spot (for Windows CE) from DejaVu Software, Inc.8 Usenet wherever you are - http://www.dejavusoftware.com/   ------------------------------  % Date: Tue, 10 Dec 2002 11:03:16 -0500N> From: "Koska, John C. (LNG-ALB)" <John.C.Koska@lexisnexis.com>( Subject: RE: UPS maxicode and OpenVMS...M Message-ID: <3D35AD137AAAD411A6BA0008C7B1B12D032C3F2E@MBCALBEXC03.BENDER.COM>d  J This message is in MIME format. Since your mail reader does not understand< this format, some or all of this message may not be legible.  ' ------_=_NextPart_001_01C2A065.A6841410h Content-Type: text/plain;o 	charset="iso-8859-1"o+ Content-Transfer-Encoding: quoted-printablef  ; Sorry for not reading your email completely and accurately.?  C I think at the AIM online store the specification can be ordered=20 B or a Word document order form can be downloaded.  I believe the=20= document is ANSI/AIM BC10-ISS ($60.00) and there is also a=20e. development diskette on Maxicode ($399.00) =20  - The link I have that seems to work for me is:s/   http: //www.aimi.org/aimstore/default.asp =204  F Within the first paragraph the text mentions the Word order form or=20C placing an order electronically.  For me, clicking on the hypertextw> words of "order" or "electronically" brings me to places where$ the specification can be ordered.=20  < Now, if you mean dead end, as in, it costs some money to get; the specification sent out.  Well, I guess you are correct.e   :) jck
 John Koska Matthew Bender & Co., Inc.   > -----Original Message-----# > From: VAXman-@SendSpamHere.ORG=20g) > Sent: Monday, December 09, 2002 8:11 PM  > To: Info-VAX@Mvb.Saic.Coml* > Subject: Re: UPS maxicode and OpenVMS... >=20 >=205 > In article <3DF51A76.4B21AE57@aaa.com>, Jan-Erik=20r: > =3D?iso-8859-1?Q?S=3DF6derholm?=3D <aaa@aaa.com> writes:  > >You could always start here : > >t > >http: //www.maxicode.com/ > >e > >Jan-Erik S=F6derholmp >=20 >=20B > If you'd have read the entire *two* sentences, you see that I=20 > did visit that< > site and the specification link there leads to a dead end. >=20 > --; > VAXman- OpenVMS APE certification number: AAA-0001    =20  > VAXman(at)TMESIS(dot)COM >           =20g9 >   "Well my son, life is like a beanstalk, isn't it?"=20)
 In articleD <3D35AD137AAAD411A6BA0008C7B1B12D032C3F28@MBCALBEXC03.BENDER.COM>, = "Koska, 8 John C. (LNG-ALB)" <John.C.Koska@lexisnexis.com> writes:B >This message is in MIME format. Since your mail reader does not =
 understand= >this format, some or all of this message may not be legible.  >t* >------_=3D_NextPart_001_01C29FCC.FE12B9A0 >Content-Type: text/plain; >	charset=3D"iso-8859-1" > > >Anyone using an application on OpenVMS Alpha that takes UPS = information andt@ >creates UPS Maxicode (w ww.maxicode.com) bitmap image, PCL or =
 postscript for 
 >printing?  G Of course, the "specifications" link at this site doesn't lead one to =e the  code's specifcations. =20x  H If you can find a specification for maxicode, please let me know.  I'd = love to code up PostScript for it.a   --2 VAXman- OpenVMS APE certification number: AAA-0001 VAXman(at)TMESIS(dot)COM
           =20i7   "Well my son, life is like a beanstalk, isn't it?"=20    >=20  ' ------_=_NextPart_001_01C2A065.A6841410c Content-Type: text/html; 	charset="iso-8859-1"h+ Content-Transfer-Encoding: quoted-printables  1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">d <HTML> <HEAD>9 <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =* charset=3Diso-8859-1">@ <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
 5.5.2654.19">i. <TITLE>RE: UPS maxicode and OpenVMS...</TITLE> </HEAD>e <BODY>  C <P><FONT SIZE=3D2>Sorry for not reading your email completely and =  accurately.</FONT> </P>  I <P><FONT SIZE=3D2>I think at the AIM online store the specification can =i be ordered </FONT>9 <BR><FONT SIZE=3D2>or a Word document order form can be = ' downloaded.&nbsp; I believe the </FONT>eH <BR><FONT SIZE=3D2>document is ANSI/AIM BC10-ISS ($60.00) and there is = also a </FONT>E <BR><FONT SIZE=3D2>development diskette on Maxicode ($399.00)&nbsp; =  </FONT>t </P>  F <P><FONT SIZE=3D2>The link I have that seems to work for me is:</FONT>! <BR><FONT SIZE=3D2>&nbsp; http: =a1 //www.aimi.org/aimstore/default.asp&nbsp; </FONT>  </P>  I <P><FONT SIZE=3D2>Within the first paragraph the text mentions the Word =a order form or </FONT>*C <BR><FONT SIZE=3D2>placing an order electronically.&nbsp; For me, =   clicking on the hypertext</FONT>2 <BR><FONT SIZE=3D2>words of &quot;order&quot; or =; &quot;electronically&quot; brings me to places where</FONT>s< <BR><FONT SIZE=3D2>the specification can be ordered. </FONT> </P>  I <P><FONT SIZE=3D2>Now, if you mean dead end, as in, it costs some money =u
 to get</FONT>tH <BR><FONT SIZE=3D2>the specification sent out.&nbsp; Well, I guess you = are correct.</FONT>- </P>   <P><FONT SIZE=3D2>:) jck</FONT>D$ <BR><FONT SIZE=3D2>John Koska</FONT>8 <BR><FONT SIZE=3D2>Matthew Bender &amp; Co., Inc.</FONT> </P>  8 <P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>> <BR><FONT SIZE=3D2>&gt; From: VAXman-@SendSpamHere.ORG </FONT>F <BR><FONT SIZE=3D2>&gt; Sent: Monday, December 09, 2002 8:11 PM</FONT>8 <BR><FONT SIZE=3D2>&gt; To: Info-VAX@Mvb.Saic.Com</FONT>G <BR><FONT SIZE=3D2>&gt; Subject: Re: UPS maxicode and OpenVMS...</FONT>  <BR><FONT SIZE=3D2>&gt; </FONT>  <BR><FONT SIZE=3D2>&gt; </FONT>lG <BR><FONT SIZE=3D2>&gt; In article &lt;3DF51A76.4B21AE57@aaa.com&gt;, =t Jan-Erik </FONT>< <BR><FONT SIZE=3D2>&gt; =3D?iso-8859-1?Q?S=3DF6derholm?=3D =" &lt;aaa@aaa.com&gt; writes:</FONT>@ <BR><FONT SIZE=3D2>&gt; &gt;You could always start here :</FONT># <BR><FONT SIZE=3D2>&gt; &gt;</FONT>w< <BR><FONT SIZE=3D2>&gt; &gt;http: //www.maxicode.com/</FONT># <BR><FONT SIZE=3D2>&gt; &gt;</FONT>t7 <BR><FONT SIZE=3D2>&gt; &gt;Jan-Erik S=F6derholm</FONT>  <BR><FONT SIZE=3D2>&gt; </FONT>a <BR><FONT SIZE=3D2>&gt; </FONT>iH <BR><FONT SIZE=3D2>&gt; If you'd have read the entire *two* sentences, = you see that I </FONT>- <BR><FONT SIZE=3D2>&gt; did visit that</FONT>eH <BR><FONT SIZE=3D2>&gt; site and the specification link there leads to = a dead end.</FONT> <BR><FONT SIZE=3D2>&gt; </FONT>e! <BR><FONT SIZE=3D2>&gt; --</FONT>iC <BR><FONT SIZE=3D2>&gt; VAXman- OpenVMS APE certification number: =h( AAA-0001&nbsp;&nbsp;&nbsp;&nbsp; </FONT>7 <BR><FONT SIZE=3D2>&gt; VAXman(at)TMESIS(dot)COM</FONT>  <BR><FONT =tI SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=c ;&nbsp; </FONT> G <BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp; &quot;Well my son, life is like a =s" beanstalk, isn't it?&quot; </FONT> <BR><FONT SIZE=3D2>In article =eI &lt;3D35AD137AAAD411A6BA0008C7B1B12D032C3F28@MBCALBEXC03.BENDER.COM&gt;,=h'  &quot;Koska, John C. (LNG-ALB)&quot; =i6 &lt;John.C.Koska@lexisnexis.com&gt; writes:</FONT></P>  G <P><FONT SIZE=3D2>&gt;This message is in MIME format. Since your mail =w! reader does not understand</FONT> I <BR><FONT SIZE=3D2>&gt;this format, some or all of this message may not =- be legible.</FONT> <BR><FONT SIZE=3D2>&gt;</FONT>G <BR><FONT SIZE=3D2>&gt;------_=3D_NextPart_001_01C29FCC.FE12B9A0</FONT> 7 <BR><FONT SIZE=3D2>&gt;Content-Type: text/plain;</FONT> = <BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =I' charset=3D&quot;iso-8859-1&quot;</FONT>e <BR><FONT SIZE=3D2>&gt;</FONT>E <BR><FONT SIZE=3D2>&gt;Anyone using an application on OpenVMS Alpha =s% that takes UPS information and</FONT> H <BR><FONT SIZE=3D2>&gt;creates UPS Maxicode (w ww.maxicode.com) bitmap =# image, PCL or postscript for</FONT>h' <BR><FONT SIZE=3D2>&gt;printing?</FONT>m </P>  E <P><FONT SIZE=3D2>Of course, the &quot;specifications&quot; link at =i( this site doesn't lead one to the</FONT>6 <BR><FONT SIZE=3D2>code's specifcations.&nbsp; </FONT> </P>  H <P><FONT SIZE=3D2>If you can find a specification for maxicode, please =" let me know.&nbsp; I'd love</FONT>7 <BR><FONT SIZE=3D2>to code up PostScript for it.</FONT>i </P>   <P><FONT SIZE=3D2>--</FONT> > <BR><FONT SIZE=3D2>VAXman- OpenVMS APE certification number: =@ AAA-0001&nbsp;&nbsp;&nbsp;&nbsp; VAXman(at)TMESIS(dot)COM</FONT> <BR><FONT =aG SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =. </FONT>gH <BR><FONT SIZE=3D2>&nbsp; &quot;Well my son, life is like a beanstalk, = isn't it?&quot; </FONT>r </P>   <P><FONT SIZE=3D2>&gt; </FONT> </P>   </BODY>r </HTML>n) ------_=_NextPart_001_01C2A065.A6841410--u   ------------------------------  % Date: Tue, 10 Dec 2002 11:22:11 -0500y> From: "Koska, John C. (LNG-ALB)" <John.C.Koska@lexisnexis.com>( Subject: RE: UPS maxicode and OpenVMS...M Message-ID: <3D35AD137AAAD411A6BA0008C7B1B12D032C3F32@MBCALBEXC03.BENDER.COM>R  J This message is in MIME format. Since your mail reader does not understand< this format, some or all of this message may not be legible.  ' ------_=_NextPart_001_01C2A068.4B396210i Content-Type: text/plain;3 	charset="iso-8859-1"4  7 I believe you are correct, and well worth looking into.t   Thanks.l  
 John Koska Matthew Bender & Co., Inc.   > -----Original Message-----3 > From: Ken Randell [mailto:ken.randell@fortel.com] * > Sent: Monday, December 09, 2002 10:41 PM > To: Info-VAX@Mvb.Saic.Com * > Subject: Re: UPS maxicode and OpenVMS... >  > > > If I read this right & you can use Tomcat, then why not try  > CSWS 1.3 running= > on VMS 7.3-1 and the Tomcat server (2.0 I think).  I don't   > know what minimum = > version your maxicode requires, but CSWS & Tomcat are free t > (well, with theu. > OS anyway).  It might be worth looking into. >  >   ' ------_=_NextPart_001_01C2A068.4B3962102 Content-Type: text/html; 	charset="iso-8859-1"e  1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">  <HTML> <HEAD>H <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">H <META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.19">. <TITLE>RE: UPS maxicode and OpenVMS...</TITLE> </HEAD>  <BODY>  N <P><FONT SIZE=2>I believe you are correct, and well worth looking into.</FONT> </P>   <P><FONT SIZE=2>Thanks.</FONT> </P>  ! <P><FONT SIZE=2>John Koska</FONT>j6 <BR><FONT SIZE=2>Matthew Bender &amp; Co., Inc.</FONT> </P>  6 <P><FONT SIZE=2>&gt; -----Original Message-----</FONT>z <BR><FONT SIZE=2>&gt; From: Ken Randell [<A HREF="mailto:ken.randell@fortel.com">mailto:ken.randell@fortel.com</A>]</FONT>E <BR><FONT SIZE=2>&gt; Sent: Monday, December 09, 2002 10:41 PM</FONT>"6 <BR><FONT SIZE=2>&gt; To: Info-VAX@Mvb.Saic.Com</FONT>E <BR><FONT SIZE=2>&gt; Subject: Re: UPS maxicode and OpenVMS...</FONT>p <BR><FONT SIZE=2>&gt; </FONT>d <BR><FONT SIZE=2>&gt; </FONT> ] <BR><FONT SIZE=2>&gt; If I read this right &amp; you can use Tomcat, then why not try </FONT>u- <BR><FONT SIZE=2>&gt; CSWS 1.3 running</FONT>u] <BR><FONT SIZE=2>&gt; on VMS 7.3-1 and the Tomcat server (2.0 I think).&nbsp; I don't </FONT>s. <BR><FONT SIZE=2>&gt; know what minimum</FONT>\ <BR><FONT SIZE=2>&gt; version your maxicode requires, but CSWS &amp; Tomcat are free </FONT>, <BR><FONT SIZE=2>&gt; (well, with the</FONT>N <BR><FONT SIZE=2>&gt; OS anyway).&nbsp; It might be worth looking into.</FONT> <BR><FONT SIZE=2>&gt; </FONT>o <BR><FONT SIZE=2>&gt; </FONT>a </P>   </BODY>  </HTML>B) ------_=_NextPart_001_01C2A068.4B396210--    ------------------------------  % Date: Tue, 10 Dec 2002 09:50:22 -0700d From: Kevin Handy <kth@srv.net> ( Subject: Re: UPS maxicode and OpenVMS...& Message-ID: <3DF61B4E.4000508@srv.net>   Koska, John C. (LNG-ALB) wrote:rJ > Anyone using an application on OpenVMS Alpha that takes UPS information C > and creates UPS Maxicode (www.maxicode.com) bitmap image, PCL or r > postscript for printing?  9 FWIW: I've done a UPS label with the Maxicode blob on it,n9 but I used an Eltron printer for the Maxicode part of it,u7 since it has it built in. Sorry, I could never find anye. useful info on creating maxicode from scratch.  8 Another problem you'll have is verifying the data on the9 blob, unless you can afford a better bar code reader thana9 I could.  Ended up sending samples to UPS and having them 2 look for problems.  It's not easy to get it right.   > K > I currently do barcode printing of 3 of 9 code to Intermec printers, but pK > now there is a requirement to output UPS Maxicode.  We are looking for a tJ > solution that runs on OpenVMS, rather than on another platform and have ) > to integrate it into the print process.o > K > I have come across Peernet at www.peernet.com , which according to their   > website... > K > "Enterprise Labeling has been developed in 100% Java, and can operate on eK > any Java 2 platform running a Java Enterprise Application Server or Java  G > Servlet Runner - such as Tomcat, BEA WebLogic, Apache-JServ, Allaire -I > JRun, Inprise Application Server, or IBM WebSphere Application Server. sE > As well, Enterprise Labeling is platform independent, and has been u@ > tested on the Solaris, Linux, MAC OS X, and Windows platforms. >  > "e > K > This leads me to believe that I would need Java(tm) 2 Enterprise Edition wI > (J2EE) that would come from one of the middleware companies mentioned, >D > rather than Java(tm) 2 Standard Edition (J2SE).   With J2EE, then   > Peernet might have a solution. > J > Any other solutions out there?  And do you think my chain of thought is + > correct on having J2EE for Peernet stuff?e > H > Ultimately, I guess I will have to contact Peernet on their solution, H > but it would be nice to know of other solutions or if anyone is using 
 > their's. >    ------------------------------  % Date: Tue, 10 Dec 2002 08:45:43 -0500t# From: "mhr" <mreilly36@comcast.net>m' Subject: Re: Using old VRT19-HA Monitoru0 Message-ID: <uTKdnVnzd-bvcmigXTWcoA@comcast.com>  L www.si87.com had video cards for these old ff/sog monitors as well as syn on( green adapters, both linux and win boxes mhr)I "Ray Fusci" <rxfxuxsxcxix(at)xcxhxaxrxtxexrx(dot)xnxext> wrote in messageo) news:uva87r3lk10edb@corp.supernews.com... D > One cable that you can use has DEC part# BC13L-10. It has five BNC
 > connectors:eK > Red, Green, Blue, White (horizontal Sync) and Black (Vertical Sync).  Youf- > can just leave the Black and White hanging.n >eG > The greater challenge is to find a video card (or adapters) that will- drive- > the G > monitor. It will need to support "Sync on Green," and it will need tos
 > support thecI > (fixed) frequencies available on the monitor. IIRC, there was more than0 oneoC > monitor badged as a VRT19-HA. I believe the GDM-1961 and GDM-2039@ > were two.c > H > I believe the VRT19-HA does 66 or 72 Hz, 1280x1024. You'll need to see0 > which monitor you have, and look up its specs. > > > The VRT19-HA does NOT do VGA, so you wouldn't be able to see@ > DOS boot screens, for example. Makes it of limited usefulness. >vJ > You'd be better off trading it to someone who is using a 5-BNC multisync8 > monitor on his VAX or Alpha. Then you'd both be happy. >f
 > regards, >l >r0 > "VAXVMS" <bounce@notmail.com> wrote in messageG > news:BA52530E3149734A9BAABDBBFA808E4903027BA8@rlghncst964.usps.gov...> > > 5 > > The VRT-17s have Sony Trinitron tubes inside 'em.i: > > And wall-to-wall metal shielding surrounding the tube. > >l4 > > I suspect the same is true for the 19s, but I've& > > never had occasion to open one up. > > 7 > > Definitely a superior level of construction than isi* > > the norm forthings manufactured today. > >r= > > A 3 BNC => VGA adapter does exist- I'm virtually positiveh+ > > that it's mentioned in the OpenVMS FAQ.t > >e> > > Also if you websearch on "BNC to VGA" and/or "VGA to BNC",: > > you'll get a large number of hits for places that have > > cables.V > >r
 > > WWWebb > > =========================r > > I had one of those > >s$ > > They are a sony, and very heavy." > > Spent ages looking ofr a cable/ > > for it. Didn't have the skill/understandingd > > on how to make my own. > >b% > > Eventually after four house movese# > > I sadly had to through it away.e > > Worked great on my VAX 4000s > > though.I > >i > > not really any help sorryo > >I > > kiwi > >  > > ? > > "Jack Trachtman" <Jack.Trachtman@vmmc.org> wrote in messagee; > > news:69d784c4.0211291505.336a34f5@posting.google.com...h= > > > Can anyone tell me if I can use an old VRT19-HA monitoro; > > > with one of the newer graphics cards (some version ofe > > > a Number 9 card)?  > > >w9 > > > The monitor takes an RGB cable (only 3 wires).  Any 4 > > > idea where to get a conversion cable?  Thanks. > >  > > ========================$ > > William W. Webb / DSSC/RLM, USPS > > OpenVMS Support Services* > > 4924 Green Road Raleigh, NC 27616-2800> > > 919.874.3043 <FirstInitialDotLastNameAtEmailDotUSPSDotGov> >H >i   ------------------------------    Date: 10 Dec 2002 02:33:40 -0800 From: mb301@hotmail.com (MB) Subject: Re: Vestu= Message-ID: <1d08b916.0212100233.4c0d7a1a@posting.google.com>D  D DECmigrate is a binary translator -- it converts a binary executableB (that is, compiled) program for OpenVMS VAX or ULTRIX RISC on MIPS? into a binary executable program optimized for OpenVMS Alpha oriA Compaq's Tru64 UNIX. To convert the code, DECmigrate works like a_A compiler: it uses the binary code for Alpha or MIPS as if it were.? source code and generates equivalent native Alpha binaries. TheiE original and newly translated binaries are functionally the same, butw? the translated versions run faster, taking advantage of Alpha's  superior performance.o  G http://www.openvms.compaq.com/doc/72final/6459/6459pro.html#my_pref_syms  - http://www.support.compaq.com/amt/decmigrate/t   Have fun:-)u Mark  ^ "Barry Strets" <Barrys2552@attbi.com> wrote in message news:<ucgJ9.5266$hw3.1990@sccrnsc04>...3 > What is VEST???? and where do I get a copy of it.e >  > Barry Streetst > bstreets@echoman.com   ------------------------------  % Date: Tue, 10 Dec 2002 17:44:45 +0100 4 From: Didier Morandi <Didier.Morandi.nospam@Free.fr> Subject: Re: Vests& Message-ID: <3DF619FD.1030600@Free.fr>  7 See also: http://www.softresint.com/news/DECmigrate.htmV   D.   MB a crit: F > DECmigrate is a binary translator -- it converts a binary executableD > (that is, compiled) program for OpenVMS VAX or ULTRIX RISC on MIPSA > into a binary executable program optimized for OpenVMS Alpha ortC > Compaq's Tru64 UNIX. To convert the code, DECmigrate works like a C > compiler: it uses the binary code for Alpha or MIPS as if it wereuA > source code and generates equivalent native Alpha binaries. ThelG > original and newly translated binaries are functionally the same, butiA > the translated versions run faster, taking advantage of Alpha's  > superior performance.v > I > http://www.openvms.compaq.com/doc/72final/6459/6459pro.html#my_pref_symt > / > http://www.support.compaq.com/amt/decmigrate/u > 
 > Have fun:-)n > Mark > ` > "Barry Strets" <Barrys2552@attbi.com> wrote in message news:<ucgJ9.5266$hw3.1990@sccrnsc04>... > 3 >>What is VEST???? and where do I get a copy of it.l >> >>Barry Streets  >>bstreets@echoman.com >    ------------------------------  # Date: Tue, 10 Dec 2002 06:54:18 GMT + From: "Barry Strets" <Barrys2552@attbi.com>.
 Subject: Vest + Message-ID: <ucgJ9.5266$hw3.1990@sccrnsc04>e  1 What is VEST???? and where do I get a copy of it.o  
 Barry Streetsk bstreets@echoman.com   ------------------------------  % Date: Tue, 10 Dec 2002 09:08:46 +0100t4 From: Didier Morandi <Didier.Morandi.nospam@Free.fr>4 Subject: [search] looking for 1986 DECcies in France& Message-ID: <3DF5A10E.8000000@Free.fr>  N I'm looking for folks who worked in 1986/87 for DEC or other business-related P vendors on a huge VAX/VMS/DNC project in the Rhone/Alps area. Please answer via  email. Thanks.  H Je cherche  prendre contact avec des anciens de DEC France et d'autres P entreprises qui auraient particip  un grand projet de commande numrique avec K VAX/VMS dans la rgion Rhne/Alpes en 1986/87. Merci de rpondre par email.   
 D. aka DTL   ------------------------------   End of INFO-VAX 2002.682 ************************