How To Analyze The Intermittent Problem; Intermittent Symptoms - IBM iSeries Series Hardware Problem Analysis And Isolation

12. Was a manufacturing engineering service (MES), system upgrade, feature, or any other field bill of
material or feature field bill of material installed just before the intermittent problems started
occurring?
v No: Continue with the next step.
v Yes: Review the installation instructions to ensure that each step was performed correctly. Then
continue with the next step of this procedure.
13. Is the problem associated with a storage device?
v No: Continue with the next step.
v Yes: Ensure that the customer is using the correct storage device cleaning procedures and good
storage media. Then continue with the next step of this procedure.
14. Ensure that all the items in Preventive maintenance (PM) are being performed regularly.
Perform the following to help prevent intermittent thermal checks:
v Ensure that the AMDs on all disk units, tape units, and power supplies are working.
v Exchange all air filters as recommended.
15. If necessary, review the intermittent problems with your next level of support and installation planning
representative.
Ensure that all installation planning checks were made on the system. Because external conditions
are constantly changing, the site may need to be checked again.
This ends the procedure.

How to analyze the intermittent problem

For use by authorized service providers.
Use this procedure to begin analyzing an intermittent problem.
1. Is a reference code associated with the intermittent problem?
v No: Continue with the next step.
v Yes: Go to the System reference code list, and find the reference code. If the actions in the system
reference code tables do not correct the intermittent problem, return here and continue with the next
step.
2. Is a symptom associated with the intermittent problem?
v No: Continue with the next step.
v Yes: Go to "Intermittent symptoms." If it does not correct the intermittent problem, return here and
continue with the next step.
3. Go to "Failing area INT-PIPs" on page 17. If it does not correct the intermittent problem, return here
and continue with the next step.
4. Send the data you have collected to your next level of support so that an Authorized Program Analysis
Report (APAR) or a Licensed Internal Code Trouble Report (LICTR) can be written.
This ends the procedure.

Intermittent symptoms

For use by authorized service providers.
Use the table below to find the symptom and description of the intermittent problem. Then perform the
corresponding intermittent problem isolation procedures (INT-PIPs) (which begin at "Intermittent PIPs" on
page 108).
Although an INT-PIP may correct the intermittent problem, use your best judgment to determine if you
should perform the remainder of the INT-PIPs shown for the symptom.
Table 1. Intermittent symptoms
16
iSeries: iSeries Server 270, 800, 810, 820, 825, 830, 840, 870, 890, SB2, and SB3 Hardware Problem Analysis and Isolation