DFHPI1007 DATE TIME APPLID TRANID TRANNUM {XML | JSON} to data transformation failed because of incorrect input ({XML_FORMAT_ERROR | UNEXPECTED_CONTENT | HEADER_FORMAT_ERROR | UNDEFINED_ELEMENT | UNDEFINED_NAME_SPACE | ARRAY_OVERFLOW | NAME_TOO_LONG | PREFIX_TOO_LONG | NAME_SPACE_TOO_LONG | UNEXPECTED_XOP_INCLUDE | XOP_INCLUDE_ERROR | DUPLICATE_CHOICE | MISSING_XSI_TYPE | UNKNOWN_XSI_TYPE | MISSING_ATTRIBUTE | MIXED_CONTENT | MISSING_EQUALS_ATTR | MISSING_CLOSE_TAG_CHAR | MISSING_QUOTE_OR_APOSTROPHE | MISSING_END_QUOTE | DUPLICATE_ATTRIBUTE | MISMATCHED_TAGS | UNSUPPORTED_ENTITY | INVALID_UNICODE_DATA} error_qualifier) for {WEBSERVICE | XMLTRANSFORM | BUNDLE | EVENTBINDING | SCACOMPOSITE | JVMSERVER pipeline handler program | EPADAPTER | OSGIBUNDLE | PROGRAM | POLICY | EPADAPTERSET | APPLDEF | TRANSACTION | URIMAP | PLATDEF | LIBRARY | WARBUNDLE | EBABUNDLE | TCPIPSERVICE | JVMSERVER | FILE | PIPELINE | JSONTRANSFRM | EARBUNDLE | PACKAGESET | TYPE UNKNOWN} resource_name.

Explanation

CICS has failed to convert some XML or JSON data into application data. In the case of XML, this 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 or JSON 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.

The possible error codes and qualifiers associated with this message are:

XML_FORMAT_ERROR error_type

The XML or JSON is not well formed. See the trace for further details.

UNEXPECTED_CONTENT

Character data has been found between two XML tags at a place where such text was not expected.

HEADER_FORMAT_ERROR

There is a problem reading the namespace attributes from the XML namespaces container.

UNDEFINED_ELEMENT element_name

The XML includes an unexpected XML tag, or the JSON includes an unexpected JSON object.

UNDEFINED_NAME_SPACE name_space

The XML includes an XML namespace prefix that has not been defined.

ARRAY_OVERFLOW array_name

Too many instances of an array or list of tags has been found in the XML.

NAME_TOO_LONG

An XML tag name longer than 255 characters has been found.

PREFIX_TOO_LONG

An XML namespace prefix longer than 255 characters has been found.

NAME_SPACE_TOO_LONG

An XML namespace name longer than 255 characters has been found.

UNEXPECTED_XOP_INCLUDE

An xop:Include element should only appear in place of the data for a base64binary field, but was found in some other context.

XOP_INCLUDE_ERROR

An xop:include element was found in a valid context, but the referenced attachment could not be found.

DUPLICATE_CHOICE element_name

A second entry has been found from a mutually exclusive group of options. Only the first option that was found was expected.

MISSING_XSI_TYPE element_name

An xsi:type attribute was expected for the XML tag but could not be found.

UNKNOWN_XSI_TYPE type_name

An xsi:type attribute was found for a data type that is not supported. Data types are supported only if they were present in the original XML schema.

MISSING_ATTRIBUTE attribute_name element_name namespace

A required attribute with the specified name and namespace was expected but is missing from the specified XML tag. No default value is known for the attribute. If the namespace is not specified, the XML attribute must not be qualified with a namespace.

MIXED_CONTENT element_name

The identified element included character data that is not marked up with XML tags. These characters are only tolerated if the XML schema specified mixed="true" for the element.

MISSING_EQUALS_ATTR attribute_name element_name

The identified element has an attribute that is missing an equals character prior to its value; for example, <tag attribute"value"> instead of <tag attribute="value">.

MISSING_CLOSE_TAG_CHAR element_name

The identified element is missing a '>' character. The tag might be a self closing tag that would normally take the following form: <tag/> .

MISSING_QUOTE_OR_APOSTROPHE attribute_name element_name

The identified element has an an attribute that is missing a delimiter for its value; for example, <tag attribute=value"> instead of <tag attribute="value">.

MISSING_END_QUOTE attribute_name element_name

The identified element has an an attribute that is missing its terminating value delimiter; for example, <tag attribute="value> instead of <tag attribute="value">.

DUPLICATE_ATTRIBUTE attribute_name element_name

The identified element has an two attributes with the same name.

MISMATCHED_TAGS start_tag_name end_tag_name

A pair of opening and closing XML tags do not match; for example, <open></close> rather than <open></open>.

UNSUPPORTED_ENTITY entity_name

An unsupported entity has been found in the XML.

INVALID_UNICODE_DATA element_name

An XML tag contains invalid Unicode data.

System action

The XML or JSON conversion process halts.

If CICS is acting as a Web service provider, a SOAP Fault message (in the case of SOAP) or an error message (in the case of JSON) is returned to the requester. If CICS is acting as a Web service requester, a response code of INVREQ is returned to the calling application program with a RESP2 code of 14. If CICS is processing a TRANSFORM command, an INVREQ is returned with a RESP2 code of 3.

An exception entry is written to the trace table.

User response

Examine the exception trace entry for further information. 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.

Correct or change the partner process to ensure that the XML sent to CICS is appropriate to be consumed by CICS.

If a SOAP or JSON message is changed by a handler program as part of the CICS PIPELINE processing then ensure that the handler has not introduced this problem.

Module

DFHPICC

XMEOUT parameters/Message inserts

  1. DATE
  2. TIME
  3. APPLID
  4. TRANID
  5. TRANNUM
  6. Value chosen from the following options:
  7. Value chosen from the following options:
  8. error_qualifier
  9. Value chosen from the following options:
  10. resource_name

Destination

CPIO