It happens debugs are created and at first sight it is not clear why or how. Here's a list of different locations to check. Feel free to reply with more locations or with a request to enhance or clarify. I can update this original text after your reply and if needed.

General things to check:

• Which user is seen in the debug header?
• On which systems (CS, clients) are debugs created?
• Which processes/agents are generating debugs?
• Which sessions are generating debugs (all, only scheduled, only specific clients, other subsets ....)?
• What postfix (end of the file name) is seen?

The answers may help to understand which of the following may possibly apply.

1. GUI debugs

File --> Preferences ...

Note that this would generate at least GUI debugs on the GUI system (MANAGER, GUICORE, BACKUP, etc). When these are seen, it is clear the debugs are enabled out of a GUI. Any session started from this GUI would also generate debugs (on all systems involved in the session). Just restart the GUI to disbale the debug creation. Check wether the debugs are gone. It is still possible there are other locations in addition to this GUI setting.

2. CRS debugs

When CRS debugs are seen on the Cell Server, all sessions started in whatever way will inherrit the debug enablement. Stop CRS debugging to disable this. Check wether the debugs are gone.

3. omnirc/.omnirc

The omnirc file may contain a debug statement. That may be on a client system (check omnirc on the client where the debugs are seen). But if it is set on the cell server, it will also generate debugs on clients. Remove the line from omnirc and save to disable. Restart services if the setting was on the cell server. Restart the Inet service on a client. Check wether the debugs are gone.

4. Inet debugs

When the inet service is debugged, all agents started by it will inherrit the debug setting. This is local to the client itself. Restart the service (services.msc on windows, systemd [or xinetd in the past] on Linux) without a debug option. Check wether the debugs are gone.

5. Environment

Possibly an environment parameter OB2DBG is set on the OS level. This could be on the cell server or on a client. Commands to verify this are "env" on Linux and "set" on Windows. However, make sure to check the environment of the correct user (the one that is seen in the debug header). Note that on a client it may also be inherrited from the cell server (and so it may be the backup owner on the cellserver rather than the inet user on the client). On Windows the environment parameters can also be checked in the Advanced system settings from the system properties.

If the parameter is found then delete it. Restart services on the cell server and/or inet on the client(s). Note that the parameters may be gone already and this service restart may be the only action still required (which is making things pretty confusing in that case).

6. Windows registry

This is basically the OS environment also, like above. But if it was not found there then search the registry for OB2DBG. Delete any keys found and restart services.

More may possibly still get added ....

You may be interested to some of my other Support Tips too: Support Tips listed per category.