6.Command Specification | PERSISTENT RESERVE IN |
GENERATION: This field will contain a
Additional Length: This filed contains a counter of the number of bytes in the Reservation key list. If the allocation length specified by the PERSISTENT RESERVE IN command is not sufficient to contain the entire parameter list, then only the bytes from 0 to the maximum allowed allocation length will be sent to the application client. The incremental remaining bytes will be truncated, although the Additional Length field will still contain the actual number of bytes in the reservation key list without consideration of any truncation resulting from an insufficient allocation length. This will not be considered an error.
Reservation Key: The reservation key list contains the
The returned the parameter data provided in response to a PERSISTENT RESERVE IN command with the READ RESERVATION service action has the following format:
Table
Bit | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
Byte |
|
|
|
|
|
|
|
|
0 | (MSB) |
|
| GENERATION |
|
|
| |
3 |
|
|
|
|
|
|
| (LSB) |
4 | (MSB) |
|
| Additional Length |
|
|
| |
7 |
|
|
|
|
|
|
| (LSB) |
8 | (MSB) |
|
| Reservation descriptor |
|
|
| |
23 |
|
|
|
|
|
|
| (LSB) |
GENERATION: This field will be defined for the PERSISTENT RESERVE IN READ KEYS parameter data.
Additional Length: This filed contains a counter of the number of bytes to follow in Reservation descriptor. If the allocation length specified by the PERSISTENT RESERVE IN command is not sufficient to contain the entire parameter list, then only the bytes from 0 to the maximum allowed allocation length will be sent to the application client. The incremental remaining bytes will be truncated, although the Additional Length field will still contain the actual number of bytes of Reservation descriptor and will not be affected by the truncation. This will not be considered an error.
Reservation descriptor: The format of this field is defined in Table
Table
Bit | 7 | 6 |
| 5 |
| 4 |
| 3 |
| 2 |
| 1 | 0 | |
Byte |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
0 | (MSB) |
|
|
|
| Reservation Key |
|
|
|
| ||||
7 |
|
|
|
|
|
|
|
|
|
|
|
|
| (LSB) |
8 | (MSB) |
|
|
|
|
|
|
|
| |||||
11 |
|
|
|
|
|
| (0 0 0 0) |
|
|
|
| (LSB) | ||
12 |
|
|
|
|
|
| Reserved |
|
|
|
| |||
13 |
|
| SCOPE |
|
|
|
|
|
|
| TYPE |
| ||
14 |
|
|
|
|
|
| Obsolete |
|
|
|
| |||
15 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Reservation descriptor for each reservation will contain the Reservation Key under which the persistent reservation is held. The TYPE and SCOPE of each persistent reservation as present in the PERSISTENT RESERVE OUT command that created the persistent reservation will be returned.
SONY |