RE: PJ Type Jobs

["Dennis Lovelady" <iseries@xxxxxxxxxxxx>]

To answer your question:
http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?topic=/com.ibm.
db2.udb.apdv.sample.doc/doc/java_jdbc/s-DbRsHold-java.htm

Maybe we should start again.  What problem are you having because the PJ
remains active?

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"A statesman is a politician who's been dead ten or fifteen years."
        -- Harry S. Truman 


> Do u have an example how to close "Result Sets Properly"
>
> Chamara
>
>
> On Thu, Oct 14, 2010 at 5:43 PM, Charles Wilt
> <charles.wilt@xxxxxxxxx>wrote:
>
> > There's _always_ pre-start QZDASOINIT jobs running...as long as the
> > *DATABASE host server jobs are running.
> >
> > Or do you mean that specifically, you see QZDASOINIT jobs that appear
> > to still have a connection open?
> >
> > Probably your Java code is using connection pooling...
> >
> > So even though your application is closing the connection, in reality,
> > the connection remains opens and goes back into the pool.
> >
> > Things are working as designed, and there shouldn't be an issue, if
> > you java code is closing results sets properly.
> >
> > Charles
> >
> > On Thu, Oct 14, 2010 at 6:23 AM, Chamara Withanachchi
> > <chamaraw@xxxxxxxxxx> wrote:
> > > Dear All,
> > >
> > > We are connecting to our IBM i from Java an reading/writing to SB2
> files,
> > > even the Java job ends (Closed the connection) we can see some PJ
> type
> > jobs
> > > in the system remains. How to overcome this?