Jadima Apr 2, 2006   9:50 AM GMT

You can change the file that is accessed to a lower wait time limit. This can be done using the CHGPFM command waitrcd keyword to a value -let's say 5 seconds instead of 60 seconds.

0 pointsBadges:

Acjitk Apr 2, 2006   10:22 AM GMT

If you need to keep the 60-second wait time for record locking in place and you also need to read the file for update in your current application, you can implement "soft lock" processing as follows: 1) Add the field "Locked By User Id" to the file 2) Every time the program reads the file for update, add the user id to this field 3) Every time the user has finished updating, remove the user-id from this field 4) Add a statement before the read for update step (which is holding up the users for 60 seconds) that reads without update so that the wait time for record lock is not in effect. 5) Check for a soft lock - check if the "Locked by User Id" field is not blanks. If not blanks, display the User Id in a meesage on the screen letting the current user know who is locking it. This will display instantly rather than the file wait time. 6) The only problem with this approach is that the soft lock remains on the record if a job is cancelled before the soft lock is removed. You will need to provide the users an override when the soft lock exists which means that they can try to update anyway (usually after they check with the user in the message to see if they are really locking the record). You can do this by making the message display in a window which gives them the option to read for update regardless of the warning that the record is locked. If they decide to override the soft lock warning, the worst that will happen is that they will have to wait 60 seconds if the record is truly locked just like they did before.

0 pointsBadges:

Centex Apr 3, 2006   9:42 AM GMT

If you cannot change the physical file wait time, you can also override the record wait time with an OVRDBF before opening the file with your program. We normally change it to *NONE in this situation so you get an immediate signal back to the program.

0 pointsBadges:

Pbrown0108 Apr 3, 2006   6:35 PM GMT

Thank you all for your responses. I was finally able to use the OVRDBF command to change the amount of time that would be used trying to read a locked record. Again thanks to all of you.

0 pointsBadges:

TomLiotta Dec 2, 2009   9:04 AM GMT

A nice aspect of the override is that it applies only in that job. It doesn't change the file, and that means it doesn't mess with timings in other jobs. An override can tune the behavior for each individual job. Tom

125,585 pointsBadges: