1753936 Members
9545 Online
108811 Solutions
New Discussion юеВ

Re: Anal/dis/rep/read

 
Wim Van den Wyngaert
Honored Contributor

Anal/dis/rep/read

I do anal/dis/rep/read on a station with 1 disk.
I get :

ANALDISK-W-READFILE (2126,1,0)
error reading VBN325
SYSTEM-F-PARITY, parity error

I thought this was a temporary file but after a reboot I get the same result (same fileid).

How is this possible ? How can I delete and recreate this file ?

Wim
Wim
30 REPLIES 30
Bojan Nemec
Honored Contributor

Re: Anal/dis/rep/read

Hi,

Can you find out which file is this? Have you try:

$ PIPE DIR/FILE/NOHEAD/COL=1 disc:[*...] | SEA SYS$PIPE "(2126,1,0)"

Or there is an LOSTHEADER for this file?

Bojan
Uwe Zessin
Honored Contributor

Re: Anal/dis/rep/read

You normally get prompted to recover lost files to [SYSLOST]. I would first try and find out a bit more about the file, perhaps it is entered in a directory anyway and you have discovered a bug:

$ dump/header/blocks=count=0/identifier=(11516,7,0) dsa0:
.
Wim Van den Wyngaert
Honored Contributor

Re: Anal/dis/rep/read

Bojan,

Did that with output to a file and searched the file (pipe doesn't allow /window and with your statement you don't see the name).

Result : debug.exe.

Why didn't anal/dis/rep/read report this name and dir did ?

Uwe : I specified /repair. So if it was lost : it should get repaired. No ?
Wim
Uwe Zessin
Honored Contributor

Re: Anal/dis/rep/read

Ah, I see that you did not specifiy /CONFIRM. In that case you don't get prompted and lost files usually get automatically entered in [SYSLOST], but as I already wrote: you might have discovered a bug in VMS.

Have you tried the command I gave you? Did you get any useful output?
.
labadie_1
Honored Contributor

Re: Anal/dis/rep/read

Uwe answer is perfectly correct, but I like DFU
$ mc dfu
search disk/fid=(2126)
labadie_1
Honored Contributor

Re: Anal/dis/rep/read

a little improvement

$ pipe dump/header/block=count=0/ident=(14633,1,0) dra1: | sea sys$pipe "File name:"

gives File name: XXX

:-)

Wim Van den Wyngaert
Honored Contributor

Re: Anal/dis/rep/read

All,

I recreated debug.exe. No more parity errors now.

So, why wasn't the name debug.exe given by anal ?
Wim
labadie_1
Honored Contributor

Re: Anal/dis/rep/read

I find in the doc

ANALYZE/DISK_STRUCTURE Output

------------------------
By default, the Analyze/Disk_Structure utility directs all output to your terminal. If you prefer, you can use the /LIST qualifier to generate a file containing the following information for each file on the disk:

File identification (FID)
File name
Owner
Errors associated with the file


-----------------------

so you shoud add /list to get the file name

source:
http://www.pi-net.dyndns.org/docs/openvms0731/731final/6048/6048pro_005.html
Wim Van den Wyngaert
Honored Contributor

Re: Anal/dis/rep/read

Gerard,

I think this is not correct. /list will give you a list of all files.

Normally, anal will report the file name. For some unknown reason it didn't (corruption ?). The dir command is getting its info elsewere and did find the name.

So, why didn't anal report the file name ?

Wim
Wim