The HOTX driver tests the TPF DASD support by creating a 'hot record' (default using #HOTREC) to blast channels and to test cache.
The instances created by the HOTX driver stress the DASD system by repeatedly finding and filing the "hot record." The first time it runs, it allocates a 4K frame on the system heap for the subsystem to store the information which is 8 bytes for each entry containing the flags (run, stat, stop, ebrout) of all ordinals (0x00-0x13) of all I-streams (up to 24).
|HOTx Driver Readme (Text)||English||7302|
|HOTx Driver Readme (PDF)||English||18256|
|HOTX User Guide||English||33836|
|Download||RELEASE DATE||LANGUAGE||SIZE(Bytes)||Download Options|
|HOTX Driver Module||26 Mar 2012||English||53376||HTTP|