Getting thread status and statistics via command line

[Ian Morris]

Is there a command that will give you whether or not a thread is “opening”, “up”, or “down”?

Also, is there a command that will give you thread statistics just like when you right click a thread and view its status?  Specifically, I’m interested in seeing the “Last Read” and “Last Write”.

Topic

[Todd Lundstedt]

hciconnstatus will get you the up, opening stuff.

Tom Boyd wrote a TCL script to get status, queued, last r/w times, etc… and even a monitor mode where you could monitor one specific thread.  I honestly don’t recall how I came to possess it, because I can’t find where he posted it on Clovertech (in a quick search).  He called it “tomst”.  You might ask him if he can send it to you.

I need to do some work on it, because it bombs off if a thread name begins with a number.

[Rob Abbott]

“hcmsiutil -dd ” will give you the statistics you are looking for.

Rob Abbott
Cloverleaf Emeritus

[Ian Morris]

Rob Abbott wrote:

“hcmsiutil -dd ” will give you the statistics you are looking for.

I found that the command is “hcimsiutil -dd “.  Thank you for pointing me in the right direction though.

[Jim Kosloskey]

Todd,

If msistats is being used then there are two options as I receall for getting thread stats. One is using the thread name and the other is using an index from the TOC.

If using the thread name and the thread name happens to start with a number then (as you have discovered) msistats attempts to use the thread name as an index and fails because the thread name is not likely a valid index.

Thus for the msistats dump proc I have I only use the index.

If you need an example let me know and I will send you my msistats dump proc.

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Ian Morris]

Why is it that you don’t get the number of queued messages with the hciconnstatus command?  I should see 178 pending messages somewhere in this info.

bash-3.1$ hcimsiutil -dd Inthlth_ADT_TCPIP_send

Thread Data Section for: Inthlth_ADT_TCPIP_send

Scn Addr     : 0x0x50006038

Scn Version  : 1

Scn Updated  : Fri Jan 22 11:34:05 2010

Sample Taken  : Wed Jul 21 13:44:11 2010

Sample Added  : Wed Jul 21 13:36:23 2010

Start Time    : Mon Jun 28 08:09:41 2010

Stop Time     : never

Proto Status  : 2

Proto Flags   : 0

Proto Last Rd : never

Proto Last Wt : Mon Jun 28 09:18:05 2010

Proto Err Time: never

Proto Err Msg :

Xlate Count   : 0

Forward Count : 0

Error Count   : 4117

IB Latency    : 0.000

OB Latency    : 401381.696

Total Latency : 1017340.728

Msgs In       : 4118

Msgs Out      : 4220

Bytes In      : 477248

Bytes Out     : 3591395

IB Pre-SMS QD : 0

IB Post-SMS QD: 0

OB Pre-SMS QD : 0

OB Data QD    : 178

OB Reply QD   : 0

Pre-Xlate QD  : 0

Inter-thread Statistics

Sent    Recvd   pxqd X time  T on Q  Latency Thread name

---

---

—-

---

---

---

---

     0       0    0   0.000   0.000   0.000 omni_dft_recv1                  

     0       0    0   0.000   0.000   0.000 GEQSPeri_ADT_send              

     0       0    0   0.000   0.000   0.000 HlthScribe_ADT_send            

     0       0    0   0.000   0.000   0.000 HPM_ORU_FILE                    

     0       0    0   0.000   0.000   0.000 Medinet_ORD_recv                

     0    4397    0   0.000 51282.789 660915.543 Meditech_ADT_recv              

     0       0    0   0.000   0.000   0.000 meditech_dft_send1              

     0       0    0   0.000   0.000   0.000 lawson_dft_send1                

     0       0    0   0.000   0.000   0.000 slab_adt_send                  

     0       0    0   0.000   0.000   0.000 LAB_ORU_FILE                    

     0       1    0   0.000 1040.903 356425.186 Inthlth_ADT_TCPIP_send          

     0       0    0   0.000   0.000   0.000 Omni_ADT_send                  

     0       0    0   0.000   0.000   0.000 Med_Lab_Res_recv                

     0       0    0   0.000   0.000   0.000 Dietary_ADT_send                

     0       0    0   0.000   0.000   0.000 Omni_RDS_send                  

     0       0    0   0.000   0.000   0.000 Med_Lab_Text_recv              

     0       0    0   0.000   0.000   0.000 Inthlth_ORU_TCPIP_send          

     0       0    0   0.000   0.000   0.000 Inthlth_ORU_send                

     0       0    0   0.000   0.000   0.000 summit2_adt_send                

     0       0    0   0.000   0.000   0.000 Omni_RDS_Prof_send              

     0       0    0   0.000   0.000   0.000 Med_RAD_Res_recv                

     0       0    0   0.000   0.000   0.000 Meditech_RDE_MFN_recv          

     0       0    0   0.000   0.000   0.000 CPAL_ORU_recv                  

     0       0    0   0.000   0.000   0.000 Omni_MFN_send                  

     0       0    0   0.000   0.000   0.000 Meditech_RES_send              

     0       0    0   0.000   0.000   0.000 UDS_ADT_send                    

     0       0    0   0.000   0.000   0.000 CPAL_ORM_send                  

     0       0    0   0.000   0.000   0.000 Live_ADT_recv                  

Todd Lundstedt wrote:

hciconnstatus will get you the up, opening stuff.

Tom Boyd wrote a TCL script to get status, queued, last r/w times, etc… and even a monitor mode where you could monitor one specific thread.  I honestly don’t recall how I came to possess it, because I can’t find where he posted it on Clovertech (in a quick search).  He called it “tomst”.  You might ask him if he can send it to you.

I need to do some work on it, because it bombs off if a thread name begins with a number.

[Ian Morris]

Nevermind,

Answered my own question.  I’m guessing it’s the OB Data QD line.

[Author]

Replies