The user account is disabled when I try to debug

On an IBM i partition running version 7.6, when I try to run the command to debug a program, my user profile gets disabled.

I've tried using different clients and recreating the configuration to prevent the password from being cached, but the problem occurs every time.

The debugger version is 3.0.5, extension version 3.0.4.

From the logs, I see:
```
(2026-08-31 20:55:24.0887) DBGM0021I Initializing service entry points for user BUZZI on host NEBULA.ELMEC.COM.
Connected to host LOCALHOST

(2026-08-31 20:58:19.0448) Debugging batch program: BUZZI/TSTMSGW
Batch command line: SBMJOB CMD(CALL PGM(BUZZI/TSTMSGW)) INLLIBL(QGPL QTEMP) CURLIB(qgpl) JOBQ(QSYSNOMAX) MSGQ(*USRPRF) CPYENVVAR(*YES)
Connection: LOCALHOST
Error message: IBM i Debug Server has not been started yet.
Please run the STRDBGSVR command from a user profile with enough authority.

(2026-08-31 20:58:19.0776) Launch configuration: {"com.ibm.etools.systems.as400.debug.ui.connection.connectionName.": "LOCALHOST", "com.ibm.etools.systems.as400.debug.ui.debugProgram.library.": "BUZZI", "com.ibm.etools.systems.as400.debug.ui.debugProgram.name.": "TSTMSGW", "com.ibm.etools.systems.as400.debug.ui.debugProgram.type.": "*PGM", "com.ibm.etools.systems.as400.debug.ui.error.launchInfoTab": "IBM i Debug Server has not been started yet.
Please run the STRDBGSVR command from a user profile with enough authority.", "com.ibm.etools.systems.as400.debug.ui.launchCommand.LaunchCommandName": "SBMJOB CMD(CALL PGM(BUZZI/TSTMSGW)) INLLIBL(QGPL QTEMP) CURLIB(qgpl) JOBQ(QSYSNOMAX) MSGQ(*USRPRF) CPYENVVAR(*YES)"}
org.eclipse.core.runtime.CoreException: IBM i Debug Server has not been started yet.
Please run the STRDBGSVR command from a user profile with enough authority.
at com.ibm.etools.iseries.debug.internal.core.AS400LaunchConfiguratonBaseDelegate.handleLaunchFailure(AS400LaunchConfiguratonBaseDelegate.java:507)
at com.ibm.etools.iseries.debug.internal.core.AS400LaunchConfiguratonBaseDelegate.launch(AS400LaunchConfiguratonBaseDelegate.java:137)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:803)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:716)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:711)
at com.ibm.etools.iseries.daas.internal.dap.IBMiDAPBaseLauncher.launchFromConfiguration(IBMiDAPBaseLauncher.java:265)
at com.ibm.etools.iseries.daas.internal.dap.IBMiDAPBaseLauncher.launch(IBMiDAPBaseLauncher.java:248)
at com.ibm.etools.iseries.daas.internal.dap.IBMiDAPLaunchExtension.launch(IBMiDAPLaunchExtension.java:40)
at com.ibm.debug.pdt.daas.internal.dap.requests.DAPLaunchRequest.processRequest(DAPLaunchRequest.java:125)
at com.ibm.debug.pdt.daas.internal.dap.requests.DAPRequest.process(DAPRequest.java:112)
at com.ibm.debug.pdt.daas.internal.dap.requests.DAPRequest.process(DAPRequest.java:97)
at com.ibm.debug.pdt.daas.internal.dap.DAPRequestProcessor$1.run(DAPRequestProcessor.java:119)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
```

But if I run STRFBGSVR:
```
Additional Message Information

Message ID . . . . . . : CPFAC00 Severity . . . . . . . : 40
Message type . . . . . : Diagnostic
Date sent . . . . . . : 31/08/26 Time sent . . . . . . : 21:15:29

Message . . . . : Debug server router function already active.
Cause . . . . . : Only one copy of the debug server router function may be
active at a time.
Recovery . . . : Use the ENDDBGSVR command and then try the STRDBGSVR
command again.

Bottom
Press Enter to continue.

F3=Exit F6=Print F9=Display message details F12=Cancel
F21=Select assistance level
```

And also from the extension i can see that all jobs required are active:

Start with the launch path shown in AS400LaunchConfiguratonBaseDelegate.java and IBMiDAPBaseLauncher.java, then compare the captured “server has not been started” error with CPFAC00 from STRDBGSVR. Reproduce on IBM i 7.6 using the listed debugger and extension versions; done means debugging no longer disables the user profile and the required jobs remain active.

Written by the indexing model from the issue text.