Re: Embedded SQL Question

The need unique cursor names across the entire system is spurious at best, and makes system maintenance difficult or maybe even impossible if you use third party software that has embedded SQL. If you don't have the source, how would you know what cursor is being used? You must have had some special situation. I have always used C1, and never run into problems.

Mark Murphy
Atlas Data Systems
mmurphy@xxxxxxxxxxxxxxx


-----dlclark@xxxxxxxxxxxxxxxx wrote: -----
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
From: dlclark@xxxxxxxxxxxxxxxx
Date: 02/16/2017 11:40AM
Subject: Re: Embedded SQL Question


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

I have never used Embedded SQL programs, and I am asking this question

on

behalf of a colleague, so please excuse me if it appears a little vague.

If I have Program X, which uses embedded SQL, and there are 2 programs A

&

B, running in the same job stream and same Activation Group, which call
Program X, is it possible that programs A and B could be reading each
other's cursor?

If yes, would running them in separate Activation Groups solve the

issue?

Is there any other way to overcome the issue?

At the very least, just make sure your cursor names are unique
across the system. If you're using cursor names like C1, etc., you can
run into problems.

Sincerely,

Dave Clark