The user can control installation functions using an IMON parameter file.
An example of a IMON parameter file is supplied with IMON under the standard name SYSPAR.IMON-BAS.<version>. This file contains all IMON parameters with their default settings. In addition the file contains comments in the German and English languages that describe the function and optional values of each of the parameters.
To generate the installation procedure, IMON first evaluates the parameters that the user specified when calling the installation function. If a customer-specific IMON parameter file with the default name $TSOS.SYSPAR.IMON.<customer_code> exists, IMON also evaluates the parameters in this file. If it does not exist IMON evaluates the file $TSOS.SYSPAR.IMON. The parameter file is evaluated for all installations of deliveries with the customer code defined in the name.
The user can create the customer-specific IMON parameter file by copying the standard parameter file and modifying the parameters to meet his or her requirements. If there is no customer-specific parameter file, the installation procedure can be generated with the default settings documented in the IMON parameter file supplied.
The standard parameter file has been extended and reorganized. It now consists of a dynamic and a static section:
The dynamic section
In the dynamic section the user can enter the name of the global DSSM catalog and installation user ID(s) for certain supply units. The dynamic section also aids in automating the installation procedure even for nonstandard installations. The preset values for this automation are displayed when the corresponding query screens are output and can be changed by the user.
The dynamic section should be located at the beginning of the IMON parameter file for performance reasons, i.e. before the static section. It starts with the keyword START-DYN-PAR and ends with the keyword END-DYN-PAR. The lines of the dynamic section begin with the character string “****”. The standard parameter file supplied already contains a dynamic section that consists only of the beginning and end lines. You can enter input lines for the desired settings between these two lines:
Preset for the DSSM catalog:
The line containing the new default value for the name of the DSSM catalog (SYS.SSD.CAT.X is the preset value) begins with the keyword DSSM-CAT. The new name is specified in the following form:
****DSSM-CAT <filename 1..48 without-gen-vers>Preset value for the installation ID for a supply unit:
The preset value for an installation ID for a supply unit begins with the keyword SU. The name of the supply unit and the name of the installation ID follow. The preset value is specified in the following form:
****SU <text 1..30 without-sep> <name 1..8>If the preset values for the installation ID(s) for several supply units are to be changed, the corresponding number of input lines must be added.
See "IMON parameter file for optional installation functions " for an example.
The static section
This section contains all optional IMON parameters with the default settings, which can only be modified using the parameters file. It also contains comments in English and German explaining the functions of the individual parameters and their optional values.
Comment lines start with the character “**”. Input lines that are evaluated during generation of the installation procedure start with “*” and contain statements for the generation program. Parameter values are defined in the following format using the SET statement:
SET <parameter_name> "<value>"
Example of a parameter from the default parameter file
* SET ZVUNLOAD "Y"
“Y” is defined by default for the ZVUNLOAD parameter, i.e. the volume is unloaded automatically after installation.
The following functions are preset in the static part of the IMON parameter file and can, if desired, be changed. The presettings in the default parameter file correspond also to the behavior of IMON V2.2:
The reference file $SERVICE.SOLREF.IMON.SW-CONF is generated.
Generation of this reference file can be suppressed.
Data volumes used for installation are unloaded automatically.
Unloading of the data volumes can be suppressed.
The SCI files are backed up automatically before they are registered (see "Backing up the SCI" (Software Configuration Inventory (SCI) )). Backing up of the SCI files can be suppressed.
The source file for creating the DSSM catalog is created or expanded under the name <dssm-catalog>.SRC.
In addition you can specify that the source file will not be appended to and is to be recreated for each installation instead.
The name of the DSSM catalog to be expanded can be specified explicitly or creation of the source file can be suppressed.
The installation result is registered in the standard SCI of the target system.
You have the option of defining that the installation result is to be registered in the SCI currently open. If the SCI currently open is set, the dialog query is suppressed (see "Example with SDF statements " for an example of the dialog query).
The SYSSII files are incorporated into the target system and incorporated into the SOLLIB.IMON.SYSSII library under the work file ID (possibly with a prefix).
You have the option of suppressing transfer of the SYSSII files.
There is no special storage location defined for documentation files (Release Notices and readme files; item type *FE, *FG and files whose names begin with SYSFGM. or SYSRME.). They are installed under the installation ID.
You have the option of setting a central storage location for documentation files.
There is no special storage location defined for subsystem declarations (item type SSC, SSD and files whose names begin with SYSSSC. or SYSSSD.). They are installed under the installation ID.
You have the option of setting a central storage location for subsystem declarations.
The save data media created by IMON during installation and parking do not have deletion or overwrite protection. You can also optionally specify a retention period from 1 to 999 days.
REP loaders can be generated when parking a delivery. You can also optionally specify that the REP files are only to be added to the RMS depot.
If the files to be installed already exist, then their previous file attributes (ACCESS, USER-ACCESS and MIGRATE) are kept. You can also optionally specify that the file attributes are set to match the data specified for the SOLIS2 delivery.
The product movement file (PMF) for each delivery is saved in the customer system in the PLAM library $<work file ID>.SOLLIB.IMON.PBD. You can also optionally specify that this file is to be deleted after installation without making a backup copy.
The product movement file (PBD) for each delivery is saved in the customer system in the PLAM library $<work file ID>.SOLLIB.IMON.PBD. You can optionally specify that this PBD file is to be deleted at the end of the installation process without saving it in the PLAM library.
Optionally it can be agreed that in customer systems which have a default user ID which is not TSOS, $.TASKLIB and $.MACROLIB should be processed instead of $TSOS.TASKLIB and $TSOS.MACROLIB.
Optionally a specific tape repository can be employed for robot use. The tape repository must be specified in the /SECURE-RESOURCE-ALLOCATION command for processing the SOLIS delivery medium.
Information on using central storage locations
The default for each of the parameters for specifying central storage locations is a null string (""). If you intend to use a central storage location, the corresponding parameter value must be changed in “<storage_location>” in the customer-specific IMON parameter file, where <storage_location> must be specified as a <partial-filename 1..23>.
Input format: [:<catid>:][$<userid>.][<prefix>.]
IMON expands partial storage locations (i.e. where the catalog or user ID is missing) in accordance with the following rules:
The TSOS user ID is assumed if no user ID is specified.
The catalog ID is specified as a function of the target system if not catalog ID is specified:
In the case of an installation on the home pubset, the default catalog ID of the specified or an expanded user ID is assumed.
In the case of an installation on an imported pubset, the catalog ID of the imported pubset is assumed.
Example
The user with the customer ID CUST01 wishes to automate an installation procedure. The user does not use the standard DSSM catalog, but instead uses a DSSM catalog named SYS.SSD.CAT.SYS1. For some supply units the user has defined some of his or her own installation user IDs to reserve some storage space for the TSOS user ID. The pecial user IDs are TOOLS and COMPIL in this example $TOOLS for the supply units PERCON and LMS $COMPIL for the supply units COBOL85 and PLI1 Furthermore, the documentation files are to be stored centrally on the HOME pubset under the RZINFO user ID.
Procedure
Create a copy of the standard parameter file supplied with IMON V3.2 (file name SYSPAR.IMON-BAS.032) under the user-specific name ($TSOS.SYSPAR.IMON.<customer ID>):
/copy-file from-file=$.SYSPAR.IMON-BAS.032,to-file=$TSOS.SYSPAR.IMON.CUST01Edit the user-specific parameter file:
The presets to be changed for the DSSM catalog and the desired installation IDs are entered in the dynamic section:
****START-DYN-PAR ****DSSM-CAT $TSOS.SYS.SSD.CAT.SYS1 ****SU PERCON TOOLS ****SU LMS TOOLS ****SU COBOL85 COMPIL ****SU PLI1 COMPIL ****END-DYN-PAR
The changes to the preset for the storage location of the documentation files are made in the dynamic section. To do this, the preset for the ZVDOCPRF parameter
* SET ZVDOCPRF ""must be changed to:
* SET ZVDOCPRF ":HOME:$RZINFO."