Trace bits
Trace bits and least significant Byte
The LogMask and the CollectedLogMask settings are controlled with trace bits. The following graphic illustrates this:
The trace level of the log mask is set by the least significant byte (LSB) of the TraceMask-setting. Change this single digit to set a new trace level.
| Least Significant Byte (LSB) | Meaning |
|---|---|
| xxxxxxx0 | Logging is turned off |
| xxxxxxx1 | Only fatal errors are logged |
| xxxxxxx2 | Only fatal errors and errors are logged |
| xxxxxxx3 | Only fatal errors, errors and warnings are logged |
| xxxxxxx4 | Only fatal errors, errors, warnings and informational messages are logged |
| xxxxxxx5 - xxxxxxxF | Fatal errors, errors, warnings, informational and debug messages are logged |
The other digits of the Tracemask-parameters define which trace message types are logged when the trace level in the last digit is set to debug. The following list shows all defined trace bits of the trace mask. They are only relevant when the trace level of the log mask is set to log debug messages. Conversely, setting the trace level to log debug messages requires that also one or several of the trace bits are set. Multiple messages can be combined via bitwise OR.
| Definition for CRMConnectorSAP | Trace Bit | Definition for CRMConnectorOutboundSAP | Trace Bit |
|---|---|---|---|
| COMMUNICATION | 0x00000010 | RfcServer | 0x00002000 |
| TPI | 0x00000020 | CREATE | 0x01000000 |
| ICM | 0x00000040 | DELETE | 0x02000000 |
| AGENT | 0x00000080 | BEGIN_METHOD | 0x04000000 |
| CALL | 0x00000100 | END_METHOD | 0x08000000 |
| ROUTE | 0x00000010 | ||
| TRANSACTION | 0x00002000 | ||
| SCHEDULER | 0x00004000 | ||
| CONFIG | 0x00008000 | ||
| MESSAGE_NAME | 0x00010000 | ||
| MESSAGE_DETAIL | 0x00020000 | ||
| HEARTBEAT | 0x00040000 | ||
| PERFORMANCE_DATA | 0x00080000 | ||
| MANAGER | 0x00080000 | ||
| CREATE | 0x00080000 | ||
| DELETE | 0x00080000 | ||
| BEGIN_METHOD | 0x00080000 | ||
| END_METHOD | 0x00080000 | ||
| COLLECTED | 0x80000000 |
| Definition for Data Store | Trace Bit | Definition for Chat Connector | Trace Bit |
|---|---|---|---|
| COMMUNICATION | 0x00000010 | COMMUNICATION | 0x00000010 |
| SERVICE | 0x00000800 | SERVICE | 0x00000020 |
| TRANSACTION | 0x00002000 | CHATCONNECTOR | 0x00000040 |
| SCHEDULER | 0x00004000 | MMGATEMCO | 0x00000080 |
| CONFIG | 0x00008000 | MULTISESSIONUSERMAPPING | 0x00000100 |
| MESSAGE_NAME | 0x00010000 | AGENTTASK | 0x00000200 |
| MESSAGE_DETAIL | 0x00020000 | MCILGATE | 0x00000400 |
| HEARTBEAT | 0x00040000 | MCILGATEMCO | 0x00000800 |
| PERFORMANCE_DATA | 0x00080000 | CHATGATEMCO | 0x00001000 |
| CREATE | 0x01000000 | JABBERGATEMCO | 0x00002000 |
| DELETE | 0x02000000 | JABBERGATE | 0x00004000 |
| BEGIN_METHOD | 0x04000000 | COLLECTED | 0x80000000 |
| END_METHOD | 0x08000000 | ||
| COLLECTED | 0x80000000 |
Multiple message type settings can be combined via bitwise OR. Note that the COLLECTED bit (0x80000000) must be set to activate the collected trace messages. If this bit is not set, the TraceMaskCollectMsg-settings have no effect and no collected trace messages are logged.