Works perfectly.

Thanks a lot Chuck.

Vinay


On Fri, Mar 9, 2012 at 4:02 PM, CRPence <CRPbottle@xxxxxxxxx> wrote:

In Program_A, issue before the CALL Program_B:
OVRDBF &FILEA TOFILE(*FILE) MBR(&MBR) OVRSCOPE(*CALLLVL)

After the CALL Program_B:
DLTOVR &FILEA LVL(*)

Regards, Chuck

On 08-Mar-2012 16:18 , Vinay Gavankar wrote:

I am hoping someone here can help me figure out how to solve this
with minimal changes.

I have a CLLE Program A (which is always a submitted job) which has
the Library, File and Member information (&LIBA,&FILEA,&MBRA).

Program A calls a CLLE Program B with only Library & File as
parameters (&LIBA &FILEA).

Program B does an OVRDBF for FILEX with Library & File name -

OVRDBF FILE(FILEX) TOFILE(&LIBA/&FILEA)

and then calls CBLLE Program C, which opens the file.

I want the &MBRA to be opened.

I am free to change Program A.

Program B is an old program being called from multiple places, so
I want minimum changes to it (avoid passing a new parameter, if
possible).

Is there a way I can do an override in Program A, then in Program B,
if an override exists, do not do an additional override. Or maybe
change the OVRDBF command in Program B, so that the previous override
takes precedence? If the program B is not called from any other
program, I want the override to work as is.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].