Re: Query Manager Queries -- 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: Query Manager Queries
From: Buck Calabro <kc2hiz@xxxxxxxxx>
Date: Thu, 15 Jun 2023 13:17:18 -0400
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

On 6/15/2023 12:51 PM, James H. H. Lampert via MIDRANGE-L wrote:

I'm analyzing some very complex customer code that does a few things I'd never seen before. Including running Query Manager queries

I found this for extracting the SQL for inspection, using RTVQMQRY:

https://www.rpgpgm.com/2013/08/getting-sql-statement-of-query.html

but I'm not entirely sure where the data from the query definitions I'm looking at is actually going.

Can somebody shed some light on this?

The retrieved source goes into the source file that is specified on the RTVQMQRY command.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Query Manager Queries , James H. H. Lampert

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.