We've all seen programmers slumping in their chairs, eyes glazed, brows furrowed, having gone several hours past the point of accomplishing much, perhaps about to create bugs that will have to be corrected later. If they had taken short breaks all along, refreshing body and mind, they could have gotten just as much work done, while slowing the onset of debilitating repetitive strain injury (RSI).
Is the QAUDJRN security audit journal cluttered with too much information?
You hear the same complaints again and again: The security audit journal, QAUDJRN, contains too many entries. It's too hard to make sense of all the details. Do you really care that you have 1,592 program-adopt entries one day and only 450 the next? Do you need to copy the journal receiver to a database file every day? What exactly do all the different entry types mean?