Precisely Speaking
May 21, 2012, 07:12:36 PM *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: So what's news with you?  Tell us about it in "Getting To Know You"!
 
   Home   Help Calendar Login Register  
Pages: [1]   Go Down
  Print  
Author Topic: Lock Message  (Read 522 times)
DonQuixote
Rock Star
*****
Posts: 108


To Dream the Impossible Dream...


« on: March 08, 2011, 03:31:07 PM »

When using a standard maintenance screen a locked record will pop-up an message for a locked record. "Record Locked by xxxxxxxxx"
How does it know which 'user' is locking the record?
Logged
Tom Pellitieri
Rock Star
*****
Posts: 171


Tom Pellitieri - Toledo, Ohio


« Reply #1 on: March 09, 2011, 08:29:41 AM »

Assuming you're using Prelude on AIX, the standard lock message reports the AIX User ID locking the record.  We have assigned a unique AIX ID to each connection (PC, terminal, etc.) so we have some hope of finding out who is holding the lock open.

You can always use /LLOCKS to see all of the current record locks.  The following columns are provided:

S - Conflict State - This is H for the current holder, and W for those waiting.  Only appears when there's a wait state.
UNO - UniData Number - This is the Port Number from /LISTU
Unbr - User Number - This is the AIX Process ID
Uid - User ID - This is assigned sequentially by AIX when a User ID is created (e.g., through SMIT)
Uname - User Name - This is the AIX User ID.  Uid and Uname always go together
TTY - Terminal Port
Filename
Inode Nbr - UniData File Index Number
DNbr - (Not certain)
Record ID - The item locked in the file

You also will see a timestamp for the lock.

Hopefully this will give you enough info to track down the person locking the record.

--Tom

Logged
precisonline
President/Chief Technologist
Administrator
Rock Star
*****
Posts: 1532



WWW
« Reply #2 on: March 18, 2011, 12:40:32 PM »

As I recall, the message that comes up in SB+ screens showing the AIX user is remarkably inconsistent.  With a little bit of programming you can read the lock table in BASIC with GETREADU() and parse through it to get the port number, then you could use that to read the $PASSxxx record in DMSECURITY and grab the user, group, pretty much anything you might need.
Logged

-Kevin
Accidents "happen"; success, however, is planned and executed.
Pages: [1]   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.7 | SMF © 2006-2008, Simple Machines LLC Valid XHTML 1.0! Valid CSS!