Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!info-vax
From: gihill@THUNDER.UUCP
Newsgroups: mod.computers.vax
Subject: (none)
Message-ID: <8602261853.AA05263@thunder.UUCP>
Date: Wed, 26-Feb-86 13:53:04 EST
Article-I.D.: thunder.8602261853.AA05263
Posted: Wed Feb 26 13:53:04 1986
Date-Received: Sun, 2-Mar-86 19:23:15 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 18
Approved: info-vax@sri-kl.arpa


 Subject: Shareable Image Problem on VMS

We have a home-made shareable image (written in PL/1) that is linked 
to a lot of our applications programs.  Since converting from VMS 3.6 to 
4.0 some of these programs have been acting strangly. e.g. - going into 
infinite loops, or bombing on 'reserved operand fault'.  This always 
occurs where the program makes a call to the VMS Run-time library. 
e.g.- LIB$GET_FOREIGN.  The problem goes away if we link the program 
with .OBJ files instead of the shareable image.
	   
N.B. - We didn't use any fancy LINK options when we created the 
shareable image, only "UNIVERSAL=name" and "GSMATCH=ALWAYS,0,0". 

Could the linker be at fault (unlikely), or do I have to create
shareable images differently on VMS 4.0 ?  Any Hints ??

	Please reply to : watmath!thunder!gihill