0 INFO-VAX	Mon, 27 Jan 2003	Volume 2003 : Issue 53      Contents:" Re: ALphaServer 2100A Disk Options, Re: AlphaServer 4100 Firmware update problem( AlphaServer 4100 Firmware update problem, Re: AlphaServer 4100 Firmware update problem Re: DECnet-Plus vs DECnet IV Re: DECnet-Plus vs DECnet IV Re: DECnet-Plus vs DECnet IV Re: DECnet-Plus vs DECnet IV Re: DECnet-Plus vs DECnet IV Re: DECnet-Plus vs DECnet IV Re: DECnet-Plus vs DECnet IV Re: dynamic DNS  RE: EV7, ES47 question RE: EV7, ES47 question RE: EV7, ES47 question RE: EV7, ES47 question Re: EV7, ES47 question# FA: OpenVMS 7.2, 7.2-1 Full Doc Set $ Re: Firesafes Was: How to Backup OSX$ Re: Firesafes Was: How to Backup OSX! Re: High hit rate VMS Web server? ! Re: High hit rate VMS Web server? $ Re: How to get Digital printer parts$ Re: How to get Digital printer parts$ Re: How to get Digital printer parts Re: Marvel Performance: Re: OT Battersea Power Station. Was Re: Marvel Performance Queue manager file size - fixed $ Re: Queue manager file size question$ RE: Queue manager file size question$ Re: Queue manager file size question  Raid failed apparently good disk$ Re: Raid failed apparently good disk$ Re: Raid failed apparently good disk@ Re: Storage network with VMS cluster and other OSses, ESS, EMC2? Re: VAX network monitor...  F ----------------------------------------------------------------------  % Date: Mon, 27 Jan 2003 07:57:47 +0100 6 From: =?ISO-8859-1?Q?Arne_Vajh=F8j?= <arne@vajhoej.dk>+ Subject: Re: ALphaServer 2100A Disk Options ) Message-ID: <3E34D86B.7070508@vajhoej.dk>    rob kas wrote:1  > I'm trying to keep our last VMS machine alive. F  > Does anyone know if the 9 Gig Disks will work in  AlphaServer 2100  InternalK  > RAID racks?   Failing that does anyone have a suggestion for adding Disk   > Space to this old girl.  = I know some 2100's with RAID and both 2, 4 and 9 GB disks in.    Arne   ------------------------------  % Date: Sun, 26 Jan 2003 14:31:49 -0500 3 From: "Homer J. Simpson" <hsimpson@burnsenergy.com> 5 Subject: Re: AlphaServer 4100 Firmware update problem 4 Message-ID: <erWY9.11127$2W.1719@news.bellsouth.net>  4 I see the EISA error; did you run the ECU to fix it?  G If you want to experiment, take out all the option cards and try again.     < "Clay M. Denton" <denton@orison.dsserv.com> wrote in message2 news:oh383v0aknuaqdav630pmfk562ek00m9t0@4ax.com...6 > Trying to update the firmware on an AlphaServer 4100 > System has 4 5/533 CPUs < > Is currently running 5.1 (yes - I know - ancient) firmware > D > V6.0 firmware (latest for 4100) instructions talk about the 2 step process - update SRMF > first, then AlphaBIOS.  I get a "FAILED" message every time I try to update.  > 6 > So, loaded an old 5.3 firmware disk - same failures. > G > Then, tried to reapply 5.1 disk - all default answers - failed again.  > L > Cannont find any information about the existence of a firmware/flash write protect jumper1 > or setting which would be causing me a problem.  > J > Did successfully update firmware on a FDDI controller in the same system
 from the same  > firmware disk. > J > Tried using the failsafe loader floppy - but that only seems to apply if the firmware is  > corrupt to start with. > @ > Any ideas?  I'm including a log of one of the update sessions. >  > Clay >  > Initializing...  >  >  SROM V3.0 on cpu0 >  SROM V3.0 on cpu2 >  SROM V3.0 on cpu1 >  SROM V3.0 on cpu3 > XSROM V5.1 on cpu2 > XSROM V5.1 on cpu1 > XSROM V5.1 on cpu0 > XSROM V5.1 on cpu3! > BCache testing complete on cpu0 ! > BCache testing complete on cpu1 ! > BCache testing complete on cpu2 ! > BCache testing complete on cpu3  > mem_pair0 - 128 MB& > 20..20..20..20..21..21..21..21..23..+ > please wait 3 seconds for T24 to complete  > 24..24..24..24..! > Memory testing complete on cpu3 ! > Memory testing complete on cpu2 ! > Memory testing complete on cpu1 ! > Memory testing complete on cpu0  > starting console on CPU 0  > sizing memory  >   0    128 MB SYNC > starting console on CPU 1  > starting console on CPU 2  > starting console on CPU 3  > probing IOD1 hose 1  >   bus 0 slot 1 - NCR 53C810 ! >   bus 0 slot 2 - QLogic ISP1020 # >   bus 0 slot 3 - DECchip 21140-AA # >   bus 0 slot 4 - DECchip 21140-AA  > probing IOD0 hose 0  >   bus 0 slot 1 - PCEB . > EISA Data in non-volatile storage is corrupt >  > EISA Configuration Error$ > Run the EISA Configuration Utility >   >     probing EISA Bridge, bus 1! >   bus 0 slot 2 - QLogic ISP1020 ! >   bus 0 slot 5 - QLogic ISP1020  > configuring I/O adapters...  >   ncr0, hose 1, bus 0, slot 1  >   isp0, hose 1, bus 0, slot 2 ! >   tulip0, hose 1, bus 0, slot 3 ! >   tulip1, hose 1, bus 0, slot 4 " >   floppy0, hose 0, bus 1, slot 0 >   isp1, hose 0, bus 0, slot 2  >   isp2, hose 0, bus 0, slot 5 $ > System temperature is 23 degrees C6 > AlphaServer 4100 Console V5.1-3, 4-FEB-1998 16:40:08 >  > CPU 0 booting  > " > (boot dka500.5.0.1.1 -flags 0,0)1 > block 0 of dka500.5.0.1.1 is a valid boot block ) > reading 1082 blocks from dka500.5.0.1.1  > bootstrap code read in > Building FRU table5 > base = 200000, image_start = 0, image_bytes = 87400  > initializing HWRPB at 2000# > initializing page table at 1f2000  > initializing machine state% > setting affinity to the primary CPU  > jumping to bootstrap code  > < >                     ++++++++++++++++++++++++++++++++++++++< >                     +   AlphaServer 4100/4000 Firmware   +< >                     +          README-First !!!          +< >                     ++++++++++++++++++++++++++++++++++++++ > < > 1. Please CAREFULLY read this readme file IN ITS ENTIRETY. >  > K > 2. When updating console firmware, it is recommended that you update both  the H >    SRM and AlphaBIOS consoles at the same time to insure compatibility between  >    versions. >  > 8 > 3. Helpful Hints on using the UPDATE and LIST commands > > >    UPD> update srm*      to update the SRM console firmware.; >    UPD> update alpha*    to update the AlphaBIOS console. A >    UPD> update *         to update all firmware in your system. H >    UPD> update * -all    to update all firmware in your system without having1 >                          to confirm each update F >    UPD> list             to display adapters in your system that are	 supported A >                          by the Loadable Firmware Utility [LFU]  > 8 > Hit <RETURN> to scroll text, or <CTRL/C> to skip text. > + > The default bootfile for this platform is  > ! >         [AS4X00]AS4X00_V5_1.EXE  > 9 > Hit <RETURN> at the prompt to use the default bootfile.  >  > Bootfile:  > " > Starting Firmware Update Utility= > Copying source: to 119a000 from 2e8200 size 17e600(1566208)  >  > Unpacking firmware files2 >     as4x00_readme adr = 1000020 len = 1000(4096)1 >     readme       adr = 1001240 len = 1000(4096) 5 >     srmrom       adr = 1002460 len = f4800(1001472) 4 >     arcrom       adr = 10f6e80 len = 80000(524288)2 >     cipca_fw     adr = 11770a0 len = ce00(52736)4 >     dfxaa_fw     adr = 1318620 len = 38a00(231936)4 >     kzpsa_fw     adr = 1351240 len = 74000(475136) > 8 >           ***** Loadable Firmware Update Utility *****L > -------------------------------------------------------------------------- ---- >  Function    DescriptionL > -------------------------------------------------------------------------- ----9 >  Display     Displays the system's configuration table. % >  Exit        Done exit LFU (reset). D >  List        Lists the device, revision, firmware name, and update	 revision.  >  Lfu         Restarts LFU.3 >  Readme      Lists important release information. B >  Update      Replaces current firmware with loadable data image.5 >  Verify      Compares loadable and hardware images. + >  ? or Help   Scrolls this function table. L > -------------------------------------------------------------------------- ---- >  > UPD> upd *H > WARNING: updates may take several minutes to complete for each device. > . > Confirm update on: AlphaBIOS       [Y/(N)] y > ) >                           DO NOT ABORT! 1 > AlphaBIOS       Updating to V5.64-1...  FAILED.  > . > Confirm update on: srmflash        [Y/(N)] y > ) >                           DO NOT ABORT! 0 > srmflash        Updating to V5.1-3...  FAILED. >  > UPD> exiy  > exiy: No such command  >  > UPD> exit  > C > Errors occured during update with the following devices:AlphaBIOS 
 > srmflash >   > Do you want to exit? [Y/(N)] y >    ------------------------------  % Date: Sun, 26 Jan 2003 10:43:06 -0600 / From: Clay M. Denton <denton@orison.dsserv.com> 1 Subject: AlphaServer 4100 Firmware update problem 8 Message-ID: <oh383v0aknuaqdav630pmfk562ek00m9t0@4ax.com>  4 Trying to update the firmware on an AlphaServer 4100 System has 4 5/533 CPUs : Is currently running 5.1 (yes - I know - ancient) firmware  W V6.0 firmware (latest for 4100) instructions talk about the 2 step process - update SRM L first, then AlphaBIOS.  I get a "FAILED" message every time I try to update.  4 So, loaded an old 5.3 firmware disk - same failures.  E Then, tried to reapply 5.1 disk - all default answers - failed again.   Y Cannont find any information about the existence of a firmware/flash write protect jumper / or setting which would be causing me a problem.   V Did successfully update firmware on a FDDI controller in the same system from the same firmware disk.  X Tried using the failsafe loader floppy - but that only seems to apply if the firmware is corrupt to start with.  > Any ideas?  I'm including a log of one of the update sessions.   Clay   Initializing...      SROM V3.0 on cpu0  SROM V3.0 on cpu2  SROM V3.0 on cpu1  SROM V3.0 on cpu3 XSROM V5.1 on cpu2 XSROM V5.1 on cpu1 XSROM V5.1 on cpu0 XSROM V5.1 on cpu3 BCache testing complete on cpu0  BCache testing complete on cpu1  BCache testing complete on cpu2  BCache testing complete on cpu3  mem_pair0 - 128 MB  $ 20..20..20..20..21..21..21..21..23..) please wait 3 seconds for T24 to complete  24..24..24..24.. Memory testing complete on cpu3  Memory testing complete on cpu2  Memory testing complete on cpu1  Memory testing complete on cpu0  starting console on CPU 0 
 sizing memory    0    128 MB SYNC starting console on CPU 1  starting console on CPU 2  starting console on CPU 3  probing IOD1 hose 1    bus 0 slot 1 - NCR 53C810    bus 0 slot 2 - QLogic ISP1020 !   bus 0 slot 3 - DECchip 21140-AA !   bus 0 slot 4 - DECchip 21140-AA  probing IOD0 hose 0    bus 0 slot 1 - PCEB , EISA Data in non-volatile storage is corrupt   EISA Configuration Error" Run the EISA Configuration Utility       probing EISA Bridge, bus 1   bus 0 slot 2 - QLogic ISP1020    bus 0 slot 5 - QLogic ISP1020  configuring I/O adapters...    ncr0, hose 1, bus 0, slot 1    isp0, hose 1, bus 0, slot 2    tulip0, hose 1, bus 0, slot 3    tulip1, hose 1, bus 0, slot 4     floppy0, hose 0, bus 1, slot 0   isp1, hose 0, bus 0, slot 2    isp2, hose 0, bus 0, slot 5 " System temperature is 23 degrees C4 AlphaServer 4100 Console V5.1-3, 4-FEB-1998 16:40:08  
 CPU 0 booting     (boot dka500.5.0.1.1 -flags 0,0)/ block 0 of dka500.5.0.1.1 is a valid boot block ' reading 1082 blocks from dka500.5.0.1.1  bootstrap code read in Building FRU table3 base = 200000, image_start = 0, image_bytes = 87400  initializing HWRPB at 2000! initializing page table at 1f2000  initializing machine state# setting affinity to the primary CPU  jumping to bootstrap code   :                     ++++++++++++++++++++++++++++++++++++++:                     +   AlphaServer 4100/4000 Firmware   +:                     +          README-First !!!          +:                     ++++++++++++++++++++++++++++++++++++++  : 1. Please CAREFULLY read this readme file IN ITS ENTIRETY.    M 2. When updating console firmware, it is recommended that you update both the N    SRM and AlphaBIOS consoles at the same time to insure compatibility between    versions.    6 3. Helpful Hints on using the UPDATE and LIST commands  <    UPD> update srm*      to update the SRM console firmware.9    UPD> update alpha*    to update the AlphaBIOS console. ?    UPD> update *         to update all firmware in your system. M    UPD> update * -all    to update all firmware in your system without having /                          to confirm each update O    UPD> list             to display adapters in your system that are supported  ?                          by the Loadable Firmware Utility [LFU]   6 Hit <RETURN> to scroll text, or <CTRL/C> to skip text.  ) The default bootfile for this platform is            [AS4X00]AS4X00_V5_1.EXE   7 Hit <RETURN> at the prompt to use the default bootfile.   
 Bootfile:     Starting Firmware Update Utility; Copying source: to 119a000 from 2e8200 size 17e600(1566208)    Unpacking firmware files0     as4x00_readme adr = 1000020 len = 1000(4096)/     readme       adr = 1001240 len = 1000(4096) 3     srmrom       adr = 1002460 len = f4800(1001472) 2     arcrom       adr = 10f6e80 len = 80000(524288)0     cipca_fw     adr = 11770a0 len = ce00(52736)2     dfxaa_fw     adr = 1318620 len = 38a00(231936)2     kzpsa_fw     adr = 1351240 len = 74000(475136)  6           ***** Loadable Firmware Update Utility *****N ------------------------------------------------------------------------------  Function    DescriptionN ------------------------------------------------------------------------------7  Display     Displays the system's configuration table. #  Exit        Done exit LFU (reset). L  List        Lists the device, revision, firmware name, and update revision.  Lfu         Restarts LFU.1  Readme      Lists important release information. @  Update      Replaces current firmware with loadable data image.3  Verify      Compares loadable and hardware images. )  ? or Help   Scrolls this function table. N ------------------------------------------------------------------------------  
 UPD> upd *F WARNING: updates may take several minutes to complete for each device.  , Confirm update on: AlphaBIOS       [Y/(N)] y  '                           DO NOT ABORT! / AlphaBIOS       Updating to V5.64-1...  FAILED.   , Confirm update on: srmflash        [Y/(N)] y  '                           DO NOT ABORT! . srmflash        Updating to V5.1-3...  FAILED.  	 UPD> exiy  exiy: No such command   	 UPD> exit   G Errors occured during update with the following devices:AlphaBIOS        srmflash           Do you want to exit? [Y/(N)] y   ------------------------------  % Date: Sun, 26 Jan 2003 17:15:04 -0600 / From: Clay M. Denton <denton@orison.dsserv.com> 5 Subject: Re: AlphaServer 4100 Firmware update problem 8 Message-ID: <0uq83v0u9rko3dnf9u93l8jfopl3cqmr0o@4ax.com>  W I actually caused the EISA error during some of my debugging - ran a clear_srm_nvram or  something similar...   Clay  X On Sun, 26 Jan 2003 14:31:49 -0500, "Homer J. Simpson" <hsimpson@burnsenergy.com> wrote:  5 >I see the EISA error; did you run the ECU to fix it?  > H >If you want to experiment, take out all the option cards and try again. >  > = >"Clay M. Denton" <denton@orison.dsserv.com> wrote in message 3 >news:oh383v0aknuaqdav630pmfk562ek00m9t0@4ax.com... 7 >> Trying to update the firmware on an AlphaServer 4100  >> System has 4 5/533 CPUs= >> Is currently running 5.1 (yes - I know - ancient) firmware  >>E >> V6.0 firmware (latest for 4100) instructions talk about the 2 step  >process - update SRM G >> first, then AlphaBIOS.  I get a "FAILED" message every time I try to  >update. >>7 >> So, loaded an old 5.3 firmware disk - same failures.  >>H >> Then, tried to reapply 5.1 disk - all default answers - failed again. >>M >> Cannont find any information about the existence of a firmware/flash write  >protect jumper 2 >> or setting which would be causing me a problem. >>K >> Did successfully update firmware on a FDDI controller in the same system  >from the same >> firmware disk.  >>K >> Tried using the failsafe loader floppy - but that only seems to apply if  >the firmware is >> corrupt to start with.  >>A >> Any ideas?  I'm including a log of one of the update sessions.  >> >> Clay  >> >> Initializing... >> >>  SROM V3.0 on cpu0  >>  SROM V3.0 on cpu2  >>  SROM V3.0 on cpu1  >>  SROM V3.0 on cpu3  >> XSROM V5.1 on cpu2  >> XSROM V5.1 on cpu1  >> XSROM V5.1 on cpu0  >> XSROM V5.1 on cpu3 " >> BCache testing complete on cpu0" >> BCache testing complete on cpu1" >> BCache testing complete on cpu2" >> BCache testing complete on cpu3 >> mem_pair0 - 128 MB ' >> 20..20..20..20..21..21..21..21..23.. , >> please wait 3 seconds for T24 to complete >> 24..24..24..24.. " >> Memory testing complete on cpu3" >> Memory testing complete on cpu2" >> Memory testing complete on cpu1" >> Memory testing complete on cpu0 >> starting console on CPU 0 >> sizing memory >>   0    128 MB SYNC  >> starting console on CPU 1 >> starting console on CPU 2 >> starting console on CPU 3 >> probing IOD1 hose 1 >>   bus 0 slot 1 - NCR 53C810" >>   bus 0 slot 2 - QLogic ISP1020$ >>   bus 0 slot 3 - DECchip 21140-AA$ >>   bus 0 slot 4 - DECchip 21140-AA >> probing IOD0 hose 0 >>   bus 0 slot 1 - PCEB/ >> EISA Data in non-volatile storage is corrupt  >> >> EISA Configuration Error % >> Run the EISA Configuration Utility  >>! >>     probing EISA Bridge, bus 1 " >>   bus 0 slot 2 - QLogic ISP1020" >>   bus 0 slot 5 - QLogic ISP1020 >> configuring I/O adapters...  >>   ncr0, hose 1, bus 0, slot 1  >>   isp0, hose 1, bus 0, slot 2" >>   tulip0, hose 1, bus 0, slot 3" >>   tulip1, hose 1, bus 0, slot 4# >>   floppy0, hose 0, bus 1, slot 0   >>   isp1, hose 0, bus 0, slot 2  >>   isp2, hose 0, bus 0, slot 5% >> System temperature is 23 degrees C 7 >> AlphaServer 4100 Console V5.1-3, 4-FEB-1998 16:40:08  >> >> CPU 0 booting >># >> (boot dka500.5.0.1.1 -flags 0,0) 2 >> block 0 of dka500.5.0.1.1 is a valid boot block* >> reading 1082 blocks from dka500.5.0.1.1 >> bootstrap code read in  >> Building FRU table 6 >> base = 200000, image_start = 0, image_bytes = 87400 >> initializing HWRPB at 2000 $ >> initializing page table at 1f2000 >> initializing machine state & >> setting affinity to the primary CPU >> jumping to bootstrap code >>= >>                     ++++++++++++++++++++++++++++++++++++++ = >>                     +   AlphaServer 4100/4000 Firmware   + = >>                     +          README-First !!!          + = >>                     ++++++++++++++++++++++++++++++++++++++  >>= >> 1. Please CAREFULLY read this readme file IN ITS ENTIRETY.  >> >>L >> 2. When updating console firmware, it is recommended that you update both >theI >>    SRM and AlphaBIOS consoles at the same time to insure compatibility  >between >>    versions.  >> >>9 >> 3. Helpful Hints on using the UPDATE and LIST commands  >>? >>    UPD> update srm*      to update the SRM console firmware. < >>    UPD> update alpha*    to update the AlphaBIOS console.B >>    UPD> update *         to update all firmware in your system.I >>    UPD> update * -all    to update all firmware in your system without  >having 2 >>                          to confirm each updateG >>    UPD> list             to display adapters in your system that are 
 >supportedB >>                          by the Loadable Firmware Utility [LFU] >>9 >> Hit <RETURN> to scroll text, or <CTRL/C> to skip text.  >>, >> The default bootfile for this platform is >>" >>         [AS4X00]AS4X00_V5_1.EXE >>: >> Hit <RETURN> at the prompt to use the default bootfile. >> >> Bootfile: >># >> Starting Firmware Update Utility > >> Copying source: to 119a000 from 2e8200 size 17e600(1566208) >> >> Unpacking firmware files 3 >>     as4x00_readme adr = 1000020 len = 1000(4096) 2 >>     readme       adr = 1001240 len = 1000(4096)6 >>     srmrom       adr = 1002460 len = f4800(1001472)5 >>     arcrom       adr = 10f6e80 len = 80000(524288) 3 >>     cipca_fw     adr = 11770a0 len = ce00(52736) 5 >>     dfxaa_fw     adr = 1318620 len = 38a00(231936) 5 >>     kzpsa_fw     adr = 1351240 len = 74000(475136)  >>9 >>           ***** Loadable Firmware Update Utility ***** M >> --------------------------------------------------------------------------  >----  >>  Function    Description M >> --------------------------------------------------------------------------  >---- : >>  Display     Displays the system's configuration table.& >>  Exit        Done exit LFU (reset).E >>  List        Lists the device, revision, firmware name, and update 
 >revision. >>  Lfu         Restarts LFU. 4 >>  Readme      Lists important release information.C >>  Update      Replaces current firmware with loadable data image. 6 >>  Verify      Compares loadable and hardware images., >>  ? or Help   Scrolls this function table.M >> --------------------------------------------------------------------------  >----  >>
 >> UPD> upd * I >> WARNING: updates may take several minutes to complete for each device.  >>/ >> Confirm update on: AlphaBIOS       [Y/(N)] y  >>* >>                           DO NOT ABORT!2 >> AlphaBIOS       Updating to V5.64-1...  FAILED. >>/ >> Confirm update on: srmflash        [Y/(N)] y  >>* >>                           DO NOT ABORT!1 >> srmflash        Updating to V5.1-3...  FAILED.  >> >> UPD> exiy >> exiy: No such command >> >> UPD> exit >>D >> Errors occured during update with the following devices:AlphaBIOS >> srmflash  >>! >> Do you want to exit? [Y/(N)] y  >> >  >    ------------------------------    Date: 26 Jan 2003 13:26:14 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen) % Subject: Re: DECnet-Plus vs DECnet IV 3 Message-ID: <BVPWcOmmlruZ@eisner.encompasserve.org>   V In article <H9C354.A6C@world.std.com>, bdc@world.std.com (Brian 'Jarai' Chase) writes:  J > Hehe.  I like how TCP/IP's ARP is "messy" even though it scales to allowI > one to have any number of NICs in a given machine.  Whereas Phase IV is L > definitely "cleaner" by limiting one to a single interface per machine perK > network.  So the solution to support multiple NICs is to setup a separate F > ethernet segment for each each?!?!  Nice.  That's a really "elegant" > solution.   B It is foolish to protect against an interface failing without also# protecting against a cable failing.    ------------------------------  # Date: Sun, 26 Jan 2003 18:59:27 GMT ( From: "Mark E. Levy" <mlevy70@attbi.com>% Subject: Re: DECnet-Plus vs DECnet IV - Message-ID: <jeWY9.42518$rM2.35637@rwcrnsc53>   : "Brian 'Jarai' Chase" <bdc@world.std.com> wrote in message  news:H9C354.A6C@world.std.com.... > In article <%zRY9.41530$4y2.2029@sccrnsc04>,J > Hehe.  I like how TCP/IP's ARP is "messy" even though it scales to allowI > one to have any number of NICs in a given machine.  Whereas Phase IV is L > definitely "cleaner" by limiting one to a single interface per machine perK > network.  So the solution to support multiple NICs is to setup a separate F > ethernet segment for each each?!?!  Nice.  That's a really "elegant" > solution.   K Yes, messy. Have you ever heard of an ARP storm? They would bring my former F employer's entire network to it's knees every once in a while. Doesn't happen with DECnet.    -- Mark E. Levy" System Management Associates, Inc. Phone: 847-730-3193  Fax:   847-730-3194  Cell:  847-370-3071  Text:  melevy@vtext.com or        melevy@skytel.com   ------------------------------  # Date: Sun, 26 Jan 2003 22:01:30 GMT - From: bdc@world.std.com (Brian 'Jarai' Chase) % Subject: Re: DECnet-Plus vs DECnet IV & Message-ID: <H9CD6I.GpM@world.std.com>  3 In article <BVPWcOmmlruZ@eisner.encompasserve.org>, . Larry Kilgallen <Kilgallen@SpamCop.net> wrote:) > In article <H9C354.A6C@world.std.com>,  1 > bdc@world.std.com (Brian 'Jarai' Chase) writes:   L > > Hehe.  I like how TCP/IP's ARP is "messy" even though it scales to allowK > > one to have any number of NICs in a given machine.  Whereas Phase IV is N > > definitely "cleaner" by limiting one to a single interface per machine perM > > network.  So the solution to support multiple NICs is to setup a separate H > > ethernet segment for each each?!?!  Nice.  That's a really "elegant"
 > > solution.  > D > It is foolish to protect against an interface failing without also% > protecting against a cable failing.   E That presumes you're dealing with a single shared cable, like 10Base2 F thinnet.  Given the age of DECnet Phase IV, that was probably the most. common way to run ethernet during that time.    J With hubs or switches, cable failure is no longer an issue since there areH separate cables for each interface.  You would still have a single pointH of failure at the hub or switch, but you could have multiple switches.  I This gets you back to the point of having a scenerio that's equivalent to I having separate physical networks, so there's no benefit to be had unless F your bandwidth requirements are such that you need something like four* NICs but don't want to have four switches.  J From a redundancy standpoint, taken in the context of the state-of-the-artJ at that time, I'll agree that the DECnet Phase IV approach is a reasonableF one.  As ethernet evolved, and hubs and switches hubs came into use, IC think a number of situations would arise where maintaining separate F physical networks for multihomed systems would require more effort andG equipment costs than it was worth.  And following this thread, it seems E like there were changes made to DECnet-Plus (is this another name for ! DECnet Phase V?) to address this?   C I'd still be curious to know what changes were made the more recent F version(s) of DECnet to allow the support of multiple NICs on a single network.  D Mark Levy mentioned in a followup parallel to this one that TCP/IP'sH reliance on ARP for ethernet resulted in ARP storms.  I don't think thisJ is very common.  It's certainly something I've never encountered on any ofJ the networks where I've worked, and in trying to research the causes a bitF more, Google only returns 277 hits for the combined keywords "arp" andC "storm."  It seems like there are three scenerios for this: [1] the J ethernet segment in question is overloaded with systems, [2] the arp cacheG has the expiration for its entries set to be to frequent, [3] someone's J doing something malicious on your LAN.  The first is an indication of muchH larger problems that'll be felt on an ethernet segment regardless of theG higher level networking protocols used, owing to how ethernet copes (or G fails to cope) with traffic on a busy segment.  The second represents a J configuration error.  The third and last--well--if someone or something isI on your net generating hostile ARP requests, yes, you're in trouble.  But I this is case regardless of what protocol you're running on that ethernet.   F My guess is that I've (or apparently much anyone else, if you feel theG number of google hits offers a representative sample) never encountered I any problems with arp storms because I'm guessing the conditions for them F aren't like to arise on modern ethernet switches.  It is the case thatF I've only worked in evironments where there have been less than 10,000C NICs attached to our LAN.  I'd estimate that at my current place of 9 employment, we've around 5000 NICs interfaced to our LAN.    -brian.  --  F --- Brian Chase | bdc@world.std.com | http://world.std.com/~bdc/ -----5                    Do not fold, mutilate, or spindle.    ------------------------------  # Date: Sun, 26 Jan 2003 22:44:09 GMT - From: bdc@world.std.com (Brian 'Jarai' Chase) % Subject: Re: DECnet-Plus vs DECnet IV & Message-ID: <H9CF5M.9ox@world.std.com>  = In article <9UWY9.43159$VU6.39261@rwcrnsc52.ops.asp.att.net>, ' Mark E. Levy <mlevy70@attbi.com> wrote: < > "Larry Kilgallen" <Kilgallen@SpamCop.net> wrote in message/ > news:BVPWcOmmlruZ@eisner.encompasserve.org...   F > > It is foolish to protect against an interface failing without also' > > protecting against a cable failing.  > J > And actually, DECnet makes this easier, as both interfaces have the same
 > address.  I It sounds like this is DECnet's default behavior, which makes sense given H the focus VMS places on redundancy.  In defense of the alternatives, I'dE add that the above is something that can be easily configured for the   TCP/IP networking on my systems.   The options include:  I [1] Having a single IP address across multiple NICs.  If the NIC fails or H     the cable fails, there's automatic failover to the remaining working     link(s).  F [2] Having a single IP address across multiple NICs /with/ multiplexedE     traffic--so I've trunked 2x 1Gb/s ethernet adapters into a single J     logical interface that's capable of 2Gb/s.  If one of the links fails,E     I'm dropped down to 1GB/s.  Currently, I believe this trunking is 1     limited to 2x 1Gb/s NICs and 4x 100Mb/s NICs.   A [3] Having multiple IP addresses aliased to a single NIC.  From a G     redundancy standpoint, this is a bad idea, but there are situations G     where it's quite handy to be able to do this and redundancy is not  B     the driving factor.  (i.e. setting up multiple IPs on a singleH     interface for a webserver, transitioning the address scheme of one'sE     network, assigning all your alotted IP addresses so it looks like ;     you're making active use of your IPv4 Class C network.)   I Admittedly, the benefits listed in [3] above are only relevant in case of / one using TCP/IP for their networking protocol.   F As a LAN protocol, TCP/IP is probably rather bloated in comparision toI DECnet or any number of other alternatives.  Personally, I can forgive it E for that given that it's a general purpose protocol that can run over % /anything/--including carrier pigeon:   *    <URL:http://www.blug.linux.no/rfc1149/>   -brian.  --  F --- Brian Chase | bdc@world.std.com | http://world.std.com/~bdc/ -----5                    Do not fold, mutilate, or spindle.    ------------------------------  # Date: Sun, 26 Jan 2003 19:44:05 GMT ( From: "Mark E. Levy" <mlevy70@attbi.com>% Subject: Re: DECnet-Plus vs DECnet IV = Message-ID: <9UWY9.43159$VU6.39261@rwcrnsc52.ops.asp.att.net>   : "Larry Kilgallen" <Kilgallen@SpamCop.net> wrote in message- news:BVPWcOmmlruZ@eisner.encompasserve.org... I > In article <H9C354.A6C@world.std.com>, bdc@world.std.com (Brian 'Jarai'  Chase) writes: > L > > Hehe.  I like how TCP/IP's ARP is "messy" even though it scales to allowK > > one to have any number of NICs in a given machine.  Whereas Phase IV is J > > definitely "cleaner" by limiting one to a single interface per machine per D > > network.  So the solution to support multiple NICs is to setup a separateH > > ethernet segment for each each?!?!  Nice.  That's a really "elegant"
 > > solution.  > D > It is foolish to protect against an interface failing without also% > protecting against a cable failing.   H And actually, DECnet makes this easier, as both interfaces have the same address.   -- Mark E. Levy" System Management Associates, Inc. Phone: 847-730-3193  Fax:   847-730-3194  Cell:  847-370-3071  Text:  melevy@vtext.com or        melevy@skytel.com   ------------------------------  % Date: Sun, 26 Jan 2003 19:43:19 -0400 0 From: JF Mezei <jfmezei.spamnot@vl.videotron.ca>% Subject: Re: DECnet-Plus vs DECnet IV / Message-ID: <3E347281.A423729E@vl.videotron.ca>    Brian 'Jarai' Chase wrote:L > With hubs or switches, cable failure is no longer an issue since there areJ > separate cables for each interface.  You would still have a single pointH > of failure at the hub or switch, but you could have multiple switches.  M Can your ISP provide you with 2 distinctive lines feeding the same IP address N ? To the really paranoid, can 2 different ISPs provide you the same IP address ? (I didn,t think so).    J At one point, don't you come to a single point of failure somewhere insideC your ISP's router which balances your traffic between the 2 lines ?     F > Mark Levy mentioned in a followup parallel to this one that TCP/IP's6 > reliance on ARP for ethernet resulted in ARP storms.  G Haven't Code Red, Nimda and Yesterday's SQL virus/worm caused ARP havok M throughout the world between the ISPs and customers ? I know my cable modem's I receive light has been flashing ever since  Code Red. Perhaps not such an K issue for an intranet, as long as none of your machines have caught some of  those viruses.   ------------------------------  # Date: Mon, 27 Jan 2003 02:02:18 GMT ( From: "Mark E. Levy" <mlevy70@attbi.com>% Subject: Re: DECnet-Plus vs DECnet IV , Message-ID: <Kq0Z9.53188$Ve4.6402@sccrnsc03>  = "JF Mezei" <jfmezei.spamnot@vl.videotron.ca> wrote in message ) news:3E347281.A423729E@vl.videotron.ca...2 > Brian 'Jarai' Chase wrote:J > > With hubs or switches, cable failure is no longer an issue since there aremL > > separate cables for each interface.  You would still have a single pointJ > > of failure at the hub or switch, but you could have multiple switches. >nG > Can your ISP provide you with 2 distinctive lines feeding the same IPC addresseH > ? To the really paranoid, can 2 different ISPs provide you the same IP address, > ? (I didn,t think so).  L Yea, they can. It requires a router that supports the BGP4 routing protocol.   -- Mark E. Levy" System Management Associates, Inc. Phone: 847-730-3193O Fax:      847-730-3194 Cell:      847-370-3071h Text:     melevy@vtext.com or               melevy@skytel.com   ------------------------------  % Date: Mon, 27 Jan 2003 00:42:01 +0100  From: Dirk Munk <munk@home.nl> Subject: Re: dynamic DNS4 Message-ID: <im_Y9.43221$7F3.3852918@zwoll1.home.nl>   Arne Vajhj wrote: > Dirk Munk wrote: >  >> Phillip Helbig wrote: >>% >>> As one can see from, for example,i* >>>    http://www.technopagan.org/dynamic/J >>> there are many dynamic-DNS providers out there.  Can anyone recommend H >>> one which is not only good in general but also easy to use from VMS? >  >  >> How about VMS itself ?w >  >  > ???? > @ > He has a changing IP address from his ISP and need to register0 > that to the same IP name each time it changes. > , > Very common problem with xDSL connections. > 5 > Running DNS on his VMS box obviously does not solve  > the problem !@ > ; > And as he stated there are sites out there providing thisS
 > service. > . > Problem is to find one that is VMS friendly. >  > Arne > L Sorry, my mistake. I did not read the mesage carefully and thought he meant R dynamic DNS sofware, AKA Bind Server. This is in TCP/IP services as you will know.   ------------------------------  # Date: Sun, 26 Jan 2003 22:08:20 GMT . From: peter@langstoeger.at (Peter LANGSTOEGER) Subject: RE: EV7, ES47 questionn4 Message-ID: <o%YY9.235434$TY.2376160@news.chello.at>  _ In article <CIEJLCMNHNNDLLOOGNJIOELCGHAA.tom@kednos.com>, "Tom Linden" <tom@kednos.com> writes: & >Michael Unger (unger@decus.de) wrote,1 >>"Paul Repacholi" <prep@prep.synonet.com> wrote:a >>E >>> What can you put in the AGP slot with VMS? (perhaps not today...)e >>H >>There has been an announcement of the "ATI Radeon 7500 AGP Controller"H >>for AlphaServer systems and the installation guide is available at theE >>Q/HP web site. It explicitely describes the configuration for Tru64 
 >>and VMS. >uH >VMS is not mentioned as supported for the 7500, only the VX1, either in >PCI or AGP form factor.  @ There is a typo in the description of the ATI, namely the "ES4".F Maybe it is not the only one and there is support for OpenVMS, too ;-)  3 >Now all you need is a desktop system to put it in.i  L Does a ES47 qualify as desktop ? Unfortunately it is not listed for the VX1.& Only ES40, ES45, DS10[L], DS20[E], ...   --   Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialistm E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------    Date: 26 Jan 2003 16:52:41 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen)  Subject: RE: EV7, ES47 question 3 Message-ID: <xd2dDpzzOTBZ@eisner.encompasserve.org>   e In article <o%YY9.235434$TY.2376160@news.chello.at>, peter@langstoeger.at (Peter LANGSTOEGER) writes:S  N > Does a ES47 qualify as desktop ? Unfortunately it is not listed for the VX1.( > Only ES40, ES45, DS10[L], DS20[E], ...  D There was an ES47 listed, but the ES47 was just announced last week.F Various dates were rumored for its announcement, so I would not expectE support for it to be listed in documentation for peripherals until itn was surely announced.g   ------------------------------    Date: 26 Jan 2003 16:57:57 -0600- From: Kilgallen@SpamCop.net (Larry Kilgallen)  Subject: RE: EV7, ES47 question83 Message-ID: <8TSpIP$BNnK+@eisner.encompasserve.org>n  c In article <xd2dDpzzOTBZ@eisner.encompasserve.org>, Kilgallen@SpamCop.net (Larry Kilgallen) writes: g > In article <o%YY9.235434$TY.2376160@news.chello.at>, peter@langstoeger.at (Peter LANGSTOEGER) writes:A > O >> Does a ES47 qualify as desktop ? Unfortunately it is not listed for the VX1.r) >> Only ES40, ES45, DS10[L], DS20[E], ...r > F > There was an ES47 listed, but the ES47 was just announced last week.H > Various dates were rumored for its announcement, so I would not expectG > support for it to be listed in documentation for peripherals until its > was surely announced.    The AlphaStation ES47 page at   9 	http://h18002.www1.hp.com/alphaserver/workstations/es47/b  N lists the Radeon 7500 AGP graphics controller as supported, rather than "VX1".   ------------------------------  # Date: Mon, 27 Jan 2003 00:07:51 GMT4. From: peter@langstoeger.at (Peter LANGSTOEGER) Subject: RE: EV7, ES47 question 4 Message-ID: <rL_Y9.236494$TY.2408552@news.chello.at>  c In article <8TSpIP$BNnK+@eisner.encompasserve.org>, Kilgallen@SpamCop.net (Larry Kilgallen) writes:0d >In article <xd2dDpzzOTBZ@eisner.encompasserve.org>, Kilgallen@SpamCop.net (Larry Kilgallen) writes:h >> In article <o%YY9.235434$TY.2376160@news.chello.at>, peter@langstoeger.at (Peter LANGSTOEGER) writes: >>  P >>> Does a ES47 qualify as desktop ? Unfortunately it is not listed for the VX1.* >>> Only ES40, ES45, DS10[L], DS20[E], ... >>  G >> There was an ES47 listed, but the ES47 was just announced last week. I >> Various dates were rumored for its announcement, so I would not expectiH >> support for it to be listed in documentation for peripherals until it >> was surely announced. >  >The AlphaStation ES47 page at >p: >	http://h18002.www1.hp.com/alphaserver/workstations/es47/ >eO >lists the Radeon 7500 AGP graphics controller as supported, rather than "VX1".n  ; But not for OpenVMS, so this is almost meaningless to us...r  F I hope to see the official announcement of VX1 (or better) for OpenVMSG on an ES47 soon (and then I hope to win the lotto jackpot to be able to  buy a such a machine ;-)   -Peter  C PS: I still don't understand why it is named ES47 and not eg. DS27.rA Will it be able to run with 4 CPUs in the (very near) future ? Oro4 did HPQ marketing eventually choose the wrong name ?   --   Peter "EPLAN" LANGSTOEGERt% Network and OpenVMS system specialistt E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  % Date: Mon, 27 Jan 2003 01:48:12 +0100t6 From: Martin Heller <martin.nospam.heller@mheller.org> Subject: Re: EV7, ES47 question9* Message-ID: <3E3481CC.1030503@mheller.org>   Peter LANGSTOEGER schrieb:e > In article <8TSpIP$BNnK+@eisner.encompasserve.org>, Kilgallen@SpamCop.net (Larry Kilgallen) writes:  > e >>In article <xd2dDpzzOTBZ@eisner.encompasserve.org>, Kilgallen@SpamCop.net (Larry Kilgallen) writes:  >>h >>>In article <o%YY9.235434$TY.2376160@news.chello.at>, peter@langstoeger.at (Peter LANGSTOEGER) writes: >>>s >>> P >>>>Does a ES47 qualify as desktop ? Unfortunately it is not listed for the VX1.* >>>>Only ES40, ES45, DS10[L], DS20[E], ... >>>-G >>>There was an ES47 listed, but the ES47 was just announced last week.pI >>>Various dates were rumored for its announcement, so I would not expect-H >>>support for it to be listed in documentation for peripherals until it >>>was surely announced. >> >>The AlphaStation ES47 page ate >>; >>	http://h18002.www1.hp.com/alphaserver/workstations/es47/  >>P >>lists the Radeon 7500 AGP graphics controller as supported, rather than "VX1". >  > = > But not for OpenVMS, so this is almost meaningless to us...  > H > I hope to see the official announcement of VX1 (or better) for OpenVMSI > on an ES47 soon (and then I hope to win the lotto jackpot to be able to- > buy a such a machine ;-) >  > -Peter > E > PS: I still don't understand why it is named ES47 and not eg. DS27.oC > Will it be able to run with 4 CPUs in the (very near) future ? Or 6 > did HPQ marketing eventually choose the wrong name ?C Nope, it's the right one. There will be a 4 processor rack version. @ SPECint_rate2000 34.6, SPECfp_rate2000 58.9 for a 4 CPU version. 8GB per CPU from mid 2003 on.    Yours,	 M. Hellerx   ------------------------------  % Date: Sun, 26 Jan 2003 20:16:30 -0500w3 From: "Homer J. Simpson" <hsimpson@burnsenergy.com> , Subject: FA: OpenVMS 7.2, 7.2-1 Full Doc Set2 Message-ID: <lu%Y9.717$fk6.611@news.bellsouth.net>  = http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=2304544526    ------------------------------  # Date: Sun, 26 Jan 2003 18:42:22 GMTk% From: Tony Lawrence <tony@pcunix.com>r- Subject: Re: Firesafes Was: How to Backup OSX1= Message-ID: <i_VY9.43093$eM6.66565@rwcrnsc51.ops.asp.att.net>    Paul Sture wrote:a > <snip> > @ > Just for everyone's amusement, I stumbled across the following > page about tapes:: > > > http://storageconference.org/2001/EmergTechPanel/Schwarz.pdf >  > "1972d > $ > IBM begins development on its last  > tape drive (3480) ever because' > of the declining cost of disk drives"  > , > There are graphs of prices trends as well. >     C I think it's *possible* that dvdram or other optical devices might nG someday replace tape (and who knows, might even replace hard drives if  G you could ever make them fast enough) but the big advantage to tape is aC that you can always increase capacity by making the media a little oF thinner and a lot longer (disregarding the obvious phyical limits, of E course).   That's not equivalent to packing bits tighter to increase OF storage on a disk drive - as long as you can fit longer tape into the I drive, you can store more.  In theory, you could take a 4mm dat tape and iF design a tape that ran for hundreds miles and was fed in from outside H (obviously some clever engineering would be necessary).  The same drive  could write much larger data..  I For some reason that made me think of those car cd adaptors that let you sF play a cd through your tape player.  I'm thinking of that in reverse: F take a "tape" that actually feeds its data off to something else when F written.  Nothing to do with the previous point; just a random though  looking for an application :-)    H If I had to bet on it, I'd put my money on tape being around even after G hard drives are solid state or quantum devices or whatever.  They just u keep getting bigger and faster.r       -- h
 Tony Lawrence , Free SCO, Mac OS X and  Linux Skills Tests: % http://aplawrence.com/skillstest.htmlr   ------------------------------    Date: 26 Jan 2003 13:17:56 +0800, From: Paul Repacholi <prep@prep.synonet.com>- Subject: Re: Firesafes Was: How to Backup OSXe- Message-ID: <87wukswku3.fsf@prep.synonet.com>   . Paul Repacholi <prep@prep.synonet.com> writes:  % > This is what you do NOT want to see # > http://www.mso.anu.edu.au/collesss   Sorry, wrong link, use. http://www.mso.anu.edu.au/colless/StromloFire/   --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.)@                                              West Australia 6076* comp.os.vms,- The Older, Grumpier Slashdot. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------  % Date: Sun, 26 Jan 2003 14:10:48 -0400h0 From: JF Mezei <jfmezei.spamnot@vl.videotron.ca>* Subject: Re: High hit rate VMS Web server?/ Message-ID: <3E3424A6.CC630A35@vl.videotron.ca>1  # Ok here is a more generic question:   L One can have a shareable image that is loaded into the web server's process.N With OSU's threads, this could be very efficicent. Is this scalable ? (eg: oneK process doing all of the work, in a multi-cpu environment, this wouldn't beb very efficient, right ?)  H One can have a decnet object that gets "calls" from the web server. ThisD entails a decnet connection establishement, as well as an additionalB "transport" of the data bewteen the web server and the processes.  	aK In terms of transports, one can get decnet, tpcip or ICC. In a cluster thiseH allows good load balancing.  And Decnet would allow the CGI process withF database access to reside on a decnet node outside of the TCPIP world.  N One could have a multi threading stub inside the web server process which thenM switches the requests amongst a pool of mailboxes (MBA:) and sends/reads data 8 from individual CGI processes residing on the same node.  I Are there other methods ? Which is used most ? Can one truly achieve high.F performance with network link between the web server and CGI process ?   ------------------------------  # Date: Sun, 26 Jan 2003 22:12:34 GMTo6 From: Jeffrey Coffield <jeffrey@digitalsynergyinc.com>* Subject: Re: High hit rate VMS Web server?4 Message-ID: <3E345C36.8060403@digitalsynergyinc.com>   JF Mezei wrote:   K > Are there other methods ? Which is used most ? Can one truly achieve high0H > performance with network link between the web server and CGI process ?  D The slow part is going to be usually between the web server and the G Internet (T1, etc) while the connection between the web server and the *? system running the application will probably be at least 100MB.-   ------------------------------  % Date: Sun, 26 Jan 2003 14:02:44 -0400-0 From: JF Mezei <jfmezei.spamnot@vl.videotron.ca>- Subject: Re: How to get Digital printer partst/ Message-ID: <3E3422C2.B04BC567@vl.videotron.ca>s   John Nebel wrote:v > D > It is a Canon EX print engine and www.printerparts.com sells parts > 3 > C2001-67912-OEM is a kit which includes the fuser     M Many thanks. I also found the fuser heater alone for $23.00 (USD, which comesaK to about $100 canadian when all is said and done with transport :-( :-( :-(   J Would Digital/HP parts departments have this available, or would they sell  only the actual fuser assembly ?  N (fuser assembly is a big "block" that includes the 2 rollers, one of which has= the heater inside), as well as heat sensors, thermostat etc.)   T Also, how common is it for the heater to blow ? (it is a glorified halogen lighbulb)   ------------------------------    Date: 26 Jan 2003 18:07:12 -0800/ From: chris@applied-synergy.com (Chris Scheers)x- Subject: Re: How to get Digital printer partsc= Message-ID: <754a27c1.0301261807.5d3d543c@posting.google.com>   > IIRC, error 50 is a general fuser error.  It could also be the: thermistor on the fuser.  Make sure that that didn't blow.  C On the LJII/III family (DEClaser 2100), error 50 quite often wasn'teF the fuser at all, but was the high voltage power supply.  I don't knowF whether or not that is still true in the EX family, but you might want to check it.  
 Good luck!    g JF Mezei <jfmezei.spamnot@vl.videotron.ca> wrote in message news:<3E3422C2.B04BC567@vl.videotron.ca>...n > John Nebel wrote:t > > F > > It is a Canon EX print engine and www.printerparts.com sells parts > > 5 > > C2001-67912-OEM is a kit which includes the fuser  >  > O > Many thanks. I also found the fuser heater alone for $23.00 (USD, which comesaM > to about $100 canadian when all is said and done with transport :-( :-( :-(a > L > Would Digital/HP parts departments have this available, or would they sell" > only the actual fuser assembly ? > P > (fuser assembly is a big "block" that includes the 2 rollers, one of which has? > the heater inside), as well as heat sensors, thermostat etc.)I > V > Also, how common is it for the heater to blow ? (it is a glorified halogen lighbulb)   ------------------------------  % Date: Mon, 27 Jan 2003 00:13:50 -0400C0 From: JF Mezei <jfmezei.spamnot@vl.videotron.ca>- Subject: Re: How to get Digital printer partso/ Message-ID: <3E34B1F6.67B727D3@vl.videotron.ca>>   Chris Scheers wrote: > @ > IIRC, error 50 is a general fuser error.  It could also be the< > thermistor on the fuser.  Make sure that that didn't blow.  L Took the halogen tube/heater out. It was producing no heat. And checking theK leads, there is infinite resistance between the 2 ends (eg: elements inside $ offer no route for current to flow.)  ? The thermostat was allowing current to flow, so that wasn't it.    ------------------------------    Date: 26 Jan 2003 13:27:11 +0800, From: Paul Repacholi <prep@prep.synonet.com> Subject: Re: Marvel Performanceo- Message-ID: <87smvgwkeo.fsf@prep.synonet.com>p  - young_r@encompasserve.org (Rob Young) writes:   ^ > In article <87ptqlyu7b.fsf@prep.synonet.com>, Paul Repacholi <prep@prep.synonet.com> writes:* > > Shane Smith <ssmith@icius.com> writes: > > = > >> Picture: Winged pig flying over Battersea power station.n > > A > > I am sure there is some significance in the `Battersea' part, B > > but entropy seems to have won :( Could you fill in the missing	 > > part?  > >  > C > http://support.uni-oldenburg.de/~floyd/english/appendix/pigs.htmln > U > The first pig was designed by E.R.G. Amsterdam in December 1976 for the Album Cover R > of Animals. This pig was photographed in front of the Battersea Power Station in	 > London.  > F > http://support.uni-oldenburg.de/~floyd/english/appendix/batters.html  D Thank you! That is what I was looking for. Must get a CD of Animals, and DSoM for that matter.>   --  < Paul Repacholi                               1 Crescent Rd.,7 +61 (08) 9257-1001                           Kalamunda.O@                                              West Australia 6076* comp.os.vms,- The Older, Grumpier Slashdot. Raw, Cooked or Well-done, it's all half baked.F EPIC, The Architecture of the future, always has been, always will be.   ------------------------------  # Date: Sun, 26 Jan 2003 19:15:58 GMTA" From:   VAXman-  @SendSpamHere.ORGC Subject: Re: OT Battersea Power Station. Was Re: Marvel Performancef0 Message-ID: <00A1A8CD.EC05F073@SendSpamHere.ORG>  U In article <B5rPB4Q7ocjo@elias.decus.ch>, p_sture@elias.decus.ch (Paul Sture) writes:B
 >{...snip...}l >> >- >> http://www.tmesis.com/where_is_the_pig.jpg8 >0 >A nice pic.  L Took that from the train with the wide angle.  Before we take off this time,K I hope to have a polarizing filter which will fit that large lens and avoide? things like the reflection of the lights in the train's window.+    F >An interesting use of another former power station is the Tate ModernF >art gallery in London. I am told that the sheer size and space of the9 >place is something you need to experience to appreciate.l >e* >http://www.tate.org.uk/modern/default.htm  K Last time the Tate was mentioned here, I was labelled right-wing extremist.u   --O VAXman- OpenVMS APE certification number: AAA-0001     VAXman(at)TMESIS(dot)COMb            e5   "Well my son, life is like a beanstalk, isn't it?" i   ------------------------------  % Date: Sun, 26 Jan 2003 14:12:24 -0500 0 From: "GH" <nospam-holdenga@sourcecomputing.com>( Subject: Queue manager file size - fixed- Message-ID: <b11bti$2tnm$1@news3.infoave.net>e  6 That did the trick.  I got back over 2 million blocks.   Thanks!i  6 "Paul Sture" <p_sture@elias.decus.ch> wrote in message# news:2ZJQ4aMioZt6@elias.decus.ch...>4 > In article <b1137q$2o6l$1@news3.infoave.net>, "GH"- <nospam-holdenga@sourcecomputing.com> writes: J > >   I have a uVAX 3100 running VMS 7.1.  The qman$journal file has grown toH > > over 1 gb in size, and is slowly consuming the system disk.  Is this normal, D > > or is there a convenient way to truncate this file periodically? > >e > >u >b > $ RUN SYS$SYSTEM:JBC$COMMAND > JBC$COMMAND>DIAGNOSTIC 7 >lI > Control returns to the command prompt and your problem should be fixed.>1 > IIRC there's an ECO available which fixes this.r >1I > If you are not in the position to apply the ECO, or it's not convenient)H > to do so at the moment, you can run the above commands periodically in > the meantime.  >  > -- > Paul Sture   ------------------------------  % Date: Sun, 26 Jan 2003 14:08:29 -0500 0 From: "GH" <nospam-holdenga@sourcecomputing.com>- Subject: Re: Queue manager file size question - Message-ID: <b11bqh$2t7q$1@news3.infoave.net>*   It's a 2gb disk.    . "Tom Linden" <tom@kednos.com> wrote in message3 news:CIEJLCMNHNNDLLOOGNJIIELHGHAA.tom@kednos.com...>B > The statement implies that the system disk is larger than 1GByte; > Not allowed on this system (unless you have reburnt ROMs)g >t > >-----Original Message-----e3 > >From: Paul Sture [mailto:p_sture@elias.decus.ch] ) > >Sent: Sunday, January 26, 2003 9:08 AMs > >To: Info-VAX@Mvb.Saic.Com0 > >Subject: Re: Queue manager file size question > >t > > 5 > >In article <b1137q$2o6l$1@news3.infoave.net>, "GH" 0 > ><nospam-holdenga@sourcecomputing.com> writes:K > >>   I have a uVAX 3100 running VMS 7.1.  The qman$journal file has grown- toD > >> over 1 gb in size, and is slowly consuming the system disk.  Is > >this normal, E > >> or is there a convenient way to truncate this file periodically?e > >> > >> > >n > >$ RUN SYS$SYSTEM:JBC$COMMANDY > >JBC$COMMAND>DIAGNOSTIC 7  > > J > >Control returns to the command prompt and your problem should be fixed.2 > >IIRC there's an ECO available which fixes this. > >>J > >If you are not in the position to apply the ECO, or it's not convenientI > >to do so at the moment, you can run the above commands periodically inx > >the meantime. > >e > >--g
 > >Paul Sturee > >o > >---) > >Incoming mail is certified Virus Free. = > >Checked by AVG anti-virus system (http://www.grisoft.com).-D > >Version: 6.0.435 / Virus Database: 244 - Release Date: 12/30/2002 > >r > ---a( > Outgoing mail is certified Virus Free.< > Checked by AVG anti-virus system (http://www.grisoft.com).C > Version: 6.0.435 / Virus Database: 244 - Release Date: 12/30/2002i >h   ------------------------------  % Date: Sun, 26 Jan 2003 22:02:45 -0500s  From: John Santos <JOHN@egh.com>- Subject: RE: Queue manager file size questions4 Message-ID: <1030126215740.631A-100000@Ives.egh.com>  & On Sun, 26 Jan 2003, Tom Linden wrote:  B > The statement implies that the system disk is larger than 1GByte; > Not allowed on this system (unless you have reburnt ROMs)" >   / This depends on which model of uVAX 3100 it is!n  @ Is it a VAXStation 3100?  Way bad to have disks bigger than 1GB.  ; MicroVAX 3100 model 10 or 20?  Also bad, no upgraded PROMs.0  ; MicroVAX 3100 model 10e or 20e?  Console VMB before V6.4 isj< bad, but PROM upgrades were available, at least at one time.  $ Other MicroVAX 3100 models are fine.   See the Fine FAQ.c     > >-----Original Message-----63 > >From: Paul Sture [mailto:p_sture@elias.decus.ch]9) > >Sent: Sunday, January 26, 2003 9:08 AMA > >To: Info-VAX@Mvb.Saic.Com0 > >Subject: Re: Queue manager file size question > >i > >a5 > >In article <b1137q$2o6l$1@news3.infoave.net>, "GH" 0 > ><nospam-holdenga@sourcecomputing.com> writes:N > >>   I have a uVAX 3100 running VMS 7.1.  The qman$journal file has grown toD > >> over 1 gb in size, and is slowly consuming the system disk.  Is > >this normal, E > >> or is there a convenient way to truncate this file periodically?r   -- m John Santosr Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  % Date: Mon, 27 Jan 2003 07:57:39 +0100 6 From: =?ISO-8859-1?Q?Arne_Vajh=F8j?= <arne@vajhoej.dk>- Subject: Re: Queue manager file size question ) Message-ID: <3E34D863.6000508@vajhoej.dk>-  	 GH wrote: L  >   I have a uVAX 3100 running VMS 7.1.  The qman$journal file has grown toH  > over 1 gb in size, and is slowly consuming the system disk.  Is this  normal,oC  > or is there a convenient way to truncate this file periodically?g     $ MCR JBC$COMMANDp     JBC$COMMAND> DIAGNOSTIC 73     JBC$COMMAND> CTRL/Z    Arne   ------------------------------    Date: 26 Jan 2003 15:23:15 -0800! From: soterro@yahoo.com (Soterro)t) Subject: Raid failed apparently good diskr= Message-ID: <d5440555.0301261523.48e8bc5a@posting.google.com>e   Hello,  A Based probably on my misunderstanding of this RAID stuff, I can't.D figure out what is happening with my KZESC controller and its disks, on a Sable machine.r  E I had a small RAID-1 array of two disks, for testing. It used to workt* fine, now SRM always reports errors on it.  A I started the RCU to see that one disk is FLD (failed I guess). Ip
 wondered why.dB If I take out the disk and put it into another channel of the same? controller, (like moving from 0 to 1) it shows up there as RDY.tE Another disk put in its place also shows up in the list ok. If I takeu? the 'failed' disk and put it on the builtin controller, the SRMhC startup (read) tests succeed. This looks like the disk is (to whichu1 extent?) good, but it just fails the KZESC tests.   F What could have happened there, and is there a way to recover it? It'sF not a big loss, but I'd really like to know what and why happened, and if there's any cure.  
 Thanks a lot,  Sorina   ------------------------------  % Date: Sun, 26 Jan 2003 20:15:42 -0500 3 From: "Homer J. Simpson" <hsimpson@burnsenergy.com>o- Subject: Re: Raid failed apparently good diske2 Message-ID: <Ct%Y9.715$fk6.578@news.bellsouth.net>  J Update firmware on the system, the RAID controller, and, if available, theJ disk.  Use the (firmware-matching) RCU to make optimal. Oh yeah, do a fullE backup first and leave room for some crisis recovery time at the end.o  . "Soterro" <soterro@yahoo.com> wrote in message7 news:d5440555.0301261523.48e8bc5a@posting.google.com...i > Hello, >rC > Based probably on my misunderstanding of this RAID stuff, I can'tsF > figure out what is happening with my KZESC controller and its disks, > on a Sable machine.m >iG > I had a small RAID-1 array of two disks, for testing. It used to workl, > fine, now SRM always reports errors on it. > C > I started the RCU to see that one disk is FLD (failed I guess). I  > wondered why.oD > If I take out the disk and put it into another channel of the sameA > controller, (like moving from 0 to 1) it shows up there as RDY.eG > Another disk put in its place also shows up in the list ok. If I takekA > the 'failed' disk and put it on the builtin controller, the SRM E > startup (read) tests succeed. This looks like the disk is (to whichi3 > extent?) good, but it just fails the KZESC tests.' > H > What could have happened there, and is there a way to recover it? It'sH > not a big loss, but I'd really like to know what and why happened, and > if there's any cure. >r > Thanks a lot,n > Sorine   ------------------------------  % Date: Sun, 26 Jan 2003 20:16:54 -0500o From: Everhart <ge@gce.com>o- Subject: Re: Raid failed apparently good disko+ Message-ID: <b121ac$a48$1@bob.news.rcn.net>e   Soterro wrote: > Hello, > C > Based probably on my misunderstanding of this RAID stuff, I can't F > figure out what is happening with my KZESC controller and its disks, > on a Sable machine.u > G > I had a small RAID-1 array of two disks, for testing. It used to workr, > fine, now SRM always reports errors on it. > C > I started the RCU to see that one disk is FLD (failed I guess). I  > wondered why.hD > If I take out the disk and put it into another channel of the sameA > controller, (like moving from 0 to 1) it shows up there as RDY.aG > Another disk put in its place also shows up in the list ok. If I takeiA > the 'failed' disk and put it on the builtin controller, the SRMcE > startup (read) tests succeed. This looks like the disk is (to which 3 > extent?) good, but it just fails the KZESC tests.  > H > What could have happened there, and is there a way to recover it? It'sH > not a big loss, but I'd really like to know what and why happened, and > if there's any cure. >  > Thanks a lot,. > SorineK If you have a failed disk, best advice is to prepare some free space to getnI a copy of its data, pull it and get it good and cold, and try powering itgJ up that way. Sometimes a disk that was giving trouble can be made to mountH then. Do back/phys or some such, to get a copy off the device as fast asI you can, onto something else. (Reason for this is to avoid a lot of extra F head seeks that will warm it up.) Keep the disk WELL cooled till done.  H Doesn't always work but sometimes does. If you only need a few files offG the disk you can try copying them somewhere first, instead of or beforet the attempt at back/phys.h  H It is unlikely a disk that has failed badly will self heal enough to use	 for long.f   Glenn Everhart   ------------------------------  % Date: Sun, 26 Jan 2003 19:25:17 -0500s  From: John Santos <JOHN@egh.com>I Subject: Re: Storage network with VMS cluster and other OSses, ESS, EMC2? 4 Message-ID: <1030126183623.631A-100000@Ives.egh.com>  / On Wed, 22 Jan 2003, Brian 'Jarai' Chase wrote:k  0 > In article <3E2DA813.2060503@regenstrief.org>,> > Gunther Schadow  <gschadowREMOVETHIS@regenstrief.org> wrote: > 	 > > [...]  [...]   G > > Anyone here have real experience with ESS? In our situation we havenD > > reasons to do ESS because our partners in the same computer roomH > > have it (not on VMS) and they find maintenance service very good andF > > like to have an integrated backup strategy (Tivoli). But, how muchH > > of this backup strategy would work cross-filessystems? I would thinkF > > unless it is a raw blockwise backup independent from file-systems,G > > there is pretty little chance of a common backup mechanism for bothi2 > > VMS and Unix file systems. But I may be naive. > I > I know that Tivoli's TSM can support a wide variety of client platforms G > with all sort of different filesystem types. (or now it is IBM's TSM,eI > apparently; a few years ago it was called IBM ADSM before they flung itgH > off to Tivoli.  Now it seems to be back, directly under the control ofJ > IBM.)  It and VERITAS NetBackup are the two biggest players in the worldJ > of large scale backups.  Neither have an OpenVMS client in their currentJ > releases.  I seem to recall that TSM had one a number of years ago, but K > I may be remembering incorrectly.  Having managed both a large TSM system@K > on AIX and now a large NetBackup system on Solaris; I can say that TSM isVH > by far the superior product from a purely technical standpoint, but it; > does have a few things about it that I really don't like.r  B One of my customers started using TSM when it was Tivoli.  The VMSI client wasn't from Tivoli but a 3rd-party, Storage Solutions Specialists, A Inc. of Colorado Springs, CO.  Their web site is www.storsol.com.oC It still seems to be current; the latest version is dated Nov 2002.a  D > My experiences with IBM, from the standpoint of their hardware andI > support, have been positive.  Their support folks are really top notch,tL > and I never had any hassles getting something when I needed it in a timelyB > manner.  Of course, it all tends to come at a rather high price. > 	 > -brian.r   -- g John Santosb Evans Griffiths & Hart, Inc. 781-861-0670 ext 539   ------------------------------  % Date: Sun, 26 Jan 2003 15:35:49 -0700M From: Kevin Handy <kth@srv.net>:# Subject: Re: VAX network monitor... $ Message-ID: <3E3462C5.40800@srv.net>   Shiva MahaDeva wrote:@= > In my job we have 30 Micro VAX running VMS V5.5 in network.a0 > Id like to create a procedure to continuously7 > verify if any server is down. How could I make this ?t4 > Issuing "dir vax01::sys$manager:operator.log" is a+ > way, but Id like a most intelligent way.r
 > We use UCX.e > Thanks in advance.  : If you have a Unix/Linux box in there somewhere, you might want to look at 'mon'.  . 	http://www.kernel.org/pub/software/admin/mon/    ? It will do such things as e-mail/page/etc when a service fails.t= It can also require that a service be down for some number ofa$ tries before alarming the condition.   ------------------------------   End of INFO-VAX 2003.053 ************************a single point of failure somewhere insideC your ISP's router which balances your traffic between the 2 lines ?     F > Mark Levy mentioned in a followup parallel to this one that TCP/IP's6 > reliance on ARP for ethernet resulted in ARP storms.  G Haven't Code Red, Nimda and Yesterday's SQL virus/worm caused ARP havok M throughout t۪    ۪    £۪    ã۪    ģ۪    ţ۪    ƣ۪    ǣ۪    ȣ۪    ɣ۪    ʣ۪    ˣ۪    ̣۪    ۪ͣ    Σ۪    ϣ۪    У۪    ѣ۪    ң۪    ӣ۪    ԣ۪    գ۪    ֣۪    ף۪    أ۪    ٣۪    ڣ۪    ۣ۪    ܣ۪    ݣ۪    ޣ۪    ߣ۪    ۪    ۪    ۪    ۪    ۪    ۪    ۪    ۪    ۪    ۪    ۪    ۪    ۪    ۪    ۪    ۪    ۪    ۪    ۪    ۪    ۪    ۪    ۪    ۪    ۪    ۪    ۪    ۪    ۪    ۪    ۪    ۪    