yes I read it, and that would be great if every single client, every
single site had the same wisdom as you, I've worked at sites where I was
not the lead z/os or mvs guy, I had no control over what anyone else
did, and we all paid the consequences updating a live system, acceptable
or not, I change the allocation to not allocate secondary space period.
my main issue was how the space was defined initially using the
serverpac dialog, been burnt a couple times during the SP install, so I
update the space requirements then.
that is for MY site, and my MY way of installing and maintaining a
site IMHO I've seen it done wrong, and things gone bad, and seen it
done a way that's safe and makes sense, that methodology I adopt.
Carmen
On 9/22/2022 4:02 PM, Mark Zelden wrote:
On Thu, 22 Sep 2022 15:24:58 -0500, Carmen Vitullo <[email protected]> wrote:
why is the Health checker issuing a CSVH0979I message LINKLST SET
LNKST00 data sets allocated with secondary space? if what you say is
valid ?
Did you read the explanation (see below)? It is a suggestion. Health
Checker has a very large number of checks and suggestions. Not every
one applies to every shop or every LPAR. Neither of the 2 reasons apply to
the systems I maintain and I disable that check except in my sandbox LPARs
because of the reasons I already stated.
Secondary or no secondary no one better be updating a live LNKLST data
set without a very good reason and thinking about the possible consequences.
All changes to the sysres set go in with rolling IPLs and change control.
Our ISV runtime libs are all on a secondary / tertiary sysres volumes and
are indirectly catalogued just like the IBM OS libraries.
=================================================================
Explanation: CSVH0979I has been placed in the message buffer for each
LNKLST LNKLST set. It lists all data sets with secondary space
defined.
IBM suggests that partitioned data sets (PDS's) in the LNKLST be
allocated with only primary extents, for two reasons. First, a PDS
allocated with only primary space defined has only one extent. This
makes it easier to stay within the 255-extent limit for an active
LNKLST concatenation without having to reallocate data sets with
fewer initial extents. Second, if a PDS will be updated while in
the LNKLST set, it can be extended if it has been allocated using
secondary space. This can cause members to be placed in extents that
did not exist when the LNKLST concatenation was activated. An
attempt to access a member in a new extent causes the requesting
program to abend.
This suggestion does not apply to partitioned data set extended
(PDSE) program libraries. A PDSE program library counts as only one
extent.
=================================================================
Best Regards,
Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
ITIL v3 Foundation Certified
mailto:[email protected]
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
