A user sent me a report in which a locking error printed. Obviously, the error should have been handled better and that I can fix. But what does this error indicate: "Error: Locking Error - code:19"? (I just need to know what code '19' indicates.)

Remember I don't use LOKSER, but instead use ALOCK/AUNLOK which equates to LOCK/UNLOCK.SBR.

I'm not clear on where that error is coming from. (I don't see any obvious messages matching that format in the ALOCK/AUNLOK routines or any of the underlying routines, or anywhere in A-Shell for that matter.) But it's possible that the message is assembled from parts, message files, system functions, etc., making it difficult to search for..

The Linux system error 19 is "ENODEV" (no such device), but that doesn't sound like it would be related to a purely synthetic locking scheme like ALOCK/AUNLOK.

If you have TRACE=BASERR set in the miame.ini (which I always recommend), then the ashlog should show the complete error message and contextual information that might be helpful to understand the cause.

I'm only concerned about the return code from LOCK.SBR. The error message was formatted by my program. And ashlog won't help because there was no program error, just a return code. So is there any way to identify what LOCK.SBR's return code '19' indicates?

Ahhh, now I get it. ALOCK.SBR is actually a wrapper for the same underlying QFLOCK-based locking scheme as XLOCK. So the return code in the case of a locking conflict is the job # holding the conflicting lock.

Thank you!