Analytica Business Systems: Pervasive.SQL and Btrieve Specialists

Pervasive.SQL, Btrieve and More KnowledgeBase | Article #55 | Techniques for Trace
View an Article   Back
Title: Techniques for Trace 
Category: Pervasive.SQL PSQL (Any Version) 
Keywords: mkde, trace, btrieve 
Description: Question:
How do I use the microkernel trace feature to see how my application functions?

Here are the steps for tracing an application's database accesses:
1. Get all users out of the database
2. Have one user get the application to the point that you are interested in.
3. In the PCC, go to the Configuration/Server/Debugging settings and enable MKDE Tracing for all operations.
4. Remember apply the change. You don't have to stop and start the services to enable tracing. This is the only setting in the configuration this is true for.
5. Run the application for the process you want to check out.
6. When it is done, go back to disable MKDE Tracing and Apply again.
7. Now, you can review the contents of the MKDE.TRA log file you just created (its default location is \PVSW\BIN\MKDE.TRA. This is a developer-level log file, but any Btrieve developer can read most of the information in there to let you know exactly what transpired which that process was running. You will see operation codes, data buffers, and such. See the online manuals for exact details if you need help with the analysis, contact us for help. 

If you like our free Pervasive Knowledge Base Service, please consider purchasing your next Pervasive Software Product from our online store or call or email us!

In the meantime, to help us keep this service free, would you mind clicking on one of the ads at the left? Thanks for visiting!