Message RMSF0007 LOCK REQUEST FAIL appears repeatedly in log
If the RMSF0007 message logs repeatedly for an extended period of time, it may indicate that a procedure has locked the record and is now hung and is not releasing the record, thereby preventing other procedures from accessing the record.
Usually the error occurs when the lock is EXCL(usive) and is not freed.
The most common case of error is during the update of RAMDB from the RAMSTAGE, requested by a remote region.
Messages similar to this appear in the log repeatedly.
RMSF0007 LOCK REQUEST FAILED - TYPE(EXCL) RC(8) FDBK(0) TEXT(123456.NM02BSYS.05.09.26) LOCK($RMSTAGE.A000NM02A000NM03.$EEPAPORT______)
START RMSF0007 05.55.16.52 A000NM01 NM01BSYS RMSF0007 LOCK REQUEST FAILED - TYPE(EXCL) RC(8) FDBK(0) TEXT(123456.NM02BSYS.05.09.26) LOCK($RMSTAGE.A000NM02A000NM03.$EEPAPORT_______)
N23E49 PROC RMSF0007 LINE 00480001 TOO MANY PARAMETERS AFTER &DO
N23601 RMSF0007 PROCESSING TERMINATED DUE TO ERROR. NCLID 123477
To identify the NCL which has the lock, issue the following commands, using the reference in TEXT() string:
o SHOW LOCKS TEXT=text_from_RMSF0007
o SHOW NCLLOCKS TEXT=text_from_RMSF0007
o SHOW NCL ID=nclid_from_show_ncllocks
A recycle of the offending region will resolve the lock.