re: SQLRPGLE cursor questions

Dieter wrote:

... if local means local to a procedure, it doesn't make too much sense,

because a cursor is not stateless. To encapsulate a > cursor, put it to a
module with setXXX and getXXX procedures and write data Access modules.

Yes, local to a procedure, or "Subprocedure" as named in the RDP outline.

I'm in over my head, but I see legacy RLA as "not stateless", so
thought maybe I would not need to declare cursors uniquely
between subprocedures.

Now, I know this does not work, but am not sure why.

For example: can a service program successfully declare a cursor
having the same name as cursor declared in a module invoking that
service program?

How about a called stored proceedure?