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