×
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.
On 03 May 2012 06:27, John Rusling wrote:
Not expected. EDCNW1 is called by EDPROC, but EDCNW1 doesn't call
anything itself.
On 02 May 2012 19:46, CRPence wrote:
<snip>
It appears this CLLE program EDPROC was invoked with recursion by
the RPG program EDCNW1; i.e. the stack shows EDPROC calling EDCNW1
which then calls EDPROC. That may or may not be expected.?
</snip>
OK. Been a long time, so maybe I am misinterpreting something.
Looking closer, perhaps this is how a stack is manifest for a failed
call via EDPROC; i.e. something like LIC exception 080# [see WRKMSGD
MCH0800 and review the range for suspects] upon an attempt to invoke the
EDCNW1 in WZZZJBL0 Procedure: _QRNP_PEP_EDCNW1 which, per seeing the
PEP, might be the case. In that case, the source of the error is the CL
request [¿CALLPRC?] at statement 64600 which is at fault.
I just confirmed that [way back when] the message range MCH0800 [aka
MCH080#] all have DMPLST(*JOB). Even more corroboration that is a
reasonable guess at the fault\origin for the dumps.... and that the
stack is manifest in that [initially confusing to me] manner.
Regards, Chuck
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.
midrange.com
