topic Re: Getting %CMS-F-BADLIB in Operating System - OpenVMS

Getting %CMS-F-BADLIB

Ken McNulty — Fri, 25 Feb 2005 06:28:46 GMT

Hi. We are trying to run command $CMS FET UP7200.SCO and we are getting:-
%CMS-F-BADLIB, there is something wrong with your library
-CMS-F-ILLCONREC, illegal control record in element file.
The only info we can get on this relates to running a conversion. But we haven't run a conversion. One clue(?). The system this is happening on is/was a cluster consisting of an Alpha and a Vax. We have removed the Vax. However, we have been running these commands on the Alpha for years - so this is probably a pink salmon. Any thoughts? Thanks in Advance. Ken McNulty

Re: Getting %CMS-F-BADLIB

Ian Miller. — Fri, 25 Feb 2005 06:35:41 GMT

have you tried the CMS VERIFY command? - I think it does repairs too.

Re: Getting %CMS-F-BADLIB

Kris Clippeleyr — Fri, 25 Feb 2005 07:14:29 GMT

Hi,

I think that CMS VERIFY/REPAIR or CMS VERIFY/RECOVER might help.

Regards,
Kris (aka Qkcl)

Re: Getting %CMS-F-BADLIB

Ken McNulty — Fri, 25 Feb 2005 08:43:59 GMT

Hi, Thanks for that, unfortunately it hasn't cleared the problem.
Ken McNulty

Re: Getting %CMS-F-BADLIB

David B Sneddon — Fri, 25 Feb 2005 08:54:58 GMT

Ken,

Is it possible that the VAX and Alpha had different
versions of CMS and you only accessed certain libraries
from the VAX and other libraries from the Alpha?
What version of CMS is/was installed?
Have you tried the CMS CONVERT LIBRARY command?

Regards
Dave

Re: Getting %CMS-F-BADLIB

David B Sneddon — Fri, 25 Feb 2005 08:57:46 GMT

Ken,

Another quick question. Does the CMS VERFIY command
indicate *any* problem at all with the library?

Dave

Re: Getting %CMS-F-BADLIB

Ken McNulty — Fri, 25 Feb 2005 09:17:12 GMT

Hi Dave. It's very possible that there were different libraries on the VAX and Alpha. 'Problem is, no-one knows/remembers. We used to keep different program libraries/executables for different platforms - Vax and Alpha - hence the heterogenous cluster. However, the Vaxes (I refuse to say Vaxen) have long since passed into history, we were just tidying up the last few support remnants. We have been totally Alpha based for 2 or 3 years. That's no to say there isn't something lurking deep in the bowels of some code or DCL somewhere. The programmer who is dealing with this has just gone off for the weekend. He says that the VERIFY says everything's OK and he'll try the CONVERT on Monday.
Cheers,
Ken McNulty

Re: Getting %CMS-F-BADLIB

Jan Schollaert — Fri, 25 Feb 2005 09:18:30 GMT

Hi,

Perhaps this old (1993) article helps.

Cheers,

Jan

SOURCE: Digital Equipment Corporation

PROBLEM:

RESERVEing or FETCHing a CMS element generates the following errors:

%CMS-F-BADLIB, there is something wrong with your CMS library
-CMS-F-ILLCONREC, illegal control record in element file

Issuing a "$ CMS VERIFY/REPAIR" command on the CMS library usually does
not fix the problem.

SOLUTION:

Following are several suggested options one can try to repair the CMS
library:

1) The first option is to look in the correct CMS subdirectory and see
if there are multiple versions of the element data file.

$ DIRECTORY/SIZE [.CMSLIB...]your_corrupt_element_file.ext;*

If there are multiple copies of the file, you need to determine
which copy is the "good" copy. Rename the extra copy/copies and
try your RESERVE/FETCH command again. If your CMS operation works,
then you can remove the extra files from the CMS library area.

2) If there is only one copy of the element data file or the file size
of the element is 0 blocks, your second option is be to restore
this file from a recent BACKUP copy of the library into the correct
CMS library subdirectory, delete the old, "bad" copy, and run a "$
CMS VERIFY/REPAIR" command on the CMS library.

3) It is not normally required that you restore the entire library
from backup. If successful modifications to the element have been
made since the last backup, the library control file may be out of
sync with the element that is restored from backup. If this is the
case, you will get errors during the verification of this element
and will need to restore the entire library from backup to place
the control file in sync with the element data files.

ANALYSIS:

This error indicates corruption in the element data file. It can be
caused by editing of the element data file (i.e. those files that
exist in the CMS$xxx subdirectories within the CMS library directory)
or by a CMS operation being terminated while it is in the process of
writing out a modified element data file.