1 INFO-VAX	Thu, 22 Jun 2006	Volume 2006 : Issue 345       Contents:" Re: A sorry saga - ra3000 reloaded8 Re: how to turn off OPCOM messages on a console terminal8 Re: how to turn off OPCOM messages on a console terminal8 Re: how to turn off OPCOM messages on a console terminal8 Re: how to turn off OPCOM messages on a console terminal8 Re: how to turn off OPCOM messages on a console terminal RE: Hung System RWMBX state  Re: Hung System RWMBX state  Re: InfoServer 100 trouble) Re: New OpenVMS Virtualization Whitepaper ) Re: New OpenVMS Virtualization Whitepaper ) Re: New OpenVMS Virtualization Whitepaper 5 Re: OT: IA64's speed beaten by orders of magnitude... . Re: Setting up my NIC for Gb Ethernet traffic.  F ----------------------------------------------------------------------  % Date: Thu, 22 Jun 2006 12:09:22 +0100 0 From: Chris Sharman <chris.sharman@sorry.nospam>+ Subject: Re: A sorry saga - ra3000 reloaded ) Message-ID: <449A7A62.60309@sorry.nospam>    Tim Jackson wrote:@ > "Chris Sharman" <chris.sharman@sorry.nospam> wrote in message N >> But I think the problems are hardware/ra3000 config related, following its L >> being unplugged, as Tim Jackson suggested: that's presumably why when we K >> bought it, it arrived with its very own UPS, which we hadn't ordered or   >> expected. >>F >> When the ra3000 goes back in, it will be restored from the interim G >> internal disks, anyway - and I'm going to replace that damn battery.  > M > Your problems sound so familiar to me!  The only difference being that our  H > power problems were caused not by unplugging the power cables, but by O > accidental pushing of the RA3000 power button (near top right of the unit on  M > the front) by a misaligned front door panel edge just catching the button.  K > Took ages to find this.  Correction was by snipping some of the (excess)    > plastic away from the door! :)  H We've been running for nearly 4 weeks now on the interim disks, without J incident, with the offending ra3000 mounted readonly to recover odd files./ I'm now looking at moving back onto the ra3000.   1 You suggested "reinitialize the disks with SWCC". : How's that done ? Or is it enough to initialize from VMS ?H Or is it deletion and recreation (necessarily with the serial cable for  the first one).   I I'm reconfiguring the disks anyway, so I deleted the old virtual disks -  I when I deleted the last of them, SWCC lost contact with the array (which  0 is documented behaviour I should have expected).I I've got SWCC (HSZ22 folder) on a network disk (lost the original dist'n  C kit), and it works fine on my pc. It doesn't run right on a laptop  I though - it initially complained that it needed SNMP, which I installed,  C then it complained that there was "an error", and left me an empty   applet window.A I managed to access the array via hyperterm ("<esc> &" to start,  C password decraid), and even created an initial disk, but it wasn't   configured quite right. D I eventually lugged my pc down to the server room, and connected it G directly to the ra3000, and configured it all that way - but it leaves  C me a little nervous for the future that I'm unable to successfully  < install a working SWCC on another laptop - anyone know how ?  I Oh, and for anyone who wants to know (since it's not documented anywhere  G I've found): the correct serial cable for the RA3000 is 9 pin straight  & (ie 1-1, 2-2, ..., 9-9) female-female.  E For anyone else with a powerfailed ra3000 - we lost a week - I've no  H reason to doubt Tim Jackson's recommendation to cut losses early with a $ re-initialize and restore from tape.   Chris    ------------------------------  + Date: Thu, 22 Jun 2006 06:05:03 +0000 (UTC) P From: helbig@astro.multiCLOTHESvax.de (Phillip Helbig---remove CLOTHES to reply)A Subject: Re: how to turn off OPCOM messages on a console terminal $ Message-ID: <e7dbuf$5qb$1@online.de>  5 In article <4499B426.42F9F045@teksavvy.com>, JF Mezei ' <jfmezei.spamnot@teksavvy.com> writes:     > Hoff Hoffman wrote: L > >    The OPCOM mechanisms discussed in SYLOGICALS provide more flexibilityD > > than does the "bigger hammer" that is the REPLY command, as (forF > > instance) you could choose to display specific subset of the OPCOMA > > messages displayed at the console using SYLOGICALS mechanism.  >  > I > Instead of pointing you to the FAQ , I'll point you to another document  > that is often mentioned: > 
 > 	$HELP  :-)  >  > J > HELP REPLY shows that you can disable specific classes of opcom messages+ > just like the logical schemes in SYLOGIN.  >  > aka REPLY/DISABLE=SECURITY  I Yes, of course, but the interesting thing here is that no-one was logged  + in at the terminal where the messages were.    ------------------------------  % Date: Thu, 22 Jun 2006 02:10:37 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> A Subject: Re: how to turn off OPCOM messages on a console terminal , Message-ID: <449A3432.BBACFCEB@teksavvy.com>  / Phillip Helbig---remove CLOTHES to reply wrote: J > Yes, of course, but the interesting thing here is that no-one was logged- > in at the terminal where the messages were.   H REPLY/ENABLE/PERM makes the status of permanent for that terminal across9 sessions, even if some totally unprivileged user logs in.   L So if you want to disable it, you also need to do the /PERM for the /DISABLE   ------------------------------  # Date: Thu, 22 Jun 2006 14:23:16 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com>A Subject: Re: how to turn off OPCOM messages on a console terminal 2 Message-ID: <oJxmg.2163$BC6.1957@news.cpqcorp.net>  / Phillip Helbig---remove CLOTHES to reply wrote: 7 > In article <4499B426.42F9F045@teksavvy.com>, JF Mezei ) > <jfmezei.spamnot@teksavvy.com> writes:    K >> HELP REPLY shows that you can disable specific classes of opcom messages , >> just like the logical schemes in SYLOGIN.  F    SYLOGICALS, I expect was meant.  SYLOGIN comes into play only when ) somebody logs in on the specified device.    >> aka REPLY/DISABLE=SECURITY   F    Yep, that'll work.  And at its core, that path very similar to how D the SYLOGICALS OPCOM-control mechanisms basically work -- well, the B SYLOGICALS OPC$* logical names can and do inherently effect their G settings rather earlier in the OPCOM startup processing.  (I happen to  G use SYLOGICALS rather more commonly, too, as it is enabled before, for  E instance, a blizzard of OPCOM messages can scrozzle the display on a    DECwindows workstation console.)  K > Yes, of course, but the interesting thing here is that no-one was logged  - > in at the terminal where the messages were.   D    And SYLOGICALS allows an easy way to control the output as OPCOM I starts, and allows a way to control which messages go to the console and   which go to the OPERATOR.LOG.    ------------------------------  % Date: Thu, 22 Jun 2006 08:15:57 -0700 ( From: Jeff Cameron <roktsci@comcast.net>A Subject: Re: how to turn off OPCOM messages on a console terminal 0 Message-ID: <C0C0023D.22224%roktsci@comcast.net>  @ On 6/21/06 11:05 PM, in article e7dbuf$5qb$1@online.de, "PhillipJ Helbig---remove CLOTHES to reply" <helbig@astro.multiCLOTHESvax.de> wrote:  7 > In article <4499B426.42F9F045@teksavvy.com>, JF Mezei ( > <jfmezei.spamnot@teksavvy.com> writes: >  >> Hoff Hoffman wrote:L >>>    The OPCOM mechanisms discussed in SYLOGICALS provide more flexibilityD >>> than does the "bigger hammer" that is the REPLY command, as (forF >>> instance) you could choose to display specific subset of the OPCOMA >>> messages displayed at the console using SYLOGICALS mechanism.  >>   >>  J >> Instead of pointing you to the FAQ , I'll point you to another document >> that is often mentioned:  >>  
 >> $HELP  :-)  >>   >>  K >> HELP REPLY shows that you can disable specific classes of opcom messages , >> just like the logical schemes in SYLOGIN. >>   >> aka REPLY/DISABLE=SECURITY  > J > Yes, of course, but the interesting thing here is that no-one was logged- > in at the terminal where the messages were.  > J Any terminal may have OPCOM enabled without a user being logged in. I onceK had a VAXStation 3100 at my desk which was a member of an 8 node cluster. I L configured its serial port connected to a printer to print out only Security related messages.   K Hoff's suggestion is the best. For your OPCOM on the console, using the OPC ; logical names are the best suggestion and is most flexible.    ------------------------------  % Date: Thu, 22 Jun 2006 12:09:08 -0400  From: norm.raphael@metso.comA Subject: Re: how to turn off OPCOM messages on a console terminal Q Message-ID: <OF2D1DC406.EB9ED9AF-ON85257195.005725CE-85257195.0058BA49@metso.com>   J Can I get "REPLY/TO" messages to go to the operator.log file only, but not hang.    Here's an excerpt: [start] F %%%%%%%%%%%  OPCOM  11-JUN-2006 09:18:22.46  %%%%%%%%%%%    (from node	 NODE1  at   11-JUN-2006 09:18:22.46) & Request 3798, from user USERx on NODE1. CSTI006O APPLID, Reply with an APPLID command.   ***************   F %%%%%%%%%%%  OPCOM  11-JUN-2006 09:23:47.91  %%%%%%%%%%%    (from node	 NODEA  at   11-JUN-2006 09:23:47.92)  Request 3798 was canceled  [end]   H The app puts out this every 5 minutes and apparently the new one cancels! the prior one, but if no terminal A is REPLY/ENABLED the application eventually fills some buffer (or  something) and hangs.     C Jeff Cameron <roktsci@comcast.net> wrote on 06/22/2006 11:15:57 AM:   B > On 6/21/06 11:05 PM, in article e7dbuf$5qb$1@online.de, "PhillipE > Helbig---remove CLOTHES to reply" <helbig@astro.multiCLOTHESvax.de>  wrote: > 9 > > In article <4499B426.42F9F045@teksavvy.com>, JF Mezei * > > <jfmezei.spamnot@teksavvy.com> writes: > >  > >> Hoff Hoffman wrote:B > >>>    The OPCOM mechanisms discussed in SYLOGICALS provide more flexibility F > >>> than does the "bigger hammer" that is the REPLY command, as (forH > >>> instance) you could choose to display specific subset of the OPCOMC > >>> messages displayed at the console using SYLOGICALS mechanism.  > >> > >>C > >> Instead of pointing you to the FAQ , I'll point you to another  document > >> that is often mentioned:  > >> > >> $HELP  :-)  > >> > >>D > >> HELP REPLY shows that you can disable specific classes of opcom messages. > >> just like the logical schemes in SYLOGIN. > >> > >> aka REPLY/DISABLE=SECURITY  > > E > > Yes, of course, but the interesting thing here is that no-one was  logged/ > > in at the terminal where the messages were.  > > G > Any terminal may have OPCOM enabled without a user being logged in. I  onceK > had a VAXStation 3100 at my desk which was a member of an 8 node cluster.  I E > configured its serial port connected to a printer to print out only  Security > related messages.  > I > Hoff's suggestion is the best. For your OPCOM on the console, using the  OPC = > logical names are the best suggestion and is most flexible.  >    ------------------------------  % Date: Thu, 22 Jun 2006 08:25:24 -0400 1 From: "Farrell, Michael" <MFarrell@Voltdelta.com> $ Subject: RE: Hung System RWMBX stateL Message-ID: <085BCCCF596B684092B66310B1D3BA7D02CC732E@NJ103EX1.EAST.VIS.COM>  H Has anyone else tried this?  ANAL/SYS doesn't recognize this or anything like it.   -----Original Message-----7 From: JF Mezei [mailto:jfmezei.spamnot@teksavvy.com]=20 & Sent: Wednesday, June 21, 2006 4:47 PM To: Info-VAX@Mvb.Saic.Com $ Subject: Re: Hung System RWMBX state   Suggestion:     SDA> SHOW MAILBOX/STATUS=3DRWMBX  C This would scan through all processes in RWMBX status, and find out E which mailbox devices are causing the RWMBX status, and for each such E mailbox, would list all processes that have channels assigned to that G mailbox and whether their status is RMBBX because of an attempted write  to that mailbox.  D Obviously, if the server process doesn't have a read QIO issued, theG system won't be able to tell you which server process isn't reading the E messages from the mailbox, but you'd still see that server process as 2 having a channel assigned to that problem mailbox.  : (or perhaps this could be done outside of $ANA/SYSTEM with $ANA/MAILBOX/STATUS=3DRWMBX)   ------------------------------  # Date: Thu, 22 Jun 2006 14:28:48 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com>$ Subject: Re: Hung System RWMBX state1 Message-ID: <AOxmg.2164$lD6.371@news.cpqcorp.net>    Farrell, Michael wrote: J > Has anyone else tried this?  ANAL/SYS doesn't recognize this or anything
 > like it.  L    Um, I expect that was an enhancement suggestion -- not an actual command.   > -----Original Message-----7 > From: JF Mezei [mailto:jfmezei.spamnot@teksavvy.com]  ( > Sent: Wednesday, June 21, 2006 4:47 PM > To: Info-VAX@Mvb.Saic.Com & > Subject: Re: Hung System RWMBX state > 
 > Suggestion:  >   > SDA> SHOW MAILBOX/STATUS=RWMBX  F    Looked at modifying the existing MBX$SDA example?  If you hurried, B you might be able to get the changes submitted in before I finish  packaging the Freeware.    ------------------------------    Date: 22 Jun 2006 08:53:59 -0700 From: phil@rephil.org # Subject: Re: InfoServer 100 trouble C Message-ID: <1150991639.099292.270500@m73g2000cwd.googlegroups.com>    gl@decadence.it wrote:  . > unfortunately, I don't have the VAX CONDIST.. > I'm looking for the software on bootable CD.) > I'm sure I'll find in a way or another.   F If memory serves, it's on VMS Freeware, either v3, 4, or 5.  If not, I might be able to dig it up.    Cheers,  Phil M   ------------------------------    Date: 22 Jun 2006 01:02:22 -0700  From: "Ian Miller" <ijm@uk2.net>2 Subject: Re: New OpenVMS Virtualization WhitepaperB Message-ID: <1150963342.719944.51080@i40g2000cwc.googlegroups.com>  B It covers wonderful new abbreviations  such as the Global Workload1 Manager, HP VM, iCAP, TiCAP, GiCAP, PPU, and PCL.    ------------------------------    Date: 22 Jun 2006 03:38:13 -0700# From: "Galen" <gltackett@gmail.com> 2 Subject: Re: New OpenVMS Virtualization WhitepaperB Message-ID: <1150972693.200697.209810@r2g2000cwb.googlegroups.com>   Ian Miller wrote: D > It covers wonderful new abbreviations  such as the Global Workload3 > Manager, HP VM, iCAP, TiCAP, GiCAP, PPU, and PCL.    NAASMF!   * (That is, "New acronyms are so much fun!")   ------------------------------    Date: 22 Jun 2006 09:48:09 -0700- From: "Doug Phillips" <dphill46@netscape.net> 2 Subject: Re: New OpenVMS Virtualization WhitepaperB Message-ID: <1150994889.517780.76480@c74g2000cwc.googlegroups.com>   Galen wrote: > Ian Miller wrote: F > > It covers wonderful new abbreviations  such as the Global Workload5 > > Manager, HP VM, iCAP, TiCAP, GiCAP, PPU, and PCL.  > 	 > NAASMF!  > , > (That is, "New acronyms are so much fun!")    C Maybe I just got a lucky card, but I got a Bingo on the first page!   / < http://isd.usc.edu/~karl/Bingo/bbbingo.html >    ------------------------------  # Date: Thu, 22 Jun 2006 13:06:19 GMT F From: lederman@star.enet.dec.DISABLE-JUNK-EMAIL.com (Bart Z. Lederman)> Subject: Re: OT: IA64's speed beaten by orders of magnitude..., Message-ID: <fBwmg.33$Pv.73@news.oracle.com>  F >> IBM and Georgia tech have built a chip that runs at 350 Ghz. And byI >> dipping in in liquid helium at near 0 kelvin, they were able to boost  >> its speed to nearly 500 Ghz.  >>   > H >I noticed that they didn't say what kind of chip.  I doubt it was some : >Power CPU, right?  What was it?  Some silly JK flip-flop? > C >Making a "simple" chip run at 350Ghz isn't like making a Power or   >Itanium run at 350Ghz.     7 What has frequently been done in the past for this kind 7 of experiment, or proof that devices can run at a given < speed, is to construct something called a 'ring oscillator'.= Basically, it's several transistors hooked up in series, with > the output of the last one going to the input of the first one= (hence the "ring" designation).  You then let it run, and see ? how fast it oscillates.  This gives a simple direct measurement 5 of the switching speed of the individual transistors.   ? Yes, this is simpler than a complex logic circuit or a CPU, but = it's the first step in showing that the devices will reliably = operate at a given speed.  Testing devices intended for logic D switching is a little different that testing for analog applications$ like signal amplification (usually).   ------------------------------    Date: 21 Jun 2006 11:16:04 -0500. From: brooks@cuebid.zko.hp.nospam (Rob Brooks)7 Subject: Re: Setting up my NIC for Gb Ethernet traffic. , Message-ID: <a4VFbaEOiUJ5@cuebid.zko.hp.com>  $ dave.baxter@bannerhealth.com writes:  G > e.g. I noticed that there are some Console Environment variables that @ > appear to relate to NIC's, can anyone shed any light on those.  D As Colin correctly stated in an earlier reply, please set bit six inC the sysgen param LAN_FLAGS.  As that parameter is likely 0 now, the 0 value to which it should be set is 64 (decimal).  I You should set your ethernet card to auto-negotiate at the console level. O All modern LAN drivers supplied by VMS should correctly autonegotiate, assuming @ a correctly-behaving switch.  If it doesn't, please let us know!  F You should not need to set *anything* within LANCP to get jumbo frames working.   Please post the output of    SCACP> SHOW LAN   , once you've set LAN_FLAGS = 64 and rebooted.  @ Note that in VMS V8.3, $ SHOW DEVICE /FULL has been enhanced for LAN devices . . .    SISKO Alpha> sho dev/full ewb0  L Device EWB0:, device type DEGPA, is online, network device, error logging is'     enabled, device is a template only.   O     Error count                    1    Operations completed                  0 O     Owner process                 ""    Owner UIC                      [SYSTEM] O     Owner process ID        00000000    Dev Prot              S:RWPL,O:RWPL,G,W O     Reference count                0    Default buffer size                 512 O     Current preferred CPU Id       1    Fastpath                              1   O Operating characteristics: Link up, Full duplex, Autonegotiation, Jumbo frames.   $     Speed (Mbits/sec)           1000O     Def. MAC addr  00-60-6D-21-1E-DF    Current MAC addr      00-60-6D-21-1E-DF    --    H Rob Brooks    VMS Engineering -- Exec Group     brooks!cuebid.zko.hp.com   ------------------------------   End of INFO-VAX 2006.345 ************************