RE: CPU usage for QZDASOINIT -- MIDRANGE-L

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

Subject: RE: CPU usage for QZDASOINIT
From: Buck Calabro <Buck.Calabro@xxxxxxxxxxxx>
Date: Thu, 29 Aug 2002 14:43:23 -0400
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>

>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

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: CPU usage for QZDASOINIT , Adam Lang

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.