Re: JDBC Connectivity -- MIDRANGE-L

Subject: Re: JDBC Connectivity
From: CRPence <crp@xxxxxxxxxxxxxxxxxxxx>
Date: Fri, 30 Nov 2007 14:24:24 -0600
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

If there is an authority failure, likely it is very simple. Turn on auditing for *AUTFAIL [and *SECURITY ?], reproduce the error scenario, and review the authority failure (T-AF) audit record. Grant the appropriate authority to the object that was identified, to the user that was not authorized. If granting that authority is suspect, then investigate for corrective fixes, associated with [by searching on] that user, job, and object.

Regards, Chuck

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.