Argument | Description |
as_filename | String (Optional). The full path and filename to save the trace results to. If set to an empty string "", PowerHome will default create the trace file in the current directory (typically c:\powerhome) with a filename of "phtrace_yyyymmddhhmmss.pbp" where yyyymmddhhmmss is the current date and time |
as_label | String (Optional). An optional user defined label to be stored at the top of the trace file. If set to empty string "", PowerHome will default use a label of "Start Trace yyyymmddhhmmss" where yyyymmddhhmmss is the current date and time |
ai_clocktype | Integer (Optional). The clock type to use during the trace. Valid values are 0 for none, 1 for clock, 2 for process, and 3 for thread. Using values of 1, 2, or 3 will cause clock and timing information to also be written to the trace file. Storing clock info can be expensive in terms of efficiency and may not always be necessary to solve certain problems |
ai_options | Integer (Optional). The options to use for the tracing session. Values are added together to achieve the desired mode of operation with each value specifying a particular operation type to store in the trace file. Valid values are 1 for Object Create/Destroy, 2 for Routine, 4 for Line, 8 for User, 16 for SQL, 32 for Error, and 64 for Garbage Collection |
If the overload for this function without parameters is used. It will use the default value for as_filename and as_label. The clocktype will be 1 and the options will be 10 (Routine and User)
Tracing is not something a user would typically do on his own. The resulting trace file is not human readable and must be decoded by the developer using the PowerBuilder development environment in which PowerHome was written in. Tracing will usually be initiated at the developers request to help a user track down problems or issues they may be having