Since the contents of the database in a production client must always be consistent (production clients do not have the value "T" in the CCCATEGORIE field of table T000), there are particularly strict requirements for debugging in them:

• The most important is that all database changes must be rolled back in the event of a program termination. To ensure that this is possible, a dialog process converts to a debugging process when a user wants to work with the Debugger. This process is assigned to the user for the duration of their debugging session. When the user has finished debugging, the process reverts to a normal dialog process.
• To ensure that debugging activities cannot block the whole system, only half of all dialog processes can be used for debugging.

In test clients, where data integrity is not so crucial, dialog processes are available for debugging in addition to a fixed number of debugging processes. The dialog processes are not exclusively assigned to a user, but are released after each step in the Debugger. Consequently, a database commit occurs after each step, and the database changes cannot therefore be rolled back if a program termination occurs.