Hi,

it's not easy that all stars are aligned and five wolfs crying at the same 
time but all it's possible... About local fix... it's too... 

OA17708: UNABLE TO IPL SYSTEMS BACK INTO A SYSPLEX, MSGIXC455D AT IPL TIME

APAR status
Closed as program error.

KNOWN IMPACT:
System(s) cannot rejoin a sysplex

Local fix 
.
BYPASS/CIRCUMVENTION:
Ensure all systems are up when ACOUPLE / PSWITCH of the sysplex
CDS is done.
.
RECOVERY ACTION:
[b] IPL system with a system name not previously used in the sysplex [/b]
.  If that is not possible, contact L2 for further assistance.



Error description 
When a system joins a sysplex it is given a slot number and a
sequence number.  The sequence number increase by one for each
system that joins the sysplex.  Moreover, everytime a systems
joins a sysplex it is given a new sequence number.
.
Assume there are 2 systems in a sysplex CDS1 and CDS2 are the
primary and alternate sysplex couple datasets.  SY1 in slot 1
with sequence number 1 and SY2 in slot 2 with sequence number 2.
Now assume SY2 is IPLd 6 times.  SY2 is still in slot 2 and
now has sequence number 8.  Then take SY2 down.  On SY1 format
new sysplex couple datasets CDS3 and CDS4.  Use:
SETXCF COUPLE,TYPE=SYSPLEX,ACOUPLE=(CDS3)
to bring in the new alternate.  XCF assumes each system will
update its own system record.  Problem: SY2 is not active and
therefore cannot update it's information.
SETXCF COUPLE,TYPE=SYSPLEX,PSWITCH
CDS3 is now the primary CDS
SETXCF COUPLE,TYPE=SYSPLEX,ACOUPLE=(CDS4)
SETXCF COUPLE TYPE=SYSPLEX,PSWITCH
CDS4 is now the primary CDS.  The sysplex couple dataset now
reflects a high sequence number of 1!  It nolonger reflects the
high sequence number from SY2 or 8.
When SY2 tries to IPL back into the sysplex it receives:
IXC455D REPLY INTERVAL=NNN SECONDS TO RECHECK CONNECTIVITY OR R
TO  REINITIALIZE XCF
because the sequence number on the system, SY1 is higher than
the sequence number in the sysplex CDS!

----------------------------------------------------------------------
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

Reply via email to