Wrkprb needs long time to start: Difference between revisions

From Try-AS/400
Jump to navigation Jump to search
New
 
rework: Does not work
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
Over time, it might become apparent that '''Wrkprb needs longer time to start''', especially if the problem handling facility was used heavily.
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.<ref>Like a 9401-150.</ref>


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&thinsp;MiB, and the accompanying LF 24&thinsp;MiB.
__TOC__


A possible solution would be to use ''RGZPFM'' to reorganise the database file. But the command refuses to work on an empty database file.<ref>One with no records, that is.</ref>
== 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&thinsp;KiB, and the accompanying LF 24&thinsp;KiB. This is laughably small.


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.
So it's not clear why the command experiences gradual slowdown over time.
 
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)<ref>Since there's no ''reusedlt'' parameter for ''CHGLF'', I wonder why the index needed so much space.</ref>
 
This approach applies also to any other database file showing significant slowdown over time.


== Footnotes ==
== Footnotes ==

Latest revision as of 00:14, 22 May 2026

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.[1]

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.

Footnotes

  1. ↑ Like a 9401-150.
Retrieved from "http://try-as400.pocnet.net/index.php?title=Wrkprb_needs_long_time_to_start&oldid=1725"