Placement and activation in the customer-specific installation

ePlacement and activation can be defined as follows in the customer-specific installation:

	In menu mode	Using the INSTALL-UNITS statement
Placement
Customer-specific placement	Via the menu: Edit, option 4 (Install): “Global installation parameters”: Placement mode: 2 (Other)	PLACEMENT-MODE= *BY-DIALOG
	The context switches to the “Supply units placement parameters” dialog box. The following values can be changed there:
Modify path names (catalog ID, user ID, prefix)	Modify the values in the “Catid”, “Userid”, “Prefix” columns	Modify the values in the “Catid”, “Userid”, “Prefix” columns
Overwrite existing files Yes Only in certain cases No	Modify the value in the “Replace files” column Y (preset) M N	REPLACE-OLD-FILES= *YES (preset) *MINIMUM *NO
Force location No Only in certain cases Yes	Modify the value in the “Force Loc.” column N (preset) M Y	FORCE-LOCATION= *NO (preset) *MINIMUM *YES
Activation
Customer-specific activation	Via the menu: Edit, option 4 (Install): “Global installation parameters”: Activation preparation mode: 2 (Other) The “Global activation preparation parameters” dialog box is displayed. The following values can be modified there:	ACTIVATION-MODE= *PARAMETERS(...)
Syntax file processing	1 (Yes) 2 (No) SDF param file	SYNTAX-FILE-PROCESS= *BY-DIALOG / *NO / *YES
Message file processing	1 (Yes) 2 (No) MIP param file System message file name	MESSAGE-FILE-PROCESS= *BY-DIALOG / *NO / *YES
DSSM processing	1 (Yes) 2 (No) DSSM Catalog name Keep old version: 1 (Yes) 2 (No)	DSSM-FILE-PROCESS= *BY-DIALOG / *NO / *YES
RMS processing	1 (Depot and Loader) 2 (Depot only) 3 (No) Depot location: 1 (Standard) 2 (Enforced) Location	REP-FILE-PROCESS= *BY-DIALOG / *NO / *YES
POSIX processing	1 (cfg) 2 (all) 3 (no)	POSIX-PROCESSING= *BY-DIALOG / *BY-CONFIGURATION-FILE / *ALL / *NO

Placement – specifying the depot location of the files to be installed

IMON reads the supply components (release items) of the supply units to be installed from the distribution medium and stores them as installation items on the target system. The file attributes of an installation item are taken from the delivery information. The depot location, i.e. the path name of the installation item is affected by the definitions in the delivery information and other user input.

The path name is formed as follows in the case of further user input:

:<catid>:$<userid>.[<prefix>]<item-name>

where:

