AS/400 – MCH5804 Lock space location operation not satisfied in specified A specified time interval of 60 seconds has elapsed

5 pts.
Tags:
AS/400
iSeries V6R1
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

Answer Wiki

Thanks. We'll let you know when a new response is added.

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

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following