Mark Pace wrote:
But, did you remember to issue LNKLST UPDATE to pick up the new library
for those address spaces currently running?
No, that I did not do.
I did a LNKLST DEFINE with a copyfrom the old LNKLST.
I did a LNKLST ADD to ad my new link library.
and I did a LNKLST ACTIVATE.
Now I'm not sure what address space(s) to tell about this updated LNKLST.
So I tried
LNKLST UPDATE,JOB=SYSLOGD
LNKLST UPDATE,JOB=LLA
F LLA,REFRESH
SET MPF=(00)
and I still get the same messages.
Since you're adding a new library with new modules, and not removing or
overriding anything, it should be safe enough to just update all address
spaces. I use the following command for this purpose:
SETPROG LNKLST,UPDATE,JOB=*
--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd, Suite 800
Los Angeles, CA 90045
310-338-0400 x318
[EMAIL PROTECTED]
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
