Date Format

Previous topic - Next topic

DDP021

We had an odd issue here...A customer was using a generic indexer and send their .ind file to us...They are using a FROM_DATE and To_Date...We had collected well over 100,000 files in groups of 5000...On the last run of 3500 we had a failure on one of the FROM_DATE..I

Row 779:  The string "19280320" could not be converted to a date from the format of %Y%m%d

We believe there is a type in  the .ind file seeing as all the other FROM_DATE fields in previous files are either 2008 or 2009...The issue is, the field itself in the file is formatted correctly..The only difference is the date is 1928...It appears for some reason, CMOD doesn't like that number...Once we removed it, the remaining files in the .ind file loaded successfully...Is anyone aware of this kind of issue...Does something need to  be done on the setup to allow a date of 19##?......

Justin Derrick

Depending on your version of CMOD, CMOD can only properly interpret dates between 1970 and 2070.

You'll want to upgrade to DB2 v9 and use the new date format, which supports an enormously larger range of dates.

-JD.
Call:  +1-866-533-7742  or  eMail:  jd@justinderrick.com
IBM CMOD Wiki:  https://CMOD.wiki/
FREE IBM CMOD Webinars:  https://CMOD.Training/
IBM CMOD Professional Services: https://CMOD.cloud

Interests: #AIX #Linux #Multiplatforms #DB2 #TSM #SP #Performance #Security #Audits #Customizing #Availability #HA #DR

DDP021

Thanks Justin as always!!!...We figured there was some limitation on the date....Also, from what we've been able to determine, the 1928 was obviously a typo on the .ind file itself seeing at it was the only occurrence in over 118,000 PDF's...Appreciate the info going forward in the event we would ever happen to run into a date older that 1970!!!

Take care!!!

Dave