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.
If you are not familiar with it, the SET_SERVER_SBS_ROUTINGprocedure provides the ability to route work to a specific subsystem based upon the IBM i user profile.
There are two significant enhancements to this procedure on all supported releases – 7.3, 7.2, and even 7.1!
1. These additional host servers are now supported:
o Central server (QZSCSRVS jobs)
o Data queue server (QZHQSSRV jobs)
o File server (QPWFSERVSO jobs)
o Network print server (QNPSERVS jobs)
The servers below were already supported:
o Database server (QZDASOINIT)
o DDM/DRDA server (QRWTSRVR)
o Remote command server (QZRCSRVS)
2. You can now specify to accept or deny the attempt to connect if the subsystem specified for the user profile is not started. Previously, if the subsystem was not active, the request would run in the default subsystem.
This service now has a new parameter, ALLOW_ROLLOVER. This new parameter allows you to specify the action to take if the specified subsystem is not active.
Valid values are:
o NO – If the alternate subsystem cannot be used, the connection request will fail.
o YES – If the alternate subsystem cannot be used, the connection request will succeed by using a batch immediate job in the default subsystem.
If this parameter is not specified, the default is YES.
This function is provided in the base release of IBM i 7.3. For IBM i 7.2 you will need the DB2 Group PTF SF99702, Level 11 or later, and for IBM i 7.1 you need SF99701, Level 40 or later.
You now have even more capability to take advantage of subsystems on IBM i, which is a very powerful way to manage workloads.
This blog post was originally published on IBMSystemsMag.com and is reproduced here by permission of IBM Systems Media.