HP 3000 Manuals

HP ALLBASE/4GL Developer Administration Manual

Version Definition Screen 

This screen can be accessed from the Versions option on the main menu.
The version definition screen allows you to define the name, password,
and users for a version.  The screen also allows you to define the
development security code for the version.

A version is a set of additional parameters that operate in conjunction
with an application to modify the application to suit the needs of a
particular user or group of users.


NOTE  The base application must exist before you can define a version of
      an application.


Screen Image 


            

Field Descriptions 

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

You cannot use any of the following reserved application names as version
names:  administ, developr, HPlogo, hpqm, HPLIBnnn or ULIBnnn (where nnn
is the three-digit language identifier).

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


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


A version cannot have the same name as its base application, or any other
application or version on the system.

Version ID. This is a display-only field.  It displays an identification
number for the version.

Application.  The field becomes an input field if you have entered a new
version name in the Version field.  In this case, enter the name of the
application on which you want to base the version.  This application must
exist before you can define the version.

This field becomes a display-only field if you have entered an existing
version name in the Version field.  In this case, the field displays the
name of the base application of the version you have named.  You can't
change the application name in this case.

Current Password.  This field is only active if you have already defined
a password for the version.

If you want to change the existing password for a version, enter the
current password in this field.

New Password.  Optional.  Enter a password for the version.  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 for the version.  If you
don't reenter exactly the same password, HP ALLBASE/4GL displays an error
message, and returns the cursor to the New Password field


NOTE  The version password only applies to end users of the version.  If
      you define a password for a version, the end user must enter the
      password on the HP ALLBASE/4GL sign-on screen to access the
      version.  Developer users can access the version without entering
      the password.


Current Development Security Code.  This field is only active if you have
already defined a development security code for the version.  If you want
to change the existing development security code for a version, enter the
current development security code in this field.

New Development Security Code.  Enter a new development security code in
this field.  HP ALLBASE/4GL does not echo the code as you type it in.

The version development security code must start with an alphabetic
character and can contain up to eight characters.  Development security
codes can contain 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.

Valid Users/Groups.  Enter the name of each end user, or user group to be
allowed to access the version.  For a version under development, you must
include the name of the developers in the user list.

The end user names, user groups, and developer names must be defined on
the relevant user validation screen before you can enter the names here.
Enter *ALL to allow all users and developers access to the version.

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

Function Keys 

f1       Applic.  Defn  Cancels the current screen and displays the
        application 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 a version, the original
developer can ensure that secured items within the version can only be
modified by a developer who has signed on to the version under the
correct development security code.

When all the required fields on the appropriate developer screen have
been completed, the developer of the version 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 version without entering the
development security code.  Under these circumstances, the developer can
examine the secured components of the version, but cannot change them.

MPE/iX 5.0 Documentation