Kyle Stewart
New User
Joined: 18 Jan 2024
Posts: 2
Location: USA
|
|
|
|
I created new Sysplex, CFRM, ARM, BPXMCMDS, SFM, LOGR, WLM CDSes at my production site. I used IXCMIAPU to copy the policies into the CFRM, ARM & SFM CDSes.
We use DASD replication between our production and contingency site so the new, unused CDSes would be there. I updated the COUPLExx member to point at the new CDSes and the existing CFRM Policy (multi-site policy.)
This is according to IBM's manual re: IXCL1DSU & IXCMIAPU in 'MVS Setting Up a Sysplex. We are z/OS 2.3 so no IBM support. Moving to 2.5 in the near future.
Instead of getting an IPL I get:
IXC373I XCF / XES OPTIONAL FUNCTIONS ENABLED:
IXC470I SYSTEM ZUT1TEC1 EFFECTIVE VALUES: INTERVAL=165 OPNOTIFY=168 DEFAULT USER INTERVAL: 165 DERIVED SPIN INTERVAL: 165 DEFAULT USER OPNOTIFY: + 3 COMPUTED FOR: XCF INITIALIZATION
IXC412I SYSPLEX CONFIGURATION IS NOT COMPATIBLE WITH REQUIRED CONFIGURATION
IXC413I MONOPLEX SYSPLEX CONFIGURATION PREVENTED BY PLEXCFG=MULTISYSTEM
IXC413I XCFLOCAL SYSPLEX CONFIGURATION PREVENTED BY PLEXCFG=MULTISYSTEM
IXC214I COUPLESS IS THE CURRENT COUPLE PARMLIB MEMBER
IXC240I IF XCF-LOCAL MODE INITIALIZATION IS DESIRED, RE-IPL WITH
"PLEXCFG=XCFLOCAL" AND "COUPLE=**"
IXC207A XCF INITIALIZATION IS RESTARTED. RESPECIFY COUPLE SYSTEM PARAMETER,
REPLY COUPLE=XX.
Only replying 'r 00,couple=**' to get XCFLOCAL works, but no Sysplex!
I deleted, recreated and just used IXCMIAPU to load the CFRM primary (not both primary & alternate as before--just in case.) I get the same results.
I would really appreciate some insight as this is a critical situation for us.
Thanks,
Kyle |
|
