1 INFO-VAX	Sun, 16 May 2004	Volume 2004 : Issue 270       Contents: BTCROUT  Re: installation boot failure  Re: installation boot failure  Re: installation boot failure  Re: installation boot failure  LDAP TLS/SSL support for VMS! Re: Reboot forces Shadowset Merge 8 Re: [General]: Understanding 'Mean Time Between Failure'  F ----------------------------------------------------------------------  " Date: Sat, 15 May 04 22:14:49 +100 From: rok@nuk.uni-lj.si  Subject: BTCROUT& Message-ID: <40a69660$1@NUK.Uni-Lj.Si>  !  OpenVMS AXP V7.3-2, all patches.   1 %BACKUP-I-BTCROUT, routine ODS-5 RMS SYNTAX ERROR    $ help/mess BTCROUT > %MSGHLP-F-NOTFOUND, message not found in Help Message database  E  OK, someday it will be found there. But right now, is there anybody  ! to let me know what's that about?    Regards,  D Rok Vidmar                       Internet:  rok.vidmar@nuk.uni-lj.si; National and University Library  Phone:     +386 1 421 5461 ; Turjaska 1, SI-1000 Ljubljana    Fax:       +386 1 421 5464  Slovenia   ------------------------------  + Date: Sat, 15 May 2004 12:50:04 -0500 (CDT)  From: sms@antinode.org& Subject: Re: installation boot failure) Message-ID: <04051512500449@antinode.org>    From: "o-o-o" <bkt@null.net>   > [...] C > %PKB0, Copyright (c) 1998 IntraServer Technology Inc. PKW V2.1.21 @ > %PKB0, SCSI Chip is SYM53C875, Operating mode is SE Ultra SCSI* > %PKB0, OFFLINE. ROM Checksum read error.C > %PKC0, Copyright (c) 1998 IntraServer Technology Inc. PKW V2.1.21 @ > %PKC0, SCSI Chip is SYM53C875, Operating mode is SE Ultra SCSI* > %PKC0, OFFLINE. ROM Checksum read error. > [...]  > any ideas?  @    Sounds like the symptom when one has a non-VMS edition of theG IntraServer SCSI card.  The VMS driver checks the ROM on the card, does F not see the magic number for the VMS edition of the card, and declaresD it to be unsuitable.  The plan, I gather, was to charge more for theC VMS-compatible card, and use the proceeds to pay for the VMS driver  development.  H    Presumably, one could be clever and patch the driver code to skip theF check, no doubt violating some license agreement somewhere.  An easierG plan might be to get a cheap QLogic SCSI card.  The official DEC QLogic D card was a KZPBA-CA/-CX (for the single-ended one), but VMS seems toF tolerate a generic QLogic card with the ISP1040B chip on it.  (It evenE likes the one with the "SGI p/n 9980983" sticker on it instead of the C DEC KZPBA sticker).  Tru64 UNIX, however, seems to demand a genuine G KZPBA, as it behaves very badly when it sees a non-DEC-labeled ISP1040B  card.   D    I assume that while you have two VMS-useless SCSI cards (PKB0 andF PKC0), PKA0 is ok, so if that's some on-board SCSI, you may be able to stick a disk or two on that.  H ------------------------------------------------------------------------  4    Steven M. Schweda               (+1) 651-699-98183    382 South Warwick Street        sms@antinode-org     Saint Paul  MN  55105-2547    ------------------------------  % Date: Sat, 15 May 2004 23:21:57 +0200 , From: "Hans Vlems" <hvlems.dotweg@zonnet.nl>& Subject: Re: installation boot failure* Message-ID: <2gng40F4pj9oU1@uni-berlin.de>  ) "o-o-o" <bkt@null.net> schreef in bericht 4 news:%nopc.351$Bk1.291@newssvr23.news.prodigy.com...J > Thanks for the tip, that works, and I can boot the CD. However on boot I get  > checksum errors:$ > Installing required known files... >  > Configuring devices... > C > %PKB0, Copyright (c) 1998 IntraServer Technology Inc. PKW V2.1.21  > @ > %PKB0, SCSI Chip is SYM53C875, Operating mode is SE Ultra SCSI > * > %PKB0, OFFLINE. ROM Checksum read error. > C > %PKC0, Copyright (c) 1998 IntraServer Technology Inc. PKW V2.1.21  > @ > %PKC0, SCSI Chip is SYM53C875, Operating mode is SE Ultra SCSI > * > %PKC0, OFFLINE. ROM Checksum read error. > # > %EWA0, FastFD mode set by console  > K > and once I'm in the install utility, I can't see my SCSI hard drives. All  I 2 > see are the CDROM, floppy drive, and tape drive:6 > Enter device name for target disk: (? for choices) ? > + > Device Device Error Volume Free Trans Mnt  > * > Name Status Count Label Blocks Count Cnt >  > DAD0: Online 0 > . > DKA500: Mounted wrtlck 0 ALPHA0731 7785 87 1 >  > DVA0: Online 0 >  >  > 4 > Enter device name for target disk: (? for choices) >  > any ideas? > H The SCSI adapter is intended for WindowsNT. When I got my 5305 they justA changed the SCSI adapter for a VMS supported model, the KZPCM-DA. 6 There may be other (cheaper?) SCSI adapters available.< The SCSI-2 PKA channel has one free slot, next to the CDrom." See:  http://home.zonnet.nl/hvlems   Hans   ------------------------------  % Date: Sat, 15 May 2004 23:14:04 +0200 , From: "Hans Vlems" <hvlems.dotweg@zonnet.nl>& Subject: Re: installation boot failure* Message-ID: <2gnfl7F4olijU1@uni-berlin.de>  I <sms@antinode.org> schreef in bericht news:04051512500449@antinode.org...  > From: "o-o-o" <bkt@null.net> > 	 > > [...] E > > %PKB0, Copyright (c) 1998 IntraServer Technology Inc. PKW V2.1.21 B > > %PKB0, SCSI Chip is SYM53C875, Operating mode is SE Ultra SCSI, > > %PKB0, OFFLINE. ROM Checksum read error.E > > %PKC0, Copyright (c) 1998 IntraServer Technology Inc. PKW V2.1.21 B > > %PKC0, SCSI Chip is SYM53C875, Operating mode is SE Ultra SCSI, > > %PKC0, OFFLINE. ROM Checksum read error.	 > > [...]  > > any ideas? > B >    Sounds like the symptom when one has a non-VMS edition of theI > IntraServer SCSI card.  The VMS driver checks the ROM on the card, does H > not see the magic number for the VMS edition of the card, and declaresF > it to be unsuitable.  The plan, I gather, was to charge more for theE > VMS-compatible card, and use the proceeds to pay for the VMS driver  > development. > J >    Presumably, one could be clever and patch the driver code to skip theH > check, no doubt violating some license agreement somewhere.  An easier  H Unfortunately that does not work, apparently DEC had the firmware on theE SCSI card modified. The modification is no problem for Windows but it A makes the VMS driver barf. The very same hardware, though under a : slightly different part no, works perfectly well with VMS.  G The onboard PKA channel is useful though. It drives the standard CDrom. D There is an empty bay next to the CDrom drive and there is an unusedG power  and SCSI connector to hook up a disk or tape drive. It is SCSI-2 G (50 pin) hardware. I put a 2 GB disk in there without mounting brackets 0 and copied three Freeware CD's versions onto it.  I > plan might be to get a cheap QLogic SCSI card.  The official DEC QLogic F > card was a KZPBA-CA/-CX (for the single-ended one), but VMS seems toH > tolerate a generic QLogic card with the ISP1040B chip on it.  (It evenG > likes the one with the "SGI p/n 9980983" sticker on it instead of the E > DEC KZPBA sticker).  Tru64 UNIX, however, seems to demand a genuine I > KZPBA, as it behaves very badly when it sees a non-DEC-labeled ISP1040B  > card.  > F >    I assume that while you have two VMS-useless SCSI cards (PKB0 andH > PKC0), PKA0 is ok, so if that's some on-board SCSI, you may be able to > stick a disk or two on that. > J > ------------------------------------------------------------------------ > 6 >    Steven M. Schweda               (+1) 651-699-98185 >    382 South Warwick Street        sms@antinode-org  >    Saint Paul  MN  55105-2547    ------------------------------  # Date: Sun, 16 May 2004 02:26:05 GMT  From: "o-o-o" <bkt@null.net>& Subject: Re: installation boot failure> Message-ID: <1jApc.27318$IP6.15810@newssvr22.news.prodigy.com>  L You know I had not, but that is a good idea. I guess debian is the way to go on an alpha?  K "David J. Dachtera" <djesys.nospam@NeOaSrPtAhMlNiOnWk.net> wrote in message 0 news:40A58909.C387C57E@NeOaSrPtAhMlNiOnWk.net... > o-o-o wrote: > > I > > Thanks for the help. This box was indeed running NT4.0 SP6 when I got  it. L > > But I blew it away, switched the console to serial, switched the os type to& > > VMS, and thought I'd give it a go.I > > the next question is, does anyone want an alpha that can't run VMS? I  don't.4 > > It has some nice parts that could be salvaged... > ( > Other posters have some ideas for VMS. > " > Have you considered Alpha Linux? >  > --   > David J. Dachtera  > dba DJE Systems  > http://www.djesys.com/ > * > Unofficial Affordable OpenVMS Home Page:! > http://www.djesys.com/vms/soho/    ------------------------------  # Date: Sat, 15 May 2004 19:06:35 GMT # From: Jonas Lindholm <jlhm@usa.net> % Subject: LDAP TLS/SSL support for VMS 9 Message-ID: <%Stpc.76446$Nn4.16602468@twister.nyc.rr.com>   A Does anyone know when the LDAP API for VMS will support TLS/SSL ?    /Jonas   ------------------------------  % Date: Sat, 15 May 2004 14:39:55 -0500 @ From: "David J. Dachtera" <djesys.nospam@NeOaSrPtAhMlNiOnWk.net>* Subject: Re: Reboot forces Shadowset Merge6 Message-ID: <40A6720B.3D5B5D9B@NeOaSrPtAhMlNiOnWk.net>   Tom Linden wrote:  > ; > I have three shadow sets on a BA356 attached to two nodes > > (7.3 and 7.3-1 alphas) If I shutdown and reboot another node: > in the cluster it causes a merge operation on the shadowC > sets, which takes 24 hours!  (74GB disks and bandwidth on BA3565)  > $ > the shutdown command I ma using isG >   SHUTDOWN == "@SYS$SYSTEM:SHUTDOWN 0 SHUTDOWN YES YES LATER NO NONE"  > ? > Now if I manually dismount the shadow sets from the node I am C > shutting down, then this doesn't happen, but in order to do that, . > I have to stop the queue manager (open file)  E There's your clue right there - an open file on the volume preventing  clean dismount.   H You'll find there is no work-around for this. You'll have to get a clean% dismount to prevent the shadow merge.    --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  ( Unofficial Affordable OpenVMS Home Page: http://www.djesys.com/vms/soho/    ------------------------------  % Date: Sun, 16 May 2004 05:05:23 +0800 , From: Paul Repacholi <prep@prep.synonet.com>A Subject: Re: [General]: Understanding 'Mean Time Between Failure' - Message-ID: <87pt95wgdo.fsf@prep.synonet.com>   , "Jack Peacock" <peacock@simconv.com> writes:  E > As I understand the procedure vendors determine the MTBF by testing = > drives under accelerated conditions (higher temp, etc.) and A > extrapolate what the MTBF would be under normal conditions.  It A > isn't practical to actually run a batch for 50,000 hours before ? > putting the drives on the market so I don't disagree with the A > procedure...but I don't put much faith in MTBF figures (or MTTR B > either, if you don't have a spare the MTTR is days regardless of > vendor claims).   C Look in the fine print. Most MTBFs are a MIL spec procedure that is A based soley on part counts and types. Tot up all the bits in each / catagory, do the arithmatic, out pops a number.    --  < 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.   ------------------------------   End of INFO-VAX 2004.270 ************************