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

The CICS® management client interface provides FEEDBACK records in the <feedback> element of a CICS management client interface response. You can use the extra information provided in FEEDBACK records to diagnose problems with CICS management client interface requests.

About this task

You have attempted to delete the CICS local file resource MYFILE_A, using a client API DELETE request with the following URI:
http://mvs2c.mycorp.com:27850/CICSSystemManagement/CICSLocalFile/IBEUR912?
CRITERIA=file%3DMYFILE_A
Although you receive an HTTP/1.1 200 OK response from the CICS management client interface indicating that the request was correctly formed, no record is returned and the response includes the following information:
<resultsummary api_function="PERFORM SET" api_response1="1038" api_response1_alt="TABLEERROR" 
api_response2="1361" api_response2_alt="DATAERROR" recordcount="1"/>
  <errors>
		<feedback action="DISCARD" eibfn="4C10" eibfn_alt="DISCARD FILE" eyu_cicsname="MAS1" keydata="MYFILE_A" 
     resp="16" resp2="2"/>
  </errors>

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 this 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 value is TABLEERROR, and the EYUDA reason value is DATAERROR.
  3. Determine the API call that failed by combining the information in the api_function attribute of the <resultsummary> tag with the action attribute from the <feedback> element.
    Using this information, you can determine that the failure occurred when the CICS management client interface was trying to delete the file using the CICSPlex SM API command EXEC CPSM PERFORM SET ACTION('DISCARD').
  4. Identify the associated EXEC CICS command from the eibfn_alt attribute of the <feedback> element.
    The eibfn_alt value represents the command EXEC CICS DISCARD FILE.
  5. Use the resp and resp2 attributes of the <feedback> element to determine the exact cause of the failure.
    Both the values are presented in decimal format.
    1. Look up the symbolic name for the CICS resp value 16.
      See EIB fields for a list of EIBREP values.
      From this list, you can determine that an EIBRESP field with a value of 16 has the symbolic name INVREQ.
    2. Finally, look up the meaning of the INVREQ response with a resp2 value of 2 for the EXEC CICS DISCARD FILE command.
      See DISCARD FILE for a list of RESP2 values for the INVREQ condition.
      From this list, you can determine that the cause of the failure of an EXEC CICS DISCARD FILE command that returns an INVREQ condition with a RESP2 value of 2 is The file is not closed.