ALLBASE/SQL Message Manual (36216-90213)

Chapter 2 69

ALLBASE/SQL Warning Messages

ACTION No action required if 24 is acceptable.

34400 MESSAGE Specified lock is not currently held by any

users.

(DBWARN 34400)

CAUSE The LOCK OBJECT screen was being accessed when this

message was displayed. The table, page, or row that you

speciﬁed is not locked.

ACTION No action is necessary. Check that you speciﬁed the correct

lock object.

34402 MESSAGE CID not connected to the DBEnvironment.

(DBWARN 34402)

CAUSE The CID that you speciﬁed is not a valid CID.

ACTION Check that you speciﬁed the correct CID.

34403 MESSAGE No locks qualify under the LOCKFILTER and

LOCKTABFILTER.

(DBWARN 34403)

CAUSE No locks were found that matched the selection criteria

deﬁned by the LOCKFILTER and LOCKTABFILTER

variables.

ACTION No action is necessary. Use the SET command to check the

current value of each variable. If necessary, use the SET

LOCKFILTER or SET LOCKTABFILTER command to

change a value.

34404 MESSAGE No other session is waiting on this session.

(DBWARN 34404)

CAUSE The LOCK IMPEDE screen was being accessed when this

message was displayed. The session that is being analyzed

is not holding any lock that is causing another session to

wait.

ACTION No action is necessary. Check that you have speciﬁed the

correct session.

34405 MESSAGE XID changed while collecting data! (DBWARN

34405)

CAUSE The LOCK SESSION, LOCK IMPEDE, or LOCK

TABSUMMARY screen was being accessed when this

message was displayed. To minimize performance

degradation of the DBEnvironment, SQLMON itself never

holds locks or latches in the LOCK subsystem; it

essentially performs "dirty" reads to collect data. While

data was being collected, the transaction id of the session

being analyzed changed.

ACTION No action is necessary. When interpreting the screen, keep