× 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.



Cyndi,

There are some things you can do. Advice:
1. Use the autotuner.
2. Use the shared pool size min&max with reasonable numbers
3. Make all pools *CALC
4. Remove as much from *BASE as you can - a separate pool for the socket servers.
5. Tune your system values - QACTJOB, QADLACTJOB and same for QTOT
6. Tune your socket server pre-start jobs for better thresholds
7. Timeslices are a silver bullet - email me for the secret :-)

Hope that helps,
Trevor

----- Original Message ----- From: "Cyndi Bradberry"
Subject: memory pools


Everyone,
We have been receiving complaints from users that the system is slow for approximately one month. None of us are tuning specialists, so directions to the manual must be specific.

Here is the System Status screen:

Work with System Status BOISE 01/25/07 15:35:51
% CPU used . . . . . . . :       11.4    Auxiliary storage:
% DB capability . . . . : 5.4 System ASP . . . . . . : 387.5 G Elapsed time . . . . . . : 05:36:20 % system ASP used . . : 55.7330 Jobs in system . . . . . : 2065 Total . . . . . . . . : 387.5 G % perm addresses . . . . : .015 Current unprotect used : 6774 M % temp addresses . . . . : .148 Maximum unprotect . . : 6805 M

Type changes (if allowed), press Enter.

System Pool Reserved Max -----DB----- ---Non-DB--- Pool Subsystem
 Pool   Size (M)  Size (M)  Active  Fault  Pages  Fault  Pages
   1      183.33     93.42   +++++     .0     .0    2.9    3.4   *MACHINE
   2      781.66      1.00      61    1.0   15.1    2.1    6.0   *BASE
   3       20.16       .00       7     .0     .0     .0     .2   *SPOOL
   4     1008.87       .05      40    1.7   21.6    3.7    7.7   *INTERACT
5 22.00 .00 3 .0 .0 .0 .0 6 LSAMS

Bottom
Command
===>
F3=Exit   F4=Prompt   F5=Refresh   F9=Retrieve   F10=Restart   F12=Cancel
F19=Extended system status         F24=More keys

Pool 1,3, & 4 are set to Calc, pool 5 is static.

As you can see below, most of our subsystems are in pool 2. Byteme (programmers sybsystem) and QINTER are shown in 2 & 4. QUSRWRK is in pool 2. We have been busy beavers and have nearly 80 jobs running in QUSRWRK (socket servers that are in TIMW mostly).

                             Work with Subsystems
System: BOISE
Type options, press Enter.
  4=End subsystem   5=Display subsystem description
  8=Work with subsystem jobs

                      Total     -----------Subsystem Pools------------
Opt  Subsystem     Storage (M)   1   2   3   4   5   6   7   8   9  10
     BYTEME                .00   2   4
     FAXCOM                .00   2
     LSAMS               22.00                       5
     QBATCH                .00   2
     QCMN                  .00   2
     QCTL                  .00   2
     QINTER                .00   2   4
     QPGMR                 .00   2   2
     QSERVER               .00   2
     QSPL                  .00   2   3
     QSYSWRK               .00   2
     QUSRWRK               .00   2
     TESTSBS               .00   2   4


Bottom
Parameters or command
===>
F3=Exit   F5=Refresh   F11=Display system data   F12=Cancel
F14=Work with system status

Our interactive users are fussing that things are running slowly. There are 60 to 80 interactive users. We have an enterprise box, model 810, 7406 processor feature.

Do we need to reassign where pools are ? Maybe get another chip of memory ?

Suggestions welcome.

Cyndi B.
Boise, ID


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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 [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.