by Dawn May | Jul 24, 2017 | Server Jobs, Subsystems, Networking
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.
by Dawn May | Apr 18, 2017 | Subsystems, Documentation, IBM i Services, Work Management
Some of you may have read the subsystem configuration experience reports that were written way back in 2004, which was about when V5R3 became available. The experience reports were under the related information section of the Work Management topic. The subsystem configuration experience reports were covered in three sections:
- Why multiple subsystems are important, along with how to configure subsystems for server jobs
- How to configure interactive subsystems
- How to manage server jobs
by Dawn May | Dec 1, 2015 | Server Jobs, Subsystems, IBM i Services, Work Management
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.
by Dawn May | Nov 10, 2015 | Prestart Jobs, Server Jobs, Security, Work Management
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.
by Dawn May | Jun 27, 2012 | Server Jobs, Navigator for i, Networking, Work Management
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.