Example: Diagnosing a CICS management client interface error using <resultsummary> information

The CICS® management client interface, <resultsummary> element contains return codes that help you determine the cause of errors.

About this task

You have attempted to perform a START action on a CICSManagedRegion resource (that is, a CICSPlex® SM managed CICS region or MAS) using a CICS management client interface PUT request with the following URI and XML body:
http://wmvs2c.mycorp.com:27650/CICSSystemManagement/CICSManagedRegion/IBEUR912?
CRITERIA=CICSNAME%3DDEVRGN1 
 	
	<request>
  		<action name="START"/>
	</request>
Although you receive an HTTP/1.1 200 OK response from the CICS management client interface, no record is returned and the response includes the following <resultsummary> information:
<resultsummary api_function="PERFORM SET" api_response1="1026" api_response1_alt="NOTFOUND" 
api_response2="1301" api_response2_alt="ACTION" recordcount="1"/>

Procedure

To understand the reason for this problem:

  1. Determine the source of the error from the api_function attribute.
    This attribute indicates that the CICS management client interface has attempted to call the PERFORM SET function but the call has failed.
  2. Determine the reason for the failure from the api_response1_alt and api_response2_alt attributes.
    These values are CICSPlex SM EYUDA response and reason codes.

    The EYUDA response has the symbolic name NOTFOUND, and the EYUDA reason value has the symbolic name ACTION. These values mean that the attempted action was not found in the CICSPlex SM MAS resource table. The only actions available for the MAS resource table are STOP, STOPUNCON, and FORCEDISCON. The START action is not permitted. See the MAS table to confirm the actions available for a MAS resource.