HP e3000 MPE/iX Release 6.0 System Software Maintenance Manual (30216-90272)

Appendix A 161
Manually Installed Products
Installing HP ALLBASE/4GL
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 usingHP4STOA 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 ISQL VALIDATE 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 orHP4BLDR, 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