Is your JOBLOG outq filling up with annoying JobLog completion messages after a JDBC connection from a servlet? Look at the Joblogs in your Joblog outq and see if you find some that have Job nnnnnn/QEJB/QZSOSIGN started on ... in subsystem ... in it. Does it show that it ended with CPF1164 Completion 00? If you are getting many joblogs for this completion message then you can end this nuisance by doing the following: Check to see if Subsystem QUSRWRK is active. This subsystem was added in release V4R5 to shift work from QSYSWRK. If your company is like many companies you probably use your old QSTRUP (IPL program) from a previous release and might not be aware that in the sample QSTRUP they added a new subsystem called QUSRWRK to be started. Without QUSRWRK being active, the WebSphere Application Server's (WAS) version 3.5.x JDBC connection job will use whatever JOBD/subsystem is available including it's own QEJBJOBD in QEJBSBS. When this happens the joblogs pile up. If your QUSRWRK is active, and this still happens then you need to look at the Joblog carefully and see what JOBD/subsystem it is using and adjust your QSTRUP CLP to start QUSRWRK before it. Generally speaking, QUSRWRK should be started after QSPL in QSTRUP.
==================================
MORE INFORMATION ON THIS TOPIC
==================================
Ask your Web development questions--or help out your peers by answering them--in our live discussion forums.
The Best Web Links: tips, tutorials and more.
Check out this live Q&A with Dave Slater and Jim Mason, How to best get started with WebSphere Development Tools.
