| Author |
Message
|
| moepi |
 Posted: Tue Jun 10, 2003 5:47 am Post subject: Trace Nodes On Unix |
 |
|
Novice
Joined: 11 Jul 2001
Posts: 21
Location: South Africa
|
I have added trace nodes on the message flows. The problem is that one cannot predict when the message flows will actually write into the trace files.
Environment: SunOS 5.8 Generic_108528-18 sun4u sparc SUNW,Ultra-Enterprise
WMQI 2.1 with CSD04
Please assist.
|
|
| Back to top |
|
 |
| fschofer |
| Posted: Tue Jun 10, 2003 6:19 am Post subject: |
|
|
Knight
Joined: 02 Jul 2001
Posts: 524
Location: Mainz, Germany
|
Hi,
take a look at the command 'mqsichangetrace'
in the Administration Guide to configure your
trace settings.
After a deploy to your broker or a broker restart
you may have to configure the trace settings again.
Greetings
Frank |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jun 10, 2003 9:22 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I don't think mqsichangetrace necessarily helps moepi.
But I'm not clear what moepi is asking about, either?
Why did you add trace nodes to your message flow, and why do you want to know when data will be written to them? What are you trying to accomplish? |
|
| Back to top |
|
|
| moepi |
| Posted: Tue Jun 10, 2003 11:04 pm Post subject: |
|
|
Novice
Joined: 11 Jul 2001
Posts: 21
Location: South Africa
|
Hi Jeff,
I'm still in development phase. I'm using traces to keep track of the path the message took. I also want to know if the outcome from a particular node is as expected.
Thanks,
Moepi |
|
| Back to top |
|
|
| lung |
| Posted: Wed Jun 11, 2003 1:05 am Post subject: |
|
|
Master
Joined: 27 Aug 2002
Posts: 291
Location: Malaysia
|
If your trace node is in the way of the message path, then it will write the trace.
What is your problem here, exactly? Is your broker not writing the trace files correctly? Or what?  |
|
| Back to top |
|
|
| moepi |
| Posted: Wed Jun 11, 2003 1:59 am Post subject: |
|
|
Novice
Joined: 11 Jul 2001
Posts: 21
Location: South Africa
|
Hi Lung,
I don't know if its the Broker not writting the traces or what. My problem is that I cannot predict when the message flow is going to write into the traces.
It will write for the first request and then write again after say ten requests. Other requests will be going thru the same path,but no traces will be updated.
Ta,
Moepi |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jun 11, 2003 5:52 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Okay, then in this case mqsichangetrace may help. It will allow you to trace your trace nodes...  It's documented in the Administration Guide.
But how are your trace nodes configured? Are you writing to usertrace, or a file, or the system log? What do you have as your pattern?
Also, how are you determining that the trace isn't being updated? |
|
| Back to top |
|
|
| moepi |
| Posted: Wed Jun 11, 2003 7:04 am Post subject: |
|
|
Novice
Joined: 11 Jul 2001
Posts: 21
Location: South Africa
|
Hi,
Q: But how are your trace nodes configured?
A: I'm not sure on this one. I just drag the node and use it.
Q: Are you writing to usertrace, or a file, or the system log?
A: File
Q:Also, how are you determining that the trace isn't being updated?
A: I check the last entries in the log file.
Q:What do you have as your pattern?
A: ${Root}; ${ExceptionList} or ${Environment.Variables.Something}
Please note that the same message flows can write to trace files on Windows NT.
Below is any example of the first trace:
File Path : CallQuotes.RequestAuditlog.log
>>>>> Start
UserId : ${Root.MQMD.UserIdentifier}
Product Code : ${Environment.Variables.Product_Code}
Contract No. : ${Environment.Variables.Contract_No}
System Id. : ${Environment.Variables.System_Id}
Current Date/Time : ${CURRENT_DATE}/${CURRENT_TIME}
>>>>> End
Second trace:
File Path : /opt/mqadmin/mqsilogs/callquotes/requests/CallQuotes.DB_Store.pass.log
>>>>> Start
${Root}
>>
${ExceptionList}
>>>>> End
Note that I'm writing to different folders on the system.
Ta,
Moepi |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jun 11, 2003 10:09 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Okay. Everything you've got is reasonable, and should work as expected based on what I can see.
That said, I wonder if there is anything other than the broker that would be putting a write lock on the trace file?
Again, though, it does sound like you need to use the mqsichangetrace command to enable debug level tracing on your message flow to find out what the trace node thinks is going on. The mqsichangetrace command is documented in the Administration Guide. |
|
| Back to top |
|
|
|
|
