Extended Message; Table 6-4: Extended Message Format; Table 6-5: Supported Extended Message Codes - Tandberg Data SLR7-140 PROGRAMMER Manual

Byte
0
1
2
3 - n+1
Extended Message Code
01h
03h
Table 6-5:
Tandberg Data
6.3.

Extended Message

A value of one (01h) of the first byte of a message
indicates the beginning
message. The minimum
extended message is three. The extended message format
is shown in the table below.
Value Description
01h Extended Message
n Extended Message Length
y Extended Message Code
x Extended Message Arguments
Table 6-4: Extended Message Format
The extended message
bytes of the extended message code plus the extended
message arguments to follow. Therefore, the total length
of the message is equal to the extended message length
plus two. A value of zero for the extended message
length indicates 256 bytes to follow.
The extended messages supported by the are shown in the
table below. The
detail in Sections 6.3.1 and 6.3.2.
Description
Synchronous Data Transfer Request
Wide Data Transfer Request
Supported Extended Message Codes
To comply with the ANSI standard [2] and [5], Wide Data
Transfer must
Synchronous Data
Transfer agreement is in effect, it will be reset to
asynchronous mode if the Wide Data Transfer Request is
accepted.
If a parity error is detected during a MESSAGE-OUT phase
the Drive will consume all the remaining bytes in the
message and ask for a re-transfer of the whole message.
If a parity error is detected during a MESSAGE-IN phase
the Initiator may signal a parity error by transferring
a MESSAGE PARITY message back to the Drive. The Drive
responds by transferring the whole message once more.
6-5 Tandberg SLR Product Line SCSI Functional Specifications
of a
number of
length specifies
extended messages
be negotiated
Transfer. If
Message System
multiple-byte extended
bytes sent for
the length
are described
prior to negotiating
a Synchronous
an
in
in
Data