This document explains why a unload file created by PDTULDCC may differ considerably in size and content in comparison to a unload file created by PDTBATCC.
Why does my PDTULDCC unload file differ considerably in size and content in comparison to my PDTBATCC unload file?
z/OS 1.11 and above.
Module PDTULDCC does not automatically unload some of the record types that PDTBATCC does. For example, the DATATYPE=ALL parameter does not unload dynamic SQL statistics or static and dynamic SQL text as it does in the PDTBATCH job. Also, the PDTULDCC does not give you the option to unload additional keys statistics. Depending on the options in effect, this may result in an unload file that differs considerably in size and content than the unload file produced when PDTBATCC is explicitly invoked.
The use of PDTULDCC should be replaced with PDTBATCC. The DATATYPE parameter allows PDTBATCC to produce an unload file without the requirement to generate report output. SYSIN parameters allow tailoring of the PDTBATCC unload output file content.