Shooting randomly...

Specify ACTGRP(*NEW) in your SQLRPGLE source to ensure that upon termination, that all resources are closed... OR
RCLACTGRP to reclaim the resources after the program returns to CL...

Any Triggers over the file? Triggers have to be sensitive to commit status too...

In your application with the read only cursor, you seem to say you have other statements to do inserts, deletes, updates... Why not use an updatable cursor, and then:
delete ... where current of MyCursor,
Update ... where current of MyCursor,

Hope some of this might narrow your issue.
-Eric DeLong

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Campin
Sent: Friday, March 02, 2012 11:09 AM
To: Midrange Systems Technical Discussion
Subject: Re: Journaling commit issue with SQL open path remaining open.

I think something else is going on. Commits are not held up because a table
is open. That would mean that no running program could commit until a file
was closed. You need to find out which job is issuing the updates and find
out why commits are not being run.

On Fri, Mar 2, 2012 at 9:10 AM, Michael Schutte <mschutte369@xxxxxxxxx>wrote:

Having an issue with a continuously running program.

CL program is scheduled to run. This CL program will issue DLYJOB 600
after making calls to RPGLE and SQLRPGLE programs and then wake up and do
it all over again.

One of the programs that it calls is a SQLRPGLE program. The SQL program
was compiled with CLOSQLCSR(*ENDACTGRP).

This program declares a cursor (for read only).
Opens the cursor
Fetch one record
Dow sqlcod = 0

SQL Selects to the same file defined in the cursor.
SQL Inserts, deletes and or updates occur.

fetch next record
Close the cursor
*Inlr = *on

When the program ends, you still see the files active when you do a 14 to
do a DSPJOB for the cl that is running.

I do understand that you can change the compile to CLOSQLCSR(*ENDMOD) and
that might fix the issue. Or do a RCLRSC in the cl before going to asleep.

The issue is that the Journal Commits are backing up and not executing
because the file is still active. This has only become a problem since
yesterday, the program has been running for several months. (FYI, the job
does end daily and restarts daily but runs for the entire day with the
delay wait of 600).

There doesn't appear to be any changes made to the iSeries. I would have
imagined that if the SQL open data paths were causing this Journal Entry,
then would have been a BIG problem at my previous employer where SQL was
widely used.

Any thoughts?

Hope I was clear.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by 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].