Replies: 8 comments
-
Hello Sam And I can see that subdirectories and files which are created when Debug Service is started still have Read only authority for anyone else than you (as shown in attached Excel file created with "WITH OBJS AS (SELECT PATH_NAME FROM TABLE(QSYS2.IFS_OBJECT_STATISTICS(START_PATH_NAME => '/QIBM/UserData/IBMIDEBUGSERVICE', subtree_directories => 'YES'))) SELECT OBJS.PATH_NAME, OBJECT_TYPE, OWNER, DATA_AUTHORITY, OBJECT_OPERATIONAL, OBJECT_MANAGEMENT, OBJECT_EXISTENCE, OBJECT_ALTER, OBJECT_REFERENCE, DATA_READ, DATA_ADD, DATA_UPDATE, DATA_DELETE, DATA_EXECUTE FROM OBJS, TABLE(QSYS2.IFS_OBJECT_PRIVILEGES(PATH_NAME)) where AUTHORIZATION_NAME = '*PUBLIC';" SQL statement). |
Beta Was this translation helpful? Give feedback.
-
But wait... Files created by me at debug session time are owned by Sam's profile as he started the Debug Service.
|
Beta Was this translation helpful? Give feedback.
-
So, sounds good to me now. |
Beta Was this translation helpful? Give feedback.
-
I'm in a dialog with Holger exactly about that (we're both members of CEAC). Stay tuned... |
Beta Was this translation helpful? Give feedback.
-
@MarcoDeSenas Interestingly, some of the messages are in German. PUB400 is a German machine after all but I wonder is there is a way to fix that. |
Beta Was this translation helpful? Give feedback.
-
Excellent, thanks. Staying tuned... Hopefully whatever you come up with can become a documented recommendation for other systems that may have similar sharing/authority issues. |
Beta Was this translation helpful? Give feedback.
-
Ideally, IBM could create two new TCP servers, one for the Debug Server and one for the Debug Service, and include them in the list of available servers for SERVER parameter of STRTCPSVR command. Just like existing *DBG server. Mmmmm, three distinct debug services, this is quite confusing for me! |
Beta Was this translation helpful? Give feedback.
-
Glad it works, even though you seriously messed with it 🤣 The debug server is fine as it. It's been around for years, used by RDi, and well integrated with the OS ( The debug service is not integrated with IBM i at all. It's a Java based HTTP server (because IBM wanted to reuse existing bricks I guess), delivered with some shell scripts and...that's it. At this point you're on your own. We try to provide a good user experience in Code for IBM i by wrapping it in commands and automating the configuration as much as possible but at the core, it lacks an actual integration with the OS. Anyway, keep an eye on this PR; this is where the next improvement will come from: #1990 Once it's merged, Holger will be able to generate the certificate and configure the service so it can be called with a good old |
Beta Was this translation helpful? Give feedback.
-
Question: Is it possible with version 2.9.0 to debug on PUB400, or is there something coming in a later release that we should wait for?
Last week (4/15), for the first time on PUB400.COM I was able to use VS Code to step through a program. Yeah!
On 4/19, Marco, another PUB400 user, tried debugging but he failed, getting "
CPD0168 Not authorized to library DIMARCO1
". We're guessing that was because I was the user of the QB5ROUTER job and as such it had no access to his library. I killed my QB5ROUTER job.Marco then tried debugging again, but got "
EQAVS1007E on port 8005 could not be connected.
".Today (4/22) I deleted the
QIBM/UserData/IBMIDEBUGSERVICE/
since I owned it and had full rights. The only thing I couldn't delete wasQIBM/UserData/IBMIDEBUGSERVICE/certs
, since that was owned by another user (train248).I started again with the debug walkthrough and then tried debugging. Now I get port 8005 could not be connected:
I presume that is because someone else now "owns" the QB5ROUTER job:
I tried
IBM iDebug: Stop Debug Service
and got "EQARD1028E The request to stop the Remote Debug Service daemon failed because port 8001 was invalid or the daemon was not running
."Here's a link to the PUB400 Forum discussion in case it is useful. April 15 is where I start discussions with Marco:
https://pub400.com/mbr/forum.nd/listposts?yBID=1&yBSID=3&yTID=2024-01-02-18.43.19.752652
Here's what I'm seeing in the DEBUG CONSOLE when debugging fails.
Here's the OUTPUT tab when I start debugging a program:
/home/LENNONS: test -r /QIBM/ProdData/IBMiDebugService/package.json
{
"code": 1,
"signal": null,
"stdout": "",
"stderr": ""
}
Active extensions
Remote system
Enabled features
Shell env
Variants
Errors
Beta Was this translation helpful? Give feedback.
All reactions