Some things that may point you in the right direction: D PARMLIB D PROG,APF (assuming you are using PROGxx)
MXI's PARM command ISPF command DDLIST APF Don Imbriale -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Daniel McLaughlin Sent: Monday, May 14, 2007 12:52 PM To: [email protected] Subject: Catalog and APF 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! *********************************************************************** Bear Stearns is not responsible for any recommendation, solicitation, offer or agreement or any information about any transaction, customer account or account activity contained in this communication. *********************************************************************** ---------------------------------------------------------------------- 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
