AS/400 – MCH5804 Lock space location operation not satisfied in specified A specified time interval of 60 seconds has elapsed
On my as/400, iSeries verson V6R1, an application program has returned an error message, I do not understand what this message means. Any help would be appreciated.
MCH5804 Severity . . . . . . . : 20 Message type . . . . . : Escape Date sent . . . . . . : 04/26/10 Time sent . . . . . . : 17:21:37 Message . . . . : Lock space location operation not satisfied in specified time interval. Cause . . . . . : A specified time interval of 60 seconds has elapsed and a Lock Space Location or Lock Teraspace Storage Location has not been satisfied. The lock holder type is 1. The lock holder name is BYBYGEKS1 BD902 519359. The lock holder thread identifier is X'0000000000000001'. The lock holder type has the following meaning: 0 - The lock holder is a Licensed Internal Code (LIC) task
Software/Hardware used:
AS/400 iSeries
MCH5804 Severity . . . . . . . : 20 Message type . . . . . : Escape Date sent . . . . . . : 04/26/10 Time sent . . . . . . : 17:21:37 Message . . . . : Lock space location operation not satisfied in specified time interval. Cause . . . . . : A specified time interval of 60 seconds has elapsed and a Lock Space Location or Lock Teraspace Storage Location has not been satisfied. The lock holder type is 1. The lock holder name is BYBYGEKS1 BD902 519359. The lock holder thread identifier is X'0000000000000001'. The lock holder type has the following meaning: 0 - The lock holder is a Licensed Internal Code (LIC) task
Software/Hardware used:
AS/400 iSeries
ASKED:
April 27, 2010 9:57 PM
UPDATED:
April 29, 2010 1:49 AM
Answer Wiki:
I don't know how much can be answered, but I'll post what I get out of the message.
A "Lock Space Location" operation was requested by job 519359/BD902/BYBYGEKS1 (known because of "The lock holder type is 1.") The lock request type was <i>Synchronous request</i> because the check was MCH5804. (58 is x'3A' and 04 is x'04'.) A <i>space location lock wait time-out</i> will be signaled for a synchronous request if time runs out.
See the <a href="http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/rzatk/LOCKSL.htm">Lock Space Location (LOCKSL)</a> MI instruction topic. Review it for discussion of what the instruction does, and scan for '3A04' to find specific mentions of the exception.
But as for what that job was doing...? You'll have to tell us. Whatever it was trying to do, it ran out of time. In general, it was trying to lock a storage location, but conflicting locks were held longer than this job intended to wait. Whatever is/was stored at that address (storage location) was locked elsewhere for too long, or something very close to that.
Tom
To see all answers submitted to the Answer Wiki: View Answer History.
Is a fix of V6R1 see this IBM link with PTS that corretion:
http://www-01.ibm.com/support/docview.wss?uid=nas30d01d46b6527bfb8862576f10068a5d5
ATT:
Lujan