tracking important system limits

8/10/2019 Tracking Important System Limits

1/11

You are in: IBM i Technology Updates> IBM i Technology Updates> DB2 for i - Technology Updates> DB2 for i - Services>

Tracking Important System Limits

Disclaimer:

The description of the content below is being made available to you at time of announcement.

However, these functions are not available for use and supported until the DB2 PTF Group has been released.

Note: Phase 3 is coming with DB2 PTF Group SF99702 (7.2 only) Level 3.

Read about it below.

A new type of health indicator is available to help you understand when the system is trending

towards an outageor serious condition.

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 new health touchpoint on IBM i. The system

instrumentation for automated tracking will focus 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 the SYSLIMTBL physical file

and provides a wealth of contextual information regarding the rows in the table.

See these articles for more detail:

OnDemand Tracking of Important System Limits on IBM iOnDemand Tracking of Important System Limits on IBM i

and

http://m.iprodeveloper.com/systems-management/gain-big-insights-db2-i-system-limits-

phase-2

Phase 1 (delivered with TR6)

Tracking Important System LimitsTracking Important System Limits| Updated 10/5/14 byScottForstie | Tags: None

M i Technology Updates : Tracking Important System Limits file:///U:/MAKE_IT/BASIS/Tracking Important System Limits.ht

n 11 27.11.2014 11:09


2/11


n 11 27.11.2014 11:09


3/11


4/11


n 11 27.11.2014 11:09


5/11

Example 1. Examine active job levels over time

-- How close am I coming to hitting the Maximum Active jobs limit?

SELECT SBS_NAME, SIZING_NAME, CURRENT_VALUE, MAXIMUM_VALUE , A.*

FROM QSYS2.SYSLIMITS A

WHERE LIMIT_ID = 19000

ORDER BY CURRENT_VALUE DESC

Figure 1. Example output from the QSYS2/SYSLIMITS view


n 11 27.11.2014 11:09


6/11


n 11 27.11.2014 11:09


7/11

QSYS2/SYSLIMITS view definition:


n 11 27.11.2014 11:09


8/11


n 11 27.11.2014 11:09


9/11

QSYS2/SYSLIMTBL table definition:

LAST_CHANGE_TIMESTAMP FOR COLUMN LASTCHG TIMESTAMP

The timestamp indicating when this row was inserted into the QSYS2/SYSLIMTBL table.

LIMIT_CATEGORY FOR COLUMN CATEGORY SMALLINTThe category of limit corresponding to this instance of System Limits detail.

This smallint value maps to the following:

0 - DATABASE

1 - JOURNAL

2 - SECURITY

3 - MISCELLANEOUS

4 - WORK MANAGEMENT

5 - FILE SYSTEM

6 - SAVE RESTORE

7 - CLUSTER

8 - COMMUNICATION

LIMIT_TYPE FOR COLUMN LIMTYPE SMALLINT

The type of limit corresponding to this instance of System Limits detail.

This smallint value maps to the following:

1 - OBJECT

2 - JOB

3 - SYSTEM

4 - ASP

LIMIT_ID INTEGER

The unique System Limits identifier. The limit identifier values are instrumented within the

QSYS2/SQL_SIZING table, within the SIZING_ID column.

SQL can be used to observe these values.For example:

SELECT SIZING_ID, SUPPORTED_VALUE, SIZING_NAME, COMMENTS

FROM QSYS2.SQL_SIZING

ORDER BY SIZING_ID DESC

JOB_NAME VARCHAR(28)

The name of the job when the instance of System Limits detail was logged.

USER_NAME FOR COLUMN CURUSER VARCHAR(10)

The name of the user in effect when the instance of System Limits detail was logged.


n 11 27.11.2014 11:09


10/11

CURRENT_VALUE FOR COLUMN CURVAL BIGINT

SYSTEM_SCHEMA_NAME FOR COLUMN SYS_NAME VARCHAR(10)

The library name for this instance of System Limits detail, otherwise this is set to NULL.

SYSTEM_OBJECT_NAME FOR COLUMN SYS_ONAME VARCHAR(30)

The object name for this instance of System Limits detail, otherwise this is set to NULL.

SYSTEM_TABLE_MEMBER FOR COLUMN SYS_MNAME VARCHAR(10)

The member name for an object limit specific to Database members, otherwise this is set to

NULL.

OBJECT_TYPE FOR COLUMN OBJTYPE VARCHAR(7)

This is the IBM i object type when an object name has been logged under the

SYSTEM_SCHEMA_NAME and SYSTEM_OBJECT_NAME columns

When no object name is specified, this column will be set to NULL.

ASP_NUMBER FOR COLUMN ASPNUM SMALLINT

Contains NULL or the ASP number related to this row of System Limits detail.

Phase 3 includes instrumentation for some IFS File Systems.

File systems instrumented for object limits:

root (/) file system

Open systems file system (QOpenSys)

Document library services file system (QDLS)

User-defined file systems (UDFSs)


on 11 27.11.2014 11:09


11/11

See these articles for more detail:

http://iprodeveloper.com/systems-management/ondemand-tracking-

important-system-limits-ibm-i

http://iprodeveloper.com/systems-management/gain-big-insights-db2-i-

system-limits-phase-2

Comments

There are no comments.


tracking important system limits

Documents