IBM Support

Tracking Important System Limits

News


Abstract

System limit tracking provides IBM i health insight:
1) Recognize when the IBM i is trending towards an outage or serious condition.
2) Identify a run-away job that is endlessly consuming an operating system resource.

Content

You are in: IBM i Technology Updates > Db2 for i - Technology Updates > IBM i Services (SQL) > Tracking Important System Limits
Automatic tracking of System Limits enables you to:
  •     Understand when an application is trending towards a failure
  •     Gain insight regarding application or system outages
  •     Identify applications which are operating inefficiently
  •     Establish a general use mechanism for communicating limit information
Automatic tracking of important system limits is a health touchpoint on IBM i. The system instrumentation for automated tracking focuses on a subset of system limits. As those limits are consumed, tracking information is registered in a Db2 for i system table called QSYS2/SYSLIMTBL.  A view named QSYS2/SYSLIMITS is built over SYSLIMTBL and provides additional contextual information regarding the rows in the table.

IBM Documentation:  System Health Services

Messages are sent to the QSYSOPR message queue daily when critical limits have been reached.

Alerts for IBM i System Limits

Enhanced with IBM i 7.6 SF99960 Level 1:

  • Add tracking for a new work management limit: 19004 (Maximum message keys in job message queue ) 

Enhanced with IBM i 7.5 SF99950 Level 8 and IBM i 7.4 SF99704 Level 29:

  • Added alert support for 16100 (Maximum number of members in a source physical file) and 18304 (Maximum sequence number of a *MAXOPT1 or *MAXOPT2 journal)

Enhanced with IBM i 7.5 SF99950 Level 5 and IBM i 7.4 SF99704 Level 26:

  • Added alert support for 15002 (Maximum number of deleted rows in a partition)

Enhanced with IBM i 7.4 SF99704 Level 15 and IBM i 7.3 SF99703 Level 26:

  • Add SYSIBMADM based Global Variables to control the pruning of historically old rows
  • Change the nightly default pruning behavior to remove any row that is older the 90 days

Enhanced with IBM i 7.4 base release and IBM i 7.3 SF99703 Level 15:

  • Add tracking for a new database limit: 15003 (Maximum size of the data in a table partition)
  • When sending the alert message to QSYSOPR, use the SQL7062 message identifier

See this presentation for additional details:

[{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000000CHeAAM","label":"IBM i Db2"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions"}]

Document Information

Modified date:
29 March 2025

UID

ibm11136884

Page Feedback