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


  1.  Home
  2. MIDRANGE-L
  3. December 2014

Re: how to determine cost savings based on resource utilization

As to OPNQRYF, things are better at 7.2 -

With 7.2, some native database access begins to use SQE by default, including:

* Work with Query (WRKQRY) command, when one of the run options is used
* Run Query (RUNQRY) command
* Open Query File (OPNQRYF) command

This does make the question of converting from OPNQRYF to true SQL a murkier one, I think - AND it lets us leave the OPNQRYF usage alone in many cases.

Not sure this helps the OP make a decision - except to update hardware, not code, as others have stated.

Vern

On 12/3/2014 8:00 PM, Nathan Andelin wrote:
I think it has already been well articulated that code modernization won't
reduce resource utilization (CPU, memory, storage, etc.). It's more likely
that more compute resources will be consumed after a modernization
initiative.

One exception may be if your OPNQRYF definitions are not properly aligned
with your database indexes. In that case the SQL SQE could improve
performance a lot.
-snip-

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
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.