Edward Jaffe wrote:
McKown, John wrote:
I know that I can dynamically update the Linklist to add or delete
datasets. The question is, how many times? I know that the IPL linklist
stays around for the duration. But if I dynamically update the lnklst,
find a problem, then dynamically update again, is the "replaced"
linklist eliminated entirely (assuming no job is using it)?
Every new LNKLST set is given a new name. Old ones are not "replaced".
Rather, new ones are activated. Once activated, all new address spaces
will use it. Existing address spaces continue to use whatever LNKLST
SET they're currently using. To force an already-running address space
to use your newly-activated LNKLST SET, use SETPROG LNKLST,UPDATE (at
your own risk).
Oops. Sorry. I see you are asking about storage occupancy for
no-longer-used LNKLST sets.
My understanding is that the storage occupied by a no-longer-in-use
LNKLST set is NOT released. This is based on empirical observation that
the old names still appear in the OCO control blocks that represent
LNKLST sets. If you run a utility like SHOWMVS or MXI, you will still
see the old LNKLST sets listed with zero address spaces using them.
But, Peter will have to say for sure. The code is OCO. :-(
--
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
