Jerry, Seymour hit the nail on the head. Using LNKLST00 is the “old or non dynamic” method and doesn’t allow PDE. Coding LNKLST as part of the PROGxx concatenation is using dynamic link list and does allow pdse. While I haven’t tried it, I suspect the same would be true if retiring LPALST00 in favor of putting those statements in the PROG concatenation as well.
_______________________________ Dave Jousma Vice President | Director, Platform Engineering Fifth Third Bank | 1830 East Paris Ave, SE | Grand Rapids, MI 49546 ________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Jerry Whitteridge <[email protected]> Sent: Monday, February 2, 2026 12:29:03 PM To: [email protected] <[email protected]> Subject: Re: EXTERNAL Email: Re: [EXTERNAL] Do you still have to add PDS/e separately at IPL in lnklst Lizette - Rex and Dave post finally triggered why we add the PDS/E to the Linklist after IPL. From my memories it relates to the PDS/E's in the Linklist at IPL time can't be dynamically removed from the linklist. We did maintenance by removing libraries and then readding them . Jerry Whitteridge Sr Manager Managed Services Tech Operations & Innovation [email protected] 480 578 7889 -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Pommier, Rex Sent: Monday, February 2, 2026 10:19 AM To: [email protected] Subject: EXTERNAL Email: 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 -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Lizette Koehler Sent: Monday, February 2, 2026 9:03 AM To: [email protected] Subject: [EXTERNAL] Do you still have to add PDS/e separately at IPL in lnklst 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? So PROG00 for nip only has pds datasets. A Minute or two after nip I issue a command to rebuild lnklst and include PDS/e datasets in lnklst. Lizette ---------------------------------------------------------------------- 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 ________________________________ Warning: All e-mail sent to this address will be received by the corporate e-mail system, and is subject to archival and review by someone other than the recipient. This e-mail may contain proprietary information and is intended only for the use of the intended recipient(s). If the reader of this message is not the intended recipient(s), you are notified that you have received this message in error and that any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately. ________________________________ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
