Re: Subsystems, Shared Pools and Routing Entries

[Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>]

And BTW, I realize I'm making some assumptions here.

For example, I think that the "subsystem monitor" refers to the entry in 
WRKACTJOB that has the same name as the subsystem description and (at 
least on my system) user QSYS.  It's the one that is outdented in the 
display.  I don't know a lot about that job, but I gather that it takes 
care of the coordination of the other jobs within the subsystem.

I took from your post that it's that job that should not run in a shared 
pool for performance reasons (if, for example, there were no activity 
slots available then slow job startup could occur).  Thus my questions 
about two pools, and how to route that monitor job.  If I'm completely 
offbase, I'm sure you'll let me know.  :)


On 12/22/2018 11:27 AM, Joe Pluta wrote:
> That implies two pools, one for the monitor and one for the jobs.  I 
> don't see any obvious way to route the monitor, so does it magically 
> get  assigned to the first pool defined in the POOLS keyword?  That 
> would mean something like
>
> POOLS((1 *BASE) (2 *SHRPOOLx))
>
> If so, then I have to change all my routing entries to point to the 
> second pool.  Not impossible, but a bit more tedious since MIMIX has 
> about 20 routing entries.  Or is there a special routing entry you can 
> add just for the subsystem monitor?
>
>
> On 12/22/2018 11:11 AM, Jim Oberholtzer wrote:
> > Joe,
> >
> > In that misconfiguration IBM i saves you buy simply moving the job to 
> > *BASE (In my view the job should fail to start but that's another 
> > discussion) so work continues.
> >
> > One other thing.  Vision/Syncsort recommending that the Mimix 
> > subsystem only have a shared pool is in my opinion (and many other 
> > folks) incorrect.  The subsystem monitor needs to get an activity 
> > level whenever it wants, and it could very likely run into conflicts 
> > if the specific shared pool is not set up properly.  I've fixed this 
> > at I don't know how many Mimix customers.  Now jobs in those 
> > subsystems start quickly and get on with it without any hold up.
> >
> >
> > --
> > Jim Oberholtzer
> > Agile Technology Architects
> >
> > -----Original Message-----
> > From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> On Behalf Of Joe 
> > Pluta
> > Sent: Saturday, December 22, 2018 11:05 AM
> > To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> > Subject: Subsystems, Shared Pools and Routing Entries
> >
> > I'm just going through some steps to clean up a few things.  One 
> > thing is that the fine folks from MIMIX recommend we move MIMIX into 
> > its own pool.  Not a bad idea.  They recommend a shared pool rather 
> > than a private pool, and I'm okay with that.  I was able to create 
> > the shared pool with no problem by assigning memory to it (although 
> > I'm not sure how to remove it, but that's a different issue).  And 
> > then they say to set up the MIMIX subsystem to have only that shared 
> > pool using POOLS((1 *SHRPOOLx)).  Again, I understand.  And finally, 
> > make sure all the routing entries point to pool 1 (which they should 
> > have been already, and were).
> >
> > So I'm okay with this.  Instead of all the MIMIX routing entries 
> > shoving jobs into *BASE, they'll now go into a shared pool. Yay!
> >
> > But while reviewing things I ran into a weird case.  I found a 
> > subsystem pointing to a shared pool, but the shared pool has no 
> > memory defined in WRKSHRPOOL.  For arguments sake, say it has 
> > POOLS((1 *SHRPOOL6)) but
> > *SHRPOOL6 is currently defined with no memory.  How does THAT work? 
> > Obviously it's wrong, but the subsystem is running.  Since that 
> > subsystem is incorrectly defined, do all the routing entries just get 
> > funneled into *BASE? That's what seems to be happening according to 
> > WRKACTJOB.
> >
> >
> >
> > --
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) 
> > mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To 
> > subscribe, unsubscribe, or change list options,
> > visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take 
> > a moment to review the archives at 
> > https://archive.midrange.com/midrange-l.
> >
> > Please contact support@xxxxxxxxxxxx for any subscription related 
> > questions.
> >
> > Help support midrange.com by shopping at amazon.com with our 
> > affiliate link: https://amazon.midrange.com