After the modules were updated but before any refresh or compress, LLA would still have the old TTRs. A load would successfully fetch the old module.
If a compress was done, then a refresh is essential since the updated modules and any that followed them in the PDS would have new TTRs. Without a refresh the TTRs would point to "garbage" which the loader would try to interpret as control data and end up in left field somewhere. If the updated modules caused the PDS to grow into a new extent (one that was not allocated at IPL time), after a refresh LLA would experience extent violations because the DEB is built at IPL time. After a compress and a refresh, if all the modules fit into the old extents there should be no problem. All of which begs the question: Why are you updating an active dataset?! Do you change the oil in your car with the engine running? -----Original Message----- From: Paul Schuster [mailto:snip] Sent: Tuesday, February 19, 2008 10:30 AM To: [email protected] Subject: CSVDYLPA DCBPTR=CVTLINK Hello: I have a situation where some load modules in a LINKLIST library were changed. I do not know if an LLA refresh was done. When CSVDYLPA REQUEST=ADD,DCBPTR=CVTLINK attempts to load one of these modules, it encounters this error: IEW4009I FETCH FAILED FOR MODULE xxxxxxx FROM DDNAME -DYNLPA- BECAUSE OF AN I/O ERROR. IEW4005I FETCH FOR MODULE xxxxxxx FROM DDNAME -DYNLPA- FAILED BECAUSE IEWFETCH ISSUED RC 0F AND REASON 40 If I use a STEPLIB pointing to the correct library, and then use the LOAD macro to load the module into storage all is ok. My question: Is there a way using CSVDYLPA to force a read of the real PDS directory and not use the LLA one? Alternatively, what options are there to avoid the IEW4009I problem? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
