Example: Diagnosing a CICS management client interface install error

To install a BAS resource using the CICS management client interface, you use a PUT request with an INSTALL action. If the install action fails, CICSPlex® SM generates a BINSTERR record containing diagnostic information. This record is returned in an <installerror> element, which is a child element of <feedback>.

About this task

You have attempted to install a URIMAP resource named URIMAP_A into the region DEVRGN1, using a PUT request with the following URI and XML body:
http://wmvs2c.mycorp.com:27640/CICSSystemManagement/CICSDefinitionURIMap/IBEUR912?
CRITERIA=name%3DURIMAP_A

<request>
  <action name="INSTALL">
    <parameter name="TARGET" value="DEVRGN1"/>
    <parameter name="USAGE" value="LOCAL"/>
  </action>
</request>
Although you receive an HTTP/1.1 200 OK response from the CICS management client interface indicating that the request was correctly formed, the URIMAP is not installed. 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="INSTALL" attribute1="NAME" errorcode="31">  <installerror eibfn="3036" 
		eibfn_alt="CREATE  URIMAP" errorcode="4" eyu_cicsname="IBWUIA" resourcename="URIMAP_A" 
		resourceversion="1" resp="16" resp2="500"/>
    </feedback>
  </errors>
To understand the reason for this problem, perform these steps:

Procedure

  1. Determine the source of the error from the api_function attributes.
    This attribute indicates that the CICS management client interface has tried 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 perform the CICSPlex SM API command EXEC CPSM PERFORM SET ACTION('INSTALL')
  4. Identify the associated EXEC CICS command from the eibfn_alt attribute of the <installerror> element.
    The eibfn_alt represents the command EXEC CICS CREATE URIMAP
  5. Use the value of the errorcode attribute of the <installerror> element to determine the CICSPlex SM BINSTERR error code.
    See BINSTERR table for a list of error codes and their meanings. In this case the errorcode value 4 is (INSTFAIL) - Install failure.
  6. Use the resp and resp2 attributes of the <installerror> 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 EIBRESP 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 500 for the EXEC CICS CREATE URIMAP commands.
      See RESP2 values for EXEC CICS CSD commands for a list RESP2 values for the EXEC CICS CREATE command.