           Digital Equipment Corporation                                  Confidential And Proprietary
           Mass Storage Control Protocol                                                 Version 2.4.0
           STATUS AND EVENT CODE DEFINITIONS                                                  Page B-1
                                                                                          11 June 1992


     1                                             APPENDIX B

     2                                  STATUS AND EVENT CODE DEFINITIONS



     3                                                NOTES


     4             1.  The combination of a status or event  code  with  a  subcode  expressed
     5                 (assuming 16 bit symbols) as:

     6                                         (subcode *ST.SUB)+code

     7             2.  The subcode values shown in Table B-2 are only returned as status codes
     8                 in  end  messages.  They are never returned as event codes in error log
     9                 messages.  In addition, the references to other tables within Table B-2
    10  |              indicate  that those tables contain subcodes which are only returned as
    11  |              status codes in end messages.  Some of the tables referenced  by  Table
    12  |              B-2  show  subcodes  listed as both status and event subcodes, however,
    13  |              under certain conditions some  subcode  values  are  only  returned  as
    14  |              status codes.

    15             3.  The subcode values shown in Tables B-3 through B-10, and Table B-12 may
    16                 be  returned  (as  indicated  in  the  "EV" and "ST" columns) as status
    17                 codes, event codes or both.  In those tables, an asterisk in  the  "EV"
    18                 column  indicates that the code and subcode may be returned as an event
    19                 code.  An asterisk in the "ST"  column  indicates  that  the  code  and
    20                 subcode may be returned as a status code.

    21             4.  The  subcode  values  shown  in  Table  B-9,  "Bad  Block   Replacement
    22                 Completion"  Event  Only Subcode Values, are only returned as the event
    23                 code in "Bad Block Replacement Attempt" error log messages, where  they
    24                 report  the completion status of a bad block replacement attempt.  They
    25                 are never returned as status codes.  The subcode values shown in  Table
    26                 B-11,  "Informational"  Event Only Subcode Values, are only returned as
    27                 event codes for reporting informational logs.

    28  |          5.  Status and Event code/subcode descriptions  that  reference  this  note
    29  |              have  meaning  only  for  VMS  and  for  HSC  controllers that provided
    30                 "Bundled Shadowing" support, See Appendix E, "Waivers and  Exceptions",
    31                 Section   E.3.1.1.8,   ""Bundled   Shadowing"   Specific   Status  Code
    32                 Definitions".








                                                        
                                         *** RESTRICTED DISTRIBUTION ***
           Digital Equipment Corporation                                  Confidential And Proprietary
           Mass Storage Control Protocol                                                 Version 2.4.0
           STATUS AND EVENT CODE DEFINITIONS                                                  Page B-2
                                                                                          11 June 1992


     1                                 Table B-1:  Status and Event Codes

     2     +--------------------+--------------------------+-----------------------------------------+
     3     |       Value        |   Preferred Mnemonics    |                                         |
     4     +------+------+------+--------+-----------------+     Status or Event Code                |
     5     | Dec. | Oct. | Hex. | 16 bit |     32 bit      |                                         |
     6     +------+------+------+--------+-----------------+-----------------------------------------+
     7     |   31 |   37 |   1F | ST.MSK | MSCP$M_ST_MASK  | Status / event code mask                |
     8     |   32 |   40 |   20 | ST.SUB | MSCP$K_ST_SBCOD | Subcode multiplier                      |
     9     |      |      |      |        |                 |                                         |
    10     |    0 |    0 |    0 | ST.SUC | MSCP$K_ST_SUCC  | Success                                 |
    11     |    1 |    1 |    1 | ST.CMD | MSCP$K_ST_ICMD  | Invalid Command                         |
    12     |    2 |    2 |    2 | ST.ABO | MSCP$K_ST_ABRTD | Command Aborted                         |
    13     |    3 |    3 |    3 | ST.OFL | MSCP$K_ST_OFFLN | Unit-Offline                            |
    14     |    4 |    4 |    4 | ST.AVL | MSCP$K_ST_AVLBL | Unit-Available                          |
    15     |    5 |    5 |    5 | ST.MFE | MSCP$K_ST_MFMTE | Media Format Error                      |
    16     |    6 |    6 |    6 | ST.WPR | MSCP$K_ST_WRTPR | Write Protected                         |
    17     |    7 |    7 |    7 | ST.CMP | MSCP$K_ST_COMP  | Compare Error                           |
    18     |    8 |   10 |    8 | ST.DAT | MSCP$K_ST_DATA  | Data Error                              |
    19     |    9 |   11 |    9 | ST.HST | MSCP$K_ST_HSTBF | Host Buffer Access Error                |
    20     |   10 |   12 |    A | ST.CNT | MSCP$K_ST_CNTLR | Controller Error                        |
    21     |   11 |   13 |    B | ST.DRV | MSCP$K_ST_DRIVE | Drive Error                             |
    22     |   12 |   14 |    C |   -    |        -        | "Bundled Shadowing"  (see Note 5)       |
    23     |   13 |   15 |    D | ST.WHE | MSCP$K_ST_WHEAE | Write History Entry Access Error        |
    24     |   20 |   24 |   14 | ST.BBR | MSCP$K_ST_BBR   | Bad Block Replacement Completion        |
    25     |   21 |   25 |   15 | ST.PRM | MSCP$K_ST_IPARM | Invalid Parameter                       |
    26     |   22 |   26 |   16 | ST.INF | MSCP$K_ST_INFO  | Informational (not an error)            |
    27     |   23 |   27 |   17 | ST.LDR | MSCP$K_ST_LOADR | Media Loader Error (see note below)     |
    28     |   24 |   30 |   18 | ST.HER | MSCP$K_ST_HOST  | Host Error                              |
    29  |  |   25 |   31 |   19 | ST.CAC | MSCP$K_ST_CAC   | Cache Error                             |
    30     |   30 |   36 |   1E | ST.SCO | MSCP$K_ST_SBCERR| Subcommand Error                        |
    31     +------+------+------+--------+-----------------+-----------------------------------------+



















                                                        
                                         *** RESTRICTED DISTRIBUTION ***
           Digital Equipment Corporation                                  Confidential And Proprietary
           Mass Storage Control Protocol                                                 Version 2.4.0
           STATUS AND EVENT CODE DEFINITIONS                                                  Page B-3
                                                                                          11 June 1992


     1                               Table B-2:  Status Only Subcode Values

     2      +------+---------------------+---------------------------------------------------------+
     3      | Sub- |   Code + Subcode    |                                                         |
     4      | code +------+-------+------+                 Status Subcode                          |
     5      |      | Dec. |  Oct. | Hex. |                                                         |
     6      +------+------+-------+------+---------------------------------------------------------+
     7      | "Success" Subcode values:  |                                                         |
     8      |    0 |    0 |     0 |    0 | Normal                                                  |
     9      |    1 |   32 |    40 |   20 | Spin-down Ignored                                       |
    10      |    2 |   64 |   100 |   40 | Still Connected                                         |
    11      |    4 |  128 |   200 |   80 | Duplicate Unit Number                                   |
    12      |    8 |  256 |   400 |  100 | Already Online                                          |
    13      |   16 |  512 |  1000 |  200 | Still Online                                            |
    14      |   32 | 1024 |  2000 |  400 | Incomplete Replacement                                  |
    15      |   64 | 2048 |  4000 |  800 | Invalid RCT                                             |
    16      |  128 | 4096 | 10000 | 1000 | Read Only Volume Format                                 |
    17      +------+------+-------+------+---------------------------------------------------------+
    18      | "Invalid Command" Subcode values:                                                    |
    19      |    0 |    1 |     1 |    1 | Invalid Message Length                                  |
    20      | many |      |       |      | Other  "Invalid Command" subcodes values are referenced |
    21      |      |      |       |      | as follows (note that this is combined with the  status |
    22      |      |      |       |      | code):                                                  |
    23      |      |      |       |      |                                                         |
    24      |      |      |       |      |      offset*256.+code                                   |
    25      |      |      |       |      |                                                         |
    26      |      |      |       |      | where "offset" is the command message offset symbol for |
    27      |      |      |       |      | the  field  in  error  and "code" is the symbol for the |
    28      |      |      |       |      | "Invalid Command" status code.                          |
    29      +------+------+-------+------+---------------------------------------------------------+
    30      | "Command Aborted" Subcode values:                                                    |
    31      |    0 |    2 |     2 |    2 | Subcodes are not used.                                  |
    32      +------+------+-------+------+---------------------------------------------------------+
    33      | "Unit-Offline" Subcode values:                                                       |
    34      |    0 |    3 |     3 |    3 | Unit unknown or online to another controller.           |
    35      |    1 |   35 |    43 |   23 | No  volume  mounted  or  drive  disabled  via  RUN/STOP |
    36      |      |      |       |      | switch (unit is in known substate).                     |
    37      |    2 |   67 |   103 |   43 | Unit is inoperative                                     |
    38      |      |      |       |      |   For  SI  drives, the  controller has marked the drive |
    39      |      |      |       |      |   inoperative  due  to  an  unrecoverable  error  in  a |
    40      |      |      |       |      |   previous  level 2  exchange, the drive's C1  flag  is |
    41      |      |      |       |      |   set, or  the  drive  has a duplicate unit identifier. |
    42      |    4 |  131 |   203 |   83 | Duplicate unit number                                   |
    43      |    8 |  259 |   403 |  103 | Unit disabled by field service or diagnostic.           |
    44      |      |      |       |      |   For SI drives, the drive's DD flag is set.            |
    45      |   16 |  515 |  1003 |  203 | Exclusive Use                                           |
    46      +------+------+-------+------+---------------------------------------------------------+




                                                        
                                         *** RESTRICTED DISTRIBUTION ***
           Digital Equipment Corporation                                  Confidential And Proprietary
           Mass Storage Control Protocol                                                 Version 2.4.0
           STATUS AND EVENT CODE DEFINITIONS                                                  Page B-4
                                                                                          11 June 1992



     1                            Table B-2: Status Only Subcode Values (cont.)

     2      +------+---------------------+---------------------------------------------------------+
     3      | Sub- |   Code + Subcode    |                                                         |
     4      | code +------+-------+------+                 Status Subcode                          |
     5      |      | Dec. |  Oct. | Hex. |                                                         |
     6      +------+------+-------+------+---------------------------------------------------------+
     7      | "Unit-Available" Subcode values:                                                     |
     8      |    0 |    4 |     4 |    4 | Available                                               |
     9      |    2 |   68 |   104 |   44 | "Bundled Shadowing" (see Note 5)                        |
    10      |    4 |  132 |   204 |   84 | "Bundled Shadowing" (see Note 5)                        |
    11      |   32 | 1028 |  2004 |  404 | Already In Use                                          |
    12      +------+------+-------+------+---------------------------------------------------------+
    13      | "Media Format Error" Subcode values -- see Table B-3                                 |
    14      +------+------+-------+------+---------------------------------------------------------+
    15      | "Write Protected" Subcode values:                                                    |
    16      |    8 |  262 |   406 |  106 | Unit is Data Safety Write Protected                     |
    17      |  128 | 4102 | 10006 | 1006 | Unit is Software Write Protected                        |
    18      |  256 | 8198 | 20006 | 2006 | Unit is Hardware Write Protected                        |
    19      +------+------+-------+------+---------------------------------------------------------+
    20      | "Compare Error" Subcode values -- see Table B-4                                      |
    21      +------+------+-------+------+---------------------------------------------------------+
    22      | "Data Error" Subcode values -- see Table B-5                                         |
    23      +------+------+-------+------+---------------------------------------------------------+
    24      | "Host Buffer Access Error" Subcode values -- see Table B-6                           |
    25      +------+------+-------+------+---------------------------------------------------------+
    26      | "Controller Error" subcode values -- see Table B-7                                   |
    27      +------+------+-------+------+---------------------------------------------------------+
    28      | "Write History Entry Access Error" subcodes:                                         |
    29      |    1 |   45 |    55 |   2D | Previous Allocation Failure                             |
    30      |    2 |   77 |   115 |   4D | Allocation Failure Table Full                           |
    31      |    8 |  269 |   415 |  10D | No such entry                                           |
    32      +------+------+-------+------+---------------------------------------------------------+
    33      | "Subcommand Error" subcode values -- see Table B-12                                  |
    34      +------+------+-------+------+---------------------------------------------------------+















                                                        
                                         *** RESTRICTED DISTRIBUTION ***
           Digital Equipment Corporation                                  Confidential And Proprietary
           Mass Storage Control Protocol                                                 Version 2.4.0
           STATUS AND EVENT CODE DEFINITIONS                                                  Page B-5
                                                                                          11 June 1992


     1                  Table B-3:  "Media Format Error" Status or Event Subcode Values

     2      +------+---------------------+-+-+-----------------------------------------------------+
     3      | Sub- |   Code + Subcode    |E|S|                                                     |
     4      | code +------+-------+------+V|T|     Status or Event Subcode                         |
     5      |      | Dec. |  Oct. | Hex. | | |                                                     |
     6      +------+------+-------+------+-+-+-----------------------------------------------------+
     7      | many |     |        |      |*|*| "Data Error" accessing RCT or FCT.                  |
     8      |      For  every "Data Error"  subcode  that  may be reported as a status code (i.e., |
     9      |      for every  subcode  listed  in  Table B-5 that  has  an  asterisk in  the  "ST" |
    10      |      column), the  exact  same  subcode   value may be returned  as a "Media  Format |
    11      |      Error" subcode value.  These  subcodes  indicate  that a transfer to the unit's |
    12      |      FCT or  RCT (using  the multicopy  structure read and  write algorithms) failed |
    13      |      for the  specified reason.  The  subcode reports the error that occurred on the |
    14      |      last  copy  of  the multicopy  structure.  For  example, the  subcode  value  7 |
    15      |      (combined  code and subcode value of 229 decimal) indicates that the FCT or RCT |
    16      |      is unreadable due to an Uncorrectable ECC Error.                                |
    17      |                                                                                      |
    18      |      In  addition  to  the subcode  values  copied from "Data Error" subcode values, |
    19      |      the subcode values listed below also exist.                                     |
    20      +------+------+-------+------+-+-+-----------------------------------------------------+
    21      |    4 |  133 |   205 |   85 |-|-| "Bundled Shadowing" (see Note 5)                    |
    22      +------+------+-------+------+-+-+-----------------------------------------------------+
    23      |    5 |  165 |   245 |   A5 | |*| Disk isn't formatted with 512 byte sectors          |
    24      |      |      |       |      | | |   The  disk's FCT  indicates that  it is  formatted |
    25      |      |      |       |      | | |   with 576 byte  sectors, yet either the controller |
    26      |      |      |       |      | | |   or the drive only supports 512 byte sectors.      |
    27      +------+------+-------+------+-+-+-----------------------------------------------------+
    28      |    6 |  197 |   305 |   C5 | |*| Disk isn't formatted or FCT corrupted               |
    29      |      |      |       |      | | |   The disk's FCT does not indicate that the disk is |
    30      |      |      |       |      | | |   formatted with either 512 or 576 byte sectors.    |
    31      +------+------+-------+------+-+-+-----------------------------------------------------+
    32      |    8 |  261 |   405 |  105 |*|*| RCT corrupted.                                      |
    33      |      |      |       |      | | |   The RCT  search algorithm  encountered an invalid |
    34      |      |      |       |      | | |   RCT  entry.  This  subcode  may  be  returned  by |
    35      |      |      |       |      | | |   replacement  (searching   the  RCT   for  a   new |
    36      |      |      |       |      | | |   replacement block), by revectoring (searching the |
    37      |      |      |       |      | | |   RCT  to  locate the replacement  block for  a bad |
    38      |      |      |       |      | | |   block), and when a unit is brought "Unit-Online." |
    39      +------+------+-------+------+-+-+-----------------------------------------------------+
    40      |    9 |  293 |   445 |  125 |*| | No replacement block available.                     |
    41      |      |      |       |      | | |   Replacement  was attempted for a bad block, but a |
    42      |      |      |       |      | | |   replacement block  could not  be allocated (i.e., |
    43      |      |      |       |      | | |   the  volume's RCT is  full).  This subcode may be |
    44      |      |      |       |      | | |   returned  both during actual replacement and when |
    45      |      |      |       |      | | |   an interrupted  replacement is  completed as part |
    46      |      |      |       |      | | |   of bringing a unit "Unit-Online."                 |
    47      +------+------+-------+------+-+-+-----------------------------------------------------+



                                                        
                                         *** RESTRICTED DISTRIBUTION ***
           Digital Equipment Corporation                                  Confidential And Proprietary
           Mass Storage Control Protocol                                                 Version 2.4.0
           STATUS AND EVENT CODE DEFINITIONS                                                  Page B-6
                                                                                          11 June 1992



     1               Table B-3: "Media Format Error" Status or Event Subcode Values (cont.)

     2      +------+---------------------+-+-+-----------------------------------------------------+
     3      | Sub- |   Code + Subcode    |E|S|                                                     |
     4      | code +------+-------+------+V|T|     Status or Event Subcode                         |
     5      |      | Dec. |  Oct. | Hex. | | |                                                     |
     6      +------+------+-------+------+-+-+-----------------------------------------------------+
     7      |   10 |  325 |   505 |  145 |*| | No multicopy protection.                            |
     8      |      |      |       |      | | |   All  but  one  copy  of  a  block  in a multicopy |
     9      |      |      |       |      | | |   structure are bad.  This is a  warning  that  the |
    10      |      |      |       |      | | |   disk  should  be  reformatted  or replaced at the |
    11      |      |      |       |      | | |   earliest convenient time.                         |
    12      +------+------+-------+------+-+-+-----------------------------------------------------+


    13                     Table B-4:  "Compare Error" Status or Event Subcode Values

    14      +------+---------------------+-+-+-----------------------------------------------------+
    15      | Sub- |   Code + Subcode    |E|S|                                                     |
    16      | code +------+-------+------+V|T|     Status or Event Subcode                         |
    17      |      | Dec. |  Oct. | Hex. | | |                                                     |
    18      +------+------+-------+------+-+-+-----------------------------------------------------+
    19      |    0 |    7 |    7  |    7 |*|*| Subcodes  are  not  used.  Note: the  compare error |
    20      |      |      |       |      | | | code  is only used  as an event code when the error |
    21      |      |      |       |      | | | occurs   during   a read-compare  or  write-compare |
    22      |      |      |       |      | | | operation.                                          |
    23      +------+------+-------+------+-+-+-----------------------------------------------------+


    24                      Table B-5:  "Data Error" Status or Event Subcode Values

    25      +------+---------------------+-+-+-----------------------------------------------------+
    26      | Sub- |   Code + Subcode    |E|S|                                                     |
    27      | code +------+-------+------+V|T|     Status or Event Subcode                         |
    28      |      | Dec. |  Oct. | Hex. | | |                                                     |
    29      +------+------+-------+------+-+-+-----------------------------------------------------+
    30      |    0 |    8 |    10 |    8 | |*| Sector was written with "Force Error" modifier      |
    31      +------+------+-------+------+-+-+-----------------------------------------------------+












                                                        
                                         *** RESTRICTED DISTRIBUTION ***
           Digital Equipment Corporation                                  Confidential And Proprietary
           Mass Storage Control Protocol                                                 Version 2.4.0
           STATUS AND EVENT CODE DEFINITIONS                                                  Page B-7
                                                                                          11 June 1992



     1                   Table B-5: "Data Error" Status or Event Subcode Values (cont.)

     2      +------+---------------------+-+-+-----------------------------------------------------+
     3      | Sub- |   Code + Subcode    |E|S|                                                     |
     4      | code +------+-------+------+V|T|     Status or Event Subcode                         |
     5      |      | Dec. |  Oct. | Hex. | | |                                                     |
     6      +------+------+-------+------+-+-+-----------------------------------------------------+
     7      |    2 |   72 |   110 |   48 |*|*| Invalid header.                                     |
     8      |      |      |       |      | | |   The  subsystem read  an invalid  or  inconsistent |
     9      |      |      |       |      | | |   header for the requested sector.  For recoverable |
    10      |      |      |       |      | | |   errors,  this code  implies that  a retry  of the |
    11      |      |      |       |      | | |   transfer read  a valid header.  For unrecoverable |
    12      |      |      |       |      | | |   errors,  this code  implies  that  the  subsystem |
    13      |      |      |       |      | | |   attempted  tertiary  revectoring  and  determined |
    14      |      |      |       |      | | |   that  the  requested  sector  is  not  revectored |
    15      |      |      |       |      | | |   (i.e.,  the RCT indicates  that the sector is not |
    16      |      |      |       |      | | |   revectored).  Causes of an invalid header include |
    17      |      |      |       |      | | |   header  missync,  header   sync  timeout,  and  a |
    18      |      |      |       |      | | |   garbage (inconsistent) header.                    |
    19      +------+------+-------+------+-+-+-----------------------------------------------------+
    20      |    3 |  104 |   150 |   68 |*|*| Data Sync not found (Data Sync timeout).            |
    21      +------+------+-------+------+-+-+-----------------------------------------------------+
    22      |    4 |  136 |   210 |   88 |*| | Correctable error in ECC field.                     |
    23      |      |      |       |      | | |   A transfer  encountered  a correctable  error  in |
    24      |      |      |       |      | | |   which only  the ECC field was affected.  That is, |
    25      |      |      |       |      | | |   all  data bits  were correct  but some portion of |
    26      |      |      |       |      | | |   the ECC field was incorrect.  The severity of the |
    27      |      |      |       |      | | |   error (i.e., the  number of symbols  in error) is |
    28      |      |      |       |      | | |   unknown.  If the  number of  symbols in  error is |
    29      |      |      |       |      | | |   known,  an "n Symbol ECC Error" subcode should be |
    30      |      |      |       |      | | |   returned instead.                                 |
    31      +------+------+-------+------+-+-+-----------------------------------------------------+
    32  |   |    5 |  168 |   250 |   A8 |*| | Header Threshold Event                              |
    33  |   |      |      |       |      | | |   This is not an error. Data correction or recovery |
    34  |   |      |      |       |      | | |   was used in the header portion of a block at      |
    35  |   |      |      |       |      | | |   levels within the range of normal device          |
    36  |   |      |      |       |      | | |   operation. This subcode is typically used when    |
    37  |   |      |      |       |      | | |   sufficient events are available to justify        |
    38  |   |      |      |       |      | | |   reporting them to automated fault analysis tools. |
    39  |   |      |      |       |      | | |   The information in the log message is unlikely to |
    40  |   |      |      |       |      | | |   be useful for any  other purpose.                 |
    41  |   +------+------+-------+------+-+-+-----------------------------------------------------+








                                                        
                                         *** RESTRICTED DISTRIBUTION ***
           Digital Equipment Corporation                                  Confidential And Proprietary
           Mass Storage Control Protocol                                                 Version 2.4.0
           STATUS AND EVENT CODE DEFINITIONS                                                  Page B-8
                                                                                          11 June 1992



     1                   Table B-5: "Data Error" Status or Event Subcode Values (cont.)

     2      +------+---------------------+-+-+-----------------------------------------------------+
     3      | Sub- |   Code + Subcode    |E|S|                                                     |
     4      | code +------+-------+------+V|T|     Status or Event Subcode                         |
     5      |      | Dec. |  Oct. | Hex. | | |                                                     |
     6      +------+------+-------+------+-+-+-----------------------------------------------------+
     7  |   |    6 |  200 |   310 |   C8 |*| | Data Threshold Event                                |
     8  |   |      |      |       |      | | |   This is not an error. Data correction or recovery |
     9  |   |      |      |       |      | | |   was used in the data portion of a block at levels |
    10  |   |      |      |       |      | | |   within the range of normal device operation. This |
    11  |   |      |      |       |      | | |   subcode is typically used when sufficient events  |
    12  |   |      |      |       |      | | |   are available to justify reporting them to        |
    13  |   |      |      |       |      | | |   automated fault analysis tools. The information in|
    14  |   |      |      |       |      | | |   the log message is unlikely to be useful for any  |
    15  |   |      |      |       |      | | |   other purpose.                                    |
    16  |   +------+------+-------+------+-+-+-----------------------------------------------------+
    17      |    7 |  232 |   350 |   E8 |*|*| Uncorrectable ECC Error.                            |
    18      |      |      |       |      | | |   A    transfer   without   the   "Suppress   Error |
    19      |      |      |       |      | | |   Correction"  modifier  encountered  an  ECC error |
    20      |      |      |       |      | | |   that  exceeds  the  correction capability  of the |
    21      |      |      |       |      | | |   subsystem's  error  correction  algorithms, or  a |
    22      |      |      |       |      | | |   transfer  with  the "Suppress  Error  Correction" |
    23      |      |      |       |      | | |   modifier encountered an ECC error of any severity |
    24      |      |      |       |      | | |   whatsoever.                                       |
    25      +------+------+-------+------+-+-+-----------------------------------------------------+
    26      |    8 |  264 |   410 |  108 |*| | One Symbol ECC Error.                               |
    27      |    9 |  296 |   450 |  128 |*| | Two Symbol ECC Error.                               |
    28      |   10 |  328 |   510 |  148 |*| | Three Symbol ECC Error.                             |
    29      |   11 |  360 |   550 |  168 |*| | Four Symbol ECC Error.                              |
    30      |   12 |  392 |   610 |  188 |*| | Five Symbol ECC Error.                              |
    31      |   13 |  424 |   650 |  1A8 |*| | Six Symbol ECC Error.                               |
    32      |   14 |  456 |   710 |  1C8 |*| | Seven Symbol ECC Error.                             |
    33      |   15 |  488 |   750 |  1E8 |*| | Eight Symbol ECC Error.                             |
    34      |   16 |  520 |  1010 |  208 |*| | Nine Symbol ECC Error.                              |
    35      |   17 |  552 |  1050 |  228 |*| | Ten Symbol ECC Error.                               |
    36      |   18 |  584 |  1110 |  248 |*| | Eleven Symbol ECC Error.                            |
    37      |   19 |  616 |  1150 |  268 |*| | Twelve Symbol ECC Error.                            |
    38      |   20 |  648 |  1210 |  288 |*| | Thirteen Symbol ECC Error.                          |
    39      |   21 |  680 |  1250 |  2A8 |*| | Fourteen Symbol ECC Error.                          |
    40      |   22 |  712 |  1310 |  2C8 |*| | Fifteen Symbol ECC Error.                           |
    41      |      |      |       |      | | |   A transfer  encountered  a correctable  ECC error |
    42      |      |      |       |      | | |   with  the  specified  number  of  ECC  symbols in |
    43      |      |      |       |      | | |   error.  The  number of  symbols in  error roughly |
    44      |      |      |       |      | | |   corresponds to the severity of the error.         |
    45      +------+------+-------+------+-+-+-----------------------------------------------------+




                                                        
                                         *** RESTRICTED DISTRIBUTION ***
           Digital Equipment Corporation                                  Confidential And Proprietary
           Mass Storage Control Protocol                                                 Version 2.4.0
           STATUS AND EVENT CODE DEFINITIONS                                                  Page B-9
                                                                                          11 June 1992


     1               Table B-6:  "Host Buffer Access Error" Status or Event Subcode Values

     2      +------+---------------------+-+-+-----------------------------------------------------+
     3      | Sub- |   Code + Subcode    |E|S|                                                     |
     4      | code +------+-------+------+V|T|     Status or Event Subcode                         |
     5      |      | Dec. |  Oct. | Hex. | | |                                                     |
     6      +------+------+-------+------+-+-+-----------------------------------------------------+
     7      |    0 |    9 |    11 |    9 | |*| Host buffer access error, cause not available.      |
     8      |      |      |       |      | | |   The controller was unable to access a host buffer |
     9      |      |      |       |      | | |   to perform a transfer, but has no visibility into |
    10      |      |      |       |      | | |   the cause of the error.                           |
    11      +------+------+-------+------+-+-+-----------------------------------------------------+
    12      |    1 |   41 |    51 |   29 | |*| Odd transfer address                                |
    13      +------+------+-------+------+-+-+-----------------------------------------------------+
    14      |    2 |   73 |   111 |   49 | |*| Odd byte count                                      |
    15      +------+------+-------+------+-+-+-----------------------------------------------------+
    16      |    3 |  105 |   151 |   69 |*|*| Nonexistent memory error                            |
    17      +------+------+-------+------+-+-+-----------------------------------------------------+
    18      |    4 |  137 |   211 |   89 |*|*| Host memory parity error                            |
    19      +------+------+-------+------+-+-+-----------------------------------------------------+
    20      |    5 |  169 |   251 |   A9 |*|*| Invalid page table entry                            |
    21      |      |      |       |      | | |   (See the  Storage  Systems Port Specification for |
    22      |      |      |       |      | | |    additional detail.)                              |
    23      +------+------+-------+------+-+-+-----------------------------------------------------+
    24      |    6 |  201 |   311 |   C9 |*|*| Invalid buffer name                                 |
    25      |      |      |       |      | | |   The key in the buffer name does not match the key |
    26      |      |      |       |      | | |   in the buffer descriptor, the V bit in the buffer |
    27      |      |      |       |      | | |   descriptor is clear, or the index into the Buffer |
    28      |      |      |       |      | | |   Descriptor  Table  is  too large. (See the BI VAX |
    29      |      |      |       |      | | |   Port Specification for additional detail.)        |
    30      +------+------+-------+------+-+-+-----------------------------------------------------+
    31      |    7 |  233 |   351 |   E9 |*|*| Buffer length violation                             |
    32      |      |      |       |      | | |   The  number  of  bytes  requested   in  the  MSCP |
    33      |      |      |       |      | | |   command   exceeds  the buffer length as specified |
    34      |      |      |       |      | | |   in   the  buffer  descriptor.  (See  the  BI  VAX |
    35      |      |      |       |      | | |   Port Specification for additional detail.)        |
    36      +------+------+-------+------+-+-+-----------------------------------------------------+
    37      |    8 |  265 |   411 |  109 |*|*| Access control violation                            |
    38      |      |      |       |      | | |   The   access   mode   specified   in  the  buffer |
    39      |      |      |       |      | | |   descriptor   is  protected  against  by  the PROT |
    40      |      |      |       |      | | |   field   in   the   PTE.  (See  the  BI  VAX  Port |
    41      |      |      |       |      | | |   Specification for additional detail.)             |
    42      +------+------+-------+------+-+-+-----------------------------------------------------+








                                                        
                                         *** RESTRICTED DISTRIBUTION ***
           Digital Equipment Corporation                                  Confidential And Proprietary
           Mass Storage Control Protocol                                                 Version 2.4.0
           STATUS AND EVENT CODE DEFINITIONS                                                 Page B-10
                                                                                          11 June 1992


     1                   Table B-7:  "Controller Error" Status or Event Subcode Values

     2      +------+---------------------+-+-+-----------------------------------------------------+
     3      | Sub- |   Code + Subcode    |E|S|                                                     |
     4      | code +------+-------+------+V|T|     Status or Event Subcode                         |
     5      |      | Dec. |  Oct. | Hex. | | |                                                     |
     6      +------+------+-------+------+-+-+-----------------------------------------------------+
     7      |    0 |   10 |    12 |    A |-|-| Reserved  for host  detected command  timeout error |
     8      |      |      |       |      | | | logging.  This  subcode  is  never  reported  by  a |
     9      |      |      |       |      | | | controller.                                         |
    10      +------+------+-------+------+-+-+-----------------------------------------------------+
    11      |    1 |   42 |    52 |   2A |*|*| SERDES overrun or underrun error.                   |
    12      |      |      |       |      | | |   Either the  drive is too fast for the controller, |
    13      |      |      |       |      | | |   or (more typically) a  controller hardware  fault |
    14      |      |      |       |      | | |   has  prevented controller  microcode  from  being |
    15      |      |      |       |      | | |   able to keep up with data transfer to or from the |
    16      |      |      |       |      | | |   drive.                                            |
    17      +------+------+-------+------+-+-+-----------------------------------------------------+
    18      |    2 |   74 |   112 |   4A |*|*| EDC error.                                          |
    19      |      |      |       |      | | |   The  sector was  read with correct or correctable |
    20      |      |      |       |      | | |   ECC and an invalid  EDC.  There is most  likely a |
    21      |      |      |       |      | | |   fault in  the ECC logic of either this controller |
    22      |      |      |       |      | | |   or the controller that last wrote the sector.     |
    23      +------+------+-------+------+-+-+-----------------------------------------------------+
    24      |    3 |  106 |   152 |   6A |*|*| Software Logic error.                               |
    25      |      |      |       |      | | |   Some  high  level  check detected  an  error that |
    26      |      |      |       |      | | |   indicates a fault in the execution of code within |
    27      |      |      |       |      | | |   the controller. For example, an inconsistent data |
    28      |      |      |       |      | | |   structure  is  detected (a nonzero reserved field |
    29      |      |      |       |      | | |   or a value in a field outside its valid range) or |
    30      |      |      |       |      | | |   an error in the code  flow  occurs.   This  error |
    31      |      |      |       |      | | |   almost   always   implies   the  existence  of  a |
    32      |      |      |       |      | | |   microcode bug.                                    |
    33      +------+------+-------+------+-+-+-----------------------------------------------------+
    34      |    4 |  138 |   212 |   8A |*|*| Internal EDC error.                                 |
    35      |      |      |       |      | | |   Some  low  level  check detected an  inconsistent |
    36      |      |      |       |      | | |   data    structure.  For   example,  a   microcode |
    37      |      |      |       |      | | |   implemented checksum or vertical parity (hardware |
    38      |      |      |       |      | | |   parity  is  horizontal)  associated with internal |
    39      |      |      |       |      | | |   sector data was inconsistent.  This error usually |
    40      |      |      |       |      | | |   implies a fault in the memory addressing logic of |
    41      |      |      |       |      | | |   one  or  more  of  the   controller's  processing |
    42      |      |      |       |      | | |   elements.  It  may also  result from a double bit |
    43      |      |      |       |      | | |   error   or  other  error  that  exceeds the error |
    44      |      |      |       |      | | |   detection capability of the controller's hardware |
    45      |      |      |       |      | | |   memory checking circuitry.                        |
    46      +------+------+-------+------+-+-+-----------------------------------------------------+
    47      |    5 |  170 |   252 |   AA |*|*| LESI Adaptor Card parity error on input (adaptor to |
    48      |      |      |       |      | | | controller).                                        |
    49      +------+------+-------+------+-+-+-----------------------------------------------------+

                                                        
                                         *** RESTRICTED DISTRIBUTION ***
           Digital Equipment Corporation                                  Confidential And Proprietary
           Mass Storage Control Protocol                                                 Version 2.4.0
           STATUS AND EVENT CODE DEFINITIONS                                                 Page B-11
                                                                                          11 June 1992



     1                Table B-7: "Controller Error" Status or Event Subcode Values (cont.)

     2      +------+---------------------+-+-+-----------------------------------------------------+
     3      | Sub- |   Code + Subcode    |E|S|                                                     |
     4      | code +------+-------+------+V|T|     Status or Event Subcode                         |
     5      |      | Dec. |  Oct. | Hex. | | |                                                     |
     6      +------+------+-------+------+-+-+-----------------------------------------------------+
     7      |    6 |  202 |   312 |   CA |*|*| LESI   Adaptor   Card    parity   error  on  output |
     8      |      |      |       |      | | | (controller to adaptor).                            |
     9      +------+------+-------+------+-+-+-----------------------------------------------------+
    10      |    7 |  234 |   352 |   EA |*|*| LESI Adaptor Card "cable in place" not asserted.    |
    11      +------+------+-------+------+-+-+-----------------------------------------------------+
    12      |    8 |  266 |   412 |  10A |*|*| Controller overrun or underrun.                     |
    13      |      |      |       |      | | |   The   controller  attempted  to  perform too many |
    14      |      |      |       |      | | |   concurrent transfers, causing one or more of them |
    15      |      |      |       |      | | |   to fail due to a data overrun or underrun.        |
    16      +------+------+-------+------+-+-+-----------------------------------------------------+
    17      |    9 |  298 |   452 |  12A |*|*| Controller memory error.                            |
    18      |      |      |       |      | | |   The controller  detected an  error in an internal |
    19      |      |      |       |      | | |   memory, such  as  a parity error or nonresponding |
    20      |      |      |       |      | | |   address.  This  subcode  only  applies  to errors |
    21      |      |      |       |      | | |   that  do not  affect the controller's  ability to |
    22      |      |      |       |      | | |   properly  generate end and error log messages, as |
    23      |      |      |       |      | | |   errors  that  might  affect  end  and  error  log |
    24      |      |      |       |      | | |   messages  are not  reported via MSCP.  Therefore, |
    25      |      |      |       |      | | |   for most  controllers  this  subcode will only be |
    26      |      |      |       |      | | |   returned for controller  memory errors in data or |
    27      |      |      |       |      | | |   buffer    memory     and    noncritical   control |
    28      |      |      |       |      | | |   structures.  If the  controller  has several such |
    29      |      |      |       |      | | |   memories,  the   specific   memory   involved  is |
    30      |      |      |       |      | | |   reported   as   part  of the error address in the |
    31      |      |      |       |      | | |   error log message.                                |
    32      +------+------+-------+------+-+-+-----------------------------------------------------+
    33      |   10 |  330 |   512 |  14A |-|-| "Bundled Shadowing (see Note 5)                     |
    34      +------+------+-------+------+-+-+-----------------------------------------------------+
    35      |   11 |  362 |   552 |  16A |*|*| Drive Interface Hardware error.                     |
    36      |      |      |       |      | | |   The controller detected an error that indicates a |
    37      |      |      |       |      | | |   fault in the Drive Interface Hardware.            |
    38      +------+------+-------+------+-+-+-----------------------------------------------------+
    39      |   12 |  394 |   612 |  18A |*|*| Host Interface Hardware error.                      |
    40      |      |      |       |      | | |   The controller detected an error that indicates a |
    41      |      |      |       |      | | |   fault in the Host Interface Hardware.             |
    42      +------+------+-------+------+-+-+-----------------------------------------------------+
    43      |   13 |  426 |   652 |  1AA |*|*| Internal Bus error.                                 |
    44      |      |      |       |      | | |   The controller detected an error that indicates a |
    45      |      |      |       |      | | |   fault in the Internal Bus Hardware.               |
    46      +------+------+-------+------+-+-+-----------------------------------------------------+



                                                        
                                         *** RESTRICTED DISTRIBUTION ***
           Digital Equipment Corporation                                  Confidential And Proprietary
           Mass Storage Control Protocol                                                 Version 2.4.0
           STATUS AND EVENT CODE DEFINITIONS                                                 Page B-12
                                                                                          11 June 1992



     1                Table B-7: "Controller Error" Status or Event Subcode Values (cont.)

     2      +------+---------------------+-+-+-----------------------------------------------------+
     3      | Sub- |   Code + Subcode    |E|S|                                                     |
     4      | code +------+-------+------+V|T|     Status or Event Subcode                         |
     5      |      | Dec. |  Oct. | Hex. | | |                                                     |
     6      +------+------+-------+------+-+-+-----------------------------------------------------+
     7      |   14 |  458 |   712 |  1CA |*|*| Policy Processor error.                             |
     8      |      |      |       |      | | |   The controller detected an error that indicates a |
     9      |      |      |       |      | | |   fault in the internal Policy Processor hardware.  |
    10      +------+------+-------+------+-+-+-----------------------------------------------------+
    11      |   15 |  490 |   752 |  1EA |*| | Fault Management Analysis event                     |
    12      |      |      |       |      | | |  Some specific  fault management  threshold  within |
    13      |      |      |       |      | | |  the  controller   has  been  exceeded.  The server |
    14      |      |      |       |      | | |  is still operating with designed functionality and |
    15      |      |      |       |      | | |  performance.   Further  analysis  is  required  to |
    16      |      |      |       |      | | |  determine if  Field Service action is needed.  For |
    17      |      |      |       |      | | |  example, a pool of spare memory pages has been two |
    18      |      |      |       |      | | |  thirds consumed  to  map around bad  pages.   This |
    19      |      |      |       |      | | |  event code would  have the informational flag  set |
    20      |      |      |       |      | | |  and  the  Controller Dependent  Information  field |
    21      |      |      |       |      | | |  would be used to further define the event.         |
    22      +------+------+-------+------+-+-+-----------------------------------------------------+
    23      |   16 |  522 |  1012 |  20A |*| | Self Test error.                                    |
    24      |      |      |       |      | | |  The controller detected  an error  while executing |
    25      |      |      |       |      | | |  an  internal  self test.   The  error detected may |
    26      |      |      |       |      | | |  still allow continued operation of the server. For |
    27      |      |      |       |      | | |  example, a  periodic test of an unused device port |
    28      |      |      |       |      | | |  detects an error in that device port.  This  event |
    29      |      |      |       |      | | |  code  would  use Controller Dependent  Information |
    30      |      |      |       |      | | |  field to further define the event.                 |
    31      +--------------------------------------------------------------------------------------+
    32      |   20 |  650 |  1212 |  28A | |*| Remote Connection Lost                              |
    33      +------+------+-------+------+-+-+-----------------------------------------------------+
    34      |   21 |  682 |  1252 |  2AA | |*| Remote   Connection  Request  Failed,  insufficient |
    35      |      |      |       |      | | | resources to request remote connection              |
    36      +------+------+-------+------+-+-+-----------------------------------------------------+
    37      |   22 |  714 |  1312 |  2CA |*|*| Remote  Connection  Request  Failed, subsystem port |
    38      |      |      |       |      | | | address responded but subsystem system address does |
    39      |      |      |       |      | | | not match                                           |
    40      +------+------+-------+------+-+-+-----------------------------------------------------+
    41      |   23 |  746 |  1352 |  2EA |*|*| Remote  Connection  Request  Failed, subsystem port |
    42      |      |      |       |      | | | address responded but no MSCP server present        |
    43      +------+------+-------+------+-+-+-----------------------------------------------------+
    44      |   24 |  778 |  1412 |  30A |*|*| Remote  Connection  Request  Failed, subsystem port |
    45      |      |      |       |      | | | address responded but no resources available        |
    46      +------+------+-------+------+-+-+-----------------------------------------------------+



                                                        
                                         *** RESTRICTED DISTRIBUTION ***
           Digital Equipment Corporation                                  Confidential And Proprietary
           Mass Storage Control Protocol                                                 Version 2.4.0
           STATUS AND EVENT CODE DEFINITIONS                                                 Page B-13
                                                                                          11 June 1992



     1                Table B-7: "Controller Error" Status or Event Subcode Values (cont.)

     2      +------+---------------------+-+-+-----------------------------------------------------+
     3      | Sub- |   Code + Subcode    |E|S|                                                     |
     4      | code +------+-------+------+V|T|     Status or Event Subcode                         |
     5      |      | Dec. |  Oct. | Hex. | | |                                                     |
     6      +------+------+-------+------+-+-+-----------------------------------------------------+
     7      |   25 |  810 |  1452 |  32A |*|*| Remote  Connection  Request  Failed, subsystem port |
     8      |      |      |       |      | | | address responded but no credits available          |
     9      +------+------+-------+------+-+-+-----------------------------------------------------+
    10      |   26 |  842 |  1512 |  34A |*|*| Remote  Connection Request Failed, no response from |
    11      |      |      |       |      | | | subsystem port address                              |
    12      +------+------+-------+------+-+-+-----------------------------------------------------+
    13      |   27 |  874 |  1552 |  36A |*|*| Remote  Connection  Request  Failed, subsystem port |
    14      |      |      |       |      | | | address responding but negative  acknowledge  retry |
    15      |      |      |       |      | | | algorithm exhausted                                 |
    16      +------+------+-------+------+-+-+-----------------------------------------------------+
    17      |   28 |  906 |  1612 |  38A |*|*| Remote  Connection  Request  Failed, subsystem port |
    18      |      |      |       |      | | | request timeout exceeded                            |
    19      +------+------+-------+------+-+-+-----------------------------------------------------+
    20      |   29 |  938 |  1652 |  3AA |*|*| Local   Connection   Request  Failed,  insufficient |
    21      |      |      |       |      | | | resources to request local connection               |
    22      +------+------+-------+------+-+-+-----------------------------------------------------+
    23      |   30 |  970 |  1712 |  3CA |*|*| Local   Connection  Request  Failed, subsystem port |
    24      |      |      |       |      | | | address responded but rejected with Disconnected    |
    25      +------+------+-------+------+-+-+-----------------------------------------------------+
    26  |   |   31 | 1002 |  1752 |  3EA |*| | Last Fail - Hardware                                |
    27  |   |      |      |       |      | | |   The controller detected a fatal hardware error    |
    28  |   |      |      |       |      | | |   that can not be resolved without bugcheck/reinit- |
    29  |   |      |      |       |      | | |   ialization. After reinitialization the controller |
    30  |   |      |      |       |      | | |   builds a last fail error log packet describing    |
    31  |   |      |      |       |      | | |   the reason for the bugcheck.                      |
    32  |   +------+------+-------+------+-+-+-----------------------------------------------------+
    33  |   |  32  | 1034 |  2012 |  40A |*| | Last Fail - Software                                |
    34  |   |      |      |       |      | | |   The controller detected a fatal software error    |
    35  |   |      |      |       |      | | |   that can not be resolved without bugcheck/re-     |
    36  |   |      |      |       |      | | |   initialization. After reinitialization the        |
    37  |   |      |      |       |      | | |   controller builds a last fail error log packet    |
    38  |   |      |      |       |      | | |   describing the reason for the bugcheck.           |
    39  |   +------+------+-------+------+-+-+-----------------------------------------------------+










                                                        
                                         *** RESTRICTED DISTRIBUTION ***
           Digital Equipment Corporation                                  Confidential And Proprietary
           Mass Storage Control Protocol                                                 Version 2.4.0
           STATUS AND EVENT CODE DEFINITIONS                                                 Page B-14
                                                                                          11 June 1992


     1                      Table B-8:  "Drive Error" Status or Event Subcode Values

     2      +------+---------------------+-+-+-----------------------------------------------------+
     3      | Sub- |   Code + Subcode    |E|S|                                                     |
     4      | code +------+-------+------+V|T|     Status or Event Subcode                         |
     5      |      | Dec. |  Oct. | Hex. | | |                                                     |
     6      +------+------+-------+------+-+-+-----------------------------------------------------+
     7      |    1 |   43 |    53 |   2B |*|*| Drive command time out.                             |
     8      |      |      |       |      | | |   For  SI drives, the  controller's timeout expired |
     9      |      |      |       |      | | |   for either a level 2 exchange or the assertion of |
    10      |      |      |       |      | | |   Read/Write Ready after an Initiate Seek.          |
    11      +------+------+-------+------+-+-+-----------------------------------------------------+
    12      |    2 |   75 |   113 |   4B |*|*| Controller detected transmission error.             |
    13      |      |      |       |      | | |   For SI drives, the controller detected an invalid |
    14      |      |      |       |      | | |   framing  code  or a  checksum  error in a level 2 |
    15      |      |      |       |      | | |   response  from  the  drive.  The UDA50 and UDA50A |
    16      |      |      |       |      | | |   also  return this subcode for controller detected |
    17      |      |      |       |      | | |   protocol errors.  All other SI controllers return |
    18      |      |      |       |      | | |   subcode 10 for protocol errors.                   |
    19      +------+------+-------+------+-+-+-----------------------------------------------------+
    20      |    3 |  107 |   153 |   6B |*|*| Positioner error (misseek).                         |
    21      |      |      |       |      | | |   The  drive  reported  that  a  seek operation was |
    22      |      |      |       |      | | |   successful, but  the  controller  determined that |
    23      |      |      |       |      | | |   the drive  had  positioned itself to an incorrect |
    24      |      |      |       |      | | |   cylinder.                                         |
    25      +------+------+-------+------+-+-+-----------------------------------------------------+
    26      |    4 |  139 |   213 |   8B |*|*| Lost read/write ready during or between transfers.  |
    27      |      |      |       |      | | |   For  SI drives, Read/Write ready was negated when |
    28      |      |      |       |      | | |   the  controller  attempted to initiate a transfer |
    29      |      |      |       |      | | |   or  at  the    completion   of  a  transfer,  and |
    30      |      |      |       |      | | |   Read/Write  ready  had  previously  been asserted |
    31      |      |      |       |      | | |   (indicating  completion  of  the preceding seek). |
    32      |      |      |       |      | | |   This  usually  results   from  a  drive  detected |
    33      |      |      |       |      | | |   transfer error, in which case an additional error |
    34      |      |      |       |      | | |   log  message  may  be  generated  containing  the |
    35      |      |      |       |      | | |   "Drive detected error" subcode.                   |
    36      +------+---------------------+-+-+-----------------------------------------------------+
    37      |    5 |  171 |   253 |   AB |*|*| Drive clock dropout.                                |
    38      |      |      |       |      | | |   For  SI  drives, either  data  or state clock was |
    39      |      |      |       |      | | |   missing  when  it should have been present.  This |
    40      |      |      |       |      | | |   is usually detected by means of a timeout.        |
    41      +------+------+-------+------+-+-+-----------------------------------------------------+
    42      |    6 |  203 |   313 |   CB |*|*| Lost receiver ready for transfer.                   |
    43      |      |      |       |      | | |   For  SI  drives, Receiver Ready  was negated when |
    44      |      |      |       |      | | |   the controller  attempted to  initiate a transfer |
    45      |      |      |       |      | | |   or  did   not  assert  at  the  completion  of  a |
    46      |      |      |       |      | | |   transfer.  This  includes   all   cases  of   the |
    47      |      |      |       |      | | |   controller's  timeout  expiring  for  a  transfer |
    48      |      |      |       |      | | |   operation (level 1 real time command).            |
    49      +------+------+-------+------+-+-+-----------------------------------------------------+

                                                        
                                         *** RESTRICTED DISTRIBUTION ***
           Digital Equipment Corporation                                  Confidential And Proprietary
           Mass Storage Control Protocol                                                 Version 2.4.0
           STATUS AND EVENT CODE DEFINITIONS                                                 Page B-15
                                                                                          11 June 1992



     1                   Table B-8: "Drive Error" Status or Event Subcode Values (cont.)

     2      +------+---------------------+-+-+-----------------------------------------------------+
     3      | Sub- |   Code + Subcode    |E|S|                                                     |
     4      | code +------+-------+------+V|T|     Status or Event Subcode                         |
     5      |      | Dec. |  Oct. | Hex. | | |                                                     |
     6      +------+------+-------+------+-+-+-----------------------------------------------------+
     7      |    7 |  235 |   353 |   EB |*|*| Drive detected error.                               |
     8      |      |      |       |      | | |   For  SI  drives, the  controller  received  a Get |
     9      |      |      |       |      | | |   Status  or Unsuccessful response with the EL flag |
    10      |      |      |       |      | | |   set,  or  the controller received such a response |
    11      |      |      |       |      | | |   with  the  DR  flag  set  and it does not support |
    12      |      |      |       |      | | |   automatic diagnosis for that drive type.          |
    13      +------+------+-------+------+-+-+-----------------------------------------------------+
    14      |    8 |  267 |   413 |  10B |*|*| Controller detected pulse or state parity error.    |
    15      |      |      |       |      | | |   For  SI drives, the  controller detected  a pulse |
    16      |      |      |       |      | | |   error  on  either  the  state or data line or the |
    17      |      |      |       |      | | |   controller  detected  a  parity  error in a state |
    18      |      |      |       |      | | |   frame.                                            |
    19      +------+---------------------+-+-+-----------------------------------------------------+
    20      |   10 |  331 |   513 |  14B |*|*| Controller detected protocol error.                 |
    21      |      |      |       |      | | |   For  SI drives, a level 2 response from the drive |
    22      |      |      |       |      | | |   had  correct  framing codes and checksum, but was |
    23      |      |      |       |      | | |   not  a  valid  response within the constraints of |
    24      |      |      |       |      | | |   the  SI  protocol.  That  is, the response had an |
    25      |      |      |       |      | | |   invalid  opcode, was  an  improper length, or was |
    26      |      |      |       |      | | |   not  a  possible  response  in the context of the |
    27      |      |      |       |      | | |   exchange.                                         |
    28      +------+------+-------+------+-+-+-----------------------------------------------------+
    29      |   11 |  363 |   553 |  16B |*|*| Drive failed initialization.                        |
    30      |      |      |       |      | | |   For  SI  drives, the  drive  clock did not resume |
    31      |      |      |       |      | | |   following  a controller attempt to initialize the |
    32      |      |      |       |      | | |   drive.  This implies that the drive encountered a |
    33      |      |      |       |      | | |   fatal initialization error.                       |
    34      +------+------+-------+------+-+-+-----------------------------------------------------+
    35      |   12 |  395 |   613 |  18B |*|*| Drive ignored initialization.                       |
    36      |      |      |       |      | | |   For  SI  drives, the  drive  clock  did not cease |
    37      |      |      |       |      | | |   following  a controller attempt to initialize the |
    38      |      |      |       |      | | |   drive.  This  implies  that  the  drive  did  not |
    39      |      |      |       |      | | |   recognize the initialization attempt.             |
    40      +------+------+-------+------+-+-+-----------------------------------------------------+
    41      |   13 |  427 |   653 |  1AB |*|*| Receiver Ready collision.                           |
    42      |      |      |       |      | | |   For SI drives, the controller attempted to assert |
    43      |      |      |       |      | | |   its  Receiver  Ready (to  receive a response) and |
    44      |      |      |       |      | | |   the drive's Receiver Ready was still asserted (to |
    45      |      |      |       |      | | |   receive a command).                               |
    46      +------+------+-------+------+-+-+-----------------------------------------------------+



                                                        
                                         *** RESTRICTED DISTRIBUTION ***
           Digital Equipment Corporation                                  Confidential And Proprietary
           Mass Storage Control Protocol                                                 Version 2.4.0
           STATUS AND EVENT CODE DEFINITIONS                                                 Page B-16
                                                                                          11 June 1992


     1              Table B-9:  "Bad Block Replacement Completion" Event Only Subcode Values

     2      +------+---------------------+---------------------------------------------------------+
     3      | Sub- |   Code + Subcode    |                                                         |
     4      | code +------+-------+------+         Event Subcode                                   |
     5      |      | Dec. |  Oct. | Hex. |                                                         |
     6      +------+------+-------+------+---------------------------------------------------------+
     7      |    0 |   20 |    24 |   14 | Bad block successfully replaced.                        |
     8      +------+------+-------+------+---------------------------------------------------------+
     9      |    1 |   52 |    64 |   34 | Block verified OK; not a bad block.                     |
    10      +------+------+-------+------+---------------------------------------------------------+
    11      |    2 |   84 |   124 |   54 | Replacement  failure;  REPLACE  command or its analogue |
    12      |      |      |       |      | failed.                                                 |
    13      +------+------+-------+------+---------------------------------------------------------+
    14      |    3 |  116 |   164 |   74 | Replacement failure; inconsistent RCT.                  |
    15      +------+------+-------+------+---------------------------------------------------------+
    16      |    4 |  148 |   224 |   94 | Replacement failure; drive access failure.              |
    17      |      |      |       |      |   One  or  more  transfers specified by the replacement |
    18      |      |      |       |      |   algorithm failed.                                     |
    19      +------+------+-------+------+---------------------------------------------------------+
    20      |    5 |  180 |   264 |   B4 | Replacement failure; no replacement block available.    |
    21      |      |      |       |      |   Replacement  was  attempted  for  a  bad block, but a |
    22      |      |      |       |      |   replacement  block  could  not  be  allocated  (i.e., |
    23      |      |      |       |      |   the volume's RCT is  full).                           |
    24      +------+------+-------+------+---------------------------------------------------------+
    25      |    6 |  212 |   324 |   D4 | Replacement failure; recursion failure.                 |
    26      |      |      |       |      |   Two successive RBNs were bad.                         |
    27      +------+------+-------+------+---------------------------------------------------------+



    28                  Table B-10:  "Media Loader Error" Status or Event Subcode Values

    29      +------+---------------------+-+-+-----------------------------------------------------+
    30      | Sub- |   Code + Subcode    |E|S|                                                     |
    31      | code +------+-------+------+V|T|     Status or Event Subcode                         |
    32      |      | Dec. |  Oct. | Hex. | | |                                                     |
    33      +------+------+-------+------+-+-+-----------------------------------------------------+
    34      |    1 |   55 |   67  |   37 |*|*| Loader command time out                             |
    35      +------+------+-------+------+-+-+-----------------------------------------------------+
    36      |    2 |   87 |  127  |   57 |*|*| Controller detected transmission error              |
    37      +------+------+-------+------+-+-+-----------------------------------------------------+
    38      |    3 |  119 |  167  |   77 |*|*| Controller detected protocol error                  |
    39      +------+------+-------+------+-+-+-----------------------------------------------------+
    40      |    4 |  151 |  227  |   97 |*|*| Loader detected error                               |
    41      +------+------+-------+------+-+-+-----------------------------------------------------+





                                                        
                                         *** RESTRICTED DISTRIBUTION ***
           Digital Equipment Corporation                                  Confidential And Proprietary
           Mass Storage Control Protocol                                                 Version 2.4.0
           STATUS AND EVENT CODE DEFINITIONS                                                 Page B-17
                                                                                          11 June 1992


     1                       Table B-11:  "Informational" Event Only Subcode Values

     2      +------+---------------------+---------------------------------------------------------+
     3      | Sub- |   Code + Subcode    |                                                         |
     4      | code +------+-------+------+         Event Subcode                                   |
     5      |      | Dec. |  Oct. | Hex. |                                                         |
     6      +------+------+-------+------+---------------------------------------------------------+
     7      |   1  |   54 |   66  |   36 | Media Quality log                                       |
     8      +------+------+-------+------+---------------------------------------------------------+
     9      |   2  |   86 |  126  |   56 | Unload / Spin down statistics                           |
    10      +------+------+-------+------+---------------------------------------------------------+
    11      |   3  | 118  |  166  |  76  | Disk Copy Data Correlation                              |
    12      +------+------+-------+------+---------------------------------------------------------+


    13                   Table B-12:  "Subcommand Error" Status or Event Subcode Values

    14      +------+---------------------+-+-+-----------------------------------------------------+
    15      | Sub- |   Code + Subcode    |E|S|                                                     |
    16      | code +------+-------+------+V|T|     Status or Event Subcode                         |
    17      |      | Dec. |  Oct. | Hex. | | |                                                     |
    18      +------+------+-------+------+-+-+-----------------------------------------------------+
    19      | 1024 |      Destination/source flag bit: 0=Destination, 1=Source                     |
    20      +------+------+-------+------+-+-+-----------------------------------------------------+
    21      |    1 |   62 |    76 |   3E |*|*| Destination -- command timed out                    |
    22      +------+------+-------+------+-+-+-----------------------------------------------------+
    23      | 1025 |32830 |100076 | 803E |*|*| Source -- command timed out                         |
    24      +------+------+-------+------+-+-+-----------------------------------------------------+
    25      |    2 |   94 |   136 |   5E |*|*| Destination -- inconsistent state                   |
    26      +------+------+-------+------+-+-+-----------------------------------------------------+
    27      | 1026 |32862 |100136 | 805E |*|*| Source -- inconsistent state                        |
    28      +------+------+-------+------+-+-+-----------------------------------------------------+
    29      |    4 |  158 |   236 |   9E |*|*| Destination -- unrecoverable error                  |
    30      +------+------+-------+------+-+-+-----------------------------------------------------+
    31      | 1028 |32926 |100236 | 809E |*|*| Source -- unrecoverable error                       |
    32      +------+------+-------+------+---------------------------------------------------------+















                                                        
                                         *** RESTRICTED DISTRIBUTION ***
           Digital Equipment Corporation                                  Confidential And Proprietary
           Mass Storage Control Protocol                                                 Version 2.4.0
           STATUS AND EVENT CODE DEFINITIONS                                                 Page B-18
                                                                                          11 June 1992


     1  |                  Table B-13:  "Cache Error" Status or Event Subcode Values

     2  |   +------+---------------------+-+-+-----------------------------------------------------+
     3  |   | Sub- |   Code + Subcode    |E|S|                                                     |
     4  |   | code +------+-------+------+V|T|     Status or Event Subcode                         |
     5  |   |      | Dec. |  Oct. | Hex. | | |                                                     |
     6  |   +------+------+-------+------+-+-+-----------------------------------------------------+
     7  |   | many |      |       |      |*|*| "Data Error"                                        |
     8  |   |      For every "Data Error" subcode that may be reported as a status code (i.e., for |
     9  |   |      every subcode listed in Table B-5, "Data Error" Status or Event Subcode Values, |
    10  |   |      that has an asterisk in the "ST" column), the exact same subcode value may be   |
    11  |   |      returned as a "Cache Error" subcode value. These subcodes indicate that a       |
    12  |   |      transfer to the unit's cache failed for the specified reason. For example, the  |
    13  |   |      subcode value 7 (combined code and subcode value of 249 decimal) indicates that |
    14  |   |      the cache block accessed is unreadable due to an Uncorrectable ECC Error.       |
    15  |   |                                                                                      |
    16  |   |      In addition to the subcode values copied from "Data Error" subcode values, the  |
    17  |   |      subcodes listed below also exist.                                               |
    18  |   +------+------+-------+------+-+-+-----------------------------------------------------+
    19  |   |    4 |  153 |   231 |   99 |*| | Cache Disabled                                      |
    20  |   |      |      |       |      | | |   The controller has determined that the ability of |
    21  |   |      |      |       |      | | |   the cache to maintain data integrity is in        |
    22  |   |      |      |       |      | | |   question. Therefore, the cache has been disabled. |
    23  |   |      |      |       |      | | |   Note that before the cache is disabled, a cache   |
    24  |   |      |      |       |      | | |   flush operation is performed.                     |
    25  |   +------+------+-------+------+-+-+-----------------------------------------------------+
    26  |   |    5 |  185 |   271 |   B9 |*|*| Cache Detected Error                                |
    27  |   |      |      |       |      | | |   For controller internal caches, the controller    |
    28  |   |      |      |       |      | | |   received an unsuccessful response from the cache, |
    29  |   |      |      |       |      | | |   indicating a hardware error.                      |
    30  |   +------+------+-------+------+-+-+-----------------------------------------------------+
    31  |   |    6 |  217 |   331 |   D9 |*|*| Hardware Port Error                                 |
    32  |   |      |      |       |      | | |   The controller received an unsuccessful response  |
    33  |   |      |      |       |      | | |   from the device port, used as a cache, indicating |
    34  |   |      |      |       |      | | |   a hardware error.                                 |
    35  |   +------+------+-------+------+-+-+-----------------------------------------------------+















                                                        
                                         *** RESTRICTED DISTRIBUTION ***
