I'd like to propose solutions to two problems I've experienced with file record locks and data area locks. The first problem involves how users typically respond to file record locks.
After the record wait time has expired on a file record lock, the user must answer a message. IBM has set the default reply to "C" or Cancel. If the user has not already keyed ahead (through buffering), just pressing Enter (the typical user idea) cancels the job. Instead of changing the maximum record wait time on all files, why not change the default reply from Cancel to Retry?
CHGMSGD MSGID(RPG1218) + MSGF(QRPGMSGE) DFT('R')
On data area locks, the wait time comes from the default wait time for the job. Since data areas give you no retry option, try the following solution:
CHGJOB DFTWAIT(*NOMAX)
Preferably, this statement would be a part of the initial program specified in the user profile. Only users with *JOBCTL authority may run this command.
LATEST COMMENTS
MC Press Online