Re: Debugging ISeries Job

Jeff,

To debug a program require change authority to the program object. To
service the job and thereby debug the program when it's run under another
user profile, requires *USE authority to the other profile--specifically
you need *OBJOPR (object operational), *READ, and *EXECUTE authorities.

Here's the verbiage from help:

If you are setting a service entry point for a user profile other than
that of the iSeries connection in the Remote Systems view, then your
iSeries connection profile must have:
o Authority to debug the program that will contain the service entry
point.
o *ALLOBJ authority or *USE authority to the user profile of the
specified userid.

You can also do it if you have *SERVICE authority. But my system
administrator would never allow that kind of security exposure. At least
with *USE authority to the specific profile, he can track what the
security exposures are. I debug quite frequently having only *CHANGE
authority to the program and *USE to the profile for the job I'm
debugging.

HTH,
Michael Quigley

wdsci-l-bounces@xxxxxxxxxxxx wrote on 03/06/2009 01:00:03 PM:

----- Message from Jeff Buening <JeffBuening@xxxxxxxxxxxxxxxxxxx> on
Fri, 6 Mar 2009 12:39:42 -0500 -----

To:

wdsci-l@xxxxxxxxxxxx

Subject:

[WDSCI-L] Debugging ISeries Job

I have been showing some of the other programmers debugging ISeries Jobs

in WDSC. In order for me to debug someone else's job (like the night
operator) the administrator needed to give me *USE authority to their
profile. There are certain Security issues with this and was just
wondering if having that authority is the only way to Debug some other
users job. Also the *USE authority has different levels like Execute,
Read, Write, etc... Is their a minimum that is needed to debug some
else's job, if *USE is what is needed? Just trying to give the minimum
that is needed to Debug some else's job.

Thanks,
Jeff Buening

Programmer/Analyst
jeff.buening@xxxxxxxxxxxxxxxxxxx
Phone: 419-586-8599
FAX #: 419-586-6224
www.celinainsurance.com