Security to use RDP's debugger when you do not have *SERVICE

I was recently talking to some people who didn't know (since they had that
authority) that others often can't use the RDP debugger because it uses
STRSRVJOB under the covers and they do not have *SERVICE authority. I am
wondering if my knowledge is an ancient tidbit. Because I am seeing ptf
cover letters for V5R3 that says that was true but they came out with a
ptf that allowed you to not have to use the circumvention of giving
*SERVICE authority to those programmers who wanted to debug. And that ptf
is now on a cume.
http://www-912.ibm.com/a_dir/as4ptf.nsf/a18db68aae4a7d81862566ba005d145c/8a01f72308e5954d8625733f005d90a2?OpenDocument&Highlight=2,debug,service,authority

So, do they have matching ptf's for supported OS's or is it now in the
base?

I see there may still be a limitation on trying to debug a job running
under a different user profile this way. You need some access to the user
profile as outlined in
http://www-912.ibm.com/a_dir/as4ptf.nsf/a18db68aae4a7d81862566ba005d145c/2af1b7b575d3f2c486257380006e3405?OpenDocument&Highlight=2,debug,service,authority

We tend to not give *ALLOBJ authority to our development staff. Increases
security and cuts back on those "works for me, sucks to be you" responses
to the end users. Not that they would put it like that but it's just a
way to summarize.


Rob Berendt