[Paul Sullivan]

Sorry to keep at this but, I looked through random SMAT files and saw the message ID window. I did a grep on those ID’s and had a hit. Below though is a snipit from the process .err log. Neither of these ID’s respond to grep.

[msg :RecP:WARN/0:    rad_xlate:04/08/2014 07:26:13] [0.0.53146388] The # 6

ent encountered ‘DG1’ is out of order for message type ‘ORU_R01’.  Segment

ed.

[xpm :xlt :WARN/0:    rad_xlate:04/08/2014 07:26:13] Warning during PathCop

e # 6 segment encountered ‘DG1’ is out of order for message type ‘ORU_R01’.

ment ignored.

[msg :RecP:WARN/0:    rad_xlate:04/08/2014 07:40:07] [0.0.53148712] The # 7

ent encountered ‘DG1’ is out of order for message type ‘ORU_R01’.  Segment

ed.

[/b]

[Paul Sullivan]

Looking more into this. I have a notion that our SMAT files are not saving any message ID’s. Tried using the message ID range search in SMAT on some messages from today and got nothing. Is there somewhere SMAT determines what is saved.

[Paul Sullivan]

Did a grep on *.idx. Came up with nothing. This is from today, so I should not need to worry about an archived message.

[Paul Sullivan]

Can I search on the 0.0.xxxxxx message ID in SMAT? There are many routes in this one process, makes it rough to pin it down.

[Paul Sullivan]

That did the trick. Jim K helped me with the specific routing yesterday.

[Paul Sullivan]

Appreciate the replies and I will practice with this bit of tcl, but I did not really think my issue through well enough. Turns out there may be 1000+ combinations to choose from. Not something I wish to maintain a table for. I went the hard code route and is running OK.

[Paul Sullivan]

Can one or more of these sessions be set up as a go-to-meeting? Long drive for a short meeting.

[Paul Sullivan]

Thanks Jim, that did the trick.

[Author]

Replies