<snip> I have seen few vendors suggesting an IPL as requisite if you are doing the product install for first time and If it's upgrade then it's not required.
I am ignorant here. How does this makes a difference ? Why a dynamic update won't work if it's a first install ? </snip> I do not think that the responses I saw addressed the actual questions asked. The responses targeted whether dynamic would work at all and why it might not. Those responses were all correct. To summarize, "it depends". Consider even the case of the product that uses the CSVDYLPA exit to watch for updates via dynamic LPA to modules of interest to the product so that the product can update pointers that it has previously stashed related to the "original" LPA copy of the module, now to be related to the "new" LPA copy. If there is more than one such update, it can be challenging (sometimes impossible, given the performance needs of the product) to make all the updates in such a way that there is no window in which could could be using a mixture of new and old. And writing things so that a mixture of new and old can be expensive and is not always worth it. And that's only for multiple updates to LPA. Some correctly mentioned the concern about a mixture of LPA and LNKLST updates. Having all your parts at the same level can be really important, for obvious reasons. Maybe you can get away with stopping and restarting your product. But when you have parts in LPA, that usually means that things could be within those modules across the stop/restart and that can be complicated. Anyway, back to the OP's questions: nothing comes to mind, unless the product is stashing away information in a repository that persists across IPLs so that "after the first install" the product is relying on data that it built on that first install. Otherwise, whether "first install" or "re-IPL after install", you're just talking about modules and configuration files that (usually) the customer has set up and they often could not tell the difference between "first install" and "re-IPL". "Upgrade" might be able to make do (if the conditions allow) with "dynamic". And if they do, so normally would "first install" (keeping in mind that "dynamic" consumes common storage resources that might conceivably not be available at the time of the dynamic update). Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
