iCan Blog Archive

As I have written in the past few blogs, Navigator for i has been enhanced significantly with the latest updates. Read the Navigator for i EnhancementsIFS Enhancements to Navigator for i, and Performance Data Investigator – Better than Ever blogs if you haven’t read them already.

This week, I’ll continue the review of Navigator enhancements by sharing a few details on one of the enhancements to Disk Management.

As noted last week, the cover letter for PTF SI47573 has a brief summary of the enhancements that were made. For Disk Management, this summary is:

  • Disk Management
    • The user access restrictions on Disk Management has been removed. In previous service packs, in order to use the isk Management features on IBM Navigator for i, the user/password from XPF and Service tools must be equal and uppercase. In this service pack, we removed the restriction and allow the user to have a different user and password for XPF and Service Tools. 
  • Rebuild disk unit data 
    • Capability for a user to rebuild data on a failed disk unit in a parity set.

This blog article will review the second item – rebuild disk unit data.

In the latest service pack of IBM Navigator for i, IBM added the “Rebuild Data” action for the disk units list. This action allows the ability to rebuild data on failed disk units belonging to a failed parity set. This allows the user to easily recover from the failure. 

IBM i service tools, “Work with Disk Units” has the “Work with Disk Unit Recovery” function to rebuild device parity disk unit data. The rebuild functionality is now part of the Web Navigator interface starting with the latest service pack.


Figure 1: New Action, Rebuild Data 


Figure 2: Rebuild data on a disk unit confirmation panel


Figure 3: The disk unit list after rebuilding data on a disk unit.

I’d like to thank Ting ting Sun(孙婷婷)for writing the information regarding the Disk Management enhancements this week. Ting ting Sun(孙婷婷)is part of the IBM i development team in the China Systems and Technology Lab in Beijing.

This blog post was originally published on IBMSystemsMag.com and is reproduced here by permission of IBM Systems Media.