Here are the steps for this cause code:
(looks like you can figure out which unit it thinks is missing (step 3)
and make sure it's seated properly)
(based on this, also looks like you may need to do step 11, which
involves needing a console)
LIC pips
If the Cause Code is:
0002: Disk units are missing from the disk configuration.
Data from the control panel can be used to find information about the
missing disk unit. See "Hardware SRC Formats" in the AS/400 Service
Functions.
1. Did you enter this procedure because all the devices listed on the
Display Missing Units display (reached from the Disk Configuration
Error Report or the Disk Configuration Warning Report display) have a
reference code of 0000?
No Yes
| Go to step 20 of this procedure.
2. Have you installed a new disk enclosure in a disk unit and not
restored the data to the disk unit?
No Yes
| Ignore SRC A600 5090.
Continue with the disk unit exchange recovery procedure (see
"Disk Service
Support" in Chapter 7, "Recovery Procedures" on page 7-1).
This ends the procedure.
3. Use the function 11 through 18 information recorded on the Problem
Summary Form to determine the disk unit that stopped communicating with
the system:
· Function 14 four rightmost characters contain the IOP direct select
address.
· Function 16 contains the disk unit type, level and model number.
· Function 17 contains the disk unit serial number.
Note: For 9337 Disk Units, the 5 rightmost characters contain the disk
unit serial number.
Are the problem disk units 660x or 671x Disk Units?
No Yes
| Go to step 5 of this procedure.
4. Attempt to get all devices attached to the MSIOP to Ready status by
performing the following:
a. The MSIOP address (MSIOP Direct Select Address) to use is the four
rightmost characters of function 14.
b. Verify the following and correct if necessary before continuing with
step 11 of this procedure:
· All cable connections are made correctly and are tight.
· All storage devices have the correct signal bus address, as
indicated in the system configura-
tion list.
Chapter 4. Problem Isolation Procedures (PIPs) 4-65
LIC pips
- All storage devices are powered on and ready.
5. Did you enter this procedure because there was an entry in the
Service Action Log which has the reference code B6005090?
Yes No
| Go to step 11 of this procedure.
6. Are customer jobs running on the system now?
Yes No
| Attention: Ensure that the customer is not running any jobs
before continuing with this proce-
dure.
Go to step 11 of this procedure.
7. Perform the following:
a. Select System Service Tools (SST).
b. Select the Work with disk units option.
c. Select the Display disk configuration option.
d. Select the Display disk configuration status option.
Are any disk units missing from the configuration?
Note: Missing disk units are indicated by an asterisk (*).
This ends the procedure.
8. Do all of the disk units that are missing from the configuration
have a status of "Suspended"?
Yes No
Attention: Ensure that the customer is not running any jobs before
continuing with this proce-
dure.
Go to step 11 of this procedure.
9. Use the Service Action Log to determine if there are any entries for
the missing disk units (see "Using
the Service Action Log" on page 1-5).
Are there any entries in the Service Action Log for the missing disk
units that were logged since the
last IPL?
Yes No
3· Go to step 21 of this procedure.
10. Use the information in the Service Action Log and go to the SRC
information for the specific disk unit
in Chapter 2, "Unit Reference Codes" on page 2-1.
Perform the action indicated for the unit reference code.
This ends the procedure.
11. Select Manual mode and perform an IPL to DST (see "Dedicated
Service Tools (DST)" in the AS/400
Sen/ice Functions information).
Does the Disk Configuration Error Report or the Disk Configuration
Warning Report display appear?
4-66 AS/400 940x Models 600, 620, S10 and S20 Problem Analysis, Repair
and Parts V4R2
Post by KoohiisanWell, I brought it back up to get the error code, and if I cycle the
display to say "13-3" and hit Enter I get 0002.
And I don't know what kind of IOA this box has...at all! I'll post a
pic of the back and you can let me know, because I have no clue what I
should hook up to... :(
Post by b***@gmail.comI have a running 600 and, from the problem analysis manual for models
Select function 13 on the control panel and press the Enter key. The 8
characters of the SRC are displayed. The 4 leftmost characters are the
cause code.
Depending on the cause code (0001 to 0099) different actions are
performed but most do involve IPL to DST.
So you do need a console.
In my case, I use a PC running client access, connected with a special
serial cable to the first comm port on the 600; it's a little tricky to
configure a serial console. In your case, it may be easier to
borrow/buy a twinax terminal (or twinax emulation card for a PC) if
that's what the 600 was originally configured as.
Post by KoohiisanSo how would I reset the adapter?
I looked over the article on IBM per the prior post...but I have no
console so I can not get to DST...also, although I plugged a network
line into the network adapter on back (#2838) I never showed
connectivity on my router and could not get into the box via Operations
Navigator. What can I do? I really don't want a twinax 5250 terminal
laying around just for these rare console needs if I can get by with
something via network. Ideas?
Post by jackoHere is what I found online, hope it helps.
The DASD I/O Adapter could not be configured correctly after
the IPL. I/O Processor microcode was changed to reset the
adapter and retry the configuration
Post by BradKoohiisan
It could be the removal of the disk, it will depend on whether the disk
that was taken from your system was removed using the DST functions or
if it was just removed.
IBM would recommend you run their Published procedure LIC-PIP11 to
diagnose the fault. You can find this and more details of the 5090
error at the following site (just search for 5090)
http://publib.boulder.ibm.com/iseries/v5r2/ic2924/index.htm?info/rzar7/rzar7b6xx.htm
Assuming the worst, that you've either had the disk incorrectly
removed, used and replaced or that you've had a disk fail in transit
with not disk protection. Then you are going to have to reload OS/400
on your system at home.
But I'd start with LIC-PIP11 and check for sure.
Good luck, Brad.