HP 3000 Manuals

HP ALLBASE/4GL Developer Administration Manual

Application Unloading Screen 

This screen, which you can access from the Utilities option on the main
menu, allows you to write a complete application, and up to 10 versions
of the application, to a separate external file.  You can then write this
file to disk, tape or cartridge for transport to another HP ALLBASE/4GL
system, or create a backup copy of the application.

The application unloading process does not delete the application or
change it in any way.  Use the administrator deletions screen to delete
an application.

Screen Image 


            

Field Descriptions 

Application.  Enter the name of the application that you want to unload.

Versions.  Enter the names of the versions that you want to unload with
the application.  You cannot unload versions without unloading the base
application.


CAUTION  Under some circumstances, KSAM data files used by versions on
         the target system may be corrupted during subsequent application
         loading if you attempt to unload two or more versions with an
         application.

         Don't attempt to unload more than one version with an
         application if the versions use different formats for their data
         files.


Initial Release.  If you enter Y in this field, the system writes the
application and version definition records from the application and
version definitions screens to the external file.

If you enter N in this field, the definition records for the application
(and versions) are not written to the external file.


NOTE  You must enter Y in this field if you are unloading an application
      for first release to a run-only HP ALLBASE/4GL site.  The system
      administrator for the run-only site cannot create new application
      or version definitions.  The run-only site system administrator can
      only add or delete users for the application or version.


Unload Run-Only Copy.  Enter Y in this field to unload a run-only copy of
the application.  Enter N in this field if you want to include the
developer's source code with the unloaded application.

If you unload an application without the application source (that is, a
run-only copy of the application), the generated components of the
unloaded application cannot be modified, copied, or deleted.

If you enter Y in this field, HP ALLBASE/4GL displays a message asking if
you want to create a data file structure file.  If you enter Y in
response to the message, HP ALLBASE/4GL creates a file nameS in the group
and account identified by the HP4FSPATH variable, where name is the
application or version name.  This file contains the definition of the
data files used by the application or version you are unloading.  The
file contains the definitions for KSAM data files used by the base
application if you are unloading an application by itself.  The file
contains the definition for KSAM data files used by the version if you
are unloading a version with the base application.

Don't attempt to unload more than one version with the application if the
KSAM data files for the version require reformatting.

During the application loading process on the destination system, HP
ALLBASE/4GL uses the nameS file in conjunction with the existing
file-structure files for the application or version (in the group and
account identified by the HP4FSPATH variable) to reformat the data files.
Refer to Additional Information for more information about data file
reformatting.

External File Name.  Display-only field.  The display in this field
becomes the name of the base application you are unloading.  HP
ALLBASE/4GL creates the file in the the group and account identified by
the HP4APPNPATH variable.

Function Keys 

f1       Printing  Cancels the current screen and displays the
        administrator documentation screen.

f2       Deletes  Cancels the current screen and displays the
        administrator deletions screen.

f4       Load Applic.    Cancels the current screen and displays the
        application loading screen.

f6       Commit Data  Starts the application unloading process.

Additional Information 

The application unloading process writes the definition of an entire
application and up to ten versions to an application definition file in
the group and account identified by the current value of the HP4APPNPATH
variable.  The name of the application definition file is the name of the
base application you are unloading.

After you have unloaded the application, you can use the application
definition file for the following purposes:

   *   To transport the application to a different HP ALLBASE/4GL
       installation on the same system.

   *   To transport the application to a different HP ALLBASE/4GL system
       on a different system.

   *   To create a backup copy of the application on tape.

You can move an unloaded application to a different HP ALLBASE/4GL
installation on the same system.  (That is, an HP ALLBASE/4GL
installation contained in a set of S-files other than the S-files used to
develop the application.)  To do this, use the appropriate operating
system commands to move or copy the application definition file to the
group and account identified by the HP4APPNPATH variable for the
destination system.

To transport an application to an HP ALLBASE/4GL system on a different
system, or to create a backup copy of the application, you will need to
copy the application definition file to tape.

