I initially wrote about the SET_SERVER_SBS_ROUTING procedure in this post, Route Db2 Requests to a Specific Subsystem, and then again in this post, Route Remote Command Requests to a Specific Subsystem. I’m back again with another post to tell you about more enhancements to this IBM i Service.
(more…)If you’re like me, it was nice to take a break from work last week. This week is turning out to be very busy, so this blog is very brief.
In the blog, Route Db2 Requests to a Specific Subsystem, I described the support that allows you to route work requests by user profile for the QZDASOINIT and QRWTSRVR server jobs.
(more…)In the blog Route Db2 Requests to a Specific Subsystem, I wrote how you can use the QSYS2.SET_SERVER_SBS_ROUTING procedure to route work for database queries using the QZDASOINIT or QRWTSRVR server jobs to customized subsystems. This is a new way to route work based upon the requesting user profile that augments the other ways you can route work to subsystems.
(more…)We all know that a key advantage to IBM i is the work management capabilities, in particular the ability to segregate work into different subsystems. One of the more challenging areas for this, however, has been prestart server jobs. By default, these prestart jobs run in the QUSRWRK subsystem. You can configure the subsystem in which these prestart server jobs run by routing the requests based upon the client IP address, but that’s often not sufficient. Many requests may come from one IP address, or perhaps you would like to segregate work based upon some other criteria – for example, the requesting user profile.
(more…)