On 21-Jun-2016 19:06 -0500, CRPence wrote:
<<SNIP>>
Is the issue specific to debug from RDi, or does the same issue
occur from green-screen debug when using Start Service Job
(STRSRVJOB) to debug the job running with the /different user/; or
sbreak if that is the means via RDi?
For reference; inline copies of the APARs are included, given the
links to their documents will likely disappear soon, due to the OS
releases being out of support for so long:
[
http://archive.midrange.com/wdsci-l/200605/threads.html#00320]
NB the thread is broken into two: "(no subject)" and "MCH1001-Attempt to
use permanent system object &1 without authority"
[
http://archive.midrange.com/midrange-l/201606/threads.html#00060]
the cross-posted version of this thread, though replies are not also
cross-posted
[
http://www.ibm.com/support/docview.wss?uid=nas225e029b30a37aa5d862574a6003c745d]
"SE34653 - OSP-OTHER-INCORROUT AF-A ENTRIES ARE BEING POSTED BY DEBUG.
APAR (Authorized Program Analysis Report)
Abstract:
OSP-OTHER-INCORROUT AF-A ENTRIES ARE BEING POSTED BY DEBUG.
Error Description:
AF-A entries are being posted by debug when OPMSRC(*yes) and
*service for the special authority in the user profile are
specified.
Problem Summary:
AF-A security journal entries are sometimes incorrectly
reported by the System i Debugger when OPMSRC(*yes) is
specified on the STRDBG command and *SERVICE special authority
is specified for the user profile. Message MSGMCH1001 "Attempt
to use permanent system object XYZ without authority."
sometimes incorrectly appears in the job log.
Problem Conclusion:
Installation of this PTF will avoid the incorrect generation of
AF-A security journal entries by the System i Debugger when
OPMSRC(*yes) is specified on the STRDBG command and *SERVICE
special authority is specified for the user profile. Message
MSGMCH1001 "Attempt to use permanent system object XYZ without
authority." will no longer be incorrectly generated.
Temporary Fix:
Comments:
Circumvention:
None.
PTFs Available:
R610 SI32698 PTF Cover Letter 9111 [c9111610]
Affected Modules:
Affected Publications:
Summary Information:
Status............................................ CLOSED PER
HIPER........................................... No
Component.................................. 5761SS100
Failing Module.......................... RCHMGR
Reported Release................... R610
Duplicate Of.............................. "
[
http://www.ibm.com/support/docview.wss?uid=nas260380c77fa5d5be7862571dc003c8987]
"SE26773 - OSP-MSGMCH1001 Error in service job debug with OPMSRC(*YES)
APAR (Authorized Program Analysis Report)
Abstract:
OSP-MSGMCH1001 Error in service job debug with OPMSRC(*YES)
Error Description:
incorrectly getting "attempt to access system object" error
message
Problem Summary:
When using the system debugger, the customer is receiving the
error message MCH1001 "Attempt to use permanent system object
XYZ without authority." when issuing a STEP INTO debugger
command.
The error occurs when the program being debugged is running
under a profile that does not have *SERVICE authority and
is being debugged via a service job.
For the error to occur, the customer must be using the system
debugger via the Websphere Development Studio Client for
iSeries, or the IBM Rochester Graphical User Interface to
the system debugger, or the STRDBG system command
specifying the OPMSRC(*YES) operand.
The presence of the MCH1001 message in this instance does
not keep the debugger from functioning correctly.
Problem Conclusion:
Once this PTF is applied, the system debugger will no longer
incorrectly generate the MCH1001 "Attempt to use permanent
system object XYZ without authority." error message when
the debugger user issues a STEP INTO debug command.
Temporary Fix:
Comments:
Circumvention:
The circumvention is to ignore the MCH1001 error messages.
PTFs Available:
R530 SI28608 PTF Cover Letter 8085 [c8085530]
R540 SI28304 PTF Cover Letter 8183 [c8183540]
Affected Modules:
Affected Publications:
Summary Information:
Status............................................ CLOSED PER
HIPER........................................... No
Component.................................. 5722SS100
Failing Module.......................... RCHMGR
Reported Release................... R530
Duplicate Of.............................. "
midrange.com
