I generally do the same, but I do keep a backup policy defined just never activated, so really the only other way I think this could happen is if a policy change was pending for some reason, like a structure move from one CF to another, once the policy changes were no longer pending the old or invalid policy became active.? so you say "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 partition number for the CF LPAR." you can define policies all day with no issues until they become started using a SETXCF command, or the PLEX is re initialized I believe. even if the incorrect formatted couple datasets I 'don't think' this would cause your issue, without testing this theory I cannot be 100%.
----- Original Message ----- From: "J Ellis" <[email protected]> To: [email protected] Sent: Monday, July 24, 2017 12:55:35 PM Subject: Re: What casues IPL/XCF to read the CFRM data set for the policy ? the name of the policy never changed, either in the parmlib member or the CFRM data set, the policy wa simply overlaid with the same name, but bad serial number and partition number. and, we ran that way for months. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
