At 16:19 -0800 on 01/12/2014, retired mainframer wrote about Re: z/OS
1.13 PTF apply Issue:
LINKLST datasets that occupy secondary extents at IPL time do not suffer
from this problem. It only arises if the dataset grows into a NEW extent
after the IPL. The problem arises then because the LINKLST DEB was built
when the LINKLST was defined and any attempt by LLA to access the new extent
is flagged as outside the DASD area specified in the DEB.
Whether a LINKLST dataset should not have secondary extents (thus causing
SMPE to fail if the current allocation is insufficient) or should (possibly
resulting in the need for appropriate post-SMPE adjustments) is an
administrative decision, not a technical one.
It's not part of LINKLST but the only dataset I know of that never tolerates
a secondary extent is SYS1.NUCLEUS.
OTOH: You should not be doing SMPE Maintainance to the live system.
If you are going against a maintenance set of SYSRES Volumes as
opposed to the set you are IPL'ed from, going into a secondary extent
is not an issue. Also, if you use PDSE datasets not PDS ones, the
secondary extent issue may not exist (or is less) since as you edit a
file, the old version's space is released back to free space and will
be reused. With PDS, it becomes GAS and only is recovered by doing a
compress.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
