Converting a JSON document into a text/binary data structure has now become easier and much more efficient with the new tpf_dfdl_serializeDoc function. This function takes a JSON document and DFDL handle as input then returns the address and length of the converted data structure. This new API that does direct conversion requires that the order of elements in the document matches the order of elements in the DFDL schema. The REST interfaces have also been updated to make use of this more efficient processing. See documentation for tpf_dfdl_serializeDoc for more information.
In addition, JSON documents that are unordered in relation to the DFDL definition can now be serialized using the existing tpf_dfdl_serializeData function. Since JSON is by definition unordered, this now allows for any JSON document to be serialized through DFDL. REST interfaces can consume a JSON body containing unordered name/value pairs through a new "unordered" property in the z/TPF service descriptor for the RESTful service. Since there is a greater efficiency when order can be maintained and thus a cost benefit, a distinction is allowed to be made. See updates to the z/TPF service descriptor documentation for more details.
PJ45191 also split the DFDL module into a library section (DFDL) and common deployment section (DFDR). Due to a new segment (DFDR) being needed during system restart, this APAR must be either loaded through the image loader or accepted by the e-type loader.