HP e3000 MPE/iX Release 6.5 System Software Maintenance Manual (30216-90325)
190 AppendixA
Manually Installed Products
Installing HP ALLBASE/4GL
• 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 runningHP4BLDR, you cannot recover any
of the previously specified system definitions.
1. 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.
1. Log on to the HP4GLR account.
2. 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.
:NEWGROUP HP4OLDSR
:HP4SCOPY.HP4GL.SYS HP4SR HP4OLDSR
:PURGEGROUP HP4SR
3. Execute the following command:
:HP4BLDR.HP4GLR.SYS
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.
4. Reenter your system definitions using the printout created before AUTOINST.
:HP4GLR
5. 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.
6. 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.
7. 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.