As far as I know, the unique cursor name requirement is only within a given module.
-----Original Message-----
From: Vinay Gavankar [mailto:vinaygav@xxxxxxxxx]
Sent: Thursday, February 16, 2017 10:37 AM
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:
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.