So what jobs are in the subsystem? You said "the Catalina job and its associated JVM job" but to me those are just a single job/process. Are they separate things in the IBM world?
Thanks for your insights, Mr. Schultz. And yours, too, Herr Hoffmann.
On an IBM Midrange box (AS/400, iSeries, whatever IBM is calling it this week), when a shell script (a non-native construct in the IBM Midrange world - the native equivalent is something called a CL program, which is a compiled object) spawns off a JVM process, it shows up as a separate job, typically with the rather cryptic name QP0ZSPWT.
As I recall, when we first started using Tomcat (6, I think!) on IBM Midrange boxes, the Catalina job would terminate after spawning off the JVM job. Or if you called catalina.sh from a terminal session, you'd get your command line back. This changed with (I think) Tomcat 7.
At any rate, that's literally all that's in the dedicated subsystem (which is fairly easy to set up on an IBM Midrange box; just create a subsystem description, with a private memory pool, if desired, give it a routing entry and a job queue, do a STRSBS on it, and you've got your subsystem, along with a way to send jobs into it).
At any rate, we don't currently have any dumps on that particular customer box, because unless we're planning on having dumps analyzed, they're just wasting disk on a box that is not exactly hip-deep in unused mass storage. Hopefully, the next time this happens, it will happen at a time when our webapp developers aren't hip-deep in other projects (famous last words).
-- JHHL --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
