Creating New ODP for a file

I have a procedure within a service program that calls itself recursively.
This procedure has the standard SETLL, READE  read loop.
For each subsequent call I need a new unshared open data path for the file in
the read loop.  The reason for this is when I return back to the procedure don't
want the file pointer to be affected by the previous calls to the procedure.

Is there a way that I can create an new open data path and use it within each
call to the procedure?

I've tried creating a module that is called when the procedure is first entered
into, this module does an OVRDBF.  I've tried OPNDBF with a new unique OPNID on
each procedure call.   The file is setup to have USROPN.  So I do an explicit
open if it's not already open.  The service program is created with a named
activation group.
Some of the parameters I've used on the OVRDBF that haven't worked are:

OVRDBF     FILE(OECLSFCN02) SECURE(*YES) OVRSCOPE(*CALLLVL) SHARE(*NO)
OVRDBF     FILE(OECLSFCN02) SECURE(*NO) OVRSCOPE(*CALLLVL) SHARE(*NO)
OVRDBF     FILE(OECLSFCN02) SECURE(*YES) OVRSCOPE(*ACTGRPDFN) SHARE(*NO)
OVRDBF     FILE(OECLSFCN02) SECURE(*NO) OVRSCOPE(*ACTGRPDFN) SHARE(*NO)

Any ideas would be helpful.
Thanks in advance.
Brian Ellis.








+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---