Re: RDi debug & authority failures

On 22-Jun-2016 09:03 -0500, dlclark wrote:

On 03-Jun-2016 13:28 -0500, Justin Taylor wrote:

On 03-Jun-2016 08:24 -0500, Justin Taylor wrote:

I'm debugging an RPGLE webservice that uses CGIDEV2. It's
generating a lot of authority failures (AF) against IBM objects
(QSYS/Q* stuff). […]

The AF entries only occur in debug. […]

Would I be correct to presume that you at least have debug
configured for production library/file access?

RDi-> Window-> Preferences-> Run/Debug-> IBM i Debug-> Update production files

-- or --

STRDBG UPDPROD(*YES)

FWiW, that setting [UPDPROD(*YES)] for that debugging attribute would be moot, with respect to the issue of the T-AF entries logged, as the protection afforded by Update Production Files (UPDPROD) setting of *NO, is unrelated to authority. That prophylactic feature is implemented entirely within the /Open/ method(s), as a check of the Library Type (TYPE) for the library in which the file resides, if\after determining from the job's Work Control information that the job is both under debug and that the UPDPROD(*NO) setting is currently in effect for that debug session. For maximal safety, the test of the Library Type value is supposed to be coded within the OS as "If LibType<>'TEST' then…"; i.e. any value other than 'TEST', even a corrupted value, will cause the library to be treated as if the TYPE attribute of that library is 'PROD'.