RE: OVRDBF from an RPG?

David,

the easiest way would be to work with the UsrOpn and ExtFile keywords for your file definitions.

HTH,


Peter Colpaert
Software Engineer, Philips Consumer Luminaires

Industrieterrein Satenrozen 11, 2550 Kontich, Belgium
Tel. +32/ 3 450 74 09, Fax +32/ 3 450 74 33, Internal 1317
peter.colpaert@xxxxxxxxxxx, www.philips.com

Simply Switch to printing double-sided and printing less

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-
bounces@xxxxxxxxxxxx] On Behalf Of David FOXWELL
Sent: donderdag 2 april 2009 14:57
To: RPG programming on the IBM i / System i
Subject: OVRDBF from an RPG?

Hi,

I've another problem with files with the same names in different
libraries.

I have a Procedure1 in Module1 that calls Procedure2 in Module2.
Procedure2 opens implicitly a file F2. Then it calls Procedure3 in
Module3 which opens a file F3. It's possible that other procedures are
called, opening files in this same, cascading manner.

So after my first call to Procedure2, I'll have Files2 and 3 open when
control returns to Procedure1.

On my next call to Procedure2, I may want Files2 and 3 of a different
library.

Could I just open and close my files in the beginning of Procedures2
and 3, and issue an OVRDBF in Procedure1 ?
Would it work? Would I have to use QCMDEXC or is there an easy API way?


Thanks.
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.