Wrkprb needs long time to start

From Try-AS/400
Revision as of 14:37, 24 July 2020 by PoC (talk | contribs) (New)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

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

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 hat 36 MiB, and the accompanying LF 24 MiB.

A possible solution would be to use RGZPFM to reorganise the database file. But the command refuses to work on an empty database file.[1]

Another possibility is to delete and recreate the members of the files in question. Members are bound to the record structure laid out in the file itself. So deleting and re-adding file members does no harm except getting rid of all the deleted records. 

RMVM FILE(QUSRSYS/QASXPROB2) MBR(QASXPROB2)
RMVM FILE(QUSRSYS/QASXPROB) MBR(QASXPROB)
ADDPFM FILE(QUSRSYS/QASXPROB) MBR(QASXPROB)
ADDLFM FILE(QUSRSYS/QASXPROB2) MBR(QASXPROB2)

To prevent this from happening again, allow the OS to reuse allocated space. 

CHGPF FILE(QUSRSYS/QASXPROB) REUSEDLT(*YES)[2]

This approach applies also to any other database file showing significant slowdown over time.

Footnotes

  1. ↑ One with no records, that is.
  2. ↑ Since there's no reusedlt parameter for CHGLF, I wonder why the index needed so much space.
Retrieved from "http://try-as400.pocnet.net/index.php?title=Wrkprb_needs_long_time_to_start&oldid=884"