SCSI Verification Tests ****************************************** This is a preliminary program distributed for review and comment. It should not be represented as any "official" NBS test of SCSI conformance. The SCSI Verification Tests are C language programs which work with the Adaptec SDS-1 SCSI Development System, Revision A. They are invoked by the batch file ssdv.bat. The seperate programs are: NAME TESTS begin.c Before testing commands, this program allows the operator to set some initialization information and tailor the testing function. Then the system sends back some target parameters to the operator. arbitr.c Tests the ARBITRATION function for Direct-Access and/or Sequential-Access Devices. tuready.c Tests the TEST UNIT READY command for Direct-Access Device. (Note: Operator action is required to make the unit not ready. The best way to do this depends upon the device itself. Turning off power to the controller, however, won't work. Removing the power cable to the device may work, or removing the media may work.) mread.c Tests the Mandatory READ command for Direct-Access Devices. mwrite.c Tests the Mandatory WRITE command for Direct-Access Devices. eread.c Tests the Extended READ command for Direct-Access Devices. ewrite.c Tests the Extended WRITE command for Direct-Access Devices. sense.c Tests the REQUEST SENSE command for Direct-Access Devices. vverify.c Tests the VERIFY command for Direct-Access Devices. inquiry.c Tests the INQUIRY command for Direct-Access Devices. reserve.c Tests the RESERVE and RELEASE command for Direct-Access Devices. readcapa.c Tests the READ CAPACITY command for Direct-Access Devices. mreads.c Tests Mandatory READ command for Sequential-Access Devices. The final products of SCSI STANDARD VERIFICATION are a couple of reports: a Test Result Report and a Test Procedure Report. To get the reports, you must use two batch files: ssdv.bat and tp.bat. To generate the Test Result Report, enter: C>ssdv While executing, the screen will show the execution sequence of this batch file. After it has completed(when the DOS prompt appears), the Test Result Report can be printed out to the printer: C>print ssdv.tr Then to generate Test Procedure Report, enter: C>tp ssdv After it has completed, print out the Test Procedure Report by entering: C>print ssdv.tp NOTE: 1: These tests do not test every possible command, feature or combination of features. The tests basically assume a Direct Access Device which implements the Parity and Arbitration options and the Extended Command Set. Parity checking itself is not tested. A basic test of RESERVE and RELEASE is included, however many options, such as Extent Reservation and Queued Reservations are not tested. These are conformance tests, not performance tests, and all tests are based upon some requirements of X3.131-1986. Each program begins with on explaination of the specific requirements of X3.131-1986 to be tested. A partial test of Sequential Access Device is included; we expect to extend this in the future. 2: We have included both of the source programs and the executable programs. You can directly execute these programs or assemble these source programs and then execute them. In addition, we have included a Test Data Report(ssdv.tr) and a Test Procedure Report (ssdv.tp) which we have run here at NBS. You should delete these files before you test a new device. 3: It will take a long time to test READ CAPACITY command and Mandatory READ command for Sequential-Access Device. 4: After you interrupt executing test programs, you must delete *.tmp, *.liu, ssdv.tr or ssdv.tp before you restart the test programs. 5: If you have some suggestion for these tests or find something wrong in the programs, we'd very much like to know about it. Please make your comments or suggested corrections on a floppy and mail this to us. If you do make corrections to a program please be careful to clearly warn those corrections with appropriate comments. Our address is: William E. Burr National Bureau of Standards Building 225, Room A216 Gaithersburg, MD 20899