|
Chuck.
(Roger Pence works at ASNA...)
-sjl
"Dan" wrote in message
news:CALhCG5BEyisUtnoKFbdsj-8GNo4DKe+usMzA4JO9w+v_4ee8rA@xxxxxxxxxxxxxx...
Roger <<<, thank you for your reply. Your suggestion to add the
predicate "andWHFNAM <> WHPNAM" had no impact on the behavior.
- Dan
On Mon, May 11, 2015 at 4:18 PM, CRPence <crpbottle@xxxxxxxxx> wrote:
On 08-May-2015 09:37 -0500, Dan wrote:
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
On 07-May-2015 11:22 -0500, Jonathan Mason wrote:
In the looping case, for which the CYCLE specifications apparently could
I use the following UDTF which produces an indented hierarchicalthis query to loop endlessly? I just tried this on another program,
list of objects and programs/modules/service programs that call
them. <<SNIP>>
Are there any scenarios of which you're aware that would cause
and let the query run for a good 10 minutes before I killed it.
The job had no halts; the CPU was running, and the temp storage on
the job was climbing into the tens of gigabytes. I'm not sure how I
would debug this. The other five programs I tried with this finished
within 5 seconds. I would expect the depth on this program to be no
more than 10 levels, probably closer to 5.
<<SNIP>>
not properly stop the iterative processing of recursion, what was the
result set for the initialization SELECT; i.e. what was the result-set of
the following query, replacing :iObject with the the program name
specified
as the value for which the looping was exhibited as the effect?:
select WHFNAM, WHOTYP, WHLNAM, WHPNAM
from PGMREFS
where WHFNAM = :iObject
and WHLNAM not in('QSYS', 'QGPL')
And what was the Display Program References (DSPPGMREF) that generated
the data for the Output File (OUTFILE) named PGMREFS that was referenced
in
the above SELECT?
Just a SWAG, but if the following predicate was appended, ANDed as
composed, to the above query, does the problematic looping persist or is
the issue resolved?:
and WHFNAM <> WHPNAM
--
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.
--
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 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-2025 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.