|
Jay,
Try this before calling program two?
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_71/rtref/fflush.htm
Mark
On Sunday, January 24, 2021, 4:37:59 PM EST, Jay Vaughn <
jeffersonvaughn@xxxxxxxxx> wrote:
Bruce. Actually the more I think about this, this is not the same
situation.
I can do whatever I want to the file in the first pgm. It’s when pgm 2 is
called that it can’t see the changes. So I’m fairly certain your situation
was not calling subsequent pgms inside the exit pgm.
Jay
On Jan 22, 2021, at 4:00 PM, Bruce Vining <bruce.vining@xxxxxxxxx>wrote:
use
I don't have access anymore to my old code, but I know I didn't have to
a new descriptor or change any of the original programs using this exit.an
In my case the open was to basically an empty file and I then decrypted
(obviously) encrypted instance of the file from the "real" directory tothe
directory the user program used. It was for a legal firm and EVERYTHINGan
was encrypted, but the applications only saw the results of the
decryption. Something is going on here...
On Fri, Jan 22, 2021 at 2:36 PM Randy Cayton <randy_cayton@xxxxxxxxxxx>
wrote:
sounds good , have a good one
On Fri, Jan 22, 2021 at 1:33 PM Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
wrote:
We have an exit point on our IFS files.opening
When an IFS file is open, our exit pgm fires.
Now the way I understand it, is that this file is in the process of
and our exit pgm is part of that open process.one
Our exit pgm does this...
call pgm1 (modify file contents being opened)
call pgm2 (use those modified contents)
However, we are not seeing the modified contents in pgm2.
We were thinking of the obvious solutions.
1.) after pgm 1, close() and reopen in pgm2... but this is part of the
initial file opening so close() is not allowed in this exit pgm.
2.) after pgm1, obtain a new fileID (scanDescriptor), but the original
passed in via the exit pgm parm, is still the same. How would we get
thisupdated one (if one exists)?
3.) after pgm 1 is there a "commit" of some sorts we need to do, as
relatedIFS file is under commitment control.
Any input would be appreciated.
Jay
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
intendedquestions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
*Randy Cayton*
Senior Software Engineer, Transportation
Direct: +1 440 721-2640
--
This email and any files transmitted with it are confidential and
relatedsolely for the use of the addressee. If you are not the intended
addressee,
then you have received this email in error and any use, dissemination,
forwarding, printing, or copying of this email is strictly prohibited.
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
Thanks and Regards,
Bruce
931-505-1915
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
link: https://amazon.midrange.com
Help support midrange.com by shopping at amazon.com with our affiliate
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.