(E332xxxx) Licensed Internal Code error codes

For use by service providers.

The Hardware Management Console generates E302xxxx error codes when it encounters a problem during an update of the firmware for the managed system.

If you do not find an SRC in the table that follows, contact your next level of support for assistance.
Notes:
  1. The SRCs on this page are from the Power Systems hardware documentation, and the Descriptions apply to a single CEC enclosure or I/O enclosure. The Action and Failing Item fields are modified as appropriate for DS8000® architecture and repair methods.
  2. SRCs missing from the following tables might be found on the Power Systems online documentation. You can use the SRC description as is to define the problem. Do not use the Action and Failing Item without contacting the next level of support first.
  3. To display the Power Systems hardware online documentation, go to the Web site http://www-01.ibm.com/support/knowledgecenter/.
    • In the IBM Systems Hardware Information right content pane, click POWER6 reference codes listing.
Table 1. (E332xxxx) Licensed Internal Code error codes
SRC Description/Action Failing Item
E3326601 The HMC failed to retrieve a platform system dump from the managed system. For details, refer to reference code B3036601 in (B3xxxxxx) Connection monitoring reference codes.  
E3326602 The HMC failed to retrieve a dump from the service processor. For details, refer to reference code B3036601 in (B3xxxxxx) Connection monitoring reference codes.  
E3326604 The HMC failed to retrieve a power subsystem dump from the managed system. For details, refer to reference code B3036604 in (B3xxxxxx) Connection monitoring reference codes  
E332FFFF This SRC occurs when the HMC has gathered javacore and heapdump data from a Java problem.

Problem determination: This SRC is informational. If there are no other symptoms, the serviceable event containing SRC E332FFFF can be closed. If E332FFFF is accompanied by hung processes (such as HMC WUI interface or TPCR), a reboot of the HMC will likely be needed. If further debug is needed, contact your next level of support prior to rebooting the HMC.