|
>I exclude a user from a library. I then create a program that needs to >execute a program in that library. I wanted the user to have access only >through programs. I tried to do this by compiling the program with *owner >authority (the owner has *all authority to the library and objects in the >library). When I try to run the program using the excluded user I get an >error saying the user is not authorized to the library. What am I doing >wrong? Jose, In addition to the good answers sent by John Earl and Tom Liotta you received a few incorrect answers. Each time a user calls a program the user needs authority to the library of the program, the program itself, any objects (files, data areas, commands, other programs, etc.) used by the program as well as the libraries of all those objects. You did not say where the program the user calls resides. I assume that you placed it in a different library that the user has authority to. If that is the case, then the user will be allowed to call the first program, and that first program will be allowed to call the second program in the restricted library because the first programs owner is authorized to both the restricted library and the second program. If the second program has the use adopted authority (USEADPAUT) attribute set to *NO then the adopted authority of the first program will not be propagated down to the second program and would not be useable by that program to access any of the objects in the restricted library. This may be the cause of the error messages you see that says the user is not authorized to the restricted library. Note: Some system have the QUSEADPAUT (use adopted authority) system value set to cause programs created by most users to default to not using adopted authority that is propagated to them by their callers. Ed Fishel, edfishel@xxxxxxxxxx
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.