Re: Getting a CPF4269 - 'Not authorized to object QADBERAP in QRECOVERY type *FILE.'

Thanks Chuck.

Unfortunately, the process in question is our EOD job which is
submitted by an external system. It'd probably take me a week to get
the process changed to run under an *ALLOBJ user and would probably
require a signed policy exception from the CIO.

So I'll pass your post along to the sysadmins and let then get in
touch with IBM.

Thanks again,
Charles



On Wed, Dec 16, 2009 at 3:56 PM, CRPence <CRPbottle@xxxxxxxxx> wrote:

CRPence wrote:

<<SNIP>> the SQL DELETE may or may not have completed without
error without said defect [e.g. perhaps cpf5090 is manifest as
sql0901 or similar].

  Of course performing the still failing request, again, with a
user having the special authority *ALLOBJ, would answer the question
of how the SQL DELETE might be impacted.  For that user having the
necessary authority, that the query component does not adopt, would
no longer be an issue.  Thus whatever issue remains, if even one
still does remain, would be manifest as the more appropriate error
[e.g. the SQL code reflecting the CPF5090 or similar] or the query
activity would be able to complete without an error such that the
problem would be circumvented.  If circumvented just once in that
fashion, likely the next invocation by the unauthorized user would
also complete without error, because the condition which gave rise
to the need to open the ERAP file no longer persists.

Regards, Chuck
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.