Work with configuration data for logical partitions

Use DST and SST to clear, copy and update configuration data, to configure nonconfigured disk units, to clear nonreporting resources, to accept a disk unit as a load source, and to delete logical partitions on the server.

You may need to work with logical partition configuration data. Typically, you will need to do so in order to recover from hardware failures, to correct errors, or to perform maintenance after hardware movement.

The server maintains the configuration data for all logical partitions on the load source of each logical partition. The configuration data maintained on the primary partition is considered the master copy. Problems can occur when the configuration information on the primary partition and a secondary partition conflicts, or after you initialize disk units during an installation.

• Recover logical partition configuration data
  You can use this option to recover logical partition configuration data if one of your secondary partitions is running the i5/OS™ operating system. This procedure is part of a full server recovery.
• Save all configuration data
  You can use iSeries Navigator to save logical partition configuration data in a file on your computer. This function is used when all of the secondary partitions on your iSeries are running a guest operating system.
• Restore all configuration data
  You can use iSeries Navigator to restore all of your configuration data.
• Clear partition configuration data for logical partitions
  You can clear the configuration data for the topics.
• Update partition configuration data on all logical partitions
  You can update the configuration data for every active logical partition by copying it manually from the primary partition to all active logical partitions.
• Clear partition configuration data from nonconfigured disk units
  When you move disk units among logical partitions or servers, you may need to erase any old configuration data before the server can use the logical partition again.
• Clear nonreporting resources on logical partitions
  
• Accept a disk unit as load source for a logical partition
  
• Copy partition configuration data between IPL sources
  Your server may experience a disk read error of logical partition configuration data if you restart from the A or B IPL source, but not both
• Delete all of your logical partitions
  There may be a time when you need to erase all your logical partitions to make the server non-partitioned again.