home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: Product
/
Product.zip
/
opusd10e.zip
/
OPUSADD.ZIP
/
OPUSZUG.HLP
(
.txt
)
< prev
next >
Wrap
OS/2 Help File
|
1995-09-11
|
20KB
|
698 lines
ΓòÉΓòÉΓòÉ 1. Program overview ΓòÉΓòÉΓòÉ
Using the OPUS User and Access Control program, a user with administrator
privilege can view or update an OPUS User Access File. aktualisieren. The User
Access File contains both users and their access privileges for the various
functions and data classes. The User Access File is encrypted and can be viewed
only with this program.
The OPUS User and Access Control program can also maintain access files other
than the main access file, which pertains to the OPUS data base. The
administrator can thus update a file without consideration for the fact that
the file is inaccessible to OPUS users during logon or logoff.
As for the main OPUS program, logon is required. The user must be registered in
the access file with administrator privilege. When delivered, the OPUS system
contains two user IDs: "Admin" and "OPUS", whereby the passwords are also
"Admin" and "OPUS", respectively. "Admin" has the required adminstrator
privilege. Following the first logon, the administrator should change the
password for "Admin".
Program functions
The major functions of the program can be divided into two groups:
o User maintenance
o Maintenance of access levels
User maintenance includes the creation, modificatiion, or deletion of user
entries. In addition to user ID and password, these entries contain the
assigned access level and his/her number in the OPUS Persons/Entities section
of the OPUS data base.
Maintenance of access levels includes the definition of access privileges for
various program functions and data classes depending on the user's function in
the respective project.
There are four access levels:
Administrator/Management
The access level Administrator/Management always has all privileges.
Secretary
The access level Secretary is intended for employees who carry out
administrative functions on behalf of management but who are not
considered to be project members.
Project manager
The access level Project manager includes employees who do or can
perform project management functions. A user with this access level
need not be the manager of every project he/she is assigned to.
He/she can also function simply as a normal project member. For the
access level Project manager there are 3 sets of access privileges,
depending on whether the user is the project manager, is assigned to
the project as a member, or is not assigned to the project.
Project member
The access level Project member applies to all other employees. There
are two access level sets in this case, depending on whether the user
is assigned to the project or not.
ΓòÉΓòÉΓòÉ 2. Main window ΓòÉΓòÉΓòÉ
Select a topic:
o Program overview
o File menu
o Maintenance menu
ΓòÉΓòÉΓòÉ 2.1. File menu ΓòÉΓòÉΓòÉ
This menu allows you to:
o open an access file
o save the current access file
o exit the program
Overview
Open Displays the Open Users File dialog for defining the
access file.
Save Saves the current access file
Exit The program is terminated.
ΓòÉΓòÉΓòÉ 2.1.1. File/Open menu itemn ΓòÉΓòÉΓòÉ
Select this menu item to define the name of an access file. The Open Users File
dialog appears.
ΓòÉΓòÉΓòÉ 2.1.2. File/Save menu item ΓòÉΓòÉΓòÉ
This menu item saves the currently open access file.
ΓòÉΓòÉΓòÉ 2.1.3. File/Exit menu item ΓòÉΓòÉΓòÉ
Select this menu item to exit the program. If the current access file has been
modified but not yet saved, you will be asked whether the file should be saved
before exiting.
ΓòÉΓòÉΓòÉ 2.2. Maintenance menu ΓòÉΓòÉΓòÉ
This menu supports the maintenance of user entries in the access file as well
as of the tables that define the access privileges.
Until an access file has been opened, this menu item is disabled.
Overview
Users Displays the OPUS User Maintenance dialog.
Access levels Displays the OPUS User Access Levels dialog.
ΓòÉΓòÉΓòÉ 2.2.1. Maintenance/Users menu item ΓòÉΓòÉΓòÉ
The OPUS User Maintenance dialog appears to allow you to view or change user
entries.
ΓòÉΓòÉΓòÉ 2.2.2. Maintenance/Access levels menu item ΓòÉΓòÉΓòÉ
The OPUS User Access Levels dialog is displayed to allow you to view or modify
the access levels, which contain the access privileges.
ΓòÉΓòÉΓòÉ 2.3. Help menu ΓòÉΓòÉΓòÉ
Select this menu to get information on using the OPUS User and Access Control
program or the OS/2 help system.
Overview
Help index Displays the help information index. for the OPUS User
and Access Control program.
Extended help Displays the program overview.
Help for help Explains how to use the help system.
Product information Displays the version number of the program.
ΓòÉΓòÉΓòÉ 2.3.1. Help/Help index menu item ΓòÉΓòÉΓòÉ
Displays the help information index. for the OPUS User and Access Control
program.
You can use the index as follows:
o Select a topic from the list, or
o Click on Search and enter a string.
ΓòÉΓòÉΓòÉ 2.3.2. Help/Extended help menu item ΓòÉΓòÉΓòÉ
This menu item shows general information about the OPUS User and Access Control
program.
ΓòÉΓòÉΓòÉ 2.3.3. Help/Help for help menu item ΓòÉΓòÉΓòÉ
This menu item explains how to use the help system.
ΓòÉΓòÉΓòÉ 2.3.4. Help/Product information menu point ΓòÉΓòÉΓòÉ
Using this menu item, you can determine the version number of the program.
ΓòÉΓòÉΓòÉ 3. Dialogs ΓòÉΓòÉΓòÉ
o OPUS User Logon
o Open Users File
o OPUS User Maintenance
o OPUS User Access Levels
ΓòÉΓòÉΓòÉ 3.1. OPUS User Logon ΓòÉΓòÉΓòÉ
The OPUS User Logon dialog is used to identify the user and to specify the
access file pertaining to the OPUS data base.
Fields
User ID OPUS user ID
Password The password associated with the ID
Data base directory Specifies the directory containing the access file to
be used to verify this logon. This field is present
only if the OPUS initialization file (OPUS.INI) does
not exist. If no entry is made, the access file is
expected to be in the current directory.
ΓòÉΓòÉΓòÉ 3.1.1. User ID ΓòÉΓòÉΓòÉ
This entry must match an entry in the access file specified via the Data base
directory field. The entry must have been assigned an access level of
Administrator.
ΓòÉΓòÉΓòÉ 3.1.2. Password ΓòÉΓòÉΓòÉ
A password is required only if it was defined for this user ID by the
administrator. If a password is not defined in the access file user entry, no
entry is permitted in this field.
ΓòÉΓòÉΓòÉ 3.1.3. Data base directory ΓòÉΓòÉΓòÉ
This field specifies the directory containing the OPUS data base, and therefore
the access file. This field is present only if the OPUS initialization file
(OPUS.INI) does not exist. If the user leaves this field blank, the access file
is expected to be in the current directory.
ΓòÉΓòÉΓòÉ 3.2. Open Users File ΓòÉΓòÉΓòÉ
The Open Users File dialog specifies the access file to be loaded. The default
(preset) value is the path and file name of the file used for logon. The entry
can be changed, however, to allow another access file to be opened. This option
can be utilized when it is desired not to interfere with the operational OPUS
environment. The main access file can first be copied, the copy updated, and
then copied back to the main file.
Fields
Access file Path and file name of the access file to be loaded.
ΓòÉΓòÉΓòÉ 3.2.1. Access file ΓòÉΓòÉΓòÉ
Path and file name of the access file to be loaded. This file can be different
from the one used for logon.
ΓòÉΓòÉΓòÉ 3.3. OPUS User Maintenance ΓòÉΓòÉΓòÉ
The OPUS User Maintenance dialog is used to view and maintain user entries in
the access file.
Fields
User ID OPUS user ID
Password The password corresonding to the user ID
PERSON No. Number of this user in the Persons/Entities section of
the OPUS data base.
Access level Access level assigned to this user
User logged on Indication that the user is currently using OPUS or
the OPUS User and Access Control program.
Buttons
Add Adds a user entry to the access file. The appropriate
information must have previously specified in the fields.
Delete Deletes the entry designated by the field User ID
Change Updates the user entry from the field contents. The user ID
can also be changed in this case.
Close Closes the dialog and returns to the main window.
ΓòÉΓòÉΓòÉ 3.3.1. User ID ΓòÉΓòÉΓòÉ
OPUS user identifier assigned by the administrator.
ΓòÉΓòÉΓòÉ 3.3.2. Password ΓòÉΓòÉΓòÉ
Entry of a password is optional. It may be entered only if the user entry
contains a password.???
ΓòÉΓòÉΓòÉ 3.3.3. PERSON No. ΓòÉΓòÉΓòÉ
Number of this user in the Persons/Entities section of the OPUS data base. This
number serves to identify the OPUS data pertaining to the user. It is shown in
the Update Employes bearbeiten dialog in the OPUS program.
ΓòÉΓòÉΓòÉ 3.3.4. Access level ΓòÉΓòÉΓòÉ
The access level to be used when this user logs on to the OPUS program.
ΓòÉΓòÉΓòÉ 3.3.5. User logged on ΓòÉΓòÉΓòÉ
A check mark means that the user may be using the OPUS program or the OPUS User
and Access Control program. If this is not the case, such as after a previous
OPUS session terminated abnormally or if the access file was busy at logoff
time, the user will be notified at the next logon that the user ID is already
active. By resetting the check mark, the "logged on" state is reset, and no
such message will occur.
ΓòÉΓòÉΓòÉ 3.4. OPUS User Access Levels ΓòÉΓòÉΓòÉ
The OPUS User Access Levels dialog allows you to view and possibly modify OPUS
access privileges.
The access privileges are defined internally in 6 sets, or tables. Each table
contains the access privileges for a specific combination of access level and
project function.
The individual tables cover the following cases. The term "current project"
means any project being displayed or defined:
o Secretary level
o Project manager level (user is the manager of the current project)
o Project manager level (user is only a member of the current project)
o Project manager level (user is not assigned to the current project)
o Project member level (user is assigned to the current project)
o Project member level (user is not assigned to the current project)
A specific table is selected when you select the appropriate combination of
access level and project function.
There is no table for the Admin level, since this level by definition has all
privileges.
Fields
Access level Designation of the access level
When the user is... Function of the user on the current project.
Access category Classification of the access objects
Access object a program function or data class subject to
access control
Access privileges for this object The type of access for this object
Buttons
Change Defines the privileges as indicated by the
current settings
Close Closes the dialog and returns to the main window.
ΓòÉΓòÉΓòÉ 3.4.1. Access levels ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ 3.4.1.1. Administrator ΓòÉΓòÉΓòÉ
Administrator
ΓòÉΓòÉΓòÉ 3.4.1.2. Secretary ΓòÉΓòÉΓòÉ
Secretary
ΓòÉΓòÉΓòÉ 3.4.1.3. Project manager ΓòÉΓòÉΓòÉ
Project manager
ΓòÉΓòÉΓòÉ 3.4.1.4. Project member ΓòÉΓòÉΓòÉ
Project member
ΓòÉΓòÉΓòÉ 3.4.2. User functions ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ 3.4.2.1. Member ΓòÉΓòÉΓòÉ
Project member
ΓòÉΓòÉΓòÉ 3.4.2.2. Not assigned ΓòÉΓòÉΓòÉ
The user is not assigned to the project.
ΓòÉΓòÉΓòÉ 3.4.2.3. Project manager ΓòÉΓòÉΓòÉ
Project manager
ΓòÉΓòÉΓòÉ 3.4.3. Access categories ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ 3.4.3.1. Functions ΓòÉΓòÉΓòÉ
This category includes the main functions, or modules, or the program.
ΓòÉΓòÉΓòÉ 3.4.3.2. System data ΓòÉΓòÉΓòÉ
This category includes data that is not specific to a particular person/entity
or project.
ΓòÉΓòÉΓòÉ 3.4.3.3. Person/Entity data ΓòÉΓòÉΓòÉ
This group includes data concerning persons and organizational entities.
ΓòÉΓòÉΓòÉ 3.4.3.4. Project data ΓòÉΓòÉΓòÉ
This group includes data concerning projects, task groups, and tasks.
ΓòÉΓòÉΓòÉ 3.4.3.5. Confidential data ΓòÉΓòÉΓòÉ
This group includes confidential data, usually of a financial nature.
ΓòÉΓòÉΓòÉ 3.4.4. Access object ΓòÉΓòÉΓòÉ
Program function or data class subject to access control. These objects are
fixed and cannot be changed.
For more information, see the help information for the OPUS program.
ΓòÉΓòÉΓòÉ 3.4.5. Access privileges ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ 3.4.5.1. None ΓòÉΓòÉΓòÉ
No access permitted to the object.
ΓòÉΓòÉΓòÉ 3.4.5.2. Available ΓòÉΓòÉΓòÉ
The function is available.
ΓòÉΓòÉΓòÉ 3.4.5.3. Delete/Add/Change ΓòÉΓòÉΓòÉ
Full access is permitted for the object.
ΓòÉΓòÉΓòÉ 3.4.5.4. Add/Change ΓòÉΓòÉΓòÉ
The object can be added or changed but not deleted.
ΓòÉΓòÉΓòÉ 3.4.5.5. Read only ΓòÉΓòÉΓòÉ
The object can be viewed but not changed.
ΓòÉΓòÉΓòÉ 3.4.5.6. Only own data ΓòÉΓòÉΓòÉ
Access to Person data or Time recording data is limited to that for the current
user.
ΓòÉΓòÉΓòÉ 3.4.5.7. Only project members ΓòÉΓòÉΓòÉ
Access to Person or Time recording data is limited to that for members of the
current project.
ΓòÉΓòÉΓòÉ <hidden> Message ΓòÉΓòÉΓòÉ
Explanation: The access file cannot be opened because it is currently being
accessed by another process.
Response: If repeated attempts are unsuccessful, you will have to terminate the
program in question.
ΓòÉΓòÉΓòÉ <hidden> Message ΓòÉΓòÉΓòÉ
Explanation: The specified file is not recognizable as an OPUS access file.
Response: Correct the entry, or restore the access file.
ΓòÉΓòÉΓòÉ <hidden> Message ΓòÉΓòÉΓòÉ
Explanation: Either the user ID or password does not match a user ID entry in
the access file.
Response: Ensure that the entry is correct. Slowly enter the password again. If
the user entry does not contain a password, an entry in the password field is
not permitted.
ΓòÉΓòÉΓòÉ <hidden> Message ΓòÉΓòÉΓòÉ
Explanation: The specified user ID is not assigned the access level
"Administrator".
Response: Use an appropriate ID.
ΓòÉΓòÉΓòÉ <hidden> Message ΓòÉΓòÉΓòÉ
Explanation: The access file does not exist in the specified directory.
Response: Correct the directory entry, or restore the access file.
ΓòÉΓòÉΓòÉ <hidden> Message ΓòÉΓòÉΓòÉ
Explanation: When the access file was delivered, a maximum number of users
(licenses) was defined. This number has been reached.
Response: Delete unneeded user entries, or obtain additional licenses.
ΓòÉΓòÉΓòÉ <hidden> Message ΓòÉΓòÉΓòÉ
Explanation: According to the user entry, the user ID already in use (active).
The licensing agreement prohibits one user ID from being used by more than one
user at the same time.
It may happen that there is actually no active OPUS session, for example after
a previous OPUS session terminated abnormally or the access file was busy at
logoff time.
Response: If there is indeed no other OPUS session using this ID, select "Yes".
ΓòÉΓòÉΓòÉ <hidden> Message ΓòÉΓòÉΓòÉ
Explanation: The format of the access file is not compatible with the program
version. This can be the fault of either the file or the program.
Response: Ensure that you are using the correct file and the correct program
version.
ΓòÉΓòÉΓòÉ <hidden> Message ΓòÉΓòÉΓòÉ
Explanation: The user ID "ADMIN" is a fixed element within the access file and
may not be deleted or changed.
ΓòÉΓòÉΓòÉ 4. Terms ΓòÉΓòÉΓòÉ
Click on a term:
Administrator
Current project
User logon
User function
Access level
User maintenance
User ID
Data base directory
Password
Object category
PERSON No.
Project members
Project manager
Project member
Secretary
Table
User access file
Access object
Access privileges
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
1. An OPUS user responsible for the maintenance of OPUS user entries and
access privileges.
2. The topmost access level
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
A project currently under examination by OPUS
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
Specification of a user ID and, if necessary, password at the beginning of the
OPUS User and Access Control program. On the basis of this logon information,
the program can determine whether the user is authorized to perform the
functions provided by the program.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
The function performed by the user on the current project. The following are
possible:
o the employee is the project manager
o the employee is assigned to the project
o the employee is not assigned to the project
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
A data structure containing access privilege information. There are 4 access
levels:
o Administrator/Management
o Secretary
o Project manager
o Project member
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
Changing, adding, oir deleting user entries in the access file
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
A 1-8 character entry that uniquely identifies an OPUS user.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
The pathname of the directory containing the OPUS data base and thereby the
user access file.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
A 1-8 character entry permitting confirmation that the entry of the user ID is
authorized.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
A grouping of logically related access objects.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
The unique number assigned to a person or entity in the OPUS data base. The
PERSON No. represents the link between the access file and the OPUS data base.
It enables OPUS to determine which person-related data apply to the current
user.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
A collective term for the project manager and the remaining project members
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
1. The project member with responsibility for the execution and schedule of
the project.
2. An access level for employees who could possible manage one or more
projects, although they need not manage all projects they are assigned to.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
A project member other than the project manager.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
An access level for employees who conduct administrative tasks on behalf of
management.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
A data structure in the access file that contains the access privileges for a
specific combination of access level and user function.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
A special file augmenting the OPUS data base that contains OPUS user entries
and the definitions of the access levels.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
A program function or data class subject to access control. The access objects
are fixed.
ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ
Indicators providing the privilege of the user to use a certain program
function or to access data of a certain class.