RE: SQL issues in program

I have the job running right now. It successfully completed 6 files and is
now stuck. The call stack shows the following 3 programs after the calls to
my programs:

Program Statement Procedure
QSQROUTE QSYS 8402 QSQROUTE
QSQRUN3 QSYS 10636 SQL_Insert
QDBGETMQO QSYS 2765 QDBGETMQO

It is still at a run status. I have let it just run for as long as 7 hours.
I never see anything different in the call stack and there are no messages
returned. Is there something I can look at in debug or somewhere else to
determine what it is doing or what is wrong?

Could it have something to do with the previous occurrence of Insert/Delete
having 0 records?

Thanks!


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Scott and Kelly Curry
Sent: Tuesday, September 20, 2011 7:48 PM
To: 'RPG programming on the IBM i / System i'
Subject: RE: SQL issues in program

It shows the procedure SQL_Insert or SQL_Delete then the last program is
QDBGETMQO. I am going by memory, but I believe that is correct. I will post
the actual job call stack tomorrow. It is a batch job so I do a WRKACTJOB
then select that job to view the log, call stack, etc.


-----Original Message-----
From: rpg400-l-bounces+kscurry=bresnan.net@xxxxxxxxxxxx
[mailto:rpg400-l-bounces+kscurry=bresnan.net@xxxxxxxxxxxx] On Behalf Of
Dennis Lovelady
Sent: Tuesday, September 20, 2011 7:05 PM
To: 'RPG programming on the IBM i / System i'
Subject: RE: SQL issues in program

If you WRKJOB and then look at the Call Stack for the job while it's
apparently hung, what are the last few procedures listed? Is a lock
involved? (Sounds like a lock.)

(Don't be tempted to do the WRKJOB from the same job that's running the
program. Look at it passively, from another job.)

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"The unfortunate thing about this world is that good habits are so much
easier to give up than bad ones."
-- Somerset Maugham

I have an SQLRPGLE program that first calls a procedure to insert records
into File A. I then have another procedure that is called repeatedly for
different files. This procedure uses dynamic SQL to insert records into
different files using certain criteria along with File A. Then it uses
dynamic SQL to delete the same records it inserted, also using File A.



My program will run okay for a few files, then it just hangs up on the
insert or delete portion of the SQL. I have put it in debug and it remains
on the execute statement, it isn't looping within the program. There is
nothing changing in the call stack or open files. I removed the file it

got

hung up on and ran it again. It will run then it will hang up on a

different

file.



Is there something specific that needs to be done in my program to allow

it

to properly handle repeated dynamic SQL's? I can include portions of my

code

if helpful. I am not using cursor open/close. I just have Prepare and
Execute statements.



Any help would be appreciated.



Thanks,



Kelly



--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing

list

To post a message email: 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
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.