Define User Exits for Date Aging

Optim provides extensive facilities for aging date columns. To do so, the solutions support hundreds of date formats and allow you to augment the distributed date formats.

(See Customizing Date Formats.) Further, Optim provides a set of semantic rules that you can customize to ensure that aged dates adhere to the business rules embedded in your applications. The semantic rules as well as the date format can be extended. Optim provides user exits to handle any situation that cannot be handled through the product extensions.

This section discusses an exit to handle dates expressed in non-standard date formats when aging.

Exits can be written in assembler language, COBOL, or PL/I.

Overview

Two sample COBOL date format exit programs, FOPHXIT1 and FOPHXIT2, are included in the Optim samples library (SFOPSAMP).

These exits are useful for handling:

Non-standard formatting.
Values to be skipped other than those automatically handled.
Dates for which the aging is dependent on another date.

To use a date format exit, specify the name of the exit on the EXIT parameter of the FORMAT statement in the member FOP9SAPF in the install library.

A date format exit consists of a single load module which is dynamically loaded and called to perform Get, Put and Term functions. A single entry point is used. The exit is called with an entry code indicating the desired function along with function-specific parameters. These parameters are passed to the exit using a standard z/OS-format parameter list.