There was no change in this processing aside from, actually, detecting some of the additional cases and issuing even more messages (some of these messages might alert you that LLA will not function properly, for example).
Since the beginning of MVS, the only required LNKLST libraries were SYS1.LINKLIB (and later MIGLIB and CSSLIB were added). No other library's being missing caused anything more than a message. I'm sure, given enough formal customer input, we would consider changing the severity of the messages. We will not in all likelihood change to require a response (though we could conceivably provide an option in PROGxx that would ask "please issue WTOR for this case rather than just a WTO") I'm a little confused about "unplanned outage". This might depend on when this was detected. It would not cause an "outage" in and of itself in all likelihood. If it was long enough after the IPL completes to be truly an outage, rather than a failed IPL, you could likely use dynamic LNKLSTto make the missing library available. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- 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
