Tried to bring up 1.7 this weekend in PRODUCTION and ran into major issues. While climibing back through the logs we discover things like the network trying to come up using SYS1.SISTCLIB, which is normal, except it and other tasks are showing APF issues. Hmmmmm. It's in there.
1. New volumes cloned from installation set 2. Using VOL(XXXXXX) parameter in APF and LNKLST members 3. Smoke and flames at IPL. Output from failing task shows library pointing back to the installation set. ?? I must have really botched the cloning process and am really baffled about the whole thing. Didn't we used to clone like that and life was good? Or did we clone and clip the new volumes back? Install volumes: xxxMS1, xxxMS2, xxxMS3 Clones: : xxxPS!, xxxPS2, xxxPS3 Thank you all...my boss is getting itchy and it's review time..gulp! ---------------------------------------------------------------------- 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
