Table of Contents
Advertisement
Intermittent Problems
v Product Activity Log information can provide time and device relationships.
v Information on environmental conditions when the failure occurred can be
Types of Intermittent Problems
There are four major types of intermittent problems:
v Code (PTFs)
v Configuration
v Environment
v Intermittent hardware failure
Note: If you suspect that an intermittent problem is occurring, increase the log
General Intermittent Problem Checklist
The following steps have been successful in correcting intermittent problems on
the AS/400 system. Performing these steps removes the known causes of most
intermittent problems. Therefore, it is important that you perform all of these
steps. Some customers have a high availability requirement for the AS/400 system
(such as 24 hours a day, 7 days a week). It is very important that you perform all
the steps in this checklist to ensure that the system can meet this availability
requirement.
16
iSeries Model 830, 840, SB2, and SB3 Problem Analysis, Repair and Parts V5R1
helpful (for example, an electrical storm occurring when the failure occurred).
– Licensed Internal Code
– OS/400 (operating system)
– Licensed program products
– Other application software
– Non-supported hardware that is used on the system
– Non-supported system configurations
– Non-supported communication networks
– Model and feature upgrades that are not performed correctly
– Moving of down-level hardware from other systems to the AS/400 system
– Incorrectly configured or incorrectly cabled devices
– Power line disturbance–for example, reduced voltage (sag), a pulse, a surge,
or total loss of voltage on the incoming AC voltage line
– Power line transient–for example, a lightning strike
– Electrical noise (constant or intermittent)
– Defective grounding or a ground potential difference
– Mechanical vibration
sizes to the largest sizes possible. Select the Product activity log option on the
Start a Service Tool display (see "Product Activity Log" in the iSeries Service
Functions information).
1. Discuss the problem with the customer. Look for the following symptoms:
v An SRC or reference code that goes away when you power off the system,
then power on the system.
v Repeated failure patterns that you cannot explain. For example, the problem
occurs at the same time of day or on the same day of the week. Look for
some type of pattern.
v Failures that started after system installation
v Failures that occurred during customer usage.
- Quick Links:
- Table of Contents
Hide quick links:
Advertisement
Table of Contents
