Problem
or
message
(these
appear
in
upper
case
in
the
console)
Meaning
or
corrective
action
PCI
I/O
processor
rejected
assignment
or
removal
of
an
IOA
The
I/O
processor’s
(IOP)
licensed
internal
code
(LIC)
has
rejected
the
assignment
of
an
I/O
adapter
(IOA)
to
that
IOP,
or
the
IOP’s
LIC
has
rejected
the
removal
of
an
IOA
which
the
IOP
owns.
Word
5
of
the
SRC
is
the
Direct
Select
Address
(DSA)
of
the
IOP.
Word
7
of
the
SRC
is
the
DSA
of
the
IOA.
1.
To
find
the
IOP
go
to
using
the
DSA
in
word
5
of
the
SRC.
2.
To
find
the
IOA
go
to
using
the
DSA
in
word
7
of
the
SRC.
Use
HSM
concurrent
maintenance
functions
to
assign
or
remove
the
IOA.
See
in
the
iSeries
(TM)
Service
Functions
manual
for
help
in
using
the
HSM
concurrent
maintenance
functions.
Assignment
failures
can
be
from:
v
The
IOP
already
being
at
its
capacity
to
accept
IOA
assignments.
v
The
IOA
is
not
a
type
supported
by
the
IOP.
Corrective
action:
v
Add
another
IOP
for
LIC
to
assign
the
IOA
to
if
necessary.
v
Re-assign
the
IOA
to
another
IOP
using
concurrent
maintenance.
Removal
failures:
v
This
is
a
LIC
problem
and
should
be
reported.
v
Call
your
next
level
of
support.
Linux
owned
slot
-
no
IOP
is
allowed
An
I/O
processor
card
was
found
in
a
PCI
Bridge
Set
that
is
allocated
to
a
Linux
partition.
The
IOP
will
not
be
supported
in
this
card
position.
This
ends
the
procedure.
MA_BRDG
For
use
by
authorized
service
providers.
MA_BRDG:
multi-adapter
bridge.
The
problem
is
the
multi-adapter
bridge
hardware
on
a
system
bus.
1.
Is
the
location
information
for
this
failing
component
available
in
the
Service
Action
Log?
v
No
:
Continue
with
the
next
step.
v
Yes
:
Use
the
location
information
in
the
Service
Action
Log,
and
go
to
step
4
(See
page
2.
Were
you
sent
here
by
an
A6xx
xxxx
or
B6xx
xxxx
SRC,
and
no
location
information
was
available
in
the
Service
Action
Log?
v
No
:
Continue
with
the
next
step.
v
Yes
:
Record
the
bus
number
value,
BBBB,
in
word
7
of
the
SRC.
See
(located
in
the
Bus
PIP
Overview
topic)
for
help
in
determining
the
bus
number.
Search
for
the
bus
number
in
HSM
or
the
System
Configuration
Listing
to
determine
which
frame
or
I/O
tower
contains
the
failing
component.
Record
the
frame
or
tower
type,
and
go
to
step
4
(See
page
Analyze
hardware
problems
363
