IBM 8649 Hardware Maintenance Manual - Page 34

messages, Starting, diagnostic, programs

Page 34 highlights

Text messages The diagnostic text message format is as follows: Function Name: Result (test specific string) where: Function Name is the name of the function being tested when the error occurred. This corresponds to the function code (fff) shown in the error code format in the previous section. Result can be one of the following: Passed This result occurs when the diagnostic test is completed without any errors. Failed This result occurs when the diagnostic test discovers an error. User Aborted This result occurs when you stop the diagnostic test before it is complete. Not Applicable This result occurs when you specify a diagnostic test for a device that is not present. Aborted This result occurs when the test could not proceed, for example, because of the system configuration. Warning This result occurs when a possible problem is reported during the diagnostic test, such as when a device driver is not found. test specific string is additional information that you can use to analyze the problem. Starting the diagnostic programs Complete the following steps to start the diagnostic programs: 1. Turn on the server and watch the screen. Note: To run the diagnostic programs, you must start the server with the highest level password that is set. That is, if an administrator password is set, you must enter the administrator password, not the user password, to run the diagnostic programs. 2. When the message F2 for Diagnostics appears, press F2. 3. Type the appropriate password; then, press Enter. 4. Select either Extended or Basic from the top of the screen. 5. When the Diagnostic Programs screen appears, select the test you want to run from the list that appears; then, follow the instructions on the screen. 24 IBM xSeries 225 Types 8649: Hardware Maintenance Manual and Troubleshooting Guide

  • 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
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194

Text
messages
The
diagnostic
text
message
format
is
as
follows:
Function
Name:
Result
(test
specific
string)
where:
Function
Name
is
the
name
of
the
function
being
tested
when
the
error
occurred.
This
corresponds
to
the
function
code
(fff)
shown
in
the
error
code
format
in
the
previous
section.
Result
can
be
one
of
the
following:
Passed
This
result
occurs
when
the
diagnostic
test
is
completed
without
any
errors.
Failed
This
result
occurs
when
the
diagnostic
test
discovers
an
error.
User
Aborted
This
result
occurs
when
you
stop
the
diagnostic
test
before
it
is
complete.
Not
Applicable
This
result
occurs
when
you
specify
a
diagnostic
test
for
a
device
that
is
not
present.
Aborted
This
result
occurs
when
the
test
could
not
proceed,
for
example,
because
of
the
system
configuration.
Warning
This
result
occurs
when
a
possible
problem
is
reported
during
the
diagnostic
test,
such
as
when
a
device
driver
is
not
found.
test
specific
string
is
additional
information
that
you
can
use
to
analyze
the
problem.
Starting
the
diagnostic
programs
Complete
the
following
steps
to
start
the
diagnostic
programs:
1.
Turn
on
the
server
and
watch
the
screen.
Note:
To
run
the
diagnostic
programs,
you
must
start
the
server
with
the
highest
level
password
that
is
set.
That
is,
if
an
administrator
password
is
set,
you
must
enter
the
administrator
password,
not
the
user
password,
to
run
the
diagnostic
programs.
2.
When
the
message
F2
for
Diagnostics
appears,
press
F2.
3.
Type
the
appropriate
password;
then,
press
Enter.
4.
Select
either
Extended
or
Basic
from
the
top
of
the
screen.
5.
When
the
Diagnostic
Programs
screen
appears,
select
the
test
you
want
to
run
from
the
list
that
appears;
then,
follow
the
instructions
on
the
screen.
24
IBM
xSeries
225
Types
8649:
Hardware
Maintenance
Manual
and
Troubleshooting
Guide