The DISX utility comprises of software in the 'master'
virtual machine (DISXX) and each 'slave' virtual machine (DISXXnn).The 'master' virtual machine controls the testing process. The 'slave' machines actually test the DASD - one slave machine tests one device.
The 'master' verifies
the input parameters and autologs a 'slave' machine for each device to be tested, to a maximum of the number of processes specified. The maximum number of processes depends on the number of 'slave' virtual machines defined in the VM
directory.
The 'slave' machine will test the DASD. Each test consists of a format cycle followed by at least one test cycle. The format cycle (which is only performed once) writes a 47476-byte record on every track of the
device and then reads every record back. The user may specify how many subsequent test cycles the 'slave' machine is to perform. Each cycle writes records of various sizes randomly over the device and reads the records back to
verify what has been written.
The user may also specify an error threshold, which if reached, terminates the test for that device. The error threshold resets itself after the format cycle.
Once the test for a device has been
completed, a message log is sent the 'master'. The 'slave' machine logs itself off ready to be used for the next device to be tested. The message log contains the start and end times of each cycle performed together with notice
of any errors found. These include the appropriate sense bytes, if available.
The 'master' machine will remain active until all the devices specified have been tested. Message log files for each device tested may be viewed
and/or printed from the 'master' machine.
During processing, PFkeys can be used to display the status of the tests, stop the test immediately, or stop the test on the completion of the current active cycle.