HP 3000 Manuals HP 3000 Manuals
User Access All HP ALLBASE/4GL user access to HP ALLBASE/SQL databases is controlled by the security provisions of HP ALLBASE/SQL, and is determined by the user's MPE/iX logon name. This logon name may not be the same as the user's HP ALLBASE/4GL name. The type of user access required for database users depends on the security requirements of the applications you are using. The access requirements for the various HP ALLBASE/4GL user types are summarized in the following paragraphs. System Administrator. The HP ALLBASE/4GL system administrator must be the database creator, or have database administrator authority (dba) for an application database. Developer Users. Developer users must have connect authority and resource authority for an application database. Without resource authority, developers cannot create tables or modules in the database environment. Developer users (as determined by the developer's MPE/iX login name rather than the developer's HP ALLBASE/4GL user name) must be members of the SQL owner group for the application. Application End Users. All application end users require connect authority for the application database. All application end users must have run authority for the module for the applications or versions they use. The module name is owner_group.name where owner_group is the SQL owner group for the application, and name is the name of the application or version. Application end users should not be members of the SQL owner group for the application. If they are members of this group, they will have authority to create, delete, or modify database tables and modules. Database Connect and Release HP ALLBASE/4GL connects to, and releases from, the application database environment automatically. In the developer environment, HP ALLBASE/4GL connects to the application database environment when a developer creates a table, deletes a table, generates a select list, or generates an SQL logic block. HP ALLBASE/4GL also connects to the application database in application testing mode when the user executes a command that requires database access. Once HP ALLBASE/4GL has connected to the application database, the connection is maintained for the duration of the HP ALLBASE/4GL session. In the run-time environment, HP ALLBASE/4GL connects to an application database automatically when the user executes a command that requires database access. HP ALLBASE/4GL then retains the connection to the database for the duration of the HP ALLBASE/4GL session. Multi-User Databases While an application is under development, the database environment for the application should be configured as a multi-user database. When a developer creates a table or generates an SQL logic block, HP ALLBASE/4GL connects to the database environment. This database connection is then maintained for the duration of the HP ALLBASE/4GL session. If the developer uses the application testing option, HP ALLBASE/4GL attempts to connect to the database a second time. This generates an error condition if the database is configured as a single user database. If required in the run-time environment, HP ALLBASE/4GL applications can use single-user databases.