Comments on: Avoid reading uncommited records in RPG/400 http://itknowledgeexchange.techtarget.com/itanswers/avoid-reading-uncommited-records-in-rpg400/ Wed, 19 Jun 2013 04:33:39 +0000 hourly 1 By: tomliotta http://itknowledgeexchange.techtarget.com/itanswers/avoid-reading-uncommited-records-in-rpg400/#comment-84929 tomliotta Tue, 07 Dec 2010 04:47:09 +0000 #comment-84929 And in RPG/400!

Tom

]]> By: tomliotta http://itknowledgeexchange.techtarget.com/itanswers/avoid-reading-uncommited-records-in-rpg400/#comment-84928 tomliotta Tue, 07 Dec 2010 04:45:50 +0000 #comment-84928 Although updates may be locked, reads shouldn’t be — unless commitment control says otherwise.

I don’t understand why commitment control is being used, but the question restricts any answer from giving a commitment control reply. One job (or program) is updating a file in commit mode but other jobs (or programs) are expected to find a way around it without using the facility provided for it. That doesn’t make sense to me.

Why not STRCMTCTL? It seems easy enough.

Tom

]]> By: philpl1jb http://itknowledgeexchange.techtarget.com/itanswers/avoid-reading-uncommited-records-in-rpg400/#comment-84925 philpl1jb Tue, 07 Dec 2010 01:34:54 +0000 #comment-84925 RPG/400 .. not RPGLE (RPG IV)!!! seems to be alot of that this week.

I take it that one job has updated or written the record and it’s yet to be committed.
In that case the record is locked. Any other job that attempts to access the record for update will be refused access.

Phil

]]>