why would my cron’d hcicyclesavemsgs5 -d -c -o 15

[Anonymous]

routine cycle inbounds for “R_from_MedQuist1” but not “R_from_MedQuist”?

Topic

[Keith McLeod]

The hcicyclesavemsgs makes use of the hciconnstatus command.  There is a format statement in hciconnstatus that uses 15 characters for the unique part of the thread name.  If you count the characters in the names you are using, they appear to be the same to the program.

Modify hciconnstatus format line to something like:

   set hfmt “%-15.15s %-28.28s %-5.5s %-7.7s %-20.20s” ;# Heading format

   set fmt “%-15.15s %-28.28s %-5.5s %-7.7s %-20.20s” ;# Output line format

This gives 28 characters of uniqueness and displays pretty well also. Then try your hcicyclesavemsgs.

[Anonymous]

That should fix it. Tx, Neil

[Anonymous]

When anyone gets ambitious and rewrites the script in TCL you should use ‘msiTocEntry’ to get a list of the connections in a site with no name limits.

[Anonymous]

R_from_MedQuist1 twice?  

(Note: I have cyclesaved the R_from_MedQuist thread through the GUI)

Here’s what’s posted to my log file…

Processing

   Root: /hci/qdx5.2/integrator, site: prod, proc: results, thread: R_from_MedQuist1

       20050411.23:56:52 Cycling saved IB msg file R_from_MedQuist1

           cmd: hcicmd -v -p results -c ‘R_from_MedQuist1 save_cycle in’ >>/dev/null 2>&1

       20050411.23:56:52 Backing up idx & msg files.

       20050411.23:56:52 Deleting old backup idx & msg files:

       20050411.23:56:53 No saved OB msg file for this thread

Processing

   Root: /hci/qdx5.2/integrator, site: prod, proc: results, thread: R_from_MedQuist1

       20050411.23:57:00 No saved IB msg file for this thread

       20050411.23:57:01 No saved OB msg file for this thread

It doesn’t attempt to process R_from_MedQuist?

Here’s what a /hci/qdx5.2/integrator/bin/hciconnstatus shows for the “results” proc…  

Process         Connection                   State Proto S When                

---

---

---

---

---

results         R_to_MSCardiology            up    up      Wed Mar 30 15:16:37

results         R_from_Pyramis               up    up      Tue Feb 22 09:37:12

results         R_from_CernProd              up    up      Tue Feb 22 09:37:06

results         R_to_Results2                up    up      Tue Feb 22 12:48:54

results         R_from_MedQuist              up    up      Tue Feb 22 09:40:02

results         R_from_Psyche                up    up      Tue Feb 22 09:37:18

results         R_from_Idx                   up    up      Tue Feb 22 09:37:14

results         R_from_MedQuist1             up    up      Tue Feb 22 09:39:51

results         OR_to_Results                up    up      Tue Feb 22 09:37:17

results         R_to_Results                 up    up      Tue Feb 22 09:37:08

results         R_to_ResultsFTP              up    opening Sun Mar 06 08:19:20

[Anonymous]

the cycle routine wouldn’t handle the file names we used.

We switched R_from_MedQuist1 to R1_from_MedQuist and  all’s well now !

[Mike Grieger]

Not only do you need to modify the hciconnstatus as mentioned above to handle longer thread names, but you must also make the thread names more unique than just adding a digit to the end to differentiate them.  The hcicyclesavemsgs has a wild-card build into it when searching the thread names, so the first one it finds in the netconfig is what it will use (which is why it found the same one twice).  I believe the snipped below from hcicyclesavemsgs illustrates – look for the ($conn).$

while () {

chop;

if (/^S+s+(S+)s+ups+S+.*$/) {

($conn) = $1;

foreach (@NETCONFIG) {

$NCline = $_;

chop($NCline);

if ($NCline =~ /^protocol ($conn).*$/) {

($conn) = $1;

  printf(“nProcessingn    Root: %s, site: %s, proc: %s, thread: %sn”,$rootpath,$site,$proc,$conn);

last;

}

[Author]

Replies