INFO-VAX Fri, 22 Feb 2008 Volume 2008 : Issue 106 Contents: ANAL/DISK output, how to determine file Re: ANAL/DISK output, how to determine file Re: ANAL/DISK output, how to determine file Re: ANAL/DISK output, how to determine file Re: ANAL/DISK output, how to determine file Re: Errors during shadow set merge Re: Errors during shadow set merge Re: Errors during shadow set merge Re: Errors during shadow set merge how to check firmware version? Re: how to check firmware version? Re: how to check firmware version? Re: how to check firmware version? Re: how to process/produce un*x 'diff' formats ? Re: Iffy DCL IF Re: LK-201 error question Re: LK-201 error question Re: LK-201 error question Re: Microsoft pro says OpenVMS best OS ever invented! Re: Microsoft pro says OpenVMS best OS ever invented! Re: Microsoft pro says OpenVMS best OS ever invented! Re: Oracle 10.2.0.2 on my OpenVMS HP Integrity Re: regex within a DCL procedure Re: Samba and text files Re: Samba and text files ---------------------------------------------------------------------- Date: Fri, 22 Feb 2008 08:24:39 -0800 (PST) From: tadamsmar Subject: ANAL/DISK output, how to determine file Message-ID: <92b5e849-ea13-47b9-a94f-7af04f8a8904@s12g2000prg.googlegroups.com> I get: %ANALDISK-W-BADHEADER, file (25695,87,0) with no file name. HELP/MESS BADHEADER says to restore the file. But how do you figure out the file name? ------------------------------ Date: Fri, 22 Feb 2008 08:39:26 -0800 (PST) From: IanMiller Subject: Re: ANAL/DISK output, how to determine file Message-ID: I usually use DFU DFU SEARCH/FID=(25695,87,0) devname ------------------------------ Date: Fri, 22 Feb 2008 08:48:34 -0800 (PST) From: Hein RMS van den Heuvel Subject: Re: ANAL/DISK output, how to determine file Message-ID: <6b957f64-7adb-406d-a07c-18c43f104fb5@q78g2000hsh.googlegroups.com> On Feb 22, 11:24=A0am, tadamsmar wrote: > I get: > > %ANALDISK-W-BADHEADER, file (25695,87,0) > > with no file name. > > HELP/MESS BADHEADER says to restore the file. =A0 But how do you figure > out the file name? It is legal for a file NOT to have a name, so assume that is the case. Typically used for temporary files of course. The other possibility is that the corruption is bad enough that the usual FID_TO_NAME does not work. You could TRY: $DUMP/HEADER/BLOCK=3DCOUNT=3D0 dev:/ID=3D25695 or... $ pipe dir/file/nohead/wid=3Dfile=3D60 [000000...] | searc sys$pipe "(25695," or $DUMP/BLOCK=3D(START=3D<25695+4*cluster+bitmapsize-1>,COUNT=3D1) dev: [000000]INDEXF.SYS I suggest to just /REPAIR and hope for the best. Hein. ------------------------------ Date: Fri, 22 Feb 2008 08:51:11 -0800 (PST) From: Hein RMS van den Heuvel Subject: Re: ANAL/DISK output, how to determine file Message-ID: <837fa32f-cc56-4991-bda7-c987d03dfcff@28g2000hsw.googlegroups.com> Ah! Forgot about the DFU. Yes, like Ian indicates, also try DFU SEARCH/FID=25695 devname: I would just provide the file-id, not the sequence number just in case it is the corrupted part. Hein. ------------------------------ Date: Fri, 22 Feb 2008 12:14:13 -0500 From: "Richard B. Gilbert" Subject: Re: ANAL/DISK output, how to determine file Message-ID: <47BF02E5.3050809@comcast.net> tadamsmar wrote: > I get: > > %ANALDISK-W-BADHEADER, file (25695,87,0) > > with no file name. > > HELP/MESS BADHEADER says to restore the file. But how do you figure > out the file name? Well, I'd look in INDEXF.SYS for the file ID. The file name may be an illegal string, corrupted, or missing entirely. Make an IMAGE backup before trying to fix it! If you screw up, you'll at least be able to restore the status quo ante. ------------------------------ Date: Fri, 22 Feb 2008 06:46:08 -0800 (PST) From: tadamsmar Subject: Re: Errors during shadow set merge Message-ID: <8147d49f-87ea-47b3-b6aa-f4e6259ced2b@e10g2000prf.googlegroups.com> On Feb 21, 8:27=A0pm, John Santos wrote: > Richard B. Gilbert wrote: > > tadamsmar wrote: > > >> On Feb 21, 7:54 am, tadamsmar wrote: > > >>> On Feb 20, 10:19 pm, Michael Austin > >>> wrote: > > >>>> tadamsmar wrote: > > >>>>> On Feb 18, 11:17 pm, Michael Austin > >>>>> wrote: > > >>>>>> tadamsmarwrote: > > >>>>>>> On Feb 18, 5:00 pm, "Richard B. Gilbert" > >>>>>>> wrote: > > >>>>>>>> tadamsmarwrote: > > >>>>>>>>> I noticed I was getting errors when adding a member to a shadow > >>>>>>>>> set. > >>>>>>>>> I have been getting errors during shadow set merges since I boug= ht > >>>>>>>>> this refurb DS10. > >>>>>>>>> Got 109 error today when I remerged after doing an image. =A016 > >>>>>>>>> errors > >>>>>>>>> on DKA0 and 93 on DKA100. > >>>>>>>>> What do you think is causing this? > >>>>>>>>> Are these soft errors? > >>>>>>>>> Here is the log for one: > >>>>>>>>> **** V3.4 =A0********************* ENTRY 1667 > >>>>>>>>> ******************************** > >>>>>>>>> Logging OS =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A01. Ope= nVMS > >>>>>>>>> System Architecture =A0 =A0 =A0 =A0 =A0 =A0 =A0 2. Alpha > >>>>>>>>> OS version =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 V= 7.3-2 > >>>>>>>>> Event sequence number =A0 =A0 =A0 =A0 11474. > >>>>>>>>> Timestamp of occurrence =A0 =A0 =A0 =A0 =A0 =A0 =A018-FEB-2008 0= 9:52:48 > >>>>>>>>> Time since reboot =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A077 Day(= s) 1:23:46 > >>>>>>>>> Host name =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0EESD > >>>>>>>>> System Model =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Alp= haServer DS10 617 MHz > >>>>>>>>> Entry Type =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A01. Dev= ice Error > >>>>>>>>> ---- Device Profile ---- > >>>>>>>>> Unit =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 $1$DKA0 > >>>>>>>>> Product Name =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ATL= AS10K2-TY184L > >>>>>>>>> Vendor =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 QUANTUM > >>>>>>>>> -- Driver Supplied Info - > >>>>>>>>> Device Firmware Revision =A0 =A0 =A0 =A0 =A0 =A0 DA40 > >>>>>>>>> VMSSCSIError Type =A0 =A0 =A0 =A0 =A0 =A0 =A0 5. Extended Sense = Data from Device > >>>>>>>>> SCSIID =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00 > >>>>>>>>> SCSILUN =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x00 > >>>>>>>>> SCSISUBLUN =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00 > >>>>>>>>> Port Status =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00000001 =A0NORMAL =A0-= =A0normal successful > >>>>>>>>> completion > >>>>>>>>> SCSICommand Opcode =A0 =A0 =A0 =A0 =A0 =A0 x28 =A0Read (10 byte = command) > >>>>>>>>> Command Data > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x= 00 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x= 02 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x= 06 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x= 44 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x= 8A > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x= 00 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x= 00 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x= 01 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x= 00 > >>>>>>>>> SCSIStatus =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x02 =A0Check = Condition > >>>>>>>>> Remaining Byte Length =A0 =A0 =A0 =A0 =A0 =A018. > >>>>>>>>> --- Device Sense Data --- > >>>>>>>>> Error Code =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0xF0 =A0Cur= rent Error > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Information Bytes are Valid > >>>>>>>>> Segment # =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00 > >>>>>>>>> Information Byte 3 =A0 =A0 =A0 =A0 =A0 =A0 =A0x02 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0Byte 2 =A0 =A0 =A0 =A0 =A0 =A0 =A0x06 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0Byte 1 =A0 =A0 =A0 =A0 =A0 =A0 =A0x44 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0Byte 0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x8A =A0= LBA: =A0x0206448A > >>>>>>>>> Sense Key =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x03 =A0Med= ium Error > >>>>>>>>> Additional Sense Length =A0 =A0 =A0 =A0 x0A > >>>>>>>>> CMD Specific Info Byte 3 =A0 =A0 =A0 =A0x21 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Byte 2 =A0 =A0 =A0 =A0x23 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Byte 1 =A0 =A0 =A0 =A0x3E > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Byte 0 =A0 =A0 =A0 =A0xD4 > >>>>>>>>> ASC & ASCQ =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x1100 =A0ASC = =A0=3D =A0 x0011 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 ASCQ =3D =A0 x0000 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Unrecovered Read Error > >>>>>>>>> FRU Code =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x00 > >>>>>>>>> Sense Key Specific Byte 0 =A0 =A0 =A0 x80 =A0Valid Sense Key Dat= a > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Byte 1 =A0 =A0 =A0 x00 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Byte 2 =A0 =A0 =A0 xA0 > >>>>>>>>> ----- Software Info ----- > >>>>>>>>> UCB$x_ERTCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 16. Retries= Remaining > >>>>>>>>> UCB$x_ERTMAX =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 16. Retries= Allowable > >>>>>>>>> IRP$Q_IOSB =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x0000000000000000 > >>>>>>>>> UCB$x_STS =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x08021810 =A0Online > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Software Valid > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Unload At Dismount > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Volume is Valid on the local > >>>>>>>>> node > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Unit supports the Extended > >>>>>>>>> Function bit > >>>>>>>>> IRP$L_PID =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x82640450 =A0Requestor= "PID" > >>>>>>>>> IRP$x_BOFF =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 4416. Byte Pa= ge Offset > >>>>>>>>> IRP$x_BCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0512. Trans= fer Size In Byte(s) > >>>>>>>>> UCB$x_ERRCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 32. Errors = This Unit > >>>>>>>>> UCB$L_OPCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A022716780. QIO's This = Unit > >>>>>>>>> ORB$L_OWNER =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00010004 =A0Owners UIC > >>>>>>>>> UCB$L_DEVCHAR1 =A0 =A0 =A0 =A0 =A0 =A0x1C4D4008 =A0Directory Str= uctured > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 File Oriented > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Sharable > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Available > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Mounted > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Error Logging > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Capable of Input > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Capable of Output > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Random Access > > >>>>>>>> Is that system under service contract? =A0If so, ask to have the > >>>>>>>> drive > >>>>>>>> replaced! > >>>>>>>> I hope you have a recent backup that's readable. =A0 If you don't= , > >>>>>>>> try to > >>>>>>>> make one! =A0Right now!!!! > >>>>>>>> It could be just a single bad block. =A0It could also be all the > >>>>>>>> warning > >>>>>>>> you are going to get that the disk is failing! =A0Once you hear > >>>>>>>> that "loud > >>>>>>>> scraping sound" it's all over!! > >>>>>>>> If you don't have a service contract, order a replacement disk > >>>>>>>> and get a > >>>>>>>> rush on the delivery! > >>>>>>>> Meanwhile, keep an eye on the disk. =A0If you get more error > >>>>>>>> messages with > >>>>>>>> different LBAs it means the situation is deteriorating and you > >>>>>>>> may have > >>>>>>>> an emergency within a few minutes or hours.- Hide quoted text - > >>>>>>>> - Show quoted text - > > >>>>>>> Are these hard or soft errors? > > >>>>>> These are generally HARD errors - do what he said and order a disk > >>>>>> ASAP.- Hide quoted text - > > >>>>>> - Show quoted text - > > >>>>> I am skeptical that its the disks (In my original message, I indicat= ed > >>>>> that I get errors for both disks) > > >>>>> I have had this problem for a while. =A0I have run: > > >>>>> ANAL/MEDIA/EXER > > >>>>> on the disks and found no errors. > > >>>>> These error bursts only happen when I do a shadow set merge. > > >>>>> I suspect something about the SCSI, or connections, that is stressed= > >>>>> by a merge. > > >>>> I still suspect the media - and I can back it up with 24 years of > >>>> reading error logs... can you?- Hide quoted text - > > >>>> - Show quoted text - > > >>> No. > > >>> Here is a log of my recent findings > > >>> Merged the shadow set, getting 16 errors on DKA0 and 83 errors on > >>> DKA100. > > >>> Did a ANALYZE/MEDIA/EXER=3DFULL of DKA100 and found 1 bad block. =A0Go= t a > >>> good many errors logged during the ANALYZE. > > >>> Merged the shadow set, getting 16 errors on DKA0 and 5 errors on > >>> DKA100. > > >>> Did a ANALYZE/MEDIA/EXER=3DFULL of DKA0 and found 0 bad blocks. =A0Got= a > >>> good 0 errors logged during the ANALYZE. > > >>> Merged the shadow set, getting 4 errors on DKA0 and 19 errors on > >>> DKA100. > > >>> I will swap out one of the disks and give it a try. =A0Put in a disk > >>> that is logging no errors at its current location.- Hide quoted text -= > > >>> - Show quoted text - > > >> I swapped the dka100 disks between two DS10s (same model disks). > > >> Then I merged the shadowset on the problem machine. =A0 I got 4 errors > >> on dka100 and 16 on dka0. =A0All indicating unrecoverable. > > >> On the other machine a got about 34 errors on dka100 (most indicating > >> unrecoverable) during the shadowset merge. =A0But I realized that I had= > >> found 1 bad block on it when it it was on the problem machine using > >> ANALYZE. =A0So, I ran ANAL/MEDIA/EXER=3DFULL and found 13 bad blocks. > > >> I suspect there must be more than bad disks on the problem machine, > >> since it got 4 unrecovable errrors (at 2 LBAs) on a disk that had none > >> recently during shadowset merges on the other machine. > > >> BTW, =A0when you do a DIAGNOSE/TRANS/SUMMARY all these errors > >> are listed as SCSI errors, but when you look at the sense data in > >> detailed report, most are identified as medium errors. > > >> I guess will ask the vendor for a couple of disks under the warranty, > >> but I have no confidence that it will solve the problem. =A0Maybe I nee= d > >> the machine replaced. > > > It is possible that you have a problem with a cable, or a host bus > > adapter either as a contributing factor or (less likely) as the whole > > problem. > > Or it could be a problem with SCSI bus termination, either no terminator > or double termination or an extra terminator in the middle or a bad > terminator. =A0We had an old BA350(?) shelf (fast/narrow, gray disks) > that we daisychained an external 8mm tape drive to, worked fine for a > year or two, and then someone inserted a tape upside down or backwards > and busted it. =A0DEC (or maybe Compaq) replaced the drive about 5 times, > they kept failing. =A0Would work fine in a short test but full volume > backups would usually fail. =A0After they replaced the drive about 4 or > 5 times, someone said the magic word "termination", and so I took the > covers off the BA350 and discovered whoever had added the external > tape drive had neglected to remove the internal terminator. =A0After > removing it, the latest "DOA" tape drive worked fine. =A0For some reason > the original drive had no problem with the double termination, but > all the replacements did. > > BTW, I thought analyze/media/exer did nothing with disks newer than > about SDI (RAxx) vintage. =A0Have you tried ANA/DISK/READ_CHECK, or > (if V7.3-2 or later) ANA/DISK/SHADOW? =A0If the shadow copies are > finding and replacing a bunch of existing bad blocks, once the > shadow copy completes, the bad blocks should be safely sequestered, > and /read_check or /shadow should come up clean. > > -- > John Santos > Evans Griffiths & Hart, Inc. > 781-861-0670 ext 539 Thanks, I tried ANA/DISK/SHADOW. On both systems, the command eventually terminated with a SYSTEM-F- PARITY. There was no information in the command output file. But DIAG/TRAN showed one error on both DKA0 and DKA100 on *the same logical block at the same time* (there are only two disks in the shadow set) on the problem system. DIAG/TRAN showed one error on DKA100 on the other system. However before a swapped the disks, the dka100 on the non-problem (other) DS10 was not logging any unrecoverable errors. And, I never get errors when I do a tape backup with verify. And, before I swapped the disks I rarely got errors except when merging the shadow set on the problem system. The symptom that started my analysis was the fact that errors were always logged on the problem system when I did a shadowset merge. These errors always arise after the 90% point in the shadowset merge and in ANA/DISK/SHADOW. No errors early ever. ------------------------------ Date: Fri, 22 Feb 2008 07:03:24 -0800 (PST) From: tadamsmar Subject: Re: Errors during shadow set merge Message-ID: <07227626-2a5b-47b9-b525-b09bc78f8a77@s37g2000prg.googlegroups.com> On Feb 21, 8:27=A0pm, John Santos wrote: > Richard B. Gilbert wrote: > > tadamsmar wrote: > > >> On Feb 21, 7:54 am, tadamsmar wrote: > > >>> On Feb 20, 10:19 pm, Michael Austin > >>> wrote: > > >>>> tadamsmar wrote: > > >>>>> On Feb 18, 11:17 pm, Michael Austin > >>>>> wrote: > > >>>>>> tadamsmarwrote: > > >>>>>>> On Feb 18, 5:00 pm, "Richard B. Gilbert" > >>>>>>> wrote: > > >>>>>>>> tadamsmarwrote: > > >>>>>>>>> I noticed I was getting errors when adding a member to a shadow > >>>>>>>>> set. > >>>>>>>>> I have been getting errors during shadow set merges since I boug= ht > >>>>>>>>> this refurb DS10. > >>>>>>>>> Got 109 error today when I remerged after doing an image. =A016 > >>>>>>>>> errors > >>>>>>>>> on DKA0 and 93 on DKA100. > >>>>>>>>> What do you think is causing this? > >>>>>>>>> Are these soft errors? > >>>>>>>>> Here is the log for one: > >>>>>>>>> **** V3.4 =A0********************* ENTRY 1667 > >>>>>>>>> ******************************** > >>>>>>>>> Logging OS =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A01. Ope= nVMS > >>>>>>>>> System Architecture =A0 =A0 =A0 =A0 =A0 =A0 =A0 2. Alpha > >>>>>>>>> OS version =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 V= 7.3-2 > >>>>>>>>> Event sequence number =A0 =A0 =A0 =A0 11474. > >>>>>>>>> Timestamp of occurrence =A0 =A0 =A0 =A0 =A0 =A0 =A018-FEB-2008 0= 9:52:48 > >>>>>>>>> Time since reboot =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A077 Day(= s) 1:23:46 > >>>>>>>>> Host name =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0EESD > >>>>>>>>> System Model =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Alp= haServer DS10 617 MHz > >>>>>>>>> Entry Type =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A01. Dev= ice Error > >>>>>>>>> ---- Device Profile ---- > >>>>>>>>> Unit =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 $1$DKA0 > >>>>>>>>> Product Name =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ATL= AS10K2-TY184L > >>>>>>>>> Vendor =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 QUANTUM > >>>>>>>>> -- Driver Supplied Info - > >>>>>>>>> Device Firmware Revision =A0 =A0 =A0 =A0 =A0 =A0 DA40 > >>>>>>>>> VMSSCSIError Type =A0 =A0 =A0 =A0 =A0 =A0 =A0 5. Extended Sense = Data from Device > >>>>>>>>> SCSIID =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00 > >>>>>>>>> SCSILUN =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x00 > >>>>>>>>> SCSISUBLUN =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00 > >>>>>>>>> Port Status =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00000001 =A0NORMAL =A0-= =A0normal successful > >>>>>>>>> completion > >>>>>>>>> SCSICommand Opcode =A0 =A0 =A0 =A0 =A0 =A0 x28 =A0Read (10 byte = command) > >>>>>>>>> Command Data > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x= 00 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x= 02 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x= 06 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x= 44 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x= 8A > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x= 00 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x= 00 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x= 01 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x= 00 > >>>>>>>>> SCSIStatus =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x02 =A0Check = Condition > >>>>>>>>> Remaining Byte Length =A0 =A0 =A0 =A0 =A0 =A018. > >>>>>>>>> --- Device Sense Data --- > >>>>>>>>> Error Code =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0xF0 =A0Cur= rent Error > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Information Bytes are Valid > >>>>>>>>> Segment # =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00 > >>>>>>>>> Information Byte 3 =A0 =A0 =A0 =A0 =A0 =A0 =A0x02 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0Byte 2 =A0 =A0 =A0 =A0 =A0 =A0 =A0x06 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0Byte 1 =A0 =A0 =A0 =A0 =A0 =A0 =A0x44 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0Byte 0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x8A =A0= LBA: =A0x0206448A > >>>>>>>>> Sense Key =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x03 =A0Med= ium Error > >>>>>>>>> Additional Sense Length =A0 =A0 =A0 =A0 x0A > >>>>>>>>> CMD Specific Info Byte 3 =A0 =A0 =A0 =A0x21 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Byte 2 =A0 =A0 =A0 =A0x23 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Byte 1 =A0 =A0 =A0 =A0x3E > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Byte 0 =A0 =A0 =A0 =A0xD4 > >>>>>>>>> ASC & ASCQ =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x1100 =A0ASC = =A0=3D =A0 x0011 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 ASCQ =3D =A0 x0000 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Unrecovered Read Error > >>>>>>>>> FRU Code =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x00 > >>>>>>>>> Sense Key Specific Byte 0 =A0 =A0 =A0 x80 =A0Valid Sense Key Dat= a > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Byte 1 =A0 =A0 =A0 x00 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Byte 2 =A0 =A0 =A0 xA0 > >>>>>>>>> ----- Software Info ----- > >>>>>>>>> UCB$x_ERTCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 16. Retries= Remaining > >>>>>>>>> UCB$x_ERTMAX =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 16. Retries= Allowable > >>>>>>>>> IRP$Q_IOSB =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x0000000000000000 > >>>>>>>>> UCB$x_STS =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x08021810 =A0Online > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Software Valid > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Unload At Dismount > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Volume is Valid on the local > >>>>>>>>> node > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Unit supports the Extended > >>>>>>>>> Function bit > >>>>>>>>> IRP$L_PID =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x82640450 =A0Requestor= "PID" > >>>>>>>>> IRP$x_BOFF =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 4416. Byte Pa= ge Offset > >>>>>>>>> IRP$x_BCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0512. Trans= fer Size In Byte(s) > >>>>>>>>> UCB$x_ERRCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 32. Errors = This Unit > >>>>>>>>> UCB$L_OPCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A022716780. QIO's This = Unit > >>>>>>>>> ORB$L_OWNER =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00010004 =A0Owners UIC > >>>>>>>>> UCB$L_DEVCHAR1 =A0 =A0 =A0 =A0 =A0 =A0x1C4D4008 =A0Directory Str= uctured > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 File Oriented > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Sharable > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Available > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Mounted > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Error Logging > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Capable of Input > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Capable of Output > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Random Access > > >>>>>>>> Is that system under service contract? =A0If so, ask to have the > >>>>>>>> drive > >>>>>>>> replaced! > >>>>>>>> I hope you have a recent backup that's readable. =A0 If you don't= , > >>>>>>>> try to > >>>>>>>> make one! =A0Right now!!!! > >>>>>>>> It could be just a single bad block. =A0It could also be all the > >>>>>>>> warning > >>>>>>>> you are going to get that the disk is failing! =A0Once you hear > >>>>>>>> that "loud > >>>>>>>> scraping sound" it's all over!! > >>>>>>>> If you don't have a service contract, order a replacement disk > >>>>>>>> and get a > >>>>>>>> rush on the delivery! > >>>>>>>> Meanwhile, keep an eye on the disk. =A0If you get more error > >>>>>>>> messages with > >>>>>>>> different LBAs it means the situation is deteriorating and you > >>>>>>>> may have > >>>>>>>> an emergency within a few minutes or hours.- Hide quoted text - > >>>>>>>> - Show quoted text - > > >>>>>>> Are these hard or soft errors? > > >>>>>> These are generally HARD errors - do what he said and order a disk > >>>>>> ASAP.- Hide quoted text - > > >>>>>> - Show quoted text - > > >>>>> I am skeptical that its the disks (In my original message, I indicat= ed > >>>>> that I get errors for both disks) > > >>>>> I have had this problem for a while. =A0I have run: > > >>>>> ANAL/MEDIA/EXER > > >>>>> on the disks and found no errors. > > >>>>> These error bursts only happen when I do a shadow set merge. > > >>>>> I suspect something about the SCSI, or connections, that is stressed= > >>>>> by a merge. > > >>>> I still suspect the media - and I can back it up with 24 years of > >>>> reading error logs... can you?- Hide quoted text - > > >>>> - Show quoted text - > > >>> No. > > >>> Here is a log of my recent findings > > >>> Merged the shadow set, getting 16 errors on DKA0 and 83 errors on > >>> DKA100. > > >>> Did a ANALYZE/MEDIA/EXER=3DFULL of DKA100 and found 1 bad block. =A0Go= t a > >>> good many errors logged during the ANALYZE. > > >>> Merged the shadow set, getting 16 errors on DKA0 and 5 errors on > >>> DKA100. > > >>> Did a ANALYZE/MEDIA/EXER=3DFULL of DKA0 and found 0 bad blocks. =A0Got= a > >>> good 0 errors logged during the ANALYZE. > > >>> Merged the shadow set, getting 4 errors on DKA0 and 19 errors on > >>> DKA100. > > >>> I will swap out one of the disks and give it a try. =A0Put in a disk > >>> that is logging no errors at its current location.- Hide quoted text -= > > >>> - Show quoted text - > > >> I swapped the dka100 disks between two DS10s (same model disks). > > >> Then I merged the shadowset on the problem machine. =A0 I got 4 errors > >> on dka100 and 16 on dka0. =A0All indicating unrecoverable. > > >> On the other machine a got about 34 errors on dka100 (most indicating > >> unrecoverable) during the shadowset merge. =A0But I realized that I had= > >> found 1 bad block on it when it it was on the problem machine using > >> ANALYZE. =A0So, I ran ANAL/MEDIA/EXER=3DFULL and found 13 bad blocks. > > >> I suspect there must be more than bad disks on the problem machine, > >> since it got 4 unrecovable errrors (at 2 LBAs) on a disk that had none > >> recently during shadowset merges on the other machine. > > >> BTW, =A0when you do a DIAGNOSE/TRANS/SUMMARY all these errors > >> are listed as SCSI errors, but when you look at the sense data in > >> detailed report, most are identified as medium errors. > > >> I guess will ask the vendor for a couple of disks under the warranty, > >> but I have no confidence that it will solve the problem. =A0Maybe I nee= d > >> the machine replaced. > > > It is possible that you have a problem with a cable, or a host bus > > adapter either as a contributing factor or (less likely) as the whole > > problem. > > Or it could be a problem with SCSI bus termination, either no terminator > or double termination or an extra terminator in the middle or a bad > terminator. =A0We had an old BA350(?) shelf (fast/narrow, gray disks) > that we daisychained an external 8mm tape drive to, worked fine for a > year or two, and then someone inserted a tape upside down or backwards > and busted it. =A0DEC (or maybe Compaq) replaced the drive about 5 times, > they kept failing. =A0Would work fine in a short test but full volume > backups would usually fail. =A0After they replaced the drive about 4 or > 5 times, someone said the magic word "termination", and so I took the > covers off the BA350 and discovered whoever had added the external > tape drive had neglected to remove the internal terminator. =A0After > removing it, the latest "DOA" tape drive worked fine. =A0For some reason > the original drive had no problem with the double termination, but > all the ... > > read more =BB- Hide quoted text - > > - Show quoted text - I looked under the hood of the problem DS10. There is no terminator in the middle. That is, there is one open 80-pin plug-in along the cable. I don't have a terminator for that. I could experiment with connecting a disk there. ------------------------------ Date: Fri, 22 Feb 2008 08:22:19 -0800 (PST) From: tadamsmar Subject: Re: Errors during shadow set merge Message-ID: <8c7cdb0e-4b25-49a8-895d-73b1ba35657a@u69g2000hse.googlegroups.com> On Feb 22, 11:14=A0am, Tad Winters wrote: > tadamsmar wrote innews:07227626-2a5b-47b9-b525-b09bc= 78f8a77@s37g2000prg.googlegroups.com: > > =A0[..snip..] > > > > > I looked under the hood of the problem DS10. =A0There is no terminator > > in the middle. =A0That is, there is one open =A080-pin plug-in along the= > > cable. > > > I don't have a terminator for that. =A0I could experiment with > > connecting a disk there. > > You only terminate at the end of the SCSI bus. =A0In some cases, the last > device on the bus can be configured to terminate, but I have never liked > that. =A0I want to be able to remove the terminator, attach another device= , > and put the terminator on the end. > Again, the SCSI bus needs exactly 1 terminator at the end of the bus. The last device is a tape drive, I think. I guess I would have to check its jumpers against specs (if I can find them) to tell if it is configured to terminate? ------------------------------ Date: Fri, 22 Feb 2008 08:27:02 -0800 (PST) From: tadamsmar Subject: Re: Errors during shadow set merge Message-ID: <81fe4c8a-feed-480f-91ec-b36234e46fa0@64g2000hsw.googlegroups.com> On Feb 21, 8:27=A0pm, John Santos wrote: > Richard B. Gilbert wrote: > > tadamsmar wrote: > > >> On Feb 21, 7:54 am, tadamsmar wrote: > > >>> On Feb 20, 10:19 pm, Michael Austin > >>> wrote: > > >>>> tadamsmar wrote: > > >>>>> On Feb 18, 11:17 pm, Michael Austin > >>>>> wrote: > > >>>>>> tadamsmarwrote: > > >>>>>>> On Feb 18, 5:00 pm, "Richard B. Gilbert" > >>>>>>> wrote: > > >>>>>>>> tadamsmarwrote: > > >>>>>>>>> I noticed I was getting errors when adding a member to a shadow > >>>>>>>>> set. > >>>>>>>>> I have been getting errors during shadow set merges since I boug= ht > >>>>>>>>> this refurb DS10. > >>>>>>>>> Got 109 error today when I remerged after doing an image. =A016 > >>>>>>>>> errors > >>>>>>>>> on DKA0 and 93 on DKA100. > >>>>>>>>> What do you think is causing this? > >>>>>>>>> Are these soft errors? > >>>>>>>>> Here is the log for one: > >>>>>>>>> **** V3.4 =A0********************* ENTRY 1667 > >>>>>>>>> ******************************** > >>>>>>>>> Logging OS =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A01. Ope= nVMS > >>>>>>>>> System Architecture =A0 =A0 =A0 =A0 =A0 =A0 =A0 2. Alpha > >>>>>>>>> OS version =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 V= 7.3-2 > >>>>>>>>> Event sequence number =A0 =A0 =A0 =A0 11474. > >>>>>>>>> Timestamp of occurrence =A0 =A0 =A0 =A0 =A0 =A0 =A018-FEB-2008 0= 9:52:48 > >>>>>>>>> Time since reboot =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A077 Day(= s) 1:23:46 > >>>>>>>>> Host name =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0EESD > >>>>>>>>> System Model =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Alp= haServer DS10 617 MHz > >>>>>>>>> Entry Type =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A01. Dev= ice Error > >>>>>>>>> ---- Device Profile ---- > >>>>>>>>> Unit =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 $1$DKA0 > >>>>>>>>> Product Name =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 ATL= AS10K2-TY184L > >>>>>>>>> Vendor =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 QUANTUM > >>>>>>>>> -- Driver Supplied Info - > >>>>>>>>> Device Firmware Revision =A0 =A0 =A0 =A0 =A0 =A0 DA40 > >>>>>>>>> VMSSCSIError Type =A0 =A0 =A0 =A0 =A0 =A0 =A0 5. Extended Sense = Data from Device > >>>>>>>>> SCSIID =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00 > >>>>>>>>> SCSILUN =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x00 > >>>>>>>>> SCSISUBLUN =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00 > >>>>>>>>> Port Status =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00000001 =A0NORMAL =A0-= =A0normal successful > >>>>>>>>> completion > >>>>>>>>> SCSICommand Opcode =A0 =A0 =A0 =A0 =A0 =A0 x28 =A0Read (10 byte = command) > >>>>>>>>> Command Data > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x= 00 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x= 02 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x= 06 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x= 44 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x= 8A > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x= 00 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x= 00 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x= 01 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x= 00 > >>>>>>>>> SCSIStatus =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x02 =A0Check = Condition > >>>>>>>>> Remaining Byte Length =A0 =A0 =A0 =A0 =A0 =A018. > >>>>>>>>> --- Device Sense Data --- > >>>>>>>>> Error Code =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0xF0 =A0Cur= rent Error > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Information Bytes are Valid > >>>>>>>>> Segment # =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00 > >>>>>>>>> Information Byte 3 =A0 =A0 =A0 =A0 =A0 =A0 =A0x02 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0Byte 2 =A0 =A0 =A0 =A0 =A0 =A0 =A0x06 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0Byte 1 =A0 =A0 =A0 =A0 =A0 =A0 =A0x44 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0Byte 0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x8A =A0= LBA: =A0x0206448A > >>>>>>>>> Sense Key =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x03 =A0Med= ium Error > >>>>>>>>> Additional Sense Length =A0 =A0 =A0 =A0 x0A > >>>>>>>>> CMD Specific Info Byte 3 =A0 =A0 =A0 =A0x21 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Byte 2 =A0 =A0 =A0 =A0x23 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Byte 1 =A0 =A0 =A0 =A0x3E > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Byte 0 =A0 =A0 =A0 =A0xD4 > >>>>>>>>> ASC & ASCQ =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x1100 =A0ASC = =A0=3D =A0 x0011 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 ASCQ =3D =A0 x0000 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Unrecovered Read Error > >>>>>>>>> FRU Code =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x00 > >>>>>>>>> Sense Key Specific Byte 0 =A0 =A0 =A0 x80 =A0Valid Sense Key Dat= a > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Byte 1 =A0 =A0 =A0 x00 > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Byte 2 =A0 =A0 =A0 xA0 > >>>>>>>>> ----- Software Info ----- > >>>>>>>>> UCB$x_ERTCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 16. Retries= Remaining > >>>>>>>>> UCB$x_ERTMAX =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 16. Retries= Allowable > >>>>>>>>> IRP$Q_IOSB =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0x0000000000000000 > >>>>>>>>> UCB$x_STS =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x08021810 =A0Online > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Software Valid > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Unload At Dismount > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Volume is Valid on the local > >>>>>>>>> node > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Unit supports the Extended > >>>>>>>>> Function bit > >>>>>>>>> IRP$L_PID =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 x82640450 =A0Requestor= "PID" > >>>>>>>>> IRP$x_BOFF =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 4416. Byte Pa= ge Offset > >>>>>>>>> IRP$x_BCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0512. Trans= fer Size In Byte(s) > >>>>>>>>> UCB$x_ERRCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 32. Errors = This Unit > >>>>>>>>> UCB$L_OPCNT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A022716780. QIO's This = Unit > >>>>>>>>> ORB$L_OWNER =A0 =A0 =A0 =A0 =A0 =A0 =A0 x00010004 =A0Owners UIC > >>>>>>>>> UCB$L_DEVCHAR1 =A0 =A0 =A0 =A0 =A0 =A0x1C4D4008 =A0Directory Str= uctured > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 File Oriented > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Sharable > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Available > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Mounted > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Error Logging > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Capable of Input > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Capable of Output > >>>>>>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 Random Access > > >>>>>>>> Is that system under service contract? =A0If so, ask to have the > >>>>>>>> drive > >>>>>>>> replaced! > >>>>>>>> I hope you have a recent backup that's readable. =A0 If you don't= , > >>>>>>>> try to > >>>>>>>> make one! =A0Right now!!!! > >>>>>>>> It could be just a single bad block. =A0It could also be all the > >>>>>>>> warning > >>>>>>>> you are going to get that the disk is failing! =A0Once you hear > >>>>>>>> that "loud > >>>>>>>> scraping sound" it's all over!! > >>>>>>>> If you don't have a service contract, order a replacement disk > >>>>>>>> and get a > >>>>>>>> rush on the delivery! > >>>>>>>> Meanwhile, keep an eye on the disk. =A0If you get more error > >>>>>>>> messages with > >>>>>>>> different LBAs it means the situation is deteriorating and you > >>>>>>>> may have > >>>>>>>> an emergency within a few minutes or hours.- Hide quoted text - > >>>>>>>> - Show quoted text - > > >>>>>>> Are these hard or soft errors? > > >>>>>> These are generally HARD errors - do what he said and order a disk > >>>>>> ASAP.- Hide quoted text - > > >>>>>> - Show quoted text - > > >>>>> I am skeptical that its the disks (In my original message, I indicat= ed > >>>>> that I get errors for both disks) > > >>>>> I have had this problem for a while. =A0I have run: > > >>>>> ANAL/MEDIA/EXER > > >>>>> on the disks and found no errors. > > >>>>> These error bursts only happen when I do a shadow set merge. > > >>>>> I suspect something about the SCSI, or connections, that is stressed= > >>>>> by a merge. > > >>>> I still suspect the media - and I can back it up with 24 years of > >>>> reading error logs... can you?- Hide quoted text - > > >>>> - Show quoted text - > > >>> No. > > >>> Here is a log of my recent findings > > >>> Merged the shadow set, getting 16 errors on DKA0 and 83 errors on > >>> DKA100. > > >>> Did a ANALYZE/MEDIA/EXER=3DFULL of DKA100 and found 1 bad block. =A0Go= t a > >>> good many errors logged during the ANALYZE. > > >>> Merged the shadow set, getting 16 errors on DKA0 and 5 errors on > >>> DKA100. > > >>> Did a ANALYZE/MEDIA/EXER=3DFULL of DKA0 and found 0 bad blocks. =A0Got= a > >>> good 0 errors logged during the ANALYZE. > > >>> Merged the shadow set, getting 4 errors on DKA0 and 19 errors on > >>> DKA100. > > >>> I will swap out one of the disks and give it a try. =A0Put in a disk > >>> that is logging no errors at its current location.- Hide quoted text -= > > >>> - Show quoted text - > > >> I swapped the dka100 disks between two DS10s (same model disks). > > >> Then I merged the shadowset on the problem machine. =A0 I got 4 errors > >> on dka100 and 16 on dka0. =A0All indicating unrecoverable. > > >> On the other machine a got about 34 errors on dka100 (most indicating > >> unrecoverable) during the shadowset merge. =A0But I realized that I had= > >> found 1 bad block on it when it it was on the problem machine using > >> ANALYZE. =A0So, I ran ANAL/MEDIA/EXER=3DFULL and found 13 bad blocks. > > >> I suspect there must be more than bad disks on the problem machine, > >> since it got 4 unrecovable errrors (at 2 LBAs) on a disk that had none > >> recently during shadowset merges on the other machine. > > >> BTW, =A0when you do a DIAGNOSE/TRANS/SUMMARY all these errors > >> are listed as SCSI errors, but when you look at the sense data in > >> detailed report, most are identified as medium errors. > > >> I guess will ask the vendor for a couple of disks under the warranty, > >> but I have no confidence that it will solve the problem. =A0Maybe I nee= d > >> the machine replaced. > > > It is possible that you have a problem with a cable, or a host bus > > adapter either as a contributing factor or (less likely) as the whole > > problem. > > Or it could be a problem with SCSI bus termination, either no terminator > or double termination or an extra terminator in the middle or a bad > terminator. =A0We had an old BA350(?) shelf (fast/narrow, gray disks) > that we daisychained an external 8mm tape drive to, worked fine for a > year or two, and then someone inserted a tape upside down or backwards > and busted it. =A0DEC (or maybe Compaq) replaced the drive about 5 times, > they kept failing. =A0Would work fine in a short test but full volume > backups would usually fail. =A0After they replaced the drive about 4 or > 5 times, someone said the magic word "termination", and so I took the > covers off the BA350 and discovered whoever had added the external > tape drive had neglected to remove the internal terminator. =A0After > removing it, the latest "DOA" tape drive worked fine. =A0For some reason > the original drive had no problem with the double termination, but > all the replacements did. > > BTW, I thought analyze/media/exer did nothing with disks newer than > about SDI (RAxx) vintage. =A0Have you tried ANA/DISK/READ_CHECK, or > (if V7.3-2 or later) ANA/DISK/SHADOW? =A0If the shadow copies are > finding and replacing a bunch of existing bad blocks, once the > shadow copy completes, the bad blocks should be safely sequestered, > and /read_check or /shadow should come up clean. > > -- > John Santos > Evans Griffiths & Hart, Inc. > 781-861-0670 ext 539 ANAL/DISK/READ does not give a parity error, but ANAL/DISK/SHADOW reliably gives a parity error at the same LBA. Does that mean that the parity error is in free space, not in a file? ------------------------------ Date: Fri, 22 Feb 2008 08:04:58 -0800 (PST) From: tadamsmar Subject: how to check firmware version? Message-ID: <9233c3a4-88af-4c28-9811-f6a1771822b1@64g2000hsw.googlegroups.com> How do you check the firmware version. Is there a way to do it with your system up? I have VMS 7.2-3 ------------------------------ Date: Fri, 22 Feb 2008 08:13:45 -0800 (PST) From: DaveG Subject: Re: how to check firmware version? Message-ID: <0e6d0309-614d-4c2b-a0fe-ce0157f35dc3@e10g2000prf.googlegroups.com> On Feb 22, 10:04=A0am, tadamsmar wrote: > How do you check the firmware version. > > Is there a way to do it with your system up? > > I have VMS 7.2-3 One way to check f/w version: $ana/sys SDA> clue config (then look for console ver on first screen) ------------------------------ Date: 22 Feb 2008 17:19:30 +0200 From: vax@chclu.chemie.uni-konstanz.de () Subject: Re: how to check firmware version? Message-ID: <47bef612@merkur.rz.uni-konstanz.de> In article <9233c3a4-88af-4c28-9811-f6a1771822b1@64g2000hsw.googlegroups.com>, tadamsmar writes: |>How do you check the firmware version. |> |>Is there a way to do it with your system up? |> |>I have VMS 7.2-3 |> mc sys$etc:scsi_info eberhard ------------------------------ Date: Fri, 22 Feb 2008 11:59:58 -0500 From: "Richard B. Gilbert" Subject: Re: how to check firmware version? Message-ID: <47BEFF8E.3080703@comcast.net> tadamsmar wrote: > How do you check the firmware version. > > Is there a way to do it with your system up? > > I have VMS 7.2-3 Yes. See HELP LEXICAL F$GETSYI. ------------------------------ Date: 22 Feb 2008 07:39:49 -0600 From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) Subject: Re: how to process/produce un*x 'diff' formats ? Message-ID: In article <932eb794-f1d2-4b5d-a068-822ed9796fb7@q78g2000hsh.googlegroups.com>, Pierre writes: > hi, > > un*x people do like to send modification of source files in so called > 'diff' unified format > http://en.wikipedia.org/wiki/Diff#Unified_format > > I'm building a 'portable' un*x programs and I have a few of such files > to process in order to have the the lastest modification posted by > some guy. > > do you have any idea of how to process such files on VMS ? and how to > produce mine to give them VMS code to include into their common code ? These files can be processed by utilities available from gnu. There have been ports of these utilities in the past, and if the current port won't rnu on VMS, fixing it is generally small work. Or you can fix the source files on a nearby eunichs system and copy the results to VMS. ------------------------------ Date: 22 Feb 2008 10:41:30 -0600 From: burley+news@encompasserve.org (Graham Burley) Subject: Re: Iffy DCL IF Message-ID: <7kS4cGHv4H7U@eisner.encompasserve.org> In article , norm.raphael@metso.com writes: > Are you planning to report it? I've had a response from dcl at hp.com to the effect that they'll consider generating a warning message re the data lines in a future release of DCL. ------------------------------ Date: Fri, 22 Feb 2008 08:45:29 -0500 From: norm.raphael@metso.com Subject: Re: LK-201 error question Message-ID: This is a multipart message in MIME format. --=_alternative 004B8F80852573F7_= Content-Type: text/plain; charset="US-ASCII" That thought had occurred to me. To the best of my ability to read the markings on the back, they are the same as a working LK201. Do you know where a variant matrix might be available? David J Dachtera wrote on 02/21/2008 09:07:29 PM: > norm.raphael@metso.com wrote: > > > > I just got a replacement LK-201 Keyboard and plugged it > > into a VT-320 and got a Keyboard error 4 message and > > all four leds on the keyboard light up solid. > > > > What is it telling me? > > Is it telling you that you need a different variant of the LK201? > > My VT320 here came with an LK201PE. Both are still in the original > cartons, though I have used them in the past, just not recently. > > David J Dachtera > DJE Systems --=_alternative 004B8F80852573F7_= Content-Type: text/html; charset="US-ASCII"
That thought had occurred to me.
To the best of my ability to read the markings on the back, they are the same as a working LK201.
Do you know where a variant matrix might be available?

