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



We have never done anything with this file from what IBM ships and we have one in QSYS and one in QUSRSYS, The one in QSYS is dated 8/10/09 V7R1 and in QUSRSYS 22/21/06 V5R3. So I should probably delete the one in QUSRSYS?

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Thursday, June 06, 2013 11:45 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Performance question and SQL SERVER - RESOLVED

On 06 Jun 2013 04:29, Vernon Hamberg wrote:
So you do have to specify it with CHGQRYA if you want anything other
then the one in QUSRSYS or the defaults. It's important NOT to delete
the one in QUSRSYS, BTW.

In general, a QAQQINI should *not* even exist in QUSRSYS; i.e. none should exist to be deleted. Ideally any copy of QAQQINI in QUSRSYS could and would be deleted on most every system. The one to *not* delete is the file in QSYS.

--
Regards, Chuck
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx 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 ...

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.