![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Traces accesses only of the named request type (for example, N=FORALLS), independent of TABLE field. The maximum number of rows that the system creates in the @MESSAGETRACE and @MESSAGEDUMP SES tables. When the number of rows in the table reaches the number given in COUNT, the table is cleared and restarted. Use this field with caution: Y means create HEX dump of messages in table @MESSAGEDUMP. Ignored if MESSAGELOG=Y. When dumping, indicates the maximum number of bytes to show from the outbound message. When dumping, indicates the maximum number of bytes to show from the inbound message. Y means create a HEX dump of all messages in the message log. Y means show all messages on the message log, including those normally erased by TIBCO Object Service Broker. Use a rule or the Table Editor to set the value of @TRACEMESSAGES.TRACE to Y and then run the applications to be traced. Message tracing can be further refined by modifying other fields of the @TRACEMESSAGES table.Unless you specifically route messages to the message log or to the @MESSAGEDUMP session table, all messages are logged in the @MESSAGETRACE session table. By analyzing the occurrences in the @MESSAGETRACE table, you can determine the access paths requested by the Execution Environment for each table access. This information can be used to optimize your application by using different variations of application table access statements.
• Use DUMP=Y with caution, and only on the advice of your TIBCO Support representative.
• Setting MESSAGELOG to Y can be used to suppress inserts to the @MESSAGETRACE and @MESSAGEDUMP tables. This would show that these accesses are not interfering with other processing. Use this option only on the advice of an TIBCO Support representative.
• Using KEEPMESSAGELOG=Y causes the message log to increase in size dramatically. Use this option only on the advice of your TIBCO Support representative.The TRACEON sample rule illustrates how a typical TAM table call and message flow trace is activated. To capture TAM table calls and Execution Environment or Data Object Broker messages for a given session, execute the TRACEON rule. If you are interested in the calls for a particular table, modify the rule and specify a table name for the statement @TRACEMESSAGES.TABLE='tablename' (where tablename is the name of the table you are interested in). For results to this example, refer to @MESSAGETRACE.
To deactivate the trace and examine the results, run the TRACEOFF rule as shown below. Deactivate the TAM trace and then examine the contents of the @MESSAGETRACE and @MESSAGEDUMP tables using the Table Browser. If you want to print the contents of the @MESSAGEDUMP, edit out unprintable characters in the character portion of the trace prior to printing (use the Table Editor).
The TRACEON sample rule causes the collection of a generalized trace. Refer also to the information for @MESSAGEDUMP and @MESSAGETRACE.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |