We are starting to compile entire COBOL subsystems in batch. Out of say,
500 programs, we are getting maybe twenty errors, more questionables,
and a large number of warnings. I would like to produce and manage
listings to aid in finding and correcting these errors, questionables,
and warnings.

AFAIK, my choices are to send the listing to STDList, and get a FILEDES
that is the program name, or to send to a disc file. We already are
producing a very large number of STDLists, and having trouble managing
them for lack of time to look at the interesting stuff (and we already
have a third-party product in place that reads in the STDLists, so they
are no solution). I hate to add to this massive list. But disc files
have to be built, which I have already written a job to do, building
them 999,999 so the compiles don't fail just for this. But my choices
seem limited for those that I do not want to keep around. I hate to
purge and build hundreds of files with 0 ERROR(s), 0 QUESTIONABLE, 0
WARNING(s). I guess I could write a command file to grep for this
string, and when found, purge and build again. I don't think that would
be as easy with spool files.

Do I have other choices for managing compile listings? Is there a better
way than I describe to manage either of these choices? Should I just
quit whining and learn to live with it?