DFHPI9034 W   Schema type type is being restricted to a total of value digits.

Explanation

An XML schema document contains type definition type. This type specifies a total number of digits which is too large for the target programming language to support. DFHSC2LS is restricting the type definition to a total of value digits.

System action

The XML assistant continues processing. If at runtime an XML document is processed with a value which is too large for the target field in the language structure then a conversion error will be indicated.

User response

Consider whether you need to be able to support numbers which require more digits than are allowed in the DFHSC2LS mappings. If it is acceptable for CICS to impose this maximum length then you may safely ignore this message.

Consider changing the WSDL document or XML schema to avoid this problem. For example, you could change the problematic XML construct for a different one that is supported. For example, the xsd:any construct is supported by both DFHWS2LS and DFHSC2LS and can be used as a replacement for most other constructs at mapping level 2.1 onwards. A change of this type can usually be made without breaking interoperability with partner processes that are implemented using the original XML schema or WSDL document. If changing or simplifying the XML schema or WSDL is not acceptable then other options exist:
  • If you are using DFHWS2LS, then at runtime level 2.1 onwards you can use the XML-ONLY parameter to opt-out of the CICS supplied XML transformation service. This results in a WSBind file being generated that tells CICS that the application will work directly with the SOAP Body in the DFHWS-BODY container.
  • If you are implementing a Web service provider application then you could consider writing your own XML capable SOAP application handler.
  • If you are implementing a Web service requester application then you could consider writing an XML capable application that uses the DFHPIRT channel linkable SOAP interface.
Other products may exist that can help process or omit the problematic XML constructs. For example, IBM's Rational Developer for System Z (RDz) product supports a "meet-in-middle" mapping scenario that allows omitting of specific XML constructs.

Module

DFHSC2LS

Destination

SYSPRINT



DFHPI9034W.html | Timestamp icon Last updated: Sunday, 4 June 2017