HP 3000 Manuals

HP ALLBASE/4GL Developer Administration Manual

Application Definition Screen 

This screen allows you to define the name of an application, its
password, development security code, and its valid developers, users, and
user groups.  This screen can be accessed from the Applications option on
the main menu.

Screen Image 


            

Field Descriptions 

Application.  Enter the name used to identify the application.
Application names must start with an alphabetic character, and can have
up to eight characters.  The application name can use the characters A to
Z, and 0 to 9.  The application name must be unique.

You cannot use the names administ or developr as application names.

The application name HPlogo is reserved for storing HP ALLBASE/4GL
sign-on screen logo windows.  The application names HPLIBnnn and ULIBnnn 
(where nnn is the three digit language identifier) are reserved for
storing module builder templates.  The name hpqm is also reserved.  If HP
ALLBASE/QUERY is installed on the system, this application allows direct
access to HP ALLBASE/QUERY. You may alter the definitions of these
reserved applications, but do not use these names for new applications.

HP ALLBASE/4GL uses the application name as the name for files that are
created during the application unloading process and the application
generation process.  The application name must be a legal MPE/iX file
name.


NOTE  HP ALLBASE/4GL is case sensitive with respect to application names
      even though MPE/iX file names are not case sensitive.  This means
      that you must be careful about your choice of application names.
      For example, HP ALLBASE/4GL regards the two applications Accounts 
      and ACCOUNTS as distinct.  However, the files generated during the
      application unloading process and the application generation
      process all have the name ACCOUNTS.


Current Password.  This field is not active unless you have already
defined a password for the application.

If you have already defined a password for the application, this field
becomes an active input field.  You must enter the existing password into
this field before you can change the password.  HP ALLBASE/4GL does not
echo the password to the screen as you type it in.

New Password.  Optional.  If you are defining a password for the
application or changing the existing password, this field becomes an
active input field.  Enter the new password into this field.  Passwords
must start with an alphabetic character and can have up to eight
characters.  Passwords can contain alphabetic characters, 0 to 9, and _
(underscore).  HP ALLBASE/4GL is case sensitive with respect to
passwords.

HP ALLBASE/4GL does not echo the password on the screen as you type it
in.

Repeat New Password.  Reenter the new password in this field.  You must
reenter exactly the same password, or HP ALLBASE/4GL displays an error
message and returns the cursor to the New Password field.


NOTE  The password defined in the above group of fields only applies to
      end users for the application.  If you define a password for an
      application, end users must enter the password on the HP
      ALLBASE/4GL sign-on screen to access the application.  Developer
      users can access the application without entering the application
      password.


Current Development Security Code.  This field is not active unless you
have already defined a development security code for the application.  To
change an existing development security code for an application, enter
the current code in this field.

New Development Security Code.  If you are defining a development
security code for a new application or changing the development security
code for an existing application, enter the new code in this field.  HP
ALLBASE/4GL does not echo the code as you type it in.

A development security code must start with an alphabetic character and
can contain up to eight characters.  Development security codes can use
alphabetic characters, 0 to 9, and _ (underscore).  HP ALLBASE/4GL is
case sensitive with respect to development security codes.

Repeat New Security Code.  Reenter the new development security code in
this field.  If you don't enter exactly the same code as you entered in
the field above, HP ALLBASE/4GL displays an error message, and returns
the cursor to the New Development Security Code field.

Initial Action Name.  Enter the name of the first action executed within
the application.

Type.  Enter M if the first action in the application is a menu.  Enter P
if the first action is a process.

SQL Owner Group.  Enter the name of the SQL owner group for the
application.  HP ALLBASE/4GL converts this name to uppercase characters
as you enter it.

HP ALLBASE/4GL automatically transfers ownership of all tables and
modules created from within HP ALLBASE/4GL to this owner group.

Don't attempt to change the SQL owner group name for an application after
development has commenced.  If you do, you may invalidate database
modules containing stored sections for the application.

SQL Database Name.  Enter the external name (and optionally the group and
account name) for the SQL DBECon file for the data base environment for
the application. 

You can specify a fully qualified file name in the form
FILE.GROUP.ACCOUNT, or simply specify a DBECon file name.  If you don't
specify a fully qualified DBECon file name, HP ALLBASE/4GL appends the
current values of the HP4SQLPATH variable to the file name you specify.

The database environment must exist, and must contain at least one DBE
fileset and at least one DBE file before the application can be
developed.

Valid Users/Groups.  Enter the names of the developers, end users, or
user groups to be allowed to access the application.  For an application
under development, you must include the developer's name in this list.

These names must be defined on the relevant user validation screens
before you can enter them on this screen.  Alternatively, enter *ALL to
allow all developers and end users to access the application.

Description.  These are documentation fields.  Enter a description of the
application.  HP ALLBASE/4GL automatically records the time and date of
the last modification.

Function Keys 

f1       Version Defn  Cancels the current screen and displays the
        version definition screen.

f2       Utility Menu  Cancels the current screen and displays the
        administrator utilities menu.

f3       User Menu  Cancels the current screen and displays the user
        validation menu.

f4       System Menu  Cancels the current screen and displays the
        system-wide specifications menu.

Additional Information 

If you assign a development security code to an application, the original
developer can ensure that secured items within the application can only
be modified by a developer who has signed on to the application under the
correct development security code.

When all the required fields on the appropriate developer screen have
been completed, the developer of the application can secure items by
setting the secured field for the items to Y. Refer to the HP ALLBASE/4GL
Developer Reference Manual for details of the items that can be secured.

A developer can still sign on to the application without entering the
development security code.  Under these circumstances, the developer can
examine the secured components of the application, but cannot change
them.

HP ALLBASE/SQL Databases 

Database Security.     

All user access to HP ALLBASE/SQL database environments is controlled by
the security provisions defined in HP ALLBASE/SQL.

All application developers require RESOURCE and CONNECT authority for the
database environment.  Developer users must be members of the SQL owner
group shown on this screen.

Application end users must have CONNECT authority for the database
environment and must also have RUN authority for the module used by the
application.  Application end users should not be members of the SQL
owner group shown on this screen.

Multi-User Databases.     

During application development, HP ALLBASE/SQL databases should be
configured as multi-user databases.

HP ALLBASE/4GL connects to the database when a developer creates or
deletes HP ALLBASE/SQL tables.  HP ALLBASE/4GL also connects to the
database when a developer generates an SQL logic block or generates an
entire application.

Once HP ALLBASE/4GL connects to a database from the developer
environment, the connection is maintained for the remainder of the
session.  If a developer attempts to run an application using the
Application Testing option in the developer environment, HP ALLBASE/4GL
attempts to create a second connection to the database.  This connection
cannot succeed if the database for the application is a single user
database.

HP TurboIMAGE/iX Databases 

If an application accesses any HP TurboIMAGE/iX databases, you must
define the database on the database definition screen, and grant the
application access to the database on the parameters for database access
screen.  Both of these tasks must be done before the application can use
an HP TurboIMAGE/iX database.

MPE/iX 5.0 Documentation