Wrkprb needs long time to start

Over time, it might become apparent that Wrkprb needs longer time to start, especially if the problem handling facility was used heavily on a slow machine.

Problem description

This stems from the fact that the used database files grow indefinitely, because they were created with the flag REUSEDLT disabled. That means, deleted records stay forever, but cannot be accessed. In my case, the PF had 36 KiB, and the accompanying LF 24 KiB. This is laughably small.

So it's not clear why the command experiences gradual slowdown over time.