Just when you think you have everything figured out, a compiler bug creeps in and spoils everything. Consider our case. We created a command called List Largest Objects (LSTLRGOBJ) which runs a CL program which then calls an Auto- Report program. The report shows, among other things, the date each object was used last.

We would have remained in blissful ignorance of the Auto-Report bug if a user had not called to inform us that LSTLRGOBJ was printing dates last used in the future! He ran the report in February 1992, and the date last used for several objects was in August 1992. We all want to be ready for the future, but this is ridiculous.

We checked the logic of the program and everything was correct. Suspecting a problem with Auto-Report, we replaced it with an RPG program using identical logic. The RPG program produced correct data.

While we're at it, we'd like to report another problem with Auto-Report. Don't expect Auto-Report programs to work with externally described files, because they won't. We have found that although the Auto-Report compiler produces no errors, the reports produced list blanks and zeros where you would expect data. It seems that you cannot code in the O-specs any field names from externally described files. You must use a C-spec to MOVE the external field into a work field, then code the work field in the O-specs.