×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
While the SYSLIMTBL table is created and maintained by the system, it is
there for your use. You can make whatever changes you want. Deleting
rows that represent objects that don't exist is allowed. Similarly, if
some exceptional (and probably well-understood) activity added rows that
don't reflect normal processing, those rows could be deleted so they do
not interfere with future evaluation. You can even delete the table and it
will get re-created the next time an insert of a new row is attempted. In
addition to modifying the table, you can also add triggers to it if there
is some action you want to take with certain changes (such as send a
notification when a certain limit is logged).
As mentioned by Rob in another post, the system will purge older
information according to the values of the system provided global
variables. After you start looking at this information on a regular basis
to understand what "normal" activity looks like, you might want to adjust
the global variable settings. Usually the defaults are adequate. The
actual time when the system cleans up of aged values and low consumption
level values shouldn't matter. Just know that it does happen.
dspfd QSYS2/SYSLIMTBL shows
Allow read operation . . . . . . . . . . . : Yes
Allow write operation . . . . . . . . . . . : Yes
Allow update operation . . . . . . . . . . : ALWUPD *YES
Allow delete operation . . . . . . . . . . : ALWDLT *YES
So I'm guessing that if I want to purge those 5 ancient rows pertaining
to
objects which no longer exist I'm free to do so?
Sue Romano
Db2 for IBM i Development
midrange.com
