# Incorrect date on generated DDM - Linux

**URL:** <https://techcommunity.softwareag.com/t/incorrect-date-on-generated-ddm-linux/60114>\
**Category:** Forum\
**Tags:** Adabas-Natural, Natural, Natural-Add-on-Products, Natural-Predict\
**Created:** [August 11, 2005, 3:43pm UTC](https://techcommunity.softwareag.com/t/incorrect-date-on-generated-ddm-linux/60114 "2005-08-11T15:43:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Priscilla\_Fuller](https://avatars.discourse-cdn.com/v4/letter/p/b5ac83/32.png) [@Priscilla\_Fuller](https://techcommunity.softwareag.com/u/Priscilla_Fuller)\
**Post date:** [August 11, 2005, 3:43pm UTC](https://techcommunity.softwareag.com/t/incorrect-date-on-generated-ddm-linux/60114/1 "2005-08-11T15:43:49Z")

</div>

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.

Thanks

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 2, 2021, 2:40pm UTC](https://techcommunity.softwareag.com/t/incorrect-date-on-generated-ddm-linux/60114/2 "2021-04-02T14:40:14Z")

</div>