Debug related issues.

[a4ginatl]

I believe I now have all the IBMi PTFs and apps/extensions installed.

I have the extension installed and see that we need to generate a certificate to use it.
We can generate a local cert, that is not a problem.
The question is: Is it a plain Jane cert or would the debugger looking for certain attributes on the cert? If yes, what would they be?

I cannot find any videos on debugging with Code4i, it could be that I don't know how to ask for videos on using the debugger. Are there any videos or documents?

To run the debugger, does it require the 5250 terminal to use the debugger?

Thanks, Darryl Freinkel.

---

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

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

Active extensions

COBOL (cobol): 25.8.13
Code for IBM i Spooled Files (vscode-ibmi-userspooledfiles): 1.1.2
Code for IBM i Walkthroughs (vscode-ibmi-walkthroughs): 0.5.0
Configuration Editing (configuration-editing): 1.0.0
Db2 for IBM i (vscode-db2i): 1.14.0
Emmet (emmet): 1.0.0
Error Lens (errorlens): 3.26.0
Git (git): 1.0.0
Git Base (git-base): 1.0.0
GitHub (github): 0.0.1
GitHub Authentication (github-authentication): 0.0.2
IBM i Debug (ibmidebug): 3.0.0
IBM i Project Explorer (vscode-ibmi-projectexplorer): 2.12.3
JSON Language Features (json-language-features): 1.0.0
JavaScript Debugger (js-debug): 1.102.0
Merge Conflict (merge-conflict): 1.0.0
Node Debug Auto-attach (debug-auto-launch): 1.0.0
Server Ready Action (debug-server-ready): 1.0.0
Source Orbit (vscode-sourceorbit): 1.4.1
TODO Highlight (vscode-todo-highlight): 1.0.5
Terminal Suggest for VS Code (terminal-suggest): 1.0.1
TypeScript and JavaScript Language Features (typescript-language-features): 1.0.0

---

Remote system

Setting	Value
IBM i OS	V7R4M0
Tech Refresh	11
CCSID Origin	65535
Runtime CCSID	65535
Default CCSID	37
SSHD CCSID	?
cqsh	true
SQL	Enabled
Source dates	Disabled

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
chsh	iconv
ls	setccsid
md5sum	tar
sort	uname
stat
tn5250

Shell env

BUILDLIB=GRPLIB
CURLIB=GRPLIB
HOME=/home/DXF
HOST=S1030723
LIBLS=PRDMODS QGPL PRDFILES# USRTEST USRFILES# PGMTEST MDRST MDRSTPRD MDRSTUSR MDRSTDEV DXFLIB QGDDM QTEMP ROBOTLIB
LOGIN=dxf
LOGNAME=dxf
MAIL=/var/spool/mail/dxf
OLDPWD=/home/DXF
PATH=/QOpenSys/pkgs/bin:/QOpenSys/usr/bin:/usr/ccs/bin:/QOpenSys/usr/bin/X11:/usr/sbin:.:/usr/bin:/QOpenSys/usr/bin:/usr/bin
PWD=/home/DXF
SHELL=/QOpenSys/pkgs/bin/bash
SHLVL=1
SSH_CLIENT=10.245.16.186 57996 22
SSH_CONNECTION=10.245.16.186 57996 10.10.20.10 22
TZ=<CST>6<CDT>,M3.2.0,M11.1.0
USER=dxf
USERNAME=DXF
WORKDIR=/home/DXF
_=/QOpenSys/pkgs/bin/env

Variants

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

[sebjulliand]

All the documentation about the debugger can be found here: https://codefori.github.io/docs/developing/debug
There are no videos or other document, as far as I know.

The Debug Service certificate must be generated or imported in the LPAR Digital Certificate Manager first (there may already be one you use if you have other services running securely). Ideally, the certificate common name (CN) should be the LPAR's host name, and it should also have the IPv4 address and fully qualified domain name as Subject Alternative Names.

But it's nothing out of the ordinary; the debug service won't look for any specific attributes.
Once the debug service keystore has been generated from iNav, you can start it from there too.

Once both the debug service and the debug are started (both from iNav), you can debug from VS Code. No need to use a 5250 terminal.