Testing and Running Applications in NonStop › Rebuild a NonStop Application › Access and Use the Diagram Trace Utility

Access and Use the Diagram Trace Utility

You can test all the generated C applications using the Diagram Trace Utility on NonStop. Each application requires transaction codes to map to the correct Procedure Steps and Action Blocks.

After you enable the Diagram Trace Utility, invoke your application based on the information provided in the following table:

While testing an application, any of its procedure steps or action blocks that have been generated with trace will communicate with the Diagram Trace Utility. The application screens (Block Mode only) will be updated after control is returned from the Diagram Trace Utility.

The Diagram Trace Utility lets you step through the execution of the application by viewing the sequence of action block calls and action diagram statements being executed as the generated program executes.

Note: For more information, see the Diagram Trace Utility User Guide.

Multi-user Diagram Trace Utility Support (Distributed Server Applications Only)

When a remote server application is started, one copy of the applini file for that application is available. Setting the trace environment variables within this applini file will allow only one Diagram Trace Utility to trace any of the servers that make up this server application.

Test environments involve multiple testers working with the same server application. In this scenario, you need to debug from multiple client workstations and therefore, use multiple Diagram Trace Utilities.

More information:

Using the Applini File

Override the Default Trace Environment Variables

A client transaction can transfer its host and port information of the client that is executing it. By providing this information, the server can establish communication with the Diagram Trace Utility running on that client workstation.

Follow these steps:

1. Build the server application that has been generated with trace (as before).
2. Leave the trace environment variables within the applini file that is located in the server application's model directory commented out.
3. Start your servers using the PWCOLD command.
4. Invoke the Diagram Trace Utility on your client workstation.
5. Edit the application.ini file residing in your client application's executables directory.
6. Uncomment and set the trace environment variables. You can use localhost for the TRACE_HOST variable.
7. Launch the Client Manager on your client workstation and configure to communicate with your server.
8. Execute your client application.

   The Diagram Trace Utility on the client workstation will be used to trace the server for each transaction initiated from that client.

Regenerate Remote Files After Testing

The code generated on the CA Gen Workstation for testing with trace includes features, such as trace calls, that are only needed during testing. These features increase the size of the load module significantly and impact the application's performance. Even if no changes are required as a result of the tests performed, you must regenerate the load module without trace before it is placed into production.