HP 3000 Manuals HP 3000 Manuals
Unloading Procedure To unload an application, you must display the application unloading screen by selecting the Unload Application option on the utilities menu. Enter the name of the application you want to unload in the Application field and enter the names of any versions you want to unload with the application in the Versions fields. Don't attempt to unload more than one version of an application if the versions use different format data files. If you do unload more than one version with a base application, and the versions use different data file formats, data file corruption may occur when the application and versions are loaded to the destination system. Initial Release The entry in the Initial Release field determines whether the application (and version) definition records from the application (and version) header screens are unloaded with the application. These records contain the application password definition and the names of the authorized users for the application. Normally, you would enter Y in this field if you are unloading an application for first release to another HP ALLBASE/4GL system. You must enter Y in this field if you are unloading an application for first release to an HP ALLBASE/4GL run-time environment. The run-time environment administrator cannot create new application definitions. In general, you should enter N in this field if you are unloading an application for subsequent release to a run-time environment. In this case, the existing application definition, which includes the user names and password definition for the application, is not overwritten. Even if you do enter N in this field, you can load the application into a different HP ALLBASE/4GL developer environment that does not contain a definition record for the application. However, you must complete the application definition screen, and enter the list of valid users for the application. Under these conditions, the Secured field on all components in the application will be set to Y. To develop the application, the developer must set the Secured field to N, and then commit the definition of the component before it can be modified. Run-Only Copy Enter Y in this field if you do not want to include the application source code with the unloaded application. Enter N in this field if you do want to include the application source code. The unloaded application can be loaded into a different HP ALLBASE/4GL developer environment or an HP ALLBASE/4GL run-time environment regardless of your entry in this field. The presence or absence of the application source code does not make any difference to the execution of the application in an HP ALLBASE/4GL run-time environment. However, the generated components of an application unloaded without the source information cannot be modified even if the application is loaded into an HP ALLBASE/4GL developer environment. In general, you should not include the application source code in applications released to HP ALLBASE/4GL run-time environments. The source code is not required to run the application and its presence will waste disk space. Application Generation When you complete your entries on the application unloading screen and press the Commit Data function key, HP ALLBASE/4GL displays a message asking if you want to generate the entire application. If you enter Y in response to this message, HP ALLBASE/4GL generates the entire application. If you enter N in response to the message, HP ALLBASE/4GL checks whether the application uses an HP ALLBASE/SQL database. If the application does use HP ALLBASE/SQL, HP ALLBASE/4GL asks you if you want to generate the SQL logic blocks in the application. In general, it's best to generate the entire application before you unload it so you can be sure that all generated components in the unloaded application are up to date. If the application uses an HP ALLBASE/SQL database, HP ALLBASE/4GL creates the database module files for the application (and versions) you are unloading. These files contain the definitions for the database module for the application (and version) and the definition for the tables used by the application (and version). If you don't generate the application, or at least the SQL logic blocks in an application before you unload it, the database module files may not exist, or may not be up to date. If errors occur during generation of an SQL logic block, the database module files are deleted at the end of the unloading procedure so that the application cannot be loaded with incorrect SQL logic blocks. If an SQL table definition contains inconsistencies (such as the name of a record layout name that has since been deleted), an error message will be displayed, and no database module files will be created. When the generate process finishes, HP ALLBASE/4GL displays a message asking if you want to continue with the unload. If you enter Y in response to the message, HP ALLBASE/4GL unloads the application into the external file. If you enter N, the unload process terminates. File-Structure File If you are unloading a run-only copy of an application, HP ALLBASE/4GL initially displays a message asking you if you want to create the file-structure file for the application. If you enter Y in response to this message, HP HP ALLBASE/4GL builds a file NAME in the group and account identified by the variable HP4FSPATH and NAME is the name of the application you are unloading. The HP4FSPATH variable must be set before you execute the unloading process. This file contains the details of the structure of the data files for the application. HP ALLBASE/4GL then creates the application definition file for the application. You must enter Y in response to this message if you are unloading an application for release to an HP ALLBASE/4GL run-time environment to update an existing application where the existing KSAM data files must be reformatted. All KSAM data files for the application stored under the group and account identified by the variable HP4DATAPATH on the target system that have structure files present are reformatted if the file-structure file is present during the application loading process. Enter N in response to the message if you do not require the file-structure file. Unloading Applications for Run-Time Environments Since HP ALLBASE/4GL run-time environments cannot use the generate program in the HP ALLBASE/4GL developer, all applications unloaded for release to run-time environments must be generated. The source code for generated components is not required to run the application, and can be excluded from the unloaded copy by entering Y in the Unload Run-Only Copy field. In addition, run-time environments do not have the ability to create KSAM data files. To install an application on a run-time environment, any KSAM data files required by the application must be installed on the destination system. Once installed, the run-time environment maintains the KSAM data files. The KSAM data files on the run-time environment must be copied onto the system from tape. The files can be empty, or they can contain data that was entered on the development system. If you unload an application to update an existing application in an HP ALLBASE/4GL run-time environment, you may need to provide a file-structure file to reformat existing KSAM data files. This is only necessary if the structure of the data files has changed. If the application uses HP ALLBASE/SQL, the database environment should exist on the target system. When the application is loaded onto the system, the load procedure uses the appropriate database module files to create the HP ALLBASE/SQL tables required in the DBEnvironment. If the database environment does not exist, HP ALLBASE/4GL will not be able to connect to the database. Under these conditions, HP ALLBASE/4GL displays a message to allow entry of a different database environment name. If the application uses HP TurboIMAGE/iX, the database management system should exist on the target system. The run-time environment application installation procedure assumes that the release tape for the application contains all of the files mentioned below. The run-time environment system administrator needs to know the names of these files and the names of the groups and accounts containing these files to load the application to the run-time environment.
NOTE The run-time environment S-files are not the same as the developer environment S-files. You should not include any S-files on release tapes.
To transport an application to an HP ALLBASE/4GL run-time environment, the distribution media must contain the following files: * Application Definition File - NAME.!HP4APPNPATH Where NAME is the name of the application. * Database Module Files (HP ALLBASE/SQL applications) - NAME.!HP4DBMPATH Where NAME is the name of the application. If you are also unloading one or more versions with the application, you must include the database module file for each version as well. * HP TurboIMAGE/iX Database Files - NAME.!HP4TIPATH Where NAME is the name of the database root file. * KSAM Data Files (Initial application installation) - fileK.!HP4DATAPATH - file.!HP4DATAPATH - fileS.!HP4DATAPATH Where file is the MPE/iX name of the application data file. You must include the key file, data file, and structure file for each KSAM data file. * File-structure file (For update of an existing application.) - NAME.!HP4FSPATH Where NAME is the name of the application. You may need to obtain a list of the names of data files used by the application from the application developer.