To complete the installation of HP ALLBASE/4GL some additional
steps must be performed.
You must complete these installation procedures on a terminal
other than the system console. You cannot run HP ALLBASE/4GL on
the system console.
First Time Install
To complete the installation of the HP ALLBASE/4GL Developer
system or the HP ALLBASE/4GL Run-Time system, perform the following
steps after updating the system with the CSLT.
Create the account in which you want to use HP ALLBASE/4GL. You
can select any name for the account, but HP recommends that you use
the names HP4GL for the HP ALLBASE/4GL Developer System and
HP4GLR for the HP ALLBASE/4GL Run-Time System.
Log on to the new account and execute the following command file:
Developer:
:HELLO MGR.HP4GL
:HP4BLD.HP4GL.SYS
or
Run-Time:
:HELLO MGR.HP4GLR
:HP4BLDR.HP4GLR.SYS
HP4BLD (or HP4BLDR)will create several groups
within the account. After the groups are created, the utility copies
several files from the SYS account into the newly created
groups.
Proceed to the section called "Install the Environment" and follow
the steps to complete the installation.
Upgrade Existing Systems
This section describes how to update HP ALLBASE/4GL systems.
Before attempting an update, you must understand the following precautionary
conditions.
Developer System:
If you are using the HP ALLBASE/4GL Developer system, you must
save your applications and system definitions using HP4STOA
before you upgrade to the new version of HP ALLBASE/4GL. Applications
and system definitions will be lost if they are not saved.
After upgrading the HP ALLBASE/4GL Developer system, you will be
instructed to reload your applications and system definitions. You
will also need to regenerate HP ALLBASE/4GL applications before any
of the applications can be run.
Before regeneration can occur, you may first need to migrate all
of your ALLBASE/SQL databases. Check with the ALLBASE/SQL
installation instructions to see if your databases need to be
migrated.
Run-Time System:
If you are using the Run-Time System, at the end of the upgrade
procedures you must reload your applications from the tape or files
supplied by your application supplier.
If any of your applications use ALLBASE/SQL, check the HP
ALLBASE/SQL installation instructions to see if your databases need
to be migrated. After the database migration completes, use the
ISQLVALIDATE command to recompile all of the
SQL-stored sections (including SQL Logic Blocks). Applications that
use HP ALLBASE/4GL need to be regenerated using the new version of
HP ALLBASE/4GL before they can be run. Contact your application
developer.
Developer Systems: Before Running AUTOINST
We recommend that you perform the steps described in this
section before running AUTOINST.
NOTE: The following steps save your HP ALLBASE/4GL applications so they
can be reloaded at the end of the upgrade. If you do not save your applications
before running HP4BLD or HP4BLDR, you will lose these
applications.
Use HP4STOA instead of the HPALLBASE/4GL Administrator unload facility
to save the applications. The HP4STOA utility must be invoked for each
application you created in the environment. Although HP4STOA is slower
than the unload facility, HP4STOA performs two functions that the
unload facility does not. HP4STOA preserves the menu security defined
for the application and extracts the system definitions including the
following:
User names and passwords
Menu item security definitions
System specifications
Logic command and communication area synonyms
Master titles
Once the upgrade is complete, each of the files created with HP4STOA
must be input to HP4ATOS. The applications need to be fully
regenerated before they can be run.
Refer to the HP ALLBASE/4GL Developer Reference Manual Volume 2 for
details on HP4STOA and HP4ATOS.
NOTE: The following steps assume that your HP ALLBASE/4GL account is
called HP4GL. If you used another name, substitute it for
HP4GL in these instructions.
Log on to the HP4GL account.
Set the HP4SPATH environment variable:
:SETVAR HP4SPATH "HP4S.HP4GL"
Use HP4STOA to extract each of your applications and the
system definitions.
The record size and number of records allocated in the BUILD
command is adequate for most cases. In some extreme case,
HP4STOA fails because the file limits (record size or number
of records allocated) are exceeded. If the limits are reached, purge
the file and rebuild it with a larger limit. Then, repeat the
HP4STOA command.
The following applications do not need to be extracted from the
environment because they are part of the base environment delivered
with the new version of HP ALLBASE/4GL.
administ
developr
example
HPLIB000
hpqm
sqldemo
tutorial
Use the following commands to create a new group and to copy any
existing HP ALLBASE/4GL system files from the current S-file group
to this new group. The S-file group is then purged so the updated
S-files can be copied into the HP4S group. The existing
S-files are saved in case you forget to save all your applications.
Complete the following steps after running AUTOINST and after saving
your ALLBASE/4GL applications. You will lose your HP ALLBASE/4GL applications
if the following steps are performed before you run AUTOINST or save
your HP ALLBASE/4GL applications.
Update the HP4GL account. You must be logged into the
HP4GL account.
:HP4BLD.HP4GL.SYS
HP4BLD creates several groups within the account. After
creating the groups, the utility copies several files from the
SYS account into the newly created groups.
Set the system variable HP4SPATH to point to the group
containing the HP ALLBASE/4GL S files.
Regenerate your applications by running ALLBASE/4GL; log in as the
developer for each application and use the GENERATE ALL
feature.
You may need to migrate all of your ALLBASE/SQL databases
before you can use HP ALLBASE/4GL to regenerate your applications.
Check with the ALLBASE/SQL installation instructions to see if your
databases need to be migrated.
Run-Time Systems: Before Running AUTOINST
When you update to the new ALLBASE/4GL system, all existing
administrator definitions for the system are overwritten by the
defaults provided by the new ALLBASE/4GL system. As a result, the
following definitions are lost during the update:
User names and passwords
Menu item security definitions
System specifications for date and decimal number format, the
currency float symbol, and the HP-UX environment
specifications
Logic command synonyms and communication area synonyms
Master titles
NOTE: You should perform the following step before running
AUTOINST. If you do not print your system definitions before running
HP4BLDR, you cannot recover any of the previously specified system
definitions.
Print the reports of these items using the administrator
documentation menu before you perform the update. It is not possible
to save this information in the Run-Time System.
Run-Time Systems: After Running AUTOINST
The following steps assume that your HP ALLBASE/4GL account is called
HP4GLR. If you used another name, substitute it for HP4GLR
in the following instructions.
Log on to the HP4GLR account.
The following commands create a new group and copy any existing
HP ALLBASE/4GL system files from the current S-file group to this new
group. The S-file group is then purged so the updated S files can be
copied into the HP4S group.
HP4BLDR creates several groups within the account. After
the groups are created, the utility copies several files from the
SYS account into the newly created groups.
Reenter your system definitions using the printout created before
AUTOINST.
:HP4GLR
Reload your HP ALLBASE/4GL applications from the tape or files
supplied by your HP ALLBASE/4GL application supplier. For full
instructions on loading applications, refer to the HP ALLBASE/4GL
Run-Time Administration Manual.
If you are upgrading the HP ALLBASE/4GL Run-Time System and your
applications use HP ALLBASE/SQL, check with the HP ALLBASE/SQL
installation instructions to see if your databases need to be
migrated.
Use the ISQL VALIDATE command to recompile all of the
SQL-stored sections (including SQL logic blocks). You'll need to use
the VALIDATE command on each of your ALLBASE/SQL databases.
Both the modules and procedures need to be validated.
Following is an example of using VALIDATE:
:ISQL
isql> CONNECT TO 'DBEnvironmentName';
isql> VALIDATE ALL MODULES;
isql> VALIDATE ALL PROCEDURES:
Applications that use HP ALLBASE/4GL need to be regenerated
using the new version of HP ALLBASE/4GL before they can be run.
Contact your application developer.
Install the Environment
The default HP ALLBASE/4GL installation assumes that the MPE/iX system is
configured to support the American version as well as the native computer
language.
To run HP ALLBASE/4GL on a terminal that supports the line-drawing
character set, set the MPE/iX variable HP4TERM as follows:
:SETVARHP4TERM "HPL"
Refer to the HP ALLBASE/4GL Developer Administration
Manual or the HP ALLBASE/4GL Run-Time Administration
Manual for further information on setting up the HP
ALLBASE/4GL environment.