This is on IDS 934 TC2.
A partial output of this query follows ...

database sysmaster;
select count(*) as numext, sum(pe_size) as totsize, tabname[1,32] as tabnam
from systabnames, sysptnext
where partnum = pe_partnum
and dbsname = 'team'
group by 3
having count(*) > 1
order by 1 desc, 2 desc;

numext totsize tabnam
----------------- ---------------------------------- --------------------------------
33 398 286_1223
23 248 sysindices
18 198 286_2396
18 160 sysobjstate
17 144 sysconstraints
16 232 sysprocbody
15 178 286_1839
13 220 340_2246
12 83 287_2137
11 603 290_1934
11 468 304_1380
11 189 375_2380
10 286 247_984

Should I try to get the number of extents down on system tables?
Also, on automatic indexes, when should you worry about how many extents
they are in?
sending to informix-list

Bill Hamilton wrote:
> This is on IDS 934 TC2.
> A partial output of this query follows ...
<SNIP>
> Should I try to get the number of extents down on system tables?
> Also, on automatic indexes, when should you worry about how many extents
> they are in?
> sending to informix-list

Not to worry. All system catalog tables are cached in the data dictionary
cache so extent fragmentation in the catalog is not a problem since about
IDS 7.1.

Art S. Kagel