× 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.


  1.  Home
  2. RPG400-L
  3. April 2013

RE: Troubleshooting a stalled procedure

Michael Ryan:

You mentioned web service. Is it waiting for something to be returned
from the web service call?

I'd like to think so, but in other testing, the web service returns results within about 20 seconds. And I can get the debugger to pause on the line that sends the call.
-- Michael Koester

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

You mentioned web service. Is it waiting for something to be returned
from the web service call?


On Thu, Apr 4, 2013 at 2:05 PM, Koester, Michael <mkoester@data-
east.com>wrote:

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


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.