That guess is incorrect. Load modules which need to be accessed during NIP before LNKLST processing are placed into SYS1.NUCLEUS (and also into SYS1.LINKLIB if they are also accessed after LNKLST processing). In effect, the "early LNKLST before the LNKLST has been opened" is SYS1.NUCLEUS.
As I have mentioned before, the best overview of the order of system initialization processing can be obtained by using the IPCS IPLDATA STATUS command against a dump or ACTIVE storage. Jim Mulder -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Pommier, Rex Sent: Monday, February 2, 2026 12:19 PM To: [email protected] Subject: Re: [EXTERNAL] Do you still have to add PDS/e separately at IPL in lnklst Lizette, I sure hope that isn't true. 😊 If it is, my system hasn't been IPLed in years. CEE.SCEERUN2 and TCPIP.SEZALOAD are 2 libraries close to the beginning of my PROG00 member, used at IPL. My uneducated guess is that NIP opens SYS1.LINKLIB outside of finding it in PROG00 because this library is needed to start the SMSPDSE address space. It then builds the full PROGxx concatenation for linklist processing after SMSPDSE is running. Rex ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
