Re: is there a way to let the record lock (R I D C) error stay at theprogram that do the CHAIN

This is pet peeve of mine. 
 
Fix PGMB. 
 
There should be no reason at all for any program including PGMB to have a
record locked long enough for the error routine to kick in.
 
If you do not know how to prevent a record lock then read the archives. Its
been discussed regularly and fully. 
 
If you still need an example, look at the last program on http://www
martinvt.com/Code_Samples/FAQ/faq.html 
It shows how to keep a record unlocked, and how to check to be sure the
record wasn't changed between your read and your need to update.
---------------------------------------------------------
Booth Martin http://www.MartinVT.com
Booth@xxxxxxxxxxxx
---------------------------------------------------------
 
-------Original Message-------
 
From: RPG programming on the AS400 / iSeries
Date: 12/23/2003 3:14:01 PM
To: RPG programming on the AS400 / iSeries
Subject: is there a way to let the record lock (R I D C) error stay at
theprogram that do the CHAIN
 
Here is the program flow:
1) PGMA call PGMB.
2) PGMA has *PSSR routine.
3) Both program run in the same name activation group.
 
problem I have:
1) PGMB CHAIN to a file and sometime gets record lock error RNX1218. When I
test run the program, the record lock error is caught by PGMA *pssr routine
and I did not get an option for retry the CHAIN operation.
 
 
Is there a way to do this:
1) Is there a way to get the retry option without removing the *pssr in
PGMA?
 
thanks