DFHPI1009 DATE TIME APPLID TRANID TRANNUM {XML | JSON} to data transformation failed. A conversion error ({UNKNOWN_CONVERSION | INPUT_TOO_LONG | OUTPUT_OVERFLOW | NEGATIVE_UNSIGNED | NO_FRACTION_DIGITS | FRACTION_TOO_LONG | INVALID_CHARACTER | ODD_HEX_DIGITS | INVALID_BASE64 | NOT_PURE_DBCS | INVALID_FIELD_SIZE | EXPONENT_OVERFLOW | EXPONENT_UNDERFLOW | ABSTIME_INVALID}) occurred when converting field fieldname 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 | 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 converting a value within the XML or JSON.

The possible error codes associated with this message are:

INPUT_TOO_LONG

The value of an XML tag that was declared as numeric contains more than 31 digits.

OUTPUT_OVERFLOW

An XML tag or JSON property contains a value that is too long to fit in the associated field of the commarea, or it contains a numeric value which is outside the permitted range for the associated field in the commarea.

NEGATIVE_UNSIGNED

A negative number has been found in an XML tag or JSON property that was declared as unsigned.

NO_FRACTION_DIGITS

An XML tag or JSON property contains a number which contains a decimal point but is not followed by any valid fractional digits.

FRACTION_TOO_LONG

An XML tag contains a number with more non-zero fractional digits than the XML schema allows.

INVALID_CHARACTER

An XML tag or JSON property contains a character that is inconsistent with the declared type of that tag. For example, a tag declared as hexBinary contains a value that is not in the range 0-9 + a-f + A-F.

ODD_HEX_DIGITS

An XML tag that was declared as hexBinary contains an odd number of hexadecimal characters.

INVALID_BASE64

An XML tag that was declared as base64Binary contains a value that is not consistent with the base64 encoding.

NOT_PURE_DBCS

An XML tag that maps to a pure DBCS language structure field contains a value that cannot be represented in pure DBCS.

INVALID_FIELD_SIZE

A floating point type with an unsupported precision level has been discovered.

EXPONENT_OVERFLOW

An overflow condition has been encountered whilst transforming a floating point value.

EXPONENT_UNDERFLOW

An underflow condition has been encountered whilst transforming a floating point value.

ABSTIME_INVALID

An attempt to convert an xsd:dateTime into a CICS ABSTIME value failed. This may be because the value in the XML does not conform to RFC3339, or the value represented may not be representable as a CICS ABSTIME value.

UNKNOWN_CONVERSION

An unrecognized conversion type has been requested.

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 4.

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.

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

If a SOAPmessage 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. fieldname
  9. Value chosen from the following options:
  10. resource_name

Destination

CPIO