×
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.
I'm looking at this SQL:
select
system_pool_id,
pool_name,
maximum_active_threads,
current_threads,
decimal(decimal(current_threads, 15, 3) / decimal(maximum_active_threads, 15, 3), 15, 3),
current_ineligible_threads,
description
from qsys2.memory_pool_info
;
Some pools, like *BASE, get downright nasty when that percentage of current threads gets too high. While others, like *SPOOL, let you bust that Maximum with impunity. Right now *SPOOL has 25 for the maximum and 381 for current and zero for ineligible.
Has anyone thought of trying to get Halcyon to alert you upon a certain percentage? For example, sometime before this occurs
Message ID . . . . . . : CPF0909
Message . . . . : Ineligible condition threshold reached for pool 02.
Cause . . . . . : More than 255 threads are waiting on the ineligible queue
for system pool 02.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
midrange.com
