QtrcWriteStack()--Write Call Stack Trace Data
Syntax
#include <qtrc.h> int QtrcWriteStack (unsigned int Coded_Level, const char *Component, const char *Subcomponent, const char *Function, const char *Label);Service Program Name: QTRCMGR
Default Public Authority: *USE
Threadsafe: Yes
The QtrcWriteStack() function writes a component trace record as call stack data to an active trace collection if certain trace conditions are met.
Each call to the QtrcWriteStack() function is considered a trace point. A component trace record is written to the trace collection when all the trace conditions are met for a given trace point. The trace conditions include:
- A trace collection must be active for the current thread.
- The specified Component must be part of the trace collection.
- The active trace level that was used for the specified Component when the trace collection was started must allow the Coded_Level of the trace point.
Each trace point must indicate the desired trace level using the Coded_Level parameter. This trace level is compared against the active trace level that was used for the specified Component when the trace collection was started. Components are defined to the trace collection using the Start Trace (STRTRC) CL command. The Coded_Level must be one of the following values:
QTRC_LEVEL_ERROR (1) | ERROR-level trace point. A component trace record is written if the Component has an active trace level of either *ERROR, *INFO, or *VERBOSE. |
QTRC_LEVEL_INFO (2) | INFO-level trace point. A component trace record is written if the Component has an active trace level of either *INFO or *VERBOSE. |
QTRC_LEVEL_VERBOSE (3) | VERBOSE-level trace point. A component trace record is written if the Component has an active trace level of *VERBOSE. |
Parameters
- Coded_Level
- (Input)
The trace level of the trace point.
- Component
- (Input)
A pointer to the null-terminated component name. The component name should be 10 characters in length or less. If more than 10 characters are specified, only the first 10 characters are used.
- Subcomponent
- (Input)
A pointer to the null-terminated subcomponent name. The subcomponent name should be 10 characters in length or less. If more than 10 characters are specified, only the first 10 characters are used. This parameter can be set to NULL if no subcomponent is to be defined.
- Function
- (Input)
A pointer to the null-terminated function name. The function name should be 512 characters in length or less. If more than 512 characters are specified, only the first 512 characters are used. This parameter can be set to NULL if no function is to be defined.
- Label
- (Input)
A pointer to the null-terminated label that will precede the call stack data. The label should be 128 characters in length or less. If more than 128 characters are specified, only the first 128 characters are used. This parameter can be set to NULL if no label is to be defined.
Authorities and Locks
None.
Return Value
- 0
- QtrcWriteStack() was successful. However, the component trace record will only be written if the trace conditions are met.
- value
- QtrcWriteStack() was not successful. An error condition was detected which would prevent the component trace record from ever being written.
Error Conditions
If QtrcWriteStack() was not successful, the error condition returned usually indicates one of the following errors. Under some conditions, the value returned could indicate an error other than those listed here.
Error condition | Additional information |
---|---|
[EINVAL] |
The specified Coded_Level is not one of the supported trace levels. The specified Component is not a valid component name. |
[EFAULT] | |
[EUNKNOWN] |
Error Messages
None.
Usage Notes
- If the QtrcWriteStack() function is called multiple times, there may be a noticeable performance impact. The QtrcGetActiveLevel() API can be used, and the results saved into a variable for later, multiple uses. The variable can be used to quickly check if the specified Component is currently active at the appropriate trace level, prior to calling the QtrcWriteStack() function. The variable should be periodically updated, to ensure a current view of the component's active trace level. Refer to the QTRC Trace APIs for additional information concerning the use of trace levels.
- Refer to the QTRC Trace APIs for additional information concerning the Coded_Level, Component, Subcomponent, Function, and Label parameters.
Related Information
- QtrcGetActiveLevel()--Get Active Trace Level
- QtrcWriteHexDump()--Write Hexadecimal Dump Trace Data
- QtrcWriteHexDumpF()--Write Hexadecimal Dump Trace Formatted Data
- QtrcWriteText()--Write Text Trace Data
- QtrcWriteTextPrintF()--Write Text Trace Data using Print Formatted
- QtrcWriteTextPPrintF()--Write Text Trace Data using Pointer-based Print Formatted
- QtrcWriteTextVPrintF()--Write Text Trace Data using Variable Argument List Print Formatted
- Start Trace (STRTRC) CL command
- For additional information about the QTRC Trace environment, see QTRC Trace APIs.
Example
The following example uses an INFO-level trace point to write call stack trace data for a component named MYCOMP. The component trace record will be written to the active trace collection if the STRTRC CL command was used before calling the example, specifying either TRCTYPE((MYCOMP *INFO)) or TRCTYPE((MYCOMP *VERBOSE)).
Note: By using the code examples, you agree to the terms of the Code license and disclaimer information.
#include <qtrc.h> #include <stdio.h> #include <errno.h> int main(int argc, char *argv[]) { const char *myComp = "MYCOMP"; int rc; rc = QtrcWriteStack(QTRC_LEVEL_INFO, myComp, "SUBCOMP", argv[0], "Call stack shows how we got here" ); if (rc != 0) { printf("QtrcWriteStack() failed with error %d\n", rc); return -1; } printf("Use the ENDTRC CL command with PRTTRC(*YES) in order to\n"); printf("see the component trace records that were written to the\n"); printf("trace collection.\n"); return 0; }Example Output:
Use the ENDTRC CL command with PRTTRC(*YES) in order to see the component trace records that were written to the trace collection.
API introduced: V6R1
[ Back to top | Problem Management APIs | APIs by category ]