Diagnosing deployment errors

Deployment errors can occur when you use CICS Explorer® or CICSPlex® SM to deploy bundles, or install resources in CICS®. The most common deployment errors are described, including the symptom of the problem, the cause and the solution.

About this task

If a deployment error occurs, Bundle resources typically install in a DISABLED state. Information and error messages associated with installing resources are located in the system log.

Procedure

  • You receive a DFHEC1003 error message from CICS:
    DFHEC1003 08/23/2010 17:31:58 IYK3ZMC1 The CICS event capture component failed to create the EVENTBINDING resource                
               MyEPCatalogSampleEventBinding in BUNDLE MYTEST because the XML data in the event binding could not be parsed.      
    An error has occurred creating event binding evbname in bundle bundle. This is probably caused by an error or inconsistency in the event binding XML. If the event binding was built by the event binding editor, this might indicate an error in CICS code. To resolve this issue:
    1. Inspect the CICS trace and EC domain message log for any related trace entries or messages.
    2. Validate the event binding against the event processing schema for the CICS system into which the bundle is being installed.
    3. Correct the event binding, discard the bundle, and reinstall it.
  • You receive a DFHEC1013 error message from CICS:
    DFHEC1013 08/23/2010 17:17:22 IYK3ZMC1 The CICS event capture component failed to create the EVENTBINDING resource              
               MyEPCatalogSampleEventBinding in BUNDLE MYTEST because the event binding schema level is not supported: 0900.   
    The event binding schema level is not supported and the EVENTBINDING resource cannot be created.
    This is probably caused by an error or inconsistency in the event binding XML. If the event binding was built by the event binding editor, this might indicate an error in CICS code. To resolve this issue:
    1. Inspect the CICS trace and EC domain message log for any related trace entries or messages.
    2. Validate the event binding against the event processing schema for the CICS system into which the bundle is being installed.
    3. Correct the event binding, discard the bundle, and reinstall it.
  • You receive a DFHPI1007 error message from CICS:
    DFHPI1007 08/23/2010 17:31:58 IYK3ZMC1 00165 XML to data transformation failed because of incorrect input 
    (XML_FORMAT_ERROR PI not closed) for EVENTBINDING MyEPCatalogSampleEventBinding.  
    CICS has failed to convert some XML data into application data. This XML may be the body of a SOAP message received from a partner process. The reason for the failure is due to a problem with the content of the XML. The XML is either not well formed, invalid with respect to the XML schema or does not conform to one of the internal constraints of the CICS XML transformation service. An error_qualifier may be provided to help identify the source of the problem. In some cases the error_qualifier will be empty. To resolve this issue:
    1. Examine the exception trace entry for further information.
    2. Consider using the WEBSERVICE or XMLTRANSFORM validation option to test that the XML is valid for the schema. XML is case sensitive. Ensure that the XML element, attribute, and namespace names used within the XML are correct with respect to the schemas that describe the XML.
    3. Correct or change the partner process to ensure that the XML sent to CICS is appropriate to be consumed by CICS.
    4. If a SOAP message is changed by a handler program as part of the CICS PIPELINE processing then ensure that the handler has not introduced this problem.
  • You receive a DFHRL0102 error message from CICS:
    DFHRL0102 E 08/23/2010 17:17:22 IYK3ZMC1 CEDA The CICS resource life-cycle manager failed to create the resource                
               MyEPCatalogSampleEventBinding and returned with reason CALL_BACK_ERROR.     

    The CICS resource lifecycle resource class, DFHRLRS, failed to create the resource resource_name.

    To resolve this issue:
    1. Correct the problem identified in the message.
    2. If the message reports that no further information is available, refer to trace.