IBM Support

Detecting damaged objects after a loss of utility power



Loss of utility power to the system may cause damage to objects. Often, messages in the System History Log do not identify the objects that are damaged. There is no easy way to detect damaged objects on the system. Save of objects is the most direct way to detect damaged objects, without having to use each object.

Resolving The Problem

To detect damaged objects, the following is recommended.

1) Check to see if errors are detected in the operating system.


Please note, this can be a long running command.
If error are detected, the job log will identify the operating system
options in error. Recovery is to re-install those product options and
apply PTFs. A "good" operating system is needed to perform save
operations, to detect damaged objects.

2) Save all user data, to detect damage on user objects first.

Possible actions are to: run specific save commands, or
Go Save option 23 All user data, or
if you have a CL program to save user data - run it.
If you use BRMS, run the control group.

Please note, first time detected damage of an object that the system
is trying to save will end that backup immediately. The system will
mark the header of this object as damaged. Previously marked
damaged objects will not be saved, however there will be a message
in the job log indicating an object could not be saved.

The job log should be reviewed to identify the damaged object(s) and
object(s) not saved. The messages in the job log will identify the
recovery action to be taken. These could be corrected immediately,
or later, all at one time.

After review of the job log restart the backup to detect if there are any
additional objects that may be damaged. This is a repetitive process,
and continues until all the damaged objects have been identified or
the save of user data is complete.

Most damaged objects need to be deleted and restored from a
backup tape containing the object. If the damaged object was not
saved, it has to be recreated. If the damaged object that cannot be
recreated, this is lost data.

3) After all user data has been saved and restored, a save of system
information should be performed next. It is recommended to use
Go Save option 22 System data only.

Average time needed to complete this is about approximately 1 hour,
and is dependant upon the number of IBM i licensed program
products installed, the number of private authorities on user profiles,
and system resources available.

Any damage with other licensed program products is usually fixed by
re-installing the product and applying PTFs.

References for saving the system and user data are:

Version 7.1
Systems management
Recovering your system

Version 7.2
Systems management
Recovering your system

Version 7.3
Systems management
Recovering your system

Backing up your system

Version 7.2
Systems management
Backing up your system

Systems management
Backing up your system

Task 4: Recovering from damaged objects and unreadable sectors

[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.1.0"}]

Document Information

Modified date:
18 December 2019