IBM Support

TEMS 6.3.0 on z/OS 2.1 receives several *KLVSQ000 QUIESCE MODE HAS BEEN ENTERED FOR FREE EXTENDED STORAGE

Question & Answer


Question

Our R-TEMS 6.3.0 on z/OS 2.1 receives several
*KLVSQ000 QUIESCE MODE HAS BEEN ENTERED FOR FREE EXTENDED STORAGE
and
KLVSQ000 QUIESCE MODE HAS BEEN RELEASED FOR FREE EXTENDED STORAGE
with REGION=0M followed by CT/ENGINE ABEND S0C4 U0000 AT 98788102

Answer

A possible root cause of this issue is that the storage quiesce is related to many reconnections.
Eg. the RKLVLOG may show lot of occurrences like:

2017.087 01:50:35.10 (0000-E22F53C3:ko4tsmgr.cpp,243,"TaskManager::process") Hub connection lost, attempting to reconnect
....
2017.087 01:50:46.68 (0001-E22F53C3:ko4tsmgr.cpp,250,"TaskManager::process") Hub reconnected.

This may happen when an unknown event occurred at the HUB which caused the HUB to mark itself as disconnected:

03/26/17 04:39:21 KDS9142I The TEMS HUB_XXXX is disconnected from the hub TEMS ip.pipe:#1.2.3.4[1918].

Once this occurs the HUB needs to be recycled.
It will no longer sends pings, which is the cause of the RTEMS disconnects.
There are other issues that can occur while the HUB is in this state.
Recycling the HUB should clear up the problem at the RTEMS.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSAVT4","label":"IBM Tivoli Management Services on z\/OS"},"Platform":[{"code":"PF035","label":"z\/OS"}],"Component":"","Version":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
02 February 2018

UID

dwa1377047