×
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 28-Jun-2016 14:42 -0500, Hayes, Daniel wrote:
[…] here is the RPG.
I am not a good choice with regard to reading\reviewing RPG with that
old syntax. AIUI, that program will only perform the CALL @@CCX once
per invocation, and that the program would terminate with LR on
immediately after that CALL; each GOTO seen, should not, AIUI, change
that as the effect.
The joblog showed no indication of P04572 running [i.e. no messaging
from\to that program]. Thus the joblog also shows no indication that
the program P04572 called J04572CCX, despite the implication being, that
must be the case; neither the second invocation nor the first invocation
of the program J04572CCX show any information about how\by-what the CLP
was invoked, so that is consistent.
Seems to me, from what I have reviewed, that the most logical
conclusion is that the program P04572 was invoked twice, and each time
effected the expected\coded, one CALL @@CCX. As I alluded in a prior
reply, seems possible the issue is not that J04572CCX is being called a
second time, but that P04572 is being called a second time; that if a
repeat invocation is a problem, then the OP pursued the wrong invocation
as the origin for that problem.?
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
