Introduction › Session Considerations › Performance Standards

Performance Standards

All Activities Permissible

During a debugger session, you can perform any activity related to DC/UCF, not just debugging. For a given session, there are no restrictions on the number or kinds of entities debugged or on the length of the session.

For example, within a single debugger session, you can successively:

• Initiate a debugger setup phase
• Leave the debugger setup phase to conduct an online PLOG session
• Return to the setup phase to debug another program
• Leave the debugger setup phase again to conduct an IDD session
• Execute one of the programs you are debugging

Minimize Unrelated Work

When the DEBUG task code initiates a debugger session, the DC/UCF system saves your current screen, whether or not the screen is directly related to any modules being debugged. Consequently, the debugger incurs some processing overhead each time the current screen changes. For best performance, therefore, keep work unrelated to the debugging process to a minimum.

Also, although the setup phase is pseudo conversational, the runtime phase is completely conversational, which ties up system resources. Even database resources are tied up while the debugger has control.

In order to use resources most efficiently, therefore, always return control to DC/UCF before you leave your terminal or attend to concerns other than debugging.