× 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.



Ok, how would I do it with wrkqry?  Just start the debug, go into wrkqry and
create the query, run it.  end debug and check the log?

Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
http://www.rutgersinsurance.com
----- Original Message -----
From: "Buck Calabro" <Buck.Calabro@commsoft.net>
To: <midrange-l@midrange.com>
Sent: Thursday, August 29, 2002 2:43 PM
Subject: RE: CPU usage for QZDASOINIT


> >Apparently STRSQL is not on the system.
>
> That puts a crimp in things, but not a fatal one.  If you have Query/400
you
> can use that in place of STRSQL.  Or you can use QMQRY.  I am pretty sure
> the FAQ has an entry on using it.  http://faq.midrange.com  The point is
> that if you run an SQL statement in a job with debug active, the SQL
> optimiser puts messages in the job log describing what it considered
before
> running the statement.
>   --buck
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.



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.