Disk Wipe of iSeries

I'm looking to find a way to clear all disks on a iseries 170 running V5R3. This clear must rewrite all data to biniar 0's or 1's. Thanks!

Answer Wiki

Thanks. We'll let you know when a new response is added.

You have already 1 and 0 on your Iseries disks and of course.

The Iseries are not little games as some PC. They use a lot of complex technologies as Mirroring and Raid 5 to manage there disks. So let them do it.

The way to clean the Iseries storage is :
1) Delete unused files
2) Reorganize files by files (RGZPFM command)
3) ….

See RedBooks or IBM publication on UDB for that.


Discuss This Question: 2  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Ayahel1
    You can IPL in manual mode from the I_BASE CD to the IPL setup screen on the console and select "Initialize the system and install the operating system". After the initialize part the disks are scratched with 0's and 1's
    0 pointsBadges:
  • TomLiotta
    The first question to ask is "How will anyone know if it was done?" In practical terms, once the drives are logically removed from the system image, the data is worthless. If you add the drive even back into the same system, it will be formatted before it's active. And if you try to add it to another kind of system (assuming the hardware is compatible), it's not only formatted, it's 'low-level' formatted. The actual map of sectors is changed because the sector sizes are different for AS/400s from other systems. In some real ways, the formatting possibly isn't always important because of the 'scatter loading' that the disk subsystem applies to objects. Extents of objects are placed across multiple disks. This scattering is kind of similar to how file extents may be scattered across a single Windows disk drive. Windows scattering is what you clean up by running defragmentation. But it's far less desirable due to the physical difference between single and multiple disk arms. So, an object that should be erased is already broken into parts across multiple disk drives. This makes the data useless (as an object) as long as the disks aren't kept in an integrated whole. When a disk is taken out of an AS/400, the logical processes that keep track of all object parts are disconnected from the disk -- the data no longer has an index. When a drive is physically put into another AS/400, the new system doesn't recognize the drive and doesn't have an index for it and is forced to format it to a known state -- essentially blanks. When the drive is put into a non-as/400 system, the 528-byte sector size can't be read; so, the whole surface must be formatted down to the actual sectors themselves. Overall, the harder question would be "How can I not destroy the info on the disks?" Except under military levels of security, the necessary reformatting might be done automatically simply by removing a couple drives from the logical storage pool, unplugging the drives from the system, swapping the drive positions, and then adding them back into the system disk configuration. There may be no need to look for extra functions. Maybe you can just follow basic directions to remove and add drives -- basic disk maintenance. Tom
    125,585 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: