First I would try listing the XL path for the program inside linkedit

Eg

LINKEDIT 
>LISTPROG PRQA

PROGRAM        : PRQA
XL LIST        : XLNMV4.PUB
CAPABILITIES   : BA, IA 

This shows you the default path the program will search for it's unresolved XLs. 

Secondly, I would try running the program in different ways 

RUN PRQA.TONY.DEVELOP;Xl="XLNMV4.TONY.DEVELOP"
RUN PRQA.TONY.DEVELOP;XL="XlNMV4.PUB.SWIMS"
RUN PRQA.PUB.SWIMS;Xl="XLNMV4.TONY.DEVELOP"
RUN PRQA.PUB.SWIMS;XL="XLNMV4.PUB.SWIMS" 

This should hopefully isolate whether it's the XL or the program that's got the problem.  Note it's adviseable to fully qualify the XL names. 

and check all the files are released

And also remember that MPE now supports linked libaries 

For example 

LinkEd> listxl xla 

LIBRARY NAME   : XLA
XL LIST        : XLNMV4.PUB.SWIMS HELLO.PE.VESOFT

So if I compile a program to use XLA it will first serach XLA and then XLNMV4 etc for any unresolved externals. 

Best of luck. 


>>> "Leonard S. Berkowitz" <[log in to unmask]> 26/04/01 20:36:27 >>>
In a testing account, a program failed to load with four UNRESOLVED EXTERNALS.
This program does load and run with no problem in production.

I seen that the test XL was created in January, probably some update from the
vendor, as we are testing a new application module.

I can find references (LINKEDIT: LISTXL) to these externals in both the
production XL and the test XL In fact these externals seem to be present in
many, many modules in both XL files.

Why does this program load in production, but not in test?

Thanks.
===================
Leonard S. Berkowitz
Perot Health Care Systems
(Harvard Pilgrim Health Care account)
voice: 617-509-1212
fax:   617-509-3737
pager: 781-226-2431

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *