Re: Service entry point debug with condition

Martijn van Breden <m.vanbreden-FA3Mb2GlndWL1xShJLHXDbmx5lbCioqB8/[email protected]>
Newsgroups gmane.editors.websphere.iseries
Message-ID <AM7P194MB0804491E03114FF8BFF4B9D6C65DA@AM7P194MB0804.EURP194.PROD.OUTLOOK.COM>
Hello David,

I've had this working in a similar situation. I created an additional  subprocedure (called it 'debugEntry") in the web program that was called right after the parameters from STDIN and/or Query_String and/or EnvVars were parsed. The subprocedure had the relevant values I needed to discriminate between the individual calls and did nothing but return. From the SEP-interface I was able to pick the program and the debugEntry subprocedure and enter the the conditions for the input parameters for that specific procedure. This method always worked for me.


Kind regards



Martijn van Breden

lead software architect




Folks:

Does anyone work with SEP debug with conditions?

I'm trying to debug an RPG program, invoked from the web server, but
only if a specific entry parameter has a specific value.

If I set the condition for the SEP to "i_req.sessionid = 'dmgtest'",
the job hangs ... but never enters debug.

It appears that the job is TRYING to  enter debug, as the call stack
shows 'QTESEPEH' as the last entry (immediately after the program I'm
trying to debug), but it never gets any farther.

After that, even if I remove the SEP condition, the program won't
enter debug until I shut down RDi and re-launch it.

Any suggestions?

David

--
IBM i on Power Systems: For when you can't afford to be out of business!

I'm riding in the American Diabetes Association's Tour de Cure to
raise money for diabetes research, education, advocacy, and awareness.
You can make a tax-deductible donation to my ride by visiting
https://mideml.diabetessucks.net.

I may have diabetes, but diabetes doesn't have me!
--
This is the Rational Developer for IBM i   (WDSCI-L) mailing list
To post a message email: [email protected]
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request-+hD5IHI5Xscn3HwCXmMcX9BPR1lH4CV8@public.gmane.org
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: [email protected]
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request-+hD5IHI5Xscn3HwCXmMcX9BPR1lH4CV8@public.gmane.org
Before posting, please take a moment to review the archives
at https://archive.midrange.com/wdsci-l.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.