RE: Creating SQL View in CL closes SQL cursor in RPG program -- MIDRANGE-L

Well, I guess I didn't try everything! I was doing a final test whereby
I ran the RUNSQLSTM statement from within the RPG program. After it
executed I went to the job log and saw that a COMMIT operation had
executed. The primary cursor was then again closed. I searched for
COMMIT in my inbox and found Charles' post. I added "WITH HOLD" to my
cursor DECLARATION and this time it worked - the primary cursor was not
closed! Success!

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Charles Wilt
Sent: Friday, July 25, 2014 10:29 AM
To: Midrange Systems Technical Discussion
Subject: Re: Creating SQL View in CL closes SQL cursor in RPG program

Taking a cue from John Voris' post...

Do you have a COMMIT being done somewhere by chance?

The default for a static DECLARE CURSOR is WITHOUT HOLD - "Does not
prevent
the cursor from being closed as a consequence of a
commit operation."

Reading the docs for WITH HOLD I also notice: "All cursors are
implicitly
closed by a CONNECT (Type 1)"

So I'm thinking your CL is probably initiating a new connection; thus
closing the cursor.

I'd move the create view to the RPG.

Since RUNSQLSTM is an OPM program and runs in the DFTACTGRP, you may be
able to get it to work by running the RPG program in a *NEW or a named
activation group.

Charles

On Fri, Jul 25, 2014 at 10:04 AM, Vernon Hamberg
<vhamberg@xxxxxxxxxxxxxxx>
wrote:

I'm going to suggest that you embed the CREATE VIEW statement into the

RPG

code in a procedure, maybe - make it the first thing you run in the

program.

Or, if the view is needed to do something more with the results from

the

other cursor, put its definition in as part of a JOIN or some such.

Nested

table expression instead of the view.

Otherwise, you might look at the create attribute that controls when

the

cursor is closed. It might make a difference.

HTH
Vern

On 7/25/2014 7:54 AM, Siwicki, Gary (GSiwicki) wrote:

In my RPG program, I call a CL that has a RUNSQLSTM command that uses
the commands in a TXT source member to create an SQL view in QTEMP.

The

only command executed is "CREATE VIEW". When this occurs, there is
already another, unrelated SQL cursor that is open and being

processed

in the RPG program. When the view is created by the CL program, as

soon

as control is returned to the RPG program, the "unrelated" SQL cursor

closed.

I realize this is a very awkward way of creating a view but it was
decided that this is the best way to address the unique needs of the
application. Does anyone know what's going on here? I posted here
because I don't think this really has much to do with RPG.

Gary Siwicki

RPG Developer

Lincare, Inc.

(727) 431-8186

************************************************************
************************************************************
************************************************************
************************
This message originates from Lincare Holdings Inc. It contains
information which may be confidential or privileged and is intended

only

for the individual or entity named above.
It is prohibited for anyone else to disclose, copy, distribute or use

the

contents of this message.
All personal messages express views solely of the sender, which are

not

to be attributed to Lincare Holdings Inc., and may not be copied or
distributed without this disclaimer.
If you received this message in error, please notify us immediately

MailAdmin@xxxxxxxxxxx or (800) 284-2006.
************************************************************
************************************************************
************************************************************
************************

--
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.