After a hard down of the coupling facility, TPX did not automatically reconnect after the CF was restarted:
TPXL0010 06/17/09.168 12:53:11.20 SIGNON TERMINAL: TCPTA215 USER: USERXX TPXL0036 06/17/09.168 12:53:13.15 ACB TPXGAT03 SELECTED FOR USER USERXX APPL TSOT1 2398E3C8 TPXL0136 06/17/09.168 12:57:47.34 SESSION ENDED: TSOT1004 TPXGAT03 TSOT1 USERXX 2398E3C8 TPXL0018 06/17/09.168 13:17:55.43 TIMEOUT: USERID: USERXX TERMID: TCPTA215 1 15 20 L TPXL0036 06/17/09.168 13:33:37.45 ACB TPXGAT02 SELECTED FOR USER USERXX APPL TSOT1 2398E3C8 TPXL5125 06/17/09.168 13:50:14.59 CF-EVT-EXIT: TPXLTDA CONNECTIVITY LOST, STRUCT TPX_PLEXTPXT TPXL5130 06/17/09.168 13:50:15.71 CF-REQ: Func=0000, Rc=00000000, Rsn=00000000, Lst#=0000, Enty= TPXL5132 06/17/09.168 13:50:15.71 CF Disconnect/Fail - Rc=00000000 Rsn=00000000 TPXL5503 06/17/09.168 13:50:16.69 XCF Disconnect - Group=TPXT Member=TPXLTDA TPXL0050 06/17/09.168 13:55:45.98 LOSTERM EXIT ENTERED FOR SESSION TCPTA215 SB: 2398EAE8, REASON 20, UNCONDITIONAL ERMINATION TPXL0025 06/17/09.168 13:55:45.98 LOGOFF TERMINAL: TCPTA215 2398EAE8 TPXL0010 06/17/09.168 13:55:45.98 SIGNOFF TERMINAL: TCPTA215 USER: USERXX
TPX 5.2 supports a system-managed rebuild of the Coupling Facility. This is an "on-the-fly" occurrence which does not actually cause a hard disconnect.
A hard disconnect requires TPX to issue a second connect to the CF. That is not available with TPX 5.2.
Once the TPXL5132 CF Disconnect/Fail message occurs in TPX 5.2, the only possible recovery is to recycle TPX, since TPX 5.2 does not support user-managed rebuild.
As of TPX 5.3, the product has been enhanced to keep generic resource TPX instances active when the coupling facility structure fails until it is active again. Then the TPX instances will rebuild their portion of the coupling facility structure and allow sign-ons as usual.