The first part of this article series showed how DSPOBJD can easily provide statistics to manage a general recompilation project. But it only touched the surface of all the things you get with the DSPxxx commands.
Written by Jean-Paul Lamontre
Let's start with a review of the information we gathered in Part I by just using DSPOBJD.
Objects by Type and Year
This data is concerned with counting objects by type and by year of source update (for those that have a source, of course).
If we had used ODCCEN plus ODCDAT (i.e., the object creation date) instead of ODSRCC plus ODSRCD, we'd have gotten a report on recompilation instead of a report on source update.
Managers and developers working with legacy RPG and COBOL applications face serious testing challenges. Few, if any, of these applications have a complete set of specifications of how the applications should perform, and even fewer have a complete library of test cases. Results from over 12,000 software projects show that detecting and removing defects is the single most costly task in software development.
Several months ago, I was visiting customers and reviewing their computer operations. A question that comes up more than I can believe is, "What do we do with all of the reports that are sitting on output queues?" This question always amazes me. There are companies with reports that have been sitting on output queues for five years or more!