1 INFO-VAX	Sat, 21 Jul 2001	Volume 2001 : Issue 402       Contents: RE: a CI question 0 Re: Adding an Alpha processor - any VMS changes?0 Re: Adding an Alpha processor - any VMS changes?( Re: Alpha:  an invitation to communicate( Re: Alpha:  an invitation to communicate( Re: Alpha:  an invitation to communicate( Re: Alpha:  an invitation to communicate( Re: Alpha:  an invitation to communicate' Re: Alpha: an invitation to communicate * RE: Best file spec for incremental backup? Re: Creating TK50 images Re: KERMIT.HLB Re: Process adopts ItaniumD RE: Security-Enhancing Products for Compaq OpenVMS from PointSecu	reC Re: Security-Enhancing Products for Compaq OpenVMS from PointSecure $ Re: Selling VMS to another company ?$ Re: Selling VMS to another company ?5 Re: SMS on VMS [was RE: Full port of VMS to Itanium.] 5 Re: SMS on VMS [was RE: Full port of VMS to Itanium.]  V7.3 XFCACHE-W-DATALOSS ?  Re: VAX 8250 Console Command Re: VMS Trivia Question  VS3100 driving me mental!!, [Q] CXX, global variables, Shareable library  F ----------------------------------------------------------------------  % Date: Sat, 21 Jul 2001 09:12:38 +0100 5 From: "Steeples, Oliver" <Oliver.Steeples@compaq.com>  Subject: RE: a CI questionN Message-ID: <F498D199EDB12D468CD2C66680D3080116D600@reoexc04.emea.cpqcorp.net>  I Unsure what you mean by packet mode as it's either async or sync and both ) are packet based.  As for the answer.....   B The CIPCA uses a new, more optimal CI arbitration algorithm calledE Synchronous Arbitration instead of the older Asynchronous Arbitration H algorithm. The two algorithms are completely compatible with each other.C Under CI saturation conditions, both the old and new algorithms are J equivalent and provide equitable round-robin access to all nodes. However,E under less than saturation conditions, the new algorithm provides the  following benefits:   I Reduced packet transmission latency due to reduced average CI arbitration  time. # Increased node-to-node throughput.    G Complete elimination of CI collisions that waste bandwidth and increase I latency in configurations containing only Synchronous Arbitration nodes.    F Reduced CI collision rate in configurations with mixed Synchronous andK Asynchronous Arbitration CI nodes. The reduction is roughly proportional to G the fraction of CI packets being sent by the Synchronous Arbitration CI  nodes.    K Support for Synchronous Arbitration is latent in the HSJ controller family. D In configurations containing both CIPCAs and HSJ controllers, Compaq; recommends enabling the HSJs to use Synchronous Arbitration     G Or put another way, synchronous arbitration means the the CIPCA and the J HSJxx will keep better track of when their arbitration slot is during idleL times on the CI.  The CIXCD will continue to start timing when either it hasJ work to do or the last traffic is complete.  This means that the CIXCD mayL cause a collision at the frequency it does now which is not a problem rather7 than almost no collisions with synchronous arbitration.     J The controllers should be set for async unless you had a cipca, or a largeD cluster.  Also 4k packets can be used for better performance.  Other performace enhancements are:  F 1)set CI node id's so HSC's low (0,1..) then HSJ40's, 50's, vax's thenL alphas at the top.  This way the faster alphas do not get constant cntrol of the CI. 4 2) check HSJ's upto 3.7j and 5.7j HSOF respectively.G 3) check cipca/hsj's set for 16/32 mode.  Ideally want 16 due to ci arb  polling 5 4) sysgen values pamaxport, panumpoll, papollinterval . 5) terminators on unused ports on star coupler     Regards, 	Oliver   ? "Artoo-Detoo, you know better than to trust a strange computer"      -----Original Message-----% From: Dirk Munk [mailto:munk@home.nl] $ Sent: Friday, July 20, 2001 11:15 PM To: Info-VAX@Mvb.Saic.Com  Subject: a CI question    A It seems there are three communication modes available on CI raid , controllers (HSJ40, HSJ50 etc.) . These are: synchronous mode asynchronous mode  packet mode   H Can someone please explain to me what the difference between these modesA is, and when I should choose which mode ? Of course we are always $ looking for maximum performance ....   regards,   Dirk   ------------------------------  % Date: Sat, 21 Jul 2001 13:47:46 +0200 " From: "Hans Vlems" <hvlems@iae.nl>9 Subject: Re: Adding an Alpha processor - any VMS changes? ( Message-ID: <9jbptu$osn$1@news.IAEhv.nl>  E That is correct, SMP became available with V5.0. Before that the boot 	 processor J did all the IO work for the entire system. So you could have cpu#1 running at 100% B while the second one never got over 10% on an IO intensive system.L In VMS V5 that was a lot better , even though in V5.x the primary cpu had to handle VMS related tasks.J No idea whether V7 is different from V5 in that respect. We no longer have VMS on multiprocessors.   Hans  8 Joe Heimann <heimann@nog.ecs.umass.edu> wrote in message% news:9jaq3p$2i$1@odo.ecs.umass.edu... # > Hans Vlems <hvlems@iae.nl> wrote: G > > Nope, for 4.6 you needed a special kit to turn multi-processing on. B > > At least that's what I remember from 4.6 and 4.7 on a VAX8350.E > > In fact the second cpu was turned on only since we installed V5.0  > G > If I remember right, on a 8350 you could run the second processor but H > only in ASMP mode before VMS 5.0 came out.  I remember seeing the codeD > to start the processor in the old startup files for our 8350.  WasE > cleaning out some old cruft from its system disk a year or two ago.  > 
 > Joe Heimann  >  > heimann@ecs.umass.edu  >    ------------------------------  % Date: Sat, 21 Jul 2001 10:22:15 -0400 ) From: "Neil Rieck" <n.rieck@sympatico.ca> 9 Subject: Re: Adding an Alpha processor - any VMS changes? : Message-ID: <ogg67.8276$OK2.1271565@news20.bellglobal.com>  0 "Tom Steuver" <steuver@nku.edu> wrote in message) news:tkts59e6pr0c94@corp.supernews.com... G > I'm adding a processor to our Alpha Server 2100.  Do I need to do any 1 > changes to OpenVMS for it to function properly?  > 	 > Thanks, 
 > Tom Steuver  >   . Nope. I do this all the time on VAX and Alpha.E 1. register and load the required SMP license for each additional CPU  2. install the CPU then reboot? 3. run the system for 24 hours then execute @sys$update:autogen    p.s. #1 H If you install the CPU and boot without the required license loaded, theI system will come up with license errors AND only a console log on will be 
 permitted.   p.s. #2 I Contrary to many other (NT related) SMP explanations associated with this L thread, in VMS all computable tasks are perceived as waiting in a queue withJ many CPUs serving that queue (think of this as a generic print queue whichI sends print jobs to more than one print queue). When you do a "$SHOW SYS" J command with the SMP kernel running, scan for tasks with state = "CUR" andH the number following it will indicate which CPU is currently serving it.  
 Neil Rieck Kitchener/Waterloo/Cambridge,  Ontario, Canada.! http://www3.sympatico.ca/n.rieck/    ------------------------------  % Date: Sat, 21 Jul 2001 02:26:52 -0400 ' From: "Bill Todd" <billtodd@foo.mv.com> 1 Subject: Re: Alpha:  an invitation to communicate ( Message-ID: <9jb733$8e1$1@pyrite.mv.net>  * "Magnus M" <mmad@tips.se> wrote in message- news:XqZ57.755$Ta.2043@news3.global-ip.net...  > 4 > "Bill Todd" <billtodd@foo.mv.com> wrote in message$ > news:9j9gt8$t5q$1@pyrite.mv.net... > > . > > "Magnus M" <mmad@tips.se> wrote in message1 > > news:O3V57.750$Ta.1929@news3.global-ip.net...  > >  > > ... I > > That his is the only public entry from a Compaq employee stating that  > CompaqF > > lied through its teeth is hardly surprising.  What you should findE > > surprising is the lack of any public entries from Alpha engineers  stating F > > that Compaq told the truth:  if indeed that's the case, there's no% > > job-related reason not to air it.  > > % > > > and he didn\t get too specific.  > >  > > Exactly what part of > > C > > "This is a complete and total FABRICATION on the part of Compaq 
 > management. I > > Anyone who believes these cowardly words probably deserves to be lied  to"  > > + > >  do you feel requires more specificity?  > F > I meant technically specific, that was upset and felt that lies were spread
 > is obvious. L > I would have been interested in figures for EV8 based on simulations, more	 > detail.   H Interesting perhaps, but unrelated to the question, which is in no way a technical issue.  E Compaq says its Alpha engineers said "Alpha would have had difficulty & staying ahead of IA64 in performance".  ; The Alpha engineers say they didn't say anything like that.   J Whether you believe that the Alpha engineers in fact could have maintainedI an Alpha lead (and whether you would like some technical data to help you G second-guess them on this question - which request IMO might verge upon H being insulting) really isn't relevant to whether Compaq lied about what
 they said.   >  > > > J > > > I agree with this but then I can't say I  find many big corporations > that& > > > are much better in this respect. > > B > > I'm not really familiar with how IBM operates, but my distinct
 impression > isK > > that it differs markedly from Compaq in the respects I mentioned above. I > > Information from someone better-acquainted with such details would be  nice4 > > (Terry has thrown some bouquets their way IIRC). > F > On the other hand IBM is infamous for killing off excellent internal
 > projects& > in favour of bloated replacements...  L While that's hardly admirable, it doesn't have anything like the same effect/ on customers and on their ability to trust IBM.   %  I remember Jim Gray stating (in  the I > System R reunion notes) that someone had had an excellent product idea,  > "WhichK > of course at IBM meant was a perfect guarantee that the project would get  > cancelled").  K IIRC it's been well over a decade since Jim worked at IBM (he was at Tandem F and DEC for quite a while, and most recently Microsoft).  Gerstner hasJ apparently transformed the corporation in many ways, and I'd at least hope( that this area is one of those affected.   - bill   ------------------------------    Date: 21 Jul 2001 00:11:52 -0700/ From: Brannon_Batson@yahoo.com (Brannon Batson) 1 Subject: Re: Alpha:  an invitation to communicate = Message-ID: <4495ef1f.0107202311.490d844e@posting.google.com>   Z "Magnus M" <mmad@tips.se> wrote in message news:<XqZ57.755$Ta.2043@news3.global-ip.net>...4 > "Bill Todd" <billtodd@foo.mv.com> wrote in message$ > news:9j9gt8$t5q$1@pyrite.mv.net... > >  > > [snip]   > >  > > Exactly what part of > > O > > "This is a complete and total FABRICATION on the part of Compaq management. M > > Anyone who believes these cowardly words probably deserves to be lied to"  > > + > >  do you feel requires more specificity?  > B > I meant technically specific, that [he] was upset and felt that  > lies were spread is obvious. > L > I would have been interested in figures for EV8 based on simulations, more	 > detail.   @ Don't be ridiculous, that stuff is all confidential and you knowD it...there's living dangerously, and there's career suicide.  If you@ want a technical argument for EV8, then go read Paul's excellent) analysis at http://www.realworldtech.com/   F Perhaps you misunderstood...I'm not trying to *prove* anything to you.E  It has been suggested that this deal was technically motivated.  I'm E an Alpha architect, and I claim otherwise.  If you (and whoever else) @ would rather believe Compaq's bullshit, then that's your choice.   > [snip]   Brannon : not speaking for Compaq, soon to be not speaking for Intel   ------------------------------  % Date: Sat, 21 Jul 2001 01:03:22 -0700 + From: "Dennis O'Connor" <dmoc@primenet.com> 1 Subject: Re: Alpha:  an invitation to communicate - Message-ID: <9jbd1j$dqj$1@nnrp2.phx.gblx.net>   5 "Brannon Batson" <Brannon_Batson@yahoo.com> wrote ... G >  It has been suggested that this deal was technically motivated.  I'm , > an Alpha architect, and I claim otherwise.  > In all fairness, Brannon, it's entirely possible for competent9 senior engineers to have different opinions as to whether 2 a product can be built within the usual real-world7 constraints (staffing, delivery date, cost, etceteras). . Until the product _has_ been built, of course.  4 Whether this was the case with Alpha, I do not know. --3 Dennis O'Connor                   dmoc@primenet.com . Vanity Web Page http://www.primenet.com/~dmoc/   ------------------------------    Date: 21 Jul 2001 15:11:33 +0200& From: Florian Weps <fweps@pop.agri.ch>1 Subject: Re: Alpha:  an invitation to communicate : Message-ID: <871ynaxw8q.fsf@bubulina.localdomain.localnet>  / JF Mezei <jfmezei.spamnot@videotron.ca> writes:   N > Consider that when Compaq bought Tandem, it kept Tandem as a separate entity > and kept the Tandem name.   D OBPedant: By now there are compaq labels on Tandem hardware as well.   Florian  --  8 Once upon the Python spoke, / Now he lacks interpreters,? Withering in his laurelled fires / All the bitter rock interns, ? From within those jewelled eyes / Tells you only what you know, O Know, but dare not realise.                -- Lawrence Durrell, "Delphi" (1965)    ------------------------------    Date: 21 Jul 2001 15:28:25 +0200& From: Florian Weps <fweps@pop.agri.ch>1 Subject: Re: Alpha:  an invitation to communicate : Message-ID: <87snfqwgw6.fsf@bubulina.localdomain.localnet>  ( peter@abbnm.com (Peter da Silva) writes:  F > A Win32 program has hardcoded registry and file system locations, soI > you can really only run a single instance of an application under it. A E > Win32 program assumes it has write-access to the entire system, and D > breaks if you attempt to secure it. A Win32 program assumes only aH > single user instance is running on the machine, and the security modelF > breaks down if you have some trusted and some untrusted code running > concurrently.  > K > I can imagine Microsoft producing an operating system suited for a server G > environment, where multiple applications not designed to interoperate G > run on a single computer, but it won't be anything like Windows NT as B > we know it. This isn't something Moore's Law can solve for them.  A Oh, but yes. They will design an MVS-like system running multiple E instances of the entire NT Kernel and Win32 subsystem. Given a strong D enough processor, they can run these in multiple instances of an x86 emulator...   A Of course, the underlying meta-kernel will still be a single-user 9 design with lots of GUI code running with all privileges.    Florian    --  8 Once upon the Python spoke, / Now he lacks interpreters,? Withering in his laurelled fires / All the bitter rock interns, ? From within those jewelled eyes / Tells you only what you know, O Know, but dare not realise.                -- Lawrence Durrell, "Delphi" (1965)    ------------------------------  % Date: Sat, 21 Jul 2001 19:36:44 +0010 % From: paddy.o'brien@zzz.tg.nsw.gov.au 0 Subject: Re: Alpha: an invitation to communicate5 Message-ID: <01K67D7U5VDE002Y39@tgmail.tg.nsw.gov.au>    Marty Kuhrt wrote:  / [His experience with Compaq service -- snipped]   O My experience for both hardware and software support is different.  I have had  Q nothing but excellent support and good turn-around time.  One of my machines was  O put on the support contract with the wrong serial number.  They told me that I  R would have a 4-hr support rather than the normal 1 or 2-hr.  Half an hour later I O was rung back and they had traced the error and my support would be within the  
 next hour.  K However, where I think that they have screwed up in the support area is as  Q contractors.  I was on the tendering committee for the hardware contract for our  O corporate machines (IIRC it was the last months of Digital).  Their tender was  L complete (they gave two, one for normal contracting and one for OMC).  They 1 provided CVs for key personnel and their backups.   R When the company was taken over by Compaq, these key people gradually disappeared P and not replaced by any equivalent knowledgeable people.  The turnover of their N contactors is horrendous, and few have a chance to learn our corporate set-up  before they leave.  Q Every change scenario that has happened on our corporate machines has meant that lR nothing works correctly for several days.  Their normal solutions to any problems R are at high cost to our company.  One of the few things our corporate IT has done @ right is apparently to vow that never again will Compaq be used.  N Luckily, I manage our departmental machines and am only beholden on corporate ' (hence Compaq contractors) for network.r   Regards, Paddy   ------------------------------  % Date: Sat, 21 Jul 2001 18:40:22 +0200E From: zessin@decus.deo3 Subject: RE: Best file spec for incremental backup?i* Message-ID: <009FF59D.0FE66841.1@decus.de>   Tom Adams wrote:; > We had been using [*...] as the file spec for incrementalc/ > backups that might be used to recover a disk.S > & > Is [000000...] a better choice? Why?  = I beleive it is a better choice, because this will find files28 in the master file directory (eg. [000000]ABC.DAT) which7 [*...] does not (at least not the last time I checked).a   Oh, by the way:-: If you have a directory like [000000]$ABC.DIR then you get  different results whether you do     $ directory DISK:[*...]" or      $ directory DISK:[000000...]  , That _is_ documented (at least on V7.2-1)...   -- C
 Uwe Zessin   ------------------------------  % Date: Sat, 21 Jul 2001 16:52:42 +0100i+ From: "antonio.carlini" <arcarlini@iee.org>t! Subject: Re: Creating TK50 images ' Message-ID: <3B59A54A.7D9C7E29@iee.org>i   Brian Tillman wrote:J > Sorry, you can't generate a backup saveset _from_ a tape device.  If theK > tape is ANSI-labeled, mount it and COPY it to somewhere on a disk.  If it K > contains a backup saveset already, MOUNT it and COPY the saveset to disk.d0 > Then COPY the saveset to the new TK cartridge.  + Copying will work 99% of the time. It will n' fail if the tape had a bad spot when itw( was originally written since BACKUP will, have noticed and kept writing further copies- of that block until it moved on to good tape..) Similarly if the tape has developed a bad $ spot since being written (say in the% intervening fifteen years or so since % MicroVMS came out!) then copying willu% hit an error whereas a backup restore * *might* be able to work around the problem) using the inbuilt redundancy of savesets.   & I'd still go with TPC to try and image% the tape. If there are bad spots thata" TPC cannot get around then you may% have to manually restore the savesetsH% and repackage them (the commands usedn# to generate the savesets are storedr" withing the saveset and displayed  by BACKUP/LIST).   Antonior   -- o   ---------------h- Antonio Carlini             arcarlini@iee.orgI   ------------------------------   Date: 21 Jul 2001 15:27:01 GMT0 From: fdc@watsun.cc.columbia.edu (Frank da Cruz) Subject: Re: KERMIT.HLBm5 Message-ID: <9jc705$lsj$1@newsmaster.cc.columbia.edu>i  9 In article <3b589e27.45930661@news.jamison1.pa.home.com>,  ADR <adroso@home.com> wrote:E : I have VMS Kermit-32 V3.3.126 (which I use only in emergencies) andsD : I'm missing the KERMIT.HLB file.  Does anybody have this?  Thanks! :d& The source for all Kermit material is:  !   http://www.columbia.edu/kermit/m  I I'm sure you know, and everybody else does, that Kermit-32 is indeed only H for emergencies, since development and support was discontinued about 14H years ago, and that the current and supported Kermit software for VMS is	 C-Kermit:7  -   http://www.columbia.edu/kermit/ckermit.htmlr  D That said, you can find what you are looking for (sort of) among the
 following:  /   ftp://kermit.columbia.edu/kermit/b/vmsmit.hlpd/   ftp://kermit.columbia.edu/kermit/b/vmssys.hlp /   ftp://kermit.columbia.edu/kermit/b/vmsusr.hlpa  F These are VMS Help files.  One or more of these is would be the source for the Help library.d   - Frank,   ------------------------------  # Date: Sat, 21 Jul 2001 08:52:37 GMTt. From: Burnie M <burniem.NOSPAM@ozemail.com.au># Subject: Re: Process adopts Itanium 8 Message-ID: <4mgiltk96hh3jrb6ugicc7tro3dkeh7erj@4ax.com>   Neil what are you smoking ?n   Multinet maybe but TCPware ?D We run it (TCPware) but the upside is it appears to be morphing into MNtf   Burnie M    0 On Fri, 20 Jul 2001 10:45:16 -0400, "Neil Rieck" <n.rieck@sympatico.ca> wrote:-  : >I love their stack (TCPware) so this is good news for me. >  >Neil Rieck< >Kitchener/Waterloo/Cambridge, >Ontario, Canada.s" >http://www3.sympatico.ca/n.rieck/ >b; >"Bob Koehler" <koehler@encompasserve.org> wrote in messagea. >news:iqU2SUUdSKOf@eisner.encompasserve.org...
 >> In articleOB ><OF7462A3CB.459E5E7C-ON03256A8F.00419D09@ep-bc.petrobras.com.br>,, >fabio_compaq@ep-bc.petrobras.com.br writes: >> > Process adopts ItaniumV >> >H >> > http://www.process.com/about/process-compaq-intelrelease071901.html >> > >>G >> "Compaq's AlphaServer Intel processor"?  I hope Compaq's not callingo
 >> them that.M >>I >> ---------------------------------------------------------------------- B >> Bob Koehler                     | Computer Sciences Corporation@ >> NASA GSFC Flight Software       | Federal Sector, Civil GroupH >>                                 | please remove ".aspm" when replying >d   ------------------------------  % Date: Sat, 21 Jul 2001 13:43:03 -0400i+ From: "Main, Kerry" <Kerry.Main@compaq.com> M Subject: RE: Security-Enhancing Products for Compaq OpenVMS from PointSecu	re5R Message-ID: <BE56C50EA024184DAF48F0B9A47F5CF48DBFB8@kaoexc01.americas.cpqcorp.net>   Fyi -o   External WEB site pointers:tD http://www.openvms.compaq.com/OPENVMS/compaq-pointsecure_letter.html3 http://www.openvms.compaq.com/openvms/Security.html- http://www.pointsecure.com/    Regards,  
 Kerry Main Senior Consultant  Compaq Canada Inc. Professional Services: Voice: 613-592-4660e Fax  :  819-772-7036 Email: Kerry.Main@Compaq.com     -----Original Message-----2 From: deltauh@yahoo.com [mailto:deltauh@yahoo.com] Sent: July 20, 2001 12:03 PM To: Info-VAX@Mvb.Saic.ComgH Subject: Security-Enhancing Products for Compaq OpenVMS from PointSecure     Has anybody else seen this?r   -----Original Message-----> From: OpenVMS-Info@compaq.com [mailto:OpenVMS-Info@compaq.com]' Sent: Wednesday, July 18, 2001 11:52 AMs To: deltauh@yahoo.comP Cc: OpenVMS-Info@compaq.comeH Subject: Security-Enhancing Products for Compaq OpenVMS from PointSecure     Dear Valued OpenVMS Customer,d  B PointSecure and Compaq are pleased to announce the availability ofI security-enhancing products for Compaq OpenVMS that will provide you with K high quality security and compliance applications available for the OpenVMS @ platform.  They are System Detective AO and System Detective IS.  I Compaq has committed to promoting Independent Software Vendors (ISVs) whoeC provide valuable business solutions for OpenVMS AlphaServer systems K customers. Through such efforts as the Java application initiative, OpenVMSeL Galaxy software, and OpenVMS' leadership cluster technology, Compaq providesK a strong foundation on which you can build and depend upon your e-business.p  D Additionally, Compaq is enhancing OpenVMS to comply with the DefenseA Information Infrastructure Common Operating Environment (DII COE).C specifications. DII COE on OpenVMS enables Compaq to participate in-G government bids that require a long-term commitment (up to 20 years) tosD support OpenVMS. Moreover, OpenVMS support for DII COE enhances UNIXL application portability to OpenVMS, as well as extends these benefits beyond the government sector.  J For customers who require additional security beyond the level inherent inL OpenVMS, PointSecure's security products have been saving companies time andH money for over 10 years. Through both automated and interactive securityG functions, PointSecure strives to bring administrators peace of mind byiI enabling them to set pre-defined rules corresponding to security policieseI and provide proactive security responses. These factors, coupled with the D ability to monitor interactive sessions, make it possible to preventC malicious activity with as little as one keystroke. The goal of thefI PointSecure products is to give system administrators more time utilizingaD the system and less time worrying about security issues.  As an ISV,J PointSecure understands the commitment Compaq has made to OpenVMS and willL continue to provide and enhance the functionality of PointSecure's products.  G Compaq has positively reviewed the PointSecure security products SystemtH Detective AO and System Detective IS. System Detective AO, a rules-basedL automated tool, is designed to enforce user accountability while controllingJ access to OpenVMS systems. System Detective IS interactively monitors userI sessions and allows system administrators the ability to monitor, log andu% enforce predefined security policies.w  J PointSecure and Compaq will continue to address the security needs of yourD business with OpenVMS-based solutions.  If you would like additionalH information regarding these products or need assistance with security orA compliance issues, please don't hesitate to call your PointSecureiL representative or visit http://www.pointsecure.com.  For more information on0 Compaq OpenVMS AlphaServer systems, please visit http://www.compaq.com/openvms.   Rich Marcello						Rod Endoo Vice President						Presidentd0 Compaq Computer Corporation				PointSecure, Inc. richard.marcello@compaq.comd rod.endo@pointsecure.com   ------------------------------  # Date: Sat, 21 Jul 2001 13:22:38 GMTf= From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)uL Subject: Re: Security-Enhancing Products for Compaq OpenVMS from PointSecure0 Message-ID: <009FF54F.25DC3E0E@SendSpamHere.ORG>  ` In article <e6e1751e.0107200803.4223be42@posting.google.com>, deltauh@yahoo.com (daniel) writes: >Has anybody else seen this? >  >-----Original Message-----f? >From: OpenVMS-Info@compaq.com [mailto:OpenVMS-Info@compaq.com]l( >Sent: Wednesday, July 18, 2001 11:52 AM >To: deltauh@yahoo.com >Cc: OpenVMS-Info@compaq.comI >Subject: Security-Enhancing Products for Compaq OpenVMS from PointSecureh >  >a >Dear Valued OpenVMS Customer, >iC >PointSecure and Compaq are pleased to announce the availability offJ >security-enhancing products for Compaq OpenVMS that will provide you withL >high quality security and compliance applications available for the OpenVMSA >platform.  They are System Detective AO and System Detective IS.1 {...snip...}  G Yes and I fired it back at the two email addresses listed at the bottom7F of the message I'd received.  It was sent authored by some PeeCee pro-H gram which obviously does line wrapping.  Why can't people use their re-H turn keys?  It was one long run-on mess which was truncated at 255 char- acters and unreadable.  G Seeing as how I am a VMS customer and use VMS, wouldn't a message aboutlG security and VMS be better targetted at VMS users/managers/etc. than ati PeeCee weenies?n --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COMi             J   "And of course, I'm a genius, so people are naturally drawn to my fiery I   intellect.  Their admiration overwhelms their envy!" -- Calvin & Hobbesw   ------------------------------  # Date: Sat, 21 Jul 2001 13:26:32 GMTa= From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-) - Subject: Re: Selling VMS to another company ?e0 Message-ID: <009FF54F.B1B26B23@SendSpamHere.ORG>  i In article <2fd964e0.0107201006.42312aeb@posting.google.com>, magalettac@hotmail.com (magalettac) writes:tF >Compaq seems to have a luke warm story at best with its intentions inA >regards to VMS, Would it be possible to sell the worlds greatestoG >operating system to a company that would be able to do the right thing-: >with it ? Does such a company exist. A company that couldF >market,update, and build momentum for this operating system. With theF >hardware platform becoming more and more of a non issue in the coming* >years,could this actually have a chance ?  L The death of Alpha makes the sale of VMS to any other party quite a bit lessL attractive.  Would you purchase a car knowing that in three years time gaso-L line would become obsolete?  Oh, sure you might find that you can "redesign"L the car after investing a whole slew of money into it but the assurance that$ it will run and run well is dubious.   --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COMs             J   "And of course, I'm a genius, so people are naturally drawn to my fiery I   intellect.  Their admiration overwhelms their envy!" -- Calvin & Hobbes-   ------------------------------  # Date: Sat, 21 Jul 2001 17:45:17 GMTw& From: "john nixon" <jnixon@cfl.rr.com>- Subject: Re: Selling VMS to another company ?n= Message-ID: <Ncj67.40462$uo3.5984287@typhoon.tampabay.rr.com>p  L It seems to me that what would make more sense would be for Compaq to createK a new spin-off company that would include VMS and all its layered products.nL That way the Compaq shareholders (of whom I am proud to be one) would retainL equity, while allowing the VMS Company to compete unrestricted with both theF old Compaq, and with M$shaft (and SUNW, IBM etc...).  There are also aH multitude of tax advantages for doing it that way, (if the IRS approves)K because instead of the company  receiving taxable cash,  shareholders would I receive one share of VMS stock for every X number of CPQ shares they own. C After the initial spin-off, VMS stock would trade on its own merit.f  G The new VMS company would have it's own management heirarchy and profit)G centers.  It would hit the ground with a loyal customer base, and (verytJ importantly) it would have its own marketing group (for which I would voteH to have Sue head up;  (after all, she said I look like Robert Redford)).    6 "magalettac" <magalettac@hotmail.com> wrote in message7 news:2fd964e0.0107201006.42312aeb@posting.google.com...eG > Compaq seems to have a luke warm story at best with its intentions inaB > regards to VMS, Would it be possible to sell the worlds greatestH > operating system to a company that would be able to do the right thing; > with it ? Does such a company exist. A company that could G > market,update, and build momentum for this operating system. With the G > hardware platform becoming more and more of a non issue in the comingh+ > years,could this actually have a chance ?m >n >g > Any thoughts,n	 > Carminee >r   ------------------------------  # Date: Sat, 21 Jul 2001 09:16:02 GMTc. From: Burnie M <burniem.NOSPAM@ozemail.com.au>> Subject: Re: SMS on VMS [was RE: Full port of VMS to Itanium.]8 Message-ID: <6qhilt4ljebmq5rjniqlcoqt04m1qs6f0b@4ax.com>   Yes, Semas SMSCs run on VMS E (The HP SMSC runs on 2 x dual ES40 with 4GB and 112 disks as the backr# end plus 2 x DS10 on the front end)b+ Many companies including Vodafone use them.l  C VMS is also used for AUC, SCCP Relay, GMLR and HLR in some Telecoms < companies. These are real 'realtime' systems and HLRs can beC considered at the heart of a GSM mobile phone network just a trivalm1 point lower in priority than the MSCs themselves.p  D Sorry for the TLAs but yes VMS is at the core of Telecoms especially GSM mobile networks.   Burnie M    @ On Wed, 18 Jul 2001 23:48:03 +0200, "Hans Vlems" <hvlems@iae.nl> wrote:  J >I can only comment on the Ericson gear. It used to come with a VMS systemF >that monitored the PABX. Since BC08 Ericson moved to the NT platform.L >Though that did not influence the stability of the PABX one bit, the NT box >islJ >a lot more difficult (if not impossible) to build your own interfaces on. >  >Hans Vlems  > < >William Chesters <williamc_sp@paneris.org> wrote in message- >news:m2ofqit8wr.fsf@beertje.william.bogus...yA >> > From what I understand ... and I am sure I will be correctednD >> > if I am wrong ... is that Short Message Service (SMS) (Cellular@ >> > Phone messaging) runs on VMS and VMS only.  That was passedE >> > on to me in May 2000 and may be a bit of hype.  Apparently, very < >> > popular in Europe and driven one segment of VMS growth. >>A >> VMS was (is?) widely used in telecoms, and especially GSM, theaG >> standard behind all modern European phones + many others.  Not least.A >> because Ericsson switches all shipp(ed?) with a VAX in overallc1 >> control, and they still make most of the gear.e >>H >> So to SMS you could probably add every other development in GSM.  ButK >> it has been a long time since I worked in that world, so I may be wrong.n1 >> That was the last time I even saw VMS, too .... >n   ------------------------------  % Date: Sat, 21 Jul 2001 05:30:24 -0400t- From: JF Mezei <jfmezei.spamnot@videotron.ca>,> Subject: Re: SMS on VMS [was RE: Full port of VMS to Itanium.], Message-ID: <3B594BB0.76EA27F7@videotron.ca>   Burnie M wrote:yF > Sorry for the TLAs but yes VMS is at the core of Telecoms especially > GSM mobile networks.  L You make it sound like all GSM networks make extensive use of GSM. Funny howN the local GSM network here in canada seems to only advertise for window weenie and Sun Solaris jobs.c  N I keep hearing how lotteries run on VMS, yet the provicial lottery is a tandemJ shop. I keep hearing how telecom runs on VMS, yet I never see adds for VMS( folks from the local telecom companies.   K And if you look at the Compaq web site, you'll find plenty of telecom stuff 
 for Tru64.   ------------------------------  % Date: Sat, 21 Jul 2001 16:45:41 +0930 / From: Mark Daniel <Mark.Daniel@wasd.vsm.com.au>." Subject: V7.3 XFCACHE-W-DATALOSS ?. Message-ID: <3B592C1D.563E021@wasd.vsm.com.au>  D Recently (just) installed V7.3 on DS20 (1024MB) has started spitting OPA0 messages reporting0  F   %XFCCACHE-W-DATALOSS, read I/O completetion with <less bytes that it thinks it should>-  H We have been COPYing a *lot* of small files around (documentation CDs to hard-disk).a  G This is not in the HELP message database (yet).  Anyone else seen this?t   As always, TIA.e --   Illegitimis nil carborundum.   ------------------------------  % Date: Sat, 21 Jul 2001 16:43:28 +0100C+ From: "antonio.carlini" <arcarlini@iee.org>o% Subject: Re: VAX 8250 Console Commandl' Message-ID: <3B59A320.6FF97693@iee.org>i   Christopher Smith wrote: >  > > -----Original Message-----4 > > From: antonio.carlini [mailto:arcarlini@iee.org] > ( > > The VAX 82x0/83x0 can most certainly+ > > NI boot - however I do not believe that( > L > I read that to be: "The VAX 82x0/83x0 can most certainly NT boot..." which@ > not only sounds very german, but nearly impossible as well! :)  1 If you drop the "VAX" bit and imagine AlphaServern1 in there instead, it probably can boot WIndows NTd+ (although whether that was ever a supporteda! config mercifully slips my mind!)y   Antonioa   -- r   ---------------H- Antonio Carlini             arcarlini@iee.orgn   ------------------------------  # Date: Sat, 21 Jul 2001 13:08:46 GMTC* From: "David Cressey" <david@dcressey.com>  Subject: Re: VMS Trivia Question2 Message-ID: <y9f67.24$YQ.678@petpeeve.ziplink.net>  = You've already got the answers, so it's too late to  compete.a  I I learned something new in the thread.  I knew that VMS got the date zeros point from Smithsonian, but myG understanding of where they got the zero date was apparently incorrect.c  ? One sidelight about the "insert queue" instructions on the VAX:e  F When the VAX first made its debut,  my expertise was with TOPS-10, theH operating system for the DECsystem-10.  TOPS-10 maintained doubly linkedK lists to keep track of the job queues  (process queues, if you like).  Each-I link in the chain consisted of two job numbers, stored in halfwords,  ando) used as indexes into the job queue array.u  L With the PDP-10 instructions set, it took six instructions to put a job intoB a new queue and to close up the old queue.  Before doing those sixK instructions,  they had to turn off interrupts,  and turn them on after theeD six instructions.  Otherwise interrupt level code might trip over an% inconsistent state of the job queues.s  I This worked, but it was highly unaesthetic.  My understanding is that theoE VAX "insert queue" instructions,  or at least some of their variants,-K enabled VMS to maintain its queues without turning off the interrupts.  Bute9 I never learned VMS internals,  so I don't actually know.-  / Anybody out there who knows the answer to this?    -- Regards,     David Cresseyt     www.dcressey.com* "Shawn" <sfm1115@bjc.org> wrote in message* news:3b5859db.12188986@news.starnet.net...B > We just received software from RAXCO and there was a trivia typeF > poster in it.  On it it asks what happened on 17-Nov-1858, any ideas2 > we are lost here.  Is that the Star Date thingy. >i > Also what does INSQTI mean?: >w > Thanks >c >.   ------------------------------  % Date: Sat, 21 Jul 2001 18:30:16 +0100n5 From: "Stephen V. Kearney" <ste@the-neuk.demon.co.uk>i# Subject: VS3100 driving me mental!!FA Message-ID: <995736900.22291.0.nnrp-08.c1edbfcc@news.demon.co.uk>o  H I know there are millions of posts on Google and I'm sure I've read them all, but....  G VaxStation 3100, early on, with 16megs and two hdd, DKA200 system and ap seagate hawk for data.  J Basically, it won't autoboot. It will reboot from a shutdown with a reboot% option, but will not from a power-on.B  6 The system disk (dka300) is a 'proper' DEC badged one.  8 This is test 50, test 0 and a sho dev, can anyone help!!  # There is no ethernet connected yet.    KA42-A  V1.3  < F...E...D...C...B...A...9...8...7...6...5...4...3_..2_..1?..      ?  E  0040  0000.0005  ?  C  0080  0000.4001  ?  4  00D4  100F.1F63 ??  1  00C0  0000.7004   >>> sho boot DKA300 >>> sho halt 1a >>> sho bflg 00000000 >>>    Result of test 50A   KA42-A  V1.3 ID 08-00-2B-15-29-55      MONO     0000.0001   ? CLK      0000.0005s    NVR      0000.0001w  ? DZ       0000.4001P;       00000001 00000001 00000001 00004001 00000000 00000000a    MEM      0010.0001h       01000000    MM       0000.0001e    FP       0000.0001e    IT       0000.0001q    SCSI-A   0808.0001  V1.58D       FFFFFF05 FFFFFF05 FFFFFF05 00000001 FFFFFF05 FFFFFF05 FFFFFF03 FFFFFF05    SCSI-B   0404.0001  V1.58D       FFFFFF05 FFFFFF05 00000001 FFFFFF05 FFFFFF05 FFFFFF05 FFFFFF03 FFFFFF05    SYS      0000.0001S  ? SPGFX    100F.1F63  V1.3n;       00000060 00000068 00000068 00000000 00000000 00000000  ?? NI       0000.7004r >>>-   Test 0   KA42-A  V1.3        01     CUo    <    F 00B0  MONO     0000.0001       3 0005        0 00:04:49<    C 0080  DZ       0300.0001       3             0 00:04:50<    B 0010  MEM      003C.0001       2 0007        0 00:04:56<    7 80A0  SCSI-A   6000.0001       8 0002        0 00:04:56                     3200.0001e<    6 80A1  SCSI-B   6000.0001       8 0002        0 00:04:56                     2200.0001l<    4 00D4  SPGFX    3000.0001       2             0 00:04:38<    1 00C0  NI       0000.0001       3             0 00:04:56       Sho dev shows..m   >>> sho dev D  VMS/VMB  ULTRIX    ADDR    DEVTYP  NUMBYTES  RM/FX  WP  DEVNAM  REVD  -------  ------  --------  ------  --------  -----  --  ------  ---#  ESA0     SE0     08-00-2B-15-29-55t  D  DKA300   RZ3     A/3/0/00  DISK     1.05 GB   FX        RZ26L  440C!  ...HostID....    A/6       INITR,  D  DKB200   RZ10    B/2/0/00  DISK     2.10 GB   FX        RZ28M  0744!  ...HostID....    B/6       INITRl               00     0 00:05:32o     ?06 HLT INST     PC = 00005A0F  >>>s   That last bit worries me!i   >>>b works perfectly.f   HELP!!   Steven   ------------------------------    Date: 21 Jul 2001 00:41:19 -07005 From: Hiroyuki_Tanaka4@excite.co.jp (Hiroyuki Tanaka) 5 Subject: [Q] CXX, global variables, Shareable library = Message-ID: <68cfa44d.0107202341.47f3508f@posting.google.com>e   Dear Reader,  @ I am interested in making a shareable image using CXX on OVMS.  7 I can acheive what I wish to do using the C compiler.  eC But I am interested to know what to do to acheive the same with thev
 CXX compiler.r   In C ---cglob.c---- globalvalue variable1 = 1; globalvalue variable2 = 2; void procedure ( ) {a }o ---cglob.c---- $cc cglob.cs  / Then in the object using $anal/object cglob.objc- 	9)  Global Symbol Specification (EGSD$C_SYM)  		data type: DSC$K_DTYPE_Z (0) 		symbol flags:t 			(0)  EGSY$V_WEAK      0 			(1)  EGSY$V_DEF       1 			(2)  EGSY$V_UNI       0 			(3)  EGSY$V_REL       0 			(4)  EGSY$V_COMM      0 			(5)  EGSY$V_VECEP     0 			(6)  EGSY$V_NORM      0
 		psect: 0 		value: %X'00000000 00000001' 		symbol: "VARIABLE1"   . 	10)  Global Symbol Specification (EGSD$C_SYM) 		data type: DSC$K_DTYPE_Z (0) 		symbol flags:d 			(0)  EGSY$V_WEAK      0 			(1)  EGSY$V_DEF       1 			(2)  EGSY$V_UNI       0 			(3)  EGSY$V_REL       0 			(4)  EGSY$V_COMM      0 			(5)  EGSY$V_VECEP     0 			(6)  EGSY$V_NORM      0
 		psect: 0 		value: %X'00000000 00000002' 		symbol: "VARIABLE2"i  . 	11)  Global Symbol Specification (EGSD$C_SYM) 		data type: DSC$K_DTYPE_Z (0) 		symbol flags:  			(0)  EGSY$V_WEAK      0 			(1)  EGSY$V_DEF       1 			(2)  EGSY$V_UNI       0 			(3)  EGSY$V_REL       1 			(4)  EGSY$V_COMM      0 			(5)  EGSY$V_VECEP     0 			(6)  EGSY$V_NORM      1
 		psect: 3 		value: 0 (%X'00000000')f 		code address psect: 1l  		code address: 0 (%X'00000000') 		symbol: "PROCEDURE"   / Then I can link to make a shareable image with e $link/share cglob+sys$input/opt $ symbol_vector=(procedure=procedure,- variable1=data,- variable2=data) 	 (ctrl-z).O  * I get what I want. With the values I want.  ; However when I try in CXX I cannot acheive the same resultse   ---cxxglob.cxx---- int variable1 = 1; int variable2 = 2;0 extern "C" { void procedure ( ); }   //Stop CXX  void procedure ( ) {  }- ---cxxglob.cxx----  - But in the anal/obje the data is different.  r, 	2)  Program Section Definition (EGSD$C_PSC)> 		alignment: 16-byte boundary                      <-- psect 1 		attribute flags: 			(0)  EGPS$V_PIC       0 			(1)  EGPS$V_LIB       0 			(2)  EGPS$V_OVR       1 			(3)  EGPS$V_REL       1 			(4)  EGPS$V_GBL       1 			(5)  EGPS$V_SHR       0 			(6)  EGPS$V_EXE       0 			(7)  EGPS$V_RD        1 			(8)  EGPS$V_WRT       1 			(9)  EGPS$V_VEC       0 			(10) EGPS$V_NOMOD     0 			(11) EGPS$V_COM       0 		allocation: 4 (%X'00000004') 		symbol: "VARIABLE1"e  , 	3)  Program Section Definition (EGSD$C_PSC)> 		alignment: 16-byte boundary                      <-- psect 2 		attribute flags: 			(0)  EGPS$V_PIC       0 			(1)  EGPS$V_LIB       0 			(2)  EGPS$V_OVR       1 			(3)  EGPS$V_REL       1 			(4)  EGPS$V_GBL       1 			(5)  EGPS$V_SHR       0 			(6)  EGPS$V_EXE       0 			(7)  EGPS$V_RD        1 			(8)  EGPS$V_WRT       1 			(9)  EGPS$V_VEC       0 			(10) EGPS$V_NOMOD     0 			(11) EGPS$V_COM       0 		allocation: 4 (%X'00000004') 		symbol: "VARIABLE2". ....- 	7)  Global Symbol Specification (EGSD$C_SYM)h 		data type: DSC$K_DTYPE_Z (0) 		symbol flags:u 			(0)  EGSY$V_WEAK      0 			(1)  EGSY$V_DEF       1 			(2)  EGSY$V_UNI       0 			(3)  EGSY$V_REL       1 			(4)  EGSY$V_COMM      0 			(5)  EGSY$V_VECEP     0 			(6)  EGSY$V_NORM      0
 		psect: 1 		value: 0 (%X'00000000')r 		symbol: "VARIABLE1"i  - 	8)  Global Symbol Specification (EGSD$C_SYM)f 		data type: DSC$K_DTYPE_Z (0) 		symbol flags:) 			(0)  EGSY$V_WEAK      0 			(1)  EGSY$V_DEF       1 			(2)  EGSY$V_UNI       0 			(3)  EGSY$V_REL       1 			(4)  EGSY$V_COMM      0 			(5)  EGSY$V_VECEP     0 			(6)  EGSY$V_NORM      0
 		psect: 2 		value: 0 (%X'00000000')6 		symbol: "VARIABLE2"S  - 	9)  Global Symbol Specification (EGSD$C_SYM)  		data type: DSC$K_DTYPE_Z (0) 		symbol flags:e 			(0)  EGSY$V_WEAK      0 			(1)  EGSY$V_DEF       1 			(2)  EGSY$V_UNI       0 			(3)  EGSY$V_REL       1 			(4)  EGSY$V_COMM      0 			(5)  EGSY$V_VECEP     0 			(6)  EGSY$V_NORM      1
 		psect: 4 		value: 0 (%X'00000000')r 		code address psect: 3s  		code address: 0 (%X'00000000') 		symbol: "PROCEDURE"a  ? I can see that the anal/object is different.  I do not claim to E understand any of this but it appears different and has no values. SooC I cannot see how the values can be linked into my global variables.n  A I have looked in the CXX manual.  The example shows mixed CXX andl macro.  4 Do I need to use macro to acheive the same with CXX?  B Could anyone give me a pointer to what I should be doing in CXX to  acheive the same and the C code?  0 Are there any simple examples available for CXX?  F If this is not the correct group for this question could you advise of the correct group.  ! Thanks once again for you help.  u   Tanaka   ------------------------------   End of INFO-VAX 2001.402 ************************