Re: How to get called program to write records to physical file member.

So I could just do *JOB and be ok, but would *CALLLVL cover it as well? I
rather not over scope more than neccessary... The orininating program is
in a named activation group, but it is calling a another program that is
in the default activation group.


Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777



Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
04/28/2010 02:14 PM
Please respond to
RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>


To
RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
cc

Subject
Re: How to get called program to write records to physical file member.






what is the OVRSCOPE() on your OVRDBF?


Thanks,
Tommy Holden



From: Bryce Martin <BMartin@xxxxxxxxxxxx>
To: RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
Date: 04/28/2010 01:11 PM
Subject: How to get called program to write records to physical
file member.
Sent by: rpg400-l-bounces@xxxxxxxxxxxx



So here's the situation, and my lack of understanding of how things work
at the call stack level I think is the problem.

I have a program, in that program I use QCMDEXC to create a new member on
a physical file. Then I do an OVRDBF to that member. I then call another


program - yes program, not a module or service program, to write some
records to that file. Then I call a procedure from a module that is bound


to my program to do some stuff and read from that member I just created
and populated. The problem is that the called program isn't writing to
the member I created, its writing to the *FIRST member of the file. My
bound procedure is looking in the member I did the OVRDBF to but its
blank.

Can someone explain why the called program doesn't retain the OVRDBF to
the proper member and what I can do to fix this? Is the only way to do it


by passing the member name to the called program so it can do its own
OVRDBF?

Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777
--- This message (including any attachments) is intended only for the use
of the individual or entity to which it is addressed and may contain
information that is non-public, proprietary, privileged, confidential, and

exempt from disclosure under applicable law. If you are not the intended
recipient, you are hereby notified that any use, dissemination,
distribution, or copying of this communication is strictly prohibited. If
you have received this communication in error, please notify us and
destroy this message immediately. ---