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.
SQL server mode jobs are the jobs named QSQSRVR that run in the QSYSWRK subsystems. One of the more common concerns that has been raised with QSQSRVR jobs is the difficulty to manage them, and in particular, the inability to configure the subsystem in which they run.
In a 2010 7.1 announcement, there was a one-sentence statement that I thought would be good to expand upon:
IBM i 7.1 workload management enhancement enables clients to limit to the number of cores on which a selected workload can run concurrently.
So what is this, why would you want to use it and how do you get it?
This week I’m going to review the support IBM i has for “server jobs.” Most of this is not new, but I’m not sure this is widely known. There are three parts to this:
- How to identify a job as a server job
- How you can define a custom TCP application server
- IBM’s documentation on server jobs