Multiple HP ALLBASE/4GL Systems [ HP ALLBASE/4GL Developer Administration Manual ] MPE/iX 5.0 Documentation
HP ALLBASE/4GL Developer Administration Manual
Multiple HP ALLBASE/4GL Systems
One MPE/iX system can support a number of HP ALLBASE/4GL systems
simultaneously, and each HP ALLBASE/4GL system in turn can support a
number of users and applications. Typically, you might want to use
multiple HP ALLBASE/4GL environments if you are using the same MPE/iX
system for developing multiple applications.
If you need to use multiple HP ALLBASE/4GL environments on your MPE/iX
system, you don't need to create multiple copies of the entire HP
ALLBASE/4GL system. The only parts you need to duplicate are the HP
ALLBASE/4GL S-files. More than one HP ALLBASE/4GL developer environment
can share the same program files, message catalogs and terminal support
files.
Note that the program files and message catalogs are not the same for the
developer and run-time environments. A developer environment and a
run-time environment cannot share program files or message catalogs. The
terminal support files are identical for both the developer environment
and the run-time environment.
If you do use more than one set of HP ALLBASE/4GL S-files, they must be
in separate groups. The S-file groups can be in the same account, or in
different accounts.
When you use multiple S-file sets, the MPE/iX variable HP4SPATH must be
set correctly for each user. You will also need to set the HP4DATAPATH
variable, the HP4TIPATH variable, and the HP4SQLPATH variable for each
user, according to the S-file set being used.
The following table is an example showing the values of the MPE/iX
environment variables required to access the two HP ALLBASE/4GL
environments. This table assumes you have copied the HP ALLBASE/4GL
S-files to the HP4S groups in two accounts called HP4DEVEL and HP4TEST.
User Variable Typical Value
Developer HP4SPATH HP4S.HP4DEVEL
HP4DATAPATH DEVDATA.HP4DEVEL
HP4SQLPATH DEVSQL.HP4DEVEL
HP4TIPATH DEVTI.HP4DEVEL
Test user HP4SPATH HP4S.HP4TEST
HP4DATAPATH TESTDATA.HP4TEST
HP4SQLPATH TESTSQL.HP4TEST
HP4TIPATH TESTTI.HP4TEST
Run-Only Applications
If required, completed applications can be unloaded from the development
S-files and loaded into the test environment S-files as run-only
applications. This reduces disk usage since run-only applications do not
require the developer source information to be present. Unloading
applications in run-only form also ensures that they cannot be modified.
MPE/iX 5.0 Documentation