-RMS-F-PLV, unsupported prolog version

Hello, I found an extra RZ28 disc drive in our computer room. I wanted to see what was on it before I put it to good use. I mounted the disc (dkb400:) and it appears to be a system disc from long ago, as it is labelled vaxvmssys.

I did a directory on it and found an lmf$license.ldb file in [vms$common.sysexe]. To see what licenses were in this file, I did a lic list/data=dkb400:[vms$common.sysexe]lmf$license.ldb.

Executing this license command resulted in the error, -RMS-F-PLV, ...

I tried to do a convert/reclaim and it just gave me the same error. Then I tried typing the file, got the same error. I tried backing up the file to a save set, restoring it to a different disc/directory, then retried everything, still getting the same error. The file is 36 blocks in size, so apparently, there is still something in the file. Can anybody help with how to restore this file to good health and accessibility? Thanks!

Re: -RMS-F-PLV, unsupported prolog version

>> -RMS-F-PLV, ...

While officiallyy that just means 'unsupport prolog', in practice it tends to mean that the file is hosed.

Your first steps towards understanding should be DIR/FULL and ANAL/RMSnext steps might be DUMP/HEAD/BLOC=COUNT=4(first block probably shows the corruption, the 4th block woudl have the start of the first data bucket... if any)

If this is a serious problem for you (doesn't sound like it is :-), and you need further help, then please be sure to attach a .TXT file with the output from those commands to a future reply.

>> I tried to do a convert/reclaim

What on earth posessed you to do ever try that? It is a file changing option. You don;t want to use that on anything but a known-to-be-good file, and even then...

HELP/MESSAGE mentions conver/reclaim as a potential victim, not as a solution!

Re: -RMS-F-PLV, unsupported prolog version

rz28 disks are below what's generally found on eBay these days; these 2.1 GB spindles are not worth the shipping costs.

Whole BA350, BA353 and BA356 shelves go out in the trash.

(There are some free-for-shipping StorageWorks shelves out in comp.os.vms right now.)

In practice, these disks get replaced.

Here, you may well have found out why this particular disk was wandering around your machine room loose; it's a bad disk. INITIALIZE /ERASE the disk and try it. If that fails to clear up the issues here, replace the disk brick. (And with a disk as old as an RZ28, I'd not expect much.)

Re: -RMS-F-PLV, unsupported prolog version

To answer Steven's question, I mounted the disc on an Alpha DEC3000 Model 600, running OpenVMS 8.3. Since the disc has the label, AXPVMSSYS, I did not believe that is was a VAX system. Anyway, here is some output from all of your many suggestions to try:

Re: -RMS-F-PLV, unsupported prolog version

Just like I predicted. The file prologue is corrupted, in this case entirely zeroed out.

Did you actually bother to look at the dump data? There seems little point in posting anything more then 'it turns out that the file contents is zeroes'. This file data is hosed.RMS can not invent data out of nothingness.

Re: -RMS-F-PLV, unsupported prolog version

> Ah, I see.> [...]

One of the major defects in the ITRC Forumpoints nonsense is that the people awardingthe points are the people who don't knowenough to solve their own problems, and who,in many cases, can't distinguish a goodanswer from a poor one.

Which is one of the reasons I try to avoidthinking about the whole Forum pointswaste-of-time. When HP hires full-timeprofessional Answer Judges to award thepoints (and I'm not holding my breath), I'llre-examine the situation.