FDM not masking dates with particular years

Document ID : KB000098890
Last Modified Date : 31/05/2018
Show Technical Document Details
Issue:
Using the FDM function, HASHDOB, to mask a column defined as character and containing a date value in the format dd-mmm-yy (eg 12-DEC-55).  FDM masks all dates except for dates that end in years from 18 to 37.  This happens with both TDM 4.5 and 4.3.  What can be done to make this work?
Environment:
TDM 4.5 and 4.3
FDM is the component.
Cause:
Need to work around JAVA date/time "assumptions"
Resolution:
Please contact CA Support to get FastDataMasker-4.7.422.0.zip  If you are downloading a GA version of TDM after May 30, 2018, please check with CA Support to make sure that this fix was incorporated into the GA you are downloading.  This fix resolved the problem .

Follow-up Question:
Just curious as to what the cause was. We did think that it was a bit more than coincidence that the problem started with the year 18 being that it was 2018 now. However didn’t understand why only dates from 18 up to 37 were effected. Was it just a simple case of adding 10?

Answer:
The java date formatter we use interprets 2 year dates like 37 as 2037, since FDM then thinks the birth date is after the current date, it ignores it. This only occurred with string dates, normal dates or datetime was not affected.
Additional Information:

Video URL on how to open a Support Case - https://communities.ca.com/videos/5898-demo-how-to-open-a-support-case

You can download the latest version of TDM by following the directions in this document: https://support.ca.com/us/knowledge-base-articles.TEC1903942.html.   

To contact support, go to https://www.ca.com/us/services-support/ca-support/contact-support.html