HP 3000 Manuals HP 3000 Manuals
Portability Mechanism In general, applications are portable across the operating systems that support HP ALLBASE/4GL. To transport an application from one operating system to another, you must unload the application from the source system and copy the required files onto the target file system. You can then use the HP ALLBASE/4GL application loading utility to load the application into the target system. The files involved in transporting applications are: * The unloaded application file. * The database module files. * The data file-structure file. The names for these files are shown in the following table. ----------------------------------------------------------------------------- | | | | | File Type | Operating System | File Name | | | | | ----------------------------------------------------------------------------- | | | | | Application | HP-UX | $HP4SPATH/name.uld | | Definition File | MPE/iX | NAME.!HP4APPNPATH | | | | | ----------------------------------------------------------------------------- | | | | | Database Module File | HP-UX | $HP4SPATH/name.dbm | | | MPE/iX | NAME.!HP4DBMPATH | | | | | ----------------------------------------------------------------------------- | | | | | File Structure File | HP-UX | $HP4SPATH/name.ufs | | | MPE/iX | NAME.!HP4FSPATH | | | | | ----------------------------------------------------------------------------- Application Definition File The administrator application unloading utility unloads the definition of an application (and up to 10 versions of the application) into a single application definition file. The application definition file can contain the developer source code, or can contain a run-only application. The application source code is not required to transport run-only applications between operating systems. An application definition file created on one operating system can be loaded into an HP ALLBASE/4GL system running under a different operating system provided you observe the precautions that are outlined in the following paragraphs. Under the MPE/iX operating system, the application definition file must be a variable length ASCII file with a maximum record length of at least 1 kilobyte. When shipping an application definition file from HP-UX to MPE/iX, the file can be shipped as a fixed length record binary file. Under the MPE/iX operating system, HP ALLBASE/4GL uses the current value of the variable HP4APPNPATH to determine the name of the group and account used for application definition files. Under the HP-UX operating system, HP ALLBASE/4GL creates or reads application definition files in the directory containing the HP ALLBASE/4GL S-files. Refer to chapter 12 for more information about application definition files. Database Module Files A database module file contains the definition of the stored module for an application or a version. HP ALLBASE/4GL creates a database module file when you generate either an entire application, or the SQL logic blocks in an application or version that uses HP ALLBASE/SQL. HP ALLBASE/4GL creates one database module file for an application, and one for each version of the application. A database module file is not required for an application that does not access an HPs database. The HP ALLBASE/4GL application loading utility automatically installs the database module in the application database environment during the application loading procedure. The database module files are portable between the HP-UX operating system and the MPE/iX operating system. Under the MPE/iX operating system, the database module file must be a fixed length binary file with a record length of 500 bytes. Under the MPE/iX operating system, HP ALLBASE/4GL uses the current value of the variable HP4DBMPATH to determine the name of the group and account used for database module files. Under the HP-UX operating system, HP ALLBASE/4GL creates or reads database module files in the directory containing the HP ALLBASE/4GL S-files. Refer to the HP ALLBASE/4GL Developer Administration Manual for more information about database module files. File Structure File The file structure file is only required if you are porting run-only applications that access KSAM or KSAM data files, and the files need to be reformatted to reflect changes to the record layouts. This file is not required for applications that use HP ALLBASE/SQL databases or HP TurboIMAGE/XL databases. HP ALLBASE/4GL builds a file structure file during the unloading process for a run-only application. During the application loading process, HP ALLBASE/4GL uses the file structure file to reformat the application data files if required. Under the MPE/iX operating system, the file structure file must be a fixed length binary file with a maximum record length of at least 8 kilobytes. Under the MPE/iX operating system, HP ALLBASE/4GL uses the current value of the variable HP4FSPATH to determine the name of the group and account used for file structure files. Under the HP-UX operating system, HP ALLBASE/4GL creates or reads file structure files in the directory containing the HP ALLBASE/4GL S-files. Refer to the HP ALLBASE/4GL Developer Administration Manual for more information about run-time application data file reformatting.