Interesting. On both of my systems, 9999 says Pool identifier 1.
--
Sean Porterfield
-----Original Message-----
From: Jim Oberholtzer
Sent: Wednesday, January 30, 2013 18:03
To: Midrange Systems Technical Discussion
Subject: Re: Spool APIs performance and memory pools
The reason it is highly recommended that the first subsystem pool be *BASE is to ensure the subsystem monitor job can get an activity level and memory when it needs to do some work. This work is usually very very fast, pop up, do it, go away, but if there is not an activity level available for it, all things stop until it does get an activity level, hence the recommendation.
So for spool, subsystem pool 1 is *BASE, subsystem memory pool 2 is *SPOOL. As delivered there are four routing entries, 10,50, 60, and 9999. All of them should point to subsystem pool 2 (*SPOOL).
Hard and fast, nope, just really good practice particularly for spooling which tends to have quite a bit of activity.
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects
On 1/30/2013 4:11 PM, Charles Wilt wrote:
Ok, I tried to find a link to the *BASE as pool 1, but couldn't.
The v4r5 work management guide mentions that the memory for the
subsystem <monitor> job itself comes from whatever is defined as pool 1.
But it also shows an example of changing it to a private pool....
I know that I've seen "expert" recommendations to have pool 1 be base
for all SBSD. But it's obviously not as hard and fast as I recall.:)
Charles
--
This email is confidential, intended only for the named recipient(s) above and may contain information that is privileged. If you have received this message in error or are not the named recipient(s), please notify the sender immediately and delete this email message from your computer as any and all unauthorized distribution or use of this message is strictly prohibited. Thank you.
midrange.com
