No, the LNKLSTxx is not processed at all unless you wanted to still
using it despite of IBM recommendations.
I have never used LNKLSTxx and I don't have such member in my PARMLIB
concat.
However... it is both off topic and irrelevant. Irrelevant, because
LNKLSTxx can contain and by default contains PDSE's.
--
Radoslaw Skorupka
Lodz, Poland
W dniu 03.02.2026 o 16:19, Seymour J Metz pisze:
The IPL link list is only from LNKLSTxx; PROGxx is processed later.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
________________________________________
From: IBM Mainframe Discussion List<[email protected]> on behalf of Radoslaw
Skorupka<[email protected]>
Sent: Tuesday, February 3, 2026 9:22 AM
To:[email protected] <[email protected]>
Subject: Re: Do you still have to add PDS/e separately at IPL in lnklst
External Message: Use Caution
W dniu 02.02.2026 o 16:02, Lizette Koehler pisze:
I was told at IPL time that during nip My Link list should only contain PDS
data sets. That PDSE data sets should be added later with a separate SETPROG
command.
Is that still a true process?
I was told that in order to do rebuilds dynamically on the Link List containing
PDSE's, it needs to be done shortly after nip processing.
If that is no longer true when did the restriction get lifted?
I'm pretty sure you have some PDSE's on you LNKLST already.
For yeeears IBM provide SYS1.SIEALNKE, SYS1.SIEAMIGE, SYS1.SHASLNKE and
many other libraries which should be on LNKLST concatenation and by
default those libraries are out in PROGxx, which is read during IPL.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