David J Dachtera <djesys.no@spam.comcast.net> wrote on 02/21/2008 09:07:29 PM:

> norm.raphael@metso.com wrote:
> >
> > I just got a replacement LK-201 Keyboard and plugged it
> > into a VT-320 and got a Keyboard error 4 message and
> > all four leds on the keyboard light up solid.
> >
> > What is it telling me?
>
> Is it telling you that you need a different variant of the LK201?
>
> My VT320 here came with an LK201PE. Both are still in the original
> cartons, though I have used them in the past, just not recently.
>
> David J Dachtera
> DJE Systems
--=_alternative 004B8F80852573F7_=-- ------------------------------ Date: Fri, 22 Feb 2008 08:55:12 -0500 From: JF Mezei Subject: Re: LK-201 error question Message-ID: <47bed475$0$30974$c3e8da3@news.astraweb.com> norm.raphael@metso.com wrote: > > That thought had occurred to me. > To the best of my ability to read the markings on the back, they are the > same as a working LK201. > Do you know where a variant matrix might be available? I know that LK201s have worked on VT220s and VT320s interchangeably. I have some LK201-BQ a rare bread. The letters indicate the language variant. The BQ was for Bilingual-Québec. French letter layout, but english ALL-IN-1 Mnemonics. ------------------------------ Date: Fri, 22 Feb 2008 09:26:45 -0500 From: norm.raphael@metso.com Subject: Re: LK-201 error question Message-ID: This is a multipart message in MIME format. --=_alternative 004F56D7852573F7_= Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable JF Mezei wrote on 02/22/2008 08:55:12 AM: > norm.raphael@metso.com wrote: > >=20 > > That thought had occurred to me. > > To the best of my ability to read the markings on the back, they are=20 the > > same as a working LK201. > > Do you know where a variant matrix might be available? >=20 > I know that LK201s have worked on VT220s and VT320s interchangeably. >=20 > I have some LK201-BQ a rare bread. The letters indicate the language > variant. The BQ was for Bilingual-Qu=E9bec. French letter layout, but > english ALL-IN-1 Mnemonics. These are all en Anglais ;) . --=_alternative 004F56D7852573F7_= Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable
JF Mezei <jfmezei.spamnot@vaxination.ca> wrote on 02/22/2008 08:55:12 AM:

