I am curious if anyone else has run across this. in April we installed a new BC12 with 2 JES3 LPARS in a SYSPLEX and 1 internal coupling facility.
first IPL was good, systems cam up using the CF as would be expected with POLICY0 soon after the system were up and verified, an incorrect policy0 was written into the CFRM data set, had the wrong serial number and wrong partion number for the CF LPAR. both systems have been IPL'd successfully multiple times since the install. For reasons not needed for this discussion, when the JES3 systems are IPL'd it is a 'plex wide' ipl, that is, we bring the local down, then the global, then bring up the Global , then the local. works fine for us. NO POR's or deactivatins of the CF have been done since the install. on Sunday last, the IPL's failed, becasue XCF couldn't find the CF - because of the incorrect policy0 overlay I mentioned above. Again, we have been fine since April in this state. the only change we can identify at this time is we took the volumes that the XCF data sets live on OUT of PPRC on Friday. It appears that the flawed policy0 has been lurking in the CFRM data set since the install, but was never activated until this last Sunday. So, we are trying to determine what caused the data set to be used all thought and ideas are welcome. thanks, Joe ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
