Users Guide

Table 4. Exit Codes
Value Message Name Display Name Description
0 SUCCESSFUL Success
The update was successful.
1 UNSUCCESSFUL
(FAILURE)
Unsuccessful
An error occurred during the update process; the update
was not successful.
2 REBOOT_REQUIRED Reboot required
You must restart the system to apply the updates.
3 DEP_SOFT_ERROR Soft dependency error
Some possible explanations are:
• You attempted to update to the installed version of the
software.
• You tried to downgrade to a previous version of the
software.
To avoid receiving this error, provide the /f option.
4 DEP_HARD_ERROR Hard dependency error
The required prerequisite software was not found on the
system. The update was unsuccessful because the system
did not meet BIOS, driver, or firmware prerequisites for the
update to be applied, or because no supported device was
found on the target system.
5 QUAL_HARD_ERROR Qualification error
The DUP is not applicable to the system. Some possible
explanations are:
• The operating system is not supported by the DUP.
• The system is not supported by the DUP.
• The DUP is not compatible with the devices found in
your system.
A QUAL_HARD_ERROR cannot be suppressed by using
the /f switch.
6 REBOOTING_SYSTEM Rebooting system
The system is being rebooted.
9 RPM_VERIFY_FAILED RPM verification has failed
The Linux DUP framework uses RPM verification to ensure
the security of all DUP dependent Linux utilities. If security is
compromised, the framework displays a message and an
RPM Verify Legend, and then exits with exit code 9.
RPM produces output only if there is a verification failure.
The format of the output is:
.SM5DLUGT 'utility name'
For example, if the fmt command is compromised, the
framework displays the message:
rpm verify
failed: .M...... /usr/bin/fmt
RPM Verify Output Legend:
.‑ Verification test passed
S‑ File Size differs
M‑ Mode differs (includes permissions and file type)
5‑ MD5 sum differs
D‑ Device major/minor number mismatch
L‑ ReadLink(2) path mismatch
Command Line Interface Reference
21