DFHPI1008 DATE TIME APPLID TRANID TRANNUM {XML | JSON} generation failed because of incorrect input ({ARRAY_CONTAINER_TOO_SMALL | DATA_STRUCTURE_TOO_SMALL | ARRAY_TOO_LARGE | ARRAY_TOO_SMALL | CONTAINER_NOT_FOUND | CONTAINER_NOT_BIT | CONTAINER_NOT_CHAR | BAD_CHOICE_ENUM | LENGTH_TOO_LONG | LITTLE_ENDIAN_BOM | 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 | TYPE UNKNOWN} resource_name.

Explanation

CICS has failed to generate XML or JSON due to a problem with the data received from the CICS application. 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:

ARRAY_CONTAINER_TOO_SMALL array_name

A CICS container does not hold sufficient data given the number of instances of the data expected and the length of one instance of the data.

DATA_STRUCTURE_TOO_SMALL expected_length

The container passed to CICS does not hold the expected quantity of data. There are several possible causes for this problem including:

  • The binding file and the application are out of step. For example, CICS may be expecting data consistent with version 1 of an application, but the application has been updated to version 2. In which case, the binding file needs updating and redeploying.

  • A provider mode Web service may have failed to populate the data container prior to exiting. CICS may be receiving the same data as output that it originally passed to the Web service as input.

  • The application may be deliberately truncating the data it passes to CICS.

ARRAY_TOO_LARGE array_name

Too many instances of a structure have been supplied in a container given the maximum value specified in the XML schema.

ARRAY_TOO_SMALL array_name

Too few instances of a structure have been supplied in a container given the minimum value specified in the XML schema.

CONTAINER_NOT_FOUND container_name

A container named in the input structure cannot be found.

CONTAINER_NOT_BIT container_name

A container named in the input structure exists but is of the wrong type. The container must be created in BIT mode rather than CHAR mode.

CONTAINER_NOT_CHAR container_name

A container named in the input structure exists but is of the wrong type. The container must be created in CHAR mode rather than BIT mode.

BAD_CHOICE_ENUM enum_name

An enumerated value in the input structure has been set to an invalid value.

LENGTH_TOO_LONG field_name

The length value specified for this field is longer than the maximum length permitted for the field. For example, the maximum length of the field may be 255 characters, but the length may have been initialized to x'4040' which indicates 16448 characters of data.

LITTLE_ENDIAN_BOM field_name

The Byte Order Marker for a UTF-16 field contains an unexpected Little Endian BOM. If a BOM character is used then it must be Big Endian.

INVALID_UNICODE_DATA field_name

A UTF-16 field contained an invalid code point.

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, in most cases, a RESP2 code of 14. If CICS is processing a TRANSFORM command, an INVREQ is returned with a RESP2 code of 5.

An exception entry is written to the trace table.

User response

Examine the exception trace entry for further information.

Correct the CICS application to ensure that the data presented to CICS is appropriate to be converted into XML or JSON.

Module

DFHPIII

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