Application Generation.   

When you press the  Commit Data  function key, HP ALLBASE/4GL displays a
message asking if you want to generate the entire application.  Enter Y
to generate the entire application and any versions of the application
before calling the unloading routine.

If you enter N in response to the message, HP ALLBASE/4GL checks if the
application accesses an HP ALLBASE/SQL database.  If it does, HP
ALLBASE/4GL issues a further message asking if you want to generate all
SQL logic blocks in the application.  Enter Y to generate all SQL blocks
in the application and any versions of the application before calling the
unloading routine.

HP ALLBASE/SQL Applications.   

Any application that uses an HP ALLBASE/SQL database consists of a series
of records in the HP ALLBASE/4GL S-files, and a number of preprocessed
sections stored as a module in the database environment.  HP ALLBASE/4GL
creates one database module for a base application, and one module for
each version of the application.

HP ALLBASE/4GL also stores a copy of the database environment modules for
each application and version in the group and account identified by the
HP4DBMPATH variable.  The database module files have the same name as the
application or version.

To transport an application that uses HP ALLBASE/SQL to another site, you
must also copy the database module files for the application and each 
version of the application to tape.

Generating the application before it's unloaded ensures that the database
module files and the generated records for the application are
up-to-date.

HP TurboIMAGE/iX Applications.   

No extra procedures are necessary to unload applications that access one
or more HP TurboIMAGE/iX databases.

HP TurboIMAGE/iX Data Set Reformatting.   

HP ALLBASE/4GL has no facilities for reformatting HP TurboIMAGE/iX data
sets.

If you need to reformat an HP TurboIMAGE/iX data set to reflect changes
to field types or the structure of record layouts, you can use HP
TurboIMAGE DBchange/XL, if it exists on your system.  This tool allows
you to alter the security and structure of an HP TurboIMAGE/iX database
with ease.

Limitations.   

The application unloading process does not include the definitions of any
logic command synonyms or communication area synonyms in the unloaded
application.

Menu item security definitions included with unloaded applications will
not apply when the application is loaded into another HP ALLBASE/4GL
system.  If menu item security is required when the application is loaded
to a different HP ALLBASE/4GL system, the menu security must be redefined
when the application is loaded onto the destination system.

Run-Time Environment Data File Reformatting.     

HP ALLBASE/4GL provides a mechanism for automatically reformatting KSAM
data files for run-only applications.  A data file must be reformatted if
any field specifications have changes, or the structure of the default
record layout for the file has changed.

The automatic data file reformatting mechanism uses the file-structure
file (in the group and account identified by the variable HP4FSPATH) that
is created during the application unloading process, and the structure
files (nameS files) associated with each data file.  During the
application loading process, HP ALLBASE/4GL compares the information in
the file-structure file with the structure in the nameS file.  If the
data file structure has changed, HP ALLBASE/4GL reformats the file to
reflect the new structure.

When you unload a run-only copy of an application, HP ALLBASE/4GL
displays a message asking if you want to create the file-structure file.
Enter Y in response to the message if you want to create the
file-structure file so data files on the destination system are
reformatted.  You only need to enter Y in response to this message if you
are unloading an application to update an existing application on the
destination system, and the KSAM data file structures have changed.

HP ALLBASE/4GL then creates the application definition file for the
application.

If you don't need to reformat data files on the destination system, enter
N in response to the message.

Refer to Chapter 6  for more information about reformatting data
files.

Unloading Run-Time Environment Applications 

Since run-only HP ALLBASE/4GL systems cannot use the generate program in
the HP ALLBASE/4GL developer, all applications unloaded for release to
run-only sites must be generated.  The source code for generated
components is not required at the run-only site, and can be excluded from
the unloaded copy by entering Y in the Unload Run-Only Copy field.

Refer to Chapter 6  for more information about unloading applications
for run-time environments.

MPE/iX 5.0 Documentation