×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
We recently had a record lock in one of or new program (which uses
subprocedures and no exception error handling) and the program ended.
(Normally as I was to learn after reading related parts from the Redbooks
Who Knew You Could Do That with RPG IV and RPG Exception and Error Handling
as well as checking this list's archives.
From my understanding of what I have read once an exception is handled there
is no way to retry the failing statement. In OPM programs, when a record
lock was encounter a retry option was available to the operator. Much of
what I read in the archives suggested fixing the program which was causing
the lock in the first place but I could not find any information on how
others were handling the record lock scenario in the program attempting the
lock.
If a batch job attempts to read a record for update and that record is
locked is there any way to retry the read so that the program doesn't
continue on with the next record.
I have seen examples of messages issued stating that the record is locked
and what job is locking the record. So the user who locked the record
completes his job releasing the lock. How or can the batch job now attempt
to reread the record? From what I have read I don't believe so but I would
like some confirmation or advise.
Thanks in advance,
Rob R
midrange.com
