Queued Commands using Developers Toolbox (DTB – API)
A new feature implemented in Developers Toolbox (DTB) allows you to specify that tests issue queued commands up to a specified queue depth.
As an example the code sequence below will execute a sequential write test on the device at HA 6, Target 0, LUN 0. The test will run for one minute, and will attempt to achieve a queue depth of 4.
VCSCSIPrepareForNewDiskTestSequence();
VCSCSIAddDiskDeviceToBeTested(6,0,0);
VCSCSISetQueueDepth(4);
VCSCSIAddDiskWriteTest_Time(1);
VCSCSIStartDiskTestSequence();
To see the actual queue depth achieved use BAM to capture the test I/O. The Queue Depth Meter will show you maximum and instantaneous queue depth. You can also use the Trace Performance Analysis and the I/O Statistics tab to see what queue depth was achieved.
Upgrade your old license for only $895! Ends April 30th!
For a limited time you can upgrade your old SCSItoolbox Suite to version 6.1.1 for the annual Performa price of $895.00! If your license is more than a year out of Performa coverage this offer will save you $1400.00! This upgrade will upgrade your old version of the SCSItoolbox Suite, even a new hardware key if your license is older than 5 years! To qualify for the offer you only need a valid serial number. If you’re ready to purchase go to the Performa product page online and complete the order form here: http://www.stbsuite.com/products/performa/
New! Tape motion tutorial walkthrough and movie.
We’ve added a new Tape motion tutorial available online here: http://www.scsitoolbox.com/Training/Videos/TapeMotion.wmv
SCSIToolbox provides an easy to use command center to completely control your tape drive. Simply right-click on a tape device in the device display and choose Motion/Data, or click the top-menu choice Tape->Commands->Motion/Data commands.
View full article with Screenshots
Ask Dr. SCSI – You don’t need BAM – or do you?
Q. You don’t need BAM – or do you?
A. After all, you’re just making a little test for a “known good” peripheral. But your test is hanging occasionally.
While capturing the test I/O using BAM you notice a flash of RED on the screen – a CHECK CONDITION. Your device is reporting that it is write protected Write protect Screenshot you check the device and find a defective intermittent write protect sensor!
You didn’t need BAM to write your test, but it saved you lots of troubleshooting time!
BAM-on!