This looks fine.
If you run DSPSBSD on each of the subsystems, and take option 2 for Pool Definitions, you will see how many pools are defined for that subsystem, and whether it's defined as *BASE, *INTERACT, *SPOOL, *SHRPOOLxx - or as a Private Pool (size defined).
Work with subsystems is showing you for example, that subsystem QINTER has 2 pools defined to it. The first pool defined (1) is the system pool 2 - which WRKSYSSTS shows you is the *BASE pool. The second pool defined (2) is system pool 4, which WRKSYSSTS shows you is *INTERACT.
System pool 1 is always *MACHINE, and system pool 2 is always *BASE. From there it depends on what order the subsystems that use other pools are started.
The subsystem monitor runs in the 1st pool defined to the subsystem (usually *BASE - system pool 2).
Other pools used in the subsystems are determined by the Pool identifier on the routing entries for the subsystem (DSPSBSD, #7, F9).
As a first step I would carve out a separate pool for Batch jobs.
In WRKSHRPOOL assign a size and activity level for *SHRPOOL1.
In subsystem QBATCH:
Pool Storage Activity
ID Size (K) Level
For routing entries 300, 700 & 9999 (the 3 default entries) change all Pool identifiers to 2.
And maybe also change subsystem QPGMR same as above for Pool Id's.
For routing entries 10, 20, 700 & 9999 (the 4 default entries) change Pool identifiers to 1, 2, 2, 1.
You may want to try QPFRADJ sysval at '3' to see how the system handles it (note your pool sizes and activity levels so if it makes a mess of things you can change QPFRADJ back to '0' and put you pool sizes & activity levels back where they were.
If you decide to try QPFRADJ = '3', use WRKSHRPOOL, F11, to set reassonable min/max sizes - so for example it won't take away all the memory from QINTER during lunchtime (assuming anyone actually takes lunch and doesn't just grab a sandwich and work at their desks these days !).
-----Size %----- -----Faults/Second-----
Pool Priority Minimum Maximum Minimum Thread Maximum
*MACHINE 1 22.50 55.00 10.00 .00 10.00
*BASE 2 4.50 80.00 10.00 2.00 100
*INTERACT 1 2.50 80.00 5.00 .50 200
*SPOOL 3 .50 15.00 5.00 1.00 100
*SHRPOOL1 2 .75 80.00 10.00 2.00 100
*SHRPOOL2 2 1.00 100 10.00 2.00 100
*SHRPOOL3 2 1.00 100 10.00 2.00 100
*SHRPOOL4 2 1.00 100 10.00 2.00 100
*SHRPOOL5 2 1.00 100 10.00 2.00 100
*SHRPOOL6 2 1.00 100 10.00 2.00 100
Would suggest changing paging option for the pools (can't change *MACHINE) from *FIXED to *CALC for all pools, via WRKSYSSTS or WRKSHRPOOL - again, try it - it may work for you, it may not.
Neil Palmer DPS Data Processing Services Canada Ltd.
50 Acadia Avenue, Ste.102 AS/400~~~~~
Markham, Ontario, Canada. ____________ ___ ~
Phone:(905) 474-4890 x303 |OOOOOOOOOO| ________ o|__||=
Cell.:(416) 565-1682 x303 |__________|_|______|_|______)
Fax: (905) 474-4898 oo oo oo oo OOOo=o\
http://www.DPSlink.comiSeries 400 The Ultimate Business Server
"oludare" <email@example.com> Sent by: firstname.lastname@example.org
I just came back from Common 2000 at Baltimore, MD and I'm looking around and changing some of my system's configurations as they relate to PERFORMANCE TUNNING. One of my discovery on my system seems weird. Below you'll see the printouts from my WRKSYSSTS & WRKSBS. I think my SUBSYSTEMS are not defined properly, their references to SUBSYSTEMS POOLS doesn't appear OK to me.
Please advice on how to set this up correctly.
Work with System Status
% CPU used . . . . . . . : 10.0 Auxiliary storage:
Elapsed time . . . . . . : 00:00:02 System ASP . . . . . . : 84.89 G
Jobs in system . . . . . : 10957 % system ASP used . . : 47.5937
% addresses used: Total . . . . . . . . : 84.89 G
Permanent . . . . . . : .010 Current unprotect used : 2214 M
Temporary . . . . . . : .224 Maximum unprotect . . : 2440 M
Type changes (if allowed), press Enter.
System Pool Reserved Max
Pool Size (K) Size (K) Active Pool Subsystem Library
1 97180 58428 +++++ *MACHINE
2 189984 0 36 *BASE
3 10484 0 8 *SPOOL
4 750928 0 62 *INTERACT
This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact