|
|
|
|
|
DIPs can be traced by embedding debug information in the DIP and displaying it via the trace command and the db_pr command. This is an optional step, but is recommended. This feature is enabled by VSstartup or startup. The purpose of this capability is debugging the DIP during development, rather than providing information about problems in the production application. Include as many db_pr statements as are necessary. The debug information should be strategically placed in the DIP code. When the DIP is running, issue the trace command from the shell command line to print debug information on your terminal as it is executed in the DIP code. The db_pr statements may be left in while the application is in production. They do not impose a cost or cause any disadvantage.
