RE: Troubleshooting a stalled procedure

Charles, the call stack looks like this:
Type Program Statement Procedure
QCMD QSYS /0519
QUICMENU QSYS /00C1
1 QUIMNDRV QSYS /0610
2 QUIMGFLW QSYS /04D7
3 QUICMD QSYS /056F
4 QCMD QSYS /01C8
TESTSTUFF GSTTSTLIB _QRNP_PEP_TESTSTUFF
TESTSTUFF GSTTSTLIB 9100 TESTSTUFF
WS3PRVSN GSTTSTLIB 2100000001 WS3GETRGDV

That's it, and it stays that way until I cancel the job.

-- Michael
~~~~~~~~~~~~~~~~~

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-
bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Thursday, April 04, 2013 2:00 PM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: Troubleshooting a stalled procedure

Working along Buck's line of thought...
C
an you copy and paste the call stack?

If your procedure isn't the last one, that would tell you something.
In particular, if Buck is right, one of the well-known DB routines
would be last.

Charles


On Thu, Apr 4, 2013 at 1:49 PM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 4/4/2013 1:35 PM, Koester, Michael wrote:

... but 1) Without debug, WRKACTJUB > call stack shows the same
thing

(indefinitely).

OK so it's really a problem with the code and not the debugger.

...call stack confirms that the intended procedure is at stmt
2100000001 (whatever that is), but nothing else happens.

You can tell what that statement is by looking at the compiler

listing.

Typically, numbers like that are I/O. Is it possible there is a
record lock and the wait time is really long? That would look like a

'stuck'

program.
--buck