Dette indhold er ikke tilgængeligt i dit sprog endnu.
Debugging ILE programs is now available inside of Visual Studio Code. We’ve added UI to make sure setting up the Debug Service to be a swift process.
After configuring the Debug Service, launching a debug session is a click of a button away. When you have active source open, a new Debug button will appear in the navigation bar. Breakpoints can be set prior to debugging, or during the debugging session.
Clicking the Debug button will display an input box which will allow the user to customise the command which starts the debug job. This allows the developer to pass in parameters, or call another program to launch the debug session.
After the debug session has started, every session will break on entry. You can read more about the debugging UI on the Debug actions section on the Visual Studio Code documentation .
To debug a program from the Object Browser, right-click on the program object and select the Debug Program option. Like before this will also display an input box to modify the command which starts the debug job.
/QIBM/ProdData/IBMiDebugService/bin/certsTo make use of the Debug Service, you need the following PTFs:
After you have installed the PTFs, the connection inside of Visual Studio Code will need to be restarted.
After connecting to a system in Code for IBM i, if the PTFs are installed but the service is not configured (i.e. the certificates don’t exist) you will see a notice asking if you’d like to open the Walkthrough to configure the Debug Service. Clicking the button will open the Walkthrough.
This Walkthrough can easily configure the Debug Service and start it up. The last steps have buttons to ‘Generate certificates’ and ‘Start debug service’. Running them in order will do all the work to setup the service.
It will ask you to confirm the initialisation.
The ‘Start debug service’ button will spin up the Debug Service. If the Debug Service is already running, it will ask you if you want to end the existing instance before starting a new one - this is a requirement. It is not recommended to run two instances of the Debug Service at once.
You can also start the Debug Service through the command palette:
The Debug Service depends on two ports by default:
These ports can be changed in /QIBM/ProdData/IBMiDebugService/bin/DebugService.env, both DBGSRV_PORT and DBGSRV_SECURED_PORT respectively.
If DBGSRV_SECURED_PORT is changed, make sure to:
DBGSRV_SECURED_PORT). Every user will need to do this step.
As depicted in this diagram, the client (VS Code, IBM i Debug) connects to the Debug Service, which talks to the Debug Server.
STRDBGSVR. You may get an error message in VS Code if you attempt to debug when the Debug Server is not running.
This is a limitation for CL. The local variables will not show up in the Variables view for CL. You can add a local variable to the Watch view to inspect its value. The CL limitation also exists in RDi.
There is a known issue that when you start debugging from VS Code, the debugger hangs and doesn’t launch.
The fix is to check if you’ve got a prior debug job stuck in MSGW. You can do this with WRKACTJOB, or a similar command like WRKSBSJOB QBATCH.
Users should no longer face this issue as we now submit debug jobs to QSYSWRK with QSYSNOMAX.
STRDBGSVR requirementThe Debug Service that is started depends on the traditional Debug Server.
If you receive this message, do as it says. Simply start the Debug Server with STRDBGSVR from a greenscreen.
It is always recommended you use a hostname in the connection settings to make use of the debugger when in secure mode.
Error that is shown when connecting to the debugger if connecting using an IP address.
This error occurs when the hostname used to connect to the debugger (which might be the IP address that was configured in the connection settings) is not the same as the host name created as part of the certificate.
If you are using a system that doesn’t have a host name (for example YOURSYSTEM, or pub400.com), then an entry should be added to your device’s ‘hosts’ file. This entry should be the same on all devices in your network to ensure that everyone is using the same hostname.
c:\Windows\System32\Drivers\etc\hosts/etc/hostsYour entry might look like this:
# IP HOSTNAME192.168.0.20 MYIBMIIf you find that you’ve added your local hostname entry and the error is still occurring, then you may need to delete the existing certificates from /QIBM/ProdData/IBMiDebugService/bin/certs on the IFS and generate them again in the Walkthrough.