-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SEP Debugger Cannot Be Run for A Different User #2495
Comments
Hi! It's on IBM's roadmap and being worked on (search the issues, you'll find a few references to this). |
Ah, thanks Sebastian. I did do a quick search, but the filter was for "open" issues and didn't find any. To save the same issue/question being raised by others doing the same, might I suggest keeping one of these open for people to find? |
You're welcome |
@PaulDV-Culina This is already supported in the current IBM i debug client (v2.0.2). You also need to update the debug service PTF to v2.0.1. The SEP hitter profile is the current logon profile by default. But you can use a context menu action to change the hitter profile. If you have debug client v2.0.2, you can right click on a SEP and select the "Modify User Profile..." action and set it to the user profile that the web service is running on. |
Thanks Morris. Forgive my ignorance, but what do you mean by updating the debug service PTF to v2.0.1? |
@PaulDV-Culina To use the newer debug client (v2.0.2), you need to update the debug service PTF to the following level: |
Thank you! Very useful - I'll put in the support request 👍 |
In RDi, we are used to being able to debug programs which are being invoked by other users/jobs, e.g. web services running in the IWS, users demonstrating a Production issue, etc., but there doesn't seem to be a way to do this with the debugger in VS Code.
Am I missing a setting somewhere or is this not possible?
If it's not possible, can it be confirmed that this feature is being worked on, please?
Many thanks,
Paul.
The text was updated successfully, but these errors were encountered: