Attempt to find the error code that originally sent you to the “Checkpoint and Error Code Index” on page162 table.1. If you can not find the error code in the service processor error log, start with the error code at thebottom of the list. Proceed to 3 below.2. If you can find the error code in the service processor error log, observe the time stamps and look fora group of failures that happened within minutes prior to this error code. In this group, start at the errorcode with the earliest time stamp. Proceed to 3.3. Examine the list of error codes you obtained from 1 or 2 and look for any of the form 4xxB xxxx.Can you find any error codes of the form 4xxB xxxx?No Proceed to step 6.Yes Proceed to step 4.4. Do any of the error codes of the form 4xxB xxxx have the same first two characters on the left as thefirst two characters on the left of the error code that sent you to the MAP?No Proceed to step 6.Yes Proceed to step 5.5. Adjust the order of the list of error codes you obtained from steps 1 or 2 by placing the error codes ofthe form 4xxB xxxx with the same first two characters as the error code that sent you to this MAP onthe bottom of the list. Start step 6 at the bottom of the adjusted list of error codes. Proceed to step 6.6. To get a list of possible FRUs, select the detail screen for each error code. Record the listed locationcodes and their order.Note: If the error code that results from this procedure is 406x 0EA0, 406x 0EA1, 406x 0EA2, or 406x0EA4, do not go back to the “Checkpoint and Error Code Index” on page 162 with this errorcode. Look for a hardware error in the service processor error log of the form 450x yyyy, 460xyyyy, or 4B2x yyyy that occurred just prior to the 406x 0EAy error. Use this hardware error codeinstead when returning to the “Checkpoint and Error Code Index” on page 162.Note: If there are no hardware error codes in the form 450x yyyy, 460x yyyy, or 4B2x yyyy thatoccurred just prior to the 406x 0EAy error, look for the last firmware checkpoint of the form Exxxbefore the 406x 0EAy error. (Ignore checkpoints that do not have the form Exxx.) Use thischeckpoint when returning to the Checkpoints and Error Codes Index.Return to the step in the “Checkpoint and Error Code Index” on page 162 table immediately after thestep that sent you to this ″Confirming Initial Error Code″ procedure to perform the listed repair actions.If the repair actions for an error code are ineffective, continue to work upward through this group oferror codes (which is forward in time from the earliest time stamp to the latest) until either the problemis fixed, you reach the error code that was first reported, or you are at the top of the list.Four-Character CheckpointsFour-character progress codes and checkpoints in the form 8xxx, 9xxx, Axxx, Bxxx, and Exxx are listed in“Firmware Checkpoints” on page 140. If you have a four-character code that begins with any characterother than 8, 9, A, B, or E, refer to the RS/6000 Eserver pSeries Diagnostic Information for Multiple BusSystems.Replacing the Operator PanelLicensed programs frequently rely on system information that is stored in the vital product data (VPD)module on the operator panel. If you replace the operator panel, the system VPD information (for examplethe machine type and serial number) is restored to the new VPD module in the operator panel.160 EserverpSeries 615 Service Guide
