INSTALL

The INSTALL command stores the modules contained in an installable module file into a DBEnvironment.

Scope

ISQL only.

ISQL Syntax

IN [STALL] FileName [DROP] [ IN DBEFileSetName ] [ NO OPTINFO ]

Parameters

FileName

identifies the file containing the installable module. When first created by an ALLBASE/SQL preprocessor, the file is named SQLMOD. Name qualification follows MPE/iX conventions:

   FileName[/Lockword][.Group[.Account]]

DROP

specifies that an existing module with the same name as the module to be installed will be dropped. The default is not to drop an existing module.

IN DBEFileSetName

specifies a DBEFileSet where the modules are to be installed.

NO OPTINFO

indicates that the access plan optimization information (generated by SETOPT) is not to be installed into the DBE. The system generated access plan information will be used instead.

Description

In prompting mode, ISQL prompts you for an option. For example:
isql=> INSTALL; File name> FileName;
You must establish a DBE session with the CONNECT or START DBE command before using the INSTALL command.
After installation of the module is complete, the following message appears if AUTOCOMMIT is off:
Number of sections installed: n COMMIT WORK to save to DBEnvironment.
If AUTOCOMMIT is on, ISQL processes a COMMIT WORK after the module is installed, and the following message appears:
Number of sections installed: n DBEnvironment has been updated.
Before installing a module, ALLBASE/SQL determines the validity of each section in the module based on current DBEnvironment objects and authorization. A section is marked invalid, but stored, if it is for a statement that accesses an object that does not exist or that the module owner is not authorized to execute. You can use the VALIDATE statement to revalidate invalid sections or you can let ALLBASE/SQL revalidate sections when you run the program.
If a module by the same OwnerName.ModuleName already exists in the target DBEnvironment, the module is not installed unless the DROP option is specified.
You can determine the names of the modules in a module installation file by using the ISQL LIST INSTALL command.
A module stored in the DBEnvironment by a preprocessor, or a module installed in ISQL, should never be executed directly from ISQL by typing the name of the module. The module should be executed by running the executable program file.
A module installation file may contain more than one module. However, the preprocessors insert only a single module into each module installation file. If you want to install several modules from the same file, you must first concatenate the separate module installation files. The following example concatenates MOD1 and MOD2 into MODALL, which can then be used for the installation:
:FILE MODALL;DISC=5000,10,1;REC=250,,F,BINARY;ACC=APPEND :FCOPY FROM=MOD1;TO=*MODALL;NEW :FCOPY FROM=MOD2;TO=*MODALL :RESET MODALL
Refer to one of the ALLBASE/SQL application programming guides for information on preprocessors, modules, and using SQL in application programs.

Authorization

You must have the authority to start a DBE session in the target DBEnvironment.

Example

   isql=> INSTALL;



   File name> SQLMOD;

   Name of module in this file:  PGMR1@ACCT3.PROGRAM1

   Number of sections installed:  1



   Total number of sections installed:  1

   COMMIT WORK to save to DBEnvironment.



   isql=>