Suppress warnings re exclusive locking

Question

We're using ASE 15.7 on Windows but this may apply to other platforms. Certain stored procs where we're locking a table in exclusive mode inside a trans generate warnings: (number 12103, Severity 10)
Table 'x' in database 'y' was not locked in 'exclusive' mode because a covering lock in 'exclusive' mode was found.
I guess I have 2 questions - are we doing something wrong that's causing this and is there a way to suppress these?  According to the docs it's informational.

Answer 1

Hi David,
You aren't doing anything particularly wrong.
If you were writing your own reporting client using the Open Client SDK, or perhaps using some existing client that had some features for defining error handlers, you avoid seeing the message by using an error handler that did not output it.  If you are using a general purpose client like isql, there currently isn't a way to directly surpress output of the message.  There is an open feature request for that, CR 234335.  However, it has been open since 2001, and I don't expect to see any action on it soon.  (You could open an incident to express your interest in it and increase its priority if you wish).  However, there is also a way to just avoid the message in the first place.
The message is output when you use LOCK TABLE to request a lock that you already have.
You can avoid it by checking master..syslocks to see if you already have such a lock and only calling LOCK TABLE if you don't have it.
if not exists (
                    select id from master..syslocks
                    where id = object_id("t1")
                    and type = 1
                    and spid = @@spid
begin
      lock table t1 in exclusive mode
end
------  demonstration:
create table t1 (c1 int)
go
begin tran
lock table t1 in exclusive mode - - create an existing exlusive table lock
go
lock table t1 in exclusive mode  -- try to get another exclusive table lock
go                                               -- this outputs the message
if not exists (select id from master..syslocks
  where id = object_id("t1")
  and type = 1
  and spid = @@spid)
begin
lock table t1 in exclusive mode
end
go                                                  -- this does not output the message
rollback tran
go
id          dbid   page       type   spid   class
         fid    context row    loid        partitionid nodeid
(0 rows affected)
id          dbid   page       type   spid   class
         fid    context row    loid        partitionid nodeid
   576002052      6          0      1     14 Non Cursor Lock
              0       0      0          28           0   NULL
(1 row affected)