Start of change

PROCESS_SYSTEM_LIMITS_ALERTS procedure

The QSYS2.PROCESS_SYSTEM_LIMITS_ALERTS procedure can be called to send alerts for any tracked limits that have exceeded their alerting level in the last 24 hours. Start of changeIt also prunes the system limits table (QSYS2.SYSLIMTBL), index advice table (QSYS2.SYSIXADV), and SQL error logging facility table (QSYS2.SQL_ERRORT).End of change

This procedure performs the same checks that are done by the system processing of the alerts. If a limit has reached its alerting level, message SQL7062 is sent to the QSYSOPR message queue. Calling the procedure repeatedly can send duplicate alerts. See System limit alerts for details.

This procedure can be submitted in a job to be run at a user-determined time to look for runaway situations.

Start of changeThis procedure performs pruning as defined by the SYSIBMADM.QIBM_SYSTEM_LIMITS_xxx_BY_DAYS global variables, and by the SYSIBMADM.QIBM_SYSIXADV_BY_DAYS and SYSIBMADM.QIBM_SELF_BY_DAYS global variables. Rows that have exceeded the value of the global variable will be deleted from the associated table. End of change

Authorization: This procedure, implemented by the QSYS2/LIM_ALERTS program, is shipped with *PUBLIC *EXCLUDE authority.

To call this procedure the user must have *EXECUTE Start of changeand *OBJOPREnd of change authority to the QSYS2/LIM_ALERTS program.

Read syntax diagramSkip visual syntax diagramPROCESS_SYSTEM_LIMITS_ALERTS()

The schema is QSYS2.

Example

To schedule a job that will run every weekday at noon to report system limits that have reached their reporting threshold values in the last 24 hours, the following CL command can be run.
ADDJOBSCDE JOB(CHKALERT) 
CMD(RUNSQL SQL('CALL QSYS2.PROCESS_SYSTEM_LIMITS_ALERTS()') COMMIT(*NONE) )
FRQ(*WEEKLY) SCDDATE(*NONE) 
SCDDAY(*MON *TUE *WED *THU *FRI ) SCDTIME('12:00:00')
End of change