During installation, the supplied software is brought to the target system (depot location) from the distribution medium or the park ID. The depot locations provided can be customized to the configuration of the customer’s system. During this process the release units and the release items they contain are converted to installation units and installation items and installed in the target system.
The SOLIS2 delivery and the Software Configuration Inventory (SCI) must be open. If an SCI was not explicitly opened, IMON implicitly uses the standard SCI of the home pubset.
There are two different installation types for BS2000 software:
Default installation
With this type of installation, the entire delivery is stored on the home pubset or on an imported pubset under the user ID specified by Fujitsu Technology Solutions. Installation on the home pubset is the installation variant most frequently used.
Customer-specific installation
The following are examples of customer-specific installations: installations under different user IDs; installations where the software is first parked; multiple installations from a park ID or from software which is already installed.
The first time installation and migration of the operating system are described in the manuals “Migration Guide” [6 (Related publications )] and “System Installation” [5 (Related publications )].
Information on installing private software is given in the section "Structure and Installation Information file (SYSSII file)".
The installation process is initiated by the IMON function “Edit: Install” or the INSTALL-UNITS statement. It is divided into two stages:
| Installation preparation Actual installation process |
The result of the installation preparation stage is the generation of a procedure that also contains the special features of the delivery and the customer-specific requirements.
Execution of this procedure then initiates the actual installation process. The delivery documentation is stored in a library. This library is assigned the following name: $<work file ID>.<package name>.<customer ID>.DOC
Installation procedures can be started selectively.
Software which is parked or already installed can be multiply installed if the erasing of the files is prevented by park and working file recognition.
Supplementary information on overwriting existing installation items, on what to do if the user ID conflicts, on deleting installation files that are no longer required, and on activating special installation items can also be entered.
Optional and special installation functions can be controlled and automated (if desired) using a customer-specific IMON parameter file (see section "IMON parameter files").
IMON reads the structural format of the supply units from the product movement file. IMON extracts the release items of the processed supply units from the distribution medium and stores them in the target system as installation items. The file attributes and the path names (file names) of the installation items are formed in accordance with specific rules (see "Path name, logical ID and type of an installation item ").