|
On Jan 18, 2021, at 1:45 PM, Reeve <rfritchman@xxxxxxxxx> wrote:
:) Didn't say you didn't, merely offering a suggestion. The behavior you're
experiencing looks like a rollback has taken place.
COMMIT is a job/activation group function used to signal a transaction made
up of multiple CRUD operations is complete. It's not issued against a
file: the idea of COMMIT is to maintain the integrity of the transaction
across multiple resources. Extra credit if you know the meaning of
"ACID"!
Use COMMIT/COMMIT WITH HOLD (if SQL) in your program and the changes to the
resources opened under commitment control will be made permanent.
Just saying.
On Mon, Jan 18, 2021 at 4:56 AM Jay Vaughn <jeffersonvaughn@xxxxxxxxx>--
wrote:
I know how to do commitment control in rpg for PF’s (both native and
sql)...
But what is the rpg syntax to issue a commit on a stmf?
Jay
Sent from my iPhone
exitOn Jan 17, 2021, at 11:51 PM, x y <xy6581@xxxxxxxxx> wrote:
if the file is journaled, you'll need to do a COMMIT.
On Sun, Jan 17, 2021 at 4:43 PM Jay Vaughn <jeffersonvaughn@xxxxxxxxx>
wrote:
So I have a stmf file opened in my exit pgm registered to
QIBM_QP0L_SCAN_OPEN.
I want to clear that file... and then later write to it further in the
writtenpgm.
I do a ftruncate64() in my exit pgm and if I do a wrklnk and look at the
bytes, it did clear it and set the bytes to 0.
Good...
But when I later write to the file later on in the exit pgm, the data I
thought I cleared returns and my new data appends to it.
Is this because the file was never closed before the new data was
relatedto it?
How can I ensure it is cleared and then allowed to write to in this same
exit pgm without the ability to close it before the write?
Is there some functionality with the below exit pgmoutput ds fields that
can be set to allow my clear to "stick"?
8 8 CHAR(1) Update object scan information
9 9 CHAR(1) Scan status
tia
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
related questions.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
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.