HP Integrity Superdome 2 8/16 HP Smart Update Manager 5.3 User Guide - Page 42

Windows smart-component return codes, In Linux

Get HP Integrity Superdome 2 8/16 PDF manuals and user guides View all HP Integrity Superdome 2 8/16 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 42 highlights

In Linux, the negative return codes are reported. These return codes are determined by subtracting the negative value from 256. Return code SUCCESS_NO_REBOOT SUCCESS_REBOOT Value 0 1 SUCCESS_NOT_REQUIRED 3 FAILURE_GENERAL -1 FAILURE_BAD_PARM -2 FAILURE_COMPONENT_FAILED -3 Linux 0 1 3 255 254 253 Windows smart-component return codes Windows 0 1 3 255 254 253 Text The installation was successful. The installation was successful, but a reboot is required. The component was current or not required. A general failure occurred. For details, see the error log. A bad input parameter was encountered. The installation of the component failed. Error level 0 1 2 3 Linux smart-component return codes Single-target servers: Meaning The smart component was not installed. For more information, see the log file. The smart component was installed successfully. The smart component was nstalled successfully, but the system must be restarted. The installation was not attempted because the required hardware is not present, the software is current, or there is nothing to install. Error level 0 1 2 3 Multi-target servers: Meaning The smart component was installed successfully. The smart component was installed successfully, but the system must be restarted. The installation was not attempted because the required hardware is not present, the software is current, or there is nothing to install. The smart component was not installed. For more information, see the log file. Error level 0 1 Meaning The installation of the deliverable was successful. No reboot is required. The installation of the deliverable was successful. Reboot is required for the deliverable to be enabled. 42 Using scripts to deploy updates

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
In Linux, the negative return codes are reported. These return codes are determined by subtracting
the negative value from 256.
Text
Windows
Linux
Value
Return code
The installation was successful.
0
0
0
SUCCESS_NO_REBOOT
The installation was successful, but a
reboot is required.
1
1
1
SUCCESS_REBOOT
The component was current or not
required.
3
3
3
SUCCESS_NOT_REQUIRED
A general failure occurred. For details,
see the error log.
255
255
-1
FAILURE_GENERAL
A bad input parameter was
encountered.
254
254
-2
FAILURE_BAD_PARM
The installation of the component
failed.
253
253
-3
FAILURE_COMPONENT_FAILED
Windows smart-component return codes
Meaning
Error level
The smart component was not installed. For more
information, see the log file.
0
The smart component was installed successfully.
1
The smart component was nstalled successfully, but the
system must be restarted.
2
The installation was not attempted because the required
hardware is not present, the software is current, or there
is nothing to install.
3
Linux smart-component return codes
Single-target servers:
Meaning
Error level
The smart component was installed successfully.
0
The smart component was installed successfully, but the
system must be restarted.
1
The installation was not attempted because the required
hardware is not present, the software is current, or there
is nothing to install.
2
The smart component was not installed. For more
information, see the log file.
3
Multi-target servers:
Meaning
Error level
The installation of the deliverable was successful. No reboot
is required.
0
The installation of the deliverable was successful. Reboot
is required for the deliverable to be enabled.
1
42
Using scripts to deploy updates