> norm.raphael@metso.com wrote:
> >
> > That thought had occurred to me.
> > To the best of my ability to read the markings on the back, they are the
> > same as a working LK201.
> > Do you know where a variant matrix might be available?
>
> I know that LK201s have worked on VT220s and VT320s interchangeably. >
> I have some LK201-BQ a rare bread. The letters indicate the language > variant. The BQ was for Bilingual-Qu=E9bec. French letter layout, but<= br> > english ALL-IN-1 Mnemonics.

These are all en Anglais  ;) . --=_alternative 004F56D7852573F7_=-- ------------------------------ Date: Fri, 22 Feb 2008 03:08:17 -0800 (PST) From: IanMiller Subject: Re: Microsoft pro says OpenVMS best OS ever invented! Message-ID: Readers of OpenVMS.Org have known this for nearly a week. See http://www.openvms.org/stories.php?story=08/02/17/5922249 for some good comments by Keith Cayemberg ------------------------------ Date: Fri, 22 Feb 2008 03:10:47 -0800 (PST) From: IanMiller Subject: Re: Microsoft pro says OpenVMS best OS ever invented! Message-ID: On Feb 22, 2:33 am, JF Mezei wrote: > > Note the use of past tense. Digital is past tense - get used to it. As I replied to the article. HP OpenVMS is still the best operating system in the world. ------------------------------ Date: Fri, 22 Feb 2008 04:32:02 -0800 (PST) From: AEF Subject: Re: Microsoft pro says OpenVMS best OS ever invented! Message-ID: <8f11ed26-c0a0-4c64-8525-09c42fdf2d36@s13g2000prd.googlegroups.com> On Feb 22, 7:10 am, IanMiller wrote: > On Feb 22, 2:33 am, JF Mezei wrote: > > > > > Note the use of past tense. > > Digital is past tense - get used to it. > > As I replied to the article. HP OpenVMS is still the best operating > system in the world. C'mon. All operating systems were invented in the past. In fact, all _inventions_ were invented in the past. That's how "past" works. AEF ------------------------------ Date: Fri, 22 Feb 2008 04:56:46 -0800 (PST) From: Hein RMS van den Heuvel Subject: Re: Oracle 10.2.0.2 on my OpenVMS HP Integrity Message-ID: <5527c596-1b8c-4eb5-af12-6e815f51c774@u72g2000hsf.googlegroups.com> On Feb 22, 1:42=A0am, andrew...@gmail.com wrote: > Hi, > I have just installed Oracle 10.2.0.2 on my OpenVMS HP Integrity > server. > > After installation I used dbca to create a database. I could acces the > database via SQLplus, I > imported data and added users. > > But then I rebooted, and now it does not work. > > I get and error ORA-12170 TNS:Connect time out occurred Did you try a simple start? $ @ORAUSER sid ! where sid is the database instance ID of the target database. $ SQLPLUS "/ AS SYSDBA" SQL> STARTUP > > I have looked at my listener.ora file and tnsnames.ora file but can > find no obvious reason for the timeout. Oracle 10.2 is particular about RMS control file format. They must be 'unix' like: carriage_return. If they are not (DIR/FULL) then on an 8.3 system you can convert them using: $conver/fdl=3D"record; carr carr; form stream_lf" old new > I would like to start Oracle automatically on boot up, and there does > not seem to be an Oracle$startup.com file. > > Any pointers to how to make it work would be appreciated? The Oracle Install guide tries to address this, but doe not provide actual details: http://download.oracle.com/docs/cd/B19306_01/install.102/b25414/postinst.htm= #i1036714 "4.5 Performing Configuration Tasks as the SYSTEM User You must log into a System Administrator account to perform the following configuration task Automating Database Startup and Shutdown (Optional) You can configure the system to automatically start Oracle Database when the system starts up (in your SYSTARTUP procedure) and to shut down Oracle Database when the system shuts down (in your SYSHUTDWN procedure). Automating database startup is optional, but automatic shutdown is recommended because it guards against improper shutdown of the database." Good luck, hein. ------------------------------ Date: Fri, 22 Feb 2008 00:51:42 -0800 (PST) From: Rob Subject: Re: regex within a DCL procedure Message-ID: On Feb 22, 3:42=A0am, "Richard B. Gilbert" wrote: > Tom Linden wrote: > > On Thu, 21 Feb 2008 14:38:39 -0800, Richard B. Gilbert =A0 > > wrote: > > >> You can do that. =A0See LIB$SET_SYMBOL. > > > Not good enough. =A0I want to have user defined lexicals. > > Lots of luck! =A0The basic problem is that DCL.EXE would have to be > modified to recognize that "F$MUMBLE()" is a lexical function, to know > how to parse its arguments and the type of the value it returns. =A0This, > in turn, means that you have to modify DCL.EXE. =A0Last time I looked, the= > license terms prohibited reverse engineering the code. =A0You can, or once= > could, get source listings for DCL but I don't think the source license > allows you to use the code in your own product. > > DCL provides a mechanism for defining commands but not for defining new > lexical functions. =A0I realize that this was terribly short sighted but > that's the way the cookie crumbles! > > What problem are you trying to solve? =A0What is it that you think a new > lexical should do? =A0Why should HP spend the precious time of their > developers in providing the "hooks" that you would need? One thing I did ask for when the Compaq Community site used to be around was the ability to parse command qualifiers for DCL command files. I know you can do $@myfile "/this=3Dthat" and then interpret the the string, but I wanted something more akin to a CLD. I wouldn't then have to remember the sequence and format for 8 parameters, just do @myfile /runtype=3Dmorning /path=3Dmypath:, etc, etc. Rob. ------------------------------ Date: Fri, 22 Feb 2008 06:33:05 -0500 From: "PEN" Subject: Re: Samba and text files Message-ID: Hi Michael, "Michael Moroney" wrote in message news:fpkvr3$8j4$1@pcls6.std.com... >I installed HP's Samba kit on a system and when I try to access a text > file from a PC I get junk. It appears it's accessing the file directly, > bypassing RMS, and the "junk" is the RMS record delimiters. Is there any > way to access the text files as text files? I'm doing this for VMS > software development, where some want to access the VMS files with their > PCs to use source code aware software tools rather than VMS editors. > > Going the other way (for example, creating a file with Notepad) works, > although the files show up as "Stream" format, which is kind of weird, > but I guess that's how PCs store text. > > Is there anything I missed? Samba is useless for what I need, unless I > convert all files to "Stream" format. Simply add the following line to the share stanza (or in the [global] section if you want it for all shares) and Variable Length record formatted files will be processed correctly by Samba: vfs objects = varvfc Regards, Paul ------------------------------ Date: Fri, 22 Feb 2008 17:16:27 +0000 (UTC) From: moroney@world.std.spaamtrap.com (Michael Moroney) Subject: Re: Samba and text files Message-ID: "PEN" writes: >Hi Michael, >> Is there anything I missed? Samba is useless for what I need, unless I >> convert all files to "Stream" format. >Simply add the following line to the share stanza (or in the [global] >section if you want it for all shares) and Variable Length record formatted >files will be processed correctly by Samba: >vfs objects = varvfc Thanks, Paul, but quickly inserting that line in the [global] area of smb.conf and restarting samba had no effect. I'll study the documentation on that later. ------------------------------ End of INFO-VAX 2008.106 ************************