Examples: Missing or non-reporting system bus resources

The following examples show some of the reasons why the system might show missing resources and corresponding actions to take.

• Residual resource names after a reconfiguration of resources. When resources are removed from a partition, there are two options:
  • 1=Remove leaves the resource names (usually when switching resources across partitions temporarily. This option is used when the customer intends to switch the resources back to the original partition sometime in the future and wants to use the same resource names when the future switch occurs). If this option is selected, the resource names will show as non-reporting in the partition that they were removed from following the next IPL of that partition.
  • 2=Remove and clear hardware resource(s) removes the resource names (when permanently moving or removing the resource).

  Corrective action: Work with the customer to understand why the option to leave resource names was selected. These resources should be left as is if the customer intends to switch the resource back to the partition from which they were removed. If they are removed and the resource is switched back to that partition, a new resource name is created and the resource name is incremented. This will cause problems with the device descriptor that uses this resource; for example, TAP01 being used by multiple partitions.

• The resource has actually failed or has been removed from the system.

  Corrective action: Find out why each missing or non-reporting resource exists. Follow normal problem-determination procedures including analyzing the service action log.