[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

249.0. "LNK$LIBRARY not seen if not in LNM$SYSTEM_TABLE" by COMICS::EDWARDSN (Dulce et decorum est pro PDP program) Wed Feb 26 1997 06:20

A customer has asserted, but I haven't been able to demonstrate just yet,
that if he has a system owned logical name table which defines the 
logicals LNK$LIBRARY .. LNK$LIBRARY_6 (seven in total, no gaps in the 
numbering) the linker fails to resolve at least one of the libraries.

I asked him to move the definitions into the LNM$SYSTEM_TABLE and the linker
then resolves the undefined symbols.

If he performs a SHO LOG LNK$* from the process which is performing the link
then the logicals can be seen in his system logical table and they are 
pointing to the correct place.

Is it possible that there is a restriction/limitation on the linker which 
means that these logicals MUST be defined in the system table if they are
to be defined at a system level? 
Or is it a bug inasmuch as the linker should be looking in this table for 
the logicals and isn't.

This behaviour has only crept in since an upgrade from VMS 6.1 to VMS 6.2
If you require any more information I'll do my best to provide it.

Any thoughts, suggestions?

Neil

T.R	Title	User	Personal Name	Date	Lines
249.1		MARVIN::CARLINI		`Wed Feb 26 1997 07:35`	7
	What does SHOW LOGICAL LNK$* show (from the process issuing the LINK) when the link operation fails? How has this system-owned logical name table been made visible to the process performing the link? Antonio
249.2		QUARK::LIONEL	Free advice is worth every cent	`Wed Feb 26 1997 08:49`	7
	Yes, this is a restriction of the linker and is even documented, sort of, in the linker manual. The only tables the linker will look in are the standard process, group and system tables - not even the job table. I filed a QAR about this a year or so ago, the response was that the linker's behavior would not change. Steve
249.3	I'd use an options file...	XDELTA::HOFFMAN	Steve, OpenVMS Engineering	`Wed Feb 26 1997 08:57`	3
	(Shared) options files are generally a better approach than LNK$LIBRARY.
249.4		AUSS::GARSON	DECcharity Program Office	`Thu Feb 27 1997 01:15`	6
	re .0 I too QARd this (V5 #1448) but unfortunately the QAR has been deleted from the system so I can't tell you when I did this or what the text of the response was. I have a record that the gist of the response was "NO".
249.5	The linker manual scares me.	COMICS::EDWARDSN	Dulce et decorum est pro PDP program	`Thu Feb 27 1997 04:05`	6
	I thought I'd read the linker manual carefully to attempt to spot any restrictions, maybe I just wasn't reading hard enough. Thanks for the replies. This helps. Neil.
249.6		QUARK::LIONEL	Free advice is worth every cent	`Thu Feb 27 1997 11:29`	5
	If you look at the description of /USERLIBRARY, it says that the default is "to search the process, group and system logical name tables". There is no option to search other tables. Steve