Incorrect date on generated DDM - Linux

I wanted to unload all the DDMs that have changed since a certain date (using SYSOBJH), and have discovered that all DDMs generated by Predict have the same source date - on a box using Predict 4.2.2 the date is 2000-01-01, on a box using Predict 4.3.2 the date is 1900-01-01. The catalog date is correct. Is there anyway to force Predict to use today’s date when generating DDMs?

I can pick up the files that have changed using the Predict Retrieval function, so I am not totally panic stricken, but would prefer the date on the DDM to be correct.