×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Paul Nelson wrote:
Is there any way through standard OS means to obtain field level
security? For example, if I give Jane Doe the ability to create a
query over the employee master file, is there a way to let her see
everything except the salary field?
This is a V5R4 system. Does V6 have this feature?
To establish field level security that prevents the ability of a user
to view data from a field, create a logical file which does not include
that field. Then grant both the data read right [*READ] and the object
operational right [*OBJOPR] to user JANEDOE to the logical view, and
then both revoke *OBJOPR right to user JANEDOE and grant *READ right to
user JANEDOE to the physical file. In that manner the user JANEDOE will
be able to query the logical view of the data, yet have no access to the
the physical file.
<code>
create table pnelson.limited ( public char, private char )
-- sql naming establishes that *public will have *exclude
create view pnelson.limitedvw as (
select public from pnelson.limited
) -- expose only the data from column /public/
grtobjaut pnelson/limited *file janedoe aut(*read)
grtobjaut pnelson/limitedvw *file janedoe aut(*objopr *read)
</code>
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.