On Mon, 22 Aug 2022 18:32:21 +0000, Pommier, Rex <[email protected]> wrote:
>Hi list, > >I don't know if this is specifically a Syncsort issue or a more generic >confusion about linklist datasets. Here goes. > >We have the SYNCLINK library defined in the linklist. We have installed >Precisely's IEBGENER replacement as part of our install. We determined >SYNCLINK was too small. I allocated a larger version of the library on the >same volume as the current one. We had an IPL scheduled for Saturday so right >before the IPL, I logged in and did the library swap. My process was (as I >thought) pretty standard. > >Shut down LLA and VLF >SETPROG LNKLST,UNALLOCATE >Rename the 2 libraries to get the new, larger one with the right name >SETPROG LNKLST,ALLOCATE >Start LLA and VLF. Nope, not standard. Perhaps before dynamic LNKLST - *and* if you had planned on really doing the rename just before an IPL and not trying to run any jobs. I still see people do it this way though (minus bothering to do the "reallocate" and re-starting LLA). >The operator then needed to run a couple pre-IPL jobs that use IEBGENER. They >failed with >IEW4009I FETCH FAILED FOR MODULE IEBGENER FROM DDNAME -LNKLST- BECAUSE OF AN >I/O ERROR. >IEW4005I FETCH FOR MODULE IEBGENER FROM DDNAME -LNKLST- FAILED BECAUSE >IEWFETCH ISSUED RC 0F AND REASON 40 >CSV031I LIBRARY ACCESS FAILED FOR MODULE IEBGENER, RETURN CODE 24, REASON CODE >26080021, DDNAME *LNKLST* Because the original extents are still known to the LNKLST. > >The manuals were less than helpful. This has been covered countless times on this list, in SHARE presentations and while I didn't just search a manual to see what it says these days, a quick google search did turn up this hit that explains how to do this safely and what NOT to do (what you did) and why it caused a problem. https://www.ibm.com/support/pages/using-dynamic-lnklst-facility-safely-and-properly Don't feel bad, I work with a lot of Jr. sysprogs and it seems everyone gets this wrong and doesn't understand how it is supposed to work until they break break something. Thankfully it's in a sandbox LPAR 99% of the time because they know better than to be mucking with a production system. 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
