Re: SQL statements through JDBC causing QPSRVDMP's

[Pete Helgren <Pete@xxxxxxxxxx>]

That might be a possibility Vern, I'd look into it but it appears the 
application is using some syntax that is incompatible with V5R3M0.  
Specifically, it uses row_number() over() to get some information it 
uses to track what rows are displayed so I need to find a work around 
(it looks like on V5R4M0 has this and it wasn't PTF'd back to V5R3M0).  
The customer I was test against it at V5R4M0 but my machine here back at 
the office is V5R3M0.

I'll post that issue in a separate thread.  Then,  once I get the 
application talking to DB2 again, I'll pursue the DUMP issues.

Pete


vhamberg@xxxxxxxxxxx wrote:
> Pete
>
> Crazy thought - is there a CCSID of 66535 anywhere in the mix? Individual fields? System? The JDBC stuff started requiring a real CCSID at one point.
>
> Vern
>
>  -------------- Original message ----------------------
> From: Pete Helgren <Pete@xxxxxxxxxx>
>   
> > Elvis,
> >
> > FWIW, I am getting a dump, not a job log, which I suppose is a good 
> > thing if it wasn't in hex.  I did run STRDBMON from Navigator and I can 
> > see the statements. Nothing looks strange to me and the few statements 
> > that I knew what to substitute in for the ? parameter markers, ran fine 
> > using interactive SQL. (Man, I wish there was a way to see the actual 
> > statements that were processed, including what as substituted in for the 
> > parameter markers so you could just cut and paste into interactive SQL...)
> >
> > I think the connections coming and going are a by-product of the abends 
> > that are happening with the dumps, although I can't say that for sure.
> >
> > I'll do some additional searching.  I am also going to try this on a 
> > V5R3M0 box and see if anything different happens.
> >
> > Thanks
> >
> > Elvis Budimlic wrote:
> >     
> > > Might be an issue with the query engine.  
> > > There are probably SQE traces in the IFS, VLOGs and perhaps a problem you
> > > can report (WRKPRB).
> > >
> > > Since you have a joblog, you may also want to search for an existing PTF (if
> > > there is one) using some eye-catching keyword:
> > >
> > > http://www-912.ibm.com/ImprovedSearch/searchoptions.jsp
> > >
> > > If that doesn't yield any APARs/PTFs, open a PMR with IBM.  I'm sure they'll
> > > be able to figure out what's happening with the joblog and other traces
> > > available to them.
> > >
> > > BTW, you can see what queries are running in a number of ways.  One of the
> > > easy to use ones is database monitor (STRDBMON).  Other is JDBC exit point.
> > > Not sure knowing what the query is will help you though, but dbmon also
> > > captures errors.
> > > Also, the fact that your Java tool doesn't maintain persistent connections
> > > is hurting your performance (QZDASOINIT jobs disappear/reappear quickly).
> > >
> > > HTH, Elvis
> > >
> > > Celebrating 11-Years of SQL Performance Excellence on IBM i5/OS and OS/400
> > > www.centerfieldtechnology.com
> > >