|
It all depends on what the Query Optimizer wants to do. I've seen plenty of times where the OPNQRYF will finish immediately, but the real work happens once you start to use the data. With that many records, GSORT would be faster too :-) Art On 2/21/07, Doug Palme <dpalme@xxxxxxxxxxx> wrote:
I am not the one running it, I would have not used opnqryf myself and yes it does take a while to run (about 4 hours). I was trying to figure out why they were running at the same time. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pat Barber Sent: Wednesday, February 21, 2007 9:03 AM To: Midrange Systems Technical Discussion Subject: Re: Is this unusual? OPNQRYF | CPYFRMQRYF That doesn't sound correct. Cpyfrmqryf needs a open data path to copy from. Job logs are not real clear when checking on opnqryf. That's a really large file to be using opnqryf against. That job must run for a while ? Wouldn't a logical make more sense ? Is the job doing record selection or just using opnqryf to sort the file ? You could actually end up with "2" files of 25mb using this method. Douglas Palme wrote: > We are running a CL in batch that is opening a query file over a PF with > approx 25m records, the next line of code is CPYFRMQRYF. > In checking the job log it appears that BOTH are running simultaneously. -- 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. **************************************************************************** This transmission may contain information that is privileged, Confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. **************************************************************************** -- 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 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.