So I had a chance to look more, here is the answer if you have not found it ..
Question:
Service entry point without a condition works for me but conditional service entry point does not work. The program appears to be hung from a 5250 session when a conditional service entry point is hit.
Answer:
It may be an authority issue with your debug user profile. Your debug user profile need to have *USE authority to the profile that owns the QB5ROUTER job and also its job description. Suppose the owner of the QB5ROUTER job is USR1 and your debug user profile is USR2, and the job description of the USR1 profile is QGPL/USR1, you can use the following commands from a terminal session to grant additional authority to your debug user profile:
GRTOBJAUT OBJ(QGPL/USR1) OBJTYPE(*ALL) USER(USR2) AUT(*USE)
GRTOBJAUT OBJ(USR1) OBJTYPE(*USRPRF) USER(USR2) AUT(*USE)
You need to restart the debug service and the debug router (QB5ROUTER) after these changes.
---
Mike Hockings, M.Eng.
IBM Rational Developer for System z and Power Systems Software Technical Support
IBM Canada Ltd. Laboratory
hockings@xxxxxxxxxx<mailto:hockings@xxxxxxxxxx>
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of Mike Hockings <hockings@xxxxxxxxxx>
Date: Thursday, July 17, 2025 at 4:36 PM
To: Rational Developer for IBM i <wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject: [EXTERNAL] Re: [WDSCI-L] Service entry point debug with condition
Hey David,
Just for you alone I asked the peeps in the know and was told that they found an authority requirement with conditional SEPs that also applies to conditional SEP in RDi. They created a FAQ entry for this in Merlin debug doc but I have not pursued it further, that exercise is left to the gentle reader.
https://ibm.github.io/merlin-docs/#/./guides/ide/debug?id=frequently-asked-questions
Mike
---
Mike Hockings, M.Eng.
IBM Rational Developer for System z and Power Systems Software Technical Support
IBM Canada Ltd. Laboratory
hockings@xxxxxxxxxx<mailto:hockings@xxxxxxxxxx>
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of David Gibbs via WDSCI-L <wdsci-l@xxxxxxxxxxxxxxxxxx>
Date: Wednesday, July 16, 2025 at 5:28 PM
To: Rational Developer for IBM i <wdsci-l@xxxxxxxxxxxxxxxxxx>
Cc: David Gibbs <david@xxxxxxxxxxxx>
Subject: Re: [WDSCI-L] [EXTERNAL] Service entry point debug with condition
On Wed, Jul 16, 2025 at 1:50 PM Greg Wilburn <
gwilburn@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
I am able to set SEP and set a conditional breakpoint on a line of code.
But the job always jumps into debug the instant it starts.
I hit F8 or click run... then it will break into the job when the
condition is met.
Or am I not understanding? Is there a way to have the SEP not jump into
debug until the condition is met?
I’m not talking about conditional breakpoints. This is a conditional SEP.
When you are setting a sep debug, there is a condition field in the dialog.
I’m not at my desk right now, but I think it’s just above the user profile
field.
David
--
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/wdsci-l .
--
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/wdsci-l .
midrange.com
