The following steps are part of the installation preparations:
Selecting the products to be installed from the delivery set
Carrying out system-specific adaptations (customizing)
placement – specification of the depot location of the files to be installed
activation – preparation for activation of the software to be installed
Controlling installation functions using the IMON parameter files
Checking the software configuraton on the basis of the reference files
Generating the procedure
You select the supply units to be installed when calling the installation function from IMON.
IMON together use the other specifications relating to the target system, the depot location for files, and activation of the software to be installed to generate a procedure containing all of the process steps needed to install the selected supply units.
1. Selecting the products to be installed from the delivery set
When you open a delivery (menu mode: File:Open:SOLIS2 delivery; SDF statement:
INSTALL-UNITS), you specify whether the delivery should be fetched from the distribution medium itself or from the SCI.
If the delivery was already opened, it is registered in the SCI and can be opened via the “Registered delivery” option (in the File:Open:SOLIS2 delivery:Registered menu or using the SDF statement INSTALL-UNITS ...,DISTRIBUTION=*REGISTERED-MEDIUM).
If a number of deliveries are affected, they are installed in the order in which they were created. The order is taken from the package names of the individual deliveries. The files in a supply unit are installed together.
IMON will offer a complete or partial installation depending on the selection made when opening the delivery:
Complete installation
All supply units contained in the delivery are offered by IMON for installation. If a supply unit from this delivery was already registered in the SCI, IMON outputs an appropriate warning when the data volume is opened.
Partial installation
In this case, only those supply units that were not installed are offered for selection (e.g. when opening a delivery that is already registered and partially installed).
PLAM libraries can be used directly as an input medium for installing software (in the menu: File:Open:SOLIS2 delivery:Library and Edit:Install or using the SDF statement INSTALL-UNITS ...,DISTRIBUTION-MEDIUM=*LIBRARY).
2. System-specific adaptations (customizing)
System-specific adaptations can be made once the set of supply units to be installed has been defined. Global and local installation parameters can be specified for this purpose.
Global parameters apply to all selected supply units, whereas local parameters apply only to specific supply units.
Placement – specifying the definitive depot location
The depot location of the files (installation location) is defined by specifying a catalog ID, and/or user ID, and/or a prefix.
Fujitsu Technology Solutions specifies a default depot location for each supply unit. If a default installation is carried out, the installation items are installed in these predefined depot locations (see "Placement and activation in the default installation "). To install to these predefined depot locations, it is enough
to simply leave unchanged the default value 1 of the “Placement mode” in the “Global installation parameters” dialog box in menu mode or the *STD default of the PLACEMENT-MODE operand in the SDF statement INSTALL-UNITS.
However user-specific depot locations can also be selected. To do this, the value 2 is assigned to the “Placement mode” option of the “Global installation parameters” dialog box in menu mode. When working with SDF statements, INSTALL-UNITS ..., PLACEMENT=*BY-DIALOG is specified. IMON branches in both cases to a (further) dialog box in which specifications relating to the depot location can be entered locally, i.e. separately for each supply unit.
Activation – activating the software to be installed
Once the installation items have been placed, IMON performs measures to prepare the activation of special installation items. The relevant preparatory measures should ensure that the installed software runs correctly in the user system from the next system start.
Until then the installed software is locked for system users (see LOCK-PRODUCT-VERSION, „Commands“ [4 (Related publications )] manual).
Even before the actual installation, IMON:
generates the subsystem catalog
activates the syntax files
activates the message files
stores system corrections (reps) in the RMS depot and creates the corresponding loaders
makes preparations for adding POSIX satellites to the POSIX system
starts procedures
To do this, entries must be made in various files (parameter or configuration files). The measures depend on the installation item type and the general conditions of the BS2000 version.
If activation is to be carried out as prescribed by SNI for the individual supply units, it is enough to simply leave unchanged the default value 1 of the “Activation preparation mode” option in the “Global installation parameters” dialog box in menu mode or the *STD default of the ACTIVATION-MODE operand in the SDF statement INSTALL-UNITS.
User-specific measures are introduced in menu mode by specifying the value 2 for the “Activation preparation mode” option. When working with SDF statements, INSTALL-UNITS ..., ACTIVATION-MODE=*PARAMETERS(...) is specified.
IMON branches in both cases to a (further) dialog box in which specifications relating to the activation mode can be entered locally, i.e. separately for each supply unit.
If an installed supply unit is already run in the current system without a break in system running, the user can execute a “dynamic activation”. For this, the installation of the supply unit must have been successfully completed and the supply unit must support activation in the current system. A supply unit is dynamically activated with the SDF statement ACTIVATE-UNITS or through the menu Edit: Activate.
3. Controlling installation functions via the IMON parameter files
The user can also control installation functions via two different IMON parameter files:
For optional installation functions a sample IMON parameter file is provided with IMON and is named SYSPAR.IMON-BAS.<version>. The user can copy this file and change the parameter settings in the file to meet his or her requirements. IMON evaluates the parameter file stored with the name SYSPAR.IMON.<user code> under the user ID from which the installation was started. If it does not exist IMON evaluates the file $TSOS.SYSPAR.IMON.
On request IMON can also save various installation parameters in a special parameter file (the default parameter file is SYSPAR.IMON.LAST under the user ID from which installation was started). From this parameter file IMON automatically takes parameter values for the corresponding installation parameters and uses them for the current installation. This function enables customers to automate non-standard installations because it is no longer necessary to reenter the same non-standard parameters in the various dialog boxes of the FHS menu interface.
For more detailed information on the IMON parameter file, see section "IMON parameter files".
4. Checking the software configuration on the basis of reference files
The check is carried out on the basis of the current reference file set in the IMON options (default is $TSOS.SYS.IMON.SCI.REF on the home pubset). The dependencies of the supply units to be installed on the supply units already are listed in a protocol (see section "IMON reference files").
The check can also be suppressed using (Operand CHECK-CONFIGURATION=*NO in the statement INSTALL-UNITS or Check-Configuration =2 (No) in the dialog box Global Installation parameters.
5. Generating the procedure
The procedure is generated by IMON. To do this, parameters that were assigned values in Step 1 (selection) and Step 2 (customizing) as well as the IMON parameter files (if they were provided in Step 3) are evaluated.
IMON generates the procedure. It contains the work steps needed to install the selected delivery. The structure of the procedure supports a restart/recovery mechanism in the event of errors (see "Principle sequence of an installation step with error handling" (The troubleshooting process ).
Installation procedures can be started selectively.
IMON outputs an appropriate message to confirm generation.