IMON generates the <work>.<package>.<date>.IE installation procedure from the user input during the installation. This installation procedure is then started as a background procedure. The procedure executes individual isolated processing steps, the installation steps (e.g. backing up files, RMS processing).
The beginning of each installation step is reported on the console.
The principle sequence of an installation step is illustrated in figure 80.
If an error occurs during an installation step, a message that must be answered is output on the console. The installation procedure is interrupted until the message is answered.
The following are the possible response alternatives:
Answer | Effect | Notes |
<tsn>.0 | REPEAT: The installation step is repeated. | The installation step should only be repeated if the error was eliminated in the meantime (e.g. cancelation of a file lock) as otherwise the same error situation will arise. |
<tsn>.1 | CANCEL: The installation is canceled. A restart is possible | The installation should be aborted if the error cannot be eliminated immediately. Once the error is eliminated, the installation can be restarted at the installation step that was interrupted (see "Restarting an aborted installation"). Note that the installation steps that have already been carried out are not reconstructed, i.e. the initial status is not recreated for files that were changed. |
<tsn>.2 | IGNORE: The error is ignored and must be rectified manually. Processing is continued at the next installation step. | The error should only be ignored in exceptional cases as during subsequent processing it will be assumed that the “defective” installation step was terminated without an error. This assumption can cause other errors under some circumstances. A restart is not possible. |
The cause of the error can be determined using the <work>.<package>.<date>.IL installation log. An overview of the course of the installation can be found in the <work>.<package>.IC console log (for information on evaluating the console log, see the section "Contents and
structure of the console log").
More detailed information on the error situation and possible methods of rectifying it can be obtained using the HELP-MSG-INFORMATION command.
Principle sequence of an installation step with error handling
Figure 80: Principle sequence of an installation step with error handling
Important files in the installation
In addition to the installation procedure, during installation logging files that classify the generation parameters and the sequence of the installation are created. The following table shows the most important files:
File | Filename |
Installation procedure | <work>.<package>.<date>.IE |
Console log Contains all of the installation procedure console messages | <work>.<package>.IC |
Installation log SYSLST log of the installation procedure | <work>.<package>.<date>.IL |
Registration log Logs the registration in the SCI | <work>.<package>.<time-stamp>.II |
RMS log Information on the RMS processing | <work>.<package>.<date>.IR |
Installation actions | <work>.<package>.<date>.IA |
Installation parameters Parameters that were specified for the installation | <work>.<package>.<date>.IP |
File provision | <work>.<package>.<date>.CD |
Log of changes to file attributes Warning if the current file attributes of an installed file differ from the default file attributes | <work>.<package>.<date>.IW |
Restart file Information for restarting the installation procedure | <work>.<package>.<date>.RS |
Backup of the current SCI A backup copy of both SCI files is generated automatically during the installation. | <work>.<package>.<date>.SCI <work>.<package>.<date>.SCI.GPN |
Backup of the DSSM catalog | SOLSAV.<date> |
Procedure for deleting parked files | <park>.IMONDEI.PRK.<su>.<package> |
Backup of the original library Comparative basis used in the execution of the Undo function | :<target-catid>:$SYSSAG.IMON.UNDO.<su> |
Explanation of the name components
<work> | |
Work file ID and a prescribed prefix (if one has been assigned) (e.g. $SYSSAG. or $SYSSAG.W1.) | |
<package> | |
Package name | |
| <dssm> | |
| Name of the DSSM catalog | |
| <park> | |
| Park ID (e.g. $PARKSW1.) | |
| <su> | |
| Name of a supply unit | |
| <date> | |
| Time stamp of the installation in the form <month><day><time><year>, where | |
<month> | |
is the first three letters of the month name | |
<day> | |
| a one-letter or two-letter day of the month | |
<time> | |
| time at which the installation starts in the form hhmmss | |
<year> | |
| four-digit year | |