Debug service version 2.0.1 is below the minimum required version 3.0.0. Please update the debug service PTF.

[VTurturro]

👉🏻 Hi
I followed the instruction provided in the documentation in order to use the debugger (installed PTFs, activated bash and so on).
Nevertheless when I connect to the IBM i system I receive the error reported in the title of this issue.
What can I do to find where and what the problem is ?
Thanks in advance for your support

---

⚠️ REMOVE THIS LINE AND ANY SENSITIVE INFORMATION BELOW! ⚠️

Context	Version
Code for IBM i version	2.16.3
Visual Studio Code version	1.102.0
Operating System	win32_x64

Active extensions

Autenticazione GitHub (github-authentication): 0.0.2
Azione per server pronto (debug-server-ready): 1.0.0
Bob Cozzi's RPG IV to RPG Free Conversion (rpgiv2free): 1.0.4
COBOL (cobol): 25.7.28
Code for IBM i Spooled Files (vscode-ibmi-userspooledfiles): 1.1.2
Code for IBM i Walkthroughs (vscode-ibmi-walkthroughs): 0.5.0
Collegamento automatico per debug di Node (debug-auto-launch): 1.0.0
Creazione estensione (extension-editing): 1.0.0
Db2 for IBM i (vscode-db2i): 1.13.3
ESLint (vscode-eslint): 3.0.10
Emmet (emmet): 1.0.0
Error Lens (errorlens): 3.26.0
Esegui merge del conflitto (merge-conflict): 1.0.0
Funzionalità dei linguaggi TypeScript e JavaScript (typescript-language-features): 1.0.0
Funzionalità del linguaggio JSON (json-language-features): 1.0.0
GIT (git): 1.0.0
Git Base (git-base): 1.0.0
GitHub (github): 0.0.1
IBM i Debug (ibmidebug): 3.0.0
IBM i Project Explorer (vscode-ibmi-projectexplorer): 2.12.3
Indenticator (indenticator): 0.7.0
IntelliCode (vscodeintellicode): 1.3.2
Modifica della configurazione (configuration-editing): 1.0.0
RPGLE (vscode-rpgle): 0.32.1
Richieste pull GitHub (vscode-pull-request-github): 0.114.3
Source Orbit (vscode-sourceorbit): 1.4.1
Supporto di npm per VS Code (npm): 1.0.1
TODO Highlight (vscode-todo-highlight): 1.0.5

---

Remote system

Setting	Value
IBM i OS	V7R5M0
Tech Refresh	5
CCSID Origin	280
Runtime CCSID	280
Default CCSID	280
SSHD CCSID	?
cqsh	true
SQL	Enabled
Source dates	Enabled

Enabled features

/QOpenSys/pkgs/bin	/usr/bin	/QSYS.lib/ILEDITOR.lib	/QSYS.LIB	/QIBM/ProdData/IBMiDebugService/bin	/QOpenSys/QIBM/ProdData/JavaVM/jdk80	/QOpenSys/QIBM/ProdData/JavaVM/jdk11
bash	attr	GETNEWLIBL.PGM	QZDFMDB2.PGM	startDebugService.sh	64bit	64bit
find	iconv
git	setccsid
grep	uname
ls
md5sum
sort
stat
tar
tn5250

Shell env

BUILDLIB=QGPL
CURLIB=QGPL
HOME=/home/VTURTURRO
HOST=10.250.108.1
LIBLS=CORSORPGB0 DB_TEST FAQ400DB QTEMP QGPL
LOGIN=vturturro
LOGNAME=vturturro
MAIL=/var/spool/mail/vturturro
OLDPWD=/home/VTURTURRO
PASE_USRGRP_LIMITED=N
PATH=/QOpenSys/usr/bin:/usr/ccs/bin:/QOpenSys/usr/bin/X11:/usr/sbin:.:/usr/bin
PWD=/home/VTURTURRO
SHELL=/QOpenSys/pkgs/bin/bash
SHLVL=1
SSH_CLIENT=192.168.53.2 59346 22
SSH_CONNECTION=192.168.53.2 59346 10.250.108.1 22
TZ=<CET>-1<CEST>,M3.5.0,M10.5.0/03:00:00
USER=vturturro
USERNAME=VTURTURRO
WORKDIR=/home/VTURTURRO
_=/QOpenSys/usr/bin/env

