IBM Support

CONDITION(0B100016) SENSE(00000000 0000 000000) and CONDITION(0B100208) SENSE(08380000 0000) after CF upgrade

Troubleshooting


Problem

Client received the STATUS(FAILED) CONDITION(0B100016) SENSE(00000000 0000 000000) and CONDITION(0B100208) SENSE(08380000 0000) messages shortly after Coupling Facility (CF) upgrade.

Symptom

Client installed a new CF.  After the install, GDPS was talking to RADT81, but an hour and a half later they noticed:

06:36:12 GEONVSA RADT81 STATUS(FAILED) CONDITION(0B100208) SENSE(08380000 0000)
06:36:12 GEONVSA 00000000) CPCSNAME(IBM390PS.RADT81)

its prior status had been in service

then they saw:

06:45:53 GEONVSA ING814E BCPII CONNECTION TO NTVB1/AUTHW004 ABORTED BY THE CPC
06:45:53 GEONVSA RADT81/R/IBM390PS.WCFT81 SUPPORT ELEMENT. CAUSE(RESTART_CONS
06:45:53 GEONVSA REASON(OTHER) LASTS(200326033618)

06:52:37 GEONVSA ING815I BCPII CONNECT FROM NTVB1/AUTHW004 TO CPC
06:52:37 GEONVSA RADT81/./IBM390PS.RADT81 RETURNED: ERROR(224)
06:52:44 GEONVSA GEO252E HMC monitoring: RAD2Z
06:52:44 GEONVSA THE HW FUNCTION HAS FAILED FOR RADT81

followed by a good message then a hardware failure

07:01:12 GEONVSA ING815I BCPII CONNECT FROM NTVB1/AUTHW004 TO CPC
07:01:12 GEONVSA RADT81/./IBM390PS.RADT81 RETURNED: SUCCESS
07:01:28 GEONVSA GEO252E HMC monitoring: RAD2Z
07:01:28 GEONVSA THE HW FUNCTION HAS FAILED FOR RADT81

ING815I BCPII CONNECT FROM NTVB1/AUTHW004 TO CPC RADT81/./IBM390PS.RADT81 RETURNED: SUCCESS
GEOTRC AUTLXH NTVB1 PH21004-VPCLXMON: xDR Monitor is started in a MTMM-Si
GEOTRC AUTCPC24 NTVB1 GDPS420-VPCEAOMS: The HW function has failed
GEOTRC AUTCPC24 NTVB1 GDPS420-VPCEAOMS: RADT81 STATUS(FAILED) CONDITION(0B100016) SENSE(00000000 0000 00000000) CPCSNAME(IBM390PS.RADT81)
CNM493I INGMSGU1 : #0000107 : MSGID=GEO252E : GEOMSG GEO252E HMC monitori
GEO252E HMC monitoring: RAD2Z
THE HW FUNCTION HAS FAILED FOR RADT81

 

Cause

Did not carry out SAz/OS BCPii SUSPEND before working on the SE, HMC, or CPC, followed by the SAz/OS BCPii RESUME, either using SAz/OS command or the GDPS dialogs.

Diagnosing The Problem

The SA codes such as "CONDITION(0B100016) SENSE(00000000 0000 000000)" and "CONDITION(0B100208) SENSE(08380000 0000)" are outlined in the SA pubs, as well as the meaning of the ING* messages like ING815I and ING814E.
Detailed information on the codes;
COND 016 HWMCA_DE_INVALID_OBJECT_ID
COND 208 Execution of request was failed by the target support element. This indication is normally accompanied by a condition report that is returned as the error reason, and may also be accompanied by sense data further identifying the cause of the failure.
08380000 Sense code
 Request not executable because of resource or component state incompatibility:                            
 The request is not executable because it is not compatible with the state of a resource or component in the receiver.

1. When doing maintenance on the CPC/SE/HMC, it is strongly recommended that you utilize the GDPS Suspend/Resume feature to avoid BCPii outages when installing SE maintenance.
    From GDPS 'standard action' panel
    Select '1 CPC Ops'
    From next panel "S" for SE operation
    Suspend/Resume is on next panel
2. Important SAzOS maintenance. APARs OA53910, OA58623, OA59265.

Open a HW ticket from the HMC, to have the logs sent to IBM to diagnose and to verify the M/C level of the machine, to make sure it is up to date.
The ISQXCON SUSPEND & RESUME commands are used to manage PROCOPS connections during planned maintenance events for the SE or HMC, see the ISQXCON topic:  https://ibm.biz/BdzfqQ
The INGHWSRV topic discusses this service and diagnostic command that can help you recover from SA-BCPii connection problems, like terminating all BCPii connections, and the use of the SUSPEND and RESUME target hardware parameters, see https://ibm.biz/Bd2spc
Within the INGHWSRV topic, under Usage we have the following comments:
“It is recommended to use SUSPEND as part of an operational procedure before allowing an IBM customer engineer (CE) to perform a repair or a MCL upgrade action which requires an SE reboot or restart. Use RESUME to recover a previously suspended SA-BCPii SE connection, once the IBM CE has ended the repair/upgrade action.
Note, that SA-BCPii application such as GDPS, may provide SUSPEND/RESUME support in their user interfaces or APIs. It is recommended to use the application-provided support in those cases.”
As mentioned earlier, be aware of HIPER APAR OA53910, which if not installed, can result in LPAR(s) being varied out of the sysplex if you hit this condition, see https://www.ibm.com/support/pages/node/3915489
The earlier mentioned APAR that recently closed APAR OA58623 has been flagged as PE, the fixing APAR is OA59230, which at the time this technote was created, is still open and being worked on.

Resolving The Problem

A reboot of the SE did not correct the problem.
In this case, the issue was resolved by carrying out an HMC rediscover.

Document Location

Worldwide

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSWRCJ","label":"IBM Tivoli System Automation for z\/OS"},"ARM Category":[{"code":"a8m0z0000000Ao7AAE","label":"System Automation for z\/OS"}],"ARM Case Number":"","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
02 April 2020

UID

ibm16151809

Page Feedback