1 INFO-VAX	Tue, 09 Aug 2005	Volume 2005 : Issue 441       Contents:* 7.3-2 Crashes when a Samba Client connects) Re: Another VMS system bites the dust :-( ) Re: Another VMS system bites the dust :-(  AS2100 with KZPBA  Re: AS2100 with KZPBA  Re: AS2100 with KZPBA  Re: EFI is out to lunch  Re: EFI is out to lunch  Re: EFI is out to lunch  Re: EFI is out to lunch 1 Gartner upgrades HP's vendor rating to "Positive" 5 Re: Gartner upgrades HP's vendor rating to "Positive" 5 Re: Gartner upgrades HP's vendor rating to "Positive" ; Re: how to get rid of "explicit carriage returns" in a file ; Re: HP Pearl - HP Says Over 5,000 Applications on Integrity ; InformationWeek: Intel Says Itanium Chip Is Doing Just Fine ? Re: InformationWeek: Intel Says Itanium Chip Is Doing Just Fine ? Re: InformationWeek: Intel Says Itanium Chip Is Doing Just Fine  Is it Possible?  Re: Is it Possible? 7 Re: Killing a process that has allocated the tape drive 7 Re: Killing a process that has allocated the tape drive 7 Re: Killing a process that has allocated the tape drive 7 Re: Killing a process that has allocated the tape drive 7 Re: Killing a process that has allocated the tape drive 7 Re: Killing a process that has allocated the tape drive 7 Re: Killing a process that has allocated the tape drive 6 Mark Hurd to be keynote speaker at HP Technology Forum: Re: Mark Hurd to be keynote speaker at HP Technology Forum Re: PERL RE: PERL+ Re: strange terminal-characteristic problem + Re: strange terminal-characteristic problem + Re: strange terminal-characteristic problem + Re: strange terminal-characteristic problem + Re: strange terminal-characteristic problem + Re: strange terminal-characteristic problem + Re: strange terminal-characteristic problem + Re: strange terminal-characteristic problem  Vax/VMS Calculator Re: Vax/VMS Calculator Re: Vax/VMS Calculator Re: Vax/VMS Calculator  F ----------------------------------------------------------------------  % Date: Mon, 08 Aug 2005 20:20:45 -0000 1 From: wspencer@ap.dontspamme.org (Warren Spencer) 3 Subject: 7.3-2 Crashes when a Samba Client connects 1 Message-ID: <96ACA7719wspenceraporg@216.168.3.30>   	 Hi Folks,   I I've got an OpenVMS crash I need to sort out and I'm looking for help on   where to go next.     J This is an OpenVMS 7.3-2 box, with all (applicable) patches applied.  The H tcpip stack is Multinet 4.4A, with all applicable patches applied.  The  problem is this:  I When any Samba client attempts to connect to this box, Multinet fires up  E smbd_startup.com (as it should) and the box crashs with "SSRVEXCEPT,  % Unexpected system service exception".   E The Samba version is 2.2.8, freshly compiled & installed on this box.    Some other info:  G - Either a local or remote samba client connecting will cause the crash 6 - The crash always happens on the first client connect< - The crash always happens - Samba has yet to work correctlyF - I've configured smbd as a Multinet service, so Multinet is invoking K smbd_startup.com.  But I'm not sure if this is the way it's supposed to be   set up.   - Any ideas where to go next?  What to look at?    Many thanks!   ws   --   Warren Spencer Senior Software Engineer The Associated Press   ------------------------------   Date: 8 Aug 2005 13:41:10 -0500 % From: frey@encompasserve.org (Sharon) 2 Subject: Re: Another VMS system bites the dust :-(3 Message-ID: <MFB2p3HiQ+Lu@eisner.encompasserve.org>   [ In article <42E66FB6.D8E2C26@teksavvy.com>, JF Mezei <jfmezei.spamnot@teksavvy.com> writes:  > "Stanley F. Quayle" wrote:E >> I had proposed CHARON-VAX as a replacement back in September 2004. D >> They were already on their way to the replacement system.  *sigh* >  > E > Did they replace it with tandem technology ? any other HP product ?  >  > L > Integration is "interesting" argument. I don't see why VMS system couldn'tN > connect to other systems to pick the information and do all the fancy stuff.  E 	Speaking as a VMS software engineer who specializes in 911 dispatch  J systems, the answer is it can.  And does.  And does it well, but I'm sure O everyone here isn't surprised to hear that.  My coworkers and I have full time  J jobs implementing and upgrading real-time interfaces between the dispatch M software on VMS and mobile computers, radios, phones, maps, databases, other   computer systems, etc.  P > What I'd like to know is whether HP fought to maintain this VMS account or if,P > as usual, they had already written off all VMS acocunts so they doN't feel bad > when losing them.   E 	My guess is that HP has nothing to do with it, and possibly no clue  P that they're out there.  These kinds of systems are usually purchased through a P 3rd party vendor like mine, who sells the full hardware&software package to the 
 end customer.    --    	  - Sharon " "Gravity...  is a harsh mistress!"   ------------------------------   Date: 8 Aug 2005 16:22:59 -0500 ; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) 2 Subject: Re: Another VMS system bites the dust :-(3 Message-ID: <Y0VIEjGirc3j@eisner.encompasserve.org>   [ In article <MFB2p3HiQ+Lu@eisner.encompasserve.org>, frey@encompasserve.org (Sharon) writes: G > 	My guess is that HP has nothing to do with it, and possibly no clue  R > that they're out there.  These kinds of systems are usually purchased through a R > 3rd party vendor like mine, who sells the full hardware&software package to the  > end customer.  >  > --   >  >  - Sharon $ > "Gravity...  is a harsh mistress!"  6    Gee I hope Montgomery County is using your product.   ------------------------------  $ Date: Mon, 8 Aug 2005 17:50:11 -04002 From: "Jonathan Boswell" <jsb.NOSP@M.cdrh.fda.gov> Subject: AS2100 with KZPBA2 Message-ID: <osQJe.286$n5.350@mencken.net.nih.gov>  C I've got a bizarre situation that's driving me crazy.  I've got two K Alphaserver 2100RM's with a shared SCSI bus using the embedded NCR-810 SCSI L adapter.  (Yes, this is supported.)  Since the bus is shared, the controllerH has to show up in VMS with the same device letter on both hosts, in thisE case as pka0.  This all works fine until I install a KZPBA-CA running D firmware 5.57 into one of the AS2100's.  All is copacetic within theL console, with device naming conventions as I expect.  But once VMS comes up,L the embedded controller becomes pkb0 and the KZPBA becomes pka0, after whichE all hell breaks loose.  Can anybody clue me in as to how the embedded I controller is getting booted off pka0 and becomes pkb0 once VMS comes up?    ------------------------------   Date: 8 Aug 2005 15:11:01 -0700  From: sean@obanion.us  Subject: Re: AS2100 with KZPBAC Message-ID: <1123539061.859367.298110@o13g2000cwo.googlegroups.com>   ? SCSI port naming is based on order of discovery, which VMS uses E different rules that the console.  You probably need to use SCSI port E allocation classes to force naming to be consistent, and is discussed 5 in the Guidelines for OpenVMS Cluster Configurations.      Sean   ------------------------------   Date: 8 Aug 2005 15:29:50 -0700 % From: "martin" <baechtel@comcast.net>  Subject: Re: AS2100 with KZPBAB Message-ID: <1123540190.830612.56990@g49g2000cwa.googlegroups.com>  D I had the same thing on an Alphastation and a KZPSC-BA. The KZPSC-BAG needed flashed with the lastest firmware. This is a multi-step setup. I E see you have a FDA e-mail address are you in the Rockville office? If E so I can help you set it up I'm just up the street. It been about two G years work on an 2100 I may have to dig up the Docs on your controllers + setup.  Setting the boot no problem at all.    Jonathan Boswell wrote: E > I've got a bizarre situation that's driving me crazy.  I've got two M > Alphaserver 2100RM's with a shared SCSI bus using the embedded NCR-810 SCSI N > adapter.  (Yes, this is supported.)  Since the bus is shared, the controllerJ > has to show up in VMS with the same device letter on both hosts, in thisG > case as pka0.  This all works fine until I install a KZPBA-CA running F > firmware 5.57 into one of the AS2100's.  All is copacetic within theN > console, with device naming conventions as I expect.  But once VMS comes up,N > the embedded controller becomes pkb0 and the KZPBA becomes pka0, after whichG > all hell breaks loose.  Can anybody clue me in as to how the embedded K > controller is getting booted off pka0 and becomes pkb0 once VMS comes up?    ------------------------------  % Date: Mon, 08 Aug 2005 14:26:19 -0400 , From: Forrest Kenney <Forrest.Kenney@hp.com>  Subject: Re: EFI is out to lunch& Message-ID: <42F7A3CB.59766976@hp.com>  ; 	Certain hardware failures can also result in the EFI shell > looping.  I managed to do that by adding in a PCI card with a 7 16550 UART on it.  System hung forever in the firmware.   6 	You should also see if you can get control before it > drops into the shell.  If so see if you can get into the boot  manager and get it to respond.  8 	For trouble shooting unplug the network, and any disks A and just hook up a serial console.  Then see if you can get into   the shell and do anything.     Forrest    ------------------------------  # Date: Mon, 08 Aug 2005 21:14:51 GMT " From:   VAXman-  @SendSpamHere.ORG  Subject: Re: EFI is out to lunch0 Message-ID: <00A47FC5.269EEBDA@SendSpamHere.ORG>  U In article <42F7A3CB.59766976@hp.com>, Forrest Kenney <Forrest.Kenney@hp.com> writes:  > < >	Certain hardware failures can also result in the EFI shell? >looping.  I managed to do that by adding in a PCI card with a  8 >16550 UART on it.  System hung forever in the firmware.  > Hey, now we're getting somewhere.  Though, I have added no NEW> hardware to the box as it came configured from HP save for the= addition of 2GB of memory that the box was short-changed when  it shipped.   = There is NOTHING connected to any serial port on this system. = Only the console serial port (the DB9 connector on the 3 DB9- < DB25 cable assemble) and YES it is connected to the one that= is labelled CONSOLE.  THis has been working for months.  I've ; booted and rebooted more times than I care to have counted. < This system WAS running just fine in my cluster for building= a software package.  I was powering it down to boot it stand- ' alone to test this software just built.       7 >	You should also see if you can get control before it  ? >drops into the shell.  If so see if you can get into the boot   >manager and get it to respond.   < Explain.  when I bring up the COnsole (MP:CO) I see it check; the hardware (looking for SCSI devices, luns etc.) and then < it would typically go to the EFI Boot menu.  I defined a VMS< boot item there too but almost never use it as I let it drop< to the Shell> prompt and use my "boot" alias command since I- tend to conversationally boot it most often.        9 >	For trouble shooting unplug the network, and any disks  B >and just hook up a serial console.  Then see if you can get into  >the shell and do anything.   = The only network connection is the gigabit ethernet which is  < to the main processor, not the mgt processor but I'll remove/ it.  I'll try pulling the disks too.  Thanks...     $ To quote from the movie "War Games":  = "I'd piss on a spark plug if I thought it would do any good!"    --  K VAXman- A Bored Certified VMS Kernel Mode Hacker   VAXman(at)TMESIS(dot)COM              5   "Well my son, life is like a beanstalk, isn't it?"     ------------------------------  # Date: Mon, 08 Aug 2005 22:11:10 GMT * From: "FredK" <fred.nospam@nospam.dec.com>  Subject: Re: EFI is out to lunch3 Message-ID: <2MQJe.10036$hx2.6760@news.cpqcorp.net>   K You have to explicitly enable it and give it an address.  I believe it also  supports Kerberos.  H "Bob Koehler" <koehler@eisner.nospam.encompasserve.org> wrote in message- news:v1W5jSVMFnhy@eisner.encompasserve.org... I > In article <acRIe.9956$7L6.4459@news.cpqcorp.net>, hoff@hp.nospam (Hoff  Hoffman) writes: > C > >   The consoles on I64 can have more than one connection, and it C > >   can be a bit surprising when you first see another session on 2 > >   another line acquire and access the console. > J >    Which brings up the question of whether it's possible that the scriptI >    kiddies on the network have find some way to attach to this console?  > @ >    I'm under the impression that the console is IP accessable. >    ------------------------------  % Date: Mon, 08 Aug 2005 18:21:25 -0400 , From: Forrest Kenney <Forrest.Kenney@hp.com>  Subject: Re: EFI is out to lunch& Message-ID: <42F7DAE5.1F9021C9@hp.com>  > 	Please remove all the disks and network connection.  Then do  the following.  6 1) Power the system down and pull the power cable out   , 2) Plug in power and log into the MP console   3) Power the system up  A 4) Use the CO command to get to the power up information and the      boot manager menue   D 5) Get a log of all of this, also check the server logs for problems  E 6) When it get far enough along it will before falling into the sell  E    present you with an option to get to the boot maint utility.  Try       to get into that if possible.  A 	This feels like either broken hardware, of a bad script file on  @ the boot disk(s).  That is why we would like you to remove them.   Forrest         ! VAXman-, @SendSpamHere.ORG wrote:  > W > In article <42F7A3CB.59766976@hp.com>, Forrest Kenney <Forrest.Kenney@hp.com> writes:  > > D > >       Certain hardware failures can also result in the EFI shell@ > >looping.  I managed to do that by adding in a PCI card with a: > >16550 UART on it.  System hung forever in the firmware. > @ > Hey, now we're getting somewhere.  Though, I have added no NEW@ > hardware to the box as it came configured from HP save for the? > addition of 2GB of memory that the box was short-changed when 
 > it shipped.  > ? > There is NOTHING connected to any serial port on this system. ? > Only the console serial port (the DB9 connector on the 3 DB9- > > DB25 cable assemble) and YES it is connected to the one that? > is labelled CONSOLE.  THis has been working for months.  I've = > booted and rebooted more times than I care to have counted. > > This system WAS running just fine in my cluster for building? > a software package.  I was powering it down to boot it stand- ) > alone to test this software just built.  > > > >       You should also see if you can get control before it@ > >drops into the shell.  If so see if you can get into the boot! > >manager and get it to respond.  > > > Explain.  when I bring up the COnsole (MP:CO) I see it check= > the hardware (looking for SCSI devices, luns etc.) and then > > it would typically go to the EFI Boot menu.  I defined a VMS> > boot item there too but almost never use it as I let it drop> > to the Shell> prompt and use my "boot" alias command since I. > tend to conversationally boot it most often. > @ > >       For trouble shooting unplug the network, and any disksC > >and just hook up a serial console.  Then see if you can get into  > >the shell and do anything.  > > > The only network connection is the gigabit ethernet which is> > to the main processor, not the mgt processor but I'll remove1 > it.  I'll try pulling the disks too.  Thanks...  > & > To quote from the movie "War Games": > ? > "I'd piss on a spark plug if I thought it would do any good!"  >  > --M > VAXman- A Bored Certified VMS Kernel Mode Hacker   VAXman(at)TMESIS(dot)COM  > 6 >   "Well my son, life is like a beanstalk, isn't it?"   ------------------------------  # Date: Tue, 09 Aug 2005 00:31:14 GMT 1 From: Keith Parris <keithparris_NOSPAM@yahoo.com> : Subject: Gartner upgrades HP's vendor rating to "Positive"3 Message-ID: <mPSJe.10045$_B2.8421@news.cpqcorp.net>   9 http://www.hp.com/hpinfo/newsroom/press/2005/050805a.html > HP's Vendor Rating Upgraded by Leading Technology Analyst Firm   PALO ALTO, Calif., Aug. 5, 2005 D --------------------------------------------------------------------E HP today announced that it has been upgraded to a "positive" overall  E vendor rating by technology analyst firm, Gartner, Inc., in its 2005   Vendor Rating report.   I Published annually, Gartner's Vendor Rating reports evaluate information  C technology vendors based on specific criteria related to corporate  F viability, market offerings, and customer service and support. Vendor H Rating research is a qualitative evaluation of a vendor as a whole, not , just on its position within a single market.  I Gartner upgraded HP to "positive," from an overall "promising" rating in   2004.  ... G A complete copy of Gartner's 2005 Vendor Rating report is available at   http://h71028.www7.hp.com/erc/cache/49205-0-0-0-121.aspx?bodycontentparams=258252-0-0-0-121&ERL=true&pageTitle=Enterprise%20library:%20Gartner:%20Vendor%20Rating%20-%20Hewlett-Packard%20(July%202005)  ... D --------------------------------------------------------------------H More near and dear to our hearts here, of course, was how Gartner rated C OpenVMS. Integrity Servers got an overall "Promising" rating, with  C OpenVMS explicitly included there, along with positive words about  E Montecito. "Legacy" OpenVMS (i.e. on Alpha) was rated "Caution", but  D that is a big improvement over the "Strong Negative" rating Gartner F reportedly had in the draft report, lumping OpenVMS in with death-row G inmates MPE/iX and Tru64. Kudos go to Bob Blatz and crew for the great  3 extent to which they were able to turn that around.    ------------------------------  % Date: Mon, 08 Aug 2005 20:28:39 -0500 2 From: David J Dachtera <djesys.nospam@comcast.net>> Subject: Re: Gartner upgrades HP's vendor rating to "Positive"+ Message-ID: <42F806C6.143748A3@comcast.net>    Keith Parris wrote:  > ; > http://www.hp.com/hpinfo/newsroom/press/2005/050805a.html @ > HP's Vendor Rating Upgraded by Leading Technology Analyst Firm > ! > PALO ALTO, Calif., Aug. 5, 2005 F > --------------------------------------------------------------------F > HP today announced that it has been upgraded to a "positive" overallF > vendor rating by technology analyst firm, Gartner, Inc., in its 2005 > Vendor Rating report.  > J > Published annually, Gartner's Vendor Rating reports evaluate informationD > technology vendors based on specific criteria related to corporateG > viability, market offerings, and customer service and support. Vendor I > Rating research is a qualitative evaluation of a vendor as a whole, not . > just on its position within a single market. > J > Gartner upgraded HP to "positive," from an overall "promising" rating in > 2004.  > ... H > A complete copy of Gartner's 2005 Vendor Rating report is available at > http://h71028.www7.hp.com/erc/cache/49205-0-0-0-121.aspx?bodycontentparams=258252-0-0-0-121&ERL=true&pageTitle=Enterprise%20library:%20Gartner:%20Vendor%20Rating%20-%20Hewlett-Packard%20(July%202005)  > ... F > --------------------------------------------------------------------I > More near and dear to our hearts here, of course, was how Gartner rated D > OpenVMS. Integrity Servers got an overall "Promising" rating, withD > OpenVMS explicitly included there, along with positive words aboutF > Montecito. "Legacy" OpenVMS (i.e. on Alpha) was rated "Caution", butE > that is a big improvement over the "Strong Negative" rating Gartner G > reportedly had in the draft report, lumping OpenVMS in with death-row H > inmates MPE/iX and Tru64. Kudos go to Bob Blatz and crew for the great5 > extent to which they were able to turn that around.   F Well, I'd call that 90-degree turn, not a 180. To be a 180, it's gottaC go from "Strong Negative" to "Strong Positive", or whatever is even H better than that ("Must Have"?). However, since the Alphacide, and still? lacking even so much as an acknowledgment of error on corporate D management's part, I guess "Caution" is the probably the best we can hope for, realistically.  H As to Gartner in general, given their sources of funding, I consider any0 info from Gartner to be highly suspect, at best.   --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/    Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------   Date: 8 Aug 2005 20:18:01 -0700 $ From: "AEF" <spamsink2001@yahoo.com>> Subject: Re: Gartner upgrades HP's vendor rating to "Positive"B Message-ID: <1123557481.385662.13510@g49g2000cwa.googlegroups.com>   David J Dachtera wrote:  > Keith Parris wrote:  > > = > > http://www.hp.com/hpinfo/newsroom/press/2005/050805a.html B > > HP's Vendor Rating Upgraded by Leading Technology Analyst Firm > > # > > PALO ALTO, Calif., Aug. 5, 2005 H > > --------------------------------------------------------------------H > > HP today announced that it has been upgraded to a "positive" overallH > > vendor rating by technology analyst firm, Gartner, Inc., in its 2005 > > Vendor Rating report.  > > L > > Published annually, Gartner's Vendor Rating reports evaluate informationF > > technology vendors based on specific criteria related to corporateI > > viability, market offerings, and customer service and support. Vendor K > > Rating research is a qualitative evaluation of a vendor as a whole, not 0 > > just on its position within a single market. > > L > > Gartner upgraded HP to "positive," from an overall "promising" rating in	 > > 2004.  > > ... J > > A complete copy of Gartner's 2005 Vendor Rating report is available at > > http://h71028.www7.hp.com/erc/cache/49205-0-0-0-121.aspx?bodycontentparams=258252-0-0-0-121&ERL=true&pageTitle=Enterprise%20library:%20Gartner:%20Vendor%20Rating%20-%20Hewlett-Packard%20(July%202005)  > > ... H > > --------------------------------------------------------------------K > > More near and dear to our hearts here, of course, was how Gartner rated F > > OpenVMS. Integrity Servers got an overall "Promising" rating, withF > > OpenVMS explicitly included there, along with positive words aboutH > > Montecito. "Legacy" OpenVMS (i.e. on Alpha) was rated "Caution", butG > > that is a big improvement over the "Strong Negative" rating Gartner I > > reportedly had in the draft report, lumping OpenVMS in with death-row J > > inmates MPE/iX and Tru64. Kudos go to Bob Blatz and crew for the great7 > > extent to which they were able to turn that around.  > H > Well, I'd call that 90-degree turn, not a 180. To be a 180, it's gottaE > go from "Strong Negative" to "Strong Positive", or whatever is even J > better than that ("Must Have"?). However, since the Alphacide, and stillA > lacking even so much as an acknowledgment of error on corporate F > management's part, I guess "Caution" is the probably the best we can > hope for, realistically.    E Well, I'd give it at least 100 deg. because 90 deg. would be neutral. E So promising could be 110, 120, or even 130 deg.! At least we've made " it to the right half of the board!    J > As to Gartner in general, given their sources of funding, I consider any2 > info from Gartner to be highly suspect, at best.    ' Unless, of course, they complete a 180?    ------------------------------  % Date: Mon, 08 Aug 2005 14:15:03 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> D Subject: Re: how to get rid of "explicit carriage returns" in a file, Message-ID: <42F7A123.C6109D3A@teksavvy.com>  / Phillip Helbig---remove CLOTHES to reply wrote: H > longest < 80 bytes).  However, I see <CR> at the end of each line and,G > where there is supposed to be more than one line break, in addition a  > <CR> on a line by itself.    With TPU   [DO] replace <CR>  <CTRL-V> <CR> [ENTER]  [ENTER]  ALL   L eg: replace all CRs with nothing. (CTRL-V means next character is to be used as data and not executed).   ------------------------------  % Date: Mon, 08 Aug 2005 20:19:57 -0500 2 From: David J Dachtera <djesys.nospam@comcast.net>D Subject: Re: HP Pearl - HP Says Over 5,000 Applications on Integrity+ Message-ID: <42F804BD.A3869E63@comcast.net>    Tom Linden wrote:  > K > On Sun, 7 Aug 2005 15:45:39 -0400, Main, Kerry <Kerry.Main@hp.com> wrote:  > K > > While I would love to see Sybase back on OpenVMS, the fact is that from L > > an enterprise perspective, even with some of its latest features, SybaseK > > ASE is struggling against Oracle, SQL Server and the likes of MySQL and  > > other freeware DB's. > J > Well, I am aware of one wall street powerhouse that was lost as a result	 > therof.   $ Lost as a biz or lost as a VMS site?   --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/    Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------  # Date: Tue, 09 Aug 2005 00:14:38 GMT 1 From: Keith Parris <keithparris_NOSPAM@yahoo.com> D Subject: InformationWeek: Intel Says Itanium Chip Is Doing Just Fine3 Message-ID: <OzSJe.10044$wy2.8898@news.cpqcorp.net>   %  From InformationWeek, July 28, 2005: J http://www.informationweek.com/story/showArticle.jhtml?articleID=166403335 --- ; Despite Critics, Intel Says Itanium Chip Is Doing Just Fine   I Shipments of the Itanium 2 processor grew 170% from the first quarter of  " 2004 to the first quarter of 2005.    By Darrell Dunn, InformationWeek
 July 28, 2005   G The Itanium processor has been criticized over the past several years,  E and some computer makers that had offered Itanium-based servers have  G backed away from that market. But the high-end processor is doing just   fine, Intel said Thursday.  I Shipments of the Itanium 2 processor grew 170% from the first quarter of  H 2004 to the first quarter of 2005, according to the company, and now it I is generating more than a quarter of the revenue of the more-established  ! Power server architecture by IBM.   G Itanium 2 processors will occupy the top spot on Intel's new numbering  @ scheme also unveiled on Thursday -- the 9000 series. The server I architecture is currently being used by more than 40% of the 100 largest  C companies in the world, and nine of the top 10, says Kirk Skaugen,  2 general manager of Intel's server platforms group.  B Intel earlier this month introduced what it says will be the last D single-core upgrade to the Itanium 2 processor line, with dual-core  versions expected next year. ...    ------------------------------  # Date: Tue, 09 Aug 2005 01:28:50 GMT ( From: Alan Greig <greigaln@netscape.net>H Subject: Re: InformationWeek: Intel Says Itanium Chip Is Doing Just Fine= Message-ID: <mFTJe.37382$ia4.12096@fe1.news.blueyonder.co.uk>    Keith Parris wrote:   ' >  From InformationWeek, July 28, 2005: L > http://www.informationweek.com/story/showArticle.jhtml?articleID=166403335 > --- = > Despite Critics, Intel Says Itanium Chip Is Doing Just Fine   H Despite critics Compaq say Alpha is doing just fine seems familiar from H   the not too distant past. Hey there was even a time I almost believed  them.   K > Shipments of the Itanium 2 processor grew 170% from the first quarter of  $ > 2004 to the first quarter of 2005.  D Shipments of AMD-64 were up far more than that over the same period.  D > Intel earlier this month introduced what it says will be the last F > single-core upgrade to the Itanium 2 processor line, with dual-core  > versions expected next year.  % A year behind AMDs dual core support.      --  
 Alan Greig   ------------------------------  % Date: Tue, 09 Aug 2005 01:29:01 -0400 ( From: Bill Todd <billtodd@metrocast.net>H Subject: Re: InformationWeek: Intel Says Itanium Chip Is Doing Just FineR Message-ID: <OLednZ2dnZ2I9jqMnZ2dnb2iZd-dnZ2dRVn-y52dnZ0@metrocastcablevision.com>   Alan Greig wrote:  >  >  > Keith Parris wrote:    ...   I >> Shipments of the Itanium 2 processor grew 170% from the first quarter  ( >> of 2004 to the first quarter of 2005. >  > F > Shipments of AMD-64 were up far more than that over the same period.  F And without having had to depend upon captive markets like HP-UX (and @ now VMS as well) which had no real alternative, their preferred 8 processor families having been shot out from under them.  D As long as HP's Itanic sales (and one might reasonably suspect that F they're mostly HP-UX, plus now some VMS, sales) constitute the *vast* H preponderance of all Itanic sales (which of course they do today:  only F SGI makes other Itanic sales of any significance whatsoever, and they I are only a small fraction of HP's Itanic sales), the 'success' of Itanic  G won't reflect any particular intrinsic strength and can be expected to  H top out at the most at about what combined PA-RISC and Alpha sales used H to be (though quite possibly significantly lower, since people like the F Tru64 and MPE crowds were completely abandoned and quite a few of the B HP-UX and VMS people just aren't interested in such an 'upgrade').  E But until Intel officially scuttles the boat, you can expect them to  * continue to wax proud over its wallowings.   - bill   ------------------------------   Date: 8 Aug 2005 14:06:42 -0700 ! From: susan_skonetski@hotmail.com  Subject: Is it Possible?C Message-ID: <1123531713.872189.216190@g49g2000cwa.googlegroups.com>    Dear Newsgroup Folks,    Is the following possible?  G When folks raise a fixable problem that they also post when the problem  has been fixed.   # In my opinion this does two things.   G 1. It stops the person that raises the problem looking like all they do , is raise problems that never have solutions.  F 2. It stops me getting the same problem over and over again even after its been resolved.  E Everyone wants to help which is a great thing, but to have a bunch of 7 people going after the same problem is a waste of time.   A By the way I say fixable, something that we in engineering can do  something about.  
 Warm Regards,  Sue    ------------------------------  % Date: Mon, 08 Aug 2005 14:30:14 -0700 , From: Ken Fairfield <my.full.name@intel.com> Subject: Re: Is it Possible?+ Message-ID: <dd8it7$pu3$1@news01.intel.com>   " susan_skonetski@hotmail.com wrote: > Dear Newsgroup Folks,  >  > Is the following possible? > I > When folks raise a fixable problem that they also post when the problem  > has been fixed.   & This used to be called "netiquette"...  % > In my opinion this does two things.  > I > 1. It stops the person that raises the problem looking like all they do . > is raise problems that never have solutions. > H > 2. It stops me getting the same problem over and over again even after > its been resolved.  = And those points were the rationale, or at least, part of the > rationale.  Another was to save bandwidth (which we apparently don't care about anymore).  = IIRC, the suggestion used to be along the lines of, "Ask that A replies be sent directly to the original poster, with the promise , to "summarize" the responses for the group."  G > Everyone wants to help which is a great thing, but to have a bunch of 9 > people going after the same problem is a waste of time.  > C > By the way I say fixable, something that we in engineering can do  > something about.  " Thanks for everything you do, Sue!  
 	Regards, Ken  --  6 I don't speak for Intel, Intel doesn't speak for me...  
 Ken Fairfield ! D1C Automation VMS System Support " who:   kenneth dot h dot fairfield where: intel dot com   ------------------------------  % Date: Mon, 08 Aug 2005 14:09:55 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> @ Subject: Re: Killing a process that has allocated the tape drive, Message-ID: <42F79FF0.A406B64E@teksavvy.com>   Richard Maher wrote:L > The "software" always has the option of CANCELing any pending I/O when theN > user process is being run down. The fact that it chooses not to do so may be > for good reasons.   N I had read somewhere that not all drivers support the cancel IO operation  and( that the tape driver was one such beast.  M Personally, I think that the tape driver is something VMS engineers should be M ashamed of.  When you say that a tape problem may require a reboot, it brings & VMS down to the same level as Windows.  N So, the driver cancels the Pending IO and remembers that the tape unit is in aH state of limbo because it may still be performing some operation such asN seeking end of tape or rewinding. When the tape unit completes its opration itM sends something to the driver which then does nothing with it. Next person to K access the tape unit , the driver remembers the "state of limbo" and does a ( reset on the unit and asks for a rewind.  & I don't see why that couldn't be done.   ------------------------------  % Date: Mon, 08 Aug 2005 14:20:22 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> @ Subject: Re: Killing a process that has allocated the tape drive, Message-ID: <42F7A262.35F52B89@teksavvy.com>   Bob Koehler wrote:C >    I've seen device drivers without a properly implemented cancel F >    routine (yes, this is also "software").  I've seen hardware whichG >    would not cooperate (no interface to cancel a DMA once requested).     N Is it the hardware which deposits stuff in a specific physical memory location8 that currently belongs to a use process, or the driver ?  I If it is the hardware, then all VMS hardware tape drives should have been L designed with the ability of the driver to cancel the hardware's operation.   L Couldn't the driver simply ZAP the DMA location in the hardware so that whenL the hardware completes its operation, the whatecer data is written to a safe6 system buffer zone instead of the user process space ?   ------------------------------  % Date: Mon, 08 Aug 2005 20:10:40 -0000 1 From: wspencer@ap.dontspamme.org (Warren Spencer) @ Subject: Re: Killing a process that has allocated the tape drive1 Message-ID: <96ACABF1Cwspenceraporg@216.168.3.30>   1 matakan@inteltek.com.tr (MUSTAFA ATAKAN) wrote in B <F014DACB8BE63442993543B780A2F018014A62DC@asteriks.inteltek.ist>:    >Hi, > G >  I have a problem in killing a process that has already allocated the H >tape drive (that is, the system user mounted the tape drive, but closedH >the session without deallocating the drive). I want to the kill processF >since I want to mount the tape drive (as a system user, of course) in( >another telnet session. In other words: >   F I've had luck in the past just by cycling the power on the tape drive.   ws   --   Warren Spencer Senior Software Engineer The Associated Press   ------------------------------  # Date: Mon, 08 Aug 2005 20:14:58 GMT ( From: Alan Greig <greigaln@netscape.net>@ Subject: Re: Killing a process that has allocated the tape drive= Message-ID: <63PJe.39351$FG3.38977@fe3.news.blueyonder.co.uk>    JF Mezei wrote:  > Richard Maher wrote: > L >>The "software" always has the option of CANCELing any pending I/O when theN >>user process is being run down. The fact that it chooses not to do so may be >>for good reasons.  >  > P > I had read somewhere that not all drivers support the cancel IO operation  and* > that the tape driver was one such beast. > O > Personally, I think that the tape driver is something VMS engineers should be O > ashamed of.  When you say that a tape problem may require a reboot, it brings ( > VMS down to the same level as Windows.  F The days when DEC made the O/S, the tape drive, designed the hardware G interfaces, wrote all the drivers fromn scratch etc are long gone. But  I the tape hang problem in my experience happens far more often with third  H party non-qualified drives. You cannot really blame VMS engineering for  this.   F As for Windows XP - lets look at the CD/DVD writer support as I don't E have a tape drive hooked up. My experience is that Windows XP almost  G always allows a process wedged accessing the drive to be killed. It is  F my subjective experience that the likelyhood of an XP crash some time B downstream appears significantly greater after such a forced kill.   --  
 Alan Greig   ------------------------------   Date: 8 Aug 2005 16:18:25 -0500 ; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) @ Subject: Re: Killing a process that has allocated the tape drive3 Message-ID: <sCCia7YWN6B$@eisner.encompasserve.org>   \ In article <42F79FF0.A406B64E@teksavvy.com>, JF Mezei <jfmezei.spamnot@teksavvy.com> writes: > O > Personally, I think that the tape driver is something VMS engineers should be O > ashamed of.  When you say that a tape problem may require a reboot, it brings ( > VMS down to the same level as Windows.  C    I think the cancel I/O could use a better estimate of the proper A    timeout, and if the hardware is appropriate the cancel routine E    might be able to differentiate between a seek and a data transfer, 8    but other than that you're barking up the wrong tree.  P > So, the driver cancels the Pending IO and remembers that the tape unit is in aJ > state of limbo because it may still be performing some operation such asP > seeking end of tape or rewinding. When the tape unit completes its opration itA > sends something to the driver which then does nothing with it.    E    The tape unit doesn't sent data to the driver.  Tape I/O is direct B    I/O which means it maps directly to the hardware address of theE    application's buffer.  The easiest way to keep track of the simple H    fact that that physical page cannot be used by anyone else is to keepD    the process around until the I/O completes.  This happens all theB    time and since most I/O complete in milliseconds no one notices)    the delay in running down the process.   E    The problem is not being able to tell the tape unit to shut up and E    go away, a hardware design issue that the software must live with.   A    Changing the tape I/O to buffered I/O would cause unacceptable     performance.    ------------------------------   Date: 8 Aug 2005 16:20:52 -0500 ; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) @ Subject: Re: Killing a process that has allocated the tape drive3 Message-ID: <P+KWWELnRv70@eisner.encompasserve.org>   e In article <96ACABF1Cwspenceraporg@216.168.3.30>, wspencer@ap.dontspamme.org (Warren Spencer) writes:  > H > I've had luck in the past just by cycling the power on the tape drive.  D    I've had luck in the past just by going to lunch.  The timeout is    about 20 minutes.   ------------------------------   Date: 8 Aug 2005 16:20:15 -0500 ; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) @ Subject: Re: Killing a process that has allocated the tape drive3 Message-ID: <baTt5Pc0insd@eisner.encompasserve.org>   \ In article <42F7A262.35F52B89@teksavvy.com>, JF Mezei <jfmezei.spamnot@teksavvy.com> writes: > Bob Koehler wrote:D >>    I've seen device drivers without a properly implemented cancelG >>    routine (yes, this is also "software").  I've seen hardware which H >>    would not cooperate (no interface to cancel a DMA once requested). >  > P > Is it the hardware which deposits stuff in a specific physical memory location: > that currently belongs to a use process, or the driver ?  ;    The hardware.  Tape I/O is direct I/O, not buffered I/O.   K > If it is the hardware, then all VMS hardware tape drives should have been N > designed with the ability of the driver to cancel the hardware's operation.   >    You want cheap reliable DLTs, you buy what's on the market.  N > Couldn't the driver simply ZAP the DMA location in the hardware so that whenN > the hardware completes its operation, the whatecer data is written to a safe8 > system buffer zone instead of the user process space ?  G    For some hardware yes, but for most hardware no.  Most hardware will G    not respond predictably to modifying a DMA address after the DMA has     been started.   ------------------------------  # Date: Tue, 09 Aug 2005 00:35:50 GMT 1 From: Keith Parris <keithparris_NOSPAM@yahoo.com> ? Subject: Mark Hurd to be keynote speaker at HP Technology Forum 1 Message-ID: <GTSJe.10046$SA2.63@news.cpqcorp.net>   D HP Technology Forum 2005 to Feature Keynote Address by CEO Mark Hurd9 http://www.hp.com/hpinfo/newsroom/press/2005/050808a.html    PALO ALTO, Calif., Aug. 8, 2005 D --------------------------------------------------------------------E HP today announced that Mark Hurd, the company's president and chief  D executive officer, will be the featured keynote speaker at HP's new A signature technical training event, the HP Technology Forum 2005.   G Hurd, who joined HP in April after previously serving as president and  G chief executive officer at NCR Corp., will address the forum attendees  G on the first day of the event, which will be held Sept. 12 - 15 in the  ( Morial Convention Center in New Orleans. ... I More information on the HP Technology Forum 2005, including registration  8 forms, is available at http://www.hptechnologyforum.com. ...    ------------------------------  % Date: Mon, 08 Aug 2005 20:37:14 -0500 2 From: David J Dachtera <djesys.nospam@comcast.net>C Subject: Re: Mark Hurd to be keynote speaker at HP Technology Forum + Message-ID: <42F808CA.E25B9BEF@comcast.net>    Keith Parris wrote:  > F > HP Technology Forum 2005 to Feature Keynote Address by CEO Mark Hurd; > http://www.hp.com/hpinfo/newsroom/press/2005/050808a.html  > ! > PALO ALTO, Calif., Aug. 8, 2005 F > --------------------------------------------------------------------F > HP today announced that Mark Hurd, the company's president and chiefE > executive officer, will be the featured keynote speaker at HP's new C > signature technical training event, the HP Technology Forum 2005.  > H > Hurd, who joined HP in April after previously serving as president andH > chief executive officer at NCR Corp., will address the forum attendeesH > on the first day of the event, which will be held Sept. 12 - 15 in the* > Morial Convention Center in New Orleans. > ... J > More information on the HP Technology Forum 2005, including registration: > forms, is available at http://www.hptechnologyforum.com. > ...   F Well, that would be truly excellent, if he were planning to take "openB mike" questions. Of course, he'd have to be willing to face "toughC questions", give honest and frank answers, be willing to admit past F mistakes of both HP and its predecessors in the OpenVMS market, and beF willing to make on-the-spot "tough decisions" about HP will do to undoB at some of the extensive, nearly fatal damage that was done to theC OpenVMS market and a fair number (at least six figures) of business  relationships.    E That'd put him head-and-shoulders above any other CEO in the country.   - ...which makes it highly unlikely, I suppose.    --   David J Dachtera dba DJE Systems  http://www.djesys.com/  ) Unofficial OpenVMS Hobbyist Support Page: " http://www.djesys.com/vms/support/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/   " Unofficial OpenVMS-IA32 Home Page: http://www.djesys.com/vms/ia32/    Coming soon:& Unofficial OpenVMS Marketing Home Page   ------------------------------  * Date: Mon, 8 Aug 2005 17:55:40 +0000 (UTC)P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply) Subject: Re: PERL $ Message-ID: <dd86as$s6b$1@online.de>  F In article <890539d905080810135acd3ba0@mail.gmail.com>, Carl Friedberg  <frida.fried@gmail.com> writes:   - > The distributed version of perl (now 5.8.7)  > ) > http://www.perl.com/download.csp#stable  > H > You will, however, need a C compiler, a make tool (MMK), GZIP for VMS,I > and TAR for VMS, all but C available on the freeware cdroms (as is Perl  > itself, I suspect)  % I have all these utilities installed.   H > http://h71000.www7.hp.com/freeware/freeware70/perl/freeware_readme.txt >  > You can find readme.vms here:  > 0 > http://perl.active-venture.com/README.vms.html > I > Direct specific questions to the VMS Perl mailing list vmsperl@perl.org    Thanks.    ------------------------------  $ Date: Mon, 8 Aug 2005 15:51:27 -0400' From: "Main, Kerry" <Kerry.Main@hp.com>  Subject: RE: PERL R Message-ID: <FD827B33AB0D9C4E92EACEEFEE2BA2FB6B1C51@tayexc19.americas.cpqcorp.net>   > -----Original Message-----3 > From: Phillip Helbig---remove CLOTHES to reply=20 - > [mailto:helbig@astro.multiCLOTHESvax.de]=20  > Sent: August 8, 2005 12:19 PM  > To: Info-VAX@Mvb.Saic.Com  > Subject: PERL  >=20H > What is the best source for PERL for VMS?  I would prefer a version=20B > which just works out of the box and, of course, is compatible=20 > with PERL=20= > on other systems.  However, it should work fine with ODS-2.  >=20 > Is there a VMS PERL for VAX? >=20 >=20   Phillip,  @ Not sure what other resources are also available, but check out:  G http://h71000.www7.hp.com/openvms/products/ips/apache/csws_modperl.html  http://www.sidhe.org/vmsperl/    Regards   
 Kerry Main Senior Consultant  HP Services Canada Voice: 613-592-4660  Fax: 613-591-4477  kerryDOTmainAThpDOTcom (remove the DOT's and AT)=20  4 OpenVMS - the secure, multi-site OS that just works.   ------------------------------  * Date: Mon, 8 Aug 2005 17:57:18 +0000 (UTC)P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)4 Subject: Re: strange terminal-characteristic problem$ Message-ID: <dd86dt$s6b$2@online.de>  C In article <1123518829.600891.114830@o13g2000cwo.googlegroups.com>, & "WhoDat?" <whohe@whoever.com> writes:   G > Are all of your system's consoles (OPA0:'s) set to 300 or is this the  > only one set to 300?  8 All of them (at least, that is what SHOW TERMINAL says).  C > >From everything you've said, the problem is in the software or a F > setting, not the hardware. You said the problem followed the "disk",E > but really, it followed the software, no? You've changed everything ? > except the operating system and setting files. I think you've % > eliminated the hardware, don't you?    I agree.  I > Compare your sylogin and your user login files to the system that works  > and see what's different.   D They are the same.  Not just identical, but the same physical file,  located off the system disk.  ( > How about patches? Are all of your 7.3# > systems at the same patch level?     Yes.   ------------------------------   Date: 8 Aug 2005 12:10:21 -0700 # From: "WhoDat?" <whohe@whoever.com> 4 Subject: Re: strange terminal-characteristic problemC Message-ID: <1123528221.157158.163360@f14g2000cwb.googlegroups.com>   / Phillip Helbig---remove CLOTHES to reply wrote: E > In article <1123518829.600891.114830@o13g2000cwo.googlegroups.com>, ' > "WhoDat?" <whohe@whoever.com> writes:  > I > > Are all of your system's consoles (OPA0:'s) set to 300 or is this the  > > only one set to 300? > : > All of them (at least, that is what SHOW TERMINAL says).    C As (I think it was) JF said, SHOW TERM doesn't really show what the E console settings are. Some MicroVaxen are hard-wired for 9600 baud, 8 F bits and no parity. Some (like the "Mighty MicroVAX II") have a switchG in the back to set the speed. The console *must* be in a known state so 2 the system can communicate with it before booting.   > E > > >From everything you've said, the problem is in the software or a H > > setting, not the hardware. You said the problem followed the "disk",G > > but really, it followed the software, no? You've changed everything A > > except the operating system and setting files. I think you've ' > > eliminated the hardware, don't you?  > 
 > I agree. > K > > Compare your sylogin and your user login files to the system that works  > > and see what's different.  > E > They are the same.  Not just identical, but the same physical file,  > located off the system disk. > * > > How about patches? Are all of your 7.3$ > > systems at the same patch level? >  > Yes.  ? I still think the best bet is a conditional SET TERM someplace. G SYLOGIN.COM is usually located on the system disk in SYS$MANAGER and is B pointed to by SYS$SYLOGIN. That file usually has a conditional setA term. The fact that your SET HOST makes the terminal act properly @ re-enforces the suspicion because that logon would probably do a different SET TERM. Maybe doing   " $ SEARCH disk[000000...]*.COM OPA0  ? would reveal something. The one thing you know for sure is that F *something* on the "problem" system disk is different from your othersC because you've changed all of the hardware (and firmware) and still  have the problem.    ------------------------------  * Date: Mon, 8 Aug 2005 20:22:25 +0000 (UTC)P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)4 Subject: Re: strange terminal-characteristic problem$ Message-ID: <dd8eu1$bi5$1@online.de>  C In article <1123528221.157158.163360@f14g2000cwb.googlegroups.com>, & "WhoDat?" <whohe@whoever.com> writes:   1 > Phillip Helbig---remove CLOTHES to reply wrote: G > > In article <1123518829.600891.114830@o13g2000cwo.googlegroups.com>, ) > > "WhoDat?" <whohe@whoever.com> writes:  > > K > > > Are all of your system's consoles (OPA0:'s) set to 300 or is this the  > > > only one set to 300? > > < > > All of them (at least, that is what SHOW TERMINAL says). > E > As (I think it was) JF said, SHOW TERM doesn't really show what the G > console settings are. Some MicroVaxen are hard-wired for 9600 baud, 8 H > bits and no parity. Some (like the "Mighty MicroVAX II") have a switchI > in the back to set the speed. The console *must* be in a known state so 4 > the system can communicate with it before booting.  H Right.  I don't think that this is the case with the VAXstation, though.G I think it just wants the VT to be set up properly (8 bits, no parity,  $ one stop bit, receive=transmit etc).  A > I still think the best bet is a conditional SET TERM someplace. I > SYLOGIN.COM is usually located on the system disk in SYS$MANAGER and is D > pointed to by SYS$SYLOGIN. That file usually has a conditional setC > term. The fact that your SET HOST makes the terminal act properly B > re-enforces the suspicion because that logon would probably do a > different SET TERM.    SYSMAN> do sh log sys$sylogin 2 %SYSMAN-I-OUTPUT, command execution on node GLADIAC    "SYS$SYLOGIN" = "CLUSTER_MANAGER:SYLOGIN.COM" (LNM$SYSTEM_TABLE) 2 %SYSMAN-I-OUTPUT, command execution on node DANEELC    "SYS$SYLOGIN" = "CLUSTER_MANAGER:SYLOGIN.COM" (LNM$SYSTEM_TABLE) 2 %SYSMAN-I-OUTPUT, command execution on node ELIJAHC    "SYS$SYLOGIN" = "CLUSTER_MANAGER:SYLOGIN.COM" (LNM$SYSTEM_TABLE) ! SYSMAN> do sh log cluster_manager 2 %SYSMAN-I-OUTPUT, command execution on node GLADIAF    "CLUSTER_MANAGER" = "DISK$USER:[SYSTEM.MANAGER]" (LNM$SYSTEM_TABLE)2 %SYSMAN-I-OUTPUT, command execution on node DANEELF    "CLUSTER_MANAGER" = "DISK$USER:[SYSTEM.MANAGER]" (LNM$SYSTEM_TABLE)2 %SYSMAN-I-OUTPUT, command execution on node ELIJAHF    "CLUSTER_MANAGER" = "DISK$USER:[SYSTEM.MANAGER]" (LNM$SYSTEM_TABLE) SYSMAN> do sh log disk$user 2 %SYSMAN-I-OUTPUT, command execution on node GLADIA-    "DISK$USER" = "DSA510:" (LNM$SYSTEM_TABLE) 2 %SYSMAN-I-OUTPUT, command execution on node DANEEL-    "DISK$USER" = "DSA510:" (LNM$SYSTEM_TABLE) 2 %SYSMAN-I-OUTPUT, command execution on node ELIJAH-    "DISK$USER" = "DSA510:" (LNM$SYSTEM_TABLE)   
 > Maybe doing  > $ > $ SEARCH disk[000000...]*.COM OPA0 >  > would reveal something.   , This produces a few hundred lines of output.  D SYSMAN> do search sys$sysdevice:[*...]*.com opa0,set,term/match=and  reveals nothing interesting.  ) > The one thing you know for sure is that H > *something* on the "problem" system disk is different from your othersE > because you've changed all of the hardware (and firmware) and still  > have the problem.   C Note that I replaced the hardware with similar hardware.  Maybe the C hard-wired settings on the VAXstation 4000 and VAX 4000 models are  
 different.   ------------------------------  % Date: Mon, 08 Aug 2005 17:45:02 -0400 ' From: Dave Froble <davef@tsoft-inc.com> 4 Subject: Re: strange terminal-characteristic problem0 Message-ID: <11ffkb3jtrtr3ff@corp.supernews.com>  / Phillip Helbig---remove CLOTHES to reply wrote:   J > The one with the printer symbol is the console port, OPA0:, and that is G > what I am using.  The other one, with the double arrows, is a serial  H > port, but not the console port.  It works fine (no scrambling either).  I Ok, I haven't gone out to check my VAXstation 4000 systems yet, but, I'm  G pretty sure the MMJ port is the console port, and the DB25 port is the   printer/serial port.  > Just to confirm, are you using the MMJ port, or the DB25 port?   --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com 170 Grimplin Road  Vanderbilt, PA  15486    ------------------------------   Date: 8 Aug 2005 14:44:40 -0700 # From: "WhoDat?" <whohe@whoever.com> 4 Subject: Re: strange terminal-characteristic problemC Message-ID: <1123537480.822530.182790@g14g2000cwa.googlegroups.com>   / Phillip Helbig---remove CLOTHES to reply wrote: E > In article <1123528221.157158.163360@f14g2000cwb.googlegroups.com>, ' > "WhoDat?" <whohe@whoever.com> writes:  > 3 > > Phillip Helbig---remove CLOTHES to reply wrote: I > > > In article <1123518829.600891.114830@o13g2000cwo.googlegroups.com>, + > > > "WhoDat?" <whohe@whoever.com> writes:  > > > M > > > > Are all of your system's consoles (OPA0:'s) set to 300 or is this the  > > > > only one set to 300? > > > > > > > All of them (at least, that is what SHOW TERMINAL says). > > G > > As (I think it was) JF said, SHOW TERM doesn't really show what the I > > console settings are. Some MicroVaxen are hard-wired for 9600 baud, 8 J > > bits and no parity. Some (like the "Mighty MicroVAX II") have a switchK > > in the back to set the speed. The console *must* be in a known state so 6 > > the system can communicate with it before booting. > J > Right.  I don't think that this is the case with the VAXstation, though.H > I think it just wants the VT to be set up properly (8 bits, no parity,& > one stop bit, receive=transmit etc). >   E Unless the VAXstatsion serial console does an autobaud (I don't know) @ then the speed must be *known* to the system, too, before it can3 communicate. But, that doesn't seem to be relevant.     C > > I still think the best bet is a conditional SET TERM someplace. K > > SYLOGIN.COM is usually located on the system disk in SYS$MANAGER and is F > > pointed to by SYS$SYLOGIN. That file usually has a conditional setE > > term. The fact that your SET HOST makes the terminal act properly D > > re-enforces the suspicion because that logon would probably do a > > different SET TERM.  >  > SYSMAN> do sh log sys$sylogin 4 > %SYSMAN-I-OUTPUT, command execution on node GLADIAE >    "SYS$SYLOGIN" = "CLUSTER_MANAGER:SYLOGIN.COM" (LNM$SYSTEM_TABLE)    <snip: okay>   > > Maybe doing  > > & > > $ SEARCH disk[000000...]*.COM OPA0 > >  > > would reveal something.  > . > This produces a few hundred lines of output. >   G That's not too bad. Try searching for "IF",".","OPA0"/MAT=AND to narrow A it down. Also add /OUT=somefile for that disk, then the same on a C "working" disk. You could do a /window=0 to just get a list of file = names to eliminate the obvious, then a do quick edit of each.   D Does maybe your common SYS$SYLOGIN or users login refer to something back on the system disk?  E > SYSMAN> do search sys$sysdevice:[*...]*.com opa0,set,term/match=and  > reveals nothing interesting. >   F A conditional SET TERM probably wouldn't match those three because the9 "OPA0" would be on the IF line and not the SET TERM line.     + > > The one thing you know for sure is that J > > *something* on the "problem" system disk is different from your othersG > > because you've changed all of the hardware (and firmware) and still  > > have the problem.  > E > Note that I replaced the hardware with similar hardware.  Maybe the D > hard-wired settings on the VAXstation 4000 and VAX 4000 models are > different.  > I understood you to say that you booted the system disk from aG completely different box, terminal, cable and all, and you had the same  problem on both computers.  : If not, then I've misunderstood and I'm sorry I jumped in.  F If so, then I don't see how any hardware or firmware differences couldE be a factor. ?? It has to be something on the disk because that's the E only thing common to the problem -- unless you can think of something G else. I've had systems that I swear were possessed by evil spirits, but < they all ran microslop (or would the terms "evil spirit" and "microslop" be redundant?);-)    ------------------------------  * Date: Mon, 8 Aug 2005 22:18:45 +0000 (UTC)P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)4 Subject: Re: strange terminal-characteristic problem$ Message-ID: <dd8lo5$kop$1@online.de>  < In article <11ffkb3jtrtr3ff@corp.supernews.com>, Dave Froble <davef@tsoft-inc.com> writes:   1 > Phillip Helbig---remove CLOTHES to reply wrote:  > L > > The one with the printer symbol is the console port, OPA0:, and that is I > > what I am using.  The other one, with the double arrows, is a serial  J > > port, but not the console port.  It works fine (no scrambling either). > K > Ok, I haven't gone out to check my VAXstation 4000 systems yet, but, I'm  I > pretty sure the MMJ port is the console port, and the DB25 port is the   > printer/serial port.  G There are two MMJ ports, labeled with a printer (the console port, the  E one I am using) and with two arrows.  In addition, there is the DB25   port.   @ > Just to confirm, are you using the MMJ port, or the DB25 port?  D The MMJ with the printer symbol.  It is definitely the console port.   ------------------------------  * Date: Mon, 8 Aug 2005 22:22:00 +0000 (UTC)P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)4 Subject: Re: strange terminal-characteristic problem$ Message-ID: <dd8lu7$kop$2@online.de>  C In article <1123537480.822530.182790@g14g2000cwa.googlegroups.com>, & "WhoDat?" <whohe@whoever.com> writes:   G > > Note that I replaced the hardware with similar hardware.  Maybe the F > > hard-wired settings on the VAXstation 4000 and VAX 4000 models are > > different. > @ > I understood you to say that you booted the system disk from aI > completely different box, terminal, cable and all, and you had the same  > problem on both computers.  A I had disk + cable + VT + computer for both nodes.  I swapped the H cables, swapped the VTs.  The problem remained with the "node".  I then G replaced each computer with another one BUT OF SIMILAR HARDWARE  (i.e.  E VAXstation with VAXstation, VAX with VAX) and found that the problem   stayed with the system disk.   ------------------------------  % Date: Mon, 08 Aug 2005 20:38:36 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> 4 Subject: Re: strange terminal-characteristic problem, Message-ID: <42F7FB0B.98A324DD@teksavvy.com>  5 Have you tried SET TERM/NOEIGHTBIT/HOSTSYNC/TTSYNC  ?   K Maybe VMS thinks the terminal is capable of 8 bits, but the hardware serial L port isn't for that model. /NOEOIGHTBUIT tells VMS that the terminal isn'T 8Y bit escape sequence capable and applications such as TPU then use 7 bit escape sequences.    ------------------------------   Date: 8 Aug 2005 15:45:56 -0700  From: contracer11@gmail.com  Subject: Vax/VMS Calculator C Message-ID: <1123541156.398134.108890@g43g2000cwa.googlegroups.com>   @ Please, can you tell me where could I get a graphical calculator" to download in my VAX and use it ? Thanks.    ------------------------------  $ Date: Mon, 8 Aug 2005 20:02:21 -0400- From: William Webb <william.w.webb@gmail.com>  Subject: Re: Vax/VMS Calculator 7 Message-ID: <8660a3a105080817025874029d@mail.gmail.com>   3 On 8 Aug 2005 15:45:56 -0700, contracer11@gmail.com  <contracer11@gmail.com> wrote:B > Please, can you tell me where could I get a graphical calculator$ > to download in my VAX and use it ?	 > Thanks.  >=20 >=20   VAX?=20   
 Graphical?  
 I'm confused.    WWWebb   --=20 C NOTE: This email address is only used for noncommerical VMS-related  correspondence. C All unsolicited commercial email will be deemed to be a request for 8 services pursuant to the terms and conditions located at# http://bellsouthpwp.net/w/e/webbww/    ------------------------------  # Date: Tue, 09 Aug 2005 00:41:59 GMT 1 From: Keith Parris <keithparris_NOSPAM@yahoo.com>  Subject: Re: Vax/VMS Calculator 3 Message-ID: <rZSJe.10047$ZD2.1858@news.cpqcorp.net>    contracer11@gmail.com wrote:B > Please, can you tell me where could I get a graphical calculator$ > to download in my VAX and use it ?  L There is one included with DECwindows. So you probably want to fire that up.   ------------------------------  % Date: Mon, 08 Aug 2005 20:45:41 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com>  Subject: Re: Vax/VMS Calculator , Message-ID: <42F7FCB3.CCB563C4@teksavvy.com>   contracer11@gmail.com wrote: > B > Please, can you tell me where could I get a graphical calculator$ > to download in my VAX and use it ?    @ There is a basic GUI/MOTIF calculator that comes with decwindowsL decw$calc.exe. It is very basic though. It is GUI, but not graphical (eg: it8 won't draw fancy graphs for you like the one on the mac)   ------------------------------   End of INFO-VAX 2005.441 ************************                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  