Chuck,
I added the DSPJOB for program stack and when I was able to recreate the duplication I found this dspjob:
5722SS1 V5R4M0 060210 Display Job 6/30/16 12:23:15 Page 1
Job . . . : DEVA1 User . . . : DDHAYES Number . . . . : 398973
Job Call Stack
Thread . : 000007BD
Module or Ctl
Type Program Statement Identifiers Instruction Activation Group Expanded Type Bdy
QCMD QSYS 0512 *DFTACTGRP 0000000000000001 Y
QUICMENU QSYS 00C1 *DFTACTGRP 0000000000000001 N
1 QUIMNDRV QSYS 060C *DFTACTGRP 0000000000000001 N
2 QUIMGFLW QSYS 04C8 *DFTACTGRP 0000000000000001 N
3 QUICMD QSYS 048D *DFTACTGRP 0000000000000001 N
STRJDE UTILITY 1500 0015 *DFTACTGRP 0000000000000002 N
J98INITA JDFOBJ 13800 00EB *DFTACTGRP 0000000000000002 N
J98INITV JDFOBJ 19500 00FB *DFTACTGRP 0000000000000002 N
P00MENU JDFOBJ 05DF *DFTACTGRP 0000000000000002 N
J04257 JDFOBJ 2300 0012 *DFTACTGRP 0000000000000002 N
P04257 CCXJDEOBJ 164300 0984 *DFTACTGRP 0000000000000002 N
P04257W2 CCXJDEOBJ 145000 0743 *DFTACTGRP 0000000000000002 N
P04571 CCXJDEOBJ .RESPGM 03C5 *DFTACTGRP 0000000000000002 N
P04572T3 CCXJDEOBJ *DFTACTGRP 0000000000000002 P04572T3 QTEMP Y
Procedure: _QRNP_PEP_P04572T3
P04572T3 CCXJDEOBJ 163200 *DFTACTGRP 0000000000000002 P04572T3 QTEMP N
Procedure: P04572T3
P04572 CCXJDEOBJ 33015 015E *DFTACTGRP 0000000000000002 N
J04572CCX CCXJDEOBJ 1900 000D *DFTACTGRP 0000000000000002 N
* * * * * E N D O F L I S T I N G * * * * *
I see the T3 program listed 2 times, but not sure the implications of that.
And this is what it looks like when I do not have the issue:
5722SS1 V5R4M0 060210 Display Job 6/30/16 12:26:28 Page
Job . . . : DEVA1 User . . . : DDHAYES Number . . . . : 398973
Job Call Stack
Thread . : 000007BD
Module or Ctl
Type Program Statement Identifiers Instruction Activation Group Expanded Type Bdy
QCMD QSYS 0512 *DFTACTGRP 0000000000000001 Y
QUICMENU QSYS 00C1 *DFTACTGRP 0000000000000001 N
1 QUIMNDRV QSYS 060C *DFTACTGRP 0000000000000001 N
2 QUIMGFLW QSYS 04C8 *DFTACTGRP 0000000000000001 N
3 QUICMD QSYS 048D *DFTACTGRP 0000000000000001 N
STRJDE UTILITY 1500 0015 *DFTACTGRP 0000000000000002 N
J98INITA JDFOBJ 13800 00EB *DFTACTGRP 0000000000000002 N
J98INITV JDFOBJ 19500 00FB *DFTACTGRP 0000000000000002 N
P00MENU JDFOBJ 05DF *DFTACTGRP 0000000000000002 N
J04257 JDFOBJ 2300 0012 *DFTACTGRP 0000000000000002 N
P04257 CCXJDEOBJ 164300 0984 *DFTACTGRP 0000000000000002 N
P04257W2 CCXJDEOBJ 145000 0743 *DFTACTGRP 0000000000000002 N
P04571 CCXJDEOBJ .RESPGM 03C5 *DFTACTGRP 0000000000000002 N
P04572 CCXJDEOBJ 33015 015E *DFTACTGRP 0000000000000002 N
J04572CCX CCXJDEOBJ 1900 000D *DFTACTGRP 0000000000000002 N
* * * * * E N D O F L I S T I N G * * * * *
Thanks,
Danny Hayes | Sr JDE Developer - IT | 813 901-2150 x133154
-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Tuesday, June 28, 2016 8:52 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: I have an anomaly, please explain to me. **External Email**
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.?
--
Regards, Chuck
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx<mailto:RPG400-L@xxxxxxxxxxxx> To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx<mailto:RPG400-L-request@xxxxxxxxxxxx>
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related questions.
This communication is intended only for the use of the individual or entity named as the addressee. It may contain information which is privileged and/or confidential under applicable law. If you are not the intended recipient or such recipient's employee or agent, you are hereby notified that any dissemination, copy or disclosure of this communication is strictly prohibited. If you have received this communication in error, please immediately notify CareCentrix Compliance Hot Line at (877) 848-8229 and notify the sender by electronic mail. Please expunge this communication without making any copies. Thank you for your cooperation.
midrange.com
