Date Aging function

The File-AID/Data Solutions Date Aging function includes the Formatted Date Aging Criteria, Date Calculator, and Business Rules functions. This function is accessed by selecting option 1 from the Primary Option Menu. The Date Aging function enables users to create time-dimensional test data by automating the process of incrementing, decrementing, or specifying default values for day, month, year, and century fields.

Formatted Aging Criteria controls the aging process. Each component of the date can be aged independently. The date pattern specifies the format in which the date is stored. Once the aging criteria is created, it can be saved, modified, used, and re-used.

Guidelines of date aging

File-AID/Data Solutions uses the following guidelines for processing date aging (plus or minus):

  • Increases to dates are processed in the order: Century and Year (together), Month, and then Day.
  • Decreases to dates are processed in the order: Day, Month, and then Century and Year (together).
  • Increases/decreases of CCYY are executed on the date format (Gregorian or Julian) passed by the date pattern exit. If the result is not a leap year, 0229 is adjusted to 0228 (Gregorian) and 366 is adjusted to 365 (Julian).
  • When you have a 2-digit year (no century is specified), Data Solutions must make an assumption regarding century. If the year is 60 or greater, Data Solutions assumes the date is 20th century (19yy). If the year is 59 or less, Data Solutions assumes the date is 21st century (20yy). The century assumption takes place in the COBOL exit (AGER0000 - AGER9999) so you can customize your own exits.
  • When processing date formats without a century (2-digit year), you may override the default pivot year value, 60, by entering a new pivot year value in the -C- (Century) field.
  • Month processing is based on the Gregorian format, regardless of the date format passed by the exit. When a date result is not a valid Gregorian date, the date is adjusted downward. For example, April 31 becomes April 30.
  • Day processing is based on the Julian date format, regardless of the date format passed by the exit. The result is always valid.
  • Necessary date adjustments to correct invalid dates are made after CCYY and MM date values are applied.
  • If you want to produce the original date after processing total equal plus and minus values, you must specify the date change values exclusively in Days and the record date must include a century value. The exclusive use of Days eliminates the possibility of Data Solutions adjusting invalid dates. Unless the date includes a century value, Data Solutions must make assumptions regarding century which may produce an end date different by one day from the start date.

This section provides information about the following topics:

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*