Incompatibility between WPS and WD/z - Random data in the COBOL fields associated with the missing tags from WPS

We use WDforZ to produce a WSDL and adapter programs for SOAP for
CICS communications with WebSphere Process Server (WPS). We have found
that WPS does not always send all the XML tags from the WSDL file
(sometimes if there is nothing to send, start/end tags will be sent
with nothing in between them, sometimes the tags will not be sent at
all).
When no tags are sent, we are finding random data in the COBOL fields
associated with the missing tags. This seems to be because the adapter
AML to COCOL converter is not initialising the input structure. It
appears to only initialise fields once a tag has been found in the
input XML stream. Thus there seems to be an incompatibility between the
operation of WPS and WdforZ.

During PMR investigation between WDz and WPS level 2 support personnel the problem recreation scenario was sent to
Simon Holdsworth (STSM - Bindings Architect for WebSphere ESB and Process Server ) and his assessment of the requirement is as follows:
The current position in WESB/WPS v7, is that we still don't
automatically check for these conditions within XML documents, and we don't
automatically create/remove/truncate/pad elements to match the schema
constraints. This is even with the newest XML technology (XCI) that we
are adding in v7. This is a valid requirement, but not one that we
would be able to deliver in v7.

This requirement has been raised in the appropriate Design Change Request / Product Requirements database on "Project Central" against WPS, however as that location is "internal access only" and prevents the end requester (the client) from tracking that enhancement request externally, we have been advised to raise this RFE and reference the WPS enhancement request on Project Central ref# FB002798