0% found this document useful (0 votes)

8K views

Ibm Error Report

Uploaded by

Mahesh Gulbarga

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

8K views

Ibm Error Report

Uploaded by

Mahesh Gulbarga

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 856

System i® and System p®

Reference codes

System i® and System p®

Reference codes
Note
Before using this information and the product it supports, read the information in “Notices,” on
page 839 and the manual IBM Systems Safety Information, G229-9054.

Thirteenth Edition (September 2007)

© Copyright International Business Machines Corporation 2004, 2006.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Reference codes . . . . . . . . . . . 1 (573A, 576A) Reference codes . . . . . . . 148
List of system reference codes . . . . . . . . 2 (573B) Reference codes . . . . . . . . . 148
(1xxx) System power control network (SPCN) (573C) Reference codes . . . . . . . . . 149
reference codes . . . . . . . . . . . . 6 (6320, 6321, 632B, 632C, 6330, 6331, 6333, 6336,
(1400) Bulk power subsystem reference codes . . 22 6337) Optical storage unit reference codes . . . 150
(1750, 2105, 2107) Disk unit reference codes. . . 44 (6A59) Workstation adapter console reference
(180A, 283C, 283D, 283F, 28B9, 28CB, 28CC, codes . . . . . . . . . . . . . . . 155
28D2, 28DB, 28DF, 506D, 506E) Device backplane (7208) Tape drive reference codes . . . . . . 156
reference codes . . . . . . . . . . . . 45 (9348) Tape unit reference codes . . . . . . 162
(2058) Reference codes. . . . . . . . . . 52 (9427) Tape unit reference codes . . . . . . 163
(20A8, 20Dx, 20EE, 20FF, 2102, 220x, 25Ax, 25Cx, (A1xx) Service processor reference (attention)
2602, 2803, 2B2x) Model 185 and A50 reference codes . . . . . . . . . . . . . . . 168
(error) codes . . . . . . . . . . . . . 53 (A2xx, B2xx) Logical partition reference codes 169
(2689) Reference codes. . . . . . . . . . 67 (A6xx, B6xx) Licensed Internal Code reference
(2724, 2744, 6149) Reference codes . . . . . . 71 codes . . . . . . . . . . . . . . . 182
(2742, 2793, 2805) Reference codes . . . . . . 71 (A7xx, B7xx) Licensed Internal Code reference
(2743, 2760) Reference codes . . . . . . . . 72 codes . . . . . . . . . . . . . . . 219
(2745) Reference Codes . . . . . . . . . 72 (A9xx, B9xx) Reference codes . . . . . . . 240
(2746) Twinaxial – workstation adapter reference (AAxx) Partition firmware reference (attention)
codes . . . . . . . . . . . . . . . 73 codes . . . . . . . . . . . . . . . 241
(2748, 2757, 2763, 2778, 2780, 2782, 5703, 5709) (B000) Network reference codes . . . . . . 243
Reference codes . . . . . . . . . . . . 74 (B001) Reference codes . . . . . . . . . 244
(2749, 2767, 2768, 2842, 2843, 2844, 284B, 5702, (B002) Reference codes . . . . . . . . . 262
570B) Reference codes . . . . . . . . . . 80 (B003) Asynchronous communications reference
(2750, 2751) Reference codes . . . . . . . . 89 codes . . . . . . . . . . . . . . . 269
(2761) Reference codes. . . . . . . . . . 90 (B004) Reference codes . . . . . . . . . 276
(2765, 2766, 2787, 280D, 280E, 5704) Reference (B005) Reference codes . . . . . . . . . 281
Codes . . . . . . . . . . . . . . . 90 (B006) Common Licensed Internal Code
(2771, 2772) Reference codes . . . . . . . . 92 reference codes . . . . . . . . . . . . 284
(281x) Reference codes. . . . . . . . . . 92 (B008) Reference codes . . . . . . . . . 298
(2838, 2849) Reference codes . . . . . . . . 93 (B009) Reference codes . . . . . . . . . 305
(2847) Reference codes. . . . . . . . . . 93 (B010) Reference codes . . . . . . . . . 308
(287F) Reference codes. . . . . . . . . . 97 (B013) Reference codes . . . . . . . . . 326
(2890) Reference codes. . . . . . . . . . 97 (B014) Reference codes . . . . . . . . . 328
(2892) Reference codes . . . . . . . . . 101 (B015) Reference codes . . . . . . . . . 330
(3490) Tape unit reference codes . . . . . . 106 (B017) Reference codes . . . . . . . . . 331
(3494) Tape library reference codes . . . . . 110 (B018) Reference codes . . . . . . . . . 331
(3570) Tape unit reference codes . . . . . . 112 (B019) Reference codes . . . . . . . . . 332
(358x, 3592, 4685, 5755, 6279, 6381, 6382, 6383, (B020) Reference codes . . . . . . . . . 333
6384, 6386, 6387, 63A0, 7207) Tape unit reference (B021) Reference codes . . . . . . . . . 334
codes . . . . . . . . . . . . . . . 116 (B022) Reference codes . . . . . . . . . 341
(3590) Tape unit reference codes . . . . . . 120 (B025) Reference codes . . . . . . . . . 346
(40xx) Model 185 and A50 reference (error) (B026) Reference codes . . . . . . . . . 347
codes . . . . . . . . . . . . . . . 124 (B028) Reference codes . . . . . . . . . 348
(432x, 660x, 671x, 673x) Disk unit reference (B030) Reference codes . . . . . . . . . 355
codes . . . . . . . . . . . . . . . 125 (B038) Reference codes . . . . . . . . . 356
(4758) Reference codes . . . . . . . . . 134 (B040) Reference codes . . . . . . . . . 361
(4764) Reference codes . . . . . . . . . 134 (B045) Reference codes . . . . . . . . . 364
(4812) Reference codes . . . . . . . . . 135 (B070) Reference codes . . . . . . . . . 364
(4B20) Model 185 and A50 reference (error) (B075) Workstation adapter console reference
codes . . . . . . . . . . . . . . . 137 codes . . . . . . . . . . . . . . . 372
(5700, 5701) Reference codes . . . . . . . 138 (B1xx) Service processor firmware reference
(5706, 5707) Reference codes . . . . . . . 138 codes . . . . . . . . . . . . . . . 377
(5708, 574F, 575B) Reference codes . . . . . 139 (B1xx) Service processor firmware reference
(571A, 571B, 571E, 571F, 573D, 573E, 57FF) code descriptions . . . . . . . . . . . 378
Reference codes . . . . . . . . . . . 141

© Copyright IBM Corp. 2004, 2006 iii

(B1xx) Service processor firmware reference SCSD Devices SRNs (ssss-102 to ssss-640) . . . 784
code callouts . . . . . . . . . . . . 461 Using service request numbers . . . . . . . 786
(B3xx) Connection monitoring reference codes 463 List of progress codes . . . . . . . . . . 787
(BAxx) Partition firmware reference (error) Service processor progress codes . . . . . . 788
codes . . . . . . . . . . . . . . . 469 (BCxx) Base motherboard controller progress
(BBxx) High performance switch reference codes 478 codes . . . . . . . . . . . . . . . 789
(BF67) Linux reference codes . . . . . . . 478 (C1xx) Service processor progress codes
(BF75) Linux reference codes . . . . . . . 481 (checkpoints) . . . . . . . . . . . . 789
(BF77) Linux reference codes . . . . . . . 484 (C2xx) Virtual service processor progress codes 795
(CBxx) IBM Network Manager reference codes 489 IPL status progress codes . . . . . . . . 797
(DAxx) Partition firmware reference (error) (C700) Server firmware IPL status progress
codes . . . . . . . . . . . . . . . 491 codes . . . . . . . . . . . . . . . 801
(E2xx) Licensed Internal Code error codes . . . 491 (C900) IPL status progress codes . . . . . . 802
(E3xx) Licensed Internal Code error codes . . . 491 (CAxx) Partition firmware progress codes . . . 803
(E302) Firmware update error codes . . . . . 492 CF00 xxxx Linux Kernel Progress Codes . . . 810
(E303) Formatting media error codes . . . . 523 (Dxxx, Exxx) System firmware progress codes
(E332) Licensed Internal Code error codes . . . 524 for Models A50 and 185 only . . . . . . . 810
(E338) Licensed Internal Code error in guided (D1xx) Service processor progress codes (service
maintenance in Service Focal Point . . . . . 524 processor dump and platform dump) . . . . 816
(E355) errors. . . . . . . . . . . . . 524 (D1xx) Service processor status progress codes 817
(E35A) HMC code level . . . . . . . . . 526 (D200) Partition status progress codes . . . . 818
(E36C) HMC scheduled task errors . . . . . 526 (D6xx) General status progress codes . . . . 819
(E35F) Persistence error codes . . . . . . . 526 (D9xx) General status progress codes . . . . 820
(E3CA) Error regarding a media device. . . . 527 AIX IPL progress codes . . . . . . . . . 820
(E3D4) Call home errors . . . . . . . . . 530 Using progress codes . . . . . . . . . . . 837
(E3F0) Trace failure . . . . . . . . . . 531 Reference codes that begin with a number sign (#) 838
(E4xx) Licensed Internal Code error codes . . . 531
Using system reference codes . . . . . . . . 532 Appendix. Notices . . . . . . . . . 839
Block replacement of FRUs . . . . . . . . . 533 Trademarks . . . . . . . . . . . . . . 840
List of service request numbers . . . . . . . 533 Regulatory notices. . . . . . . . . . . . 841
Five-Digit SRNs 10104 through SSA03 . . . . 534 Class A Notices. . . . . . . . . . . . 841
SRNs 101-000 through 59D-xxx . . . . . . 543 Class B Notices . . . . . . . . . . . . 843
SRNs 60B-xxx through 69D-203 . . . . . . 556 Terms and conditions. . . . . . . . . . . 845
SRNs 700-xxx through 7C1-117 . . . . . . 584 Product recycling and disposal . . . . . . . 846
SRNs 801-xxxx through 899-xxx . . . . . . 608 Battery return program . . . . . . . . . . 846
SRNs 900-001 through xxxxxxxx . . . . . . 627 IBM Cryptographic Coprocessor Card Return
SRNs A00-FF0 through A25-001 . . . . . . 673 Program . . . . . . . . . . . . . . . 847
SRNs 2502-101 through 25D0-108 . . . . . . 687
SRNs 2600-101 through 2D07-xxxx . . . . . 759

iv System i® and System p®: Reference codes

Reference codes
Reference codes are diagnostic aids that help you determine the source of a hardware or operating
system problem. Using a reference code enables you to find the solution to fix the problem. To use
reference codes effectively, you must use them in conjunction with other service and support procedures.

Note: System reference codes (SRCs) often indicate failing items. Some failing items are required to be
exchanged in groups until the problem is solved. Other failing items are flagged as mandatory
exchange and must be exchanged before the service action is complete, even if the problem
appears to have been repaired. For more information, see “Block replacement of FRUs” on page
533.

If you were not directed to this page by another procedure, begin the troubleshooting process by using
the following link:

Start of call procedure

1. Does the reference code contain a hyphen (-), for example, 111-459?
v Yes: See “List of service request numbers” on page 533.
v No: Continue with the next step.
2. Does the reference code contain exactly 5 characters?
v Yes: See “List of service request numbers” on page 533.
v No: Continue with the next step.
3. Is the first character of the reference code a number sign (#)?
v Yes: See “Reference codes that begin with a number sign (#)” on page 838.
v No: Continue with the next step.
4. Is the reference code a 3-digit hexadecimal number?
v Yes: Prepend 101 and a hyphen (-) to the number, then use that number to refer to the “List of
service request numbers” on page 533.
v No: Continue with the next step.
5. Is the reference code a 4–digit hexadecimal number that begins with 0, 2, BC, D, or E?
v Yes: See “Using progress codes” on page 837.
v No: Continue with the next step.
6. Is the reference code an alphanumeric string that begins with HSC or a 6-digit number that begins
with 0 and does not contain a hyphen (-)?
v Yes: See HMC error codes.
v No: See “List of system reference codes” on page 2.

If you need more information about reference codes, such as reference code formats and how to use
reference code information, see the following pages:

“Using service request numbers” on page 786

“Using progress codes” on page 837

“Using system reference codes” on page 532

© Copyright IBM Corp. 2004, 2006 1

List of system reference codes

The system reference codes (SRCs) in this list represent reference code types and are organized by their
first character, with numbers preceding letters. If you do not find the SRC that you are looking for in this
list, ask your next level of support for assistance.

For more information about SRCs, including details about using this list of SRCS, see “Using system
reference codes” on page 532.

Note: SRCs often indicate failing items. Some failing items are required to be exchanged in groups until
the problem is solved. Other failing items are flagged as mandatory exchange and must be
exchanged before the service action is complete, even if the problem appears to have been
repaired. For more information, see “Block replacement of FRUs” on page 533.

0 1 2 3 4 5 6 7 8 9 A B C D E F H #

1
1xxx
1400
1750
180A

2
2058
20A8
20Dx
20EE
20FF
2102
2105
2107
220x
25Ax
25Cx
2602
2689
2724
2742
2743
2744
2745
2746
2748
2749
2750
2751
2757
2760
2761
2763
2765
2766
2767
2768
2771

2 System i® and System p®: Reference codes

List of system reference codes

2772
2778
2780
2782
2787
2793
2803
2805
280D
280E
281x
2838
283C
283D
283F
2842
2843
2844
2847
2849
284B
287F
2890
2892
28B9
28CB
28CC
28D2
28DB
28DF
2B2x

3
3490
3494
3570
358x
3590
3592

4
40xx
432x
4685
4758
4764
4812
4B20

5
506D
506E
5700
5701
5702
5703

Reference codes 3
List of system reference codes

5704
5706
5707
5708
5709
570B
571A
571B
571E
571F
573A
573B
573C
573D
573E
574F
5755
575B
576A
57FF

6
6149
6279
632x
6330
6331
6333
6336
6337
6381
6382
6383
6384
6386
6387
63A0
660x
671x
673x
6A59

7
7207
7208

9
9348
9427

A
A1xx
A2xx
A6xx

4 System i® and System p®: Reference codes

List of system reference codes

A7xx
A9xx
AAxx

B
B000
B001
B002
B003
B004
B005
B006
B008
B009
B010
B013
B014
B015
B017

B018
B019
B020
B021
B022
B025
B026
B028
B030
B038
B040
B045
B070
B075
B1xx
B2xx
B3xx
B6xx
B7xx
B9xx
BAxx
BBxx
BCxx (For 4-digit codes that begin with BC, see “List of progress codes” on page 787.)
BF67
BF75
BF77

C
CBxx
For all other codes that begin with C and for 4-digit codes that begin with a
space character or a zero, see “List of progress codes” on page 787.

D
DAxx
For codes that begin with D and for 4-digit codes that begin with a space character or a
zero, see “List of progress codes” on page 787.

Reference codes 5
List of system reference codes

E
Exxx (For 4-digit codes that begin with E, see “List of progress codes” on page 787.)
E2xx
E3xx
E302
E303
E332
E338
E355
E35A
E35F
E36C
E3CA
E3D4
E3F0
E4xx

H
For codes that begin with H, see HMC error codes.

#
For codes that begin with a number sign (#), see
“Reference codes that begin with a number sign (#)” on page 838.

(1xxx) System power control network (SPCN) reference codes

The system power control network (SPCN) detected a failure.
1. Look at the four rightmost characters of the SRC from Function 11. These characters are the unit
reference code.
2. Find the unit reference code in the following table.

For details on the Failing Item column entries, see the SPCN Failing Items Detail table.

Table 1. SPCN reference codes:

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
00A0 SPCN BATs in process TWRCARD

No action required. This reference code is logged for information only. If

this reference code is present for more than 1 minute, exchange the failing
items.
00AA Download in process

No action required. This reference code is logged for information only.

00AC Detected AC loss ACMODUL

If system powers on normally or stays powered on after AC power failure,

no replacement of parts may be needed.
00AD Service Processor Reset caused a system power off TWRCARD
00BA The system is running on the Battery Power Unit.

No action required. This reference code is displayed for information only.

00BC Battery Power Unit test is in process.

No action required. This reference code is displayed for information only.

6 System i® and System p®: Reference codes

1xxx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
00CA Thermal calibration in progress
00EF Remote EPO switch is OFF
1500 Detected AC loss PWRSPLY
TWRCARD
Before replacing any parts, verify that the AC input voltage is correct.
1501 Power supply failure PWRSPLY
TWRCARD
1502 Power supply failure PWRSPLY
TWRCARD
CBLALL
1503 Power supply failure PWRSPLY
TWRCARD
1510 Detected AC loss PWRSPLY
TWRCARD
Before replacing any parts, verify that the AC input voltage is correct.
1511 Power supply failure PWRSPLY
TWRCARD
1512 Power supply failure PWRSPLY
TWRCARD
CBLALL
1513 to 1514 Power supply failure PWRSPLY
TWRCARD
1516 No Power Supplies Present PWRSPLY
TWRCARD
The required power supplies are not installed, or if installed, defective.
1517 Power supply failure PWRSPLY
TWRCARD
1520 Detected AC loss PWRSPLY
TWRCARD
Before replacing any parts, verify that the AC input voltage is correct.
1521 Power supply failure PWRSPLY
TWRCARD
1522 Power supply failure PWRSPLY
TWRCARD
CBLALL
1523 to 1524 Power supply failure PWRSPLY
TWRCARD
1526 No Power Supplies Present PWRSPLY
TWRCARD
The required power supplies are not installed, or, if installed, defective.
1527 Power supply failure PWRSPLY
TWRCARD
1530 Detected AC loss PWRSPLY
TWRCARD
Before replacing any parts, verify that the AC input voltage is correct.
1531 Power supply failure PWRSPLY
TWRCARD
1532 Power supply failure PWRSPLY
TWRCARD
CBLALL

Reference codes 7
1xxx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
1533 Power supply failure PWRSPLY
TWRCARD
1611 Regulator 1 Fault PWR1918
TWRCARD
1612 Regulator 1 Communication Fault PWR1918
TWRCARD
1613 Regulator 1 Domain Fault PWR1918
TWRCARD
1621 Regulator 2 Fault PWR1918
TWRCARD
1622 Regulator 2 Communication Fault PWR1918
TWRCARD
1623 Regulator 2 Domain Fault PWR1918
TWRCARD
1631 Regulator 3 Fault PWR1918
TWRCARD
1632 Regulator 3 Communication Fault PWR1918
TWRCARD
1633 Regulator 3 Domain Fault PWR1918
TWRCARD
1B01 Load fault on the +12V bus PWR1900
TWRCARD
1B02 Load fault on the +5V bus PWR1900
TWRCARD
1B03 Load fault on the +3.3V bus PWR1900
TWRCARD
1B04 Load fault on the -12V bus PWR1900
TWRCARD
1B05 Load fault on the +1.8V bus PWR1904
TWRCARD
1B06 Load fault on the +2.5V bus PWR1904
TWRCARD
1B0A Load Fault on the +12V/-12v bus PWR1904
TWRCARD
1B0F, 1C02 Load Fault on the +1.2V bus PWR1904
TWRCARD
1C04 Load Fault on the +1.5V bus PWR1904
TWRCARD
1C06 Load Fault on the 1.8/2.5V bus PWR1904
TWRCARD
1D00 to 1D01 FSP Card SS Fault CARDFLT
1D02 to 1D03 OSC Card SS Fault CARDFLT
1D04 to 1D05 Lightstrip SS Fault CARDFLT
LITSTRP
CABLEH
1D10 MUX Card SS Fault CARDFLT
1D11 to 1D18 IO Hub Card SS Fault CARDFLT

8 System i® and System p®: Reference codes

1xxx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
1D60 RIO/HSL Adapter Card Switch fault SI_CARD
TWRCARD
1D61 to 1D62 Removable Media Planar Switch fault DEVBPLN
TWRCARD
1D63 RIO/HSL Adapter Card Switch fault SI_CARD
TWRCARD
1F01 TMS limit reached - log only
1F02 SPCN trace information saved
2600 to 2601 Power Good Fault PGDPART
2602 Power Good Fault PWR1918
TWRCARD
2603 Power Good Fault PGDPART
2605 to 2609 Power Good Fault PWR1900
TWRCARD
2612 Optical Converter 5V Fault CBLALL
TWRCARD
The SPCN detected a fault on the SPCN card optical converter 5V.
2613 Configuration Requires 200V Input CBLALL

Configuration now requires 200V AC power(both supplies need to be the

same voltage).
2630 to 2632 Regulator Fault PWR1918
TWRCARD
2633 to 2635 Regulator Fault SYSBKPL
TWRCARD
2636 to 2637 Regulator Fault PWR1918
TWRCARD
2638 to 2639 Regulator Fault SYSBKPL
2640 to 2642 Regulator Fault PWR1918
TWRCARD
3100 I2C Bus Controller Communication fault I2CBUS
TWRCARD
3101 I2C Bus 1 Communication fault I2CBUS
TWRCARD
3102 I2C Bus 2 Communication fault I2CBUS
TWRCARD
3103 I2C Bus 3 Communication fault I2CBUS
TWRCARD
3104 I2C Bus 4 Communication fault I2CBUS
TWRCARD
3105 I2C Bus 5 Communication fault I2CBUS
TWRCARD
3106 I2C Bus 6 Communication fault I2CBUS
TWRCARD
3109 I2C Bus Adapter Communication fault I2CBUS
TWRCARD
310A to 310B I2C Bus SPCN VPD Communication fault I2CBUS
TWRCARD

Reference codes 9
1xxx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
3110 I2C Bus DASD Backplane 1 Communication fault I2CBUS
TWRCARD
3111 I2C Bus DASD Backplane 2 Communication fault I2CBUS
TWRCARD
3112 I2C Bus DASD Backplane 3 Communication fault I2CBUS
TWRCARD
3113 I2C Bus Adapter Communication fault I2CBUS
TWRCARD
3114 I2C Bus PCI Backplane Communication fault I2CBUS
TWRCARD
3115 I2C Bus Panel Communication fault I2CBUS
TWRCARD
3116 I2C Bus Fan Local Controller Communication fault I2CBUS
TWRCARD
3118 I2C Bus SPCN VPD Communication fault I2CBUS
TWRCARD
3120 Voltage Adjust Failure SYSBKPL
TWRCARD
3121 I2C Bus 2 Communication fault I2CBUS
TWRCARD
3122 to 3125 I2C Bus SPCN VPD Communication fault I2CBUS
TWRCARD
3200 MUX Hardware Failed HMUX
TWRCARD
Device select mux HW fail drawer1
3201 Device select mux HW fail drawer 2 HMUX
TWRCARD
3202 Device select mux HW fail drawer 3 HMUX
TWRCARD
3203 Device select mux HW fail drawer 4 HMUX
TWRCARD
4201 UPS Reported, Utility Failure On
4203 UPS Reported, Battery Low On
4212 Config ID does not match HW PWR1917
4213 BBU in wrong Location BATRY
4221 BBU Fault BATRY
4222 BBU Comm Fault BATRY
TWRCARD
CBLALL
4225 BBU Expired BATRY
4410 Internal Battery Power Unit Fault BATRY
BATCHGR
Internal Battery Power Unit in the system has failed. TWRCARD
CBLALL
4411 Internal Battery Power Unit Charger Fault BATCHGR
TWRCARD
Internal Battery Power Unit Charger in the system has failed. CBLALL

10 System i® and System p®: Reference codes

1xxx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
4412 Internal Battery Power Unit Charger Fault BATCHGR
BATRY
Internal Battery Power Unit Charger in the system has failed. TWRCARD
CBLALL
4413 Internal Battery Power Unit Charger Fault BATRY
BATCHGR
Internal Battery Power Unit Charger in the system has failed. TWRCARD
CBLALL
4414 Battery Charger Load fault PWROC
BATRY
TWRCARD
CBLALL
4415 Battery Power Unit missing BATRY
TWRCARD
CBLALL
4417 Battery Charger Unit missing BATCHGR
TWRCARD
CBLALL
4600 to 4601 UPS Interface Failure UPSUNIT
TWRCARD
5000 to 5001 FSP fail over failed due to configuration mismatch TWRCARD
7110, 7120 Power supply failure PWRSPLY
TWRCARD
7200 Thermal Sensor Fault AMBTEMP
7201 Ambient temperature is out of range AMBTEMP
7202 Ambient temperature is back in range
7203 Ambient temperature exceeded limit AMBTEMP

The system will shut down in 15 minutes.

7205 Ambient temperature exceeded limit AMBTEMP

The system will shut down in 20 seconds.

7211 Ambient temperature is out of range AMBTMP1

Ambient Temperature is above nominal for CPU performance.

7212 Ambient temperature is back in range AMBTMP2

Ambient Temperature has returned to nominal.

7300 Power supply failure PWRSPLY
TWRCARD
7610 Air Moving Device Fault AIRMOVR
TWRCARD
The Air Moving Device is operating at the wrong speed. Ensure the fans,
and fan tray are fully seated into the fan connectors.
7611 Air Moving Device missing error AIRMOVR
TWRCARD
A problem was detected with an Air Moving Device which can be caused
by an Air Moving Device not being installed. Ensure the fans, and fan tray
are fully seated into the fan connectors. Install Air Moving Device if
missing, replace if already installed.

Reference codes 11
1xxx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
7620 Air Moving Device Fault AIRMOVR
TWRCARD
The Air Moving Device is operating at the wrong speed. Ensure the fans,
and fan tray are fully seated into the fan connectors.
7621 Air Moving Device missing error AIRMOVR
TWRCARD
A problem was detected with an Air Moving Device which can be caused
by an Air Moving Device not being installed. Ensure the fans, and fan tray
are fully seated into the fan connectors. Install Air Moving device if
missing, replace if already installed.
7630 Air Moving Device Fault AIRMOVR
TWRCARD
The Air Moving Device is operating at the wrong speed. Ensure the fans,
and fan tray are fully seated into the fan connectors.
7631 Air Moving Device missing error AIRMOVR
TWRCARD
A problem was dectected with an Air Moving Device which can be caused
by an Air Moving Device not being installed. Ensure the fans, and fan tray
are fully seated into the fan connectors. Install Air Moving Device if
missing, replace if already installed.
7640 Air Moving Device Fault AIRMOVR
TWRCARD
The Air Moving Device is operating at the wrong speed. Ensure the fans,
and fan tray are fully seated into the fan connectors.
7641 Air Moving Device missing error AIRMOVR
TWRCARD
A problem was detected with an Air Moving Device which can be caused
by an Air Moving Device not being installed. Ensure the fans, and fan tray
are fully seated into the fan connectors. Install Air Moving Device if
missing, replace if already installed.
7650 Air Moving Device Fault. AIRMOVR
TWRCARD
Ensure the fans, and fan tray are fully seated into the fan connectors.
7651 Air Moving Device missing error. AIRMOVR
TWRCARD
Ensure the fans, fan tray are fully seated into the fan connectors.
7690 Air Moving Device Fault. AIRMOVR
TWRCARD
Ensure the fans, and fan tray are fully seated into the fan connectors.
7691 Air Moving Device missing error. AIRMOVR
TWRCARD
Ensure the fans, fan tray are fully seated into the fan connectors.
8400 No VPD Found due to Invalid Bypass PWR1917
8402 Unable to Collect VPD VPDPART
TWRCARD
8404 to 8406 Processor Unit VPD Mismatch VPDPART
TWRCARD
8409 No Processor Installed VPDPART
TWRCARD
840D SPCN Configuration mismatch IDPART
TWRCARD
840E SPCN Default Configuration loaded IDPART
TWRCARD

12 System i® and System p®: Reference codes

1xxx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
8410 to 8417 Invalid Processor VPD VPDPART
TWRCARD
8420 to 8427 No Processor VPD VPDPART
TWRCARD
8430 Cable not connected IDPART
TWRCARD
8431 Cable should not be present IDPART
TWRCARD
8432 Secondary unit not present IDPART
TWRCARD
8440 Invalid Dasd backplane PWR1915
8450 to 8451 SPCN Configuration mismatch PWR1918
TWRCARD
8455 to 8456 Power Supply Missing PWRSPLY
TWRCARD
8460 All PWR nodes guarded
8470 to 8477 Processor Unit VPD Mismatch VPDPART
TWRCARD
8700 to 8701 BPC AC Loss PWR2402
8710 to 8711 DCA UART Communication Fault DCA
TWRCARD
SYSBKPL
8720 to 8721 BPC ethernet Communication fault CABLEH
BPC
TWRCARD
8731 BPC critical fault, no present node books powered on CABLEH
NEXTLVL
8732 BPC critical fault, ced cage id mismatch - cabling error CABLEH
NEXTLVL
8733 BPC critical fault, no node books present to power on CABLEH
NEXTLVL
8734 BPA Error collection failed CABLEH
NEXTLVL
8735 BPC/HMC fault, No BPC IP addresses BPC
8740 to 8741 BPC fault, failed to reach standby BPC
8910 External Netfinity Server 3.3V fault ALTMANL
TWRCARD
8920 External Netfinity Server Power Good fault TWRCARD
ALTMANL
8930 Integrated Netfinity Adapter fault TWRCARD
8940 to 8943 External Netfinity Server R485 Communication fault TWRCARD
CBLALL
8A00 IO Power control changed to another system unit

Reference codes 13
1xxx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
9002 Received a bad return code

Partition Firmware has detected a condition that may require attention.

Check error log for other errors that may have been reported at the same
time as this condition was reported. If this SRC persists contact next level
of support.
9012 Address not valid. TWRCARD
CBLALL
LIC command had a frame address that was not valid.

Exchange the SPCN frame-to-frame cables to the failing frame.

9013 Invalid Node Address. TWRCARD
CBLALL
The address in the SPCN command does not match the secondary nodes
assigned address.

Exchange the failing items for the SPCN node reporting the error.
9014 A command has an invalid address mode. AJDG301
TWRCARD
A command from the system unit specified a unit address of D or E or had
a frame address of 00.

Exchange the failing items in the system unit.

9016, 9021 A command to an SPCN node was rejected.

No action required. This reference code is logged for information only.

9022 Addressed Unit not in frame.

The addressed unit does not exist in the addressed frame.

No action required. This reference code is logged for information only.

9023 Addressed Unit exists, but the frame is powered off.

The addressed unit is in a frame that is powered off.

No action required. This reference code is logged for information only.

9024 SPCN Licensed Internal Code not valid.

The Licensed Internal Code in one of the secondary nodes is not valid. The
code will be reloaded.

No action required. This reference code is logged for error analysis only.
9025 SPCN Licensed Internal Code is not valid.

The Licensed Internal Code in one of the frames is not valid. The code will
be reloaded.

No action required. This reference code is logged for error analysis only.
9026 Battery Power Unit is reporting a low charge.

The battery power unit is not charged enough to run a test.

No action required. This reference code is logged for information only.

9027 Battery Power Unit is defective.

No action required. This reference code is logged for information only.

14 System i® and System p®: Reference codes

1xxx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
9028 SPCN Licensed Internal Code is not valid.

The Licensed Internal Code in the primary node is not valid. The code will
be reloaded.

No action required. This reference code is logged for error analysis only.
9029 SPCN VPD Damaged TWRCARD

The VPD record in the EEPROM has bad data.

Exchange the failing items for the node reporting the failure.
902C Battery Power Unit test was aborted.

The battery power unit test was aborted.

No action required. This reference code is logged for information only.

902D Addressed frame is not in SPCN configuration table.

The addressed frame is not in the SPCN configuration table.

No action required. This reference code is logged for information only.

9031 Frame-to-Frame Communications Failure

The SPCN detected a BCC error on a transmission from another frame. The
transmission is attempted again.

No action required. This reference code is logged for error analysis only.
9032 SPCN Communications Failure, unit to rack.

The frame detected a BCC error on a transmission from a secondary node

to the frame. The transmission is attempted again.

No action required. This reference code is logged for error analysis only.
9033 SPCN Communications Failure, rack to unit.

A secondary node detected a BCC error on a transmission from the frame.

The transmission is attempted again.

No action required. This reference code is logged for error analysis only.
9034 Unsupported Packet Size

The receiving node detected a packet exceeding 70 bytes. The frame can
also return this code if a secondary node returns more than 10 bytes to a
PAS command.

No action required. This reference code is logged for error analysis only.
9035 Secondary SPCN node timeout.

A secondary SPCN node did not respond to a command. The command

was attempted again and failed.

No action required. This reference code is logged for error analysis only.
9036 Frame Timeout

One or more frames did not respond to a command. The command is

attempted again.

No action required. This reference code is logged for error analysis only.

Reference codes 15
1xxx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
903B Invalid Packet Length for data sent.

The number of bytes sent or received does not match the number of bytes
specified in the command.

No action required. This reference code is logged for error analysis only.
9041 Invalid Load Type AJDG301
TWRCARD
The down load was successful, but the wrong type of Licensed Internal
Code was loaded. The operation was attempted again but was not
successful. Exchange the failing items for the node reporting the fault.
9042 EEPROM Failure TWRCARD

The EEPROM in an SPCN node cannot be written successfully.

Exchange the SPCN node reported in the failure.

9043 Download Failure TWRCARD

The Licensed Internal Code download to an SPCN node was completed

but was not successful.

Exchange the failing SPCN node.

9046 QDS Packet Sequence Error TWRCARD

The Packet Sequence number is wrong. The download was stopped.

9047 QDS Block Sequence Error TWRCARD

The Block Sequence number is wrong. The download was stopped.

9048 The SPCN ROS and EEPROM LIC is not compatable. TWRCARD
AJDG301
The LIC levels in the nodes ROS and EEPROM are not compatible.

Exchange the failing items for the failing node.

9080 Undefined Status Code TWRCARD
BACKPLN
An SPCN node returned an unknown status code.

Exchange the failing SPCN node.

90F0 A frame was dropped from the SPCN configuration. PWR1907
TWRCARD
A frame was dropped from the SPCN configuration. This is usually caused CBLALL
by a loss of ac power or a problem with the frame-to-frame cable.
90F1 A frame was added to the SPCN configuration.

No action required. This reference code is logged for information only.

90F2 Slave disappeared

A slave was dropped from the SPCN configuration. This is usually caused
by a loss of ac power. (This is for a 24 inch rack)
90F3 Slave reappeared
9101 VLIC-SPCN Timeout TWRCARD
CTLPNL
A Licensed Internal Code timeout occurred. The SPCN failed to respond to SVCPROC
a Licensed Internal Code command.

16 System i® and System p®: Reference codes

1xxx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
9102 Assign Permanent Address command failure TWRCARD

A node failed to perform an Assign Permanent Address command.

9103 Download Initialize Timeout TWRCARD

An SPCN node failed to enter the download state after an Initialize for
Download command.

Exchange the failing SPCN node.

9104 Download Completion Timeout TWRCARD

An SPCN node failed to leave the download state.

Exchange the failing SPCN node.

9105 Load Damaged Timeout TWRCARD

An SPCN node failed to enter the operational state.

Exchange the failing SPCN node.

9106 An SPCN LID was not found.

No action required. This reference code is logged for information only.

9107 An SPCN microcode download is required.

No action required. This reference code is logged for error analysis only.
9108 A status change occured in one of the SPCN nodes.

No action required. This reference code is logged for information only.

9109 Licensed Internal Code part number is not correct. TWRCARD

The AROS part number field was not updated to the correct level after the
system attempted to load new Licensed Internal Code.
910A RIO Download Required
910B Maximum number of retrys exceeded
9110 Battery Power Unit capacity test failed. BATRY

The battery power unit was not able to pass the capacity test.
9111 SPCN is too large for VLIC. AJDG301

There are more nodes in the network than VLIC can service.
9112 Primary SPCN node is reporting load damaged. TWRCARD

The Licensed Internal Code for the primary SPCN node is damaged. The
reload failed because the code could not be found.
9113 Secondary SPCN node is reporting load damaged. TWRCARD

The Licensed Internal Code for the secondary SPCN node is damaged. The
reload failed because the code could not be found.
9114 Frame SPCN node is reporting load damaged. TWRCARD

The Licensed Internal Code for a SPCN node is damaged. The reload failed
because the code could not be found.

Reference codes 17
1xxx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
9115 SPCN Command rejected by the Service Processor.

The service processor rejected an SPCN command from the Licensed

Internal Code.

No action required. This reference code is logged for information only.

9116 SPCN - Control Panel interface failure.

The SPCN to control panel interface is not working.

9117 SPCN - Control Panel interface is now working.

The SPCN to control panel interface is now working.

No action required. This reference code is logged for information only.

9118 PHYP out of memory AJDG301
9119 NVRAM Write Failed TWRCARD
911A Too many racks attached

Reduce the number of racks to maximum configuration on the system.

911B SPCN CEC node code failure AJDG301
911C Two nodes have same VPD VPDPART
911D RIO Download Failure TWRCARD
SI_CARD
911E Temporary VPD written TWRCARD
911F CEC not found TWRCARD
9120 Duplicate backplane VPD SYSBKPL
9131 Invalid XM Return Code
9132 Node contains temporary VPD
9133 Bad PCI Correlation Problem CBLALL

PCI bus not matched

9134 PCI bus VPD error

Check Error Log for B700 xxxx Reference Codes.

9135 Open SPCN Loop CBLALL
TWRCARD
9136 The manually started download was interrupted
9137 Bad PCI Correlation Problem CBLALL

SPCN node not matched

9138 Bad Location Code CBLALL
9139 Open SPCN loop resolved
913A RIO download sent retry
91DD All SPCN Downloads Complete
91DE RIO Download Complete
91FB Write VPD on next IPL

18 System i® and System p®: Reference codes

1xxx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
9212 Frame Address field not valid. TWRCARD

A Licensed Internal Code command had a frame address that is not valid.

Exchange the failing items for the failing node.

9213 Invalid Address status, secondary node. TWRCARD

The address in the SPCN command does not match the assigned address of
the secondary node.

Exchange the failing items for the failing node.

9214 Invalid Address Mode status TWRCARD
AJDG301
Invalid Address Mode occurred during Frame Command processing.
9215 Invalid Frame Command status TWRCARD
AJDG301
Invalid Frame Command occurred during Frame Command processing.
921B System Unit SPCN Port Fault status. TWRCARD
AJDG301
System Unit Port Fault occurred during Command processing.
922B Address Unassigned status TWRCARD
AJDG301
A secondary node has no address assigned during Command processing.
9231 Frame-to-Frame Communications Failure TWRCARD
CBLALL
A frame-to-frame communications failure occurred during STF processing.
9232 Intrarack Communications Failure TWRCARD
CBLALL
An SPCN secondary node to frame communications failure occurred
during Command processing.
9233 Intrarack Communications Failure TWRCARD
CBLALL
An SPCN frame to secondary node communications failure occurred
during Command processing.
9234 Unsupported Packet Size status TWRCARD
CTLPNL
Unsupported Packet Size occurred during STF and Secondary Node SVCPROC
Command processing.
9235 SPCN Secondary Node Timeout status TWRCARD
AJDG301
An SPCN Secondary Node Timeout occurred during Command processing. CBLALL

If the failing secondary node is in a 9337, go to the “Analyzing Problems”

section in the 9337 Disk Array Service Information manual.
9236 Frame Timeout status TWRCARD
CBLALL
An SPCN Frame Node Timeout occurred during Network post processing.
9238 Secondary Node Fault TWRCARD
AJDG301
An SPCN Secondary Node Fault occurred during Command processing.
9239 Frame Node Fault TWRCARD
AJDG301
An internal error in the SPCN frame node prevents the running of a Frame
command.

Reference codes 19
1xxx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
923A ASA Failure TWRCARD
AJDG301
The frame address returned by a secondary node does not match the
address of the frame.
923B Invalid Packet Length for data sent. AJDG301
TWRCARD
An Invalid Packet Length occurred for data exchanged.
9280 Response Stack Overflow CBLALL
AJDG301
Too many responses were received during System Frame command TWRCARD
processing.
9281 Response Overrun CBLALL
AJDG301
Response Overrun occurred during System Frame processing. TWRCARD
9282 No Free Entries CBLALL
AJDG301
No free entries were found during System Frame processing. TWRCARD
9283 ARA Failure TWRCARD
AJDG301
An Assign Frame Address Failure occurred during ARA Preprocessing.
9284 Undefined status TWRCARD
AJDG301
Undefined Status occurred during Frame or STF processing.
9285 BCC Fault TWRCARD

A BCC Error was detected during Network post processing.

9286 Length Check Error. TWRCARD
AJDG301
Length Check occurred during SPCN post processing.
9287 Undefined status TWRCARD
AJDG301
Undefined Status occurred during Command processing.
9288 Configuration Error TWRCARD
AJDG301
A configuration error was detected during System Frame processing.
9289 Invalid Packet Length for data sent. AJDG301
TWRCARD
Invalid Packet Length occurred for data exchanged.
C62E SPCN Network Fault TWRCARD
CBLALL
An SPCN frame-to-frame communication failure was detected.
CB15 EEPROM Failure TWRCARD

Table 2. SPCN failing items:

Failing Item Description Document Description

ACMODUL AC Module See the service documentation for instructions.
AIRMOVR Fan and Blower assemblies See the service documentation for instructions.
AJDG301 Vertical Licensed Internal Code. Service Functions; APAR or LICTR
ALTMANL Alternate Manual Required See the service documentation for instructions.
AMBTEMP Ambient temperature exceeded limit See the service documentation for instructions.

20 System i® and System p®: Reference codes

1xxx

Failing Item Description Document Description

AMBTMP1 Ambient temperature too high See the service documentation for instructions.
AMBTMP2 Ambient temperature is within range See the service documentation for instructions.
BACKPLN Back Plane Unit See the service documentation for instructions.
BATCHGR Battery Power Unit Charger See the service documentation for instructions.
BATRY Battery Power Unit See the service documentation for instructions.
BPC BPC Fault See the service documentation for instructions.
CABLEH cable all for 24 inch unit See the service documentation for instructions.
CARDFLT Card Fault See the service documentation for instructions.
CBLALL Cable Failure See the service documentation for instructions.
CTLPNL Control Panel See the service documentation for instructions.
DCA DCA fault See the service documentation for instructions.
DEVBPLN Device backplane See the service documentation for instructions.
HMUX MUX Hardware fail See the service documentation for instructions.
I2CBUS I2C Bus Part See the service documentation for instructions.
IDPART Vital Product Data Parts See the service documentation for instructions.
LITSTRP Litestrip See the service documentation for instructions.
NEXTLVL Call next level of support See the service documentation for instructions.
PGDPART Power Good Part See the service documentation for instructions.
PWR1900 Power-PIP 1900 See the service documentation for instructions.
PWR1902 Power-PIP 1902 See the service documentation for instructions.
PWR1903 Power-PIP 1903 See the service documentation for instructions.
PWR1904 Power-PIP 1904 See the service documentation for instructions.
PWR1906 Power-PIP 1906 See the service documentation for instructions.
PWR1907 Power-PIP 1907 INFORMATION
PWR1908 Power-PIP 1908 See the service documentation for instructions.
PWR1909 Power-PIP 1909 See the service documentation for instructions.
PWR1911 Power-PIP 1911 See the service documentation for instructions.
PWR1915 Power-PIP 1915 See the service documentation for instructions.
PWR1916 Power-PIP 1916 See the service documentation for instructions.
PWR1917 Power-PIP 1917 See the service documentation for instructions.
PWR1918 Power-PIP 1918 See the service documentation for instructions.
PWR2402 Power 2402 for 24 inch unit See the service documentation for instructions.
PWROC Power Supply overcurrent See the service documentation for instructions.
PWRSPLY Power Supply See the service documentation for instructions.
SI_CARD System Interconnect controller See the service documentation for instructions.
SVCPROC Service Processor Card See the service documentation for instructions.
SYSBKPL System unit backplane See the service documentation for instructions.
TWRCARD Card enclosure or backplane See the service documentation for instructions.
UPSUNIT UPS unit part See the service documentation for instructions.
VPDPART VPD Communication Part See the service documentation for instructions.

Reference codes 21
1400

(1400) Bulk power subsystem reference codes

For use by service providers.

The bulk power subsystem reference codes are issued from the 24–inch power subsystem and are meant
to be serviced through the Service focal point application on the Hardware Management Console (HMC).
This list of (1400) bulk power subsystem reference codes is included here for informational use only.

actions before exchanging Failing
Reference Code Items Failing Item
3215 BPC-B side detects that IBF-3B is IBF-3B
defective. BPR-3B
CBL-IBF3B
BPC-B
BPE-BOARD-B
3218 BPC-A side detects that IBF-3A is BPR-3A
disconnected. IBF-3A
CBL-IBF3A
BPC-A
BPE-BOARD-A
3219 BPC-B side detects that IBF-3B is BPR-3B
disconnected. IBF-3B
CBL-IBF3B
BPC-B
BPE-BOARD-B
321A BPA-A side detects that IBF-3A has IBF-3A
dropped below a usable level. BPR-3A
BPC-A
BPE-BOARD-A
321B BPA-B side detects that IBF-3B has IBF-3B
dropped below a usable level. BPR-3B
BPC-B
BPE-BOARD-B
321C BPA-A side detects that IBF-3A has IBF-3A
been charged to normal capcity.
321D BPA-B side detects that IBF-3B has IBF-3B
been charged to normal capcity.
4001 The Auto-Code-Download (ACDL) of
the power subsystem encountered an
error.
4002 The frame MTMS was not resolved
by the time the BPC reached HMC
standby. Contact your next level of
support for assistance.
4003 The BPC found duplicate Mailbox IP
addresses on Network A. Contact
your next level of support for
assistance.
4004 The BPC found duplicate Mailbox IP
addresses on Network B. Contact
your next level of support for
assistance.
4005 A DHCP address was not assigned
on Network A. Contact your next
level of support for assistance.
8130 CAGE P/T Fru recovery.
8131 The UEPO switch has been used-This
is an informational SRC.
8132 A send secure vpd command was
received - Informational SRC.

Reference codes 43
1400

Description/Action Perform all

actions before exchanging Failing
Reference Code Items Failing Item
8133 A TMS (60) was received -
Informational SRC.
8134 This contains an ACDL log -
Informational SRC.
8135 There has been an internal bulk
power software error.

(1750, 2105, 2107) Disk unit reference codes

1. If the error is reported on the control panel, the unit reference code is characters 5 through 8 of the
top 16 character line of function 11. If the error is reported on the console, the unit reference code is
the 4 rightmost characters of word 1.
2. Find the unit reference code in the following table.

For more on the Failing Item column entries, see Table 2. Disk unit failing items details, which follows
the reference code table below.

Table 1. (1750, 2105, 2107) Disk unit reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
3002 Addressed device is not responding FCPORT
FCDEV
FCIOA
FCINTF
OPT_CLN
3010 Disk device returned wrong response to IOP FCDEV
FCIOA
OPT_CLN
3020 Storage subsystem configuration error FCDEV
FCIOA
If an MES is being installed, verify the configuration. OPT_CLN
3029 A device replacement has occurred

No action required. This reference code is logged for information only.

3100 Fibre Channel interface error occurred FCINTF
FCDEV
FCIOA
OPT_CLN
3109 IOP timed out a disk command FCDEV
FCINTF
FCIOA
OPT_CLN
34FF Format in progress

The device indicated that a format is in progress. When the format is

complete, the device should be useable. No action is required. This
reference code is logged for information only.
FFF3 Disk media format bad FCDEV
FFF4 Disk device problem FCDEV
FFF5 Disk sector read error FCDEV

44 System i® and System p®: Reference codes

1750, 2105, 2107

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
FFF6 Disk device detected recoverable error FCDEV

A disk unit service action is recommended only if the Service Action Log
contains an entry for this reference code. For more information, see Using
the Service Action Log.
FFFA Disk device wrong response was recovered by the IOP FCDEV
FCIOA
A disk unit service action is recommended only if the Service Action Log OPT_CLN
contains an entry for this reference code. For more information, see Using
the Service Action Log.
FFFE Temporary Fibre Channel interface error FCINTF
FCDEV
A disk unit service action is recommended only if the Service Action Log FCIOA
contains an entry for this reference code. For more information, see Using OPT_CLN
the Service Action Log.

Table 2. Disk Unit failing items details

Failing Item Description Document Description

FCDEV Fibre Channel device See the service documentation for instructions.
FCINTF Fibre Channel interface See the service documentation for instructions.
FCIOA Fibre Channel IOA See the service documentation for instructions.
FCPORT Port not operational See the service documentation for instructions.
IOP I/O processor card See the service documentation for instructions.
OPT_CLN Fiber optic cleaning kit See the service documentation for instructions.

(180A, 283C, 283D, 283F, 28B9, 28CB, 28CC, 28D2, 28DB, 28DF, 506D,
506E) Device backplane reference codes
1. If the error is reported on the control panel, the unit reference code is characters 5 through 8 of the
top 16 character line of function 11. If the error is reported on the console, the unit reference code is
the 4 rightmost characters of word 1.
2. Find the unit reference code in the following table.

Attention: The 673x is a read cache. Perform all actions required for 673x as a disk drive and logic card
except where separate 673x cache instructions are provided.

For more on the Failing Item column entries, see Table 2. Device backplane failing items details, which
follows the reference code table below.

Table 1. (180A, 283C, 283D, 283F, 28B9, 28CB, 28CC, 28D2, 28DB, 28DF, 506D, 506E) Device backplane
reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
1511 A non-fatal error occurred on power supply 1 DISKPWR
DISKFAN
FI01106
DEVBPLN

Reference codes 45
180A, 283C, 283D, 283F, 28B9, 28CB, 28CC, 28D2, 28DB, 28DF, 506D, 506E

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
1515 A fatal error occurred on power supply 1 DISKPWR
DISKFAN
FI01106
DEVBPLN
1521 A non-fatal error occurred on power supply 2 DISKPWR
DISKFAN
FI01106
DEVBPLN
1525 A fatal error occurred on power supply 2 DISKPWR
DISKFAN
FI01106
DEVBPLN
3002 Addressed device backplane failed to respond to selection DEVBPLN
STORIOA
FI01140
FI01106
3109 I/O adapter timed out a device backplane command DEVBPLN
STORIOA
FI01140
FI01106
7611 A fatal error occurred on redundant fan 1 DISKFAN
7614 A fatal error occurred on fan 1 DISKFAN
7621 A fatal error occurred on redundant fan 2 DISKFAN
7624 A fatal error occurred on fan 2 DISKFAN
7631 A fatal error occurred on redundant fan 3 DISKFAN
7634 A fatal error occurred on fan 3 DISKFAN
8401 Removable media power fault DEVBPLN
8404 System log entry only, no service action required
FFF4 Device backplane problem DEVBPLN
STORIOA
FI01140
FI01106

Table 2. Device backplane failing items details

Failing Item Description Document Description

08F5352 Token-ring network adapter Repair and Parts; removal and installation
procedures
08F5361 Communications input/output processor card Repair and Parts; removal and installation
procedures
17G2504 Tape Unit Repair and Parts; removal and installation
procedures
21F1511 Internal power cable Repair and Parts; removal and installation
procedures
21F1512 Internal power cable Repair and Parts; removal and installation
procedures
21F1512 Internal power cable Repair and Parts; removal and installation
procedures

46 System i® and System p®: Reference codes

180A, 283C, 283D, 283F, 28B9, 28CB, 28CC, 28D2, 28DB, 28DF, 506D, 506E

Failing Item Description Document Description

21F1513 Internal signal cable Repair and Parts; removal and installation
procedures
21F1514 Internal power cable Repair and Parts; removal and installation
procedures
21F1519 Internal signal cable Repair and Parts; removal and installation
procedures
21F1530 Card enclosure Repair and Parts; removal and installation
procedures
21F1687 Diskette adapter card Repair and Parts; removal and installation
procedures
21F1688 Multiple function I/O processor card Repair and Parts; removal and installation
procedures
21F1689 Multiple function I/O processor card Repair and Parts; removal and installation
procedures
21F2070 Bus cable Repair and Parts; removal and installation
procedures
21F3986 Tape I/O processor card Repair and Parts; removal and installation
procedures
21F4383 Multiple function I/O processor card Repair and Parts; removal and installation
procedures
21F4493 Ethernet controller card Repair and Parts; removal and installation
procedures
21F4579 Disk drive logic card Repair and Parts; removal and installation
procedures
21F4863 Magnetic storage device IOP card Repair and Parts; removal and installation
procedures
21F4867 Communication adapter Repair and Parts; removal and installation
procedures
21F4868 Communication adapter Repair and Parts; removal and installation
procedures
21F4869 Token-ring controller card Repair and Parts; removal and installation
procedures
21F4882 Diskette adapter card Repair and Parts; removal and installation
procedures
21F4882 Diskette adapter card Repair and Parts; removal and installation
procedures
21F5620 Disk unit power regulator Repair and Parts; removal and installation
procedures
21F5620 Disk unit power regulator Repair and Parts; removal and installation
procedures
21F5650 AC Module Repair and Parts; removal and installation
procedures
21F5680 AC Module Repair and Parts; removal and installation
procedures
21F5772 Control panel Repair and Parts; removal and installation
procedures
21F5774 External signal cable Repair and Parts; removal and installation
procedures

Reference codes 47
180A, 283C, 283D, 283F, 28B9, 28CB, 28CC, 28D2, 28DB, 28DF, 506D, 506E

Failing Item Description Document Description

21F5774 Cable assembly Repair and Parts; removal and installation
procedures
21F5861 Tape Unit Repair and Parts; removal and installation
procedures
21F8566 Tape Unit Repair and Parts; removal and installation
procedures
21F8633 Tape Unit Repair and Parts; removal and installation
procedures
21F8719 Tape Unit Repair and Parts; removal and installation
procedures
21F8872 Cable Carrier Repair and Parts; removal and installation
procedures
21F8890 D/SE Module Repair and Parts; removal and installation
procedures
21F9208 ISDN adapter card Repair and Parts; removal and installation
procedures
21F9215 Power regulator card Repair and Parts; removal and installation
procedures
21F9586 Cable assembly Repair and Parts; removal and installation
procedures
21F9907 Cable assembly Repair and Parts; removal and installation
procedures
21F9937 Cable assembly Repair and Parts; removal and installation
procedures
21F9951 Tape Unit Repair and Parts; removal and installation
procedures
21F9987 Tape unit IOP card Repair and Parts; removal and installation
procedures
2452557 Fan 9346 Service Guide; Installation and Removal,
SY31-0688
26F5028 Communication adapter Repair and Parts; removal and installation
procedures
375892 Power cord; U.S.A., Asia-Pacific group,
Americas group
4234002 Test diskette (8 inch) System operation information
46F4115 Ethernet network adapter card Repair and Parts; removal and installation
procedures
46F4239 Token-ring network adapter Repair and Parts; removal and installation
procedures
55F5199 Disk drive logic card Repair and Parts; removal and installation
procedures
55F5209 Disk drive and logic card Repair and Parts; Recovery Procedures
59X4718 Communications input/output processor card Repair and Parts; removal and installation
procedures
59X4723 Tape unit IOP card Repair and Parts; removal and installation
procedures
59X4723 Tape I/O processor card Repair and Parts; removal and installation
procedures

48 System i® and System p®: Reference codes

180A, 283C, 283D, 283F, 28B9, 28CB, 28CC, 28D2, 28DB, 28DF, 506D, 506E

Failing Item Description Document Description

59X4723 Token-ring network adapter Repair and Parts; removal and installation
procedures
59X4819 Multiple function I/O processor card Repair and Parts; removal and installation
procedures
6369759 Test diskette (5-1/4 inch) System operation information
6369881 Diskette unit Repair and Parts; removal and installation
procedures
6462385 Power cord; Europe, Mid-East, Asia
6495268 External signal cable 9346 Service Guide; Installation and Removal,
SY31-0688
72X5631 Terminating plug Repair and Parts; removal and installation
procedures
72X5631 Terminating plug 9346 Service Guide; Installation and Removal,
SY31-0688
72X5631 Terminating plug Repair and Parts; removal and installation
procedures
72X6361 Diskette unit Repair and Parts; removal and installation
procedures
72X6374 Work station attachment Repair and Parts; removal and installation
procedures
72X6385 Magnetic storage device IOP card Repair and Parts; removal and installation
procedures
72X6386 Diskette adapter card Repair and Parts; removal and installation
procedures
72X6387 Communications I/O processor card Repair and Parts; removal and installation
procedures
72X6388 Communications adapter card Repair and Parts; removal and installation
procedures
72X6389 Multiple interface adapter Repair and Parts; removal and installation
procedures
72X6390 Communications adapter card Repair and Parts; removal and installation
procedures
72X6391 Token-ring network adapter Repair and Parts; removal and installation
procedures
73F8987 Disk drive and logic card Repair and Parts; Recovery Procedures
73F8994 Disk drive logic card Repair and Parts; removal and installation
procedures
73F9138 Planar board Repair and Parts; removal and installation
procedures
73F9139 Planar board Repair and Parts; removal and installation
procedures
73F9166 Planar board Repair and Parts; removal and installation
procedures
73F9193 Power regulator card Repair and Parts; removal and installation
procedures
73F9232 Cable assembly Repair and Parts; removal and installation
procedures

Reference codes 49
180A, 283C, 283D, 283F, 28B9, 28CB, 28CC, 28D2, 28DB, 28DF, 506D, 506E

Failing Item Description Document Description

73F9244 Disk unit power regulator Repair and Parts; removal and installation
procedures
73F9267 ASCII work station IOP card Repair and Parts; removal and installation
procedures
73F9290 Control panel Repair and Parts; removal and installation
procedures
73F9290 Control panel Repair and Parts; removal and installation
procedures
73F9345 Tape Unit Repair and Parts; removal and installation
procedures
73F9393 Tape Unit Repair and Parts; removal and installation
procedures
74F1541 Card enclosure Repair and Parts; removal and installation
procedures
74F1542 Card enclosure Repair and Parts; removal and installation
procedures
74F1543 Card enclosure Repair and Parts; removal and installation
procedures
74F1544 Card enclosure Repair and Parts; removal and installation
procedures
74F1649 Tape Unit Repair and Parts; removal and installation
procedures
74F1760 DC Bulk Module Repair and Parts; removal and installation
procedures
74F2201 Multiple function I/O processor card Repair and Parts; removal and installation
procedures
74F2232 Multiple function I/O processor card Repair and Parts; removal and installation
procedures
79X3795 Terminating plug Repair and Parts; removal and installation
procedures
8266352 Power supply 9346 Service Guide; Installation and Removal,
SY31-0688
85F7295 Multiple function I/O processor card Repair and Parts; removal and installation
procedures
85F7305 Multiple function I/O processor card Repair and Parts; removal and installation
procedures
85F7405 Base power supply Repair and Parts; removal and installation
procedures
85F7418 Cable assembly Repair and Parts; removal and installation
procedures
85F7646 Magnetic storage device IOP card Repair and Parts; removal and installation
procedures
85F7846 Terminating plug Repair and Parts; removal and installation
procedures
85F9785 Control panel Repair and Parts; removal and installation
procedures
85F9840 Internal signal cable Repair and Parts; removal and installation
procedures

50 System i® and System p®: Reference codes

180A, 283C, 283D, 283F, 28B9, 28CB, 28CC, 28D2, 28DB, 28DF, 506D, 506E

Failing Item Description Document Description

85F9845 Internal power cable Repair and Parts; removal and installation
procedures
92X3030 Feature power supply Repair and Parts; removal and installation
procedures
92X3080 Disk unit power regulator Repair and Parts; removal and installation
procedures
92X4041 Diskette unit Repair and Parts; removal and installation
procedures
92X4044 Cable assembly Repair and Parts; removal and installation
procedures
92X4091 Cable assembly Repair and Parts; removal and installation
procedures
92X4143 Planar board Repair and Parts; removal and installation
procedures
92X6551 Planar board Repair and Parts; removal and installation
procedures
92X7512 Flex cable 9346 Service Guide; Installation and Removal,
SY31-0688
92X7514 Internal tape unit signal cable 9346 Service Guide; Installation and Removal,
SY31-0688
92X7515 Internal signal cable 9346 Service Guide; Installation and Removal,
SY31-0688
92X7516 Internal power cable 9346 Service Guide; Installation and Removal,
SY31-0688
93X0901 Disk drive logic card Repair and Parts; removal and installation
procedures
93X0911 Disk drive and logic card Repair and Parts; Recovery Procedures
93X2520 Disk drive and logic card Repair and Parts; Recovery Procedures
93X2701 I/O processor card Repair and Parts; removal and installation
procedures
93X2730 9346 IOP card Repair and Parts; removal and installation
procedures
93X2777 I/O processor card Repair and Parts; removal and installation
procedures
A0B00E1 Licensed Internal Code for programmable tape Service Functions; APAR or LICTR
unit
AJDG301 Vertical Licensed Internal Code Service Functions; APAR or LICTR
AJEDA00 I/O processor Licensed Internal Code Service Functions; APAR or LICTR
AJEDA00 I/O processor Licensed Internal Code Service Functions; APAR or LICTR
AJEH901 I/O processor Licensed Internal Code Service Functions; APAR or LICTR
AJGJQ01 I/O processor Licensed Internal Code Service Functions; APAR or LICTR
AJSLC01 I/O processor Licensed Internal Code Service Functions; APAR or LICTR
AJSLC01 I/O processor Licensed Internal Code Service Functions; APAR or LICTR
BACKPLN Card enclosure or backplane See the service documentation for instructions.
CMPRES1 Compressed device and compression IOA are See the service documentation for instructions.
not compatible

Reference codes 51
180A, 283C, 283D, 283F, 28B9, 28CB, 28CC, 28D2, 28DB, 28DF, 506D, 506E

Failing Item Description Document Description

DEVBPLN Device backplane See the service documentation for instructions.
DEVTERM Device terminator See the service documentation for instructions.
DISKDRV Disk drive and logic card See the service documentation for instructions.
DISKDRV Disk drive and logic card See the service documentation for instructions.
DISKDRV Disk drive and logic card See the service documentation for instructions.
DISKDRV Disk drive and logic card See the service documentation for instructions.
DISKDRV Disk drive and logic card See the service documentation for instructions.
DISKDRV Disk drive and logic card See the service documentation for instructions.
DISKDRV Disk drive and logic card See the service documentation for instructions.
DISKFAN Fan assembly See the service documentation for instructions.
DISKLC Disk drive logic card See the service documentation for instructions.
DISKLC Disk drive logic card See the service documentation for instructions.
DISKLC Disk drive logic card See the service documentation for instructions.
DISKLC Disk drive logic card See the service documentation for instructions.
DISKLC Disk drive logic card See the service documentation for instructions.
DISKLC Disk drive logic card See the service documentation for instructions.
DISKLC Disk drive logic card See the service documentation for instructions.
DISKPWR Power Supply See the service documentation for instructions.
DISKTRY Disk unit tray See the service documentation for instructions.
DISKTRY Disk unit tray See the service documentation for instructions.
DISKTRY Disk unit tray See the service documentation for instructions.
DISKTRY Disk unit tray See the service documentation for instructions.
DISKTRY Disk unit tray See the service documentation for instructions.
DISKTRY Disk unit tray See the service documentation for instructions.
DISKTRY Disk unit tray See the service documentation for instructions.
MSEDMED Defective diskette System operation information
MSETCAR Defective tape or damaged cartridge System operation information
MSETFOR The data format is incorrect; the tape cannot be System operation information
read
MSETMED Defective removable media System operation information
STORIOA Storage I/O adapter See the service documentation for instructions.
SVCDOCS Customer engineer directed to system problem See the service documentation for instructions.
analysis
USEUSER System Operator/User System operation information

(2058) Reference codes

Find the unit reference code in the following table. For more on the Failing Item column entries, see Table
2. Failing items details, which follows the reference code table below.

Table 1. (2058) Reference codes

52 System i® and System p®: Reference codes

2058

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
B990 I/O adapter hardware error detected IOA
FI00130
IOP
MA_BRDG

Table 2. Failing items details

Failing Item Description Document Description

IOA I/O adapter card See the service documentation for instructions.
IOP I/O processor card See the service documentation for instructions.
MA_BRDG Multi-adapter bridge See the service documentation for instructions.

(20A8, 20Dx, 20EE, 20FF, 2102, 220x, 25Ax, 25Cx, 2602, 2803, 2B2x)
Model 185 and A50 reference (error) codes
Use the following tables to find the system reference code (SRC) for your model 185 or A50:
v 20A8 xxxx: The firmware could not perform a network boot of the system
v 20Dx xxxx: A hardware problem caused a firmware failure, or firmware detected a hardware failure
v 20EE xxxx: One of the following problems might have occurred:
– The system detected a problem in the firmware
– The system did not find an operating system on the devices specified in the boot list
– The system detected a problem in the com port settings
– The system encountered a problem when installing the firmware image
v 20FF xxxx: The system detected a problem when the firmware was collecting VPD
v 2102 xxxx: The system detected a problem with a USB-attached CD-ROM drive
v 220x xxxx: The system detected a failure in a communications adapter
v 25Ax xxxx: The system encountered failures because of a problem in NVRAM
v 25Cx xxxx: The system detected a problem in one or more memory DIMMs.
v 2602 xxxx: The system detected a problem with the microcode on a PCI adapter
v 2803 xxxx: The system detected a problem with the time-of-day clock
v 2B2x xxxx: The system encountered a hardware failure in a processor

Table 1. (20A8) Model 185 and A50 reference (error) codes

Reference Code Description/Action Perform all actions before Failing Item

exchanging Failing Items
20A80000 Insufficient information to boot.

Verify that the network addresses on the server

and gateway are correct.
20A80001 Client IP address is already in use by another
network device.

Verify that the network addresses on the server

and gateway are correct.
20A80002 Cannot get gateway IP address.

Verify that the network addresses on the server

and gateway are correct.

Reference codes 53
20A8, 20Dx, 20EE, 20FF, 2102, 2200, 25Ax, 25Cx, 2602, 2803, 2B2x

Reference Code Description/Action Perform all actions before Failing Item

exchanging Failing Items
20A80003 Cannot get server hardware address.

Verify that the network addresses on the server

and gateway are correct.
20A80004 Bootp failed. Do the following:
1. Verify that the bootp server is configured
correctly for this client.
2. Check the network connections, then retry
the operation.
20A80005 File transmission (TFTP) failed. Do the
following:
1. Verify that the bootp server is configured
correctly for this client.
2. Check the network connections, then retry
the operation.
20A80006 Boot image too large. Do the following:
1. Verify that the bootp server is configured
correctly for this client.
2. Check the network connections, then retry
the operation.

Table 2. (20Dx) Model 185 and A50 reference (error) codes

Reference Code Description/Action Perform all actions before Failing Item

exchanging Failing Items
20D0000F Self-test failed on device. The error or location SYSBKP2
code information may not be available. Do the
following:
1. If a location code is specified, replace the
device at that location.
2. Replace the system backplane.
20D00010 Selftest failed on device. Cannot locate package. SYSBKP2
Do the following:
1. If a location code is reported with the error,
replace the device at that location code.
2. Check for system firmware updates, and
apply if available.
3. Replace the system backplane.
20D00011 RTAS attempt to allocate memory failed. Do the SYSBKP2
following:
1. Check for system firmware updates, and
apply if available.
2. Replace the system backplane.
20D008xx Failure to access VPD data, where xx is: SYSBKP2
xx Description
-------------------
0E, 0F Machine type or model
10, 11 System serial number
16, 17 Universal un

54 System i® and System p®: Reference codes

20A8, 20Dx, 20EE, 20FF, 2102, 2200, 25Ax, 25Cx, 2602, 2803, 2B2x

Reference Code Description/Action Perform all actions before Failing Item

exchanging Failing Items
20D00900 Failed to generate universal unique ID (UUID) SYSBKP2
value. Do the following:
1. Replace the memory DIMMs in the system.
2. Replace the system backplane.
20D00901 Failed to communicate with the BMC. Replace SYSBKP2
the system backplane.
20D00902 The system is booting from the permanent (B) SYSBKP2
firmware side.

If the system was already booting from the

permanent (B) side, this is an informational
message.

If it was not, it indicates that the system was

unable to boot from the temporary (A)
firmware side. Do the following:
1. Follow the operating system procedure to
reject the firmware update.
2. Reinstall the latest system firmware.
3. If the problem persists, replace the system
backplane.
20D00903 The firmware was not able to find the SYSBKP2
/openprom package. Do the following:
1. Check for system firmware updates and
apply if available.
2. Replace the system backplane.
20D10004 Failed to locate BMC device tree node. Do the SYSBKP2
following:
1. Check for system firmware updates, and
apply if available.
2. If the problem persists, replace the system
backplane.
20D10005 Failed to reboot system. Do the following: SYSBKP2
1. Check for system firmware updates, and
apply if available.
2. If the problem persists, replace the system
backplane.
20D10006 Failed to reboot system. Do the following: SYSBKP2
1. Check for system firmware updates, and
apply if available.
2. If the problem persists, replace the system
backplane.
20D10007 Firmware error before stdout ready. Do the SYSBKP2
following:
1. Check for system firmware updates, and
apply if available.
2. If the problem persists, replace the system
backplane.

Reference codes 55
20A8, 20Dx, 20EE, 20FF, 2102, 2200, 25Ax, 25Cx, 2602, 2803, 2B2x

Reference Code Description/Action Perform all actions before Failing Item

exchanging Failing Items
20D1000A Failed to send boot failed message to the BMC. SYSBKP2
Do the following:
1. Check for system firmware updates, and
apply if available.
2. If the problem persists, replace the system
backplane.
20D10010 Stack underflow from fiber channel adapter. Do SYSBKP2
the following:
1. Check for microcode updates for the fiber
channel adapter, and apply if available.
2. Check for system firmware updates, and
apply if available.
3. If the problem persists, replace the system
backplane.
20D10011 Failed to set the watchdog timer in the base SYSBKP2
motherboard controller. Do the following:
1. Check for system firmware updates, and
apply if available.
2. If the problem persists, contact your next
level of support.

Table 3. (20EE) Model 185 and A50 reference (error) codes

Reference Code Description/Action Perform all actions before Failing Item

exchanging Failing Items
20EE000A Reserved NEXTLVL

Contact your next level of support for

assistance.
20EE000B The system was not able to find an operating
system on the devices in the boot list.

Verify that the boot list contains at least one

device with a valid operating system boot
image.
20EE000F Unable to find the package node. Do the SYSBKP2
following:
1. Check for system firmware updates, and
apply if available.
2. If the problem persists, replace the system
backplane.
20EE0010 Unable to run the root vpd method. Do the SYSBKP2
following:
1. Check for system firmware updates, and
apply if available.
2. If the problem persists, replace the system
backplane.

56 System i® and System p®: Reference codes

20A8, 20Dx, 20EE, 20FF, 2102, 2200, 25Ax, 25Cx, 2602, 2803, 2B2x

Reference Code Description/Action Perform all actions before Failing Item

exchanging Failing Items
20EE0011 Unable to execute the vpd method. Do the SYSBKP2
following:
1. Check for system firmware updates, and
apply if available.
2. If the problem persists, replace the system
backplane.
20EE0012 Unable to execute the mem-dimm-vpd method. SYSBKP2
Do the following:
1. Check for system firmware updates, and
apply if available.
2. If the problem persists, replace the system
backplane.
20EE0015 Failed to read VPD boot path field value. Do SYSBKP2
the following:
1. Verify that the boot list is correct.
2. Check for system firmware updates, and
apply if available.
3. If the problem persists, replace the system
backplane.
20EE0016 Failed to update VPD with the new boot path SYSBKP2
field value. Do the following:
1. Verify that the boot list is correct.
2. Check for system firmware updates, and
apply if available.
3. If the problem persists, replace the system
backplane.
20EE0020 The environment variable boot-device exceeds SYSBKP2
the allowed character limit. Do the following:
1. Verify that the boot list is correct.
2. Check for system firmware updates, and
apply if available.
3. If the problem persists, replace the system
backplane.
20EE0021 The environment variable boot-device SYSBKP2
contained more than seven entries. Do the
following:
1. Verify that the boot list is correct.
2. Check for system firmware updates, and
apply if available.
3. If the problem persists, replace the system
backplane.
20EE0022 The environment variable boot-device SYSBKP2
contained an entry that exceeded 255 characters
in length. Do the following:
1. Verify that the boot list is correct.
2. Check for system firmware updates, and
apply if available.
3. If the problem persists, replace the system
backplane.

Reference codes 57
20A8, 20Dx, 20EE, 20FF, 2102, 2200, 25Ax, 25Cx, 2602, 2803, 2B2x

Reference Code Description/Action Perform all actions before Failing Item

exchanging Failing Items
20EE0100 Fcode resident on an I/O adapter is not
supported on this system. This error code only
affects boot-time operation, not the functionality
of the adapter under the operating system.

Informational message. The Fcode driver of the

adapter is not supported on this system. A
compatible driver may be produced in the
future, but does not guarantee one. Additional
information may be available from your next
level of support.
20EE0101 The baud rate specified for the com port is SYSBKP2
invalid. Do the following:
1. Use the System Management Services (SMS)
menus to check the baud rate. Reset it to a
valid value, if necessary.
2. Check for system firmware updates, and
apply if available.
3. Replace the system backplane.
20EE0102 An invalid number of data bits was specified SYSBKP2
for the com port. Do the following:
1. Use the SMS menus to check the data bit
setting. Reset it to a valid value, if
necessary.
2. Check for system firmware updates, and
apply if available.
3. Replace the system backplane.
20EE0103 An invalid number of stop bits was specified SYSBKP2
for the com port. do the following:
1. Use the SMS menus to check the stop bit
setting. Reset it to a valid value, if
necessary.
2. Check for system firmware updates, and
apply if available.
3. Replace the system backplane.
20EE0104 An invalid parity setting was specified for the SYSBKP2
com port. Do the following:
1. Use the SMS menus to check the parity
setting. Reset it to a valid value, if
necessary.
2. Check for system firmware updates, and
apply if available.
3. Replace the system backplane.
20EE0105 An invalid handshake setting was specified for SYSBKP2
the com port. Do the following:
1. Use the SMS menus to check the handshake
setting. Reset it to a valid value, if
necessary.
2. Check for system firmware updates, and
apply if available.
3. Replace the system backplane.

58 System i® and System p®: Reference codes

20A8, 20Dx, 20EE, 20FF, 2102, 2200, 25Ax, 25Cx, 2602, 2803, 2B2x

Reference Code Description/Action Perform all actions before Failing Item

exchanging Failing Items
20EE0200 Installing an image to the permanent side is not
allowed. Do the following:
1. Boot from the temporary side.
2. Install the firmware.
Note: If you are not able to boot from the temp
side, perform the system firmware rejection
function in the operating system, then attempt
to install the latest firmware.
20EE0201 The format of the firmware installation image is
not correct.

Install the firmware using a known good

image.
20EE0210 Installing system firmware failed; the firmware
may be corrupted. Install the firmware using a
known good image.
Note: If the system firmware is corrupted,
perform the system firmware rejection function,
then attempt to install the firmware again.
20EE0220 Installing the system firmware failed; the
firmware may be corrupted. Install the
firmware using a known good image.
Note: If the system firmware is corrupted,
perform the system firmware rejection function,
then attempt to install the firmware again.

Table 4. (20FF) Model 185 and A50 reference (error) codes

Reference Code Description/Action Perform all actions before Failing Item

exchanging Failing Items
20FF0001 Problem with VPD. Do the following: SYSBKP2
1. Replace the part indicated by the location
code.
2. If no location code is specified, replace the
system backplane.

Table 5. (2102) Model 185 and A50 reference (error) codes

Reference Code Description/Action Perform all actions before Failing Item

exchanging Failing Items
21020010 USB CD-ROM remained busy longer than the SYSBKP2
time allowed. Do the following:
1. Retry the operation.
2. Check for system firmware updates, and
apply if available.
3. Replace the USB CD-ROM drive.
4. Replace the system backplane.

Reference codes 59
20A8, 20Dx, 20EE, 20FF, 2102, 2200, 25Ax, 25Cx, 2602, 2803, 2B2x

Reference Code Description/Action Perform all actions before Failing Item

exchanging Failing Items
21020011 USB CD-ROM: execution of ATA/ATAPI SYSBKP2
command was not completed within the time
allowed. Do the following:
1. Retry the operation.
2. The CD in the USB CD-ROM drive may not
be readable. Try another CD.
3. Replace the USB CD-ROM drive.
4. Replace the system backplane.
21020012 USB CD-ROM: execution of ATA/ATAPI SYSBKP2
command by the USB CD-ROM failed. Do the
following:
1. Check the power and signal connectors
going to the USB CD-ROM drive, and
correct any problems that you find.
2. Retry the operation. If the problem persists,
continue with the next step.
3. The CD in the USB CD-ROM drive may not
be readable. Try another CD. If the problem
persists, continue with the next step.
4. Replace the USB CD-ROM drive.
5. Replace the system backplane.
21020013 USB CD-ROM: bootable CD is missing from the
CD-ROM drive.

Place a bootable CD-ROM in the USB CD-ROM

drive.
21020014 USB CD-ROM: the CD in the drive has been SYSBKP2
changed. Do the following:
1. Retry the operation.
2. Check for system firmware updates, and
apply if available.
3. Replace the USB CD-ROM drive.
4. Replace the system backplane.
21020015 USB CD-ROM: ATA/ATAPI packed command SYSBKP2
execution by USB CD-ROM failed. do the
following:
1. The CD in the USB CD-ROM drive may not
be readable. Try another CD. If the problem
persists, continue with the next step.
2. Check for system firmware updates, and
apply if available.
3. Replace the USB CD-ROM drive.
4. Replace the system backplane.

Table 6. (220x) Model 185 and A50 reference (error) codes

Reference Code Description/Action Perform all actions before Failing Item

exchanging Failing Items
25A00001 L2 cache controller failure. Do the following: SYSBKP2
1. Check for system firmware updates, and
apply if available.
2. Replace the system backplane.
25A10001 Cache L2 SRAM failure SYSBKP2
1. Check for system firmware updates, and
apply if available.
2. Replace the system backplane.

Reference codes 61
20A8, 20Dx, 20EE, 20FF, 2102, 2200, 25Ax, 25Cx, 2602, 2803, 2B2x

Reference Code Description/Action Perform all actions before Failing Item

exchanging Failing Items
25A80xxx NVRAM problems SYSBKP2

Errors reported against NVRAM can be caused

by low battery voltage and (more rarely) power
outages that occur during normal system usage.
With the exception of the 25A80000 error, these
errors are warnings that the NVRAM data had
to be reestablished and do not require any FRU
replacement unless the error is persistent. When
one of these errors occurs, any system
customization (for example, boot device list)
information has been lost. If the error is
persistent, replace the system backplane.
25A80000 Initialization failed, device test failed

Refer to the actions for error code 25A80xxx.

25A80100 NVRAM data validation check failed. Do the
following:
1. Before replacing any system component,
turn off and then turn on the system unit.
Then, retry the operation.
2. If the problem persists, refer to the actions
for error code 25A80xxx.
25A80201 Unable to expand target partition: saving
configuration variable

Refer to the actions for error code 25A80xxx.

25A80202 Unable to expand target partition: writing error
log entry

Refer to the actions for error code 25A80xxx.

25A80203 Unable to expand target partition: writing VPD
data

Refer to the actions for error code 25A80xxx.

25A80210 Setenv/$Setenv parameter error: name contains
a null character

Refer to the actions for error code 25A80xxx.

25A80211 Setenv/$Setenv parameter error: name contains
a null character

Refer to the actions for error code 25A80xxx.

62 System i® and System p®: Reference codes

20A8, 20Dx, 20EE, 20FF, 2102, 2200, 25Ax, 25Cx, 2602, 2803, 2B2x

Reference Code Description/Action Perform all actions before Failing Item

exchanging Failing Items
25A80998 NVRAMRC script evaluation error: command NEXTLVL
line execution error

Running of a command line within the nvram

configuration variable nvramrc (script) resulted
in a throw being run.

This script can be modified by the firmware

SMS utilities, the operating system, a PCI
adapter ROM code or utility, or an operator (by
using the open firmware script editing
command nvedit). Resolving the problem may
not be possible without a detailed analysis of
the NVRAM script, the current system
configuration, and device tree contents. Contact
your next level of support for assistance.
25A80999 NVRAMRC script evaluation error: stack NEXTLVL
unbalanced on completion

This is a firmware debug environment error. No

user action or FRU replacement exists for this
error. If this error persists, call your next level
of support.

Table 8. (25Cx) Model 185 and A50 reference (error) codes

Reference Code Description/Action Perform all actions before Failing Item

exchanging Failing Items
25C00000 No DIMMs detected. Do the following: SYSBKP2
1. Ensure that all DIMMs are properly seated.
Reseat them if necessary, and reboot the
system.
2. Replace the DIMMs one at a time until the
failing DIMM is isolated.
3. Replace the system backplane.

Reference codes 63
20A8, 20Dx, 20EE, 20FF, 2102, 2200, 25Ax, 25Cx, 2602, 2803, 2B2x

Reference Code Description/Action Perform all actions before Failing Item

exchanging Failing Items
25C0xxyy DIMM failure, where xx and yy indicate: SYSBKP2
xx Description
-------------------
01 DIMM2 missing
10 DIMM1 missing
12 DIMM1 not supported
14 DIMM1 failed
21 DIMM2 not supported
22 DIMM1 and DIMM2 unsupported
41 DIMM2 failed
88 DIMM1 and DIMM2 mismatch

yy Description
-------------------
01 DIMM4 missing
10 DIMM3 missing
12 DIMM3 not supported
14 DIMM3 failed
21 DIMM4 not supported
22 DIMM3 and DIMM4 unsupported
41 DIMM4 failed
88 DIMM3 and DIMM4 mismatch

Do the following:
1. Verify that the DIMMs in the system are
supported. Replace all unsupported DIMMs,
then reboot the system.
2. Verify that the DIMMs are installed in pairs.
If they are not, properly install the DIMMs.
Reboot the system.
3. Ensure that the DIMMs are properly seated;
reseat if necessary. Reboot the system.
4. If the problem persists, replace the system
backplane.
25C10001 Memory DIMM failure SYSBKP2
1. Insure that the DIMMs are properly seated;
reseat if necessary. Reboot the system.
2. Replace the DIMM specified by the location
code, then reboot the system.
3. Replace the companion DIMM in the pair,
then reboot the system.
4. If the problem persists, replace the system
backplane.
25C10002 Memory DIMM is not supported SYSBKP2
1. Verify that the DIMMs in the system are
supported. Replace all unsupported DIMMs,
then reboot the system.
2. Verify that the DIMMs are installed in one
or more pairs. If they are not, properly
install the DIMMs, then reboot the system.
3. If the problem persists, replace the system
backplane.

64 System i® and System p®: Reference codes

20A8, 20Dx, 20EE, 20FF, 2102, 2200, 25Ax, 25Cx, 2602, 2803, 2B2x

Reference Code Description/Action Perform all actions before Failing Item

exchanging Failing Items
25C10003 The companion (in the pair) of the memory SYSBKP2
DIMM specified by the location code is failing,
unsupported, missing, or unmatched. Do the
following:
1. Verify that the DIMMs in the system are
supported. Replace all unsupported DIMMs,
then reboot the system.
2. Verify that the DIMMs are installed in one
or more pairs. If they are not, properly
install the DIMMs, then reboot the system.
3. Replace the companion of the DIMM
specified by the location code.
4. Replace the DIMM specified by the location
code.
5. If the problem persists, replace the system
backplane.

Table 9. (2602) Model 185 and A50 reference (error) codes

Reference Code Description/Action Perform all actions before Failing Item

exchanging Failing Items
26020008 PCI device fcode evaluation error. SYSBKP2
v If the location code identifies a slot, do the
following:
1. Reseat the adapter and reboot the system.
2. Replace the adapter.
3. Check for system firmware updates, and
apply if available.
4. If the problem persists, replace the system
backplane.
v If the location code identifies the system
backplane, replace the system backplane.
26020009 The PCI adapter Fcode left a data stack
imbalance. Do the following:
1. Check for adapter microcode updates, and
apply if available.
Note: Using the adapter for booting is not
recommended until after you install the new
adapter microcode.
2. If no microcode updates are available, or if
installing new microcode does not correct
the problem, replace the PCI adapter.

Table 10. (2803) Model 185 and A50 reference (error) codes

Reference codes 65
20A8, 20Dx, 20EE, 20FF, 2102, 2200, 25Ax, 25Cx, 2602, 2803, 2B2x

Reference Code Description/Action Perform all actions before Failing Item

exchanging Failing Items
2803000A The Hypervisor function to get or set the SYSBKP2
time-of-day (TOD) reported an error.

Errors reported against the real time clock

might be caused by low battery voltage or
(more rarely) power outages that occur during
normal system usage. These errors are
warnings that the real time clock data content
needs to be reestablished. Unless the error is
persistent, these errors do not require any FRU
replacement. When one of these errors occurs,
the system loses time and date information.

Reset the server time and date through the

installed operating system.

If the error is persistent, do the following:

1. Check for system firmware updates, and
apply if available.
2. Replace the system battery.
3. Replace the system backplane.
28030001 Real-time-clock not updating: real-time-clock SYSBKP2
initialization required.

Set the time and date.

Note: This is normally an informational
message. If the problem persists, replace the
system backplane.
28030002 Bad time/date values SYSBKP2

Set the time and date.

Note: This is normally an informational
message. If the problem persists, replace the
system backplane.
28030003 Real-time-clock not updating: not correctable. SYSBKP2

Replace the system backplane.

28030004 Real-time-clock operating mode parameters (for
example, data mode) changed. Do the
following:
1. Set the time and date.
2. Refer to the actions under 28030001.
28030005 Real-time-clock battery error SYSBKP2

Replace the system backplane.

Table 11. (2B2x) Model 185 and A50 reference (error) codes

Reference Code Description/Action Perform all actions before Failing Item

exchanging Failing Items
2B200x31 Processor x is faulty SYSBKP2

Replace the system backplane.

66 System i® and System p®: Reference codes

20A8, 20Dx, 20EE, 20FF, 2102, 2200, 25Ax, 25Cx, 2602, 2803, 2B2x

Reference Code Description/Action Perform all actions before Failing Item

exchanging Failing Items
2B208888 Operating system termination request received

Informational message.
2B2x00EE An exception error has been reported on a SYSBKP2
processor

The type of interrupt that caused the exception

is specified by the x as follows:
x Description
-------------------
0 Unknown interrupt
1 System reset interrupt (SRI)
2 Machine check interrupt (MCI)
3 Data storage interrupt (DSI)
4 Instruction storage interrupt (ISI)
5 External interrupt (EXI)
6 Alignment interrupt (ALI)
7 Program interrupt (SRI)
8 Floating unavailable interrupt (FUI)

Do the following:
1. Check for system firmware updates, and
apply if available.
2. Replace the system backplane.

(2689) Reference codes

Find the unit reference code in the following table. For more on the Failing Item column entries, see Table
2. Failing items details, which follows the reference code table below.

Table 1. (2689) Reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
0A17 A permanent I/O processor failure occurred 2689
AJDG301
AJDGP01
0A22 Adapter card storage error AJDGP01
AJDG301
2689
1307 I/O adapter resource not available. AJDGP01
AJDG301
1310 I/O adapter resource not available. 2689
AJDGP01
The INA processor error log is being filled faster than the errors are being
reported to the system. Check other errors reported to the system and
correct them.
3000 An I/O adapter failure occurred. 2689
AJDGP01
3001 I/O adapter Licensed Internal Code failed. 2689
AJDGP01
3006 An I/O adapter failure occurred. 2689
ANYBUS
3080 I/O adapter Licensed Internal Code failed. AJDGP01

Reference codes 67
2689

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
3081 I/O adapter error; logged only.
3084 An I/O adapter failure occurred. AJDGP01
2689
3087 I/O adapter resource not available. AJDGP01
AJDG301
NTUSER
6070 An I/O adapter failure occurred. 2689
6071 I/O adapter Licensed Internal Code failed. AJDGP01
6072 I/O adapter Licensed Internal Code failed. AJDGP01
2689
6075 I/O adapter resource not available. AJDGP01
6083, 6085 I/O adapter Licensed Internal Code failed. AJDGP01
2689
6201 A permanent I/O processor failure occurred 2689
AJDGP01
6202 I/O processor Licensed Internal Code error AJDGP01
2689
6203 A permanent I/O processor failure occurred NETSERV
2689
AJDGP01
6210 I/O processor Licensed Internal Code error NETSERV
AJDGP01
6222 A permanent I/O processor failure occurred AJDGP01
2689
6223 A permanent I/O processor failure occurred 2689
AJDGP01
6225 A permanent I/O processor failure occurred AJDGP01
AJDG301
2689
6226 I/O processor card detected device error AJDG301
AS4NTDD
6227 A HostLAN error was detected NTUSER
AJDGP01
2689
6228 Windows initiated a warm boot AJDGP01
2689
6501 A Windows fatal error occurred 2689
AJDGP01
6502 A Windows fatal error occurred AJDGP01
2689
6530 A Virtual SCSI error was detected NTVSCSI
NTOPSYS
6531 A Virtual SCSI error was detected NTVSCSI
AS4NTDD
NTOPSYS
AJDGP01
6532 A Virtual SCSI error was detected NTOPSYS
AJDGP01
AS4NTDD

68 System i® and System p®: Reference codes

2689

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
6533 A Virtual SCSI error was detected NTUSER
NTOPSYS
AS4NTDD
6534 A Virtual SCSI error was detected AS4NTDD
AJDGP01
NTOPSYS
6535 A Virtual SCSI error was detected NTUSER
NTDEVDR
AJDGP01
6538 A Virtual SCSI error was detected NTVSCSI
NTOPSYS
6539 A Virtual SCSI error was detected NTVSCSI
AS4NTDD
NTOPSYS
AJDGP01
653A A Virtual SCSI error was detected NTOPSYS
AJDGP01
AS4NTDD
653B A Virtual SCSI error was detected NTUSER
NTOPSYS
AS4NTDD
653C A Virtual SCSI error was detected AS4NTDD
AJDGP01
NTOPSYS
653D A Virtual SCSI error was detected NTUSER
NTDEVDR
AJDGP01
653F A Virtual SCSI error was detected NTDEVDR
NTOPSYS
AJDG301
6540 A Virtual SCSI error was detected NTVSCSI
AJDGP01
AJDG301
6541 A permanent I/O processor failure occurred 2689
AJDGP01
6542 Licensed Internal Code error detected. AJDG301
AJDGP01
6543 A Windows fatal error occurred NTOPSYS
NTVSCSI
6544 A Virtual SCSI error was detected NTVSCSI
NTOPSYS
6580 A Windows fatal error occurred DISKIMG
2689
AJDGP01
6590 A Netfinity Server error was detected
65B0 A HostLAN error was detected NTLANDD
NTOPSYS
65B1 A HostLAN error was detected NTLANDD
NTOPSYS
AJDG301

Reference codes 69
2689

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
65B2 A HostLAN error was detected NTDEVDR
NTOPSYS
AJDG301
8301 An I/O adapter failure occurred. AJDGP01
2689
B3B1 to B3B7 A permanent I/O processor failure occurred 2689
B3B8 An I/O adapter failure occurred. 2689
B3B9 A permanent I/O processor failure occurred 2689
B3E0 I/O processor detected a fault condition 2689
B3E1 An I/O adapter failure occurred. 2689
B4B0 I/O adapter hardware error detected 2689
B4B1 A Netfinity Server error was detected NETSERV
AJDGP01
B4B9 An I/O adapter failure occurred. 2689
B4BC A Netfinity Server error was detected NETSERV
B4BF A Netfinity Server error was detected NSCABLE
B904 A permanent I/O processor failure occurred AJDGP01
2689
B935 Incompatible hardware detected. AJDGP01
2689
B960 I/O processor Licensed Internal Code error AJDGP01
2689
BE00 An I/O adapter failure occurred. AJDGP01
2689

Table 2. Failing items details

Failing Item Description Document Description

2689 I/O adapter card Repair and Parts; removal and installation
procedures
AJDG301 Licensed Internal Code See the service documentation for instructions.
AJDGP01 I/O card Licensed Internal Code See the service documentation for instructions.
ANYBUS Remote HSL Network Bus See the service documentation for instructions.
AS4NTDD Device Driver See the service documentation for instructions.
DISKIMG Server Storage Space Object See the service documentation for instructions.
NETSERV Direct Attach Netfinity Server See the service documentation for instructions.
NSCABLE Direct Attach Netfinity Server cable See the service documentation for instructions.
NTDEVDR Device Driver See the service documentation for instructions.
NTLANDD Device Driver See the service documentation for instructions.
NTOPSYS Windows Operating System See the service documentation for instructions.
NTUSER User-initiated action See the service documentation for instructions.
NTVSCSI Device Driver See the service documentation for instructions.

70 System i® and System p®: Reference codes

2689

(2724, 2744, 6149) Reference codes

1. Look at characters 5 through 8 of the top 16 character line of function 11 (4 rightmost characters of
word 1). These 4 characters are the unit reference code.
2. Look at the last 8 characters of the top 16 character line of function 12 (word 3). These 8 characters are
the direct select address of the card (BBBBCcbb). The unit address portion of the card address is
characters 1 through 8 of the bottom 16 character line of function 11 (word 4). Card locations can be
found using the 16 character address. See SRC Address Formats.
3. Find the unit reference code in the following table.

For more on the Failing Item column entries, see Table 2. Failing items details, which follows the
reference code table below.

Table 1. (2724, 2744, 6149) Reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
B904 I/O adapter Licensed Internal Code failed. AJDGP01
FI00719
B920 I/O adapter Licensed Internal Code failed. AJDGP01
FI00718
FI00719
B921 I/O adapter hardware error detected FI00719
FI00718
AJDGP01
MA_BRDG
B934 Incompatible hardware detected. FI00719
FI00718

Table 2. Failing items details

Failing Item Description Document Description

AJDGP01 Input/Output Processor Licensed Internal Code Service Functions; APAR or LICTR
MA_BRDG Multi-adapter bridge See the service documentation for instructions.

(2742, 2793, 2805) Reference codes

1. Look at characters 5 through 8 of the top 16 character line of function 11 (4 rightmost characters of
word 1). These 4 characters are the unit reference code.
2. Look at the last 8 characters of the top 16 character line of function 12 (word 3). These 8 characters are
the direct select address of the card (BBBBCcbb). The unit address portion of the card address is
characters 1 through 8 of the bottom 16 character line of function 11 (Word 4). Card locations can be
found using the 16 character address. See SRC Address Formats.
3. Find the unit reference code in the following table.

For more on the Failing Item column entries, see Table 2. Failing items details, which follows the
reference code table below.

Table 1. (2742, 2793, 2805) Reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
B940 I/O adapter hardware error detected FI00719
AJDGP01
MA_BRDG

Reference codes 71
2742

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
B941 One of the ports on the IOA has failed. FI00719
AJDGP01

Table 2. Failing items details

Failing Item Description Document Description

AJDGP01 Licensed Internal Code Service Functions; APAR or LICTR
MA_BRDG Multi-adapter bridge See the service documentation for instructions.

(2743, 2760) Reference codes

1. Look at characters 5 through 8 of the top 16 character line of function 11 (4 rightmost characters of
word 1). These 4 characters are the unit reference code.
2. Look at the last 8 characters of the top 16 character line of function 12 (word 3). These 8 characters are
the direct select address of the card (BBBBCcbb). The unit address portion of the card address is
characters 1 through 8 of the bottom 16 character line of function 11 (Word 4). Card locations can be
found using the 16 character address. See SRC Address Formats.
3. Find the unit reference code in the following table.

For more on the Failing Item column entries, see Table 2. Failing items details, which follows the
reference code table below.

Table 1. (2743, 2760) Reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
B950 Licensed Internal Code error AJDGP01
FI00718
FI00719
B951 I/O adapter hardware error detected FI00719
FI00718
AJDGP01
MA_BRDG

Table 2. Failing items details

Failing Item Description Document Description

AJDGP01 LIC - Input/Output Processor Licensed Internal Service Functions; APAR or LICTR
Code
MA_BRDG Multi-adapter bridge See the service documentation for instructions.

(2745) Reference Codes

72 System i® and System p®: Reference codes

2742

For more on the Failing Item column entries, see Table 2. Failing items details, which follows the
reference code table below.

Table 1. (2745) Reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
B904 I/O adapter Licensed Internal Code failed. AJDGP01
FI00719
B934 Incompatible hardware detected. FI00719
FI00718
B940 I/O adapter hardware error detected FI00719
FI00718
AJDGP01
MA_BRDG
B941 to B942 One half of I/O adapter failed. FI00719
FI00718
AJDGP01

Table 2. Failing items details

Failing Item Description Document Description

AJDGP01 LIC - Input/Output Processor Licensed Internal Service Functions; APAR or LICTR
Code
MA_BRDG Multi-adapter bridge See the service documentation for instructions.

(2746) Twinaxial – workstation adapter reference codes

1. Look at characters 5 through 8 of the top 16 character line of function 11 (4 rightmost characters of
word 1). These 4 characters are the unit reference code.
2. Look at the last 8 characters of the top 16 character line of function 12 (word 3). These 8 characters are
the direct select address of the card (BBBBCcbb). The unit address portion of the card address is
characters 1 through 8 of the bottom 16 character line of function 11 (Word 4). Card locations can be
found using the 16 character address. See SRC Address Formats.
3. Find the unit reference code in the following table.

For more on the Failing Item column entries, see Table 2. Workstation adapter failing items details, which
follows the reference code table below.

Table 1. (2746) Twinaxial – workstation adapter reference codes

Reference codes 73
2746

Table 2. Workstation adapter failing items details

Failing Item Description Document Description

AJDGP01 LIC - Input/Output Processor Licensed Internal Service Functions; APAR or LICTR
Code
MA_BRDG Multi-adapter bridge See the service documentation for instructions.

(2748, 2757, 2763, 2778, 2780, 2782, 5703, 5709) Reference codes
If the error is reported on the control panel, the unit reference code is characters 5 through 8 of the top 16
character line of function 11. If the error is reported on the console, the unit reference code is the 4
rightmost characters of word 1.

Find the unit reference code in the following table.

For more on the Failing Item column entries, see Table 2. Failing Items Details, which follows the
reference code table below.

Table 1. (2748, 2757, 2763, 2778, 2780, 2782, 5703, 5709) Reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
1310 I/O processor resource not available

The I/O processor error log is being filled faster than the errors are being
reported to the system. Check other errors reported to the system and
correct them.
3006 System bus error IOP
ANYBUS
STORIOA
3020 I/O processor detected a SCSI bus configuration error USER
FI01107
Error occurred on SCSI bus 0. To correct or isolate a possible user error or STORIOA
configuration error, perform IOPIP17. Use the failing item (FI) codes to find
failing devices.
3021 I/O processor detected a SCSI bus configuration error USER
FI01107
Error occurred on SCSI bus 1. To correct or isolate a possible user error or STORIOA
configuration error, perform IOPIP17. Use the failing item (FI) codes to find
failing devices.
3022 I/O processor detected a SCSI bus configuration error USER
FI01107
Error occurred on SCSI bus 2. To correct or isolate a possible user error or STORIOA
configuration error, perform IOPIP17. Use the failing item (FI) codes to find
failing devices.
3023 I/O processor detected a SCSI bus configuration error USER
FI01107
Error occurred on SCSI bus 3. To correct or isolate a possible user error or STORIOA
configuration error, perform IOPIP17. Use the failing item (FI) codes to find
failing devices.
3100 I/O processor card detected interface error FI01107
STORIOA
Error occurred on SCSI bus 0. FI01140
DEVBPLN
Perform IOPIP13.

74 System i® and System p®: Reference codes

2748, 2757, 2763, 2778, 2780, 2782, 5703, 5709

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
3101 I/O processor card detected interface error FI01107
STORIOA
Error occurred on SCSI bus 1. FI01140
DEVBPLN
Perform IOPIP13.
3102 I/O processor card detected interface error FI01107
STORIOA
Error occurred on SCSI bus 2. FI01140
DEVBPLN
Perform IOPIP13.
3103 I/O processor card detected interface error FI01107
STORIOA
Error occurred on SCSI bus 3. FI01140
DEVBPLN
Perform IOPIP13.
3120 I/O Processor detected that the bus is not operational SVCDOCS

A device was added to SCSI bus 0 of the I/O Adapter and caused the bus
to become not operational. Remove the device.
3121 I/O Processor detected that the bus is not operational SVCDOCS

A device was added to SCSI bus 1 of the I/O Adapter and caused the bus
to become not operational. Remove the device.
3122 I/O Processor detected that the bus is not operational SVCDOCS

A device was added to SCSI bus 2 of the I/O Adapter and caused the bus
to become not operational. Remove the device.
3123 I/O Processor detected that the bus is not operational SVCDOCS

A device was added to SCSI bus 3 of the I/O Adapter and caused the bus
to become not operational. Remove the device.
3140 I/O Processor detected that the bus is now operational

This reference code and the 3120 reference code that occurred before it
require no service action, since SCSI bus 0 is now operational.
3141 I/O Processor detected that the bus is now operational

This reference code and the 3121 reference code that occurred before it
require no service action, since SCSI bus 1 is now operational.
3142 I/O Processor detected that the bus is now operational

This reference code and the 3122 reference code that occurred before it
require no service action, since SCSI bus 2 is now operational.
3143 I/O Processor detected that the bus is now operational

This reference code and the 3123 reference code that occurred before it
require no service action, since SCSI bus 3 is now operational.
3150 I/O processor detected a SCSI bus configuration error SVCDOCS

Internal and external SCSI cables are connected to SCSI bus 0 at the same
time. Correct the SCSI bus 0 configuration.
3151 I/O processor detected a SCSI bus configuration error SVCDOCS

Internal and external SCSI cables are connected to SCSI bus 1 at the same
time. Correct the SCSI bus 1 configuration.

Reference codes 75
2748, 2757, 2763, 2778, 2780, 2782, 5703, 5709

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
3400 I/O processor card detected device error FI02112
STORIOA
FI01106
DEVTERM
FI01140
3401 Device backplane problem DEVBPLN
3501 I/O processor Licensed Internal Code error AJDGP01
IOP
3600 to 3601 System log entry only, no service action required
8008 A permanent cache battery pack failure occurred CACHBAT
STORIOA
NOTE: Under a certain configuration, this SRC may not represent an error
that requires a service action. Depending on the configuration of the
system, the Storage IOA may have been altered and/or the Storage IOA
Cache may have been disabled to allow attachment of OEM Storage that
emulates a Load Source drive. If this is the case, this error will be posted
each time the IOA is IPLed and it can be ignored.
8009 Impending cache battery pack failure CACHBAT
8012 Attached read cache devices exceed capacity supported by IOA SVCDOCS

Reduce the number of read caches on the IOA.

8100 I/O processor Licensed Internal Code error AJDGP01
IOP
8130 IOA detected recoverable device bus error

An error occurred on SCSI bus 0. No action is required. This reference code

is logged for information only.
8131 IOA detected recoverable device bus error

An error occurred on SCSI bus 1. No action is required. This reference code

is logged for information only.
8132 IOA detected recoverable device bus error

An error occurred on SCSI bus 2. No action is required. This reference code

is logged for information only.
8133 IOA detected recoverable device bus error

An error occurred on SCSI bus 3. No action is required. This reference code

is logged for information only.
8140 IOA detected recoverable device bus error

No action is required. This reference code is logged for information only.

8141 IOA detected recoverable device error

No action is required. This reference code is logged for information only.

8145 A recoverable I/O processor error occurred. STORIOA
8146 Disk device detected recoverable error FI01105

76 System i® and System p®: Reference codes

2748, 2757, 2763, 2778, 2780, 2782, 5703, 5709

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
8150 A permanent I/O processor failure occurred STORIOA
ANYBRDG
NOTE: Under a certain configuration, this SRC may not represent an error
that requires a service action. Depending on the configuration of the
system, the Storage IOA may have been altered and/or the Storage IOA
Cache may have been disabled to allow attachment of OEM Storage that
emulates a Load Source drive. If this is the case, this error will be posted
each time the IOA is IPLed and it can be ignored.
8151 I/O processor Licensed Internal Code error AJDGP01
STORIOA
8155 to 8156 A permanent I/O processor failure occurred AJDGP01
STORIOA
8157 I/O adapter card error SVCDOCS

Display the Service Action Log entry for this SRC. If the Failing Item
indicates I/O adapter, then replace the I/O adapter. If the Failing Item
indicates SVCDOCS, then do NOT replace the I/O adapter. This is a
recoverable error. Perform the following for the I/O processor that the I/O
adapter is attached to:

1. If the I/O Processor is not operable and disk units are attached, use
Hardware Service Manager to re-IPL the IOP. Other resources attached to
the IOP may then need to be Varied On.

2. If disk units are not attached, perform the VRYCFG RESET(*YES)

command to reset the IOP and Vary On attached resources.
8200 I/O processor Licensed Internal Code error AJDGP01
IOP
9000 I/O processor card detected device error FI01105
STORIOA
9001 I/O processor card detected device configuration error SVCDOCS

Perform IOPIP33.
9002 I/O processor card detected device error FI01105
STORIOA
Perform IOPIP16. FI01140
BACKPLN
FI01106
9008 I/O card does not support functions expected by devices SVCDOCS

Perform IOPIP25.
9009 Call your next level of support for assistance SVCDOCS
9010 Cache data associated with attached devices cannot be found SVCDOCS

Perform IOPIP31.
9011 Cache data belongs to devices other than those attached SVCDOCS

Perform IOPIP32.
9014 Mode jumper overridden due to cache data in conflicting mode SVCDOCS

See JOVERRIDE.
9015 Mode jumper missing SVCDOCS

See JMISSING.

Reference codes 77
2748, 2757, 2763, 2778, 2780, 2782, 5703, 5709

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
9020 to 9021 Array not functional due to present hardware configuration. SVCDOCS

Perform IOPIP20.
9022 to 9024 Array not functional due to present hardware configuration. SVCDOCS

Perform IOPIP22.
9025 Disk unit is not supported at its physical location. SVCDOCS

Perform IOPIP21.
9026 Array not functional due to present hardware configuration. SVCDOCS

Perform IOPIP22.
9027 Array not functional due to present hardware configuration. SVCDOCS

Perform IOPIP34.
9028 Incorrect hardware configuration change has been detected. SVCDOCS

Reduce the number of arrays on IOP. Either move all devices in an array to
another IOP that supports arrays, or stop an array on this IOP.
9029 Incorrect hardware configuration change has been detected. SVCDOCS

Contact your next level of support.

902F Array addendum Product Activity Log entry

This entry contains additional array information for 90xx reference codes
when the array contains more than 10 array members. Use the 90xx entry
that occurred at the same time as this reference code as the starting point
for this problem.
9030 Array no longer protected due to missing or failed disk unit SVCDOCS

Perform IOPIP21.
9031 Automatic rebuild initiated for array

Either a previous rebuild was interrupted and was automatically restarted,

or a hot spare disk unit was used to automatically rebuild the array. Look
for other reference codes and take action on them.
9032 A disk unit in an array is missing or failed FI02112
SVCDOCS
The array is still protected, but the disk unit should be replaced.

Perform IOPIP21.
9040 Array protection temporarily suspended

No action required. Protection will be automatically restarted.

9041 Background array parity check detected and corrected errors AJDGP01

Call your next level of support to report the problem.

9042 An array parity error has been detected and corrected NEXTLVL

Call your next level of support to report the problem.

9050 Required cache data cannot be located for a disk unit. SVCDOCS

Perform IOPIP30.

78 System i® and System p®: Reference codes

2748, 2757, 2763, 2778, 2780, 2782, 5703, 5709

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
9051 IOP cache data exists for a missing or failed device. SVCDOCS

If all configured units are missing, a 9054 reference code may appear in the
product activity log. If so, perform the action indicated for the 9054
reference code.

Otherwise, perform IOPIP27.

9052 Cache data exists for device that has been modified. SVCDOCS

Contact your next level of support.

9053 IOP resources not available due to previous problems. SVCDOCS

Take action on other IOP reference codes which have surfaced.

If you cannot get to SST or DST, and cannot perform a type A or B IPL,
perform a type D IPL from removable media. Look for Product Activity
Log entries for other IOP reference codes and take action on them.
9054 IOP resources not available due to previous problems. SVCDOCS

Power off the system and remove all new or replacement disk units. IPL
the system to DST. If you cannot perform a type A or B IPL, perform a
type D IPL from removable media.

Look for Product Activity Log entries for other IOP reference codes and
take action on them.
9071 Link from IOA to auxiliary cache IOA went operational

No service action required.

9072 Link from IOA to auxiliary cache IOA went non-operational

No service action required.

9073 Incompatible or non-operational auxiliary cache IOA attached SVCDOCS

Perform IOPIP40.
9081 I/O processor card detected device error FI01105
STORIOA
9082 I/O processor card detected device error FI01105
STORIOA
Perform IOPIP16. FI01140
BACKPLN
FI01106
9090 Disk unit has been modified after the last known status. SVCDOCS

Re-IPL the system. If any reference codes are surfaced, go to List of system
reference codes and use the new reference code as the entry point to the
problem.

If you cannot resolve the problem, contact your next level of support.
9091 Incorrect hardware configuration change has been detected. SVCDOCS

Re-IPL the system. If any reference codes are surfaced, go to List of system
reference codes and use the new reference code as the entry point to the
problem.

If you cannot resolve the problem, contact your next level of support.

Reference codes 79
2748, 2757, 2763, 2778, 2780, 2782, 5703, 5709

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
9092 Disk unit requires initialization before use. SVCDOCS

Perform IOPIP26.
9093 Read cache device not in correct format SVCDOCS

Contact your next level of support.

B934 Incompatible hardware detected. STORIOA
FF3D I/O adapter detected a recoverable error STORIOA
ANYBRDG
FF6D I/O processor detected a recoverable system bus error IOP
ANYBUS

Table 2. Failing items details

Failing Item Description Document Description

AJDGP01 I/O processor Licensed Internal Code Service Functions; APAR or LICTR
ANYBRDG System I/O bus or any attached card See the service documentation for instructions.
ANYBUS IOP card bus error See the service documentation for instructions.
BACKPLN Card Enclosure or Planar Board See the service documentation for instructions.
CACHBAT Cache battery pack See the service documentation for instructions.
DEVBPLN Device backplane See the service documentation for instructions.
DEVTERM Terminating plug See the service documentation for instructions.
IOP I/O processor card See the service documentation for instructions.
NEXTLVL Call your next level of support for assistance See the service documentation for instructions.
PCIBUS Any PCI card on the PCI bus See the service documentation for instructions.
STORIOA Storage I/O adapter See the service documentation for instructions.
SVCDOCS Customer engineer directed to system problem See the service documentation for instructions.
analysis
USER System Operator/User See the service documentation for instructions.

(2749, 2767, 2768, 2842, 2843, 2844, 284B, 5702, 570B) Reference codes
1. If the error is reported on the control panel, the unit reference code is characters 5 through 8 of the
top 16 character line of function 11. If the error is reported on the console, the unit reference code is
the 4 rightmost characters of word 1.
2. Find the unit reference code in the following table.

Attention: The 673x is a read cache. Perform all actions required for 673x as a disk drive and logic card
except where separate 673x cache instructions are provided.

For more on the Failing Item column entries, see Table 2. Failing Items Details, which follows the
reference code table below.

Table 1. (2749, 2767, 2768, 2842, 2843, 2844, 284B, 5702, 570B) Reference codes

80 System i® and System p®: Reference codes

2749, 2767, 2768, 2842, 2843, 2844, 284B, 5702, 570B

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
0A17 A permanent I/O processor failure occurred IOP
MA_BRDG
AJDGP01
AJDG301
0A22 I/O processor detected a storage transfer error AJDGP01
AJDG301
IOP
MA_BRDG
102E Out of alternate sectors for disk storage FI01105
1306 I/O processor card or Licensed Internal Code error AJDGP01
IOP
A microprocessor exception occurred on the I/O processor. FI01104
BACKPLN
1307 I/O processor resource not available AJDGP01
AJDG301
1310 I/O processor resource not available

The I/O processor error log is being filled faster than the errors are being
reported to the system. Check other errors reported to the system and
correct them.
1317 I/O processor card error SVCDOCS

Display the Service Action Log entry for this SRC. If the Failing Item
indicates IOP, then replace the IOP. If the Failing Item indicates SVCDOCS,
then do NOT replace the IOP. This is a recoverable error. Perform the
following:

1. If the I/O Processor is not operable and disk units are attached, use
Hardware Service Manager to re-IPL the IOP. Other resources attached to
the IOP may then need to be Varied On.

2. If disk units are not attached, perform the VRYCFG RESET(*YES)

command to reset the IOP and Vary On attached resources.
2200 I/O processor Licensed Internal Code error AJDGP01
2201 Removable media error during IPL USER
FI01105
2202 Removable media error during IPL FI00022
FI01105
3000 A permanent I/O processor failure occurred FI01101
IOP
MA_BRDG
3001 Not valid condition in I/O Processor Licensed Internal Code IOP
AJDGP01
The Licensed Internal Code found a condition that should not have
occurred.
3002 Addressed device failed to respond to selection FI01105
STORIOA
Perform IOPIP16. FI01140
FI01141
FI01106
3006 System bus error IOP
ANYBUS
FI01101

Reference codes 81
2749, 2767, 2768, 2842, 2843, 2844, 284B, 5702, 570B

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
3020 I/O processor detected a SCSI bus configuration error USER
FI01107
Error occurred on SCSI bus 0. To correct or isolate a possible user error or STORIOA
configuration error, perform IOPIP17. Use the failing item (FI) codes to find
failing devices.
3021 I/O processor detected a SCSI bus configuration error USER
FI01107
Error occurred on SCSI bus 1. To correct or isolate a possible user error or STORIOA
configuration error, perform IOPIP17. Use the failing item (FI) codes to find
failing devices.
3022 I/O processor detected a SCSI bus configuration error USER
FI01107
Error occurred on SCSI bus 2. To correct or isolate a possible user error or STORIOA
configuration error, perform IOPIP17. Use the failing item (FI) codes to find
failing devices.
3023 I/O processor detected a SCSI bus configuration error USER
FI01107
Error occurred on SCSI bus 3. To correct or isolate a possible user error or STORIOA
configuration error, perform IOPIP17. Use the failing item (FI) codes to find
failing devices.
3080 I/O processor Licensed Internal Code error AJDGP01
3081 System log entry only, no service action required
3084 I/O processor card or Licensed Internal Code error AJDGP01
IOP
A microprocessor exception occurred on the I/O processor. FI01104
MA_BRDG
3087 I/O processor resource not available AJDGP01
AJDG301
The Licensed Internal Code could not allocate resources on the I/O IOACNFG
processor card. FI01104
3100 I/O processor card detected interface error FI01107
STORIOA
Error occurred on SCSI bus 0. FI01140
DEVBPLN
Perform IOPIP13.
3101 I/O processor card detected interface error FI01107
STORIOA
Error occurred on SCSI bus 1. FI01140
DEVBPLN
Perform IOPIP13.
3102 I/O processor card detected interface error FI01107
STORIOA
Error occurred on SCSI bus 2. FI01140
DEVBPLN
Perform IOPIP13.
3103 I/O processor card detected interface error FI01107
STORIOA
Error occurred on SCSI bus 3. FI01140
DEVBPLN
Perform IOPIP13.
3109 I/O processor timed out a device command FI01105
STORIOA
Perform IOPIP16. FI01140
BACKPLN
FI01106

82 System i® and System p®: Reference codes

2749, 2767, 2768, 2842, 2843, 2844, 284B, 5702, 570B

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
3110 I/O processor card detected interface error FI01105
STORIOA
Perform IOPIP16. FI01140
BACKPLN
FI01106
3120 I/O Processor detected that the bus is not operational SVCDOCS

A device was added to SCSI bus 0 of the I/O Adapter and caused the bus
to become not operational. Remove the device.
3121 I/O Processor detected that the bus is not operational SVCDOCS

A device was added to SCSI bus 1 of the I/O Adapter and caused the bus
to become not operational. Remove the device.
3122 I/O Processor detected that the bus is not operational SVCDOCS

A device was added to SCSI bus 2 of the I/O Adapter and caused the bus
to become not operational. Remove the device.
3123 I/O Processor detected that the bus is not operational SVCDOCS

A device was added to SCSI bus 3 of the I/O Adapter and caused the bus
to become not operational. Remove the device.
3136 The removable media device is assigned elsewhere USER
FI01105
3140 I/O Processor detected that the bus is now operational

This reference code and the 3120 reference code that occurred before it
require no service action, since SCSI bus 0 is now operational.
3141 I/O Processor detected that the bus is now operational

This reference code and the 3121 reference code that occurred before it
require no service action, since SCSI bus 1 is now operational.
3142 I/O Processor detected that the bus is now operational

This reference code and the 3122 reference code that occurred before it
require no service action, since SCSI bus 2 is now operational.
3143 I/O Processor detected that the bus is now operational

Internal and external SCSI cables are connected to SCSI bus 0 at the same
time. Correct the SCSI bus 0 configuration.
3151 I/O processor detected a SCSI bus configuration error SVCDOCS

Internal and external SCSI cables are connected to SCSI bus 1 at the same
time. Correct the SCSI bus 1 configuration.
3200 A tape/CD or disk device reported a failure FI01105
STORIOA
IOP
MEDIA
3203 Disk media format bad FI01105

Reference codes 83
2749, 2767, 2768, 2842, 2843, 2844, 284B, 5702, 570B

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
3205, 3215 Disk sector read error FI01105

Disk unit data may need to be reloaded, but the disk unit does not need to
be replaced.
3250 Disk unit requires initialization before use. USER

Perform a D-IPL and work on errors found in the log.

3300 Storage unit detected a media problem MEDIA
FI00121
Perform IOPIP01. FI01141
3400 I/O processor card detected device error FI02112
STORIOA
NOTE: If external devices are attached check EXTSCSI and DEVTERM first. FI01106
DEVTERM
FI01140
3401 Device backplane problem DEVBPLN
3501 I/O processor Licensed Internal Code error AJDGP01
IOP
3600 to 3601 System log entry only, no service action required
6070 A permanent I/O processor failure occurred IOP
6071 I/O processor Licensed Internal Code error AJDGP01
6072 I/O processor Licensed Internal Code error AJDGP01
IOP
6073 IPL device not ready MEDIA
FI01105
USER
6075 I/O processor resource not available AJDGP01
6076 I/O processor card detected media error MEDIA
AJDGP01
FI01105
6081 to 6083 I/O processor Licensed Internal Code error AJDGP01
IOP
6085 I/O processor Licensed Internal Code error AJDGP01
IOP
MA_BRDG
6200 A permanent IOA hardware error occurred FCIOA
OPT_CLN
6201 IOA LID is not valid AJDGP01
6602 An I/O processor Licensed Internal Code error occurred. AJDGP01
8000 A permanent IOP or cache adaptor card failure occurred. STORIOA
CACHE
Note: DO NOT replace both FRUs at the same time. Exchange the FRUs
one at a time in the order shown.
8002 A permanent cache adaptor card failure occurred. CACHE
STORIOA
Note: DO NOT replace both FRUs at the same time. Exchange the FRUs
one at a time in the order shown.
8004 Voltage drop detected on I/O processor 5 volt power supply. FI01141
STORIOA

84 System i® and System p®: Reference codes

2749, 2767, 2768, 2842, 2843, 2844, 284B, 5702, 570B

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
8005 A recoverable IOP or cache adaptor card error occurred. STORIOA
CACHE
Note: DO NOT replace both FRUs at the same time. Exchange the FRUs
one at a time in the order shown.
8007 A recoverable cache adaptor card error occurred. CACHE
STORIOA
Note: DO NOT replace both FRUs at the same time. Exchange the FRUs
one at a time in the order shown.
8010 to 8011 A permanent cache adaptor card failure occurred. CACHE
STORIOA
The cache adaptor card may be missing, broken or incompatible.
Note: DO NOT replace both FRUs at the same time. Exchange the FRUs
one at a time in the order shown.
8100 I/O processor Licensed Internal Code error AJDGP01
IOP
8130 IOA detected recoverable device bus error

An error occurred on SCSI bus 0. No action is required. This reference code

is logged for information only.
8131 IOA detected recoverable device bus error

An error occurred on SCSI bus 1. No action is required. This reference code

is logged for information only.
8132 IOA detected recoverable device bus error

An error occurred on SCSI bus 2. No action is required. This reference code

is logged for information only.
8133 IOA detected recoverable device bus error

An error occurred on SCSI bus 3. No action is required. This reference code

is logged for information only.
8140 IOA detected recoverable device bus error

No action is required. This reference code is logged for information only.

8141 IOA detected recoverable device error

No action is required. This reference code is logged for information only.

8145 A recoverable I/O processor error occurred. STORIOA
8146 Disk device detected recoverable error FI01105
8150 A permanent I/O processor failure occurred STORIOA
ANYBRDG
8151 I/O processor Licensed Internal Code error AJDGP01
STORIOA
8155 to 8156 A permanent I/O processor failure occurred AJDGP01
STORIOA

Reference codes 85
2749, 2767, 2768, 2842, 2843, 2844, 284B, 5702, 570B

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
8157 I/O adapter card error SVCDOCS

1. If the I/O Processor is not operable and disk units are attached, use
Hardware Service Manager to re-IPL the IOP. Other resources attached to
the IOP may then need to be Varied On.

2. If disk units are not attached, perform the VRYCFG RESET(*YES)

command to reset the IOP and Vary On attached resources.
8200 I/O processor Licensed Internal Code error AJDGP01
IOP
8300 I/O processor card or Licensed Internal Code error STORIOA
IOP
A microprocessor exception occurred on the I/O processor. AJDGP01
8301 Not valid condition in I/O Processor Licensed Internal Code FI01101
AJDGP01
The Licensed Internal Code found a condition that should not have IOP
occurred.
8400 I/O processor Licensed Internal Code error AJDGP01
9000 I/O processor card detected device error FI01105
STORIOA
9001 I/O processor card detected device configuration error SVCDOCS

Perform IOPIP33.
9002 I/O processor card detected device error FI01105
STORIOA
Perform IOPIP16. FI01140
BACKPLN
FI01106
9008 I/O card does not support functions expected by devices SVCDOCS

Perform IOPIP25.
9009 Call your next level of support for assistance SVCDOCS
9010 Cache data associated with attached devices cannot be found SVCDOCS

Perform IOPIP31.
9011 Cache data belongs to devices other than those attached SVCDOCS

Perform IOPIP32.
9012 IOP requires a cache adaptor card but cannot find it. CACHE

The cache adapter card is missing or broken.

Perform IOPIP29.
9013 The IOP and attached cache adaptor card are not compatible. SVCDOCS

Perform IOPIP19.
9020 to 9021 Array not functional due to present hardware configuration. SVCDOCS

Perform IOPIP20.

86 System i® and System p®: Reference codes

2749, 2767, 2768, 2842, 2843, 2844, 284B, 5702, 570B

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
9022 to 9024 Array not functional due to present hardware configuration. SVCDOCS

Perform IOPIP22.
9025 Disk unit is not supported at its physical location. SVCDOCS

Perform IOPIP21.
9026 Array not functional due to present hardware configuration. SVCDOCS

Perform IOPIP22.
9027 Array not functional due to present hardware configuration. SVCDOCS

Perform IOPIP34.
9028 Incorrect hardware configuration change has been detected. SVCDOCS

Contact your next level of support.

902F Array addendum Product Activity Log entry

This entry contains additional array information for 90xx reference codes
when the array contains more than 10 members. Use the 90xx entry that
occurred at the same time as this reference code as the starting point for
this problem.
9030 Array no longer protected due to missing or failed disk unit SVCDOCS

Perform IOPIP21.
9031 Automatic rebuild initiated for array

Either a previous rebuild was interrupted and was automatically restarted,

or a hot spare disk unit was used to automatically rebuild the array. Look
for other reference codes and take action on them.
9040 Array protection temporarily suspended

No action required. Protection will be automatically restarted.

9041 Background array parity check detected and corrected errors AJDGP01

Call your next level of support to report the problem.

9050 Required cache data cannot be located for a disk unit. SVCDOCS

Perform IOPIP30.
9051 IOP cache data exists for a missing or failed device. SVCDOCS

If all configured units are missing, a 9054 reference code may appear in the
product activity log. If so, perform the action indicated for the 9054
reference code.

Otherwise, perform IOPIP27.

9052 Cache data exists for device that has been modified. SVCDOCS

Perform IOPIP28.

Reference codes 87
2749, 2767, 2768, 2842, 2843, 2844, 284B, 5702, 570B

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
9053 IOP resources not available due to previous problems. SVCDOCS

Take action on other IOP reference codes which have surfaced.

Power off the system and remove all new or replacement disk units. IPL
the system to DST. If you cannot perform a type A or B IPL, perform a
type D IPL from removable media.

Look for Product Activity Log entries for other IOP reference codes and
take action on them.
9081 I/O processor card detected device error FI01105
STORIOA
9082 I/O processor card detected device error FI01105
STORIOA
Perform IOPIP16. FI01140
BACKPLN
FI01106
9090 Disk unit has been modified after the last known status. SVCDOCS

Re-IPL the system. If any reference codes are surfaced, go to List of system
reference codes and use the new reference code as the entry point to the
problem.

If you cannot resolve the problem, contact your next level of support.
9091 Incorrect hardware configuration change has been detected. SVCDOCS

Re-IPL the system. If any reference codes are surfaced, go to List of system
reference codes and use the new reference code as the entry point to the
problem.

If you cannot resolve the problem, contact your next level of support.
9092 Disk unit requires initialization before use. SVCDOCS

Perform IOPIP26.
B3B1 to B3B7 A permanent I/O processor failure occurred IOP
B3B8 Multi-adapter bridge error detected. MA_BRDG
IOP
B3B9 A permanent I/O processor failure occurred IOP
B3E0 to B3E1 I/O processor detected a fault condition. IOP
MA_BRDG
B410 to B411 A permanent I/O processor failure occurred STORIOA
B412 Tape/CD or disk bus interface error occurred FI01107
FI01140
Perform IOPIP16. STORIOA
DEVTERM
B935 Unknown hardware detected FI01101
AJDGP01
IOP
MA_BRDG

88 System i® and System p®: Reference codes

2749, 2767, 2768, 2842, 2843, 2844, 284B, 5702, 570B

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
BE00 I/O processor detected a fault condition. AJDGP01
IOP
FI01104
MA_BRDG
FF3D I/O adapter detected a recoverable error STORIOA
ANYBRDG
FF6D I/O processor detected a recoverable system bus error IOP
ANYBUS

Table 2. Failing items details

Failing Item Description Document Description

AJDG301 Vertical Licensed Internal Code Service Functions; APAR or LICTR
AJDGP01 I/O card Licensed Internal Code Service Functions; APAR or LICTR
AJDGP01 I/O processor Licensed Internal Code Service Functions; APAR or LICTR
ANYBRDG System I/O bus or any attached card See the service documentation for instructions.
ANYBUS IOP card bus error See the service documentation for instructions.
BACKPLN Card Enclosure or Planar Board See the service documentation for instructions.
CACHBAT Cache battery pack See the service documentation for instructions.
CACHE Cache adaptor card See the service documentation for instructions.
CMPRES1 Compressed device and compression IOA are See the service documentation for instructions.
not compatible
CTLPNL Control panel, or the interface to the Control See the service documentation for instructions.
panel
DEVBPLN Device backplane See the service documentation for instructions.
DEVTERM Terminating plug See the service documentation for instructions.
FCIOA Fibre Channel IOA See the service documentation for instructions.
IOACNFG Configuration error See the service documentation for instructions.
IOP I/O processor card See the service documentation for instructions.
MA_BRDG Multi-adapter bridge See the service documentation for instructions.
MEDIA Defective media See the service documentation for instructions.
OPT_CLN Fiber optic cleaning kit See the service documentation for instructions.
PCIBUS Any PCI card on the PCI bus See the service documentation for instructions.
STORIOA Storage I/O adapter See the service documentation for instructions.
SVCDOCS Customer engineer directed to system problem See the service documentation for instructions.
analysis
USER System Operator/User See the service documentation for instructions.

(2750, 2751) Reference codes

1. Look at characters 5 through 8 of the top 16 character line of function 11 (4 rightmost characters of
word 1). These 4 characters are the unit reference code.
2. Look at the last 8 characters of the top 16 character line of function 12 (word 3). These 8 characters are
the direct select address of the card (BBBBCcbb). The unit address portion of the card address is
characters 1 through 8 of the bottom 16 character line of function 11 (Word 4). Card locations can be
found using the 16 character address. See SRC Address Formats.

Reference codes 89
2749, 2767, 2768, 2842, 2843, 2844, 284B, 5702, 570B

3. Find the unit reference code in the following table.

Table 1. (2750, 2751) Reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
B980 to B983 I/O adapter hardware error detected FI00719
FI00730

(2761) Reference codes

Table 1. (2761) Reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
B980 to B983 I/O adapter hardware error detected FI00719
FI00730

(2765, 2766, 2787, 280D, 280E, 5704) Reference Codes

If the error is reported on the control panel, the unit reference code is characters 5 through 8 of the top 16
character line of function 11. If the error is reported on the console, the unit reference code is the 4
rightmost characters of word 1.

Find the unit reference code in the following table.

For more on the Failing Item column entries, see Table 2. Failing Items Details, which follows the
reference code table below.

Table 1. (2765, 2766, 2787, 280D, 280E, 5704) Reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
3020 I/O processor detected a configuration error SVCDOCS

Either too many devices or the wrong kind of devices have been
configured under the IOA. Change the configuration.
3100 I/O processor card detected interface error FCINTF
ANYFC
FCIOA
OPT_CLN
3120 I/O processor detected a port failure FCPORT
FCIOA
FCDEV
OPT_CLN
3140 I/O Processor detected that a port is now operational

This reference code and the 3120 reference code that occurred before it
require no service action, since the port is now operational.

90 System i® and System p®: Reference codes

2765, 2766, 2787, 280D, 280E, 5704

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
3400 I/O processor card detected device error FCDEV
FCINTF
ANYFC
FCIOA
OPT_CLN
34FF Format in progress

The device indicated that a format is in progress. When the format is

complete, the device should be useable. No action is required. This
reference code is logged for information only.
8130, 8140 Recovered Fibre Channel interface error

No action required. This reference code is logged for information only.

8141 IOA detected recoverable device error

No action required. This reference code is logged for information only.

8145 A recoverable I/O processor error occurred. FCIOA
OPT_CLN
8146 Disk device detected recoverable error FCDEV
8150 A permanent I/O processor failure occurred FCIOA
ANYBRDG
OPT_CLN
8151 I/O processor Licensed Internal Code error AJDGP01
FCIOA
IOP
OPT_CLN
8155 to 8156 A permanent I/O processor failure occurred AJDGP01
FCIOA
OPT_CLN
9091 to 9092 Incorrect hardware configuration change has been detected. SVCDOCS

Reset the I/O processor and then IPL the I/O processor. For information
about how to reset and IPL the I/O processor, see Debug the resource. If an
I/O processor reset and I/O processor IPL does not resolve the problem,
contact your next level of support.
FF3D Recovered IOA error FCIOA
ANYBRDG
OPT_CLN

Table 2. Failing items details

Failing Item Description Document Description

AJDGP01 I/O processor Licensed Internal Code Service Functions; APAR or LICTR
ANYBRDG System I/O bus or any attached card See the service documentation for instructions.
ANYFC Any Fibre Channel device See the service documentation for instructions.
FCDEV Fibre Channel device See the service documentation for instructions.
FCINTF Fibre Channel interface See the service documentation for instructions.
FCIOA Fibre Channel IOA See the service documentation for instructions.
FCPORT Port not operational See the service documentation for instructions.
IOP I/O processor card See the service documentation for instructions.

Reference codes 91
2765, 2766, 2787, 280D, 280E, 5704

Failing Item Description Document Description

OPT_CLN Fiber optic cleaning kit See the service documentation for instructions.
SVCDOCS Customer engineer directed to system problem See the service documentation for instructions.
analysis

(2771, 2772) Reference codes

1. Look at characters 5 through 8 of the top 16 character line of function 11 (4 rightmost characters of
word 1). These 4 characters are the unit reference code.
2. Look at the last 8 characters of the top 16 character line of function 12 (word 3). These 8 characters are
the direct select address of the card (BBBBCcbb). The unit address portion of the card address is
characters 1 through 8 of the bottom 16 character line of function 11 (Word 4). Card locations can be
found using the 16 character address. See SRC Address Formats.
3. Find the unit reference code in the following table.

For more on the Failing Item column entries, see Table 2. Failing items details, which follows the
reference code table below.

Table 1. (2771, 2772) Reference codes

Table 2. Failing items details

Failing Item Description Document Description

AJDGP01 LIC - Input/Output Processor Licensed Internal Service Functions; APAR or LICTR
Code
MA_BRDG Multi-adapter bridge See the service documentation for instructions.

(281x) Reference codes

Table 1. (281x) Reference codes

92 System i® and System p®: Reference codes

281x

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
B910 I/O adapter hardware error detected FI00719
FI00730
FI00718

(2838, 2849) Reference codes

1. Look at characters 5 through 8 of the top 16 character line of function 11 (4 rightmost characters of
word 1). These 4 characters are the unit reference code.
2. Look at the last 8 characters of the top 16 character line of function 12 (word 3). These 8 characters are
the direct select address of the card (BBBBCcbb). The unit address portion of the card address is
characters 1 through 8 of the bottom 16 character line of function 11 (Word 4). Card locations can be
found using the 16 character address. See SRC Address Formats.
3. Find the unit reference code in the following table.

For more on the Failing Item column entries, see Table 2. Failing items details, which follows the
reference code table below.

Table 1. (2838, 2849) Reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
B904 I/O adapter Licensed Internal Code failed. AJDGP01
FI00719
B930 I/O adapter Licensed Internal Code failed. AJDGP01
FI00718
FI00719
B931 I/O adapter hardware error detected FI00719
FI00718
AJDGP01
MA_BRDG
B933 Incompatible hardware detected. FI00719
AJDGP01

Table 2. Failing items details

Failing Item Description Document Description

AJDGP01 LIC - Input/Output Processor Licensed Internal Service Functions; APAR or LICTR
Code
MA_BRDG Multi-adapter bridge See the service documentation for instructions.

(2847) Reference codes

Find the unit reference code in the following table. For more on the Failing Item column entries, see Table
2. Failing items details, which follows the reference code table below.

Table 1. (2847) Reference codes

Reference codes 93
2847

The I/O processor error log is being filled faster than the errors are being
reported to the system. Check other errors reported to the system and
correct them.
3000 A permanent I/O processor failure occurred FCIOA
IOP
MA_BRDG
OPT_CLN
3001 Not valid condition in I/O Processor Licensed Internal Code IOP
AJDGP01
The Licensed Internal Code found a condition that should not have
occurred.
3002 Addressed device is not responding FCPORT
FCDEV
FCIOA
FCINTF
OPT_CLN
3006 System bus error IOP
ANYBUS
FCIOA
OPT_CLN
3080 I/O processor Licensed Internal Code error AJDGP01
3081 System log entry only, no service action required
3084 I/O processor card or Licensed Internal Code error AJDGP01
IOP
A microprocessor exception occurred on the I/O processor. FCIOA
MA_BRDG
OPT_CLN
3087 I/O processor resource not available AJDGP01
AJDG301
The Licensed Internal Code could not allocate resources on the I/O FCIOA
processor card. OPT_CLN
3100 I/O processor card detected interface error FCINTF
ANYFC
FCIOA
OPT_CLN
3109 I/O processor timed out a device command FCDEV
FCINTF
FCIOA
OPT_CLN

94 System i® and System p®: Reference codes

2847

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
3120 I/O processor detected a port failure FCPORT
FCIOA
FCDEV
OPT_CLN
3200 A disk device reported a failure FCDEV
FCIOA
IOP
OPT_CLN
3501 I/O processor Licensed Internal Code error AJDGP01
IOP
6070 A permanent I/O processor failure occurred IOP
6071 I/O processor Licensed Internal Code error AJDGP01
6072 I/O processor Licensed Internal Code error AJDGP01
IOP
6075 I/O processor resource not available AJDGP01
6076 I/O processor card detected media error AJDG301
AJDGP01
FCDEV
6081 to 6083 I/O processor Licensed Internal Code error AJDGP01
IOP
6085 I/O processor Licensed Internal Code error AJDGP01
IOP
MA_BRDG
6200 A permanent IOA hardware error occurred FCIOA
OPT_CLN
6201 IOA LID is not valid AJDGP01
8100 I/O processor Licensed Internal Code error AJDGP01
IOP
8150 A permanent I/O processor failure occurred FCIOA
ANYBRDG
OPT_CLN
8155 to 8156 A permanent I/O processor failure occurred AJDGP01
FCIOA
OPT_CLN
8200 I/O processor Licensed Internal Code error AJDGP01
IOP
8300 I/O processor card or Licensed Internal Code error FCIOA
IOP
A microprocessor exception occurred on the I/O processor. AJDGP01
OPT_CLN
8301 Not valid condition in I/O Processor Licensed Internal Code FCIOA
AJDGP01
The Licensed Internal Code found a condition that should not have IOP
occurred. OPT_CLN
B3B1 to B3B7 A permanent I/O processor failure occurred IOP
B3B8 Multi-adapter bridge error detected. MA_BRDG
IOP
B3E0 to B3E1 I/O processor detected a fault condition. IOP
MA_BRDG

Reference codes 95
2847

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
B935 Unknown hardware detected FCIOA
AJDGP01
IOP
MA_BRDG
OPT_CLN
BE00 I/O processor detected a fault condition. AJDGP01
IOP
FCIOA
MA_BRDG
OPT_CLN

Table 2. Failing items details

Failing Item Description Document Description

AJDG301 Vertical Licensed Internal Code Service Functions; APAR or LICTR
AJDGP01 I/O processor Licensed Internal Code Service Functions; APAR or LICTR
AJDGP01 I/O card Licensed Internal Code Service Functions; APAR or LICTR
ANYBRDG System I/O bus or any attached card See the service documentation for instructions.
ANYBUS IOP card bus error See the service documentation for instructions.
ANYFC Any Fibre Channel device See the service documentation for instructions.
BACKPLN Card Enclosure or Planar Board See the service documentation for instructions.
CACHBAT Cache battery pack See the service documentation for instructions.
CACHE Cache adaptor card See the service documentation for instructions.
CMPRES1 Compressed device and compression IOA are See the service documentation for instructions.
not compatible
CTLPNL Control panel, or the interface to the Control See the service documentation for instructions.
panel
DEVBPLN Device backplane See the service documentation for instructions.
DEVTERM Terminating plug See the service documentation for instructions.
FCDEV Fibre Channel device See the service documentation for instructions.
FCINTF Fibre Channel interface See the service documentation for instructions.
FCIOA Fibre Channel IOA See the service documentation for instructions.
FCPORT Port not operational See the service documentation for instructions.
IOACNFG Configuration error See the service documentation for instructions.
IOP I/O processor card See the service documentation for instructions.
MA_BRDG Multi-adapter bridge See the service documentation for instructions.
MEDIA Defective media See the service documentation for instructions.
OPT_CLN Fiber optic cleaning kit See the service documentation for instructions.
PCIBUS Any PCI card on the PCI bus See the service documentation for instructions.
STORIOA Storage I/O adapter See the service documentation for instructions.
SVCDOCS Customer engineer directed to system problem See the service documentation for instructions.
analysis
USER System Operator/User See the service documentation for instructions.

96 System i® and System p®: Reference codes

287F

(287F) Reference codes

For more on the Failing Item column entries, see Table 2. Failing items details, which follows the
reference code table below.

Table 1. (287F) Reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
B9A0 I/O adapter hardware error detected FI00719
AJDGP01

Table 2. Failing items details

Failing Item Description Document Description

AJDGP01 Input/Output Processor Licensed Internal Code Service Functions; APAR or LICTR

(2890) Reference codes

Find the unit reference code in the following table. For more on the Failing Item column entries, see Table
2. Failing items details, which follows the reference code table below.

Table 1. (2890) Reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
0A17 A permanent I/O processor failure occurred IOP
MA_BRDG
AJDG301
AJDGP01
0A22 Adapter card storage error AJDGP01
AJDG301
IOP
MA_BRDG
1307 I/O adapter resource not available. AJDGP01
AJDG301
1310 I/O adapter resource not available. IOP
AJDGP01
The INS processor error log is being filled faster than the errors are being
reported to the system. Check other errors reported to the system and
correct them.
3000 An I/O adapter failure occurred. IOP
AJDGP01
3001 I/O adapter Licensed Internal Code failed. IOP
AJDGP01
3006 An I/O adapter failure occurred. IOP
ANYBUS

Reference codes 97
2890

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
3080 I/O adapter Licensed Internal Code failed. AJDGP01
3081 I/O adapter error; logged only.
3084 An I/O adapter failure occurred. AJDGP01
IOP
IOA
MA_BRDG
3087 I/O adapter resource not available. AJDGP01
AJDG301
NTUSER
IOA
6070 An I/O adapter failure occurred. IOP
6071 I/O adapter Licensed Internal Code failed. AJDGP01
6072 I/O adapter Licensed Internal Code failed. AJDGP01
IOP
6075 I/O adapter resource not available. AJDGP01
6083 I/O adapter Licensed Internal Code failed. AJDGP01
IOP
6085 I/O adapter Licensed Internal Code failed. AJDGP01
IOP
MA_BRDG
6201 A permanent I/O processor failure occurred IOP
AJDGP01
6202 I/O processor Licensed Internal Code error AJDGP01
IOP
6210 I/O processor Licensed Internal Code error AJDGP01
6221 I/O processor resource not available AJDG301
6222 A permanent I/O processor failure occurred AJDGP01
IOP
6223 A permanent I/O processor failure occurred IOP
AJDGP01
6224 A permanent I/O processor failure occurred DISKIMG
AJDGP01
IOP
MEMORY
6225 A permanent I/O processor failure occurred AJDGP01
AJDG301
IOP
6226 I/O processor card detected device error AJDG301
AS4NTDD
6227 A HostLAN error was detected NTUSER
AJDGP01
IOP
6228 Windows initiated a warm boot AJDGP01
IOP
6501 A Windows fatal error occurred IOP
AJDGP01
6502 A Windows fatal error occurred AJDGP01
IOP

98 System i® and System p®: Reference codes

2890

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
6530 A Virtual SCSI error was detected NTVSCSI
NTOPSYS
6531 A Virtual SCSI error was detected NTVSCSI
AS4NTDD
NTOPSYS
AJDGP01
6532 A Virtual SCSI error was detected NTOPSYS
AJDGP01
AS4NTDD
6533 A Virtual SCSI error was detected NTUSER
NTOPSYS
AS4NTDD
6534 A Virtual SCSI error was detected AS4NTDD
AJDGP01
NTOPSYS
6535 A Virtual SCSI error was detected NTUSER
NTDEVDR
AJDGP01
6538 A Virtual SCSI error was detected NTVSCSI
NTOPSYS
6539 A Virtual SCSI error was detected NTVSCSI
AS4NTDD
NTOPSYS
AJDGP01
653A A Virtual SCSI error was detected NTOPSYS
AJDGP01
AS4NTDD
653B A Virtual SCSI error was detected NTUSER
NTOPSYS
AS4NTDD
653C A Virtual SCSI error was detected AS4NTDD
AJDGP01
NTOPSYS
653D A Virtual SCSI error was detected NTUSER
NTDEVDR
AJDGP01
653F A Virtual SCSI error was detected NTDEVDR
NTOPSYS
AJDG301
6540 A Virtual SCSI error was detected NTVSCSI
AJDGP01
AJDG301
6541 A permanent I/O processor failure occurred IOP
AJDGP01
6542 Licensed Internal Code error detected. AJDG301
AJDGP01
6543 A Windows fatal error occurred NTOPSYS
NTVSCSI
6580 A Windows fatal error occurred DISKIMG
IOP
AJDGP01

Reference codes 99
2890

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
65B0 A HostLAN error was detected NTLANDD
NTOPSYS
65B1 A HostLAN error was detected NTLANDD
NTOPSYS
AJDG301
65B2 A HostLAN error was detected NTDEVDR
NTOPSYS
AJDG301
8301 An I/O adapter failure occurred. AJDGP01
IOP
B3B1 to B3B7 A permanent I/O processor failure occurred IOP
B3B8 Multi-adapter bridge error detected. MA_BRDG
IOP
B3B9 A permanent I/O processor failure occurred IOP
B3E0 I/O processor detected a fault condition IOP
MA_BRDG
B3E1 An I/O adapter failure occurred. IOP
MA_BRDG
B4B0 I/O adapter hardware error detected IOP
B4B1 I/O adapter hardware error detected IOP
MEMORY
B4B2 Incompatible hardware detected. IOP
B4B3 Incompatible hardware detected. IOA
B4B4 I/O adapter hardware error detected IOP
IOA
MEMORY
B4B5 An I/O adapter failure occurred. AJDGP01
IOP
B4B8 Adapter card storage error MEMORY
IOP
B4B9 An I/O adapter failure occurred. IOP
B4BC I/O adapter error; logged only. IOP
IOA
B4BE Adapter card storage error MEMORY
IOP
B904 A permanent I/O processor failure occurred AJDGP01
IOP
B935 Incompatible hardware detected. IOA
AJDGP01
IOP
MA_BRDG
B960 I/O processor Licensed Internal Code error AJDGP01
IOP
IOA
B961 An error was detected on one of the attached adapter cards. IOA
IOP
AJDGP01

100 System i® and System p®: Reference codes

2890

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
BE00 An I/O adapter failure occurred. AJDGP01
IOP
IOA
MA_BRDG

Table 2. Failing items details

Failing Item Description Document Description

AJDG301 Licensed Internal Code See the service documentation for instructions.
AJDGP01 I/O card Licensed Internal Code See the service documentation for instructions.
ANYBUS System bus See the service documentation for instructions.
AS4NTDD Device Driver See the service documentation for instructions.
DISKIMG Server Storage Space Object See the service documentation for instructions.
IOA IOA Communications adapter card Repair and Parts; removal and installation
procedures
IOP Communications Input/Output Processor card Repair and Parts; removal and installation
procedures
IOP I/O adapter card Repair and Parts; removal and installation
procedures
MA_BRDG Multi-adapter bridge See the service documentation for instructions.
MEMORY DIMM 0 See the service documentation for instructions.
MEMORY Storage card See the service documentation for instructions.
MEMORY DIMM in first populated DIMM position See the service documentation for instructions.
MEMORY DIMM 3 See the service documentation for instructions.
MEMORY DIMM 2 See the service documentation for instructions.
MEMORY DIMM 1 See the service documentation for instructions.
NTDEVDR Device Driver See the service documentation for instructions.
NTLANDD Device Driver See the service documentation for instructions.
NTOPSYS Windows Operating System See the service documentation for instructions.
NTUSER User-initiated action See the service documentation for instructions.
NTVSCSI Device Driver See the service documentation for instructions.

(2892) Reference codes

Find the unit reference code in the following table. For more on the Failing Item column entries, see Table
2. Failing items details, which follows the reference code table below.

Table 1. (2892) Reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
0A17 A permanent I/O processor failure occurred IOP
MA_BRDG
AJDG301
AJDGP01

Reference codes 101

2892

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
0A22 Adapter card storage error AJDGP01
AJDG301
IOP
MA_BRDG
1307 I/O adapter resource not available. AJDGP01
AJDG301
1310 I/O adapter resource not available. IOP
AJDGP01
The INS processor error log is being filled faster than the errors are being
reported to the system. Check other errors reported to the system and
correct them.
1317 I/O processor card error SVCDOCS

Display the Service Action Log entry for this SRC. If the Failing Item
indicates to replace hardware, then replace hardware. If the Failing Item
indicates SVCDOCS, then do NOT replace hardware. This is a recoverable
error. If the resource is not operable, use Hardware Service Manager to
re-IPL the resource. Perform the VRYCFG command to Vary On the
NWSD.
3000 An I/O adapter failure occurred. IOP
AJDGP01
3001 I/O adapter Licensed Internal Code failed. IOP
AJDGP01
3006 An I/O adapter failure occurred. IOP
ANYBUS
3080 I/O adapter Licensed Internal Code failed. AJDGP01
3081 I/O adapter error; logged only.
3084 An I/O adapter failure occurred. AJDGP01
IOP
IOA
MA_BRDG
3087 I/O adapter resource not available. AJDGP01
AJDG301
NTUSER
IOA
6070 An I/O adapter failure occurred. IOP
6071 I/O adapter Licensed Internal Code failed. AJDGP01
6072 I/O adapter Licensed Internal Code failed. AJDGP01
IOP
6075 I/O adapter resource not available. AJDGP01
6083 I/O adapter Licensed Internal Code failed. AJDGP01
IOP
6085 I/O adapter Licensed Internal Code failed. AJDGP01
IOP
MA_BRDG
6201 A permanent I/O processor failure occurred IOP
AJDGP01
6202 I/O processor Licensed Internal Code error AJDGP01
IOP
6204 I/O adapter failure due to a thermal condition IOP

102 System i® and System p®: Reference codes

2892

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
6210 I/O processor Licensed Internal Code error AJDGP01
6221 I/O processor resource not available AJDG301
6222 A permanent I/O processor failure occurred AJDGP01
IOP
6223 A permanent I/O processor failure occurred IOP
AJDGP01
6224 A permanent I/O processor failure occurred DISKIMG
AJDGP01
IOP
MEMORY
6225 A permanent I/O processor failure occurred AJDGP01
AJDG301
IOP
6226 I/O processor card detected device error AJDG301
AS4NTDD
6227 A HostLAN error was detected NTUSER
AJDGP01
IOP
6228 Windows initiated a warm boot AJDGP01
IOP
6501 A Windows fatal error occurred IOP
AJDGP01
6502 A Windows fatal error occurred AJDGP01
IOP
6530 A Virtual SCSI error was detected NTVSCSI
NTOPSYS
6531 A Virtual SCSI error was detected NTVSCSI
AS4NTDD
NTOPSYS
AJDGP01
6532 A Virtual SCSI error was detected NTOPSYS
AJDGP01
AS4NTDD
6533 A Virtual SCSI error was detected NTUSER
NTOPSYS
AS4NTDD
6534 A Virtual SCSI error was detected AS4NTDD
AJDGP01
NTOPSYS
6535 A Virtual SCSI error was detected NTUSER
NTDEVDR
AJDGP01
6538 A Virtual SCSI error was detected NTVSCSI
NTOPSYS
6539 A Virtual SCSI error was detected NTVSCSI
AS4NTDD
NTOPSYS
AJDGP01

Reference codes 103

2892

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
653A A Virtual SCSI error was detected NTOPSYS
AJDGP01
AS4NTDD
653B A Virtual SCSI error was detected NTUSER
NTOPSYS
AS4NTDD
653C A Virtual SCSI error was detected AS4NTDD
AJDGP01
NTOPSYS
653D A Virtual SCSI error was detected NTUSER
NTDEVDR
AJDGP01
653F A Virtual SCSI error was detected NTDEVDR
NTOPSYS
AJDG301
6540 A Virtual SCSI error was detected NTVSCSI
AJDGP01
AJDG301
6541 A permanent I/O processor failure occurred IOP
AJDGP01
6542 Licensed Internal Code error detected. AJDG301
AJDGP01
6543 A Windows fatal error occurred NTOPSYS
NTVSCSI
6580 A Windows fatal error occurred DISKIMG
IOP
AJDGP01
65B0 A HostLAN error was detected NTLANDD
NTOPSYS
65B1 A HostLAN error was detected NTLANDD
NTOPSYS
AJDG301
65B2 A HostLAN error was detected NTDEVDR
NTOPSYS
AJDG301
8301 An I/O adapter failure occurred. AJDGP01
IOP
B3B1 to B3B7 A permanent I/O processor failure occurred IOP
B3B8 Multi-adapter bridge error detected. MA_BRDG
IOP
B3B9 A permanent I/O processor failure occurred IOP
B3E0 I/O processor detected a fault condition IOP
MA_BRDG
B3E1 An I/O adapter failure occurred. IOP
MA_BRDG
B4B0 I/O adapter hardware error detected IOP
B4B1 I/O adapter hardware error detected IOP
MEMORY
B4B2 Incompatible hardware detected. IOP

104 System i® and System p®: Reference codes

2892

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
B4B3 Incompatible hardware detected. IOA
B4B4 I/O adapter hardware error detected IOP
IOA
MEMORY
B4B5 An I/O adapter failure occurred. AJDGP01
IOP
B4B8 Adapter card storage error MEMORY
IOP
B4B9 An I/O adapter failure occurred. IOP
B4BC I/O adapter error; logged only. IOP
IOA
B4BE Adapter card storage error MEMORY
IOP
B904 A permanent I/O processor failure occurred AJDGP01
IOP
B935 Incompatible hardware detected. IOA
AJDGP01
IOP
MA_BRDG
B960 I/O processor Licensed Internal Code error AJDGP01
IOP
IOA
B961 An error was detected on one of the attached adapter cards. IOA
IOP
AJDGP01
BE00 An I/O adapter failure occurred. AJDGP01
IOP
IOA
MA_BRDG

Table 2. Failing items details

Failing Item Description Document Description

Reference codes 105

2892

Failing Item Description Document Description

MEMORY DIMM in first populated DIMM position - See the service documentation for instructions.
DIMM 0 or DIMM 1
MEMORY Storage card See the service documentation for instructions.
MEMORY DIMM 3 See the service documentation for instructions.
MEMORY DIMM 2 See the service documentation for instructions.
MEMORY DIMM 0 See the service documentation for instructions.
MEMORY DIMM 1 See the service documentation for instructions.
NTDEVDR Device Driver See the service documentation for instructions.
NTLANDD Device Driver See the service documentation for instructions.
NTOPSYS Windows Operating System See the service documentation for instructions.
NTUSER User-initiated action See the service documentation for instructions.
NTVSCSI Device Driver See the service documentation for instructions.
SVCDOCS Customer engineer directed to system problem See the service documentation for instructions.
analysis

(3490) Tape unit reference codes

A tape or tape library device failure occurred.

Note: Use this table to handle reference codes that might be displayed during a type D IPL to install the
operating system. If you are not performing a type D IPL of the operating system, consult any
error logs that you find in the Serviceable Event View. If you cannot locate an error log in the
Serviceable Event View that corresponds with the failure, run a verification test for the tape unit.
1. Verify that the device has power.
2. Check the device for any error indications. Refer to the device service information to resolve any error
indications.
3. Clean the recording head in the tape device.
4. Attempt the failing operation again. Does the operation complete successfully?
v Yes: You have corrected the problem. This ends the procedure.
v No: Look at the 4 rightmost characters of the Data display for Function 11, which represent the unit
reference code. Find the unit reference code in the following table.

For more on the Failing Item column entries, see Table 2. Tape unit failing items details, which follows
the reference code table below.

Table 1. (3490) Tape unit reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
0xxx, 1xxx, 2000 Tape unit failure

Use online problem analysis and the 3490 Tape Unit service information to
analyze the problem.
2001 Tape path dirty or write data check error MHK0001
DHK0002
Clean the tape path using the cleaning procedures in the 3490 Magnetic
Tape Subsystem Operator’s Guide, GA32-0124.

Use the 3490 Tape Unit service information to continue analyzing the
problem.

106 System i® and System p®: Reference codes

3490

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
2003 Tape path dirty or write identification record error MHK0001
DHK0002
Clean the tape path using the cleaning procedures in the 3490 Magnetic
Tape Subsystem Operator’s Guide, GA32-0124.

Use the 3490 Tape Unit service information to continue analyzing the
problem.
2008 Tape path dirty or read data check error MHK0001
DHK0002
Clean the tape path using the cleaning procedures in the 3490 Magnetic
Tape Subsystem Operator’s Guide, GA32-0124.

Use the 3490 Tape Unit service information to continue analyzing the
problem.
2009 Tape path dirty or read identification record error MHK0001
DHK0002
Clean the tape path using the cleaning procedures in the 3490 Magnetic
Tape Subsystem Operator’s Guide, GA32-0124.

Use the 3490 Tape Unit service information to continue analyzing the
problem.
2010 Tape unit failure

Use online problem analysis and the 3490 Tape Unit service information to
continue analyzing the problem.
2014 Recoverable tape unit failure; logged only

No action required. This reference code is logged for information only.

2015 Tape unit failure DHK0002
FI00856
Clean the tape path using the cleaning procedures in the 3490 Magnetic FI00845
Tape Subsystem Operator’s Guide, GA32-0124.

Use the 3490 Tape Unit service information to continue analyzing the
problem.
2017 Write Protect violation reported by tape unit; logged only

No action required. This reference code is logged for information only.

202x, 205x, 206x, Tape unit failure
21xx, 22xx
Use online problem analysis and the 3490 Tape Unit service information to
continue analyzing the problem.
23xx Tape Library failure

Use the 3494 Tape Library Dataserver Maintenance Information to analyze

the problem.
26xx, 27xx, 3xxx, Tape unit failure
4xxx, 5xxx, 6xxx,
7xxx, 8xxx Use online problem analysis and the 3490 Tape Unit service information to
continue analyzing the problem.
9020 I/O processor detected a SCSI bus configuration error UHKCNFG
FI00851
Before exchanging any parts, verify that the following conditions are not FI00130
present:
v Tape and DASD devices attached to the same type 6501 I/O processor
v A device type or model that is not given support

Reference codes 107

3490

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
9100 Interface error detected by I/O processor or by tape unit FI00851
FI00856
Before exchanging any parts, do the following: 05H3834
1. Ensure that an interposer is connected between the I/O processor and EXTSCSI
the SCSI cable. 61G8324
2. Ensure that the SCSI cable between the interposer and the device is
seated correctly, and that there are no bent or damaged pins on the
SCSI cable.
3. Ensure that a terminating plug is attached to the device end of the SCSI
cable.
9200 I/O processor addressed the tape unit; no response FI00851
FI00856
Before exchanging any parts, do the following: 05H3834
1. Ensure that the device is powered on. EXTSCSI
2. Ensure that an interposer is connected between the I/O processor and 61G8324
the SCSI cable.
3. Ensure that the SCSI cable between the interposer and the device is
seated correctly, and that there are no bent or damaged pins on the
SCSI cable.
4. Ensure that a terminating plug is attached to the device end of the SCSI
cable.
9201 Tape unit command timeout FI00851
FI00856
Before exchanging any parts, do the following: 05H3834
1. Ensure that the device is powered on. EXTSCSI
2. Ensure that an interposer is connected between the I/O processor and 61G8324
the SCSI cable.
3. Ensure that the SCSI cable between the interposer and the device is
seated correctly, and that there are no bent or damaged pins on the
SCSI cable.
4. Ensure that a terminating plug is attached to the device end of the SCSI
cable.
9210 Illegal or unsupported tape unit response FI00851
FI00856
FI00130
9300 Tape unit failure DHK0002
9301 Tape device failure, redundancy lost DHK0002

The tape unit detected a hardware failure that does not prevent the tape
unit from completing the present operation.

See the 3590 Tape Unit service information to determine the failing item.
9302 I/O processor Licensed Internal Code error FI00130

108 System i® and System p®: Reference codes

3490

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
9320 Tape device Licensed Internal Code failure FI00851

Do the following:
1. Take a dump of the tape device Licensed Internal Code (see the 3490
Tape Drive service information).
2. Power off the tape unit. Then power on the tape unit to resume
operation.
9350 Tape unit detected a read or write error on tape medium MHKTMED
UHKCLN
A permanent read or write error occurred, and the tape unit determined FI00851
that the tape cartridge is defective. Exchange the tape cartridge.
9351 I/O processor Licensed Internal Code error FI00130

If the system is operational, take a dump of the I/O processor data. For
more information, see the iSeries Service Functions information or ask your
next level of support for assistance.
9355 The data format is incorrect; the tape cannot be read MHKTMED
UHKCLN
The tape device does not give support to the data format on the tape FI00851
cartridge. Re-initialize the tape cartridge or use a different tape cartridge.
9500 I/O processor Licensed Internal Code error FI00130

Use online problem analysis and the 3490 Tape Unit service information to
continue analyzing the problem.
9800 to 9803 I/O processor successfully recovered from temporary error

No action required. This reference code is logged for information only.

9810 Problem analysis has determined a part should be replaced.

This reference code is used for ending Online Problem Analysis with a list
of failing items. (Information Only)
9899 Problem analysis completed, the problem has been corrected. UHKFIXD

This reference code is used for ending Online Problem Analysis when no
problem was found or the problem was corrected.
9900 Licensed Internal Code for tape unit was not upgraded

The I/O processor loading of Licensed Internal Code (LIC) to the

programmable tape unit was not completed.

The tape unit will continue to operate with the previous LIC. You may do
either of the following:
v Wait for next IPL when the system will attempt to load the LIC for the
tape unit again.
v Perform TU-PIP4 to reset the IOP and the tape unit. When the IOP is
reset, if the device has the wrong level of LIC, the IOP will attempt to
load the new LIC.

Reference codes 109

3490

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
Axxx, Bxxx, Cxxx, Tape unit failure
Dxxx, Exxx, F00x
Use online problem analysis and the 3490 Tape Unit service information to
continue analyzing the problem.
FFD5 Device error reported; tape I/O processor UHK0003
DHK0002
Verify the following:
1. That power is switched on in the 3490 Tape Unit Rack:
v Set the 3490 Rack Unit Emergency Power Off switch to the On
position.
v Ensure that the 3490 Rack Enable/Off switch is set to the Enable
position.
v Press the 3490 Rack Power On button.
2. Verify the following on 3490 Tape Unit:
v The Channel Enable/Disable switches are set to the Enable position.
v The Normal/Test switch is set to the Normal position.
v The CU Online/Offline switch is set to the Online position.
v The Drive Address Online/Offline switches are set to the Online
position.
v The Drive DC Power switches are set to the On position.

If you are attempting to perform an IPL from the device that had the error,
verify that the drive control unit address switch has an address of
hexadecimal 7 and the drive unit address switch has an address of 0.

Use the 3490 Tape Unit service information to continue analyzing the
problem.
FFF6 Volume statistics; logged only

No action required. This reference code is logged for information only.

Table 2. Tape unit failing items details

Failing Item Description Document Description

05H3834 Interposer Magnetic tape subsystem service information
61G8324 Terminating plug Magnetic tape subsystem service information
DHK0002 I/O device Use the sense bytes and 3490 MI to find the
failing items
EXTSCSI External signal cable Problem Analysis; Symbolic FRU Isolation
MHK0001 Tape Magnetic tape subsystem operator’s information
MHKTMED Defective tape Magnetic tape subsystem operator’s information
UHK0003 I/O device not communicating Magnetic tape subsystem operator’s information
UHKCLN Tape unit needs cleaning Magnetic tape subsystem operator’s information
UHKCNFG Tape configuration detected by I/O processor; Installation
not valid
UHKUSRT System Operator/User System operation information

(3494) Tape library reference codes

A tape or tape library device failure occurred.

110 System i® and System p®: Reference codes

3494

Note: Use this table to handle reference codes that might be displayed during a type D IPL to install the
operating system. If you are not performing a type D IPL of the operating system, consult any
error logs that you find in the Serviceable Event View. If you cannot locate an error log in the
Serviceable Event View that corresponds with the failure, run a verification test for the tape unit.
1. Verify that the device has power.
2. Check the 3494 Library Manager console for error indications. Refer to the 3494 service information to
resolve any error indications.
3. Attempt the failing operation again. Does the operation complete successfully?
v Yes: The problem has been corrected. This ends the procedure.
v No: Look at the 4 rightmost characters of the Data display for Function 11, which represent the unit
reference code. Find the unit reference code in the following table.

For more on the Failing Item column entries, see Table 2. Tape library failing items details, which follows
the reference code table below.

Table 1. (3494) Tape library reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
2301 Library device failure 3494

Library attachment facility equipment check.

Use the 3494 Tape Library Dataserver Maintenance Information and follow
the procedures for analyzing a ″LIBRARY PROBLEM - NO ERROR
MESSAGE.″
2303 Library device failure DHALIBC
DHADEVC
Device control unit and library manager Licensed Internal Code are
incompatible.

Use the 3494 Tape Library Dataserver Maintenance Information and follow
the procedures for analyzing a ″LIBRARY PROBLEM - NO ERROR
MESSAGE.″
2306 to 2307 Library device failure 3494

Library vision failure.

Use the 3494 Tape Library Dataserver Maintenance Information and follow
the procedures for analyzing a ″LIBRARY PROBLEM - NO ERROR
MESSAGE.″
2308 Library device failure 3494

Library manager equipment check.

Use the 3494 Tape Library Dataserver Maintenance Information and follow
the procedures for analyzing a ″LIBRARY MANAGER HARDWARE
PROBLEM″
2309 Library device failure 3494

Library equipment check.

Use the 3494 Tape Library Dataserver Maintenance Information and follow
the procedures for analyzing a ″LIBRARY PROBLEM - NO ERROR
MESSAGE.″

Reference codes 111

3494

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
2310 to 2311 Library device requires operator intervention

Put the library into pause mode and perform the intervention indicated on
the library manager console.
2319 Tape unit failure FI00851

Use the tape unit service information to analyze the failure.

2321 Library enclosure environmental alert was detected. 3494

Use the 3494 Tape Library Dataserver Maintenance Information and follow
the procedures for analyzing a ″LIBRARY PROBLEM - NO ERROR
MESSAGE.″

Table 2. Tape library failing items details

Failing Item Description Document Description

3494 Library device IBM 3494 Maintenance Information, SA37-0270
DHADEVC 3490 Control Unit Licensed Internal Code Refer to I/O device service information
DHALIBC 3494 Library Manager Licensed Internal Code IBM 3494 Maintenance Information, SA37-0270

(3570) Tape unit reference codes

A tape or tape library device failure occurred.

For more on the Failing Item column entries, see Table 2. Tape unit failing items details, which follows
the reference code table below.

Table 1. (3570) Tape unit reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
9020 I/O processor detected a SCSI bus configuration error UHZCNFG
DHZDEV
Before exchanging any parts, verify that the following conditions are not FI00130
present:
v Tape and DASD devices attached to an I/O processor that does not
support tape and DASD devices at the same time.
v A device type or model that is not given support.

112 System i® and System p®: Reference codes

3570

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
9100 Interface error detected by I/O processor or by tape unit DHZDEV
FI00131
Before exchanging any parts, do the following: 05H3834
1. Ensure that an interposer is connected between the I/O processor and EXTSCSI
the SCSI cable. 61G8324
2. Ensure that the SCSI cable between the interposer and the device is
seated correctly, and that there are no bent or damaged pins on the
SCSI cable.
3. Ensure that a terminating plug is attached to the device end of the SCSI
cable.
9101 Fibre Channel interface error detected FCIOA
FCDEV
If the attached device is an external device, do the following before FCCABLE
exchanging any parts:
1. Ensure that the Fibre Channel cable is correctly connected to the ports.
2. Clean the Fibre Channel connectors.
3. If there is a hub attached, verify that the hub is operational.
4. If there is a gateway device attached, refer to the gateway device
service documentation for additional problem analysis procedures.
5. refer to the tape device service documentation for additonal problem
analysis procedures.
9102 Gateway device detected a SCSI interface error DHZDEV
FCGATE
Use the gateway device service documentation to analyze the problem. EXTSCSI
61G8324
9200 I/O processor addressed the tape unit; no response DHZDEV
FI00131
Before exchanging any parts, do the following: 05H3834
1. Ensure that the device is powered on. EXTSCSI
2. Ensure that an interposer is connected between the I/O processor and 61G8324
the SCSI cable.
3. Ensure that the SCSI cable between the interposer and the device is
seated correctly, and that there are no bent or damaged pins on the
SCSI cable.
4. Ensure that a terminating plug is attached to the device end of the SCSI
cable.
9201 Tape unit command timeout DHZDEV
FI00131
Before exchanging any parts, do the following: 05H3834
1. Ensure that the device is powered on. EXTSCSI
2. Ensure that an interposer is connected between the I/O processor and 61G8324
the SCSI cable.
3. Ensure that the SCSI cable between the interposer and the device is
seated correctly, and that there are no bent or damaged pins on the
SCSI cable.
4. Ensure that a terminating plug is attached to the device end of the SCSI
cable.

Reference codes 113

3570

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
9202 Tape unit failed after Licensed Internal Code was loaded DHZDEV
FI00131
Before exchanging any parts, do the following: 05H3834
1. Ensure that the device is powered on. EXTSCSI
2. Ensure that an interposer is connected between the I/O processor and 61G8324
the SCSI cable.
3. Ensure that the SCSI cable between the interposer and the device is
seated correctly, and that there are no bent or damaged pins on the
SCSI cable.
4. Ensure that a terminating plug is attached to the device end of the SCSI
cable.
9210 Illegal or unsupported tape unit response DHZDEV
FI00131
FI00130
9211 Gateway device detected a bus protocol error FCGATE
FCIOA
Use the gateway device service documentation to analyze the problem. DHZDEV
ANYFC
FCCABLE
EXTSCSI
61G8324
9300 Tape unit failure DHZDEV
9301 Tape device failure, redundancy lost DHZDEV

The tape unit detected a hardware failure that does not prevent the tape
unit from completing the current operation.

Refer to the 3570 Tape Unit service information to determine the failing
item.
9302 I/O processor Licensed Internal Code error FI00130

If the system is operational, perform a dump of the I/O processor data. For
more information, see Performing an IOP dump using hardware service
manager.
9303 Gateway device failure FCGATE

Use the gateway device service documenation to analyze the problem.

9310 Licensed Internal Code for the tape unit is not correct DHZDEV
FI00130
9320 Tape device Licensed Internal Code failure FI00130
DHZDEV
Perform the following:
1. Take a dump of the tape unit Licensed Internal Code (see the 3570 Tape
Unit service information).
2. Power off the tape unit. Then power on the tape unit to resume
operation.
3. Ask your next level of support for assistance.
9321 Gateway device Licensed Internal Code error FCCODE

Use the gateway device service documenation to analyze the problem.

9350 Tape unit detected a read or write error on tape medium MHZTMED
UHZCLN
A permanent read or write error occurred, and the tape unit determined DHZDEV
that the tape cartridge is defective. Exchange the tape cartridge.

114 System i® and System p®: Reference codes

3570

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
9351 Tape with excessive error rate was mounted in tape device. MHZTMED
UHZCLN
The tape unit detected that the mounted tape cartridge has a history of DHZDEV
excessive read and write errors. It is recommended that you exchange the
tape cartridge.
9355 The data format is incorrect; the tape cannot be read UHZUSER
MHZTMED
The tape unit does not give support to the data format on the tape UHZCLN
cartridge. Use a different tape cartridge. DHZDEV
9500 I/O processor Licensed Internal Code error FI00130

If the system is operational, perform a dump of the I/O processor data. For
more information, see Performing an IOP dump using hardware service
manager.
9800 to 9803 I/O processor successfully recovered from temporary error

No action required. This reference code is logged for information only.

9810 Problem analysis has determined a part should be replaced.

This reference code is used for ending Online Problem Analysis with a list
of failing items. (Information Only)
9899 Problem analysis completed, the problem has been corrected. UHZFIXD

This reference code is used for ending Online Problem Analysis when no
problem was found or the problem was corrected.
9900 Licensed Internal Code for tape unit was not upgraded UHZUSER

The I/O processor loading of Licensed Internal Code (LIC) to the

programmable tape unit was not completed.

The tape unit will continue to operate with the previous LIC. You may do
either of the following:
v Wait for next IPL when the system will attempt to load the LIC for the
tape drive again.
v Perform TU-PIP4 to reset the IOP and the tape unit. When the IOP is
reset, if the device has the wrong level of LIC, the IOP will attempt to
load the new LIC.
FFF6 Tape volume statistics logged (no action required)

Table 2. Tape unit failing items details

Failing Item Description Document Description

05H3834 Interposer IBM 3570 Tape Drive Service Guide
61G8324 Terminating plug IBM 3570 Tape Drive Service Guide
ANYFC Any device on Fibre Channel interface Problem Analysis; Symbolic FRU Isolation
DHZDEV Tape unit failure IBM 3570 Tape Drive Service Guide
EXTSCSI External signal cable Problem Analysis; Symbolic FRU Isolation
FCCABLE Fibre Channel cable Problem Analysis; Symbolic FRU Isolation
FCCODE Gateway device Licensed Internal Code Problem Analysis; Symbolic FRU Isolation
FCDEV Fibre Channel device Problem Analysis; Symbolic FRU Isolation
FCGATE Gateway device IBM SAN Data Gateway Service Guide

Reference codes 115

3570

Failing Item Description Document Description

FCIOA Fibre Channel IOA Problem Analysis; Symbolic FRU Isolation
MHZTMED Defective tape Magnetic tape subsystem service information
UHZCLN Tape unit needs cleaning Magnetic tape subsystem operator’s information
UHZCNFG Tape configuration detected by I/O processor; Installation
not valid
UHZUSER Operator action required System operation information

(358x, 3592, 4685, 5755, 6279, 6381, 6382, 6383, 6384, 6386, 6387, 63A0,
7207) Tape unit reference codes
A tape or tape library device failure occurred.

Note: Use this table to handle reference codes that might be displayed during a type D IPL to install the
operating system. If you are not performing a type D IPL of the operating system, consult any
error logs found in the Serviceable Event View. If you cannot locate an error log in the Serviceable
Event View that corresponds with the failure, run a verification test for the tape unit.
1. Verify that the device has power.
2. Check the device for any error indications. Refer to the device service information to resolve any error
indications.
3. Clean the recording head in the tape device.
4. Attempt the failing operation again. Does the operation complete successfully?
v Yes: You have corrected the problem. This ends the procedure.
v No: Look at the 4 rightmost characters of the Data display for Function 11, which represent the unit
reference code. Find the unit reference code in the following table.

For more on the Failing Item column entries, see Table 2. Tape unit failing items details, which follows
the reference code table below.

Table 1. (358x, 3592, 4685, 5755, 6279, 6381, 6382, 6383, 6384, 6386, 6387, 63A0, 7207) Tape unit reference
codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
3202 Tape unit configuration error UH7CNFG
FI00871
Before exchanging any parts, verify that the following condition is not
present:
v The attached device type or model is only supported on an I/O adapter
that is attached to an I/O processor.
9020 Tape unit configuration error UH7CNFG
FI00871
Before exchanging any parts, verify that the following conditions are not PTFSRCH
present:
v Tape and DASD devices attached to an I/O Processor that does not
support Tape and Dasd devices at the same time.
v An unsupported device type or model is attached.

116 System i® and System p®: Reference codes

358x, 3592, 4685, 5755, 6279,6381, 6382, 6383, 6384, 6386, 6387, 63A0, 7207

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
9100 Interface error detected by system or by tape unit FI00871
FI01112
If the attached device is an external device, do the following before FI00872
exchanging any parts: DEVTERM
1. If an interposer is required, make sure that it is connected between the
I/O processor and the SCSI cable.
2. Ensure that the SCSI cable is seated correctly, and that there are no bent
or damaged pins on the SCSI cable.
3. Ensure that a terminating plug is attached to the device end of the SCSI
cable.
9101 Fibre Channel interface error detected FCIOA
FCDEV
If the attached device is an external device, do the following before FCCABLE
exchanging any parts:
1. Ensure that the Fibre Channel cable is correctly connected to the ports.
2. Clean the Fibre Channel connectors.
3. If there is a hub attached, verify that the hub is operational.
4. If there is a gateway device attached, refer to the gateway device
service documentation for additional problem analysis procedures.
5. refer to the tape device service documentation for additonal problem
analysis procedures.
9102 Gateway device detected a SCSI interface error FI00871
FCGATE
Use the gateway device service documentation to analyze the problem. FI00872
DEVTERM
9200 Tape unit is not responding FI00871
FI01112
If the attached device is an external device, do the following before FI00872
exchanging any parts: DEVTERM
1. Ensure that the device is powered on.
2. If an interposer is required, make sure that it is connected between the
I/O processor and the SCSI cable.
3. Ensure that the SCSI cable is seated correctly, and that there are no bent
or damaged pins on the SCSI cable.
4. Ensure that a terminating plug is attached to the device end of the SCSI
cable.
9201 Tape unit command timeout FI00871
FI01112
If the attached device is an external device, do the following before FI00872
exchanging any parts: DEVTERM
1. Ensure that the device is powered on. MH7TMED
2. If an interposer is required, make sure that it is connected between the
I/O processor and the SCSI cable.
3. Ensure that the signal cable is seated correctly, and that there are no
bent or damaged pins on the SCSI cable.
4. Ensure that a terminating plug is attached to the device end of the SCSI
cable.

Reference codes 117

358x, 3592, 4685, 5755, 6279,6381, 6382, 6383, 6384, 6386, 6387, 63A0, 7207

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
9202 Tape unit failed after Licensed Internal Code was loaded FI00871
FI01112
If the attached device is an external device, do the following before FI00872
exchanging any parts: DEVTERM
1. Ensure that the device is powered on.
2. If an interposer is required, make sure that it is connected between the
I/O processor and the SCSI cable.
3. Ensure that the SCSI cable is seated correctly, and that there are no bent
or damaged pins on the SCSI cable.
4. Ensure that a terminating plug is attached to the device end of the SCSI
cable.
9210 Illegal or unsupported tape unit response FI00871
FI01112
PTFSRCH
9211 Gateway device detected a bus protocol error FCGATE
FCIOA
Use the gateway device service documentation to analyze the problem. FI00871
ANYFC
FCCABLE
FI00872
DEVTERM
9300 Tape unit failure FI00871
9301 Tape device failure, redundancy lost FI00871

The tape unit detected a hardware failure that does not prevent the tape
unit from completing the current operation.
9302 Tape device failure or media error MH7TMED
FI00871
The tape unit detected a failure that may be caused by a hardware failure
or a media error.

Refer to the tape unit service information for possible information on

diagnositic tests that can be run to isolate between hardware and media
failures.
9303 Gateway device failure FCGATE

Use the gateway device service documenation to analyze the problem.

9310 Licensed Internal Code for the tape unit is not correct PTFSRCH
FI00871
9320 Tape device Licensed Internal Code failure FI00130
FI00871
9321 Gateway device Licensed Internal Code error FCCODE

Use the gateway device service documenation to analyze the problem.

9350 Tape unit detected a read or write error on tape medium MH7TMED
UH7CLN
A permanent read or write error occurred. Clean the tape unit and retry FI00871
the operation.

If cleaning the tape unit does not correct the problem, exchange the tape
media.

118 System i® and System p®: Reference codes

358x, 3592, 4685, 5755, 6279,6381, 6382, 6383, 6384, 6386, 6387, 63A0, 7207

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
9351 Tape with excessive error rate was mounted in tape device. MH7TMED
UH7CLN
The tape unit detected that the mounted tape cartridge has a history of FI00871
excessive read and write errors. It is recommended that you exchange the
tape cartridge.
9355 The data format is incorrect; the tape cannot be read UH7USER
MH7TMED
The tape unit has detected that the data format on the tape media is not UH7CLN
supported. FI00871
Clean the tape unit and retry the operation.

If the operation continues to fail, use a different tape cartridge.

9500 Licensed Internal Code error PTFSRCH

If the system is operational, perform a dump of the I/O processor data. For
more information, see Performing an IOP dump using hardware service
manager.
9800 to 9804 System successfully recovered from temporary I/O error

No action required. This reference code is logged for information only.

9810 Problem analysis has determined a part should be replaced.

This reference code is used for ending Online Problem Analysis with a list
of failing items. (Information Only)
9899 Problem analysis completed, the problem has been corrected. UH7FIXD

This reference code is used for ending Online Problem Analysis when no
problem was found or the problem was corrected.
9900 Licensed Internal Code for tape unit was not upgraded UH7USER

The I/O processor loading of Licensed Internal Code (LIC) to the

programmable tape unit was not completed.

No action required. This reference code is logged for information only.

9902 An IOP dump was initiated

No action required.
FFF6 Tape volume statistics logged (no action required)

Table 2. Tape unit failing items details

Failing Item Description Document Description

ANYFC Any device on Fibre Channel interface Problem Analysis; Symbolic FRU Isolation
DEVTERM Terminating plug Problem Analysis; Symbolic FRU Isolation

Reference codes 119

358x, 3592, 4685, 5755, 6279,6381, 6382, 6383, 6384, 6386, 6387, 63A0, 7207

Failing Item Description Document Description

FCCABLE Fibre Channel cable Problem Analysis; Symbolic FRU Isolation
FCCODE Gateway device Licensed Internal Code Problem Analysis; Symbolic FRU Isolation
FCDEV Fibre Channel device Problem Analysis; Symbolic FRU Isolation
FCGATE Gateway device IBM SAN Data Gateway Service Guide
FCIOA Fibre Channel IOA Problem Analysis; Symbolic FRU Isolation
MH7TMED Defective tape Magnetic tape subsystem service information
PTFSRCH Licensed Internal Code Service Functions; APAR or LICTR
UH7CLN Tape unit needs cleaning Magnetic tape subsystem operator’s information
UH7CNFG Tape configuration detected by system is not Installation
valid
UH7FIXD Problem no longer exists System operation information
UH7USER Operator action required System operation information

(3590) Tape unit reference codes

A tape or tape library device failure occurred.

For more on the Failing Item column entries, see Table 2. Tape unit failing items details, which follows
the reference code table below.

Table 1. (3590) Tape unit reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
9020 I/O processor detected a SCSI bus configuration error UHQCNFG
FI00851
Before exchanging any parts, verify that the following conditions are not FI00130
present:
v Tape and DASD devices attached to an I/O processor that does not
support tape and DASD devices at the same time.
v A device type or model that is not given support

120 System i® and System p®: Reference codes

3590

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
9100 Interface error detected by I/O processor or by tape unit FI00851
FI00131
Before exchanging any parts, do the following: 05H3834
1. Ensure that an interposer is connected between the I/O processor and EXTSCSI
the SCSI cable. 61G8324
2. Ensure that the SCSI cable between the interposer and the device is
seated correctly, and that there are no bent or damaged pins on the
SCSI cable.
3. Ensure that a terminating plug is attached to the device end of the SCSI
cable.
9101 Fibre Channel interface error detected FCIOA
FCDEV
If the attached device is an external device, do the following before FCCABLE
exchanging any parts:
1. Ensure that the Fibre Channel cable is correctly connected to the ports.
2. Clean the Fibre Channel connectors.
3. If there is a hub attached, verify that the hub is operational.
4. If there is a gateway device attached, refer to the gateway device
service documentation for additional problem analysis procedures.
5. refer to the tape device service documentation for additonal problem
analysis procedures.
9102 Gateway device detected a SCSI interface error FI00851
FCGATE
Use the gateway device service documentation to analyze the problem. EXTSCSI
61G8324
9200 I/O processor addressed the tape unit; no response FI00851
FI00131
Before exchanging any parts, do the following: 05H3834
1. Ensure that the device is powered on. EXTSCSI
2. Ensure that an interposer is connected between the I/O processor and 61G8324
the SCSI cable.
3. Ensure that the SCSI cable between the interposer and the device is
seated correctly, and that there are no bent or damaged pins on the
SCSI cable.
4. Ensure that a terminating plug is attached to the device end of the SCSI
cable.
9201 Tape unit command timeout FI00851
FI00131
Before exchanging any parts, do the following: 05H3834
1. Ensure that the device is powered on. EXTSCSI
2. Ensure that an interposer is connected between the I/O processor and 61G8324
the SCSI cable.
3. Ensure that the SCSI cable between the interposer and the device is
seated correctly, and that there are no bent or damaged pins on the
SCSI cable.
4. Ensure that a terminating plug is attached to the device end of the SCSI
cable.

Reference codes 121

3590

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
9202 Tape unit failed after Licensed Internal Code was loaded FI00851
FI00131
Before exchanging any parts, do the following: 05H3834
1. Ensure that the device is powered on. EXTSCSI
2. Ensure that an interposer is connected between the I/O processor and 61G8324
the SCSI cable.
3. Ensure that the SCSI cable between the interposer and the device is
seated correctly, and that there are no bent or damaged pins on the
SCSI cable.
4. Ensure that a terminating plug is attached to the device end of the SCSI
cable.
9210 Illegal or unsupported tape unit response FI00851
FI00131
FI00130
9211 Gateway device detected a bus protocol error FCGATE
FCIOA
Use the gateway device service documentation to analyze the problem. FI00851
ANYFC
FCCABLE
EXTSCSI
61G8324
9300 Tape unit failure FI00851
9301 Tape device failure, redundancy lost FI00851

The tape unit detected a hardware failure that does not prevent the tape
unit from completing the present operation.

See the 3590 Tape Unit service information to determine the failing item.
9302 I/O processor Licensed Internal Code error FI00130

If the system is operational, perform a dump of the I/O processor data. For
more information, see Performing an IOP dump using hardware service
manager.
9303 Gateway device failure FCGATE

Use the gateway device service documenation to analyze the problem.

9310 Licensed Internal Code for the tape unit is not correct FI00851
FI00130
9320 Tape device Licensed Internal Code failure FI00130
FI00851
Do the following:
1. Take a dump of the tape device Licensed Internal Code (see the 3590
Tape Unit service information).
2. Power off the tape unit. Then power on the tape unit to resume
operation.
9321 Gateway device Licensed Internal Code error FCCODE

Use the gateway device service documenation to analyze the problem.

9350 Tape unit detected a read or write error on tape medium MHQTMED
UHQCLN
A permanent read or write error occurred, and the tape unit determined FI00851
that the tape cartridge is defective. Exchange the tape cartridge.

122 System i® and System p®: Reference codes

3590

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
9351 Tape with excessive error rate was mounted in tape device. MHQTMED
UHQCLN
The tape unit detected that the installed tape cartridge has a history of FI00851
excessive read and write errors. It is recommended that you exchange the
tape cartridge.
9355 The data format is incorrect; the tape cannot be read MHQTMED
UHQCLN
The tape device does not give support to the data format on the tape FI00851
cartridge. Format the tape cartridge again or use a different tape cartridge.

See the 3590 Tape Drive Operator’s Guide for instructions on formatting a
tape cartridge.
9500 I/O processor Licensed Internal Code error FI00130

No action required. This reference code is logged for information only.

9810 Problem analysis has determined a part should be replaced.

This reference code is used for ending Online Problem Analysis with a list
of failing items. (Information Only)
9899 Problem analysis completed, the problem has been corrected. UHQFIXD

This reference code is used for ending Online Problem Analysis when no
problem was found or the problem was corrected.
9900 Licensed Internal Code for tape unit was not upgraded

The I/O processor loading of Licensed Internal Code (LIC) to the

programmable tape unit was not completed.

Table 2. Tape unit failing items details

Failing Item Description Document Description

05H3834 Interposer IBM 3590 Tape Drive Service Guide
61G8324 Terminating plug IBM 3590 Tape Drive Service Guide
ANYFC Any device on Fibre Channel interface Problem Analysis; Symbolic FRU Isolation
EXTSCSI External signal cable Problem Analysis; Symbolic FRU Isolation
FCCABLE Fibre Channel cable Problem Analysis; Symbolic FRU Isolation
FCCODE Gateway device Licensed Internal Code Problem Analysis; Symbolic FRU Isolation
FCDEV Fibre Channel device Problem Analysis; Symbolic FRU Isolation

Reference codes 123

3590

Failing Item Description Document Description

FCGATE Gateway device IBM SAN Data Gateway Service Guide
FCIOA Fibre Channel IOA Problem Analysis; Symbolic FRU Isolation
MHQTMED Defective tape Magnetic tape subsystem service information
UHQCLN Tape unit needs cleaning Magnetic tape subsystem operator’s information
UHQCNFG Tape configuration detected by I/O processor; Installation
not valid

(40xx) Model 185 and A50 reference (error) codes

The system detected a power, voltage, or thermal problem.

Table 1. (40xx) Model 185 and A50 reference (error) codes

Reference Code Description/Action Perform all actions before Failing Item

exchanging Failing Items
40100100 Power supply failure

Replace the power supply. (For more

information, see Removing and replacing parts
in the model 185 and A50.)
40100111 VRM 1 failure VRMOD
SYSBKP2
40100122 VRM 2 failure VRMOD
SYSBKP2
40100133 VRM ECID setting VRMOD
SYSBKP2
40100134 The system detected a voltage problem VRMOD
SYSBKP2
40100144 Unfused board (ECID) SYSBKP2
40110111 The system detected a battery failure

Replace the battery. (For more information, see

Removing and replacing parts in the model 185
and A50.)
40200111 Warning temperature reached

Do the following:
1. Check the airflow to the fans, and correct
any problems that you find.
2. Look in the operating system error log for
error codes that indicate a problem with a
fan. Take the appropriate action for the error
codes that you find.

124 System i® and System p®: Reference codes

40xx

Reference Code Description/Action Perform all actions before Failing Item

exchanging Failing Items
40200222 Critical temperature reached

The system will power itself down to standby

when a critical temperature is reached. If this
occurs, do the following:
1. Check the connections on the fan, and
correct any problems that you find.
2. Verify that the airflow to the fan is not
blocked, and correct any problems that you
find.
40210100 A fan was failing but recovered

Informational message. A replacement fan was

hot-plugged in place of a failing fan. The
system will clear the rollup card LED.
40210111 A fan failed

Look at the rollup LED card to identify the fan

that failed, then do the following:
1. Check the connections on the fan, and
correct any problems that you find.
2. Verify that the airflow to the fan is not
blocked, and correct any problems that you
find.
3. If you find no obvious problems, replace the
fan. (For more information, see Removing
and replacing parts in the model 185 and
A50.)
40500111 Loss of rollup LED card

Reseat the rollup LED card. You can reseat the

rollup LED card while the system is powered
on, but the system might reset and reboot.

(432x, 660x, 671x, 673x) Disk unit reference codes

Find the unit reference code in the following table. If the failing item is a disk unit, go to Start Disk
Service.

Attention: The 673x is a read cache. Perform all actions required for 673x as a disk drive and logic card
except where separate 673x cache instructions are provided.

For more on the Failing Item column entries, see Table 2. Disk unit failing items details, which follows
the reference code table below.

Table 1. (432x, 660x, 671x, 673x) Disk unit reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
102E Out of alternate sectors for disk storage DISKDRV

Reference codes 125

432x, 660x, 671x, 673x

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
3002 Addressed device failed to respond to selection DISKDRV
STORIOA
BACKPLN
FI01106
FI01140
3010 Disk device returned wrong response to IOA DISKDRV
STORIOA
FI01140
FI01141
3020 Storage subsystem configuration error DISKDRV
FI01106
If an MES is being installed, verify the configuration. STORIOA
FI01140
3029 A device replacement has occurred

No action required. This reference code is logged for information only.

3100 Tape/optical or disk bus interface error occurred DISKDRV
STORIOA
Perform DSKIP03. FI01106
FI01140
3109 IOA timed out a disk command DISKDRV
STORIOA
FI01106
FI01140
3110 Disk bus interface error occurred STORIOA
DISKDRV
Perform DSKIP03. FI01106
FI01140
3130 Device Licensed Internal Code SVCDOCS

The device is not supported with the level of code currently on the system.
Contact your next level of support.
3131 Device or IOA Licensed Internal Code SVCDOCS

The device does not support a needed attribute and is running with
degraded performance. Contact your next level of support.
7000 Disk sector read error DISKDRV

No action required. This reference code is logged for information only.

7001 Temporary disk data error DISKDRV

A disk unit service action is recommended only if the Service Action Log
contains an entry for this reference code. For more information, see Using
the Service Action Log.
7003 Device format error

If the disk has not been formatted by the system, initialize and format the
disk. See Work with disk unit recovery.
7004 System log entry only. No service action required.
7050 Data compression failure SVCDOCS

Contact your next level of support.

126 System i® and System p®: Reference codes

432x, 660x, 671x, 673x

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
7051 Compressed device and compression IOA are not compatible CMPRES1

The customer should perform the procedure specified in “Recovering From

6xxx7051 SRC” in the Backup and Recovery Guide .

7052 Data compression warning SVCDOCS

The customer should perform the procedure specified in “Recovering From

6xxx7052 SRC” in the Backup and Recovery Guide .

70DD System log entry only, no service action required
FFF2 Disk motor problem DISKDRV
FFF3 Disk media format not valid DISKDRV
FFF4 Disk device problem DISKDRV
STORIOA
FFF5 Disk sector read error DISKDRV

A disk unit service action is recommended only if the Service Action Log
contains an entry for this reference code. For more information, see Using
the Service Action Log.
FFF6 Disk device detected recoverable error DISKDRV

A disk unit service action is recommended only if the Service Action Log
contains an entry for this reference code. For more information, see Using
the Service Action Log.
FFF7 Temporary disk data error DISKDRV

No action required. This reference code is logged for information only.

FFF8 to FFF9 Temporary disk data error DISKDRV

A disk unit service action is recommended only if the Service Action Log
contains an entry for this reference code. For more information, see Using
the Service Action Log.
FFFA Temporary disk bus error DISKDRV
STORIOA
A disk unit service action is recommended only if the Service Action Log FI01140
contains an entry for this reference code. For more information, see Using FI01141
the Service Action Log. BACKPLN
FFFB SCSI bus reset occurred

No action required. This reference code is logged for information only.

FFFE Temporary disk bus error DISKDRV
STORIOA
A disk unit service action is recommended only if the Service Action Log FI01106
contains an entry for this reference code. For more information, see Using FI01140
the Service Action Log.

Failing Item Description Document Description

CARDTMP Operating voltage or temperature range limit See the service documentation for instructions.
exceeded
IOA I/O adapter card See the service documentation for instructions.
IOP I/O processor card See the service documentation for instructions.
MA_BRDG Multi-adapter bridge See the service documentation for instructions.

(4764) Reference codes

Find the unit reference code in the following table. For more on the Failing Item column entries, see Table
2. Failing items details, which follows the reference code table below.

Table 1. (4764) Reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
B990 I/O adapter hardware error detected IOA
AJDG301
B991 Tampering of cryptographic card suspected. IOA
AJDG301
B992 Operating voltage and/or temperature range limits exceeded. CARDTMP

Correct any conditions in the physical environment which may have

caused the voltage and/or temperature out-of-range error on the 4764
adapter card. After the conditions have been corrected, vary off and then
vary back on the 4764 device description associated with the 4764 adapter
card.

Table 2. Failing items details

134 System i® and System p®: Reference codes

4764

Failing Item Description Document Description

AJDG301 Licensed Internal Code See the service documentation for instructions.
CARDTMP Operating voltage or temperature range limit See the service documentation for instructions.
exceeded
IOA I/O adapter card See the service documentation for instructions.

(4812) Reference codes

Find the unit reference code in the following table. For more on the Failing Item column entries, see Table
2. Failing items details, which follows the reference code table below.

Table 1. (4812) Reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
6201 A permanent I/O processor failure occurred IOA
FI00730
6202 I/O processor Licensed Internal Code error FI00730
IOA
6204 I/O adapter failure due to a thermal condition IOA
6210 I/O processor Licensed Internal Code error FI00730
6221 I/O processor resource not available LICCODE
DISKIMG
6222 A permanent I/O processor failure occurred FI00730
IOA
6223 A permanent I/O processor failure occurred IOA
FI00730
6225 A permanent I/O processor failure occurred FI00730
LICCODE
IOA
6226 A Virtual SCSI error was detected LICCODE
AS4NTDD
FI00730
6227 Windows initiated a warm boot NTUSER
FI00730
IOA
6228 Windows initiated a warm boot FI00730
IOA
6501 A Windows fatal error occurred IOA
FI00730
6502 A Windows fatal error occurred FI00730
IOA
6530 A Virtual SCSI error was detected NTVSCSI
NTOPSYS
6531 A Virtual SCSI error was detected NTVSCSI
AS4NTDD
NTOPSYS
FI00730
6532 A Virtual SCSI error was detected NTOPSYS
FI00730
AS4NTDD

Reference codes 135

4812

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
6533 A Virtual SCSI error was detected NTUSER
NTOPSYS
AS4NTDD
6534 A Virtual SCSI error was detected AS4NTDD
FI00730
NTOPSYS
6535 A Virtual SCSI error was detected NTUSER
NTDEVDR
FI00730
6538 A Virtual SCSI error was detected NTVSCSI
NTOPSYS
6539 A Virtual SCSI error was detected NTVSCSI
AS4NTDD
NTOPSYS
FI00730
653A A Virtual SCSI error was detected NTOPSYS
FI00730
AS4NTDD
653B A Virtual SCSI error was detected NTUSER
NTOPSYS
AS4NTDD
653C A Virtual SCSI error was detected AS4NTDD
FI00730
NTOPSYS
653D A Virtual SCSI error was detected NTUSER
NTDEVDR
FI00730
653F A Virtual SCSI error was detected NTDEVDR
NTOPSYS
LICCODE
6540 A Virtual SCSI error was detected NTVSCSI
FI00730
LICCODE
6541 A permanent I/O processor failure occurred IOA
FI00730
6542 Licensed Internal Code error detected. LICCODE
FI00730
6543 A Windows fatal error occurred NTOPSYS
NTVSCSI
6580 A Windows fatal error occurred NTOPSYS
NTVSCSI
DISKIMG
IOA
FI00730
B4B0 I/O adapter hardware error detected IOA
B4B1, B4B4 I/O adapter hardware error detected IOA
MEMORY
B4B5 An I/O adapter failure occurred. FI00730
IOA
B4B8 Adapter card storage error MEMORY
IOA

136 System i® and System p®: Reference codes

4812

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
B4B9 An I/O adapter failure occurred. IOA
B4BC I/O adapter error; logged only. IOA
B4BE Adapter card storage error MEMORY
IOA
B904 A permanent I/O processor failure occurred FI00730
IOA
B960 I/O processor Licensed Internal Code error FI00730
IOP

Table 2. Failing items details

Failing Item Description Document Description

AS4NTDD Device Driver See the service documentation for instructions.
DISKIMG Server Storage Space Object See the service documentation for instructions.
IOA I/O adapter card Repair and Parts; removal and installation
procedures
IOP I/O adapter card Repair and Parts; removal and installation
procedures
LICCODE SLIC Licensed Internal Code Service Functions; APAR or LICTR
MA_BRDG Multi-adapter bridge See the service documentation for instructions.
MEMORY Storage card See the service documentation for instructions.
MEMORY DIMM in first populated DIMM position - See the service documentation for instructions.
DIMM 0 or DIMM 1
NTDEVDR Device Driver See the service documentation for instructions.
NTLANDD Device Driver See the service documentation for instructions.
NTOPSYS Windows Operating System See the service documentation for instructions.
NTUSER User-initiated action See the service documentation for instructions.
NTVSCSI Device Driver See the service documentation for instructions.

(4B20) Model 185 and A50 reference (error) codes

The system detected a problem with a processor.

Table 1. (4B20) Model 185 and A50 reference (error) codes

Reference Code Description/Action Perform all actions before Failing Item

exchanging Failing Items
4B200111 A checkstop occurred SYSBKP2

If this error code only occurs once, it is not a

problem. If this error code persists, replace the
system backplane.
4B200120 Processor 0 failed to initialize SYSBKP2

On a two-way system, this error implies that

one processor is still functioning, and the
system will continue to operate in a degraded
mode. At some point, you should replace the
system backplane.

Reference codes 137

4B20

Reference Code Description/Action Perform all actions before Failing Item

exchanging Failing Items
4B200121 Processor 1 failed to initialize SYSBKP2

On a two-way system, this error implies that

one processor is still functioning, and the
system will continue to operate in a degraded
mode. At some point, you should replace the
system backplane.
4B200122 No processors were detected SYSBKP2

(5700, 5701) Reference codes

1. Look at characters 5 through 8 of the top 16 character line of function 11 (4 rightmost characters of
word 1). These 4 characters are the unit reference code.
2. Look at the last 8 characters of the top 16 character line of function 12 (word 3). These 8 characters are
the direct select address of the card (BBBBCcbb). The unit address portion of the card address is
characters 1 through 8 of the bottom 16 character line of function 11 (Word 4). Card locations can be
found using the 16 character address. See SRC Address Formats.
3. Find the unit reference code in the following table.

For more on the Failing Item column entries, see Table 2. Failing items details, which follows the
reference code table below.

Table 1. (5700, 5701) Reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
A001 I/O adapter Licensed Internal Code error detected AJDGP01
B9A0 I/O adapter hardware error detected FI00719
FI00718
AJDGP01
MA_BRDG
B9B0 I/O adapter hardware error detected FI00719
LICCODE
MA_BRDG

Table 2. Failing items details

Failing Item Description Document Description

AJDGP01 LIC - Input/Output Processor Licensed Internal Service Functions; APAR or LICTR
Code
LICCODE Licensed Internal Code See the service documentation for instructions.
MA_BRDG Multi-adapter bridge See the service documentation for instructions.

(5706, 5707) Reference codes

Find the unit reference code in the following table. For more on the Failing Item column entries, see Table
2. Failing items details, which follows the reference code table below.

Table 1. (5706, 5707) Reference codes

138 System i® and System p®: Reference codes

5706, 5707

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
A001 I/O adapter Licensed Internal Code error detected AJDGP01
B9B0 I/O adapter hardware error detected IOA
AJDGP01

Table 2. Failing items details

Failing Item Description Document Description

AJDGP01 I/O card Licensed Internal Code See the service documentation for instructions.
IOA Communications adapter card See the service documentation for instructions.

(5708, 574F, 575B) Reference codes

Find the unit reference code in the following table. For more on the Failing Item column entries, see Table
2. Failing items details, which follows the reference code table below.

Table 1. (5708, 574F, 575B) Reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
1310 I/O adapter resource not available

The I/O adapter error log is being filled faster than the errors are being
reported to the system. Check other errors reported to the system and
correct them.
3006 System bus error AUXIOA
ANYBRDG
IOP
3100 Interface error AUXCBL
AUXIOA
Error occurred on SCSI bus 0. PRIMIOA
3101 Interface error AUXCBL
AUXIOA
Error occurred on SCSI bus 1. PRIMIOA
3400 SCSI resource error AUXCBL
PRIMIOA
6075 I/O processor resource not available PTFSRCH
8008 A permanent cache battery pack failure occurred CACHBAT
AUXIOA
NOTE: Under a certain configuration, this SRC may not represent an error
that requires a service action. Depending on the configuration of the
system, the Storage IOA may have been altered and/or the Storage IOA
Cache may have been disabled to allow attachment of OEM Storage that
emulates a Load Source drive. If this is the case, this error will be posted
each time the IOA is IPLed and it can be ignored.
8009 Impending cache battery pack failure CACHBAT

Reference codes 139

5708, 574F, 575B

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
8130 IOA detected recoverable SCSI bus error

An error occurred on SCSI bus 0. No action is required. This reference code

is logged for information only.
8131 IOA detected recoverable SCSI bus error

An error occurred on SCSI bus 1. No action is required. This reference code

is logged for information only.
8140 IOA detected recoverable SCSI bus error

No action is required. This reference code is logged for information only.

8141 IOA detected recoverable SCSI resource error

No action is required. This reference code is logged for information only.

8145 A recoverable error occurred AUXIOA
8150 A permanent failure occurred AUXIOA
ANYBRDG
NOTE: Under a certain configuration, this SRC may not represent an error
that requires a service action. Depending on the configuration of the
system, the Storage IOA may have been altered and/or the Storage IOA
Cache may have been disabled to allow attachment of OEM Storage that
emulates a Load Source drive. If this is the case, this error will be posted
each time the IOA is IPLed and it can be ignored.
8151 Licensed Internal Code error PTFSRCH
AUXIOA
8155 to 8156 A permanent failure occurred PTFSRCH
AUXIOA
8157 I/O adapter card error SVCDOCS

1. If the I/O Processor is not operable and disk units are attached, use
Hardware Service Manager to re-IPL the IOP. Other resources attached to
the IOP may then need to be Varied On.

2. If disk units are not attached, perform the VRYCFG RESET(*YES)

command to reset the IOP and Vary On attached resources.
8300 IOA hardware or PCI bus error AUXIOA
ANYBRDG
PTFSRCH
8301 Not valid condition in Licensed Internal Code PTFSRCH
AUXIOA
8302 Missing Licensed Internal Code SVCDOCS
AUXIOA
Ensure that the code necessary to support this I/O adapter is loaded.
9055 Write cache data is available for attached storage IOA

No service action required.

9071 Link from IOA to auxiliary cache IOA went operational

No service action required.

140 System i® and System p®: Reference codes

5708, 574F, 575B

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
9072 Link from IOA to auxiliary cache IOA went non-operational

No service action required.

9073 Disconnected, incompatible, or non-operational storage IOA SVCDOCS

Perform IOPIP41.
FF3D I/O adapter detected a recoverable error AUXIOA
ANYBRDG

Table 2. Failing items details

Failing Item Description Document Description

AJDGP01 I/O processor Licensed Internal Code Service Functions; APAR or LICTR
ANYBRDG System I/O bus or any attached card See the service documentation for instructions.
ANYBUS IOP card bus error See the service documentation for instructions.
AUXCBL Cable assembly See the service documentation for instructions.
AUXIOA I/O adapter card See the service documentation for instructions.
BACKPLN Card Enclosure or Planar Board See the service documentation for instructions.
CACHBAT Cache battery pack See the service documentation for instructions.
DEVBPLN Device backplane See the service documentation for instructions.
DEVTERM Terminating plug See the service documentation for instructions.
IOP I/O processor card See the service documentation for instructions.
PCIBUS Any PCI card on the PCI bus See the service documentation for instructions.
PRIMIOA Storage I/O adapter See the service documentation for instructions.
PTFSRCH Licensed Internal Code See the service documentation for instructions.
STORIOA Storage I/O adapter See the service documentation for instructions.
SVCDOCS Customer engineer directed to system problem See the service documentation for instructions.
analysis
USER System Operator/User See the service documentation for instructions.

(571A, 571B, 571E, 571F, 573D, 573E, 57FF) Reference codes

Find the unit reference code in the following table. For more on the Failing Item column entries, see Table
2. Failing items details, which follows the reference code table below.

Table 1. (571A, 571B, 571E, 571F, 573D, 573E, 57FF) Reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
1310 I/O adapter resource not available

The I/O adapter error log is being filled faster than the errors are being
reported to the system. Check other errors reported to the system and
correct them.

Reference codes 141

571A, 571B, 571E, 571F, 573D, 573E, 57FF

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
3000 A permanent failure occurred FI01101
ANYBRDG
3006 System bus error FI01101
ANYBRDG
PTFSRCH
3020 SCSI bus configuration error USER
FI01107
Error occurred on SCSI bus 0. To correct or isolate a possible user error or STORIOA
configuration error, perform IOPIP17.
3021 SCSI bus configuration error USER
FI01107
Error occurred on SCSI bus 1. To correct or isolate a possible user error or STORIOA
configuration error, perform IOPIP17.
3022 SCSI bus configuration error USER
FI01107
Error occurred on SCSI bus 2. To correct or isolate a possible user error or STORIOA
configuration error, perform IOPIP17.
3023 SCSI bus configuration error USER
FI01107
Error occurred on SCSI bus 3. To correct or isolate a possible user error or STORIOA
configuration error, perform IOPIP17.
3100 Interface error FI01107
STORIOA
Error occurred on SCSI bus 0. FI01140
DEVBPLN
Perform IOPIP13.
3101 Interface error FI01107
STORIOA
Error occurred on SCSI bus 1. FI01140
DEVBPLN
Perform IOPIP13.
3102 Interface error FI01107
STORIOA
Error occurred on SCSI bus 2. FI01140
DEVBPLN
Perform IOPIP13.
3103 Interface error FI01107
STORIOA
Error occurred on SCSI bus 3. FI01140
DEVBPLN
Perform IOPIP13.
3120 Bus is not operational SVCDOCS

Adding a device to SCSI bus 0 of the I/O Adapter caused the bus to
become not operational. Remove the device.
3121 Bus is not operational SVCDOCS

Adding a device to SCSI bus 1 of the I/O Adapter caused the bus to
become not operational. Remove the device.
3122 Bus is not operational SVCDOCS

Adding a device to SCSI bus 2 of the I/O Adapter caused the bus to
become not operational. Remove the device.

142 System i® and System p®: Reference codes

571A, 571B, 571E, 571F, 573D, 573E, 57FF

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
3123 Bus is not operational SVCDOCS

Adding a device to SCSI bus 3 of the I/O Adapter caused the bus to
become not operational. Remove the device.
3140 Bus is operational

This reference code and the 3120 reference code that occurred before it
require no service action because SCSI bus 0 is now operational.
3141 Bus is operational

This reference code and the 3121 reference code that occurred before it
require no service action because SCSI bus 1 is now operational.
3142 Bus is operational

This reference code and the 3122 reference code that occurred before it
require no service action because SCSI bus 2 is now operational.
3143 Bus is operational

This reference code and the 3123 reference code that occurred before it
require no service action because SCSI bus 3 is now operational.
3150 SCSI bus configuration error SVCDOCS

Internal and external SCSI cables are connected to SCSI bus 0 at the same
time. Correct the SCSI bus 0 configuration.
3151 SCSI bus configuration error SVCDOCS

The device is not supported in the current configuration. An I/O processor

might be required.
3400 Device error FI02112
STORIOA
NOTE: If external devices are attached check EXTSCSI and DEVTERM first. FI01106
FI01140
3401 Device backplane problem DEVBPLN
3501 Licensed Internal Code error FI01105
PTFSRCH
The device type is either unsupported or the code has not been loaded to
support it.
3601 System log entry only, no service action required
8008 A permanent cache battery pack failure occurred CACHBAT
STORIOA
NOTE: Under a certain configuration, this SRC may not represent an error
that requires a service action. Depending on the configuration of the
system, the Storage IOA may have been altered and/or the Storage IOA
Cache may have been disabled to allow attachment of OEM Storage that
emulates a Load Source drive. If this is the case, this error will be posted
each time the IOA is IPLed and it can be ignored.
8009 Impending cache battery pack failure CACHBAT

Reference codes 143

571A, 571B, 571E, 571F, 573D, 573E, 57FF

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
8100 Licensed Internal Code error PTFSRCH
STORIOA
8130 IOA detected recoverable device bus error

An error occurred on SCSI bus 0. No action is required. This reference code

is logged for information only.
8131 IOA detected recoverable device bus error

An error occurred on SCSI bus 1. No action is required. This reference code

is logged for information only.
8132 IOA detected recoverable device bus error

An error occurred on SCSI bus 2. No action is required. This reference code

is logged for information only.
8133 IOA detected recoverable device bus error

An error occurred on SCSI bus 3. No action is required. This reference code

is logged for information only.
8140 IOA detected recoverable device bus error

No action is required. This reference code is logged for information only.

8141 IOA detected recoverable device error

No action is required. This reference code is logged for information only.

8145 A recoverable error occurred STORIOA
8146 Disk device detected recoverable error FI01105
8150 A permanent failure occurred STORIOA
ANYBRDG
NOTE: Under a certain configuration, this SRC may not represent an error
that requires a service action. Depending on the configuration of the
system, the Storage IOA may have been altered and/or the Storage IOA
Cache may have been disabled to allow attachment of OEM Storage that
emulates a Load Source drive. If this is the case, this error will be posted
each time the IOA is IPLed and it can be ignored.
8151 Licensed Internal Code error PTFSRCH
STORIOA
8155 to 8156 A permanent failure occurred PTFSRCH
STORIOA
8157 I/O adapter card error SVCDOCS

Display the Service Action Log entry for this SRC. If the Failing Item
indicates an I/O adapter, then replace the I/O adapter. If the Failing Item
indicates SVCDOCS, then do NOT replace the I/O adapter. This is a
recoverable error. Perform the following for the I/O processor that the I/O
adapter is attached to:
1. If the I/O processor is not operable and disk units are attached, use
Hardware Service Manager to re-IPL the IOP. Other resources attached
to the IOP may then need to be Varied On.
2. If disk units are not attached, perform the ″VRYCFG RESET(*YES)″
command to reset the IOP and Vary On attached resources.
8300 IOA hardware error or PCI bus error STORIOA
ANYBRDG
PTFSRCH

144 System i® and System p®: Reference codes

571A, 571B, 571E, 571F, 573D, 573E, 57FF

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
8301 Not valid condition in Licensed Internal Code PTFSRCH
STORIOA
8302 Missing Licensed Internal Code SVCDOCS
STORIOA
Ensure that the code necessary to support this I/O adapter is loaded.
8400 Licensed Internal Code error PTFSRCH
8404 System log entry only, no service action required
9000 Device error FI01105
STORIOA
9001 Device configuration error SVCDOCS

Perform IOPIP33.
9002 Device error FI01105
STORIOA
Perform IOPIP16. FI01140
BACKPLN
FI01106
9008 I/O card does not support functions expected by devices SVCDOCS

Perform IOPIP25.
9009 Call your next level of support for assistance SVCDOCS
9010 Cache data associated with attached devices cannot be found SVCDOCS

Perform IOPIP31.
9011 Cache data belongs to devices other than those attached SVCDOCS

Perform IOPIP32.
9020 to 9021 Array not functional due to present hardware configuration. SVCDOCS

Perform IOPIP20.
9022 to 9024 Array not functional due to present hardware configuration. SVCDOCS

Perform IOPIP22.
9025 Disk unit is not supported at its physical location. SVCDOCS

Perform IOPIP21.
9026 Array not functional due to present hardware configuration. SVCDOCS

Perform IOPIP22.
9027 Array not functional due to present hardware configuration. SVCDOCS

Perform IOPIP34.
9028 Incorrect hardware configuration change has been detected. SVCDOCS

Reduce the number of arrays on this I/O adapter. Either move all the
devices in an array to another I/O adapter that supports arrays, or stop an
array on this I/O adapter.
9029 Incorrect hardware configuration change has been detected. SVCDOCS

Contact your next level of support.

Reference codes 145

571A, 571B, 571E, 571F, 573D, 573E, 57FF

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
902F Array addendum Product Activity Log entry

Either a previous rebuild was interrupted and was automatically restarted,

Perform IOPIP21.
9040 Array protection temporarily suspended

No action required. Protection will be automatically restarted.

9041 Background array parity check detected and corrected errors PTFSRCH

Call your next level of support to report the problem.

9042 An array parity error has been detected and corrected NEXTLVL

Call your next level of support to report the problem.

9050 Required cache data cannot be located for a disk unit. SVCDOCS

Perform IOPIP30.
9051 Cache data exists for a missing or failed device SVCDOCS

If all configured units are missing, a 9054 reference code may appear in the
product activity log. If so, perform the action indicated for the 9054
reference code.

Otherwise, perform IOPIP27.

9052 Cache data exists for device that has been modified. SVCDOCS

Contact your next level of support.

9053 IOA resources not available due to previous problems SVCDOCS

Take action on other reference codes which have surfaced.

If you cannot get to SST or DST, and cannot perform a type A or B IPL,
perform a type D IPL from removable media. Look for Product Activity
Log entries for other reference codes and take action on them.
9054 IOA resources not available due to previous problems SVCDOCS

Power off the system and remove all new or replacement disk units. IPL
the system to DST. If you cannot perform a type A or B IPL, perform a
type D IPL from removable media.

Look for Product Activity Log entries for other reference codes and take
action on them.

146 System i® and System p®: Reference codes

571A, 571B, 571E, 571F, 573D, 573E, 57FF

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
9071 Link from IOA to auxiliary cache IOA went operational

No service action required.

9072 Link from IOA to auxiliary cache IOA went non-operational

No service action required.

9073 Incompatible or non-operational auxiliary cache IOA attached SVCDOCS

Perform IOPIP40.
9081 Device error FI01105
STORIOA
9082 Device error FI01105
STORIOA
Perform IOPIP16. FI01140
BACKPLN
FI01106
9090 Disk unit has been modified after the last known status. SVCDOCS

Re-IPL the system. If any reference codes are surfaced, go to List of system
reference codes and use the new reference code as the entry point to the
problem.

If you cannot resolve the problem, contact your next level of support.
9091 Incorrect hardware configuration change has been detected. SVCDOCS

Re-IPL the system. If any reference codes are surfaced, go to List of system
reference codes and use the new reference code as the entry point to the
problem.

If you cannot resolve the problem, contact your next level of support.
9092 Disk unit requires initialization before use. SVCDOCS

Perform IOPIP26.
9902 System log entry only, no service action required
C000 System log entry only, no service action required

No action is required. This reference code is logged for information only.

C402 Licensed Internal Code error PTFSRCH

Ask your next level of support for assistance.

FF3D I/O adapter detected a recoverable error STORIOA
ANYBRDG
FF6D Recoverable system bus error STORIOA
ANYBRDG
PTFSRCH

Table 2. Failing items details

Failing Item Description Document Description

Reference codes 147

571A, 571B, 571E, 571F, 573D, 573E, 57FF

Failing Item Description Document Description

Failing Item Description Document Description

AJDG301 Licensed Internal Code See the service documentation for instructions.
IOA Communications adapter card See the service documentation for instructions.

Reference codes 149

573C

Failing Item Description Document Description

UJE40 Network Termination, Network or Network Communications Configuration
devices

(6320, 6321, 632B, 632C, 6330, 6331, 6333, 6336, 6337) Optical storage
unit reference codes
An optical storage unit failure occurred.
Notes:
1. If the system is available, use online diagnostic tests when possible.
2. Use the Hardware Service Manager (HSM) verify function (via DST or SST) and verify that the unit is
operating correctly.
3. Search the problem log (WRKPRB) for a recent optical storage entry that may assist in analyzing the
problem. The WRKPRB entry will provide a unit reference code that can be found in the following
table.

Perform the following:

1. If the system is available, attempt the failing operation again with an optical media that is known to
be good.
Does the operation complete successfully?
v Yes: The original optical media may be defective, or the problem may be intermittent.
Attempt the failing operation again with the original optical media to verify.
This ends the procedure.
v No: Look at the 4 rightmost characters of the Data display for word 1. These 4 characters are the
unit reference code. Find the unit reference code in the following table.

For more on the Failing Item column entries, see Table 2. Optical storage unit failing items details, which
follows the reference code table below.

Table 1. (6320, 6321, 6330, 6331, 6333, 6336, 6337) Optical storage unit reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
C000 System log entry only, no service action required

No action is required. This reference code is logged for information only.

C002 SCSI selection or reselection timeout occurred FI00870
CNVTCRD
FI01106
STORIOA
MEDIA
FI01141
FI01140
C010 Undefined sense key returned by device FI00870
C020 Device internal configuration error FI00870
C100 SCSI bus command error occurred FI00870
CNVTCRD
FI01106
STORIOA
MEDIA
FI01141
FI01140

150 System i® and System p®: Reference codes

6320, 6321, 632B, 632C, 6330, 6331, 6333, 6336, 6337

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
C110 SCSI command timeout occurred FI00870
CNVTCRD
FI01106
STORIOA
MEDIA
FI01141
FI01140
C210 Unexpected device condition recovered

The device successfully recovered from a temporary error.

No action is required. This reference code is logged for information only.

C300 Media or device error occurred MEDIA
FI00870
Perform the following:
1. Clean the disk.
2. Attempt the failing operation again.
3. If this does not correct the problem, exchange the failing items.
C301 Media or device error occurred

Dust check encountered. The optical media or the optical lens of the drive
is dirty.

Clean the optical drive and the media contained in the drive.
C302 Media or device error occurred

The device encountered an ’out of spare sectors’ condition when writing to

the media. The media can no longer be written to but is still readable.

Clean the optical drive and the media contained in the drive.
C303 Media had an unknown format

No action required. This reference code is logged for information only.

C333 Incompatible media was detected MEDIA
FI00870
Perform the following:
1. Verify that the disk has a supported format.
2. If the format is supported, clean the disk and attempt the failing
operation again.
3. If the operation fails again and results in the same reference code, ask
your media source for a replacement disk.
C400 Interface error detected by device FI00870
CNVTCRD
FI01106
STORIOA
FI01140
FI01141
C402 Licensed Internal Code error FI00130

Ask your next level of support for assistance.

CFF2 Recovered from device not ready - Start Unit issued

The device successfully recovered from a temporary error.

No action is required. This reference code is logged for information only.

Reference codes 151

6320, 6321, 632B, 632C, 6330, 6331, 6333, 6336, 6337

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
CFF4 Internal device error occurred FI00870
MEDIA
CFF6 Device successfully recovered from a temporary error

No action is required. This reference code is logged for information only.

CFF7 Recovered device error

The device successfully recovered from a temporary error.

No action is required. This reference code is logged for information only.

CFFE Recovered SCSI bus error

The device successfully recovered from a temporary error.

No action is required. This reference code is logged for information only.

FF09 Licensed Internal Code for optical device was not upgraded

This reference code is logged for information only.

FF3D Recovered IOA error

The device successfully recovered from a temporary error.

No action is required. This reference code is logged for information only.

FF6D Recovered System bus error

The device successfully recovered from a temporary error.

No action is required. This reference code is logged for information only.

Table 2. (6320, 6321, 6330, 6331, 6333, 6336, 6337) Optical storage unit failing items details

Failing Item Description Document Description

46G3532 CD-ROM device with tray Repair and Parts; removal and installation
procedures
88G4918 CD-ROM device, Apex part Repair and Parts; removal and installation
procedures
CDTRAY Flex cable on tray assembly See the service documentation for instructions.
CNVTCRD Converter card See the service documentation for instructions.
DEVTERM Bus Terminator See the service documentation for instructions.
MEDIA Optical Media System operation information
STORIOA Storage I/O adapter See the service documentation for instructions.

Table 3. (632B) Optical storage unit reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
CFC1 Virtual media list access problem SVCDOCS

A virtual optical device cannot access the file containing the list of
volumes.

On this partition and the Network File System server, ensure the proper
file is specified and proper authority is granted.

152 System i® and System p®: Reference codes

6320, 6321, 632B, 632C, 6330, 6331, 6333, 6336, 6337

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
CFC2 Error reading virtual volume list SVCDOCS

A non-recoverable error was detected while reading the list of volumes.

Check for errors on the Network File System server and resolve them.
Then retry the operation. If the failure reoccurs, contact your hardware
service provider.
CFC3 Virtual media volume list is not valid SVCDOCS

The data in the list of volumes is not valid.

On the Network File System server, ensure that the proper file is specified,
that all files are entered correctly, that there are no blank lines, and that the
character set used is valid.
CFC4 Virtual optical volume access problem SVCDOCS

A virtual optical device cannot access the file containing the specified
optical volume.

On the Network File System server, ensure the proper file is specified in
the list of volumes, and that the proper authority is granted.
CFC5 Error reading virtual optical volume SVCDOCS

A non-recoverable error was detected while reading a virtual optical

volume.

Check for errors on the Network File System server and resolve them.
Then retry the operation. If the failure reoccurs, contact your hardware
service provider.
CFC6 Virtual optical volume is not valid SVCDOCS

The file specified does not contain data that can be processed as a virtual
optical volume.

On the Network File System server, ensure all the files specified in the list
of optical volumes are correct.
CFC7 Virtual optical device detected error SVCDOCS

A virtual optical device detected an error reported by the Network File

System server that cannot be recovered.

Check for errors on the Network File System server and resolve them.
Then retry the operation. If the failure reoccurs, contact your hardware
service provider.
CFC8 Virtual optical device error NEXTLVL

A virtual optical device encountered a non-recoverable error.

Contact your next level of support for assistance.

Table 4. (632B) Optical storage unit failing items details

Failing Item Description Document Description

NEXTLVL Call your next level of support for assistance Call your next level of support for assistance
SVCDOCS Customer engineer directed to system problem See the service documentation for instructions.
analysis

Reference codes 153

6320, 6321, 632B, 632C, 6330, 6331, 6333, 6336, 6337

Table 5. (632C) Optical storage unit reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
C000 System log entry only, no service action required

No action is required. This reference code is logged for information only.

C002 SCSI selection or reselection timeout occurred

Refer to the hosting partition for problem analysis.

C010 Undefined sense key returned by device

Refer to the hosting partition for problem analysis.

C020 Device internal configuration error

Refer to the hosting partition for problem analysis.

C100 SCSI bus command error occurred

Refer to the hosting partition for problem analysis.

C110 SCSI command timeout occurred

Refer to the hosting partition for problem analysis.

C210 Unexpected device condition recovered

The device successfully recovered from a temporary error.

No action is required. This reference code is logged for information only.

C300 to C302 Media or device error occurred

Refer to the hosting partition for problem analysis.

C303 Media had an unknown format

No action required. This reference code is logged for information only.

C333 Incompatible media was detected

Perform the following:

1. Verify that the disk has a format that is given support.
2. If the format is given support, clean the disk and attempt the failing
operation again.
3. If the operation fails again with the same reference code, ask your
media source for a replacement disk.
C400 Interface error detected by device

Refer to the hosting partition for problem analysis.

C402 Licensed Internal Code program error occurred PTFSRCH

Ask your next level of support for assistance.

CFF2 Recovered from device not ready - Start Unit issued

The device successfully recovered from a temporary error.

No action is required. This reference code is logged for information only.

CFF4 Internal device error occurred

Refer to the hosting partition for problem analysis.

154 System i® and System p®: Reference codes

6320, 6321, 632B, 632C, 6330, 6331, 6333, 6336, 6337

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
CFF6 The device successfully recovered from a temporary error

No action is required. This reference code is logged for information only.

CFF7 Recovered device error

The device successfully recovered from a temporary error.

No action is required. This reference code is logged for information only.

CFFE Recovered SCSI bus error

The device successfully recovered from a temporary error.

No action is required. This reference code is logged for information only.

FF3D Recovered IOA error

The device successfully recovered from a temporary error.

No action is required. This reference code is logged for information only.

FF6D Recovered System bus error

The device successfully recovered from a temporary error.

No action is required. This reference code is logged for information only.

Table 6. (632C) Optical storage unit failing items details

Failing Item Description Document Description

46G3532 CD-ROM device with tray Repair and Parts; removal and installation
procedures
88G4918 CD-ROM device, Apex part Repair and Parts; removal and installation
procedures
CDTRAY Flex cable on tray assembly See the service documentation for instructions.
DEVTERM Bus Terminator See the service documentation for instructions.
MEDIA Optical Media System operation information
PTFSRCH Licensed Internal Code See the service documentation for instructions.

(6A59) Workstation adapter console reference codes

The workstation adapter console detected a failure.

Look at characters 5 through 8 of the top 16 character line of function 11 (4 rightmost characters of word
1). These 4 characters are the unit reference code. Find the unit reference code in the following table.

For more on the Failing Item column entries, see Table 2. Workstation adapter console failing items
Details, which follows the reference code table below.

Table 1. (6A59) Workstation adapter console reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
0AD2 to 0AD3 Communications adapter card test failed FI00718

Reference codes 155

6A59

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
0B25 Communications adapter card test failed FI00719
FI00718
FI00727
0BA0, 0BAB, 0BB0, Communications adapter card test failed FI00719
0BD0 to 0BD1 FI00718
0BEE I/O card Licensed Internal Code ended abnormally FI00719
FI00718
0C10 Communications adapter card test failed FI00719
FI00718
FI00727
0C20 Communications adapter card test failed FI00719
FI00718
0C30 Adapter card failed modem interface test FI00719
FI00718
0C40, 0C43 Synchronous-data-link-control send-receive test failed FI00719
FI00718
0C50, 0C53 Binary synchronous control send-receive test failed FI00719
FI00718
0C60, 0C63 Asynchronous send-receive test failed FI00719
FI00718
0C70, 0C80 Communications adapter card test failed FI00719
FI00718
0C90 Communications adapter card X.21 test failed FI00719
FI00718
0CA1, 0CC0 Communications adapter card test failed FI00719
FI00718
5007 Diagnostic wrap test completed; no errors detected
5008 Diagnostic wrap test completed; error was detected FI00719
DPAC
FI00718
FFFF User suspected communications problem. UNAUPPR

Table 2. Workstation adapter console failing items details

Failing Item Description Document Description

DPAC Communications two-port adapter cable Problem Analysis; Symbolic FRU Isolation
UNAUPPR User suspected problem

(7208) Tape drive reference codes

A tape or tape library device failure occurred.

156 System i® and System p®: Reference codes

7208

3. Clean the recording head in the tape device.

4. Attempt the failing operation again. Does the operation complete successfully?
v Yes: You have corrected the problem. This ends the procedure.
v No: Is the failing tape unit located in a type 9427 Tape Library device?
– Yes: Go to “(9427) Tape unit reference codes” on page 163.
– No: Look at the 4 rightmost characters of the Data display for Function 11, which represent the
unit reference code. Find the unit reference code in the following table.

Table 1. (7208) Model 012 Tape drive reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
0001 Tape unit failure 46G2227
ML2TMED
The tape drive reported a hardware error to the IOP; the amber light on
the tape drive may be blinking.

Perform TU-PIP2.
030B Tape unit detected a read error on the tape medium ML2TMED
46G2227
Read (or write) errors may be caused by: 46G3934
v Poor or damaged tape 42F7300
v Dirty read/write heads
v Damaged data cartridges
v Using a data cartridge previously recorded in a format or density that is
not correct
v Using the wrong data cartridge (for example, one in a different format or
density from another set of data cartridges)

If the data on the tape was not written by i5/OS®, the format or the
density may not be correct. Get or make a new copy of the data cartridge.

If you are performing a write or a save operation, initialize the tape. See
the note below.

If you are performing a read or a restore operation, the tape may be worn
or the device that wrote the tape may be the cause of the problem.

Perform TU-PIP2.

When the system is available, perform the following:

v Verify the operation of the tape drive. Use the VFYTAP system
command.
Note: When a tape is initialized, a new label is recorded at the beginning
of the tape, and any data recorded previously is erased and overwritten. To
initialize used tapes, use the INZTAP system command with “Check for
active files” option of *NO.

Use of the INZTAP “Clear” (security erase) option is not recommended.

The 7208 Tape Drive performs a write operation to erase all of the tape;
writing (erasing) a full-size tape takes up to 3.5 hours.
0311, 0316 Tape unit detected a read error on the tape medium ML2TMED
46G2227
Perform the Action for reference code 030B. 46G3934
42F7300

Reference codes 157

7208

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
031C The data format is incorrect; the tape cannot be read ML2TMED
46G2227
The tape format is not known or not compatible. The data cartridge may
not have been recorded using i5/OS.

Get another copy of the data cartridge recorded in a format and density
given support by i5/OS.
0336 The data format is incorrect; the tape cannot be read ML2TMED
46G2227
The tape format is not known or not compatible. The data cartridge may 46G3934
not have been recorded using i5/OS. 42F7300
Get another copy of the data cartridge recorded in a format and density
given support by i5/OS.
0337 to 0338, 033D Tape unit detected a read error on the tape medium ML2TMED
46G2227
Perform the Action for reference code 030B. 46G3934
42F7300
0395 to 0397, 039D Tape unit detected a write error on tape medium ML2TMED
to 039F 46G2227
Perform the Action for reference code 030B.
03AE, 03B0 Tape unit detected a read or write error on tape medium ML2TMED
46G2227
Perform the Action for reference code 030B.
03B3 to 03B4 Tape unit detected a write error on tape medium ML2TMED
46G2227
Perform the Action for reference code 030B.
03B5 Tape unit detected a read error on the tape medium ML2TMED
46G2227
Perform the Action for reference code 030B.
0417 to 0419, 0458, Tape unit failure 46G2227
045A, 0467 to ML2TMED
0468, 046D, 0498 The tape drive reported a hardware error to the IOP; the amber light on 46G3934
to 049A, 049C, the tape drive may be blinking. 42F7300
04A1 to 04A8,
04AB to 04AD, Perform TU-PIP2.
04FA, 04FC to
04FD
3002 I/O processor addressed the tape unit; no response 46G2227
46G3934
The tape drive did not respond to commands from the IOP. Perform the FI00830
following: FI00141
1. Ensure that the system interface cable is connected. 46G2599
2. Ensure that power is on. 17G1500
42F7300
If the above items are correct, call your next level of support
3004 Tape unit failed after Licensed Internal Code was loaded 46G2227

The tape drive does not respond to IOP commands after new Licensed
Internal Code was transferred to the tape drive.

9810 Problem analysis has determined a part should be replaced.

This reference code is used for ending Online Problem Analysis with a list
of failing items. (Information only)
9899 Problem analysis completed, the problem has been corrected. UL2FIXD

This reference code is used for ending Online Problem Analysis when no
problem was found or the problem was corrected.
9900, FF09 Licensed Internal Code for tape unit was not upgraded UL2WAIT

The I/O processor loading of Licensed Internal Code (LIC) to the

programmable tape drive was not completed.

The tape drive will continue to operate with the previous LIC. You may do
either of the following:
v Wait for next IPL when the system will attempt to load the LIC for the
tape drive again.
v Perform TU-PIP4 to reset the IOP and the tape drive. When the IOP is
reset, if the device has the wrong level of LIC, the IOP will attempt to
load the new LIC.
FF4D I/O processor successfully recovered from temporary error 46G2227
FI00141
No action required. This reference code is logged for information only. FI00830
46G2599
When the system is available, display the operator messages, find message 46G3934
CPI946B, and press F14 to run online problem analysis to see if the error 17G1500
threshhold has been exceeded. 42F7300
AJEDA00

Reference codes 161

7208

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
FF5D I/O processor successfully recovered from temporary error 46G2227
46G3934
No action required. This reference code is logged for information only. FI00830
FI00141
When the system is available, display the operator messages, find message 46G2599
CPI946B, and press F14 to run online problem analysis to see if the error 17G1500
threshhold has been exceeded. 42F7300
FFF6 Tape volume statistics logged (no action required)

No action required. This reference code is logged for information only.

FFF8 Asynchronous device attached; synchronous device expected 46G2227

The attached device is operational and working in the asynchronous mode

of data transfer.

The IBM tape unit uses the synchronous mode of data transfer; if the
attached device is an IBM tape unit, exchange the tape unit.
FFFE Tape unit detected a read error on the tape medium ML2TMED
46G2227
Perform the Action for reference code 030B. 46G3934
42F7300
FFFF Tape unit detected a write error on tape medium ML2TMED
46G2227
Perform the Action for reference code 030B.

Table 2. Model 012 Tape drive failing items

Failing Item Description Document Description

17G1500 Internal signal cable 7208 Model 012 5.0GB External 8mm Tape Drive
Service Guide
42F7300 Fan 7208 Model 012 5.0GB External 8mm Tape Drive
Service Guide
46G2227 Tape drive 7208 Model 012 5.0GB External 8mm Tape Drive
Service Guide
46G2599 Terminating plug 7208 Model 012 5.0GB External 8mm Tape Drive
Service Guide
46G3934 Power supply 7208 Model 012 5.0GB External 8mm Tape Drive
Service Guide
AJEDA00 I/O processor Licensed Internal Code Service Functions; APAR or LICTR
ANYBUS IOP card bus error Problem Analysis; Symbolic FRU Isolation
ML2TMED Defective tape 7208 Model 012 5.0GB External 8mm Tape Drive
Service Guide
UL2CLN Tape unit needs cleaning Magnetic tape subsystem operator’s information
UL2CNFG Tape configuration detected by I/O processor; Magnetic tape subsystem operator’s information
not valid
UL2USR1 Operator action required Magnetic tape subsystem operator’s information
UL2WAIT Wait to next IPL or perform TU-PIP4 Problem Analysis

(9348) Tape unit reference codes

A tape or tape library device failure occurred.

162 System i® and System p®: Reference codes

9348

Use the following procedure to handle reference codes that might be displayed during a type D IPL to
install the operating system. If you are not performing a type D IPL of the operating system, consult any
error logs that you find in the Serviceable Event View. If you cannot locate an error log in the Serviceable
Event View that corresponds with the failure, run a verification test for the tape unit.
1. Verify that the device has power.
2. Check the device for any error indications. Refer to the device service information to resolve any error
indications.
3. Clean the recording head in the tape device.
4. Attempt the failing operation again. Does the operation complete successfully?
v Yes: The problem has been corrected. This ends the procedure.
v No: Look at the 4 rightmost characters of the Data display for Function 11, which represent the unit
reference code. See the 9348 Tape Unit Service Information and find the unit reference code.

(9427) Tape unit reference codes

A tape or tape library device failure occurred.

For more on the Failing Item column entries, see Table 2. Tape unit failing items details, which follows
the reference code table below.

Table 1. (9427) Tape unit reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
0001 Tape unit failure

Refer to the 9427 8mm Tape Cartridge Library Service Guide.

Reference codes 163

9427

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
03xx Tape unit detected an error on the tape medium

Read (or write) errors may be caused by:

v Poor or damaged tape
v Dirty read/write heads
v Damaged data cartridges
v Using a data cartridge previously recorded in a format or density that is
not correct
v Using the wrong data cartridge (for example, one in a different format or
density from another set of data cartridges)

Do the following:
1. Clean the tape unit and retry the operation.
2. If cleaning the tape unit does not correct the problem, exchange the
tape media.
04xx Tape unit failure

The tape drive reported a hardware error to the IOP; the amber light on
the tape drive may be blinking.

Refer to the 9427 8mm Tape Cartridge Library Service Guide.

3xxx Device or interface error.

Refer to the 9427 8mm Tape Cartridge Library Service Guide.

4016 to 4017 Licensed Internal Code for the tape unit is not correct AJEDA00
9020 I/O processor detected a SCSI bus configuration error ULYCNFG
86G9251
Before exchanging any parts, verify that the following conditions are not FI00130
present: 86G9254
v Tape and DASD devices attached to an I/O Processor that does not
support attachment of both tape and DASD devices at the same time.
v A device type or model that is not given support.
9100 Interface error detected by I/O processor or by tape unit 86G9251
FI00131
Before exchanging any parts, do the following: 86G9254
1. Ensure that the device is powered on. EXTSCSI
2. Ensure that the SCSI cable between the device and the I/O Processor or 86G9255
I/O Adaptor is seated correctly, and that there are no bent or damaged 86G9274
pins on the SCSI cable. 17G9134
FI00130
3. Ensure that a terminating plug is attached to the device.
9200 I/O processor addressed the tape unit; no response 86G9251
86G9274
Before exchanging any parts, do the following: 86G9254
1. Ensure that the device is powered on. FI00131
2. Ensure that the SCSI cable between the device and the I/O Processor or EXTSCSI
I/O Adaptor is seated correctly, and that there are not bent or damaged 17G9134
pins on the SCSI cable. 87G1531
86G9255
3. Ensure that the terminating plug is attached to the device.

164 System i® and System p®: Reference codes

9427

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
9201 Tape unit command timeout 86G9251
FI00131
Before exchanging any parts, do the following: 86G9254
1. Ensure that the device is powered on. EXTSCSI
2. Ensure that the SCSI cable between the device and the I/O Processor or 17G9134
I/O Adaptor is seated correctly, and that there are not bent or damaged 86G9255
pins on the SCSI cable. 86G9274
FI00130
3. Ensure that the terminating plug is attached to the device.
9202 Tape unit failed after Licensed Internal Code was loaded 86G9251
86G9274
Before exchanging any parts, do the following: 86G9254
1. Ensure that the device is powered on.
2. Ensure that the SCSI cable between the device and the I/O Processor or
I/O Adaptor is seated correctly, and that there are not bent or damaged
pins on the SCSI cable.
3. Ensure that the terminating plug is attached to the device.
9210 Illegal or unsupported tape unit response 86G9251
FI00130
FI00131
9300 Tape unit failure 86G9251
LIBDEV
The tape drive reported a hardware error to the IOP; the amber light on MLYTMED
the tape drive may be blinking. 86G9274
86G9255
Perform TU-PIP2.
9301 Tape device failure, redundancy lost 86G9251
LIBDEV
The tape device detected a hardware failure that does not prevent the tape MLYTMED
unit from completed the current operation. 86G9274
86G9255
Refer to the Tape unit service information to determine the failing item.
9302 Tape device failure or media error MLYTMED
86G9251
The tape unit detected a failure that may be caused by a hardware failure
or a media error.

Refer to the tape unit service information for possible information on

diagnostic tests that can be run to isolate between hardware and media
failures.
9310 Licensed Internal Code for the tape unit is not correct 86G9251
FI00130
9320 Tape device Licensed Internal Code failure FI00130
86G9251
9350 Tape unit detected a read or write error on tape medium MLYTMED
86G9251
A permanent read or write error occured. Clean the tape unit and retry the
operation.

If cleaning the tape unit does not correct the problem, exchange the tape
media.
9351 Tape with excessive error rate was mounted in tape device. MLYTMED
ULYCLN
The tape unit detected that the mounted tape cartridge has a history of 86G9251
excessive read and write errors. It is recommended that you exchange the
tape cartridge.

Reference codes 165

9427

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
9355 The data format is incorrect; the tape cannot be read ULYUSR1
MLYTMED
The tape unit has detected that the data format on the tape media is not ULYCLN
supported. 86G9251
Clean the tape unit and retry the operation.

If the operation continues to fail, use a different tape cartridge.

9500 I/O processor Licensed Internal Code error FI00130

If the system is operational, perform a dump of the I/O processor data. For
more information, see Performing an IOP dump using hardware service
manager.
9600 Equipment Check Failure on Library Device. LIBDEV

See library device service information to resolve the error.

9800 to 9803 I/O processor successfully recovered from temporary error

No action required. This reference code is logged for information only.

9810 Problem analysis has determined a part should be replaced.

This reference code is used for ending Online Problem Analysis with a list
of failing items. (Information only)
9899 Problem analysis completed, the problem has been corrected. ULYFIXD

This reference code is used for ending Online Problem Analysis when no
problem was found or the problem was corrected.
9900 Licensed Internal Code for tape unit was not upgraded ULYWAIT

The I/O processor loading of Licensed Internal Code (LIC) to the

programmable tape drive was not completed.

The I/O processor loading of Licensed Internal Code (LIC) to the

programmable tape drive was not completed.

166 System i® and System p®: Reference codes

9427

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
FF4D I/O processor successfully recovered from temporary error 86G9251
FI00141
No action required. This reference code is logged for information only. EXTSCSI
17G9134
When the system is available, display the operator messages, find message 86G9253
CPI946B, and press F14 to run online problem analysis to see if the error 86G9255
threshhold has been exceeded. AJSLC01
FF5D I/O processor successfully recovered from temporary error 86G9251
86G9253
No action required. This reference code is logged for information only. EXTSCSI
FI00141
When the system is available, display the operator messages, find message 17G9134
CPI946B, and press F14 to run online problem analysis to see if the error 86G9255
threshhold has been exceeded.
FFF6 Tape volume statistics logged (no action required)

No action required. This reference code is logged for information only.

FFF8 Asynchronous device attached; synchronous device expected 86G9251

The attached device is operational and working in the asynchronous mode

of data tranfer. The IBM tape unit uses the synchronous mode of data
transfer; if the attached device is an IBM tape unit, exchange the tape unit.
FFFE Tape unit detected a read error on the tape medium MLYTMED
86G9251
Perform the Action for reference code 03xx. 86G9253
FFFF Tape unit detected a write error on tape medium MLYTMED
86G9251
Perform the Action for reference code 03xx.

Table 2. Tape unit failing items details

Failing Item Description Document Description

17G9134 Terminating plug Magnetic tape subsystem service information
86G9251 Tape Drive 7208 Model 012 5.0GB External 8mm Tape Drive
Service Guide
86G9251 Tape drive Magnetic tape subsystem service information
86G9253 Power supply Magnetic tape subsystem service information
86G9254 Controller logic card Magnetic tape subsystem service information
86G9255 Internal signal cable Magnetic tape subsystem service information
87G1531 Operator Panel/LCD Assembly Magnetic tape subsystem service information
AJSLC01 I/O processor Licensed Internal Code Service Functions; APAR or LICTR
EXTSCSI Cable assembly Problem Analysis; Symbolic FRU Isolation
LIBDEV Media Library Device Magnetic tape subsystem service information
MLYTMED Defective tape System operation information
ULYCLN Tape unit needs cleaning Magnetic tape subsystem operator’s information
ULYCNFG Tape configuration detected by I/O processor; Magnetic tape subsystem operator’s information
not valid
ULYUSR1 Operator action required Magnetic tape subsystem operator’s information
ULYWAIT Wait to next IPL or perform TU-PIP4 Problem Analysis

Reference codes 167

A1xx

(A1xx) Service processor reference (attention) codes

An A1xx system reference (attention) code is an attention code posted by the service processor. An A1XX
SRC offers information about a platform or service processor dump, confirms a control panel function
request, or indicates an issue with a service processor wake-on-LAN setting.

The A1xx table uses the following format:

v The first column, Reference Code, contains numbers that identify a particular action your server
performs during initialization of firmware.
v The second column, Description/Action, offers a brief description about this SRC. It may also contain
instructions for continuing the problem analysis.
v The third column, Failing Item, offers a link to instructions service actions for recovering from a hang
on an attention code. Click the failing item code only when you experience a hang condition on an
attention code. For example, a hang condition occurs when your server performs a requested action
but the SRC in the control panel display does not change for several minutes and the service processor
appears to be hung.

Table 1. (A1xx) Service processor reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
A1003000 Platform dump was successful FSPSPD1
A1003001 Reserved (for platform dump) FSPSPD1
A1003022 Confirm partition dump (control (operator) panel function 22) FSPSPD1

The control panel displays this attention code after you request a partition
dump (panel function 22). When you see this code, scroll to function 22
again on the panel and press Enter to perform the partition dump.
A1003042 Confirm platform dump (control panel function 42) FSPSPD1

The control panel displays this attention code after you request a platform
dump (panel function 42). When you see this code, scroll to function 42
again on the panel and press Enter to perform the platform dump.
A1003043 Confirm service processor dump (control panel function 43) FSPSPD1

The control panel displays this attention code after a service processor
dump (panel function 43) is requested. When you see this code, scroll to
function 43 again on the panel and press Enter to perform the service
processor dump.
A1008008 Confirm fast power-off (control panel function 08) FSPSPD1

This attention code is displayed on the control panel after you request a
fast power-off (panel function 08). When you see this code, scroll to
function 08 again on the panel and press Enter to perform the fast
power-off.
A1008009 Beginning emergency power off (EPO) countdown FSPSPD1
A100800A Proceeding with EPO. This SRC displays after the countdown has FSPSPD1
completed successfully.
A1751000 Service processor service action in progress FSPSPD1
A181D000 The hypervisor did not respond to a ROLE or FAILOVER message. FSPSPD1
A181D001 The hypervisor did not post an Xdown interrupt when a reset/reload FSPSPD1
occurred.
A1A3C100 Invalid operational mode for remote power on (wake on LAN)

Check the service processor settings for remote power on.

168 System i® and System p®: Reference codes

A2xx, B2xx

(A2xx, B2xx) Logical partition reference codes

When the server posts these SRCs, you can find them in the Serviceable Event View or the view that you
use to see informational logs (such as the Product Activity Log or ASM).
1. Characters 3 and 4 of word 1 are the partition ID of the logical partition with the problem.
2. If the SRC begins with A2xx, no service action is required. If the SRC begins with B2xx, find the next
4 characters of the SRC (called the unit reference code) in the following table.

Table 1. (A2xx, B2xx) Logical partition reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
1150 A problem occurred during the IPL of a partition. LPARCFG

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format).

This is a partitioning configuration problem. The LPARCFG Symbolic FRU

will help correct the problem.

If the problem persists, call your next level of support.

1225 A problem occurred during the IPL of a partition. SVCDOCS

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format).

The partition attempted to IPL prior to the platform fully initializing. Retry
the partition IPL after the platform IPL has fully completed and the
platform is not in standby mode. If that IPL fails, call your next level of
support.
1230 A problem occurred during the IPL of a partition. LPARCFG
LICCODE
The partition ID is characters 3 and 4 of the B2xx reference code in word 1
of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format).

This is a partitioning configuration problem. The partition is lacking the

necessary resources to IPL.

This error might occur when you shut down a partition that is set to
automatically IPL and then turn the managed system off and back on.
When the partition automatically IPLs, it uses the resources specified in
PHYP NVRAM, and this error occurs when the server does not find the
exact resources specified in NVRAM. The solution is to activate the
partition by using the partition profile on the HMC. The HMC applies the
values in the profile to NVRAM. When the partition IPLs, it uses the
resources specified in the profile.
1260 A problem occurred during the IPL of a partition. SVCDOCS

The partition could not IPL at the Timed Power On setting because the IPL
setting of the partition was not set to Normal. The partition ID is characters
3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal
format). If characters 3 and 4 are both zero, then the partition ID is in
extended word one as LP=xxx (in decimal format).

Reference codes 169

A2xx, B2xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
1265 A problem occurred during the IPL of a partition. SVCDOCS

The partition could not IPL. The partition ID is characters 3 and 4 of the
B2xx reference code in word 1 of the SRC (in hexadecimal format). If
characters 3 and 4 are both zero, then the partition ID is in extended word
one as LP=xxx (in decimal format).

An operating system MSD IPL was attempted with the IPL side on
D-mode. This is not a valid operating system IPL scenario, and the IPL will
be halted. This SRC is usually seen when a D-mode SLIC install fails and
attempts an MSD.
1266 A problem occurred during the IPL of a partition. SVCDOCS

You are attempting to IPL an operating system that is not supported.

1280 A problem occurred during a partition Main Storage Dump. NEXTLVL

A mainstore dump IPL did not complete due to configuration mismatch.

Contact your next level of support.
1281 A partition memory error occurred SVCDOCS

An attempt to perform a partition dump failed. A partition memory error

occurred. The failed memory will no longer be used. The partition dump
was terminated. The partition ID is in extended word one as LP=xxx (in
decimal format). Re-IPL the partition.
1310 A problem occurred during the IPL of a partition. SVCDOCS

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). No alternate (D-mode) IPL IOP was selected. The IPL will attempt
to continue, but there may not be enough information to find the correct
D-mode load source.

Have the customer configure an alternate IPL IOP for the partition. Then
retry the partition IPL.
1320 A problem occurred during the IPL of a partition. SVCDOCS

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). No default load source IOP was selected for an A/B-mode IPL.
The IPL will attempt to continue, but there may not be enough information
to find the correct load source.

Have the customer configure a load source IOP for the partition. Then retry
the partition IPL.

170 System i® and System p®: Reference codes

A2xx, B2xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
1321 A problem occurred during the IPL of a partition. SVCDOCS

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). The IOA for the load source device needed an IOP, and none was
detected. Check your LPAR configuration and make sure the correct slot is
specified for the IPL load source. Then retry the partition IPL.
1322 A problem occurred during the IPL of a partition. SVCDOCS

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). During the partition IPL, code tried to determine if the device in a
slot was an I/O Processor or an I/O Adapter. That check failed. Check
your LPAR configuration and make sure that the correct slot is specified
for the IPL load source. Then retry the partition IPL. If this does not
resolve the problem, perform LICIP15.
2048 A problem occurred during a partition Main Storage Dump. NEXTLVL

A mainstore dump IPL did not complete due to a copy error. Contact your
next level of support.
2058 A problem occurred during a partition Main Storage Dump. NEXTLVL

A mainstore dump IPL did not complete due to a copy error. Contact your
next level of support.
2250, 2300 A problem occurred during the IPL of a partition. SLOTUSE

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). A slot that was needed for the partition was unavailable. See the
Symbolic FRU SLOTUSE for more information on the cause of this error.
2310, 2320, 2425 to A problem occurred during the IPL of a partition. NEXTLVL
2426
The partition ID is characters 3 and 4 of the B2xx reference code in word 1
of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). The platform LIC for this partition attempted an operation. There
was a failure. Contact your next level of support.
2475 A problem occurred during the IPL of a partition. SLOTUSE

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

If you have a RAID enablement card (CCIN 5709) on your system, it will
disable an embedded SCSI adapter. If that embedded slot is called out in
the error, you can safely ignore this error.

Reference codes 171

A2xx, B2xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
2485 A problem occurred during the IPL of a partition. NEXTLVL

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). The platform LIC for this partition attempted an operation. There
was a failure. Contact your next level of support.
3000 System log entry only, no service action required

A user requested an immediate termination and main store dump of a

partition. The partition ID is in extended word one as LP=xxx in decimal
format.
3081 A problem occurred during the IPL of a partition. LICCODE

IPL did not complete due to a copy error. Contact your next level of
support.
3110 A problem occurred during the IPL of a partition. SVCDOCS

The search for a valid load source device was exhausted. The partition ID
is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in
hexadecimal format). If characters 3 and 4 are both zero, then the partition
ID is in extended word one as LP=xxx (in decimal format). Perform
LICIP15.
3113 A problem occurred during the IPL of a partition. SVCDOCS

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). A problem occurred on the path to the load source for the
partition.

If present, look in the Serviceable Event View for a B7xx xxxx during the
partition’s IPL. Correct that error and retry the partition IPL.
3114 A problem occurred during the IPL of a partition. NEXTLVL

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format).

The B2xx xxxx SRC Format is Word 1: B2xx3114, Word 3: Bus, Word 4:
Board, Word 5: Card.
3120 System log entry only, no service action required

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). Retry count exceeded. This is logged for each unsuccessful attempt
to IPL with a loadsource candidate. If the IPL fails, look for other
serviceable errors.
3123 System log entry only, no service action required

172 System i® and System p®: Reference codes

A2xx, B2xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
3125 A problem occurred during the IPL of a partition. LICCODE

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format).

This is a platform LIC main store utilization problem. The platform LIC
could not obtain a segment of main storage within the platform’s main
store to use for managing the creation of a partition.
3128 A problem occurred during the IPL of a partition. NEXTLVL

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). An unexpected failure return code was returned when attempting
to query the IOA slots that are assigned to an IOP.

Look for B700 69xx errors in the Serviceable Event View and work those
errors.
3130 A problem occurred during the IPL of a partition. NEXTLVL

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). If word 3 is zero, then this SRC is informational and can be
ignored.

Otherwise there is a problem in the platform LIC. A nonzero bus number

has no associated bus object.

Look for B700 69xx errors in the Serviceable Event View and work those
errors.

If there are no serviceable B700 69xx errors, or if correcting the errors did
not correct this problem, contact your next level of support.
3135 A problem occurred during the IPL of a partition. NEXTLVL

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). An unknown bus type was detected.
3140 A problem occurred during the IPL of a partition. SVCDOCS

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). The load source IOP is not owned by the partition. This is a
configuration problem in the partition. Have the customer reconfigure the
partition to have the intended load source IOP.

If there is not a configuration problem then contact your next level of

support.

Reference codes 173

A2xx, B2xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
3141 System log entry only, no service action required

The IOP in the slot used for the last successful IPL of the operating system
was replaced with an I/O Adapter. The IPL will continue by searching for
a valid load source device.

Check the LPAR configuration if required, and ensure that the tagged I/O
for the partition is correct.
3142 System log entry only, no service action required

The I/O Adapter in the slot used for the last successful IPL of the
operating system was replaced with an I/O Processor. The IPL will
continue by searching for a valid load source device.

Check the LPAR configuration if required, and ensure that the tagged I/O
for the partition is correct.
3143 System log entry only, no service action required

The I/O Adapter in the slot used for the last successful IPL of the
operating system was removed. The IPL will continue by searching for a
valid load source device.

Check the LPAR configuration if required, and ensure that the tagged I/O
for the partition is correct.
3144 System log entry only, no service action required

The I/O Processor in the slot used for the last successful IPL of the
operating system was removed. The IPL will continue by searching for a
valid load source device.

Check the LPAR configuration if required, and ensure that the tagged I/O
for the partition is correct.
3200 System log entry only, no service action required

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format).

Look for a SRC in the Serviceable Event View logged at the time the
partition was performing an IPL.

This error indicates a failure during a search for the load source. There may
be a number of these failures prior to finding a good load source. This is
normal. If a B2xx3110 error is logged, a B2xx3200 may be posted to the
control panel. Work the B2xx3110 error in the Serviceable Event View. If the
system IPL hangs at B2xx3200 and you cannot check the SRC history,
perform the actions indicated for the B2xx3110 SRC.

174 System i® and System p®: Reference codes

A2xx, B2xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
4158 System log entry only, no service action required

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format).

Look for a SRC in the Serviceable Event View logged at the time the
partition was performing an IPL.

This error indicates a failure during a search for the load source. It is usual
for a number of these failures to occur prior to finding a valid load source.
This is normal. If a B2xx3110 error is logged, a B2xx3200 may be posted to
the control panel. Work the B2xx3110 error in the Serviceable Event View. If
the system IPL hangs at B2xx3200 and you cannot check the SRC history,
perform the actions indicated for the B2xx3110 SRC.
5106 A problem occurred during the IPL of a partition. NEXTLVL

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

Contact your next level of support.

5109 A problem occurred during the IPL of a partition. NEXTLVL

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). There was a partition main storage dump problem. Contact your
next level of support.
5114 A problem occurred during the IPL of a partition. NEXTLVL

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). There is not enough space to contain the partition main storage
dump. Contact your next level of support.
5115 A problem occurred during the IPL of a partition. NEXTLVL

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). There was an error reading the partition’s main storage dump
from the partition’s load source into main storage.
5117 A problem occurred during the IPL of a partition. SVCDOCS

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). A partition main storage dump has occurred but cannot be written
to the load source device because a valid dump already exists.

Use the Main Storage Dump Manager to rename or copy the current main
storage dump.

Reference codes 175

A2xx, B2xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
5121 A problem occurred during the IPL of a partition. NEXTLVL

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). There was an error writing the partition’s main storage dump to
the partition’s load source.
5122 to 5123 System log entry only, no service action required

A problem occurred during the IPL of a partition.

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format).

An error occurred when writing the partition’s main storage dump to the
partition’s load source. No service action required.
5135 A problem occurred during the IPL of a partition. NEXTLVL

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). There was an error writing the partition’s main storage dump to
the partition’s load source.
5137 A problem occurred during the IPL of a partition. NEXTLVL

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). There was an error writing the partition’s main storage dump to
the partition’s load source.
5145 A problem occurred during the IPL of a partition. NEXTLVL

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). There was an error writing the partition’s main storage dump to
the partition’s load source.
5148 A problem occurred during the IPL of a partition. NEXTLVL

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). An error occurred while doing a main storage dump that would
have caused another main storage dump.

Contact your next level of support.

6006 A problem occurred during the IPL of a partition. NEXTLVL

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). A platform LIC error occurred when the partition’s memory
initialized. The IPL will not continue.

Contact your next level of support.

176 System i® and System p®: Reference codes

A2xx, B2xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
6012 A problem occurred during the IPL of a partition. NEXTLVL

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). The partition’s LID failed to completely load into the partition’s
mainstore area.

Contact your next level of support.

6015 A problem occurred during the IPL of a partition. LSERROR

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format).

The load source media is corrupted or not valid.

6025 A problem occurred during the IPL of a partition. LSERROR

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format).

This is a problem with the load source media being corrupt or not valid.
6027 A problem occurred during the IPL of a partition. NEXTLVL

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format).

A failure occurred when allocating memory for an internal object used for
LID load operations. Ensure the partition was allocated enough main
storage, verify that no memory leaks are present, and then retry the
operation.
6110 A problem occurred during the IPL of a partition. LSERROR

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). Error on load source device.
690A A problem occurred during the IPL of a partition. NEXTLVL

An error occurred while copying Open Firmware into the partition load
area. Contact your next level of support.

Reference codes 177

A2xx, B2xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
7200 System log entry only, no service action required

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). An error condition was encountered when communicating with
the load source I/O Processor for the partition identified in the xx field of
the B2xx SRC.

This informational error indicates a failure resetting the I/O Processor in

the preceding B2xx3200 error. This may be normal. If there is a hardware
failure there will be a different serviceable event. If the system IPL hangs at
B2xx7200 and you cannot check the SRC history, perform the actions
indicated for the B2xx3110 SRC.
8080 System log entry only, no service action required
8081 A problem occurred during the IPL of a partition. LICCODE

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). An internal LIC timeout has occurred. The partition may continue
to IPL but it may experience problems while running.
8105 A problem occurred during the IPL of a partition. SVCDOCS

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). There was a failure loading the VPD areas of the partition.
Possible causes are:
v Corrupted/unsupported load source media
v Insufficient resources allocated to the partition
v Unsupported partition configuration by the operating system

If the problem is due to media, replace the load source media. If the
problem is due to insufficient resources, allocate enough resources to the
partition. If the problem is due to unsupported partition configuration,
correct the partition configuration.
8107 A problem occurred during the IPL of a partition. LICCODE

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). There was a problem getting a segment of main storage in the
platform’s main store.
8109 A problem occurred during the IPL of a partition. LICCODE

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). A failure occurred. The IPL is terminated. Ensure that there is
enough memory to IPL the partition.
8112 A problem occurred during the IPL of a partition. LICCODE

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). A failure occurred. The IPL is terminated.

178 System i® and System p®: Reference codes

A2xx, B2xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
8113 A problem occurred during the IPL of a partition. LICCODE

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

There was an error mapping memory for the partition’s IPL. Call your next
level of support.
8114 A problem occurred during the IPL of a partition. LICCODE

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

There was a failure verifying VPD for the partition’s resources during IPL.
Call your next level of support.
8115 A problem occurred during the IPL of a partition. LICCODE

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). There was a low level partition to partition communication failure.
8117, 8121, 8123, A problem occurred during the IPL of a partition. NEXTLVL
8125, 8127, 8129
Partition did not IPL due to platform Licensed Internal Code error.

Contact your next level of support.

813A A problem occurred during the IPL of a partition. SVCDOCS

Ensure that the console device cables are connected properly. If the cables
are already connected properly, replace the cables. Re-IPL the partition. If
the problem reoccurs, contact your next level of support.
A100 to A101 A problem occurred after a partition ended abnormally. SVCDOCS

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). This partition could not stay running and shut itself down.

Work any error logs in the Serviceable Event View. If there are no errors,
contact your next level of support.
B07B System log entry only, no service action required
B215 A problem occurred after a partition ended abnormally. NEXTLVL

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). There was a communications problem between this partition’s
service processor and the platform’s service processor.

The platform will need to be re-IPLed before that partition can be used.
Call your next level of support.

Reference codes 179

A2xx, B2xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
C1F0 A problem occurred during a power off a partition NEXTLVL

Internal platform Licensed Internal Code error occurred during partition

shutdown or re-IPL.

Contact your next level of support.

D150 A problem occurred after a partition ended abnormally. LICCODE

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). There was a communications problem between this partition and
code that handles resource allocation. Call your next level of support.
E0AA A problem occurred during the IPL of a partition. SVCDOCS

Ensure that the console device cables are connected properly. If the cables
are already connected properly, replace the cables. Re-IPL the partition. If
the problem reoccurs, contact your next level of support.
F001 A problem occurred during the IPL of a partition. SVCDOCS

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). An operation has timed out.

Ignore this error if there are other serviceable errors. Work those error logs
for this partition and for the platform from the Serviceable Event View. If
there are no errors, contact your next level of support.
F003 A problem occurred during the IPL of a partition. NEXTLVL

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). Partition processors did not start LIC within the timeout window.

Capture a Partition Dump and call your next level of support.

F004 A system request to power off a partition failed NEXTLVL

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). The partition did not respond to a system request to power off the
partition. This partition had a communications problem.

If the partition is an i5/OS partition, capture a Partition Dump. Contact

your next level of support.

180 System i® and System p®: Reference codes

A2xx, B2xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
F005 A system request to power off a partition failed NEXTLVL

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

If the partition is an i5/OS partition, perform a Partition Dump and contact

your next level of support.

For all other partition types, a Partition Dump is not supported. If the
system is Hardware Management Console (HMC) or Integrated
Virtualization Manager (IVM) controlled, do an immediate partition power
off. If the system is not HMC or IVM controlled, perform a Function 8 on
the control panel. After the partition has powered off, re-IPL the partition,
collect error logs and contact your next level of support.
F006 A problem occurred during the IPL of a partition. SVCDOCS

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

of the SRC (in hexadecimal format). If characters 3 and 4 are both zero,
then the partition ID is in extended word one as LP=xxx (in decimal
format). The code load operation for the partition’s IPL timed out.

Work any error logs for this partition in the Serviceable Event View. If there
are no errors, contact your next level of support.
F007 A problem occurred during a power off a partition LICCODE

The partition ID is characters 3 and 4 of the B2xx reference code in word 1

A timeout occurred during the process of trying to stop a partition from

running. Contact your next level of support.
F008 A problem occurred during the IPL of a partition.

During an IPL, a timeout occurred while waiting for a ready message from
the partition.

Look for other errors. Re-IPL the partition to recover.

F009 System log entry only, no service action required

During an IPL, a timeout occurred while waiting for a response to a

message.

Look for other errors. Re-IPL the partition to recover.

F00A to F00B System log entry only, no service action required

During an IPL, a timeout occurred while waiting for a response to a

message.

Look for other errors. If this SRC is displayed in the operator panel, then
panel function 34 might be used to retry the current IPL while the partition
is still in the failed state.

Reference codes 181

A2xx, B2xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
F00C System log entry only, no service action required

During an IPL, a timeout occurred while waiting for a response to a

message.

Look for other errors. If this SRC is displayed in the operator panel, then
panel function 34 might be used to retry the current IPL while the partition
is still in the failed state.
F00D Timeout occurred during a main store dump IPL

If this SRC is displayed in the operator panel during a main store dump
IPL, then panel function 34 might be used to retry the current main store
dump IPL while the partition is still in the failed state.

(A6xx, B6xx) Licensed Internal Code reference codes

Use this table for both A6xx and B6xx reference codes. Bus errors are of the form B600 69xx. Other
subsystems that produce Licensed Internal Code errors are also represented in the B6xx Reference Code
Table.

Perform the following:

1. Find the SRC in the SRC column of the following table.
2. Perform the actions in the What You Should Do column of the table.

In all cases, after you determine the failing item, go to the locations table for the system or tower you are
working on to determine the location, and to the removal and replacement procedure for the failing item.

Table 1. General description of recommended actions

SRC What You Should Do

11 A6xx xxxx Licensed Internal Code intervention is needed.
1. Look at characters 5 through 8 of the top 16 character
line of function 11 (4 rightmost characters of word 1).
These 4 characters are the unit reference code.
2. See the following table (Table 2) and find the unit
reference code.
11 B6xx xxxx The Licensed Internal Code detected a failure.
1. Look at characters 5 through 8 of the top 16 character
line of function 11 (4 rightmost characters of word 1).
These 4 characters are the unit reference code.
2. See the following table (Table 2) and find the unit
reference code.
3. When working with the Product Activity Log, System
Licensed Internal Code entries often occur as a
secondary effect of other hardware related entries.
The following list is a suggested method of isolating
these kinds of problems.
a. Examine the date and time of the informational
reference codes.
b. Determine if any other reference codes were
logged at or before the same date and time.
c. Start the service approach based on these other
logged errors.

182 System i® and System p®: Reference codes

A6xx, B6xx

For more on the Failing Item column entries, see Table 3. Licensed Internal Code failing items details,
which follows the reference code table below.

Table 2. (A6xx, B6xx) Licensed Internal Code reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
0000 Operating system status code

This reference code is for information only. It is shown in the Product

activity log as a side effect of a condition that was detected by LIC.

Normally, no action should be taken as a result of information reference

codes. However, to isolate the root cause, use these suggestions:
1. Examine the date and time of the informational reference code.
2. Determine if any other reference codes have been logged at or before
the same date and time.
3. Begin the service approach based on these other logged errors.
0102 A machine check occurred during IPL

Words 2 to 9 of this SRC contain additional diagnostic information. Record

SRC words 1 through 9 before attempting to IPL again and report the
problem to your Software Service Provider.
0103 Main storage dump must be copied for service.

Perform LICIP01.
0104 Terminate Immediate reference code is bad AJDG301

Perform LICIP08.
0105 More than one request to terminate the system was issued AJDG301

Perform LICIP08.
0106 Terminate Immediate data is not valid AJDG301

Perform LICIP08.
0107 Main storage dump must be copied for service.

The server detected an unrecoverable machine check condition.

Collect all the words of the SRC and the main store dump and send to
your system manufacturer for analysis.
0109 An unrecoverable memory error occurred SVCDOCS

Re-IPL the partition that terminated. Then, look for and correct errors with
SRCs of the form B1xxxxxx in the Serviceable Event View that indicate the
replacement of memory in the failing item list. If there are no B1xxxxxx
SRCs in the Serviceable Event View that indicate a memory problem,
perform a slow boot in order to run diagnostics on the memory. Then, look
for and correct erros with SRCs of the form B1xxxxxx in the Serviceable
Event View.
0202 Unrecoverable read error

Restore the Licensed Internal Code using “Licensed Internal Code Install
and Restore” in the iSeries Service Functions information.

Reference codes 183

A6xx, B6xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
0210 The system ASP has run out of disk storage

The out of storage condition in the system ASP can be caused by an

allocation failure in some other system software. This could be a looping
condition that continues to allocate storage. Contact your service
representative for assistance with the Main Storage Dump.
0231 Disk sanitize action completed successfully

No service action required. This entry is logged for information only.

0232 Disk sanitize action did not complete successfully

Provide the Product Activity Log entry to your next level of support for
analysis.
0244, 0255, 0266 Contact was lost with the device indicated FI00580
FI00500
Do not power off the system. FI00302
FI00301
Perform LICIP13. AJDG301
0277 A compression disk unit cannot complete an operation.

Note: Do not power off the system when performing this procedure.

Look at the 4 leftmost characters of the Data display for word 7. These four
characters indicate the type of problem that exists and the recovery action
to perform.

If these characters are 8402 or 2002, the compression disk unit is

temporarily full of data. The command to the compression disk is being
held. When the storage subsystem controller has created sufficient space on
the compression disk unit to contain the data, the command which is being
held will be released and the system will resume normal processing. If the
system does not resume normal processing within 20 minutes, contact your
next level of support.

If these characters are 8400 or 2000, the compression disk unit is full of
data. The command to the compression disk is being held.

The customer should perform the recovery actions specified in “Disk Unit

Full Considerations” in the Backup and Recovery Guide .

0302 Recursion in exception handler AJDG301

Perform LICIP08.
0304 Component specific exception handler return code not valid AJDG301

Perform LICIP08.
0305 Exception while storage management lock is held AJDG301

Perform LICIP08.
0307 to 0308 LIC exception code detected a problem AJDG301

Component Specific Exception Handler recursion is detected in an OS/400

process.

Perform LICIP08.
0317 Traceback for code not found AJDG301

Perform LICIP08.

184 System i® and System p®: Reference codes

A6xx, B6xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
0323 to 0329 LIC exception code detected a problem AJDG301

Perform LICIP08.
0333 A branch to a bad address was attempted AJDG301

Perform LICIP08.
0334 Exception Handler could not be removed AJDG301

Perform LICIP08.
0335 Code resumed to not valid address following exception AJDG301

Perform LICIP08.
0401 A machine check occurred during IPL AJDG301

Perform LICIP08.
0402 A machine check occurred during authority initialization AJDG301

Perform LICIP08.
0403 Unhandled exception during IPL or install AJDG301

Perform LICIP08.
0405 Unhandled exception in authority recovery AJDG301

Perform LICIP08.
0406 Unhandled exception in data base recovery AJDG301

Perform LICIP08.
0407 Unhandled exception in data base initialization AJDG301

Perform LICIP08.
0408 Unhandled exception in journal recovery AJDG301

Perform LICIP08.
0409 Unhandled exception in journal synchronization AJDG301

Perform LICIP08.
0410 Unhandled exception in journal clean up AJDG301

Perform LICIP08.
0411 Unhandled exception in commit recovery AJDG301

Perform LICIP08.
0412 Unhandled exception in commit initialization AJDG301

Perform LICIP08.
0413 Rebuild of recovery object index failed AJDG301

Perform LICIP08.
0414 Install of operating system failed on read from media FI00300

Perform LICIP08.
0415 Create user profile failed AJDG301

Perform LICIP08.

Reference codes 185

A6xx, B6xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
0417 Initiating the initial process failed AJDG301

Perform LICIP08.
0418 to 0419, 0420 The information loaded from the install media is not valid AJDG301

Perform LICIP08.
0421 Bad return code creating a queue or message AJDG301

Perform LICIP08.
0422 The Load/Dump command failed AJDG301

Perform LICIP08.
0439 Opening the IPCF connection failed AJDG301

Perform LICIP08.
0440 Termination code is not valid AJDG301

Perform LICIP08.
0441 Power off system command failed AJDG301

Perform LICIP08.
0443 Programmed IPL command failure AJDG301

Perform LICIP08.
0446 Error during machine termination AJDG301

Perform LICIP08.
0447 Failure to reach MI boundary AJDG301

Perform LICIP08.
0449 Exception in MI boundary manager AJDG301

Perform LICIP08.
0506 Attempt to destroy a task with critical flag on AJDG301

Perform LICIP08.
0607 Maximum stack size exceeded in process or task AJDG301

Perform LICIP08.
0620 Event management index is not usable AJDG301

Perform LICIP08.
0650 Resource management segment could not be created or extended AJDG301

A main store dump was initiated.

Words 2 to 9 of this SRC contain additional diagnostic information. Record

SRC words 1 through 9.

Perform a system IPL and collect the Product activity log and main store
dump and provide them along with the recorded SRC information to IBM
Service Support.

The problem may also be that there is not enough auxiliary storage.

186 System i® and System p®: Reference codes

A6xx, B6xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
0801 Invalid LID directory detected FI00070
FI00300
During system IPL, the LIDMgr detected an I/O failure or media failure AJDG301
while trying to read the LID directory.

Perform LICIP08.
0802 LID directory unusable AJDG301

During system IPL, the LIDMgr detected that the LID directory and
associated load source is not usable.

Reinstall the Licensed Internal Code by using Utilities to install and restore
Licensed Internal Code.

For more information, contact IBM Service Support.

0901 The LinkLoader has found its bad flag ON

This reference code is usually the result of a system termination while the
LinkLoader is performing its work.

Reinstall the Licensed Internal Code by using Utilities to install and restore
Licensed Internal Code.
0902 Unable to perform programmed IPL

The LinkLoader was not successful in performing a programmed IPL.

Perform a system IPL. If the problem persists, examine the main storage
dump and determine the reason for the failure of the programmed IPL.
1001 Enqueuing a task to the TDQ which is already enqueued on TDQ AJDG301

Perform LICIP08.
1103 MISR not readable; must be readable for Normal Mode install

MISR is not readable. Perform a manual install to reinitialize the system.

1104 Failure reading media or not install media

Determine that correct install media is loaded. If correct install media is

installed, media could be corrupt. Obtain another copy of the install media
and reattempt the install. If the install still fails, contact your service
representative.
1201 Critical database segment could not be created AJDG301

Perform LICIP08.
1204 Error in constraint enforcement AJDG301

Perform LICIP08.
1210 Object not found in the in-use table AJDG301

Perform LICIP08.
1215 Error in critical code sequence AJDG301

Perform LICIP08.
1219 A back leveled driver has been detected AJDG301

Perform LICIP08.

Reference codes 187

A6xx, B6xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
1604 Not able to create APPN task AJDG301

An error occurred during task creation which requires a power off of the
system.

Perform LICIP08.
1724 An attempt to create a segment failed AJDG301

The create could fail for two reasons:

v A code problem
Perform LICIP08.
v No free auxiliary storage on the system
Add additional DASD if the create failed because no auxiliary storage
was available.
1730 An IPL is needed to restore system performance GG4PL01

Licensed Internal Code has detected a condition that is impacting system

performance. System operation can continue, but system performance may
be noticeably reduced until the next IPL.

Look at the Product Activity Log entry, and find the value at offset
x’000180’. If the value equals x’00000122’, the error was caused by too
much processor memory being installed.

For more information, contact IBM Service Support.

3000 Logical partition service function Main Storage Dump. AJDG301

Copy the current main storage dump to media. For more information on
how to copy a Main Storage Dump, refer to the iSeries Service Functions
Information (see ″Copying a Main Storage Dump″ under ″Working with
Storage Dumps″).
41FC Installation of LIC failed SVCDOCS

Words 12 and 13 of this SRC contain additional diagnostic information.

Install LIC using physical media.

To determine what caused the failure, collect SRC information and contact
your next level of support.
41FD Installation of LIC failed SVCDOCS

A main store dump was initiated. Words 12 and 13 of this SRC contain
additional diagnostic information.

To recover the partition using the previously installed LIC, perform a

B-mode IPL. You can then re-try the installation of LIC. Otherwise, install
LIC using physical media.

To determine what caused this failure, collect SRC information and main
store dump and contact your next level of support.
4401 Missing DASD units.

Copy the current main storage dump to media.

For more information on how to perform a Main Storage Dump, refer to

iSeries Service Functions information (see ″Copying a Main Storage Dump″
under ″Working with Storage Dumps″).

188 System i® and System p®: Reference codes

A6xx, B6xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
4402 Missing DASD units.

Copy the current main storage dump to media. Then exit the Main Storage
Dump Manager.

For more information on how to perform a Main Storage Dump, refer to

iSeries Service Functions information (see ″Copying a Main Storage Dump″
under ″Working with Storage Dumps″).
4403 Storage Management failed to reach full paging.

Copy the current main storage dump to media.

For more information on how to perform a Main Storage Dump, refer to

iSeries Service Functions information (see ″Copying a Main Storage Dump″
under ″Working with Storage Dumps″).
4404 Auto copy failed or not attempted.

Copy the current main storage dump. If copying to system ASP, existing
copies may need to be deleted or renamed. Then exit the Main Storage
Dump Manager.

For more information on how to perform a Main Storage Dump, refer to

iSeries Service Functions information (see ″Copying a Main Storage Dump″
under ″Working with Storage Dumps″).
4405 System ASP threshold exceeded after auto copy done.

Delete other system ASP copies or exit the Main Storage Dump Manager
and then from DST copy the Auto Copy to media and then delete the Auto
Copy in system ASP.
4420 MSD Manager not configured to save dump information

The platform produced dump data, but the Main Storage Dump (MSD)
Manager was not configured to automatically copy the dump to an
Auxiliary Storage Pool (ASP). The dump will be lost if the system power is
lost. Use MSD Manager to manually copy the current platform dump to
media or an ASP.
4421 Insufficient space in the ASP to store a platform dump

The platform produced dump data, and the Main Storage Dump (MSD)
Manager was configured to automatically copy the dump to an Auxiliary
Storage Pool (ASP), but there was not sufficient free space available in the
ASP. The dump will be lost if the system power is lost. Manually copy the
current platform dump from the platform by performing one of the
following:
v Make room in the designated ASP and then use the MSD Manager to
copy the current platform dump to ASP.
v Use the MSD Manager to delete other dump copies, then copy the
current platform dump to ASP.
v Use the MSD Manager to copy the current platform dump to a different
ASP.
v Use the MSD Manager to copy the current platform dump to media.
4422 A platform dump is saved in MSD Manager PLDUMP

The platform produced dump data. The dump data was copied to the
Main Storage Dump (MSD) Manager.

Reference codes 189

A6xx, B6xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
4700 Processor On Demand error detected. CTLPNCD

Processor on Demand Data Block key is not valid.

Replace the Processor Capacity card.

4701 Processor On Demand error detected. AJDG301

Processor On Demand Data Block contains data that does not match the
expected data.

Contact your service provider.

4703 Processor On Demand error detected. AJDG301

Processor On Demand Serialization has failed during IPL.

Contact your service provider.

4710 Processor On Demand error detected. SPNLCRD

SPCN communication failure during Processor On Demand.

Look in the Product Activity Log for other SPCN errors and perform the
actions indicated for those errors.
4712 Processor On Demand error detected. CTLPNCD

Correct any Processor Capacity card or SPCN failures.

4713 Incorrect Processor Capacity Card installed. CTLPNCD

The Processor Capacity Card is the failing item since it has been swapped
in from a different system.

Put the Processor Capacity Card back in the system it came from, and
reinstall this system’s original Processor Capacity Card.
4714 The CUoD data is not present. A problem may exist.

The Processor Capacity Card was changed and there may be a problem.

If the system did have any activated standby processors before the
Processor Capacity Card was replaced, then new processor on demand
activation codes must be obtained to restore the previous activations.

Contact your service provider.

4715 Processor On Demand error detected. CTLPNCD

Correct any Processor Capacity card or SPCN failures.

4730 Processor On Demand error detected. AJDG301

Processor On Demand standby processors are in use.

Contact your service provider.

4731 Processor On Demand error detected. AJDG301

The Processor On Demand Trial Activation period is not valid. Contact

your next level of support.
4733 Processor On Demand error detected. AJDG301

Contact your service provider.

190 System i® and System p®: Reference codes

A6xx, B6xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
4740 Processor On Demand error detected. AJDG301

The Processor On Demand Activation code just entered is not valid.

Contact your next level of support.

4741 Processor On Demand error detected. AJDG301

An invalid Processor On Demand Activation code has been entered more

than 5 consecutive times. Contact your service provider.
4745 Processor Capacity card replaced on activated POD system.

Contact IBM Support to order a replacement Processor On Demand

activation code.
4747 1 hour left in POD 14 day Trial Activation Period.

If a new activation code was purchased, it should be entered now.

Otherwise, the system will revert back to its previous activation state at the
end of the Trial Activation Period.
5001 DST received no response from a work station controller FI00380
AJDG301
The workstation I/O processor for the system or partition console did not
respond.

Perform RTRIP01 to determine which Isolation procedure to perform.

5002 DST problem attempting to use the system console AJDG301
FI00380
A code problem occurred during an attempt to use the system console.

Perform LICIP03.
5003 Service program failed FI00320
FI00602
The ASCII system console failed to respond. UG4USR1
AJDG301
FI00380
5004 DST console failed to respond FI00320
FI00602
The system console failed to respond. UG4USR1
AJDG301
Perform RTRIP02 to determine which isolation procedure to perform. FI00380
5005 Service program failed FI00320
FI00602
The workstation adapter system console failed to respond. UG4USR1
AJDG301
Perform WSAIP01. FI00380
5007 Service program failed FI00320
FI00602
The workstation adapter console failed to respond. UG4USR1
AJDG301
Perform RTRIP07 to determine which isolation procedure to perform. FI00380
5008 DST console failed to respond FI00719

Perform OPCIP03.
5010 IPL service function ended abnormally AJDG301

Perform LICIP04.

Reference codes 191

A6xx, B6xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
5082 DST lost contact with the console AJDG301
UG4USR1
A service program lost contact with the system console.

Perform RTRIP03 to determine which isolation procedure to perform.

5083 IPL service function ended abnormally AJDG301
UG4USR1
A service program lost contact with the system console.

Perform TWSIP01.
5090 System startup failed in unattended IPL mode FI00580
FI00500
Perform the following: FI00301
v If reference code A6005090 is displayed on the control panel for more FI00021
than 10 minutes, perform LICIP11. FI00065
v For reference code B6005090, perform LICIP11. AJDG301

5092 System is in DASD migration mode

“Install Licensed Internal Code” and “Upgrade Load Source” was specified
but the key is not in the manual position. Change the key position to
manual and perform a system IPL.
5094 IASP detected a failure during the vary on operation SVCDOCS

Perform LICIP12.
50FF DST unrecoverable program error AJDG301
FI00380
Perform LICIP03.
5120 System LIC detected a program exception AJDG301
FI00130
System LIC detected a programming problem. If performance or other
system degradation is occurring, the system may be operating with
reduced resources.

Check the Product activity log for related entries. If this reference code is
logged with a Class of Informational, then no action is required.

Otherwise, perform LICIP01.

5121 System LIC program exception occurred AJDG301

System LIC detected a programming problem for which a main storage

dump may have been initiated.

A problem log entry may be generated for this ref code.

Perform LICIP01.
5122 System LIC program exception occurred FI00130
AJDG301
System LIC detected an IOP programming problem for which an IOP FI00131
dump may have been initiated.

Perform LICIP01.

192 System i® and System p®: Reference codes

A6xx, B6xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
5123 System LIC program exception occurred FI00130
AJDG301
System LIC detected an interface problem with the IOP or an IOP FI00131
programming problem for which an IOP and main storage dump may have
been initiated.

Perform LICIP01.
5126 Addressed device failed to respond to selection DISKDRV
STORIOA
DISKTRY
FI01106
FI01140
FI01141
DEVTERM
BACKPLN
5127 IOP timed out a disk command DISKDRV
STORIOA
FI01106
DISKTRY
FI01140
FI01141
DEVTERM
BACKPLN
5128 I/O processor failure FI01112
FI01107
512D An IOP dump was initiated

Copy the IOP dump entry and any related entries from the Product
Activity Log to suitable media, and give to an IBM service representative.
512E System LIC program exception occurred AJDG301
FI00130
The system was in a D IPL mode when the problem was detected. A main
storage dump was not taken.

Perform LICIP01.
5206 System LIC detected a missing IOP LIC code load UG4USR1

System LIC detected a missing IOP LIC code load during IPL of the IOP.
This indicates that either the IOP code load is not installed on the system
load source device or that system LIC was unable to successfully read that
load from the load source device.

Perform LICIP01.
5209 System LIC detected an IOP timeout during IOP IPL UG4USR1
FI00130
Verify that all IOP cable connections are secure, and check tape and other AJDG301
non-disk devices and media to verify that they are in a ready state.

Perform LICIP01.
5219 System LIC program exception occurred FI00310
FI00318
An IOP signalled to system LIC that it had entered a critical internal state. FI00065
LIC automatically attempted to restart the IOP. FI00130
AJDG301
This reference code is logged for information only. No action is required.

Reference codes 193

A6xx, B6xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
5275 The system issued a reset/reload to the IOP.

System Licensed Internal Code detected that an IOP Reset/Reload has

occurred, and that the IOP successfully recovered.

Users who were signed on to a Workstation device under the IOP will need
to sign back on. Any LAN/WAN communications lines under the IOP will
need to be restarted. Tape/Optical devices under the IOP may need to be
varied back on.

To determine the cause of the IOP Reset/Reload, check the Product

Activity Log for additional entries logged with the same System Log ID,
and perform any actions indicated for those errors.
5276 IOP Reset was issued AJGLD01
AJDG301
LIC has detected a problem with the Service Processor IOP and has reset it FI00021
but has not initiated reload of the Service Processor.

If the load source is mirrored, some system operations may be able to

continue normally. However, some system service operations have been
suspended and the system should be scheduled for power down as soon as
possible.

Perform RTRIP08.
5310 System LIC program exception occurred LPARSUP

System LIC detected a logical partition configuration data consistency error.

Copy the Product Activity Log data for this error and any related entries
and contact your next level of hardware service support.
5311 System LIC program exception occurred LPARSUP

LPAR configuration data does not match current system configuration. The
system will not IPL past DST until the problem is corrected.

Following is a list of problems which may have caused this SRC to be

reported:
v Non-configured disk unit which was previously a load source on a
partitioned system.
v Load source configuration data does not match partition for which it is
being used.
v Load source configuration data does not match system serial number for
which it is being used.
v Load source configuration data is newer than primary partition
configuration data.

Perform LPRIP01.
5312 System LIC program exception occurred

LPAR configuration data informational error.

The LPAR configuration data was found to be or inconsistent on a

secondary partition’s load source. The data was automatically updated to
the current system level.

194 System i® and System p®: Reference codes

A6xx, B6xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
5313 System LIC program exception occurred LPARCFG

LPAR configuration data informational error.

The LPAR configuration data was found to be inconsistent on a primary

partition and could only be corrected with an older copy of the data.
5320 Incorrect hardware configuration detected.

An I/O Adapter used by a guest partition is located in a card slot on the

same PCI bridge set as an I/O Processor. Guest partition data may be lost
if any of the following occur:
v A primary partition Type D IPL is performed.
v The I/O Adapter is moved to an operating system partition.
v An error causes the logical partition (LPAR) configuration to not be used.

To correct the hardware configuration, either the I/O Adapter or the I/O
Processor must be moved to a new location. Use the LPAR Validation Tool
(LVT) to create a valid configuration. For more information about the LPAR
Validation Tool, see the following web site:

http://www.ibm.com/eserver/iseries/lpar
5340 Secondary partition not running at optimum.

Check the Primary partition’s Product Activity Log for system processor
entries from approximately the same time. Perform the actions indicated
for those entries.
5341 Secondary partition not running at optimum.

Check the primary partition Product Activity Log for system memory
entries from approximately the same time. Perform the actions indicated
for those entries.
5342 Secondary partition not running at optimum.

Check the Primary partition’s Product Activity Log for system processor
entries from approximately the same time. Perform the actions indicated
for those entries.
5343 Secondary partition not running at optimum.

Check the Primary partition’s Product Activity Log for system memory
errors from approximately the same time. Perform the actions indicated for
those entries.
5344 Secondary partition not running at optimum. LPARSUP

The interactive performance specified in the configuration data for this

partition could not be met.

Contact your next level of support.

5350 Secondary partition software release not supported.

The logical partition software version is outside the supported release

delta. Check the Release Delta from the Primary partition ″Display
Partition Release Level″ screen.

Check the LPAR documentation for the release level of the Primary
partition and determine what the supported Release Delta is.

Reference codes 195

A6xx, B6xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
5380 System LIC program exception occurred LPARSUP

Record the Product Activity Log (PAL) hex data for this SRC or print the
PAL entry.

Contact your next level of support.

5390 System LIC program exception occurred LPARSUP

Record the Product Activity Log (PAL) hex data for this SRC or print the
PAL entry.

Contact your next level of support.

5505 The copying of DASD log data to the IOP log was successful

IOP log data can be copied to a spool file for examination by the
development lab.
5555 SLIC I/O DASD subsystem error recovery in progress.
5600 Unrecoverable read error SVCDOCS

VPD data could not be read.

Look for other errors implicating hardware. There is no way to know what
VPD read has failed, but the resource is not useable and should generate
an error.

If no such error occurred, call your next level of support.

6900 System bus error Contact your next level of support. FI00065
AJDG301
6901 Bus Expansion Adapter card failed Contact your next level of support. LBUSADP
AJDG301
6902 Bus Expansion Adapter card failed Contact your next level of support. FI00203
AJDG301
6905 Optical bus failed Contact your next level of support. FI00065
LBUSADP
AJDG301
6906 High Speed Link (HSL) I/O bridge failure SIIOADP
OPT_CLN
LIC could not access part of the HSL I/O bridge VPD. The bridge and HSL
loop may be prevented from becoming operational.

For this reference code the failing item list presented in the Service Action
Log (SAL), or serviceable event viewer you are working with, can be
different from the failing item list documented here. That is due to the
differences in system models and features installed.

If the Service Action Log (SAL) or serviceable event view on the HMC is
available then use the failing item list presented there for servicing this
reference code.

NOTE: A fiber optic cleaning kit may be required for optical HSL
connections.

196 System i® and System p®: Reference codes

A6xx, B6xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
6907 High Speed Link (HSL) I/O bridge failure SIIOADP
OPT_CLN
LIC detected invalid data in the HSL I/O bridge VPD. The bridge and HSL
loop may not have become operational.

For this reference code the failing item list presented in the Service Action
Log (SAL), or serviceable event view you are working with, can be
different from the failing item list documented here. That is due to the
differences in system models and features installed.

If the Service Action Log (SAL) or serviceable event view on the HMC, is
available then use the failing item list presented there for servicing this
reference code.

NOTE: A fiber optic cleaning kit may be required for optical HSL
connections.
6908 High Speed Link (HSL) I/O bridge failure SIIOADP
OPT_CLN
LIC data in the I/O bus vpd could not be accessed. The I/O Bus identified
in the SRC may not have become operational.

If there is a B600 6906 reference code, close this problem in the serviceable
event view you are working with and work the 6906 error.

If the Service Action Log or serviceable event view on the HMC or service
processor is available then use the failing item list presented there for
servicing this reference code.

NOTE: A fiber optic cleaning kit may be required for optical HSL
connections.

Reference codes 197

A6xx, B6xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
6909 High Speed Link (HSL) I/O bridge failure SIIOADP
OPT_CLN
LIC detected invalid data in the I/O bus VPD. The bus and resources
associated with it may not be operational.

If the Service Action Log (SAL) or serviceable event viewer on the HMC is
available then use the failing item list presented there for servicing this
reference code.

If the serviceable event view only indicated a frame or enclosure see the
locations section for the frame or enclosure type. The location of the HSL
I/O Bridge will be given in the locations tables.

NOTE: A fiber optic cleaning kit may be required for optical HSL
connections.
690A Associated adapter not found in this partition LICIP16

Perform LICIP16.
6910 I/O processor failure FI00310
FI00318
An I/O processor timed out, returned bad status, or is not following the FI00065
system bus protocol. FI00130
AJDG301
Perform LICIP07.
6938 Not valid system configuration detected

This system model does not allow a configuration of more than three
(non-OptiConnect) I/O Processors.

Power down the system and remove the extra (non-OptiConnect) I/O
Processor(s) so that there are three or less. Restart the system.
6944 Missing or failed I/O processor cards FI00317
FI00316
A system bus appears to be empty. If the bus is not empty, two I/O AJDG301
processors in consecutive slots may be missing or broken. If there are
broken I/O processors, then another more serious SRC has occurred.
Otherwise find the bus number for this failure from the Product activity
log and use the system configuration list to verify the configuration of the
I/O processors on that bus.
6960 Multi-adapter bridge card slot error, do not use card slot SLOTERR

Slot unavailable due to 64 bit card in adjacent slot.

One of the messages documented with the symbolic FRU will describe the
problem. See the SLOTERR symbolic FRU for a list of messages and
corrective actions.

198 System i® and System p®: Reference codes

A6xx, B6xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
6961 Multi-adapter bridge card slot error, do not use card slot SLOTERR
MASBUS
LED control failure, do not use slot.

The card location is not available for use. The Failing Item with the card
slot error is in the Failing Item list for this reference code.

See the SLOTERR symbolic FRU for the list of messages and a further
description of the problem detected by Licensed Internal Code.

If the Service Action Log or a serviceable event viewer on the HMC is

available for this problem then use the failing item list presented there for
servicing this reference code.

If a serviceable event view is not available then use the failing item list
documented here. By following the procedures in the symbolic FRUs listed
here you will isolate to the correct FRU list based on system model and
features installed.
6962 Multi-adapter bridge card slot error, do not use card slot SLOTERR
MASBUS
Power control failure, do not use slot.

If there is a Linux partition in the system, any IOPs plugged into slots
owned by a Linux partition will not power on. This error will be logged.
Correct the situation by removing the IOP cards.

The card location is not available for use. The Failing Item with the card
slot error is in the Failing Item list for this reference code.

See the SLOTERR symbolic FRU for the list of messages and a further
description of the problem detected by Licensed Internal Code.

If the Service Action Log, or serviceable event view on the HMC is

available then use the failing item list presented there for servicing this
reference code.

Reference codes 199

A6xx, B6xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
6963 Multi-adapter bridge card slot error, do not use card slot SLOTERR
MASBUS
Power control failure, do not use slot.

The card location is not available for use. The Failing Item with the card
slot error is in the Failing Item list for this reference code.

See the SLOTERR symbolic FRU for the list of messages and a further
description of the problem detected by Licensed Internal Code.

If the Service Action Log or serviceable event viewer on the HMC is

available then use the failing item list presented there for servicing this
reference code.

If serviceable event view is not available then use the failing item list
documented here. By following the procedures in the symbolic FRUs listed
here you will isolate to the correct FRU list based on system model and
features installed.
6964 Multi-adapter bridge configuration change or error MABRCFG

One of several errors or configuration problems has occurred under a

Multi-adapter bridge. If you are using the Service Action Log (SAL), or the
serviceable event viewer on the HMC or the service processor, then the
correct FRU, description and card position(s) will be listed. Use the FRUs
and descriptions in the serviceable event view you are working with to
determine the problem.

If you do not have access to the Service Action Log, or serviceable event
view on the HMC or service processor, then word 4 of the SRC has more
information. Examine the last 4 digits in word 4 to determine the problem
by comparing them to the list below and using the FRU(s) listed here.
1. xxxx2022 - IOP found in slots owned by a Linux partition. The
Mutli-adapter Bridge and PCI Bridge set that it controls are assigned to
a Linux partition. The IOP found in the SLOT indicated by the DSA in
word 7 will not be configured.
2. xxxx2014 - I/O adapters were found under the Multi-adapter Bridge
but there is no IOP to support them. The adapters cannot be used.
3. xxxx2015 - An card type was found that cannot be supported in the
card position where it is located.

See the MABRCFG symbolic FRU for the list of messages, a further
description of the problem detected by Licensed Internal Code and the
corrective action.
6965 Multi-adapter bridge configuration change or error MABRCFG

Card type not supported in this slot.

An I/O processor or I/O adapter card type is installed in the location

indicated in word 7 of the SRC. The card type is not supported in that slot
under the Multi-adapter bridge. The card is unavailable.

See the MABRCFG symbolic FRU for the list of messages, a further
description of the problem detected by Licensed Internal Code and the
corrective action.

200 System i® and System p®: Reference codes

A6xx, B6xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
6966 Multi-adapter bridge configuration change or error MABRCFG

I/O processor removed from multi-adapter bridge card slot.

On the previous IPL an I/O processor was in the card location specified in
word 7 of the SRC. The I/O processor was not detected on this IPL.

See the MABRCFG symbolic FRU for the list of messages, a further
description of the problem detected by Licensed Internal Code and the
corrective action.
6967 Multi-adapter bridge configuration change or error MABRCFG

I/O adapter unavailable due to moved I/O processor card.

The I/O adapter specified in word 7 of the SRC is not available. On the
previous IPL there was an I/O processor card the adapter was assigned to.
The I/O processor was not detected on this IPL.

See the MABRCFG symbolic FRU for the list of messages, a further
description of the problem detected by Licensed Internal Code and the
corrective action.
6968 Multi-adapter bridge configuration change or error MABRCFG

IOA removed from multi-adapter bridge slot.

On the previous IPL an I/O adapter was in the card slot specified in word
7 of the SRC. That I/O adapter was not detected on this IPL.

See the MABRCFG symbolic FRU for the list of messages, a further
description of the problem detected by Licensed Internal Code and the
corrective action.
6969 Multi-adapter bridge configuration change or error MABRCFG

I/O adapter replaced by I/O processor card.

On the previous IPL there was an I/O adapter in the location specified in
word 7 of the SRC. This IPL LIC detected that the IOA was replaced by an
IOP in that location.

See the MABRCFG symbolic FRU for the list of messages, a further
description of the problem detected by Licensed Internal Code and the
corrective action.
696A Card slot test failed FI00131
BACKPLN
Perform LICIP14.

Reference codes 201

A6xx, B6xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
696B Card slot could not be validated

This can be caused by ″PCI error injection policy″ being set to ″YES″ and
an I/O Processor being installed on the same Multi-adapter bridge domain
as the I/O Adapter. Do one of the following:

-- Using the HMC or a customer PC with a Web browser access the

Advanced System Management Interface (ASMI) and disable PCI error
injection policy.

-- Vary off the I/O Adapter. Using Hardware Service manager in SST/DST,
locate the I/O Adapter resource. Using concurrent maintenance on the
associated packaging resource, remove the I/O Adapter and install it in a
location that does not have I/O Processors on the same Multi-adapter
bridge domain.

-- Vary off the I/O Adapter. Use the concurrent maintenance option in
Hardware Service Manager in SST/DST to power off all I/O Processors
located on the same Multi-adapter bridge domain as the I/O Adapter. Use
concurrent maintenance to power off and power on the I/O Adapter. Then
use concurrent maintenance to power on the I/O Processors located on the
same Multi-adapter bridge domain as the I/O Adapter.

202 System i® and System p®: Reference codes

A6xx, B6xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
6970 High Speed Link (HSL) resource failure SI_PHB
PRI_PCI
A system PCI bus failure was detected. Word 7 of the SRC contains the bus MA_BRDG
number. BRDGSET
OPT_CLN
This failure can occur when a tower in an HSL loop is powered off using
concurrent maintenance. If this is the case, close this problem.

This error is most likely in the hardware that makes up the PCI bus, the
PCI bus side of the HSL I/O bridge or the multi-adapter bridge. In some
cases it may be caused by a failing IOP in the multi-adapter bridge’s
domain. When an IOP is causing the problem, the failing IOP cannot be
identified.

NOTE: This SRC can occur for the PCI bus resource on a PCI bus in an
I/O expansion unit when the unit is powered off for a concurrent
maintenance action.

Exchange the failing items, one at a time, in the order they are listed in the
serviceable event view or this document until you get to the BRDGSET or
BRDGSTx symbolic FRU. If the problem still exists after exchanging the
failing items up to, but not including, BRDGSET or BRDGSTx then perform
MABIP03 to determine the failing I/O processor card.

If the Service Action Log, or serviceable event view on the HMC or service
processor, is available then use the failing item list presented there for
servicing this reference code.

NOTE: A fiber optic cleaning kit may be required for optical HSL
connections.
6971 High Speed Link (HSL) resource failure MA_BRDG
MASBUS
Failure in a multi-adapter bridge or on the bus to the card location it PIOCARD
controls.

For this reference code the failing item list presented in the Service Action
Log (SAL) or serviceable event view you are working with, can be different
from the failing item list documented here. That is due to the differences in
system models and features installed.

If the Service Action Log (SAL) or serviceable event viewer is available

then use the failing item list presented there for servicing this reference
code.

Perform MABIP02

Reference codes 203

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
6985 High Speed Link (HSL) loop status message SIRSTAT
HSL_LNK
If this SRC is not in the Service Action Log (SAL), or serviceable event SIIOADP
view you are using, then it is informational. Use FRU SIRSTAT to SICNTRL
determine what this SRC means. Otherwise, continue with the following OPT_CLN
steps:

This error can appear as a serviceable event when a tower, or I/O unit or
another system in the loop did not complete powering on before LIC on
this system checked this loop for errors. Search the Product Activity Log
(PAL) for the last B600 6985 SRC logged for this loop and use FRU
SIRSTAT to determine if this error requires service. If the last entry
indicates the loop is functioning (determined by FRU SIRSTAT) then no
service action is required, close this problem

There may be multiple B600 6985 logs with xxxx 3205 in word 4 errors for
the same loop resource in the serviceable event view. This is caused by
retry and recovery attempts. If there is a B600 6985 with xxxx 3206 or xxxx
3208 in word 4 after the above B600 6985 entries in the PAL, then the
recovery efforts were successful. If this is the case, close all the B600 6985
entries for that loop resource in the serviceable event view.
1. If you find a B600 6981 in the serviceable event view then close that
problem and go to step 2. Otherwise perform the following:
v Perform RIOIP06 to determine if any other systems are connected to
this loop and return here. (HSL_LNK or HSLxxxx FRU in the Service
Action Log (SAL) entry, or serviceable event view you are working
with, indicates the loop number.) If there are other system(s) then
continue with the steps that follow, otherwise go to step 2.
v Check for HSL failures on the other system(s) before replacing parts.
HSL failures are serviceable event entries with HSL I/O Bridge and
Network Interface Controller (NIC) resources. Ignore B600 6982 and
B600 6984 entries. If there are HSL failures on other system(s) then
continue with the steps that follow, otherwise go to step 2.
v Repair the problems on the other systems and return to this step.
After making repairs on the other system(s) check the Product
Activity Log (PAL) of this system for a B600 6985 logged after the
repairs you made on the other system(s). If you find one then
continue with the steps that follow, otherwise go to step 2.
v For the B600 6985 log you found, use FRU SIRSTAT to determine if
the loop is now complete. If the loop is complete then this problem
has been resolved. Use RIOIP01 to verify that the loop is now
working properly. Otherwise, go to step 2.
2. Use the serviceable event’s FRU list when it is available.
If this SRC appears in the Service Action Log (SAL), or the serviceable
event view you are using, with the Symbolic FRU HSL_LNK or
HSLxxxx listed as a FRU, then perform problem isolation procedure
RIOIP01. Otherwise exchange the FRUs listed in the serviceable event
view.

NOTE: A fiber optic cleaning kit may be required for optical HSL
connections.

Reference codes 207

A6xx, B6xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
6986 System bus error TWRCARD
CBLALL
During IPL, system LIC detected an HSL I/O bridge that was already
initialized. The bridge should have been in a flushed and unintialized state
after powering on. There is a problem with SPCN components that
prevented the tower from powering off after a previous power off was
issued. The tower will not be configured for this IPL.

This reference code is equivalent to 1xxx 90F0. When referring to the

″CBLALL″ symbolic FRU in the Failing Item list, perform the ″CBLALL″
procedure using reference code ″90F0″.

Word 5 of the SRC identifies the frame. Determine the frame by breaking
down word 5:

Word 5 -> xxxx xxNN where: NN is the frame number in hexadecimal

format.
6987 High Speed Link (HSL) connection failure HSL_LNK
OPT_CLN
Failures are occurring on the HSL link.

There may be B600 6982 errors logged on the same loop and about the
same time as this error. Close those errors and continue to correct the
problem by working this error.
v If there is a cable FRU in the serviceable event entry:
1. If the connection is copper and either end has a loose connection,
reseat the cable. To do this, disconnect the connection and wait a
minimum of 30 seconds. Then reconnect the cable and complete the
tightening process in at most 30 seconds. Repeat the process at the
other end of the cable. If the error persists, replace the FRUs in the
Service Action Log (SAL), or serviceable event view you are using.
2. If the connection is optical, clean the connections at both ends of the
cable. See OPT_CLN. If the error persists, replace the FRUs in the
Service Action Log (SAL), serviceable event view you are using.
3. If the error persists, replace the FRUs at each end of the cable starting
with the FROM FRU listed in the serviceable event view you are
using.
v If there was no cable in the Service Action Log (SAL), or serviceable
event view you are using, then replace the FRUs listed in the serviceable
event view.
6990 Service processor failure SVCPROC

The FRU list displayed in the Service Action Log (SAL), or serviceable
event view you are working with, may vary from the failing item list given
in this document. Use the FRU list in the serviceable event view if it is
available to you.
6991 to 6992 Service processor failure AJDGP01
6993 Service processor failure SVCPROC
AJDGP01
A failure occurred with the service processor hardware or the service
processor LIC.

208 System i® and System p®: Reference codes

A6xx, B6xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
6994 Service processor failure SVCPROC

The FRU list displayed in the Service Action Log (SAL) or serviceable event
view you are working with, may vary from the failing item list given in
this document. Use the FRU list in the serviceable event view if it is
available to you.
699C Wrap plug is installed on Bus Expansion Adapter card

This reference code is for information only. It indicates the presence of a

wrap plug on the local optical link card.
69A8 Informational bus reference code

This reference code is for information only and might include the
following:
v Optical speed encode
v Broken optical links now operational
v Other information
69B8 Bus hardware configuration problem Contact your next level of support. FI00187
AJDG301
69C1 A failure occurred on another system Contact your next level of support. FI01040
FI00206
FI00182
AJDG301
69C2 Information only, no service action required. HSL OptiConnect normal
connection to another system or partition.

This reference code is informational only.

HSL OptiConnect has established connection normally. The local system or

partition is participating in HSL Opticonnect with other systems or
partitions on the same HSL loop.
69C3 Information only, no service action required. Opticonnect normal remote
disconnection from OptiConnect participation.

This reference code is informational only.

HSL Opticonnect disconnected normally from a remote node. The local

system or partition has stopped participating in HSL Opticonnect with the
remote system or partition on the same HSL loop. Possible reasons include:
v A remote system or partition went off line due to a normal power off or
disable of HSL Opticonnect.
69C5 I/O processor failure Contact your next level of support. FI00206
FI01040
AJDG301

Reference codes 209

A6xx, B6xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
69C6 Abnormal or unexpected HSL OptiConnect disconnection from a remote REM_SYS
system or partition.

The local system or partition disconnected from a remote system or

partition due to an unexpected event or failure. The problem is most likely
with the remote system or partition. Intervention at the remote system is
most likely required. Examine both the local and remote HSL
OptiConnected systems or partitions for problems on this HSL loop.

disconnected. The system must be re-IPL’d to recover. Before re-IPL’ing the
system initiate a main store dump.

After getting the dump, examine the Service Action Log (SAL), or
serviceable event view you are using, on the local system or partition for
HSL Opticonnect failures that occurred at approximately the same time this
error occurred.

Examine the remote systems or partitions for problems. Examine the

Service Action Log (SAL), or serviceable event view you are using, on the
remote systems or partitions for HSL Opticonnect problems that occurred
at approximately the same time this error occurred.

Collect all the Product Activity Log information for this failure on all
systems and partitions on this HSL loop. Be sure to record all words in the
SRCs. Contact your next level of support with the information you have
collected.
69D0 Bus Expansion Adapter card failed Contact your next level of support. FI00182
FI00055
AJDG301
69D8 Bus Expansion Adapter failed Contact your next level of support. FI00182
FI00203
FI00055
LBUSADP
AJDG301
69D9 Host Ethernet Adapter (HEA) failure HEA

Firmware detected a hardware failure in the Host Ethernet Adapter (HEA).

69DA System log entry only, no service action required
69DB LIC failure SVCDOCS

A Licensed Internal Code error occurred. The partition will continue to run
with this Host Ethernet Adapter (HEA) disabled. Perform a partition dump
and then IPL the partition to recover the HEA. Send the partition dump to
your next level of support.
69DC The HEA is not connected to the Ethernet switch

The Host Ethernet Adapter (HEA) is not connected to the Ethernet switch.
If the HEA connection is not needed, no service action is required.

If the HEA connection is needed, verify that the cable is connected and the
switch is powered on. After repairing the problem, verify that the
connection has been restored.
69DD The HEA connection to the Ethernet switch has been restored

System log entry only, no service action required.

69DE HEA Media Interface Adapter Failure HEA
AJDG301
Firmware detected a failure in the HEA Media Interface Adapter.
69E0 Bus Expansion Adapter card failed FI00203
AJDG301
Contact your next level of support.

Reference codes 213

A6xx, B6xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
69E8 Bus Expansion Adapter failed Contact your next level of support. FI00203
FI00205
FI00057
AJDG301
69F0 Bus Expansion Adapter failed Contact your next level of support. FI00180
FI00182
FI00203
FI00056
FI00205
LBUSADP
AJDG301
69F8 Bus Expansion Adapter failed Contact your next level of support. FI00180
FI00203
FI00182
FI00186
FI00057
AJDG301
7001 ISDN call in rejected GG4COMM
7002 Lines not selected GG4COMM
7003 Network interfaces not selected GG4COMM
7004 TCP/IP informational error

This reference code is logged when the TCP/IP Attribute “Log Protocol
Errors” is set, and the TCP/IP System LIC “silently discards” an inbound
datagram. “Silently discard” is defined to mean discard the received
datagram without reporting an error to the originating host device.
Examples of such datagrams are those with checksums or destination
addresses which are not valid.

This reference code is for information only. Normally no action should be

taken as a result of this reference code. It is generated in order to assist
with remote device or TCP/IP network problem determination.
7055 Statistics were logged, no service action required

This reference code is logged for information only.

7100 APPN session initiation attempt has timed out AJDG301
GG4PL03
This reference code is used to indicate that LIC timed out on a request to GG4PL01
initiate a session. GG4PL02

The user must run problem analysis for this reference code. If this indicates
a software problem, the user should dial IBM Software Support for
assistance.

The Problem Determination Procedure (PDP) will indicate whether the

original timeout condition still exists and what the corrective actions
should be.

214 System i® and System p®: Reference codes

A6xx, B6xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
7101 APPN session initiation attempt has failed GG4PL04
GG4PL05
This reference code is used to indicate that LIC attempted to satisfy a GG4PL06
session initiation request, but some failure condition was detected by LIC. AJDG301
The failure condition could be a configuration or operational problem in
the network.

The user must run problem analysis for this reference code. If this indicates
a software problem, the user should dial IBM Software Support for
assistance.

The Problem Determination Procedure (PDP) will indicate whether the

original timeout condition still exists and what the corrective actions
should be.
7102 APPN CP-CP session ended.
7201 A utility failure occurred.

This reference code is for information only. The Uninterruptible Power

System (UPS) is reporting a utility failure.
7202 Utility power restored.

This reference code is for information only. The Uninterruptible Power

System (UPS) is reporting that utility power has been restored.
7203 A battery low condition was detected.

This reference code is for information only. The Uninterruptible Power

System (UPS) is reporting a battery low condition.
7204 Uninterruptible Power System reported a bypass active

This reference code is for information only. The Uninterruptible Power

System (UPS) is reporting a bypass is active.
7205 Battery low condition was reset.

This reference code is for information only. The Uninterruptible Power

System (UPS) is no longer reporting a battery low condition.
7206 UPS reported bypass no longer active

This reference code is for information only. The Uninterruptible Power

System (UPS) is no longer reporting a bypass active condition.
7207 Battery Power Unit needs service FI00315

The replacement period for BPU 1, installed in the System Unit, has been
exceeded.
7208 Battery Power Unit needs service FI00315

The replacement period for BPU 2, installed in the System Unit, has been
exceeded.
7209 Battery Power Unit needs service FI00315

The replacement period for BPU 1, installed in the Expansion Unit, has
been exceeded.
720A Battery Power Unit replacement dates do not match

The replacement dates for one of the Battery Power Units do not match.
Run ″Display Hardware Configuration″ and verify that the dates match the
labels on the batteries.

Reference codes 215

A6xx, B6xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
7701 SCSI jumper card was not detected. 21H7625
BACKPLN
7702 Incorrect SCSI jumper card detected 21H7625
7703 System LIC detected a program exception

Storage Management detected a DASD datacheck condition and the

defective sector was reallocated.

Perform a system IPL to restart the system.

7704 General failure detected by HRI component. AJDG301
7777 Hardware configuration change detected

A hardware resource is missing. The resource reported in to the system on

a previous IPL, but has not reported in on the current IPL. This could
occur for several different reasons.
1. It could be a normal situation where the resource is currently powered
off. In this case, when the resource is powered back on, it will no longer
be missing.
2. The hardware resource could also be missing if it has been removed
from the system, for example, a tape drive that was replaced with a
different tape drive. The service representative should use the
Hardware service manager to remove the entry for this resource.
3. The resource may not have reported in on this IPL because it is failing.
Perform problem analysis to determine why the resource is failing.
8000 An external storage subsystem disk unit connection failed

Look for other errors in the Service Action Log (SAL), or serviceable event
view you are working with, and fix them.
8001 An external storage subsystem disk unit connection failed

Look for other errors in the Service Action Log, or serviceable event view
you are working with, and fix them.
8002 Maximum number of redundant connections exceeded

An attempt to activate a connection from another I/O adapter to an

external storage subsystem disk unit failed because the maximum number
of connections are already active for this disk unit. No action required.
8003 External storage subsystem disk unit connection was restored

No action required.
8004 An external storage subsystem disk unit connection failed

Could not read configuration information from the disk unit. Look for
other errors in the Service Action Log, or serviceable event view you are
working with, and fix them.
8005 High performance connection failed

A high performance connection to an external storage subsystem disk unit

failed.

There are still two or more external storage subsystem disk unit
connections, but performance might be degraded.

Look for other errors in the Service Action Log, or serviceable event view
you are working with, and fix them.

216 System i® and System p®: Reference codes

A6xx, B6xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
8006 High performance connection failed

A high performance connection to an external storage subsystem disk unit

failed.

There is still one more external storage subsystem disk unit connection, but
performance might be degraded.

Look for other errors in the Service Action Log, or serviceable event view
you are working with, and fix them.
8007 High performance connection was restored

A high performance connection to an external storage subsystem disk unit

was restored.

Performance is no longer degraded.

No action required.
CF00 Permanent error on optical device. SVCDOCS

A type D IPL terminated because of an optical load source device failure. If

the optical load source is an external optical device, check the cables. If that
does not correct the problem, replace the optical device. If the optical load
source is an internal optical device, replace the optical device. If the optical
load source is a virtual device, ensure it is set up correctly.
CFFC Optical library device condition not expected OPTLCBL
DRVSWCH
The optical disk drive addressing within the optical library is incorrect.
This error is likely to be the result of faulty cabling or switch setting
following service to an optical library.

Contact your hardware service provider.

CFFD Optical drive failure OPTLDRV
CFFF Media determined to be bad in Optical library
F103 Main storage dump must be copied for service.

Perform LICIP01.
F104 Logical partition service function Main Storage Dump.

The hypervisor terminated a partition with an unresponsive Operating

System. A Main Store Dump must be done for service. Call your next level
of support when the dump is complete.

Perform LICIP01.
F105 Licensed Internal Code detected error NEXTLVL
FDC0 LIC program reported informational error

This reference code is logged for information only. No action required.

FDC5 LIC program failed and data was captured GG4FFDC

This reference code indicates first failure data capture (FFDC) data was
collected for a problem reported by licensed internal code.

The user should dial IBM Software Support for assistance.

Table 3. Licensed Internal Code failing items details

Reference codes 217

A6xx, B6xx

Failing Item Description Document Description

21H7625 Incorrect, defective or missing SCSI jumper card Repair and Parts; removal and installation
procedures
AJDG301 Licensed Internal Code Service Functions; APAR or LICTR
AJDGP01 Service Processor LIC Repair and Parts; removal and installation
procedures
AJGLD01 I/O card Licensed Internal Code Service Functions; APAR or LICTR
BACKPLN Card enclosure or backplane See the service documentation for instructions.
BRDGSET PCI Bridge set, Multi-adapter bridge domain See the service documentation for instructions.
cards
BSTWRPL FC 9074, FC 9079 Base I/O tower card with See the service documentation for instructions.
service processor
CBLALL SPCN cable to HSL connected I/O tower See the service documentation for instructions.
CTLPNCD System Unit Control Panel Card Assembly See the service documentation for instructions.
CVTCARD HSL (SI) I/O Adapter for FC 5076 SPD migrated See the service documentation for instructions.
tower
DEVTERM Terminating plug See the service documentation for instructions.
DISKDRV Disk Drive and Logic Card See the service documentation for instructions.
DISKTRY Disk unit tray See the service documentation for instructions.
DRVSWCH Drive address switch See the service documentation for instructions.
GG4COMM Communications failure
GG4FFDC LIC program failed and data was captured
GG4PL01 System performance problem
GG4PL02 Network performance problem
GG4PL03 Switched link activation failure message not
answered
GG4PL04 Transmission groups in the network must be
activated
GG4PL05 Class-of-service specified does not provide a
route
GG4PL06 COS acceptable TGs and nodes do not exist for
the route
HEA Host Ethernet Adapter See the service documentation for instructions.
HSL_LNK HSL (SI) cable or connection or interposer See the service documentation for instructions.
LBUSADP SPD local bus adapter, where optical daughters See the service documentation for instructions.
plug
LICIP16 LIC Isolation Procedure Service Functions; APAR or LICTR
LOC_SYS Local HSL Opticonnect system or partition. Local HSL OptiConnect system
LPARCFG ″LPARCFG″ LPAR configuration - processors, See the service documentation for instructions.
memory or ld src
LPARSUP ″LPARSUP″ LPAR complex problem, call next See the service documentation for instructions.
level of support.
MABRCFG Multi-adapter bridge configuration error or See the service documentation for instructions.
change
MASBUS Multi-adapter bridge secondary bus or card slot See the service documentation for instructions.
MA_BRDG Multi-adapter bridge high level symbolic See the service documentation for instructions.

218 System i® and System p®: Reference codes

A6xx, B6xx

Failing Item Description Document Description

NEXTLVL Call your next level of support for assistance Rio PIP 55
OPTDRIV Optical Disk Drive See the service documentation for instructions.
OPTLCBL Optical Library drive cabling See the service documentation for instructions.
OPTLDRV Optical Library optical drive See the service documentation for instructions.
OPT_CLN Fiber optic cleaning kit Fiber optic cleaning kit
PIOCARD PCI nodes adapter card, IOP or IOA See the service documentation for instructions.
PLDUMP Platform dump occurred See the service documentation for instructions.
PPCIMIN Primary PCI bus in 5075 I/O tower See the service documentation for instructions.
PPCISYS Primary PCI bus in a system unit See the service documentation for instructions.
PPCITWR Primary PCI bus in a 5074 I/O tower See the service documentation for instructions.
PRI_PCI Primary system PCI bus to a MaB, high level See the service documentation for instructions.
symbolic
REM_NIC A remote NIC in a cluster.
REM_SYS HSL opticonnect remote system or partition. Remote HSL OptiConnect system
SIADPCD High Speed Link (SI) I/O adapter card in FC See the service documentation for instructions.
5074 I/O tower
SICNTRL HSL (SI) controller, high level symbolic See the service documentation for instructions.
SIIOADP High Speed Link (SI) I/O adapter, high level See the service documentation for instructions.
symbolic
SIRGCFG SI ring invalid configuration See the service documentation for instructions.
SIRSTAT System Interconect ring status See the service documentation for instructions.
SI_CARD HSL (SI) controller card on a system unit See the service documentation for instructions.
SI_PHB PCI host bridge adapter, high level symbolic See the service documentation for instructions.
SLOTERR Multi-adapter bridge slot error See the service documentation for instructions.
SPNLCRD SPCN panel card See the service documentation for instructions.
STORIOA Active I/O processor See the service documentation for instructions.
SVCDOCS Customer engineer directed to system problem See the service documentation for instructions.
analysis
SVCDOCS Equipment failure; not isolated Service Functions; APAR or LICTR
SVCPROC Service Processor See the service documentation for instructions.
SYSBKPL System unit backplane See the service documentation for instructions.
TWRBKPL FC 5075 I/O tower backplane See the service documentation for instructions.
TWRCARD SPCN failing component in HSL I/O tower See the service documentation for instructions.
TWRPLNR FC 5074, FC 9074, FC 9079 I/O tower PCI card See the service documentation for instructions.
planar
UG4USR1 Operator response required

(A7xx, B7xx) Licensed Internal Code reference codes

Use this table for A7xx and B7xx reference codes.

Perform the following actions:

1. Find the unit reference code by looking at characters 5 through 8 of the top 16 character line of
function 11 (4 rightmost characters of word 1). These 4 characters are the unit reference code.

Reference codes 219

A7xx, B7xx

2. Look up the unit reference code in the following table.

3. Perform the actions in the Description/Action column of the table.

In all cases, once the failing item is determined, go to the locations table for the system you are working
on to determine the location, and use the remove and replace procedure for the failing item.

Table 1. (A7xx, B7xx) Licensed Internal Code (LIC) Reference Codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
0102 Platform LIC detected an error SVCDOCS

A machine check occurred during IPL. Words 2 to 9 of this SRC contain

additional diagnostic information. Record SRC words 1 through 9 before
attempting to IPL again and report the problem to next level of support.
0103 Platform LIC failure LICCODE

Work with the FRU list in the serviceable event view if there is one,
otherwise use the FRU list documented here to determine the parts to
exchange.

The platform Licensed Internal Code (LIC) detected an internal problem.

Collect all the SRC words and the platform system dump, then contact
your next level of support.
0104 Platform LIC failure LICCODE

Machine check, undefined error occurred.

0105 Platform LIC detected an error NEXTLVL

More than one request to terminate the system was issued.

0106 Platform LIC failure LICCODE

Work with the FRU list in the serviceable event view if there is one,
otherwise use the FRU list documented here to determine the parts to
exchange.

A secondary failure due to an invalid SRC occurred when the platform

attempted to terminate.

Collect all the SRC words and the platform system dump, then contact
your next level of support.
0107 Platform LIC failure SVCDOCS

The server detected an unrecoverable machine check condition. Collect all

the words of the SRC and the platform dump and send to your system
manufacturer for analysis.
0200 System firmware has experienced a low storage condition SVCDOCS

No immediate action is necessary.

Continue running the system normally. At the earliest convenient time or

service window work with your service provider to take a platform dump
and reIPL the system.

220 System i® and System p®: Reference codes

A7xx, B7xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
0302 Platform LIC failure LICCODE

Work with the FRU list in the serviceable event view if there is one,
otherwise use the FRU list documented here to determine the parts to
exchange.

Perform a platform system dump and notify your service provider. IPL the
system.
0441 Service processor failure SVCPROC
NEXTLVL
Work with the FRU list in the serviceable event view if there is one,
otherwise use the FRU list documented here to determine the parts to
exchange.

The platform encountered an error early in the IPL or termination process.

0443 Service processor failure SVCPROC
NEXTLVL
0601 System log entry only, no service action required

Support can use this SRC and associated data to determine why the time of
day for a partition was lost. No corrective action is required.
0602 Platform LIC detected an error NEXTLVL

Work with the FRU list in the serviceable event view if there is one,
otherwise use the FRU list documented here to determine the parts to
exchange.

Platform Licensed Internal Code (LIC) detected an error condition. The

second word indicates the severity of the error and the specific error
condition. If word 2 is 10000A01 then record the SRC words and call your
next level of support; otherwise this does not require service.
0611 System clock problem SVCDOCS

Work with the FRU list in the serviceable event view if there is one,
otherwise use the FRU list documented here to determine the parts to
exchange.

For systems managed by an HMC, use the ASM interface to reset the
system clock at power on standby. For systems without an HMC, you can
ignore this error.

If the error occurs a second time, call your next level of support.
0621 System log entry only, no service action required

No service action required.

0641 Platform LIC detected an error SVCDOCS

A platform LIC failure occurred. Perform a platform dump and contact

your next level of support.

Reference codes 221

A7xx, B7xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
0650 Platform LIC detected an error NEXTLVL

Resource management was unable to allocate main storage. A platform

dump was started.

Words 2 to 9 of this SRC contain additional diagnostic information. Record

SRC words 1 through 9. Collect the platform dump and the configuration
of the memory allocation for all partitions on this system. Provide the
platform dump, configuration data, and the recorded SRC information to
your next level of support.
0651 The system detected an error in the system clock hardware

This is a serviceable event only if this error appears in a serviceable event

view.

If this is a serviceable event, then work with the FRU list in the serviceable
event view if there is one. Otherwise, use the FRU list documented in the
Failing Items column to determine the parts to exchange.

If the system did not log this error as a serviceable event, then no service
action is required.
0803 to 0804 System log entry only, no service action required
0A00 System log entry only, no service action required

A user request initiated an I/O tower/drawer power off. No corrective

action is required.
0A10 System log entry only, no service action required

No action is required, unless the Hardware Management Console (HMC)

indicates that the concurrent platform firmware update failed. In that case,
the system must be re-IPLed in order for the firmware update to occur.
Collect the error log data for this SRC and contact PHYP development to
debug the problem.
1150 to 1151 System log entry only, no service action required

No action needed unless a serviceable event was logged. If a serviceable

event was logged, resolve that error.
1152 System log entry only, no service action required

No service action is required for this event.

If there is a A7001150 src present, then the service processor was reset
automatically to correct for the communications problem. If something
more severe occurred there will be a SRC requiring a service action logged
as well.
1160 Service processor failure SVCPROC
LICCODE
Work with the FRU list in the serviceable event view if there is one,
otherwise use the FRU list documented here to determine the parts to
exchange.

The platform encountered an error communicating with the service

processor. The platform code attempts a graceful shutdown of partitions
and powers off the server after a certain time, or when the last partition
indicates shutdown, whichever comes first.

222 System i® and System p®: Reference codes

A7xx, B7xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
1161 System log entry only, no service action required

The platform encountered a service processor event indicating that the

power status has changed. Note that this is A7xx only.
1730 Platform LIC detected an error CAPACTY

The VPD for the system is not what was expected at IPL.

When word 9 is 00180003, a redundant VPD chip exists, and the system
will continue to run. Replace the VPD card at your next scheduled
maintenance. When word 9 is not 00180003 replace the VPD card
immediately.

Work with the FRU list in the serviceable event view, if there is one.
Otherwise, use the FRU list documented here to determine the parts to
exchange.
1731 Platform LIC detected an error MEMDIMM

The VPD for the system is not what was expected at IPL. The VPD on a
memory DIMM is not correct and the memory on the DIMM cannot be
used, resulting in reduced memory.

Work with the FRU list in the serviceable event view, if there is one.
Otherwise, use the FRU list documented here to determine the parts to
exchange.
1732 Platform LIC detected an error ANYPROC

The VPD for the system is not what was expected at IPL. The VPD on a
processor card is not correct and the processor card cannot be used,
resulting in reduced processing power.

Work with the FRU list in the serviceable event view if there is one.
Otherwise, use the FRU list documented here to determine the parts to
exchange.
1733 Platform LIC detected an error

If required Capacity on Demand functions are not available, re-IPL the

system. Otherwise, no service action is required.
173A System log entry only, no service action required

A VPD collection overflow occurred, no service action required.

If a system problem is suspected, look for other errors in the serviceable

event view.
173B Platform LIC detected an error SVCDOCS

A platform LIC failure occurred during VPD collection.

Look for and correct errors with SRCs of the form B1xxxxxx in the
Serviceable Event View. If that does not correct the problem, contact your
next level of support.

Reference codes 223

A7xx, B7xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
4091 User intervention required

The system power on has reached a standby state. The firmware does not
have partition configuration information.

Use the Hardware Management Console (HMC) to activate one or more

partitions to change the system from a standby state to an operating state.
If the HMC does not manage the server, perform Restoring your server to
factory settings.
4400 There is a platform dump to collect SVCDOCS

Work with the FRU list in the serviceable event view if there is one,
otherwise use the FRU list documented here to determine the parts to
exchange.

Use the operating system’s interface designated to collect platform dumps.

4401 Platform LIC failure NEXTLVL

Work with the FRU list in the serviceable event view if there is one,
otherwise use the FRU list documented here to determine the parts to
exchange.

The platform LIC detected an internal problem.

Contact your next level of support.

4402 Platform LIC failure NEXTLVL

A platform LIC error occurred while attempting to allocate the memory

necessary to create a platform resource dump.
4700 Platform LIC detected an error SVCDOCS
CAPACTY
A problem occurred when initializing, reading, or using system VPD.

Capacity on Demand is not available because the stored activation code is

not valid. Contact your next level of support to verify your activation code.
If the activation code is valid, replace the VPD card.
4701 Platform LIC detected an error CAPACTY

A problem occurred when initializing, reading, or using system VPD. The

IPL failed.

Work with the FRU list in the serviceable event view if there is one,
otherwise use the FRU list documented here to determine the parts to
exchange.
4703 Platform LIC failure LICCODE

A problem occurred when initializing, reading, or using system VPD. The

Capacity on Demand function is not available. If Capacity on Demand
function is required, re-IPL the system. If that does not correct the problem,
contact your next level of support.
4704 Platform LIC detected an error SVCDOCS

The Capacity on Demand function is no longer available. If Capacity on

Demand functions are required, look for and correct errors with SRCs of
the form B1xxxxxx in the Serviceable Event View. If that does not correct
the problem, or no errors were found, contact your next level of support.

224 System i® and System p®: Reference codes

A7xx, B7xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
4705 Platform LIC failure

A problem occurred when initializing, reading, or using system VPD. The

A communications problem with the service processor occurred while

initiating Capacity on Demand. The Capacity on Demand function is not
available.

If Capacity on Demand function is required, look for errors with SRCs of

the form B1xxxxxx or B7xx69xx in the Serviceable Event View. Work those
errors. If that does not correct the problem, contact your next level of
support.
4712 Platform LIC detected the VPD card is missing CAPACTY

A problem occurred when initializing, reading, or using system VPD.

Work with the FRU list in the serviceable event view if there is one,
otherwise use the FRU list documented here to determine the parts to
exchange.
4713 Platform LIC detected an error SVCDOCS

The VPD card has been exchanged with a not valid card. Reinstall the
original VPD card in the system.
4714 Platform LIC has detected a new VPD card SVCDOCS

The new VPD card requires new activation codes. Enter the new activation
codes.
4715 Platform LIC detected an error SVCDOCS
CAPACTY
A problem occurred when initializing, reading, or using system VPD.

Look for errors with SRCs of the form B1xxxxxx in the Serviceable Event
View. Work those errors first. If that does not correct the problem, replace
the VPD card.

Work with the FRU list in the serviceable event view if there is one,
otherwise use the FRU list documented here to determine the parts to
exchange.
4716 User intervention required SVCDOCS
LPARCFG
The Capacity on Demand activation code recovery period has been started.
Either obtain more capacity by obtaining new activation codes or allocate
fewer resources in the LPAR configuration.
4730 Platform LIC detected an error SVCDOCS
LPARCFG
A problem occurred when configuring the logical partitions on the system.
More resources were allocated than there are available for use. Either
obtain more capacity by obtaining new activation codes or allocate fewer
resources in the LPAR configuration.

Reference codes 225

A7xx, B7xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
4731 Platform LIC detected an error SVCDOCS

The system has been running with full Capacity on Demand resources
activated. In one hour, the system will terminate and unlicensed resources
will no longer be available. To prevent the system from terminating, enter
an activation code of all zeroes. Then obtain the proper activation codes for
the resources being used or allocate fewer resources in the LPAR
configuration.
4733 Platform LIC failure

The Capacity on Demand function is not available. If Capacity on Demand

function is required, re-IPL the system. If that does not correct the problem,
contact your next level of support.
4740 Platform LIC detected an error

An incorrect activation code has been detected. Resources associated with

this activation code have been disabled. Enter a valid activation code.
4741 Platform LIC detected an error

The number of allowable attempts to enter a valid activation code has been
exceeded. The system will continue to run, but a system IPL is required in
order to retry entering a valid activation code.
4742 Platform LIC detected an error SVCDOCS

A communications problem with the service processor occurred. No

Capacity on Demand changes can be made, but you can continue to run
with the current Capacity on Demand resources.

Look for errors with SRCs of the form B1xxxxxx or B7xx69xx in the
Serviceable Event View. Work those errors first. If that does not correct the
problem, re-IPL the system. If that does not correct the problem, contact
your next level of support.
4747 User intervention required SVCDOCS

One hour remains until the On/Off Capacity on Demand request expires.
Permanently activate the temporary Capacity on Demand resources, enter a
new On/Off Capacity on Demand request for the temporary resources, or
remove all temporary resources from partitions before the request expires.
4748 User intervention required SVCDOCS

One hour remains until the Reserve Capacity on Demand request expires.
In order to reactivate temporary resources, a new Reserve Capacity on
Demand enablement code is required.
4749 User intervention required SVCDOCS

One hour remains until the Trial Customer on Demand activation expires.
Obtain a permanent activation code or remove all temporary resources
from partitions before the request expires.
4750 A Capacity on Demand change has been detected

A Reserve Capacity on Demand resource has been activated.

4788 System log entry only, no service action required

The data obtained from the system is not what was expected. The IPL will
continue. Should other errors occur, contact your next level of support.

226 System i® and System p®: Reference codes

A7xx, B7xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
47C1 Capacity on Demand data mismatch

The data obtained from the system is not what was expected. The system
will perform a slow IPL in order to obtain the correct data. If other errors
occur, contact your next level of support.
47CB Fast system IPL changed to slow system IPL

The server detected a not valid Capacity On Demand activation and

terminated the system. The allocated resources for the system might exceed
those that are available for use.
47FF System log entry only, no service action required

The Capacity on Demand History Log has been written to the error log. No
service action is required.
5120 Platform LIC detected an error NEXTLVL

Work with the FRU list in the serviceable event view if there is one,
otherwise use the FRU list documented here to determine the parts to
exchange.

If the system is not exhibiting problematic behavior, this error may safely
be ignored. Otherwise, contact your next level of support.
5121 Platform LIC failure NEXTLVL

Licensed Internal Code program exception occurred.

Platform Licensed Internal Code detected a programming problem for

which a platform dump may have been initiated.

Send the system error log and the platform dump, if it occurred, to your
next level of support.
5122 Platform LIC detected an error SVCDOCS

Platform Licensed Internal Code detected that an IOP request failed.

This error indicates a failure during a search for the load source. There may
be a number of these failure prior to finding a good load source. This is
normal. If a B2xx3110 error is logged, a B2xx3200 or B7005122 may be
posted to the control panel. Work the B2xx3110 error in the Serviceable
Event View. If the system IPL hangs at B2xx3200 or B7005122 and you
cannot check the SRC history, perform the actions indicated for the
B2xx3110 SRC.
5123 Platform LIC detected an error

A Licensed Internal Code program exception or data collection occurred.

This may indicate an IOP programming problem or an IO Adapter boot
problem. Look for other errors. If no other errors are present, Licensed
Internal Code has recovered from any exception conditions, or this SRC has
logged informational platform boto or hardware data.

Reference codes 227

A7xx, B7xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
5190 Operating System error SVCDOCS

Work with the FRU list in the serviceable event view if there is one,
otherwise use the FRU list documented here to determine the parts to
exchange.

The platform detected a problem in an Operating System. Check for errors

in the partition ID specified in word 4 of the SRC. If correcting those errors
does not correct the problem, or if you find no errors, contact your next
level of support.
5191 Platform LIC detected an error SVCDOCS
LICCODE
A virtual adapter configuration error occurred.

A partition tried to use a virtual adapter which is associated with another

virtual adapter in a remote partition and virtual slot. However, either no
virtual adapter is configured there, or the wrong kind of virtual adapter is
configured there.

The partition ID of the virtual adapter with the problem is in word 4 of the
SRC (in hexadecimal format). The virtual slot number of the adapter with
the incorrect configuration is the last four digits of word 6 of the SRC (in
hexadecimal format).

Use the Hardware Management Console (HMC) to verify or reconfigure

the incorrect virtual adapter configuration. If the configuration is correct,
continue with the next failing item in the list.
5209 Platform LIC detected an error

System Licensed Internal Code detected an IOP timeout during IOP IPL.

This may be caused by loose connections, improperly seated cards, media,

or removeable media drive not in a ready state. Look for other errors.
5219 Platform LIC detected an error

Information only, no service action required.

Licensed Internal Code program exception occurred.

An IOP signalled to system Licensed Internal Code that it had entered a

critical internal state. Licensed Internal Code automatically attempted to
restart the IOP.
5300 Platform LIC detected a failure while partitioning resources

Work with the FRU list in the serviceable event view if there is one,
otherwise use the FRU list documented here to determine the parts to
exchange.

Platform partitioning code encountered an error. This SRC represents a

large number of possible problems, most of which involve the platform
Licensed Internal Code (LIC).

Work any error logs found in the Serviceable Event View. If this fails to
correct the problem, or if there are no other errors, contact your next level
of support.

228 System i® and System p®: Reference codes

A7xx, B7xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
5301 User intervention required SVCDOCS

System detected a problem with the Logical Partition (LPAR)

Configuration.

Use the Hardware Management Console to reconfigure the LPAR

configuration.

Check Hardware Management Console (HMC) partition state.

1. If in Recovery state then use the HMC to perform ″Recovering partition
data on a managed system″.
2. Use HMC to activate partitions.
5400 A resource has been disabled due to hardware problems SVCDOCS

Work with the FRU list in the serviceable event view if there is one,
otherwise use the FRU list documented here to determine the parts to
exchange.

The platform detected a problem with a processor. The processor is not

functional.

Look in the Serviceable Event View for a B1xx xxxx error that implicates a
processor.

If the Serviceable Event View contains no B1xx xxxx error, or if resolving

the error fails to correct the problem, contact your next level of support.
5600 Problem initializing, reading or using system VPD

Look for other errors in the Serviceable Event View. If no other errors have
been logged, contact your next level of support.
5601 Platform LIC failure NEXTLVL

Work with the FRU list in the serviceable event view if there is one,
otherwise use the FRU list documented here to determine the parts to
exchange.

There was a problem initializing, reading, or using system VPD.

6900 PCI host bridge failure PRIPCI
MA_BRDG
If you find a B7006981 SRC logged at about same time and listing parts MABIP50
from same enclosure as one of the FRUs here, then close this problem and PIOCARD
work the B7006981 SRC.

Work with the FRU list in the serviceable event view, if there is one.
Otherwise, use the FRU list documented here to determine the parts to
exchange.

If the Serviceable Event View is not available, use the failing item list
presented here for servicing this reference code.
6906 System bus error SIIOADP

Work with the FRU list in the serviceable event view if there is one,
otherwise use the FRU list documented here to determine the parts to
exchange.

Reference codes 229

A7xx, B7xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
6907 System bus error SIIOADP
LICCODE
If this event appears in a serviceable event view, work with the failing item
list found there. If this event does not appear in a serviceable event view,
no service action is required.
6908 System bus error SIIOADP
MA_BRDG
Work with the FRU list in the serviceable event view if there is one,
otherwise use the FRU list documented here to determine the parts to
exchange.
6909 System bus error SIIOADP
MA_BRDG
Work with the FRU list in the serviceable event view if there is one, LICCODE
otherwise use the FRU list documented here to determine the parts to
exchange.
6944 Platform LIC detected an error

A system bus appears to be empty. If the bus is not empty, a hardware or

configuration problem might exist. Look for other errors.
6950 Platform LIC detected an error SVCDOCS

A platform dump has occurred. The system has lost all the configured
system settings (such as the HMC access and ASMI passwords, time of day,
network configuration, hardware deconfiguration policies, etc.) that you
might have set through user interfaces. Also, the system has lost the
platform error logs and partition-related information, and the service
processor is reset. Perform the recovery actions for the SVCPROC FRU but
do not replace the service processor. The platform dump should be sent to
your service provider.
6951 Platform LIC detected an error SVCDOCS

An error occurred because a partition needed more NVRAM than was

available.

The partition is still functional, but is operating in a degraded mode.

Configuration information may be lost at the next IPL. In order to make
more NVRAM available, delete one or more partitions.
6965 Platform LIC detected an error

Unknown hardware detected. Look for other errors.

6970 PCI host bridge failure PRIPCI
MA_BRDG
If this event does not appear in a serviceable event view, no service action MABIP50
is required. PIOCARD

If this event appears in a serviceable event view, and if you find a

B7006981 SRC logged at about the same time and listing parts from the
same enclosure as one of the FRUs listed in the serviceable event view for
B7006970, then close this problem and work the B7006981 SRC. Otherwise,
work on the B7006970 SRC.
6971 PCI secondary bus failure MABIP51
PIOCARD
If this event appears in a serviceable event view, work with the failing item MASBUS
list found there. If this event does not appear in a serviceable event view, MA_BRDG
no service action is required.

230 System i® and System p®: Reference codes

A7xx, B7xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
6972 System bus error MA_BRDG
PRIPCI
Work with the FRU list in the serviceable event view if there is one,
otherwise use the FRU list documented here to determine the parts to
exchange.
6973 System bus error PIOCARD
MA_BRDG
If you find a B7006981 SRC logged on the same expansion unit as one of SVCPROC
the FRUs here, then close this problem and work the B7006981 SRC. Use PRIPCI
the unit value of the location codes to determine if the expansion unit is MASBUS
the same.

Work with the FRU list in the serviceable event view, if there is one.
Otherwise, use the FRU list documented here to determine the parts to
exchange.

If the first half of word 7 is not 0001, remove SVCPROC (the service
processor) from the list of possible FRUs.
6974 IOP rejected the assignment of an IOA

An I/O Processor rejected the assignment of an I/O Adapter during the

IPL of an i5/OS partition.

If the partition IPLed successfully, this event is logged for information only.
No service action is required.

If the partition failed to IPL, replace the IOA. If that does not resolve the
problem, replace the IOP that controls the IOA.

The Direct Select Address (DSA) of the IOA is in word 7 of the SRC. In
order to find the location of the IOA, see DSA translation to get the unit
type in which the IOA is located. Then, using the DSA and unit type, go to
Card positions to find the location of the IOA.
6980 Network Interface Controller (NIC) resource failure SICNTRL
LICCODE
If the serviceable event view contains a FRU list, work with those FRUs. OPT_CLN
Otherwise, exchange the failing items listed here.

NOTE: A fiber optic cleaning kit may be required for optical HSL
connections.

A platform dump has occurred. Send the dump to your service provider.
6981 High Speed Link (HSL) I/O bridge failure SIIOADP

If you find a 1xxx SRC logged on the same expansion unit as one of the
FRUs here, then close this problem and work the 1xxx SRC. Use the unit
value of the location codes to determine if the expansion unit is the same.

Work with the FRU list in the serviceable event view, if there is one.
Otherwise, use the FRU list documented here to determine the parts to
exchange.
6982 High Speed Link (HSL) connection failure RIOIP11
HSL_LNK
Work with the FRU list in the serviceable event view if there is one, OPT_CLN
otherwise use the FRU list documented here to determine the parts to FRPORT
exchange. TOPORT
NOTE: A fiber optic cleaning kit may be required for optical HSL
connections.

Reference codes 231

A7xx, B7xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
6983 An invalid High Speed Link (HSL) configuration was detected SVCDOCS

Work with the FRU list in the serviceable event view if there is one,
otherwise use the FRU list documented here to determine the parts to
exchange.

The four rightmost characters of word 4 in the reference code represent the
Program Return Code (PRC), which describes the problem detected. The
four leftmost digits of word 7 represent the loop number in hexadecimal
format. Convert the loop number to decimal format before comparing it to
loop numbers shown in serviceable event views and service tools.

To determine the problem, find the PRC in the list below.

Note: The FRU description in the serviceable event view may already
contain a message that identifies the problem.
v xxxx 0000 indicates bus numbers were not assigned. Contact your next
level of support.
v xxxx 0008 indicates the system serial number is not set. Set the serial
number on the system unit. If the problem persists contact your next
level of support.
v xxxx 029A indicates an unsupported I/O tower hardware level. Upgrade
the tower hardware to a supported level.
v xxxx 3201 indicates there are HSL OptiConnect clustered systems on
both HSL/RIO loops on the same adapter. You will need to ensure that
only one HSL/RIO loop per adapter is used for HSL OptiConnect.
v xxxx 3211 indicates two or more HSL adapters are connected to each
other on the same system unit. This is not a supported configuration.
Re-cable the system so that it has a supported configuration.
v xxxx 3212 indicates the HSL adapter hardware level does not support
HSL OptiConnect. Upgrade your HSL adapter hardware to a supported
level for HSL OptiConnect.
v xxxx 3213 indicates that the switchable tower configuration is not valid.
Re-cable your HSL OptiConnect so that it has a supported configuration.
v xxxx 3217 indicates there is a model 5791, 5792, or 5794 IO drawer on a
loop with clustered systems. This is not a supported configuration.
v xxxx 3218 indicates a concurrent tower add is not allowed due to an
incomplete loop. Look for and resolve errors on the loop.

This ends the procedure.

6984 System log entry only, no service action required

An HSL loop has switched to its alternate path. This is an informational

SRC only.

This SRC can be caused by a tower on the HSL loop powering off.

This SRC may also appear in a Serviceable Event View you are using, with
a B700 6982 or B700 6981 logged at approximately the same time. In that
case the other SRC is reporting a failure and this SRC is reporting that the
alternate RIO path is now being used. Service the other SRC if present.

232 System i® and System p®: Reference codes

A7xx, B7xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
6985 High Speed Link (HSL) loop status message SVCDOCS
HSL_LNK
This is a serviceable event only if this error is in a serviceable event view. If OPT_CLN
this is a serviceable event then perform RIOIP12. Otherwise if this is NOT FRPORT
a serviceable event then to determine what this SRC means use symbolic TOPORT
FRU SIRSTAT.

Work with the FRU list in the serviceable event view if there is one,
otherwise use the FRU list documented here to determine the parts to
exchange.

NOTE: A fiber optic cleaning kit may be required for optical HSL
connections.
6986 System bus error TWRCARD
PWRCBL
Work with the FRU list in the serviceable event view if there is one,
otherwise use the FRU list documented here to determine the parts to
exchange.

If the Serviceable Event View is not available then use the failing item list
presented here for servicing this reference code.
6987 High Speed Link (HSL) connection failure HSL_LNK
OPT_CLN
Work with the FRU list in the serviceable event view if there is one,
otherwise use the FRU list documented here to determine the parts to
exchange.

If the Serviceable Event View is not available then use the failing item list
presented here for servicing this reference code.
6990 Service processor failure SVCPROC

Work with the FRU list in the serviceable event view if there is one,
otherwise use the FRU list documented here to determine the parts to
exchange.

If the Serviceable Event View is not available then use the failing item list
presented here for servicing this reference code.
6991 Platform LIC failure LICCODE

Work with the FRU list in the serviceable event view if there is one,
otherwise use the FRU list documented here to determine the parts to
exchange.

Reference codes 233

A7xx, B7xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
6992 Service processor reset occurred SVCDOCS

If this SRC does not appear in a serviceable event view then no service
action is required. The service processor reset was successful.

If this SRC appears in a serviceable event view, the service processor reset
failed. The system will continue to run if a redundant service processor
was available. If a redundant service processor was not available, the
system terminated.

Look for and correct errors with SRCs of the form B1xx xxxx in the
Serviceable Event View that were logged within approximately one hour of
the time this SRC occurred.

If there are no B1xx xxxx SRCs, or they do not resolve the problem, do the
following:

If there is only one service processor, replace it. Ensure that the firmware is
at the most recent code level.

If there is more than one service processor, use the Advanced Server
Management Interface (ASMI) to find the Garded service processor (the
one currently not being used) and replace it. Ensure that the firmware is at
the most recent code level.
6993 Service processor failure SVCPROC
LICCODE
Work with the FRU list in the serviceable event view if there is one,
otherwise use the FRU list documented here to determine the parts to
exchange.

If the Serviceable Event View is not available then use the failing item list
presented here for servicing this reference code.
6994 Service processor failure SVCPROC

Work with the FRU list in the serviceable event view if there is one,
otherwise use the FRU list documented here to determine the parts to
exchange.

If the Serviceable Event View is not available then use the failing item list
presented here for servicing this reference code.
6995 User intervention required

The system is in the process of terminating.

When all the partitions have terminated, an SRC indicating the exact cause
will be shown on the operator panel.

If the system does not terminate in a reasonable amount of time, one or

more partitions may need to be terminated manually. If this is not possible,
re-IPL the system and look for errors. If no errors are found, contact your
next level of support.
69C2 System log entry only, no service action required

Information only, no service action required.

HSL OptiConnect normal connection to another system or partition.

HSL OptiConnect established connection normally. The local system or

partition is participating in HSL Opticonnect with other systems or
partitions on the same HSL loop.

234 System i® and System p®: Reference codes

A7xx, B7xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
69C3 System log entry only, no service action required

Information only, no service action required.

Opticonnect normal remote disconnection from OptiConnect participation.

HSL Opticonnect disconnected normally from a remote node. The local

system or partition has stopped participating in HSL Opticonnect with the
remote system or partition on the same HSL loop. Possible reasons include:
v A remote system or partition went off line due to a normal power off or
because HSL Opticonnect became disabled.
69C6 Platform LIC detected an error SVCDOCS
LICCODE
Abnormal or unexpected HSL OptiConnect disconnection from a remote
system or partition.

The local system or partition disconnected from a remote system or

partition due to an unexpected event or failure. The problem, which most
likely originates with the remote system or partition, probably requires
intervention at the remote system. Examine both the local and remote HSL
OptiConnected systems or partitions for problems on this HSL loop.

Possible reasons include: A fatal software or hardware error in the remote

system or partition, or a power failure in the remote system.

If a complete HSL loop did not exist before this error occurred, the cause of
this error might be a failure or power down in an HSL component between
the local system or partition and the remote system or partition. Check for
a problem with the following:
v An HSL cable
v The HSL I/O bridge
v Power in an expansion I/O tower or unit on this loop

On the local system or partition, examine the Service Action Log (SAL) or
serviceable event view. Look for HSL failures that occurred on the same
HSL loop at approximately the same time as this error.

Examine the remote system or partition for problems. If the remote system
or partition is powered on and IPL’d, examine the SAL or serviceable event
view on the remote system or partition. Look for problems on the same
HSL loop that occurred at approximately the same time as this error.

When the remote system is IPL’d, it will automatically reconnect with this
system or partition. If you find no problems with either the local or the
remote systems or partitions, collect all the Product Activity Log (PAL)
information for this failure on both systems. Be sure to record all words in
the SRC. Contact your next level of support.

Reference codes 235

A7xx, B7xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
69C7 Platform LIC detected an error SVCDOCS
LICCODE
Abnormal or unexpected HSL OptiConnect disconnection from a remote
system or partition.

The local system or partition disconnected from a remote system or

partition due to an unexpected event or failure. Licensed Internal Code will
attempt to recover from the error. Intervention at the local or remote
system or partition might be required.

Possible causes include time out, hang, or hardware failure. The problem
may be with the local system or partition or the remote system or partition.
If a complete HSL loop did not exist before this error occurred, the cause of
this error might be a failure or power down in an HSL component between
the local system or partition and the remote system or partition. Check for
SRCs with FRUs that indicate problems with the following:
v HSL cables
v The HSL I/O bridge
v Power in an expansion I/O tower or unit on this loop

On the local system or partition, examine the SAL or serviceable event

view. Look for failures on the same loop or with the Network Interface
Controller that occurred at approximately the same time as this error.

Examine the remote system or partition for problems. Correct any HSL or
NIC problems you find with the remote and local systems or partitions. If
you find no problems with either the local or the remote systems or
partitions, collect all the PAL information for this failure on both systems.
Be sure to record all words in the SRC. Contact your next level of support.

236 System i® and System p®: Reference codes

A7xx, B7xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
69C8 Platform LIC detected an error SVCDOCS
LICCODE
Abnormal or unexpected HSL OptiConnect disconnection from a remote
system or partition.

The local system or partition disconnected from a remote system or

partition due to an unexpected event or failure. All of the HSL OptiConnect
connections on this loop will be in a failed state. Licensed Internal Code
will attempt to recover from the error. Intervention at the local or remote
system or partition might be required. Possible causes are:
v Time out of a critical message
v Licensed Internal Code code / table problem
v Network deadlock detected
The problem may be with:
v The local system or partition
v The remote system or partition

On the local system or partition, examine the SAL or serviceable event

view. Look for HSL failures on the same HSL loop or with the Network
Interface Controller that occurred at approximately the same time as this
error.

Examine the remote system or partition for problems. On the remote

system or partition, examine the SAL or serviceable event view. Look for
problems on the same HSL loop or with the Network Interface Controller
that occurred at approximately the same time as this error.

Reference codes 237

A7xx, B7xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
69C9 Platform LIC detected an error SVCDOCS
LICCODE
Abnormal or unexpected HSL OptiConnect disconnection from a remote
system or partition.

The local system or partition disconnected from a remote system or

partition due to an failure in a Licensed Internal Code virtualized bus unit.
Licensed Internal Code will attempt to recover from the error. Possible
causes are:
v Licensed Internal Code problem where the local bus unit is offline.
v Licensed Internal Code problem where the remote bus unit is offline.

On the local system or partition, examine the SAL or the serviceable event
view. Look for HSL Opticonnect failures that occurred at approximately the
same time as this error.

Examine the remote system or partition for problems. On the remote

system or partition, examine the SAL or the serviceable event view. Look
for HSL Opticonnect problems that occurred at approximately the same
time as this error.

Collect all the Product Activity Log information for this failure on all
systems and partitions on this HSL loop. Be sure to record all words in the
SRCs. Contact your next level of support.
69CF Platform LIC detected an error SVCDOCS
LICCODE
Abnormal or unexpected HSL OptiConnect disconnection from a remote
system or partition.

Licensed Internal Code internal error. All systems participating in HSL

OptiConnect will be disconnected. You must re-IPL the system to recover.
Before re-IPL’ing the system, start a platform dump.

On the local system or partition, after getting the dump, examine the SAL
or the serviceable event view. Look for HSL Opticonnect failures that
occurred at approximately the same time as this error.

Examine the remote systems or partitions for problems. On the remote

systems or partitions, examine the SAL or the serviceable event view. Look
for HSL Opticonnect problems that occurred at approximately the same
time as this error.

Collect all the PAL information for this failure on all systems and partitions
on this HSL loop. Be sure to record all words in the SRCs. Contact your
next level of support.
69E1 Host Channel Adapter HCA

The 12X Host Channel Adapter has failed.

69E2 Platform LIC failure LICCODE

A Platform Licensed Internal Code error occurred related to 12X

technology. The system will continue to run with this Host Channel
Adapter disabled. Perform a platform dump prior to IPLing the system. An
IPL is required to recover the Host Channel Adapter.
69E3 System log entry only, no service action required

Part of the HCA chip failed but was not terminating. When thresholded,
these errors will result in a B70069E1.

238 System i® and System p®: Reference codes

A7xx, B7xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
69E4 An invalid High Speed Link (HSL) configuration was detected SVCDOCS

An error was detected in the fabric. Have the customer check for problems
reported at the IBM Network Manager. This includes cases such as path
migration, etc.
69E5 System log entry only, no service action required

A 12X communications error occurred. Unrecognized command from

Subnet Manager. Does not require service.
69E6 System log entry only, no service action required

The cable connection to the switch is broken. Verify that the cable is
connected and the switch is powered on. After repairing the problem,
verify that the connection has been restored by using the IBM Network
Manager. Does not require service.
69E7 System log entry only, no service action required

The cable connection to the switch has been restored. No service action
required.
69E9 System log entry only, no service action required

Initial communication has occurred with the Subnet Manager. No service

action required. The CEC and switch firmware are now communicating.
69EA System log entry only, no service action required

Reported when the logical switch receives a setPortInfo for the switch
management port that sets a new SM LID. This indicates the point where
DMA can report changes in switch port states to SM via a TRAP and also
that SM has received and accepted out responses to the initial gets. This
proves that there is 2-way communication. Note that this will also tell us
when a subnet merge has occurred and a new SM has issued a setPortInfo
with an SMLID that differs from the previous one. No service action
required.
69EB User intervention required SVCDOCS

A 12X configuration error was detected by the HCA. Verify that the
configuration is correct at the HCA. The Port 1 and 2 configurations
conflict.
69EC User intervention required SVCDOCS

A 12X adapter in the server does not support connections to I/O

enclosures.

Upgrade the adapter at the location given in the serviceable event view to
a new version. Contact support for assistance.
69ED System log entry only, no service action required

A 12X cable connection initialized to a lower signal frequency. The link is

operational but operating at a bandwidth below its rated capacity. This
may lead to degraded I/O throughput.
BAD1 Platform firmware detected an error NEXTLVL

Platform firmware detected unexpected or not valid data returned from

non-platform firmware.

Contact your next level of support.

Reference codes 239

A7xx, B7xx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
C2AC System log entry only, no service action required SVCDOCS

The Capacity on Demand License acceptance has completed.

No corrective action is required.

F103 Platform LIC failure LICCODE

Work with the FRU list in the serviceable event view if there is one,
otherwise use the FRU list documented here to determine the parts to
exchange.

The platform LIC detected an internal problem.

Collect all the SRC words and the platform system dump, then contact
your next level of support.
F104 Operating System error SVCDOCS

Platform Licensed Internal Code terminated a partition.

If SRC word 3 is 0007, then a user may have initiated a function 22 prior to
the operating system completing the IPL. If a function 22 was not
performed, or if SRC word 3 is not 0007, look for other serviceable errors
which occurred at same time frame.
F105 Platform LIC detected an error NEXTLVL

Work with the FRU list in the serviceable event view if there is one,
otherwise use the FRU list documented here to determine the parts to
exchange.

The platform LIC detected an internal problem.

Collect all the SRC words and the platform system dump, then contact
your next level of support.
F10A Platform LIC detected an error SVCDOCS

Look for errors with SRCs of the form B1xx xxxx in the Serviceable Event
View. Work those errors first. If that does not correct the problem, collect
all the SRC words and the platform system dump, then contact your next
level of support.
F10B A resource has been disabled due to hardware problems ANYPROC

Work with the FRU list in the serviceable event view if there is one,
otherwise use the FRU list documented here to determine the parts to
exchange. The platform detected a problem with a processor. The processor
is not functional. Look in the Serviceable Event View for a B1xx xxxx error
that implicates a processor. If the Serviceable Event View contains no B1xx
xxxx error, or if resolving the error fails to correct the problem, contact
your next level of support.
F120 Platform firmware detected an error

The platform is unable to support the requested architecture options

requested by the operating system via ibm,client-architecture-support
interface.

(A9xx, B9xx) Reference codes

The A9xx and B9xx SRCs and their associated unit reference codes give information about the user
program.

240 System i® and System p®: Reference codes

A9xx, B9xx

1. Refer the user to the Reference code list in Troubleshooting. For additional help, the user should
contact the next level of support.

Note: For a brief description of some of the C9xx codes, see Initial Program Load (IPL) Information.
2. If a Licensed Internal Code error is suspected and the recovery action recommends an IPL, then take a
main storage dump to save the error conditions before the customer does an IPL. Support may need
the information saved in this dump. For more information, see Working with Storage Dumps.
3. Have the customer continue with the recommended recovery action.

(AAxx) Partition firmware reference (attention) codes

Partition firmware posts AAxx system reference (attention) codes, which offer information about the next
target state for the platform firmware. These codes might also indicate that you need to perform an
action, such as opening a firmware console or checking serial connections.

The AAxx table uses the following format:

Note: Click the failing item code only when you experience a hang condition on an attention code.
For example, a hang condition occurs when your server performs a requested action but the SRC
in the control panel display does not change for several minutes and the partition firmware
appears to be hung.

Table 1. (AAxx) Partition firmware reference (attention) codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
AA00E158 1. Open ASMI
2. Select Power/Restart Control-->Power On/Off System
3. Select ’continue to operating system’ on the option labeled “AIX/Linux
partition mode boot”
AA00E159 Waiting for the serial connection to the service processor to be established

Check the serial connection to the service processor. Correct all problems
that are found.
AA00E175 The I/O configuration exceeds the recommended size. Some operating FWFLASH
systems might crash when using this configuration.

Reference codes 241

AAxx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
AA00E1A9 The system is booting to the System Management Services (SMS) menus. FWFLASH
Note: If the system or partition returns to the SMS menus (as indicated by
this progress code) after a boot attempt failed, use the ASMI menus to
inspect the progress code history:
v Look for a BAxx xxxx reference (error) code, which might indicate why
the boot attempt failed. When you find a BAxx xxxx error code, see
“(BAxx) Partition firmware reference (error) codes” on page 469 to find
the code, then follow the actions indicated to resolve the boot problem.
v If you do not find a BAxx xxxx error code, see Problems with loading
and starting the operating system (for AIX® and Linux®) to resolve the
boot problem.
AA00E1B0 Waiting for the user to select the language and keyboard PFW1548

Select the language and keyboard.

AA00E1B1 Waiting for the user to accept or decline the license agreement PFW1548

Accept or decline the license agreement.

AA00E1F3 Admin access password prompt FWPWD

On the firmware console, enter the password for the admin user of the
service processor
AA060007 A keyboard was not found

Ensure that a keyboard is attached to the USB port assigned to the

partition.
AA06000B The system or partition was not able to find an operating system on any of
the devices in the boot list.

Modify the boot list using the SMS menus so that it includes devices that
are know to have a good copy of the operating system and retry the boot.
If you are still unable to boot an operating system, go to Problems with
loading and starting the operating system.
AA06000C The media in a device in the boot list was not bootable.

Replace the media in the device with known-good media, of modify the
boot list to boot from another bootable device. If you are still unable to
boot an operating system, go to Problems with loading and starting the
operating system.
AA06000D The media in the device in the bootlist was not found under the I/O
adapter specified by the bootlist.

Verify that the medium (CD-ROM, for example) from which you are trying
to boot is bootable, of try another medium. If you are still unable to boot
an operating system or diagnostic CD-ROM, go to Problems with loading
and starting the operating system.
AA06000E The adapter specified in the boot list is not present or is not functioning.

If AIX is being booted, and can be booted from another device, do so, then
run online AIX diagnostics against the failing adapter. If AIX cannot be
booted from another device, boot standalone AIX diagnostics from
CD-ROM or a NIM server and run diagnostics against the device.

If Linux is being booted, boot standalone AIX diagnostics from CD-ROM or

a NIM server and run diagnostics against the device.

242 System i® and System p®: Reference codes

AAxx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
AA060010 The FAT file system on the boot disk is configured in a way that might
cause a boot failure.

Increase the FAT partition size by 10% to keep the number of data clusters
fewer than approximately 4080.
AA060011 The firmware did not find an operating system image and it was unable to
detect at least one hard disk in the boot list. Firmware is now retrying the
entries in the boot list.

This error might occur before the initialization of an enclosure that contains
the boot disk completes or when the boot disk belongs to another partition.

If this problem persists, do the following:

1. Verify that the boot disk belongs to the partition that is being booted
2. Verify that the boot list in the SMS menus is correct
AA130013 Bootable media is missing from a USB CD-ROM

Put a bootable CD in the USB CD-ROM and retry the boot operation.
AA130014 The media in a USB CD-ROM has been changed.
1. Retry the operation.
2. Check for server firmware updates; apply if available, then retry the
operation.
AA170210 Setenv/$setenv parameter error: the name contains a null character. FWFLASH
AA170211 Setenv/$setenv parameter error: the value contains a null character. FWFLASH
AA190001 The server firmware function to get and set the time-of-day clock reported
an error
1. Use the operating system utility to set the system clock.
2. If the problem persists, check for server firmware updates and apply
them, if available.
AA260001 The system is waiting for someone to enter the machine type, model, and
serial number.

At the system prompt, type the machine type, model, and serial number of
the system.

(B000) Network reference codes

This SRC indicates a general network error.

Find the unit reference code in the following table.

Table 1. (B000) Network reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
0100 Ethernet network failure

Do the following:
1. Reseat your Ethernet card.
2. Check your Ethernet cable connections.
3. If the previous actions do not resolve the problem, contact your next
level of support.

Reference codes 243

B000

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
0500 Ethernet network failure

Do the following:
1. Reseat your Ethernet card.
2. Check your Ethernet cable connections.
3. If the previous actions do not resolve the problem, contact your next
level of support.
0600 Ethernet network failure

Do the following:
1. Reseat your token ring card.
2. Check your token ring cable connections.
3. If the previous actions do not resolve the problem, contact your next
level of support.
1600 Token-ring network failure

Do the following:
1. Reseat your token ring card.
2. Check your token ring cable connections.
3. If the previous actions do not resolve the problem, contact your next
level of support.

(B001) Reference codes

This SRC might indicate a communications error.

Find the unit reference code in the following table. For more on the Failing Item column entries, see Table
2. Failing items details, which follows the reference code table below.

B001

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
5892 Network call-progress-signal type 22 FI00700
FI00704
UJA35
5893 Network call-progress-signal type 23 FI00704
FI00701
FI00719
5894 Network call-progress-signal type 41 FI00700
UJE34
UJ0E3
UJA35
5895 Network call-progress-signal type 42 FI00700
UJA35
5896 Network call-progress-signal type 43 UJ0E3
FI00700
FI00704
FI00705
UJA35
5897 Network call-progress-signal type 44 FI00700
FI00705
UJA35
5898 Network call-progress-signal type 45 FI00700
FI00705
UJA35
5899 Network call-progress-signal type 46 FI00700
FI00705
UJA35
589A Network call-progress-signal type 47 FI00700
UJ0E3
UJA35
FI00705
589B Network call-progress-signal type 48 UJE34
FI00700
FI00704
UJA35
589C Network call-progress-signal type 49 UJ0E3
589D Network call-progress-signal type 51 FI00704
UJ0E3
FI00705
589E Network call-progress-signal type 52 UJE34
FI00700
FI00705
UJA35
589F Network call-progress-signal type 61 UJ0E3
58A0 Network call-progress-signal type 71 UJ0E3
58A1 Network call-progress-signal type 72 UJ0E3
58E0 Communications line not operational FI00719
UJA34
58E1 Communications connection not made UJA33
FI00730

260 System i® and System p®: Reference codes

B001

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
58E2 Communications line not operational FI00704
FI00701
FI00719
FI00730
58E4 Port or DCE error has recovered; port now available UJE34

This reference code does not identify an error but is used to report that an
X.21 port used in a short-hold mode, multiple port sharing configuration
that was temporarily not operating is now available. One of the following
reference codes may have been reported previously:
v 5870
v 5871
v 5872
v 5873
v 5893
v 5851
v 5852
v 5853
v 587B

If any of the listed reference codes are occurring frequently and are causing
performance problems, use the reported reference code to isolate the
problem.
8011 IOP activation failed. UJE34

MDMCNTRYID parameter in Network Attributes is not set. Use the

CHGNETA command to set MDMCNTRYID value.
8013 IOP activation failed. UJE34

The MDMCNTRYID parameter in Network Attributes is not valid for this

adapter. Use the CHGNETA command to change MDMCNTRYID.
8020 System log entry only, no service action required
FFFF User suspected communications problem. USER

Table 2. Failing items details

Failing Item Description Document Description

AJDG301 Licensed Internal Code See the service documentation for instructions.
UJ0E3 Communications network equipment
UJA32 Line or automatic call unit already in use Communications Configuration
UJA33 Too many communications lines in use Communications Configuration
UJA34 CNNPOLLTMR value in CRTLINSDLC Communications Configuration
command
UJA34 CNNPOLLRTY value in CRTLINSDLC Communications Configuration
command
UJA34 CTSTMR value in CRTLINSDLC command Communications Configuration
UJA34 AUTOANS, AUTODIAL, SWTCNN, CNN Communications Configuration
values in CRTLINSDLC command
UJA34 DIALRTY value in CRTCTL____ command Communications Configuration

Reference codes 261

B001

Failing Item Description Document Description

UJA34 DSRDRPTMR value in the CRTLINSDLC Communications Configuration
command
UJA34 LINESPEED value in CRTLINSDLC command Communications Configuration
UJA34 NRZI value in CRTLINSDLC command Communications Configuration
UJA34 INACTTMR value in CRTLINSDLC command Communications Configuration
UJA34 CNNTMR value in CRTLINSDLC command Communications Configuration
UJA34 SWTCNN, AUTOANS values in CRTLINSDLC Communications Configuration
command
UJA34 MAXFRAME value in CRTLINSDLC command Communications Configuration
UJA34 SNBU, MODEMRATE, DUPLEX values in Communications Configuration
CRTLINSDLC command
UJA34 MODULUS value in CRTLINSDLC command Communications Configuration
UJA34 FRAMERTY value in CRTLINSDLC command Communications Configuration
UJA34 MAXCTL value in CRTLINSDLC command Communications Configuration
UJA34 ACRSRCNAME value in CRTLINSDLC Communications Configuration
command
UJA34 EXCHID value in CRTCTL____ command Communications Configuration
UJA34 SHMNODE value in CRTLINSDLC command Communications Configuration
UJA34 NPRDRCVTMR value in CRTLINSDLC Communications Configuration
command
UJA34 Operator reset local controller (vary on/off) but Communications Configuration
not remote
UJA34 INTERFACE value in CRTLINSDLC command Communications Configuration
UJA34 SHMNODE value in CRTLINSDLC command Communications Configuration
UJA34 MAXOUT value in CRTLINSDLC command Communications Configuration
UJA34 THRESHOLD value in CRTLINSDLC command Communications Configuration
UJA34 RMTANSTMR value in the SDLC command Communications Configuration
UJA34 RSRCNAME value in the CRTLINSDLC Communications Configuration
command
UJA34 IDLTMR value in CRTLINSDLC command Communications Configuration
UJA34 ROLE value in CRTLINSDLC command Communications Configuration
UJA35 CNNNBR value in the CRTCTL____ command Communications Configuration
UJA35 RMTNETID value in CRTCTLAPPC command Communications Configuration
UJA35 STNADR value in CRTCTL_____command Communications Configuration
UJE34 Configuration or OS/400 licensed program Communications Configuration
UJE34 Excessive usage on X.21 network Communications Configuration
UJE34 X.21 network service problem Communications Configuration
UJE34 No failure found Communications Configuration
UJE39 Configuration problem in remote equipment Communications Configuration
USER User suspected communications problem. See the service documentation for instructions.

(B002) Reference codes

This SRC might indicate a communications error.

262 System i® and System p®: Reference codes

B002

Find the unit reference code in the following table. For more on the Failing Item column entries, see Table
2. Failing items details, which follows the reference code table below.

Failing Item Description Document Description

AJDG301 Licensed Internal Code See the service documentation for instructions.
UJ0E3 Communications network equipment
UJB35 CTSTMR value in CRTLINBSC command Communications Configuration
UJB35 AUTOANS, AUTODIAL, DIALCMD, SWTCNN, Communications Configuration
CNN in CRTLINBSC
UJB35 DSRDRPTMR value in the CRTLINBSC Communications Configuration
COMMAND
UJB35 INTERFACE value in CRTLINBSC command Communications Configuration
UJB35 CNN value in CRTLINBSC command Communications Configuration
UJB35 STXLRC value in CRTLINBSC command Communications Configuration
UJB35 RSRCNAME value in CRTLINBSC command Communications Configuration

268 System i® and System p®: Reference codes

B002

Failing Item Description Document Description

UJB35 RMTANSTMR value in the CRTLINBSC Communications Configuration
command
UJB35 ASPT ACRSRCNAME value in CRTLINBSC Communications Configuration
command
UJB35 MAXBUFFER value in CRTLINBSC command Communications Configuration
UJB35 THRS THRESHOLD value in CRTLINBSC Communications Configuration
command
UJB35 SNBU, MODEMRATE values in CRTLINBSC Communications Configuration
command
UJB36 DIALRTY value in CRTCTLBSC command Communications Configuration
UJB36 CNNNBR value in CRTCTL______ command Communications Configuration
UJB37 System processor workload heavy Communications Configuration
UJB37 System processor workload heavy Communications Configuration
UJC38 Line or automatic call unit already in use
UJE34 CONF Configuration or OS/400 licensed Communications Configuration
program
UJE34 No failure found Communications Configuration
USER User suspected communications problem.

(B003) Asynchronous communications reference codes

The Asynchronous Communications detected a failure.
1. Look at characters 5 through 8 of the top 16 character line of function 11 (4 rightmost characters of
word 1). These 4 characters are the unit reference code.
2. Find the unit reference code in the following table.

CHGNETA command to set MDMCNTRYID value.
8013 IOP activation failed. CNGCONF

The MDMCNTRYID parameter in Network Attributes is not valid for this

adapter. Use the CHGNETA command to change MDMCNTRYID.
8020 System log entry only, no service action required
FFFF User suspected communications problem. UNGUPPR

274 System i® and System p®: Reference codes

B003

Table 2. Asynchronous communications failing items details

Failing Item Description Document Description

21F4325 Locally attached external cable System Problem Analysis information
21F4333 Locally attached external cable System Problem Analysis information
21F9345 Communications two-port adapter cable Cable Attachment
24F8549 Multifunction I/O processor storage expansion Repair and Parts; removal and installation
procedures
AJDG301 Licensed Internal Code Service Functions; APAR or LICTR
CNGBCHR BITSCHAR value in CRTLINASC command Communications Configuration
CNGCATL THRESHOLD value in CRTLINASC command Communications Configuration
CNGCCEL THRESHOLD value in CRTLINASC command Communications Configuration
CNGCONF Configuration or OS/400 licensed program Communications Configuration
CNGDRTY DIALRTY value in CRTCTLASC command Communications Configuration
CNGLBPS LINESPEED, BITSCHAR, PARITY, STOPBITS Communications Configuration
values in CRTLINASC
CNGMAXI MAXBUFFER value in CRTLINASC command Communications Configuration
CNGMCFL DUPLEX, CNN, MODEMRATE values in Communications Configuration
CRTLINASC command
CNGSLPT RSRCNAME value in CRTLINASC command Communications Configuration
CNGTHRS THRESHOLD value in CRTLINASC command Communications Configuration
GNGALDC Any adapter card attached to this I/O processor
card
GNGIOAB System unit or I/O card enclosure
GNGLINK External devices or network
GNGLNKI Line, modems, remote equipment
GNGLNKM Line, modems, remote equipment
GNGLNKR Remote computer and data communications
equipment
GNGLNKT Remote computer and data communications
equipment
GNGOTHR Another adapter card on the same IOP to IOA
Bus
GNGRESC Line or automatic call unit already in use
GNGTP Communications line
UJB37 System processor workload heavy Communications Configuration
UJC35 ACRSRCNAME value in CRTLINASC Communications Configuration
command
UJC35 CTSTMR value in CRTLINASC command Communications Configuration
UJC35 CALLNBR value in CRTLINASC command Communications Configuration
UJC35 DSRDRPTMR value in the CRTLINASC Communications Configuration
command
UJC35 LINESPEED value in CRTLINASC command Communications Configuration
UJC35 STOPBITS value in CRTLINASC command Communications Configuration

Reference codes 275

B003

Failing Item Description Document Description

UJC35 DUPLEX, ECHO, FLOWCNTL value in Communications Configuration
CRTLINASC command
UJC35 AUTOANS, AUTODIAL, DIALCMD, SWTCNN, Communications Configuration
CNN in CRTLINASC
UJC35 PARITY value in CRTLINASC command Communications Configuration
UJC35 CNN value in CRTLINASC command Communications Configuration
UJC35 ECHO value in CRTLINASC command Communications Configuration
UJC35 EORTBL value in CRTLINASC command Communications Configuration
UJC35 FLOWCNTL value in CRTLINASC command Communications Configuration
UJC35 RMTANSTMR value in CRTLINASC command Communications Configuration
UJC36 CNNNBR value in CRTCTLASC command Communications Configuration
UJE34 No failure found Communications Configuration
UNGUPPR User suspected communications problem.

(B004) Reference codes

This SRC might indicate a communications error.

Find the unit reference code in the following table. For more on the Failing Item column entries, see Table
2. Failing items details, which follows the reference code table below.

Table 1. (B004) Reference codes

Failing Item Description Document Description

UJ0E6 Application program controlling the station
UJ0E6 Remote computer equipment
UJ0E9 X.25 network or directly attached data terminal
equipment
UJA36 MODULUS value in CRTLINX25 command Communications Configuration
UJE38 Too many logical links defined Communications Configuration
UJJ35 THRESHOLD value in CRTLINX25 command Communications Configuration
UJJ35 DFTPKTSIZE value in CRTLINX25 command Communications Configuration
UJJ35 DFTWDWSIZE value in CRTLINX25 command Communications Configuration
UJJ36 X25CNNTMR value in CRTCTL______command Communications Configuration
UJJ36 USRGRPID value in CRTCTL_____command Communications Configuration
UJJ36 LGLCHLE value in CRTLINX25 command Communications Configuration
UJJ36 LINKPCL value in CRTCTL_____command Communications Configuration
UJJ36 X25RSPTMR value in CRTCTL_____command Communications Configuration
UJJ37 No error found Communications Configuration
UJJ38 User specified X.25 parameters Communications Configuration
UJJ39 Local X.25 system configuration Communications Configuration

(B005) Reference codes

This SRC might indicate a communications error.

Find the unit reference code in the following table. For more on the Failing Item column entries, see Table
2. Failing items details, which follows the reference code table below.

Table 1. (B005) Reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
A000 to A002 Input value error in I/O card Licensed Internal Code PTFSRCH
A003 Procedure error in I/O card Licensed Internal Code PTFSRCH
A004 to A00C Input value error in I/O card Licensed Internal Code PTFSRCH
A00E Procedure error in Licensed Internal Code PTFSRCH
A010 to A012 Input value error in I/O card Licensed Internal Code PTFSRCH
A013 Wrong config data given to local area network controller PTFSRCH
A014 to A01F, Input value error in I/O card Licensed Internal Code PTFSRCH
A020 to A024
A025 Procedure error in I/O card Licensed Internal Code PTFSRCH
A027 Input value error in I/O card Licensed Internal Code PTFSRCH
A028 Input value error in I/O card Licensed Internal Code
A029 Procedure error in I/O card Licensed Internal Code PTFSRCH
A02A to A02D Input value error in I/O card Licensed Internal Code PTFSRCH
A02E Wrong frame received from remote equipment UJE39
A02F Input value error in I/O card Licensed Internal Code PTFSRCH
A201 Token-Ring controller storage not available PTFSRCH

Failing Item Description Document Description

IOA Token-ring network adapter See the service documentation for instructions.
IOP Communications I/O processor card See the service documentation for instructions.
PTFSRCH Licensed Internal Code See the service documentation for instructions.
UJE31 Token-ring network manager program See the service documentation for instructions.
UJE32 Token-ring network manager program See the service documentation for instructions.
UJE33 Nearest active upstream node See the service documentation for instructions.
UJE34 Local area network busy because of maximum See the service documentation for instructions.
usage
UJE35 Local Communications Adapter configuration See the service documentation for instructions.
UJE35 ADPTADR value in CRTLINTRN command See the service documentation for instructions.
UJE37 Token-ring network or remote station See the service documentation for instructions.
UJE38 Token-ring controller card work load exceeded See the service documentation for instructions.
UJE39 Remote computer equipment See the service documentation for instructions.
USER User suspected communications problem. See the service documentation for instructions.

(B006) Common Licensed Internal Code reference codes

The common Licensed Internal Code detected a failure.

284 System i® and System p®: Reference codes

B006

1. Look at characters 5 through 8 of the top 16 character line of function 11 (4 rightmost characters of
word 1). These 4 characters are the unit reference code.
2. Find the unit reference code in the following table.

For more on the Failing Item column entries, see Table 2. Common Licensed Internal Code failing items
details, which follows the reference code table below.

Table 1. (B006) Common Licensed Internal Code reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
1201 I/O processor resource not available AJEQU00
AJDG301
A deactivation failed to get a resource controlled by Licensed Internal
Code.
1202 Not valid condition in I/O Processor Licensed Internal Code AJEQU00
AJDG301
An error in an activation or deactivation occurred. FI00131
1203 I/O processor resource not available AJEQU00
AJDG301
A resource needed to perform a requested function is not available in the
Licensed Internal Code.
1204 Not valid condition in I/O Processor Licensed Internal Code AJEQU00
AJDG301
The Licensed Internal Code has recovered from a condition that was not FI00131
expected.
1205 to 1206 I/O processor card or Licensed Internal Code error AJEQU00
FI00131
A microprocessor exception occurred on the I/O processor. FI00132
1207 I/O processor resource not available AJEQU00
AJDG301
The Licensed Internal Code could not allocate memory resources on the
I/O processor card.
1208 Not valid condition in I/O Processor Licensed Internal Code AJEQU00
AJDG301
The Licensed Internal Code found a condition that should not have FI00131
occurred.
1209 I/O processor was not ready for interrupt that occurred AJEQU00
FI00131
1210 I/O processor resource not available

The I/O processor error log is being filled faster than the errors are being
reported to the system. Check other errors reported to the system and
correct them.
1211 System bus error FI00131
ANYBUS
AJEQU00
AJDG301
1212 A permanent I/O processor failure occurred FI00131
AJEQU00
1213 System bus error AJDG301
AJEQU00
FI00131
1214 to 1215 I/O processor card or Licensed Internal Code error FI00131
AJEQU00

Reference codes 285

B006

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
1301 I/O processor resource not available CDAWKLD
AJDGP01
An activation or deactivation failed to get a resource controlled by Licensed AJDG301
Internal Code.
1302 Not valid condition in I/O Processor Licensed Internal Code AJDGP01
AJDG301
An error in an activation or deactivation occurred. FI00131
FI00132
1303 I/O processor resource not available IOACNFG
AJDGP01
A resource needed to perform a requested function is not available in the AJDG301
Licensed Internal Code.
1304 Not valid condition in I/O Processor Licensed Internal Code AJDGP01
AJDG301
The Licensed Internal Code has recovered from an unexpected condition. FI00131
FI00132
1305 to 1306 I/O processor card or Licensed Internal Code error AJDGP01
FI00131
A microprocessor exception occurred on the I/O processor. FI00132
BACKPLN
1307 I/O processor resource not available AJDGP01
AJDG301
The Licensed Internal Code could not allocate memory resources on the IOACNFG
I/O processor card. FI00132
1308 Not valid condition in I/O Processor Licensed Internal Code AJDGP01
AJDG301
The Licensed Internal Code found a condition that should not have FI00131
occurred.
1309 I/O processor was not ready for interrupt that occurred AJDGP01
FI00131
FI00132
FI01117
1310 I/O processor resource not available

The I/O processor error log is being filled faster than the errors are being
reported to the system. Check other errors reported to the system and
correct them.
1311 System bus error FI00131
ANYBUS
AJDGP01
AJDG301
1312 A permanent I/O processor failure occurred FI00131
AJDGP01
1313 System bus error AJDG301
AJDGP01
FI00131
1316 I/O processor card or Licensed Internal Code error AJDGP01
FI00132
FI00131

286 System i® and System p®: Reference codes

B006

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
1317 I/O processor card error SVCDOCS

1. If the I/O Processor is not operable and disk units are attached, use
Hardware Service Manager to re-IPL the IOP. Other resources attached to
the IOP may then need to be Varied On.

2. If disk units are not attached, perform the VRYCFG RESET(*YES)

command to reset the IOP and Vary On attached resources.
1318 I/O processor card error FI00131
1403 Service processor Licensed Internal Code error AJDGP01
SVCPROC
A resource needed to perform a requested function is not available in the
Licensed Internal Code.
1404 Service processor Licensed Internal Code error AJDGP01
SVCPROC
The Licensed Internal Code has recovered from an unexpected condition.
1405 Service processor Licensed Internal Code error AJDGP01
SVCPROC
A recoverable microcode condition occurred on the Service processor.
1406 Service processor Licensed Internal Code failed AJDGP01
SVCPROC
A microprocessor exception occurred on the Service processor. AJDG301
1407 Service processor Licensed Internal Code failed AJDGP01
SVCPROC
The Licensed Internal Code could not allocate resources on the Service AJDG301
processor.
1408 Service processor Licensed Internal Code failed AJDGP01
AJDG301
SVCPROC
1409 Service processor Licensed Internal Code failed AJDGP01
SVCPROC
The Service processor was not ready for an interrupt that occurred.
1A01 I/O processor resource not available CDAWKLD
FI00130
A deactivation failed to get a resource controlled by Licensed Internal AJDG301
Code.
1A02 Not valid condition in I/O Processor Licensed Internal Code FI00130
FI00131
An error in an activation or deactivation occurred. FI00132
1A03 I/O processor resource not available FI00130
AJDG301
A resource that is needed to perform a requested function is not available CDAWKLD
in the Licensed Internal Code.
1A04 Recovered from condition in Licensed Internal Code. FI00130
AJDG301
The Licensed Internal Code has recovered from a condition that was not FI00131
expected. FI00132
1A05 to 1A06 I/O processor card or Licensed Internal Code error FI00130
FI00131
A microprocessor exception occurred on the I/O processor. FI00132

Reference codes 287

B006

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
1A07 I/O processor resource not available CDAWKLD
FI00132
The Licensed Internal Code could not allocate memory resources on the FI00130
I/O processor card. AJDG301
1A08 Not valid condition in I/O Processor Licensed Internal Code FI00130
FI00131
The Licensed Internal Code found a condition that should not have FI00132
occurred.
1A09 Threshold overflow FI00131
FI00132
The I/O processor card has detected a threshold of recoverable error FI01117
conditions. The errors are either wrong interruptions or memory error FI00130
corrections. If in communications, the line is still running.
Note: If a large number of these errors occur during a short time, they may
be caused by an electrically noisy environment, a defective communications
I/O processor card or modem, or a communications I/O processor code
problem.
1A10 Error reported to system

The I/O processor error log is being filled faster than the errors are being
reported to the system. Check other errors reported to the system and
correct them.

DISKTRY Disk unit tray See the service documentation for instructions.
DISKTRY Disk unit tray See the service documentation for instructions.
DISKTRY Disk unit tray See the service documentation for instructions.
DISKTRY Disk unit tray See the service documentation for instructions.
DISKTRY Disk unit tray See the service documentation for instructions.
DISKTRY Disk unit tray See the service documentation for instructions.
DISKTRY Disk unit tray See the service documentation for instructions.
DISKTRY Disk unit tray See the service documentation for instructions.
DISKTRY Disk unit tray See the service documentation for instructions.
DISKTRY Disk unit tray See the service documentation for instructions.
DISKTRY Disk unit tray See the service documentation for instructions.
DISKTRY Disk unit tray See the service documentation for instructions.
DISKTRY Disk unit tray See the service documentation for instructions.
DISKTRY Disk unit tray See the service documentation for instructions.
DISKTRY Disk unit tray See the service documentation for instructions.
DISKTRY Disk unit tray See the service documentation for instructions.
DISKTRY Disk unit tray See the service documentation for instructions.
IOACNFG Configuration error See the service documentation for instructions.
SVCDOCS Customer engineer directed to system problem See the service documentation for instructions.
analysis
SVCPROC Service Processor Card See the service documentation for instructions.
UDAWAIT Wait to next IPL or perform TU-PIP4

(B008) Reference codes

This SRC might indicate a communications error.

Find the unit reference code in the following table. For more on the Failing Item column entries, see Table
2. Failing items details, which follows the reference code table below.

B008

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
5886 Automatic call unit switched link time-out; no answer FI00703
IOA
FI00702
UJ0E3
5E01 Call error; incoming call received during outgoing call UJ0E3
6320 Automatic call unit has abandon-call attempt FI00700
UJA35
FI00703
IOA
FI00702
6322 Abandon call retry error; incorrect number length UJA35
FI00703
6870 Automatic call unit power turned off FI00703
FI00702
IOA
8011 IOP activation failed. UJE34

The MDMCNTRYID parameter in Network Attributes is not set. Use the

CHGNETA command to set MDMCNTRYID.
8013 IOP activation failed. UJE34

The MDMCNTRYID parameter in Network Attributes is not valid for this

adapter. Use the CHGNETA command to change the MDMCNTRYID
value.
8020 User suspected communications problem.
D230 ISDN channel hardware not operational 74F1624
FI00730
DA00 The I/O card LIC detected an internal error FI00730
DA01 The I/O card LIC detected an internal error FI00730
IOA
FFFF User suspected communications problem. USER

Table 2. Failing items details

Failing Item Description Document Description

74F1624 ISDN channel hardware Repair and Parts; removal and installation
procedures
AJDG301 Licensed Internal Code See the service documentation for instructions.
IOA Communications adapter card Repair and Parts; removal and installation
procedures
IOP Communications I/O processor card Repair and Parts; removal and installation
procedures
UJ0E3 Communications network equipment
UJ0E9 Communications network equipment
UJA35 CNNNBR value in CRTLINX25___command Communications Configuration
UJE34 Configuration or OS/400 licensed program Communications Configuration
UJE34 No failure found Communications Configuration
UJJ35 MAXPKTSIZE in CRTLINX25 command Communications Configuration

304 System i® and System p®: Reference codes

B008

Failing Item Description Document Description

UJJ35 ACRSRCNAME value in CRTLINX25 command Communications Configuration
UJJ35 FRAMERTY value in CRTLINX25 command Communications Configuration
UJJ35 X25DCE value in CRTLINX25 command Communications Configuration
UJJ35 DSRDRPTMR value in the CRTLINX25 Communications Configuration
command
UJJ35 INTERFACE value in CRTLINX25 command Communications Configuration
UJJ35 DFTWDWSIZE value in CRTLINX25 command Communications Configuration
UJJ35 RMTANSTMR value in the CRTLINX25 Communications Configuration
command
UJJ35 IDLTMR value in CRTLINX25 command Communications Configuration
UJJ35 RSRCNAME value in CRTLINX25 command Communications Configuration
UJJ35 DIALRTY value in CRTCTL____ command Communications Configuration
UJJ35 CTSTMR value in CRTLINX25 command Communications Configuration
USER User suspected communications problem.

(B009) Reference codes

This SRC might indicate a communications error.

Find the unit reference code in the following table. For more on the Failing Item column entries, see Table
2. Failing items details, which follows the reference code table below.

Table 1. (B009) Reference codes

B010

If any of the listed reference codes are occurring frequently and are causing
performance problems, use the reported reference code to isolate the
problem.
8011 IOP activation failed. UJE34

MDMCNTRYID parameter in Network Attributes is not set. Use the

CHGNETA command to set MDMCNTRYID value.
8013 IOP activation failed. UJE34

The MDMCNTRYID parameter in Network Attributes is not valid for this

adapter. Use the CHGNETA command to change MDMCNTRYID.
8020 System log entry only, no service action required
FFFF User suspected communications problem. USER

Table 2. Failing items details

Failing Item Description Document Description

Reference codes 325

B010

Failing Item Description Document Description

(B013) Reference codes

This SRC might indicate a cryptographic adapter error.

326 System i® and System p®: Reference codes

B013

Find the unit reference code in the following table. For more on the Failing Item column entries, see Table
2. Failing items details, which follows the reference code table below.

Table 1. (B013) Reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
6601 I/O adapter hardware error detected IOA
PTFSRCH
IOP
6602 An I/O processor Licensed Internal Code error occurred. PTFSRCH
IOA
IOP
6603 Tampering of cryptographic card suspected. IOA
IOP
PTFSRCH
6604 Operating voltage or temperature range limits exceeded. CARDTMP

Correct any conditions in the physical environment which might have

caused the voltage or temperature out-of-range error on the 4758 adapter
card. After you correct the conditions, vary off and then vary back on the
4758 device description associated with the 4758 adapter card.
6611 I/O adapter hardware error detected IOA
PTFSRCH
6613 Tampering of cryptographic card suspected. IOA
PTFSRCH
6614 Operating voltage or temperature range limits exceeded. CARDTMP

Correct any conditions in the physical environment which might have

caused the voltage or temperature out-of-range error on the cryptographic
adapter card. After you correct the conditions, vary off and then vary back
on the device description associated with the cryptographic adapter card.
6615 Cryptographic adapter LIC not loaded or not valid. LOADCY1
PTFSRCH
IOA
6616 System log entry only, no service action required
6617 Adapter monitoring circuitry has failed. IOA
PTFSRCH
6618 Adapter monitoring circuitry has exceeded threshold. IOA
PTFSRCH
The adapter can be varied on and used, but should be replaced during the
next scheduled maintenance of the system.

Table 2. Failing items details

Failing Item Description Document Description

CARDTMP Operating voltage or temperature range limit See the service documentation for instructions.
exceeded
IOA I/O adapter card See the service documentation for instructions.
IOP I/O processor card See the service documentation for instructions.
LOADCY1 I/O card Licensed Internal Code See the service documentation for instructions.
PTFSRCH Licensed Internal Code See the service documentation for instructions.

Reference codes 327

B014

(B014) Reference codes

This SRC might indicate a communications error.

Find the unit reference code in the following table. For more on the Failing Item column entries, see Table
2. Failing items details, which follows the reference code table below.

Table 1. (B014) Reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
6661 Negative-acknowledgment received
B005 Block-check error on data received UJ0E3
UJB35
UJB35
FI00704
FI00705
FI00719
UJE34
B010 Clear-to-send signal dropped on modem interface FI00701
FI00704
FI00719
AJDG301
B015 Carrier-detect dropped on modem interface FI00701
UJ0E3
FI00704
FI00705
UJB35
AJDG301
FI00719
B020 Clear-to-send signal did not come up in required time FI00701
FI00704
UJB35
FI00719
AJDG301
B025 Clear-to-send signal did not drop in required time FI00701
FI00704
UJB35
FI00719
AJDG301
B030 Remote equipment did not respond in time-out period UJ0E3
FI00700
UJB35
FI00719
FI00704
AJDG301
B035 Remote equipment did not respond in time-out period FI00700
UJB35
B037 Too many or too few synchronization characters UJ0E3
FI00700
UJB35
FI00719
FI00704
AJDG301

328 System i® and System p®: Reference codes

B014

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
B040 Time-out; no data received UJ0E3
FI00701
UJB35
UJB35
FI00719
FI00704
UJB35
FI00700
B045 Unexpected response to temporary-text-delay FI00700
UJ0E3
FI00719
UJB35
FI00704
B050 Unexpected response to wait-acknowledge FI00700
UJ0E3
FI00719
UJB35
FI00704
B055 Data loss because receive buffer full UJB35
UJ0E3
UJB35
FI00719
FI00704
FI00700
B060 No response to temporary-text-delay or wait-acknowledge UJ0E3
FI00701
UJB35
UJB35
FI00719
FI00704
UJB35
FI00700
B065 Protocol error UJB35
FI00718
FI00700
FI00719
FI00704
B070, B072 Clock signal missing from external communications interface FI00701
FI00704
FI00719
B075 Communications IOP processed data received too slow UJP37
UJB35
FI00719
UJ0E3
B085 Data-set-ready dropped on modem interface FI00701
FI00704
FI00719
UJ0E3
AJDG301
B090 Negative-acknowledgment received UJ0E3
UJB35
UJB35
FI00719
UJE34
FI00704

Reference codes 329

B014

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
B105 Data not recognized UJ0E3
FI00719
UJB35
FI00704
B110 Remote system did not receive last acknowledgment sent UJ0E3
UJB35
FI00719
FI00704

Table 2. Failing items details

Failing Item Description Document Description

AJDG301 Licensed Internal Code See the service documentation for instructions.
UJ0E3 External devices or network
UJB35 STXLRC value in CRTLINBSC command Communications Configuration
UJB35 DTASTTRTY value in CRTLINBSC command Communications Configuration
UJB35 RCVTMR value in CRTLINBSC command Communications Configuration
UJB35 MAXBUFFER value in CRTLINBSC command Communications Configuration
UJB35 CTNRTY value in CRTLINBSC command Communications Configuration
UJE34 Not valid user data sent or received Communications Configuration
UJP37 Too many line descriptions active Communications Configuration

(B015) Reference codes

This SRC might indicate a communications error.

Find the unit reference code in the following table. For more on the Failing Item column entries, see Table
2. Failing items details, which follows the reference code table below.

Table 1. (B015) Reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
A555, A5AA, I/O card Licensed Internal Code failed FI00730
A5DD, A5E1 to
A5E2, A5EE, A5F1
to A5F3, A5F5,
A5F7, A5F9 to
A5FA, A5FC
A800 I/O card Licensed Internal Code failed UJE36
A802 to A804 Input value error in I/O card Licensed Internal Code AJDG301
A807 Input value error in I/O card Licensed Internal Code FI00730
AJDG301
A814 Procedure error in Licensed Internal Code AJDG301
FI00730
A820 Procedure error in Licensed Internal Code AJDG301
A821, A823 Input value error in I/O card Licensed Internal Code AJDG301
A825, A837 Procedure error in Licensed Internal Code AJDG301
FI00730

330 System i® and System p®: Reference codes

B015

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
A83C Procedure error in Licensed Internal Code AJDG301
A83D Procedure error in Licensed Internal Code FI00730
A845 to A847 Input value error in I/O card Licensed Internal Code AJDG301
AA09 Response from I/O card Licensed Internal Code not expected FI00730
AA10 Number of stations greater than allowed in configuration UJE35
AA13, AA16 Procedure error in I/O card Licensed Internal Code FI00730
AA17 to AA18 I/O card Licensed Internal Code failed FI00730
AF04 Wrong response received from I/O card Licensed Internal Code AJDG301
AF05, AF07 Local area network adapter; remote station error UJE39
AF08 Wrong response received from I/O card Licensed Internal Code FI00730
AF09 Input value error in I/O card Licensed Internal Code FI00730
AJDG301
AFFF Procedure error in Licensed Internal Code FI00730
UJE34

Table 2. Failing items details

Failing Item Description Document Description

AJDG301 Licensed Internal Code See the service documentation for instructions.
UJE34 Local area network busy because of maximum See the service documentation for instructions.
usage
UJE35 MAXCTL value in CRTLINTRN command See the service documentation for instructions.
UJE36 Lack of I/O processor resources See the service documentation for instructions.
UJE39 Remote computer equipment See the service documentation for instructions.

(B017) Reference codes

This SRC might indicate a cryptographic adapter error.

Find the unit reference code in the following table. For more on the Failing Item column entries, see Table
2. Failing items details, which follows the reference code table below.

Table 1. (B017) Reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
0001 Low battery condition detected on IOA. CRYPBAT
9001 Information only, no service action required

Table 2. Failing items details

Failing Item Description Document Description

CRYPBAT Cryptographic adapter battery See the service documentation for instructions.

(B018) Reference codes

This SRC might indicate a communications error.

Reference codes 331

B018

Find the unit reference code in the following table. For more on the Failing Item column entries, see Table
2. Failing items details, which follows the reference code table below.

Table 1. (B018) Reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
6004 ABEND due to unrecoverable condition. AJDGP01
6005 IOP activation failed. AJDGP01
6006 Error in OS/400 code.
6007 Error in OS/400 code. AJDG301
6008 to 6009 External devices or network
600A IOP activation failed. FI00701
GCCNET
IOA
8001 ABEND due to unrecoverable condition. AJDGP01
8002 IOP activation failed. AJDGP01
8003 ABEND due to failure to communicate with system.
8004 I/O adapter hardware error detected IOA
8005 ABEND due to unrecoverable condition. AJDGP01
8006 IOP activation failed. AJDGP01
8007 Error in OS/400 code.
8011 IOP activation failed.

The MDMCNTRYID parameter in Network Attributes is not set. Use the

CHGNETA command to set MDMCNTRYID.
8012 IOP activation failed.

The network type is *NISDN and there is a value for SPID but *NONE or
*CNNL was specified for LCLNBR. Run CHGNWIISDN and supply a
value for either the first or second local number parameter (LCLNBR) as
required, then vary on the NWI again.
8013 IOP activation failed. UCCCONF

The MDMCNTRYID parameter in Network Attributes is not valid for this

adapter. Use the CHGNETA command to change MDMCNTRYID .

Table 2. Failing items details

Failing Item Description Document Description

AJDG301 Licensed Internal Code See the service documentation for instructions.
AJDGP01 I/O card Licensed Internal Code See the service documentation for instructions.
GCCNET Network equipment
IOA Communications adapter card See the service documentation for instructions.
UCCCONF Configuration

(B019) Reference codes

This SRC might indicate a communications error.

332 System i® and System p®: Reference codes

B019

Find the unit reference code in the following table. For more on the Failing Item column entries, see Table
2. Failing items details, which follows the reference code table below.

Table 1. (B019) Reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
7004 ABEND due to unrecoverable condition. AJDGP01
7005 IOP activation failed.
7006 Error in OS/400 code.
7007 Licensed Internal Code error AJDG301
7008 Frame reject received from remote system. AJDGP01
7009 Frame reject type Y received/sent
700A IDLC sent a frame reject. GCERMT
700B IDLC frame retry limit reached.
700C to 700F, 7010 Remote configuration error.
7011 IOP activation failed. CCELCFG
AJDG301
7012 IDLC line description configuration error
8001 ABEND due to unrecoverable condition. AJDGP01
8002 IOP activation failed. AJDGP01
8003 ABEND due to failure to communicate with system.
8004 I/O adapter hardware error detected IOA
8005 ABEND due to unrecoverable condition. AJDGP01
8006 IOP activation failed.
8007 Error in OS/400 code.

Table 2. Failing items details

Failing Item Description Document Description

AJDG301 Licensed Internal Code See the service documentation for instructions.
AJDGP01 I/O card Licensed Internal Code See the service documentation for instructions.
CCELCFG IDLC line description configuration error Communications Configuration
GCERMT Data link or remote data communications
equipment
IOA Communications adapter card See the service documentation for instructions.

(B020) Reference codes

This SRC might indicate a communications error.

Find the unit reference code in the following table. For more on the Failing Item column entries, see Table
2. Failing items details, which follows the reference code table below.

Table 1. (B020) Reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
8001 ABEND due to unrecoverable condition. AJDGP01

Reference codes 333

B020

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
8004 I/O adapter hardware error detected FI00719
8005 ABEND due to unrecoverable condition. AJDGP01
8020, 8030 System log entry only, no service action required
9001 ABEND due to unrecoverable condition. AJDGP01
FI00719
9004 IOP activation failed. AJDGP01
FI00719

Table 2. Failing items details

Failing Item Description Document Description

AJDG301 OPRS OS/400 licensed program Service Functions; APAR or LICTR
AJDGP01 I/O processor Licensed Internal Code Service Functions; APAR or LICTR
CCFNWIC NWI configuation error Communications Configuration
CCFPARM IDLC MAXFRAME parameter Communications Configuration
CCFRMTC Configuration problem in remote equipment Communications Configuration
GCFIINT ISDN physical interface
GCFNET Network equipment
GCFNTWK External devices or network
GCFRMT Data link or remote data communications
equipment
GCFTOPO ISDN network topology
UCFCONF Configuration

(B021) Reference codes

This SRC might indicate a communications error.

Find the unit reference code in the following table. For more on the Failing Item column entries, see Table
2. Failing items details, which follows the reference code table below.

Table 1. (B021) Reference codes

334 System i® and System p®: Reference codes

B021

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
C242 Overrun error; threshold limit reached UNM32
UNM31
UNM31
C243 Underrun error; threshold limit reached UNM32
UNM31
UNM31
C244 Aborted frames received; threshold limit reached UNM36
UNU01
74F1663
UNM31
UNM31
C250 Number of frames retransmitted exceeded threshold limit UNM36
UNU01
UNM31
UNM31
C251 Send sequence (Ns) count error threshold limit reached UNM36
UNU01
UNM31
UNM31
FI00730
C255 Set-asynchronous-balance-mode frame received in data mode UNM36
UJE34
C257 Disconnect mode frame received when transmitting information UNM36
FI00730
C259 Unsolicited disconnect mode frame with final set received UNM36
UNM31
C25C Frame with an incorrect command field received UNM36
FI00730
C25D Frame with an incorrect format received UNM36
FI00730
C25E Frame with an incorrect NR count received UNM36
FI00730
C25F I-frame with oversized data received UNM36
AJDG301
UNM31
C260 Disconnect retry limit reached UNM36
UNU01
C261 Frame reject type W received FI00730
UNM36
C262 Frame reject type X received FI00730
UNM36
C263 Frame reject type Y received AJDG301
FI00730
C264 Frame reject type Z received FI00730
UNM36
C269 Frame with an incorrect format received UNM36
FI00730
C270 Wrong command received by communications controller FI00730
C274 Number of stations greater than allowed in configuration AJDG301
FI00730

Reference codes 335

B021

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
C275 I/O card LIC followed incorrect procedure FI00730
C276, C278 Wrong command value received by communications IOP FI00730
C279 Wrong data length received by communications controller FI00730
C27A Wrong command value received by communications IOP FI00730
C27C Communications controller task ended abnormally; type 1 FI00730
C281 Wrong command value received by communications IOP AJDG301
C28B to C28C Wrong command value received by communications IOP FI00730
C290 Wrong command value received by communications IOP AJDG301
FI00730
C291 to C293 Licensed Internal Code sent incorrect command values AJDG301
FI00730
C294 Licensed Internal Code sent incorrect command values AJDG301
FI00730
UNM31
C295 Wrong command value received by communications IOP AJDG301
FI00730
UNM31
C296 Licensed Internal Code sent incorrect command values AJDG301
FI00730
UNM31
C297 Licensed Internal Code sent incorrect command values AJDG301
FI00730
C298 Licensed Internal Code sent incorrect command values AJDG301
FI00730
UNM31
C299 I/O card LIC followed incorrect procedure FI00730
C2A0 Wrong command value received by communications IOP AJDG301
FI00730
C2A6 Frame retry limit reached UNM36
UNM31
UNU01
C2A7 Error when assigning communications controller storage UNM32
FI00730
C2A9 Communications controller storage not available UNM32

There are already two communication traces active on this resource.

C2B0 Terminal endpoint identifier assignment procedure failed UNM36
UNM31
C2B1 Terminal endpoint identifier assignment procedure failed UNM36
C2B2 to C2B3 Terminal endpoint identifier assignment procedure failed UNM36
FI00730
C2B4 Terminal endpoint identifier temporarily removed UNM36
FI00730
C2B5 OS/400 licensed program sent an incorrect configuration AJDG301
C2B7 Manually assigned TEI removed permanently UNM36
UNM31
FI00730
C2C0 OS/400 licensed program sent an incorrect configuration AJDG301

336 System i® and System p®: Reference codes

B021

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
C2C1 OS/400 licensed program sent an incorrect configuration AJDG301
FI00730
C2C2 OS/400 licensed program sent an incorrect configuration AJDG301
FI00730
UNM31
C2C3 OS/400 licensed program sent an incorrect configuration AJDG301
FI00730
C2C4 Configuration or OS/400 licensed program AJDG301
FI00730
C2C5 OS/400 licensed program sent an incorrect configuration FI00730
AJDG301
UNM31
C2C6 to C2C9, OS/400 licensed program sent an incorrect configuration AJDG301
C2CE to C2CF, FI00730
C2D0
C2D4 OS/400 licensed program sent an incorrect configuration FI00730
AJDG301
UNM31
C2D5 OS/400 licensed program sent an incorrect configuration AJDG301
C2D6 OS/400 licensed program sent an incorrect configuration FI00730
AJDG301
UNM31
C2D7 to C2D8 Licensed Internal Code sent incorrect command values AJDG301
C2E3 Licensed Internal Code sent incorrect command values FI00730
C2E5 to C2EB Licensed Internal Code sent incorrect command values AJDG301
FI00730
CA04 No error found AJDG301
FI00730
The threshold counter containing the number of outgoing calls has reached
its limit.
CA06 Outgoing calls rejected, limit exceeded. AJDG301
FI00730
CA18 No error found AJDG301
FI00730
The threshold counter containing the number of outgoing calls has reached
its limit.
CA1A Incoming call rejected, limit exceeded. AJDG301
FI00730
CA1E Controller card detected a buffer assignment error UNM36
CA23 Call rejected; wrong value from remote system UNM36
CA28 Licensed Internal Code sent an incorrect command AJDG301
FI00730
CA2A, CA30, Licensed Internal Code sent incorrect command values AJDG301
CA32 to CA33, FI00730
CA38
CA3E Licensed Internal Code sent an incorrect command AJDG301
FI00730
CA40 Licensed Internal Code sent incorrect command values AJDG301
UNM31
FI00730

Reference codes 337

B021

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
CA42 to CA44, Licensed Internal Code sent incorrect command values AJDG301
CA46 to CA47, FI00730
CA66
CA68 Licensed Internal Code sent an incorrect command UNM31
CA6C Wrong data length received by communications controller AJDG301
FI00730
CA75 Remote equipment did not respond in time-out period UNM36
CA76 ISDN Q.931 restart message received. UNM36
CA77 RESTART ACKNOWLEDGE error; threshold limit reached. 74F1663
UNM36
CA78 ISDN Q.931 protocol error. AJDG301
UNM36
FI00730
CA79 ISDN Q.931 protocol error. UNM36
AJDG301
CA80, CA82 Licensed Internal Code sent incorrect command values AJDG301
FI00730
CA84 PTF is required to enable requested nettype UNM38
AJDG301
FI00730
CA85 to CA86, Licensed Internal Code sent incorrect command values AJDG301
CA88, CA8A, FI00730
CA8C, CA8E,
CA90, CA96
CA98 Licensed Internal Code sent incorrect command values FI00730
AJDG301
CA9A, CA9C, Licensed Internal Code sent incorrect command values AJDG301
CAA0, CAA2, FI00730
CAA4
CAA6 Licensed Internal Code sent incorrect command values FI00730
AJDG301
CAA8, CAAA, Licensed Internal Code sent incorrect command values AJDG301
CAAC, CAAE, FI00730
CAB0
CAB2 Error during get configuration request UNM32
FI00730
CAB4 Resource or storage not available UNM32
AJDG301
FI00730
CAB5 to CABF OS/400 licensed program sent an incorrect configuration AJDG301
FI00730
CAF0 to CAF1 I/O card Licensed Internal Code stopped because of error FI00730
D200 Loss of synchronization error; threshold limit reached. UNM36
UNU01
74F1663
UNM31
UNM31

338 System i® and System p®: Reference codes

B021

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
D201 Local end code violation, threshold limit reached. UNU01
UNM36
74F1663
UNM31
UNM31
D202 DTSE-IN error; threshold limit reached. UNM35
UNM36
UNM31
UNM31
D203 DTSE-OUT error; threshold limit reached. UNM35
UNM36
UNM31
UNM31
D204 Far end code violation, threshold limit reached. UNM36
UNM31
UNM31
D210 Wrong command received by communications controller AJDG301
FI00730
D212 to D217 Wrong command value sent by OS/400 licensed program AJDG301
FI00730
D219 Wrong adapter type value sent by Licensed Internal Code AJDG301
D21A Wrong slot number value sent by Licensed Internal Code AJDG301
D21B to D21C Wrong command value sent by OS/400 licensed program AJDG301
FI00730
D21D Communications adapter card not installed AJDG301
FI00730
IOA
D21E ISDN channel already in use AJDG301
FI00730
D220 Physical interface could not activate 74F1663
UNM36
IOA
UNM31
D221 Physical interface lost activation 74F1663
UNM36
UNM31
IOA
D223 Loss of received signal message from remote U interface UNM35
UNM31
D224 Loss of power message received from remote U interface UNM35
D225 Loss of ISDN Power Source 1 (PS1) detected by adapter UNM36
74F1663
IOA
D226 Loss of ISDN Power Source 1 (PS1) detected by adapter 74F1663
UNM36
UNM31
IOA
D228 Physical interface temporarily lost synchronization UNM36
IOA
74F1663

Reference codes 339

B021

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
D230 Channelized hardware error detected IOA
FI00730
D232 I/O adapter hardware error detected IOA
FI00730
D233 Error in I/O card Licensed Internal Code FI00730
UNM32
D234 Error when releasing communications controller storage FI00730
D235 Error when assigning communications controller storage UNM32
FI00730
D236 ISDN channel hardware not operational AJDG301
FI00730
D240 to D241 Error in I/O card Licensed Internal Code FI00730
D244 Error when releasing communications controller storage FI00730
D245 Error when assigning communications controller storage UNM32
FI00730
D246 Error in I/O card Licensed Internal Code FI00730
D247 Wrong command value received by communications IOP FI00730
D250 Incorrect command used by I/O card Licensed Internal Code FI00730
D251 Error in I/O card Licensed Internal Code FI00730
D260 to D266 OS/400 licensed program sent an incorrect configuration AJDG301
FI00730
FFFF User suspected communications problem. USER

Table 2. Failing items details

Failing Item Description Document Description

340 System i® and System p®: Reference codes

B021

Failing Item Description Document Description

UNM32 Heavy workload on communications controller Communications Configuration
card
UNM35 Remote ISDN U interface
UNM36 RMTZ Data link or remote data communications
equipment
UNM36 External devices or network
UNM36 Network equipment
UNM38 Required PTF is not installed
UNU01 ISDN physical interface
USER User suspected communications problem.

(B022) Reference codes

This SRC might indicate a communications error.

Find the unit reference code in the following table. For more on the Failing Item column entries, see Table
2. Failing items details, which follows the reference code table below.

Table 1. (B022) Reference codes

(B025) Reference codes

This SRC might indicate a communications error.

Find the unit reference code in the following table. For more on the Failing Item column entries, see Table
2. Failing items details, which follows the reference code table below.

Table 1. (B025) Reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
A000 Input value error in I/O card Licensed Internal Code AJDGP01
A001 Input value error in I/O card Licensed Internal Code AJDG301
A013 Wrong configuration data given to Ethernet controller AJDG301
A01B, A209 Input value error in I/O card Licensed Internal Code AJDG301
A404 Ethernet adapter card error IOA
AJDGP01
A6D5 to A6D6 Wrong configuration data given to Ethernet controller AJDG301
A6D9 Ethernet adapter card error IOA
FI00722
IOP
A6E3 Ethernet adapter or network device cabling error. FI00722
UJE40
IOA
A6F2 Configured line speed not supported by network. UJE35
A6F3 Configuration of DUPLEX parameter not supported by network. UJE35
A6F4 Unable to establish a network link. UJE35
FI00722
A800 MAXFRAME value in CRTLINETH command too large. CTPLPDU
A801 Adapter does not support user-configured adapter address CTPNADR
B000 System log entry only, no service action required
B001 Automatic recovery has been attempted on the ethernet port

This error is logged for information only. No service action is required.

Table 2. Failing items details

Failing Item Description Document Description

AJDG301 Licensed Internal Code Service Functions; APAR or LICTR
AJDG301 Licensed Internal Code See the service documentation for instructions.
AJDGP01 I/O card Licensed Internal Code See the service documentation for instructions.
AJDGP01 I/O card Licensed Internal Code See the service documentation for instructions.
AJDGP01 I/O card Licensed Internal Code See the service documentation for instructions.
CTPLPDU MAXFRAME value in CRTLINETH command Communications Configuration
CTPNADR ADPTADR value in CRTLINETH command Communications Configuration
IOA Ethernet network adapter card Repair and Parts; removal and installation
procedures
IOP I/O processor card See the service documentation for instructions.
UJE35 SSAP value in CRTLINETH command Communications Configuration

346 System i® and System p®: Reference codes

B025

Failing Item Description Document Description

UJE35 MAXCTL value in CRTLINETH command Communications Configuration
UJE35 LINESPEED value in CRTLINETH command Communications Configuration
UJE35 DUPLEX value in CRTLINETH command Communications Configuration
UJE36 LANACKFRQ value in CRTCTL_____command Communications Configuration
UJE36 DSAP value in CRTCTL_____command Communications Configuration
UJE39 Remote computer equipment Communications Configuration
UJE40 Network Termination, Network or Network
devices
USER User suspected communications problem.

(B026) Reference codes

This SRC might indicate a communications error.

Find the unit reference code in the following table. For more on the Failing Item column entries, see Table
2. Failing items details, which follows the reference code table below.

Table 1. (B026) Reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
A000 I/O card Licensed Internal Code error FI00730
A001 Input value error in I/O card Licensed Internal Code FI00730
AJDG301
A002 Input value error in I/O card Licensed Internal Code FI00730
FI00730
A003 Procedure error in I/O card Licensed Internal Code FI00730
FI00730
A013 Address error on communications IOP card IOA
A01B Input value error in I/O card Licensed Internal Code AJDG301
A01C Input value error in I/O card Licensed Internal Code AJDG301
FI00730
A01D Input value error in I/O card Licensed Internal Code AJDG301
A01F Input value error in I/O card Licensed Internal Code FI00730
AJDG301
A020 Input value error in I/O card Licensed Internal Code FI00730
A022 Input value error in I/O card Licensed Internal Code AJDG301
A027 Input value error in I/O card Licensed Internal Code FI00730
A028 Input value error in I/O card Licensed Internal Code FI00730
AJDG301
A02A Input value error in I/O card Licensed Internal Code FI00730
FI00730
A02B I/O card Licensed Internal Code error FI00730
AJDG301
A02C Input value error in I/O card Licensed Internal Code FI00730
AJDG301
A02D Input value error in I/O card Licensed Internal Code AJDG301

Reference codes 347

B026

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
A030 Procedure error in I/O card Licensed Internal Code FI00730
A201 Communications adapter detected storage access error FI00730
FI00730
A203 to A204 Input value error in I/O card Licensed Internal Code AJDG301
A205 Licensed Internal Code received not correct response FI00730
A206 Input value error in I/O card Licensed Internal Code AJDG301
A209 Procedure error in I/O card Licensed Internal Code AJDG301
A20A to A20B Input value error in I/O card Licensed Internal Code AJDG301
A20C Input value error in I/O card Licensed Internal Code FI00730
AJDG301
A210 Procedure error in I/O card Licensed Internal Code FI00730
A213 I/O card Licensed Internal Code error FI00730
A300 to A302 I/O adapter hardware error detected IOA
IOP
A40B Address error on communications IOP card IOA
A6C2 I/O card Licensed Internal Code error AJDG301
A6D4 Procedure error in I/O card Licensed Internal Code AJDG301
A6D5 Input value error in I/O card Licensed Internal Code AJDG301
A6D6 Adapter card detected not valid data AJDG301
A6D7 Adapter card detected not valid data FI00730
A710 I/O adapter hardware error detected IOA
FFFF User suspected communications problem. USER

Table 2. Failing items details

Failing Item Description Document Description

AJDG301 Licensed Internal Code See the service documentation for instructions.
IOA Communications adapter card See the service documentation for instructions.
IOP Communications I/O processor card See the service documentation for instructions.
UJ9GC configuration See the service documentation for instructions.
UJ9GF External devices or network See the service documentation for instructions.
USER User suspected communications problem. See the service documentation for instructions.

(B028) Reference codes

This SRC might indicate a communications error.

B028

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
57F0 Send sequence counter error; error limit per 256 reached FI00751
FI00701
FI00704
UJ0E3
57F1 Receive sequence counter error; error limit per 256 reached FI00751
FI00700
57F2 Response time-out error; error limit per 256 reached FI00700
UJ0E3
FI00751
FI00704
UJJ35
FI00705
AJDG301
5886 Automatic call unit switched link time-out; no answer FI00703
IOA
FI00702
UJ0E3
5E01 Call error; incoming call received during outgoing call UJ0E3
6320 Automatic call unit has abandon-call attempt FI00700
UJA35
FI00703
IOA
FI00702
6322 Abandon call retry error; incorrect number length UJA35
FI00703
6870 Automatic call unit power turned off FI00703
FI00702
IOA
8011 IOP activation failed. UJE34

The MDMCNTRYID parameter in Network Attributes is not set. Use the

CHGNETA command to set MDMCNTRYID.
8013 IOP activation failed. UJE34

The MDMCNTRYID parameter in Network Attributes is not valid for this

Table 2. Failing items details

Failing Item Description Document Description

74F1624 ISDN channel hardware Repair and Parts; removal and installation
procedures
AJDG301 Licensed Internal Code See the service documentation for instructions.

354 System i® and System p®: Reference codes

B028

Failing Item Description Document Description

IOA Communications adapter card Repair and Parts; removal and installation
procedures
IOP Communications I/O processor card Repair and Parts; removal and installation
procedures
UJ0E3 Communications network equipment
UJ0E9 Communications network equipment
UJA35 CNNNBR value in CRTLINX25___command Communications Configuration
UJE34 Configuration or OS/400 licensed program Communications Configuration
UJE34 No failure found Communications Configuration
UJJ35 MAXPKTSIZE in CRTLINX25 command Communications Configuration
UJJ35 ACRSRCNAME value in CRTLINX25 command Communications Configuration
UJJ35 FRAMERTY value in CRTLINX25 command Communications Configuration
UJJ35 X25DCE value in CRTLINX25 command Communications Configuration
UJJ35 DSRDRPTMR value in the CRTLINX25 Communications Configuration
command
UJJ35 INTERFACE value in CRTLINX25 command Communications Configuration
UJJ35 DFTWDWSIZE value in CRTLINX25 command Communications Configuration
UJJ35 RMTANSTMR value in the CRTLINX25 Communications Configuration
command
UJJ35 IDLTMR value in CRTLINX25 command Communications Configuration
UJJ35 RSRCNAME value in CRTLINX25 command Communications Configuration
UJJ35 DIALRTY value in CRTCTL____ command Communications Configuration
UJJ35 CTSTMR value in CRTLINX25 command Communications Configuration
USER User suspected communications problem.

(B030) Reference codes

This SRC might indicate a communications error.

Find the unit reference code in the following table. For more on the Failing Item column entries, see Table
2. Failing items details, which follows the reference code table below.

Table 1. (B030) Reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
1FFF Severe error detected by I/O card Licensed Internal Code FI00730
FI00731
A000 Input value error in I/O card Licensed Internal Code FI00730
A001 Input value error in I/O card Licensed Internal Code FI00730
AJDG301
A013 Wrong config data given to local area network controller AJDG301
A02C Input value error in I/O card Licensed Internal Code FI00730
AJDG301
A205 I/O card Licensed Internal Code received unexpected response FI00730
E000 An undesirable connection attempt on PORT A has been made FI00701

Reference codes 355

B030

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E001 An undesirable connection attempt on PORT B has been made FI00701
E00A Station has entered a wrapped configuration FI00701
FI00731
GW8DNET
E00F Station has recovered from a wrapped configuration GW8TEMP
E010 One of the internal data path configurations failed FI00731
E011 Optical bypass switch is stuck in bypassed position FI00735
FI00731
E012 Link Confidence Test failed on PORT A FI00701
GW8DNET
FI00731
E013 Link Confidence Test failed on PORT B FI00701
GW8DNET
FI00731
E016 Physical connection mgmt for PORT A was not able to proceed FI00731
GW8DNET
E017 Physical connection mgmt for PORT B was not able to proceed FI00731
GW8DNET
E018 PORT A link has been terminated due to high error rate FI00701
GW8DNET
FI00731
E019 PORT B link has been terminated due to high error rate FI00701
GW8DNET
FI00731
E01A Active port has switched from primary to backup connection FI00701
FI00731
GW8DNET
FFFF User suspected communications problem. UW8UPPR

Table 2. Failing items details

Failing Item Description Document Description

AJDG301 OPSP OS/400 Licensed Internal Code Service Functions; APAR or LICTR
GW8DNET Distributed Data Interface Network
GW8TEMP No failure found
UW8UPPR User suspected communications problem.

(B038) Reference codes

This SRC might indicate a communications error.

Find the unit reference code in the following table. For more on the Failing Item column entries, see Table
2. Failing items details, which follows the reference code table below.

Reference codes 361

B040

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
501C, 501E Command value error in I/O card Licensed Internal Code FI00730
50E0 Wrong or no external communications cable installed UJA34
UJA34
FI00701
IOA
50E1 Communications line already in use AJDG301
UJA34
UJA34
50E3 to 50E4 Wrong command value sent by OS/400 licensed program AJDG301
UJA34
50E5 Incorrect command value sent by Licensed Internal Code AJDG301
UJA34
UJA34
UJA34
50E6 to 50E7 Incorrect command value sent by Licensed Internal Code AJDG301
FI00730
UJA34
UJA34
50E8 Wrong command value sent by OS/400 licensed program AJDG301
50E9, 50EB Incorrect command value sent by Licensed Internal Code AJDG301
UJA34
50EC to 50ED Wrong command value sent by OS/400 licensed program AJDG301
50EE Incorrect command value sent by Licensed Internal Code AJDG301
50F1 Communications line not installed AJDG301
UJA34
IOA
50F5 Network uncontrolled-not-ready warning; information only UJA34
50F6 Network controlled-not-ready warning; information only UJA34
50F8 Adapter card transmit error IOA
FI00704
5203 I/O card Licensed Internal Code resource not available FI00730
52E0 Incorrect command used by I/O card Licensed Internal Code FI00730
52E1 Wrong procedure used in I/O card Licensed Internal Code FI00730
52E2 I/O card Licensed Internal Code resource not available UJA33
UJA34
UJA34
52E4 Wrong command value sent by OS/400 licensed program AJDG301
UJA34
52E7 X.21 network not in the ready or receive-data state FI00704
UJ0E3
FI00701
IOA
52E8 to 52E9 Command value error in I/O card Licensed Internal Code FI00730
52EA I/O card Licensed Internal Code error FI00730
5301 Adapter card receive error FI00730
IOA
5302 Adapter card transmit error FI00730
IOA

362 System i® and System p®: Reference codes

B040

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
5401 Communications adapter card interrupt not expected FI00730
IOA
54E1 Communications line not operational IOA
UJA34
56E8 Clear-to-send not active on modem interface UJ0E3
UJA34
FI00704
FI00701
IOA
56E9 Clear-to-send signal failed to drop on modem interface FI00704
FI00701
IOA
56EA Clear-to-send signal dropped on modem interface UJ0E3
FI00704
UJA34
IOA
FI00701
56ED Data-set-ready turn-on time-out on modem interface FI00701
FI00704
IOA
AJDG301
56F1 Data-set-ready dropped on modem interface FI00704
FI00701
UJ0E3
IOA
A000 Input value error in I/O card Licensed Internal Code FI00730
A001 Input value error in I/O card Licensed Internal Code FI00730
AJDG301
A002 Input value error in I/O card Licensed Internal Code FI00730
A003 Input value error in I/O card Licensed Internal Code AJDG301
A00E Procedure error in Licensed Internal Code AJDG301
A016 Input value error in I/O card Licensed Internal Code AJDG301
FI00730
A01B to A01D Input value error in I/O card Licensed Internal Code AJDG301
A02D Input value error in I/O card Licensed Internal Code AJDG301
FI00730
A201 Frame Relay I/O adapter card storage not available FI00730
A204 Input value error in I/O card Licensed Internal Code AJDG301
A205 I/O card Licensed Internal Code received unexpected response AJDG301
A209 to A20B Input value error in I/O card Licensed Internal Code AJDG301
A210 Communications adapter card error FI00701
IOA
A213 Severe error detected by I/O card Licensed Internal Code FI00730
A800 Network not responding. UJ0E3
FI00730
A801 Too many frames with bad receive sequence counts UJ0E3
FI00730
A807 Network not responding. UJ0E3

Reference codes 363

B040

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
AB00 to AB02 Incorrect configuration data for Frame Relay LIC AJDG301
FFFF User suspected communications problem. UJ4UPPR

Table 2. Failing items details

Failing Item Description Document Description

AJDG301 Licensed Internal Code See the service documentation for instructions.
AJDG301 Licensed Internal Code See the service documentation for instructions.
IOA Communications adapter card See the service documentation for instructions.
UJ0E3 Communications network equipment See the service documentation for instructions.
UJ4UPPR User perceived problem
UJA33 Too many communications lines in use Communications Management
UJA34 MAXFRAME value in CRTNWIFR command Communications Configuration
UJA34 ACRSRCNAME value in CRTNWIFR command See the service documentation for instructions.
UJA34 MAXOUT value in CRTNWIFR command Communications Configuration
UJA34 AUTOANS, AUTODIAL, SWTCNN, CNN See the service documentation for instructions.
values in CRTNWIFR command
UJA34 No failure found Communications Configuration
UJA34 NRZI value in CRTNWIFR command Communications Configuration
UJA34 CTSTMR value in CRTNWIFR command See the service documentation for instructions.
UJA34 RSRCNAME value in the CRTNWIFR command Communications Configuration
UJA34 SNBU, MODEMRATE, DUPLEX values in Communications Configuration
CRTNWIFR command
UJA34 INTERFACE value in CRTNWIFR command See the service documentation for instructions.
UJA34 LINESPEED value in CRTNWIFR command Communications Configuration

(B045) Reference codes

This SRC might indicate a communications error.

Find the unit reference code in the following table.

Table 1. (B045) Reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
0C00 I/O card Licensed Internal Code failed FI00730

(B070) Reference codes

For more on the Failing Item column entries, see Table 2. Failing items details, which follows the
reference code table below.

Table 1. (B070) Reference codes

364 System i® and System p®: Reference codes

B070

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
0000 Device no response time-out; temporary error FI00601
FI00602
FI00610
0001 WS IOP detected error when transmitting data FI00602
FI00601
Is the problem intermittent? GAU7777
GAU8888
Yes: Perform the following procedures: FI00610
1. INT-PIP5 FI00615
2. INT-PIP14

No: Perform TWSIP01.

0003 WS IOP detected parity error from device FI00602
FI00601
Is the problem intermittent? GAU7777
FI00610
Yes: Perform the following procedures:
1. INT-PIP5
2. INT-PIP14

Perform TWSIP01.
0090 WS IOP detected no status change from device FI00601
FI00610
Perform TWSIP01.
0091 WS IOP detected busy time-out from device FI00601
FI00610
Perform TWSIP01.
0100 Device no response time-out; temporary error FI00601
FI00602
FI00610

366 System i® and System p®: Reference codes

B070

Reference codes 367

B070

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
0108 WS IOP detected device power turned off, and then on GAUEEEE
FI00601
Perform TWSIP01.
0109 WS IOP detected wrong device response to start command FI00601
FI00610
Perform TWSIP01.
0111 WS IOP detected wrong keyboard scan code from display FI00601
AJLYD01
Perform TWSIP01. FI00610
0120 Device detected wrong command or device ID from WS IOP FI00601
AJLYD01
Perform TWSIP01. FI00610
0121 Device detected not valid value from WS IOP FI00601
AJLYD01
Perform TWSIP01. FI00610
0122 Device detected storage or data overrun FI00601
AJLYD01
Perform TWSIP01. FI00610
0123 Device detected null or attribute exception error FI00601
FI00610
Perform TWSIP01.
0124 Device detected wrong start command from WS IOP FI00601
AJLYD01
Perform TWSIP01. FI00610
0125 WS IOP detected wrong exception response from device FI00601
FI00610
Perform TWSIP01.
0126 WS IOP detected not valid pass-through command GAU9999
FI00610
Perform TWSIP01.
0149 WS IOP detected wrong request or response from device FI00601
FI00610
Perform TWSIP01.
0170 WS IOP detected error downloading printer definition table AJDG301
FI00601
0171 WS IOP detected error downloading printer definition table FI00601
AJLYD01
0172 WS IOP detected error downloading printer definition table CAUPDT
AJDG301
FI00601
0173 WS IOP detected error downloading printer definition table CAUPDT
FI00601
0174 WS IOP detected error unloading printer definition table FI00601
AJLYD01
0175 WS IOP detected device configuration error FI00601
AJLYD01
0176 to 0177 WS IOP detected error downloading LIC to device GAUDMCC
FI00601
0181 Wrong magnetic stripe reader response FI00605
MAUFFFF
Perform TWSIP01. FI00601
FI00610

368 System i® and System p®: Reference codes

B070

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
0182 WS IOP detected wrong device type from device FI00601

Perform TWSIP01.
0183 WS IOP detected wrong display size value FI00601

Perform TWSIP01.
0184 WS IOP detected wrong keyboard identification FI00601

Verify that the correct keyboard is attached correctly to the workstation.

If the correct keyboard is attached correctly to the workstation, perform

TWSIP01.
0189 Wrong magnetic stripe reader or light pen status FI00601
FI00605
Perform TWSIP01. FI00607
FI00610
0190 WS IOP detected no status change from device FI00601
FI00610
Is the problem intermittent? GAU7777

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
0223 WS IOP detected start command to printer was lost FI00604
FI00602
FI00610
0224 Device detected wrong start command from WS IOP FI00604
AJLYD01
FI00610
0225 WS IOP detected wrong exception response from device FI00604
FI00610
0226, 0230 to 0239, Printer detected equipment error FI00604
0240 to 0248
0249 WS IOP detected wrong request or response from device FI00604
FI00610
026X, 027X, 028X Printer detected equipment error FI00604

See printer documentation for more information.

0290 WS IOP detected no status change from device FI00604
FI00610
0291 WS IOP detected busy time-out from device FI00604
FI00610
02A0 to 02AF, Printer detected equipment error FI00604
02FF
Consult the printer’s manual for additional information.
A000 Too many devices active on the workstation IOP GAUBBBB

This error occurs if you attempted to activate more workstations than

allowed.

Switch off power to (or remove) one or more of the display stations (except
for the console) that are attached to this workstation I/O processor.
Perform an initial program load (IPL) from the control panel to correct the
problem.

Refer to the local workstation diagrams for the location of workstations if

necessary.
B000 WS IOP fails to report part, model and serial number FI00610

Perform TWSIP01.
C000 WS IOP error not known AJLYD01
FI00610
D000 Work Station IOA start-up test error FI00610
D010 WS IOP storage failure corrected FI00610

Perform TWSIP01.
D011 WS IOP card storage failure FI00610
D021 WS IOP detected errors on all cables FI00602
FI00601
FI00610
FI00615
D022 WS IOP parity errors detected on all cables FI00602
FI00601
FI00610
FI00615

Reference codes 371

B070

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
D023 WS IOP detected errors on some, but not all cables FI00602
FI00601
Perform TWSIP01. FI00610
E000 WS IOP or IOA error during working operation AJLYD01
FI00610
F000 WS IOP or IOA operating system program error AJLYD01
FI00719

Table 2. Failing items details

Failing Item Description Document Description

AJDG301 OS/400 licensed program Service Functions; APAR or LICTR
AJDGP01 LIC - Input/Output Processor Licensed Internal Service Functions; APAR or LICTR
Code
AJLYD01 Work Station IOP or IOA system Licensed Service Functions; APAR or LICTR
Internal Code
CAUPDT Device Licensed Internal Code change Communications Configuration
GAU7777 Electrical interference
GAU8888 Other work station on port is failing
GAU9999 Error occurred with pass-through command
GAUBBBB Too many work stations are active on the
workstation IOP
GAUDMCC Device Licensed Internal Code change
GAUEEEE Active device turned off
MAUFFFF Magnetic stripe Refer to I/O device service information
UAUFF00 User suspected problem.

(B075) Workstation adapter console reference codes

The workstation adapter console detected a failure.
1. Look at characters 5 through 8 of the top 16 character line of function 11 (4 rightmost characters of
word 1). These 4 characters are the unit reference code.
2. Find the unit reference code in the following table.

For more on the Failing Item column entries, see Table 2. Workstation adapter console failing items
details, which follows the reference code table below.

Table 1. (B075) Workstation adapter console reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
0101 WS IOP detected error when transmitting data FI00601
GXC7777
Perform WSCIP01. FI00631
FI00730
0103 WS IOP detected parity error from device FI00601
GXC7777
Perform WSCIP01. FI00631
FI00730

372 System i® and System p®: Reference codes

B075

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
0104 Device detected parity error from WS IOP FI00601
GXC7777
Perform WSCIP01. FI00631
FI00730
0105 WS IOP detected error when transmitting data FI00601
GXC7777
Perform WSCIP01. FI00631
FI00730
0106 WS IOP detected wrong data from device FI00601
FI00631
Perform WSCIP01. GXC7777
FI00730
0107 WS IOP detected wrong address from device FI00601
GXC7777
Perform WSCIP01. FI00730
0108 WS IOP detected device power turned off, and then on GXCEEEE
FI00601
Perform WSCIP01.
0109 WS IOP detected wrong device response to start command FI00601
FI00615
Perform WSCIP01.
0111 WS IOP detected wrong keyboard scan code from display FI00601
FI00730
Perform WSCIP01.
0120 Device detected wrong command or device ID from WS IOP FI00601
FI00730
Perform WSCIP01.
0121 Device detected not valid value from WS IOP FI00601
FI00730
Perform WSCIP01.
0122 Device detected storage or data overrun FI00601
FI00730
Perform WSCIP01.
0123 Device detected null or attribute exception error FI00601
FI00730
Perform WSCIP01.
0124 Device detected wrong start command from WS IOP FI00601
FI00730
Perform WSCIP01.
0125 WS IOP detected wrong exception response from device FI00601
FI00730
Perform WSCIP01.
0126 WS IOP detected not valid pass-through command GXC9999
FI00730
Perform WSCIP01.
0149 WS IOP detected wrong request or response from device FI00601
FI00730
Perform WSCIP01.
0190 WS IOP detected no status change from device FI00601
GXC7777
Perform WSCIP01. FI00730
0191 WS IOP detected busy time-out from device FI00601
FI00730
Perform WSCIP01.

Reference codes 373

B075

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
0201 WS IOP detected error when transmitting data FI00604
GXC7777
Perform WSCIP01. FI00631
FI00730
0203 WS IOP detected parity error from device FI00604
GXC7777
Perform WSCIP01. FI00631
FI00730
0204 Device detected parity error from WS IOP FI00604
GXC7777
Perform WSCIP01. FI00631
FI00730
0205 WS IOP detected error when transmitting data FI00604
GXC7777
Perform WSCIP01. FI00631
FI00730
0206 WS IOP detected wrong data from device FI00604
FI00631
Perform WSCIP01. FI00730
0207 WS IOP detected wrong address from device FI00604
GXC7777
Perform WSCIP01. FI00730
0208 WS IOP detected device power turned off, and then on GXCEEEE
FI00604
0209 WS IOP detected wrong device response to start command FI00604
FI00730
0211 Printer detected equipment error FI00604
FI00730
0221 Device detected not valid value from WS IOP FI00604
FI00730
0224 Device detected wrong start command from WS IOP FI00604
FI00730
0225 WS IOP detected wrong exception response from device FI00604
FI00730
0290 WS IOP detected no status change from device FI00604
FI00730
0291 WS IOP detected busy time-out from device FI00604
FI00730
5000 Wrong command sent by Licensed Internal Code AJDG301
5001 Procedure error in Licensed Internal Code AJDG301
5002 Procedure error in Licensed Internal Code CXCTEMP
AJDG301
Procedure error in machine instructions
5006 Procedure error in Licensed Internal Code AJDG301
5007 Procedure error in Licensed Internal Code AJDG301
CXCMSTA
5009 Incorrect command value sent by Licensed Internal Code AJDG301
500A Procedure error in Licensed Internal Code AJDG301

374 System i® and System p®: Reference codes

B075

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
500D Incorrect command value sent by Licensed Internal Code AJDG301
CXCMAXI
5022 Procedure error in Licensed Internal Code AJDG301
5206 Communications controller storage not available CXCBUSY
56EA Clear-to-send signal dropped on modem interface GXCLINK
FI00704
CXCCTSV
FI00719
FI00701
56ED Data-set-ready turn-on time-out on modem interface FI00701
FI00704
FI00719
AJLAG01
56F1 Data-set-ready dropped on modem interface FI00704
FI00701
GXCLINK
FI00719
5710 Nonproductive receive time-out while receiving from remote CXCNPRT
FI00700
FI00705
FI00704
GXCLINK
FI00701
FI00719
5712 No data received from remote equipment; time-out AJLAG01
CXCENCD
CXCINAT
GXCLINK
FI00704
FI00705
FI00700
CXCSTAD
FI00701
CXCDTAR
FI00719
CXCMRTY
5715 Remote equipment did not respond causing an idle-time-out GXCLINK
CXCRPTO
FI00701
FI00704
CXCMRTY
FI00705
CXCENCD
FI00700
CXCDTAR
FI00719
5718 Retry limit reached for sending frames to remote equipment GXCLINK
FI00705
FI00704
FI00700
CXCMRTY
FI00719
FI00701
5719 Retry limit reached for sending frames to remote equipment FI00700

Reference codes 375

B075

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
5720 Retry limit reached for sending poll frame to remote FI00700
CXCMODU
5721 Could not send frame to remote equipment; local problem FI00704
CXCDTAR
FI00701
FI00719
FI00730
5722 Wrong command value sent by OS/400 licensed program AJLAG01
CXCSTAD
A000 Too many devices active on the workstation IOP GXCBBBB
B000 WS IOP fails to report part, model and serial number FI00615

Perform WSCIP01.
C000, D000 WS IOP error not known AJLAG01
D001 Wrong or no external communications cable installed FI00631
AJLAG01
F003 WS IOA buffer utilization threshold exceeded temporarily AJLAG01
FFFF User believes there is a problem UXCFF00

Reference code FFFF is assigned by the ANZPRB (Analyze Problems) for

user-detected errors. Run ANZPRB again if the problem still exists or look
in the problem log (WRKPRB) for possible failing FRUs.

Table 2. Workstation adapter console failing items details

Failing Item Description Document Description

AJDG301 Vertical Licensed Internal Code Service Functions; APAR or LICTR
AJLAG01 Licensed Internal Code Service Functions; APAR or LICTR
CXCBUSY Too many communications lines in use Communications Configuration
CXCCONF Configuration or OS/400 licensed program Communications Configuration
CXCCPTO CNNPOLLTMR value in CRTLINSDLC Communications Configuration
command
CXCCTSV CTSTMR value in CRTLINSDLC command Communications Configuration
CXCDTAR LINESPEED value in CRTLINSDLC command Communications Configuration
CXCENCD NRZI value in CRTLINSDLC command Communications Configuration
CXCINAT INACTTMR value in CRTLINSDLC command Communications Configuration
CXCMAXI MAXFRAME value in CRTLINSDLC command Communications Configuration
CXCMODU MODULUS value in CRTLINSDLC command Communications Configuration
CXCMRTY FRAMERTY value in CRTLINSDLC command Communications Configuration
CXCMSTA MAXCTL value in CRTLINSDLC command Communications Configuration
CXCNPRT NPRDRCVTMR value in CRTLINSDLC Communications Configuration
command
CXCRPTO IDLTMR value in CRTLINSDLC command Communications Configuration
CXCSNDT SHMNODE value in CRTLINSDLC command Communications Configuration
CXCSTAD STNADR value in CRTCTL_____command Communications Configuration
CXCTEMP No failure found Communications Configuration

376 System i® and System p®: Reference codes

B075

Failing Item Description Document Description

GXC7777 Electrical interference
GXC8888 Other workstation on port is failing
GXC9999 Error occurred with pass-through command
GXCBBBB Too many devices are active on the workstation
IOP
GXCEEEE Active device turned off
GXCLINK Communications network equipment
UXCFF00 User suspected problem

(B1xx) Service processor firmware reference codes

A B1xx reference code indicates that an event or exception occurred in service processor firmware. To
resolve any B1xx reference code, determine if the SRC requires a service action or if it is for tracking
purposes only.

Diagnostics analyze an event when it occurs to determine if the event requires service or if the event will
only be recorded for tracking purposes and future reference. The determination is based on machine type,
model, installed features, configuration, topology and activations at the time of the event. If you do not
find the SRC in a serviceable event view then it is a tracking event only and does not require service.
Tracking events appear as ″informational″ or ″Misc.″ or ″temp″ in the i5/OS Product Activity log and the
Advanced System Manage Interface (ASMI). Serviceable event views are the AIX Diagnostics Results Log,
the i5/OS Problem Log, the i5/OS Service Action Log (SAL), the HMC Service Focal Point, the Integrated
Virtualization Manager Service Focal Point, the Linux Diagnostic Messages Log, the system control panel,
or ASMI listed under serviceable events.

See “(B1xx) Service processor firmware reference code descriptions” on page 378 for a description of the
SRC.

Determine whether service action is needed or not, it is based upon where to work with the B1xx SRC:
1. Is the system managed by an HMC?
Yes: HMC. See “Hardware Management Console (HMC)” on page 378 in the following table.
No: Continue.
2. Is the system console available?
Yes:
– For AIX see “AIX” on page 378 in the following table.
– For Linux see “Linux” on page 378 in the following table.
– For i5/OS see “i5/OS” on page 378 in the following table.
– For Integrated Virtualization Manager see “Integrated Virtualization Manager” on page 378 in
the following table.
No: Continue.
3. The system console is not available.
v If you have a PC you can attach to one of the HMC ports and launch a browser, then work on the
SRC by looking at the Advanced System Management Interface (ASMI). See “Advanced System
Management Interface (ASMI)” on page 378 in the following table.
v Otherwise work on the SRC from the control panel. See “Control Panel” on page 378 in the
following table.

Table 1. How to determine the nature of a (B1xx) reference code

Reference codes 377

B1xx

Where you found the How to determine the nature of the SRC
SRC
Hardware Search for the SRC in the Service Focal Point on the HMC. See Using Service Focal Point
Management Console for the HMC for help in using the Service Focal Point.
(HMC) v If you find the SRC in the Service Focal Point, it requires a service action. Refer to
Repairing serviceable events for more information on using the Service Focal Point.
v If you do not find the SRC in the Service Focal Point, it is for tracking purposes only and
does not require service.
AIX Look in the diagnostics results log.
v If you find the SRC in the Diagnostics Results Log, it requires a service action.
v If you do not find the SRC in the Diagnostics Results Log, it is for tracking purposes
only and does not require service.
Linux Look in the diagnostics message log.
v If you find the SRC in the Diagnostics Message Log, it requires a service action.
v If you do not find the SRC in the Diagnostics Message Log, it is for tracking purposes
only and does not require service.
Note: The Linux Service Aids must be installed to view the message log: If these Service
Aids are not installed then the message log entries can not be viewed. http://
techsupport.services.ibm.com/server/lopdiags
i5/OS Look in the Service Action Log.
v If you find the SRC in the SAL, it requires a service action.
v If you do not find the SRC in the SAL, it is for tracking purposes only and does not
require service.
Integrated Look in the Service Focal Point. For details, see Using Service Focal Point for the Integrated
Virtualization Manager Virtualization Manager.
v If you find the SRC in the Service Focal Point, it requires a service action.
v If you do not find the SRC in the Service Focal point, it is for tracking purposes only and
does not require service.
Advanced System To determine if the SRC requires repair action or not using ASMI, see the table in
Management Interface Displaying error and event logs.
(ASMI)
If the SRC is in the Miscellaneous event logs row, then no repair action is needed. If the
SRC is in the Error logs row, then service is needed. Select that log and Show Details to get
the full detail format of the log. Then, use the Callout section of the Error and Event Logs
and “(B1xx) Service processor firmware reference code callouts” on page 461.
Control Panel See “(B1xx) Service processor firmware reference code callouts” on page 461 for
instructions. Collect SRC and system information (if possible). See Using the control panel
to collect reference codes and system information.

(B1xx) Service processor firmware reference code descriptions

If you wish to determine if the SRC requires a service action or if it is for tracking purposes only, see
“(B1xx) Service processor firmware reference codes” on page 377 for instructions.

Note: See Table 2. (B1xx) SRC Descriptions for a list of B1xx SRCs and descriptions.

B1xxyyyy where:
xx= Indicates the subsystem where the event or error occurred. See Table 1. (B1xx) Service processor
subsystem IDs.
yyyy= The reason for the event or error (reason code). See Table 3. (B1xx) Service processor reason
codes' ranges.

378 System i® and System p®: Reference codes

A B1xx reference code indicates that an error occurred in a service processor firmware-detected operation.
To resolve any B1xx reference code, use the following procedure:
1. Does the reference code have a format of B151 72xx or B181 72xx that displays during the power-on
process after power was connected to the server but before the server reaches the Power On Standby
state?
Yes: See the description in “Table 1. (B1xx) Service processor early termination reference codes” on
page 462. Perform Failing Item FSPSP02.
No: Continue with the next step.
2. Perform the following:
Reference codes 461
B1xx

a. Using the callout list provided with the error replace the first or next FRU or perform the first or
next isolation procedure in the list starting with the highest priority. For more information, see the
following:
v Finding part locations for links to removal and replacement information
v Service processor isolation procedures for links to service processor isolation procedures
v “(B1xx) Service processor firmware reference code descriptions” on page 378 for a description of
the SRC
b. Perform a slow-boot IPL.
Did the same error code appear?
No: Go to Verifying the repair. This ends the procedure.
Yes: Continue with the next step.
3. Is the new error code the same as the one that brought you to this procedure?
Yes: Replace the next FRU or perform the next procedure in the list.
No: Go to the Start of call procedure to service this new error code. This ends the procedure.

Table 1. (B1xx) Service processor early termination reference codes

Reference Description Action

Code
B1517200 Invalid boot request FSPSP02
B1517201 Service processor failure FSPSP02
B1517202 The permanent and temporary firmware sides are FSPSP02
both marked invalid
B1517203 Error setting boot parameters FSPSP02
B1517204 Error reading boot parameters FSPSP02
B1517205 Boot code error FSPSP02
B1517206 Unit check timer was reset FSPSP02
B151720A Power-off reset occurred. FipsDump should be FSPSP02
analyzed: Possible hardware problem
B1817200 Invalid boot request FSPSP02
B1817201 Service processor failure FSPSP02
B1817202 The permanent and temporary firmware sides are FSPSP02
both marked invalid
B1817203 Error setting boot parameters FSPSP02
B1817204 Error reading boot parameters FSPSP02
B1817205 Boot code error FSPSP02
B1817206 Unit check timer was reset FSPSP02
B1817207 Error reading from NVRAM FSPSP02
B1817208 Error writing to NVRAM FSPSP02
B1817209 The service processor boot watchdog timer FSPSP02
expired and forced the service processor to
attempt a boot from the other firmware image in
the service processor flash memory
B181720A Power-off reset occurred. FipsDump should be FSPSP02
analyzed: Possible software problem

462 System i® and System p®: Reference codes

B3xx

(B3xx) Connection monitoring reference codes

These error codes indicate a problem in the connection monitoring between the Hardware Management
Console and a partition that is running on the managed system. The HMC posts these error codes into
the error log in Service Focal Point but does not report them to the operating systems running on the
managed system.

Use the following links to display the appropriate B3xx reference code table:
v B301
v B302
v B303
v B31x
Table 1. (B301) Connection monitoring reference codes
Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
B3010001 Hardware Management Console (HMC) or partition connection monitoring NEXTLVL
fault
B3010002 HMC or partition connection monitoring fault PTNNTWK

Perform the following steps:

1. Verify the network between the HMC and the partition by pinging in
both directions. Correct any problems that you detect.
2. Reboot the HMC.
B3010004 HMC or partition connection monitoring fault NEXTLVL
B3010012, HMC or partition connection monitoring fault NEXTLVL
B3010013,
B3010019,
B3010020,
B3010023,
B3010025,
B3010026
B3010027 HMC or partition connection monitoring fault NEXTLVL

Before using the entry in the Failing Items column, do the following:
1. If you use short host names for the HMC and the partitions, ensure that
you have correctly set up the short host names. For more information,
see the instructions in ″Using Network Adapters to Communicate with
Partitions″ in the Hardware Management Console for pSeries® Installation
and Operations Guide. Correct any problems that you find, then verify
that you can ping in both directions between the HMC and the
partitions.
2. If you do not use short host names or if the previous step does not
correct the problem, use the Failing Item column.
B3010029, HMC or partition connection monitoring fault NEXTLVL
B301002B,
B301002C,
B301002D

Reference codes 463

B3xx

Table 2. (B302) Connection monitoring reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
B3020001 Hardware Management Console (HMC) or partition connection monitoring NEXTLVL
fault

Before using the entry in the Failing Items column, do the following:
1. If you use short host names for the HMC and the partitions, ensure that
you have correctly set up the short host names. For more information,
see the instructions in ″Using Network Adapters to Communicate with
Partitions″ in the Hardware Management Console for pSeries Installation and
Operations Guide. Correct any problems that you find, then verify that
you can ping in both directions between the HMC and the partitions.
2. If you do not use short host names or if the previous step does not
correct the problem, use the Failing Item column.

Table 3. (B303) Connection monitoring reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
B3030001 The communication link between the service processor and the Hardware FSPSP33
Management Console (HMC) failed. SPNETWK
Note: This error might be a temporary condition caused by either the
HMC or the system that the HMC is connected, being shutdown, restarted,
upgraded or other intermittent conditions. While attempts are made to
only report these errors when a connection has been lost. It is important to
follow the procedures in the symbolic FRU list to determine if there is still
a connection problem and how to resolve the issue.
B3030002 A single partition HMC link failed. FSPSP33
Note: This error might be a temporary condition caused by either the PTNNTWK
HMC or the system that the HMC is connected, being shutdown, restarted, SPNETWK
upgraded or other intermittent conditions. While attempts are made to
only report these errors when a connection has been lost. It is important to
follow the procedures in the symbolic FRU list to determine if there is still
a connection problem and how to resolve the issue.
B3030003 Multiple partition HMC links failed. FSPSP33
Note: This error might be a temporary condition caused by either the PTNNTWK
HMC or the system that the HMC is connected, being shutdown, restarted, SPNETWK
upgraded or other intermittent conditions. While attempts are made to HMCMTWK
only report these errors when a connection has been lost. It is important to
follow the procedures in the symbolic FRU list to determine if there is still
a connection problem and how to resolve the issue.
B3030004 All partition links for a single system to HMC failed. FSPSP33
Note: This error might be a temporary condition caused by either the PTNNTWK
HMC or the system that the HMC is connected, being shutdown, restarted, SPNETWK
upgraded or other intermittent conditions. While attempts are made to
only report these errors when a connection has been lost. It is important to
follow the procedures in the symbolic FRU list to determine if there is still
a connection problem and how to resolve the issue.
B3030005 All system links from one system to a single HMC failed. FSPSP33
Note: This error might be a temporary condition caused by either the SPNETWK
HMC or the system that the HMC is connected, being shutdown, restarted,
upgraded or other intermittent conditions. While attempts are made to
only report these errors when a connection has been lost. It is important to
follow the procedures in the symbolic FRU list to determine if there is still
a connection problem and how to resolve the issue.

464 System i® and System p®: Reference codes

B3xx

Table 3. (B303) Connection monitoring reference codes (continued)

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
B3030006 The links between a single HMC and a single managed system failed. FSPSP33
Note: This error might be a temporary condition caused by either the SPNETWK
HMC or the system that the HMC is connected, being shutdown, restarted,
upgraded or other intermittent conditions. While attempts are made to
only report these errors when a connection has been lost. It is important to
follow the procedures in the symbolic FRU list to determine if there is still
a connection problem and how to resolve the issue.
B3030007 A single HMC link to more than one managed system occurred. FSPSP33
Note: This error might be a temporary condition caused by either the SPNETWK
HMC or the system that the HMC is connected, being shutdown, restarted, HMCNTWK
upgraded or other intermittent conditions. While attempts are made to
only report these errors when a connection has been lost. It is important to
follow the procedures in the symbolic FRU list to determine if there is still
a connection problem and how to resolve the issue.
B3030008 One HMC link to another single HMC failed. FSPSP33
Note: This error might be a temporary condition caused by either the HMCNTWK
HMC or the system that the HMC is connected, being shutdown, restarted, SPNETWK
upgraded or other intermittent conditions. While attempts are made to
only report these errors when a connection has been lost. It is important to
follow the procedures in the symbolic FRU list to determine if there is still
a connection problem and how to resolve the issue.
B3030009 One HMC link to more than one HMC occurred. FSPSP33
Note: This error might be a temporary condition caused by either the HMCMTWK
HMC or the system that the HMC is connected, being shutdown, restarted, SPNETWK
upgraded or other intermittent conditions. While attempts are made to
only report these errors when a connection has been lost. It is important to
follow the procedures in the symbolic FRU list to determine if there is still
a connection problem and how to resolve the issue.
B303000A The HMC lost links to all managed systems. FSPSP33
Note: This error might be a temporary condition caused by either the SPNETWK
HMC or the system that the HMC is connected, being shutdown, restarted,
upgraded or other intermittent conditions. While attempts are made to
only report these errors when a connection has been lost. It is important to
follow the procedures in the symbolic FRU list to determine if there is still
a connection problem and how to resolve the issue.
B303000B Multiple HMCs lost links to a single managed system. FSPSP33
Note: This error might be a temporary condition caused by either the SPNETWK
HMC or the system that the HMC is connected, being shutdown, restarted, HMCMTWK
upgraded or other intermittent conditions. While attempts are made to
only report these errors when a connection has been lost. It is important to
follow the procedures in the symbolic FRU list to determine if there is still
a connection problem and how to resolve the issue.
B303000C Multiple HMCs lost links to multiple managed systems. FSPSP33
Note: This error might be a temporary condition caused by either the SPNETWK
HMC or the system that the HMC is connected, being shutdown, restarted, HMCMTWK
upgraded or other intermittent conditions. While attempts are made to
only report these errors when a connection has been lost. It is important to
follow the procedures in the symbolic FRU list to determine if there is still
a connection problem and how to resolve the issue.

Reference codes 465

B3xx

Table 3. (B303) Connection monitoring reference codes (continued)

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
B303000D Multiple HMCs lost links to multiple managed systems. FSPSP33
Note: This error might be a temporary condition caused by either the SPNETWK
HMC or the system that the HMC is connected, being shutdown, restarted, HMCMTWK
upgraded or other intermittent conditions. While attempts are made to
only report these errors when a connection has been lost. It is important to
follow the procedures in the symbolic FRU list to determine if there is still
a connection problem and how to resolve the issue.
B303000E The Network Interface Card (NIC) failed SYSNTWK

Use the error codes offered in the HMC Focal Point to diagnose and repair
the problem. For more information, see Using Service Focal Point.
Note: This error might be a temporary condition caused by either the
HMC or the system that the HMC is connected, being shutdown, restarted,
upgraded or other intermittent conditions. While attempts are made to
only report these errors when a connection has been lost. It is important to
follow the procedures in the symbolic FRU list to determine if there is still
a connection problem and how to resolve the issue.
B303000F A single partition HMC link failure occurred on a redundant path. FSPSP33
Note: This error might be a temporary condition caused by either the PTNNTWK
HMC or the system that the HMC is connected, being shutdown, restarted, SPNETWK
upgraded or other intermittent conditions. While attempts are made to
only report these errors when a connection has been lost. It is important to
follow the procedures in the symbolic FRU list to determine if there is still
a connection problem and how to resolve the issue.
B3030010 A single HMC link to one HMC failure occurred on a redundant path.
Note: This error might be a temporary condition caused by either the
HMC or the system that the HMC is connected, being shutdown, restarted,
upgraded or other intermittent conditions. While attempts are made to
only report these errors when a connection has been lost. It is important to
follow the procedures in the symbolic FRU list to determine if there is still
a connection problem and how to resolve the issue.
B3030011 Server firmware connection monitoring to the flexible service processor FSPSP33
failed. SPNETWK
Note: This error might be a temporary condition caused by either the
HMC or the system that the HMC is connected, being shutdown, restarted,
upgraded or other intermittent conditions. While attempts are made to
only report these errors when a connection has been lost. It is important to
follow the procedures in the symbolic FRU list to determine if there is still
a connection problem and how to resolve the issue.
B3030012 Flexible service processor connection monitoring of server firmware failed. FSPSP33
Note: This error might be a temporary condition caused by either the SPNETWK
HMC or the system that the HMC is connected, being shutdown, restarted,
upgraded or other intermittent conditions. While attempts are made to
only report these errors when a connection has been lost. It is important to
follow the procedures in the symbolic FRU list to determine if there is still
a connection problem and how to resolve the issue.
B3030013 The communication path (mailbox) between server firmware and the FSPSP33
flexible service processor failed. SPNETWK
Note: This error might be a temporary condition caused by either the MAILBOX
HMC or the system that the HMC is connected, being shutdown, restarted,
upgraded or other intermittent conditions. While attempts are made to
only report these errors when a connection has been lost. It is important to
follow the procedures in the symbolic FRU list to determine if there is still
a connection problem and how to resolve the issue.

466 System i® and System p®: Reference codes

B3xx

Table 3. (B303) Connection monitoring reference codes (continued)

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
B3031000 Customer reported a console problem when creating a serviceable event on
the HMC user interface.

Contact the customer for more information about the problem.

B3031001 Customer reported a power problem when creating a serviceable event on
the HMC user interface.

Contact the customer for more information about the problem.

B3031002 Customer reported a processor problem when creating a serviceable event
on the HMC user interface.

Contact the customer for more information about the problem.

B3031003 Customer reported a LAN problem when creating a serviceable event on
the HMC user interface.

Contact the customer for more information about the problem.

B3031004 Customer reported a software problem when creating a serviceable event
on the HMC user interface.

Contact the customer for more information about the problem.

B3031005 Customer reported a input/output (I/O) problem when creating a
serviceable event on the HMC user interface.

Contact the customer for more information about the problem.

B3031006 Customer reported a problem when creating a serviceable event on the
HMC user interface.

Contact the customer for more information about the problem.

B3031007 Customer tested problem reporting by creating a serviceable event on the
HMC user interface.

Contact the customer for more information about the problem.

B3031100 Customer reported a problem when creating a serviceable event on the
HMC user interface.

Contact the customer for more information about the problem.

B3031101 Customer reported a power problem when creating a serviceable event on
the HMC user interface.

Contact the customer for more information about the problem.

B3031102 Customer reported a processor problem when creating a serviceable event
on the HMC user interface.

Contact the customer for more information about the problem.

B3031103 Customer reported a LAN problem when creating a serviceable event on
the HMC user interface.

Contact the customer for more information about the problem.

B3031104 Customer reported a software problem when creating a serviceable event
on the HMC user interface.

Contact the customer for more information about the problem.

Reference codes 467

B3xx

Table 3. (B303) Connection monitoring reference codes (continued)

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
B3031105 Customer reported a input/output (I/O) problem when creating a
serviceable event on the HMC user interface.

Contact the customer for more information about the problem.

B3031106 Customer reported a problem when creating a serviceable event on the
HMC user interface.

Contact the customer for more information about the problem.

B3031107 Customer tested problem reporting by creating a serviceable event on the
HMC user interface.

Contact the customer for more information about the problem.

B3036600 The HMC failed to retrieve a dump from a managed system. If you have a
redundant HMC environment, a peer HMC might have retrieved the
dump. This might be a temporary problem.

After receiving this error, perform the following steps:

1. Ensure that there is connectivity between this HMC and managed
System reported.
2. Use the manage dumps utility to determine if dumps have been
received from the managed system.
3. If there is a peer HMC managing the same system, also check that
HMC. Managed System Dumps can be retrieved by any HMC
connected to the system. If there is a current dump from the managed
system reported in the error, than the available dump has been
retrieved.
B3036601 The HMC failed to retrieve a platform system dump from the managed
system. If you have a redundant HMC environment, a peer HMC might
have retrieved the dump. This might be a temporary problem.

After receiving this error, perform the following steps:

1. Use the manage dumps utility to determine if a dump of that type has
been received from the managed system.
2. If you have a peer HMC managing the same system, also check that
HMC. Managed System Dumps can be retrieved by any HMC
connected to the system. If there is a current dump of the type that
failed from the managed system reported in the error, than the available
dump of that type has been retrieved.
B3036602 The HMC failed to retrieve a dump from the service processor. If you have
a redundant HMC environment, a peer HMC might have retrieved the
dump. This might be a temporary problem. This might be a temporary
problem.

After receiving this error, perform the following steps:

468 System i® and System p®: Reference codes

B3xx

Table 3. (B303) Connection monitoring reference codes (continued)

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
B3036604 The HMC failed to retrieve a power subsystem dump from the managed
system. If you have a redundant HMC environment, a peer HMC might
have retrieved the dump. This might be a temporary problem.

After receiving this error, perform the following steps:

1. Use the manage dumps utility to determine if a dump of that type has
been received from the managed system.
2. If you have a peer HMC managing the same system, also check that
HMC. Managed System Dumps can be retrieved by any HMC
connected to the system. If there is a current dump of the type that
failed from the managed system reported in the error, than the available
dump of that type has been retrieved.
B3036620 Primary HMC arbitration failure for domain {0} with peers {1}.
Note: Domain indicates which domain the managed system belongs to.
Peers indicate what HMC are also connected to the service processor.

This error code indicates that this HMC did receive primary information
from a peer HMC. To resolve this issue ensure that there is connectivity to
the FSP and the other HMC connected to the managed system.
B3036625 Primary HMC arbitration failure for domain {0} with peers {1}.
Note: Domain indicates which domain the managed system belongs to.
Peers indicate what HMC are also connected to the service processor.

This error code indicates that this HMC could not communicate with the
service processor to either set itself as a primary or to determine if other
HMCs are connected. To resolve this issue ensure that there is connectivity
to the service processor and the other HMC connected to the managed
system.

Table 4. (B31x) Connection monitoring reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
B3100500, Ethernet network failure NEXTLVL
B3112420
Do the following:
1. Reseat your Ethernet card.
2. Check your Ethernet cable connections.
3. If the previous actions do not resolve the problem, contact your next
level of support.

(BAxx) Partition firmware reference (error) codes

The partition firmware detected a failure. The first eight characters in the display represent the SRC. Any
additional characters represent the associated location code. Record the location code as well as the
reference code, then find the SRC in the following table.

Table 1. (BAxx) Partition firmware reference (error) codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
BA000010 The device data structure is corrupted FWFLASH
BA000020 Incompatible firmware levels were found

Reflash the platform firmware.

Reference codes 469

BAxx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
BA000030 An lpevent communication failure occurred FWFLASH
BA000032 The firmware failed to register the lpevent queues FWFLASH
BA000034 The firmware failed to exchange capacity and allocate lpevents FWFLASH
BA000038 The firmware failed to exchange virtual continuation events FWFLASH
BA000040 The firmware was unable to obtain the RTAS code lid details FWFLASH
BA000050 The firmware was unable to load the RTAS code lid FWFLASH
BA000060 The firmware was unable to obtain the open firmware code lid details FWFLASH
BA000070 The firmware was unable to load the open firmware code lid FWFLASH
BA000080 The user did not accept the license agreement

There is no further action required. If the user did not accept the license
agreement, the system will not function.
BA000081 Failed to get the firmware license policy FWFLASH
BA000082 Failed to set the firmware license policy FWFLASH
BA010000 There is insufficient information to boot the partition FWIPIPL
BA010001 The client IP address is already in use by another network device FWIPIPL
BA010002 Cannot get gateway IP address FWHOST

If the system is a model 185 or A50, refer to partition firmware progress

code E174. For all other systems, refer to partition firmware progress code
CA00E174.
BA010003 Cannot get server hardware address FWHOST

If the system is a model 185 or A50, refer to partition firmware progress

code E174. For all other systems, refer to partition firmware progress code
CA00E174.
BA010004 Bootp failed
BA010005 File transmission (TFTP) failed FWHOST
FWADIPL
Refer to partition firmware progress code CA00E174
BA010006 The boot image is too large FWADIPL
BA020001 Partition firmware password entry error

Reenter the password.

BA020009 Invalid password entered - system locked

A password was entered incorrectly three times. Deactivate the partition

using the HMC, then reactivate it. When asked for the password, enter the
correct password.
BA030011 RTAS attempt to allocate memory failed FWFWPBL
BA04000F Self test failed on device; no error or location code information available NEXTLVL

If there was a location code reported with the error, replace the device
specified by the location code.
BA040010 Self test failed on device; cannot locate package NEXTLVL
BA040020 The machine type and model are not recognized by the server firmware NEXTLVL

Check for server firmware updates, and apply them, if available.

470 System i® and System p®: Reference codes

BAxx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
BA040030 The firmware was not able to build the UID properly for this system. As a
result, problems may occur with the licensing of the AIX operating system.
1. Using the Advanced System Management Interface (ASMI) menus,
ensure that the machine type, model, and serial number in the VPD for
this system are correct.
2. If this is a new system, check for server firmware updates and apply
them, if available.
BA040035 The firmware was unable to find the ″plant of manufacture″ in the VPD.
This may cause problems with the licensing of the AIX operating system.

Verify the that machine type, model, and serial number are correct for this
system. If this is a new system, check for server firmware updates and
apply them, if available.
BA040040 Setting the machine type, model, and serial number failed. FWFWPBL
BA040050 The h-call to switch off the boot watchdog timer failed. FWFWPBL
BA040060 Setting the firmware boot side for the next boot failed. FWFWPBL
BA050001 Rebooting a partition in logical partition mode failed. FWFWPBL
BA050004 Locating a service processor device tree node failed. FWFWPBL
BA05000A Failed to send boot failed message to the service processor FWFWPBL
BA060003 IP parameter requires 3 period (.) characters

Enter a valid IP parameter. Example: 000.000.000.000

BA060004 Invalid IP parameter

Enter a valid IP parameter. Example: 000.000.000.000

BA060005 Invalid IP parameter (>255)

Enter a valid IP parameter. Example: 000.000.000.000

BA060007 A keyboard was not found
1. Make sure that a keyboard is attached to the USB port that is assigned
to the partition.
2. Replace the USB card to which the keyboard is attached.
BA060008 No configurable adapters found by the remote IPL menu in the System FWRIPL
Management Services (SMS) utilities

This error occurs when the remote IPL menu in the SMS utilities cannot
locate any LAN adapters that are supported by the remote IPL function.
BA06000B The system was not able to find an operating system on the devices in the
boot list.

See Problems with loading and starting the operating system (AIX and
Linux)
BA06000C A pointer to the operating system was found in non-volatile storage. FWPTR
BA060020 The boot-device environment variable exceeded the allowed character limit. FWNIM
BA060021 The boot-device environment variable contained more than five entries. FWNIM
BA060022 The boot-device environment variable contained an entry that exceeded 255 FWNIM
characters in length

Reference codes 471

BAxx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
BA060030 Logical partitioning with shared processors is enabled and the operating
system does not support it.
1. Install or boot a level of the operating system that supports shared
processors.
2. Disable logical partitioning with shared processors in the operating
system.
BA060040 The system or partition is configured to use huge pages, but the operating
system image does not support huge pages.

If the problem persists, the CD in the USB CD-ROM drive might not be
readable. Remove the CD and insert another CD.
BA131010 The USB keyboard was removed.
1. Plug in the USB keyboard and reboot the partition.
2. Check for system firmware updates and apply them, if available.
BA140001 SCSI read/write optical: test unit ready failed; hardware error FWSCSI1
BA140002 SCSI read/write optical: test unit ready failed; sense data available FWSCSI1
BA140003 SCSI read/write optical: send diagnostic failed; sense data available FWSCSI3
BA140004 SCSI read/write optical: send diagnostic failed; devofl command FWSCSI3
BA150001 PCI Ethernet BNC/RJ-45 or PCI Ethernet AUI/RJ-45 adapter: internal wrap
test failure

Replace the adapter specified by the location code.

BA151001 10/100 MBPS Ethernet PCI adapter: internal wrap test failure

Replace the adapter specified by the location code.

BA151002 10/100 MBPS Ethernet card FWENET
BA153002 Gigabit Ethernet adapter failure

Verify that the MAC address programmed in the FLASH/EEPROM is

correct.
BA153003 Gigabit Ethernet adapter failure
1. Check for adapter firmware updates; apply if available.
2. Remove other cards from the PHB in which the gigabit Ethernet
adapter is plugged and retry the operation. If the operation is
successful, plug the cards in again, one at a time, until the failing card
is isolated. After you identify the failing card, replace it.
3. Replace the adapter.
BA160001 PCI auto LANstreamer™ token ring adapter: failed to complete hardware
initialization.

Replace the adapter specified by the location code.

BA161001 PCI token ring adapter: failed to complete hardware initialization.

Replace the adapter specified by the location code.

BA170xxx NVRAM problems FWNVR1
BA170000 NVRAMRC initialization failed; device test failed FWNVR2
BA170100 NVRAM data validation check failed FWNVR2

Turn off, then turn on the system.

BA170201 The firmware was unable to expand target partition - saving configuration FWNVR1
variable

474 System i® and System p®: Reference codes

BAxx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
BA170202 The firmware was unable to expand target partition - writing error log FWNVR1
entry
BA170203 The firmware was unable to expand target partition - writing VPD data FWNVR1
BA170210 Setenv/$Setenv parameter error - name contains a null character FWNVR1
BA170211 Setenv/$Setenv parameter error - value contains a null character FWNVR1
BA170220 The firmware was not able to write a variable value into NVRAM because
not enough space exists in NVRAM.

Do the following:
1. Reduce the number of partitions, if possible, so that each of the
remaining partitions has more NVRMA allocated to it.
2. Contact your next level of support.
BA170221 The setenv/$setenv function had to delete network boot information to free
space in NVRAM.

You might need to use the SMS menus to reenter the parameters for
network installation or boot.
BA170998 NVRAMRC script evaluation error - command line execution error. FWNVR3
BA170999 NVRAMRC script evaluation error - stack unbalanced on completion. NEXTLVL

This is a firmware debug environment error. There is no user action or

FRU replacement for this error.
BA180008 PCI device Fcode evaluation error. FWPCI1
BA180009 The Fcode on a PCI adapter left a data stack imbalance FWPCI1

You should load the new adapter Fcode before you use the adapter
(specified by the location code associated with this error) for booting.
BA180010 PCI probe error, bridge in freeze state FWPCI2
BA180011 PCI bridge probe error, bridge is not usable FWPCI3
BA180012 PCI device runtime error, bridge in freeze state FWPCI3
BA180013 A PCI adapter was found that this machine type and model does not
support. Is the system an IBM® Intellistation model?
v Yes: Complete the following steps.
1. Check for and apply any available server firmware udpates.
2. Replace the adapter at the location code that was reported with the
error.
v No: Remove the PCI adapter specified by the location code.
BA180014 MSI software error FWFLASH
BA180100 FDDI adapter Fcode driver is not supported on this system.

This server does not support the Fcode driver of this adapter. Service
support might have additional information.
BA180101 Stack underflow from fibre-channel adapter FWFWPBL
BA188000 An unsupported adapter was found in a PCI slot

Remove the unsupported adapter in the slot identified by the location

code.

Reference codes 475

BAxx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
BA188001 EEH recovered a failing I/O adapter

This is an informational code only, and no action is required. Since it is

informational, no location code will be reported.
BA188002 EEH could not recover the failed I/O adapter

Replace the adapter in the slot identified by the location code.

BA190001 Firmware function to get/set time-of-day reported an error FWFWPBL
BA191001 The server firmware function to turn on the speaker reported an error FWFWPBL
BA201001 The serial interface dropped data packets FWFWPBL
BA201002 The serial interface failed to open FWFWPBL
Note: Check console settings to ensure the console is defined to the correct
port. Ensure the console cables are connected to the port that is defined as
the console.
BA201003 The firmware failed to handshake properly with the serial interface FWFWPBL
BA210000 Partition firmware reports a default catch FWFWPBL
BA210001 Partition firmware reports a stack underflow was caught FWFWPBL
BA210002 Partition firmware was ready before standout was ready FWFWPBL
BA210010 The transfer of control to the SLIC loader failed FWFWPBL
BA210020 The I/O configuration exceeds the maximum size allowed by partition
firmware.

Increase the logical memory block size to 256 megabytes (MB) and reboot
the managed system.
Note: If the logical memory block size is already 256 MB, contact your next
level of support.
BA210100 The partition firmware was unable to log an error with the server NEXTLVL
firmware. No reply was received from the server firmware to an error log
that was sent previously
BA210101 The partition firmware error log queue is full NEXTLVL
BA250010 dlpar error in open firmware FWLPAR
BA250020 dlpar error in open firmware due to an invalid dlpar entity. This error may
have been caused by an errant or hung operating system process.
1. Check for operating system updates that resolve problems with
dynamic logical partitioning (dlpar) and apply them, if available.
2. Check for server firmware updates and apply them, if available.
BA250030 A hotplug operation in dynamic logical partitioning (dlpar) was terminated
for concurrent firmware update. Retry the hotplug operation after the
concurrent firmware update is complete.
BA250040 The firmware was unable to generate a device tree node FWFLASH

After you perform the FRU indicated in the Failing Items column, check
for operating system updates and apply them, if available.
BA278001 Failed to flash firmware: invalid image file

Obtain a valid firmware update (flash) image for this system.

BA278002 Flash file is not designed for this eServer™ platform

Obtain a valid firmware update (flash) image for this system.

476 System i® and System p®: Reference codes

BAxx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
BA278003 Unable to lock the firmware update lid manager
1. Reboot the system.
2. Make sure that the operating system is authorized to update the
firmware. If the system is running multiple partitions, verify that this
partition has service authority.
BA278004 An invalid firmware update lid was requested

Obtain a valid firmware update (flash) image for this system.

BA278005 Failed to flash a firmware update lid

Obtain a valid firmware update (flash) image for this system.

BA278006 Unable to unlock the firmware update lid manager

Reboot the system.

BA278007 Failed to reboot the system after a firmware flash update

Reboot the system.

BA278008 A server firmware update was attempted from the operating system. You
must perform the update by using the Hardware Management Console
(HMC).

Perform the server firmware update by using the HMC.

BA278009 The server firmware update management tools for the version of Linux
that you are running are incompatible with this system.

Go to Service and productivity tools for Linux on POWER™ and

download the latest service aids and productivity tools for the version of
Linux that you are running.
BA280000 RTAS discovered an invalid operation that may cause a hardware error NEXTLVL
BA290000 RTAS discovered an internal stack overflow FWFWPBL
BA300010 The partition exceeded the maximum number of logical memory blocks
allowed under the new memory allocation scheme.

Reduce the total logical memory block limit in the partition profile, then
reactivate the partition.
Note: The maximum number of logical memory blocks per partition is 128
kilobytes (K) under the new memory allocation scheme.
BA300020 Function call to isolate a logical memory block failed under the standard
memory allocation scheme.

Reference codes 477

BAxx

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
BA300030 Function call to make a logical memory block unusable failed under the
standard memory allocation scheme.

Do the following:
1. Upgrade the firmware of the managed system to the latest level, if a
newer level is available.
2. Upgrade the operating system to a level that supports the new memory
representation, or edit the profile to have fewer logical memory blocks
than the 8K maximum.
3. Reboot the partition.
BA300040 The partition, which is running the traditional memory representation,
exceeded the limit of 8192 logical memory blocks allowed by the standard
memory allocation scheme.

Do the following:
1. Upgrade the operating system to one that supports the new memory
representation, or edit the profile to have fewer than 8192 logical
memory blocks.
2. Reboot the partition.
BA310010 The firmware could not obtain the SRC history FWFLASH
BA310020 The firmware received an invalid SRC history FWFLASH
BA310030 The firmware operation to write the MAC address to vital product data FWFLASH
(VPD) failed

(BBxx) High performance switch reference codes

The high performance switch detected a failure. Record the location code as well as the reference code,
then find the SRC in the High Performance Switch Planning, Installation, and Service for IBM eServer p5
servers manual.

(BF67) Linux reference codes

The Linux operating system detected a failure in the emulex driver.

Use the following table to locate the last four characters of the (BF67) Linux SRC that you want to find,
then perform the suggested actions.

Note: If the suggested action in the Description/Action column does not work (or if that column does
not contain a suggested action), use the action specified in the Failing Item column.

Table 1. (BF67) Linux reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
7800 An ELS IOCB command was posted to a ring and did not complete within NEXTLVL
ULP timeout seconds.

If no ELS command is going through the adapter, reboot the system.

478 System i® and System p®: Reference codes

BF67

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
7801 The driver attempted to issue READ_SPARAM mailbox command to the NEXTLVL
HBA but there were no buffer available. This message indicates one of the
following conditions:
v A possible lack of memory resources. Try increasing the lpfc num_bufs
configuration parameter to allocate more buffers
v A possible driver buffer management problem
7802 The driver attempted to issue REG_LOGIN mailbox command to the HBA NEXTLVL
but there were no buffer available. This message indicates one of the
following conditions:
v A possible lack of memory resources. Try increasing the lpfc num_bufs
configuration parameter to allocate more buffers
v A possible driver buffer management problem
7803 This message indicates one of the following conditions: NEXTLVL
v Port rsp ring put index is greater than the size of rsp ring
v Port cmd ring get index is greater than the size of cmd ring
v Port cmd ring get index is greater than the size of cmd ring
v The assigned I/O iotag is greater than the max allowed
v The assigned I/O iotag is greater than the max allowed

This error might indicate a software driver, firmware or hardware problem.

7804 The Rctl/Type of a received frame did not match any for the configured NEXTLVL
masks for the specified ring.

This error might indicate a software driver or firmware problem.

7805 Received an unknown IOCB command completion. NEXTLVL

This error might indicate a software driver or firmware problem.

7806 The driver wan unable to find a matching command for the completion NEXTLVL
received on the specified ring.

This error might indicate a software driver or firmware problem.

7807 A unknown mailbox command completed. NEXTLVL

This error might indicate a software driver, firmware or hardware problem.

7808 The configuration parameter for scan-down is out of range. NEXTLVL

Software driver error.

7809 The driver attempted to register the HBA interrupt service routine with the NEXTLVL
host operating system but failed.

This error might indicate a hardware or driver problem.

780A The driver manages its own memory for internal usage. This error NEXTLVL
indicates a problem occurred in the driver memory management routines.
This error might also indicate the host system in low on memory resources.

This error might indicate a driver or host operating system problem.

Reference codes 479

BF67

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
780B This message indicates one of the following conditions: NEXTLVL
v ASCII string to hex conversion failed. Input byte count less than 1
v ASCII string to hex conversion failed. Input byte count greater than the
max <num>
v ASCII string to hex conversion failed. The output buffer byte size is less
than one–half of the input byte count. Every two input chars (bytes)
require one output byte

This error might indicate a software driver problem.

7A00 The driver decided to drop an ELS Response ring entry. NEXTLVL

This error might indicate a software driver or firmware problem.

7A01 Received a mailbox completion interrupt and there are no outstanding NEXTLVL
mailbox commands.

This error might indicate a hardware or firmware problem. Update

firmware.
7A02 The driver issued a CONFIG_LINK mbox command to the HBA that failed. NEXTLVL

This error might indicate a firmware or hardware problem.

Update firmware or replace adapter.

7A03 The driver issued a READ_SPARAM mbox command to the HBA that NEXTLVL
failed.

This error might indicate a firmware or hardware problem.

7A04 The driver issued a CLEAR_LA mbox command to the HBA that failed. NEXTLVL

This error might indicate a firmware or hardware problem.

7A05 A read nvparams mailbox command failed during config port. NEXTLVL

This error might indicate a hardware or firmware problem.

7A06 The driver cannot find the specified buffer in its mapping table. NEXTLVL

This error might indicate a software driver or firmware problem.

7A07 The adapter failed during power-up diagnostics after it was reset. NEXTLVL

This error might indicate a hardware or firmware problem.

7A08 The adapter failed during power-up diagnostics after it was reset. NEXTLVL

This error might indicate a hardware or firmware problem.

7A09 Adapter initialization failed when issuing READ_REV mailbox command. NEXTLVL

This error might indicate a hardware or firmware problem.

7A0A Outdated firmware was detected during initialization. NEXTLVL

This error might indicate a hardware or firmware problem.

Update firmware.
7A0B Adapter initialization failed when issuing DUMP_VPD mailbox command. NEXTLVL

This error might indicate a hardware or firmware problem.

480 System i® and System p®: Reference codes

BF67

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
7A0C Adapter initialization failed when issuing CONFIG_PORT mailbox NEXTLVL
command.

This error might indicate a hardware or firmware problem.

7A0D Adapter initialization failed when issuing CFG_RING mailbox command. NEXTLVL

This error might indicate a hardware or firmware problem.

7A0E Adapter initialization failed when issuing CONFIG_LINK mailbox NEXTLVL
command.

This error might indicate a hardware or firmware problem.

7A0F Adapter initialization failed when issuing READ_SPARM mailbox NEXTLVL
command.

This error might indicate a hardware or firmware problem.

7A10 Adapter initialization failed when issuing READ_CONFIG mailbox NEXTLVL
command.

This error might indicate a hardware or firmware problem.

7A11 Adapter initialization failed when issuing INIT_LINK mailbox command. NEXTLVL

This error might indicate a hardware or firmware problem.

7A12 The driver received an interrupt indicting a possible hardware problem. NEXTLVL

This error might indicate a hardware or firmware problem.

(BF75) Linux reference codes

The Linux operating system detected a failure in the ipr driver.

The first five characters (BFxxx) of these SRCs indicate the driver or subsystem responsible for the error,
and the last three characters specifies the error condition. The last three characters of the SRCs are
arranged such that 1xx is lowest severity and Fxx is highest severity. For example:
v Errors that require you to check cables occur in the 5xx range
v Errors that require you to perform a microcode update occur in the Axx range
v Errors that require you to replace an adapter occur in the Fxx range

Use the following table to locate the last four characters of the (BF75) Linux SRC that you want to find,
then perform the suggested actions.

Note: If the suggested action in the Description/Action column does not work (or if that column does
not contain a suggested action), use the action specified in the Failing Item column.

Table 1. (BF75) Linux reference codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
1800 8155: An unknown error was received. NEXTLVL

Have the customer update the device driver.

1A00 Firmware file %s not found. NEXTLVL

Have the customer update the adapter microcode.

Reference codes 481

BF75

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
1A01 Invalid microcode buffer. NEXTLVL

Have the customer update the adapter microcode.

1A02 Microcode buffer allocation failed. NEXTLVL

Have the customer update the adapter microcode.

1A03 Microcode buffer copy to DMA buffer failed. NEXTLVL

Have the customer update the adapter microcode.

1A04 Microcode download required. NEXTLVL

Have the customer update the adapter microcode.

1A05 Failed to map microcode download buffer. NEXTLVL

Have the customer update the adapter microcode.

1A06 8151: IOA microcode error. NEXTLVL

Have the customer update the adapter microcode and the device driver.
1C00 Adapter being reset due to command timeout. IOADPTR

Have the customer update the adapter microcode.

1C01 Invalid resource address. IOADPTR

Have the customer update the device driver.

1D00 7001: IOA sector reassignment successful. Media error. IO_DEV
1D01 Unsolicited device bus message received. IO_DEV
1D02 Device hardware error. IO_DEV
1D03 Predictive failure analysis. IO_DEV
1D04 Device error. May occur normally during concurrent maintenance. IO_DEV
1D05 Out of alternate sectors for disk storage. IO_DEV
1D06 9031: Array protection temporarily suspended, protection resuming. NEXTLVL

Hardware configuration error.

Perform MAP 3310 in the PCI-X SCSI RAID Controller Reference Guide for
Linux.

1D07 This message indicates one of the following conditions: NEXTLVL

v Array protection temporarily suspended
v IOA detected device error
v Cache data belongs to devices other than those attached
v Maximum number of arrays already exist
v Incorrect hardware configuration change has been detected

Perform MAP 3390 in the PCI-X SCSI RAID Controller Reference Guide for
Linux.

482 System i® and System p®: Reference codes

BF75

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
1D08 IOA detected a SCSI bus configuration error. Device bus error, message or NEXTLVL
command phase.

Perform MAP 3350 in the PCI-X SCSI RAID Controller Reference Guide for
Linux.

1D09 IOA cache data exists for a missing or failed device. NEXTLVL

Perform MAP 3332 in the PCI-X SCSI RAID Controller Reference Guide for
Linux.

1D0A Disk unit has been modified after the last known status. Incorrect hardware NEXTLVL
configuration change has been detected.

Perform MAP 3333 in the PCI-X SCSI RAID Controller Reference Guide for
Linux.

1D0B A permanent cache battery pack failure occurred. NEXTLVL

Perform MAP 3300 in the PCI-X SCSI RAID Controller Reference Guide for
Linux.

1D0C Cache data associated with attached devices cannot be found. NEXTLVL

Perform MAP 3320 in the PCI-X SCSI RAID Controller Reference Guide for
Linux.

1D0D Array missing two or more devices with only one device present. NEXTLVL

Perform MAP 3311 in the PCI-X SCSI RAID Controller Reference Guide for
Linux.

1D0E One or more array members not at required physical locations. NEXTLVL

Perform MAP 3312 in the PCI-X SCSI RAID Controller Reference Guide for
Linux.

1D0F Array is missing a device and parity is out of sync. NEXTLVL

Perform MAP 3313 in the PCI-X SCSI RAID Controller Reference Guide for
Linux.

1D10 Required cache data cannot be located for a disk unit. NEXTLVL

Perform MAP 3331 in the PCI-X SCSI RAID Controller Reference Guide for
Linux.

Reference codes 483

BF75

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
1D11 IOA resources not available due to previous problems. NEXTLVL

Perform MAP 3321 in the PCI-X SCSI RAID Controller Reference Guide for
Linux.

1D12 Disk unit requires initialization before use. NEXTLVL

Perform MAP 3334 in the PCI-X SCSI RAID Controller Reference Guide for
Linux.

1F00 Permanent IOA failure. IOADPTR

1F01 Invalid response handle from IOA. IOADPTR
1F02 IOA unit check with no data. IOADPTR
1F03 IOA taken offline - error recovery failed. IOADPTR
1F04 Adapter not supported in this hardware configuration. IOADPTR

Remove the unsupported adapter from the system.

1F05 Failed to set PCI DMA mask. IOADPTR
1F06 Write of cache line size failed. IOADPTR
1F07 Failed to save PCI configuration space. IOADPTR
1F08 PCI bus error. IOADPTR
1F08 Soft PCI bus error. IOADPTR
1F09 Adapter hardware error. IOADPTR

(BF77) Linux reference codes

The Linux operating system detected a failure in a driver or subsystem.

The first five characters (BFyyy) of these SRCs indicate the driver or subsystem responsible for the error:
v BF77 0xxx specifies the olympic driver
v BF77 5xxx specifies the pcnet32 driver
v BF77 6xxx specifies the bcm 5700 driver
v BF77 7xxx specifies the e100 driver
v BF77 8xxx specifies the e1000 driver

The last three characters specify the error condition. The last three characters of the SRCs are arranged
such that 1xx is lowest severity and Fxx is highest severity. For example:
v Errors that require you to check cables occur in the 5xx range
v Errors that require you to perform a microcode update occur in the Axx range
v Errors that require you to replace an adapter occur in the Fxx range

Use the following table to locate the last four characters of the (BF77) Linux SRC that you want to find,
then perform the suggested actions:
v Table 1. (BF77 0xxx) Linux reference codes (olympic driver)
v Table 2. (BF77 5xxx) Linux reference codes (pcnet32 driver)
v Table 3. (BF77 6xxx) Linux reference codes (bcm 5700 driver)

484 System i® and System p®: Reference codes

BF77

v Table 4. (BF77 7xxx) Linux reference codes (e100 driver)

v Table 5. (BF77 8xxx) Linux reference codes (e1000 driver)

Note: If the suggested action in the Description/Action column in any of the following tables does not
work (or if that column does not contain a suggested action), use the action specified in the Failing
Item column.

Table 1. (BF77 0xxx) Linux reference codes (olympic driver)

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
0A00 Unrecognized command code or unrecognized buffer address. Have the NEXTLVL
customer do the following:
1. Reload the driver and reset the device to recover lost buffers
2. Upgrade the driver
0F01 The olympic driver was unable to initialize the token ring card. IOADPTR

Corrective action may be possible depending upon the error code.

0F02 The Cardbus token ring adapter did not respond to initialization IOADPTR
commands.

Ensure that Cardbus adapter is properly inserted.

0F03 The token ring adapter was unable to join the ring. IOADPTR

Have the customer use the network configuration tool supplied by the
distributor to specify a ring speed (instead of automatically detecting ring
speed).
0F04 The adapter open request failed with the specified error code. IOADPTR
0800 The driver was unable to send a received packet to the upper layer LPARCFG
protocols because there is insufficient free memory.

The customer may need to increase system memory.

0F05 The specified hardware, PCI or parity error has occurred. IOADPTR

Have the customer reset the adapter

0F06 The specified interrupt has occurred, but was not expected by the driver or IOADPTR
a timeout occurred during device close processing.

For occasional occurances, no action is required. For excessive occurrences,

have the customer reset the adapter. If resetting the adapter does not work,
perform the action specified in the Failing Item column.
0F07 Unrecognized srb command or cannot set mac/laa address while card is IOADPTR
open.

Have the customer reload the driver

0F08 A short circuit has been detected. Have the customer do the following: IOADPTR
v Check and replace cables, if necessary
v Check and replace peer stations on ring, if necessary
0F09 An internal hardware error has been detected in the specified adapter IOADPTR
during auto removal processing.

Have the customer reload the driver

0F0A An FDX protocol error has been detected. IOADPTR

Have the customer reload the driver

Reference codes 485

BF77

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
0F0B Invalid return code in asb. IOADPTR

Have the customer upgrade the driver

Table 2. (BF77 5xxx) Linux reference codes (pcnet32 driver)

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
5800 The driver was unable to use 32-bit DMA. NEXTLVL

Have the customer verify the driver software level.

5801 Memory allocation failed. Have the customer do the following: NEXTLVL
1. Verify the driver software level
2. Increase the memory on the system
5802 Transmit timed out, resetting. NEXTLVL

Have the customer verify the driver software level.

5803 A FIFO error has occurred. NEXTLVL

Have the customer verify the driver software level.

5804 The transmit pointers are out of synchronization. NEXTLVL

Have the customer verify the driver software level.

5F00 The driver could not enable the PCI device. IOADPTR
5F01 The hardware did not request any IO resources. IOADPTR
5F02 The IO addresses for the card are already allocated. IOADPTR

Have the customer verify the driver software level.

5F03 The chip can not be accessed in 32–bit or 16–bit mode. IOADPTR

Have the customer verify the driver software level.

Table 3. (BF77 6xxx) Linux reference codes (bcm 5700 driver)

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
6500 Unable to find or create the directory under /proc/net. NEXTLVL

Have the customer verify that procfs is supported by the kernel.

6501 Insufficient kernel memory available for allocation. Have the customer do NEXTLVL
the following:
v Increase the memory on the system
v Install the driver earlier in system bringup
6502 The driver was unable to use either 64-bit or 32-bit DMA. NEXTLVL

Have the customer verify driver software level.

6503 Linux does not support a hardware feature which has been enabled. NEXTLVL

Run diagnostics to disable Turbo Teaming.

486 System i® and System p®: Reference codes

BF77

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
6504 Memory allocation failed - buffer parameters may be set too high. Have the NEXTLVL
customer do the following:
1. Reduce the tx_pkt_desc_cnt parameter of the driver
2. Reduce the rx_std_desc_cnt parameter of the driver
3. Reduce the rx_jumbo_desc_cnt parameter of the driver
6505 Conflicting rx_coalesce_ticks (0) and rx_max_coalesce_frames (0) NEXTLVL
parameters. Have the customer do the following:
1. Change the rx_coalesce_ticks parameter of the driver
2. Change the rx_max_coalesce_frames parameter of the driver
6506 Conflicting tx_coalesce_ticks (0) and tx_max_coalesce_frames (0) NEXTLVL
parameters. Have the customer do the following:
1. Change the tx_coalesce_ticks parameter of the driver
2. Change the tx_max_coalesce_frames parameter of the driver
6507 The value given to the stats_coalesce_ticks parameter is invalid. NEXTLVL

Have the customer change the stats_coalesce_ticks parameter of the driver.

6800 Either this adapter or the system does not allow the use of adapter based NEXTLVL
transmit descriptors. Have the customer do the following:
1. Verify the driver software level
2. Change the nic_tx_bd parameter
6801 This adapter does not support hardware checksum offload. Have the NEXTLVL
customer do the following:
1. Verify the driver software level
2. Change the driver’s rx_checksum parameter
3. Change the driver’s tx_checksum parameter
6802 This adapter does not support hardware TSO. Have the customer do the NEXTLVL
following:
1. Verify the driver software level
2. Change the driver’s enable_tso parameter
6A00 This adapter hardware does not support frames sizes over 1500 bytes. IOADPTR

Have the customer verify the driver software level

If you replace the adapter, use one that offers additional capablities
6F00 Unable to read the adapter’s NVRAM. IOADPTR

Have the customer verify the driver software level

6F01 Cannot get MAC addr from NVRAM. IOADPTR

Have the customer verify the driver software level

6F02 Unable to read PCI Config space or NVRAM. IOADPTR

Have the customer verify the driver software level

Table 4. (BF77 7xxx) Linux reference codes (e100 driver)

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
SRC Probable Causes Actions

Reference codes 487

BF77

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
7800 Internal error in driver, kernel, or firmware. Have the customer do the NEXTLVL
following:
1. Verify the driver software level.
2. Run diagnostics.
7801 Insufficient kernel memory is available for the driver. Have the customer NEXTLVL
do the following:
1. Install more memory in the system
2. Reconfigure the kernel to reduce memory consumption
3. Install the driver earlier in system bringup
7802 Internal error in driver, kernel, or firmware. Have the customer do the NEXTLVL
following:
1. Verify the driver software level
2. Run diagnostics
7E00 Not enough memory for the driver. Unable to initialize (or reinitialize) the IOADPTR
adapter card. Have the customer do the following:
1. Verify the driver software level
2. Reconfigure the kernel to reduce memory consumption, then reboot
7E01 The BIOS has assigned conflicting address spaces to different devices. Have IOADPTR
the customer do the following:
1. Run diagnostics
2. Upgrade the BIOS
7E02 The driver requested a DMA configuration that your system does not IOADPTR
support. Have the customer do the following:
1. Verify the driver software level
2. Run diagnostics
7E03 The adapter’s MAC address is not a valid Ethernet address. Have the IOADPTR
customer do the following:
1. Verify the driver software level
2. Run diagnostics
7F00 The EEPROM on the network adapter may be corrupted. IOADPTR
7F01 The driver cannot enable the adapter as a PCI device. IOADPTR
7F02 The network adapter failed its self-test. IOADPTR

Table 5. (BF77 8xxx) Linux reference codes (e1000 driver)

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
8E00 Cannot enable DMA for either 32 bits or 64 bits. NEXTLVL
8E01 Unable to access PCI data area for checksum value. However, the device id NEXTLVL
is valid. Have the customer do the following:
v Verify the driver software level
v Run diagnostics
v Replace board
8E02 The MAC type is not ethernet as expected. Have the customer do the IOADPTR
following:
v Verify the driver software level
v Run diagnostics

488 System i® and System p®: Reference codes

BF77

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
8F00 Adapter hardware failure. IOADPTR

(CBxx) IBM Network Manager reference codes

The IBM Network Manager detected a failure. Record the reference code and the location code, if
available, then find the failing item in Clustering systems using InfiniBand (IB) hardware.

Note: Reference codes based on events detected by the InfiniBand (IB) switches (CBxxxxxx) do not
support the Call Home feature. They will not be called home by Electronic Service Agent™. If you
attempt to use the manual function to initiate Call Home, it will not successfully generate a service
call, and you will not receive any indication that the service call was not generated.

Reference Code Description/Event name Failing Item

CB201800 linkDown IBNSLNK
CB102800 authenticationFailure IBNSAUT
CB108800 tsCardDown IBNSREM
CB109800 tsPowerSupplyDown IBNSPOW
CB10A000 tsFanDown IBNSFAN
CB10B800 tsCardRemove IBNSREM
CB10C100 tsEvent::ibSmSlaveToMaster(4) IBNSNLS
CB10C1C0 tsEvent::ibSmNodeDeleted(7) IBNSNLS
CB10C4C0 tsEvent::ibSmDbSyncNotSupported(19) IBNSNLS
CB10C500 tsEvent::ibSmDbSyncNotEnabled(20) IBNSDBS
CB10C540 tsEvent::ibSmDbSyncNoStandby(21) IBNSNLS
CB10C580 tsEvent::ibSmDbSyncDbVersionMismatch(22) IBNSSMU
CB10C5C0 tsEvent::ibSmDbSyncColdSyncTimeout(23) IBNSSMR
CB10C600 tsEvent::ibSmDbSyncSessionTimeout(24) IBNSDBT
CB10C641 tsEvent::hardwareError(25)::local I2C error::1 IBNSDIG
CB10C642 tsEvent::hardwareError(25)::remote I2C error::2 IBNSDGA
CB10C643 tsEvent::hardwareError(25)::card seeprom error::3 IBNSDIG
CB10C644 tsEvent::hardwareError(25)::DiskOnChipError::4 IBNSDIG
CB10C645 tsEvent::hardwareError(25)::single bit memory error::5 IBNSDIG
CB10C646 tsEvent::hardwareError(25)::double bit memory error::6 IBNSDIG
CB10C647 tsEvent::hardwareError(25)::real-time clock stopped::7 IBNSBAT
CB10C648 tsEvent::hardwareError(25)::real-time clock sync::8 IBNSBAT
CB10C649 tsEvent::hardwareError(25)::no fan error::9 IBNSFAN
CB10C64A tsEvent::hardwareError(25)::FPGA error::10 IBNSDIG
CB10C64B tsEvent::hardwareError(25)::IB switch ASIC error::11 IBNSDIG
CB10C64C tsEvent::hardwareError(25)::IB switch firmware error::12 IBNSDIG
CB10C64D tsEvent::hardwareError(25)::voltage/current error::13 IBNSPOW
CB10C64E tsEvent::hardwareError(25)::cpu ext bus error::14 IBNSDIG
CB10C64F tsEvent::hardwareError(25)::cpu bus error::15 IBNSDIG
CB10C650 tsEvent::hardwareError(25)::fru error::16 IBNSDIG

Reference codes 489

CBxx

Reference Code Description/Event name Failing Item

CB10C651 tsEvent::hardwareError(25)::local ethernet error::17 IBNSDIG
CB10C652 tsEvent::hardwareError(25)::management ethernet error::18 IBNSDIG
CB10C653 tsEvent::hardwareError(25)::cpu error::19 IBNSDIG
CB10C654 tsEvent::hardwareError(25)::na::20 IBNSSWE
CB10C655 tsEvent::hardwareError(25)::na::21 IBNSSWE
CB10C656 tsEvent::hardwareError(25)::na::22 IBNSSWE
CB10C657 tsEvent::hardwareError(25)::na::23 IBNSSWE
CB10C658 tsEvent::hardwareError(25)::na::24 IBNSSWE
CB10C659 tsEvent::hardwareError(25)::na::25 IBNSSWE
CB10C65A tsEvent::hardwareError(25)::na::26 IBNSSWE
CB10C65B tsEvent::hardwareError(25)::na::27 IBNSSWE
CB10C65C tsEvent::hardwareError(25)::na::28 IBNSSWE
CB10C65D tsEvent::hardwareError(25)::na::29 IBNSSWE
CB10C65E tsEvent::hardwareError(25)::na::30 IBNSSWE
CB10C65F tsEvent::hardwareError(25)::na::31 IBNSSWE
CB10C660 tsEvent::hardwareError(25)::na::32 IBNSSWE
CB10C661 tsEvent::hardwareError(25)::na::33 IBNSSWE
CB10C662 tsEvent::hardwareError(25)::na::34 IBNSSWE
CB10C663 tsEvent::hardwareError(25)::na::35 IBNSSWE
CB10C664 tsEvent::hardwareError(25)::na::36 IBNSSWE
CB10C665 tsEvent::hardwareError(25)::na::37 IBNSSWE
CB10C666 tsEvent::hardwareError(25)::na::38 IBNSSWE
CB10C667 tsEvent::hardwareError(25)::na::39 IBNSSWE
CB10C6C1 tsEvent::softwareInitiatedReboot(27); watchdog::1 IBNSSWP
CB10C6C2 tsEvent::softwareInitiatedReboot(27); assertion::2 IBNSSWP
CB10C6C3 tsEvent::softwareInitiatedReboot(27); out-of-memory::3 IBNSSWP
CB10C6C4 tsEvent::softwareInitiatedReboot(27); no working fan::4 IBNSFAN
CB10C701 tsEvent::hardwareInitiatedReboot(28); watchdog::1 IBNSSWP
CB20C740 tsEvent::ibPmPortMonitorThresholdErrorChange(29) IBNSLNK
CB20C780 tsEvent::ibPmPortMonitorThresholdUtilChange(30) IBNSLNK
CB20C7C0 tsEvent::ibPmConnectionMonitorErrorChange(31) IBNSLNK
CB20C230 tsEvent::ibPmConnectionMonitorUtilChange(32) IBNSLNK
CB100001 tsSensor::(tsSensor::tsDevSensorTemperature=warning)::1 IBNSTHM
CB100002 tsSensor::(tsSensor::tsDevSensorTemperature=normal)::2 IBNSTHM
CB100003 tsSensor::(tsSensor::tsDevSensorTemperature=critical)::3 IBNSTHM
CBFF0000 Network Manager Diagnostics Event - Report this side IBNNMD
CBFF0001 Network Manager Diagnostics Event - Report other side IBNNMD
CBFF0002 Network Manager Diagnostics Event - Report cable IBNNMD
CBFF00FF Unrecognized Unit Model IBNNURM
CB10FF00 VPD problem IBNSVPD

490 System i® and System p®: Reference codes

DAxx

(DAxx) Partition firmware reference (error) codes

The Hardware Management Console generates E2xx error codes when it encounters a Licensed Internal
Code problem.

Table 1. (E2xx) Licensed Internal Code progress codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E2BB1250 The system monitor that checks for HMC hardware failures has shutdown.
This is usually the result of the system syslog being shutdown. You will
need to shut down and restart the HMC.
E2FF450F The log manager cannot read the expected amount of data from the log
file. When this occurs, the log manager will copy the current log file to
iqyysave.log, start a new log file, and copy the error log to the new log file.
If possible, collect the iqyysave.log file with the error data for reference.
There is no other action required.
E2xxxxxx Licensed Internal Code failure on the HMC. NEXTLVL

Contact your service provider.

(E3xx) Licensed Internal Code error codes

The Hardware Management Console (HMC) generates E3xx error codes when it encounters a Licensed
Internal Code problem.

Reference codes 491

E3xx

v E302: The HMC encountered a problem during an update of the firmware for the managed system. See
“(E302) Firmware update error codes.”
v E303: See “(E303) Formatting media error codes” on page 523.
v E332: Licensed Internal Code error codes. See “(E332) Licensed Internal Code error codes” on page 524.
v E338: An error occurred during the initialization of the components required for performing guided
maintenance from Service Focal Point. See “(E338) Licensed Internal Code error in guided maintenance
in Service Focal Point” on page 524.
v E355: See “(E355) errors” on page 524.
v E35A: See“(E35A) HMC code level” on page 526.
v E35F: See “(E35F) Persistence error codes” on page 526.
v E36C: See “(E36C) HMC scheduled task errors” on page 526.
v E3CA: Error regarding a media device. See “(E3CA) Error regarding a media device” on page 527.
v E3D4: See “(E3D4) Call home errors” on page 530.
v E3F0: See “(E3F0) Trace failure” on page 531.

For all other E3xx SRCs, use the following table.

Table 1. (E3xx) Licensed Internal Code error codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E3xxxxxx Licensed Internal Code failure on the HMC. NEXTLVL

Contact your service provider.

(E302) Firmware update error codes

The Hardware Management Console generates E302 error codes when it encounters a problem during an
update of the firmware for the managed system.

Table 1. (E302) Licensed Internal Code error codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E302Exxx Licensed Internal Code failure on the HMC.

Contact your service provider.

E302F000 to Licensed Internal Code failure on the HMC.
E302F7xx
Contact your service provider.
E302F800 An error occurred while attempting to create a provider instance of the
service processor interface code as a PIHSCCECCIMClient. An exception
was thrown from the PIHSCCECCIMClient createInstance code.

Go to the Server and Partition display, refresh the screen and ensure the
system is in a good state (for example, power off, standby, or operating).
Then repeat the operation.
E302F801 An error occurred while attempting to find one of the directories used to
store data for the firmware update application.

Reboot the HMC and try the operation again. If the problem occurs again,
contact your next level of support.

492 System i® and System p®: Reference codes

E302

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E302F802 The survey from the repository method was called, but the repository
selected was not the IBM support system, the IBM Web site, the DVD, or
the hard drive.

Use the HMC graphical user interface (GUI) to reselect the source for code
updates, then retry the update. If the problem occurs again, contact your
next level of support.
E302F803 The survey from an FTP site failed when downloading the list of files from
the FTP repository failed.

Verify that you correctly entered valid values for the FTP site, user,
password, and directory. Then repeat the operation.
E302F804 The request to get a list of IBM support system fixpacks failed because the
request timed out.

Verify that the HMC is properly configured to communicate with the IBM
support system. Verify that the IBM support system has accepted the
administrative information for your HMC, then repeat the operation.

Verify that you correctly entered valid values for the FTP site, user,
password, and directory. Then repeat the operation.
E302F805 The request to get a list of IBM support system fixpacks failed with an
exception.

Repeat the operation. If it fails, call your next level of support.

E302F806 The request to get a list of IBM support system fixpacks failed with an
error code.

Repeat the operation. If it fails, call your next level of support.

E302F807 No phone server was available to service the request to get a list of IBM
support system fixpacks.

Ensure that your connection to the IBM support system is set up correctly
and repeat the operation.
E302F808 The list of fixpacks was retrieved from the IBM support system, but an I/O
exception occurred when the list was written to the hard file.

Reboot the HMC and retry the operation. If it fails again, consider
replacing the disk drive in the HMC.
E302F809 An error occurred while attempting to run the code to get the service
processor to run a query, or set, the current IPL side or the next IPL side.

Go to the Server and Partition display, refresh the screen and ensure the
system is in a good state (for example, power off, standby, or operating).
Then repeat the operation.
E302F80A An invalid object was used while attempting to create an owner for the
update.

Something is wrong with the selected target. Reboot the HMC and retry
the operation. If the problem persists contact your next level of support.
E302F80B Unable to get the name of the HMC while preparing to create a service
processor client.

Reboot the HMC and retry the operation. If it fails again, contact your next
level of support.

Reference codes 493

E302

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E302F80C Failure when attempting to read a file.

Reboot the HMC and retry the operation. If it fails again, consider
replacing the disk drive of the HMC.
E302F80D Failure when attempting to close a file.

Reboot the HMC and retry the operation. If it fails again, consider
replacing the disk drive of the HMC.
E302F80E The list of fixpacks was retrieved from the IBM support system, but an I/O
exception occurred when closing the list that was written to the hard file.

Reboot the HMC and retry the operation. If it fails again, consider
replacing the disk drive of the HMC.
E302F80F The method to import the stageable cover letter was called, but the
repository selected was not the IBM support system, the IBM Web site,, the
DVD, or the hard drive.

Use the HMC GUI to reselect the source for code updates, and then retry
the update. If the problem occurs again, contact your next level of support.
E302F810 Unable to FTP the cover letter from the specified repository to the staging
area.

Verify that the FTP site is still up, and then retry the operation.
E302F811 The request to get cover letter from the IBM support system timed out.

Verify that your connection to the IBM support system is set up correctly
and is operational. Retry the operation. If the problem occurs again, contact
your next level of support.
E302F812 The request to get cover letter from the IBM support system failed with an
exception.

Verify that your connection to the IBM support system is set up correctly
and is operational. Retry the operation. If the problem occurs again, contact
your next level of support.
E302F813 The request to get cover letter from the IBM support system failed with an
error code.

Verify that your connection to the IBM support system is set up correctly
and is operational. Retry the operation. If the problem occurs again, contact
your next level of support.
E302F814 No phone server was available to service the request to get cover letters
from the IBM support system.

Configure the HMC as a phone server and retry the operation.

E302F815 Failure when attempting to copy the cover letter from the DVD to the
staging area on the hard file.

The CD or DVD may be faulty. Try another one.

E302F816 An error occurred when attempting to get the service processor to run a
query of its state.

Go to the Server and Partition display, refresh the screen and ensure the
system is in a good state (for example, power off, standby, or operating).
Then repeat the operation.

E302

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E302F843 An error occurred while attempting to issue a ″code update complete″
action to the master service processor.

Try the operation again. If the problem occurs again, contact your next
level of support.
E302F844 An error occurred while attempting to reboot the service processor

Try the operation again. If the problem occurs again, contact your next
level of support.
E302F845 The ″import from a remote repository″ code routine was called, but the
repository selected was not the IBM support system or the IBM Web site.

Use the HMC GUI to reselect the source for code updates. If the problem
occurs again, contact your next level of support.
E302F846 An error occurred while attempting to swap the T and P sides of the
service processor.

Try the operation again. If the problem occurs again, contact your next
level of support.
E302F847 An engineering change stream was passed between components, but no
such engineering change stream exists for the targeted object.

Reboot the HMC and try the operation again. If the problem occurs again,
contact your next level of support.
E302F848 A request to import the IBM support system fixpacks and cover letters
timed out.

Verify that your connection to the IBM support system is set up correctly
and is operational. Retry the operation. If the problem reoccurs, contact
your next level of support.
E302F849 A request to import the IBM support system fixpacks and cover letters
failed.

Verify that your connection to the IBM support system is set up correctly
and is operational. Retry the operation. If the problem reoccurs, contact
your next level of support.
E302F84A Failure during an attempt to read the surveyed list of fixpacks.

Reboot the HMC and try the operation again. If the problem occurs again,
consider replacing the disk drive of your HMC.
E302F84B Failure during an attempt to close the surveyed list of fixpacks.

Reboot the HMC and try the operation again. If the problem occurs again,
consider replacing the disk drive of your HMC.
E302F84C An error occurred while attempting to get the engineering change streams
in order to list all of the updates available on the removable media.

Reboot the HMC and try the operation again. If the problem occurs again,
contact your next level of support.
E302F84D An error occurred while trying to copy the RPM files from the media
repository to the hard file.

The CD or DVD may be faulty. Try another one.

498 System i® and System p®: Reference codes

E302

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E302F84E An error occurred in a removable media code routine because the file types
were null.

Reboot the HMC and try the operation again. If the problem occurs again,
contact your next level of support.
E302F84F An error occurred in a method because one of the file arrays had a length
of zero.

Reboot the HMC and try the operation again. If the problem occurs again,
contact your next level of support.
E302F850 A failure occurred while trying to unpack the RPM file in the ″complete
concurrently″ code routine.

Reboot the HMC and try the operation again. In the HMC code released
before August 2004, there was a problem that can be corrected with
commands from the Linux command line as follows:

ls -l /opt/ccfw/data/*.rpm
rpm -qp rpmfilename
(where rpmfilename is the name of the file returned by the ls command)

rpm -e rpm packagename

(where packagename is the name of the package returned by the rpm -e
command)
E302F851 The request to retrieve fixpacks from the IBM support system failed with
an error code.

Verify that your connection to the IBM support system is set up correctly
and is operational. Retry the operation. If the problem occurs again, contact
your next level of support.
E302F852 No phone server was available to serve the request to retrieve IBM support
system fixpacks.

Configure the HMC as a phone server and retry the operation.

E302F853 An error occurred while attempting to find the directory where firmware
update files are stored for testing with the non disruptive application
panel.

Reboot the HMC and try the operation again. If the problem occurs again,
contact your next level of support.
E302F854 An error occurred while attempting to issue a read firmware update file
command to a service processor

Try the operation again. If the problem occurs again, contact your next
level of support.
E302F855 Importing from an FTP site failed when the files from the FTP repository
were not retrieved.

Try the operation again. If the problem occurs again, contact your next
level of support.
E302F856 A failure occurred when trying to query the name of the image in the RPM
file.

Try the operation again. If the problem occurs again, contact your next
level of support.

Reference codes 499

E302

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E302F857 A failure occurred while attempting to issue the runact API.

Try the operation again. If the problem occurs again, contact your next
level of support.
E302F858 An exception occurred while attempting to issue the runact API.

Try the operation again. If the problem occurs again, contact your next
level of support.
E302F859 An exception occurred while trying to query the name of the image in the
RPM file.

Try the operation again. If the problem occurs again, contact your next
level of support.
E302F85A An exception occurred while trying to unpack the RPM file in the
″complete concurrently″ code routine.

Try the operation again. If the problem occurs again, contact your next
level of support.
E302F85B An exception occurred while trying to import updates from the DVD.

The CD or DVD may be faulty. Try another one.

E302F85C An error occurred while attempting to copy the T side to the P side.

In the Licensed Internal Code Update panels, choose Select advanced

features, and then choose Accept to copy the T side to the P side. If the
problem occurs again, contact your next level of support.
E302F85D An error occurred while attempting to IPL the system unit.

The level of code requested is most likely activated on the targeted system,
but not loaded into the hypervisor firmware. Verify the activated level
through System Information. If the activated level is what is expected,
schedule a time to IPL the system.
E302F871 An error occurred during the call to start firmware update to concurrently
patch firmware.

The level of code requested is most likely activated on the targeted system,
but not loaded into the server firmware. Verify the activated level through
System Information. If the activated level is what is expected, schedule a
time to IPL the system.
E302F873 Rebooting the service processor was executed, but the system unit did not
return to the state where the T side was active within a reasonable amount
of time. This generally means that the system was not successful when
coming up with the new code level and went back to the older code level

Retry the operation. To do this, select Select Advanced Features and then
select Install And Activate. If the code update fails again, contact your
next level of support.
E302F874 Rebooting the service processor was executed, but the system unit did not
return to its original state within a reasonable amount of time.

Go to the Server and Partition display, refresh the screen and ensure the
system is in a good state (for example, power off, standby, or operating). If
it is not in a good state, then take the necessary steps to put it in a good
state. After it is in a good state, check System Information to ensure the
code update was applied. If it is now in a good state but the update is not
applied, repeat the operation.
E302F875 An error occurred while attempting to query (at standby) in an attempt to
retrieve all of the updates from the removable media.

The CD or DVD may be faulty. Try another one.

E302F876 A failure occurred while trying to query the name of the image in the RPM
file.

Reboot the HMC and try the operation again. If the problem occurs again,
contact your next level of support.
E302F877 An exception occurred while trying to query the name of the image in the
RPM file.

Reboot the HMC and try the operation again. If the problem occurs again,
contact your next level of support.
E302F878 A failure occurred trying to erase an RPM file.

Reboot the HMC and try the operation again. If the problem occurs again,
contact your next level of support.

Reference codes 503

E302

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E302F879 An exception occurred trying to erase an RPM file.

Reboot the HMC and try the operation again. If the problem occurs again,
contact your next level of support.
E302F87A A failure occurred while trying to change the permissions of an image file
after it had been pulled from an RPM package.

Reboot the HMC and try the operation again. If the problem occurs again,
contact your next level of support.
E302F87B An exception occurred while trying to change the permissions of an image
file after it had been pulled from an RPM package.

Reboot the HMC and try the operation again. If the problem occurs again,
contact your next level of support.
E302F87C After the flash write to the primary service processor was complete, the
secondary service processor did not complete operations within half an
hour.
v For systems using HMC firmware before V5R1.1, the secondary service
processor will be synchronized in the next code update. If this does not
occur, contact your next level of support.
v For systems using V5R1.1 (or newer) HMC firmware, follow the
appropriate replace and verify procedure to synchronize the secondary
service processor firmware to the primary firmware. Ensure that you set
up the service processor failover feature as desired after you complete
the replace and verify procedure.
E302F87D A failure occurred importing I/O microcode.

Try the operation again. If the problem occurs again, contact your next
level of support.
E302F87E An IPL of the service processor was executed as part of a disruptive
firmware update, but it did not put the system in its original state within a
reasonable amount of time.

Go to the Server and Partition display, refresh the screen and ensure the
system is in a good state (for example, power off, standby, or operating). If
it is not in a good state, take the necessary steps to put it in a good state.
After it is in a good state, check System Information to ensure the code
update was applied.
E302F87F Powering off the service processor was executed as part of a disruptive
firmware update, but it did not put the service processor in a powered off
state within a reasonable amount of time.

Go to the Server and Partition display, refresh the screen and ensure the
system is in a good state (for example, power off, standby, or operating). If
it is not in a good state, take the necessary steps to put it in a good state.
After it is in a good state, repeat the code update operation.
E302F880 Powering on the service processor was executed as part of a disruptive
firmware update, but it did not put the service processor in a powered on
state within a reasonable amount of time.

504 System i® and System p®: Reference codes

E302

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E302F881 An IPL was executed as part of a disruptive firmware update, but the
managed system was placed in an error state.

If this message occurs, contact your next level of support.

E302F882 A power off was executed as part of a disruptive firmware update, but the
managed system was placed in an error state.

If this message occurs, contact your next level of support.

E302F883 A power on was executed as part of a disruptive firmware update, but the
managed system was placed in an error state.

If this message occurs, contact your next level of support.

E302F884 The service processor was rebooted during a firmware update, but it did
not put the service processor in a ″not connected″ state within a reasonable
amount of time.

Go to the Server and Partition display, refresh the screen and ensure the
system is in a good state (for example, power off, standby, or operating). If
it is not in a good state, take the necessary steps to put it in a good state.
When in a good state, check System Information to ensure the code update
was applied. If it is now in a good state but the update is not applied, then
repeat the operation.
E302F885 The service processor was rebooted during a firmware update, which put
the service processor in a ″not connected″ state. However, this action did
not clear the ″not connected″ state within a reasonable amount of time.

Contact the next level of support for assistance in getting the HMC to
communicate with the service processor again.
E302F886 An exception occurred during execution of the synchronous import
program while retrieving code from a repository.

If this message occurs, contact your next level of support.

E302F887 An exception occurred during execution of the synchronous apply staged
updates program while applying code from the hard file staging area.

If this message occurs, contact your next level of support.

E302F888 A chsyscfg command was issued to change the next IPL side, but it failed.

Reboot the HMC and try the operation again. If the problem occurs again,
contact your next level of support.
E302F889 An exception occurred after a chsyscfg command was issued to change the
next IPL side.

Reboot the HMC and try the operation again. If the problem occurs again,
contact your next level of support.
E302F88A Powering off the system unit has started.
E302F88B Reading of the firmware update files has started.
E302F88C Writing of the firmware update files has started.
E302F88D Rebooting the service processor has started.
E302F88E Powering on the system unit has started.
E302F88F Restoring of the firmware update files to the P side has started.

Reference codes 505

E302

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E302F890 An error occurred while attempting to find the directory used as temporary
storage.

Reboot the HMC and try the operation again. If the problem occurs again,
contact your next level of support.
E302F891 Failure when attempting to import an RPM package from the IBM Web
site.

Verify that your LAN connections are set up properly and retry the
operation. If the problem occurs again, contact your next level of support.
E302F892 A request was received to take the service processor back to an earlier
level, but it was a concurrent request. This operation can only be
performed disruptively.

Reboot the HMC and schedule time for a disruptive update. Retry the
operation during that scheduled time. If the problem occurs again, contact
your next level of support.
E302F893 A general error occurred while applying code.

If another error occurs before this message, follow the action for that error.
If this message occurs by itself, contact your next level of support.
E302F894 A general error occurred while processing a hardware upgrade.

If another error occurs before this message, follow the action for that error.
If this message occurs by itself, contact your next level of support.
E302F895 A general error occurred while committing code.

If another error occurs before this message, follow the action for that error.
If this message occurs by itself, contact your next level of support.
E302F896 A general error occurred while exporting code to the DVD.

If another error occurs before this message, follow the action for that error.
If this message occurs by itself, contact your next level of support.
E302F897 A general error occurred while importing code.

If another error occurs before this message, follow the action for that error.
If this message occurs by itself, contact your next level of support.
E302F898 A general error occurred while rejecting code.

If another error occurs before this message, follow the action for that error.
If this message occurs by itself, contact your next level of support.
E302F899 An attempt was made to update the hypervisor firmware, but the
hypervisor reported that it is already at that level.
E302F89A A general error occurred while updating the flash on a service processor.

If another error occurs before this message, follow the action for that error.
If this message occurs by itself, contact your next level of support.

506 System i® and System p®: Reference codes

E302

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E302F89B An error occurred while swapping the T and P sides of the secondary
service processor.
v For systems using HMC firmware before V5R1.1, the secondary service
processor will be synchronized in the next code update. If this does not
occur, contact your next level of support.
v For systems using V5R1.1 (or newer) HMC firmware, follow the
appropriate replace and verify procedure to synchronize the secondary
service processor firmware to the primary firmware. Ensure that you set
up the service processor failover feature as desired after you complete
the replace and verify procedure.
E302F89C An error occurred while copying the T to the P side on the secondary
service processor.
v For systems using HMC firmware before V5R1.1, the secondary service
processor will be synchronized in the next code update. If this does not
occur, contact your next level of support.
v For systems using V5R1.1 (or newer) HMC firmware, follow the
appropriate replace and verify procedure to synchronize the secondary
service processor firmware to the primary firmware. Ensure that you set
up the service processor failover feature as desired after you complete
the replace and verify procedure.
E302F89D A failure occurred either writing the firmware to the bulk power
assemblies (BPAs), or rebooting them after writing the firmware.

If another error occurs before this message, follow the action for that error.
If this message occurs by itself, contact your next level of support.
E302F89E A failure occurred while trying to erase a file.

If another error occurs before this message, follow the action for that error.
If this message occurs by itself, contact your next level of support.
E302F89F An attempt to set a lock on a BPA frame failed. The BPA is locked by
another process.

Do the following as applicable:

1. Make sure that you do not select multiple managed systems (that are
associated with the same power frame) for simultaneous managed
system and power code update or upgrade.
2. Allow all currently running code update processes to end successfully
on all of the associated HMCs.
3. Ensure that all frame numbering, frame initialization, and repair and
verify processes that also use BPA locking end successfully on all of the
associated HMCs.
4. After all the operations are finished and a retargeting to one of the
managed systems still results in this error, remove the BPA lock. To
remove the BPA lock, use the following command from the HMC:
rmlock –e Frame*MTMS

where Frame*MTMS is the machine-type, model, and serial number of

the affected BPA.
5. Retry the operation. If the error occurs again, contact your next level of
support.

Reference codes 507

E302

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E302F8A0 An error occurred while trying to read the list of fixpacks that was
surveyed.

Reboot the HMC and retry the operation. If the problem occurs again,
consider replacing the disk drive of the HMC.
E302F8A1 An error occurred while trying to close the list of fixpacks that was
surveyed.

Reboot the HMC and retry the operation. If the problem occurs again,
consider replacing the disk drive of the HMC.
E302F8A2 An error occurred while attempting to update the server firmware.

Try the operation again. If the error occurs again, contact your next level of
support.
E302F8A3 An error occurred while querying to see if the server firmware diff file is in
memory.

Try the operation again. If the error occurs again, contact your next level of
support.
E302F8A4 An exception occurred while querying to see if the server firmware diff file
is in memory.

Try the operation again. If the error occurs again, contact your next level of
support.
E302F8A5 An exception occurred while querying to see if the HMC is the code
update owner.

Try the operation again. If the error occurs again, contact your next level of
support.
E302F8A6 An exception occurred while setting the HMC to be the code update
owner.

Try the operation again. If the error occurs again, contact your next level of
support.
E302F8A7 Licensed Internal Code failure on the HMC.

Contact your service provider.

E302F8A8 Querying to see if the service firmware diff file is in memory did not
return the proper number of elements in the vector.

Try the operation again. If the error occurs again, contact your next level of
support.
E302F8A9 A general error occurred while rebooting.

If another error occurs before this message, follow the action for that error.
If this message occurs by itself, contact your next level of support.
E302F8AA An error occurred when attempting to copy the P-side flash memory to the
T-side on the master service processor.

Try the operation again. If the error occurs again, contact your next level of
support.
E302F8AB An error occurred when attempting to copy the P-side flash memory to the
T-side on the secondary service processor.

Try the operation again. If the error occurs again, contact your next level of
support.

508 System i® and System p®: Reference codes

E302

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E302F8AC to Licensed Internal Code failure on the HMC.
E302F8CF
Contact your service provider.
E302F8D0 An I/O error occurred while reading the fixpack image.

Reboot the HMC and retry the operation. If the problem occurs again,
consider replacing the disk drive in the HMC.
E302F8D1 An error occurred while writing a firmware update file that was read from
a fixpack to disk.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F8D2 to Licensed Internal Code failure on the HMC.
E302F8EF
Contact your service provider.
E302F8F0 An error occurred while surveying the IBM Web site.

Verify that your LAN connections are set up properly and retry the
operation. If the problem occurs again, contact your next level of support.
E302F8F1 An exception occurred while surveying the IBM Web site.

Verify that your LAN connections are set up properly and retry the
operation. If the problem occurs again, contact your next level of support.
E302F8F2 An exception occurred while copying the XML file to the cover letter
during importation from the Web site.

Verify that your LAN connections are set up properly and retry the
operation. If the problem occurs again, contact your next level of support.
E302F8F3 Two hour wait period exceeded for the updating of firmware on the service
processor in the bulk power assembly.

If another error occurs before this message, follow the action for that error.
If this message occurs by itself, contact your next level of support.
E302F8F4 An error occurred while surveying the IBM Web site. The file was not
found at the Web site.

Verify that the HMC connection to the IBM Web site is working by using
the information center HELP links on the local HMC master console.
Access the IBM Web site by using the links in information center that
activate the Web browser on the HMC. If the HMC cannot connect to the
IBM Web site, contact the network administrator for your installation to
determine if a firewall or other network security process must be opened
for the HMC to access the Internet. If the HMC is on a private network, the
IBM Web site will not be available as a repository. Retry the operation
again after you successfully access the IBM Web site. If the error occurs
again, contact your next level of support.
E302F8F5 to Licensed Internal Code failure on the HMC.
E302F8FF
Contact your service provider.
E302F900 The survey from an FTP site failed when the control program was not able
to change the directory to that of the user.

Verify that the FTP site directory specified is correct and that any firewall
authentications were completed, if necessary, before performing the update.
Try the operation again. If the problem occurs again, contact your next
level of support.

Reference codes 509

E302

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E302F901 A query of the current boot side of the secondary processor returned a null.

Verify that the authentication passwords for the service processors are
synchronized and that the TCP/IP addresses of the service processors are
not in the HMC DHCP server’s removed list. Use the Update Managed
System Password field under the Server and Partition panels to reset the
password if necessary. Use the restricted shell ″mksysconn -o auto″
command to reset the HMC DHCP server’s removed list and reconnect the
affected service processors. If the problem occurs again, contact your next
level of support.
E302F902 A query of the next boot side of the secondary processor returned a null.

Verify that the authentication passwords for the service processors are
synchronized and that the TCP/IP addresses of the service processors are
not in the HMC DHCP server’s removed list. Use the Update Managed
System Password pulldown under the Server and Partition panels to reset
the password if necessary. Use the restricted shell ″mksysconn -o auto″
command to reset the HMC DHCP server’s removed list and reconnect the
affected service processors. If the problem occurs again, contact your next
level of support.
E302F903 to Licensed Internal Code failure on the HMC.
E302F90F
Contact your service provider.
E302F910 An exception occurred when querying to find out if the bulk power
assembly was N-mode.

Verify that both the primary and secondary service processors for the bulk
power assembly (or assemblies) are configured properly and available for
communication with the HMC. This is a requirement. Retry the operation.
If the problem occurs again, contact your next level of support.
E302F911 A failure occurred when querying to find out if the bulk power assembly
was N-mode.

Verify that both the primary and secondary service processors for the bulk
power assembly (or assemblies) are configured properly and available for
communication with the HMC. This is a requirement. Retry the operation.
If the problem occurs again, contact your next level of support.
E302F912 One of the bulk power assemblies targeted for firmware update has
N-mode power.

Verify that both the primary and secondary service processors for the bulk
power assembly (or assemblies) are configured properly and available for
communication with the HMC. This is a requirement. Retry the operation.
If the problem occurs again, contact your next level of support.
E302F913 One of the bulk power assemblies targeted for firmware update has an
auto-code download (ACDL) pending.

A code update cannot be performed while a service processor in the bulk

power assembly is running an auto-code download process. Depending on
the number of FRUs being loaded, this process might take a significantly
long time. After two hours, try the original operation again. If the failure
occurs again, wait two hours and manually point the next re-IPL of the
service processor to the ″P″ side by using the Flash Side Selection panels.
Perform a ″Disruptive Activate″ using the Select advanced features panels.
Wait two hours for that auto-code download to complete, then try the
original operation again. If the problem occurs again, contact your next
level of support.

510 System i® and System p®: Reference codes

E302

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E302F914 An exception occurred when attempting to start the auto-code download
(ACDL) on a bulk power assembly.
v For systems using HMC firmware before V5R2, contact your next level
of support.
v For systems using V5R2 (or newer) HMC firmware, do the following:
1. Choose Select advanced features.
2. Perform an Install and activate (implied Retrieve) Specific Level
update to the current level of power firmware on the hard drive
repository. (Choose Automatically Accept.)
3. Click Change Levels, and change None to the current level of power
firmware.
4. Leave the Managed System code level as None, and then finish the
code update.
If the problem occurs again, contact your next level of support.
E302F915 A failure occurred when attempting to start the auto-code download
(ACDL) on a bulk power assembly.
v For systems using HMC firmware before V5R2, contact your next level
of support.
v For systems using V5R2 (or newer) HMC firmware, do the following:
1. Choose Select advanced features.
2. Perform an Install and activate (implied Retrieve) Specific Level
update to the current level of power firmware on the hard drive
repository. (Choose Automatically Accept.)
3. Click Change Levels, and change None to the current level of power
firmware.
4. Leave the Managed System code level as None, and then finish the
code update.
If the problem occurs again, contact your next level of support.
E302F916 An exception occurred when attempting to determine how many FRUs
were completed during an auto-code download (ACDL).
v For systems using HMC firmware before V5R2, contact your next level
of support.
v For systems using V5R2 (or newer) HMC firmware, do the following:
1. Choose Select advanced features.
2. Perform an Install and activate (implied Retrieve) Specific Level
update to the current level of power firmware on the hard drive
repository. (Choose Automatically Accept.)
3. Click Change Levels, and change None to the current level of power
firmware.
4. Leave the Managed System code level as None, and then finish the
code update.
If the problem occurs again, contact your next level of support.

Reference codes 511

E302

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E302F917 A failure occurred when attempting to determine how many FRUs were
completed during an auto-code download (ACDL).
v For systems using HMC firmware before V5R2, contact your next level
of support.
v For systems using V5R2 (or newer) HMC firmware, do the following:
1. Choose Select advanced features.
2. Perform an Install and activate (implied Retrieve) Specific Level
update to the current level of power firmware on the hard drive
repository. (Choose Automatically Accept.)
3. Click Change Levels, and change None to the current level of power
firmware.
4. Leave the Managed System code level as None, and then finish the
code update.
If the problem occurs again, contact your next level of support.
E302F918 The auto-code download (ACDL) took too long on one side of the bulk
power assembly.
v For systems using HMC firmware before V5R2, contact your next level
of support.
v For systems using V5R2 (or newer) HMC firmware, do the following:
1. Choose Select advanced features.
2. Perform an Install and activate (implied Retrieve) Specific Level
update to the current level of power firmware on the hard drive
repository. (Choose Automatically Accept.)
3. Click Change Levels, and change None to the current level of power
firmware.
4. Leave the Managed System code level as None, and then finish the
code update.
If the problem occurs again, contact your next level of support.
E302F919 The auto-code download (ACDL) began but did not complete successfully.

Follow the actions listed for E302F918.

E302F91A An error occurred in the service processor support code during a query of
the state of a service processor for a frame.

Reboot the HMC and retry the operation. If the error occurs again, contact
your next level of support.
E302F91B A failure occurred when attempting to query the state of the system unit
after receiving an asynchronous report that the state had changed.

Reboot the HMC and retry the operation. If the error occurs again, contact
your next level of support.
E302F91C A failure occurred while copying the firmware from the T side to the P side
after a successful update of the bulk power controller code.

Perform an ″Accept″ operation using the Select advanced features panels.

This operation also accepts the system unit code. If the problem occurs
again, contact your next level of support.
E302F91D A failure occurred when trying to deactivate a bulk power assembly.

Reboot the HMC and retry the operation. If the error occurs again, contact
your next level of support.

512 System i® and System p®: Reference codes

E302

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E302F91E Licensed Internal Code failure on the HMC.

Contact your service provider.

E302F91F An exception occurred when trying to deactivate a bulk power assembly.

Reboot the HMC and retry the operation. If the error occurs again, contact
your next level of support.
E302F920 An I/O error occurred when attempting to write the power FRU code
levels to a file.

Ensure the following:

v That ample space exists in the file system that contains the /opt/ccfw
directory
v That the a user with root authority executes the following command:
dlslic –e Frame*MTMS
Note: The dlslic command is a diagnostic aid that obtains ACDL status
and creates the bpa.frus.lst file in /opt/ccfw/data directory. After you clear
the file space, if necessary, execute the dlslic command again as a user with
root authority. If the error occurs again, contact your next level of support.
E302F921 An I/O error occurred when attempting to close the file containing the
Power FRU code levels.

Perform the actions for error code E302 F920. If the error occurs again,
contact your next level of support.
E302F922 An exception occurred when attempting to set or release a lock on a bulk
power adapter frame.

Perform the actions for error code E302 F89F. If the error occurs again,
contact your next level of support.
E302F923 A failure occurred during a query of the current service processor failover
state.
v If another error occurs before this message, follow the action for that
error.
v If this message occurs during a code update Health Check, correct the
condition that caused the Health Check to fail and retry the operation.
v If this message occurs by itself, contact your next level of support.
E302F924 An exception occurred during the query of the current service processor
failover state.
v If another error occurs before this message, follow the action for that
error.
v If this message occurs during a code update Health Check, correct the
condition that caused the Health Check to fail and retry the operation.
v If this message occurs by itself, contact your next level of support.
E302F925 A failure occurred when attempting to set the service processor failover
state with the chsyscfg command.
v If another error occurs before this message, follow the action for that
error.
v If this message occurs during a code update Health Check, correct the
condition that caused the Health Check to fail and retry the operation.
v If this message occurs by itself, contact your next level of support.

Reference codes 513

E302

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E302F926 An exception occurred when attempting to set the service processor
failover state with the chsyscfg command.

Follow the actions listed for E302F925.

E302F927 An error occurred when attempting to acquire the service processor lock.

Reboot the HMC and retry the operation. If the error occurs again, contact
your next level of support.
E302F928 A timeout error occurred when attempting to acquire the service processor
lock.

Check to see if a long running DLPAR operation is in progress to the same

managed system. If there is, wait for that operation to complete and then
perform a Disruptive Activate. If the error occurs again, contact your next
level of support.
E302F929 An error occurred when attempting to release the service processor lock.

Reboot the HMC and retry the operation. If the error occurs again, contact
your next level of support.
E302F92A Dynamic service processor failover has been disabled.

Informational message.
E302F92B Dynamic service processor failover has been enabled.

Informational message.
E302F92C A firmware update reboot of the secondary service processor placed it into
a not connected state, but it did not clear that state in a reasonable amount
of time.

Contact the next level of support for assistance in getting the HMC to talk
to the service processor again.
E302F92D During readiness checking, an exception occurred in the
readBPAPowerStatus() method when attempting to determine the status of
the power subsystem.

Reboot the HMC and retry the operation. If the error occurs again, contact
your next level of support.
E302F92E During readiness checking, a null value was returned by the
readBPAPowerStatus() method when attempting to determine the status of
the power subsystem.

Reboot the HMC and retry the operation. If the error occurs again, contact
your next level of support.
E302F92F During readiness checking, an exception occurred in the
getConnectionStatus() method when attempting to determine the status of
power subsystem connections.

Reboot the HMC and retry the operation. If the error occurs again, contact
your next level of support.
E302F930 During readiness checking, a null value was returned by the
getConnectionStatus() method when attempting to determine the status of
power subsystem connections.

Reboot the HMC and retry the operation. If the error occurs again, contact
your next level of support.

514 System i® and System p®: Reference codes

E302

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E302F931 During readiness checking, an exception occurred in the getState() method
when attempting to determine the state of the power subsystem.

Reboot the HMC and retry the operation. If the error occurs again, contact
your next level of support.
E302F932 During readiness checking, an exception occurred in the isNModePower()
method when attempting to determine the state of the power subsystem.

Reboot the HMC and retry the operation. If the error occurs again, contact
your next level of support.
E302F933 During readiness checking, an exception occurred in the
getRedundantFspInfoExt() method when attempting to determine the state
of the secondary service processor.

Reboot the HMC and retry the operation. If the error occurs again, contact
your next level of support.
E302F934 During readiness checking, a null value was returned by the
getRedundantFspInfoExt() method when attempting to determine the state
of the secondary service processor.

Reboot the HMC and retry the operation. If the error occurs again, contact
your next level of support.
E302F935 During readiness checking, an exception occurred in the getState() method
when attempting to determine the state of the managed system.

Reboot the HMC and retry the operation. If the error occurs again, contact
your next level of support.
E302F936 During readiness checking, an exception occurred in the
getConnectionStatus() method when attempting to determine the status of
service processor connections.

Reboot the HMC and retry the operation. If the error occurs again, contact
your next level of support.
E302F937 During readiness checking, a null value was returned by the
getConnectionStatus() method when attempting to determine the status of
service processor connections.

Reboot the HMC and retry the operation. If the error occurs again, contact
your next level of support.
E302F938 to Licensed Internal Code failure on the HMC.
E302F9AA
Contact your service provider.
E302F9AB An error occurred during the processing for the update licensed internal
code MES select level panel handler.

Reboot the HMC and retry the operation. If the error occurs again, contact
your next level of support.
E302F9AC An error occurred during the processing for the update licensed internal
code main repository panel handler.

Reboot the HMC and retry the operation. If the error occurs again, contact
your next level of support.

Reference codes 515

E302

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E302F9AD An error occurred during the processing for the update licensed internal
code FTPpanel panel handler.

Reboot the HMC and retry the operation. If the error occurs again, contact
your next level of support.
E302F9AE An error occurred during the processing for the update licensed internal
code changeFTP panel handler.

Reboot the HMC and retry the operation. If the error occurs again, contact
your next level of support.
E302F9AF An error occurred during the processing for the advanced features task
when trying to run a tasklet exit on the client to display the license panel.
The task is terminated.

Reboot the HMC and retry the operation. If the error occurs again, contact
your next level of support.
E302F9B0 An error occurred during the processing for the MES upgrade task when
trying to run a tasklet exit on the client to display the license panel. The
task is terminated.

Reboot the HMC and retry the operation. If the error occurs again, contact
your next level of support.
E302F9B1 An error occurred during the processing for the change internal code
wizard when trying to run a tasklet exit on the client to display the license
panel. The task is terminated.

Reboot the HMC and retry the operation. If the error occurs again, contact
your next level of support.
E302F9B2 Error during processing for the Change Internal Code Wizard

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9B3 Error during processing for an internal code method.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9B4 to Error during processing for an internal panel handler.
E302F9B6
Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9B7 Error during processing of the server side of the scheduleable update task.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9B8 Error trying to perform processing in a hardware upgrade code path.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9B9 Error during the main ″service″ processing for the server side of the
hardware upgrade task. The task has been terminated.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.

516 System i® and System p®: Reference codes

E302

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E302F9BA Error during the main processing for the client side of the hardware
upgrade task. The task has been terminated.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9BB Error during the main processing for the server side of the hardware
upgrade task.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9BC Error during the processing of the actual non disruptive firmware update
task. The progress panel for the affected target is updated with error
message. The task continues to execute.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9BD Error during the main ″service″ processing for the server side of the change
internal code wizard subtasklet.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9BE Error during the main ″service″ processing for the server side of the change
internal code wizard1 panel handler.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9BF Error during the main ″service″ processing for the server side of the change
internal code wizard2 panel handler.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9C0 Error during the main ″service″ processing for the server side of the change
internal code wizard3 panel handler.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9C1 Error during the main ″service″ processing for the server side of the change
internal code wizard4 panel handler.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9C2 Error during the main ″service″ processing for the server side of the change
internal code wizard cecconcurrency panel handler.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9C3 Error during the main ″service″ processing for the server side of the change
internal code wizard cecdetails panel handler.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9C4 Error during the main ″service″ processing for the server side of the change
internal code wizard fix details panel handler.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.

Reference codes 517

E302

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E302F9C5 Error during the main ″service″ processing for the server side of the change
internal code wizard license panel handler.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9C6 Error during the main ″service″ processing for the server side of the change
internal code wizard leveldetails panel handler.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9C7 Error during the main processing for the server side of the flash side
selection task.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9C8 Error during the main ″service″ processing for the server side of the
advanced features subtasklet.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9C9 Error during processing for the advanced features panel handler.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9CA Error during processing for the advanced features retrieve panel handler.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9CB Error during processing for the advanced features implied retrieve panel
handler.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9CC Error during processing for the advanced features change levels panel
handler.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9CD Error during processing for the advanced features select change levels
panel handler.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9CE Error during processing for the advanced features install type panel
handler.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9CF Error during processing for the advanced features fix details panel handler.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9D0 Error during processing for the advanced features confirm panel handler.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.

518 System i® and System p®: Reference codes

E302

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E302F9D1 Error during processing for the advanced features level details panel
handler.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9D2 Error during the main ″service″ processing for the server side of the change
internal code task. The task is terminated.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9D3 Error during processing change internal code MainPanel panel handler. The
task is terminated.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9D4 Error during processing change internal code MainRepos panel handler.
The task is terminated.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9D5 Error during processing change internal code InbandMessage panel
handler. The task is terminated.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9D6 Error during processing change internal code FtpPanel panel handler. The
task is terminated.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9D7 Error during processing change internal code ChangeFTP panel handler.
The task is terminated.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9D8 Error trying to assign values from a SysInfoEcInternalCodeData object.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9D9 Error during the main processing for the server side of the system
information task.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9DA Error from getting null presentation task parameters in the system
information task.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9DB Error during the processing for the server side SysInfoEcTasklet system
information subtask.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.

E302

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E302F9FC Error in the change internal code wizard1 bean panelAction method. This
bean attempts to close the panel.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9FD Error in the change internal code wizard2 bean panelAction method. This
bean attempts to close the panel.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9FE Error in the change internal code wizard3 bean panelAction method. This
bean attempts to close the panel.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302F9FF Error in the change internal code wizard4 bean panelAction method. This
bean attempts to close the panel.

Reboot the HMC and retry the operation. If the problem occurs again,
contact your next level of support.
E302FA00 An error occurred while attempting to synchronize one service processor to
the other during a repair and verify operation.

Ensure that the entire repair and verify procedure executed correctly and
that the new service processor is communicating properly. If the error
continues to occur, contact your next level of support.
E302FA01 An error occurred while attempting to determine which service processor is
the source and which one is the destination for a repair and verify
operation.

Ensure that the entire repair and verify procedure executed correctly and
that the new service processor is communicating properly. If the error
continues to occur, contact your next level of support.
E302FA02 An error occurred while attempting to create a targeted service processor
object during a repair and verify operation.

Ensure that the entire repair and verify procedure executed correctly and
that the new service processor is communicating properly. If the error
continues to occur, contact your next level of support.
E302FA03 to Licensed Internal Code failure on the HMC.
E302FFFF
Contact your service provider.

(E303) Formatting media error codes

Table 1. (E303) Formatting media error codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E303300D Format Media application had an error trying to display a format message
panel on the screen. Perform the following steps:
1. Exit or Cancel the Format Media application.
2. Retry the operation

Reference codes 523

E303

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E3033011 Format Media encountered a problem accessing the removable media it is
trying to format. Perform the following steps:
1. Check the media to see if it is inserted correctly.
2. Retry the operation
3. If it still fails, the media being formatted may be defective. Try a
different media.

(E332) Licensed Internal Code error codes

Table 1. (E332) Licensed Internal Code error codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E3326601 The HMC failed to retrieve a platform system dump from the managed
system. For details, refer to reference code B3036601.
E33326602 The HMC failed to retrieve a dump from the service processor. For details,
refer to reference code B3036601.
E3326604 The HMC failed to retrieve a power subsystem dump from the managed
system. For details, refer to reference code B3036604.
E332FFFF This error occurs when the HMC receives notification that a particular
Java™ code string is corrupted. If you have the call home feature enabled,
the failure information (including the JavaCore) will be transmitted to
service and support. The support organization will examine the JavaCore
file. Otherwise, you can retry the task.

(E338) Licensed Internal Code error in guided maintenance in Service

Focal Point
An error occurred during the initialization of the components required for performing guided
maintenance from Service Focal Point.

Table 1. (E338) Licensed Internal Code error in Guided Maintenance in Service Focal Point

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E3380001 An error occurred during the initialization of the components required for NEXTLVL
performing guided maintenance from Service Focal Point.
E3380002 An error occurred during the initialization of the components required for NEXTLVL
performing guided maintenance from Service Focal Point.
E3380003 Licensed Internal Code failure on the Hardware Management Console
(HMC).

Contact your service provider.

E3380004 Licensed Internal Code failure on the HMC.

Contact your service provider.

(E355) errors
Table 1. (E355) errors

524 System i® and System p®: Reference codes

E355

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E3550037 Error initializing and or running a task. Depending on the type of
exception, the task might terminate.
E3550046 An uncaught exception has been caught by the thread group. An error log
is created to determine which code failed to handle the exception. The
secondary data block with ID "81" should be analyzed to determine the
code that is in error.
E355004D An out of memory exception has been caught in the Java Virtual Machine
(JVM). In addition to the log being created, a dump of the JVM has been
forced for this condition as well. Although it is possible the out of memory
condition will correct itself, the console application will be restarted by
problem analysis when this problem is analyzed.
E3550423 An uncaught exception has been caught. An error log is created to
determine which code failed to handle the exception. The secondary data
block with ID "81" should be analyzed to determine the code that is in
error.
E355049F Exception caught in updateChildrenOfGroup (). Look at the logged
exception for information about the error.
E3550550 Error found in the EventSummary tasklet.
E3550551 Error reading the log file.
E3550790 Error with configuration data. An error log is created to determine which
configuration data is in error.
E3550792 Error persisting an object or reading an object from persistence.
E3550813 Error launching a task. An error log is created to determine why the task
cannot be launched.
E3550830 An unexpected internal error occurred. Examine the actual exception to
determine the source and severity of the problem.
E3550832 There was an IO exception on the socket communication between a client
and the manager. Anything that causes a socket communication exception
can cause this log entry. The client or manager programs might have ended
abruptly or the connection between the two might have been physically
broken. Examine the actual IO exception and the environment in which it
occurred to determine the source and severity of the exception.
E3550911 An error occurred inside com.ibm.hwmca.base.userprof.UserProfTasklet
UserProfTasklet
E3550912 An error occurred inside com.ibm.hwmca.base.userprof.UserProfApp
UserProfApp
E3550913 Exception caught in getUIInfo(). Look at the logged HException for
information about the error.
E3550922 Exception caught in UserProfilesTasklet.
E3550950 Error trying to do the main processing for server side of the settings task.
This is the result of an exception being caught by the underlying Tasklet
infrastructure. The settings task has been ended.
E3550956 Error trying to do the main processing for client side of the network
settings task. This is the result of an exception being caught by the
underlying Tasklet infrastructure. The network settings task has been
ended.
E3550958 Error performing processing in the settings task action handler. The settings
task will likely continue to run, but it may not function as expected.

Reference codes 525

E355

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E3550959 Error performing processing in the network settings task action handler.
The network settings task will likely continue to run, but it may not
function as expected.
E355095C Error performing a firewall operation.
E3550996 An error occurred when updating the console tasks performed information.

(E35A) HMC code level

Table 1. (E35A) HMC code level error

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E35A003 The code did not function as designed. Retry the task.
E35A003 Your HMC restarts but the code it is running is Version 4 R4 or earlier.
9FEAA097 Check your HMC machine code level and update it to a minimum of
V4.R5.0. For details, see Determining your HMC machine code version and
release.

(E36C) HMC scheduled task errors

Table 1. (E36C) HMC scheduled task errors

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E36C0101 An error occurred during tasklet processing. Contact your next level of
support.
E36C0103 An error occurred while working with persisted scheduled operations.
Contact your next level of support.

(E35F) Persistence error codes

Table 1. (E35F) Persistence error codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E35F000 Error creating a new PersistenceManager. This error is logged when the
constructor of the PersistenceManager is called but the PersistenceManager
object could not be initialized correctly. For example, the path to the
persistent data store could not be created. The object is invalidated and
subsequent calls are rejected. That is, an exception is thrown for any
following calls to the PersistenceManager.
E35F0010 Error reading an object by the PersistenceManager. This error is logged
when during the read of an object an error occurs. The PersistenceManager
cannot reconstitute an object from the persistent data store.
E35F0011 Error decoding an object by the PersistenceManager.

This error is logged when during the decoding of an object an error occurs
(the error is usually an IOException). The PersistenceManager cannot
reconstitute an object from the persistent data store.
E35F0012 Error reconstituting an object by the PersistenceManager. This error is
logged when during the reconstitution a class object was not found. The
class object that was not found is the object describing the stored
PersistentData or Persistable. The PersistenceManager cannot
reconstitute an object from the persistent data store.

526 System i® and System p®: Reference codes

E35F

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E35F0013 Error reconstituting an object by the PersistenceManager. This error is
logged when during the reconstitution the required constructor to create a
Persistable from PersistentData was not found. The PersistenceManager
cannot reconstitute an object from the persistent data store.
E35F0014 Error reconstituting an object by the PersistenceManager. This error is
logged when during the reconstitution an unsupported version of the
PersistenceManager code was detected. The object to be reconstituted was
written by a different version of the PersistenceManager. The current code
does not support this version. The PersistenceManager cannot reconstitute
an object from the persistent data store.
E35F0020 Error writing an object by the PersistenceManager. This error is logged
when during the write of an object an error occurs. The
PersistenceManager cannot reconstitute an object from the persistent data
store.
E35F0021 Error encoding an object by the PersistenceManager. This error is logged
when during the encoding of an object an error occurs (the error is usually
an IOException). The PersistenceManager cannot create the encoded form
for an object.
E35F0030 Error performing the saveUpgradeData method. This error is logged when
during the saveUpgradeData task an error in the PersistenceManager
occurs. The log contains additional information on the error.
E35F0031 Error performing the restoreUpgradeData method. This error is logged
when during the restoreUpgradeData task an error in the
PersistenceManager occurs. The log contains additional information on the
error.
E35F0032 A parsing error occurred trying to parse the xml files representing
deployment preferences. The parsing occurs the first time a call is made to
Deployment.getPreferences().

Perform the following steps:

(E3D4) Call home errors

Table 1. (E3D4) Call home errors

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E3D43100 Error occurred while obtaining from call home request all data required for
RETAIN®.
E3D43101 Error building the RETAIN login information for the call home request.
E3D43102 Unsupported encoding error occurred while building the RETAIN login
information for the call home request.
E3D43103 Error returning result for the call home request.
E3D43104 Error obtaining credentials for the call home request.
E3D43105 Error obtaining data needed for credentials for the call home request.
E3D43106 Successful credential password update operation.
E3D43107 Successful system credential update operation.
E3D43108 Successful new credential operation.
E3D43108 Successful call home progress update.
E3D4310A Error occurred during submission of call home request.
E3D4310B Error occurred during file transfer associated with the call home request.
E3D4310C Error occurred during remote program execution associated with the call
home request.
E3D4310D Error adding the rsfstatusListener for the call home request.
E3D4310E Error getting the credentials from persistence for the call home request.
E3D4310F Need to update the credentials with new machine information.
E3D46F01 Error occurred while formatting the request parameters for RETAIN.

530 System i® and System p®: Reference codes

E3D4

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E3D46F10 Information RETAIN call home progressing.
E3D46F21 Error occurred retrieving a file to send to RETAIN.
E3D46F22 Error occurred compacting a file to be sent to RETAIN.
E3D46F23 Error occurred while performing local file path query.
E3D46F25 Error occurred reading a file to be sent to RETAIN.
E3D46F2D Error occurred writing a file sent from RETAIN.
E3D46F2E Error occurred executing a command issues from RETAIN.
E3D46F2F Error occurred writing a file sent from RETAIN.
E3D46F40 Error occurred getting the call home authentication token using system
credentials.
E3D46F41 Error with system authentication using system credentials.
E3D46F42 Error occurred communicating with service data receiver.
E3D46F43 Information SDR communication progressing.
E3D46F46 Error occurred connecting to RETAIN.
E3D46F71 Error occurred while parsing the command from RETAIN for the call home
request.
E3D46F72 Error reported from RETAIN for the call home request.
E3D46FB0 Error occurred sending or receiving from RETAIN.
E3D46FFF Internal error occurred while calling home. Remote connection services
might have returned an error.

(E3F0) Trace failure

Table 1. (E3F0) Trace failure

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E3F00004 The ’Perform Console Trace’ task located in Console Actions encountered
an error that caused it to end. Perform the following steps:
1. Retry the task.
Note: Do not interrupt the task while it is running.
2. If the problem persists, send the iqyylog.log to your next level of
support for analysis.
Note: To use the ’Perform Console Trace’ task, you must be a member of
the service representative role.

(E4xx) Licensed Internal Code error codes

The Hardware Management Console generates E4xx error codes when it encounters a Licensed Internal
Code problem.

Table 1. (E4xx) Licensed Internal Code progress codes

Reference Code Description/Action Perform all actions before exchanging Failing Items Failing Item
E4xxxxxx Licensed Internal Code failure on the Hardware Management Console NEXTLVL
(HMC).

Contact your service provider.

Reference codes 531

Using system reference codes

System reference codes (SRCs) indicate a server hardware or software problem that can originate in
hardware, in Licensed Internal Code, or in the operating system.

A server component generates an error code when it detects a problem. An SRC identifies the component
that detected the error code and describes the error condition. Use the SRC information to identify a list
of possible failing items and to find information about any additional isolation procedures.

SRC formats

SRCs are strings of either six or eight alphanumeric characters. The characters in the SRC typically
represent the reference code type and the unit reference code (URC):
v For SRCs displayed on the control panel, the first four characters designate the reference code type and
the second four characters designate the URC.
v For SRCs displayed on software displays, characters 1 through 4 of word 1 designate the reference
code type and characters 5 through 8 of word 1 designate the URC.

Note: For partition firmware SRCs (AAxx, BAxx, and DAxx) and service processor SRCs (A1xx and
B1xx), only the first two characters of the SRC indicate the necessary action. For partition firmware
SRCs that begin with 2xxx, only the first character indicates the necessary action. In these cases,
the term URC does not apply.

A reference code that is 6 or 8 characters long and appears in either of the following formats (xxxxxx or
xxxxxxxx) is an SRC, unless it fits one of the following conditions:
v An 8-character code that begins with a C (except CB) or D (except DA) is a progress code
v An 8-character code that begins with an H is a Hardware Management Console (HMC) error code or
message
v A 6-character code that begins with a zero (0) and does not include a hyphen is an HMC error code
v A code that begins with a number sign character (#) represents an AIX diagnostics message.

Using the list of reference codes

The list of system reference codes is organized in hexadecimal sequence, with numeric characters listed
before alphabetic characters. Each entry in the list represents the first four characters (the reference code
type) of the SRC. The entries link to more information, typically a table that lists the URCs that are
associated with that reference code type.

Unless specified otherwise on a particular SRC page, the SRC tables contain the following columns:
v The Reference Code column contains numbers that represent the unit reference code (URC).
v The Description/Action column offers a brief description of the failure that this SRC represents. It may
also contain instructions for continuing the problem analysis.
v The Failing Item column represents functional areas of the system unit. When available, the failing
function code links to the FRU that contains this function for each specific system unit.

To use the list of system reference codes, complete the following steps:
1. Click the item in the list of system reference codes that matches the reference code type that you want
to find.

Note: The SRC tables support only 8-character reference code formats. If the reference code provided
contains only 4 or 6 characters, contact your next level of support for assistance.
2. When the SRC table appears, select the appropriate URC from the first column of the table. The tables
list URCs in hexadecimal sequence, with numeric characters listed before alphabetic characters.

532 System i® and System p®: Reference codes

Using system reference codes

3. Perform the action indicated for the URC in the Description/Action column of the table.
4. If the table entry does not indicate an action or if performing the action does not correct the problem,
exchange the failing items or parts listed in the Failing Item column in the order that they are listed.
Use the following instructions to exchange failing items:

Note: Some failing items are required to be exchanged in groups until the problem is solved. Other
failing items are flagged as mandatory exchange and must be exchanged before the service
action is complete, even if the problem appears to have been repaired. For more information,
see “Block replacement of FRUs.”
v Exchange the failing item listed first.
v If exchanging the first failing item does not correct the problem, reinstall the original item and
exchange the next failing item listed.
v Continue to exchange and reinstall the failing items, one at a time, until the problem is corrected. If
exchanging the failing items does not correct the problem, ask your next level of support for
assistance.

For more information, refer to the List of system reference codes.

Block replacement of FRUs

Sometimes, multiple FRUs or procedures are called out for replacement by an SRC listed in the service
action log (SAL). Each FRU or procedure has a priority, and procedures are always in priority order, from
highest to lowest priority. Do the following:
1. Replace all high priority or mandatory FRU or procedure callouts at the same time (as a block).
2. If the problem persists after replacing or performing the high priority callouts, then replace or
perform the medium priority FRU or procedure callouts one at a time unless a medium grouping
priority is associated with the callout. A medium grouping priority, shown with an A, B, or C, means
that you need to replace all the FRUs or procedures in that group at the same time (as a block).
3. Finally, if the problem still persists after replacing or performing all the medium priority callouts, then
replace or perform the low priority FRU or procedure callouts one at a time.

The priorities of the FRU and procedure callouts are shown in the following ways, depending on how
you view the SAL.SRC:
v Advanced System Management Interface (ASMI): The ASMI shows a priority with each callout in the
log.
v Control panel: The control panel shows one of the following priorities with each callout:
– H = High
– M = Medium
– MA = Medium group A
– MB = Medium group B
– MC = Medium group C
– L = Low
v Hardware Management Console (HMC): In the Service Focal Point on the HMC, the view of the
problem data for a serviceable event displays the FRU replacement priority as High, Medium, and so
on.
v Service Action Log: In the SAL, the Part Action for the FRU in the view of the event shows the
replacement priority. For more information about how to interpret the part action code, see Using the
Service Action Log or use the help function for the SAL view.

List of service request numbers

The service request number (SRN) list is in numeric order.
Reference codes 533
List of service request numbers

For information about using this list of SRNs and about SRNs in general, see “Using service request
numbers” on page 786.

If you do not find the reference code that you are looking for in this list, ask your next level of support
for assistance.
v “Five-Digit SRNs 10104 through SSA03”
v “SRNs 101-000 through 59D-xxx” on page 543
v “SRNs 60B-xxx through 69D-203” on page 556
v “SRNs 700-xxx through 7C1-117” on page 584
v “SRNs 801-xxxx through 899-xxx” on page 608
v “SRNs 900-001 through xxxxxxxx” on page 627
v “SRNs A00-FF0 through A25-001” on page 673
v “SRNs 2502-101 through 25D0-108” on page 687
v “SRNs 2600-101 through 2D07-xxxx” on page 759
v “SCSD Devices SRNs (ssss-102 to ssss-640)” on page 784

Five-Digit SRNs 10104 through SSA03

Replace FRU parts in the order by which the ″Failing Function Codes″ are listed.

Abbreviation in Table Definition

PAA
P Adapter port number
AA SSA Address

Service Failing
Request SRN Function
Number Src. Codes Description and Action
10104 Format in progress.
Action: Refer to the SRN table in the Service Guide for the unit
containing the disk drive.
10112 Format Degraded. A format operation ended before it completed.
Action: Refer to the SRN table in the Service Guide for the unit
containing the disk drive.
1xxxx Disk drive module error.
Action: Refer to the SRN table in the Service Guide for the unit
containing the disk drive.

Replace FRU parts in the order by which the ″Failing Function Codes″ are listed.

Note: Some SRNs in this chapter may have 4 rather than 3 digits after the dash (-).

Service Failing
Request Function
Number Codes Description and Action
101-000 The system hung while attempting to configure a device.
Action: Use PFW1540: Problem isolation procedures.
101-185 A checkstop occurred.
Action: Use PFW1540: Problem isolation procedures.
101-517 The system unit failed to IPL.
Action: Use PFW1540: Problem isolation procedures.
101-518 CD-ROM read problems after boot.
Note: The boot record was read from the CD-ROM disk. However, errors
occurred when trying to mount the CD-ROM file system. This problem can
be caused by SCSI device addressing, SCSI terminator, open PTC, SCSI
cable, etc.
Action: Go to SCSI Bus Problems.
101-521 The configuration manager detected an error.
to Action: If you are running the diagnostics from a disk, try running
101-538 standalone diagnostics. If standalone diagnostics run correctly, the problem
may be damaged data on the disk. Contact your software support facility.
If a different problem occurs when you run standalone diagnostics, correct
that problem. If you were running standalone at first, have the same
problem running standalone diagnostics that you had when running
diagnostics from disk, or these actions did not resolve the problem, go
PFW1540: Problem isolation procedures.
101-544 Disk read problems occurred after booting.
Note: The boot record was read from the disk. However, errors occurred
when trying to open the disk drive. This problem can be caused by SCSI
device addressing, SCSI terminator, open PTC, SCSI cable, etc.
Action: Go to SCSI Bus Problems.

Reference codes 543

101-000 through 59D-xxx

Service Failing
Request Function
Number Codes Description and Action
101-551 The system hung while loading the software. This can be caused by a
to hardware or software problem.
101-557 Action: Run the standalone diagnostics. If the standalone diagnostics run
correctly, the problem may be a damaged disk data. Consider having the
customer contact Software Support before reinstalling the operating system
on the disk. Otherwise, go to Problem determination procedure. If a
different problem occurs when you run the standalone diagnostics, correct
that problem. If the standalone diagnostics still produces the same SRN, go
to PFW1540: Problem isolation procedures.
101-558 There is not enough memory to execute diagnostics.
Action: There must be a minimum of 16 MB of installed memory. If the
system has 16 MB or more of memory installed, suspect a problem with a
memory card.
101-559 The system halted while software was loading. This problem may be
to attributed to either hardware or software.
101-599 Action: Use the standalone diagnostics if not yet used. If the same SRN is
generated from standalone diagnostics,
go to PFW1540: Problem isolation procedures for problem isolation. If a
different problem occurs when you run the standalone diagnostics, correct
that problem.

101-000 through 59D-xxx

Service Failing
Request Function
Number Codes Description and Action
45d-230 45d The Request Sense command failed.
Action: Use MAP 0210: General problem resolution.
45d-240 45d The Openx command failed.
Action: Use MAP 0210: General problem resolution.
45d-300 45d The device configuration failed.
software Action: Use MAP 0210: General problem resolution.
45d-310 B88 SCSI adapter configuration failed.
45d Action: Use MAP 0210: General problem resolution.
software
45d-320 45d Error log analysis indicates a failure.
media Action: Use MAP 0210: General problem resolution.
45d-411 45d A reservation conflict occurred.
to B88 Action: Use MAP 0210: General problem resolution.
45d-423 software
45d-511 45d The drive returned bad or non-extended sense data.
to B88 Action: Use MAP 0210: General problem resolution.
45d-523
45d-611 45d An adapter or bus I/O error occurred.
to B88 Action: Use MAP 0210: General problem resolution.
45d-623 software
45d-711 45d A device timeout error occurred.
to B88 Action: Use MAP 0210: General problem resolution.
45d-723 software
541-xxx 541 A DLT tape device problem has occurred.
Action: Refer to the DLT tape device documentation.
542-xxx 542 An 8mm 60GB tape device problem has occurred.
Action: Refer to the 8mm 60GB tape device documentation.
56B-xxx See SCSI Devices SRN (ssss-102 through ssss-640).
56D-xxx See SCSI Devices SRN (ssss-102 through ssss-640).
57B-xxx See SCSI Devices SRN (ssss-102 through ssss-640).
57D-xxx See SCSI Devices SRN (ssss-102 through ssss-640).
58B-xxx See SCSI Devices SRN (ssss-102 through ssss-640).
58D-xxx See SCSI Devices SRN (ssss-102 through ssss-640).
59B-xxx See SCSI Devices SRN (ssss-102 through ssss-640).
59D-xxx See SCSI Devices SRN (ssss-102 through ssss-640).

SRNs 60B-xxx through 69D-203

Replace FRU parts in the order by which the ″Failing Function Codes″ are listed.

700-xxx through 802-67E

Service Failing
Request Function
Number Codes Description and Action
791-xxx See SCSI devices SRNs (ssss-102 to ssss-640.
to
793-xxx
799-101 2C3 External wrap test failed on port 0.
799 Action: Use MAP 0210: General problem resolution
799-102 2C3 External wrap test failed on port 1.
799 Action: Use MAP 0210: General problem resolution
799-201 799 Internal adapter test failed.
227 Action: Use MAP 0210: General problem resolution.
799-202 799 External wrap test failed on port 0.
227 Action: Use MAP 0210: General problem resolution.
799-203 799 External wrap test failed on port 1.
227 Action: Use MAP 0210: General problem resolution.
799-204 2C3 External wrap test failed on port 0.
799 Action: Use MAP 0210: General problem resolution.
799-205 2C3 External wrap test failed on port 1.
799 Action: Use MAP 0210: General problem resolution.
799-206 2C3 External wrap test failed on port 0.
799 Action: Use MAP 0210: General problem resolution.
software
799-207 2C3 External wrap test failed on port 1.
799 Action: Use MAP 0210: General problem resolution.
software
799-301 799 Internal adapter test failed.
227 Action: Use MAP 0210: General problem resolution.
software
799-302 799 External wrap test failed on port 0.
227 Action: Use MAP 0210: General problem resolution.
software
799-303 799 External wrap test failed on port 1.
227 Action: Use MAP 0210: General problem resolution.
software
799-304 2C3 External wrap test failed on port 0.
799 Action: Use MAP 0210: General problem resolution.
software
799-305 2C3 External wrap test failed on port 1.
799 Action: Use MAP 0210: General problem resolution.
software
799-700 799 Error log analysis indicates a hardware problem.
software Action: Use MAP 0210: General problem resolution.

900-001 through xxxxxxxx

Service Failing
Request Function
Number Codes Description and Action
950-793 793 Device does not respond.
B88 Action: Use MAP 0291: Missing device or bus problem
190 resolution.
152
950-804 807 The device is not responding.
B88 Action: Use MAP 0291: Missing device or bus problem
190 resolution.
152
950-807 804 The device is not responding.
B88 Action: Use MAP 0291: Missing device or bus problem
190 resolution.
152
950-912 912 Device does not respond.
B88 Action: Use MAP 0291: Missing device or bus problem
190 resolution.
152
950-914 914 Device does not respond.
B88 Action: Use MAP 0291: Missing device or bus problem
190 resolution.
152
950-915 915 Device does not respond.
B88 Action: Use MAP 0291: Missing device or bus problem
190 resolution.
152
950-917 917 Device does not respond.
B88 Action: Use MAP 0291: Missing device or bus problem
190 resolution.
152
950-918 918 Device does not respond.
B88 Action: Use MAP 0291: Missing device or bus problem
190 resolution.
152
950-935 935 Device does not respond.
B88 Action: Use MAP 0291: Missing device or bus problem
190 resolution.
152
950-951 951 Device does not respond.
B88 Action: Use MAP 0291: Missing device or bus problem
190 resolution.
152
950-952 952 Device does not respond.
B88 Action: Use MAP 0291: Missing device or bus problem
190 resolution.
152
950-953 953 Device does not respond.
B88 Action: Use MAP 0291: Missing device or bus problem
190 resolution.
152

650 System i® and System p®: Reference codes

900-001 through xxxxxxxx

Service Failing
Request Function
Number Codes Description and Action
950-954 954 Device does not respond.
B88 Action: Use MAP 0291: Missing device or bus problem
190 resolution.
152
950-955 955 Device does not respond.
B88 Action: Use MAP 0291: Missing device or bus problem
190 resolution.
141
152
950-956 956 Device does not respond.
B88 Action: Use MAP 0291: Missing device or bus problem
190 resolution.
152
950-959 959 Device does not respond.
B88 Action: Use MAP 0291: Missing device or bus problem
190 resolution.
152
950-960 960 Device does not respond.
B88 Action: Use MAP 0291: Missing device or bus problem
190 resolution.
152
950-964 964 The SCSI Tape Drive is not responding.
B88 Action: Use MAP 0291: Missing device or bus problem
190 resolution.
152
950-968 968 Device does not respond.
B88 Action: Use MAP 0291: Missing device or bus problem
190 resolution.
152
950-970 970 Device does not respond.
B88 Action: Use MAP 0291: Missing device or bus problem
190 resolution.
152
950-971 971 Device does not respond.
B88 Action: Use MAP 0291: Missing device or bus problem
190 resolution.
152
950-972 972 Device does not respond.
B88 Action: Use MAP 0291: Missing device or bus problem
190 resolution.
152
950-974 974 Device does not respond.
B88 Action: Use MAP 0291: Missing device or bus problem
190 resolution.
152
950-981 981 Device does not respond.
B88 Action: Use MAP 0291: Missing device or bus problem
190 resolution.
152

Reference codes 651

900-001 through xxxxxxxx

900-001 through xxxxxxxx

Service Failing
Request Function
Number Codes Description and Action
998-185 998 The Unload command failed.
media Action: Use MAP 0210: General problem resolution
998-190 998 The Mode Select command failed.
Action: Use MAP 0210: General problem resolution
998-200 998 The Test Unit Ready command failed.
media Action: Use MAP 0210: General problem resolution
998-210 998 The device configuration failed.
B88 Action: Use MAP 0210: General problem resolution
998-220 998 The Release command failed.
Action: Use MAP 0210: General problem resolution
998-230 998 The Request Sense command failed.
Action: Use MAP 0210: General problem resolution
998-240 995 The Openx command failed.
Action: Use MAP 0210: General problem resolution
998-300 995 The device configuration failed.
software Action: Use MAP 0210: General problem resolution
998-310 B88 SCSI adapter configuration failed.
995 Action: Use MAP 0210: General problem resolution
software
998-320 995 Error log analysis indicates a failure.
media Action: Use MAP 0210: General problem resolution
998-411 998 A reservation conflict occurred.
to B88 Action: Use MAP 0210: General problem resolution
998-423 software
998-511 998 The drive returned bad or non-extended sense data.
to B88 Action: Use MAP 0210: General problem resolution
998-523
998-611 998 An adapter or bus I/O error occurred.
to B88 Action: Use MAP 0210: General problem resolution
998-623 software
998-711 998 A device timeout error occurred.
to B88 Action: Use MAP 0210: General problem resolution
998-723 software
999-xxx series 999 A 7137 or 3514 disk array subsystem problem is indicated.
Action: Use 7137 or 3514 documentation.
9CC-1xx I/O Error on PCI bus.
Action: Refer to the Bus SRN to FRU Reference Table in the
system unit’s service guide.
Note: xx represents the last 2 digits of the SRN.
9CC-xxx xxx I/O Bus Data, Address Parity Error, or Time-out error.
2C9 Note: xxx represents the last 3 digits of the SRN.
Action: Use MAP 0210: General problem resolution
xxxxxx none You have a six-digit error code (like an SRN) containing no
dash (-) between the third and fourth digits.
Action: Use the ″Error Code to FRU Index″ in the service guide.
xxxxxxxx none High level platform error.
Action: Refer to the system service information.

672 System i® and System p®: Reference codes

900-001 through xxxxxxxx

SRNs A00-FF0 through A25-001

Note: Some SRNs in this chapter may have 4 rather than 3 digits after the dash (-).

Use the physical location codes and FRU numbers listed on the diagnostics Problem Report Screen.
Failing Function Codes (FFCs) are not used in this group of SRNs. For more detailed information refer to
MAP 0230: Platform error problem resolution.

Service Failing
Request Function
Number Code Description and Action
A00-FF0 Description: Error log analysis is unable to determine the error. The error
log indicates the following physical FRU locations as the probable causes.
Action: Use MAP 0230: Platform error problem resolution.
A01-00x Description: Error log analysis indicates an error detected by the CPU, but
the failure could not be isolated.
Action: Use MAP 0230: Platform error problem resolution.
A01-01x Description: CPU internal error.
Action: Use MAP 0230: Platform error problem resolution.
A01-02x Description: CPU internal cache or cache controller error.
Action: Use MAP 0230: Platform error problem resolution.
A01-03x Description: External cache parity or multi-bit ECC error.
Action: Use MAP 0230: Platform error problem resolution.
A01-04x Description: External cache ECC single-bit error.
Action: Use MAP 0230: Platform error problem resolution.
A01-05x Description: System bus time-out error.
Action: Use MAP 0230: Platform error problem resolution.
A01-06x Description: Time-out error waiting for I/O.
Action: Use MAP 0230: Platform error problem resolution.
A01-07x Description: System bus parity error. Action:
Action: Use MAP 0230: Platform error problem resolution.
A01-08x Description: System bus protocol/transfer error.
Action: Use MAP 0230: Platform error problem resolution.
A02-00x Description: Error log analysis indicates an error detected by the memory
controller, but the failure could not be isolated.
Action: Use MAP 0230: Platform error problem resolution.
A02-01x Description: Uncorrectable Memory Error.
Action: Use MAP 0230: Platform error problem resolution.
A02-02x Description: ECC correctable error.
Action: Use MAP 0230: Platform error problem resolution.
A02-03x Description: Correctable error threshold exceeded.
Action: Use MAP 0230: Platform error problem resolution.
A02-04x Description: Memory Control subsystem internal error.
Action: Use MAP 0230: Platform error problem resolution.

Reference codes 673

900-001 through xxxxxxxx

Service Failing
Request Function
Number Code Description and Action
A02-05x Description: Memory Address Error (invalid address or access attempt).
Action: Use MAP 0230: Platform error problem resolution.
A02-06x Description: Memory Data error (Bad data going to memory).
Action: Use MAP 0230: Platform error problem resolution.
A02-07x Description: Memory bus/switch internal error.
Action: Use MAP 0230: Platform error problem resolution.
A02-08x Description: Memory time-out error.
Action: Use MAP 0230: Platform error problem resolution.
A02-09x Description: System bus parity error.
Action: Use MAP 0230: Platform error problem resolution.
A02-10x Description: System bus time-out error.
Action: Use MAP 0230: Platform error problem resolution.
A02-11x Description: System bus protocol/transfer error.
Action: Use MAP 0230: Platform error problem resolution.
A02-12x Description: I/O Host Bridge time-out error.
Action: Use MAP 0230: Platform error problem resolution.
A02-13x Description: I/O Host Bridge address/data parity error.
Action: Use MAP 0230: Platform error problem resolution.
A02-15x Description: System support function error.
Action: Use MAP 0230: Platform error problem resolution.
A02-16x Description: System bus internal hardware/switch error.
Action: Use MAP 0230: Platform error problem resolution.
A03-00x Description: Error log analysis indicates an error detected by the I/O
device, but the failure could not be isolated.
Action: Use MAP 0230: Platform error problem resolution.
A03-01x Description: I/O Bus Address parity error.
Action: Use MAP 0230: Platform error problem resolution.
A03-02x Description: I/O Bus Data parity error.
Action: Use MAP 0230: Platform error problem resolution.
A03-03x Description: I/O bridge/device time-out, access or other error.
Action: Use MAP 0230: Platform error problem resolution.
A03-04x Description: I/O bridge/device internal error.
Action: Use MAP 0230: Platform error problem resolution.
A03-05x Description: I/O Error on non-PCI bus.
Action: Use MAP 0230: Platform error problem resolution.
A03-06x Description: Mezzanine bus address parity error.
Action: Use MAP 0230: Platform error problem resolution.
A03-07x Description: System bus address parity error.
Action: Use MAP 0230: Platform error problem resolution.
A03-08x Description: Mezzanine bus data parity error.
Action: Use MAP 0230: Platform error problem resolution.
A03-09x Description: System bus data parity error.
Action: Use MAP 0230: Platform error problem resolution.
A03-10x Description: Mezzanine bus time-out, transfer or protocol error.
Action: Use MAP 0230: Platform error problem resolution.
A03-11x Description: System bus time-out error.
Action: Use MAP 0230: Platform error problem resolution.

674 System i® and System p®: Reference codes

900-001 through xxxxxxxx

Service Failing
Request Function
Number Code Description and Action
A03-12x Description: Error on System bus.
Action: Use MAP 0230: Platform error problem resolution.
A03-13x Description: I/O Expansion bus parity error.
Action: Use MAP 0230: Platform error problem resolution.
A03-14x Description: I/O Expansion bus time-out error.
Action: Use MAP 0230: Platform error problem resolution.
A03-15x Description: I/O Expansion bus connection failure.
Action: Use MAP 0230: Platform error problem resolution.
A03-16x Description: I/O Expansion unit not in an operating state.
Action: Use MAP 0230: Platform error problem resolution.
A05-00x Description: Error log analysis indicates an environmental and power
warning, but the failure could not be isolated.
Action: Use MAP 0230: Platform error problem resolution.
A05-01x Description: Sensor indicates a fan has failed.
Action: Use MAP 0230: Platform error problem resolution.
A05-02x Description: System shutdown due to a fan failure.
Action: Use MAP 0230: Platform error problem resolution.
A05-03x Description: Sensor indicates a voltage outside normal range.
Action: Use Power problem isolation for your system.
A05-04x Description: System shutdown due to voltage outside normal range.
Action: Use Power problem isolation for your system.
A05-05x Description: Sensor indicates an abnormally high internal temperature.
Action: Verify that:
1. The room ambient temperature is within the system operating
environment.
2. There is unrestricted air flow around the system.
3. All system covers are closed.
4. There are no fan failures.

900-001 through xxxxxxxx

2502-101 through 25D0-108

Service Failing
Request Function
Number Codes Description and Action
2502-710 2502 Permanent controller failure.
Action: Use MAP 0210: General problem resolution.
2502-713 2502 Controller failure.
Action: Use MAP 0210: General problem resolution.
2502-720 Controller device bus configuration error.
Action: Use to MAP 0050: SCSI Bus Problems.
2503-101 2503 Adapter configuration error.
Action: Use MAP 0210: General problem resolution.
2503-710 2503 Permanent controller failure.
Action: Use MAP 0210: General problem resolution.
2503-713 2503 Controller failure.
Action: Use MAP 0210: General problem resolution.
2503-720 Controller device bus configuration error.
Action: Use to MAP 0050: SCSI Bus Problems.
2512-101 2512 Adapter configuration error.
Action: Use MAP 0210: General problem resolution.
2512-710 2512 Permanent adapter failure.
Action: Use MAP 0210: General problem resolution.
2512-711 2512 Adapter failure.
Action: Go to MAP 0210: General problem resolution
2512-712 2512 Adapter device bus configuration error.
Action: PCI-X Dual Channel Ultra320 SCSI Adapter. Use MAP
0050: SCSI Bus Problems.
PCI-X Ultra320 SCSI RAID: Use MAP 3050 in the PCI-X SCSI
RAID Controller Reference Guide for AIX.
2512-713 2512 Adapter failure.
Action: Use MAP 0210: General problem resolution.
2512-714 2512 Temporary adapter failure.
Action: Use MAP 0210: General problem resolution.
2512-715 2512 Temporary adapter failure.
Action: Use MAP 0210: General problem resolution.
2512-716 2512 PCI bus error detected by EEH.
293 Action: Use MAP 0210: General problem resolution.
2512-717 2512 PCI bus error detected by adapter.
293 Action: Use MAP 0210: General problem resolution.
2512-718 2512 Temporary PCI bus error detected by adapter
293 Action: Use MAP 0210: General problem resolution.
2512-719 Device bus termination power lost or not detected
Action: PCI-X Dual Channel Ultra320 SCSI Adapter. Use MAP
0050: SCSI Bus Problems.
PCI-X Ultra320 SCSI RAID: Use MAP 3050 in the PCI-X SCSI
RAID Controller Reference Guide for AIX.
2512-720 Adapter device bus configuration error.
Action: For a PCI-X Dual Channel Ultra320 SCSI adapter, Use to
MAP 0050: SCSI Bus Problems.

For a PCI-X Ultra320 SCSI RAID adapter, use MAP 3050 in the
PCI-X SCSI RAID Controller Reference Guide for AIX.

688 System i® and System p®: Reference codes

2502-101 through 25D0-108

Service Failing
Request Function
Number Codes Description and Action
2512-721 Temporary adapter detected device bus failure.
Action: For a PCI-X Dual Channel Ultra320 SCSI adapter, Use to
MAP 0050: SCSI Bus Problems.

For a PCI-X Ultra320 SCSI RAID adapter, use MAP 3050 in the
PCI-X SCSI RAID Controller Reference Guide for AIX.
2512-722 2512 Device bus interface problem.
Action: Use MAP 0210: General problem resolution.
2512-723 Device bus interface problem.
Action: Use MAP 0054: PCI-X SCSI Bus Problems
2512-724 2512 Temporary device bus interface problem.
Action: Use MAP 0210: General problem resolution.
2512-725 Temporary device bus interface problem.
Action: Use MAP 0054: PCI-X SCSI Bus Problems
2512-102E 722 Out of alternate disk storage for storage.
Action: Use MAP 0210: General problem resolution. If the
problem persists, use MAP 3051 in the PCI-X SCSI RAID
Controller Reference Guide for AIX.
2512-3002 722 Addressed device failed to respond to selection.
Action: Use MAP 0210: General problem resolution. If the
problem persists, use MAP 3051 in the PCI-X SCSI RAID
Controller Reference Guide for AIX.
2512-3010 722 Disk returned wrong response to adapter.
Action: Use MAP 0210: General problem resolution. If the
problem persists, use MAP 3051 in the PCI-X SCSI RAID
Controller Reference Guide for AIX.
2512-3020 Storage subsystem configuration error.
Action: Use MAP 3050 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-3100 Adapter detected device bus interface error.
Action: Use MAP 3050 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-3101 Adapter detected device bus interface error.
Action: Use MAP 3050 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-3109 Adapter timed out a disk command.
Action: Use MAP 3050 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-3110 Disk bus interface error.
Action: Use MAP 3050 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-7001 722 Temporary disk data error. Action: Use MAP 0210: General
Problem Resolution If the problem persists, use MAP 3051 in the
PCI-X SCSI RAID Controller Reference Guide for AIX.
2512-8008 2526 Permanent cache battery pack failure.
293 Action: Use MAP 3000 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-8009 2526 Impending cache battery pack failure.
293 Action: Use MAP 3000 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.

Reference codes 689

2502-101 through 25D0-108

Service Failing
Request Function
Number Codes Description and Action
2512-9000 Controller detected a device error during configuration discovery.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9001 Controller detected a device error during configuration discovery.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9002 Controller detected a device error during configuration discovery.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9008 Controller does not support function expected for one or more
disks.
Action: Use MAP 3030 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9010 Cache data associated with attached disks cannot be found.
Action: Use MAP 3020 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9011 Cache data belongs to disks other than those attached.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9020 Two or more disks are missing from a RAID-5 disk array.
Action: Use MAP 3011 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9021 Two or more disks are missing from a RAID-5 disk array.
Action: Use MAP 3011 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9022 Two or more disks are missing from a RAID-5 disk array.
Action: Use MAP 3011 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9023 One or more disk array members are not a the required physical
locations.
Action: Use MAP 3012 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9024 The physical location of disk array members conflict with
another disk array.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9025 An incompatible disk is installed at a degraded disk location in
the disk array.
Action: Use MAP 3010 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9026 A previously degraded disk in the disk array was not found at
the required physical location.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9027 A disk array is or would become degraded and the parity data is
out of synchronization.
Action: Use MAP 3013 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.

690 System i® and System p®: Reference codes

2502-101 through 25D0-108

Service Failing
Request Function
Number Codes Description and Action
2512-9028 The maximum number of functional disk arrays has been
exceeded.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9029 The maximum number of functional disk arrays has been
exceeded.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9030 The disk array is degraded due to a missing or failed disk.
Action: Use MAP 3010 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9031 Automatic reconstruction initiated for the disk array.
Action: Use MAP 3010 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9041 Background disk array parity checking detected and corrected
errors.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9050 Required cache data cannot be located for one or more disks.
Action: Use MAP 3031 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9051 Cache data exists for more than one missing or failed disks.
Action: Use MAP 3032 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9052 Cache data exists for one or more modified disks.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9054 RAID controller resources are not available due to previous
problems.
Action: Use MAP 3021 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9060 One or more disk pairs are missing from a RAID-10 disk array.
Action: Use MAP 3011 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9061 One or more disk pairs are missing from a RAID-10 disk array.
Action: Use MAP 3011 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9062 One or more disk pairs are missing from a RAID-0 disk array.
Action: Use MAP 3011 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9063 The maximum number of functional disk arrays has been
exceeded.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9073 Multiple controllers connected in an invalid configuration.
Action: Use MAP 3040 in the PCI-X SCSI RAID Controller
Reference Guide for AIX
2512-9074 Multiple controllers connected in an invalid configuration.
Action: Use MAP 3041 in the PCI-X SCSI RAID Controller
Reference Guide for AIX

Reference codes 691

2502-101 through 25D0-108

Service Failing
Request Function
Number Codes Description and Action
2512-9081 Controller detected a device error during an internal media
recovery.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9082 Controller detected a device error during an internal media
recovery.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9090 Disk has been modified after last known status.
Action: Use MAP 3033 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9091 Incorrect disk configuration change has been detected.
Action: Use MAP 3033 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9092 Disk requires formatting before use.
Action: Use MAP 3034 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9200 Identify disk to be replaced.
Action: Use MAP 3036 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2512-9032 Disk Array is degraded due to missing failed disk.
Action: Use MAP 3010 in the PCI-X SCSI RAID Controller
Reference Guide for AIX
2512-9042 Background Disk Array parity checking detected and corrected
errors on specified disk.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX
2512-FFF3 Disk media format bad.
Action: Use MAP 0210: General problem resolution. If the
problem persists, use MAP 3035 in the PCI-X SCSI RAID
Controller Reference Guide for AIX.
2512-FFF4 722 Disk drive problem.
Action: Use MAP 0210: General problem resolution. If the
problem persists, use MAP 3051 in the PCI-X SCSI RAID
Controller Reference Guide for AIX.
2512-FFF6 722 Disk detected recoverable error.
Action: Use MAP 0210: General problem resolution. If the
problem persists, use MAP 3051 in the PCI-X SCSI RAID
Controller Reference Guide for AIX.
2512-FFFA 722 Temporary disk bus error.
Action: Use MAP 0210: General problem resolution. If the
problem persists, use MAP 3051 in the PCI-X SCSI RAID
Controller Reference Guide for AIX.
2512-FFFE Temporary disk bus error.
Action: Use MAP 3050 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2513-101 2513 Adapter configuration error.
Action: Use MAP 0210: General problem resolution.
2513-710 2513 Permanent adapter failure.
Action: Use MAP 0210: General problem resolution.

692 System i® and System p®: Reference codes

2502-101 through 25D0-108

Service Failing
Request Function
Number Codes Description and Action
2513-711 2513 Adapter failure.
Action: Go to MAP 0210: General problem resolution
2513-712 2513 Adapter device bus configuration error.
Action: PCI-X Dual Channel Ultra320 SCSI Adapter. Use MAP
0050: SCSI Bus Problems.
PCI-X Ultra320 SCSI RAID: Use MAP 3050 in the PCI-X SCSI
RAID Controller Reference Guide for AIX.
2513-713 2513 Adapter failure.
Action: Use MAP 0210: General problem resolution.
2513-714 2513 Temporary adapter failure.
Action: Use MAP 0210: General problem resolution.
2513-715 2513 Temporary adapter failure.
Action: Use MAP 0210: General problem resolution.
2513-716 2513 PCI bus error detected by EEH.
293 Action: Use MAP 0210: General problem resolution.
2513-717 2513 PCI bus error detected by adapter.
293 Action: Use MAP 0210: General problem resolution.
2513-718 2513 Temporary PCI bus error detected by adapter
293 Action: Use MAP 0210: General problem resolution.
2513-719 Device bus termination power lost or not detected
Action: PCI-X Dual Channel Ultra320 SCSI Adapter. Use MAP
0050: SCSI Bus Problems.
PCI-X Ultra320 SCSI RAID: Use MAP 3050 in the PCI-X SCSI
RAID Controller Reference Guide for AIX.
2513-720 Adapter device bus configuration error.
Action: For a PCI-X Dual Channel Ultra320 SCSI adapter, Use to
MAP 0050: SCSI Bus Problems.

Service Failing
Request Function
Number Codes Description and Action
2521-803 Error Log Analysis indicates that multiple SCSI bus errors have
occurred.
Action: Run diagnostic on the adapter and the devices in System
Verification Mode. If an SRN is reported, use the SRN to resolve
the problem. If a SRN is not reported, use the SCSI service hints
to resolve the problem.
2522-101 2522 Adapter configuration error.
Action: Use MAP 0210: General problem resolution.
2522-710 2522 Permanent adapter failure.
Action: Use MAP 0210: General problem resolution.
2522-711 2522 Adapter failure.
Action: Go to MAP 0210: General problem resolution
2522-712 2522 Adapter device bus configuration error.
Action: PCI-X Dual Channel Ultra320 SCSI Adapter. Use MAP
0050: SCSI Bus Problems.
PCI-X Ultra320 SCSI RAID: Use MAP 3050 in the PCI-X SCSI
RAID Controller Reference Guide for AIX.
2522-713 2522 Adapter failure.
Action: Use MAP 0210: General problem resolution.
2522-714 2522 Temporary adapter failure.
Action: Use MAP 0210: General problem resolution.
2522-715 2522 Temporary adapter failure.
Action: Use MAP 0210: General problem resolution.
2522-716 2522 PCI bus error detected by EEH.
293 Action: Use MAP 0210: General problem resolution.
2522-717 2522 PCI bus error detected by adapter.
293 Action: Use MAP 0210: General problem resolution.
2522-718 2522 Temporary PCI bus error detected by adapter
293 Action: Use MAP 0210: General problem resolution.
2522-719 Device bus termination power lost or not detected
Action: PCI-X Dual Channel Ultra320 SCSI Adapter. Use MAP
0050: SCSI Bus Problems.
PCI-X Ultra320 SCSI RAID: Use MAP 3050 in the PCI-X SCSI
RAID Controller Reference Guide for AIX.
2522-720 Adapter device bus configuration error.
Action: For a PCI-X Dual Channel Ultra320 SCSI adapter, Use to
MAP 0050: SCSI Bus Problems.

714 System i® and System p®: Reference codes

2502-101 through 25D0-108

Service Failing
Request Function
Number Codes Description and Action
2527-3100 2527 Adapter detected device bus interface error.
Action: Use MAP 3050 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2527-3101 2527 Adapter detected device bus interface error.
Action: Use MAP 3050 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2527-3109 2527 Adapter timed out a disk command.
Action: Use MAP 3050 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2527-3110 2527 Disk bus interface error.
Action: Use MAP 3050 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2527-7001 722 Description: Temporary disk data error.
Action: Use MAP 0210: General problem resolution. If the
problem persists, use MAP 3051 in the PCI-X SCSI RAID
Controller Reference Guide for AIX.
2527-8008 2526 Permanent Cache Battery Pack failure.
293 Action: Use MAP 3000 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2527-8009 2526 Impending Cache Battery Pack failure.
293 Action: Use MAP 3000 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2527-9000 Controller detected device error during configuration discovery.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2527-9001 Controller detected device error during configuration discovery.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2527-9002 Controller detected device error during configuration discovery.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2527-9008 Controller does not support function expected for one or more
disks.
Action: Use MAP 3030 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2527-9010 Cache data associated with attached disks cannot be found.
Action: Use MAP 3020 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2527-9011 Cache data belongs to disks other than those attached.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2527-9020 Description: Two or more disks are missing from a RAID-5 Disk
Array.
Action: Use MAP 3011 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2527-9021 Two or more disks are missing from a RAID-5 Disk Array.
Action: Use MAP 3011 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.

Reference codes 715

2502-101 through 25D0-108

Service Failing
Request Function
Number Codes Description and Action
2527-9022 Two or more disks are missing from a RAID-5 Disk Array.
Action: Use MAP 3011 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2527-9023 Description: One or more Disk Array members are not at
required physical locations.
Action: Use MAP 3012 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2527-9024 Physical location of Disk Array members conflict with another
Disk Array.
Action: Use map 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2527-9025 Incompatible disk installed at degraded disk location in Disk
Array.
Action: Use MAP 3010 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2527-9026 Previously degraded disk in Disk Array not found at required
physical location.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2527-9027 Description: Disk Array is or would become degraded and parity
data is out of synchronization.
Action: Use MAP 3013 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2527-9028 Maximum number of functional Disk Arrays has been exceeded.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2527-9029 Maximum number of functional Disk Array disks has been
exceeded.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2527-9030 Disk Array is degraded due to missing/failed disk.
Action: Use MAP 3010 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2527-9031 Automatic reconstruction initiated for Disk Array.
Action: Use MAP 3010 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2527-9032 Disk Array is degraded due to missing failed disk.
Action: Use MAP 3010 in the PCI-X SCSI RAID Controller
Reference Guide for AIX
2527-9041 Background Disk Array parity checking detected and corrected
errors.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2527-9042 Background Disk Array parity checking detected and corrected
errors on specified disk.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX
2527-9050 Required cache data can not be located for one or more disks.
Action: Use MAP 3031 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.

2502-101 through 25D0-108

Service Failing
Request Function
Number Codes Description and Action
2528-9000 Controller detected a device error during configuration discovery.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9001 Controller detected a device error during configuration discovery.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9002 Controller detected a device error during configuration discovery.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9008 Controller does not support function expected for one or more
disks.
Action: Use MAP 3030 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9010 Cache data associated with attached disks cannot be found.
Action: Use MAP 3020 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9011 Cache data belongs to disks other than those attached.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9020 Two or more disks are missing from a RAID-5 disk array.
Action: Use MAP 3011 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9021 Two or more disks are missing from a RAID-5 disk array.
Action: Use MAP 3011 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9022 Two or more disks are missing from a RAID-5 disk array.
Action: Use MAP 3011 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9023 One or more disk array members are not a the required physical
locations.
Action: Use MAP 3012 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9024 The physical location of disk array members conflict with
another disk array.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9025 An incompatible disk is installed at a degraded disk location in
the disk array.
Action: Use MAP 3010 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9026 A previously degraded disk in the disk array was not found at
the required physical location.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9027 A disk array is or would become degraded and the parity data is
out of synchronization.
Action: Use MAP 3013 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.

720 System i® and System p®: Reference codes

2502-101 through 25D0-108

Service Failing
Request Function
Number Codes Description and Action
2528-9028 The maximum number of functional disk arrays has been
exceeded.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9029 The maximum number of functional disk arrays has been
exceeded.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9030 The disk array is degraded due to a missing or failed disk.
Action: Use MAP 3010 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9031 Automatic reconstruction initiated for the disk array.
Action: Use MAP 3010 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9041 Background disk array parity checking detected and corrected
errors.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9050 Required cache data cannot be located for one or more disks.
Action: Use MAP 3031 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9051 Cache data exists for more than one missing or failed disks.
Action: Use MAP 3032 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9052 Cache data exists for one or more modified disks.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9054 RAID controller resources are not available due to previous
problems.
Action: Use MAP 3021 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9060 One or more disk pairs are missing from a RAID-10 disk array.
Action: Use MAP 3011 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9061 One or more disk pairs are missing from a RAID-10 disk array.
Action: Use MAP 3011 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9062 One or more disk pairs are missing from a RAID-0 disk array.
Action: Use MAP 3011 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9063 The maximum number of functional disk arrays has been
exceeded.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9073 Multiple controllers connected in an invalid configuration.
Action: Use MAP 3040 in the PCI-X SCSI RAID Controller
Reference Guide for AIX
2528-9074 Multiple controllers connected in an invalid configuration.
Action: Use MAP 3041 in the PCI-X SCSI RAID Controller
Reference Guide for AIX

Reference codes 721

2502-101 through 25D0-108

Service Failing
Request Function
Number Codes Description and Action
2528-9081 Controller detected a device error during an internal media
recovery.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9082 Controller detected a device error during an internal media
recovery.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9090 Disk has been modified after last known status.
Action: Use MAP 3033 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9091 Incorrect disk configuration change has been detected.
Action: Use MAP 3033 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9092 Disk requires formatting before use.
Action: Use MAP 3034 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9200 Identify disk to be replaced.
Action: Use MAP 3036 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2528-9032 Disk Array is degraded due to missing failed disk.
Action: Use MAP 3010 in the PCI-X SCSI RAID Controller
Reference Guide for AIX
2528-9042 Background Disk Array parity checking detected and corrected
errors on specified disk.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX
2528-FFF3 Disk media format bad.
Action: Use MAP 0210: General problem resolution. If the
problem persists, use MAP 3035 in the PCI-X SCSI RAID
Controller Reference Guide for AIX.
2528-FFF4 722 Disk drive problem.
Action: Use MAP 0210: General problem resolution. If the
problem persists, use MAP 3051 in the PCI-X SCSI RAID
Controller Reference Guide for AIX.
2528-FFF6 722 Disk detected recoverable error.
Action: Use MAP 0210: General problem resolution. If the
problem persists, use MAP 3051 in the PCI-X SCSI RAID
Controller Reference Guide for AIX.
2528-FFFA 722 Temporary disk bus error.
Action: Use MAP 0210: General problem resolution. If the
problem persists, use MAP 3051 in the PCI-X SCSI RAID
Controller Reference Guide for AIX.
2528-FFFE Temporary disk bus error.
Action: Use MAP 3050 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2529-101 2529 Adapter configuration error.
Action: Use MAP 0210: General problem resolution.
2529-710 2529 Permanent adapter failure.
Action: Use MAP 0210: General problem resolution.

722 System i® and System p®: Reference codes

2502-101 through 25D0-108

Service Failing
Request Function
Number Codes Description and Action
2529-711 2529 Adapter failure.
Action: Go to MAP 0210: General problem resolution
2529-712 2529 Adapter device bus configuration error.
Action: PCI-X Dual Channel Ultra320 SCSI Adapter. Use MAP
0050: SCSI Bus Problems.
PCI-X Ultra320 SCSI RAID: Use MAP 3050 in the PCI-X SCSI
RAID Controller Reference Guide for AIX.
2529-713 2529 Adapter failure.
Action: Use MAP 0210: General problem resolution.
2529-714 2529 Temporary adapter failure.
Action: Use MAP 0210: General problem resolution.
2529-715 2529 Temporary adapter failure.
Action: Use MAP 0210: General problem resolution.
2529-716 2529 PCI bus error detected by EEH.
293 Action: Use MAP 0210: General problem resolution.
2529-717 2529 PCI bus error detected by adapter.
293 Action: Use MAP 0210: General problem resolution.
2529-718 2529 Temporary PCI bus error detected by adapter
293 Action: Use MAP 0210: General problem resolution.
2529-719 Device bus termination power lost or not detected
Action: PCI-X Dual Channel Ultra320 SCSI Adapter. Use MAP
0050: SCSI Bus Problems.
PCI-X Ultra320 SCSI RAID: Use MAP 3050 in the PCI-X SCSI
RAID Controller Reference Guide for AIX.
2529-720 Adapter device bus configuration error.
Action: For a PCI-X Dual Channel Ultra320 SCSI adapter, Use to
MAP 0050: SCSI Bus Problems.

For a PCI-X Ultra320 SCSI RAID adapter, use MAP 3050 in the
PCI-X SCSI RAID Controller Reference Guide for AIX.
252B-722 252B Device bus interface problem.
Action: Use MAP 0210: General problem resolution.
252B-723 Device bus interface problem.
Action: Use MAP 0054: PCI-X SCSI Bus Problems
252B-724 252B Temporary device bus interface problem.
Action: Use MAP 0210: General problem resolution.
252B-725 Temporary device bus interface problem.
Action: Use MAP 0054: PCI-X SCSI Bus Problems
252B-102E 722 Out of alternate disk storage for storage.
Action: Use MAP 0210: General problem resolution. If the
problem persists, use MAP 3051 in the PCI-X SCSI RAID
Controller Reference Guide for AIX.
252B-3002 722 Addressed device failed to respond to selection.
Action: Use MAP 0210: General problem resolution. If the
problem persists, use MAP 3051 in the PCI-X SCSI RAID
Controller Reference Guide for AIX.
252B-3010 722 Disk returned wrong response to adapter.
Action: Use MAP 0210: General problem resolution. If the
problem persists, use MAP 3051 in the PCI-X SCSI RAID
Controller Reference Guide for AIX.
252B-3020 Storage subsystem configuration error.
Action: Use MAP 3050 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252B-3100 Adapter detected device bus interface error.
Action: Use MAP 3050 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252B-3101 Adapter detected device bus interface error.
Action: Use MAP 3050 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252B-3109 Adapter timed out a disk command.
Action: Use MAP 3050 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.

728 System i® and System p®: Reference codes

2502-101 through 25D0-108

Service Failing
Request Function
Number Codes Description and Action
252B-3110 Disk bus interface error.
Action: Use MAP 3050 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252B-7001 722 Temporary disk data error. Action: Use MAP 0210: General
Problem Resolution If the problem persists, use MAP 3051 in the
PCI-X SCSI RAID Controller Reference Guide for AIX.
252B-8008 2526 Permanent cache battery pack failure.
293 Action: Use MAP 3000 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252B-8009 2526 Impending cache battery pack failure.
293 Action: Use MAP 3000 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252B-9000 Controller detected a device error during configuration discovery.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252B-9001 Controller detected a device error during configuration discovery.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252B-9002 Controller detected a device error during configuration discovery.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252B-9008 Controller does not support function expected for one or more
disks.
Action: Use MAP 3030 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252B-9010 Cache data associated with attached disks cannot be found.
Action: Use MAP 3020 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252B-9011 Cache data belongs to disks other than those attached.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252B-9020 Two or more disks are missing from a RAID-5 disk array.
Action: Use MAP 3011 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252B-9021 Two or more disks are missing from a RAID-5 disk array.
Action: Use MAP 3011 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252B-9022 Two or more disks are missing from a RAID-5 disk array.
Action: Use MAP 3011 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252B-9023 One or more disk array members are not a the required physical
locations.
Action: Use MAP 3012 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252B-9024 The physical location of disk array members conflict with
another disk array.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.

Reference codes 729

2502-101 through 25D0-108

Service Failing
Request Function
Number Codes Description and Action
252B-9025 An incompatible disk is installed at a degraded disk location in
the disk array.
Action: Use MAP 3010 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252B-9026 A previously degraded disk in the disk array was not found at
the required physical location.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252B-9027 A disk array is or would become degraded and the parity data is
out of synchronization.
Action: Use MAP 3013 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252B-9028 The maximum number of functional disk arrays has been
exceeded.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252B-9029 The maximum number of functional disk arrays has been
exceeded.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252B-9030 The disk array is degraded due to a missing or failed disk.
Action: Use MAP 3010 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252B-9031 Automatic reconstruction initiated for the disk array.
Action: Use MAP 3010 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252B-9041 Background disk array parity checking detected and corrected
errors.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252B-9050 Required cache data cannot be located for one or more disks.
Action: Use MAP 3031 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252B-9051 Cache data exists for more than one missing or failed disks.
Action: Use MAP 3032 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252B-9052 Cache data exists for one or more modified disks.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252B-9054 RAID controller resources are not available due to previous
problems.
Action: Use MAP 3021 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252B-9060 One or more disk pairs are missing from a RAID-10 disk array.
Action: Use MAP 3011 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252B-9061 One or more disk pairs are missing from a RAID-10 disk array.
Action: Use MAP 3011 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.

2502-101 through 25D0-108

Service Failing
Request Function
Number Codes Description and Action
252D-9000 Controller detected a device error during configuration discovery.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9001 Controller detected a device error during configuration discovery.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9002 Controller detected a device error during configuration discovery.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9008 Controller does not support function expected for one or more
disks.
Action: Use MAP 3030 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9010 Cache data associated with attached disks cannot be found.
Action: Use MAP 3020 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9011 Cache data belongs to disks other than those attached.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9020 Two or more disks are missing from a RAID-5 disk array.
Action: Use MAP 3011 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9021 Two or more disks are missing from a RAID-5 disk array.
Action: Use MAP 3011 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9022 Two or more disks are missing from a RAID-5 disk array.
Action: Use MAP 3011 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9023 One or more disk array members are not a the required physical
locations.
Action: Use MAP 3012 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9024 The physical location of disk array members conflict with
another disk array.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9025 An incompatible disk is installed at a degraded disk location in
the disk array.
Action: Use MAP 3010 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9026 A previously degraded disk in the disk array was not found at
the required physical location.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9027 A disk array is or would become degraded and the parity data is
out of synchronization.
Action: Use MAP 3013 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.

734 System i® and System p®: Reference codes

2502-101 through 25D0-108

Service Failing
Request Function
Number Codes Description and Action
252D-9028 The maximum number of functional disk arrays has been
exceeded.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9029 The maximum number of functional disk arrays has been
exceeded.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9030 The disk array is degraded due to a missing or failed disk.
Action: Use MAP 3010 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9031 Automatic reconstruction initiated for the disk array.
Action: Use MAP 3010 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9041 Background disk array parity checking detected and corrected
errors.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9050 Required cache data cannot be located for one or more disks.
Action: Use MAP 3031 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9051 Cache data exists for more than one missing or failed disks.
Action: Use MAP 3032 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9052 Cache data exists for one or more modified disks.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9054 RAID controller resources are not available due to previous
problems.
Action: Use MAP 3021 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9060 One or more disk pairs are missing from a RAID-10 disk array.
Action: Use MAP 3011 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9061 One or more disk pairs are missing from a RAID-10 disk array.
Action: Use MAP 3011 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9062 One or more disk pairs are missing from a RAID-0 disk array.
Action: Use MAP 3011 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9063 The maximum number of functional disk arrays has been
exceeded.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9073 Multiple controllers connected in an invalid configuration.
Action: Use MAP 3040 in the PCI-X SCSI RAID Controller
Reference Guide for AIX
252D-9074 Multiple controllers connected in an invalid configuration.
Action: Use MAP 3041 in the PCI-X SCSI RAID Controller
Reference Guide for AIX

Reference codes 735

2502-101 through 25D0-108

Service Failing
Request Function
Number Codes Description and Action
252D-9081 Controller detected a device error during an internal media
recovery.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9082 Controller detected a device error during an internal media
recovery.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9090 Disk has been modified after last known status.
Action: Use MAP 3033 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9091 Incorrect disk configuration change has been detected.
Action: Use MAP 3033 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9092 Disk requires formatting before use.
Action: Use MAP 3034 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9200 Identify disk to be replaced.
Action: Use MAP 3036 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252D-9032 Disk Array is degraded due to missing failed disk.
Action: Use MAP 3010 in the PCI-X SCSI RAID Controller
Reference Guide for AIX
252D-9042 Background Disk Array parity checking detected and corrected
errors on specified disk.
Action: Use MAP 3090 in the PCI-X SCSI RAID Controller
Reference Guide for AIX
252D-FFF3 Disk media format bad.
Action: Use MAP 0210: General problem resolution. If the
problem persists, use MAP 3035 in the PCI-X SCSI RAID
Controller Reference Guide for AIX.
252D-FFF4 722 Disk drive problem.
Action: Use MAP 0210: General problem resolution. If the
problem persists, use MAP 3051 in the PCI-X SCSI RAID
Controller Reference Guide for AIX.
252D-FFF6 722 Disk detected recoverable error.
Action: Use MAP 0210: General problem resolution. If the
problem persists, use MAP 3051 in the PCI-X SCSI RAID
Controller Reference Guide for AIX.
252D-FFFA 722 Temporary disk bus error.
Action: Use MAP 0210: General problem resolution. If the
problem persists, use MAP 3051 in the PCI-X SCSI RAID
Controller Reference Guide for AIX.
252D-FFFE Temporary disk bus error.
Action: Use MAP 3050 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
252E-101 252E Adapter configuration error.
Action: Use MAP 0210: General problem resolution.
252E-710 252E Permanent adapter failure.
Action: Use MAP 0210: General problem resolution.

736 System i® and System p®: Reference codes

2502-101 through 25D0-108

Service Failing
Request Function
Number Codes Description and Action
252E-711 252E Adapter failure.
Action: Go to MAP 0210: General problem resolution
252E-712 252E Adapter device bus configuration error.
Action: PCI-X Dual Channel Ultra320 SCSI Adapter. Use MAP
0050: SCSI Bus Problems.
PCI-X Ultra320 SCSI RAID: Use MAP 3050 in the PCI-X SCSI
RAID Controller Reference Guide for AIX.
252E-713 252E Adapter failure.
Action: Use MAP 0210: General problem resolution.
252E-714 252E Temporary adapter failure.
Action: Use MAP 0210: General problem resolution.
252E-715 252E Temporary adapter failure.
Action: Use MAP 0210: General problem resolution.
252E-716 252E PCI bus error detected by EEH.
293 Action: Use MAP 0210: General problem resolution.
252E-717 252E PCI bus error detected by adapter.
293 Action: Use MAP 0210: General problem resolution.
252E-718 252E Temporary PCI bus error detected by adapter
293 Action: Use MAP 0210: General problem resolution.
252E-719 Device bus termination power lost or not detected
Action: PCI-X Dual Channel Ultra320 SCSI Adapter. Use MAP
0050: SCSI Bus Problems.
PCI-X Ultra320 SCSI RAID: Use MAP 3050 in the PCI-X SCSI
RAID Controller Reference Guide for AIX.
252E-720 Adapter device bus configuration error.
Action: For a PCI-X Dual Channel Ultra320 SCSI adapter, Use to
MAP 0050: SCSI Bus Problems.

Service Failing
Request Function
Number Codes Description and Action
2D07-714 2D07 Temporary adapter failure.
Action: Use MAP 0210: General
problem resolution.
2D07-715 2D07 Temporary adapter failure.
Action: Use MAP 0210: General
problem resolution.
2D07-716 2D07 PCI bus error detected by EEH.
293 Action: Use MAP 0210: General
problem resolution.
2D07-717 2D07 PCI bus error detected by adapter.
293 Action: Use MAP 0210: General
problem resolution.
2D07-718 2D07 Temporary PCI bus error detected by
293 adapter
Action: Use MAP 0210: General
problem resolution.
2D07-719 Device bus termination power lost or
not detected
Action: PCI-X Dual Channel Ultra320
SCSI Adapter. Use MAP 0050: SCSI
Bus Problems.
PCI-X Ultra320 SCSI RAID: Use MAP
3050 in the PCI-X SCSI RAID Controller
Reference Guide for AIX.
2D07-720 Adapter device bus configuration
error.
Action: For a PCI-X Dual Channel
Ultra320 SCSI adapter, Use to MAP
0050: SCSI Bus Problems.

For a PCI-X Ultra320 SCSI RAID

adapter, use MAP 3050 in the PCI-X
SCSI RAID Controller Reference Guide
for AIX.
2D07-721 Temporary adapter detected device
bus failure.
Action: For a PCI-X Dual Channel
Ultra320 SCSI adapter, Use to MAP
0050: SCSI Bus Problems.

2502-101 through 25D0-108

Service Failing
Request Function
Number Codes Description and Action
2D07-9042 Background Disk Array parity
checking detected and corrected errors
on specified disk.
Action: Use MAP 3090 in the PCI-X
SCSI RAID Controller Reference Guide
for AIX
2D07-FFF3 Disk media format bad.
Action: Use MAP 0210: General
problem resolution. If the problem
persists, use MAP 3035 in the PCI-X
SCSI RAID Controller Reference Guide
for AIX.
2D07-FFF4 722 Disk drive problem.
Action: Use MAP 0210: General
problem resolution. If the problem
persists, use MAP 3051 in the PCI-X
SCSI RAID Controller Reference Guide
for AIX.
2D07-FFF6 722 Disk detected recoverable error.
Action: Use MAP 0210: General
problem resolution. If the problem
persists, use MAP 3051 in the PCI-X
SCSI RAID Controller Reference Guide
for AIX.
2D07-FFFA 722 Temporary disk bus error.
Action: Use MAP 0210: General
problem resolution. If the problem
persists, use MAP 3051 in the PCI-X
SCSI RAID Controller Reference Guide
for AIX.
2D07-FFFE Temporary disk bus error.
Action: Use MAP 3050 in the PCI-X
SCSI RAID Controller Reference Guide
for AIX.

SCSD Devices SRNs (ssss-102 to ssss-640)

Use the following table to replace FRU parts in the order by which the ″Failing Function Codes″ are
listed.
Notes:
1. Some SRNs in this chapter may have 4 rather than 3 digits after the dash (-).
2. The ssss represent the 3 or 4 digit SCSD SRNs before the dash (-).

Note:

Service Failing
Request Function
Number Codes Description and Action
ssss-102 ssss An unrecoverable media error occurred.
Action: Use MAP 0210: General problem resolution.

784 System i® and System p®: Reference codes

ssss-102 through ssss-640

Service Failing
Request Function
Number Codes Description and Action
ssss-104 ssss The motor failed to restart.
Action: Use MAP 0210: General problem resolution.
ssss-105 ssss The drive did not become ready.
Action: Use MAP 0210: General problem resolution.
ssss-106 ssss The electronics card test failed.
Action: Use MAP 0210: General problem resolution.
ssss-108 ssss The bus test failed.
Action: Use MAP 0210: General problem resolution.
ssss-110 ssss The media format is corrupted.
Action: Use MAP 0210: General problem resolution.
ssss-112 ssss The diagnostic test failed.
Action: Use MAP 0210: General problem resolution.
ssss-114 ssss An unrecoverable hardware error.
Action: Use MAP 0210: General problem resolution.
ssss-116 ssss A protocol error. Action: Check the levels of the device, adapter, diagnostic
software, and application software to be sure they are all compatible. If you
do not find a problem, call your support person.
ssss-117 ssss A write-protect error occurred.
Action: Use MAP 0210: General problem resolution.
ssss-118 ssss A SCSD command time-out occurred.
B88 Action: Use MAP 0210: General problem resolution.
ssss-120 ssss A SCSD busy or command error.
Action: Use MAP 0210: General problem resolution.
ssss-122 ssss A SCSD reservation conflict error.
Action: Use MAP 0210: General problem resolution.
ssss-124 ssss A SCSD check condition error occurred.
Action: Use MAP 0210: General problem resolution.
ssss-126 ssss A software error was caused by a hardware failure.
B88 Action: Use MAP 0210: General problem resolution.
ssss-128 190 The error log analysis indicates a hardware failure.
B88 Action: Use MAP 0210: General problem resolution.
ssss
software
ssss-129 190 Error log analysis indicates a SCSD bus problem.
B88 Action: Use MAP 0210: General problem resolution.
ssss
software
ssss-130 ssss Error log analysis indicates a problem reported by the disk drive’s
self-monitoring function.
Action: Use MAP 0210: General problem resolution.
ssss-132 ssss A disk drive hardware error occurred.
Action: Use MAP 0210: General problem resolution.
ssss-133 ssss Use the Subsystem Service Guide to complete diagnosis.
Action: Use MAP 0210: General problem resolution.
ssss-134 B88 The adapter failed to configure.
software Action: Use MAP 0210: General problem resolution.

Reference codes 785

ssss-102 through ssss-640

Service Failing
Request Function
Number Codes Description and Action
ssss-135 ssss The device failed to configure.
B88 Action: Use MAP 0210: General problem resolution.
software
ssss-136 ssss The certify operation failed.
Action: Use MAP 0210: General problem resolution.
ssss-137 ssss Unit attention condition has occurred on the Send Diagnostic command.
B88 Action: Use MAP 0210: General problem resolution.
190
ssss-138 ssss Error log analysis indicates that the disk drive is operating at a higher than
recommended temperature.
Action: Check to be sure none of the air passages in the system covers are
blocked, that no other system environmental warnings are occurring.
Otherwise, go to MAP 0210: General problem resolution.
ssss-140 199 Error log analysis indicates poor signal quality.
B88 Action: Use MAP 0210: General problem resolution.
ssss
ssss-640 Error log analysis indicates a path error.
Action: Use MAP 0285: Multipath I/O (MPIO) problem resolution.

Using service request numbers

Diagnostic applications report problems by using service request numbers (SRNs). The SRN identifies the
component that detected the error code and describes the error condition. Use the SRN information to
identify a list of possible failing items and to find information about any additional isolation procedures.

Service request number formats

If your SRC is a 5-digit hexadecimal number or contains a hyphen in the following formats (xxxxx,
xxx-xxx, xxx-xxxx, xxxx-xxx, xxxx-xxxx), it is an SRN.

Using the list of service request numbers

The list of SRNs is in numeric order. The SRNs in each range may include codes that consist of anywhere
from 6 to 8 digits. When the SRN you are looking for contains 3 digits before the dash, select the link that
contains the first 3 digits followed by the dash of that SRN. Use the same process when the SRN you are
looking for contains 4 digits before the dash. For example, if the SRN is 2570-603, click “SRNs 2502-101
through 25D0-108” on page 687, because this SRN falls between the number range of 2520-(x)xxx and
2590-(x)xxx.

The SRN tables use the following format:

v The first column, Service Request Number (SRN), contains numbers that represent specific failures of
specific functions.
v The second column, SRN Src. (SRN source code), contains the code that identifies the program or
procedure that produced the SRN. For more information about using SRN Src codes, see SRN source
code.
v The third column, Failing Function Codes, represents functional areas of the system unit. When
available, the failing function code links to the FRU that contains this function for each specific system
unit.
v The last column, Description and Action, offers a brief description of the failure that this SRN
represents. It also contains instructions for continuing the problem analysis.

786 System i® and System p®: Reference codes

Using service request numbers

To use the list of SRNs, complete the following steps:

1. Click the item in the list of SRNs that includes the SRN that you want to find.
2. When the SRN table appears, select the appropriate SRN from the first column of the table.
3. Record the code letter for the Source of SRN (the SRN Src. column).
4. Record the failing function codes in the order listed.
5. Perform the action shown in the Description and Action column.

Note: If your SRN is not listed, check to see if xxx or xxxx has been used. The -xxx or -xxxx should
always be the last SRN identified within a specific prefix. For example, for SRN 950-xxxx, the
xxxx represents the last entry within the 950 prefix.

SRN source code

When using SRNs to identify a problem and its resolution, you may need to refer to the source code of
the SRN. The SRN source code identifies the program or procedure that produced the SRN. SRN source
codes include the following:
v A: The SRN is from a steady number in the control (operator) panel display.
v B: The SRN is from a MAP (problem isolation procedure) callout.
v C: The SRN was due to a missing resource at configuration time.
v D: The SRN is from a diagnostic test after complete isolation testing.
v E: The SRN is from a POST failure.
v F: The SRN is from a diagnostic test after partial isolation testing.
v G: The SRN is from the Error Log Analysis program.
v H: The SRN is from a diagnostic message after an 888 sequence.
v J: The SRN is from built-in ROM diagnostics.
v K: The SRN is from offline diagnostics.

For more information, refer to the “List of service request numbers” on page 533.

List of progress codes

The following progress codes (or checkpoints) represent various processes that occur during initial
program load (IPL). The list of progress codes is in numeric order. A general description of the process
represented by the progress code appears beside each number (or range of numbers). Progress codes are
8-characters long, unless otherwise specified.

For information about using this list of progress codes and about progress codes in general, see “Using
progress codes” on page 837.

Use the following list to find information about specific progress codes. The first column represents the
first 4 characters of the 8 character progress code, unless otherwise specified. The second column
describes the progress code and links to information that includes one or more tables. If you do not find
the progress code that you are looking for in this list, ask your next level of support for assistance.

Progress codes: Refer to these topics:

4–character codes (those that begin with a space “AIX IPL progress codes” on page 820
character, a zero, or a two)
BCxx (4 characters) “(BCxx) Base motherboard controller progress codes” on
page 789
C1xx “Service processor progress codes” on page 788

Reference codes 787

List of progress codes

Progress codes: Refer to these topics:

C2xx “(C2xx) Virtual service processor progress codes” on
page 795
C3yx, C500, C5yx, C600, C6xx “IPL status progress codes” on page 797
C700 “(C700) Server firmware IPL status progress codes” on
page 801
C900 “(C900) IPL status progress codes” on page 802
CAxx “(CAxx) Partition firmware progress codes” on page 803
Dxxx (4 characters) “(Dxxx, Exxx) System firmware progress codes for
Models A50 and 185 only” on page 810
D1xx “Service processor progress codes”
D2xx “(D200) Partition status progress codes” on page 818
D6xx “(D6xx) General status progress codes” on page 819
D9xx “(D9xx) General status progress codes” on page 820
Exxx (4 characters) “(Dxxx, Exxx) System firmware progress codes for
Models A50 and 185 only” on page 810

Service processor progress codes

Service processor progress codes are typical reference codes that occur during the initial program load
(IPL) of the server. For more information, click the following link that corresponds to the progress code
that you want to find. If you suspect a problem, contact your next level of support for assistance.

The tables for the service processor progress codes use the following format:
v The first column, Progress Code, contains characters that represent a particular action that the service
processor performs to initialize your server.
v The second column, Description/Action, describes the type of initialization being performed.
v The third column, Failing Item, offers instructions for recovering from a hang on a progress code. Click
the link in this column to view the service actions only when you experience a hang condition on a
progress code. A hang conditions exists when the code in the control panel display does not change for
several minutes and the service processor appears to be stalled (hung). In some cases, you might notice
that the server does not power down normally.

For more information about using progress codes, see “Using progress codes” on page 837.

Use the following list to display the different types of service processor progress codes.

“(C1xx) Service processor progress codes (checkpoints)” on page 789

“(D1xx) Service processor progress codes (service processor dump and platform dump)” on page
816

“(D1xx) Service processor status progress codes” on page 817

788 System i® and System p®: Reference codes

BCxx

(BCxx) Base motherboard controller progress codes

Table 1. (BCxx) Base motherboard controller progress codes

Description/Action Perform all

actions before exchanging Failing
BMC Progress Code Items Failing Items
BC00 Set up the system clock and voltage BPCHANG
regulator module (VRM)
BC01 Set system clock spread spectrum BPCHANG
BC02 Set system clock spread spectrum BPCHANG
BC03 Collection of VPD from the processor BPCHANG
and U3 module
BC04 The PLL and the internal clock on the BPCHANG
U3 module are being set up
BC05 The PLL and the internal clock on the BPCHANG
U3 module are being set up
BC06 Initialization of the Super I/O chip BPCHANG
BC07 Boot block recover set up of the BPCHANG
Super I/O chip
BC08 Set up mode rings on the processor BPCHANG
BC09 Set up the elastic interface BPCHANG
BC0A Tune the elastic interface BPCHANG
BC0B Receiver initial align pattern BPCHANG
BC0C Receiver initial align pattern BPCHANG
BC0D Set up the fuse rings BPCHANG
BC0E Set up the fuse rings BPCHANG
BC0F More tuning of the elastic interface BPCHANG

(C1xx) Service processor progress codes (checkpoints)

C1xx progress codes, or checkpoints, offer information about the initialization of both the service
processor and the server.

Table 1. (C1xx) Service processor progress codes (checkpoints)

Progress Code Description/Action Perform all actions before exchanging Failing Items Failing Items
C10010xx Pre-standby FSPSPC1
C1001014 Pre-standby FSPSPC1
C1001020 Pre-standby FSPSPC1
C1001F00 Pre-standby: starting initial transition file FSPSPC1

Reference codes 789

C1xx

Progress Code Description/Action Perform all actions before exchanging Failing Items Failing Items
C1001F0D Pre-standby: discovery completed in initial transition file. FSPSPC1

While this system displays this checkpoint, the service processor card reads
the system vital product data (VPD). The service processor must complete
reading the system VPD before the system displays the next progress code
(checkpoint). Reading the system VPD might take as long as 15 minutes on
systems with maximum configurations or many disk drives. Wait at least
15 minutes for this checkpoint to change before you decide that the system
is hung.

If you determine that the system is hung at this checkpoint, do the

following:
v On model 285, 520, or 9131-52A, reseat the VPD card. See Exchanging
the VPD card in the model 520 and 285 for more information.
v On all other models (or if the preceding action did not resolve the
problem), use the specified action in the Failing Item column.
C1001F0F Pre-standby: waiting for standby synchronization from initial transition file FSPSPC1
C1001FFF Pre-standby: completed initial transition file FSPSPC1
C1009x02 Hardware object manager: (HOM): build cards IPL step in progress FSPSPC1
C1009x04 Hardware object manager: (HOM): build processors IPL step in progress FSPSPC1
C1009x06 Hardware object manager: (HOM): build chips IPL step in progress FSPSPC1
C1009x08 Hardware object manager: (HOM): build HOM IPL step in progress FSPSPC1
C1009x10 Hardware object manager: (HOM): configure HOM IPL step in progress FSPSPC1
C1009x12 Hardware object manager: (HOM): initialize HOM IPL step in progress FSPSPC1
C1009x18 Hardware object manager: (HOM): validate HOM IPL step in progress FSPSPC1
C1009x1B GARD IPL step in progress FSPSPC1
C1009x20 Get LBIST values IPL step in progress FSPSPC1
C1009x23 Clock test IPL step in progress FSPSPC1
C1009x28 Frequency control IPL step in progress FSPSPC1
C1009x30 Initalize JTAG IPL step in progress FSPSPC1
C1009x38 Mask attentions IPL step in progress FSPSPC1
C1009x40 CEC flush IPL step in progress FSPSPC1
C1009x48 Scan interface basic assurance tests (SIBATs) IPL step in progress FSPSPC1
C1009x50 LBIST IPL step in progress FSPSPC1
C1009x58 ABIST IPL step in progress FSPSPC1
C1009x60 Asset protection IPL step in progress FSPSPC1
C1009x68 Wire test IPL step in progress FSPSPC1
C1009x70 Memory size IPL step in progress FSPSPC1
C1009x78 Long scan initialization IPL step in progress FSPSPC1
C1009x80 Start clocks IPL step in progress FSPSPC1
C1009x88 SCOM initialization IPL step in progress FSPSPC1
C1009x90 Run interface alignment procedure IPL step in progress FSPSPC1
C1009x98 DRAM initialization IPL step in progress FSPSPC1
C1009x9B Random data test IPL step in progress FSPSPC1
C1009xA0 Memory diagnostic IPL step in progress FSPSPC1

790 System i® and System p®: Reference codes

C1xx

Reference codes 795

C2xx

Progress Code Function/Description

C200 3100 Validating ISL command parameters
C200 3111 Waiting for Bus object to become operational
C200 3112 Waiting for bus unit to become disabled
C200 3115 Waiting for creation of bus object
C200 3150 Sending ISL command to bus unit
C200 31FF Waiting for ISL command completion
C200 32FF ISL command complete successfully
C200 3300 Start SoftPOR of a failed ISL slot
C200 3350 Waiting for SoftPOR of a failed ISL slot
C200 33FF Finish SoftPOR of a failed ISL slot
Load source device connection phase
C200 4100 Waiting for load source device to enlist
C200 4200 Load source device has enlisted
C200 4300 Preparing connection to load source device
C200 43FF Load source device is connected
Main store dump phase
C200 5100 Preparing to initiate MSD phase
C200 5110 Loading SID 82 from load source device
C200 5115 MSD Phase I
C200 5120 Writing processor registers into SID 82
C200 5125 MSD Phase II
C200 5130 Writing main store pages to the load source device
C200 5133 Writing hardware page table to the load source device
C200 5135 MSD Phase III
C200 5140 Storing (final) SID 82 back to the load source device
C200 5150 Allocating the hardware page table
C200 51FF MSD processing complete
Load system Licensed Internal Code from load source phase
C200 6000 Locating First LID information on the load source
C200 6005 Clearing all partition main store
C200 6010 Locating Next LID information on the load source
C200 6020 Verifying LID information
C200 6030 Priming LP Configuration LID
C200 6040 Preparing to initiate LID load from load source
C200 6050 LP Configuration LID primed successfully
C200 6060 Waiting for LID load to complete
C200 6100 LID load completed successfully
C200 6200 Loading raw kernel memory image
C200 62FF Loading raw kernel memory image completed successfully
Load source device disconnection phase
C200 7100 Disconnecting from load source device

796 System i® and System p®: Reference codes

C2xx

Progress Code Function/Description

C200 7103 Removing load source device from LID Manager object
C200 7105 Preparing to remove the load source IP from the primary partition
C200 7110 Preparing to remove the load source IOP from the primary partition
C200 7120 Non-load source IOP has been successfully removed from the primary partition
C200 7125 Load source IOP has been successfully removed from the primary partition
C200 7130 Calling fatal error on the Transport Manager bus unit object
C200 71FF Load source is successfully disconnected
Start processors phase
C200 8040 Begin transfer slot locks to partition
C200 8060 End transfer slot locks to partition
C200 8080 Begin transfer VIO slot locks to partition
C200 80A0 End transfer VIO slot locks to partition
C200 80FF Hypervisor low level session manager object is ready
C200 8100 Initializing SP Communication Area #2
C200 8104 Loading data structures into main store
C200 8110 Initializing event paths
C200 8120 Starting processors
C200 8130 Begin associate of system ports
C200 8138 Associating system ports to the RPA partition
C200 813F End associate of system ports
C200 81FF Processors started successfully, now waiting to receive the continue acknowledgement from
System Licensed Internal Code
C200 8200 Continue acknowledgement received from System Licensed Internal Code
C200 82FF VSP IPL complete successfully

IPL status progress codes

A server that stalls during an initial program load (IPL) of the operating system indicates a problem with
the operating system code or hardware configuration. In this case, your only service action is to call your
next level of support. If the problem is in the operating system code or hardware configuration,
exchanging any hardware FRU will not fix the problem.

Below is reference information that gives a quick overview of the IPL progress codes and the function
associated with each.

Note:
v The following table contains the C6xx xxxx IPL status progress codes. Some of these codes can
appear on your control panel or HMC display. Depending on the system activity and disk
configuration the duration of time that each code is displayed can vary. Eventually the system
will continue to the next progress code until the IPL status is complete, or if an error is detected
an SRC other than a C6xx xxxx will be displayed.
v There are instances when multiple tasks might be happening at the same time, so the progress
code on the panel may not reflect the code module having problems.
The mode of the IPL (A, B, or D) determines, in part, which status SRCs are displayed. The different
types of IPL use different progress codes, so you will not see all of the progress codes in the table below
when you perform an IPL.

Reference codes 797

C3yx, C500, C5yx, C600, C6xx

The table of IPL status progress codes uses the following format:
v The first column, Progress Code, contains characters that represent a particular action your server
performs during initialization of the supported operating system.
v The second column, Function/Description, identifies the action or procedure that produced the
progress code.
For more information about using progress codes, see “Using progress codes” on page 837.

Table 1. IPL status progress codes

Progress Code Function/Description

C6nn 4404 Licensed Internal Code log started. If Auto Copy in progress, nn is the percent complete.
Module called: MsdStartSf.
C600 4405 Dump auto copy completed successfully. Module called: MsdStartSf.
C600 4406 Shutdown/Programmed IPL started (MSD related). Module called: MsdStartSf, MsdInit.
The following are DST progress codes for attended IPLs
C600 4500 Verifying network attributes
C600 4501 Looking for the console
C600 4504 Verifying system serial number
C600 4505 Verifying system type
C600 4506 Verifying system-unique ID
C600 4507 Starting ’before DST’ DASD checker
C600 4508 Verifying system password (if DASD check OK; if not OK this is checked when IPLing past
DST)
C600 4509 Starting DASD migration function (only if migrating)
C600 450A Starting ’after DST’ DASD checker (can happen twice)
The following are DST progress codes for unattended IPLs
C600 4500 Verifying network attributes
C600 4502 Starting DST display task (SSP only)
C600 4503 Checking possible MRI on media (SSP only)
C600 4504 Verifying system serial number
C600 4505 Verifying system type
C600 4506 Verifying system-unique ID
C600 4508 Verifying system password (if DASD check OK)
C600 450A Starting ’after DST’ DASD checker
C600 4A57 Parallel database recovery and is at Pass 1
C600 4A60 Parallel database initialization is at Pass 1
C600 4B57 Parallel database recovery is at Pass 2
C600 4B60 Parallel database initialization is at Pass 2
C600 4C57 Parallel database recovery is at Pass 3
C600 4C60 Parallel database initialization is at Pass 3
C600 4F57 The system is recovering all database objects. This step can take several hours.
C600 4F60 The system is examining all objects during database initialization.

Note: At this point Licensed Internal Code initialization is complete, and the i5/OS operating system
starts. All hardware is verified. Operating system initialization is complete when the sign-on screen
displays on the console.

(C700) Server firmware IPL status progress codes

A server that stalls during an initial program load (IPL) of the server firmware indicates a problem with
the server firmware code. Server firmware IPL status progress codes enable your service provider and
next level of support to more easily identify the server firmware component causing the problem.

Reference codes 801

C700

If the C700 progress that you see is not C700 4091, your only service action is to collect information on
words 3 and 4 of the SRC, and call your next level of support. For more information, see Collecting
reference codes or Displaying error and event logs.

Note: If the problem is in the server firmware code, exchanging any hardware FRU will not fix the
problem.

Table 1. (C700) Server firmware IPL status progress codes

Progress Code Function/Description

C700 4091 The system power on has reached a standby state.

If you performed a service action or recovery procedure, and C700 4091 is still displayed,
activate the partition. Activating the partition changes the system to an operating state and
clears the SRC.
C700 xxxx If the system stalls during an initial program load (IPL) of the server firmware, a problem
has occurred with the server firmware code. Exchanging any hardware FRU will not fix the
problem.

Collect information on words 3 and 4 of the SRC, and call your next level of support. For
more information, see Collecting reference codes or Displaying error and event logs.

(C900) IPL status progress codes

As your server performs an IPL, the control panel displays progress codes that indicate the status of the
IPL. Often, you can use these progress codes to help you perform problem analysis. The following list
offers information on the IPL status progress codes that have a format of C9xxxxxx.

Table 1. (C900) IPL status progress codes

Progress Code Function/Description

C900 2810 Reclaim machine context
C900 2820 Resolve system objects
C900 2825 Convert Work Control Block Table
C900 2830 System value object
C900 28C0 Prepare SPCF job
C900 28C5 Initialize system objects
C900 2910 Start system logging
C900 2920 Library and object information repository (OIR) cleanup
C900 2925 Verify POSIX** root directories
C900 2930 Database cross-reference
C900 2940 Console configuration
C900 2950 Install complex objects
C900 2960 Sign on processing
C900 2965 Software Management Services (SMS) initialization
C900 2967 Applying PTFs
C900 2968 IPL options
C900 2970 Database recovery part 1, journal recovery part 1
C900 2973 This recovery step attempts to perform any needed recovery for database files that were
being changed, created or deleted when an abnormal system end occurred.

802 System i® and System p®: Reference codes

C900

Progress Code Function/Description

C900 2976 This recovery step verifies the object recovery list performs any needed recovery for
journals and journal receivers.
C900 2978 This progress code displays after progress codes C9002A70 through C9002976 have been
completed
C900 2980 Storage requirements
C900 2990 Performance adjustments
C900 29A0 System control block
C900 29B0 Spool initialization
C900 29C0 Work control block table
C900 2A80 Before starting system jobs
C900 2A85 Bringing up POSIX SAG
C900 2A87 POSIX SAG restart and signals initialization
C900 2A90 Starting system jobs
C900 2A95 Abnormal Work Control Block Table cleanup
C900 2AA0 Damage notification
C900 2AA1 This recovery step either rolls back or completes certain uncompleted database operations
that were run under commitment control
C900 2AA2 This recovery completes certain journal operations that were in progress when the system
ended processing
C900 2AA3 This recovery sends messages to QHST for database files that may have been damaged by a
system end
C900 2AA3 This recovery sends messages to QHST for database files that may have been damaged by a
system end
C900 2AA4 This progress code displays after progress codes C9002AA0 - C9002AA3 have been
completed
C900 2AA5 Integrated File System/New File System (NFS) directory recovery
C900 2AAC Integrated File System conversion
C900 2AB0 Database recovery part 2
C900 2AC0 Document Library Object (DLO) recovery
C900 2B10 Establish event monitors
C900 2B30 QLUS job
C900 2B40 Device configuration
C900 2C10 After system arbiter
C900 2C20 SNADS recovery
C900 2C25 ZMF component (Mail Enablement (OeDS) Framework) recovery
C900 2C40 Work Control Block Table cleanup
C900 2CF0 Reclaim storage
C900 2F00 IPL complete

(CAxx) Partition firmware progress codes

Partition firmware progress codes offer information about the progress of partition firmware as it is
initializing. In some cases, a server might hang (or stall) at one of these progress codes without
displaying an 8-character system reference code (SRC). Only during such a hang condition should you
take any service action related to the progress code.
Reference codes 803
CAxx

The table of firmware progress codes uses the following format:

Table 1. (CF00) xxxx Linux kernel boot progress codes

Attention Code Function/Description Repair Action/Possible Failing FRU

CF000012 Set up initialization If the system or partition does not
progress past this code, contact your
Linux provider.
CF000015 Set up is complete If the system or partition does not
progress past this code, contact your
Linux provider.
CF000020 External interrupt controller server If the system or partition does not
initialization progress past this code, contact your
Linux provider.
CF000021 External interrupt controller server If the system or partition does not
complete progress past this code, contact your
Linux provider.
CF000100 Memory manager initialization If the system or partition does not
progress past this code, contact your
Linux provider.
″Linux ppc64″ Indicates that the kernel has finished If the system or partition does not
booting. ″Linux ppc64″ is an progress past this code, contact your
example; this text may be different Linux provider.
based on the Linux vendor and the
release.

(Dxxx, Exxx) System firmware progress codes for Models A50 and 185
only
Table 1. (Dxxx, Exxx) System firmware progress codes for Models A50 and 185 only

Attention: This table lists the 4-character system firmware progress codes for Models A50 and 185 only.
If you are looking up an 8-character SRC, such as ″AA00E1F3″, enter all eight characters in the search
field.

Progress Code Description/Action Perform all actions before exchanging Failing Failing Items
Items
D001 PCI probe process complete; create PCI interrupt routing PFW1548
properties
D002 PCI adapter NVRAM hint created; system is rebooting FWPCI5
D003 PCI probing complete PFW1548

810 System i® and System p®: Reference codes

Dxxx, Exxx

Progress Code Description/Action Perform all actions before exchanging Failing Failing Items
Items
D004 Starting install-console; loading GUI package PFW1548
D008 Initialize the console and flush the queues PFW1548
D00D Evaluating NVRAM script PFW1548
D010 First pass of open firmware initialization complete; establish PFW1548
parameters for restart.
D011 First pass of open firmware initialization complete; control PFW1548
returned to initialization firmware
D012 Second pass of open firmware initialization complete; control PFW1548
returned to initialization firmware
D099 Starting system information validation utility PFW1548
D100 The system serial number was found to be blank. On the console, Enter a valid serial number.
text that describes the requested information follows the progress You can edit the number by
code, similar to the following example: using the backspace and delete
D100: Enter the serial number (Must be 7 characters) keys. If the prompt continues
to appear after you enter the
After you enter the serial number, the console displays a number, contact your service
confirmation prompt that includes the serial number that you just representative for assistance.
entered. The prompt also asks if you want to accept the serial
number, similar to the following example:
Accept number? (Enter 'y' or 'Y' to accept)
D102 The system type number (machine type) was found to be blank. Enter a valid type number. You
On the console, text that describes the requested information can edit the number by using
follows the progress code, similar to the following example: the backspace and delete keys.
D102: Enter the type number (Must be 4 characters) If the prompt continues to
appear after you enter the
After you enter the type number, the console displays a number, contact your service
confirmation prompt that includes the type number that you just representative for assistance.
entered. The prompt also asks if you want to accept the type
number, similar to the following example:
Accept number? (Enter 'y' or 'Y' to accept)
D104 The system model number (machine type and model) was found Enter a valid system model
to be blank. On the console, text that describes the requested number. You can edit the
information follows the progress code, similar to the following number by using the
example: backspace and delete keys. If
D104: Enter the model number (Must be 3 characters) the prompt continues to
appear after you enter the
After you enter the model number, the console displays a number, contact your service
confirmation prompt that includes the model number that you just representative for assistance.
entered. The prompt also asks if you want to accept the model
number, similar to the following example:
Accept number? (Enter 'y' or 'Y' to accept)
D106 The machine universally unique ID (UUID) was found to be blank. There is no repair action for
A new value is calculated and the field is updated. this checkpoint. If the
checkpoint continues to appear
on subsequent system
power-on cycle, contact your
next level of support for
assistance.

Reference codes 811

Dxxx, Exxx

Progress Code Description/Action Perform all actions before exchanging Failing Failing Items
Items
D108 The system firmware has not established whether this system has PFW1548
an IBM logo yet. On the console, text that describes the requested
information follows this progress code, similar to the following
example:
D108: IBM logo'ed product? (1=Yes, 2=No)
D5BB This is a delay before booting the operating system to give an PFW1548
operator the opportunity to use a keystroke override to modify the
boot behavior. A countdown is displayed to indicate the time
remaining before the boot proceeds.
E101 Create RTAS node PFW1548
E102 Load and initialize RTAS PFW1548
E105 Transfer control to operating system (normal mode boot) PFW1548
E10A Load RTAS device tree PFW1548
E10B Set RTAS device properties PFW1548
E130 Build device tree PFW1548
E134 Create memory node PFW1548
E138 Create options node PFW1548
E139 Create aliases node and system aliases PFW1548
E13A Create packages node PFW1548
E140 Loading operating system PFW1548
E141 Synchronize operating system bootlist with management module PFW1548
bootlist
E142 Management module bootlist PFW1548

Set from operating system bootlist

E143 Operating system bootlist set from management module bootlist PFW1548
E149 Create boot manager node PFW1548
E14A Build vital product data-to-operating system lookup table PFW1548
E14C Create terminal emulator node PFW1548
E14D Load boot image. PFW1548

See Problems with loading and starting the operating system (AIX
and Linux)
E150 Create host (primary) PCI controller node PFW1548
E151 Probing PCI bus FWPCI5
E152 Probing for adapter FCODE; evaluate if present FWPCI5
E153 End adapter FCODE probing and evaluation FWPCI5
E154 Create PCI bridge node FWPCI5
E155 Probing PCI bridge secondary bus FWPCI5
E158 Reserved NEXTLVL
E15B Transfer control to operating system (service mode boot) PFW1548

See Problems with loading and starting the operating system (AIX
and Linux)
E15F Adapter VPD evaluation FWPCI5

812 System i® and System p®: Reference codes

Dxxx, Exxx

Progress Code Description/Action Perform all actions before exchanging Failing Failing Items
Items
E170 Beginning of PCI bus probe FWPCI5
E172 First pass of PCI device probe FWPCI5
E174 Establishing host connection FWHOST
E175 Bootp request FWHOST
E176 TFTP file transfer

816 System i® and System p®: Reference codes

D1xx

Progress Code Description/Action Perform all actions before exchanging Failing Items Failing Items
D1101xxx Dump safety net trace: SND_FSP_TRACE FSPSPD1
D1111xxx Dump /opt/p0/* FSPSPD1
D1121xxx Dump /opt/p1/* FSPSPD1
D1131xxx Dump all traces FSPSPD1
D1141xxx Dump code version FSPSPD1
D1151xxx Dump all /opt/p3 except rtbl FSPSPD1
D1161xxx Dump pddcustomize -r command FSPSPD1
D1171xxx Dump registry -l command FSPSPD1
D1181xxx Dump all /core/core.* files FSPSPD1
D1191xxx Dump BDMP component trace (after dump if enough space) FSPSPD1
D11A1xxx Dump any state information before dumping starts FSPSPD1
D1231xxx Dump update dump headers FSPSPD1
D1241xxx Dump CRC1 calculation off FSPSPD1
D1251xxx Dump CRC1 calculation on FSPSPD1
D1261xxx Dump CRC2 calculation off FSPSPD1
D1271xxx Dump CRC2 calculation on FSPSPD1
D1281xxx Dump output the calculated CRC1 (sai_headers) FSPSPD1
D1291xxx Dump output the calculated CRC2 (data and data headers) FSPSPD1
D12A1xxx Jump to the position in dump directly after CRC1 FSPSPD1
D12B1xxx Initialize the headers dump time and serial numbers FSPSPD1
D12C1xxx Display final SRC to panel FSPSPD1
D12D1xxx Remove /core/core.app.time.pid FSPSPD1
D12E1xxx Remove /core/core.* FSPSPD1
D12F1xxx Display beginning SRC to panel FSPSPD1
D1301xxx Turn off error log capture into dump FSPSPD1
D1311xxx Turn on error log capture into dump FSPSPD1
D1321xxx Store information about existing core files FSPSPD1
D1381xxx Invalidate the dump FSPSPD1
D1391xxx Check for valid dump sequence FSPSPD1
D13A1xxx Get dump identity sequence FSPSPD1
D13B1xxx Get dump length sequence FSPSPD1
D1FF1xxx Dump complete FSPSPD1
D1xx3000 - Platform dump status codes FSPSPD1
D1xx3FFF

(D1xx) Service processor status progress codes

D1xx reference codes, posted by the service processor, offer information about the state of the service
processor during a power-off operation.

Table 1. (D1xx) Service processor status progress codes

Reference codes 817

D1xx

Progress Code Description/Action Perform all actions before exchanging Failing Items Failing Items
D1xx900C Breakpoint set in CPU controls has been hit FSPSPD1
D1xxB0FF Request to initiate power-off program has been sent FSPSPD1
D1xxC000 Indicates a message is ready to send to the server firmware to power off FSPSPD1
D1xxC001 Waiting for the server firmware to acknowledge the delayed power off FSPSPD1
notification
D1xxC002 Waiting for the server firmware to send the power off message FSPSPD1
D1xxC003 Server firmware handshaking is complete FSPSPD1

(D200) Partition status progress codes

D200 xxxx SRCs are posted by the Virtual Service Processor (VSP) when powering down a partition.

Table 1. (D200) Partition status progress codes

Progress Code Description/Action Perform all actions before exchanging Failing Items Failing Items
D200A100 Received MSD SP attention
D200A110 Received CPM SP attention
D200A120 Received LL SP attention
D200A130 Received RPA end-of-life event
D200A200 Begin partition power down. SRC word 3 contains the reason for the
power off.

SRC word 3 power down reasons

v 1: White button power down (also known as delayed power off)
v 2: Partition requested power down
v 3: Partition requested end of life
v 4: System wide shutdown
v 5: Attention link loader
v 6: Attention MSD
v 7: Panel function 3 requested
v 8: Panel function 8 requested
v 9: Panel function 22 requested
v A: Panel function 34 requested
D200B050 Begin transfer slot locks to VSP
D200B05F End transfer slot locks to VSP
D200B060 Begin transfer VIO slot locks to VSP
D200B06F End transfer VIO slot locks to VSP
D200B070 Begin reset slots
D200B077 Waiting for reset slots
D200B07F End reset slots
D200B080 Begin reset VIO slots
D200B08F End reset VIO slots
D200B090 Begin soft POR slots
D200B097 Waiting soft POR slots
D200B09F End soft POR slots

818 System i® and System p®: Reference codes

D200

Progress Code Description/Action Perform all actions before exchanging Failing Items Failing Items
D200B100 Sending Hypervisor reset
D200B1FF Hypervisor reset successfully sent
D200B200 Begin forced LP reset (after the 1 second timeout)
D200B210 Send CSP/FSP soft processor reset command (word 3 processor ID, word 4
thread ID)
D200B2FF End forced LP reset
D200B300 Closing Hypervisor events paths
D200B310 Deactivating panel functions
D200B3FF Hypervisor reset complete successfully
D200C100 Sending Hypervisor I/O reset
D200C1FF Hypervisor I/O reset sent successfully
D200C200 Deallocating events
D200C2FF Hypervisor I/O reset complete successfully
D200D100 Removing partition configuration resources
D200D1FF Partition resources removed successfully
D200E050 Begin power off slots
D200E057 Waiting power off slots
D200E05F End power off slots
D200E060 Begin power off VIO slots
D200E06F End power off VIO slots
D200E080 Begin release slot locks
D200E08F End release slot locks
D200E090 Begin release VIO slot locks
D200E09F End release VIO slot locks
D200E0A0 Begin unassociate of system ports
D200E0A8 Unassociate system ports from an RPA partition
D200E0AF End unassociate of system ports
D200E100 Power off SPCN racks
D200E110 Issuing a rack power off command
D200E120 Rack power off command complete successfully
D200E1FF SPCN racks powered off phase complete

(D6xx) General status progress codes

The following table lists general status progress codes with a format of D6xx xxxx in numeric order. The
xx after D6 in each progress code represents two hexadecimal numbers that further define the progress
code.

Table 1. (D6xx) General status progress codes

Progress Code Function/Description

D6xx 0298 Managed system power down started
D6xx 0299 Managed system power down status

Reference codes 819

D6xx

Progress Code Function/Description

D6xx 430A Operating system service partition power down status: indicates that a server firmware
code update is in progress for the P-side (permanent) of the managed system.

Your server may display this progress code for an extended period of time where the ″xx″
increments periodically. Allow the server to complete the processing. Do not interrupt this
process.
D6xx 430B Operating system service partition power down status: indicates that a server firmware
code update is in progress for the T-side (temporary) of the managed system.

Your server may display this progress code for an extended period of time where the ″xx″
increments periodically. Allow the server to complete the processing. Do not interrupt this
process.
D600 43BA Operating system service partition power down status: indicates that a server firmware
code update is in progress to copy the server firmware from the T-side (temporary) of the
managed system to the P-side (permanent).

Your server may display this progress code for an extended period of time. Allow the
server to complete the processing. Do not interrupt this process.
D6xx 0483 Power failed; delay timer is running
D6xx 0484 MI run in progress
D6xx 5500 Managed system power down status; attempting to delete information from the disk
subsystem cache
D6xx 5501 Managed system power down status; indicates that the information from the disk
subsystem cache was deleted successfully
D6xx 5502 Managed system power down status; indicates that the system failed to delete information
from the disk subsystem cache
D6xx 5503 Managed system power down status, which indicates the information from the disk
subsystem cache was deleted with qualified success

(D9xx) General status progress codes

The D9xx progress codes indicate the progress of powering-off a partition. Not all progress codes below
apply to all operating systems.

Table 1. (D9xx) General status progress codes

Progress Code Function/Description

D900 2740 Power off immediate
D900 2750 All subsystems ended
D900 2760 Device configuration shutdown
D900 2770 QLUS job ending
D900 2780 Close database cross-reference files
D900 2790 QSYSARB job ending
D900 27C0 System jobs are ending

AIX IPL progress codes

This section provides descriptions for the numbers and characters that display on the operator panel and
descriptions of the location codes used to identify a particular item.

820 System i® and System p®: Reference codes

AIX IPL progress codes

Note: The AIX IPL progress codes occur on only when running AIX or booting standalone diagnostics.
The codes do not occur on servers that run Linux or on Linux partitions.

Operator panel display numbers

This section contains a list of the various numbers and characters that display in the operator panel
display. There are three categories of numbers and characters. The first group tracks the progress of the
configuration program. The second group tracks the progress of the diagnostics. The third group provides
information about messages that follow an 888 sequence.

AIX configuration program indicators

832 System i® and System p®: Reference codes

AIX IPL progress codes

Progress code Description/Action

2611 36/72 GB 4 mm internal tape drive
2612 80/160 GB internal tape drive with VXA2 technology
2613 200/400 GB LTO2 Tape drive
2614 VXA3 160/320 GB Tape Drive
2615 Configuring DAT160 80 GB Tape drive
2617 Configuring LTO3 400 GB Tape drive
2621 PCI-X Dual-port 4x HCA Adapter being configured
2631 Integrated IDE controller
2640 IDE Disk Drive, 2.5 inch
2641 73 GB SCSI disk drive 68 pin 10K rpm being identified or configured.
2642 73 GB SCSI disk drive 80 pin 10K rpm with u3 carrier being identified or configured.
2643 73 GB SCSI disk drive 80 pin 10K rpm with u3 carrier being identified or configured. (For
OpenPower systems)
2644 146 GB SCSI disk drive 68 pin 10K rpm being identified or configured.
2645 146 GB SCSI disk drive 80 pin 10K rpm with u3 carrier being identified or configured.
2646 146 GB SCSI disk drive 80 pin 10K rpm with u3 carrier being identified or configured. (For
OpenPower systems)
2647 300 GB SCSI disk drive 68 pin 10K rpm being identified or configured.
2648 300 GB SCSI disk drive 80 pin 10K rpm with u3 carrier being identified or configured.
2649 300 GB SCSI disk drive 80 pin 10K rpm with u3 carrier being identified or configured. (For
OpenPower systems)
264b 36 GB SCSI disk drive 80 pin 15K rpm with u3 carrier being identified or configured.
264d 36 GB SCSI disk drive 80 pin 15K rpm with u3 carrier being identified or configured. (For
OpenPower systems)
264e 73 GB SCSI disk drive 80 pin 15K rpm with u3 carrier being identified or configured.
2650 ESS iSCSI devices being identified or configured.
2651 SVC being identified or configured.
2652 SVCCISCOi being identified or configured.
2653 73 GB SCSI disk drive 80 pin 15K rpm with u3 carrier being identified or configured. (For
OpenPower systems)
2654 146 GB SCSI disk drive 80 pin 15K rpm with u3 carrier being identified or configured.
2655 146 GB SCSI disk drive 80 pin 15K rpm with u3 carrier being identified or configured. (For
OpenPower systems)
2656 73 GB SCSI disk drive 80 pin 15K rpm being identified or configured.
2657 146 GB SCSI disk drive 80 pin 15K rpm being identified or configured.
2658 73 GB SCSI disk drive 80 pin 10K rpm being identified or configured.
2659 146 GB SCSI disk drive 80 pin 10K rpm being identified or configured.
265b 300 GB SCSI disk drive 80 pin 10K rpm being identified or configured.
2D01 PCI-X Quad Channel U320 SCSI RAID battery pack
2D05 PCI-X266 Planar 3 GB SAS RAID adapter battery pack
2D07 PCI-X DDR Auxiliary Cache adapter

AIX diagnostics load-progress indicators

Reference codes 833

AIX IPL progress codes

Note: Some systems might produce 4-digit codes. If the leftmost digit of a 4-digit code is 0, use the three
rightmost digits.

Progress code Description/Action

c00 AIX Install/Maintenance loaded successfully.
c01 Insert the first diagnostic diskette.
c02 Diskettes inserted out of sequence.
c03 The wrong diskette is in diskette drive.
c04 The loading stopped with an irrecoverable error.
c05 A diskette error occurred.
c06 The rc.boot configuration shell script is unable to determine type of boot.
c07 Insert the next diagnostic diskette.
c08 RAM file system started incorrectly.
c09 The diskette drive is reading or writing a diskette.
c20 An unexpected halt occurred, and the system is configured to enter the kernel debug
program instead of entering a system dump.
c21 The ifconfig command was unable to configure the network for the client network host.
c22 The tftp command was unable to read client’s ClientHostName. info file during a client
network boot.
c24 Unable to read client’s ClientHostName.info file during a client network boot.
c25 Client did not mount remote miniroot during network install.
c26 Client did not mount the /usr file system during the network boot.
c29 The system was unable to configure the network device.
c31 Select the console display for the diagnostics. To select No console display, set the key
mode switch to Normal, then to Service. The diagnostic programs then load and run the
diagnostics automatically. If you continue to get the message, check the cables and make
sure you are using the serial port.
c32 A directly attached display (HFT) was selected.
c33 A TTY terminal attached to serial ports S1 or S2 was selected.
c34 A file was selected. The console messages store in a file.
c35 No console found.
c40 Configuration files are being restored.
c41 Could not determine the boot type or device.
c42 Extracting data files from diskette.
c43 Cannot access the boot/install tape.
c44 Initializing installation database with target disk information.
c45 Cannot configure the console.
c46 Normal installation processing.
c47 Could not create a physical volume identifier (PVID) on disk.
c48 Prompting you for input.
c49 Could not create or form the JFS log.
c50 Creating root volume group on target disks.
c51 No paging devices were found.
c52 Changing from RAM environment to disk environment.

834 System i® and System p®: Reference codes

AIX IPL progress codes

Progress code Description/Action

c53 Not enough space in the /tmp directory to do a preservation installation.
c54 Installing either BOS or additional packages.
c55 Could not remove the specified logical volume in a preservation installation.
c56 Running user-defined customization.
c57 Failure to restore BOS.
c58 Displaying message to turn the key.
c59 Could not copy either device special files, device ODM, or volume group information from
RAM to disk.
c61 Failed to create the boot image.
c62 Loading platform dependent debug files.
c63 Loading platform dependent data files.
c64 Failed to load platform dependent data files.
c70 Problem Mounting diagnostic CD-ROM disc.
c99 Diagnostics have completed. This code is only used when there is no console.
Fxx (xx is any number) Refer to Firmware chapter of the service manual.

Dump progress indicators (dump status codes)

The following dump progress indicators, or dump status codes, are part of a Type 102 message.

Note: When a lowercase c is listed, it displays in the lower half of the character position. Some systems
produce 4-digit codes, the two leftmost positions can have blanks or zeros. Use the two rightmost
digits.

Progress code Description/Action

0c0 The dump completed successfully.
0c1 The dump failed due to an I/O error.
0c2 A dump, requested by the user, is started.
0c3 The dump is inhibited.
0c4 The dump device is not large enough.
0c5 The dump did not start, or the dump crashed.
0c6 Dumping to a secondary dump device.
0c7 Reserved.
0c8 The dump function is disabled.
0c9 A dump is in progress.
0cc Unknown dump failure.

Crash codes

Note: Some systems may produce 4-digit codes. If the leftmost digit of a 4-digit code is 0, use the three
rightmost digits.

The crash codes that follow are part of a Type 102 message. These crash codes are grouped into three
categories:

Reference codes 835

AIX IPL progress codes

Category 1 Dump analysis is the appropriate first action in Problem Determination. Begin the
Problem Determination process with software support.
Category 2 Dump analysis most likely will not aid in Problem Determination. Begin the Problem
Determination process with hardware support.
Category 3 Both software and hardware support may be needed in Problem Determination, go to 888
sequence in operator panel display to assist in problem isolation.

Category 1 crash progress code

Progress code Description/Action

300 Data storage interrupt from the processor.
32x Data storage interrupt because of an I/O exception from IOCC.
38x Data storage interrupt because of an I/O exception from SLA.
400 Instruction storage interrupt.
700 Program interrupt.

Category 2 crash progress code

Progress code Description/Action

200 Machine check because of a memory bus error.
201 Machine check because of a memory timeout.
202 Machine check because of a memory card failure.
203 Machine check because of an out of range address.
204 Machine check because of an attempt to write to ROS.
205 Machine check because of an uncorrectable address parity.
206 Machine check because of an uncorrectable ECC error.
207 Machine check because of an unidentified error.
208 Machine check due to an L2 uncorrectable ECC.
500 External interrupt because of a scrub memory bus error.
501 External interrupt because of an unidentified error.
51x External interrupt because of a DMA memory bus error.
52x External interrupt because of an IOCC channel check.
53x External interrupt from an IOCC bus timeout; x represents the IOCC number.
54x External interrupt because of an IOCC keyboard check.
800 Floating point is not available.

Category 3 crash progress code

Progress code Description/Action

000 Unexpected system interrupt.
558 There is not enough memory to continue the IPL.
600 AIX 4.3.3.3 and above: Alignment Interrupt. If pre-AIX 4.3.3.3: AIX has crashed because the
Portability Assist Layer (PAL) for this machine type has detected a problem.
605 AIX 4.3.3.3 and above: AIX has crashed because the Portability Assist Layer (PAL) for this
machine type has detected a problem.

836 System i® and System p®: Reference codes

Using progress codes

Progress codes (or checkpoints) offer information about the stages involved in powering on and
performing initial program load (IPL). Although progress codes do not always indicate an error, in some
cases your server can pause indefinitely (hang) without displaying an 8-character reference code. Only
when you experience such a hang condition should you take any action with respect to a progress code.
When you look up a progress code, the information indicates the most appropriate action for that
progress code.

Progress code formats

Progress codes appear in several formats:

v an 8–digit hexadecimal number that begins with C (except for CB) or D (except for DA)
v a 3-digit hexadecimal number
v a 4-digit hexadecimal number that has a value between 2000 and 27FF
v a 4-digit hexadecimal number that begins with a 0, 2, BC, D, or E.

When the control panel displays more than eight characters, use only the first eight characters to find the
progress code. The characters that display beyond the first eight represent a location code that can assist
you in diagnosing the problem.
Notes:
1. Some operating systems, including Linux, do not produce progress codes when performing an IPL
2. Your server might display progress codes in the system control panel (for systems with a physical
control panel) or in the virtual console on the Hardware Management Console.

Depending on the progress code you encounter, you might use the Advanced System Management
Interface (ASMI) or System Management Services (SMS) to view progress code logs.

Using the Advanced System Management Interface to view progress code logs (all models except A50
and 185)

The service processor keeps two logs of progress codes. Use the ASMI to view the progress code logs. To
view the progress logs, complete the following steps:
1. Access the ASMI and log in
2. Select System Information, then select either Previous Boot Progress Indicators or Progress Indicator
History.
v Selecting Previous Boot Progress Indicators shows the progress codes that the server displayed in
the control panel during the last system boot.
v Progress Indicator History shows the latest progress codes that the server is currently displaying in
the control panel.

Using System Management Services to view progress code logs

Using the System Management Services (SMS) to view progress code logs (models A50 and 185)

The system management services (SMS) keeps three logs of progress codes. Use the SMS console to access
the SMS menus to look at the progress code logs. To view the logs, complete the following steps:
1. Access the SMS menus.
2. Select System Service Aids > Progress Indicator History, then select Current Boot Progress
Indicators, Previous Boot Progress Indicators or Previous Failover Permanent Side Boot.
v Selecting Current Boot Progress Indicators shows the latest progress codes that the server is
currently displaying in the control panel.

Reference codes 837

Using progress codes

v Selecting Previous Boot Progress Indicators shows the progress codes that the server displayed in
the control panel during the last system boot.
v Selecting Previous Failover Permanent Side Boot shows the progress codes that the server
displayed in the control panel during the last boot in which the server was unable to boot from the
T (temporary) side and boot from the P (permanent) side.

Selecting Progress Indicator History shows the latest progress codes that the server is currently
displaying in the control panel.

Using the list of progress codes

The list of progress codes is in numeric order. The first column represents either an entire 4 character
progress code or the first 4 characters of an 8-character progress code. The second column describes the
progress code and links to information that includes one or more tables and, when necessary, a
description of the table columns.

To use the list of progress codes, locate the code that you want to find in the first column and click the
link in the second column.

For more information, refer to the “List of progress codes” on page 787.

Reference codes that begin with a number sign (#)

When viewed from the Service Focal Point serviceable event list, a reference code that begins with a
number sign character (#) represent an AIX diagnostics message. If you do not have a Hardware
Management Console (HMC) running the Service Focal Point application you will never see a reference
code that begins with a number sign character.

You can show the text associated with the reference code by selecting the View Details action and
viewing all of the serviceable event data. The message displayed might be informational only or might
suggest a corrective action.

To resolve the event, follow the action described in the message. In general, do not suspect a hardware
problem unless performing the suggested action is ineffective.

The following example show the message associated with reference code #2533902:

No trouble was found with this adapter. However, the ethernet adapter diagnostics indicate that
there may be a problem with the connection to the network. It is suggested that Advanced
Diagnostic Testing with the wrap plug be performed on this adapter in order to better isolate
the cause of this network interface problem.

838 System i® and System p®: Reference codes

Appendix. Notices
This information was developed for products and services offered in the U.S.A.

The manufacturer may not offer the products, services, or features discussed in this document in other
countries. Consult the manufacturer’s representative for information on the products and services
currently available in your area. Any reference to the manufacturer’s product, program, or service is not
intended to state or imply that only that product, program, or service may be used. Any functionally
equivalent product, program, or service that does not infringe any intellectual property right of the
manufacturer may be used instead. However, it is the user’s responsibility to evaluate and verify the
operation of any product, program, or service.

The manufacturer may have patents or pending patent applications covering subject matter described in
this document. The furnishing of this document does not give you any license to these patents. You can
send license inquiries, in writing, to the manufacturer.

The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law: THIS INFORMATION IS PROVIDED “AS IS” WITHOUT
WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain
transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically
made to the information herein; these changes will be incorporated in new editions of the publication.
The manufacturer may make improvements and/or changes in the product(s) and/or the program(s)
described in this publication at any time without notice.

Any references in this information to Web sites not owned by the manufacturer are provided for
convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at
those Web sites are not part of the materials for this product and use of those Web sites is at your own
risk.

The manufacturer may use or distribute any of the information you supply in any way it believes
appropriate without incurring any obligation to you.

Any performance data contained herein was determined in a controlled environment. Therefore, the
results obtained in other operating environments may vary significantly. Some measurements may have
been made on development-level systems and there is no guarantee that these measurements will be the
same on generally available systems. Furthermore, some measurements may have been estimated through
extrapolation. Actual results may vary. Users of this document should verify the applicable data for their
specific environment.

Information concerning products not produced by this manufacturer was obtained from the suppliers of
those products, their published announcements or other publicly available sources. This manufacturer has
not tested those products and cannot confirm the accuracy of performance, compatibility or any other
claims related to products not produced by this manufacturer. Questions on the capabilities of products
not produced by this manufacturer should be addressed to the suppliers of those products.

All statements regarding the manufacturer’s future direction or intent are subject to change or withdrawal
without notice, and represent goals and objectives only.

The manufacturer’s prices shown are the manufacturer’s suggested retail prices, are current and are
subject to change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject to change before the
products described become available.

This information contains examples of data and reports used in daily business operations. To illustrate
them as completely as possible, the examples include the names of individuals, companies, brands, and
products. All of these names are fictitious and any similarity to the names and addresses used by an
actual business enterprise is entirely coincidental.

If you are viewing this information in softcopy, the photographs and color illustrations may not appear.

The drawings and specifications contained herein shall not be reproduced in whole or in part without the
written permission of the manufacturer.

The manufacturer has prepared this information for use with the specific machines indicated. The
manufacturer makes no representations that it is suitable for any other purpose.

The manufacturer’s computer systems contain mechanisms designed to reduce the possibility of
undetected data corruption or loss. This risk, however, cannot be eliminated. Users who experience
unplanned outages, system failures, power fluctuations or outages, or component failures must verify the
accuracy of operations performed and data saved or transmitted by the system at or near the time of the
outage or failure. In addition, users must establish procedures to ensure that there is independent data
verification before relying on such data in sensitive or critical operations. Users should periodically check
the manufacturer’s support websites for updated information and fixes applicable to the system and
related software.

Trademarks
The following terms are trademarks of International Business Machines Corporation in the United States,
other countries, or both:

Advanced Micro-Partitioning
AIX
AIX 5L
e(logo)server
eServer
Hypervisor
i5/OS
IBM
IBM Arctic960
iSeries
IntelliStation
Java™
Linux®
Micro-Partitioning
Microsoft®
OpenPower
OS/400
POWER
pSeries
System i
System i5
System p
System p5

840 System i® and System p®: Reference codes

UNIX®
Windows®
Windows NT®
xSeries
zSeries

Microsoft®, Windows®, Windows NT®, and the Windows logo are trademarks of Microsoft Corporation in
the United States, other countries, or both.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other
countries, or both.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

UNIX® is a registered trademark of The Open Group in the United States and other countries.

Other company, product or service names may be trademarks or service marks of others.

Regulatory notices

Class A Notices
The following Class A statements apply to the IBM System i models and IBM System p servers with the
exception of those that are specifically identified as Class B.

Federal Communications Commission (FCC) statement

Note: This equipment has been tested and found to comply with the limits for a Class A digital device,
pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against
harmful interference when the equipment is operated in a commercial environment. This equipment
generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with
the instruction manual, may cause harmful interference to radio communications. Operation of this
equipment in a residential area is likely to cause harmful interference, in which case the user will be
required to correct the interference at his own expense.

Properly shielded and grounded cables and connectors must be used in order to meet FCC emission
limits. IBM is not responsible for any radio or television interference caused by using other than
recommended cables and connectors or by unauthorized changes or modifications to this equipment.
Unauthorized changes or modifications could void the user’s authority to operate the equipment.

This device complies with Part 15 of the FCC rules. Operation is subject to the following two conditions:
(1) this device may not cause harmful interference, and (2) this device must accept any interference
received, including interference that may cause undesired operation.

Industry Canada Compliance Statement

This Class A digital apparatus complies with Canadian ICES-003.

Avis de conformité à la réglementation d’Industrie Canada

Cet appareil numérique de la classe A respecte est conforme à la norme NMB-003 du Canada.

European Community Compliance Statement

This product is in conformity with the protection requirements of EU Council Directive 89/336/EEC on
the approximation of the laws of the Member States relating to electromagnetic compatibility. IBM cannot

Appendix. Notices 841

accept responsibility for any failure to satisfy the protection requirements resulting from a
non-recommended modification of the product, including the fitting of non-IBM option cards.

This product has been tested and found to comply with the limits for Class A Information Technology
Equipment according to European Standard EN 55022. The limits for Class A equipment were derived for
commercial and industrial environments to provide reasonable protection against interference with
licensed communication equipment.

Warning: This is a Class A product. In a domestic environment this product may cause radio interference
in which case the user may be required to take adequate measures.

VCCI Statement - Japan

The following is a summary of the VCCI Japanese statement in the box above.

This is a Class A product based on the standard of the Voluntary Control Council for Interference by
Information Technology Equipment (VCCI). If this equipment is used in a domestic environment, radio
disturbance may arise. When such trouble occurs, the user may be required to take corrective actions.

Electromagnetic Interference (EMI) Statement - People’s Republic of China

Declaration: This is a Class A product. In a domestic environment this product may cause radio
interference in which case the user may need to perform practical action.

Electromagnetic Interference (EMI) Statement - Taiwan

The following is a summary of the EMI Taiwan statement above.

Warning: This is a Class A product. In a domestic environment this product may cause radio interference
in which case the user will be required to take adequate measures.

IBM Taiwan Contact Information

842 System i® and System p®: Reference codes

Electromagnetic Interference (EMI) Statement - Korea

Radio Protection for Germany

Dieses Gerät ist berechtigt in Übereinstimmung mit Dem deutschen EMVG vom 9.Nov.92 das
EG–Konformitätszeichen zu führen.

Der Aussteller der Konformitätserklärung ist die IBM Germany.

Dieses Gerät erfüllt die Bedingungen der EN 55022 Klasse A. Für diese von Geräten gilt folgende
Bestimmung nach dem EMVG:

Geräte dürfen an Orten, für die sie nicht ausreichend entstört sind, nur mit besonderer Genehmigung des
Bundesministers für Post und Telekommunikation oder des Bundesamtes für Post und
Telekommunikation betrieben werden. Die Genehmigung wird erteilt, wenn keine elektromagnetischen
Störungen zu erwarten sind.

(Auszug aus dem EMVG vom 9.Nov.92, Para.3, Abs.4)

Hinweis

Dieses Genehmigungsverfahren ist von der Deutschen Bundespost noch nicht veröffentlicht worden.

Class B Notices
The following Class B statements apply to model 9111-520 (stand-alone version), 9131-52A (stand-alone
version), 7047-185 and the 9111-285.

Federal Communications Commission (FCC) statement

Note: This equipment has been tested and found to comply with the limits for a class B digital device,
pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against
harmful interference in a residential installation. This equipment generates, uses, and can radiate radio
frequency energy and, if not installed and used in accordance with the instructions, may cause harmful
interference to radio communications. However, there is no guarantee that interference will not occur in a
particular installation. If this equipment does cause harmful interference to radio or television reception,
which can be determined by turning the equipment off and on, the user is encouraged to try to correct
the interference by one or more of the following measures:
v Reorient or relocate the receiving antenna.
v Increase the separation between the equipment and receiver.

Appendix. Notices 843

v Connect the equipment into an outlet on a circuit different from that to which the receiver is
connected.
v Consult an IBM authorized dealer or service representative for help.

Properly shielded and grounded cables and connectors must be used in order to meet FCC emission
limits. Proper cables and connectors are available from IBM authorized dealers. IBM is not responsible for
any radio or television interference caused by using other than recommended cables or connectors or by
unauthorized changes or modifications to this equipment. Unauthorized changes or modifications could
void the user’s authority to operate the equipment.

This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions:
(1) this device may not cause harmful interferences, and (2) this device must accept any interferences
received, including interference that may cause undesired operation.

Industry Canada Compliance Statement

This Class B digital apparatus complies with Canadian ICES-003.

Avis de conformité à la réglementation d’Industrie Canada

Cet appareil numérique de la classe B est conforme à la norme NMB-003 du Canada.

European Community Compliance Statement

This product is in conformity with the protection requirements of EC Council Directive 89/336/EEC on
the approximation of the laws of the Member States relating to electromagnetic compatibility. IBM cannot
accept responsibility for any failure to satisfy the protection requirements resulting from a
non-recommended modification of the product, including the fitting of non-IBM option cards.

This product has been tested and found to comply with the limits for Class B Information Technology
Equipment according to CISPR 22 / European Standard EN 55022. The limits for Class B equipment were
derived for typical residential environments to provide reasonable protection against interference with
licensed communication devices.

Properly shielded and grounded cables and connectors must be used in order to reduce the potential for
causing interference to radio and TV communications and to other electrical or electronic equipment.
Such cables and connectors are available from IBM authorized dealers. IBM cannot accept responsibility
for an interference caused by using other than recommended cables and connectors.

VCCI Statement - Japan

The following is a summary of the VCCI Japanese statement in the box above.

This is a Class B product based on the standard of the Voluntary Control Council for Interference by
Information Technology Equipment (VCCI). If this equipment is used in a domestic environment, radio
disturbance may arise. When such trouble occurs, the user may be required to take corrective actions.

IBM Taiwan Product Service Contact Information

844 System i® and System p®: Reference codes

Electromagnetic Interference (EMI) Statement - Korea

Radio Protection for Germany

Dieses Gerät ist berechtigt in Übereinstimmung mit Dem deutschen EMVG vom 9.Nov.92 das
EG–Konformitätszeichen zu führen.

Der Aussteller der Konformitätserklärung ist die IBM Germany.

Dieses Gerät erfüllt die Bedingungen der EN 55022 Klasse B. Für diese von Geräten gilt folgende
Bestimmung nach dem EMVG:

(Auszug aus dem EMVG vom 9.Nov.92, Para.3, Abs.4)

Hinweis

Dieses Genehmigungsverfahren ist von der Deutschen Bundespost noch nicht veröffentlicht worden.

Terms and conditions

Permissions for the use of these publications is granted subject to the following terms and conditions.

Personal Use: You may reproduce these publications for your personal, noncommercial use provided that
all proprietary notices are preserved. You may not distribute, display or make derivative works of these
publications, or any portion thereof, without the express consent of the manufacturer.

Commercial Use: You may reproduce, distribute and display these publications solely within your
enterprise provided that all proprietary notices are preserved. You may not make derivative works of
these publications, or reproduce, distribute or display these publications or any portion thereof outside
your enterprise, without the express consent of the manufacturer.

Except as expressly granted in this permission, no other permissions, licenses or rights are granted, either
express or implied, to the publications or any data, software or other intellectual property contained
therein.

Appendix. Notices 845

The manufacturer reserves the right to withdraw the permissions granted herein whenever, in its
discretion, the use of the publications is detrimental to its interest or, as determined by the manufacturer,
the above instructions are not being properly followed.

You may not download, export or re-export this information except in full compliance with all applicable
laws and regulations, including all United States export laws and regulations.

THE MANUFACTURER MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE

PUBLICATIONS. THESE PUBLICATIONS ARE PROVIDED ″AS-IS″ AND WITHOUT WARRANTY OF
ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED
WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR
PURPOSE.

Product recycling and disposal

This unit must be recycled or discarded according to applicable local and national regulations. IBM
encourages owners of information technology (IT) equipment to responsibly recycle their equipment
when it is no longer needed. IBM offers a variety of product return programs and services in several
countries to assist equipment owners in recycling their IT products. Information on IBM product
recycling offerings can be found on IBM’s Internet site at http://www.ibm.com/ibm/environment/
products/prp.shtml.

Note: This mark applies only to countries within the European Union (EU) and Norway.

Appliances are labeled in accordance with European Directive 2002/96/EC concerning waste electrical
and electronic equipment (WEEE). The Directive determines the framework for the return and recycling
of used appliances as applicable throughout the European Union. This label is applied to various
products to indicate that the product is not to be thrown away, but rather reclaimed upon end of life per
this Directive.

In accordance with the European WEEE Directive, electrical and electronic equipment (EEE) is to be
collected separately and to be reused, recycled, or recovered at end of life. Users of EEE with the WEEE
marking per Annex IV of the WEEE Directive, as shown above, must not dispose of end of life EEE as
unsorted municipal waste, but use the collection framework available to customers for the return,
recycling, and recovery of WEEE. Customer participation is important to minimize any potential effects of
EEE on the environment and human health due to the potential presence of hazardous substances in EEE.
For proper collection and treatment, contact your local IBM representative.

Battery return program

This product may contain sealed lead acid, nickel cadmium, nickel metal hydride, lithium, or lithium ion
battery. Consult your user manual or service manual for specific battery information. The battery must be
recycled or disposed of properly. Recycling facilities may not be available in your area. For information
on disposal of batteries outside the United States, go to http://www.ibm.com/ibm/environment/
products/batteryrecycle.shtml or contact your local waste disposal facility.

In the United States, IBM has established a return process for reuse, recycling, or proper disposal of used
IBM sealed lead acid, nickel cadmium, nickel metal hydride, and other battery packs from IBM

846 System i® and System p®: Reference codes

Equipment. For information on proper disposal of these batteries, contact IBM at 1-800-426-4333. Please
have the IBM part number listed on the battery available prior to your call.

For Taiwan: Please recycle batteries.

IBM Cryptographic Coprocessor Card Return Program

The following information applies only for systems originally sold prior to July 1, 2006:

This machine may contain an optional feature, the cryptographic coprocessor card, which includes a
polyurethane material that contains mercury. Please follow local ordinances or regulations for disposal of
this card. IBM has established a return program for certain IBM Cryptographic Coprocessor Cards. More
information can be found at http://www.ibm.com/ibm/environment/products/prp.shtml.

Appendix. Notices 847

848 System i® and System p®: Reference codes

Printed in USA

Personal Auto Declaration: Policy Premium Total $1,314.00
No ratings yet
Personal Auto Declaration: Policy Premium Total $1,314.00
2 pages
Bluestone Puppy Application
No ratings yet
Bluestone Puppy Application
3 pages
Questions & Answers: Cabin Crew Interview
83% (6)
Questions & Answers: Cabin Crew Interview
12 pages
HP 3PAR StoreServ 7000 Storage Service Guide
No ratings yet
HP 3PAR StoreServ 7000 Storage Service Guide
165 pages
Xtremio Oce - 1
No ratings yet
Xtremio Oce - 1
12 pages
Centera Guide
No ratings yet
Centera Guide
12 pages
Codigos Paineis HMC
No ratings yet
Codigos Paineis HMC
524 pages
Servertroubleshootingguide en PDF
No ratings yet
Servertroubleshootingguide en PDF
132 pages
HP RX4640 CPU Upgrade Guide
No ratings yet
HP RX4640 CPU Upgrade Guide
90 pages
V7000 Unified Problem Determination Guide 04
No ratings yet
V7000 Unified Problem Determination Guide 04
314 pages
Nx4 Hardware Overview and Installation
No ratings yet
Nx4 Hardware Overview and Installation
48 pages
NetApp Hardware Universe 2013
No ratings yet
NetApp Hardware Universe 2013
1 page
Docu61872 VNXe1600 Drive Support Matrix
No ratings yet
Docu61872 VNXe1600 Drive Support Matrix
6 pages
HP Superdome 2 Partitioning Administrator Guide (5900-2540, December 2012) PDF
No ratings yet
HP Superdome 2 Partitioning Administrator Guide (5900-2540, December 2012) PDF
126 pages
How To Identify If A Boot Flash Drive Has Failed On NL400
No ratings yet
How To Identify If A Boot Flash Drive Has Failed On NL400
3 pages
HP Integrity Superdome 2
No ratings yet
HP Integrity Superdome 2
29 pages
Docu42949 - All VNX CLARiiON Celerra Storage Systems Disk and FLARE OE Matrices
No ratings yet
Docu42949 - All VNX CLARiiON Celerra Storage Systems Disk and FLARE OE Matrices
142 pages
EMC Centera 4.0 GlobalServices Release Notes Rev.a37
No ratings yet
EMC Centera 4.0 GlobalServices Release Notes Rev.a37
94 pages
EMC VNXe1000 SeriesVNXe1600 Hardware Information Guide
No ratings yet
EMC VNXe1000 SeriesVNXe1600 Hardware Information Guide
52 pages
VNX e Unisphere Command Line Guide 302-000-194
No ratings yet
VNX e Unisphere Command Line Guide 302-000-194
312 pages
x3100 m5 Type 5457
No ratings yet
x3100 m5 Type 5457
688 pages
PD and Service Guide Ga32092306
No ratings yet
PD and Service Guide Ga32092306
366 pages
Docu71060 XtremIO XIOS 4.0.2, 4.0.4, and 4.0.10 With XMS 4.2.0 Storage Array RESTful API Guide
100% (2)
Docu71060 XtremIO XIOS 4.0.2, 4.0.4, and 4.0.10 With XMS 4.2.0 Storage Array RESTful API Guide
359 pages
Iseries 5.2 SRC's
No ratings yet
Iseries 5.2 SRC's
308 pages
Hitachi Virtual Storage Platform G700
No ratings yet
Hitachi Virtual Storage Platform G700
127 pages
Eternus Dx60 S2: Support and Maintenance
No ratings yet
Eternus Dx60 S2: Support and Maintenance
54 pages
7026 Enterprise Server Model M80 Model 6M1 Service Guide
No ratings yet
7026 Enterprise Server Model M80 Model 6M1 Service Guide
621 pages
Compellent Storage Center 4.5 User Guide
No ratings yet
Compellent Storage Center 4.5 User Guide
372 pages
Compellent Enterprise Manager Administrators Guide
No ratings yet
Compellent Enterprise Manager Administrators Guide
436 pages
VNVNX5200,-VNX5400,-VNX5600-VNX5800,-VNX7600-and-VNX8000-Storage-Systems-DiskX5200, VNX5400, VNX5600 VNX5800, VNX7600 and VNX8000 Storage Systems Disk and OE Matrix
No ratings yet
VNVNX5200,-VNX5400,-VNX5600-VNX5800,-VNX7600-and-VNX8000-Storage-Systems-DiskX5200, VNX5400, VNX5600 VNX5800, VNX7600 and VNX8000 Storage Systems Disk and OE Matrix
13 pages
VNX5500 Hardware Information Guide
No ratings yet
VNX5500 Hardware Information Guide
114 pages
SG 248162
No ratings yet
SG 248162
744 pages
Eternus dx100 s4 PDF
No ratings yet
Eternus dx100 s4 PDF
122 pages
VNX5700 Hardware Information Guide
100% (2)
VNX5700 Hardware Information Guide
108 pages
Data Domain - DD OS Software Versions - Dell US
No ratings yet
Data Domain - DD OS Software Versions - Dell US
3 pages
A - VNXCapacityCalculator
No ratings yet
A - VNXCapacityCalculator
11 pages
N-Series NetApp Net Apps Drive Part Numbers
No ratings yet
N-Series NetApp Net Apps Drive Part Numbers
3 pages
Docu59139 Isilon Drive Firmware Package 1.11 Release Notes
100% (1)
Docu59139 Isilon Drive Firmware Package 1.11 Release Notes
12 pages
HP StorageWorks MSL Library Extender User
No ratings yet
HP StorageWorks MSL Library Extender User
96 pages
Troubleshooting, Recovery, and Maintenance Guide: IBM Storwize V7000
No ratings yet
Troubleshooting, Recovery, and Maintenance Guide: IBM Storwize V7000
172 pages
Qauntum FRU Y Trayrobot Scalar I40 I80 RevA
No ratings yet
Qauntum FRU Y Trayrobot Scalar I40 I80 RevA
26 pages
ECS - ECS Miscellaneous How To Service Procedures-ECS Troubleshooting Procedures
100% (1)
ECS - ECS Miscellaneous How To Service Procedures-ECS Troubleshooting Procedures
87 pages
Storage Disk Drive Replacement PDF
No ratings yet
Storage Disk Drive Replacement PDF
7 pages
AMS 2300 mode switch
No ratings yet
AMS 2300 mode switch
4 pages
Lenovo Storage V3700 V2 and V3700 V2 XP: Product Guide
No ratings yet
Lenovo Storage V3700 V2 and V3700 V2 XP: Product Guide
29 pages
Nexsan RAID Storage User Manual v3 8
100% (1)
Nexsan RAID Storage User Manual v3 8
220 pages
HP - rx2620 Service Guide
No ratings yet
HP - rx2620 Service Guide
177 pages
Isilion X200 Instalation Guide
No ratings yet
Isilion X200 Instalation Guide
14 pages
TS3500-Planning Guide PDF
100% (1)
TS3500-Planning Guide PDF
261 pages
Vnxe Service Commands
No ratings yet
Vnxe Service Commands
69 pages
XIV - CLI Details
No ratings yet
XIV - CLI Details
750 pages
06 Add
No ratings yet
06 Add
190 pages
Connectrix - Brocade Departmental Firmware Upgrade Procedures-DS-6520B
No ratings yet
Connectrix - Brocade Departmental Firmware Upgrade Procedures-DS-6520B
18 pages
Vplex P Hardware Reference v4 PDF
No ratings yet
Vplex P Hardware Reference v4 PDF
78 pages
Field Installation Guide-V2 1 Foundation
No ratings yet
Field Installation Guide-V2 1 Foundation
61 pages
SC4020 HardwareOwnersManual
No ratings yet
SC4020 HardwareOwnersManual
35 pages
VMware Horizon View Essentials
From Everand
VMware Horizon View Essentials
Peter von Oven
No ratings yet
Codigos Error AIX - Sa76-0089
0% (1)
Codigos Error AIX - Sa76-0089
586 pages
Códigos de Erro P720
No ratings yet
Códigos de Erro P720
1,322 pages
830_840_SB2_SB3_Problem_analysis_Repair_Parts
No ratings yet
830_840_SB2_SB3_Problem_analysis_Repair_Parts
1,000 pages
170 250 Problem Analysis Repair Parts
No ratings yet
170 250 Problem Analysis Repair Parts
577 pages
Model830 FRU Replacement and Service PDF
No ratings yet
Model830 FRU Replacement and Service PDF
857 pages
Smart Card Applications: Design models for using and programming smart cards
From Everand
Smart Card Applications: Design models for using and programming smart cards
Wolfgang Rankl
No ratings yet
Schaffler 6308
No ratings yet
Schaffler 6308
1 page
This Pointer in C++
No ratings yet
This Pointer in C++
2 pages
The Limiting Factors of Photosynthesis
No ratings yet
The Limiting Factors of Photosynthesis
2 pages
Completed Business Environment Assignment 2-Muleba Matafwali
No ratings yet
Completed Business Environment Assignment 2-Muleba Matafwali
9 pages
Short Prayer Before Thesis Defense
100% (3)
Short Prayer Before Thesis Defense
4 pages
Advisory2019 09 - LCDS 319
No ratings yet
Advisory2019 09 - LCDS 319
5 pages
Module - 5 Pricing and Distribution Strategy: Dr. Jerry John Assistant Professor KCM
No ratings yet
Module - 5 Pricing and Distribution Strategy: Dr. Jerry John Assistant Professor KCM
25 pages
KVR Price List: SL - No Particulars Units
No ratings yet
KVR Price List: SL - No Particulars Units
32 pages
Uge 1 Test 3 Version 1
No ratings yet
Uge 1 Test 3 Version 1
8 pages
Beckhoff TwinCat
No ratings yet
Beckhoff TwinCat
34 pages
Selecting Materials in Product Design (Thesis) PDF
No ratings yet
Selecting Materials in Product Design (Thesis) PDF
240 pages
Safety Data Sheet Glass Wool
No ratings yet
Safety Data Sheet Glass Wool
3 pages
Importance of Cyber Security: Rajesh Kumar Goutam
No ratings yet
Importance of Cyber Security: Rajesh Kumar Goutam
4 pages
Motivation Letter
No ratings yet
Motivation Letter
1 page
Wacker - RT82 - Trench - Roller - SPECS
No ratings yet
Wacker - RT82 - Trench - Roller - SPECS
2 pages
Operation Manual For The A7000 Series: 2. Mounting Method
No ratings yet
Operation Manual For The A7000 Series: 2. Mounting Method
12 pages
Vav SVX08L en - 05132019
No ratings yet
Vav SVX08L en - 05132019
72 pages
Experiment No. 6 Pit Furnace Melting Practice: Aim Theory
No ratings yet
Experiment No. 6 Pit Furnace Melting Practice: Aim Theory
3 pages
Deliverables April 2019
No ratings yet
Deliverables April 2019
2 pages
Vertimec Label - 50772-0801
No ratings yet
Vertimec Label - 50772-0801
7 pages
Luminaire Data Sheet: See Our Luminaire Catalog For An Image of The Luminaire. Luminous Emittance 1
No ratings yet
Luminaire Data Sheet: See Our Luminaire Catalog For An Image of The Luminaire. Luminous Emittance 1
12 pages
Assignment - Lab Accidents and Precautions
No ratings yet
Assignment - Lab Accidents and Precautions
6 pages
CARPO V CHUA DY
No ratings yet
CARPO V CHUA DY
2 pages
Ticket To Bollywood
0% (1)
Ticket To Bollywood
2 pages
Patanjali 160117060727
No ratings yet
Patanjali 160117060727
22 pages
PERS Industry Valuations: MAMA Conference, Orlando Florida
100% (2)
PERS Industry Valuations: MAMA Conference, Orlando Florida
25 pages
MODULE 3.2 Principles of Police Organization
No ratings yet
MODULE 3.2 Principles of Police Organization
2 pages