![](/images/new-backgrounds/1142204/142204143x1.webp)
Command Specifications
media. When this is the case, a subsequent request for command support data may be successful.
c.CDB size
This field contains the number of bytes in the CDB for the operation code being queried, and the size of the "CDB Usage Data" field in the return data.
d.CDB usage data
This field contains information about the CDB for the operation code being queried. The first byte of the "CDB usage data" contains the operation code for the operation being queried. All bytes except the first byte of the "CDB usage data" contains a usage map for bits in the CDB for the operation code being queried.
The bits in the "Usage map" have a
Thus, the CDB usage bit map for Inquiry command for a device server that implements command support data but not vital product data is: 12h, 02h, FFh, 00h, 07h.
(7)VPD information
When "1" is specified in the "EVPD" bits of the CDB, the VPD information described below is transferred to the INIT by this command. The INIT specifies the type of VPD information required in the "Page code" field of the CDB. The type of VPD information supported by the IDD and its page code number are as shown below.
Page Code Page (Hex) | Function |
|
|
00 | Page code list of supported VPD information |
|
|
80 | Device serial number |
|
|
C0 | Operation mode |
|
|
Furthermore, if page codes other than those shown above (VPD information that is not supported by the IDD) are specified in the CDB, that command is terminated with a CHECK CONDITION status (ILLEGAL REQUEST [=5] / Invalid field in CBD
The format and contents of each type of VPD information are shown below.
a.Page code list
This VPD information reports the page code list of VPD information supported by the IDD. The format of this VPD information is shown in Figure 3.3.
3 - 10 |