1 INFO-VAX	Wed, 29 Aug 2001	Volume 2001 : Issue 479       Contents:$ 100 million sale for Compaq to Sabre# Re: a bit of historical perspective  alpha - ia64 Re: alpha - ia64 Re: alpha - ia64 Re: alpha - ia64 Re: alpha - ia64 Re: alpha - ia64  Re: backup software - 3rd party?$ Re: Compaq staff walk out of meeting$ Re: Compaq staff walk out of meeting, Re: Compaq to add non-MS icons to Windows XP, Re: Compaq to add non-MS icons to Windows XP, Re: Compaq to add non-MS icons to Windows XP, Re: Compaq to add non-MS icons to Windows XP, Re: Compaq to add non-MS icons to Windows XP) Re: Conference: CETS-2001 Detailed Update ) Re: Conference: CETS-2001 Detailed Update  DCLTABLES on OpenVMS 7.2-1 Re: DCLTABLES on OpenVMS 7.2-1 dynamic dcl menu Re: dynamic dcl menu Re: dynamic dcl menu Re: dynamic dcl menu2 Elsa Gloria Synergy Graphics Controller in my DS106 Re: Elsa Gloria Synergy Graphics Controller in my DS106 Re: Elsa Gloria Synergy Graphics Controller in my DS10 Re: EV7 will never ship? Re: EV7 will never ship? Re: EV7 will never ship? Re: EV7 will never ship? Re: EV7 will never ship? Re: EV7 will never ship? Re: EV7 will never ship? Re: EV7 will never ship? Re: EV7 will never ship?  Re: Feeling Better about Itanium  Re: Feeling Better about Itanium  Re: Feeling Better about Itanium  Re: Feeling Better about Itanium  Re: Feeling Better about Itanium  Re: Feeling Better about Itanium  Re: Feeling Better about Itanium  Re: Feeling Better about Itanium! Gateway lays off 25% of workforce ; Re: Looking for Digital Serial Number Identication Resource ; Re: Looking for Digital Serial Number Identication Resource ; Re: Looking for Digital Serial Number Identication Resource 1 Re: MicroVAX II - local register I/O programming? 1 Re: MicroVAX II - local register I/O programming? 1 Re: MicroVAX II - local register I/O programming?  My VMS Wish List (features)  Re: My VMS Wish List (features) > Re: OpenVMS Common Source Code? (was Re: EV7 will never ship?)* Re: still can't get my UCX licensed??????? Re: TCPIP V5.0 BIND question9 Using OpenVMS & DECprint with mid to high-speed printers.  Re: V5.5-2 Password Recovery Re: V5.5-2 Password Recovery Re: V5.5-2 Password Recovery VMS Sessions at CETS Re: VMS Sessions at CETS4 VMS's Last Stand or Conspiracy/Stupidity Theories...8 Re: VMS's Last Stand or Conspiracy/Stupidity Theories...4 Re: Wailing at Eunuchs (was: Wailing and Moaning...)' Re: Why continue with OpenVMS / Compaq? : Re: [Q]: How to get BACKUP to relabel tapes automatically?  F ----------------------------------------------------------------------  % Date: Wed, 29 Aug 2001 00:58:18 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca> - Subject: 100 million sale for Compaq to Sabre , Message-ID: <3B8C7664.D6E0BFD7@videotron.ca>  8 http://www.newswire.ca/releases/August2001/28/c2865.html  G Tandem replaces some of the Sabre applications that were on mainframes.   J Interesting that Compaq mentions that its migrating its 64 bit platform toM IA64 was a positive in this contract since  Tandem doesn't yet run on 64 bits 
 (right ?).  N This contract says a lot though about what potential customers see as a viableL platform.  Tandem is generally much more expensive, especially when you need$ lots of horsepower, compared to VMS.  N I wonder if VMS was even considered by SABRTE and/or Compaq for this contract.   ------------------------------  # Date: Tue, 28 Aug 2001 20:55:16 GMT   From: jlsue <jlsuexxxz@home.com>, Subject: Re: a bit of historical perspective8 Message-ID: <g41oot0v37ibdol6rjpcpa90rl217digdc@4ax.com>  7 On Mon, 27 Aug 2001 20:39:01 -0500, "David J. Dachtera"  <djesys.nospam@fsi.net> wrote:   >Marty Kuhrt wrote:  >>  _ >> In article <3B7D5458.3FC19B2A@videotron.ca>, JF Mezei <jfmezei.spamnot@videotron.ca> writes:  >> > Alan Greig wrote:E >> >> The Federal Trading Commission (FTC) is making an extraordinary L >> >> condition on Digital's sale of its semiconductor operations to Intel - >> > >> >> So much for regulation.  >> >P >> > Compaq is based in Texas. The person currently living in the White House is >> > based in Texas. >>   >> Using your logic... >>  L >> You're from Canada, and so is Terry Jacks, the guy who performed "SeasonsI >> in the Sun".  Finally, I have someone to blame for that horrible song!  > 3 >WOW! Now *THAT* is a *LONG* time to hold a grudge!   / Maybe, but it's hard to blame him. on this one.    ------------------------------  # Date: Tue, 28 Aug 2001 22:16:33 GMT , From: peterw@u.genie.co.uk (Peter Watkinson) Subject: alpha - ia64 7 Message-ID: <3b8c1543.16021359@news.cable.ntlworld.com>    Hi,   E One thing that confuses me about the intel swallowup of Alpha is that A with IA64 being EPIC and not RISC and AMD bringing out the Hammer D range of cpu's Intel will still be in a similar situation to that itF is in now having to cut chip prices heavily to compete with AMD. I putD this down to the fact that IA64 was designed when Alpha was still onC NT and thus Intel needed to go the EPIC route to compete with FX32. E Now that AlphaNT is no longer Intel is stuck with a cpu that needs to D be able to run 32bit code when if Alpha had never existed they couldE have produced a RISC cpu. And they are still stuck in a dogfight with F AMD when with their tyins with M$ they could have produced a processor without any legacy hiccups.   @ Looking into the future maybe one route for Intel a) could be to re-release Alpha (dream on)   F or b) could be to produce a brand new RISC cpu maybe 128bits if such a8 thing is possible to leave the competition (AMD) behind.     who knows...............  	  regards,      Peter Watkinson  peterw@u.genie.co.uk http://www.pwnavigate.com/% http://www.windsurf-international.com  http://you.genie.co.uk/peterw/$ http://www.freerider-classifieds.com   ------------------------------  # Date: Wed, 29 Aug 2001 01:48:14 GMT & From: "Smitty" <someone@microsoft.com> Subject: Re: alpha - ia64 @ Message-ID: <yRXi7.159620$Xr6.898841@news-server.bigpond.net.au>  9 "Peter Watkinson" <peterw@u.genie.co.uk> wrote in message 1 news:3b8c1543.16021359@news.cable.ntlworld.com...  >  >  > Hi,  > G > One thing that confuses me about the intel swallowup of Alpha is that C > with IA64 being EPIC and not RISC and AMD bringing out the Hammer   C The EPIC technology used in the IA-64 Itanium's is superior to RISC 
 architechure.     F > range of cpu's Intel will still be in a similar situation to that itH > is in now having to cut chip prices heavily to compete with AMD. I putF > this down to the fact that IA64 was designed when Alpha was still onE > NT and thus Intel needed to go the EPIC route to compete with FX32. G > Now that AlphaNT is no longer Intel is stuck with a cpu that needs to F > be able to run 32bit code when if Alpha had never existed they couldG > have produced a RISC cpu. And they are still stuck in a dogfight with H > AMD when with their tyins with M$ they could have produced a processor > without any legacy hiccups.   ; You won't get legacy hiccups with the Intel IA-64.  It is a K fully-functioning 64bit EPIC system, which has the ability to emulate 32bit H instructions....  This is a big advantage for Intel, not a disadvantage.   > B > Looking into the future maybe one route for Intel a) could be to > re-release Alpha (dream on)  > H > or b) could be to produce a brand new RISC cpu maybe 128bits if such a: > thing is possible to leave the competition (AMD) behind. >   L 128bits?  Ahhh.. you obviously don't even know how much trouble a 64bit chip is....J Intel is well ahead of schedule with it's IA-64 chip, and unless AMD pullsI something very special out of the box, Intel looks like it's on a winner.    >  > who knows............... >  >  regards,  >  >  > Peter Watkinson  > peterw@u.genie.co.uk > http://www.pwnavigate.com/' > http://www.windsurf-international.com   > http://you.genie.co.uk/peterw/& > http://www.freerider-classifieds.com   ------------------------------  + Date: Wed, 29 Aug 2001 03:31:00 +0000 (UTC)   From: mustang@ucc.asn.au.invalid Subject: Re: alpha - ia64 * Message-ID: <9mhnlk$10o$1@enyo.uwa.edu.au>  4 In comp.os.vms Smitty <someone@microsoft.com> wrote:  ; : "Peter Watkinson" <peterw@u.genie.co.uk> wrote in message 3 : news:3b8c1543.16021359@news.cable.ntlworld.com...  :> :> :> Hi, :>H :> One thing that confuses me about the intel swallowup of Alpha is thatD :> with IA64 being EPIC and not RISC and AMD bringing out the Hammer  E : The EPIC technology used in the IA-64 Itanium's is superior to RISC  : architechure.   % That's somewhat subjective, isn't it?    [snippy, snippy, snippy]  = : You won't get legacy hiccups with the Intel IA-64.  It is a M : fully-functioning 64bit EPIC system, which has the ability to emulate 32bit J : instructions....  This is a big advantage for Intel, not a disadvantage.   Modulo compiler performance.  C :> Looking into the future maybe one route for Intel a) could be to  :> re-release Alpha (dream on) :>I :> or b) could be to produce a brand new RISC cpu maybe 128bits if such a ; :> thing is possible to leave the competition (AMD) behind.  :>  N : 128bits?  Ahhh.. you obviously don't even know how much trouble a 64bit chip : is....  C Yes - what's a 128-bit arch going to buy you, save bragging rights?   L : Intel is well ahead of schedule with it's IA-64 chip, and unless AMD pullsK : something very special out of the box, Intel looks like it's on a winner.   O Umm, is this some schedule that comp.os.vms readers were previously unaware of? P Ahead of schedule, you say... all those "Merced/Itanium slips again!" posts were hallucinations, I guess.   D. --  ! I don't get mad.... I get stabby.    ------------------------------  % Date: Wed, 29 Aug 2001 03:24:43 +1200 # From: Bruce Hoult <bruce@hoult.org>  Subject: Re: alpha - ia64 = Message-ID: <bruce-02629E.03244329082001@news.akl.ihug.co.nz>   A In article <yRXi7.159620$Xr6.898841@news-server.bigpond.net.au>,  ' "Smitty" <someone@microsoft.com> wrote:   6 > Intel is well ahead of schedule with it's IA-64 chip  H That's a quite astounding statement.  Quite sufficient to make the rest $ of your statements tainted, in fact.   -- Bruce   ------------------------------  % Date: Wed, 29 Aug 2001 01:40:29 -0400 ' From: "Bill Todd" <billtodd@foo.mv.com>  Subject: Re: alpha - ia64 ( Message-ID: <9mhv74$nis$1@pyrite.mv.net>  1 "Smitty" <someone@microsoft.com> wrote in message : news:yRXi7.159620$Xr6.898841@news-server.bigpond.net.au...   ...   E > The EPIC technology used in the IA-64 Itanium's is superior to RISC  > architechure.   K Thanks:  it's really a relief to have an authoritative source put an end to  all this speculation.    ...   = > You won't get legacy hiccups with the Intel IA-64.  It is a G > fully-functioning 64bit EPIC system, which has the ability to emulate  32bit J > instructions....  This is a big advantage for Intel, not a disadvantage.  A Especially since while performing such emulation it will make the I performance of the past 5 years' worth of old, abandoned Intel boxes look  *really good*.   ...   7 > Intel is well ahead of schedule with it's IA-64 chip,   H This was the point at which I *knew* you had just forgotten to include a bunch of smileys...    - bill   ------------------------------  # Date: Wed, 29 Aug 2001 05:41:50 GMT  From: Dirk Munk <munk@home.nl> Subject: Re: alpha - ia64 ' Message-ID: <3B8C80A2.CAF70964@home.nl>    Peter Watkinson wrote:   > Hi,  > G > One thing that confuses me about the intel swallowup of Alpha is that C > with IA64 being EPIC and not RISC and AMD bringing out the Hammer F > range of cpu's Intel will still be in a similar situation to that itH > is in now having to cut chip prices heavily to compete with AMD. I putF > this down to the fact that IA64 was designed when Alpha was still onE > NT and thus Intel needed to go the EPIC route to compete with FX32. G > Now that AlphaNT is no longer Intel is stuck with a cpu that needs to F > be able to run 32bit code when if Alpha had never existed they couldG > have produced a RISC cpu. And they are still stuck in a dogfight with H > AMD when with their tyins with M$ they could have produced a processor > without any legacy hiccups.  > B > Looking into the future maybe one route for Intel a) could be to > re-release Alpha (dream on)  > H > or b) could be to produce a brand new RISC cpu maybe 128bits if such a: > thing is possible to leave the competition (AMD) behind.  B There is no reason for a 128 bit processor. 64 bit processors wereD developed for their memory addressing range, not for speed. A 64 bitF processor is not that much faster as a well designed 32 bit processor.  ? And guess where the enigineers came from who developed the very J successfull AMD K7 range ?   Yes, from the same group of people "who could& not keep up" with the IA64 developers.       >  >  > who knows............... >  >  regards,  >  > Peter Watkinson  > peterw@u.genie.co.uk > http://www.pwnavigate.com/' > http://www.windsurf-international.com   > http://you.genie.co.uk/peterw/& > http://www.freerider-classifieds.com   ------------------------------  # Date: Tue, 28 Aug 2001 20:51:22 GMT 6 From: "Andy Bustamante" <a_c_bustamante@earthlink.net>) Subject: Re: backup software - 3rd party? D Message-ID: <evTi7.1844$aC1.176202@newsread1.prod.itd.earthlink.net>  L OpenVMS comes with an integrated backup utility called "BACKUP."  The systemH manager's manual and the DCL dictionary provide documentation.  For veryJ large sites, tape loader (Robo) management software can add functionality,< but BACKUP will preservere your data if used correctly. What  J I had a storageworks salescritter come by the office last month, the firstI question he had was which backup product we used, exciting new news about F Veritas integration.  I explained that we wouldn't install an o/s that8 shipped without a backup solution, we're a VMS reseller.   -- Andy Bustamante  Remove the ASCII 95s to reply       K "Mike Scott" <msaxys@hotmail.com> wrote in message news:3b8bbf12@nubby2.... K > Does anyone know what the most popular 3rd party backup software solution 4 > currently in use is?  We use OpenVMS 7.1 on Alpha. > -many thanks.  >  >    ------------------------------  % Date: Tue, 28 Aug 2001 17:07:35 -0400 ' From: "Bill Todd" <billtodd@foo.mv.com> - Subject: Re: Compaq staff walk out of meeting ( Message-ID: <9mh15g$p38$1@pyrite.mv.net>  ; "Fabio Cardoso" <fabiopenvms@yahoo.com.br> wrote in message 9 news:20010828110720.1493.qmail@web20205.mail.yahoo.com...  People  1 Did you notice that IT people are the new SLAVES, 4 independet of color of skin, religion, ethnic group, etc...   *****   ( To answer your question:  No, I did not.   *****   4 IT Companies are like big farms, and the "owner" can6 sell their slaves and parts of the farms to the others2 farmers... sometimes they burn all the farm. A few5 SLAVES try to escape, but almost 90% dont know how to & work and survive outside the farms....   *****   H That's too bad, but hardly the fault of the company:  there's really notH much it can do if such people *choose* to act like slaves, and a lot theC people can do for themselves if they don't want to act like slaves.   I I certainly don't like a lot of the ways in which companies act, but have L little sympathy with complaints from reasonably well-educated and relativelyK highly-paid individuals who think such companies owe them their life-style, : rather than feel responsible for managing their own lives.   - bill   ------------------------------  # Date: Wed, 29 Aug 2001 02:49:57 GMT ' From: ben_myers@charter.net (Ben Myers) - Subject: Re: Compaq staff walk out of meeting 0 Message-ID: <3b8c578c.48370535@news.charter.net>  @ Yep, the CEOs and their buddies walk away with all the bucks forF running underperforming companies.  The stockholders and the employees get shafted.    E Check out the $1B paid to the two honchos at Computer Associates over B the last five years, as the company has slowly been sliding deeperE into the toilet amid accusations of sharp accounting practices... Ben  Myers   & Isn't a free market economy wonderful?  B On Tue, 28 Aug 2001 13:03:56 GMT, dragon <dragon@vt82.nuts> wrote:   >Interesting thoughts. >  >But the real action IS: > P >Study: CEOs still getting big pay as more workers get the ax in sagging economy3 >By Marcy Gordon, Associated Press, 8/28/2001 05:20.O >WASHINGTON (AP) As the economy began to stall last year and companies laid offhR >workers, chief executives of big corporations still got hefty pay raises and wereW >rewarded for making job cuts, according to a new study by two liberal advocacy groups.R > V >A ''decade of greed'' in the 1990s was followed last year by a particularly ''blatantQ >pattern of CEOs benefitting at the expense of their workers,'' the Institute fornT >Policy Studies and United for a Fair Economy said in their latest annual pay survey >released Tuesday. >oV >It found that chief executives of the 52 major companies that announced layoffs of atW >least 1,000 employees in the first half of 2000 earned some 80 percent more on average)S >than CEOs at 365 big corporations surveyed by Business Week magazine. The ''layoffbU >leaders'' received an average $23.7 million in total compensation, including bonusestP >and stock options, compared with an average $13.1 million for CEOs overall, the >groups' study found.b >gU >It said the top job-cutters got an average increase in salary and bonus of nearly 20pR >percent last year, compared with average raises for U.S. wage earners of around 38 >percent and 4-percent increases for salaried employees. >eO >Sarah Anderson, director of the global economy program at the Washington-basedpQ >Institute for Policy Studies, said it was galling ''especially in this period ofeT >economic downturn as people are feeling very insecure about their jobs, to see that1 >the guys at the top have cushioned themselves.'': >pQ >The yearlong economic slump is taking a toll on the nation's labor markets. LasttN >Thursday, the government reported that the number of laid-off workers drawingU >unemployment benefits had hit a nine-year peak. The Labor Department said the numbertV >of Americans collecting jobless benefits rose to 3.18 million in the week ending Aug.V >11, the highest level since September 1992, when the country was struggling to emerge >from the last recession.B > W >Against that backdrop, compensation packages for executives have drawn some criticism.e >.W >After attorneys for troubled bicycle maker Schwinn/GT asked a bankruptcy judge to keepnM >confidential the details of a $2 million bonus plan for its top managers and W >executives, he questioned the plan's fairness to rank-and-file employees and expressed 8 >reservations about keeping the information under wraps. > U >''I'm going to do a little research,'' U.S. Bankruptcy Judge Sidney Brooks in DenvercS >said last week, delaying immediate approval. ''There are some pretty hefty bonuses.N >here.'' Schwinn attorneys said the compensation plan was designed to keep keyP >personnel from quitting while the bike maker goes through Chapter 11 bankruptcy >reorganization. >nR >The Conference Board, a business organization, has criticized the liberal groups'U >executive pay surveys in the past because they include stock options for CEOs, whosei- >value can fluctuate depending on the market.- >-R >Spokesmen for the New York-based Conference Board had no immediate comment on the >latest survey.c >R >The survey also said: >DT >If the federal minimum wage, which was $3.80 an hour in 1990, had grown at the sameT >rate as executive pay over the decade, it now would be $25.50 an hour as opposed to >the current $5.15.n >gU >The 30 highest-paid women in big corporations each earned average total compensationtU >of $8.7 million last year, compared with $112.9 million for the 30 highest-paid men.  >t >On the Net:4 >Institute for Policy Studies: http://www.ips-dc.org6 >United for a Fair Economy: http://www.FairEconomy.org5 >The Conference Board: http://www.conferenceboard.org  >p >Ben Myers wrote:  >aG >> Compaq already sold a lot of engineers to Intel with the property inpE >> Hudson, MA originally used for Alpha R&D and chip production.  Not G >> sure how many real engineers they have left, except to deal with thehA >> companies to whom the manufacturing is farmed out... Ben Myerso >>/ >> On Mon, 27 Aug 2001 13:15:39 -0400, JF Mezeia( >> <jfmezei.spamnot@videotron.ca> wrote: >>O >> >Since Compaq no longer needs any fancy R&D, I wouldn't be surprised if thisiI >> >type of presentation wasn't intentionally setup to give these uselesse. >> >scientists a hint of where they should go. >> >Q >> >It costs a lot less to have a useless employee decide to quit on his own than 4 >> >to have to let him go and pay severance package. >> >P >> >Perhaps Compaq had tried to "sell" them to Intel but Intel didn't need them,U >> >so now Compaq will make their life not so happy and they will leave on their own.. >> >L >> >Interesting 180 day transformation. Compaq is really getting back to its >> >former pre-digital self. >> >> Ben Myers >> Spirit of Performance, Inc. >> 73 Westcott Road  >> Harvard, MA 01451 >> tel: 978-456-3889 >> eFax: 810-963-0412-# >> PayPal, MC, VISA, AMEX accepted.  >   	 Ben Myers  Spirit of Performance, Inc.a 73 Westcott Road Harvard, MA 01451t tel: 978-456-3889  eFax: 810-963-0412 4  PayPal, MC, VISA, AMEX accepted.   ------------------------------  # Date: Tue, 28 Aug 2001 20:37:20 GMTA= From: system@SendSpamHere.ORG (Brian Schenkenberger, VAXman-)v5 Subject: Re: Compaq to add non-MS icons to Windows XP(0 Message-ID: <00A01368.2B764285@SendSpamHere.ORG>  j In article <73Oi7.877$bB1.41553@news.cpqcorp.net>, "Fred Kleinsorge" <kleinsorge@star.zko.dec.com> writes:% >Alan E. Feldman wrote in message ...h >>D >>So, if Compaq is effectively just part of MS, why are they puttingB >>AOL, Disney, and other icons on their Windows XP desktop when MSE >>clearly doesn't want any icons but its own? And why did they choosea+ >>AOL over msn? And why not a VMS icon? ;-)M >>@ >>I guess they just don't like VMS, period. Supreme bummer. :-(( >> >  >sG >I think there is a lot of information out there on why the AOL icon is M >financially beneficial.  But exactly what would a "VMS" icon on a XP desktop  >do?  D Blue Screen of Death the PC and then cause an automatic reboot to a D banner that says: "VMS wouldn't let you down like your PC just did!" --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COMv            bJ   "And of course, I'm a genius, so people are naturally drawn to my fiery I   intellect.  Their admiration overwhelms their envy!" -- Calvin & Hobbesd   ------------------------------  % Date: Tue, 28 Aug 2001 16:57:05 -0400 0 From: Paul Anderson <paul.r.anderson@compaq.com>5 Subject: Re: Compaq to add non-MS icons to Windows XPe; Message-ID: <280820011657057717%paul.r.anderson@compaq.com>m  F In article <00A01368.2B764285@SendSpamHere.ORG>, Brian Schenkenberger,( VAXman- <system@SendSpamHere.ORG> wrote:  F > Blue Screen of Death the PC and then cause an automatic reboot to a F > banner that says: "VMS wouldn't let you down like your PC just did!"   Perfect!   Paul   -- t  Paul Anderson   OpenVMS Engineeringy   Compaq Computer Corporation    ------------------------------  % Date: Tue, 28 Aug 2001 17:10:00 -0400v- From: JF Mezei <jfmezei.spamnot@videotron.ca>a5 Subject: Re: Compaq to add non-MS icons to Windows XPl, Message-ID: <3B8C0893.C68575E0@videotron.ca>   "Alan E. Feldman" wrote:H > Maybe I'm mistaken, but putting AOL front and center on the Windows XP0 > desktop -- I don't see how MS could like that.  H Yes, MS likes that. MS sees this token irrelevant move to give Windows aM facade that is more politically correct, featuring all of MS's competitors onOQ the default desktop to be beneficial since it keeps the anti-trust  lawyers away.n  L Desktop icons are irrelevant, especially to those who upgrade machines since. they already have their subscriptions etc etc.  L Consider the possibility that while that ALO icon may appear on the desktop,L it doesn't prevent Compaq from providing an MSN CD/booklet with some sort ofF deal for free subscription for a certain amount of time as part of the
 computer box.v   ------------------------------  % Date: Tue, 28 Aug 2001 16:52:17 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca> 5 Subject: Re: Compaq to add non-MS icons to Windows XPb, Message-ID: <3B8C046E.BD5F5EE4@videotron.ca>   Fred Kleinsorge wrote:H > I think there is a lot of information out there on why the AOL icon isN > financially beneficial.  But exactly what would a "VMS" icon on a XP desktop > do?f   A big splash screen:  N "COMING SOON, TO AN INTEL BOX NEAR YOU, a ROBUST OPREATING SYSTEM THAT DOESN'TG NEED THE ALT-CTRL-DEL KEY SEQUENCE TO BE HIT AT REGULAR INTERVALS, stayo9 tuned.... you will soon be liberated from Microsoft junk"    ------------------------------  % Date: Tue, 28 Aug 2001 17:25:29 -0400S' From: "Bill Todd" <billtodd@foo.mv.com>V5 Subject: Re: Compaq to add non-MS icons to Windows XPe( Message-ID: <9mh273$r49$1@pyrite.mv.net>  : "Alan E. Feldman" <afeldman@gfigroup.com> wrote in message7 news:af1e4ce6.0108280528.2dcef437@posting.google.com...l   ...m  D > So, if Compaq is effectively just part of MS, why are they puttingB > AOL, Disney, and other icons on their Windows XP desktop when MSE > clearly doesn't want any icons but its own? And why did they chooser+ > AOL over msn? And why not a VMS icon? ;-)l >v@ > I guess they just don't like VMS, period. Supreme bummer. :-((  I I think you've got it.  The theory that Compaq's neglect of VMS is due toeE Microsoft pressure is far from universally held, and does not explainnI Compaq's willingness to treat other non-Microsoft products (such as Tru64r/ and NSK) with at least noticeably less neglect.   I Which is hardly to say that Compaq isn't quite solidly in bed with MS, ofoD course.  But I suspect that MS just doesn't consider VMS any kind ofI credible threat to its immediate markets:  only if Windows ever fielded aOD serious enterprise system *and* Compaq ever vigorously developed and8 marketed VMS would that situation seem likely to change.   - bill   >r > Dislcaimer: JMHO > Alan E. Feldman  > afeldman@gfigroup.com    ------------------------------  # Date: Wed, 29 Aug 2001 05:32:46 GMT?& From: "Jeff Killeen" <Jeff@IDM-IO.com>2 Subject: Re: Conference: CETS-2001 Detailed Update8 Message-ID: <28%i7.1110$p81.555589@typhoon1.gnilink.net>  2 "Bill Todd" <billtodd@foo.mv.com> wrote in message" news:9mbdrn$1gn$1@pyrite.mv.net... >a3 > "Jeff Killeen" <Jeff@IDM-IO.com> wrote in message'4 > news:un4i7.1903$Ia1.338158@typhoon1.gnilink.net... > >  Yes what you say:K > > is true if you look at the kernel level but if you have ever dealt withHL > > Microsoft at the applications development level Microsoft is the king ofA > > "just kidding" technical shifts (lies as you would call them)0 >0K > No, I wouldn't call them lies at all - unless you can point to statementsmD > Microsoft has offered (similar to those in the Heil/Lipcon letter)< > guaranteeing the stability of its development environment. >tL > There's a big difference between breaking existing applications (even justG > to the point where they must be recompiled - if possible - to performrL > acceptably) and requiring developers to acquire new skills if they want toK > upgrade to a new development environment (rather than just continue usingsF > their existing development environment, which continues to work just fine).  H I think it has become fairly clear that you have had little nitty grittyI hands-on development expereince in these environments.  In fact Microsoft-B did exactly what you accused Compaq of doing - they broke existingH application and impacted proformance.  For example the latest version ofI MDAC replacing DAO 3.51 with DAO 4.0 out from under existing applicationsg and breaking them...   ------------------------------  # Date: Wed, 29 Aug 2001 05:49:02 GMTe& From: "Jeff Killeen" <Jeff@IDM-IO.com>2 Subject: Re: Conference: CETS-2001 Detailed Update8 Message-ID: <in%i7.1113$p81.558946@typhoon1.gnilink.net>  L I would strongly suggest the Bill Todd's of this world read the note below -K it confirms that Sun has not been the last word in architectures forever aseJ some have suggested.  This most interesting statement in the posting is...  =     "but even then it wasn't the same kind of "dead end" that 3     VMS or Tru64 UNIX customers are thinking may bey     coming in a couple years"S  J ...that statement would have been totally dead on if it said "the dead endK >>>some<<< customers are thinking may be coming in a couple years".  And ofiG course if one guesses at the worse of case and treats it as proven fact K Compaq comes out looking terrible.  But the fact is at this point they havenF not dead ended Tru64 or VMS.  The fact is if they execute as plan (andL without attempting to play license games) the switch from Alpha to IA64 willG far less painful than the switch Sun  users had to go through when theyt+ switched from BSD SunOS 4.x to Solaris 2.x.   L The response to this will be - prove Compaq won't dead end Tru64 or OpenVMS.L Of course one can't prove a negative and I won't try.  OpenVMS and Tru64 areG not Alpha - nothing to date has shown Compaq has any desire to dead endmJ Tru64 or OpenVMS.  Killing Alpha is not evidence of dead ending OpenVMS orJ Tru64 - if killing the chip OpenVMS runs on was proof of death the OpenVMS5 would be dead today from the death of the VAX chip...u    @ "Tim Mooney" <mooney@dogbert.cc.ndsu.NoDak.edu> wrote in message( news:9meigr$jn8$1@news.ndsu.nodak.edu...8 > In article <KiTh7.295$Ia1.66096@typhoon1.gnilink.net>,' > Jeff Killeen <Jeff@IDM-IO.com> wrote:( > > H > > I am firm believer that Compaq's (Digital's) most painful wounds are self > > inflicted. >o8 > :-)  That might be common ground for you and Mr. Todd. >.B > >  I do not claim to be expert on other platforms an but haven'tL > > both IBM and SUN put their customers through major hardware and software0 > > changes that forced source level recompiles? >mH > Sun's move from Motorola 68xxx to sparc in the 80s caused the need forH > customer recompiles, but that's the only case I'm aware of from IBM or Sun.I > I've seen some scary old code from AIX 3.2.x that will still run on AIX  4.3.x,K > and (like Sun) ILP32 binaries will run on a version of the OS that's beencH > booted with an LP64 kernel.  I don't follow IBM's mainframes or AS/400 systemsoI > (or whatever they're calling them these days), so I'm not up on historyt form > them.h >P# > >  If so technically how are theyuC > > any less reliable as a business partner?  I think the answer isw technicallyiL > > they aren't any less reliable but the did it with a lot more finesse and! > > didn't self-inflict wounds...s >wJ > You're right that it's the manner in which it was done that's caused theJ > most concern.  I think when Sun moved from 68xxx to sparc, everyone knewF > in advance the move was coming, the performance benefits at the timeI > were obvious, and Sun made sure that customers knew that 68xxx binariesIJ > would be available during the transition period.  Of these three things,/ > only the last has really been done by Compaq.r > H > Also, especially in Sun's case, they were (and still are) a "one trick pony".G > There was no real concern in anyone's mind that Sun was going to quit  doing C > UNIX and leave customers with a "dead end" after they spent yearss
 transitioning C > to a new architecture.  Of course, it turns out that Sun *did* do 	 somethingeK > like that a few years later (the move from BSD SunOS 4.x to Solaris 2.x),eL > but even then it wasn't the same kind of "dead end" that VMS or Tru64 UNIXJ > customers are thinking may be coming in a couple years.  You could still buyhA > SunOS 4.x for *years* after Solaris was Sun's bread-and-butter.n >nI > Architecture switches have to happen once in a great while, but they'resG > usually only done by a company that you know has a committment to the  productsG > making the switch, and they're done when the need for the arch switch/ becomessL > overwhelmingly obvious to all.  The concerns many Compaq customers have isA > whether that committment truly is there, on the part of Compaq.2 >uJ > As we've seen for the past two months, people are also willing to debateK > whether the need for an arch switch is certain.  Only the brightest AlphaSJ > engineers probably really know for certain, and we'll probably never get2 > to hear their candid answer to that question is. >.K > The question itself is moot, at this point.  The move is going to happen. J > The real question is "What enterprise products will still be alive threeL > or five years after the architecture transition happens?".  I think that's9 > what has a lot of potential Compaq customers concerned.  >0 > Timo > --J > Tim Mooney                              mooney@dogbert.cc.ndsu.NoDak.edu@ > Information Technology Services         (701) 231-1076 (Voice)> > Room 242-J6, IACC Building              (701) 231-8541 (Fax)5 > North Dakota State University, Fargo, ND 58105-5164i   ------------------------------  % Date: Tue, 28 Aug 2001 17:19:30 -0400p, From: "tech support" <tech_support@sp32.com># Subject: DCLTABLES on OpenVMS 7.2-1s! Message-ID: <3b8b9954$1@aerostar>y  K After doing some work with new patches (including update V3) and installinglJ FORRTL V7.3-1, I seem to have caused trouble with DCLTABLES. Any "DISMOUNT  device" commands yield the error    PICARD => dismount SAFE1$MKA600:, %CLI-F-SYNTAX, error parsing 'FORCE_REMOVAL': -CLI-E-ENTNF, specified entity not found in command tables  A Any ideas how to fix this? I have tried rebooting and restoring ar< DCLTABLES.EXE from before the work, all to no avail. Thanks.   Doug K.r SPId   ------------------------------  # Date: Tue, 28 Aug 2001 21:31:04 GMTI2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)' Subject: Re: DCLTABLES on OpenVMS 7.2-1o2 Message-ID: <s4Ui7.899$bB1.41817@news.cpqcorp.net>  P In article <3b8b9954$1@aerostar>, "tech support" <tech_support@sp32.com> writes:L :After doing some work with new patches (including update V3) and installing> :FORRTL V7.3-1, I seem to have caused trouble with DCLTABLES.   B :Any ideas how to fix this? I have tried rebooting and restoring a= :DCLTABLES.EXE from before the work, all to no avail. Thanks.e  B   I will assume you have rebooted when instructed after installingC   specific ECO kits, as trying to "batch" together a series of ECO m%   kits can lead to some odd problems.A  D   It would appear you have applied a shadowing ECO kit here, as the D   /FORCE_REMOVAL was first shipped in a mainline release in OpenVMS    V7.3.d  =   Try reapplying the shadowing and/or MOUNT-related ECO kits.i  B   Do you have multiple DCLTABLES command tables around?  I've seenD   similar problems caused by a (hopefully just old and crufty) copy E   of DCLTABLES in SYS$SPECIFIC:[SYSLIB] -- these extra copies can get E   created by an "incorrect" SET COMMAND command output specification.     N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Wed, 29 Aug 2001 03:05:13 +0800t; From: "Jayasuthan ......" <suthan@eplx01.fairchildsemi.com>a Subject: dynamic dcl menu-O Message-ID: <Pine.LNX.4.33.0108290257200.14995-100000@epss09.fairchildsemi.com>    Hai,  I I working on updating my shell account menu. I try to build script out ofeC DCL that look alike dynamic pages. Not so fancy but consider okey..e  D the problem is that I hving problem with variable. It work like this  3 menu.com --> call var.com gather system informationi,        1]--> call layout.com to display menu6 menu.com <- return back to menu once a inquire is made1        2]--> return back to layout.com to displayO  G Only use single menu.com and it pass variable to layout.com to display.oA Now the problem is that first 1] call variable carried out to 2].:   here is the source:o  $ http://jjsuthan.tripod.com/alpha/vms  H change comdir path in menu.com and layout.com. Access till fullback menu> and return back to main.. the fullback variable still display.   Please help me out.. +------------------------+ ||Jayasuthan             | ||Fairchild Semiconductor| ||System Support	 |t ||http://epss09		 |> ||Tel: 604-8502630 (630) | +------------------------+   ------------------------------  % Date: Tue, 28 Aug 2001 22:40:58 +0200f, From: Didier Morandi <Didier.Morandi@gmx.ch> Subject: Re: dynamic dcl menun& Message-ID: <3B8C01D9.EDD47B4C@gmx.ch>   I jump.t   "Jayasuthan ......" wrote: >  > Hai,   Hi,t  K > I working on updating my shell account menu. I try to build script out of>E > DCL that look alike dynamic pages. Not so fancy but consider okey..o   What is a "shell account menu"?t  E "build script out of DCL": you mean you wish to generate dynamic codet2 from within a DCL command procedure? Child's game.  F > the problem is that I hving problem with variable. It work like this > 5 > menu.com --> call var.com gather system informationi. >        1]--> call layout.com to display menu  D Looks like var.com is another procedure. So, to pass data to anotherG procedure, you need to create global symbols (and NOT use local symbolsI* with the same name within the procedures).  * global symbol example: my_name == "Didier") local symbol example:  my_name = "Didier"-  E Do not do that. never mix local and global symbols with the same nameS5 (sounds to me that this may be one of your problems).c  8 > menu.com <- return back to menu once a inquire is made  G "return back" what? data? how? Could you post your source here? the URLeH you gave returns "Sorry, but the page or file that you're looking for is
 not here".  3 >        2]--> return back to layout.com to displayc  L To display what? A screen of data? a show something output? be more precise.  I > Only use single menu.com and it pass variable to layout.com to display.nC > Now the problem is that first 1] call variable carried out to 2].-  G We can guess that you mother tongue is not English, but even in German,>9 French, Spanish or something else, if you could describe:o   1. what you want to do 2. how you actually do it nowc/ 3. what is wrong in terms of parameters passing?   that would help.   cheers,    D.   ------------------------------  % Date: Wed, 29 Aug 2001 06:51:15 +0200 , From: Didier Morandi <Didier.Morandi@gmx.ch> Subject: Re: dynamic dcl menuA& Message-ID: <3B8C74C2.F2951D97@gmx.ch>   Didier Morandi wrote:r >  > F > Looks like var.com is another procedure. So, to pass data to anotherI > procedure, you need to create global symbols (and NOT use local symbols-, > with the same name within the procedures).  B Someone told me off line that you can pass data via the p1 p2.. p8H parameters. This is useless in this case as you can't get them back whenD you "return" from the called prod to the caller, unless you have set globals symbols for this.n   D.   ------------------------------    Date: 28 Aug 2001 22:25:47 -0700* From: polato@igi.pd.cnr.it (Sandro Polato) Subject: Re: dynamic dcl menuS= Message-ID: <2af2b3d8.0108282125.561526a5@posting.google.com>a   "Jayasuthan ......" <suthan@eplx01.fairchildsemi.com> wrote in message news:<Pine.LNX.4.33.0108290257200.14995-100000@epss09.fairchildsemi.com>... > Hai, > K > I working on updating my shell account menu. I try to build script out ofME > DCL that look alike dynamic pages. Not so fancy but consider okey..  > F > the problem is that I hving problem with variable. It work like this > 5 > menu.com --> call var.com gather system informationl. >        1]--> call layout.com to display menu8 > menu.com <- return back to menu once a inquire is made3 >        2]--> return back to layout.com to displayi > I > Only use single menu.com and it pass variable to layout.com to display.aC > Now the problem is that first 1] call variable carried out to 2].  >  > here is the source:y > & > http://jjsuthan.tripod.com/alpha/vms > J > change comdir path in menu.com and layout.com. Access till fullback menu@ > and return back to main.. the fullback variable still display. >  > Please help me out..  9 I can suggest you to use MenuFinder ... (www.itre.com/mf)t   ------------------------------  % Date: Tue, 28 Aug 2001 21:13:37 +02001  From: Cor Mom <cor.mom@momss.nl>; Subject: Elsa Gloria Synergy Graphics Controller in my DS10n( Message-ID: <3B8BED61.3436727E@momss.nl>   Hi,v  B I know this question has been asked before, but I haven't seen the proper answer.  G I have installed OpenVMS Alpha V7.2-1 on a AlphaServer DS10. The systemlD contains an Elsa Gloria Synergy Graphics Controller. I installed theD VMS721_UPDATE-V0300 patch, which includes the graphic driver. I also9 checked the MGMT24 in the FAQ and made the changes in theAF DECW$PRIVATE_SERVER_SETUP.COM. I changed the console to serial. SYSGENF parameter WINDOW_SYSTEM = 1. The DECW$SERVER_0_ERROR.LOG is completely empty.  H After the system reboots, it comes up, but with a clear (blue) graphicalF screen with the cursor in top-left position. DECwindows is running andG also a _WSA0: process that is running image LOGINOUT.EXE. The graphical1 screen remains empty.n  @ Does any one know what I missed? The rest of the system is fine.   Thanks in advance.   Cor MomO   ------------------------------  # Date: Tue, 28 Aug 2001 19:37:31 GMT 2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)? Subject: Re: Elsa Gloria Synergy Graphics Controller in my DS10u2 Message-ID: <%pSi7.895$bB1.41332@news.cpqcorp.net>  K In article <3B8BED61.3436727E@momss.nl>, Cor Mom <cor.mom@momss.nl> writes:e  H :I have installed OpenVMS Alpha V7.2-1 on a AlphaServer DS10. The systemE :contains an Elsa Gloria Synergy Graphics Controller. I installed therE :VMS721_UPDATE-V0300 patch, which includes the graphic driver. I alsol: :checked the MGMT24 in the FAQ and made the changes in theG :DECW$PRIVATE_SERVER_SETUP.COM. I changed the console to serial. SYSGENrG :parameter WINDOW_SYSTEM = 1. The DECW$SERVER_0_ERROR.LOG is completely  :empty.n :pI :After the system reboots, it comes up, but with a clear (blue) graphicaltG :screen with the cursor in top-left position. DECwindows is running and H :also a _WSA0: process that is running image LOGINOUT.EXE. The graphical :screen remains empty.    I   See "DECW6.  Why is DECwindows Motif not starting?".  Also see Ask The eH   Wizard topics (3419) and (5448).  Also ensure that the system console     is set to the graphic display:       >>> set console graphics     >>> init  C   And which PCI slot is the ELSA GLoria Synergy card residing in?  eG   Which ELSA GLoria Synergy?  (Was this card supplied with the system?)Y  N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Tue, 28 Aug 2001 16:10:02 -0400 , From: "J. Scott Greig" <jsgreig@geminaq.com>? Subject: Re: Elsa Gloria Synergy Graphics Controller in my DS10s0 Message-ID: <7PSi7.421$G94.53929@brie.direct.ca>   FWIW  D Recently, I had a similar problem, and found that  the target system; was missing DECW$LOGINOUT.EXE -- definitely a show stopper.    Scottd  - "Cor Mom" <cor.mom@momss.nl> wrote in message " news:3B8BED61.3436727E@momss.nl... > Hi,n >tD > I know this question has been asked before, but I haven't seen the > proper answer. >hI > I have installed OpenVMS Alpha V7.2-1 on a AlphaServer DS10. The systemtF > contains an Elsa Gloria Synergy Graphics Controller. I installed theF > VMS721_UPDATE-V0300 patch, which includes the graphic driver. I also; > checked the MGMT24 in the FAQ and made the changes in thetH > DECW$PRIVATE_SERVER_SETUP.COM. I changed the console to serial. SYSGENH > parameter WINDOW_SYSTEM = 1. The DECW$SERVER_0_ERROR.LOG is completely > empty. >MJ > After the system reboots, it comes up, but with a clear (blue) graphicalH > screen with the cursor in top-left position. DECwindows is running andI > also a _WSA0: process that is running image LOGINOUT.EXE. The graphicaln > screen remains empty.a >iB > Does any one know what I missed? The rest of the system is fine. >m > Thanks in advance. > 	 > Cor Mome   ------------------------------   Date: 28 Aug 2001 18:51:53 GMT( From: nmm1@cus.cam.ac.uk (Nick Maclaren)! Subject: Re: EV7 will never ship?t0 Message-ID: <9mgp89$4ja$1@pegasus.csx.cam.ac.uk>  3 In article <QxugolYOhXr2@eisner.encompasserve.org>, . Larry Kilgallen <Kilgallen@SpamCop.net> wrote:\ >In article <9mgcm6$ngk$1@pegasus.csx.cam.ac.uk>, nmm1@cus.cam.ac.uk (Nick Maclaren) writes: >r@ >> The thing that is completely crazy is the combination of that@ >> schedule and the projected lifetime of the system.  As anyoneB >> experienced knows, most kernel and compiler tuning problems andD >> nasty bugs do not appear until after a system has hit real users.@ >> In-house testing is just no substitute.  This is particularlyB >> serious because of the magnitude of the SMP changes between the >> EV6 and EV7.r >>  A >> The prospect of buying a system where all software developmentnB >> and probably even all active maintenance has already stopped is8 >> not one that pleases most experienced administrators. >rC >Huh ?  They said they will be using the same source control systemOG >for Alpha and IA64.  That means features (aside from hardware-specificMB >features) will naturally flow to both, until they decide to stop.  C You haven't been there, have you?  I have.  Several times, in fact,h8 and that belief is more wishful thinking than plausible.  @ The first problem occurs with problem reporting.  Things rapidly@ get into a state where, if you can't prove that a problem existsB on the new architecture (even if you are certain that it is), your problem report will be ignored.n  ? The second occurs with problems that are architecture-specific, < as are a great many of the nastier bugs and even more of the= performance problems in the SMP and exception-handling areas,eB compiler, kernel, library and all.  They don't even get looked at.  < Then you get the creeping necrosis effect, which is the real= killer.  A new operating system feature is provided, which is)? very system-dependent internally, so the commercial decision iso= not to waste money on the old system.  Exception handling andS? SMP are particularly relevant, again.  This is then used by thesA language systems (which is why it was wanted in the first place).yB This is then relied on by an application.  Now, you are snookered,8 even if you personally don't need the original facility.     Regards, Nick Maclaren,* University of Cambridge Computing Service,> New Museums Site, Pembroke Street, Cambridge CB2 3QG, England. Email:  nmm1@cam.ac.uk/ Tel.:  +44 1223 334761    Fax:  +44 1223 334679m   ------------------------------    Date: 28 Aug 2001 14:00:16 -0500+ From: young_r@encompasserve.org (Rob Young)o! Subject: Re: EV7 will never ship?s3 Message-ID: <+EaE$Ih1IXSX@eisner.encompasserve.org>n  [ In article <9mgp89$4ja$1@pegasus.csx.cam.ac.uk>, nmm1@cus.cam.ac.uk (Nick Maclaren) writes:q5 > In article <QxugolYOhXr2@eisner.encompasserve.org>,d0 > Larry Kilgallen <Kilgallen@SpamCop.net> wrote:] >>In article <9mgcm6$ngk$1@pegasus.csx.cam.ac.uk>, nmm1@cus.cam.ac.uk (Nick Maclaren) writes:t >>A >>> The thing that is completely crazy is the combination of thatiA >>> schedule and the projected lifetime of the system.  As anyone C >>> experienced knows, most kernel and compiler tuning problems and.E >>> nasty bugs do not appear until after a system has hit real users. A >>> In-house testing is just no substitute.  This is particularlysC >>> serious because of the magnitude of the SMP changes between theu >>> EV6 and EV7. >>> B >>> The prospect of buying a system where all software developmentC >>> and probably even all active maintenance has already stopped isi9 >>> not one that pleases most experienced administrators.d >>D >>Huh ?  They said they will be using the same source control systemH >>for Alpha and IA64.  That means features (aside from hardware-specificC >>features) will naturally flow to both, until they decide to stop.o > E > You haven't been there, have you?  I have.  Several times, in fact,d: > and that belief is more wishful thinking than plausible. >   = 	And you haven't been reading some of the relevant threads inr 	this newsgroup either.d  B > The first problem occurs with problem reporting.  Things rapidlyB > get into a state where, if you can't prove that a problem existsD > on the new architecture (even if you are certain that it is), your! > problem report will be ignored.p > A > The second occurs with problems that are architecture-specific,c> > as are a great many of the nastier bugs and even more of the? > performance problems in the SMP and exception-handling areas,yD > compiler, kernel, library and all.  They don't even get looked at. > > > Then you get the creeping necrosis effect, which is the real? > killer.  A new operating system feature is provided, which is A > very system-dependent internally, so the commercial decision ist  ? 	As Hoff detailed earlier, "feature  creep" is a VERY bad thing9* 	and surely he pops in to further clarify.  ? > not to waste money on the old system.  Exception handling and,A > SMP are particularly relevant, again.  This is then used by theeC > language systems (which is why it was wanted in the first place).FD > This is then relied on by an application.  Now, you are snookered,: > even if you personally don't need the original facility. >   B 	Nick, there is the whole matter of history here.  VMS engineeringB 	beat their own internal deadline for the VAX->Alpha port by about@ 	a year.  I've heard firsthand that they have some of the finest= 	software engineering techniques around.  Another fellow very F 	familiar with VAX->Alpha migration described it as "a piece of cake."  G 	Perhaps you can go on about such scary subjects but the folks involvede+ 	most likely aren't shaking in their boots.i   				Robd   ------------------------------    Date: 28 Aug 2001 14:08:05 -0500- From: Kilgallen@SpamCop.net (Larry Kilgallen) ! Subject: Re: EV7 will never ship?g3 Message-ID: <SrQsCvEne82B@eisner.encompasserve.org>a  [ In article <9mgp89$4ja$1@pegasus.csx.cam.ac.uk>, nmm1@cus.cam.ac.uk (Nick Maclaren) writes:E5 > In article <QxugolYOhXr2@eisner.encompasserve.org>,m0 > Larry Kilgallen <Kilgallen@SpamCop.net> wrote:] >>In article <9mgcm6$ngk$1@pegasus.csx.cam.ac.uk>, nmm1@cus.cam.ac.uk (Nick Maclaren) writes:p >>A >>> The thing that is completely crazy is the combination of thatsA >>> schedule and the projected lifetime of the system.  As anyoneDC >>> experienced knows, most kernel and compiler tuning problems and E >>> nasty bugs do not appear until after a system has hit real users.FA >>> In-house testing is just no substitute.  This is particularlyeC >>> serious because of the magnitude of the SMP changes between the- >>> EV6 and EV7. >>> B >>> The prospect of buying a system where all software developmentC >>> and probably even all active maintenance has already stopped is-9 >>> not one that pleases most experienced administrators.  >>D >>Huh ?  They said they will be using the same source control systemH >>for Alpha and IA64.  That means features (aside from hardware-specificC >>features) will naturally flow to both, until they decide to stop.u > E > You haven't been there, have you?  I have.  Several times, in fact,0: > and that belief is more wishful thinking than plausible. > B > The first problem occurs with problem reporting.  Things rapidlyB > get into a state where, if you can't prove that a problem existsD > on the new architecture (even if you are certain that it is), your! > problem report will be ignored.o  H I have found that they still take problem reports on both VAX and Alpha.@ Note that this is _without_ using the same source control system@ (same software, but they maintain two copies).  Coupling between& Alpha and IA64 should be even tighter.  A > The second occurs with problems that are architecture-specific, > > as are a great many of the nastier bugs and even more of the? > performance problems in the SMP and exception-handling areas, D > compiler, kernel, library and all.  They don't even get looked at. > > > Then you get the creeping necrosis effect, which is the real? > killer.  A new operating system feature is provided, which iseA > very system-dependent internally, so the commercial decision is ? > not to waste money on the old system.  Exception handling and5A > SMP are particularly relevant, again.  This is then used by the:C > language systems (which is why it was wanted in the first place).tD > This is then relied on by an application.  Now, you are snookered,: > even if you personally don't need the original facility.  ? Exception handling and SMP exist on both VAX and Alpha.  Kernele< threads is an example of a new development that was not done= for VAX.  The kernel threads interface, however, is internal,i= and the DECthreads interface seen by customers is the same ona= VAX and Alpha.  No, you don't get to use more than one CPU inc; a single process on VAX, and that is a commercial tradeoff.>> Their typical defense, which seems to have some merit, is that? aside from the cost, VAX customers do not want to see any extrac! churn in how the executive works.o   ------------------------------   Date: 28 Aug 2001 19:58:34 GMT( From: nmm1@cus.cam.ac.uk (Nick Maclaren)! Subject: Re: EV7 will never ship?-0 Message-ID: <9mgt5a$7fk$1@pegasus.csx.cam.ac.uk>  3 In article <SrQsCvEne82B@eisner.encompasserve.org>,e. Larry Kilgallen <Kilgallen@SpamCop.net> wrote: >cI >I have found that they still take problem reports on both VAX and Alpha.uA >Note that this is _without_ using the same source control systempA >(same software, but they maintain two copies).  Coupling between>' >Alpha and IA64 should be even tighter.   > I didn't notice that the newsgroups seem to have been trimmed.< I haven't used VMS since before the MicroVAX :-)  My remarks+ were generic, and referring to all systems.   ? However, this is certainly NOT true for Tru64 Unix, and is alsot' NOT true for Compaq's language systems.   @ >Exception handling and SMP exist on both VAX and Alpha.  Kernel= >threads is an example of a new development that was not doneo> >for VAX.  The kernel threads interface, however, is internal,> >and the DECthreads interface seen by customers is the same on> >VAX and Alpha.  No, you don't get to use more than one CPU in< >a single process on VAX, and that is a commercial tradeoff.? >Their typical defense, which seems to have some merit, is that @ >aside from the cost, VAX customers do not want to see any extra" >churn in how the executive works.  C No, you have missed the point.  Those things are not either presentiC or not present, but are present in different forms and to different @ levels of completeness.   Now, VMS may be exceptional, but I can8 assure you that Compaq's compilers and libraries aren't.  A Furthermore, the presence of kernel threads is precisely the sort ? of thing that I am talking about under creeping necrosis.  What7B happens is that an operation will behave subtly differently in the@ two cases, the compiler or library will be written for or tested@ with the new behaviour (sometimes accidentally), and so it goes.       Regards, Nick Maclaren,* University of Cambridge Computing Service,> New Museums Site, Pembroke Street, Cambridge CB2 3QG, England. Email:  nmm1@cam.ac.uk/ Tel.:  +44 1223 334761    Fax:  +44 1223 334679a   ------------------------------  % Date: Tue, 28 Aug 2001 16:27:38 -0400v- From: JF Mezei <jfmezei.spamnot@videotron.ca> ! Subject: Re: EV7 will never ship?r, Message-ID: <3B8BFEA9.2D05DFD5@videotron.ca>   Alan Greig wrote:uG > Ok, now that API have decided that they will never ship an EV7 due to>B > lack of demand for Alpha systems since the June announcement why) > should we assume that Compaq ever will?s   Does it really matter ?s  J Compaq reduced the negative aspect of the Alpha murder by stating it would- keep Alpha on life support for a while (EV7).   L As soon as IA64 is operational, EV7 becomes moot and irrelevant and they can cancel it if not ready yet.u  G The only relevance to EV7 post IA64 is if Compaq realises that there is K extreme reluctance of those few customers it cares about to migrate to IA64-7 and they prefer to stick to Alpha for a few more years.   I The other issue to consider is whether the EV7 engineers remain at Compaq1 until project completion.4   ------------------------------  % Date: Tue, 28 Aug 2001 16:49:19 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca>s! Subject: Re: EV7 will never ship?p, Message-ID: <3B8C03BC.59572132@videotron.ca>   Larry Kilgallen wrote:B > their name to be mentioned.  Remember the big press announcementB > regarding DII-COE where they got praise from the company that isD > equipping JSTARS with VMS ?  Certainly Compaq is not going through5 > the DII-COE effort just to put VMS on 10 airplanes.D    K Considering that these planes were still running  Data General stuff , I amsJ not sure long term commitments are really needed. Once it is installed andE running, will they really want to constantly upgrade these systems ? n  K And since they continued o operate these older DG systems well after DG hadoK stopped working with its AOSVS operating system, the same could happen with < VMS (Compaq stops work on VMS but continues to maintain it).  G Also, how does DII-COE work with regards to VMS on Alpha. Hasn't CompaqcL enssentially already announced the death of VMS on Alpha that will happen in' about 10 years when support is pulled ?t   ------------------------------  % Date: Tue, 28 Aug 2001 17:01:45 -0400I- From: JF Mezei <jfmezei.spamnot@videotron.ca>S! Subject: Re: EV7 will never ship?n, Message-ID: <3B8C06A5.EE3BE9B5@videotron.ca>   Larry Kilgallen wrote:D > Huh ?  They said they will be using the same source control systemH > for Alpha and IA64.  That means features (aside from hardware-specificC > features) will naturally flow to both, until they decide to stop.Y  G What about all the third party software that customers really require ?t   ------------------------------    Date: 28 Aug 2001 18:27:30 -0400# From: Chris Morgan <cm@mihalis.net>i! Subject: Re: EV7 will never ship?a( Message-ID: <86itf795wt.fsf@mihalis.net>  - young_r@encompasserve.org (Rob Young) writes:t  D > 	Nick, there is the whole matter of history here.  VMS engineeringD > 	beat their own internal deadline for the VAX->Alpha port by aboutB > 	a year.  I've heard firsthand that they have some of the finest? > 	software engineering techniques around.  Another fellow veryoH > 	familiar with VAX->Alpha migration described it as "a piece of cake." > I > 	Perhaps you can go on about such scary subjects but the folks involveda- > 	most likely aren't shaking in their boots.d  B With respect, "because we've been ok up till now, we will be ok inD future" isn't a wise philosophy in my opinion (that's my paraphrase,
 not a quote).   C Alpha was engineered from the ground up to support high performance E and near-perfect VAX/VMS compatibility (e.g. those VAX float formats, 
 PALcode etc).t  4 IPF hasn't been designed to support any VAX or Alpha@ peculiarities. Instead it has all of the Intel, Apollo and HP-PA1 peculiarities and a bunch of new ones of its own.   D I think the magnitude of the task is larger, and the strength of theC company behind it severely diminished. If I'm right, it is at leastrE an open question whether the Alpha->IPF port will be anything like as  successful.   E I'm reminded of the Ada95 issue. Back in '94 the big topic on the adarF newsgroup was "DEC Ada why is it so good". DEC produced the best Ada83F compiler bar none. This was another success for their indubitably fineF software engineering. Their Ada users were thus quite taken aback whenF they just punted and licensed other Ada95 compilers (Rational and then GNU Ada as I remember).R  D How do you know the Alpha/VMS crowd will not get the same shock? YouD don't. Nobody does. A lot of work is needed and will have to be paidC for. Those brave folks, ready to do the job and all, will simply doa= some other job at the flick of a bean-counters quill if he sow= decides. Or they may pull off another triumph. Let's hope so.    Cheers,E   Chrisp   --   Chris Morgan   ------------------------------  % Date: Tue, 28 Aug 2001 21:23:21 -0400s- From: JF Mezei <jfmezei.spamnot@videotron.ca>e! Subject: Re: EV7 will never ship? , Message-ID: <3B8C4408.5D9433B0@videotron.ca>   Chris Morgan wrote:aF > I think the magnitude of the task is larger, and the strength of theE > company behind it severely diminished. If I'm right, it is at least>G > an open question whether the Alpha->IPF port will be anything like asg
 > successful..  I From a technical point of view, I have no problems believing that the VMS F engineers will be able to get VMS to run on IA64 with all of the basic7 expected features, including cross-platform clustering.k  M Where I think VMS will suffer in in high end fancy stuff that nobody else hasnL (galaxies for instance).  Since neither NT nor Tru64 have these features, itJ will be an uphill battle for the VMS folks to convince the wintel folks toL build boxes that support those unique VMS features. (this isn't so much chipK dependant , but because of the fact that the PC people will be in charge of N building boxes that are far more complex than the glorified desktops installed) in a 19" rack that they currently build.)t  M I would be more comfortable if VMS and Tandem sides worked together and builtfK their own boxes. If you're going to relegate VMS to only a very few focusedcN market niches at the high end (eg: cash cow), the model is nearly identical toD Tandem's and to take advantage of all those fancy features, you needO specialised hardware that the wintel weenies don't need (or know how to build).e  E On the other hand, by forcing VMS to lower itself to wintel levels ofeL hardware, some can argue that VMS will run on commodity hardware and thus be more competitive.h  L However, the problem I see is that on the wintel el-cheapo hardware, VMS mayN not be good enough to please those few large remaining customers, and Compaq'sN total lack of marketing and its unwillingness to pit VMS against Windows won'tR make VMS realise its potential as an OS that can work from desktop to data-centre.   ------------------------------  % Date: Tue, 28 Aug 2001 15:02:02 -0400 ' From: "Bill Todd" <billtodd@foo.mv.com>s) Subject: Re: Feeling Better about Itaniuml( Message-ID: <9mgpq5$hh6$1@pyrite.mv.net>  @ "Fred Kleinsorge" <kleinsorge@star.zko.dec.com> wrote in message, news:vfOi7.882$bB1.41392@news.cpqcorp.net...< > Bill Todd wrote in message <9med7j$6ii$1@pyrite.mv.net>... > > G > >I think you confused Merced with later versions of the architecture:, > MercedG > >doesn't run much of *anything* (and certainly not server-style apps)mE > >natively as fast as its better competition does, and even McKinley1E > >apparently will be at best comparable to (some of) its competition8 (though  > >probably not to EV7). > >n >p >eL > Hmm.  It benchmarks as faster than one of the most popular "server" CPUs -H > Sparc.  All if needs is to be put into a good server box, and add high > quality server software.  J C'mon, Fred:  that's why I said 'better' competition above (e.g., Alpha orJ Power in the 64-bit realm, or any upper-crust recent IA32 chip if a 32-bitF platform will suffice - and that's comparing its performance with IA643 *native* performance, not IA64 32-bit performance).   B SPARC may be *effective* competition for IA64 (and even for betterI processors), but I doubt you'd put SPARC as a processor implementation inp; the same league as Alpha or Power - just as I didn't above.e  F (Oh, by the way:  the only SPECint2K figure I've seen for a real-worldG [DELL] Merced box was, I believe, 314 - so it indeed may not even match - USIII's performance - 370, IIRC - after all.)r   - bill   ------------------------------  % Date: Tue, 28 Aug 2001 17:06:18 -0400c- From: JF Mezei <jfmezei.spamnot@videotron.ca>o) Subject: Re: Feeling Better about Itaniumt, Message-ID: <3B8C07B6.624958CF@videotron.ca>   Marty Kuhrt wrote:O >   - has dumped the future of the chip at the core of the high margin productsp? >   - threw away superior technology and the people that did iteN >   - annoyed, upset or made cautious all their high end, high margin, clientsE >   - damaged any credibility of CPQ being more than a PC box shifter 1 >   - decided to put all their eggs in one baskett  H Ahh, but shareholders will have been given the Compaq spin and will see:  M -Compaq finally putting its house in order by dumping unprofitable endeavoursa  N -Compaq will be able to reduce costs through volume purchases of the same chip for all its systems   M -Alpha had no future , had bad image etc etc, and IA64 has promise of beating- Alpha, so why bother with Alpha   G -Compaq is going to become mre efficient by streamlining product lines.   N Remember that shareholders do not know about VMS. They knwo know about Tandem,K but now VMS. And for Tandem, the move is from someone else's chip (MIPS) to 1 someone else's chip (IA64), so it it makes sense.       K Digital and then Compaq were able to do bad things to the VMS customers foriK years, yet shareholders have never said a word about their handling of VMS.a   ------------------------------  % Date: Tue, 28 Aug 2001 17:12:06 -0400 ' From: "Bill Todd" <billtodd@foo.mv.com>r) Subject: Re: Feeling Better about Itaniume( Message-ID: <9mh1dv$pb0$1@pyrite.mv.net>  : "JF Mezei" <jfmezei.spamnot@videotron.ca> wrote in message& news:3B8C07B6.624958CF@videotron.ca... > Marty Kuhrt wrote:H > >   - has dumped the future of the chip at the core of the high margin productsA > >   - threw away superior technology and the people that did itaH > >   - annoyed, upset or made cautious all their high end, high margin, clientsvG > >   - damaged any credibility of CPQ being more than a PC box shiftere3 > >   - decided to put all their eggs in one basketi > J > Ahh, but shareholders will have been given the Compaq spin and will see: >tD > -Compaq finally putting its house in order by dumping unprofitable
 endeavours >-K > -Compaq will be able to reduce costs through volume purchases of the samee chip > for all its systemsn > G > -Alpha had no future , had bad image etc etc, and IA64 has promise ofm beatingo! > Alpha, so why bother with Alphag >sI > -Compaq is going to become mre efficient by streamlining product lines.< >gH > Remember that shareholders do not know about VMS. They knwo know about Tandem,tJ > but now VMS. And for Tandem, the move is from someone else's chip (MIPS) to3 > someone else's chip (IA64), so it it makes sense.e >c >y > I > Digital and then Compaq were able to do bad things to the VMS customerss for H > years, yet shareholders have never said a word about their handling of VMS.  L The market eventually tends to ensure that inattentive shareholders get whatK they deserve (just as inattentive customers often do).  While we might wishaF for more competent shareholders who would coerce Compaq into differentC behavior in order to improve their investments, I'm not sure that'se@ realistic given the way the market currently appears to operate.   - bill   ------------------------------  % Date: Tue, 28 Aug 2001 17:57:35 -0400 ' From: "Bill Todd" <billtodd@foo.mv.com>o) Subject: Re: Feeling Better about Itaniume( Message-ID: <9mh43a$stf$1@pyrite.mv.net>  8 "Rob Young" <young_r@encompasserve.org> wrote in message- news:FkZ5tau3z1Kf@eisner.encompasserve.org...y   ...h  D > You are mixing target segments and not making a very good argument > for some reason.  > No:  you're just confused (and the one who's mixing segments).  +   I mentioned McKinley and Power4.  I thinko? > in the context I am highlighting servers.  After all, that isa1 > where Intel thinks McKinley's target market is.   E Then why do you insist on repeating those silly assertions about IA64 G replacing IA32 in *all* segments (see quote below)?  And if you *don't* J believe it will replace IA32 in the high-volume environments (desktops andK low-end servers) any time soon (which indeed is almost certainly the case),tK where do you get the idea that the much more limited-volume (but lucrative)vI upper-end server segment will allow it to achieve the similar 'commodity'eH price status enjoyed by those high-volume systems that would allow it toK compete 'across the board' (i.e., including the lower-end server, let aloner$ desktop, segments) cost-effectively?  K You've been saying things like "All Intel processors sometime in the futureiB will be 64-bit (32-bit disappears).  At that point, 64-bit will beI commodity", and "When servers across the board are nasty commodities...", B and, to place that in the specific context I've been suggesting isK balderdash, "So in 2-3 years when the migration away from IA32 is begun..."iG Your base assumption that IA64 will take over the world any time beforeaD close to the end of the decade at the earliest (and then only if itsJ competition evaporates the way Alpha did) is based on reasoning that can't# even be dignified as being 'fuzzy'.t     They positioned   > Merced against UltraSparc III.  H Of course they did:  it's the only competition whose performance doesn'tF make Merced look like a very expensive pig (it just makes it look like4 over-priced but somewhere nearly equal competition).   >V > > But since that'sI > > exactly the low-margin market Intel said it wanted to break out of by-I > > creating IA64, I'm not sure why you think it would want to even if it( didM > > have the cash to do so.l > >e >h6 > They have $9 billion in cash.  Cash isn't a problem.  L How recent is that figure?  Last I heard (a month or two ago, I think), theyJ were going through their cash reserves at an incredibly rapid rate and had nothing like that amount left.  I Which, of course, doesn't in any way change the fact that in the unlikelyrJ event that they succeeded in pushing IA64 into the truly 'commodity' priceB range, they'd be defeating one of their main stated objectives forJ developing it (breaking out of the commodity, low-margin processor markets they're currently stuck in).   >aK > > And since AMD's 'Hammer' is a significantly smaller chip than Merced orsI > > McKinley (and based on the Athlon's high-performance core), expect it  alsoL > > to be far more cost-effective than IA64 for those customers who actuallyI > > need a 64-bit platform (and, of course, much better at running 32-bitr > > applications). >d >n> > Always these rumors, and rumors of Microsoft creating a portA > of Windows 2000 to support Hammer.  I don't think that happens.   I Gee, I can remember a time when you wouldn't have dismissed Paul DeMone'svI statements (on which the above is based) as 'rumor'.  But of course timess$ have changed for you in a major way.  L Microsoft doesn't have to port Windows to x86-64 for IA64 to get hammered inK the low-end-to-mid-range server segment we're discussing:  Linux is alreadyeL doing a decent job of penetrating that segment on IA32, and x86-64 will justH increase its advantages over Windows in that segment if Windows isn't on x86-64 too.    >eA > It's not a matter of needing 64 bit.  Initially, Intel's 64 bite > offering gets a slow start.   I No shit.  The question is whether it ever does much better than that, andr8 there's little current objective reason to expect it to.  !   But it does have the support of = > Linux and W2K both of which will continue to erode/supplantg  > entrenched Enterprise players.  I Maybe.  Someday.  The belief half a dozen years ago that Windows would doeK this contributed materially to DEC's demise, and seems to be doing the same-4 to Compaq today.  Who knows who it'll sink tomorrow?  J And Linux happily (and quite portably) runs on anything:  no advantage for IA64 there.8      Linux takes advantage of cheapE > hardware and will follow that curve in the Enterprise space.  Cheapi* > Enterprise hardware will be Intel based.  H Enterprise hardware will not in this decade be 'cheap' in the sense thatK current 'commodity' platforms are cheap:  the quality just isn't, and can't H be, there at those prices.  Once you leave the true commodity space, theK price difference between Intel's processors and others is a negligible part H of the overall system price - and can be more than offset if those otherH processors perform well enough that you don't need as many of them.  AndJ those other processors can use almost all the same ancillary hardware that2 IA64 does, so no advantage for Intel there either.   ...e  A > I heard about a bargain.  A 4 processor IBM AIX box with 2 GigseA > of RAM - for $100K U.S., that same configuration lists for $28K1C > today at Dell (4 processor Intel server, 4 Gigs of RAM instead ofc= > 2).  So maybe in a year or two, that IBM solution gets downd" > to 65K and IA64 comes in at 30K.  E If that's the case, it will be because IBM doesn't have to match IA64eL pricing to maximize its profit (i.e., because IA64 is still pretty much of aE relative pig):  there's no reason for the production costs of the twof systems to differ materially.l  J After all, such product differentiation is why IBM can price those systemsK with fat margins today and remain considerably healthier than the companiesaJ that believe only 'commodity' systems are worth concentrating on.  Too bad4 Compaq will learn this lesson far too late, if ever.   >y. > Apparently, the future will leave us 3 OSes: >A= > http://news.cnet.com/news/0-1003-200-6986291.html?tag=mn_hd    ...o  E > "Others agree. In the next seven to eight years, Linux will largelyi replacesL > Unix, Aberdeen analyst Bill Claybrook said in a July report. Linux will be onenH > of three primary operating systems in commercial use, along with IBM's z/OSD > mainframe operating system and Microsoft's Windows, he predicted."  L Which is almost exactly the situation I've been predicting as well:  WindowsC on the desktop and *some* lowish-end 'commodity' servers (the other:I lowish-end commodity servers being Unix- or in this context Linux-based),oH Unix/Linux (and could have been VMS) in the mid-range, and if Unix neverL matures sufficiently something really industrial-strength (again, could have been VMS) at the top-end.r   ...c  C > So I guess in the next 7-8 years IA64 will be running most of the8: > commercial apps and a handful running on IBM mainframes.  K You can guess whatever you want.  Just don't expect others to buy into your>L fantasies and make them self-fulfilling:  some people (and companies) preferK to create the future rather than simply drift along on whatever currents itl
 may bring.   - bill   >  > Robt >    ------------------------------    Date: 28 Aug 2001 19:58:08 -0500+ From: young_r@encompasserve.org (Rob Young)e) Subject: Re: Feeling Better about Itanium 3 Message-ID: <ibhilal+GuW2@eisner.encompasserve.org>P  R In article <9mh43a$stf$1@pyrite.mv.net>, "Bill Todd" <billtodd@foo.mv.com> writes: > : > "Rob Young" <young_r@encompasserve.org> wrote in message/ > news:FkZ5tau3z1Kf@eisner.encompasserve.org...s >  > ...p > E >> You are mixing target segments and not making a very good argument  >> for some reason.r > @ > No:  you're just confused (and the one who's mixing segments). > - >   I mentioned McKinley and Power4.  I think)@ >> in the context I am highlighting servers.  After all, that is2 >> where Intel thinks McKinley's target market is. > G > Then why do you insist on repeating those silly assertions about IA64n7 > replacing IA32 in *all* segments (see quote below)?  p    E 	Because it will happen according to Intel's own publically availableu0 	CPU roadmaps.  We can quibble about timeframes.   > And if you *don't*L > believe it will replace IA32 in the high-volume environments (desktops andM > low-end servers) any time soon (which indeed is almost certainly the case),bM > where do you get the idea that the much more limited-volume (but lucrative)iK > upper-end server segment will allow it to achieve the similar 'commodity'cJ > price status enjoyed by those high-volume systems that would allow it toM > compete 'across the board' (i.e., including the lower-end server, let aloneb& > desktop, segments) cost-effectively? >   C 	Because IA64 CPUs a year or two out (with shrink to .13 micron andl> 	such) will priced similarly to Xeon CPUs today so it won't beB 	out of the question to see 4 CPU McKinley boxes to be priced nearE 	4 CPU Xeon boxes today (okay, at $10K premium) but at a $10K premium-D 	that will put them near $30K , significanly cheaper than RISC boxes 	today.e  D 	It won't replace IA32 in the next 3 years, but that doesn't matter.  M > You've been saying things like "All Intel processors sometime in the futuredD > will be 64-bit (32-bit disappears).  At that point, 64-bit will beK > commodity", and "When servers across the board are nasty commodities...",rD > and, to place that in the specific context I've been suggesting is > balderdash,   0 	Not so.  You just aren't giving it enough time.  A > "So in 2-3 years when the migration away from IA32 is begun..."bI > Your base assumption that IA64 will take over the world any time beforehF > close to the end of the decade at the earliest (and then only if itsL > competition evaporates the way Alpha did) is based on reasoning that can't% > even be dignified as being 'fuzzy'.s >    	Time wil tell.    >   They positionedh! >> Merced against UltraSparc III.s > J > Of course they did:  it's the only competition whose performance doesn'tH > make Merced look like a very expensive pig (it just makes it look like6 > over-priced but somewhere nearly equal competition). >    	Yep.l   >> >> > But since that'srJ >> > exactly the low-margin market Intel said it wanted to break out of byJ >> > creating IA64, I'm not sure why you think it would want to even if it > didg >> > have the cash to do so. >> > >>7 >> They have $9 billion in cash.  Cash isn't a problem.s >  > How recent is that figure?     	Yesterday.a  2 > Last I heard (a month or two ago, I think), theyL > were going through their cash reserves at an incredibly rapid rate and had  > nothing like that amount left. >   5 	$6.4 billion Sept 2000, nearly $9 billion June 2001.h 	Try this:  finance.yahoo.com.  K > Which, of course, doesn't in any way change the fact that in the unlikelytL > event that they succeeded in pushing IA64 into the truly 'commodity' priceD > range, they'd be defeating one of their main stated objectives forL > developing it (breaking out of the commodity, low-margin processor markets > they're currently stuck in). >   6 	At Xeon prices, they will be quite happy I am sure.   	Deerfield (the desktopF? 	part) and follow-ons is the low-cost desktop "commodity" part . 	(how is that?)i   >>L >> > And since AMD's 'Hammer' is a significantly smaller chip than Merced orJ >> > McKinley (and based on the Athlon's high-performance core), expect it > alsoM >> > to be far more cost-effective than IA64 for those customers who actuallyeJ >> > need a 64-bit platform (and, of course, much better at running 32-bit >> > applications).s >> >>? >> Always these rumors, and rumors of Microsoft creating a portbB >> of Windows 2000 to support Hammer.  I don't think that happens. > K > Gee, I can remember a time when you wouldn't have dismissed Paul DeMone's K > statements (on which the above is based) as 'rumor'.  But of course times & > have changed for you in a major way. > N > Microsoft doesn't have to port Windows to x86-64 for IA64 to get hammered inM > the low-end-to-mid-range server segment we're discussing:  Linux is alreadybN > doing a decent job of penetrating that segment on IA32, and x86-64 will justJ > increase its advantages over Windows in that segment if Windows isn't on
 > x86-64 too.r >   @ 	Windows doesn't have to go there.  If X86-64 ever gets annoying? 	Intel will surely adjust their pricing models and discounts to = 	make sure it doesn't go anywhere.  After all, IBM dumped AMDt? 	desktop.  Again, a peak under the tent flap.  I'm sure IBM andl@ 	Compaq will rattle the X86-64 sabre to get nice IA64 discounts.  B 	If AMD somehow ever makes it into the datacenter.  Nah... scratch 	that thought ;-)u   >>B >> It's not a matter of needing 64 bit.  Initially, Intel's 64 bit >> offering gets a slow start. > K > No shit.  The question is whether it ever does much better than that, and : > there's little current objective reason to expect it to. >   - 	Vendor support.  OEM adoption.  Need a list?y   > J > Enterprise hardware will not in this decade be 'cheap' in the sense thatM > current 'commodity' platforms are cheap:  the quality just isn't, and can'tn > be, there at those prices.      0 	You are missing this one.  I'm seeing failover  	"clusters" of NT boxes runningeC 	apps with 2 GByte of memory, 2-4 CPUs.  In some senses, it doesn'tdD 	matter how crappy the hardware is.  And yes, failover because it is" 	easier to understand and support.   > B >> I heard about a bargain.  A 4 processor IBM AIX box with 2 GigsB >> of RAM - for $100K U.S., that same configuration lists for $28KD >> today at Dell (4 processor Intel server, 4 Gigs of RAM instead of> >> 2).  So maybe in a year or two, that IBM solution gets down# >> to 65K and IA64 comes in at 30K.u > G > If that's the case, it will be because IBM doesn't have to match IA64oN > pricing to maximize its profit (i.e., because IA64 is still pretty much of aG > relative pig):  there's no reason for the production costs of the twod > systems to differ materially.t > L > After all, such product differentiation is why IBM can price those systemsM > with fat margins today and remain considerably healthier than the companiesgL > that believe only 'commodity' systems are worth concentrating on.  Too bad6 > Compaq will learn this lesson far too late, if ever. >   @ 	IBM will too when the applications are available across W2K and@ 	Unix and the W2K solution is much cheaper and a majority of the 	vendor's userbase.s   >>/ >> Apparently, the future will leave us 3 OSes:  >>> >> http://news.cnet.com/news/0-1003-200-6986291.html?tag=mn_hd >  > ...  > F >> "Others agree. In the next seven to eight years, Linux will largely	 > replaceoM >> Unix, Aberdeen analyst Bill Claybrook said in a July report. Linux will beg > oneeI >> of three primary operating systems in commercial use, along with IBM'sr > z/OSE >> mainframe operating system and Microsoft's Windows, he predicted."s > N > Which is almost exactly the situation I've been predicting as well:  WindowsE > on the desktop and *some* lowish-end 'commodity' servers (the otheroK > lowish-end commodity servers being Unix- or in this context Linux-based),fJ > Unix/Linux (and could have been VMS) in the mid-range, and if Unix neverN > matures sufficiently something really industrial-strength (again, could have > been VMS) at the top-end.l >   ' 	Windows in the datacenter, eventually.6   > ...  > D >> So I guess in the next 7-8 years IA64 will be running most of the; >> commercial apps and a handful running on IBM mainframes.r > M > You can guess whatever you want.  Just don't expect others to buy into yourdN > fantasies and make them self-fulfilling:  some people (and companies) preferM > to create the future rather than simply drift along on whatever currents itr > may bring. >   ? 	No... see the analyst above.  That's his opinion, not fantasy.n   				Rob    ------------------------------  % Date: Tue, 28 Aug 2001 20:15:40 -0500t1 From: "David J. Dachtera" <djesys.nospam@fsi.net>a) Subject: Re: Feeling Better about Itanium ' Message-ID: <3B8C423C.16E53A4B@fsi.net>c   Michael Joosten wrote: >  > Jack Patteeuw wrote: > >t > T > > I hate to agree with you on this point, but your right.  IMHO, Compaq managementW > > still "doesn't get it".  The first rule of sales is, "Don't do anything to piss offmT > > your existing customer base in your attempt to get new customers or improve your > > bottom line."m >  > So? Is it still? > F > It might be the 'first rule of sales', but what if the first rule of > business is: > H > "You must pamper the shareholders, even if that means pissing off some > customers"  G Can you burn a bridge while you're still crossing it? The folly of sucheH thinking put Compaq where it is. Failure to learn from its mistakes will put Compaq in its grave.  kJ > At least nowadays. Perhaps next year the shareholderism will have cooled > down a little.  G Yeah - because they have dumped their Compaq stock and sought a companye' that at least has SOME business acumen.i   --   David J. Dachterae dba DJE Systemsj http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    Poor old Terry Hardy!  They buried him today. He lived the life of Riley while Riley was away...e   ------------------------------  % Date: Tue, 28 Aug 2001 21:49:40 -0500p+ From: Phil Mendelsohn <mend0070@tc.umn.edu>d) Subject: Re: Feeling Better about ItaniumeH Message-ID: <Pine.SOL.4.20.0108282148090.10343-100000@garnet.tc.umn.edu>  $ On Tue, 28 Aug 2001, JF Mezei wrote:  J > Ahh, but shareholders will have been given the Compaq spin and will see: > O > -Compaq finally putting its house in order by dumping unprofitable endeavoursa  I Shareholders are apparently pleased to see a dry basin when the boulevardd is littered with infants.t   ------------------------------  % Date: Wed, 29 Aug 2001 01:43:33 -0400d' From: "Bill Todd" <billtodd@foo.mv.com>y) Subject: Re: Feeling Better about Itaniumo( Message-ID: <9mhvcu$nj1$1@pyrite.mv.net>  8 "Rob Young" <young_r@encompasserve.org> wrote in message- news:ibhilal+GuW2@eisner.encompasserve.org... L > In article <9mh43a$stf$1@pyrite.mv.net>, "Bill Todd" <billtodd@foo.mv.com> writes:    ...   D > Because IA64 CPUs a year or two out (with shrink to .13 micron and0 > such) will priced similarly to Xeon CPUs today  G Not if Intel wants to recover any IA64 development costs:  Xeon pricingtK reflects the ability to leverage the broad sales base of IA32 as a whole toh" cover IA32 core development costs.  J If Intel tries to cover just *on-going* IA64 development costs in its IA64H pricing (even if it makes no effort to recoup the past 7 years' worth ofE expenditures), IA64s will be relatively expensive for the foreseeableeK future.  Of course, Intel may not be as short-sighted as Compaq was in thisuI area, but even so it will be hard-pressed to keep plowing money into IA64n> development without getting some significant immediate return.   ...t  H > > You've been saying things like "All Intel processors sometime in the futureF > > will be 64-bit (32-bit disappears).  At that point, 64-bit will be< > > commodity", and "When servers across the board are nasty commodities...",F > > and, to place that in the specific context I've been suggesting is > > balderdash,t >e1 > Not so.  You just aren't giving it enough time.   E The '2 - 3 years' quote below is yours, and that's what's balderdash.nK Stretch it out to any reasonable estimate (5 years minimum for desktops and K low-end servers to *start* to migrate off IA32 in significant numbers), andsB any argument for IA64's imminent dominance and volume-driven priceI advantages falls apart (leaving aside the fact that a lot can change in 5e years in this industry).   >eC > > "So in 2-3 years when the migration away from IA32 is begun..."n   ...v  9 > >> They have $9 billion in cash.  Cash isn't a problem.  > >  > > How recent is that figure? >i > Yesterday.  L Back on June 27th there was discussion in comp.arch on this subject that wasJ the basis for my comment, but the matter seems to be debatable and I don'tH particularly enjoy delving into Compaq's finances, let alone Intel's, so9 I'll give you this one unless other information surfaces.    ...h  D > > Which, of course, doesn't in any way change the fact that in the unlikelyH > > event that they succeeded in pushing IA64 into the truly 'commodity' pricedF > > range, they'd be defeating one of their main stated objectives forF > > developing it (breaking out of the commodity, low-margin processor marketst  > > they're currently stuck in). > >e > 5 > At Xeon prices, they will be quite happy I am sure.   I Not if they want to get back the money they've invested in developing thew product.   ...h  D > > Microsoft doesn't have to port Windows to x86-64 for IA64 to get hammered in G > > the low-end-to-mid-range server segment we're discussing:  Linux ise already K > > doing a decent job of penetrating that segment on IA32, and x86-64 willi justL > > increase its advantages over Windows in that segment if Windows isn't on > > x86-64 too.s > >p >oA > Windows doesn't have to go there.  If X86-64 ever gets annoyinge@ > Intel will surely adjust their pricing models and discounts to# > make sure it doesn't go anywhere.t  K You just don't get it:  Intel could *give away* IA64 in this segment and itiL wouldn't be attractive compared with Hammer.  The desktop and low-end serverK market will be well-served by IA32 for *at least* 4 - 5 more years, and for I many years beyond that given the option to use something like Hammer that D can execute the occasional 64-bit application while executing 32-bit1 applications with good performance (unlike IA64).t  G Perhaps I just haven't been saying this in a way you can understand, sor let's try the following:  H Wintel (including compatible AMD hardware) indisputably owns the desktopJ today, with an incredible foundation of existing IA32 applications.  LinuxI *might* succeed in challenging it or at least siphoning off enough marketmJ share to be painful or at least threatening, so Microsoft *really* doesn't/ want to rock the boat if it can avoid doing so.y  G There's no market demand whatsoever for 64-bit desktop applications, so2L Microsoft has no way to continue its desktop dominance without continuing toE support 32-bit desktop applications well.  Therefore, Microsoft won't L abandon IA32 for any hardware platform (such as IA64) that does not do this,G though it's certainly interested in *extending* the reach of Windows totI lucrative non-desktop environments *in addition* to retaining its desktopl	 monopoly.t  L Similarly, there's no reason for most desktop and low-end server applicationL developers to develop 64-bit versions of their applications, because there's4 no significant hardware base out there to sell into.  F OTOH, some small but gradually increasing number of desktop users willC eventually begin to demand the occasional 64-bit application on thetH desktop - and would prefer not to have to buy a second desktop system soJ that they could run *both* 32-bit and 64-bit applications well.  Hammer isL the answer to their wishes, and if Microsoft doesn't want Linux to grab such% users it will have to support Hammer.i  K A somewhat similar scenario exists in the low-end server market - a segmentmF Microsoft *has* been pursuing with some vigor and might be expected toJ continue to:  since low-end server applications almost by definition don'tF require a 64-bit address space, but might slowly begin to over time, a Hammer solution again is ideal.   I In other words, Hammer provides a transitional platform whereas IA64 doesvK not.  So Hammer, not IA64, is the logical inheritor of the high-volume IA32eC space, while IA64 competes as best it can with the lower-volume buta higher-margin big boys.p     After all, IBM dumped AMDs@ > desktop.  Again, a peak under the tent flap.  I'm sure IBM andA > Compaq will rattle the X86-64 sabre to get nice IA64 discounts.s  H Athlon is compatible with Px and competes directly, so vendors will playK Intel off against AMD, and vice versa, when they can.  Hammer vs. Itanic issK a completely different ball game:  *users* will decide which they want, ande  vendors will have to provide it.   ...a  F > >> So I guess in the next 7-8 years IA64 will be running most of the= > >> commercial apps and a handful running on IBM mainframes.i > >aJ > > You can guess whatever you want.  Just don't expect others to buy into yourI > > fantasies and make them self-fulfilling:  some people (and companies)c preferL > > to create the future rather than simply drift along on whatever currents it > > may bring. > >c >i@ > No... see the analyst above.  That's his opinion, not fantasy.  J Learn to read, Rob:  the analyst (if you mean Bill, with whom I worked forH the better part of a year at EMC and for whose opinion in such matters II have some respect, though I can't say he's a great engineer) said not onee9 word about what hardware the systems would likely run on.l   - bill   >r > Robm >r   ------------------------------  % Date: Tue, 28 Aug 2001 16:56:26 -0400i- From: JF Mezei <jfmezei.spamnot@videotron.ca> * Subject: Gateway lays off 25% of workforce, Message-ID: <3B8C0567.517E881B@videotron.ca>  N CNN just reports that Gateway will layoff about 25% of its worlwide workforce,# including 15% of the USA workforce.   K If Gateway is doing that poorly, one would assume that Compaq would also be I hurting. Will Compaq follow the lead of its competitors and also announcedM massive layoffs and how will that impact Compaq's wounded non-wintel business % that is mourning the death of alpha ?    ------------------------------    Date: 28 Aug 2001 13:48:42 -05009 From: kaplow_r@eisner.encompasserve.org.mars (Bob Kaplow)wD Subject: Re: Looking for Digital Serial Number Identication Resource3 Message-ID: <pRGgG5yt$tdH@eisner.encompasserve.org>o  g In article <Hxvi7.846$bB1.38998@news.cpqcorp.net>, hoffman@xdelta.zko.dec.nospam (Hoff Hoffman) writes: E >   Here are some of the classic manufacturing production site codes:m >  >     AY - Ayre, Scotland, UKh$ >     CX - Colorado Springs, CO, USA >     NI - Salem, NH, USAi >     WF - Westfield, MA, USAp > F >   Off the top, I don't recall the Fremont CA site code.  There have E >   been a number of other manufacturing sites around over the years,.A >   and there may be (are?) now other active manufacturing sites.m    L I'd guess that our first-day-order Wildfire came from the Freemont CA TandemI plant, but by then the serial numbers had changed from the traditional 10tD character codes we're discussing, to an undecypherable 6 digit code.  ! Some other codes I've seen often:r  - 	AB	Albuquerque NM?	old VAXen and early Alphar 	AG	????		DECservers 	AS	????		DECservers  	KA	????		old VAXen, early Alpha  	ZG	????		all my HSx controllers    C Wasn't there once a plant on Phoenix that made terminals, and such?n   ------------------------------    Date: 28 Aug 2001 12:01:37 -07001 From: nothome@spammers.are.scum (Malcolm Dunnett)lD Subject: Re: Looking for Digital Serial Number Identication Resource, Message-ID: <02KnGUlnaPbO@malvm5.mala.bc.ca>  4 In article <pRGgG5yt$tdH@eisner.encompasserve.org>, =   kaplow_r@eisner.encompasserve.org.mars (Bob Kaplow) writes:y > # > Some other codes I've seen often:p > " > 	KA	????		old VAXen, early Alpha 		Kanata, Ontario, Canadao   ------------------------------  # Date: Wed, 29 Aug 2001 00:30:16 GMTo2 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)D Subject: Re: Looking for Digital Serial Number Identication Resource2 Message-ID: <sIWi7.901$bB1.41939@news.cpqcorp.net>  k In article <DKBi7.123$p81.87382@typhoon1.gnilink.net>, "John Fredrickson" <jafred@bellatlantic.net> writes:f  G   Follow-ups set to comp.os.vms, to try to reduce the cross-postings...>  M :I have yet to get it to display anything. The graphics card is a Maxtor VGA,d  D   You might not get get anything with that widget.  Try removing it.  K :but when I attached the system to a monitor, keyboard, and mouse, the unitsG :powers up but displays no video. I also tried disconnecting the mouse,cL :keyboard, and monitor and connected a VT420 to the serial COM ports instead, :(9600,N,8,1), but again obtained no output.  F   I'd *guess* you are seeing the results of a graphics controller thatG   is not supported by OpenVMS -- each one of these widgets tends to be u2   a just enough different to screw up the drivers.   ..6 :When I get a console prompt, I'll learn for about it.    N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  # Date: Tue, 28 Aug 2001 19:02:55 GMTu+ From: Jeff Campbell <jcampbell@ins-msi.com>n: Subject: Re: MicroVAX II - local register I/O programming?+ Message-ID: <3B8BE37A.3FBAB947@ins-msi.com>t   sword7@speakeasy.org wrote:a > . > Jeff Campbell ?jcampbell@ins-msi.com? wrote: > ? Timothy Stark wrote:B > ?? Well, I need complete specs about TOY, scratch pad RAM, etc.. > J > ? Ok. The TOY clock chip contains 64 8-bit registers. The first ten holdG > ? the time of year. The next 4 are the control/status registers namedrJ > ? CSR A, CSR B, CSR C, and CSR D. The remaining 50 bytes are the scratch > ? pad. >  > ? Jeff Campbell  > ? n8wxs@arrl.net >  > Jeff Campbell: > K > Thank you for information!  I save it for my VAX emulator to be finished.rF > However, how about CPU registers like 20080000 location?  VMB in ROM6 > still am waiting for any bits in 20080000 forever...  B I posted another response to you over in comp.sys.dec that has theB layout of the BOOT and DIAGNOSTIC REGISTER 20080000. If you're not. able to find it lemme know and I'll repost it.   >  > Thank you! >  > -- Tim Stark >  > --4 > Timothy Stark   ???     Inet: sword7@speakeasy.orgL > --------------------------------------------------------------------------G > "For God so loved the world, that he gave his only begotten Son, thatrJ > whosoever believeth in him should not perish, but have everlasting life.0 > Amen." -- John 3:16 (King James Version Bible)    
 Jeff Campbell  n8wxs@arrl.net   ------------------------------  % Date: Tue, 28 Aug 2001 19:59:48 -0000e From: sword7@speakeasy.org: Subject: Re: MicroVAX II - local register I/O programming?/ Message-ID: <tonu1ksg9v6200@corp.supernews.com>o  , Jeff Campbell <jcampbell@ins-msi.com> wrote:D > I posted another response to you over in comp.sys.dec that has theD > layout of the BOOT and DIAGNOSTIC REGISTER 20080000. If you're not0 > able to find it lemme know and I'll repost it.   Jeff:9  G Yes, I found that in comp.sys.dec after I replied this.  Thank you for gB information.  I reviewed your two postings.  Why omission in some @ registers?  I noticed that PIE, AIE, etc. are not used. in CSRB.  E I did implemented that into my VAX emulator.  VMB in ROM finally was  D happy.  I was so impressed to noticed that LED bits in BDR register.B It was counted down to C according to my debug log file.  However,@ VMB scanned entire memory map instead of just main memory. I was> trying figured out.  I learned that I have to set bootstrap in@ progress bit in CPMBX before I started to execute VMB.  After it: was done, I finally got a '>>>' prompt!  My screen showed:  	 TS10> runt= F E D C   <-- reported from my VAX emulator for BDR register.e    PC = 20040C9E 8 4l >>>   G That is all.  Does anyone know about '20040C9E'? Why did VMB displayed t that?   @ Do you know abot MSER, CEAR, and DEAR registers in 2008000 area?I (20080004, 20080008, and 2008000C) I have no such information about that..   Thank you!!p   -- Tim Stark   -- y, Timothy Stark	<><	Inet: sword7@speakeasy.orgJ --------------------------------------------------------------------------F "For God so loved the world, that he gave his only begotten Son, that H whosoever believeth in him should not perish, but have everlasting life.. Amen." -- John 3:16 (King James Version Bible)   ------------------------------  # Date: Tue, 28 Aug 2001 22:13:42 GMTa+ From: Jeff Campbell <jcampbell@ins-msi.com> : Subject: Re: MicroVAX II - local register I/O programming?* Message-ID: <3B8C1026.5F2F387@ins-msi.com>   sword7@speakeasy.org wrote:o > . > Jeff Campbell <jcampbell@ins-msi.com> wrote:F > > I posted another response to you over in comp.sys.dec that has theF > > layout of the BOOT and DIAGNOSTIC REGISTER 20080000. If you're not2 > > able to find it lemme know and I'll repost it. >  > Jeff:  > H > Yes, I found that in comp.sys.dec after I replied this.  Thank you forC > information.  I reviewed your two postings.  Why omission in someeB > registers?  I noticed that PIE, AIE, etc. are not used. in CSRB.  8 I dunno. You will have to resurect DEC and ask them. 8-)   > F > I did implemented that into my VAX emulator.  VMB in ROM finally wasF > happy.  I was so impressed to noticed that LED bits in BDR register.D > It was counted down to C according to my debug log file.  However,B > VMB scanned entire memory map instead of just main memory. I was  @ 'C' is displayed while the boot code is initializing the consoleE program memory area. Part of this process is the building of a bitmap @ table that flags all 'good' physically addressable memory pages.  F The MicroVAX II has a limit of 16 MB of physical memory. You will need> to limit your emulator to that amount for a CPU type of UVAX2.  E The original VAX architecture defines the addressable physical memoryiD as  24 bits or 30 bits in size. The console ROM code is checking forE "real" memory top-down from the top of the physical address space. It G will locate the console's memory area at the highest available address.:G The memory map bitmap will be placed immediately below. The bitmap willeE occupy as many pages of memory as necessary to map all "real" memory.w/ This bitmap will be used by the bootstrap code.   F The bitmap does not map itself nor the 2 pages of console memory above it.   D The probe of memory available must be able to find at least 64 KB of good memory.  @ > trying figured out.  I learned that I have to set bootstrap inB > progress bit in CPMBX before I started to execute VMB.  After it< > was done, I finally got a '>>>' prompt!  My screen showed: >  > TS10> run.? > F E D C   <-- reported from my VAX emulator for BDR register.w >    PC = 20040C9E  A The address is in the halt mode ROM space. I dunno what that haltI address is.    > 8 4n > >>>d > H > That is all.  Does anyone know about '20040C9E'? Why did VMB displayed > that?  > B > Do you know abot MSER, CEAR, and DEAR registers in 2008000 area?K > (20080004, 20080008, and 2008000C) I have no such information about that.e  - MSER: 20080004 - memory system error registers  4      <31:10>   9   8   7   6   5   4   3   2   1   05      read as  mem mem cpu cpu cpu dma  ms     wrw para5       zero    cd1 cd0 nxm lpe qpe qpe leb     par enb    Bit 2 is unused, read as zero.  
 The bits are:   @     mem cd: memory code bits. loaded on parity errors. read only
     ------"       00  Q22-Bus memory or device       01  KA630 on-board memorys#       10  Memory expansion module 14#       11  memory expansion module 2i  0     cpu nxm: CPU non-existent memory error. r/w.  7     cpu lpe: CPU local address space parity error. r/w.   9     cpu qpe: CPU Q22-Bus address space parity error. r/w.   9     dma qpe: DMA Q22-bus address space parity error. r/w.g  /     ms  leb: memory system lost error bit. r/w. +              set on multiple parity errors.t  A     wrw par: write wrong parity. r/w. 1 = bad par , 0 = good par.n  @     par enb: parity enable. enables parity error detection. r/w.%              1 = enable, 0 = disable.m  A The error bits are cleared by writing a '1'. Writing a '0' has no  effect.t  * CEAR: 2008008 - CPU error address register       <31:15> unused - read as zero.    <14:00> local memory address bits : <23:9> @            Valid only when MSER bits CPU LPE or CPU QPE are set.B            The value in the low word is the faulting page address.  * DEAR: 200800C - DMA error address register       <31:15> unused - read as zero.    <14:00> local memory address bits : <23:9> 3            Valid only when MSER bit DMA QPE is set.pB            The value in the low word is the faulting page address.   > 
 > Thank you!!f >  > -- Tim Stark >  > --4 > Timothy Stark   <><     Inet: sword7@speakeasy.orgL > --------------------------------------------------------------------------G > "For God so loved the world, that he gave his only begotten Son, that J > whosoever believeth in him should not perish, but have everlasting life.0 > Amen." -- John 3:16 (King James Version Bible)   HTH,   Jeff n8wxs@arrl.net   ------------------------------  % Date: Tue, 28 Aug 2001 21:48:16 -0500m1 From: "David J. Dachtera" <djesys.nospam@fsi.net> $ Subject: My VMS Wish List (features)' Message-ID: <3B8C57F0.F6BC8828@fsi.net>   G In case I'm wrong, and VMS does survive, here's a list of features that D I think could be useful in OpenVMS-IA64 (and maybe backported to the, last supported OpenVMS-Alpha and/or -VAX)...  E Hoff - if you're out there, should I e-mail these to your personally?8   Facilities:p  	 Librarianw@ 	Add support for .CLBs (Command procedure Libraries - see below)   DCL:  " Additional/enhanced functionality:+ - Add support for floating point datatypes.eA - Add support for .CLBs (Command procedure Libraries - see below)s. - Add support for "long" strings (>1024 bytes)  ' Additional/enhanced Verbs and Keywords:v   CREATE/MAILBOX logical_nameb 	/PERMANENT (requires PRMMBX)e@ 	/TEMPORARY (requires TMPMBX, assigns a channel stored in global)         symbol DCL$MBX_CHAN_logical_name)  	/BUFFER_QUOTA=value@ 	/SYMBOL - returns mailbox device specification in global symbol         DCL$MBX_ID   DELETE/MAILBOX logical_namei9 	Requires PRMMBX or TMPMBX, as appropriate. For temporaryl4         mailbox, requires the value of global symbol/ 	DCL$MBX_CHAN_logical_name from CREATE/MAILBOX.e   ENQUEUE lock_name/qualifiers 	/EXCLUSIVEs 	/READ_ONLYg   RELEASE ( 	/LOCK lock_name	Releases the named lock/ 		/DEQUEUE	Dequeues the lock request if not yet !                         	granted.d5 	/ENTRY entry_number (identical to SET ENTRY/RELEASE)y   INCLUDE {filespec|pathspec}a? 	Processes a specified command procedure segment at the currenty         depth.2 	Reasoning: see description of F$DECLARE(), below.$ 	Supports CDD/Repository (/FROM=CDD)@ 	Supports Command procedure Libraries (/FROM=LIBRARY[=filespec],2         default = source library of current depth)   @{filespec|pathspec}, 	Add support for Command procedure LibrariesG         (/FROM=LIBRARY[=filespec], default = source library of current t         depth)+ 	Add support for CDD/Repository (/FROM=CDD) # 	Add support for /ENTRY_POINT=labele   SET HOST? 	Add support for SYS$INPUT pointing to other than a terminal tor1         RTPAD, LTPAD, DTEPAD, HSCPAD, all others.a/ 	Add support for /INPUT={filespec|pathspec} andr&         /FROM={CDD,LIBRARY[=filespec]}= 	Restore support for /SCSI (restore HSZTERM$SCSIPAD to fully r         supported status)d  H Modify READ so that /TIMEOUT works with devices other than terminals, or+ at least with both mailboxes and terminals.s  6 Modify READ to work with keys set up using DEFINE/KEY.   SET [NO]ARROW_KEYS: 	Allows cursor control key sequences to be received by DCLI         procedures via INQUIRE and READ. When NOARROW_KEYS is in effect, o:         cursor keys may set up using DEFINE/KEY to return  	user-specified strings.   SHOW ARROW_KEYSe    ( Lexical Function Additions/Enhancements:  
 F$GETJPI()F Add keyword ARROW_KEYS to accompany enhanced commands above (boolean).  ( F$GETENV( symbol_name ) (not privileged)E Doument this function and provide support for any variable defined inoH the console environment. Return $STATUS as %x00008140 if symbol does not exist.  $ F$SETENV( symbol_name ) (privileged)A Support for any user-writeable symbol in the console environment.'6 Return $STATUS as %x00008140 if symbol does not exist.   F$LOCK( lock_id, keyword )4 Alternative to ENQUEUE and RELEASE/DEQUEUE commands. - Keywords (list supported)  	DEQUEUE 	ENQUEUE
 	EXCLUSIVE
 	READ_ONLY 	RELEASE    F$SYMBOL( symbol_name, keyword ) - Keywords: , 	DEPTH	- Procedure depth at which symbol was$                   created/F$DECLAREd 	EXISTS	- Return TRUE or FALSE8 	SIZE	- Returns length of string or size of integer/real
 		  (numeric)f  	TABLE	- Returns LOCAL or GLOBAL< 	TYPE	- Returns STRING or INTEGER or REAL (same as F$TYPE())8 	VALUE	- Returns the contents of the symbol, always as a
 		  string
 	others...  ; F$PROCEDURE( depth ) or F$ENVIRONMENT( "PROCEDURE", depth )sF - Returns filespec. of the command procedure at a specified depth (may  be other than the current depth)   F$FAB( lnm, keyword )s1 - lnm is logical name specified in OPEN statement 8 - Keywords: FILESPEC, CHANNEL, others that may be usefulD   (and not otherwise be available, such as from F$FILE_ATTRIBUTES())   F$RAB( lnm, keyword )t1 - lnm is logical name specified in OPEN statementt - Keywords: 9 	RECOUNT	- returns the byte count from the last transfer -6 		  (useful for determining whether DCL can manipulate  		  the string (record) read in)7 	RRN	- Returns the relative record number of the recordr& 		  from the most recent READ or WRITE/ 		  (Sequential or Relative; Indexed may returnl" 		  unpredictable value (garbage))7 	RFA	- Returns the three-byte integer value in a stringw" 	other keywords that may be useful  
 F$GETSYI() - Add keywords: < 	UPTIME	- Returns the current system up-time as a delta time 		  expression (string)a 	FREE_LIST_SIZEl5 		- Returns the current size of the free page list ast 		  an integer 	MOD_LIST_SIZE6 		- Returns the current size of the modified page list 		  as an integerr   F$COUNT( keywords, mode )e
 - Keywords8 	USERS		- Returns the current count of users as would be 			  displayed by SHOW USERS6 	PROCESSES	- Returns the current count of processes as%  			  would bedisplayed by SHOW USERSoF - Mode (supports list of modes, counts returned are cumulative for all list elements)
 	[NO]BATCH 	[NO]INTERACTIVE 	[NO]NETWORK
 	[NO]OTHER 	[NO]SUBPROCESSl  0 F$DECLARE( symbol_name, data_type, size, table ) - Data types8 	STRING (static only, dynamic strings are still assigned 		traditionally) 	SIGNED[_INTEGER]t 	UNSIGNED[_INTEGER]  	REALn - Size (numeric)? 	Size in bytes of a static string (any legal value for a statice 	string descriptor)iA 	Size in bytes of a binary datatype corresponding to a field sizel) 	supported by the underlying architecturen
 	or math RTL.t - Table  	GLOBALa 	LOCAL  $ F$FORMAT( symbol_name, edit_string )B - DCL interface to the BAS$FORMAT() built-in function RTL routine.   F$TERMCAP( keyword )A Returns escape sequences or values. Keywords as per SMGTERMS.TXT.s  . I'm sure there's more that I could think of...   -- A David J. Dachtera  dba DJE Systemss http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/-   ------------------------------  % Date: Tue, 28 Aug 2001 23:51:44 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca>g( Subject: Re: My VMS Wish List (features)+ Message-ID: <3B8C66CF.567C0B4@videotron.ca>    ok: my contribution:  / IO$M_TIMEOUT support for TCPIP QIO connections.n  I As a matter of fact, putting IO$M_TIMOUT for all QIO for any medium whereo0 transfer of data is not assured to be immediate.   ------------------------------  # Date: Tue, 28 Aug 2001 19:26:16 GMT22 From: hoffman@xdelta.zko.dec.nospam (Hoff Hoffman)G Subject: Re: OpenVMS Common Source Code? (was Re: EV7 will never ship?)I2 Message-ID: <sfSi7.894$bB1.41429@news.cpqcorp.net>  [ In article <9mgp89$4ja$1@pegasus.csx.cam.ac.uk>, nmm1@cus.cam.ac.uk (Nick Maclaren) writes:n  F   OpenVMS VAX does not use the same source code pool as OpenVMS Alpha.H   (Various components do use common code across OpenVMS VAX and OpenVMS I   Alpha, of course, but there are two seperate source code pools in use.)n  I   We provided a no-broken-code statement on OpenVMS VAX starting with the H   OpenVMS VAX V6.0 release, and this and the lack of certain underlying G   hardware support both preclude various kernel-mode changes.  So yes, cI   there are cases where you can get stuck without a feature when you are oI   using the OpenVMS VAX platform -- the salient example here is Java, as sG   Java mandates IEEE floating point support and VAX does not have that.e  H   The problem reporting and problem tracking system is common across theH   two (and soon to be three) platforms, and across a variety of layered    products.-  G   I expect to use the same operating system source code files for both lI   OpenVMS Alpha and OpenVMS IPF, and folks here expect to make available -I   support for the next-generation OpenVMS Alpha systems, for the DII COE nG   work, and other projects -- not just the same tools and common code, -G   but the same source code pool as is planned for use with OpenVMS IPF.CI   (I certainly plan to use the same code base for the source code control 4   system itself, regardless of the target platform.)  C   The target for the port is source compatibility, meaning that thelF   application source code can be hauled across and rebuilt -- we will C   want that for ourselves, obviously.  (Though the operating system E   kernel code itself does tend to be rather less portable and rather eG   more dependent on the underlying hardware than does application code  E   using documented interfaces.  This means that the operating system  E   kernel itself will have some conditional code and some code modulesn   that are platform-specific.)  C   If there are specific compatibility concerns, I can (attempt) to e"   address them here (or off-line).  N  ---------------------------- #include <rtfaq.h> -----------------------------N       For additional, please see the OpenVMS FAQ -- www.openvms.compaq.com    N  --------------------------- pure personal opinion ---------------------------L    Hoff (Stephen) Hoffman   OpenVMS Engineering   hoffman#xdelta.zko.dec.com   ------------------------------  % Date: Tue, 28 Aug 2001 20:34:04 -0500-1 From: "David J. Dachtera" <djesys.nospam@fsi.net> 3 Subject: Re: still can't get my UCX licensed??????? ' Message-ID: <3B8C468C.DB096C55@fsi.net>e   Hoff Hoffman wrote:i > [snip]K >   I am adding a paragraph to the OpenVMS FAQ on this topic, since you arer2 >   not the first to make this particular mistake.  G It might be a good idea to mention that unlike UN*X and W/9x, W/NT, W2KcC and so on, TCP/IP is supplied and licensed separately from VMS. The0? uniqueness of the paradigm may be a contributing factor in suchr
 confusion.   My $0.02...s   -- o David J. Dachteray dba DJE Systemse http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/a   Poor old Terry Hardy!f They buried him today. He lived the life of Riley while Riley was away...g   ------------------------------  % Date: Tue, 28 Aug 2001 20:53:45 +0200t" From: "Hans Vlems" <hvlems@iae.nl>% Subject: Re: TCPIP V5.0 BIND questionn( Message-ID: <9mgp0c$j17$1@news.IAEhv.nl>  * Both images are installed, I checked that:  5 $ install list /full sys$system:tcpip$bind_server.exew  , DISK$VAXVMSRL072:<SYS0.SYSCOMMON.SYSEXE>.EXE    TCPIP$BIND_SERVER;1%                     Open Hdr Shar Prvw(         Entry access count         = 267*         Current / Maximum shared   = 1 / 1&         Global section count       = 2         Privileges = OPER   : $ install list /full sys$system:tcpip$bind_server_xfer.exe  , DISK$VAXVMSRL072:<SYS0.SYSCOMMON.SYSEXE>.EXE    TCPIP$BIND_SERVER_XFER;1l%                     Open Hdr Shar Prvw&         Entry access count         = 0*         Current / Maximum shared   = 1 / 0&         Global section count       = 2         Privileges = OPER0   $h  K Thanks for you suggestion however, feel free to post more since I'm stumpedi on this one...   Hans  ; Jason Fountain <Jason.Fountain@compaq.com> wrote in message-$ news:3B8BCD2E.A8BB0F2B@compaq.com...J > For starters, you could verify that the images were installed correctly: >i: >     $install list /full sys$system:tcpip$bind_server.exe? >     $install list /full sys$system:tcpip$bind_server_xfer.exe- >- > -jason >  > Hans Vlems wrote:1 >:J > > Today I tried to run BIND 8 for the first time. I've used UCX V4.x and BIND > > 4, no problems.  > >a
 > > Versions:- > >3 > > $ tcpip sho vers > >>: > >   DIGITAL TCP/IP Services for OpenVMS VAX Version V5.03 > >   on a VAXstation 3100/GPX running OpenVMS V7.2s > >y > > $  > >mJ > > No patches have been applied at this moment. This machine is part of a twoI > > node NI cluster. TheH > > other node runs TCPIP and DECnet-Plus too. In @TCPIP$CONFIG the BIND server > > was enabled J > > and next I ran @TCPIP$BINDSETUP. The BIND server was started and after that > > I tried nslookup.eK > > That did not return the server information so I looked whether the BINDu > > process was running.3 > > It wasn't and the log file showed this message:t > >V > > $a! > > $ ON CONTROL_Y THEN GOTO EXITp > > $ SET NOON > > $tH > > $ IF F$TRNLNM("TCPIP$BIND_SERVER_DATA","LNM$SYSTEM") .EQS. "" THEN -C > >         DEFINE TCPIP$BIND_SERVER_DATA SYS$SPECIFIC:[TCPIP$BIND]  > > $ 7 > > $ PURGE /NOLOG /KEEP=4 TCPIP$BIND_SERVER_DATA:*.LOGb > > $e> > > $ EXE = F$TRNLNM ("TCPIP$BIND_SERVER_IMAGES","LNM$SYSTEM"). > > $ IF EXE .EQS. "" THEN EXE = "SYS$SYSTEM:" > > $aH > > $ TCPIP$BIND_SERVER_XFER :== $ SYS$SYSTEM:TCPIP$BIND_SERVER_XFER.EXEC > > $ TCPIP$BIND_SERVER      :== $ SYS$SYSTEM:TCPIP$BIND_SERVER.EXEr > > $t > > $ TCPIP$BIND_SERVER L > > Sun 26 21:03:37 NOTICE: starting.  Digital TCP/IP Services for OpenVMS - > > BIND 8.t > > 1.2 V5.0-9? > > %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtualn > > address=FFFFFFFF, PC > > =0012036B, PSL=0BC00000l > > 6 > >   Improperly handled condition, image exit forced. > > 8 > >         Signal arguments              Stack contents > >m5 > >         Number = 00000005                00000000o5 > >         Name   = 0000000C                20FC0000h5 > >                  00000001                7FEB79D4r5 > >                  FFFFFFFF                7FEB7998 5 > >                  0012036B                00034D3F 5 > >                  0BC00000                00000000a5 > >                                          7FEB7940e5 > >                                          00000000 5 > >                                          00000000S5 > >                                          00158D14  > >D > >         Register dump4 > > F > >         R0 = 0400000F  R1 = FFFFFFFF  R2 = 00000000  R3 = 7FEB7980F > >         R4 = FFFFFFFF  R5 = 00000000  R6 = 0000000F  R7 = 0000000FF > >         R8 = 0003258C  R9 = 000A2F98  R10= 000A2D00  R11= 000A2CA8F > >         AP = 7FEB78C8  FP = 7FEB7888  SP = 7FEB7904  PC = 0012036B > >         PSL= 0BC00000n > >t > > $u > >t > > Any ideas? > >- > > Hans Vlems >r   ------------------------------  % Date: Tue, 28 Aug 2001 16:25:08 -0400a From: Bob Kenney <rmk@unh.edu>B Subject: Using OpenVMS & DECprint with mid to high-speed printers.' Message-ID: <3B8BFE24.92D466C9@unh.edu>h   	Folks,   : 	We're trying to find options as far as mid to large-scaleI    printing is concerned, but only in conjunction with using the DECPrintbG    Supervisor environment on OpenVMS.  We've tried out Savin/MicropressnI    and it's become a wash.  We're probably going to try Xerox next - dualpF    DocuPrint 65's would be just about right for our size.  Still, whatJ    we'd like is to do some CYA and find other DECPrint users who are doingG    large scale printing (up to 15000 pg jobs), and what kind of printerrE    manufacturers in the 65-100 pg/minute range can be printed to fromeK    DECPrint.  No corporate marketing goons need apply: I only want feedbacke    from actual DECPrint users.      
 	Thanks much.1     -- ,   Bob Kenney   ------------------------------   Date: 28 AUG 2001 16:05:55 GMT4 From: karcher@thuria.waisman.wisc.edu (Carl Karcher)% Subject: Re: V5.5-2 Password Recoveryo6 Message-ID: <28AUG01.16055539@thuria.waisman.wisc.edu>  A In a previous article, "Neil Rieck" <n.rieck@sympatico.ca> wrote:   L ->My busy little AlphaServer-4120 (EV5/300MHz) averages 1 million guesses inM ->273 seconds. Since there are 38^6 six character passwords, a worst case runmH ->would require 3010936384 guesses. Divide this number by 1M and you getJ ->3010.9 which then is multiplied by 273 then divided by 3600 to yield 228 ->hours or 9.5 days.  C You can do somewhat better than that by using hpwd.mar (do a googleeA search) instead of the $hash_password service. Either method will-4 run circles around using a rewrite of hpwd.mar in C.   ------------------------------  % Date: Tue, 28 Aug 2001 21:17:06 -0400l) From: "Neil Rieck" <n.rieck@sympatico.ca> % Subject: Re: V5.5-2 Password Recovery : Message-ID: <zoXi7.35120$zP.2317269@news20.bellglobal.com>  A "Carl Karcher" <karcher@thuria.waisman.wisc.edu> wrote in messageJ0 news:28AUG01.16055539@thuria.waisman.wisc.edu...C > In a previous article, "Neil Rieck" <n.rieck@sympatico.ca> wrote:  >cK > ->My busy little AlphaServer-4120 (EV5/300MHz) averages 1 million guesses  inK > ->273 seconds. Since there are 38^6 six character passwords, a worst caseV runpJ > ->would require 3010936384 guesses. Divide this number by 1M and you getL > ->3010.9 which then is multiplied by 273 then divided by 3600 to yield 228 > ->hours or 9.5 days. > E > You can do somewhat better than that by using hpwd.mar (do a google C > search) instead of the $hash_password service. Either method wille6 > run circles around using a rewrite of hpwd.mar in C.   Thanks for the tip(s)/.n  + I found "hpwd.mar" (MACRO-32 for VAX) here:B- http://www.agh.cc.kcl.ac.uk/files/vms/oldpds/e? which I guess we could convert for Alpha use via $MACRO/MIGRATEl  $ Surprisingly, I found "hpwd.c" here:@ http://www.openvms.compaq.com/freeware/FREEWARE50/XVMSUTILS-114/  = This always makes for good reading if you're a bit banger :-)l  
 Neil Rieck Kitchener/Waterloo/Cambridge,a Ontario, Canada.! http://www3.sympatico.ca/n.rieck/    ------------------------------  % Date: Tue, 28 Aug 2001 21:21:46 -0400e) From: "Neil Rieck" <n.rieck@sympatico.ca>V% Subject: Re: V5.5-2 Password Recoveryc: Message-ID: <XsXi7.35167$zP.2320983@news20.bellglobal.com>  7 "Joshua Cope" <Joshua.Cope@Compaq.com> wrote in message/$ news:3B8BCC95.E58BDE42@Compaq.com...J > > Case sensitivity often causes problems with our Unix students. However havingL > > it as an option selectable on either a system-wide or individual account basisE > > would be a good idea.e >iB > Case sensitive passwords, selectable on a per-account basis, was implemented,D > as part of the COE project, and will make it into a future OpenVMS release.I > I'm not sure which one yet, but I'd guess sometime after OpenVMS V7.3-1c andf > before the first Itanium SDK.t > H > The flag basically opens up the same password space found on most UNIX@ > systems, including mixed-case and non-alphanumeric characters. >n> > ------------------------------------------------------------8 > The above opinions and information are not necessarily' > those of Compaq Computer Corporation.i> > ------------------------------------------------------------  K This is good news since we'd want it on all system accounts or any accounts J exposed to the internet (whether there is a firewall or not). I'm assuming1 it will be enabled with a new /FLAG in authorize?F  
 Neil Rieck Kitchener/Waterloo/Cambridge,r Ontario, Canada.! http://www3.sympatico.ca/n.rieck/    ------------------------------  % Date: Tue, 28 Aug 2001 14:09:02 -0400 2 From: "Sue Skonetski" <susan.skonetski@compaq.com> Subject: VMS Sessions at CETSW2 Message-ID: <y6Ri7.890$bB1.41649@news.cpqcorp.net>   Dear Newsgroup,)  L I have made a request to Encompass for ALL sessions at CETS that mention VMSL which they have kindly sent,  enclosed is what I have received.  Considering; that there are always changes please do check update.daily.r  J Please note that Mark Gorhams session is at the Hilton.  The VMS receptionF is Tuesday night at 8 and you need an invitation, which you can get atA Mark's session, the campground and the VMS demo in the tradeshow.    Sue     
       1007         Monday, September 10
       1:00 PME
       208A         Thursday, September 13
       1:00 PME
       208A         Advanced6      Tru64T TruCluster for the VMScluster Professional4       Rochelle Lauer    Yale University Physics Dept  D       This hands-on workshop is designed to provide Tru64 TruClusterH technical information to attendees that have VMScluster experience. ThisH session provides hands on experience with a Tru64 TruCluster. TruClusterI details are presented using a VMScluster perspective and assumes in-deptht VMScluster knowledge.R        
       1008         Monday, September 10
       2:15 PMn
       210A         IntermediateH      Global Mailing Lists - A Case Study of a Web-enabled Administration ToolK       J Lance Wilkinson    Penn State University Library Computing ServicesE  K       Historically, global mailing list management at Penn State UniversitycD Libraries used manually edited distribution list files and hard copyH authorization forms to define system-wide aliases under PMDF. User-levelK membership management and automatic subscribe/unsubscribe facilities, usingC1 PMDF MAILSERV or the like, were not incorporated.   L       A web-enabled facility was implemented running under the COMPAQ SecureF Web Server (based upon Apache 1.3.6) on OpenVMS. Used for mailing listB creation, deletion and membership management, it allows authorizedH University Library staffers to manage membership in the mailing lists toF which they were granted control. This offloads almost all mailing listJ management to designated University Libraries staff and implements all the validation checks required.   H       This session presents the design of the web-enabled Global MailingK List facility as currently implemented at Penn State's University LibrariesED and examines a few of the implementation considerations encountered.        
       1042         Wednesday, September 12o
       9:30 AM        Hilton - Oceanside         IntermediateL      OpenVMST DII COE Initiative: Tools, Experiences and Benefits of Porting from UNIX to OpenVMS0       Joshua Cope    Compaq Computer Corporation  E       This session describes how to use and take advantage of the newRC features in OpenVMST AlphaT V7.2-6C1 operating system from a system)K management and applications development perspective. These include new filenH system, C runtime library, TCP/IP and security features. We also discussH layered products and utilities packaged with 7.2-6C1 and how Compaq usedD them to port the COE (Common Operating Environment) Kernel from UNIXE (Solaris) to OpenVMS. OpenVMS V7.2-6C1 will be the first Compaq firstcK operating system to certify against V4.2 of the COE Kernel. Attendees learn K what the DII (Defense Information Infrastructure) COE Kernel is and what iteH looks like. Learn about availability and usage of tools used for portingK original UNIX software to OpenVMS and how to ensure compatibility with UNIX:
 environments.e        
       1046         Thursday, September 13
       9:30 AM2       Hilton - Capistrano          Intermediate2      PATHWORKS and Advanced Server Troubleshooting4       Michael Stewart    Compaq Computer Corporation  B       This session covers the methods that Compaq customer supportD specialists use to troubleshoot the Advanced Server for OpenVMST andB PATHWORKS. It also includes hints and tips for using supported andL unsupported utilities for troubleshooting. We also cover recent known issues/ and limitations and their fixes or workarounds.)        
       1047         Wednesday, September 12V
       2:45 PMi
       201B         IntermediateI      Using OpenVMST Performance Management Applications to Improve Systemn Performancec4       Barry Kierstein    Compaq Computer Corporation2       Bart Lederman    Compaq Computer Corporation  @       MONITOR, DEcamds and Availability Manager provide powerfulH capabilities for performance troubleshooting, capacity planning and loadI balancing of OpenVMS AlphaT and VAX platforms. Availability Manager showstH information important to managing Galaxy nodes on GS series machines forL OpenVMS V7.3. This is one of the first opportunities for users to understandK performance issues specific to the OpenVMS GS series machines. This sessionoH demonstrates what data the utilities can collect and how the data can beG analyzed. It also demonstrates how the utilities differ in the way theytG operate and how they address different areas of performance management.sL After this session, you should understand how to best utilize OpenVMS systemF management capabilities to enhance overall system performance. A basicC understanding of OpenVMS system management, DCL commands, accounts,x% privileges, quotas, etc. is required.         
       1050         Wednesday, September 12I
       1:15 PM        Hilton - Capistranou         Wednesday, September 12,
       4:15 PMa
       213A         Intermediate*      OpenVMST TCP/IP V5.1 Technical Update4       Yanick Pouffary    Compaq Computer Corporation  L       This session shows you how to get the most out of your TCP/IP OpenVMSTL applications including NFS, BIND and IP v6. We explain how to take advantageD of the anti-spam and cluster failover (Bind and Load Broker) product@ capabilities. Learn how these enhanced applications make networkI administration/management easier and more secure, and improve application  performance.        
       1051         Wednesday, September 12d
       1:15 PMh
       304A         Wednesday, September 12l
       2:45 PMv       Hilton - San Clementeo         IntermediateI      Maximize the Performance of your TCP/IP Stack on OpenVMS: Tuning NFSs1 and Troubleshooting TCP/IP to Improve Performance-3       Mark Hollinger    Compaq Computer Corporationa  L       This session discusses tuning and troubleshooting your TCP/IP network.L Every network administrator is concerned with optimizing network performanceF and having minimal disruption to their network services. These factorsJ directly impact a company's productivity and network costs, not to mentionI the reputation of the network manager. This session describes the tunableyL parts of the TCP/IP network and provides strategies for correcting problems.E We also cover the tuning features of the TCP/IP Services for OpenVMST H products and how to troubleshoot problems with each component, including4 FTP, SMTP mail, DNS/BIND, the kernel, and many more.        
       1054         Thursday, September 13
       2:30 PM/
       201A         Intermediate      OpenVMST Engineering Panelm4       Susan Skonetski    Compaq Computer Corporation  J       This panel session provides an informational, highly interactive andD fun forum in which the audience discusses specific problems and asksK technical questions of OpenVMS engineers and product managers. Participants E are encouraged to share their creative problem-solving techniques andy/ recommendations for future releases of OpenVMS.u        
       1058         Wednesday, September 12v
       8:00 AMu
       205A         Wednesday, September 12-
       1:00 PM$
       205A         Intermediate4      Oracle9i Real Application Cluster Configuration'       James Olsen    Oracle CorporationV  I       This session is intended to give attendees hands-on experience with F configuring Oracle Real Application Clusters (formerly Oracle ParallelF Server). Participants have the opportunity to install Real ApplicationB Clusters as well as learn how to configure the cluster for On-lineH Transaction Processing (OLTP) and DSS applications. Features of Oracle9i, Real Application Cluster are also discussed.        
       1067         Thursday, September 13
       8:00 AM 
       304B         IntermediateL      Implementing Successful eBusiness Projects with Oracle Rdb for OpenVMST,       Norman Lastovica    Oracle Corporation  H       This presentation offers a clear strategy, tips, and options for aC successful eBusiness implementation with Oracle Rdb as the back-endBJ database. In addition, it discusses new functionalities both on the latestA Rdb database version 7.0.7 (which includes support for Alpha EV68bK processors) and the planned version 7.1.0 (which includes full Galaxy PhasexI III support and extensive SQL enhancements), as well as its commitment toNC making the Rdb database available on Itanium. Come and hear how theeH combination of Oracle Rdb, OpenVMS, and AlphaT servers are put to use inJ some of the world's most "mission-critical" applications in companies like	 your own.O        
       1073         Monday, September 10
       2:15 PMd!       Hilton - Pacific Ballroom Br         Introductory7      Building Your Business' Future with Compaq OpenVMSu0       Mark Gorham    Compaq Computer Corporation  J       As businesses seek to understand the implications of moving to a newL e-business model, they realize the importance of working in partnership withD a vendor who has experience providing solutions for the world's mostK demanding IT environments. With over 20 years of experience as the trusted,LF enabling solution for these environments, Compaq OpenVMST provides theF baselineplus e-business infrastructure foundation to address:  How toK handle the complexity associated with moving to e-business?  How to ensure4D my systems can handle the unforeseen capacity and management scalingF requirements to come?  How to protect against data loss and maliciousF attacks?  How to ensure best of breed responsiveness to my employees,I partners and customers? The OpenVMS e-business strategy is to continue toDJ build leadership business-critical internet infrastructure solutions that,L in concert with its strategic partners, enable businesses to make a smootherL transition to this new business model. During the session, the next stage ofH OpenVMS' e-business rollout is shared, coupled with customer experiencesG with the a focus on:  OpenVMS e-business strategy  OpenVMS e-business K architecture  Growing forward with OpenVMS e-business  OpenVMS e-business0+ solutions at work  Putting it all together         
       1079         Thursday, September 13
       9:30 AM7       Hilton - La Jolla          IntroductoryD      OpenVMS System Resource Monitoring - Migrating DECamds Users to Availability Manager4       Barry Kierstein    Compaq Computer Corporation  F       Join us for an interactive discussion on Compaq's OpenVMS systemD resource monitoring applications - DECamds and Availability Manager.J Discussion includes the merits of both applications and their similaritiesF and differences. Provide input to future product requirements. SummaryK results will help define future product features as well as to define prior0 version retirement plans.         
       1082         Wednesday, September 120
       1:15 PM        Hilton - Lido A          Introductory0      The Experience of Running Oracle on OpenVMS*       Denay Williams    Oracle Corporation  I       Customers who currently run either Oracle7, Oracle 8i or Oracle Rdb5G meet to share their experiences - both good and bad - with other users.rI Representatives from Oracle 8i/9i development, Oracle Rdb development anduB Compaq's Oracle Relationship Team will listen to your comments andD suggestions, respond to them and take them back to Oracle and CompaqI management to be addressed. Customers benefit from hearing other people'sn. experiences and will exchange tips and advice.        
       1083         Wednesday, September 12t
       9:30 AMj
       201B         Thursday, September 13       11:00 AM
       304A         Intermediate       Oracle9i for OpenVMS Update*       Denay Williams    Oracle Corporation  K       Oracle is about to release version 9.0.1 of their database server fornH OpenVMST AlphaT systems. This session describes the new features in thatJ release. It also covers how Oracle's automated porting effort enables themL to release their OpenVMS version less than 90 days after the base release isH complete. The status of version 8.1.6 and 8.1.7 is discussed. Support ofD Oracle Parallel Server (OPS) is included. This session discusses howF Oracle's vision of an e-business platform includes an OpenVMS / OracleK back-end database server that is connected to other middle-tier applicationl servers and front-end tiers.        
       1092         Wednesday, September 12t
       8:00 AMo       Hilton - Lido Ag         Intermediate<      VAX VMS to ALPHA/ OVMS Migration - Issues and Solutions#       Tanmay Sahoo    Digital India   L       This session describes the issues involved in migrating an applicationF running on VAX / VMS to Alpha / Open VMS and the solutions identified.L Specifically the issues covered are:  OS specific changes related to 64 bitI addressing , data alignment, system services, upward compatibility of VMSiJ version used, kernel level code execution (privileged code constructs) andF handling global sections arising from the 512 byte page size vis--visK variable page size  Compiler specific changes related to compiler version,rC implementations (32 bit simulated to run in 64 bit or native 64 bitkK implementation) and compiler options  Middle ware specific changes relatedaC to availability of the layered products in Alpha and usage of CDD  K Execution specific changes related to linker differences, performance, codeeC optimization, executables migration,  Issues involved in migratingmE including user-written system services and other privileged shareableyL images, device drivers and performance monitors not supplied by Compaq, codeL that uses special privileges and code that uses internal OpenVMS routines or data        
       1101         Wednesday, September 12f       11:00 AM
       304A         Thursday, September 13
       8:00 AMw
       210A         Advanced/      Server Consolidation - Planning and Designu/       Kerry Main    Compaq Computer Corporationh  H       Server Consolidation projects are on the minds of many CIOs and ITL Directors. These projects allow companies to simultaneously reduce IT costs,G increase the level of service they offer and create additional businesstI flexibility. Attendees of this session have the opportunity to learn what1F needs to be considered in the planning, design and implementation of aG Server Consolidation project. The approach discussed is based on actualbF Server Consolidation project experience across different OS platforms.H Sample topics addressed include:  Business considerations - what issuesF must be considered in the consolidation effort to achieve a successfulJ solution that is appropriate for the organization  Data integration - theK importance of understanding how application data flow integrates with other I applications  SAN integration - more details on planning the SAN for thetH consolidated server environment and multi-site considerations  WorkloadJ Management vs. Partioning discussion  Migration processes and procedures,F e.g. the importance of change management  Pre-migration testing - theJ importance of both functional and load testing for such things as databaseG exports / imports, network copy times and user account / data migrationp
 strategies        
       1102         Wednesday, September 12p
       9:30 AMn       Hilton - Lido A-         Intermediate.      Server Consolidation - Birds of a Feather/       Kerry Main    Compaq Computer Corporationt  H       Compaq consultants with Server Consolidation experience will be on? hand to talk with you about your Server Consolidation projects.e        
       1113         Wednesday, September 12 
       9:30 AMp       Hilton - Capistrano-         Introductory(      OpenVMST and Linux Interoperability4       John Wisniewski    Compaq Computer Corporation  G       What can OpenVMS and Linux do together? Learn about two operatingcI systems that work and play well together and have more in common than yousK might think! Xwindows, Mail, WEBservices, Job Control, and File Sharing arehK examined as well as how to integrate these two great operating environmentscG for maximum interoperability. Please note: No NT systems will be harmedn during this session.        
       1116         Thursday, September 13
       1:00 PM        Hilton - La Jollaa         Intermediate8      PATHWORKS and Advanced Server for OpenVMS Q&A Panel2       Brad McCusker    Compaq Computer Corporation4       Michael Stewart    Compaq Computer Corporation  E       This is a Q&A panel comprised of members of engineering and thelK Customer Support Center. All questions related to PATHWORKS and/or Advanced L Server for OpenVMS are welcome. Stump the panel and maybe win a prize! Bring9 your tough questions and save yourself a call to the CSC!d        
       1120         Wednesday, September 12u
       4:15 PMr       Hilton - Oceanside         Introductory!      OpenVMST EDU License Programd4       John Wisniewski    Compaq Computer Corporation  I       The OpenVMS EDU License program began in November 2000 and has been J very successful in providing schools, colleges and universtities with FREEH OpenVMS licenses for academic, research and student use. Come hear aboutJ this Free License program, the Continuing CSLG program and how you can use< these Compaq Software and Services programs for your school.        
       1122         Wednesday, September 12F
       8:00 AMe       Hilton - San Clementea         Intermediate3      PATHWORKS and Advanced Server Technical Updater2       Brad McCusker    Compaq Computer Corporation  L       This session provides an update on the current status of the PATHWORKSB and Advanced server products and the plans for future versions andE deliverables, including Windows 2000 integration. The session gives aoJ technical overview of new functionality, including Member server, extendedG character sets, load balancing, NT-style printing and more. We focus ontJ configuring, implementing and using the new functionality. Also covered isJ the extensive work underway to improve performance, performance monitoringG and tuning, reliability and scalability. This session is a must for all L current PATHWORKS and Advanced server customers as well as anyone wishing to7 integrate OpenVMST with Windows NT and/or Windows 2000.A        
       1123         Wednesday, September 12        11:00 AM       Hilton - Capistranor         IntroductoryI      Integrating OpenVMST PathWorks with Windows NT/Windows 2000 File anda
 Print Serversh2       Brad McCusker    Compaq Computer Corporation  J       This session introduces the options for OpenVMS-based file and printL servers and integration of those servers in a Windows NT and/or Windows 2000G domain. PathWorks for OpenVMS V6 and Advanced Server for OpenVMS V7 areuC discussed, including a functional overview of the products, WindowsaI NT/Windows 2000 domain integration, networking considerations, OpenVMS/NTXJ single sign-on, management, and a comparison of the PathWorks and AdvancedB Server for OpenVMS products. Discussion of utilizing OpenVMS as an8 enterprise-wide file and print server is also discussed.        
       1130         Friday, September 14
       9:30 AMa       Hilton - San Clementer         Advanced8      Advanced C Programming on OpenVMST Operating System4       Stephen Hoffman    Compaq Computer Corporation  I       This session covers topics of interest to experienced C programmerseJ new to programming on OpenVMST systems, specifically covering introductoryH and intermediate level OpenVMS programming topics for C programmers withJ experience on other platforms. We also cover advanced OpenVMS integration,A development and portability topics for C programmers with OpenVMS C programming experience. The presentation covers low-level technicalnH bits-n-bytes including shared memory interlocking and the correct use ofL AlphaT system memory barrier primitives. Prerequisites: Must have a detailed5 understanding of C and C programming on some platformV        
       1131         Tuesday, September 11S
       9:15 AMa!       Hilton - Pacific Ballroom Ba         Tuesday, September 11a
       2:30 PMC
       304A         Intermediate      OpenVMS Technical Updatel4       Stephen Hoffman    Compaq Computer Corporation  I       This session includes technical highlights of the OpenVMST V7.3 and H OpenVMS AlphaT V7.2-2 operating system releases, as well as a preview ofH upcoming OpenVMS releases and an introduction to the OpenVMS port to theL Intel ItaniumT Processor Family (IPF). Topics include an overview of OpenVMSI on Itanium, the new Extended File Cache, cluster features, SMP and systemtI performance improvements, RAS features and plans, shadowing enhancements,rL new products licensed with OpenVMS, and many other features and enhancements% available in and planned for OpenVMS.t        
       1132         Thursday, September 13
       1:00 PMp       Hilton - Capistranop         Advanced      OpenVMST Hints and KinksA4       Stephen Hoffman    Compaq Computer Corporation  L       This technical session provides an insider's guide on taking advantageL of OpenVMS strengths, covering the following topics: Optomizing programs forK effective failover; Failover locking; Handling security features correctly;eI Designing shareable images; User-written System Services; Message utility L and command definition utility; OpenVMS Galaxy and OpenVMS Cluster; InsightsA into C++ and the OpenVMS Debugger. Details on certain useful (anda) undocumented) features are also included.         
       1133         Wednesday, September 12B
       4:15 PM        Hilton - La Jollah         Intermediate      Denizens of comp.os.vms4       Stephen Hoffman    Compaq Computer Corporation  H       This BOF is a discussion among the participants of the comp.os.vms
 newsgroup.        
       1152         Tuesday, September 11 
       4:00 PM 
       303B         Wednesday, September 12d       11:00 AM       Hilton - Oceanside         AdvancedA      OpenVMST AlphaT and VAX - Coexistence, Migration and Upgradea4       Stephen Hoffman    Compaq Computer Corporation  H       The upgrade of application source code from OpenVMS VAX to OpenVMSI Alpha is typically a simple process. This session describes the technicalpK and application programming considerations of coexistence and of successfulc& upgrades of more complex applications.        
       1156         Tuesday, September 11a
       1:00 PMw
       201A         Intermediate7      Deploying the Apache Web Server (CSWS) on OpenVMSTs3       Powell Hazzard    Compaq Computer Corporation   J       The Apache Web Server is the world's most widely deployed Web (HTTP)G server and is now available on OpenVMS using the name Compaq Secure WebDI Server (CSWS) for OpenVMS AlphaT. CSWS is provided as part of the OpenVMSeL e-business infrastructure technology suite and is fully supported by Compaq.K The session covers installation, configuration and usage of CSWS on OpenVMSsJ Alpha. After attending this session, participants should understand how toL deploy CSWS as a building block in their Internet and e-business applicationJ environment, thereby leveraging the open-source software development style? of Apache and the unparalleled level of testing and deployment.a        
       1157         Thursday, September 13
       1:00 PM        Hilton - Oceanside         Friday, September 14       11:00 AM
       304B         Intermediate-      Java and OpenVMST - Ready for Prime Timee3       Powell Hazzard    Compaq Computer Corporatione  K       The Java programming language is designed to allow deployment of JavanL applications on any platform that implements the Java Virtual Machine (JVM).B This session explains and demonstrates how to deploy existing JavaJ applications on OpenVMS AlphaT and the secrets of implementing Java ServerG Pages (JSP) using the Tomcat JSP implementation in conjunction with thesK Compaq Secure Web Server (based upon Apache). After attending this session,7K participants should be able to deploy Java applications on any platform anddG understand the considerations for deploying Java and JSP OpenVMS Alpha.         
       1158         Wednesday, September 12n
       4:15 PMp       Hilton - San Clementer         AdvancedC      Using the New BEA Weblogic Application Server V6.0 on OpenVMSTt.       John Apps    Compaq Computer Corporation  J       This session introduces the systems professional with the concept ofK using an Enterprise Java Bean application server as the foundation to buildiF an OpenVMS e-business enterprise. The focus is the integration of thisB application server to take advantage of the latest component-basedJ applications development environment native on OpenVMS. Examples of how toF instantiate this environment along with specific customer examples are
 presented.        
       1162         Thursday, September 13
       4:00 PM 
       213A         Friday, September 14
       9:30 AMf
       210A         Intermediate*      Tips for Setting Up SANs for OpenVMST+       Wes Roberts    Compaq Global Services   F       This session discusses SANs from a VMS perspective. Many OpenVMSL customers are adding new systems with SANs and/or migrating existing storageL to a fibre channel configuration. This session provides "how to" informationL particular to setting up a SAN for OpenVMS Alpha systems, including: A briefK SAN design for high availability overview, using WWIDMGR so the console canrK access disks; identifiers, connection types and setup issues; setting pathsoE for load balancing; connecting to HSG80s from VMS; setup tips to make  troubleshooting easier.n        
       1165         Tuesday, September 11i
       1:00 PMs
       201D         Wednesday, September 12a
       2:45 PMt       Hilton - Oceanside         Introductory,      Building Secure Applications on OpenVMS<       Robert Gezelter    Robert Gezelter Software Consultant  I       Today, all applications require a degree of security to ensure thatwL data is entered, modified, and viewed by authorized individuals. OpenVMS hasB extensive facilities for controlling access to and modification ofG information and restricting access to programs. This session introducesiF attendees to the OpenVMS facilities that can be leveraged to provide aE consistent, secure computing environment without the need for specialnK user-written security code. Additionally, since these security features are L part of the base functionality provided by OpenVMS, they are more creditableF when applications are audited. These built-in functions also provide aI higher degree of assurance than custom code. The techniques described arerK applicable to all applications, whether the language used is DCL, or one ofyL the conventional programming languages used on OpenVMS (e.g. FORTRAN, COBOL,E C/C++). Examples are drawn from the speaker's consulting experiences.s        
       1178(      OpenVMST Enterprise Backup Strategy5       Andrew Schneider    Compaq Computer Corporationt  J       This session presents the updated OpenVMS backup strategy. You learnD about the OpenVMS backup utility and the automated backup solutions,L including Archive Backup System (ABS) and Storage Library System (SLS). ThisI session discusses OpenVMS support of Fibre Channel accessed tape devices,lD and OpenVMS inclusion in the Compaq Enterprise Backup Solution (EBS)	 packages.          Thursday, September 13
       9:30 AMn
       201D         Intermediate        
       11823      OpenVMST Storage Strategy and Technical Updatel2       Brian Allison    Compaq Computer Corporation  H       This session covers the technical strategy and feature updates forA support of storage in the OpenVMS operating system. This in-deptheE presentation covers all aspects of the enterprise-ready Fibre ChannelbI storage environment, including updated storage components and new low-end1H storage solutions under development. Additionally, it covers the currentA status of the other storage environments supported under OpenVMS,u specifically SCSI and CI.o         Wednesday, September 12n
       1:15 PMt
       201D         Intermediate        
       1183/      OpenVMS High Availability Technical Updater1       Verell Boaen    Compaq Computer Corporationv3       Gregory Jordan    Compaq Computer Corporationo  I       This session provides in-depth coverage of recent technical changeseF and those planned for the near future for OpenVMST in the area of HighI Availability computing. The specific technical areas covered include, buttJ are not limited to, Multipath Failover, Host-based Volume Shadowing, WriteA Bitmap/Minicopy, HSG80 Write History Logging, and PCI I/O Adapterr Hotswapping.         Wednesday, September 12 
       2:45 PMa
       201C         Thursday, September 13
       4:00 PMt
       201C         Intermediate        
       11846      OpenVMST Clustering Strategy and Technical Update1       Verell Boaen    Compaq Computer CorporationV3       Gregory Jordan    Compaq Computer Corporations  I       This session provides a technical update to the world-class OpenVMSlL Clustering product and addresses the strategy for this technology as OpenVMSK moves forward through the coming decade. Specific technical areas addressedsF include enhancements to the Lock Manager and support of LAN devices asA Cluster Interconnects (as shipped in V7.3) as well as areas undernA investigation, including the next-generation Cluster InterconnectiF technologies OpenVMS will support in the coming years. Enhancements to: disaster tolerant cluster environments are also discussed.         Tuesday, September 11r
       1:00 PMr
       201C         Intermediate        
       1202!      OpenVMS Clusters for Dummiesi6       Jennifer Johnson    Arrow/Wyle Computer Products  C       This BOF is "white board planning" for a VMS cluster, clusternL failover, hardware failure actions, rolling upgrade benefits, load balancingD conventions, etc. Prerequisites: OpenVMS knowledge, understanding of	 clusters.S         Tuesday, September 11 
       4:00 PM        Hilton - La Jolla          Intermediate        
       1204J      How to Solve Your Distributed Data Access Requirements Using Attunity Connectu        Rich Dill    Attunity Ltd.  E       Attunity Connect is an information infrastructure solution thateH provides built-in connectivity to data sources and applications across aL distributed environment that can encompass different platforms, networks andI the Internet. This session explains in detail how Attunity Connect can beoC used to transparently integrate heterogeneous applications and dataoJ sources - using industry-standard interfaces and protocols including JDBC,G ODBC and XML - and to create a single enterprise-wide virtual database.dI Attunity Connect has broad platform and database support which provides adL robust capability such that any application can access data on any platform.H This facilitates the rapid development of distributed applications whileL preserving the investment in existing data and applications. After attendingG this session, participants should gain an in-depth understanding of the J capabilities of Attunity Connect and how those capabilities can be appliedH to solve their particular data access and application integration needs.F Attunity Connect runs on many platforms including, but not limited to,9 Windows, OpenVMST VAX and AlphaT, Tru64T UNIX, and Linux.o         Friday, September 14
       8:00 AMc
       210B         Intermediate        
       1205         Friday, September 14
       8:00 AM0
       201B         Intermediate:      Turning OpenVMST Applications into EJBs and JavaBeans0       Phil Hudson    Compaq Computer Corporation  F       Enterprise Java Beans (EJB) is an object-based programming modelE designed to promote software interoperability. EJB allows two or moreeK applications (or components) to cooperate with one another easily - even if K the objects are written by different vendors at different times, or if theyaH are running on different machines with different operating systems. ThisK session focuses on how to take your OpenVMS applications and transform themwH into EJBs and/or JavaBeans using a product called Compaq BridgeWorks. ItL shows the steps needed to go from a stand alone, monolithic application to aI Java-based distributed application in minutes. In the process the sessionuC covers the features BridgeWorks provides the developer to make thisgJ transformation as easy and quick as possible. To demonstrate this point, aD live application "componentization" is included in the presentation.A Prerequisites: General familiarity with middleware, components orC object-oriented languages.        
       1206         Wednesday, September 12 
       8:00 AM        Hilton - Oceanside         Intermediate@      The Interactive Development Environment for OpenVMSTSystems.       John Apps    Compaq Computer Corporation  L       This session presents technical details about the NetBeans open-sourceI interactive development environment (IDE) software product and its use oneH OpenVMST systems. For Java developers, NetBeans has built-in support forL Swing, Java Beans, Remote Method Invocation (RMI), Java Naming and DirectoryJ Interface (JNDI), eXtensible Markup Language (XML), HTML and debugging. ItJ has code completion, word completion and abbreviations. You can also mountI sources from local disks, Concurrent Versioning System (CVS) repositories G and JavaDoc. It supports easy creation of Java Server Pages (JSP), too!wD Integrated support for the Jakarta Ant build system includes the ICEI browser. This session shows details of how to use many of these features. H Plus, we discuss on-going work with the NetBeans open-source project andJ some exciting features we are adding to make NetBeans THE IDE for all your% development needs on OpenVMS systems.n        
       1207         Friday, September 14
       8:00 AMe
       210A         IntermediateK      Case Studies: Using OpenVMST Middleware to Solve eBusiness Integration  Issues.       John Apps    Compaq Computer Corporation  J       When you get right down to it, creating and managing transactions isF the basis of all eBusiness. Middleware facilitates transactions acrossH diverse hardware and software platforms. This session focuses on OpenVMSI middleware technologies that support messaging, transactions and objects.iL Using case studies and examples, the speaker shows how OpenVMS customers useJ a range of middleware to address cross-platform transaction issues such as@ latency, scaling, transformation, portability and security usingD technologies such as message brokers, two-phase commit (2PC), objectF brokers, COM, Java, and XA-compliant architectures. This discussion isD especially useful for growing companies and enterprises that need toK integrate OpenVMS systems with other platforms such as Wintel, UNIX and IBMeF right now. The session also touches on emerging connection/integrationG technologies (such as application servers, integration servers, and ZLErI requirements) that affect the way middleware will be deployed and used inTF the near future. This information is of interest to anyone considering6 enterprise integration projects in the next two years.        
       1224         Wednesday, September 12s
       9:30 AMi
       304B         Intermediate/      Maximizing the Power of OpenVMS on a GS160 2       Peter Ranisch    Compaq Computer Corporation  K       This session explains how to improve the performance of the GS160 form; commercial applications, including the specific issues in amK NUMA-environment. The base is an application called Wallstreet. We'll coverxH the different bandwidths and latency issues for the GS160 subsystems andF fibre channel storage, and then see how it all fits together. But mostI advantage can be gained by using the supplied features of OpenVMS such asaK RMS global buffers, XFC, fast path, as well as how to make use of affinity,mJ the new LockManager features, and understanding what bottlenecks are stillE in place. We'll also cover the advantages of an EV68 vs. EV67 system.         
       1230         Wednesday, September 12e
       8:00 AMs
       303B         AdvancedF      Case Studies of Disaster Tolerant OpenVMS Cluster Implementations+       Robert Lyons    Resilient Systems Inc   J       This session discusses the issues and considerations of a multi-siteI disaster tolerant VMS cluster. It explores six real-world implementations I that were designed and installed, and provides guidance on how others canu' design their own optimal configuration.V        
       1245         Thursday, September 13       11:00 AM
       201B         Friday, September 14
       8:00 AMt
       304A         Advanced3      OpenVMST AlphaServerT GS80/160/320 Performanced3       Gregory Jordan    Compaq Computer Corporationd  J       This session covers considerations for improving OpenVMS performanceG on the GS80/160/320 AlphaServers. An overview of the GS AlphaServers isOB presented, Non-Uniform Memory Access (NUMA)is discussed, and otherC performance-enabling features in OpenVMS Version 7.3 and beyond are H described. Real examples are given along with the various steps taken toG improve performance of them. After attending this session, the attendeeiL should be able to articulate considerations for improving performance on theL GS80/160/320 AlphaServers, what NUMA is and how to plan for it, and featuresG in Version 7.3 and beyond that can be used to help improve performance.r        
       1246         Tuesday, September 11S
       4:00 PM        Hilton - San Clemente          AdvancedJ      How Best to Utilize The Extended File Cache (XFC) in OpenVMST Version 7.3.1       Mark Hopkins    Compaq Computer Corporationt  C       This session discusses how XFC can be utilized to improve I/ObJ performance. It begins with a general discussion on various places one canI buffer or cache I/O and then focuses on the features of XFC. Examples areiI shared of performance gains using real applications. After attending thisvK session, attendees should be able to describe the various places I/O can be0C buffered or cached, advantages of XFC over the cache in earlier VMS F releases, ways to monitor I/O performance and cache effectiveness, and( methods to control the cache parameters.        
       1247         Wednesday, September 12        11:00 AM       Hilton - San Clementeo         IntermediateG      Using Compaq Digital Continuous Profiling Infrastructure (DCPI) oni OpenVMST5       Anders Johansson    Compaq Computer Corporationn  K       Learn how DCPI can be used to examine application performance issues. E An overview of the tools, as well as how DCPI can be used to identifymB performance issues with applications running on OpenVMS, is given.        
       1250         Wednesday, September 12 
       1:15 PMe
       303B         AdvancedI      Advanced Topics in Compaq Enterprise Toolkit V2.0 - OpenVMST Editiont.       John Apps    Compaq Computer Corporation  H       This session covers advanced topics in using the Compaq EnterpriseI Toolkit V2.0 - OpenVMS Edition. Topics covered include: Using the ETK forsI multi-platform development (NT, VMS, and Tru64T UNIX); Project and remotetH project files and their relationships; Setting up project workspaces andH directories for various multi-level project configurations; Working withL large projects (many files in each project); Working with projects shared byH many developers; Working with files both in and out of CMS; Using CMS on non-remote projects.        
       1255         Wednesday, September 12 
       2:45 PMe
       303B         IntermediateA      Riding the Dot-Com Wave: A Case Study in Extreme VMS Clustere Scalability /       Keith Parris    Integrity Computing, Inc.   J       This session describes the experience of a site that had to at leastK double its capacity every year for four years in a row, and how VMS and VMS J Cluster technology was used to meet that need. Technical challenges duringF extreme workload growth, as well as solutions found along the way, areK described. The dot-com wave may be over, but extremely rapid scalability isSI still an issue in some industries, such as cellular billing, particularlyc	 overseas.l        
       1257         Tuesday, September 11r
       1:00 PMa
       208A         Thursday, September 13
       8:00 AMp
       208A         Intermediate!      Network Monitoring for LAVCs5/       Keith Parris    Integrity Computing, Inc.c  H       This workshop describes how to use the LAVC$FAILURE_ANALYSIS toolsE included with OpenVMST, which can generate appropriate OPCOM messagesoL whenever there is a failure or a repair of a piece of the redundant LAN usedJ to support a VMS Cluster configuraton. Examples of the setup details for aH real-world configuration, as well as the error messages generated during# some actual failures, are included.s        
       1407         Tuesday, September 11O
       8:00 AMs
       212A         Tuesday, September 11o       10:30 AM
       212A         Wednesday, September 12 
       1:00 PM 
       212A         Wednesday, September 12 
       3:30 PM 
       212A         Thursday, September 13
       8:00 AMn
       212A         Thursday, September 13       10:30 AM
       212A         IntermediateF      Configuring and Installing Fibre Channel (FC) Storage on OpenVMST4       David Fairbanks    Compaq Computer Corporation  B       Students attending this hands-on workshop gain experience inJ installing the RA8000 Fibre Channel (FC) storage system on OpenVMS. TopicsG covered include: Storage from the operating system perspective; StorageiG controller management; Fibre Channel switch basics; Drivers; Utilities;,# Booting from Fibre Channel devices.e        
       1445         Thursday, September 13       11:00 AM
       201C         Intermediate;      Disaster Tolerance/Business Continuity Technical Panel /       Paul Dolan    Compaq Computer Corporationp.       Dan Klein    Compaq Computer Corporation0       Ron LaPedis    Compaq Computer Corporation0       Mark Miller    Compaq Computer Corporation6       Thomas Sjolshagen    Compaq Computer Corporation5       Julio Valladares    Compaq Computer Corporationw1       Doug de Werd    Compaq Computer Corporatione  A       Every technology and platform has unique disaster tolerancesH attributes. They also demand different techniques, adjuncts and support.K Furthermore, they all have specific and compelling benefits drawbacks. ThiseJ panel in this session includes experts from each of the major technologiesI and services. They describe the pluses and minuses of each technology andiH answer attendee's questions. Prerequisites: A general disaster tolerance understanding.        
       1483         Thursday, September 13       11:00 AM
       304B         Introductory      Compaq Magic.0       David Cathey    Montagar Software Concepts  I       Bring your best stories and Computer Magic for a chance at fame andpF fabulous prizes. Our panel of esteemed judges will rate all stories onK techical content and entertainment value. The highest-rated stories will be8? declared the winners! Don't be shy and let's have a little fun.r        
       1559         Tuesday, September 11i
       9:15 AM        Hilton - San Clementeg         Intermediate7      Database Monitoring - Should I Write It or Buy IT?n(       Steve Lemme    Computer Associates  @       In the ever-changing business environment, Oracle databaseE administrators are responsible with the challenge of getting multiplenL databases installed and operational, on schedule with the added challenge ofK keeping them available to the enterprise. It is so easy for a DBA to become1J over occupied reacting to current problems, that eventually small problemsJ will get out of control. Although many databases start off small enough toE allow manual control, most databases grow so large that a solution isrJ necessary in order to avoid strapping a DBA to the console 24 hours a day.K Some organizations choose scripts for creating a managed environment withinoH the enterprise, while others see a value in off the shelf packages. ThisF presentation will explore the choices the DBA will need to consider in= choosing and implementing their database management strategy.a        
       1585         Tuesday, September 11 
       2:30 PM 
       304B         Wednesday, September 12i
       9:30 AMU
       210A         Introductory1      Security Standards - Ignore at Your Own Risko1       Roger French    Compaq Computer Corporationo  I       It's not just vendors that should be involved in security standardshE development. Industry, national, and international security standards K seriously affect your systems. They affect systems you connect to today andpB tomorrow. Users (companies, organizations, government agencies andC individuals), by definition, use the systems, and therefore use the L standards that others develop. This session presents a quick overview of theL types of SDOs (Standards Development Organizations), looks at who representsG whom in the SDOs, and considers the benefits and dangers of letting theaE "experts" decide. We look at the development of several internationaluK security standards (ISO 15408 based on the Common Criteria, ISO 17799 basedlJ on BS7799/Security Management Standard, ECMA/271 for business applicationsC security, the KRA and TACDFIPSFKMI defunct standards, TCPA PC Trust K standard, and the PKI Forum's developing PKI Interoperability Standard). WeoK discuss how such standards are developed, who participates and who decides.rE The session looks at a few instances where industry versus governmento! interests faced off, and who won.u        
       1586         Friday, September 14
       9:30 AMs
       201B         IntroductoryF      What You Don't Know About Public Key Infrastructure (PKI) Will Be	 Expensivee1       Roger French    Compaq Computer Corporationm  I       PKI is Public Key Infrastructure. Based on Public/Private key pairsFH where the Public Keys are published, it's possible to: 1) send encryptedE messages without exchanging secret keys; and 2) authenticate yourself,I without exchanging any secrets in advance. If PKI is that simple, why are H there not thousands of such systems today? Or one giant PKI? Because theL "PK" part is simple, but the "I" is very complex. More than the software andL hardware, infrastructure consists of policies (Security, Certificate, etc.),K Authorities (Certificate, registration, Validation), Keys (Public, Private,vK secret), Trust relationships, signatures, time stamps, hybrid systems, etc.uL This session presents an overview of a typical PKI system, what is involved,J why the various parts are necessary, and with what limitations. It definesI the common PKI terms. It examines requirements to implement a PKI system,nI including options. It addresses PKI Interoperability (the PKI Forum CA-CA-; Interoperability requirements, the U.S. Federal Bridge CA.)t        
       1589         Wednesday, September 12t
       2:45 PM 
       303A         Introductory4      Starting a Business Continuity Planning Program0       Ron LaPedis    Compaq Computer Corporation  C       There is a lot of buzz about disaster recovery and continuityaJ planning, but where do you start? This session compresses a 3 day tutorialE into a technical session. Attendees leave this session with the basicpL concepts, key activities, vocabulary, references and, of course, some horrorD stories! This session is given by a certified continuity planner and@ instructor. Prerequisite: Basic knowledge of business processes.        
       1591         Friday, September 14       11:00 AM
       201C         Intermediate0      Capacity Planning for Standard Applications/       Prem Sinha    Compaq Computer Corporation   H       As the Internet explosion accelerates, system and network solutionI providers need a tool to keep up with the performance and capacity issuesbL that arise as a part of their application deployment activity. Good responseJ time from a server makes the difference between success and failure of theD site. Monitoring performance and planning for sufficient capacity isG essential in meeting that goal. This session shows how Capacity PlannerdH products can be used to monitor performance and answer questions such asJ which server to select in order to provide required transaction throughputD or response time to a given number of clients. It simulates not onlyG different platforms (UNIX, OpenVMST and NT) but also different vendors'a= devices. The product includes a large database of performanceeH characteristics of applications such as MS-Exchange, MS-IIS, SQL Server,J SAP/R2, Print and File Servers, ALL-IN-1, SNA, POP3, etc. and multi-vendorJ device characteristics. You can create models of your own applications andK servers. Using this database one can quickly model complex applications (or A a mix of them), servers, and network components and analyze theiriJ performance impact (end-to-end response times, throughput rates and device utilizations).        
       1598         Tuesday, September 11r
       9:15 AM        Hilton - Capistranoh         IntroductoryC      Keeping Your Mission-Critical OpenVMST Systems in Prime Healtht,       Prabhakara Bhat    Computer Associates9       Dr. Johan van de Groenendaal    Computer Associatesw  K       OpenVMS systems form a critical component of eBusiness infrastructureeH in many organizations. They need to be managed in homogeneous as well asJ heterogeneous environments. CA's Unicenter, a family of modular integratedB eBusiness infrastructure management solutions, provides a suite ofC management products to monitor and manage the health, availability,PF performance, console, security, storage, and administration of OpenVMSI systems. This session covers the traditional Performance Advisor, ConsoletJ Manager, Scheduler and Watchdog, as well as the new generation of productsD for managing your OpenVMS systems in today's collaborative eBusiness environment.        
       1599         Wednesday, September 122
       4:15 PMd!       Hilton - Pacific Ballroom B          Thursday, September 13
       2:30 PMe       303CDV         Intermediate0      Creating an Enterprise Storage Architecture*       Philip Treide    Computer Associates  I       Learn about designing and configuring a storage environment that isfE aligned with your business objectives. Learn how to maximize existingdL technology on storage area networks and build cross platform data protectionL and recovery systems. Discover the strengths of Computer Associates' storage7 solutions, from data protection to resource management.e        
       1600         Monday, September 10
       2:15 PMu
       210B         Tuesday, September 11n
       9:15 AMn
       210A         Advanced6      Planning an Enterprise Disaster Recovery Strategy*       Philip Treide    Computer Associates  E       Reducing server down time and protecting data is crucial in the F eBusiness world. Building a Disaster Recovery Strategy goes way beyondK simple backup and restore. Find out how to build the entire DR strategy fornK your business, regardless of type or size with Computer Associates' Storagei3 solutions such as ARCserve, Cheetah, and Lifeguard.a        
       1601         Thursday, September 13
       8:00 AMn       Hilton - Capistrano          Intermediate@      High Performance Backup for Enterprise Storage with Cheetah*       Philip Treide    Computer Associates  J       Today's heterogeneous networked storage environments are raising theL bar for open systems data management. Learn how Cheetah, Computer AssociatesL ' new enterprise backup and recovery product for UNIX and Windows platforms,J delivers new levels of performance and scalability to the tasks of backup,J archiving and disaster recovery, with features that enhance manageability.        
       1606         Thursday, September 13
       8:00 AMn
       205A         Thursday, September 13
       1:00 PMt
       205A         Friday, September 14
       8:00 AMo
       205A         AdvancedI      Using Compaq's Digital Continuous Profiling Infrastructure (DCPI) on  OpenVMST5       Anders Johansson    Compaq Computer Corporationl3       Dennis Mattoon    Compaq Computer Corporation8  J       DCPI is a sampling-based profiling tool that is intended to help oneI understand system and application performance. It can be used to identifyeJ bottlenecks, cache thrashing, stall causes and other performance problems.L This workshop covers the installation and use of the tool on OpenVMS. DuringJ the workshop, attendees learn how to install and run DCPI to collect data.L They also run DCPI analysis tools using data captured on sample applicationsA and diagnose various software performance problems. Prerequisite: K Understanding of AlphaServersT, OpenVMS system operations, some performancee experience.         
       1616         Wednesday, September 12V
       1:15 PMT
       201B         IntroductoryH      What Your Mother Never Told You About Web Servers And Secure Socket Layer (SSL) Accelerators.       Bill Snow    Compaq Computer Corporation  J       Secure Sockets Layer (SSL) and TLS are becoming more popular all theL time. But implementing these protocols comes at a cost. SSL accelerators canH take some of the pain out of a secure implementation, but there are moreI things to know than maximum connections per second. This session exploresiI SSL implementation across different web servers, appliances and operating L systems, and provides numerical data comparing performance at many differentI system parameter values. This session reveals some surprising informationd= you won't get from any of the vendors' marketing departments.s        
       1617         Tuesday, September 11S       10:45 AM
       210A         Wednesday, September 12E
       4:15 PMc
       201C         Introductory=      Compaq MultiPrime(tm) Secures IPAQ Wireless Applicationsh3       Thomas Collins    Compaq Computer Corporationv  D       MultiPrime(tm) technology extends RSA public key technology toK low-power wireless devices by using more than two primes. It affords higherpK performance without increased power dissipation. There is a need for stronggL RSA security in wireless applications such as WAP security, personal bankingH and securities. Results of testing the Compaq IPAQ handheld PDA with RSAE cryptography will illustrate the benefits for MultiPrime for wirelessa devices.        
       1619         Wednesday, September 127
       4:15 PMs
       201D         Introductory,      Porting OpenVMS Applications to Itanium4       Gaitan D'Antoni    Compaq Computer Corporation  J       The port of OpenVMST to the Intel Itanium Processor Family (IPF) wasG announced in June, 2001. At this technical session, you learn about the F current OpenVMS IPF schedule, plans for compilers, binary translators,K performance analysis tools, and other preliminary information about porting,J your applications, your users, and your customers to Itanium-based OpenVMS systems.        
       1620         Thursday, September 13
       9:30 AM 
       210B         Friday, September 14       11:00 AM
       210C         IntermediateB      The Third Porting: Applying Past Lessons to the Alpha/Itanium
 Transition<       Robert Gezelter    Robert Gezelter Software Consultant  B       The transition from Alpha to Itanium will be the third majorG architecture assimilated by the OpenVMS and Tru64 communities since thesJ release of the original VAX-11/780 in 1978. Some aspects of each port haveK been painless, and others have proven to be challenges. The announcement of I the transition to Itanium has provoked much comment. However, much of thenK commentary has not addressed the detailed questions of what areas represent L significant problems, and what areas are likely to offer fewer problems thanL might otherwise be expected. This session will examine the technical aspectsI of the Itanium transition. Issues will be examined both in the context ofaF the Itanium transition, and in terms of how the details of the ItaniumB transition compare to previous transitions (VAX->MIPS; VAX->Alpha;F PDP-11->VAX; and MIPS->Alpha). There will be an emphasis on the issuesJ raised by the most recent experiences with porting to Alpha; while earlierF examples will be used to further illuminate the technical issues. ThisJ session will be suitable for technical and managerial IT professionals and users.        
       1624         Tuesday, September 110
       8:00 AMr
       208A         Wednesday, September 12A
       1:00 PMm
       208A         IntermediateK      Introduction to System Dump Analyzer (SDA) by Viewing OpenVMST Processs	 Internalse3       James Mehlhop    Process Software Corporationd!       Wayne Sauer    PARSEC Groupa  I       This workshop is for advanced OVMS users who need to understand theeL SDA and VMS processes at an internals level. First, the speakers cover basicF SDA commands and process internals. For the remainder of the workshop,I attendees use SDA to examine various aspects of the process internals and J scheduling. The workshop covers introduction to the SDA, process creation,E process data structures, process data structure relationships, kernel,G threads, locating process data structures, SYSGEN parameters related to1I process data structures, what is mapped in process virtual address space,A0 and analyzing process data structures using SDA.        
       1627         Friday, September 14
       8:00 AMa
       210D         Introductory0      CHARON-VAX - A Portable VAX System Emulator6       Robert Boers    Software Resources International  K       CHARON-VAX is an application program that completely emulates severalsJ models of VAX processors. The emulation is so complete that the CHARON-VAXL emulator will run OpenVMST VAX (most current versions) unmodified as well asI several other operating systems such as VAXeln and NETBSD. The CHARON-VAX F application itself runs on Linux, Windows NT, Windows 2000 and OpenVMSG AlphaT. When running the CHARON-VAX emulator on a modern ProLiantT, the E emulated VAX is actually faster than the original VAX processor. ThisiD presentation provides an overview of its development history and itsJ functionality. It describes how existing VAX applications can be preservedH unmodified while moving to a new platform and the unique opportunities aH hardware emulator provides to integrate binary VAX applications in a newK environment without requiring modifications or even source code. The optionrF of the VAX emulator to connect existing Qbus peripherals to a new hostJ system without rewriting drivers or application code is described, as wellK as the expected limits for this technology. This is a very useful tool thatnJ allows customers to run their existing VAX code on a new ProLiant or AlphaG (VMS) system. The presentation includes a demonstration of the product.n        
       1643         Wednesday, September 12e
       2:45 PM 
       304A         Friday, September 14       11:00 AM
       210D         IntermediateL      The Cool and Unhackable System - Building a Hack Proof Bunker for Floor of DEFCON9.fL       The DFWCUG has a special security whitepaper to present on hacking andK the technical underground. Learn how real professionals built a system thatbL DEFCON9 Hackers themselves dubbed "Unhackable" and "Cool". Learn how a groupJ of DFWCUG BOFH defeated the hellish maw of the hackers' best toolsmiths onG their own home turf. The whitepaper shares information learned from therL Hackers during the DEFCON9 Capture the Flag Game where all attacks are legalD and many were recorded. This sessions should not be missed by anyoneK interested in computer security and how to protect your servers from Hacker  attacks.        
       1644         Friday, September 14
       8:00 AMe       Hilton - San Clementee         Intermediate5      Making Your OpenVMST Environment HIPAA Compliante.       Dena Wright    Baylor Health Care System  D       Hospitals across the United States are mandated by the federalL government to become (Health Insurance Portability and Accountability Act ofJ 1996) HIPAA compliant. Come to this session to learn where HIPAA fits intoH heathcare provider's IT infrastructure today and where it's going in the future.e        
       1645         Thursday, September 13
       4:00 PM        Hilton - Oceanside         IntermediateK      Open Source Software on OpenVMST - Python, Perl, GNU, and a Whole Host5. of Open Source Animals on OpenVMS? Absolutely!2       JoAnn DiFrancesco    Sequel Data Systems Inc%       Steven Smiley    City of Dallasd  H       Come and learn what is available, where to get them, and hints andD tricks on how to build and install the Open Source Tools On OpenVMS!        
       1650         Thursday, September 13
       8:00 AMn       Hilton - San Clementec         Intermediate"      Upgrading OpenVMST 7.2 to 7.3)       Robert Drinjak    Efendi Associatesr       John Wisniewski    Compaqn  E       This session presents an OpenVMST 7.2 to 7.3 upgrade. While the J upgrade is being performed, hints, tips and traps are discussed as well as3 information from the Release Notes for OpenVMS 7.3.v        
       1656         Tuesday, September 11h       10:45 AM       Hilton - La Jollas         Intermediate"      PMDF on OpenVMS Working Group4       Hunter Goatley    Process Software Corporation  F       Attendees using PMDF on OpenVMS systems will discuss issues withK current version, share technical helps, discuss upcoming versions and theiryH features, and give feedback to the vendor on wants, needs and wish-list.        
       1658         Tuesday, September 11t
       2:30 PMi       Hilton - Lido As         Intermediate      MultiNet Working Group 4       Hunter Goatley    Process Software Corporation  F       Join vendor representatives to discuss MultiNet TCP/IP and shareI technical hints, features, and issues. Provide feedback to the vendor foro1 new features or wish-list items for this product.s        
       1659         Tuesday, September 11n
       4:00 PMm       Hilton - Lido A          Intermediate      TCPware Working Group4       Hunter Goatley    Process Software Corporation  E       Join vendor representatives to discuss TCPware TCP/IP features,eC issues, and share technical hints. This BOF session gives attendeeseG opportunity to provide feedback on the product and suggest features forc future releases.        
       1660         Thursday, September 13       11:00 AM       Hilton - La Jolla          Introductory:      Educational Initiative - CSLG, ESL, TEI Working Group       Kerry Smith    Compaqi  I       Meet with Compaq to discuss the latest features, pricing, products,tF and changes in the Campuswide Software Licensing Grant and EducationalG Software License programs for educational sites. If your site is on thea- CSLG/ESL program, this BOF session is a MUST!t        
       1661         Thursday, September 13
       9:30 AM        Hilton - Lido An         Intermediate.      Enterprise Directory & LDAP Working Group-       Jenny Butler    University of Tennessee   E       Discuss features and uses of an Enterprise Directory or LDAP intG production environments. This working group will provide opportunity toe? learn about Compaq's plans and products in an informal setting.t        
       1665         Wednesday, September 12d
       2:45 PMy       Hilton - Lido Ai         Intermediate      I Want my VMS!m(       Jean Norton    Sysnet Staffing Inc  F       Are you at risk of migrating away from OpenVMS? Have you alreadyD migrated away from OpenVMS? Let's get together and talk about tools,L emulators, and how to cope with withdrawal pains. By the way, it's OK to cry in this session.        
       1673         Monday, September 10       12:45 PM       303CD          Introductory4      You Can Bet Your Business on Compaq and Itanium2       Rich Marcello    Compaq Computer Corporation  L       This session addresses fundamental business issues related to Compaq'sI AlphaT to Itanium strategy. These issues include: Preserving your already J existing investment in your Tru64T UNIX or OpenVMST IT infrastructure; WhyG the investment you make today in new projects deployed on Tru64 UNIX orsJ OpenVMS, both in terms of hardware and application development costs, willH be preserved in the future; What Compaq is doing to insure the long termL viability of OpenVMS and Tru64 UNIX in the marketplace as technology leadingG enterprise class servers. These issues and others are covered, and thisoK session provides the answers to why Compaq's Alpha to Itanium strategy is a  safe bet for your business.I        
       1674         Monday, September 10
       3:45 PMo       303CD          IntroductoryK      Compaq Directions for Integrating Alpha Chip Technology with the IntelS) Itanium Processor Family: Executive Panel-2       Steve Langdon    Compaq Computer Corporation  J       Join us for this panel discussion with Compaq engineering executivesL as we discuss the plans for integrating Alpha chip technology into the IntelI Itanium Processor Family (IPF). We'll address your interests and concernsn$ about future server and OS roadmaps.        
       1684         Thursday, September 13
       4:00 PM,
       210B         Friday, September 14
       8:00 AMh
       303B         IntroductoryF      TruClusters, VMSclusters, Windows 2000 DataCenter Clusters, Linux, Clusters, and More: How Do They All Compare?/       Ken Moreau    Compaq Computer Corporation   G       This session analyzes the technologies behind Compaq's clusteringeI products, shows you where they are the same and where they are different, J and demonstrates why Compaq has the best clustering products on the market# on multiple operating environments.o        
       1690         Tuesday, September 11o       10:45 AM
       303B         IntroductoryK      Building a Protected Networked Enterprise- Security for Business: It's.6 No Longer a Technology Looking for a Problem to Solve!&       Dan Boneh    Stanford University         To be announced.        
       1691         Tuesday, September 11t
       1:00 PMc
       210B         IntroductoryE      New World Security Threats and Compaq's Strategy to Address Themd3       Michael Angelo    Compaq Computer Corporationy  I       This session provides insight into the evolving models for computertE usage and their associated threats. We also examine a number of usage L scenarios and evaluate the threats to each stage of the infrastructure. ThisG session also provides a technological overview of Compaq's strategy ande" directions for providing security.        
       1692         Thursday, September 13
       8:00 AMs
       210B         Introductory      Privacy, the New Challengei2       Dan Swartwood    Compaq Computer Corporation  F       With interconnected computers, databases, and near instantaneousH responses to requests for information, the collection, transmission, andH aggregation of personal information has become problematic for companiesH operating online. This session provides definitions, comparisons betweenI privacy and information security, and an overview of the current state ofvD affairs surrounding privacy from a legislative, standards-based, andJ consortia-based point of view. This session also covers the current issues surrounding privacy.        
       1693         Thursday, September 13
       4:00 PMd       Hilton - La Jolla          Introductory      OpenVMS Hobbyist Programi4       John Wisniewski    Compaq Computer Corporation  E       Come learn how you can obtain free OpenVMS license for Hobbyist L (Personal) use of OpenVMS. The OpenVMS Hobbyist License Program provides theL operating system license and over 150 layered product licenses for personal,I home use on your VAX or Alpha. Program license requirements and obtainingI2 your personal (used) Alpha will also be discussed.        
       1694         Thursday, September 13
       2:30 PMa
       201B         Intermediate9      Hot Topics in Real World Security: Interactive Panely3       Michael Angelo    Compaq Computer Corporationh2       John Carchide    Compaq Computer Corporation/       Bob Dennis    Compaq Computer Corporation 1       Roger French    Compaq Computer Corporation 0       Manny Novoa    Compaq Computer Corporation2       Sridhar Solur    Compaq Computer Corporation  J       This is an interactive session with the audience. What's Hot, What'sK Not, in the security world? What are the security drivers of tomorrowP Whats  will you need to know next year?        
       1695         Wednesday, September 12s
       8:00 AMs
       210A         Introductory?      Crypto 101 - Navigating DES, Public Key, Private Key, Etc.e/       Bob Dennis    Compaq Computer Corporationo  L       DES vs. SSL; symmetric vs. asymmetric keys; bulk encryption vs. secureH session setup; 128 bit or 1024 bit encryption - My customer (or boss) isF asking me questions I'm afraid to answer, for fear of saying the wrongF thing. This session is designed to clarify the technical geek speak of7 security and demystify the "black art" of cryptography.0        
       1696         Friday, September 14
       9:30 AMo
       303A         Advanced$      Implementing Analysis SolutionsI       Laura Chappell    The Protocol Analysis Institute; packet-level.coma  K       This session contains case studies of various security threats at thesD packet trace level seen 'in the wild'. Laura reviews common problemsH detected with a protocol analyzer and provides a list of proactive steps9 that you can take immediately upon return to your office.a        
       1703         Wednesday, September 12r       11:00 AM       Hilton - La Jollaa         Intermediate(      Domain Name System (DNS) Management(       Jeff Schreiber    Process Software  F       The Domain Name System (DNS) protocol, while being a very simpleH concept, can be an extremely challenging and confusing protocol to fullyA understand. Better understanding enables easier configuration and0L maintenance of your DNS. This session brings together experienced and noviceK DNS hostmasters to answer your DNS configuration and protocol questions andt to share experiences.x        
       1733         Tuesday, September 11e
       2:30 PMs       Hilton - Lido Bs         Introductory+      Encompass Local User Group Informationo$       Pamela Campbell    DataCeutics  J       Calling all Encompass Local User Group members and those who want toF join or form a new Local User Group (LUG)! This year's Advice Panel isH answering the questions and taking suggestions on how to start new LUGs,F reinvigorate existing LUGs, how LUGs should work with Encompass US and, Compaq, and what members want from the LUGs.        
       1882         Wednesday, September 12t
       8:00 AMo       Hilton - Lido B          Intermediate0      Computer Support of Air Force Organizations.       Laurie Knepper    Joint STARS Test Force  H       Discussion of topics relevant to computer technical support of AirL Force organizations. Actual topics will include such items as SATE, computerK issues, keeping up with NOTAM/TCNO suspenses, PKI, user training, technicalIH support resources, and training resources. Bring descriptions, contacts,K sources, and URLs for the resources you find most helpful in your technical0 support efforts.        
       1884         Tuesday, September 11i       10:45 AM
       303A6      OpenVMS Internals on the Itanium Processor Family0       Clair Grant    Compaq Computer Corporation  J       This session describes how some of the internals of OpenVMST will beG ported to the ItaniumT Processor Family (IPF). Mechanisms such as ASTs,1J IPLs, page protections, synchronization methods, and context switching areD presented in terms of the Intel fundamentals used to implement them.   ------------------------------  % Date: Tue, 28 Aug 2001 14:48:17 -0400d2 From: "Sue Skonetski" <susan.skonetski@compaq.com>! Subject: Re: VMS Sessions at CETSa2 Message-ID: <lHRi7.891$bB1.41577@news.cpqcorp.net>  K Please note that Mark Gorhams abstract is incorrect and his session will beI) focusing on the Alpha Intel announcement.b   Suet    = "Sue Skonetski" <susan.skonetski@compaq.com> wrote in messagea, news:y6Ri7.890$bB1.41649@news.cpqcorp.net... > Dear Newsgroup,A >MJ > I have made a request to Encompass for ALL sessions at CETS that mention VMS A > which they have kindly sent,  enclosed is what I have received.; Consideringr= > that there are always changes please do check update.daily.u > L > Please note that Mark Gorhams session is at the Hilton.  The VMS receptionH > is Tuesday night at 8 and you need an invitation, which you can get atC > Mark's session, the campground and the VMS demo in the tradeshow.  >  > Sue  >  >n >       1007 >I >       Monday, September 10 >       1:00 PMe >       208A >c >       Thursday, September 13 >       1:00 PMS >       208A >o >       Advanced8 >      Tru64T TruCluster for the VMScluster Professional6 >       Rochelle Lauer    Yale University Physics Dept >sF >       This hands-on workshop is designed to provide Tru64 TruClusterJ > technical information to attendees that have VMScluster experience. ThisJ > session provides hands on experience with a Tru64 TruCluster. TruClusterK > details are presented using a VMScluster perspective and assumes in-depthc > VMScluster knowledge.t >  >a >n >p >       1008 >d >       Monday, September 10 >       2:15 PMa >       210A >1 >       IntermediateJ >      Global Mailing Lists - A Case Study of a Web-enabled Administration > ToolD >       J Lance Wilkinson    Penn State University Library Computing Services >AB >       Historically, global mailing list management at Penn State
 UniversityF > Libraries used manually edited distribution list files and hard copyJ > authorization forms to define system-wide aliases under PMDF. User-levelG > membership management and automatic subscribe/unsubscribe facilities,m usingw3 > PMDF MAILSERV or the like, were not incorporated.e >sG >       A web-enabled facility was implemented running under the COMPAQC SecureH > Web Server (based upon Apache 1.3.6) on OpenVMS. Used for mailing listD > creation, deletion and membership management, it allows authorizedJ > University Library staffers to manage membership in the mailing lists toH > which they were granted control. This offloads almost all mailing listL > management to designated University Libraries staff and implements all the > validation checks required.a >rJ >       This session presents the design of the web-enabled Global MailingC > List facility as currently implemented at Penn State's Universitya	 LibrarieseF > and examines a few of the implementation considerations encountered. >r >e >s >  >       1042 >m >       Wednesday, September 12l >       9:30 AMe >       Hilton - Oceanside >e >       IntermediateF >      OpenVMST DII COE Initiative: Tools, Experiences and Benefits of PortingV > from UNIX to OpenVMS2 >       Joshua Cope    Compaq Computer Corporation >eG >       This session describes how to use and take advantage of the neweE > features in OpenVMST AlphaT V7.2-6C1 operating system from a system H > management and applications development perspective. These include new fileJ > system, C runtime library, TCP/IP and security features. We also discussJ > layered products and utilities packaged with 7.2-6C1 and how Compaq usedF > them to port the COE (Common Operating Environment) Kernel from UNIXG > (Solaris) to OpenVMS. OpenVMS V7.2-6C1 will be the first Compaq firstWG > operating system to certify against V4.2 of the COE Kernel. Attendeesi learnoJ > what the DII (Defense Information Infrastructure) COE Kernel is and what itJ > looks like. Learn about availability and usage of tools used for portingH > original UNIX software to OpenVMS and how to ensure compatibility with UNIX > environments.p >e >y >  >v >       1046 >  >       Thursday, September 13 >       9:30 AMt >       Hilton - Capistrano  >i >       Intermediate4 >      PATHWORKS and Advanced Server Troubleshooting6 >       Michael Stewart    Compaq Computer Corporation >CD >       This session covers the methods that Compaq customer supportF > specialists use to troubleshoot the Advanced Server for OpenVMST andD > PATHWORKS. It also includes hints and tips for using supported andG > unsupported utilities for troubleshooting. We also cover recent knownd issues1 > and limitations and their fixes or workarounds.  >  >r >y >e >       1047 >  >       Wednesday, September 12e >       2:45 PMd >       201B >o >       IntermediateK >      Using OpenVMST Performance Management Applications to Improve System?
 > Performance 6 >       Barry Kierstein    Compaq Computer Corporation4 >       Bart Lederman    Compaq Computer Corporation >wB >       MONITOR, DEcamds and Availability Manager provide powerfulJ > capabilities for performance troubleshooting, capacity planning and loadK > balancing of OpenVMS AlphaT and VAX platforms. Availability Manager shows J > information important to managing Galaxy nodes on GS series machines forC > OpenVMS V7.3. This is one of the first opportunities for users tos
 understandE > performance issues specific to the OpenVMS GS series machines. Thiso sessiontJ > demonstrates what data the utilities can collect and how the data can beI > analyzed. It also demonstrates how the utilities differ in the way they I > operate and how they address different areas of performance management.OG > After this session, you should understand how to best utilize OpenVMSn systemH > management capabilities to enhance overall system performance. A basicE > understanding of OpenVMS system management, DCL commands, accounts, ' > privileges, quotas, etc. is required.  >w >s >e >  >       1050 >  >       Wednesday, September 12, >       1:15 PM  >       Hilton - CapistranoL >  >       Wednesday, September 12l >       4:15 PMu >       213A >G >       Intermediate, >      OpenVMST TCP/IP V5.1 Technical Update6 >       Yanick Pouffary    Compaq Computer Corporation >tE >       This session shows you how to get the most out of your TCP/IPr OpenVMSTD > applications including NFS, BIND and IP v6. We explain how to take	 advantagenF > of the anti-spam and cluster failover (Bind and Load Broker) productB > capabilities. Learn how these enhanced applications make networkK > administration/management easier and more secure, and improve applicatione > performance. >  >h >a >i >       1051 >s >       Wednesday, September 12  >       1:15 PMc >       304A >a >       Wednesday, September 12r >       2:45 PM  >       Hilton - San Clementee >m >       IntermediateK >      Maximize the Performance of your TCP/IP Stack on OpenVMS: Tuning NFS 3 > and Troubleshooting TCP/IP to Improve PerformanceC5 >       Mark Hollinger    Compaq Computer Corporationf >uE >       This session discusses tuning and troubleshooting your TCP/IPi network.B > Every network administrator is concerned with optimizing network performanceoH > and having minimal disruption to their network services. These factorsL > directly impact a company's productivity and network costs, not to mentionK > the reputation of the network manager. This session describes the tunable D > parts of the TCP/IP network and provides strategies for correcting	 problems.pG > We also cover the tuning features of the TCP/IP Services for OpenVMSTiJ > products and how to troubleshoot problems with each component, including6 > FTP, SMTP mail, DNS/BIND, the kernel, and many more. >p >b >1 >  >       1054 >  >       Thursday, September 13 >       2:30 PMI >       201A >  >       Intermediate! >      OpenVMST Engineering Panelt6 >       Susan Skonetski    Compaq Computer Corporation >rL >       This panel session provides an informational, highly interactive andF > fun forum in which the audience discusses specific problems and asks@ > technical questions of OpenVMS engineers and product managers. ParticipantsG > are encouraged to share their creative problem-solving techniques andq1 > recommendations for future releases of OpenVMS.r >r >a >n >  >       1058 >n >       Wednesday, September 12s >       8:00 AMo >       205A >  >       Wednesday, September 12c >       1:00 PMy >       205A >s >       Intermediate6 >      Oracle9i Real Application Cluster Configuration) >       James Olsen    Oracle Corporationl >dK >       This session is intended to give attendees hands-on experience withpH > configuring Oracle Real Application Clusters (formerly Oracle ParallelH > Server). Participants have the opportunity to install Real ApplicationD > Clusters as well as learn how to configure the cluster for On-lineJ > Transaction Processing (OLTP) and DSS applications. Features of Oracle9i. > Real Application Cluster are also discussed. >e >I >  >  >       1067 >  >       Thursday, September 13 >       8:00 AM0 >       304B >r >       IntermediateE >      Implementing Successful eBusiness Projects with Oracle Rdb foru OpenVMST. >       Norman Lastovica    Oracle Corporation >CJ >       This presentation offers a clear strategy, tips, and options for aE > successful eBusiness implementation with Oracle Rdb as the back-endlL > database. In addition, it discusses new functionalities both on the latestC > Rdb database version 7.0.7 (which includes support for Alpha EV68.G > processors) and the planned version 7.1.0 (which includes full Galaxy  Phase K > III support and extensive SQL enhancements), as well as its commitment toyE > making the Rdb database available on Itanium. Come and hear how thexJ > combination of Oracle Rdb, OpenVMS, and AlphaT servers are put to use inL > some of the world's most "mission-critical" applications in companies like > your own.r >e >r >c >  >       1073 >h >       Monday, September 10 >       2:15 PM # >       Hilton - Pacific Ballroom Be >c >       Introductory9 >      Building Your Business' Future with Compaq OpenVMS 2 >       Mark Gorham    Compaq Computer Corporation >ML >       As businesses seek to understand the implications of moving to a newI > e-business model, they realize the importance of working in partnershipo withF > a vendor who has experience providing solutions for the world's mostD > demanding IT environments. With over 20 years of experience as the trusted,H > enabling solution for these environments, Compaq OpenVMST provides theH > baselineplus e-business infrastructure foundation to address:  How toF > handle the complexity associated with moving to e-business?  How to ensureF > my systems can handle the unforeseen capacity and management scalingH > requirements to come?  How to protect against data loss and maliciousH > attacks?  How to ensure best of breed responsiveness to my employees,K > partners and customers? The OpenVMS e-business strategy is to continue toyL > build leadership business-critical internet infrastructure solutions that,E > in concert with its strategic partners, enable businesses to make an smootherK > transition to this new business model. During the session, the next stageo ofJ > OpenVMS' e-business rollout is shared, coupled with customer experiencesI > with the a focus on:  OpenVMS e-business strategy  OpenVMS e-businesshB > architecture  Growing forward with OpenVMS e-business  OpenVMS
 e-business- > solutions at work  Putting it all togetherv >f >r >u >u >       1079 >m >       Thursday, September 13 >       9:30 AMa >       Hilton - La Jollas >  >       IntroductoryF >      OpenVMS System Resource Monitoring - Migrating DECamds Users to > Availability Manager6 >       Barry Kierstein    Compaq Computer Corporation >eH >       Join us for an interactive discussion on Compaq's OpenVMS systemF > resource monitoring applications - DECamds and Availability Manager.L > Discussion includes the merits of both applications and their similaritiesH > and differences. Provide input to future product requirements. SummaryG > results will help define future product features as well as to define  priorn > version retirement plans.a >l >l >b >i >       1082 >  >       Wednesday, September 12t >       1:15 PM: >       Hilton - Lido A  >n >       Introductory2 >      The Experience of Running Oracle on OpenVMS, >       Denay Williams    Oracle Corporation >hK >       Customers who currently run either Oracle7, Oracle 8i or Oracle RdbpI > meet to share their experiences - both good and bad - with other users. K > Representatives from Oracle 8i/9i development, Oracle Rdb development andmD > Compaq's Oracle Relationship Team will listen to your comments andF > suggestions, respond to them and take them back to Oracle and CompaqK > management to be addressed. Customers benefit from hearing other people's 0 > experiences and will exchange tips and advice. >  >: >A >  >       1083 >  >       Wednesday, September 12  >       9:30 AMu >       201B >  >       Thursday, September 13 >       11:00 AM >       304A >  >       Intermediate" >      Oracle9i for OpenVMS Update, >       Denay Williams    Oracle Corporation >tI >       Oracle is about to release version 9.0.1 of their database servern for J > OpenVMST AlphaT systems. This session describes the new features in thatL > release. It also covers how Oracle's automated porting effort enables themK > to release their OpenVMS version less than 90 days after the base release  isJ > complete. The status of version 8.1.6 and 8.1.7 is discussed. Support ofF > Oracle Parallel Server (OPS) is included. This session discusses howH > Oracle's vision of an e-business platform includes an OpenVMS / OracleA > back-end database server that is connected to other middle-tiert applicationt > servers and front-end tiers. >f >o >i >s >       1092 >n >       Wednesday, September 12y >       8:00 AM  >       Hilton - Lido Ae >s >       Intermediate> >      VAX VMS to ALPHA/ OVMS Migration - Issues and Solutions% >       Tanmay Sahoo    Digital India  > B >       This session describes the issues involved in migrating an applicationoH > running on VAX / VMS to Alpha / Open VMS and the solutions identified.J > Specifically the issues covered are:  OS specific changes related to 64 bitfK > addressing , data alignment, system services, upward compatibility of VMSnL > version used, kernel level code execution (privileged code constructs) andH > handling global sections arising from the 512 byte page size vis--visD > variable page size  Compiler specific changes related to compiler version,E > implementations (32 bit simulated to run in 64 bit or native 64 bitDE > implementation) and compiler options  Middle ware specific changest relatedwE > to availability of the layered products in Alpha and usage of CDD aH > Execution specific changes related to linker differences, performance, codeE > optimization, executables migration,  Issues involved in migratingdG > including user-written system services and other privileged shareable I > images, device drivers and performance monitors not supplied by Compaq,  codeK > that uses special privileges and code that uses internal OpenVMS routinesr or > data >  >t >r >  >       1101 >n >       Wednesday, September 12e >       11:00 AM >       304A >i >       Thursday, September 13 >       8:00 AM  >       210A >s >       Advanced1 >      Server Consolidation - Planning and Designi1 >       Kerry Main    Compaq Computer Corporationi >dJ >       Server Consolidation projects are on the minds of many CIOs and ITG > Directors. These projects allow companies to simultaneously reduce ITu costs,I > increase the level of service they offer and create additional businessnK > flexibility. Attendees of this session have the opportunity to learn what H > needs to be considered in the planning, design and implementation of aI > Server Consolidation project. The approach discussed is based on actualsH > Server Consolidation project experience across different OS platforms.J > Sample topics addressed include:  Business considerations - what issuesH > must be considered in the consolidation effort to achieve a successfulL > solution that is appropriate for the organization  Data integration - theG > importance of understanding how application data flow integrates witht otheroK > applications  SAN integration - more details on planning the SAN for thenJ > consolidated server environment and multi-site considerations  WorkloadL > Management vs. Partioning discussion  Migration processes and procedures,H > e.g. the importance of change management  Pre-migration testing - theL > importance of both functional and load testing for such things as databaseI > exports / imports, network copy times and user account / data migrationa > strategies >  >a >n >  >       1102 >  >       Wednesday, September 12S >       9:30 AMT >       Hilton - Lido A  >d >       Intermediate0 >      Server Consolidation - Birds of a Feather1 >       Kerry Main    Compaq Computer Corporation  > J >       Compaq consultants with Server Consolidation experience will be onA > hand to talk with you about your Server Consolidation projects.0 >  >  >  >  >       1113 >T >       Wednesday, September 12e >       9:30 AM  >       Hilton - CapistranoU >e >       Introductory* >      OpenVMST and Linux Interoperability6 >       John Wisniewski    Compaq Computer Corporation >tI >       What can OpenVMS and Linux do together? Learn about two operatingxK > systems that work and play well together and have more in common than you I > might think! Xwindows, Mail, WEBservices, Job Control, and File Sharing  aren@ > examined as well as how to integrate these two great operating environmentsI > for maximum interoperability. Please note: No NT systems will be harmedo > during this session. >i >  >o >  >       1116 >i >       Thursday, September 13 >       1:00 PMg >       Hilton - La Jollat >c >       Intermediate: >      PATHWORKS and Advanced Server for OpenVMS Q&A Panel4 >       Brad McCusker    Compaq Computer Corporation6 >       Michael Stewart    Compaq Computer Corporation >MG >       This is a Q&A panel comprised of members of engineering and thebD > Customer Support Center. All questions related to PATHWORKS and/or AdvancedH > Server for OpenVMS are welcome. Stump the panel and maybe win a prize! Bringe; > your tough questions and save yourself a call to the CSC!  >l >  >t >  >       1120 >n >       Wednesday, September 12l >       4:15 PM  >       Hilton - Oceanside >m >       Introductory# >      OpenVMST EDU License Program 6 >       John Wisniewski    Compaq Computer Corporation >aK >       The OpenVMS EDU License program began in November 2000 and has beenaL > very successful in providing schools, colleges and universtities with FREEJ > OpenVMS licenses for academic, research and student use. Come hear aboutL > this Free License program, the Continuing CSLG program and how you can use> > these Compaq Software and Services programs for your school. >  >  >n >a >       1122 >  >       Wednesday, September 12- >       8:00 AM  >       Hilton - San ClementeV >  >       Intermediate5 >      PATHWORKS and Advanced Server Technical Update 4 >       Brad McCusker    Compaq Computer Corporation >aD >       This session provides an update on the current status of the	 PATHWORKSeD > and Advanced server products and the plans for future versions andG > deliverables, including Windows 2000 integration. The session gives anL > technical overview of new functionality, including Member server, extendedI > character sets, load balancing, NT-style printing and more. We focus onaL > configuring, implementing and using the new functionality. Also covered isL > the extensive work underway to improve performance, performance monitoringI > and tuning, reliability and scalability. This session is a must for allrK > current PATHWORKS and Advanced server customers as well as anyone wishingt to9 > integrate OpenVMST with Windows NT and/or Windows 2000.  >d >r >r >g >       1123 >  >       Wednesday, September 12s >       11:00 AM >       Hilton - Capistrano  >  >       IntroductoryK >      Integrating OpenVMST PathWorks with Windows NT/Windows 2000 File andp > Print Servers 4 >       Brad McCusker    Compaq Computer Corporation >oL >       This session introduces the options for OpenVMS-based file and printI > servers and integration of those servers in a Windows NT and/or Windowsi 2000I > domain. PathWorks for OpenVMS V6 and Advanced Server for OpenVMS V7 areoE > discussed, including a functional overview of the products, WindowseK > NT/Windows 2000 domain integration, networking considerations, OpenVMS/NT L > single sign-on, management, and a comparison of the PathWorks and AdvancedD > Server for OpenVMS products. Discussion of utilizing OpenVMS as an: > enterprise-wide file and print server is also discussed. >a >n >o >p >       1130 >e >       Friday, September 14 >       9:30 AMo >       Hilton - San Clementet >d >       Advanced: >      Advanced C Programming on OpenVMST Operating System6 >       Stephen Hoffman    Compaq Computer Corporation >nK >       This session covers topics of interest to experienced C programmers L > new to programming on OpenVMST systems, specifically covering introductoryJ > and intermediate level OpenVMS programming topics for C programmers withL > experience on other platforms. We also cover advanced OpenVMS integration,C > development and portability topics for C programmers with OpenVMSsE > programming experience. The presentation covers low-level technicaldJ > bits-n-bytes including shared memory interlocking and the correct use ofE > AlphaT system memory barrier primitives. Prerequisites: Must have ae detailed7 > understanding of C and C programming on some platform  >t >  >a >e >       1131 >  >       Tuesday, September 11r >       9:15 AM # >       Hilton - Pacific Ballroom Be >t >       Tuesday, September 11r >       2:30 PM  >       304A >  >       Intermediate >      OpenVMS Technical UpdateS6 >       Stephen Hoffman    Compaq Computer Corporation >LK >       This session includes technical highlights of the OpenVMST V7.3 and J > OpenVMS AlphaT V7.2-2 operating system releases, as well as a preview ofJ > upcoming OpenVMS releases and an introduction to the OpenVMS port to theF > Intel ItaniumT Processor Family (IPF). Topics include an overview of OpenVMSNK > on Itanium, the new Extended File Cache, cluster features, SMP and systemdK > performance improvements, RAS features and plans, shadowing enhancements,hA > new products licensed with OpenVMS, and many other features and  enhancements' > available in and planned for OpenVMS.f >a >. >  >h >       1132 >  >       Thursday, September 13 >       1:00 PM  >       Hilton - Capistrano  >  >       Advanced >      OpenVMST Hints and Kinks 6 >       Stephen Hoffman    Compaq Computer Corporation > D >       This technical session provides an insider's guide on taking	 advantageuJ > of OpenVMS strengths, covering the following topics: Optomizing programs foruB > effective failover; Failover locking; Handling security features
 correctly;K > Designing shareable images; User-written System Services; Message utilityiE > and command definition utility; OpenVMS Galaxy and OpenVMS Cluster;t InsightsC > into C++ and the OpenVMS Debugger. Details on certain useful (andt+ > undocumented) features are also included.o >h >e >r >a >       1133 >o >       Wednesday, September 12  >       4:15 PMw >       Hilton - La Jolla  >  >       Intermediate >      Denizens of comp.os.vms6 >       Stephen Hoffman    Compaq Computer Corporation >hJ >       This BOF is a discussion among the participants of the comp.os.vms > newsgroup. >e >l >n >a >       1152 >  >       Tuesday, September 11  >       4:00 PMm >       303B >: >       Wednesday, September 12  >       11:00 AM >       Hilton - Oceanside >  >       AdvancedC >      OpenVMST AlphaT and VAX - Coexistence, Migration and Upgradep6 >       Stephen Hoffman    Compaq Computer Corporation >uJ >       The upgrade of application source code from OpenVMS VAX to OpenVMSK > Alpha is typically a simple process. This session describes the technicalrB > and application programming considerations of coexistence and of
 successful( > upgrades of more complex applications. >  >  >  >  >       1156 >  >       Tuesday, September 11  >       1:00 PM  >       201A >  >       Intermediate9 >      Deploying the Apache Web Server (CSWS) on OpenVMSTa5 >       Powell Hazzard    Compaq Computer Corporationi > L >       The Apache Web Server is the world's most widely deployed Web (HTTP)I > server and is now available on OpenVMS using the name Compaq Secure WebpK > Server (CSWS) for OpenVMS AlphaT. CSWS is provided as part of the OpenVMSeF > e-business infrastructure technology suite and is fully supported by Compaq.iE > The session covers installation, configuration and usage of CSWS onp OpenVMSsL > Alpha. After attending this session, participants should understand how toB > deploy CSWS as a building block in their Internet and e-business application L > environment, thereby leveraging the open-source software development styleA > of Apache and the unparalleled level of testing and deployment.  >c >C >o >i >       1157 >h >       Thursday, September 13 >       1:00 PMd >       Hilton - Oceanside >u >       Friday, September 14 >       11:00 AM >       304B >e >       Intermediate/ >      Java and OpenVMST - Ready for Prime Timed5 >       Powell Hazzard    Compaq Computer Corporationp >EH >       The Java programming language is designed to allow deployment of JavaG > applications on any platform that implements the Java Virtual Machinem (JVM).D > This session explains and demonstrates how to deploy existing JavaL > applications on OpenVMS AlphaT and the secrets of implementing Java ServerI > Pages (JSP) using the Tomcat JSP implementation in conjunction with the D > Compaq Secure Web Server (based upon Apache). After attending this session,I > participants should be able to deploy Java applications on any platformr andoI > understand the considerations for deploying Java and JSP OpenVMS Alpha.k >r >  >C >a >       1158 >a >       Wednesday, September 12e >       4:15 PMt >       Hilton - San Clementen >  >       AdvancedE >      Using the New BEA Weblogic Application Server V6.0 on OpenVMSTd0 >       John Apps    Compaq Computer Corporation >lL >       This session introduces the systems professional with the concept ofG > using an Enterprise Java Bean application server as the foundation tor buildtH > an OpenVMS e-business enterprise. The focus is the integration of thisD > application server to take advantage of the latest component-basedL > applications development environment native on OpenVMS. Examples of how toH > instantiate this environment along with specific customer examples are > presented. >? >H >t >n >       1162 >d >       Thursday, September 13 >       4:00 PMc >       213A >n >       Friday, September 14 >       9:30 AMu >       210A >s >       Intermediate, >      Tips for Setting Up SANs for OpenVMST- >       Wes Roberts    Compaq Global Services  >mH >       This session discusses SANs from a VMS perspective. Many OpenVMSF > customers are adding new systems with SANs and/or migrating existing storageuB > to a fibre channel configuration. This session provides "how to" informationSH > particular to setting up a SAN for OpenVMS Alpha systems, including: A brief I > SAN design for high availability overview, using WWIDMGR so the console  can G > access disks; identifiers, connection types and setup issues; settingt paths G > for load balancing; connecting to HSG80s from VMS; setup tips to maken > troubleshooting easier.  >  >v >a >i >       1165 >  >       Tuesday, September 11p >       1:00 PM  >       201D >u >       Wednesday, September 12n >       2:45 PM  >       Hilton - Oceanside >p >       Introductory. >      Building Secure Applications on OpenVMS> >       Robert Gezelter    Robert Gezelter Software Consultant >rK >       Today, all applications require a degree of security to ensure thathJ > data is entered, modified, and viewed by authorized individuals. OpenVMS haseD > extensive facilities for controlling access to and modification ofI > information and restricting access to programs. This session introducescH > attendees to the OpenVMS facilities that can be leveraged to provide aG > consistent, secure computing environment without the need for specialhI > user-written security code. Additionally, since these security featureso areoC > part of the base functionality provided by OpenVMS, they are moree
 creditableH > when applications are audited. These built-in functions also provide aK > higher degree of assurance than custom code. The techniques described areOJ > applicable to all applications, whether the language used is DCL, or one ofG > the conventional programming languages used on OpenVMS (e.g. FORTRAN,  COBOL,G > C/C++). Examples are drawn from the speaker's consulting experiences.  >  >B >  >  >       1178* >      OpenVMST Enterprise Backup Strategy7 >       Andrew Schneider    Compaq Computer Corporation  >aL >       This session presents the updated OpenVMS backup strategy. You learnF > about the OpenVMS backup utility and the automated backup solutions,I > including Archive Backup System (ABS) and Storage Library System (SLS).  ThisK > session discusses OpenVMS support of Fibre Channel accessed tape devices,OF > and OpenVMS inclusion in the Compaq Enterprise Backup Solution (EBS) > packages.o >e >       Thursday, September 13 >       9:30 AM  >       201D >e >       Intermediate >h >s >i >d >       11825 >      OpenVMST Storage Strategy and Technical Update 4 >       Brian Allison    Compaq Computer Corporation >eJ >       This session covers the technical strategy and feature updates forC > support of storage in the OpenVMS operating system. This in-depth G > presentation covers all aspects of the enterprise-ready Fibre ChannelVK > storage environment, including updated storage components and new low-end J > storage solutions under development. Additionally, it covers the currentC > status of the other storage environments supported under OpenVMS,S > specifically SCSI and CI.. >  >       Wednesday, September 12r >       1:15 PMc >       201D >  >       Intermediate >d >  >g >n >       11831 >      OpenVMS High Availability Technical Update 3 >       Verell Boaen    Compaq Computer Corporationt5 >       Gregory Jordan    Compaq Computer Corporation  >eK >       This session provides in-depth coverage of recent technical changesdH > and those planned for the near future for OpenVMST in the area of HighK > Availability computing. The specific technical areas covered include, buteL > are not limited to, Multipath Failover, Host-based Volume Shadowing, WriteC > Bitmap/Minicopy, HSG80 Write History Logging, and PCI I/O Adapterf > Hotswapping. >c >       Wednesday, September 12b >       2:45 PMI >       201C >  >       Thursday, September 13 >       4:00 PMc >       201C >i >       Intermediate >s >e >e >i >       11848 >      OpenVMST Clustering Strategy and Technical Update3 >       Verell Boaen    Compaq Computer CorporationV5 >       Gregory Jordan    Compaq Computer Corporation  > K >       This session provides a technical update to the world-class OpenVMS F > Clustering product and addresses the strategy for this technology as OpenVMS C > moves forward through the coming decade. Specific technical areas 	 addresseduH > include enhancements to the Lock Manager and support of LAN devices asC > Cluster Interconnects (as shipped in V7.3) as well as areas underoC > investigation, including the next-generation Cluster InterconnecthH > technologies OpenVMS will support in the coming years. Enhancements to< > disaster tolerant cluster environments are also discussed. >d >       Tuesday, September 11d >       1:00 PMf >       201C >o >       Intermediate >r >h >s >s >       1202# >      OpenVMS Clusters for Dummiese8 >       Jennifer Johnson    Arrow/Wyle Computer Products > E >       This BOF is "white board planning" for a VMS cluster, clusteroD > failover, hardware failure actions, rolling upgrade benefits, load	 balancingaF > conventions, etc. Prerequisites: OpenVMS knowledge, understanding of > clusters.n >o >       Tuesday, September 11t >       4:00 PM  >       Hilton - La Jollaa >n >       Intermediate >n >h >A >o >       1204L >      How to Solve Your Distributed Data Access Requirements Using Attunity	 > Connectr" >       Rich Dill    Attunity Ltd. >sG >       Attunity Connect is an information infrastructure solution thatiJ > provides built-in connectivity to data sources and applications across aJ > distributed environment that can encompass different platforms, networks andtK > the Internet. This session explains in detail how Attunity Connect can beaE > used to transparently integrate heterogeneous applications and data L > sources - using industry-standard interfaces and protocols including JDBC,I > ODBC and XML - and to create a single enterprise-wide virtual database. K > Attunity Connect has broad platform and database support which provides arD > robust capability such that any application can access data on any	 platform.sJ > This facilitates the rapid development of distributed applications whileD > preserving the investment in existing data and applications. After	 attendingwI > this session, participants should gain an in-depth understanding of thedL > capabilities of Attunity Connect and how those capabilities can be appliedJ > to solve their particular data access and application integration needs.H > Attunity Connect runs on many platforms including, but not limited to,; > Windows, OpenVMST VAX and AlphaT, Tru64T UNIX, and Linux.i >  >       Friday, September 14 >       8:00 AMl >       210B >u >       Intermediate >  >o >  >  >       1205 >  >       Friday, September 14 >       8:00 AM  >       201B >L >       Intermediate< >      Turning OpenVMST Applications into EJBs and JavaBeans2 >       Phil Hudson    Compaq Computer Corporation >rH >       Enterprise Java Beans (EJB) is an object-based programming modelG > designed to promote software interoperability. EJB allows two or moreuJ > applications (or components) to cooperate with one another easily - even ifH > the objects are written by different vendors at different times, or if theyJ > are running on different machines with different operating systems. ThisH > session focuses on how to take your OpenVMS applications and transform themJ > into EJBs and/or JavaBeans using a product called Compaq BridgeWorks. ItL > shows the steps needed to go from a stand alone, monolithic application to anK > Java-based distributed application in minutes. In the process the sessionuE > covers the features BridgeWorks provides the developer to make this L > transformation as easy and quick as possible. To demonstrate this point, aF > live application "componentization" is included in the presentation.C > Prerequisites: General familiarity with middleware, components or  > object-oriented languages. >n >a >S >e >       1206 >  >       Wednesday, September 12e >       8:00 AM  >       Hilton - Oceanside >S >       IntermediateB >      The Interactive Development Environment for OpenVMSTSystems0 >       John Apps    Compaq Computer Corporation >eB >       This session presents technical details about the NetBeans open-sourcefK > interactive development environment (IDE) software product and its use onhJ > OpenVMST systems. For Java developers, NetBeans has built-in support forD > Swing, Java Beans, Remote Method Invocation (RMI), Java Naming and	 DirectoryeL > Interface (JNDI), eXtensible Markup Language (XML), HTML and debugging. ItL > has code completion, word completion and abbreviations. You can also mountK > sources from local disks, Concurrent Versioning System (CVS) repositoriesmI > and JavaDoc. It supports easy creation of Java Server Pages (JSP), too!aF > Integrated support for the Jakarta Ant build system includes the ICEK > browser. This session shows details of how to use many of these features. J > Plus, we discuss on-going work with the NetBeans open-source project andL > some exciting features we are adding to make NetBeans THE IDE for all your' > development needs on OpenVMS systems.m >  >p >r >r >       1207 >  >       Friday, September 14 >       8:00 AMn >       210A >d >       IntermediateA >      Case Studies: Using OpenVMST Middleware to Solve eBusiness  Integrationh > Issues0 >       John Apps    Compaq Computer Corporation > L >       When you get right down to it, creating and managing transactions isH > the basis of all eBusiness. Middleware facilitates transactions acrossJ > diverse hardware and software platforms. This session focuses on OpenVMSK > middleware technologies that support messaging, transactions and objects.iJ > Using case studies and examples, the speaker shows how OpenVMS customers useeL > a range of middleware to address cross-platform transaction issues such asB > latency, scaling, transformation, portability and security usingF > technologies such as message brokers, two-phase commit (2PC), objectH > brokers, COM, Java, and XA-compliant architectures. This discussion isF > especially useful for growing companies and enterprises that need toI > integrate OpenVMS systems with other platforms such as Wintel, UNIX andr IBMmH > right now. The session also touches on emerging connection/integrationI > technologies (such as application servers, integration servers, and ZLEpK > requirements) that affect the way middleware will be deployed and used indH > the near future. This information is of interest to anyone considering8 > enterprise integration projects in the next two years. >  >t >v >e >       1224 >e >       Wednesday, September 12o >       9:30 AM  >       304B >  >       Intermediate1 >      Maximizing the Power of OpenVMS on a GS160 4 >       Peter Ranisch    Compaq Computer Corporation >bI >       This session explains how to improve the performance of the GS160e forT= > commercial applications, including the specific issues in arG > NUMA-environment. The base is an application called Wallstreet. We'llp coverVJ > the different bandwidths and latency issues for the GS160 subsystems andH > fibre channel storage, and then see how it all fits together. But mostK > advantage can be gained by using the supplied features of OpenVMS such aseC > RMS global buffers, XFC, fast path, as well as how to make use ofa	 affinity,aL > the new LockManager features, and understanding what bottlenecks are stillG > in place. We'll also cover the advantages of an EV68 vs. EV67 system.  >  >n >c >n >       1230 >n >       Wednesday, September 12. >       8:00 AM  >       303B >  >       AdvancedH >      Case Studies of Disaster Tolerant OpenVMS Cluster Implementations- >       Robert Lyons    Resilient Systems Incp > L >       This session discusses the issues and considerations of a multi-siteK > disaster tolerant VMS cluster. It explores six real-world implementationsiK > that were designed and installed, and provides guidance on how others canl) > design their own optimal configuration.o >c >; >  >i >       1245 >m >       Thursday, September 13 >       11:00 AM >       201B >  >       Friday, September 14 >       8:00 AMC >       304A >s >       Advanced5 >      OpenVMST AlphaServerT GS80/160/320 Performance 5 >       Gregory Jordan    Compaq Computer Corporation  > L >       This session covers considerations for improving OpenVMS performanceI > on the GS80/160/320 AlphaServers. An overview of the GS AlphaServers issD > presented, Non-Uniform Memory Access (NUMA)is discussed, and otherE > performance-enabling features in OpenVMS Version 7.3 and beyond areeJ > described. Real examples are given along with the various steps taken toI > improve performance of them. After attending this session, the attendee J > should be able to articulate considerations for improving performance on thehE > GS80/160/320 AlphaServers, what NUMA is and how to plan for it, anda featuresI > in Version 7.3 and beyond that can be used to help improve performance.f >  >n >  >  >       1246 >h >       Tuesday, September 11. >       4:00 PMc >       Hilton - San Clementel >t >       AdvancedL >      How Best to Utilize The Extended File Cache (XFC) in OpenVMST Version > 7.3n3 >       Mark Hopkins    Compaq Computer Corporation, >pE >       This session discusses how XFC can be utilized to improve I/O L > performance. It begins with a general discussion on various places one canK > buffer or cache I/O and then focuses on the features of XFC. Examples arewK > shared of performance gains using real applications. After attending thisVJ > session, attendees should be able to describe the various places I/O can beE > buffered or cached, advantages of XFC over the cache in earlier VMSoH > releases, ways to monitor I/O performance and cache effectiveness, and* > methods to control the cache parameters. >n >s >  >h >       1247 >g >       Wednesday, September 12d >       11:00 AM >       Hilton - San Clementel >  >       IntermediateI >      Using Compaq Digital Continuous Profiling Infrastructure (DCPI) on 
 > OpenVMST7 >       Anders Johansson    Compaq Computer Corporation  >tE >       Learn how DCPI can be used to examine application performancey issues.eG > An overview of the tools, as well as how DCPI can be used to identifyeD > performance issues with applications running on OpenVMS, is given. >  >J >  >  >       1250 >f >       Wednesday, September 12z >       1:15 PMm >       303B >p >       AdvancedK >      Advanced Topics in Compaq Enterprise Toolkit V2.0 - OpenVMST Editiont0 >       John Apps    Compaq Computer Corporation > J >       This session covers advanced topics in using the Compaq EnterpriseK > Toolkit V2.0 - OpenVMS Edition. Topics covered include: Using the ETK forJK > multi-platform development (NT, VMS, and Tru64T UNIX); Project and remotewJ > project files and their relationships; Setting up project workspaces andJ > directories for various multi-level project configurations; Working withK > large projects (many files in each project); Working with projects sharedP byJ > many developers; Working with files both in and out of CMS; Using CMS on > non-remote projects. >  >  >t >- >       1255 >  >       Wednesday, September 12t >       2:45 PMi >       303B >v >       IntermediateC >      Riding the Dot-Com Wave: A Case Study in Extreme VMS Clusters
 > Scalability 1 >       Keith Parris    Integrity Computing, Inc.n >nL >       This session describes the experience of a site that had to at leastI > double its capacity every year for four years in a row, and how VMS andc VMS L > Cluster technology was used to meet that need. Technical challenges duringH > extreme workload growth, as well as solutions found along the way, areJ > described. The dot-com wave may be over, but extremely rapid scalability isK > still an issue in some industries, such as cellular billing, particularly  > overseas.  >  >  >d >  >       1257 >  >       Tuesday, September 11  >       1:00 PMa >       208A >o >       Thursday, September 13 >       8:00 AMt >       208A >l >       Intermediate# >      Network Monitoring for LAVCsV1 >       Keith Parris    Integrity Computing, Inc.g >wJ >       This workshop describes how to use the LAVC$FAILURE_ANALYSIS toolsG > included with OpenVMST, which can generate appropriate OPCOM messagesrI > whenever there is a failure or a repair of a piece of the redundant LAN  usedL > to support a VMS Cluster configuraton. Examples of the setup details for aJ > real-world configuration, as well as the error messages generated during% > some actual failures, are included.s >o >M >s >p >       1407 >  >       Tuesday, September 11v >       8:00 AM  >       212A >  >       Tuesday, September 11  >       10:30 AM >       212A >  >       Wednesday, September 12  >       1:00 PM  >       212A >e >       Wednesday, September 12  >       3:30 PMA >       212A >e >       Thursday, September 13 >       8:00 AMS >       212A >t >       Thursday, September 13 >       10:30 AM >       212A >t >       IntermediateH >      Configuring and Installing Fibre Channel (FC) Storage on OpenVMST6 >       David Fairbanks    Compaq Computer Corporation >fD >       Students attending this hands-on workshop gain experience inL > installing the RA8000 Fibre Channel (FC) storage system on OpenVMS. TopicsI > covered include: Storage from the operating system perspective; StorageoI > controller management; Fibre Channel switch basics; Drivers; Utilities;y% > Booting from Fibre Channel devices.n >o >i >p >i >       1445 >h >       Thursday, September 13 >       11:00 AM >       201C >i >       Intermediate= >      Disaster Tolerance/Business Continuity Technical Panelc1 >       Paul Dolan    Compaq Computer Corporationt0 >       Dan Klein    Compaq Computer Corporation2 >       Ron LaPedis    Compaq Computer Corporation2 >       Mark Miller    Compaq Computer Corporation8 >       Thomas Sjolshagen    Compaq Computer Corporation7 >       Julio Valladares    Compaq Computer Corporationu3 >       Doug de Werd    Compaq Computer Corporatione >oC >       Every technology and platform has unique disaster tolerancekJ > attributes. They also demand different techniques, adjuncts and support.H > Furthermore, they all have specific and compelling benefits drawbacks. ThisL > panel in this session includes experts from each of the major technologiesK > and services. They describe the pluses and minuses of each technology and J > answer attendee's questions. Prerequisites: A general disaster tolerance > understanding. >  >  >  >  >       1483 >  >       Thursday, September 13 >       11:00 AM >       304B >n >       Introductory >      Compaq Magica2 >       David Cathey    Montagar Software Concepts > K >       Bring your best stories and Computer Magic for a chance at fame andpH > fabulous prizes. Our panel of esteemed judges will rate all stories onJ > techical content and entertainment value. The highest-rated stories will beA > declared the winners! Don't be shy and let's have a little fun.e >m >. >d >o >       1559 >t >       Tuesday, September 11e >       9:15 AMm >       Hilton - San Clemente  >p >       Intermediate9 >      Database Monitoring - Should I Write It or Buy IT? * >       Steve Lemme    Computer Associates > B >       In the ever-changing business environment, Oracle databaseG > administrators are responsible with the challenge of getting multiplerK > databases installed and operational, on schedule with the added challengen ofF > keeping them available to the enterprise. It is so easy for a DBA to becomeL > over occupied reacting to current problems, that eventually small problemsL > will get out of control. Although many databases start off small enough toG > allow manual control, most databases grow so large that a solution isyL > necessary in order to avoid strapping a DBA to the console 24 hours a day.F > Some organizations choose scripts for creating a managed environment withinJ > the enterprise, while others see a value in off the shelf packages. ThisH > presentation will explore the choices the DBA will need to consider in? > choosing and implementing their database management strategy.d >  >o >q >m >       1585 >  >       Tuesday, September 11i >       2:30 PMp >       304B >- >       Wednesday, September 12u >       9:30 AMt >       210A >h >       Introductory3 >      Security Standards - Ignore at Your Own Riski3 >       Roger French    Compaq Computer Corporationn >tK >       It's not just vendors that should be involved in security standards G > development. Industry, national, and international security standardsnI > seriously affect your systems. They affect systems you connect to todayn andcD > tomorrow. Users (companies, organizations, government agencies andE > individuals), by definition, use the systems, and therefore use thePJ > standards that others develop. This session presents a quick overview of theOC > types of SDOs (Standards Development Organizations), looks at whoC
 representsI > whom in the SDOs, and considers the benefits and dangers of letting thesG > "experts" decide. We look at the development of several internationaldG > security standards (ISO 15408 based on the Common Criteria, ISO 17799s based L > on BS7799/Security Management Standard, ECMA/271 for business applicationsE > security, the KRA and TACDFIPSFKMI defunct standards, TCPA PC Trust J > standard, and the PKI Forum's developing PKI Interoperability Standard). WeD > discuss how such standards are developed, who participates and who decides.G > The session looks at a few instances where industry versus governmentn# > interests faced off, and who won.i >  >o >a >  >       1586 >o >       Friday, September 14 >       9:30 AMe >       201B >h >       IntroductoryH >      What You Don't Know About Public Key Infrastructure (PKI) Will Be > Expensivee3 >       Roger French    Compaq Computer Corporation  >uK >       PKI is Public Key Infrastructure. Based on Public/Private key pairstJ > where the Public Keys are published, it's possible to: 1) send encryptedG > messages without exchanging secret keys; and 2) authenticate yourselftK > without exchanging any secrets in advance. If PKI is that simple, why aretJ > there not thousands of such systems today? Or one giant PKI? Because theJ > "PK" part is simple, but the "I" is very complex. More than the software andnG > hardware, infrastructure consists of policies (Security, Certificate,i etc.),D > Authorities (Certificate, registration, Validation), Keys (Public, Private,H > secret), Trust relationships, signatures, time stamps, hybrid systems, etc.D > This session presents an overview of a typical PKI system, what is	 involved,TL > why the various parts are necessary, and with what limitations. It definesK > the common PKI terms. It examines requirements to implement a PKI system, K > including options. It addresses PKI Interoperability (the PKI Forum CA-CAm= > Interoperability requirements, the U.S. Federal Bridge CA.)B >s >  >  >h >       1589 >a >       Wednesday, September 12  >       2:45 PM  >       303A >  >       Introductory6 >      Starting a Business Continuity Planning Program2 >       Ron LaPedis    Compaq Computer Corporation >tE >       There is a lot of buzz about disaster recovery and continuityrL > planning, but where do you start? This session compresses a 3 day tutorialG > into a technical session. Attendees leave this session with the basiceG > concepts, key activities, vocabulary, references and, of course, someB horrorF > stories! This session is given by a certified continuity planner andB > instructor. Prerequisite: Basic knowledge of business processes. >a >b >d >s >       1591 >i >       Friday, September 14 >       11:00 AM >       201C >  >       Intermediate2 >      Capacity Planning for Standard Applications1 >       Prem Sinha    Compaq Computer Corporationa > J >       As the Internet explosion accelerates, system and network solutionK > providers need a tool to keep up with the performance and capacity issuesnE > that arise as a part of their application deployment activity. Goodp responseL > time from a server makes the difference between success and failure of theF > site. Monitoring performance and planning for sufficient capacity isI > essential in meeting that goal. This session shows how Capacity Planner J > products can be used to monitor performance and answer questions such asL > which server to select in order to provide required transaction throughputF > or response time to a given number of clients. It simulates not onlyI > different platforms (UNIX, OpenVMST and NT) but also different vendors'J? > devices. The product includes a large database of performance J > characteristics of applications such as MS-Exchange, MS-IIS, SQL Server,L > SAP/R2, Print and File Servers, ALL-IN-1, SNA, POP3, etc. and multi-vendorL > device characteristics. You can create models of your own applications andI > servers. Using this database one can quickly model complex applicationsw (orTC > a mix of them), servers, and network components and analyze theirlL > performance impact (end-to-end response times, throughput rates and device > utilizations). >  >  >i >t >       1598 >H >       Tuesday, September 11n >       9:15 AMS >       Hilton - Capistrano  >  >       IntroductoryE >      Keeping Your Mission-Critical OpenVMST Systems in Prime Healthd. >       Prabhakara Bhat    Computer Associates; >       Dr. Johan van de Groenendaal    Computer Associatesn >p> >       OpenVMS systems form a critical component of eBusiness infrastructureJ > in many organizations. They need to be managed in homogeneous as well asL > heterogeneous environments. CA's Unicenter, a family of modular integratedD > eBusiness infrastructure management solutions, provides a suite ofE > management products to monitor and manage the health, availability,eH > performance, console, security, storage, and administration of OpenVMSK > systems. This session covers the traditional Performance Advisor, ConsolenL > Manager, Scheduler and Watchdog, as well as the new generation of productsF > for managing your OpenVMS systems in today's collaborative eBusiness > environment. >  >s >s >s >       1599 >l >       Wednesday, September 12n >       4:15 PMt# >       Hilton - Pacific Ballroom B  >h >       Thursday, September 13 >       2:30 PM 
 >       303CDe >s >       Intermediate2 >      Creating an Enterprise Storage Architecture, >       Philip Treide    Computer Associates > K >       Learn about designing and configuring a storage environment that isdG > aligned with your business objectives. Learn how to maximize existingeC > technology on storage area networks and build cross platform datat
 protectionF > and recovery systems. Discover the strengths of Computer Associates' storage 9 > solutions, from data protection to resource management.e >S >  >S >  >       1600 >a >       Monday, September 10 >       2:15 PM  >       210B >p >       Tuesday, September 11m >       9:15 AMe >       210A >i >       Advanced8 >      Planning an Enterprise Disaster Recovery Strategy, >       Philip Treide    Computer Associates >pG >       Reducing server down time and protecting data is crucial in thesH > eBusiness world. Building a Disaster Recovery Strategy goes way beyondI > simple backup and restore. Find out how to build the entire DR strategyn foruE > your business, regardless of type or size with Computer Associates'e Storagei5 > solutions such as ARCserve, Cheetah, and Lifeguard.n >h >b >l >c >       1601 >n >       Thursday, September 13 >       8:00 AM8 >       Hilton - Capistranoc >n >       IntermediateB >      High Performance Backup for Enterprise Storage with Cheetah, >       Philip Treide    Computer Associates > L >       Today's heterogeneous networked storage environments are raising theC > bar for open systems data management. Learn how Cheetah, Computerr
 AssociatesC > ' new enterprise backup and recovery product for UNIX and Windowsl
 platforms,L > delivers new levels of performance and scalability to the tasks of backup,L > archiving and disaster recovery, with features that enhance manageability. >  >  >  >  >       1606 >e >       Thursday, September 13 >       8:00 AM  >       205A >  >       Thursday, September 13 >       1:00 PMd >       205A >e >       Friday, September 14 >       8:00 AM  >       205A >d >       AdvancedK >      Using Compaq's Digital Continuous Profiling Infrastructure (DCPI) ong
 > OpenVMST7 >       Anders Johansson    Compaq Computer Corporation 5 >       Dennis Mattoon    Compaq Computer Corporationm > L >       DCPI is a sampling-based profiling tool that is intended to help oneK > understand system and application performance. It can be used to identifytL > bottlenecks, cache thrashing, stall causes and other performance problems.G > This workshop covers the installation and use of the tool on OpenVMS.  DuringL > the workshop, attendees learn how to install and run DCPI to collect data.A > They also run DCPI analysis tools using data captured on samplen applicationsC > and diagnose various software performance problems. Prerequisite:uA > Understanding of AlphaServersT, OpenVMS system operations, somet performance 
 > experience.  >H >B >  >U >       1616 >e >       Wednesday, September 12r >       1:15 PM  >       201B >  >       IntroductoryJ >      What Your Mother Never Told You About Web Servers And Secure Socket > Layer (SSL) Accelerators0 >       Bill Snow    Compaq Computer Corporation >eL >       Secure Sockets Layer (SSL) and TLS are becoming more popular all theJ > time. But implementing these protocols comes at a cost. SSL accelerators canVJ > take some of the pain out of a secure implementation, but there are moreK > things to know than maximum connections per second. This session explores K > SSL implementation across different web servers, appliances and operatingeD > systems, and provides numerical data comparing performance at many	 different K > system parameter values. This session reveals some surprising information ? > you won't get from any of the vendors' marketing departments.o >i >I >a >u >       1617 >  >       Tuesday, September 11n >       10:45 AM >       210A >  >       Wednesday, September 12b >       4:15 PM  >       201C >r >       Introductory? >      Compaq MultiPrime(tm) Secures IPAQ Wireless Applicationsf5 >       Thomas Collins    Compaq Computer Corporationp >MF >       MultiPrime(tm) technology extends RSA public key technology toF > low-power wireless devices by using more than two primes. It affords higherF > performance without increased power dissipation. There is a need for strongF > RSA security in wireless applications such as WAP security, personal bankingnJ > and securities. Results of testing the Compaq IPAQ handheld PDA with RSAG > cryptography will illustrate the benefits for MultiPrime for wirelessd
 > devices. >P >e >a >r >       1619 >  >       Wednesday, September 12t >       4:15 PMo >       201D >i >       Introductory. >      Porting OpenVMS Applications to Itanium6 >       Gaitan D'Antoni    Compaq Computer Corporation >tL >       The port of OpenVMST to the Intel Itanium Processor Family (IPF) wasI > announced in June, 2001. At this technical session, you learn about the H > current OpenVMS IPF schedule, plans for compilers, binary translators,E > performance analysis tools, and other preliminary information aboutx porting L > your applications, your users, and your customers to Itanium-based OpenVMS
 > systems. >s >s >n >s >       1620 >e >       Thursday, September 13 >       9:30 AMc >       210B >r >       Friday, September 14 >       11:00 AM >       210C >o >       IntermediateD >      The Third Porting: Applying Past Lessons to the Alpha/Itanium > Transition> >       Robert Gezelter    Robert Gezelter Software Consultant >oD >       The transition from Alpha to Itanium will be the third majorI > architecture assimilated by the OpenVMS and Tru64 communities since the L > release of the original VAX-11/780 in 1978. Some aspects of each port haveJ > been painless, and others have proven to be challenges. The announcement ofK > the transition to Itanium has provoked much comment. However, much of therC > commentary has not addressed the detailed questions of what areas 	 representtI > significant problems, and what areas are likely to offer fewer problemse thanF > might otherwise be expected. This session will examine the technical aspectshK > of the Itanium transition. Issues will be examined both in the context oftH > the Itanium transition, and in terms of how the details of the ItaniumD > transition compare to previous transitions (VAX->MIPS; VAX->Alpha;H > PDP-11->VAX; and MIPS->Alpha). There will be an emphasis on the issuesL > raised by the most recent experiences with porting to Alpha; while earlierH > examples will be used to further illuminate the technical issues. ThisL > session will be suitable for technical and managerial IT professionals and > users. >r >y >e >m >       1624 >: >       Tuesday, September 11  >       8:00 AMm >       208A >0 >       Wednesday, September 12  >       1:00 PM  >       208A >d >       IntermediateE >      Introduction to System Dump Analyzer (SDA) by Viewing OpenVMSTr Processi > Internals 5 >       James Mehlhop    Process Software Corporatione# >       Wayne Sauer    PARSEC Group  >nK >       This workshop is for advanced OVMS users who need to understand thehH > SDA and VMS processes at an internals level. First, the speakers cover basicsH > SDA commands and process internals. For the remainder of the workshop,K > attendees use SDA to examine various aspects of the process internals and1L > scheduling. The workshop covers introduction to the SDA, process creation,G > process data structures, process data structure relationships, kerneloI > threads, locating process data structures, SYSGEN parameters related toaK > process data structures, what is mapped in process virtual address space,C2 > and analyzing process data structures using SDA. >r >r >a >n >       1627 >a >       Friday, September 14 >       8:00 AM  >       210D >  >       Introductory2 >      CHARON-VAX - A Portable VAX System Emulator8 >       Robert Boers    Software Resources International >dE >       CHARON-VAX is an application program that completely emulatese several L > models of VAX processors. The emulation is so complete that the CHARON-VAXK > emulator will run OpenVMST VAX (most current versions) unmodified as welll asK > several other operating systems such as VAXeln and NETBSD. The CHARON-VAXsH > application itself runs on Linux, Windows NT, Windows 2000 and OpenVMSI > AlphaT. When running the CHARON-VAX emulator on a modern ProLiantT, theBG > emulated VAX is actually faster than the original VAX processor. This F > presentation provides an overview of its development history and itsL > functionality. It describes how existing VAX applications can be preservedJ > unmodified while moving to a new platform and the unique opportunities aJ > hardware emulator provides to integrate binary VAX applications in a newF > environment without requiring modifications or even source code. The optionH > of the VAX emulator to connect existing Qbus peripherals to a new hostL > system without rewriting drivers or application code is described, as wellH > as the expected limits for this technology. This is a very useful tool thatL > allows customers to run their existing VAX code on a new ProLiant or AlphaI > (VMS) system. The presentation includes a demonstration of the product.c >u >w >  >  >       1643 >  >       Wednesday, September 12h >       2:45 PMi >       304A >B >       Friday, September 14 >       11:00 AM >       210D >e >       IntermediateH >      The Cool and Unhackable System - Building a Hack Proof Bunker for Floor 
 > of DEFCON9.cJ >       The DFWCUG has a special security whitepaper to present on hacking and H > the technical underground. Learn how real professionals built a system thatH > DEFCON9 Hackers themselves dubbed "Unhackable" and "Cool". Learn how a groupeL > of DFWCUG BOFH defeated the hellish maw of the hackers' best toolsmiths onI > their own home turf. The whitepaper shares information learned from theiH > Hackers during the DEFCON9 Capture the Flag Game where all attacks are legalaF > and many were recorded. This sessions should not be missed by anyoneF > interested in computer security and how to protect your servers from Hacker
 > attacks. >a >  >g >e >       1644 >i >       Friday, September 14 >       8:00 AMr >       Hilton - San Clementes >e >       Intermediate7 >      Making Your OpenVMST Environment HIPAA Compliantn0 >       Dena Wright    Baylor Health Care System >iF >       Hospitals across the United States are mandated by the federalK > government to become (Health Insurance Portability and Accountability Actn ofL > 1996) HIPAA compliant. Come to this session to learn where HIPAA fits intoJ > heathcare provider's IT infrastructure today and where it's going in the	 > future.a >r >D >l >e >       1645 >, >       Thursday, September 13 >       4:00 PMn >       Hilton - Oceanside >n >       IntermediateH >      Open Source Software on OpenVMST - Python, Perl, GNU, and a Whole Host0 > of Open Source Animals on OpenVMS? Absolutely!4 >       JoAnn DiFrancesco    Sequel Data Systems Inc' >       Steven Smiley    City of Dallasc >oJ >       Come and learn what is available, where to get them, and hints andF > tricks on how to build and install the Open Source Tools On OpenVMS! >  >  >i >s >       1650 >r >       Thursday, September 13 >       8:00 AMe >       Hilton - San Clementew >s >       Intermediate$ >      Upgrading OpenVMST 7.2 to 7.3+ >       Robert Drinjak    Efendi Associates5! >       John Wisniewski    Compaq4 > G >       This session presents an OpenVMST 7.2 to 7.3 upgrade. While theoL > upgrade is being performed, hints, tips and traps are discussed as well as5 > information from the Release Notes for OpenVMS 7.3.  >K >s >b >  >       1656 >e >       Tuesday, September 11a >       10:45 AM >       Hilton - La Jollai >  >       Intermediate$ >      PMDF on OpenVMS Working Group6 >       Hunter Goatley    Process Software Corporation >hH >       Attendees using PMDF on OpenVMS systems will discuss issues withG > current version, share technical helps, discuss upcoming versions andp theirsJ > features, and give feedback to the vendor on wants, needs and wish-list. >n >s >c >e >       1658 >c >       Tuesday, September 11t >       2:30 PMe >       Hilton - Lido Ai >  >       Intermediate >      MultiNet Working Groupt6 >       Hunter Goatley    Process Software Corporation >tH >       Join vendor representatives to discuss MultiNet TCP/IP and shareK > technical hints, features, and issues. Provide feedback to the vendor for 3 > new features or wish-list items for this product.r >n >t >m >m >       1659 >  >       Tuesday, September 11s >       4:00 PMa >       Hilton - Lido AC >  >       Intermediate >      TCPware Working Group6 >       Hunter Goatley    Process Software Corporation >sG >       Join vendor representatives to discuss TCPware TCP/IP features,oE > issues, and share technical hints. This BOF session gives attendees I > opportunity to provide feedback on the product and suggest features fora > future releases. >a >c >i >t >       1660 >u >       Thursday, September 13 >       11:00 AM >       Hilton - La Jollan >l >       Introductory< >      Educational Initiative - CSLG, ESL, TEI Working Group >       Kerry Smith    Compaqc >sK >       Meet with Compaq to discuss the latest features, pricing, products,pH > and changes in the Campuswide Software Licensing Grant and EducationalI > Software License programs for educational sites. If your site is on the / > CSLG/ESL program, this BOF session is a MUST!e >  >  >p >t >       1661 >a >       Thursday, September 13 >       9:30 AMC >       Hilton - Lido A  >  >       Intermediate0 >      Enterprise Directory & LDAP Working Group/ >       Jenny Butler    University of Tennesseer >cG >       Discuss features and uses of an Enterprise Directory or LDAP inyI > production environments. This working group will provide opportunity toeA > learn about Compaq's plans and products in an informal setting.d >a >n >o >u >       1665 >  >       Wednesday, September 12o >       2:45 PMs >       Hilton - Lido A  >  >       Intermediate >      I Want my VMS!n* >       Jean Norton    Sysnet Staffing Inc >eH >       Are you at risk of migrating away from OpenVMS? Have you alreadyF > migrated away from OpenVMS? Let's get together and talk about tools,J > emulators, and how to cope with withdrawal pains. By the way, it's OK to cryt > in this session. >a >o >e >r >       1673 >e >       Monday, September 10 >       12:45 PM
 >       303CD, >  >       Introductory6 >      You Can Bet Your Business on Compaq and Itanium4 >       Rich Marcello    Compaq Computer Corporation > E >       This session addresses fundamental business issues related toc Compaq'sK > AlphaT to Itanium strategy. These issues include: Preserving your alreadyzL > existing investment in your Tru64T UNIX or OpenVMST IT infrastructure; WhyI > the investment you make today in new projects deployed on Tru64 UNIX oraL > OpenVMS, both in terms of hardware and application development costs, willJ > be preserved in the future; What Compaq is doing to insure the long termF > viability of OpenVMS and Tru64 UNIX in the marketplace as technology leadingeI > enterprise class servers. These issues and others are covered, and thisiK > session provides the answers to why Compaq's Alpha to Itanium strategy ise at > safe bet for your business.w >  >  >e >o >       1674 >n >       Monday, September 10 >       3:45 PMt
 >       303CD  >r >       IntroductoryG >      Compaq Directions for Integrating Alpha Chip Technology with theg Intele+ > Itanium Processor Family: Executive Panel 4 >       Steve Langdon    Compaq Computer Corporation >mL >       Join us for this panel discussion with Compaq engineering executivesH > as we discuss the plans for integrating Alpha chip technology into the InteliK > Itanium Processor Family (IPF). We'll address your interests and concerns & > about future server and OS roadmaps. >n >a >S >e >       1684 >  >       Thursday, September 13 >       4:00 PMh >       210B >y >       Friday, September 14 >       8:00 AMe >       303B >e >       IntroductoryH >      TruClusters, VMSclusters, Windows 2000 DataCenter Clusters, Linux. > Clusters, and More: How Do They All Compare?1 >       Ken Moreau    Compaq Computer Corporationg > I >       This session analyzes the technologies behind Compaq's clusteringyK > products, shows you where they are the same and where they are different,eL > and demonstrates why Compaq has the best clustering products on the market% > on multiple operating environments.c >a >e >t >  >       1690 >  >       Tuesday, September 11  >       10:45 AM >       303B >  >       IntroductoryH >      Building a Protected Networked Enterprise- Security for Business: It's8 > No Longer a Technology Looking for a Problem to Solve!( >       Dan Boneh    Stanford University >p >       To be announced. >n >m >n >r >       1691 >c >       Tuesday, September 11l >       1:00 PMa >       210B >a >       IntroductoryG >      New World Security Threats and Compaq's Strategy to Address Themn5 >       Michael Angelo    Compaq Computer Corporationh >mK >       This session provides insight into the evolving models for computergG > usage and their associated threats. We also examine a number of usage I > scenarios and evaluate the threats to each stage of the infrastructure.  ThisI > session also provides a technological overview of Compaq's strategy andT$ > directions for providing security. >  >a >  >e >       1692 >e >       Thursday, September 13 >       8:00 AM  >       210B >  >       Introductory! >      Privacy, the New Challenge 4 >       Dan Swartwood    Compaq Computer Corporation >iH >       With interconnected computers, databases, and near instantaneousJ > responses to requests for information, the collection, transmission, andJ > aggregation of personal information has become problematic for companiesJ > operating online. This session provides definitions, comparisons betweenK > privacy and information security, and an overview of the current state of F > affairs surrounding privacy from a legislative, standards-based, andL > consortia-based point of view. This session also covers the current issues > surrounding privacy. >m >e >o >r >       1693 >e >       Thursday, September 13 >       4:00 PM  >       Hilton - La Jollab >d >       Introductory >      OpenVMS Hobbyist Programa6 >       John Wisniewski    Compaq Computer Corporation >eG >       Come learn how you can obtain free OpenVMS license for HobbyisteJ > (Personal) use of OpenVMS. The OpenVMS Hobbyist License Program provides theSD > operating system license and over 150 layered product licenses for	 personal,tK > home use on your VAX or Alpha. Program license requirements and obtainingp4 > your personal (used) Alpha will also be discussed. >r >e >  >r >       1694 >e >       Thursday, September 13 >       2:30 PMi >       201B >r >       Intermediate; >      Hot Topics in Real World Security: Interactive Panelb5 >       Michael Angelo    Compaq Computer Corporationr4 >       John Carchide    Compaq Computer Corporation1 >       Bob Dennis    Compaq Computer Corporatione3 >       Roger French    Compaq Computer Corporationi2 >       Manny Novoa    Compaq Computer Corporation4 >       Sridhar Solur    Compaq Computer Corporation >gL >       This is an interactive session with the audience. What's Hot, What'sH > Not, in the security world? What are the security drivers of tomorrowP What" > will you need to know next year? >i >e >o >  >       1695 >a >       Wednesday, September 12, >       8:00 AMp >       210A >m >       IntroductoryA >      Crypto 101 - Navigating DES, Public Key, Private Key, Etc.t1 >       Bob Dennis    Compaq Computer Corporationo >tG >       DES vs. SSL; symmetric vs. asymmetric keys; bulk encryption vs.i secureJ > session setup; 128 bit or 1024 bit encryption - My customer (or boss) isH > asking me questions I'm afraid to answer, for fear of saying the wrongH > thing. This session is designed to clarify the technical geek speak of9 > security and demystify the "black art" of cryptography.C >u >  >p >t >       1696 >  >       Friday, September 14 >       9:30 AMy >       303A >  >       Advanced& >      Implementing Analysis SolutionsK >       Laura Chappell    The Protocol Analysis Institute; packet-level.comi > I >       This session contains case studies of various security threats ati theeF > packet trace level seen 'in the wild'. Laura reviews common problemsJ > detected with a protocol analyzer and provides a list of proactive steps; > that you can take immediately upon return to your office.  >  >  >  >n >       1703 >1 >       Wednesday, September 12D >       11:00 AM >       Hilton - La Jollae >S >       Intermediate* >      Domain Name System (DNS) Management* >       Jeff Schreiber    Process Software >TH >       The Domain Name System (DNS) protocol, while being a very simpleJ > concept, can be an extremely challenging and confusing protocol to fullyC > understand. Better understanding enables easier configuration andsG > maintenance of your DNS. This session brings together experienced andi noviceI > DNS hostmasters to answer your DNS configuration and protocol questionss and  > to share experiences.  >  >r >y >e >       1733 >  >       Tuesday, September 11  >       2:30 PMt >       Hilton - Lido BM >  >       Introductory- >      Encompass Local User Group Informationi& >       Pamela Campbell    DataCeutics >nL >       Calling all Encompass Local User Group members and those who want toH > join or form a new Local User Group (LUG)! This year's Advice Panel isJ > answering the questions and taking suggestions on how to start new LUGs,H > reinvigorate existing LUGs, how LUGs should work with Encompass US and. > Compaq, and what members want from the LUGs. >g >  >  >o >       1882 >h >       Wednesday, September 12k >       8:00 AMH >       Hilton - Lido Bo >n >       Intermediate2 >      Computer Support of Air Force Organizations0 >       Laurie Knepper    Joint STARS Test Force >oJ >       Discussion of topics relevant to computer technical support of AirE > Force organizations. Actual topics will include such items as SATE,i computerC > issues, keeping up with NOTAM/TCNO suspenses, PKI, user training,o	 technicaleJ > support resources, and training resources. Bring descriptions, contacts,C > sources, and URLs for the resources you find most helpful in yourh	 technical  > support efforts. >  >t >c >  >       1884 >p >       Tuesday, September 11  >       10:45 AM >       303A8 >      OpenVMS Internals on the Itanium Processor Family2 >       Clair Grant    Compaq Computer Corporation >sL >       This session describes how some of the internals of OpenVMST will beI > ported to the ItaniumT Processor Family (IPF). Mechanisms such as ASTs, L > IPLs, page protections, synchronization methods, and context switching areF > presented in terms of the Intel fundamentals used to implement them. >  >  >a >  >l >    ------------------------------  % Date: Tue, 28 Aug 2001 21:19:53 -0500 1 From: "David J. Dachtera" <djesys.nospam@fsi.net>o= Subject: VMS's Last Stand or Conspiracy/Stupidity Theories...l' Message-ID: <3B8C5149.E6DCB087@fsi.net>s  
 Fair warning:aF The analyst/problem-solver in me (powerful choleric) wants to have hisD say. So, Larry K. and others can skip this thread and move on to the next.   F ...and yes, I realize that some will take this as trollery(?) or flame bait...c  F Some folks have put forth conspiracy theories. They may very well haveE an acute insight. I say that because the thought occurs to me, thoughsA not a "conspiracy" theory, that there may just be some "stupidity   theories" that would hold water.  F Consider the record: some products which got promoted and marketed got  publicly axed shortly afterward.  H Why would a company INTENTIONALLY seek to destroy their own credibility?  H My guess is that they wouldn't, that there is something more sinister atE work here. We've all seen the "us and them" attitudes (on both sides) H that typically arise in corporate merger situations. It stands to reason  that Compaq may be no exception.  = Given recent revelations as cited here in this forum ("Compaq D alienates..."), I can't help feeling that even within the pre-mergerH Compaq, there were already opposing factions. The new CTO and the "chief@ science officer" would seem to be aligned with the more powerfulH faction. Those factions, who were already at war, got more to fight over< with the acquisition of Alpha (VAX was already scheduled forH "termination"), NT, Tru64 (pka Digital UNIX) and OpenVMS - none of whichC was wanted (apparently) by the more powerful of those factions. WarnE knows no logic save that of the side most likely to achieve its ends,VF the more capable of doing so. Thus, when the opposing faction tried toD capitalize on these newly acquired assets, the more powerful faction. killed them off - first Alpha/NT, then Alpha.   H Another possibility is that the "weaker" faction sees efforts being madeC to kill off these products, and tries to counter with marketing andtE promotion, only to have the stronger faction cut them off (again) "atr
 the pass".  C "What's left?", you might ask. The answer, as the old song says, is H "blowin' in the wind". As another poster cited, they've begun marketing,G in a small way, OpenVMS. This is a sworn enemy of one of the factions - F the apparently more powerful one. Heaven help us if anyone is thinking# that "the third time is the charm".k  E Whatever factors may be at work within Compaq, the sequence of events A shortly to come is predictable, albeit with only a circumstantial.F likelihood. Given the behavior displayed by Compaq as a whole to date,G there is little reason to believe that another outcome is either likely  or probable.  A I'd like to believe that the whole DII-COE initiative is based ontG commitments to existing government customers, and not an effort to sellgH more VMS into those areas of government where it retains only a marginal2 foothold, much the same as in the private sector.   G The weight of evidence, however, is preponderantly against that belief.rC Under the theories put forth here, it is entirely possible that the D DII-COE move was an act of defiance against the stronger faction andG was, in fact, doomed from the start. That is, it may hold no promise of F longevity for OpenVMS and may, in fact, be little more than VMS's Last Stand.  @ Therefore, I accept the decision by many to abandon OpenVMS. The= likelihood of my joining those ranks increases with every newc pronouncement from the "Q".n  B On the other hand, I may just be sufficiently gullible that I haveA "bought into" exactly the impression that Compaq wants to create.u   Dunno... I'm *SO* confused!6   --   David J. Dachterae dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/V   ------------------------------  % Date: Tue, 28 Aug 2001 22:42:50 -0400n- From: JF Mezei <jfmezei.spamnot@videotron.ca>SA Subject: Re: VMS's Last Stand or Conspiracy/Stupidity Theories...o, Message-ID: <3B8C56A4.487EB0A6@videotron.ca>   "David J. Dachtera" wrote:C > I'd like to believe that the whole DII-COE initiative is based onMI > commitments to existing government customers, and not an effort to sell J > more VMS into those areas of government where it retains only a marginal3 > foothold, much the same as in the private sector.k  I At a mArcello presentation last february, he worded the DII-COE in a verysI interesting way. Something to the order of "for those who need it, we arei) willing to make the DII-COE commitments".c  G The image that was gotten was that this DII-COE only applies to certainKJ customers. I wouldn't be surprised if there wasn't some escrow clause thatF allows Compaq to dump VMS and give those customers access to the code.  N However, the point you make is perhaps valid.  The VMS folks probably insertedK the equivalent of a poison pill by taking some small actions not noticed by L people with real power at Compaq, and making written contractual commitmentsL with a few customers (do we know if any customers actually signed stuff that commits Compaq to DII-COE ?).   K So, when Compaq comes and wants to kill VMS, whoever is left at the helm of J VMS can point to the costs of breaking the contracts to customers, forcingN Compaq to keep VMS on life support for a while longer. In other words, DII-COE9 may just be a disincentive to prevent Compaq to kill VMS.u  G In any event, any product whose manager must actively fight AGAINST hishI employer's wish to downgrade/kill/ignore that product is a product nobodyu% should make long term investments in.    ------------------------------    Date: 28 Aug 2001 10:11:32 -0400+ From: randall.burlew@srs.gov (Randy Burlew) = Subject: Re: Wailing at Eunuchs (was: Wailing and Moaning...)o, Message-ID: <2001Aug28.101132.13104@srs.gov>   Hamlyn Mootoo says....   Randy Burlew wrote: @ >> I agree that abuse is possible in both systems. However, yourB >> experience, even if wide, is still a very small sampling of all6 >> VMS installations. There is no basis for you to say >>  E >> "...an incredibly LARGE percentage of user accounts on VMS systemsi+ >> are running around with near full privs"  >> rD >> I would have no beef with "In my experiences, an incredibly LARGE >> percentage..."  >> cE >> You do not and cannot speak for the majority of VMS sites. We takeaF >> great care in creating user accounts so that everyone has the privsE >> they require but no more than they require. I went round and roundpG >> with a CA tech. support person because they wanted us to run our DBA ; >> accounts with BYPASS to get around a checkpoint problem.t >rG >Thanks for adding for evidence supporting my point.  CA is not a small G >software company.  In fact, I believe at one time they were consideredoG >the largest on the planet.  If their tech support made that suggestione@ >with a "straight face" then guess how many people got that sameH >suggestion too?  And that suggestion belies their tendency toward using; >that solution to fix a host of other tech support problem.  > D You just like to argue, don't you? What CA technical support says orF does is hardly germane to the issue -- their support for VMS is almostG an afterthought. I found acceptable solutions to the problem by postingdB to comp.databases.ingres and people who really used VMS responded.  F Hey, you could even be right. But I don't see how you could know that.F I think you have a extreme problem with tunnel vision if you take your@ own experiences and say that is the way it must work everywhere.  
 >IncidentallyiE >I challenge you to show me your equations and data to represent whathF >sample is statistically significant given an few hundred thousand VMS9 >installation worldwide (probably a lot less now though).i  F Because you talk about your past experiences, you must include all VMSD installations that has ever been. A lot more than a few thousand. ToG say otherwise is comparing grapes to bananas. Besides, I am not the onei2 that claimed my experiences reflected everyone's.   = Is it really that hard for you to say "In my experiences..."?t   >> eG >> The vast majority of people I know who run VMS are also very carefuliG >> about privs. Doesn't prove anything, but in my experience I find theo >> above quote hard to believe.p >> AF >> We also know exactly what our third party app installs do. It's not+ >> that hard to keep track of these things.e >> e >> Randy   ------------------------------  % Date: Tue, 28 Aug 2001 16:51:41 -0400t' From: "Bill Todd" <billtodd@foo.mv.com>y0 Subject: Re: Why continue with OpenVMS / Compaq?( Message-ID: <9mh07n$o7b$1@pyrite.mv.net>  0 <dQdelQlutrQX@XQXentQeract.com> wrote in message% news:9mg98n$qt6$1@bob.news.rcn.net...e4 > On Mon, 27 Aug 2001 22:58:44 -0400, Chuck McCrobie  <mccrobie@cablespeed.com> wrote: > >...J > > My suggestion to you die-hards is to abandon OpenVMS, Tru64, and Alpha > > _IMMEDIATELY_. > >...I > > I'm wondering just why anyone would continue/start another product onm > > OpenVMS or Tru64?h >  > Why not stay on OpenVMS?  D 1.  Because Compaq can't be trusted as its vendor (you want hardwareG upgrades?  you want software upgrades?  you want support?  maybe, mayben not).l  F 2.  Because even if you don't believe the above (some people won't, noK matter how clear the evidence) VMS *certainly* won't be getting much in thenH way of enhancements over the next few years while most efforts are being dedicated to porting it.  J 3.  Because you don't want to commit new uses to a declared-dying hardwareG platform during the 3 years between now and when VMS will supposedly be " available on a non-dying platform.  F 4.  Because if you're likely going to wind up porting existing uses toG different hardware anyway (unless you're planning to phase out your VMS G platforms before viable Alpha hardware starts to become hard to acquirerL and/or ridiculously expensive) it makes sense to evaluate porting options to other environments as well.l  H None of those reasons may apply to you, but they certainly apply to many
 customers.  -   I really don't care what chip is underneath ? > the OS, as long as its price/performance is good.  OpenVMS ish> > important because of its enterprise features which NT lacks.  H But a lot less indispensible since several Unixes acquired many of these	 features.o   > " > Compaq will port VMS to Itanium.  I So it says.  Of course, a bit over two months ago it was proclaiming withwK equal vigor that EV7 and EV8 would blow the doors off future IA64 products, = and that you should hitch your business's wagon to that star.:   ...   .   So I see NO cause for panic now, NO cause to) > abandon a good OS on good hardware now.w  K If Compaq were anything like a trustworthy vendor, that argument might havedJ at least *some* merit for at least *some* uses of VMS.  Unfortunately, ...   - bill   ------------------------------  % Date: Tue, 28 Aug 2001 15:54:27 -0700o< From: "Kenneth H. Fairfield" <Kenneth.H.Fairfield@intel.com>C Subject: Re: [Q]: How to get BACKUP to relabel tapes automatically?i) Message-ID: <3B8C2123.10A5F67E@intel.com>    John Santos wrote: [...]c  E > What's the host connection for the TZ877?  The only place I've usedeE > them is via an HSJ50 to an Alpha 4100, and MRU works fine for this.  > E > At my customer's site (where the TZ877 lives), I can load, use, and:A > unload any of the 7 tapes using MRU.  I'm not sure what happens D > after you run off the end of the 7th tape (i.e. in BACKUP); it mayC > eject the cartridge, but you can certainly load, init, and unloadlE > the 7th tape, then reposition to the 1st tape and load that one and A > start the backup.  I don't know for sure that this works with a B > TZ877 connected directly to a host SCSI adapter or via an HSZxx,B > etc.  MRU version V1.4-1, the stacker shows up on the HSJ and inD > MRU as a "DEC TZ Media Changer9823", and the tape drive as a TZ87.D > The HSJ50 is running firmware V51J-0.  (I think this is pretty oldG > and the current version is V54; I hope they haven't broken anything!)a  D OK, this is _very_ good news.  Our TZ877's are hosted on HSJ40's andE HSJ50's (in different clusters), those at various firmware revisions. C But I do have a plan to upgrade all the HSJ50's to V57 (or whatevereF is the latest/last release) and the HSJ40's to V37.  I'll get in touchD with our support people and see if I can get them to send us a copy.       Thanks!  -Kenn --6 I don't speak for Intel, Intel doesn't speak for me...   ------------------------------   End of INFO-VAX 2001.479 ************************