IXC466I INBOUND SIGNAL CONNECTIVITY ESTABLISHED WITH SYSTEM IPO2 245
VIA DEVICE 0342 WHICH IS CONNECTED TO DEVICE 0412
IXC466I OUTBOUND SIGNAL CONNECTIVITY ESTABLISHED WITH SYSTEM IPO2 246
VIA DEVICE 0343 WHICH IS CONNECTED TO DEVICE 0413
IXC466I INBOUND SIGNAL CONNECTIVITY ESTABLISHED WITH SYSTEM IPO2 247
VIA DEVICE 0340 WHICH IS CONNECTED TO DEVICE 0410
IXC466I OUTBOUND SIGNAL CONNECTIVITY ESTABLISHED WITH SYSTEM IPO2 248
VIA DEVICE 0341 WHICH IS CONNECTED TO DEVICE 0411
PXM4704 XMANAGER PLEXGRPX GRP= MEM=
PXM4704 XMANAGER PLEXGRPX GRP= MEM=
PXM4705 XMANAGER PLEXGRPX NEW=00 OLD=00 TYPE=0B
PXM4705 XMANAGER PLEXGRPX NEW=00 OLD=00 TYPE=0B
PXM4704 XMANAGER PLEXGRPX GRP= MEM=
PXM4705 XMANAGER PLEXGRPX NEW=00 OLD=00 TYPE=0B
ISG011I SYSTEM IPO2 - JOINING GRS COMPLEX
IXC467I RESTARTING PATHIN DEVICE 0340 256
USED TO COMMUNICATE WITH SYSTEM IPO2
RSN: INTERVENTION REQUIRED
IXC467I RESTARTING PATHIN DEVICE 0342 257
USED TO COMMUNICATE WITH SYSTEM IPO2
RSN: INTERVENTION REQUIRED
IXC467I RESTARTING PATHOUT DEVICE 0341 258
USED TO COMMUNICATE WITH SYSTEM IPO2
RSN: INTERVENTION REQUIRED
IXC467I RESTARTING PATHOUT DEVICE 0343 260
USED TO COMMUNICATE WITH SYSTEM IPO2
RSN: INTERVENTION REQUIRED
*18 IXC409D SIGNAL PATHS BETWEEN IPO2 AND IPO1 ARE LOST. REPLY RETRY OR
SYSNAME=SYSNAME OF THE SYSTEM TO BE REMOVED.
CTM916W PROGRAM CTMCKP WAITING FOR CTM.CKPT 10 SEC
CTM916W PROGRAM CTMCKP WAITING FOR CTM.CKPT 70 SEC
R 18,SYSNAME=IPO2,DOWN
IEE600I REPLY TO 18 IS;SYSNAME=IPO2,DOWN
*19 IXC417D CONFIRM REQUEST TO REMOVE IPO2 FROM THE SYSPLEX. REPLY
SYSNAME=IPO2 TO REMOVE IPO2 OR C TO CANCEL.
R 19,SYSNAME=IPO2
IEE600I REPLY TO 19 IS;SYSNAME=IPO2
IXC101I SYSPLEX PARTITIONING IN PROGRESS FOR IPO2 REQUESTED BY 270
XCFAS. REASON: SYSTEM ENTERED WAIT STATE
*ISG178E GLOBAL RESOURCE SERIALIZATION HAS BEEN DISRUPTED. GLOBAL
RESOURCE REQUESTORS WILL BE SUSPENDED.
IXC808I ELEMENTS FROM TERMINATED SYSTEM IPO2 WERE NOT PROCESSED BY 272
THIS SYSTEM. ARM COUPLE DATA SET IS NOT AVAILABLE TO THIS SYSTEM.
IXC105I SYSPLEX PARTITIONING HAS COMPLETED FOR IPO2 273
- PRIMARY REASON: SYSTEM ENTERED WAIT STATE
- REASON FLAGS: 000022
ISG179I SYSTEM IPO1 INITIATED AUTO RESTART PROCESSING.
ISG175I SYSTEM IPO1 RESTARTED GLOBAL RESOURCE SERIALIZATION.
ISG011I SYSTEM IPO2 - BEING PURGED FROM GRS COMPLEX
ISG013I SYSTEM IPO2 - PURGED FROM GRS COMPLEX
But if I try to activate IPO2 after this, I get same IXC409I message.
Anne D. Crabtree
System Programmer
WV Office of Technology Data Center
1900 Kanawha Blvd East
Bldg 6, Room B-110
Charleston, WV 25305
(304)957-8292
(304)558-1441 fax
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Lizette Koehler
Sent: Sunday, July 12, 2015 12:45 PM
To: [email protected]
Subject: Re: XCF HELP!
A question or two.
Did you wait long enough when the IXC409D was produced?
The system continues and will process the response when entered.
Cross-system coupling facility (XCF) tries to restart the signaling path. If
XCF restores connectivity, the message will be deleted before it is answered.
If XCF cannot fully restore connectivity between the two systems, the system
issues message IXC409D again.
Did you see any other IXC message?
IXC402D or IXC102A, XCF signaling connectivity to the removed system is no
longer relevant and the system deletes the message.
Could you post the RSP to the IXC409D you entered? And any additional messages
that occurred after that?
Not sure what is going on at this point. So, the worst case scenario would be
a sysplex wide COLD start. All LPARs down, then one up with INITIAL, the rest
JOIN. But that is not necessarily what is needed, just what might be the very
worst thing that might need to be done.
Nice webpage with XCF Commands summary
http://www.oocities.org/smtwango/MAINFRAME/MFCOMMANDS/sysplexcmd.html
Thanks
Lizette
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]]
> On Behalf Of Crabtree, Anne D
> Sent: Sunday, July 12, 2015 9:18 AM
> To: [email protected]
> Subject: XCF HELP!
>
> For the first time ever, when shutting down an LPAR in a sysplex, I
> forgot
to
> issue the V XCF,lparname,OFF!
>
> Now, I can't get that LPAR to join the sysplex. Luckily, the
> important
LPAR is
> up. The second LPAR is supposed to be in a sysplex and I am the only
> one using it. It currently has z/os 2.1 running on it.
>
> I keep getting error:
> IXC409D
> SIGNAL PATHS BETWEEN sysname1 AND sysname2 ARE LOST. REPLY RETRY OR
> SYSNAME=SYSNAME OF THE SYSTEM TO BE REMOVED.
>
> I've tried to RETRY and to give it SYSNAME that's down, but nothing helps!
> I'm sure there's some SETXCF command I need to do, but I've never done
> this before so I'm unsure.
>
> I put a question in to IBM but won't hear back till tomorrow. It
> would be
nice
> if someone is out there and can help me!!
>
> Anne D. Crabtree
> System Programmer
> WV Office of Technology Data Center
> 1900 Kanawha Blvd East
> Bldg 6, Room B-110
> Charleston, WV 25305
> (304)957-8292
> (304)558-1441 fax
>
>
----------------------------------------------------------------------
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
