RE: Embedded SQL Question

The Cursor name must be unique within the same member, i.e. it is not
allowed to use the same cursor name within different independent procedures
coded within the same source member.

If you want to read the same cursor from different programs, i.e. first
program reads the first row, next program reads the second row and again the
first program reads the 3rd row, I'd suggest to write a procedure or a
separate program (while procedure is better) which is called from both
programs.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
?Train people well enough so they can leave, treat them well enough so they
don't want to.? (Richard Branson)


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vinay
Gavankar
Sent: Donnerstag, 16. Februar 2017 17:37
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Embedded SQL Question

I am confused about "unique cursor name" warning. Only Program X has
embedded SQL. So let us say I use a unique cursor name PGMX_C1, which is not
used in anywhere else on the LPAR. When Program A & B call Program X, is
there a chance that I will run into an issue?

On Thu, Feb 16, 2017 at 11:32 AM, <dlclark@xxxxxxxxxxxxxxxx> wrote:

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 02/16/2017
11:24:06 AM:

It's never really been a concern to me. And it is quite common for
everyone to use the same cursor name
Declare C1 cursor for...
kind of stuff.

Never heard of someone getting bit by that.

We have -- not with reading each other's cursors, but with
ODP's (or something) not getting rebuilt when they should. Unique
cursor names will insure that SQL correctly handles everything it
should. You see, in our case we have the same object name in multiple
libraries -- with initial library lists controlling which libraries
are available at any given time. But we have run into issues when we
need to go across libraries against the same object name. Activation
groups are one thing, but unique cursor names are the rest of the picture.

Sincerely,

Dave Clark
--
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300

Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331




************************************************************
*********************************
This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or
proprietary information. If you have received this message in error,
please immediately notify the sender and delete and destroy the
message and all copies. All unauthorized direct or indirect use or
disclosure of this message is strictly prohibited. No right to
confidentiality or privilege is waived or lost by any error in

transmission.

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

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

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

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD