Way back in V5R1, IBM introduced the ability to route FTP and SMTP workloads to their own subsystems. By default, FTP and SMTP server jobs run in the QSYSWRK subsystem, along with a lot of other IBM i server jobs. The Server Table in the IBM i Knowledge Center documents all the IBM i server jobs along with the default subsystem in which they run. The server table does state the subsystem is configurable for these servers, but it doesn’t give you any more information.(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.(more…)
While at a conference this fall, I was asked about job accounting and prestart jobs. I thought this would be a good blog topic.
If you have set up job accounting, the system will write journal entries to the job accounting journal when the accounting code is changed or when a job ends.(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…)
Years ago, when TCP/IP was starting to become the networking standard of choice, it was not automatically when the system was started. You had to edit the system start-up program to automate starting TCP/IP and related interfaces and servers.(more…)
We all know and use TCP/IP servers. Many of these servers are set up to start when TCP/IP is started and all servers have the ability for this configuration value to be changed.(more…)