We used to have a xref file to hold a list of I-nodes and the file name. As Brain rightly states on a *nix system you can use a ls -ip | sort -k 1,1n command or ls -ip | sort +0 -1 -n
For windows we would run the Hamilton C shell so we could shell out and perform *nix command in a windows environment. The command we would run is ls -1F | sort We would then wrap the LIST.READU command so it displayed the filename, record id, login id, extn no etc -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Brian Leach Sent: 19 June 2008 15:13 To: [email protected] Subject: RE: [U2] group locks and user nbr's Doug To take the first part of your question: The lock table is used for application locks like READU and READL locks, and also for synchronisation locks. The RD and WR locks are synchronisation locks that control access to a group in a file during a read or write operation. these should be transitory only lasting milliseconds unless your system is stuffed or badly maintained. The IN locks are information locks: these are not real locks but point to the existence of a record lock somewhere in that group, to make for quicker checking. The record locks are those from Basic. As for matching up with inodes that has been discussed here various times before. If you are on UNIX you can use the ls -lsi command to list the inodes associated with files if you have a rough idea where it is. You can use find to locate the file with that inode. Under Windows inodes don't exist, they are just emulated by UniVerse, so no help there. Doing an ACCOUNT.FILE.STATS and a LIST.FILE.STATS will show you, but that does take time: something to run overnight. That user number could be a background process or a process that has died part way through a read leaving a lock behind. Brian > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of doug chanco > Sent: 19 June 2008 14:18 > To: [email protected] > Subject: [U2] group locks and user nbr's > > Hey all, > Can someone please help me understand the differences > between group locks and record locks? Also are high user > numbers (Userno below) indicative of a phantom process? > > > *Active Record Locks: > Device.... Inode.... Netnode Userno Lmode Pid Login Id > Item-ID..... > 3080194 3845801 0 137 6 RU 32694 crumjo 61570..5 > > Active Group Locks: Record Group > Group Group > Device.... Inode.... Netnode Userno Lmode G-Address. Locks > ...RD ...SH ...EX > 3080194 328935 0 53 1 RD 935D800 0 > 1 > 0 0 > > 3080194 389951 27 63180 2 RD E17000 0 > 1 > 0 0 > > * > one last question is there an easier way than finding out the > file associated with the inode and then doing a fuser on that > file to find out "what" is accessing the file? For example I > would like to know who/what is holding this group lock > > * 3080194 389951 27 63180 2 RD E17000 0 > 1 > 0 0 > > *yet all I have is an inode and a userno of 63180 DOING a > LISTU does NOT show anything with that userno > > any and all assistance appreciated! > > thanks, > dougc > > > > * > * > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ----------------------------------------- ********************************************** The contents of this e-mail are subject to contract in all cases and William Hill PLC, its subsidiaries or affiliates make no contractual commitment save where confirmed by hard copy. The contents of this e-mail do not necessarily represent the views of William Hill PLC, its subsidiaries or affiliates. We accept no liability, including liability for negligence, in respect of any statement in this e-mail. This e-mail and any files transmitted with it are confidential, may be subject to legal privilege and intended solely for the use of the individual or entity to which they are addressed. If you are not the intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited. If you have received this e-mail in error, please notify us immediately, then delete this e-mail. Please note that William Hill can accept no responsibility for viruses and it is your responsibility to scan any emails and their attachments. This message was from William Hill PLC whose registered office is Greenside House, 50 Station Road, Wood Green, London N22 7TP. Company Registration Number: 4212563 England. ********************************************* ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
