The most likely explanations are those that were mentioned:
-- a LNKLST data set did, despite your thought, go into a secondary
extent.
Does the output of the CSV_LNKLST_SPACE health check agree that you
have no secondary extents in LNKLST data sets?
-- a LNKLST data set was compressed
If you properly avoid compress without getting the proper (DISP=OLD,
exclusive) serialization, the allocations done on the LNKLST data sets
will prevent that.
But if you simply use DISP=SHR, you're on your own.
There is no reason that I can think of to refresh LLA as long as you have
not done of those things.
Peter Relson
z/OS Core Technology Design
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
