×
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.
If it is a record lock the WRKACTJOB list should show a status of LCKW.
at least during the lock. We have a few jobs that wait the default 60
seconds, then go into a delay and try again until the record or file is
clear.
From:
Buck Calabro <kc2hiz@xxxxxxxxx>
To:
rpg400-l@xxxxxxxxxxxx,
Date:
04/04/2013 12:49 PM
Subject:
Re: Troubleshooting a stalled procedure
Sent by:
rpg400-l-bounces@xxxxxxxxxxxx
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
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
