× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Paul,

What do you mean by "If the end user kills the session", you mean if they
close out the Windows app that is making the request?  Its something I
would love to be able to improve for WebSphere too, that is if the user
clicks a button which in the background runs a very long query, they get
fed up waiting for it so go off and choose other links (or log out of the
site) then the QZDASOINIT is left chugging away.  However I don't know of
any way around this.

I'd love to be able to execute queries asynchronously, something like
below, so that we'd have the option of ending stuck or long running
QZDASOINIT jobs through JDBC.  You'd also be able to solve your problem
with it, since you could nicely kill the QZDASOINIT job from the Windows
app just before it closes.  So if anyone has any ideas.....!

Regards,

Nigel Gay,
Computer Patent Annuities.


PreparedStatement stmt = conn.prepareStatment ("<insert complex select
statement here>");
stmt.executeQueryAsync ();  // and have this immediately return rather than
waiting for the iSeries database to actually process the query
boolean continue = true;

while ((continue) && (!stmt.finished ()))
{
      Thread.sleep (500);     // wait 1/2 second

      if (user has given up waiting for the query)
      {
            stmt.kill ();     // ending the QZDASOINIT job
            continue = false;
      }
}

if (continue)
{
      // completed normally
      ResultSet rs = stmt.getResultSetFromAsyncOperation ();
      // etc
}
else
{
      // user got fed up waiting, so show an error page (which they won't
see, because they gave up waiting!)
}

> I got a situation where a large long running JDBC SQL is run from Window
to
> iSeries.  It can take 20 minutes to complete.  If the end user kills the
> session, the OS400 QZDASOINIT job CPU spikes crippling the system.
Someone
> on the list noted a similar issue but solution was mentioned.
>
> Anyone seen this issue and have insight?
>
> Thanks,
>
> Paul Holm
> Senior Web Architect
> PlanetJ Corp.
> Phone: 760-432-0600, Cell: 760-415-8830
> WOW, Web Applications In Under 5 Minutes
> HYPERLINK "http://www.gotWebData.net"; \nhttp://www.gotWebData.net



********************************************************************************
The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee; access to this
email by anyone else is unauthorised.

If you are not the intended recipient: (1) you are kindly requested
to return a copy of this message to the sender indicating that you
have received it in error, and to destroy the received copy; and (2)
any disclosure or distribution of this message, as well as any action
taken or omitted to be taken in reliance on its content, is prohibited
and may be unlawful.
********************************************************************************


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.