0 INFO-VAX	Tue, 13 Jan 2004	Volume 2004 : Issue 24      Contents: Re: 500.000 AMD64's shipped... Re: 500.000 AMD64's shipped... Re: 500.000 AMD64's shipped...- Re: Alpha macro (64) and the OTS$... routines ; Re: Brazil == was: Experienced OpenVMS Admin/Guru available  Re: ds10l blowout , Re: Experienced OpenVMS Admin/Guru availableP Re: Hewlett-Packard plans to EOL the HP AlphaServer Tru64. Find out how  Sun canP Re: Hewlett-Packard plans to EOL the HP AlphaServer Tru64. Find out how  Sun canP Re: Hewlett-Packard plans to EOL the HP AlphaServer Tru64. Find out how Sun can  Re: HP FUDBusting % Re: I just scored an AlphaServer 800! / Modify the logical SYS$STARTUP, why or why not? 3 Re: Modify the logical SYS$STARTUP, why or why not? 3 Re: Non-WS Process Quotas not in Performance Manual 3 Re: Non-WS Process Quotas not in Performance Manual 3 Re: Non-WS Process Quotas not in Performance Manual 3 Re: Non-WS Process Quotas not in Performance Manual 3 Re: Non-WS Process Quotas not in Performance Manual P Re: Oracle Rdb on GS1280 with 7.3-2 exceeds 1 million transactions per minute usP Re: Oracle Rdb on GS1280 with 7.3-2 exceeds 1 million transactions per minute us/ Personal Workstation 500a/au hardware questions - Problem using bind() function in 'C' program.  Re: Problems with 7.3 and 164LX + Re: Silly Users with Password as "Password"  Size restriction of LD disks? ! Re: Size restriction of LD disks? ! Re: Size restriction of LD disks? ! Re: Size restriction of LD disks? , Re: Slightly OT: Code Red on the rise again?, Re: Slightly OT: Code Red on the rise again?@ Re: The Register: OpenVMS among most-secure of operating systems@ Re: The Register: OpenVMS among most-secure of operating systems Re: VAX architecture and Charon  Re: VAX architecture and Charon  Re: VAX architecture and Charon  Re: VAXstation question  Re: Vaxstation some question...  Re: Vaxstation some question...  Re: Vaxstation some question... ! Re: VMS runs well on HP Superdome D Re: Well Andrew, "3" count them "3" security patches for VMS in five  F ----------------------------------------------------------------------  % Date: Mon, 12 Jan 2004 16:43:23 -0500 * From: JF Mezei <jfmezei.spamnot@istop.com>' Subject: Re: 500.000 AMD64's shipped... ) Message-ID: <400314FA.F02A201D@istop.com>    mist dragon wrote:+ > http://www.theinquirer.net/?article=13566 H > Opteron has also outsaled the whole history if itanium processors last > year..  L So they claim to have shipped half a million chips. But shipped to whom ? IfL they were shipped from AMD Taiwan to AMD's wharehouse in the USA, it doesn'tR automatically mean that there are 500,000  64 bit 8086s running at customer sites.  K The fab was probably given some order to make 500k chips, so it did and now ! brags about its accomplishements.    ------------------------------  # Date: Mon, 12 Jan 2004 23:55:34 GMT 6 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)' Subject: Re: 500.000 AMD64's shipped... 2 Message-ID: <WtGMb.99346$Tz1.18020@news.chello.at>  V In article <400314FA.F02A201D@istop.com>, JF Mezei <jfmezei.spamnot@istop.com> writes: >mist dragon wrote: , >> http://www.theinquirer.net/?article=13566I >> Opteron has also outsaled the whole history if itanium processors last 	 >> year..  > J >So they claim to have shipped half a million chips. But shipped to whom ?  K I saw recently a notebook (!) with an AMD64 in a window of a photo/computer J shop here in vienna. What a surprise as the shop is destined for the crowd and not for computer freaks...   --   Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------    Date: 12 Jan 2004 21:33:38 -0800. From: mistdragon@zdnetonebox.com (mist dragon)' Subject: Re: 500.000 AMD64's shipped... = Message-ID: <7500353b.0401122133.3e66f991@posting.google.com>   L > So they claim to have shipped half a million chips. But shipped to whom ?   E Take a walk on local computer shops and malls and look at labels from = ibm, hp etc. And then take the same walk looking for itanium.   B I could ask the same question - where did those 10k itaniums go ?    M    ------------------------------    Date: 12 Jan 2004 19:16:31 -0800( From: don.braffitt@hp.com (Don Braffitt)6 Subject: Re: Alpha macro (64) and the OTS$... routines= Message-ID: <e5c311b8.0401121916.436c4506@posting.google.com>   n denny.rich@swagelok.com (Denny Rich) wrote in message news:<d28306e.0401120834.3a3be0b8@posting.google.com>...F > As we understand it, check=decimal will cause a run-time error if it3 > encounters spaces in what should be numeric data.    Correct.  E > Could there be a list of switches that had to be introduced, as was 6 > "/convert=leading", to ease the conversion to Alpha?  ? Yes. We've detailed this information in two places. In the User > Manual, we added an appendix with details on porting to Alpha:  M http://h71000.www7.hp.com/doc/73final/6297/6297_profile_053.html#cob_port_app   E In the Release Notes on Alpha, we have a troubleshooting section with D suggestions of compilation options to try based on the experience ofD many users who have ported COBOL applications to Alpha. This sectionA of the release notes is updated each version with the most recent  update being for V2.8.  A For example, use of /MATH on Alpha as refined up through V2.8 has D helped many customers striving either for compatibility with COBOL'sD arithmetic precision on VAX (/MATH=CIT3) or for higher precision now: available on Alpha with 32 digit intermediate computations
 (/MATH=CIT4).    - Don    ------------------------------  # Date: Mon, 12 Jan 2004 20:20:35 GMT 3 From: hammond@not@peek.ssr.hp.com (Charlie Hammond) D Subject: Re: Brazil == was: Experienced OpenVMS Admin/Guru available3 Message-ID: <nkDMb.12114$Zw.11679@news.cpqcorp.net>   > In article <f30679fb.0401121004.44399cdf@posting.google.com>, 0 fabiopenvms@yahoo.com.br (Fabio Cardoso) writes:n >hammond@not@peek.ssr.hp.com (Charlie Hammond) wrote in message news:<cAyMb.12096$J5.5680@news.cpqcorp.net>... ..F >> Brazil has a long standing tradition of enforcing the same entranceN >> requirements for USA visitors to Brazil that the USA requires of Brazilian  >> visitors to the USA.  > 3 >Yes I know this, but the resume this situation is:  >  >USA: Do you first ?   >BR: No, do you first ?  >USA: Do you first ?   >BR: No, do you first ?  ..  A Actually, I think the USA generally does first, for whatever real A or percived reasons.  If/when the USA stops doing, I suspect that  Brazil will follow.   F The current situation is yet another part of Homeland "Security" which$ does NOT make me feel safer.  {sigh}   --  J       Charlie Hammond -- Hewlett-Packard Company -- Ft Lauderdale  FL  USAF           (hammond@not@peek.ssr.hp.com -- remove "@not" when replying)J       All opinions expressed are my own and not necessarily my employer's.   ------------------------------  % Date: Mon, 12 Jan 2004 20:55:14 -0600 / From: Clay M. Denton <denton@orison.dsserv.com>  Subject: Re: ds10l blowout8 Message-ID: <fai600hgj2nub0udflaikb66k0m7rl3kja@4ax.com>  X Go buy a cheap laptop IDE CD-ROM drive off of eBay and mount it in the slot in the frontW of the DS10L.  run and IDE cable internally and connect the power.  Depending on the CD Y drive - you may have to buy/build an adapter widget to plug in the normal connectors, but * the parts are also out there easy to find.   Clay    U On Sun, 11 Jan 2004 22:41:46 -0500, "Jeff Morgan" <vmswiz@geonospamcities.com> wrote:    >Easy... >  > - Remove the case M > - put the system next to the refrigerator and open the door to keep the EV6  >processor cool ; > - install a bigger IDE hard drive (whatever is supported)  > - plug in a cheap IDE cdrom 8 > - boot the VMS OS installation disk from the IDE cdrom > - install VMS  > - reboot with VMS ? > - then mount and copy each of the 15 or so CDroms to separate % >subdirectories on the IDE hard drive  > - Shut down system > - remove the CDrom reader  > - put the case back on > - close the refrigerator door  >  >Repeat when necessary...  >  >: - D > L >Seriously, if you are going to run with the case open for several hours, itL >might be a good idea to keep an eye on the heat. I don't have one yet, so IJ >can't advise you on how hot this thing will get with the cover off. BeingM >very low profile, there's probably some serious fan ducting going on inside.  > J >Maybe drilling a hole in the case for the IDE and power connector for the >CDrom might not be too bad. > < >(I'm sure all the HP/CompaQ/DEC engineers just cringed! :-) > L >It's a shame there are no USB ports available and a VMS supported USB CDromM >reader. That would have reduced the real estate requirements. A USB external  >CD would only run about $50.  > % >                                Jeff  >  > L >"David J. Dachtera" <djesys.nospam@NeOaSrPtAhMlNiOnWk.net> wrote in message1 >news:400197BA.9D38DB18@NeOaSrPtAhMlNiOnWk.net...  >> Jeff Morgan wrote:  >> > [snip] E >> > Heck, buy a 200GB ide drive for $125 and keep all of the Layered 
 >Products,> >> > OS and freeware disks online ALL the time. (just kidding) >>I >> Well, that'd be cool, except - how does one get the software onto that  >> disk in the first place?  >> >> --  >> David J. Dachtera >> dba DJE Systems >> http://www.djesys.com/  >>+ >> Unofficial Affordable OpenVMS Home Page: " >> http://www.djesys.com/vms/soho/ >    ------------------------------  # Date: Tue, 13 Jan 2004 03:53:05 GMT + From: LESLIE@JRLVAX.HOUSTON.RR.COM (leslie) 5 Subject: Re: Experienced OpenVMS Admin/Guru available 2 Message-ID: <BYJMb.9289$RV5.7668@fe2.texas.rr.com>  < Bob Koehler (koehler@eisner.nospam.encompasserve.org) wrote:C : In article <ef%Lb.2764$i4.241@newsread1.news.atl.earthlink.net>,  1 : "Gary Cooper" <gwcooper@mindspring.com> writes:  : > J : > Actually, may be moot point soon as we have secret plan to make the USD : > our 11th province .. Only real problem as I recall was trying toE : > convince Texans they need to become bilingual and learn French ..  : H :    You'ld have better luck trying to convince the Quebec'ers they need, :    to become trilingual and learn Texican. :   B Some radical Chicanos want to reclaim Texas, as well as everything from Texas to the Pacifc Ocean:   H    http://www.thenewamerican.com/tna/2002/05-06-2002/vo18no09_aztlan.htm;    The New American - Aztlan and Amalgamation - May 6, 2002    --Jerry Leslie9   Note: leslie@jrlvax.houston.rr.com is invalid for email    ------------------------------    Date: 12 Jan 2004 13:18:19 -08001 From: keithparris_NOSPAM@yahoo.com (Keith Parris) Y Subject: Re: Hewlett-Packard plans to EOL the HP AlphaServer Tru64. Find out how  Sun can = Message-ID: <cf15391e.0401121318.7a914524@posting.google.com>   [ JF Mezei <jfmezei.spamnot@istop.com> wrote in message news:<3FFF0A8E.EDD7BAF6@istop.com>... O > I was under the impresison that Tru64 was going to be developed "for a little M > while", but after that would go into maintenance mode. Does anyone have the ( > timeframe this is expected to happen ?  - According to http://www.hp.com/go/tru64unix : 0 "HP is fully committed to the Tru64 UNIX roadmapB (http://h30097.www3.hp.com/unix/downloads/tru64_unix_roadmap.ppt),E delivering updates until at least 2006 with standard support at least  until 2011.    ------------------------------    Date: 12 Jan 2004 17:00:40 -08001 From: keithparris_NOSPAM@yahoo.com (Keith Parris) Y Subject: Re: Hewlett-Packard plans to EOL the HP AlphaServer Tru64. Find out how  Sun can = Message-ID: <cf15391e.0401121700.589538ac@posting.google.com>   + JF Mezei <jfmezei.spamnot@istop.com> wrote: O > What does "update" mean ? Are they going to be just bug fixes and patches, or 9 > is Tru64 getting new functionality during this period ?   E Enhancements have certainly continued unabated for the last couple of D years.  5.1A added support for LANs as a cluster interconnect, among; other things.  5.1B contained many new features as shown at ) http://h30097.www3.hp.com/unix/v51b.html. - 5.1B-1 contains more new features as shown at * http://h30097.www3.hp.com/unix/v51b1.html.  F The Roadmap indicates there will be new-hardware support added throughE the "Utah" (V5.1B-2) release slated for late this year, then remedial  releases after that.  M > Also, has HP outlined any strategy to deal with endianness differences when < > Tru64 customers are asked to migrate their data to HP-UX ?  4 There's a lot of information about the transition at@ http://h30097.www3.hp.com/transition/  There you'll find lots ofD documentation, white papers, FAQs, webcast replays, (even an on-lineA training course), assessment tools, and transition tools (and the  tools are free).  @ With regard to your specific question about endianness, the FAQsD indicate tools for data migration that will handle endianness issues  are currently under development.   ------------------------------  % Date: Mon, 12 Jan 2004 16:57:40 -0500 * From: JF Mezei <jfmezei.spamnot@istop.com>Y Subject: Re: Hewlett-Packard plans to EOL the HP AlphaServer Tru64. Find out how Sun can  ( Message-ID: <40031853.3134DC7@istop.com>   Keith Parris wrote: / > According to http://www.hp.com/go/tru64unix : 2 > "HP is fully committed to the Tru64 UNIX roadmapD > (http://h30097.www3.hp.com/unix/downloads/tru64_unix_roadmap.ppt),G > delivering updates until at least 2006 with standard support at least 
 > until 2011.   M What does "update" mean ? Are they going to be just bug fixes and patches, or 7 is Tru64 getting new functionality during this period ?   K Also, has HP outlined any strategy to deal with endianness differences when : Tru64 customers are asked to migrate their data to HP-UX ?   ------------------------------    Date: 12 Jan 2004 12:28:22 -08001 From: keithparris_NOSPAM@yahoo.com (Keith Parris)  Subject: Re: HP FUDBusting= Message-ID: <cf15391e.0401121228.56740576@posting.google.com>    Andrew Harrison SUNUK Consultancy <Andrew_No.Harrison_No@nospamn.sun.com> wrote in message news:<btub0a$pil$1@new-usenet.uk.sun.com>... 9 > Ohh dear. The Tru64 extensions to HP-UX have apparently 8 > slipped to 2005 and HP are apparently stopping selling > Tru64 in 2004.  - According to http://www.hp.com/go/tru64unix : 0 "HP is fully committed to the Tru64 UNIX roadmapB (http://h30097.www3.hp.com/unix/downloads/tru64_unix_roadmap.ppt),E delivering updates until at least 2006 with standard support at least  until 2011.    ------------------------------    Date: 12 Jan 2004 12:02:54 -08001 From: keithparris_NOSPAM@yahoo.com (Keith Parris) . Subject: Re: I just scored an AlphaServer 800!= Message-ID: <cf15391e.0401121202.3c1c835d@posting.google.com>   m Tux Wonder-Dog <wes.parish@paradise.net.nz> wrote in message news:<mIwLb.16506$ws.1897741@news02.tsnz.net>... N > Do you think that the American encompass outfit would take me on?  And would* > that be suitable for a Hobbyist License?  A Yes, and Yes.  Folks from anywhere around the world can become an D Associate of Encompass US (see http://EncompassUS.org/ for free, and? use that membership number with the OpenVMS Hobbyist program at  http://openvmshobbyist.org/    ------------------------------  % Date: Mon, 12 Jan 2004 17:21:43 -0600 ( From: brandon@dalsemi.com (John Brandon)8 Subject: Modify the logical SYS$STARTUP, why or why not?1 Message-ID: <04011217214316@dscis6-0.dalsemi.com>   I I just came across some changes to the logicals SYS$STARTUP in one of our B remote sites.  I would tend to think that this is not a good idea.  ( Anyone else doing the same type changes?   ANy other comments?         $ show logical /full sys$startup8    "SYS$STARTUP" [exec] = "MYSTARTUP" (LNM$SYSTEM_TABLE)%         = "SYS$SYSROOT:[SYS$STARTUP]"          = "SYS$MANAGER" > 1  "MYSTARTUP" [exec] = "DISK2:[SYSCOMMON]" (LNM$SYSTEM_TABLE)C 1  "SYS$MANAGER" [exec] = "SYS$SYSROOT:[SYSMGR]" (LNM$SYSTEM_TABLE)        J*o*h*n B*r*a*n*d*o*n  VMS Systems Administrator * firstname.lastname.spam.me.not@dalsemi.com   ------------------------------    Date: 12 Jan 2004 22:23:10 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen) < Subject: Re: Modify the logical SYS$STARTUP, why or why not?3 Message-ID: <W8r1MdGpivNT@eisner.encompasserve.org>   \ In article <04011217214316@dscis6-0.dalsemi.com>, brandon@dalsemi.com (John Brandon) writes:K > I just came across some changes to the logicals SYS$STARTUP in one of our D > remote sites.  I would tend to think that this is not a good idea. > * > Anyone else doing the same type changes? >  > ANy other comments?   ? As someone occasionally called upon to rescue sites in trouble,  I am of mixed emotions.   - 	On one hand, it makes problems hard to find.   * 	On the other hand, I bill by the hour :-)   ------------------------------  + Date: Mon, 12 Jan 2004 14:01:23 -0500 (EST) + From: Lord Isildur <isildur@andrew.cmu.edu> < Subject: Re: Non-WS Process Quotas not in Performance ManualH Message-ID: <Pine.LNX.4.58-036.0401121350210.5899@unix44.andrew.cmu.edu>  ' On Mon, 12 Jan 2004, Bob Koehler wrote:   B >    BSD had per-user disk quotas and per-system limits, and a fewE >    per-process limits, like heap and stack sizes.  There's a lot of B >    other resources a process can hog that are not per-process orA >    per-user limited.  Ever have a runaway process fork too many G >    children?  Sure hoses up the system when the process list is full, 9 >    and you can't start so much as a 'ps' to analyze it.   K sure, everyone's played with fork bombs. only a complete amateur would have H any trouble getting rid of one, though, unless the system was some weirdK perversion of unix. pretty much any decent unix of the past two decades has F quotas on how many slots in the process table a given user can occupy.E It might be impossible in some cases for a user to clean up his _own_ C fork bomb, this is true. root, on the other hand.. no such trouble. E even if one has one's own fork bomb to deal with... your last command F should be to exec top. once you get that, it's slow going, but you can" mop them all up and kill them off.I still a forkbomb doesn't down a machine, it just makes it _very_ slow and M of course interferes with creation of new processes. anything already running 2 just sees a lot more load, it doesnt stop working.  anyway, we're getting off topic.   Isildur    ------------------------------  % Date: Mon, 12 Jan 2004 22:28:02 +0000 ) From: Antonio Carlini <arcarlini@iee.org> < Subject: Re: Non-WS Process Quotas not in Performance Manual@ Message-ID: <CbFMb.2032$JL4.14645@newsfep4-glfd.server.ntli.net>   Lord Isildur wrote:   > > what kind of unix are you talking about? maybe 20 years ago.O > you know, BSD had process resource quotas back in 1983. A lot of the features I > VMS has today, including some of the downright defining characteristics = > (clusters anyone?) were not present in VMS in 1983, either.   A I'm diving into the middle of a thread without having followed it A all, but - for the record - clusters were just about soup in late A 1983 or thereabouts. I don't have an exact release note reference ? but I remember a reference to them in that timeframe. (Actually @ it might have been the very early months of 1984, but that still$ fits the 20-year stipulation above).  @ Of course, these were the CI-based clusters (which cost a pretty= penny back then) rather than the LAVC-based clusters that any / hobbyist can set up these days for very outlay.      Antonio      --   --------------- - Antonio Carlini             arcarlini@iee.org    ------------------------------    Date: 12 Jan 2004 14:44:34 -08007 From: jones.computer.srv@worldnet.att.net (Daryl Jones) < Subject: Re: Non-WS Process Quotas not in Performance Manual< Message-ID: <8a646952.0401121444.45717c6@posting.google.com>  	 Everyone,   F Most 3rd generation languages produced images that use a fix amount ofD process quotas once the image has been compiled and linked unless itB has dynamic capabilities (SQL) in allocating resources. Therefore,@ once the process quotas are set to be little larger than what itB requires, the image becomes a happy camper. If the image is poorlyF design or is faulty, the process quotas once consumed will cause it to: error out. A desired feature as others have remarked upon.  E The Backup Image and other images that require more process quotas to F run efficiently. Can make the process to become a CPU hog. In the caseC of the Backup Image the process quotas can be reduced thus reducing C CPU consumption without causing the image to consume the quotas and B fail. The discussion of the process quotas and other limits to theC Backup performance is System Manager guide and in the 1989 article.   B The CAM processes required the process quota values to be set highD (assumption) for the image to work. Now the problem is a performanceB issue of an image being a CPU hog. One tuning tip is to reduce theE process priority of the offending process and there are other tips in . the performance manual dealing with a CPU hog.   I hope this helps.   Regards,
 Daryl Jones                 s spamsink2001@yahoo.com (Alan E. Feldman) wrote in message news:<b096a4ee.0401101231.438306ba@posting.google.com>... j > Kilgallen@SpamCop.net (Larry Kilgallen) wrote in message news:<uuMGLBEDDCm8@eisner.encompasserve.org>...r > > In article <b096a4ee.0401091914.17f1d930@posting.google.com>, spamsink2001@yahoo.com (Alan E. Feldman) writes: > > > jones.computer.srv@worldnet.att.net (Daryl Jones) wrote in message news:<8a646952.0401091130.6776e342@posting.google.com>... >   L > > >> In the case of Backup performance, these process quotas turned out toI > > >> be performance parameters. During a backup the process quotas will K > > >> limit the performance of the backup image and not error out like the J > > >> execution of other images. Increasing these parameters will per theE > > >> article will decrease the runtime of the backup. Much like the L > > >> WSdefault, WSquota, WSexetent, and other parameters you have mention. > > > [...]  > > > C > > > Then why do these quotas even exist if they have no effect on K > > > performance (save for BACKUP)? Why not just set them all to 2^32-1 or  > > > whatever they max out at?  > > C > > Process quotas control access to system resources by individual C > > processes.  If everybody had infinite quotas, one piggy program , > > could bring the machine to a standstill. > @ > So bringing the machine to a standstill would be a performanceG > problem. Hence, process quotas should be discussed in the performance F > manual. And they're not except for wsdefault, wsquota, and wsextent. > Hence my original question.  >  > Alan E. Feldman    ------------------------------  % Date: Mon, 12 Jan 2004 19:14:55 -0500 3 From: "Richard B. Gilbert" <rgilbert88@comcast.net> < Subject: Re: Non-WS Process Quotas not in Performance Manual0 Message-ID: <886dncO4V_EcpZ7dRVn-gg@comcast.com>  H It was a long time ago but I believe the VMS V3.7 supplied a lot of the F underpinnings for CI clusters like support for HSCs and the CI.  This  was in 1984   E VMS V4.0, if I recall correctly, was the first release that actually  H allowed you to build a cluster.  Not sure when VMS V4.0 hit the streets I but I think 1985 would be a close guess.  I didn't have software support  : at the time and the release after V3.6  was, for me, V4.4.  F This was all pretty academic for me at the time, we could only afford G our 11/750 with ancillary hardware and software because DEC gave it to  C us at something like 30 or 40 percent of list price.  The hardware  H required to build a cluster would have been completely beyond our reach  unless DEC just donated it.    Antonio Carlini wrote:   > Lord Isildur wrote:  > ? >> what kind of unix are you talking about? maybe 20 years ago. H >> you know, BSD had process resource quotas back in 1983. A lot of the  >> features J >> VMS has today, including some of the downright defining characteristics> >> (clusters anyone?) were not present in VMS in 1983, either. >  > C > I'm diving into the middle of a thread without having followed it C > all, but - for the record - clusters were just about soup in late C > 1983 or thereabouts. I don't have an exact release note reference A > but I remember a reference to them in that timeframe. (Actually B > it might have been the very early months of 1984, but that still& > fits the 20-year stipulation above). > B > Of course, these were the CI-based clusters (which cost a pretty? > penny back then) rather than the LAVC-based clusters that any 1 > hobbyist can set up these days for very outlay.  >  > 	 > Antonio  >  >  > --   >  > --------------- / > Antonio Carlini             arcarlini@iee.org  >    ------------------------------  % Date: Mon, 12 Jan 2004 20:50:55 -0500 + From: Ken Robinson <kenrbnsn1@patmedia.net> < Subject: Re: Non-WS Process Quotas not in Performance ManualA Message-ID: <6.0.1.1.2.20040112204259.028e7ec0@mail.patmedia.net>   0 At 07:14 PM 1/12/2004, Richard B. Gilbert wrote:I >It was a long time ago but I believe the VMS V3.7 supplied a lot of the  K >underpinnings for CI clusters like support for HSCs and the CI.  This was   >in 1984 > F >VMS V4.0, if I recall correctly, was the first release that actually I >allowed you to build a cluster.  Not sure when VMS V4.0 hit the streets  J >but I think 1985 would be a close guess.  I didn't have software support ; >at the time and the release after V3.6  was, for me, V4.4.   G VMS v4.0 came out around summer 1984. I was working at Bellcore at the  G time. In October on 1984 I transferred to a group that was going to be  L installing three clusters of 11/785's, with each cluster consisting of 3 or E 4 machines. I was sent to a class to learn cluster system management.   I The first cluster was installed by Digital in the beginning of December,  K 1984 (or end of November) and was running just in time for me to go to the   DECUS Symposium in Anaheim.   
 Ken Robinson     ------------------------------    Date: 12 Jan 2004 11:52:41 -08001 From: keithparris_NOSPAM@yahoo.com (Keith Parris) Y Subject: Re: Oracle Rdb on GS1280 with 7.3-2 exceeds 1 million transactions per minute us = Message-ID: <cf15391e.0401121152.35705336@posting.google.com>    Andrew Harrison SUNUK Consultancy <Andrew No.Harrison No@nospamn.sun.com> wrote in message news:<btuf3v$r3e$1@new-usenet.uk.sun.com>... > > Let me see your stated possition on benchmarks is that TPC-C/ > is the one to do to measure OLTP performance.    Nope.   D Every time someone quoted TPC-C performance numbers, you would chimeF in to say that TPC-C doesn't reflect real-world performance.  I merelyE pointed out that the Transaction Processing Council (http://tpc.org/) E certainly feels there is merit in the TPC-C benchmark, and that there > are customers who find TPC-C to be valuable as one of the many< available metrics in considering the performance of vendors'
 equipment.  = > Why go to the effort of benchmarking a large system running = > RDB using a benchmark that might or might not by quite like ( > TPC-C when you could have done TPC-C ?  ( (Note that Oracle did the test, not HP.)  E The description clearly described the reasons for the test: This test E was to explore the limits of Rdb Row Cache, and they found they could E cache 1 billion rows in physical memory within the Alphaserver GS1280 B with its 64-bit-address-space Alpha processors.  And the EV7-basedA GS1280 running under OpenVMS version 7.3-2 scaled very well at 32 E processors, able to do over 1 billion transactions per minute on that D cached data, while retaining full transactional integrity guarantees( against process, disk, or node failures.   ------------------------------  % Date: Mon, 12 Jan 2004 20:00:58 -0700 4 From: Norman Lastovica <norman.lastovica@oracle.com>Y Subject: Re: Oracle Rdb on GS1280 with 7.3-2 exceeds 1 million transactions per minute us * Message-ID: <40035F6A.75ABF4EF@oracle.com>  E Keith is correct.  I ran the test.  The test was originally intended  A simply to prove that Rdb caches a billion rows.  Mostly, from my  1 perspective, to show  that the software worked.     F I borrowed a GS1280 from vms engineering for 3 days.  Loaded the data C and ran my little workload simulator (read-write transactions each  G modifying or inserting a single row).  after seeing about 13k database  A TPS, I twisted a few knobs and ran the same test a second time.   @ about 17k TPS (I was sort of disappointed that it wasn't 20k).  $ 17k TPS = just over a million TPM.    E Nothing fancy here.  This was just a quicky test to make sure that it D all worked the way we wanted it to.  And the million TPM was nothingE more than icing on the cake as far as I was concerned.  HP and Oracle = marketing people turn all this into nice sounding paragraphs.   F From my perspective, one good thing about this test is that it didn't @ require massive amounts of storage hardware nor a huge array of E RTE systems.  It was really quick and dirty.  And inexpensive to run.   D And, based on what we (VMS engineering and Rdb engineering) learned,B we plowed improvements back into both products.  So it was win-win that way as well.      Keith Parris wrote:  >  > Andrew Harrison SUNUK Consultancy <Andrew No.Harrison No@nospamn.sun.com> wrote in message news:<btuf3v$r3e$1@new-usenet.uk.sun.com>... @ > > Let me see your stated possition on benchmarks is that TPC-C1 > > is the one to do to measure OLTP performance.  >  > Nope.  > F > Every time someone quoted TPC-C performance numbers, you would chimeH > in to say that TPC-C doesn't reflect real-world performance.  I merelyG > pointed out that the Transaction Processing Council (http://tpc.org/) G > certainly feels there is merit in the TPC-C benchmark, and that there @ > are customers who find TPC-C to be valuable as one of the many> > available metrics in considering the performance of vendors' > equipment. > ? > > Why go to the effort of benchmarking a large system running ? > > RDB using a benchmark that might or might not by quite like * > > TPC-C when you could have done TPC-C ? > * > (Note that Oracle did the test, not HP.) > G > The description clearly described the reasons for the test: This test G > was to explore the limits of Rdb Row Cache, and they found they could G > cache 1 billion rows in physical memory within the Alphaserver GS1280 D > with its 64-bit-address-space Alpha processors.  And the EV7-basedC > GS1280 running under OpenVMS version 7.3-2 scaled very well at 32 G > processors, able to do over 1 billion transactions per minute on that F > cached data, while retaining full transactional integrity guarantees* > against process, disk, or node failures.   --  	 - - - - - 0  opinions expressed here are mine and mine alone.  and certainly are not intended in any way to 0  express or represent any opinions or commitment  of oracle corporation.   *  norman lastovica / oracle rdb engineering   ------------------------------  + Date: Mon, 12 Jan 2004 19:27:39 -0600 (CST)  From: sms@antinode.org8 Subject: Personal Workstation 500a/au hardware questions) Message-ID: <04011219273978@antinode.org>   H    I recently got a moderate bargain on a PWS 500a (although now, with aF Qlogic SCSI card (like, but not really a, KZPBA-CX), it claims to be a$ 500au), and now I need some insight.  :    Graphics.  This machine was running Windows NT, with anG impressive-looking Digital/Intergraph PBXGI (PBPSPBXGI) graphics card.  E I gather that this card is useless with VMS, although a fairly recent B VMS SPD no longer mentions _any_ Alpha hardware this old.  A briefF experiment with a PBXGA (ZXLp) suggested that the SRM console firmwareE did not cope well with that one, but after a firmware update, an ELSA H Gloria Synergy (ViVo, not a genuine PBXGK) seems to work nicely.  Sadly,H my best (old) display wants sync on green, hence my desire to retain theH PBXGA card.  I have not yet tried the PBXGA with VMS, but if anyone has,F I'd be interested.  (I may need to break down and get a newer display,G but it'll break my heart to lose the last trace of HP/Apollo in general 
 use here.)  G    IDE.  The next problem is the IDE CD-ROM.  This system has the Intel E SIO chip, not the Cypress, so I'm resigned to using a SCSI CD-ROM for E critical purposes, but I'd like to use an IDE CD-RW drive.  The one I B have in there now appears (as "dqa0.0.0.4.0") in the console "showA device" list, and it works as a boot device for a firmware CD-ROM = (though VMS V7.3-1 gets all huffy about it as a boot device).4  F    I've sucked down what may be the latest DQDRIVER ("X-49"), compiledH it (DQDRIVER.COM, "Compaq C V6.5-001 on OpenVMS Alpha V7.3-1"), and thenE ran LOAD_DQ_INTEL_SIO.COM.  The result is less than I had dared hope:l  . ALP2$DQA0:              Offline              0  G I assume that someone has this working and can steer me appropriately. 6 The console "show config" says:l   PCI Bus  [...]o      Bus 00  Slot 04: PCI IDEF@                                   pqa0.0.0.4.0          PCI EIDEH                                   dqa0.0.0.4.0            52X24X52 CD-RW [...]p  I    So far, the software is VMS V7.3-1, straight off the Hobbyist CD-ROM. tB Interestingly, the DECwindows automatic AUTOGEN did not succeed inF boosting the GBLPAGES (or GBLsomething), after a couple of tries, so I had to do it manually.  F    On the bright side, even with less memory than I'd like (256MB), it/ seems perkier than my AlpSta 200 4/233, so far.   H ------------------------------------------------------------------------  4    Steven M. Schweda               (+1) 651-699-98183    382 South Warwick Street        sms@antinode-orgs    Saint Paul  MN  55105-2547h   ------------------------------  % Date: Mon, 12 Jan 2004 22:26:25 -0700b/ From: "Tucker" <glarb.nospam.org@ix.netcom.com>s6 Subject: Problem using bind() function in 'C' program.0 Message-ID: <NemdnQrr5IDiHJ7dRVn-ug@comcast.com>  	 Hi there.s  ; I have a user who is using this statement in a 'C' program:   J  if( (ret=bind(fd, (struct sockaddr *)&saddr, sizeof(struct sockaddr_in))) <0)t  C (I belive the program is trying to create a TCP/IP socket, and thenp
 listen...)H The program is returning an error (return code -1) and sets errno to 76,L which translates into "function not implemented".  I am at a loss as to what might be the cause of this.    Here is the environment:   OpenVMS V7.3-1  (alpha)s C V5.6 TCPware V5.6-2  & Is there any other information needed?   Thanks, in advance,t Tucker   ------------------------------  % Date: Mon, 12 Jan 2004 17:05:04 -0800-% From: Dean Woodward <deanw@rdrop.com> ( Subject: Re: Problems with 7.3 and 164LX( Message-ID: <40034440.3090909@rdrop.com>   Tor Arne Rein wrote:H > Now, if I only could get my hands on a VMS compatible ethernet card...  ` http://search.ebay.com/search/search.dll?query=de500&ht=1&sosortproperty=1&from=R10&BasicSearch=   ------------------------------  # Date: Tue, 13 Jan 2004 00:03:40 GMTm# From: hoff@hp.nospam (Hoff Hoffman)f4 Subject: Re: Silly Users with Password as "Password"2 Message-ID: <wBGMb.12132$sQ.1235@news.cpqcorp.net>  a In article <btnevk$dm0$1@hercules.btinternet.com>, "Robert" <robert.heyes@btinternet.com> writes:mJ :Ive written a program today to check the SYSUAF.DAT for all my users in aL :group and find any naughty users who havent changed their password from theH :default I would set (which for example would be PASSWORD), eg. Username9 :JBLOGGS Password PASSWORD by doing $dir nodename"JBLOGGSlK :PASSWORD"::Login*.com and checking the return code. If the dir command was@K :successful then output that user name to a text file as the password hadntc :been changed.  J   If the password PASSWORD has been selected, then some of these users areK   fully privileged users (eg: you?) and can directly select weak passwords,hH   or somebody has altered the system security profile downward, and thus.   you've a rather larger problem lurking here.     Why?  H   The password word "password" is already in the password dictionary andJ   has been in the dictionary for a very long time -- and I found it listedJ   as far back as I checked, in OpenVMS VAX V5.5-2 -- so either the user(s)J   involved have privileges or the tools that allow them to directly changeJ   their password in AUTHORIZE or otherwise bypassing the dictionary checksH   (eg: you've added the user, selected an unfortunately weak password asG   the user's new login password, and unfortunately also explicitly usedpI   the /NOPWDEXP qualifier), or the dictionary contents have been altered, =   or the dictionary has been directly or indirectly disabled.f     Old password: [old password] New password: password Verification: passwordP %SYSTEM-F-PWDINDIC, password found in system dictionary; please choose another s tringr $i  E   Additionally, when a password is selected, the password defaults tooD   requiring a change -- a privileged user resetting the password to D   PASSWORD would have to use /NOPWDEXP to allow it to stay selected.G   Without this additional qualifier, the user has to reset the passwordk   upon next login.    I   If you want to go after this problem, add any words of local importance I   (company name, town, notable local citizens, local events of note, etc)aH   into the password dictionary, enable security alarms for authorizationG   database accesses, and then set the passwords pre-expired and force adF   password change.  Oh, and make sure that users have not had the flagG   DISPWDDIC set on their respective username entries within SYSUAF.DAT.e  J   If you want to get slightly fancier, you can use the  account expirationG   field and/or the last password change to more selectively enforce thetG   password change, or to selectively add /PWDEXP on specific usernames,aD   etc.  There are certainly many other schemes available, of course.  G   The approach you suggest -- directly probing passwords -- should trip E   breakin evasion, and you should see breakin warning attempts loggedeH   onto each username targeted -- best to update the password dictionary,G   reset the users to /PWDEXP (all, or those that have yet to change the-:   setting), and let the users re-select new(er) passwords.  K   If you additionally want to customize the password selection or rejectioniI   filtering processing on your OpenVMS system -- character-level password4J   checks and such, filtering beyond adding words to the dictionary -- then'   there is an example in SYS$EXAMPLES:..    N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faqoN  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.come   ------------------------------  % Date: Mon, 12 Jan 2004 15:43:35 -0500 ) From: "Scott Greig" <jsgreig@geminaq.com> & Subject: Size restriction of LD disks?8 Message-ID: <mGDMb.3384$1K1.11522@news20.bellglobal.com>  
 Hello all:  8 I've just received my 7.3-2 media kit, and looked at the9 LD731 directory on the freeware (V6) CD - the readme fileu
 indicates:  + "Releases LD063 and prior have a hard uppers+ volume size limit of four gigabytes (4 GB), - and larger volumes should not be configured."   @ Is this true?  I have used this product to split up large (72GB)= disks into multiple smaller (approx 24 GB) logical units, and $ everything appears to work properly.   Anyone have any answers?   TIA  Scott   8 Just a thought - could this possibly be 4 Billion blocks (Not 4 Billion bytes?)   jsg:   ------------------------------  % Date: Mon, 12 Jan 2004 16:07:16 -0500>( From: "Ivan Gold" <igold@computerch.net>* Subject: Re: Size restriction of LD disks?: Message-ID: <o_DMb.5252$5M.120855@dfw-read.news.verio.net>  4 "Scott Greig" <jsgreig@geminaq.com> wrote in message2 news:mGDMb.3384$1K1.11522@news20.bellglobal.com... > Hello all: >u: > I've just received my 7.3-2 media kit, and looked at the; > LD731 directory on the freeware (V6) CD - the readme filen > indicates: >w- > "Releases LD063 and prior have a hard upper - > volume size limit of four gigabytes (4 GB),p/ > and larger volumes should not be configured."  >nB > Is this true?  I have used this product to split up large (72GB)? > disks into multiple smaller (approx 24 GB) logical units, ande& > everything appears to work properly. >t > Anyone have any answers? >  > TIA  > Scott  >C: > Just a thought - could this possibly be 4 Billion blocks > (Not 4 Billion bytes?) >o > jsgC >m >a   ------------------------------  % Date: Mon, 12 Jan 2004 16:07:21 -0500a( From: "Ivan Gold" <igold@computerch.net>* Subject: Re: Size restriction of LD disks?: Message-ID: <t_DMb.5253$5M.120941@dfw-read.news.verio.net>  4 "Scott Greig" <jsgreig@geminaq.com> wrote in message2 news:mGDMb.3384$1K1.11522@news20.bellglobal.com... > Hello all: >v: > I've just received my 7.3-2 media kit, and looked at the; > LD731 directory on the freeware (V6) CD - the readme filet > indicates: >c- > "Releases LD063 and prior have a hard upper - > volume size limit of four gigabytes (4 GB),j/ > and larger volumes should not be configured."U >pB > Is this true?  I have used this product to split up large (72GB)? > disks into multiple smaller (approx 24 GB) logical units, andl& > everything appears to work properly. >  > Anyone have any answers? >  > TIA  > Scottr ><: > Just a thought - could this possibly be 4 Billion blocks > (Not 4 Billion bytes?) >h > jsgk >t >    ------------------------------  # Date: Tue, 13 Jan 2004 00:26:35 GMTf# From: hoff@hp.nospam (Hoff Hoffman) * Subject: Re: Size restriction of LD disks?2 Message-ID: <%WGMb.12138$sQ.5454@news.cpqcorp.net>  d In article <mGDMb.3384$1K1.11522@news20.bellglobal.com>, "Scott Greig" <jsgreig@geminaq.com> writes:  9 :I've just received my 7.3-2 media kit, and looked at thec: :LD731 directory on the freeware (V6) CD - the readme file :indicates:s :c, :"Releases LD063 and prior have a hard upper, :volume size limit of four gigabytes (4 GB),. :and larger volumes should not be configured." :cA :Is this true?  I have used this product to split up large (72GB)b> :disks into multiple smaller (approx 24 GB) logical units, and% :everything appears to work properly.a :c :Anyone have any answers?e    F   I was under the impression what I wrote was both clear and concise.      Apparently not. :-)y  F   If you configure LD devices larger than four gigabytes, then you canC   encounter partition file corruptions and/or system crashes.  Thisn,   from the engineers maintaining the driver.  G   LDDRIVER drivers built from the LD V6.4 source code pool and later --bF   and built on or after 19-MAR-2002 -- include the fix.  This includes   OpenVMS V7.3-1 and later.e  I   LDDRIVER is latent within V7.3-1 and later, and the fix is incorporatedtJ   in that release.  (The LD731 installation kit effectively only serves toJ   load a CLD, and thus allows more direct access to the existing LD tool.)    N  ---------------------------- #include <rtfaq.h> -----------------------------K     For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq(N  --------------------------- pure personal opinion ---------------------------E         Hoff (Stephen) Hoffman   OpenVMS Engineering   hoff[at]hp.como   ------------------------------    Date: 12 Jan 2004 14:45:25 -06004 From: kuhrt@nospammy.encompasserve.org (Marty Kuhrt)5 Subject: Re: Slightly OT: Code Red on the rise again?e3 Message-ID: <fYM4pxUIpfjv@eisner.encompasserve.org>n  q In article <btsj7t$b10sv$1@ID-209632.news.uni-berlin.de>, "Martin P.J. Zinser" <zinser@zinser.no-ip.info> writes:m > Hello, > G > just noticed in my logs that since Jan 8th I am getting requests for .I > default.ida, which is the way Code Red attacks IIS servers. Since I do  I > run my server on VMS I am not affected (besides of the fact that these -F > idiotic requests spoil my log). Is this an isolated occurance or do  > others see this too? >  > Greetings, Martine Hiya,a  > I've only received a few since the last time I reset the logs.> The 404s I get most now are of the "GET /scripts/nsiislog.dll"A variety.  Except for taking up some disk space this has no effect" on my VMS CSWS (Apache) server.   
 Greetings, Marty,   ------------------------------    Date: 12 Jan 2004 16:19:50 -0800( From: bob@instantwhip.com (Bob Ceculski)5 Subject: Re: Slightly OT: Code Red on the rise again?f= Message-ID: <d7791aa1.0401121619.4589025e@posting.google.com>o  _ Wayne Sewell <wayne@tachysoft.com> wrote in message news:<00A2BC09.B84269E7.5@tachysoft.com>... 0 > >From: Kilgallen@SpamCop.net (Larry Kilgallen) > >X-Newsgroups: comp.os.vms8 > >Subject: Re: Slightly OT: Code Red on the rise again?# > >Date: 11 Jan 2004 19:19:19 -0600a >  a > >o > >_Slightly_ ?  > >r( > >VMS systems should be totally immune. >  > N > Sure, there's no actual damage or disruption, but that horseshit clutters upL > the web server logs and wastes disk space.  I periodically restart the web) > servers so that the logs can be purged.h  E purveyor allows you to set auto log which automatically opens new log,B files with date stamp either daily, weekly, monthly, or yearly ...@ what are you running where you have to restart to get a new log?   ------------------------------    Date: 12 Jan 2004 12:27:44 -0800( From: bob@instantwhip.com (Bob Ceculski)I Subject: Re: The Register: OpenVMS among most-secure of operating systems-= Message-ID: <d7791aa1.0401121227.65ed6025@posting.google.com>M   Andrew Harrison SUNUK Consultancy <Andrew_No.Harrison_No@nospamn.sun.com> wrote in message news:<btuael$p9t$2@new-usenet.uk.sun.com>...4 > Keith Parris wrote:o > > Andrew Harrison SUNUK Consultancy <Andrew_No.Harrison_No@nospamn.sun.com> wrote in message news:<btk2br$a43$1@new-usenet.uk.sun.com>...3 > = > However I have made no claims whatsoever about the relativei> > number of security issues discovered for OpenVMS vs Solaris. > > > In fact I would go as far as saying that Solaris is bound to= > have more advisories for it than OpenVMS because its sourcey< > is easy to get hold of for scrutiny and because Solaris is% > much more widely used than OpenVMS.   @ "The other significant feature of these operating systems is theE language in which they are written. The two from IBM are both writteneD in assembler and OpenVMS uses a range of about ten languages, one of which is C.   = C and similar languages that use pass-by-value techniques areiC exceptionally prone to buffer overflow and the consequent potentialnD for unauthorized users to execute either their own malicious code orF other programs which run with enhanced access privileges. Avoiding theE use of these languages at the most vulnerable points, namely user I/O/E and network I/O, would appear to be wise. Linux, Unix and Windows area> almost entirely written in C, and most of their middleware andA application software is also in these vulnerable languages, so itoB should come as no surprise that they are less secure than OpenVMS, OS/400 and zOS.0  ? The other operating system that had very few vulnerabilities isjD Apple's OS 9, with the Secunia database showing just one in 2003 andB none in 2002. Again this is a proprietary operating system and theF decisions and integration of security rest with one organisation whichF does not have to concern itself with compatibility with other vendors.  D Apple recently moved to a Unix-based operating system, OS X, and the@ 24 vulnerabilities reported for it by Secunia in 2003 are a very telling comment."U   ------------------------------  % Date: Tue, 13 Jan 2004 00:11:56 -0000t4 From: "Chris Casey" <chris.caseyNOSPAM@ntlworld.com>I Subject: Re: The Register: OpenVMS among most-secure of operating systems1> Message-ID: <rJGMb.2349$YV1.383@newsfep4-winn.server.ntli.net>  K "Andrew Harrison SUNUK Consultancy" <Andrew_No.Harrison_No@nospamn.sun.com>i; wrote in message news:btuaef$p9t$1@new-usenet.uk.sun.com...l > Chris Casey wrote:' > > "Andrew Harrison SUNUK Consultancy" ' <Andrew_No.Harrison_No@nospamn.sun.com> L > > wrote in message news:btk2br$a43> Unfortunately its a pointless piece of > > research because OpenVMS > >$E > >>security advisories do not get reliably reported to CERT, BugtraqTC > >>etc so counting the ones that do only catches the excpetions toD
 > >>the rule.] > >>B > >>You know this, I know this, its well documented so why did you? > >>bother posting a reference to the The Registers article itsi6 > >>not very responsible behaviour on your part is it. > >> > >>Regards- > >>Andrew Harrison2 > >> > >2 > >0H > > Aw Andrew, change your tune won't you. You trot out the same line toH > > everything. I personally don't care anymore whether your position on CERT isaD > > true or not because you have belaboured it so much as to make it useless. > >  >h6 > Look when OpenVMS BS merchants stop trotting out the5 > OpenVMS is so secure look how few CERTS it gets lies> > and it is a huge and proven lie then I will stop responding. >e? > If you don't want a discussion about CERT then try persuading + > the OpenVMS CERT trolls to stop trolling.  >e >nL > > Unless you have some evidence that says that other operating systems are asJ > > secure as VMS then stop attacking anyone who says that VMS is the most > > secure system. > >  > >0 >1> > If you can find any reference in my postings to the relative; > security of OpenVMS vs any other OS either for or againstu? > then you are welcome to ask me to provide evidence to supporte > those claims.M > : > But then I havn't suggested that OpenVMS is more or less; > secure than any other OS so you don't get to play. I havel> > however claimed that OpenVMS isn't as secure as people think6 > it is and proved the claim on a number of occasions. > 	 > Regards  > Andrew Harrison  >u   Andrew,s  H try reading what I said. I said [rephrased for easy understanding] 'stopG attacking people who state that VMS is the most secure operating system L unless you have evidence to the contrary'. At no time did I suggest that you1 had an opinion on the matter, valid or otherwise.t   ------------------------------    Date: 12 Jan 2004 12:54:10 -0800( From: robison_m@crane.navy.mil (Zspider)( Subject: Re: VAX architecture and Charon= Message-ID: <2774a1e1.0401121254.4777ab9c@posting.google.com>a  < Bob Koehler wrote about using Charon software in a hardware- intensive environment:  o? Every time I look at the Charon-VAX websites I see disclaimers l8 that keep me from trying it in this kind of application.  s Let us know how you do.o   ***************i< Thanks for commenting, Bob.  We've had good luck with Charon< replacing an old VAXstation software development platform in< a fairly demanding engineering environment, so we decided to" attempt to take it a step further.  > We have been really happy with the Charon VAXstation emulator.< It's always been our policy to purchase hardware maintenance? contracts for our DEC stuff, but it's gotten so expensive that  < we could just about buy a PC for the price of a year's main-< tenance.  Plus, our compile and bind times for our programs ? dropped down to less than 20% of former VAX times.  Considering > that we had compile/binds that were taking close to two hours,9 our integration turnaround cycle got a significant boost.w   Michaeln   ------------------------------    Date: 12 Jan 2004 15:28:37 -0600; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler)o( Subject: Re: VAX architecture and Charon3 Message-ID: <n5LJ1kes1vam@eisner.encompasserve.org>3  h In article <2774a1e1.0401121254.4777ab9c@posting.google.com>, robison_m@crane.navy.mil (Zspider) writes:> > Thanks for commenting, Bob.  We've had good luck with Charon> > replacing an old VAXstation software development platform in> > a fairly demanding engineering environment, so we decided to$ > attempt to take it a step further.  @    Engineering environment?  That means nothing to me.  It couldE    be like my development hosts, when we run the compilers everything     gets CPU intensive.  G    Since Charon-VAX should run circles around those and they don't haverA    any hardware requirements I am thinking about replacing those.:   ------------------------------  % Date: Mon, 12 Jan 2004 18:19:15 -050013 From: "Richard B. Gilbert" <rgilbert88@comcast.net>o( Subject: Re: VAX architecture and Charon0 Message-ID: <gN-dnaAVMpnrtp7dRVn-gw@comcast.com>  +     VAX Architecture and Assembler Language   I Brunner, Richard A. "VAX Architecture Reference Manual", second edition, p Digital Press, 1991   G Frank, T.S. "Introduction to VAX-11 Archtectute and Assembly Language" r Prentice-Hall 1987  G Levy, Henry M, and Eckhouse, Jr., Richard H. "Computer Programming and o, Architecture - The VAX", Digital Press, 1989  B Kapps, Charles and Stafford, Robert L. "VAX Assembly Language and @ Architecture", Prindle, Weber, and Schmid (PWS Publishers), 1985  J Sebesta, "VAX Structured Assembly Language Programming", Benjamin/Cummings  G Baase, Sara "VAX-11 Assembly Language Programming", Prentice-Hall, 1983q  D Federighl, Francis D. and Reilly, Edwin D. "VAX Assembly Language",  MacMillan 1991   Zspider wrote:  A >We are gearing up for an attempt to replace a MicroVAX with a PCrA >running the Charon VAX emulator software.  The VAX is in a test a@ >environment and it controls a lot of instrumentation, so we'll + >be running a PCI-to-QBus card in the PC.  e >r@ >We would like to come up to speed some on the VAX architecture.= >Can someone recommend any online documentation or good booksi; >available through Amazon on VAX architecture and hardware?k >1> >Also, any comments from people using the Charon software in a5 >hardware-intensive application would be appreciated.p >o >Thank you,  >a >Michael Robison
 >812-854-4953L# >Crane Naval Surface Warfare Center  >  n >t   ------------------------------    Date: 12 Jan 2004 14:33:55 -0800 From: cellctl@lycos.com (Ben)e  Subject: Re: VAXstation question< Message-ID: <dd8c4466.0401121433.ac3de9f@posting.google.com>  C >    I don't know about 32/V, but that model will run Ultirx (DEC'skJ >    BSD UNIX), and probably one of the free BSD (NetBSD or FreeBSD) UNIX.  F I know of Ultrix... been looking for it, but it's tough to find.  I'veE never seen a copy go on eBay.  Anyone know where I might find a copy?n (or be willing to sell one?)   ------------------------------    Date: 12 Jan 2004 11:56:45 -08001 From: keithparris_NOSPAM@yahoo.com (Keith Parris)S( Subject: Re: Vaxstation some question...= Message-ID: <cf15391e.0401121156.26c33119@posting.google.com>u  k "Richard B. Gilbert" <rgilbert88@comcast.net> wrote in message news:<1v6dnTQ4kslr7Z3dRVn-ug@comcast.com>...^ > VMS doesn't partition disks.  F True in general, but VMS can partition disks using the Host-Based RAID1 Software.  And one can also partition disks usingnE storage-controller-based partitioning and present those partitions tot VMS.   ------------------------------  # Date: Mon, 12 Jan 2004 23:46:08 GMTr6 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER)( Subject: Re: Vaxstation some question...2 Message-ID: <4lGMb.99234$Tz1.65355@news.chello.at>  q In article <cf15391e.0401121156.26c33119@posting.google.com>, keithparris_NOSPAM@yahoo.com (Keith Parris) writes:0l >"Richard B. Gilbert" <rgilbert88@comcast.net> wrote in message news:<1v6dnTQ4kslr7Z3dRVn-ug@comcast.com>... >> VMS doesn't partition disks.V >pG >True in general, but VMS can partition disks using the Host-Based RAID.2 >Software.  And one can also partition disks usingF >storage-controller-based partitioning and present those partitions to >VMS.c  H May I ask again for inclusion of host-based-RAID to the OpenVMS hobbyist license program ?    -- S Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  % Date: Mon, 12 Jan 2004 18:59:00 -0500w3 From: "Richard B. Gilbert" <rgilbert88@comcast.net>i( Subject: Re: Vaxstation some question...0 Message-ID: <d_GdnUGSPv1aqZ7dRVn-uQ@comcast.com>  , This is a multi-part message in MIME format.& --------------0101070306050700070001049 Content-Type: text/plain; charset=us-ascii; format=flowed> Content-Transfer-Encoding: 7bitg  E Quite true but VMS doesn't do that!  Host-Based RAID is a separately sE licensed product.  ISTR that Host Base Volume Shadowing is a "System  I Integrated Product" but it, too, is separately licensed.  With Unix, the nI ability is built in!  Unix people think you are a little peculiar if you   don't partition your disk!  @ Partitions created by hardware RAID are clearly not part of the C operating system and, to VMS, the partitions appear to be physical  L devices and are handled as such by the host bus adapter, device driver, etc.   Keith Parris wrote:t  l >"Richard B. Gilbert" <rgilbert88@comcast.net> wrote in message news:<1v6dnTQ4kslr7Z3dRVn-ug@comcast.com>... >    >b >>VMS doesn't partition disks. >>     >> >kG >True in general, but VMS can partition disks using the Host-Based RAIDu2 >Software.  And one can also partition disks usingF >storage-controller-based partitioning and present those partitions to >VMS.@ >  r >   & --------------010107030605070007000104) Content-Type: text/html; charset=us-ascii  Content-Transfer-Encoding: 7bitn  ? <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">  <html> <head>I   <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">,   <title></title>  </head>I' <body text="#000000" bgcolor="#ffffff">MJ Quite true but <i><b>VMS</b></i> doesn't do that!&nbsp; Host-Based RAID isL a separately licensed product.&nbsp; ISTR that Host Base Volume Shadowing isH a "System Integrated Product" but it, too, is separately licensed.&nbsp;L With Unix, the ability is built in!&nbsp; Unix people think you are a little< peculiar if you <i><b>don't </b></i>partition your disk!<br> <br>? Partitions created by hardware RAID are clearly not part of themB operating system and, to VMS, the partitions appear to be physicalG devices and are handled as such by the host bus adapter, device driver,t etc.<br> <br> Keith Parris wrote:<br>t <blockquote type="cite" ;  cite="midcf15391e.0401121156.26c33119@posting.google.com"> &  <pre wrap="">"Richard B. Gilbert" <a class="moz-txt-link-rfc2396E" href="mailto:rgilbert88@comcast.net">&lt;rgilbert88@comcast.net&gt;</a> wrote in message news:<a class="moz-txt-link-rfc2396E" href="mailto:1v6dnTQ4kslr7Z3dRVn-ug@comcast.com">&lt;1v6dnTQ4kslr7Z3dRVn-ug@comcast.com&gt;</a>...   </pre>   <blockquote type="cite">-     <pre wrap="">VMS doesn't partition disks.l
     </pre>   </blockquote>u   <pre wrap=""><!---->F True in general, but VMS can partition disks using the Host-Based RAID1 Software.  And one can also partition disks usingtE storage-controller-based partitioning and present those partitions toe VMS.   </pre>
 </blockquote>m </body>h </html>   ( --------------010107030605070007000104--   ------------------------------    Date: 12 Jan 2004 16:21:40 -0800( From: bob@instantwhip.com (Bob Ceculski)* Subject: Re: VMS runs well on HP Superdome= Message-ID: <d7791aa1.0401121621.435ecc72@posting.google.com>/   Andrew Harrison SUNUK Consultancy <Andrew_No.Harrison_No@nospamn.sun.com> wrote in message news:<btubeg$ppj$1@new-usenet.uk.sun.com>...h > Fred Kleinsorge wrote:O > > "Andrew Harrison SUNUK Consultancy" <Andrew_No.Harrison_No@nospamn.sun.com>o? > > wrote in message news:btjghu$3l4$1@new-usenet.uk.sun.com...h > >  > >>Fred Kleinsorge wrote: > >>H > >>>"David J. Dachtera" <djesys.nospam@NeOaSrPtAhMlNiOnWk.net> wrote in > >  > > messagec > > 5 > >>>news:3FFB7ACA.34800557@NeOaSrPtAhMlNiOnWk.net...  > >  > > & > >>So I repeat why on earth would you' > >>want to sell hardware. You are muchs% > >>more likely to make a return fromv > >>selling SW.i > >>+ > >>You are between a rock and a hard placeE+ > >>for Itanium to survive it has to becomen, > >>a commodity, but you can only make money1 > >>at the low end if you arn't having to competet# > >>on a commodity basis with Dell.l > >  > > O > > I guess I'll ask the same question of you:  Why is Sun still in business at-K > > all?  The best you've done in a few years is break even in one quarter.s; > > Solaris runs on a PC - why not ditch all your hardware?  > >  > ; > Well because Sun was at least adjacent to making a profits9 > last year while the EBU was ~1 billion dollars a drift.  > 7 > The only thing HP can demonstrate a consistent returnt: > on is toner, this was the status quo pre merger and none< > of cost the center shuffling post merger has changed that. > 9 > Every quarter Walter Hewletts strategy looks better and ( > better and the Boards worse and worse. > 	 > Regardsi > Andrew Harrisonn  D and every week slowaris rings up another cert of the week, and every8 day it runs like the convuluted crap it and linux is ...   ------------------------------    Date: 12 Jan 2004 11:33:18 -0800/ From: david_awerbuch@yahoo.com (David Awerbuch)aM Subject: Re: Well Andrew, "3" count them "3" security patches for VMS in fivey= Message-ID: <37486a59.0401121133.3859edbb@posting.google.com>c  C WOW!!!  Talk about truth in advertising!!  My hats are off to KeitheF for being forthright and unambiguous, even as he is gamefully employed by a competitor vendor.h  
 Anyway ...  > I will not get into particulars about how many CERT alerts perE system/vendor per year, or whether these alerts target the base OS vss> add-on packages.  When we step back and take a look at the BIG& picture, we find a simple fact exists.  : In the Systems Programming world that existed prior to theC popularization of the internet, intranets, and free Linux, when thea< vendors were DEC, IBM, HP, DataPoint, Data General, Nixdorf,C Burroughs, NEC, and a bunch of others, before consolidation, beforetE Micro$oft and Linux, VMS was always recognized as the most secure andr* most robust operating system in the world.  F There is no better proof of this statement than that most of the majorD banks, brokerages, and insurance firms (to name a few industries) inC the world (not just NY or the US) - implemented their most critical F business functions first on PDP-11s running RSX-11 and migrated to VMSB on VAXen and then later to Alphas, many of which are still runningB today, all running under OpenVMS:  Funds Transfer, DDA processing;C Securities Transfer, Trading Floor, back office; claims processing,e@ claims payment; this is only a partial list.  Even the early ATM( support networks were developed for VMS!  D Those of you like me, who have been in this industry for 25 years or= more, have time after time run into these work-horse systems,sF stubbornly refusing to go away, because they will be very expensive toC reproduce.  A good part of that expense is the need to ensure theserF newly rewritten application systems remain as secure and robust as theD current production versions.  This is a goal that, while achievable,D has not been as easy to attain on a single platform as it has always" been, and remains to be, with VMS.   Happy Computing!
 Dave Awerbuch  Independent Consultant APC Consulting Services, Inc. 
 New York, USA     E P.S.  For those who don't know me, I am not a VAX specialist.  I havet
 worked on:F - DEC pdp-5, pdp-8 (OS/8e), pdp-11 (RT-11, RSTS/E, RSX-11m, Unix), Vax) (VMS/OpenVMS), Alpha (VMS/OpenVMS, WinNT)c@ - IBM System/3, System/34, Series/1 (RPS, EDX), System/88 (NSK),E System/360 (OS/MFT, OS/MVT, DOS, DOS/VSE), System/370 family (OS/VS1,r OS/VS2, OS/MVS, VM)a" - HP 300, 2000, and 3000 family.   - Data General; % - National Semiconductor Datacheckerse	 - etc....n  A I'm not bragging or showing off, I'm just documenting that I have F worked on a lot of different multi-tasking systems, not just little PC ones and not just VMS ones.c  @ P.S.S.  RSTS and RSX-11 are alive and well, being MAINTAINED andE SUPPORTED by Mentec. Inc. (http://www.mentec-inc.com/RSTSSW.html).  Iu? would not be surprised to see a company like that take over VMStA support for the VAX when HP decides it will no longer support itsG loyal DEC customers.     ----- original message -----  3 X-News: eisner.encompasserve.org comp.os.vms:293007 0 From: keith.cayemberg@conti.de (Keith Cayemberg)E Subject: Re: Well Andrew, "3" count them "3" security patches for VMSr in five Date: 9 Jan 2004 11:02:00 -0800a= Message-ID: <3a65a5c8.0401091049.199aa813@posting.google.com>,   > > F > > listen Andrew, VMS security mup kits are rarely issued, and don't 6 > > confuse ucx flaws with VMS os and kernel flaws ... >  > G > Aah, that old chestnut.  Whenever you discuss security with VMS guys eE > they always trot it out.  Does that mean we can take your figure of C > 1000+ solaris holes and cross off anything not in the kernel ? :)   u keith.cayemberg@conti.de (Keith Cayemberg) wrote in message news:<3a65a5c8.0401091049.199aa813@posting.google.com>...o > R > Yes, but first redesign and rewrite your unix to cleanly catagorize and separateP > Kernel Mode from Supervisor Mode and from User Mode. Three modes are a minimumQ > for a correct ring protection system. The use of three or more rings happens toDK > be a fully patented methodology by OpenVMS Engineering. OpenVMS has four. Q > OpenVMS also has 40 groups of higher mode functionality classified as requiringn > special named privileges.  >  > And, then... > I >  - allow access to higher mode services only through a DESCRIPTOR-based O >    calling standard which rules out "by design" the primary cause of security N >    holes - buffer-overflows. The secure Calling Standard is a central design >    theme in OpenVMS. > H >  - rewrite and install your TCP/IP stack so that it doesn't live in orN >    directly access kernel mode services except through the calling standard.B >    If the previous condition was met, your tcp/ip stack probablyF >    won't work in Supervisor mode or User Mode without these changes.D >    This is the reason why most security holes for which OpenVMS isC >    affected does not in fact lead to a security vulnerability. In-H >    this sense I agree with Andrew. Security vulnerability listings areI >    innaccurate for OpenVMS. Because they do not correctly differentiate4G >    whether only a user-mode process can be affected or a higher mode,cF >    and whether a higher privilege can be attained. A correct listingI >    must rate the severity of the security hole. In OpenVMS the severity G >    is usually lower (or meaningless) in comparison to other operatingd
 >    systems.c > H >  - design privilege assignments to be attached to a mode. If a programE >    installed in a higher mode breaks out to a user-mode prompt. All K >    privileges assigned during the program run must be automatically lost.eJ >    This prevents program privilege tailgating. OpenVMS Hackers (yes theyI >    do exist, an admirably persistent if unsuccessful lot) have recentlyeI >    discovered this functionality in OpenVMS, inwhich they intentionally-P >    installed an application with privileges and with a buffer overflow leadingG >    to a DCL prompt. Their experiment failed. This OpenVMS "knockdown"DC >    functionality can also be extended to disable the privilege ofnL >    receiving a DCL Prompt when breaking out of a program or DCL procedure,G >    just by assigning the CAPTIVE and RESTRICT flags to user accounts.S > K >  - design your Unix to provide only strictly separated (and from overflow I >    controlled) user and system stacks to prevent stack crashing leadingd( >    to access to higher mode functions. > H >  - lets also not forget a redesign of the internal logon  mechanism to >    be carried out by one > J > These are only a few of the unique, patented design decisions in OpenVMSE > resulting in a world-beating matrix of Functionality, Reliability, tF > Availability, Security, Stability, and Scalability(RT, APMP, SMP andQ > Cluster). It's an OS that was "Designed" first by 4 competing teams of experts,lI > and then the best results of these competing design teams merged into aaN > final design team. They knew of the older Unix, MVS and Multics designs, andF > naturally they innovated and improved on them for the Enterprise OS  > problem space. > C > When you are done making these elementary design changes to Unix sM > (many of which were intentionally excluded or ignored by the Unix designershH > in 1969 - Multics already had early forms many of them) you will find L > most of the commercial products on the Unix Market will no longer functionH > correctly on your New-Unix, and will also require a redesign, and then > a rewrite. > A > But at least you will finally have an OS and TCP/IP stack whichlL > "begins" to technically compare with OpenVMS within the frame of security.H > And you'll have a product which pays royalties to OpenVMS Engineering. > H > Each OS has it's strengths and weaknesses in design and implementationG > which will have a different evaluation depending on the problem space)L > it will be applied to, and depending on the design goals of the designers.L > For the general Enterprise OS problem space, I believe OpenVMS EngineeringI > has most consistently made the best decisions in design and implementediA > them with an admirably consistent high quality and methodology.i > G > OpenVMS enthusiasts can righteously bemoan that the Computer Science  L > Profession (Informatics) have failed to recognize and teach their studentsE > the sophisticated mechanisms and high principals found in OpenVMS, aF > preferring instead to favoritize the minimalistic asthetics of Unix,G > or the marketing level sophistication in OS selection. This is a realcJ > loss for enterpise efficiency (money), mission-critical system stabilityH > (lives), and the computer science profession (maturity as a science). J > A more balanced and impartial framework of scientific thought is needed.H > Computer Science needs some independence from commercial and marketingM > interests to even discover the value of many existing designs, technologiesfF > and ideas. The last major papers over OS design were written over 101 > years ago, but their work is far from complete.e > C > Critics of OpenVMS should first study and compare it's internals  G > (Professional OS comparisons and choices should not be reduced to an lC > application layer beauty contest) with an open mind concering OS s@ > design paradigms, system operations principals and reliability > methodologies.M > After recovering from the shock, they will likely no longer be as critical.n > 	 > Cheers!h >  > Keith Cayemberg,+ > IBM Business Services - Hannover, Germanyt >  > Semi-Nonstandard Disclaimer:5 > Any non-official claims concerning my semi-officialm- > opinions are hereby officially disclaimed. t" > i.e. I said it, not my employer.2 > (and no I didn't steal this one from Yogi Berra) > A > I welcome rebuttal, however a lack of response on my part only  @ > indicates a lack discretionary time to indulge in discussions ) > peripheral to my employment activities.-   ------------------------------   End of INFO-VAX 2004.024 ************************