System Load

[DDP021]

Can anyone explain on SYSTEM LOAD search where the information for DOC BEGIN DATE/DOC END DATE & START DATE and END DATE information gets pulled from? In searching the System Load we see MOST of these dates match the LOAD DATE but some do not? We discovered it by accident when trying to determine reports with bad posting dates.  Noticed when looking at the System Load these DOC  BEGIN/END and START /STOP DATES were showing really old dates.  Would it be getting these dates from the actual data?  And if so, how? Is it based off of the POSTING DATE that was defined?

[Lars Bencze]

Hi,

You are correct that the Doc begin date, Doc end date, start date and stop dates are all taken from the index data that goes with the file. For an AFP file, it would be embedded in tags in the file, and for generic indexed docs it would come from within the .ind file.
In both cases, the date field that is used is defined in the Application Group and the Application that you have defined. For example, you have a field called "MyDate" (type Date) in the Application Group, which you have tagged as "Segment" on the Field Information tab, using the corresponding check box. And you have also defined in the Application (for example) that it should be picked from page 1 of every new "Group" (aka each independent doc in the input file), row X column Y, and Z characters long. And/or you have defined the date Format to match the date in your input documents, so it gets interpreted correctly, of course.
The highest and lowest date(s) found inside the loaded file is used to determine these dates in the System Load log, and you can see it in the MsgNum 87 in the System Log too.

Hope this helps! 

[DDP021]

Thanks for the info...We define a POSTING DATE and check the SEGMENT box.  On the Application setup we input a lower case t in the Default value for the POSTING DATE definition under the LOAD INFORMATION tab.  So it will use the LOAD DATE as the POSTING DATE.  But we also have many cases where we are pulling the POSTING DATE off of the data page.  We have recently found numerous setups where we had the POSTING DATE format on the Application as m/d/y which was correct when initially defined.  Unknown to us was the application changed the data to be y/m/d.  We still successfully ingested the data as the length was the same.  But the POSTING DATE was out of order.  So instead of the posting date being 5/18/21, it was being stored as 21/5/18.  The issue was found by our systems support area who saw our CACHE being filled up.  We have report setup to remain on cache for 7 days based and then roll to TSM.  But because of the date format issue, the system never saw the correct date to know to move it off of CACHE.