[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxaxp::vmsnotes

Title:	VAX and Alpha VMS
Notice:	This is a new VMSnotes, please read note 2.1
Moderator:	VAXAXP::BERNARDO

Created:	Wed Jan 22 1997
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	703
Total number of notes:	3722

408.0. "%LIBRAR-F-MHDERR, module header error" by ZPOVC::NWE () Wed Apr 02 1997 02:14

Hi

Customer has a fortran object library, compiled on old vax machine.
Old machine conf:

VAX-11 7/50
Fortran 3.1-23
Librarian v3
Customer don't know OpenVMS version

Now he copied this library to new machine and link fortran program
with this library. He get the following error message:

	LINK-W-READERR error reading xxxx.olb
	-LBR-E-INVRA Invalid RSA
	...
	LINK-W-NOEOM No end of module record xxxx.olb

$ lib/list/fu xxxx.olb
..
.

%LIBRAR-F-MHDERR, module header error for DIG in xxxx.olb  
invalid RFA

New machine conf:

Open VMS 5.4-2
Fortran 5.6

Any suggestions or pointers are welcome.

regards,

Nwe

T.R	Title	User	Personal Name	Date	Lines
408.1	I'd Recreate -- Consider Product Upgrades, Too...	XDELTA::HOFFMAN	Steve, OpenVMS Engineering	`Wed Apr 02 1997 09:51`	16
	It's likely best if the customer recreates the objects in the library based on the newer Fortran and the original source code, as this will pick up any optimizations added by the newer compiler. Perform a LIBRAR/LIST command on the old system, and post the details. (The library format version is of interest, as is the ability of the older LIBRARIAN to access the original library without errors.) Also find out the OpenVMS or VMS version running on the old system -- and the version the customer upgraded to, V5.4-2, is also considered an antique. Also look for disk and/or file errors, via ANALYZE/RMS and via the librarian commands. If the older LIBRARIAN can access the library, determine how the library was transfered over to the newer release.
408.2		AUSS::GARSON	DECcharity Program Office	`Wed Apr 02 1997 17:42`	5
	re .* And if it turns out that the old LIBRARIAN can access the old library then you might want to extract all the object files and recreate the library (either on the new system or the old depending on what works).
408.3	RE: %LIBRAR-F-MHDERR, module header error	ZPOVC::NWE		`Thu Apr 03 1997 01:38`	20
	Hi Thanks for the replies. Customer bought this particular library around 1983 and she hasn't got any source code for this library. She also can't remember the VMS version of old system and it's no longer available. When I issue libr/list, I could see all the object files but I hit the error, when issuing libr/list/fu. " %LIBRAR-F-MHDERR, module header error for DIG in xxxx.olb invalid RFA" Analyze/rms ***.olb doesn't give any error message either. regards, Nwe
408.4		AUSS::GARSON	DECcharity Program Office	`Thu Apr 03 1997 02:36`	7
	re .3 Yech. Check BACKUPs (of both old system and new system). Try LIB/EXTR=*
408.5	Contact Vendor, Or Other Library Users...	XDELTA::HOFFMAN	Steve, OpenVMS Engineering	`Thu Apr 03 1997 08:53`	17
	:Thanks for the replies. Customer bought this particular library around 1983 :and she hasn't got any source code for this library. She also can't :remember the VMS version of old system and it's no longer available. Is the vendor still around? Otherwise, check the BACKUPs. Its not yet clear if there is a library corruption, or some other corruption occured. :When I issue libr/list, I could see all the object files but I hit the :error, when issuing libr/list/fu. When was the last time this library was used successfully, and what changed since then? (This could be a short time and an obvious cause, or this could represent years of accumulated "bit rot"...)