Error handling and activation restart

At activation IMON generates the activation procedure

$SYSSAG.<prefix>.<time-stamp>.DA from user input. This procedure is then started automatically or manually as a background procedure. It performs individual, self-contained processing steps known as activation steps (see "Structure of the activation procedure"). The step currently being processed is logged to the file $SYSSAG.<prefix>.<time-stamp>.RS.

If an error occurs during an activation 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 and Notes
<tsn>.0	(=REPEAT) The activation procedure is continued and the aborted activation 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 activation procedure is canceled. The iactivation should be aborted if the error cannot be eliminated immediately. Once the error is eliminated, the activation can be restarted at the activation step that was interrupted. The user is prompted in a console message to select one of the following start options. Restart an aborted processing step This start option is available only if the restart file (suffix RS) is still present. If it is not, a new start is performed automatically. Restart from the first processing step Note that the activation 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 activlation step. The error should only be ignored in exceptional cases as during subsequent processing it will be assumed that the “defective” activation step was terminated without an error. This assumption can cause other errors under some circumstances (e.g. a subsystem that has not been stopped cannot be stopped in the following processing step and a further error occurs). A restart is not possible.

The execution of an activation step with error handling is basically the same as the execution of an installation step as illustrated in figure 80 (The troubleshooting process ).

The cause of the error is given in the execution log (SYSLST output of the batch job) $SYSSAG.<prefix>.<time-stamp>.AL. The error can be eliminated either in the system (e.g. by releasing a file lock) or directly by editing the generated activation procedure (e.g. by correcting the command that was generated with an incorrect operand). Corrections to the activation procedure do not take effect until the procedure is called again.

Important activation files

Not only the activation procedure but also log files are created during activation; these provide information on the activation process. The most important files are listed in the following table.

File	Filename
Activation procedure	$SYSSAG.<prefix>.<time-stamp>.DA
Log of DSSM commands	$SYSSAG.<prefix>.<time-stamp>.RP
Logs of the activation procedure started as a background procedure: SYSLST log SYSOUT log console log	$SYSSAG.<prefix>.<time-stamp>.AL $SYSSAG.<prefix>.<time-stamp>.AO $SYSSAG.<prefix>.<time-stamp>.AC
Restart files: Information for restarting the activation procedure (RS file contains the number of the activation step last processed) Files are deleted if the activation procedure is completed successfully	$SYSSAG.<prefix>.<time-stamp>.RS $SYSSAG.<prefix>.<time-stamp>.RE $SYSSAG.<prefix>.<time-stamp>.TS
Temporary POSIX processing files: Add and Remove actions are logged for the POSIX system	$SYSROOT.IMON.ACTION.ADD $SYSROOT.IMON.ACTION.REM
Temporary activation lock file: Used to serialize the //ACTIVATE-UNITS jobs with the package installation of POSIX products at POSIX startup.	$SYSROOT.IMON.ACTIVATE-UNIT.SYSLST99

Explanation of the name components

<prefix>	Prefix; default prefix is IMONACU
<time-stamp>	Time stamp of the activation in the form <monat><tag><zeit><jahr>, mit
<month> <day> <time> <year>	is the first three letters of the month name a one-letter or two-letter day of the month time at which the activation starts in the form hhmmss four-digit year

Restarting an aborted activation

The relevant number of the current activation step is stored in the restart file during the activation procedure. This means that if the procedure is aborted, the restart file contains the number of the activation step that was not fully executed. When the aborted procedure is restarted, the procedure run starts with the last activation step that was not concluded.

An activation that was not concluded correctly can be repeated in the following two cases:

1. If the activation was aborted with the response <tsn>.1 when an error occurred.

2. If the activation procedure was not checked before it was terminated (e.g. using CANCEL-JOB or SHUTDOWN).

The restart is activated by restarting the activation procedure with ENTER-PROCEDURE.

The message SOL0013 EXECUTE RESTART FUNCTION ? is output on the console.

This message must be answered with <tsn>.1 or <tsn>.2.

• Answer <tsn>.1

  The activation starts at the interrupted installation step.

• Answer <tsn>.2

  The entire activation is repeated.

Notes

• You must ensure that the logging files (AL, AO, and AC suffix) are closed before the activation is restarted.

• Changes to the activation procedure only become active if the changes were made to the file under the original name.