Fitzgerald & Long Sentry, Руководство пользователя

Страница: 64 / 113

Section 2 - 34 SENTRY User’s Guide
Fitzgerald & Long
2.5 COMMAND MAINTENANCE
This program is used to update protection of VOC items in uniVerse, PI/open and UniData accounts. It is
also a convenient means of reviewing the existing protection (created by SENTRY) which may be in effect.
COMMAND.MAINT Command Maintenance 08/08/00
Account Name : /usr/sentry.dev
VOC Command : PROC.TEST PROC
1. Description : Test program
2. Subroutine : *SENTRY.COMMAND.CONTROL
3. Other Rights : NONE
===================================================================
4. Users 5. Rights
01) 201 (bee) NONE
===================================================================
6. Groups 7. Rights
02) 9 (piadm) X
Enter field number, "F"ile, "DEL"ete or "<ESC>" to exit :
Figure 32 - This is an example of the “Command Maintenance” data entry screen which is used to set
protection on verbs, paragraphs, sentences, PROCs, and menus. Selection 5 on the “Database
Maintenance Menu” invokes this program.
Through the use of permissions, protection for directories and files may be satisfactorily implemented.
However, there are
processes which also need to be protected. It is usually appropriate for users to execute
programs in their application software which updates files. This type of update is acceptable and desirable.
Updating a file via the editor or deleting records at the database prompt are actions which you would
generally prefer users not perform.
SENTRY extends the concept of permissions protection to menus, verbs, PROCs, sentences, and
paragraphs. You may allow a user to use DELETE in an application program but disallow that usage at a
database prompt. You may protect the editor so that you, or perhaps the MIS group may use it but no
other user is allowed to.