That sounds a little bizarre. Do you recall any details of why this might have been so?
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alfke, Colin Sent: Thursday, April 14, 2005 10:06 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] Locks, releases and STATU() (oh my) Ooops, I thing I forgot to mention. On some versions of UniData (5.2.4?) doing a /TCL in SB+ will cause UniData to not output information with LIST.READU. I don't recall if there is also a problem with GETREADU() - plus it's already in an array so you don't have to trim and parse (truncated) data (unless you use the DETAIL modifier).. This was corrected in 6.0.2. Hth Colin Alfke Calgary, Canada >-----Original Message----- >From: Kevin King > >The 197613 is the ID of the user session. The trick is to translate >this to a user ID. SB+ appears to be doing this with the SB.DISP.LOCK >routine, though I'm not certain how they're doing that translation. > >Oh, here's a thought. From BASIC, EXECUTE a LIST.READU, capture the >output, and then trim each line of the response. >Once a line is trimmed, field out the process ID in the third position; >if it's the process ID returned by STATUS() then get the port number >from the first position. You could then use that to read the $PASSport >record which will tell you who is logged in on that port (in <7>) and a >whole bunch of other stuff. > >-Kevin >[EMAIL PROTECTED] >http://www.PrecisOnline.com ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.9.10 - Release Date: 4/14/2005 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.9.10 - Release Date: 4/14/2005 ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