<catid>	Refers to the catalog ID of the pubset on which the supply units will be installed. The catalog ID is taken from the target system specification (TARGET-SYSTEM=*PARAMETERS(...,PUBSET = <catid>).
<userid>	Refers to the installation ID. If you specify a user ID that differs from that for the default installation, the user ID to be used is formed in accordance with the FORCE-LOCATION setting and the stipulations of the delivery information (see under: “Specifying the installation ID” "Placement and activation in the customer-specific installation ").
<prefix>	refers to a prefix that is used if the path name for the installation item can be selected freely. The prefix is specified in the following sequence: Prefix of the associated supply group Prefix of the associated supply unit Otherwise no prefix
<item-name>	refers to the installation item.

The storage location of an installation item specified in the delivery information can be changed when evaluating a customer-specific IMON parameter file (see section "IMON parameter files" (IMON parameter files )) using the options set there. The IMON parameter file can contain the following options relating to the storage location:

• One installation ID can be specified for each supply unit specified.

• The catalog ID and user ID as well as the prefix can be specified for centrally storing documentation files and subsystem declarations.

Specifying the installation ID

• FORCE-LOCATION=*NO

  Modification of the installation ID is not to be forced.

  It is specified in the following sequence:

  1. Location that was defined explicitly for the associated supply group.

  2. Location that was specified explicitly for the associated supply unit.

  If a location for the associated supply group or supply unit is prescribed explicitly (mandatory) in the delivery information, the installation is aborted if a different location is specified.

• FORCE-LOCATION=*MINIMUM

  Modification of the location (installation ID and prefix) is not forced in the case of permanently defined user IDs.

  It is specified in the following sequence:

  1. Location that is defined permanently in the product movement file for the associated supply group.

  2. Location that is defined permanently in the product movement file for the associated supply unit.

  3. Location that was specified explicitly for the associated supply group.

  4. Location that was specified explicitly for the associated supply unit.

  If a location for the associated supply group or supply unit is prescribed explicitly (mandatory) in the delivery information, the installation is continued using the mandatory location even if a different location is specified.

• FORCE-LOCATION=*YES

  Modification of the installation ID is to be forced.

  It is specified in the following sequence:

  1. Location that was defined explicitly for the associated supply group.

  2. Location that was specified explicitly for the associated supply unit.

  If a location for the associated supply group or supply unit is prescribed explicitly (mandatory) in the delivery information, the installation is continued even if a different location is specified.

  Files for which a non default location (installation ID and prefix) was forced are listed in a specific log file as this type of installation can stop the product behaving correctly.

Specifying the installation item name

If no such file exists, it is created with the file attributes defined for the supply component.

Existing files of the same name are overwritten in accordance with the user input (REPLACE-OLD-FILES=*MINIMUM/*YES). Whether or not the files are overwritten also depends on whether the delivery information rules the original file names to be mandatory.

If the file name is not mandatory, existing files are not overwritten by the user input REPLACE-OLD-FILES=*MINIMUM/*NO. The installation item is stored in a new file under the substitute path name generated by IMON. The substitute path name is formed as follows:

:<catid>:$<userid>.[<prefix>]<item-name>.nnn

The suffix nnn refers to a consecutive number from 001 through 999. If the appended suffix renders the file name too long, the installation items is shortened accordingly from the end.

The file attributes of the new file are taken from the delivery information. If the file name is mandatory, existing files are overwritten by the user input REPLACE-OLD-FILES=*MINIMUM (as with *YES also). The previous file attributes are retained.

The following applies if a file cannot be overwritten because of a file lock, for example:

• If the file is a syntax or message file (installation items of the type SDF and MES), the installation procedure tries to cancel the file lock. If this attempt is unsuccessful, the procedure is canceled and a message that requires an answer is output on the operating console. The operator’s response governs the subsequent processing:

  “Repeat” “Ignore” “Abort”

  The installation procedure attempts once again to cancel the file lock. The installation is continued despite the file lock, i.e. the affected installation item is not installed. The installation is aborted with an error.

• The installation is canceled immediately if another installation item cannot be overwritten.

If the file name is mandatory, existing files are not overwritten by the user input REPLACE-OLD-FILES=*NO and the installation is canceled.

Activation – preparing for activation of the installed software

Activation of the installed software is started using the INSTALL-UNITS statement, operand ACTIVATION-MODE=*PARAMETERS(...) or, in menu mode, in the “Global Activation Preparation Parameter” screen.

Syntax files

ACTIVATION-MODE=*PARAMETERS(SYNTAX-FILE-PROCESS=*BY-DIALOG/*NO/*YES)

Unlike in the default installation, in the customer-specific installation you can

• prevent activation of the syntax files

• modify the name of the SDF parameter file for the next system start (corresponds to MODIFY-SDF-PARAMETERS with SCOPE=*NEXT-SESSION)

Message files

ACTIVATION-MODE=*PARAMETERS(MESSAGE-FILE-PROCESS=*BY-DIALOG/*NO/*YES)

Unlike in the default installation, in the customer-specific installation you can

• prevent activation of the message files

• modify the name of the MIP parameter file

• modify the value of the MSGFIL02 system parameter and thereby the name of the global message file

Note on reinstallation of syntax and message files which have already been activated

In the course of reinstallation IMON deactivates the file concerned, renames the file <file>.nnn (suffix nnn = 001 through 999), and reactivates the renamed file. Subsequently the new component is installed under its standard name. When the next startup takes place, the syntax and message files with a suffix are automatically deleted.

Subsystem

ACTIVATION-MODE=*PARAMETERS(DSSM-PROCESSING=*BY-DIALOG/*NO/*YES)

Unlike in the default installation, in the customer-specific installation you can

• prevent processing of the subsystem catalog

• modify the name of the subsystem catalog

• retain or remove the earlier version of a removable subsystem

The subsystem catalog name specified in the selection window may be displayed there when using a customer-specific IMON parameter file (see section "IMON parameter files").

RMS files

ACTIVATION-MODE=*PARAMETERS(REP-PROCESSING=*BY-DIALOG/*NO)

When you park a supply unit, the system corrections (REP installation item) are transferred to the RMS depot (if the preset of the operand UPDATE-RMS-DEPOT from the statement PARK-UNITS or the option RMS Depot actualise=1 (Yes) on the “Park parameter” screen is kept).

You can specify that the Rep loader is to be generated during the parking procedure when using a customer-specific IMON parameter file (see section "IMON parameter files").

If the supply unit has not yet been parked, you can specify transfer to the RMS depot or the name of the RMS depot. You can also specify whether the rep loader is to be generated during the installation.

If the rep loader is generated during the installation, IMON enters the logical names in the SCI and extends the current path names with the default values from the RMS file.

If the rep loader is generated after the installation, the current path names are not contained in the SCI. The current path names must then be entered in the SCI in accordance with the SET-INSTALLATION-PATH command.

POSIX satellites

ACTIVATION-MODE=*PARAMETERS(POSIX-PROCESSING=*BY-DIALOG / *BY-CONFIGURATION-FILE / *NO / *ALL)

Unlike in the default installation, in the customer-specific installation you can prevent activation of the POSIX files.

Procedures

Procedures (of types DO and ENT) that are to be executed during installation are displayed when the installation parameters are queried. Automatic start is the default when installing on the home pubset. If the automatic start is explicitly suppressed, then the procedures must be started manually after installation is complete (just like for an installation on an imported pubset). In this case the names of the procedures to be started manually are output to SYSOUT when generating the installation procedure or to the console while the installation procedure is executing (see also the console log). Procedures of the type DO are started using the ENTER-PROCEDURE or CALL-PROCEDURE command, procedures of the type ENT are started using the ENTER-JOB command.