Why is my attempt to stop (/P) the XNET address space encountering: xntRCV001E Unexpected program failure encountered xntRCV009I SVC dump invoked RC: 0 RSN: 0 xntXES101E XES IXESXTRM returned error rc 360 rs 000 ?

Document ID : KB000011961
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

The CA Database Management Solutions for DB2 for z/OS  used with the CA Chorus DBA Discipline are installed on a given LPAR.  

Four "product sets" have been defined to run concurrently, with each "product set" consisting of an XMANAGER, XNET, and XNET's

execution spaces for OFA and U2X, and one or more SYSVIEW PMO for DB2 data collectors (IDB2 DC).

 

Question:

Why is my attempt to stop (/P) one of the XNET address spaces failing with the errors: 

xntRCV001E Unexpected program failure encountered

xntRCV009I SVC dump invoked  RC: 0 RSN: 0        

xntXES101E XES IXESXTRM returned error rc 360 rs 000 

(Subsequent attempts to stop (/P) the same address space also fails with the same errors.)

 

Environment:
CA Database Management Solutions for DB2 for z/OS r18.CA Chorus DBA Discipline 4.0z/OS 2.1
Answer:

The SVC abend condition manifested itself due to the XNET  PXNPARM members not having a unique Prefix defined for PXNPARME and OFAPROC started tasks.

Specifying non-unique started tasks (STC ) identifiers can cause storage areas to be incorrectly released when identically “named” STCs all receive the same

stop command from z/OS. This particular STC encountered that condition and the STC shutdown processing was compromised in a way that prevented

shutdown completion.  Modifying the PXNPARM members to have a unique Prefix for PXNPARME and OFAPROC started tasks will correct the Abend condition.

 

 

Additional Information:

In the interim, CANCEL could be used to terminate the started tasks.