RE: Question about subsystem pools

[Chris Bipes <rpg@xxxxxxxxxxxxxxx>]

The subsystem monitor job, i.e. the subsystem runs in memory pool 1 always.
Based on routing entries, you can place the application work into the
appropriate memory pool.  It is best not to have your subsystem taking up
resources you intended for the application to have.  I try to define all
subsystems with pool 1 as *BASE and Pool 2 as necessary.  If you look at the
routing entries for QINTER and QSPL and you will see them using Pool 2.  You
can then control what happens to a job that is reaching the end of its time
slice.  

Christopher K. Bipes     mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst   mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.         http://www.cross-check.com
6119 State Farm Drive    Phone: 707 586-0551 x 1102
Rohnert Park CA  94928 Fax: 707 586-1884

If consistency is the hobgoblin of little minds, only geniuses work here.
Karen Herbelin - Readers Digest 3/2000


-----Original Message-----
From: Allen, Stuart [mailto:sallen@fellowes.com]
Sent: Friday, April 14, 2000 7:40 AM
To: 'Midrange'
Subject: Question about subsystem pools


In the subsystem description for QINTER, it shows as
 Pool        Storage     Activity 
  ID        Size (K)      Level   
   1           *BASE              
   2       *INTERACT              

Shouldn't this subsystem only go into *interact?

Also, my QSPL sbsd shows:

 Pool        Storage     Activity 
  ID        Size (K)      Level   
   1           *BASE              
   2          *SPOOL              

Again, shouldn't this just be *spool?


Anyone have any ideas?

Regards,
Stuart
                                     
Stuart Allen
European Systems Analyst
Fellowes

mailto:sallen@fellowes.com
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---