SOURCECONN vs ORIGSOURCECONN

This topic has 1 reply, 2 voices, and was last updated 14 years, 9 months ago by Tom Rioux.

Creator

Topic
March 15, 2010 at 2:17 pm #51629
John Boyles
Participant
Hi all,

I have a need to do a little custom parsing of the SMAT files. In the .idx files, can anyone tell me the difference between the two “SOURCECONN” entries? Same question for the two “DESTCONN” entries. They seem to typically contain the same value and it’s starting to bug me. 😕

Thanks in advance!

{SOURCECONN i_clnt_int}

{ORIGSOURCECONN i_clnt_int}

{DESTCONN {{}}}

{ORIGDESTCONN {{}}}
Creator

Topic

Viewing 0 reply threads

Author

Replies
- March 15, 2010 at 4:01 pm #71032
  Tom Rioux
  Participant
  The only difference that I know of is that ORIGSOURCECONN and ORIGDESTCONN are “read only” metadata fields and are managed exclusively by the engine. Those two fields cannot be changed or modified.
  
  The SOURCECONN and DESTCONN metadata fields can be changed. My best guess is in the following scenario where one thread sends to another thread that then sends the message to the third thread.
  
  Thread 1 —-> Thread 2
  
  Thread 3
  
  In this scenario, it would seem that Thread 1 would become the ORIGSOURCECONN and Thread 2 at some point would become the SOURCECONN for Thread 3. I could be wrong…there is a precedence for it…LOL
  
  RE: Tcl Extensions in the Reference book of Cloverleaf Help.
  
  Hope this answers your question….
  
  Tom Rioux
Author

Replies

Viewing 0 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.