Re: Question about Cursors - SQLRPGLE

[rob@xxxxxxxxx]

I saw that in the archives that
     C/EXEC SQL
     C+ Set Option
     C+     CloSqlCsr = *EndMod
     C/END-EXEC
was suggested.

It was also noted that sometimes even that doesn't work and a ALCOBJ 
OBJ(xxx) CONFLICT(*RQSRLS) may be in order.

I think I am running into one of those situations.

SQL statement from GDMENU2
     C/EXEC SQL
     C+  select MANAM into :MANAM
     C+  from ZMA
     C+  where (MAID='MA' or MAID='GD')
     C+    and MAUSR=:USER
     C+    and (MANAM='SAMENU'
     C+        or MANAM='RAMENU'
     C+        or MANAM='SAMEN2'
     C+        or MANAM='RAMEN2')
     C+  fetch first row only
     C/END-EXEC

MENU3R1 calls
  GDMENUC calls
    GDMENU calls
      GDMENU2C calls
        GDMENU2
"Sometimes" exitting back to MENU3R1 leaves ZMA file locked.  Exitting 
MENU3R1 back to command line frees up the lock.
GDMENU2 

When I run it in debug:
...
CPI4325-Temporary result file built for query. ...for reason code 13.
  13 - The query involves a static cursor or the SQL FETCH FIRST clause.
...
Upon exit of MENU3R1...
5 >  *SYSTEM/DSPJOB 
    Connection to relational database GDIHQ ended.
    SQL cursors closed. 

DSPPGM GDMENU2
Close SQL cursor . . . . . . . . . . . . . . . :   *ENDMOD

It's all in the same activation group.

Haven't tried the ALCOBJ yet.  Just wondering why I would need to.

Rob Berendt