RE: Authority Collection -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: RE: Authority Collection
From: Rob Berendt <rob@xxxxxxxxx>
Date: Wed, 27 May 2020 20:50:51 +0000
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Ok, I've ran the authority collection tasks for one user who probably meets the BI class of user.
I'm running the SQL against the Authority_collection view.

IDK why it took me so long but I think that the first target I need to focus on to ensure that items do not break when I switch to the "application access only" model is to ensure that the jobs are adopting the right authority. To do this I focus on the CURRENT_ADOPTED_AUTHORITY column.
I believe that if I focus on the rows where this column is null I can get a bunch of the problems resolved.

Rob Berendt

This mailing list archive is Copyright 1997-2026 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.