Variants

{
  "american": "#@$",
  "local": "£§$"
}

[sebjulliand]

Hi @VTurturro ,
double check if the PTFs have been actually applied and not just installed).

Then, open the /QIBM/ProdData/IBMiDebugService/package.json file located on the IFS and check that version reports 3.0.0:

Finally, try connecting and reloading your connection settings (just once):

[CiTRO33]

Hi did you got the Debug-service to run?

i also have problems. if i try to regenerate the Debug Service Trust Store i got the message that PTF SJ05012 is not installed.

but it is:

but in the file QIBM/ProdData/IBMiDebugService/package.json there is still version 2.0.1

if i manuell change the version to 3.0.0 i can regenerate the trust store, but if i try to start the debug service

in /QIBM/userData/IBMiDebugService/startDebugService_workspace/startDebugServiceNavigator.log i got the message:
Environment variable DEBUG_SERVICE_KEYSTORE_PASSWORD is not set.

@sebjulliand do you have a tip what can i do?

[sebjulliand]

@CiTRO33 , changing the version to 3.0.0 in package.json if it was 2.0.x won't help you go further, I'm afraid.
However, I think (from what I observed, so it's totally empirical) that applying the PTF while the service is running can result in the files not being replaced. If that happens, you should have another folder under /QIBM/ProdData that starts with IBMiDebugService, but with a suffix. So my question would be: what folders you have under /QIBM/ProdData at the moment?

[CiTRO33]

Hi,

currently are this folders in QIBM

/QIBM/ProdData/IBMiDebugService.v2.0.1upd.src has in package.json also 2.0.1
/QIBM/ProdData/IBMiDebugService.v2upd.src 2.0.0

[sebjulliand]

Hmm...at this point, I'd suggest to start from scratch and get rid of every IBMiDebugService folders (the three of them), delete /QIBM/userData/IBMiDebugService as well and then re-apply PTF SJ05012. After it's re-applied, you should have only one /QIBM/ProdData/IBMiDebugService folder in there. In this folder, check that pakage.json has version 3.0.0. At this point, you should be good to go.

[CiTRO33]

thanks, sorry, but I have to bother you, because i got a little bit stuck , how i can re-apply the ptf (its not my daily business)

DSPPTF:

if i try to APYPTF LICPGM(5770SS1) SELECT(SJ05012) APY(*PERM)

it says the ptf is already applied.

if i try to remove the ptf
rmvPTF LICPGM(5770SS1) SELECT(SJ05012) rmv(*PERM)

it says it can't be removed because its permanently applied

[sebjulliand]

Hmm...I'm no sysadmin so my PTF knowledge is quite limited as well. Seems like you can't remove a permanently applied PTF.

However, since that PTF only installs/updates /QIBM/ProdData/IBMiDebugService...you'd need to find someone that has installed it on a 7.5 LPAR, so they could zip that folder and send it to you so it can be "installed" on your LPAR.

I don't have a 7.5 LPAR at hand though, so I can't do that for you. But if you have another LPAR, that can work.

[CiTRO33]

i will try it. i will report after my holiday - thank you

[mkwan01]

@CiTRO33 @VTurturro It is likely that you did not stop the debug service before applying the update PTF. When the debug service is running, some files are locked and the PTF apply may fail to update some of the files. You can try to remove the PTF and apply it again, if the PTF is temporarily applied. If it is permanently applied, please contact IBM Level 2 support. They will provide you a zip image to restore the driver.

[mkwan01]

In the next PTF update, we will check the debug service status and stop it if it is running, before doing the real apply work. Currently we document the requirement to stop the debug service in the PTF cover letter. However, some users may forgot to follow this requirement when updating the PTF.