{
{       CM4106 - 9836, 9853, 5832_1, 5832_2,
{                5833_1, 5833_1P, 5833_2, 5833_3P, 5833_4,
{                5837_1, 5837_1P, 5837_2, 5837_3P, 5837_4,
{                5838_1, 5838_1P, 5838_2, 5838_3P, 5838_4,
{                47444_1, 47444_1p, 47444_2, 47444_3p,
{                47444_4 subsystem failure data.
{
{ PURPOSE:
{    The purpose of this statistic is to record the failure data
{ captured by the system when accessing the subsystem.
{
{ FREQUENCY: At each failure occurrence.
{
{ CONTENT:
{    The descriptive data portion of this statistic contains:
{
{    '<mf>.<iou>.<pp>.<ch>.<cm>.<unit>*<vsn>*<class>*<message>'
{
{      Where  <mf> is the identification of the mainframe in the form
{        $SYSTEM_mmmm_ssss.  Where 'mmmm'  is  the  model  number  of
{        Central  Processor zero (CP0), e.g.  0990, and 'ssss' is the
{        serial number of that processor, e.g.  0104.
{
{      Where <iou> is the string 'IOUn' where n  is  0  or  1.   This
{        identifies  the  IOU  associated with the channel over which
{        the failure was reported.
{
{      Where <pp> is the string 'CPPn' for an I4 or the string  'PPn'
{        for an I0.  The character n is the PP number (in decimal) of
{        the PP which performed the  i/o  operation  which  is  being
{        reported.   Note  that  CPP  is the designation given to the
{        concurrent channels in an I4 IOU.
{
{      Where <ch> is the string 'CCHnp' for an I4 or 'CHn' for an I0.
{        The character n is the decimal representation of the channel
{        and p is the I4 channel port (A or B) through which the disk
{        device was accessed.  Note that CCH is the designation given
{        to the concurrent channels in the I4 IOU.
{
{      Where <cm> is the element name  of  the  disk  control  module
{        (controller) used in the failing request.
{
{      Where <unit> is the element name of the failing  disk  storage
{        device used in the failing request.
{
{      Where  <vsn>  is the recorded-vsn of the disk volume which was
{        the object of the failing request.
{
{      Where <class> is the string 'UF'  for  unrecovered,  'RF'  for
{        recovered,  'IF'  for  intermediate and 'IM' for informative
{        message.
{
{           The PP reports failure data as  an  intermediate  failure
{        log entry prior to retrying an i/o request.  An intermediate
{        failure log  entry  will  provide  the  first  failure  data
{        captured by the PP during the initial attempt at the request
{        or during a subsequent request retry.  If a retry of an  i/o
{        request  is  successful, no additional log entries are made.
{        Results of diagnostics executed  as  part  of  the  recovery
{        algorithm  will  also be reported as an intermediate failure
{        log entry.
{
{           A  recovered  failure  log  entry will be reported if the
{        controller reports  conditional  success  to  the  PP.  This
{        means that the controller recovery algorithm enabled  by the
{        PP recovered the error without PP intervention.  The counter
{        values  for  a  recovered failure contain  the first failure
{        data captured by the PP.
{
{           For unrecovered disk failures the counter values  contain
{        the failure data when all recovery attempts have failed.
{
{      Where  <message>  is a statement of failure isolation based on
{        either  diagnostic  execution  or  status  reported  by  the
{        subsystem.  The text of  the possible symptom statements are
{        identical  in content to the upper case text described under
{        counter value 8 below.
{
{    The counter-value portion of this statistic contains:
{
{   1.  Physical PP number
{       Bits 58 - 63 contain the physical PP number.
{       Bit 57 is set to 1 for an I4 concurrent PP.
{       Bits 46 - 51 contain the IOU number.
{
{   2.  Channel number
{       Bits 58-63 contain the channel number.
{       Bit 57 is set to 1 for an I4 concurrent channel.
{       Bit 56 is set to 1 if I4 concurrent channel port B.
{       Bit 55 is set to 1 if I4 concurrent channel port A.
{       Bits 46 - 51 contain the IOU number.
{
{   3.  Controller number
{
{   4.  Physical drive number
{
{   5.  Unit type
{       7 - 9836_1 (S0 only)
{       8 - 9853_X
{       9 - 5832_1
{      10 - 5832_2
{      11 - 5833_1
{      12 - 5833_1P
{      13 - 5833_2
{      14 - 5833_3P
{      15 - 5833_4
{      16 - 5838_1
{      17 - 5838_1P
{      18 - 5838_2
{      19 - 5838_3P
{      20 - 5838_4
{      21 - 47444_1
{      22 - 47444_1P
{      23 - 47444_2
{      24 - 47444_3P
{      25 - 47444_4
{      26 - 5837_1
{      27 - 5837_1P
{      28 - 5837_2
{      29 - 5837_3P
{      30 - 5837_4
{
{   6.  Logical operation code
{       1 - read
{       2 - write
{       5 - format
{
{   7.  Log entry class
{       0 - Recovered Failure Report
{       1 - Unrecovered Failure Report
{       2 - Intermediate Failure Report
{       3 - Informative Message
{     Bits 33-47 contain an isolation  code  generated  by  the  PP
{             driver when bits 48-63 equal 1.
{       0 - Media Failure
{             This  is  present  when counter word 8 has a value of
{             62.  The confidence test had to pass to get  a  media
{             failure.
{       1 - Channel failure
{             A  failure  is isolated to the channel if it occurred
{             during  the  test  mode  (I4   only)  portion  of the
{             confidence  test  or  counter word 8 has a value less
{             than 20.
{       2 - Controller failure
{             A  failure  is  isolated  to  the  controller  if  it
{             occurred   during  the PP/Controller  path  test  or
{             counter word 8 has a value of 20-49.
{       3 - Drive failure
{             This code is set if the  failure  is  isolated  to  a
{             drive  and  there  is no parity drive for the logical
{             unit or the second  drive  of  a  logical  unit  with
{             parity  failed.   A  failure that was not isolated to
{             media, the channel, or the controller  is  attributed
{             to  the  drive.   Counter  word  8 has a value of 61,
{             70-99, or 120-130 for a drive failure.
{       4 - Drive failure causing parity protection to be disabled
{             This code is set if the  failure  is  isolated  to a
{             single  drive  of  a  parity  protected logical unit.
{             Counter word 8 has a value of 61, 70-99,  or  120-130
{             for  a  drive  failure.   This   error   should   be
{             recoverable  when  the  failing  drive of the logical
{             unit with a parity drive is disabled.
{
{   8.  Failure Analysis
{       This indicates the extent to which the subsystem, the PP, and
{       the CP were able to isolate the failure when it was detected.
{       The symptom  messages  have  been  grouped  to  help  provide
{       failure  isolation.   For  an  unrecovered  failure, detailed
{       isolation, equivalent  to  that  displayed  to  the  critical
{       window,  is provided in counter word 7.  Symptom codes 53-59,
{       106, and 130-142 are only  returned  for  a  5830  subsystem.
{       Symptom codes 77, 95 and 121  are  only  returned  by the CM3
{       subsystem.  Symptom  code  19  is only returned for a 25 MB/s
{       channel. All other symptom codes could be returned for either
{       subsystem or either channel.
{
{       0 - INDETERMINATE           The   failure  did  not  manifest
{                                   itself as one  of  the  following
{                                   symptoms.   Refer to the Response
{                                   Packet       for       additional
{                                   information.
{
{         The  following  symptom statements are isolated to the IOU.
{       They can not be caused by either the controller or the  cable
{       between  the  PP  and  controller.   Counter  words  1-9  and
{       referenced words are  applicable  to  the  following  symptom
{       statements.
{
{       1 - FUNCTION TIMEOUT        The IPI channel did  not  respond
{                                   to  a  function.  Counter word 18
{                                   contains the function.
{
{       2 - CHANNEL EMPTY WHEN ACTIVATED  The  IPI  channel  did  not
{                                   force  the  channel  full when it
{                                   was activated.
{
{       3 - PERIOD COUNTER ERROR    This is bit 12 of the IPI channel
{                                   error register.
{
{       4 - PP - IPI PARITY ERROR   This is bit 5 or  6  of  the  IPI
{                                   channel    error   register   and
{                                   indicates that a parity error has
{                                   occurred on a byte of information
{                                   transferred between the IPI  chip
{                                   in the IOU and the PP.
{
{       6 - IOU ERROR               The channel error flag is set and
{                                   none  of  the  bits  in  the  IPI
{                                   channel  error register or I4 IPI
{                                   DMA error register are set.
{
{       7 - INCOMPLETE I4 TRANSFER  The PP's A register  was  nonzero
{                                   after   an  output  of  parameter
{                                   words.
{
{       8 - CHANNEL NOT EMPTY       The I4 channel did not  go  empty
{                                   after  the  output  of  parameter
{                                   words.
{
{       9 - CENTRAL MEMORY ERROR    This indicates that bit 12 or  13
{                                   of  the I4 IPI DMA error register
{                                   is set and that an uncorrected or
{                                   reject    error    response   was
{                                   received from central memory.
{
{       10 - INVALID CM RESPONSE CODE  This  is  bit 11 of the I4 IPI
{                                   DMA error register and  indicates
{                                   the  response  code  from central
{                                   memory decoded  into  an  illegal
{                                   value.
{
{       11 - CM RESPONSE CODE ERROR  This is bit 10 of the I4 IPI DMA
{                                   error   register   and  indicates
{                                   that  the  response   code   from
{                                   central memory had a parity error.
{
{       12 - CMI READ DATA PARITY ERROR  This is bit 9  of the I4 IPI
{                                   DMA error register and  indicates
{                                   that the central memory interface
{                                   logic has detected  a  read  data
{                                   parity error.
{
{       13 - Y BOARD DATA ERROR     This  is bit 4  of the I4 IPI DMA
{                                   error register and indicates that
{                                   the  Y  board has detected a data
{                                   parity error.
{
{       14 - BAS PARITY ERROR       This is bit 3  of the I4 IPI  DMA
{                                   error register and indicates that
{                                   the   X  board  has  detected   a
{                                   parity  error  on  data  received
{                                   from the barrel and slot  of  the
{                                   PP.
{
{       15 - Z BOARD ERROR          This  is bit 2  of the I4 IPI DMA
{                                   error register and indicates that
{                                   the   Z  board  has  detected  an
{                                   error.  The Z board has  the  IPI
{                                   channel chip.
{
{       16 - Y BOARD  ERROR         This is bit 1  of the I4 IPI  DMA
{                                   error register and indicates that
{                                   the   Y  board  has  detected  an
{                                   error.
{
{       17 - X BOARD ERROR          This  is bit 0  of the I4 IPI DMA
{                                   error register and indicates that
{                                   the   X  board  has  detected  an
{                                   error.
{
{       18 - DMA TEST MODE FAILURE  Test mode was used to  pass  data
{                                   through  the  adapter.   No  bits
{                                   were set in the I4 IPI channel or
{                                   I4  IPI  DMA error registers, but
{                                   the data was incorrect.
{
{
{       19 - DMA COUNT OVERFLOW     This  is  bit  15  of the IPI DMA
{                                   error register and indicates that
{                                   the IPI chip received more than 4
{                                   data requests from the Y board.
{
{         The  following  symptom  statements  are  most   likely   a
{       controller problem but may be caused by the IOU, IPI channel,
{       or  cable.   Counter  words  1-9  and  referenced  words  are
{       applicable for the following symptom statements.
{
{       20 - CAN NOT SELECT CONTROLLER  The  SLAVE  IN  line  was not
{                                   set  after the PP sent the select
{                                   code to the controller.
{
{       21 - BIT SIGNIFICANT RESPONSE   ERROR   The  bit  significant
{                                   response which  is  in  bits  0-7
{                                   of   the   IPI   channel   status
{                                   register is incorrect.
{
{       22 - NO SYNC IN             During  a  bus  control  sequence
{                                   SYNC IN did not set.
{
{       23 - SYNC IN DID NOT DROP   During  a  bus  control  sequence
{                                   SYNC IN did not drop.
{
{       24 - IPI SEQUENCE ERROR     This is bit 4  of the IPI channel
{                                   error  register  and indicates an
{                                   illegal   sequence   of   control
{                                   signals  has  occurred on the IPI
{                                   interface.
{
{       25 - IPI CHANNEL PARITY ERROR This is bit  2 or 3 of the  IPI
{                                   channel    error   register   and
{                                   indicates that  the  IPI  channel
{                                   has  detected  a  parity error on
{                                   bus A of the IPI interface.
{
{       27 - SLAVE IN NOT SET       During an ending status  sequence
{                                   or  a  request  transfer settings
{                                   sequence SLAVE IN did not set.
{
{       28 - SLAVE IN DID NOT DROP  During a deselect sequence  or  a
{                                   request     transfer     settings
{                                   sequence SLAVE IN did not drop.
{
{       29 - INCOMPLETE TRANSFER    Not all  words  were  transferred
{                                   when the channel was inactivated.
{                                   Status from the controller didn't
{                                   indicate  an error.  Refer to the
{                                   Residual Word  count  in  counter
{                                   word  17  to  see how many 16-bit
{                                   words were not transferred.
{
{       30 - CHANNEL STAYED ACTIVE  Following an information exchange
{                                   the controller did not drop SLAVE
{                                   IN.   The  controller drops SLAVE
{                                   IN when the last  word  has  been
{                                   transferred  or  if no words have
{                                   been transferred for its  timeout
{                                   limit of about 26 milliseconds.
{
{       31 - BUFFER COUNTER ERROR   This is bit 15 of the IPI channel
{                                   error register.
{
{       32 - SYNC COUNTER ERROR     This is bit 13 of the IPI channel
{                                   error register.
{
{       33 - LOST DATA              This is bit 7  of the IPI channel
{                                   error   register.   It  indicates
{                                   that the  controller ended a data
{                                   transfer  and  the  IPI channel's
{                                   buffer is not empty.
{
{       34 - BUS PARITY             This is bit 6  of  ending  status
{                                   received from the controller.  It
{                                   indicates  that  the   controller
{                                   detected a parity  error  on  the
{                                   IPI  interface.  Ending status is
{                                   right  justified  in counter word
{                                   19.
{
{       35 - COMMAND REJECT         This is reported in bits  0-3  of
{                                   ending  status  received from the
{                                   controller.   If a value of 2, 3,
{                                   6, or 8 is  in  these  bits,  the
{                                   controller   has   rejected   the
{                                   command sent by the  PP.   Ending
{                                   status   is  right  justified  in
{                                   counter word 19.
{
{       36 - SYNC OUTS NOT EQUAL SYNC INS  This is reported  in  bits
{                                   0-3  of  ending  status  received
{                                   from the  controller.   If  these
{                                   bits  have  a  value  of  9,  the
{                                   controller's SYNC OUT  count  and
{                                   its  SYNC IN count were not equal
{                                   when the transfer ended.   Ending
{                                   status   is  right  justified  in
{                                   counter word 19.
{
{       37 - BUS B ACKNOWLEDGE INCORRECT   During   a   bus   control
{                                   sequence bus B received from  the
{                                   controller was nonzero.  Bus B is
{                                   in  the  right-most 8 bits of the
{                                   IPI channel status register.
{
{       38 - NO CONTROLLER RESPONSE  A command  or  a  state sequence
{                                   sent  to  the  controller was not
{                                   responded to within the  allotted
{                                   time.
{
{       39 - ENDING STATUS WRONG    This   is   reported  if  bit  7,
{                                   indicating  successful,  was  not
{                                   set  in  ending  status  from the
{                                   controller  and  bits  in  ending
{                                   status  did not isolate to a code
{                                   of 34, 35,  36,  or  70.   Ending
{                                   status  is  right  justified  in
{                                   counter word 19.
{
{         The  following  symptom statements are informative and will
{       have counter word 7 set to a value of 3.  Counter  words  1-9
{       are applicable  for  symptom  statements  50-52.  All counter
{       words, except 17-23, are applicable for the remaining symptom
{       statements.
{
{       50 - EXECUTING CONTROLLER DIAGNOSTICS  Execution  of a  power
{                                   on  (slave)  reset  seequence was
{                                   initiated. This causes controller
{                                   diagnostics to be executed.
{
{       51 - CONTROLLER DIAGNOSTICS PASSED   The controller self-test
{                                   diagnostic  portion  of the power
{                                   on reset completed without error.
{                                   Also, during  recovery  for  this
{                                   request,   the    message     'NO
{                                   CONTROLLER  RESPONSE'   was   not
{                                   reported.
{
{       52 - CONTROLLER DIAGNOSTICS PASSED - LAST ERROR CODE IS XXXX
{                                   the  controller self-test portion
{                                   of the power on  reset  completed
{                                   without  error.   Also a previous
{                                   error   message   indicated    NO
{                                   CONTROLLER RESPONSE.   This means
{                                   that  the   controller   probably
{                                   wrote  error   status   into  its
{                                   EEPROM, displayed an  error  code
{                                   on  its 2-digit error display and
{                                   stopped  communicating  with  the
{                                   PP.
{
{       53 - CONTROLLER ALTERNATE PORT EVENT  The controller detected
{                                   an error from its alternate port.
{                                   Reference parameter ID 15 in  the
{                                   response    packet    for    more
{                                   information.
{
{       54 - DRIVE ALTERNATE PORT EVENT  The drive detected  an event
{                                   from    its     alternate   port.
{                                   Reference parameter ID 25 in  the
{                                   response    packet    for    more
{                                   information.
{
{       55 - RESTORING DRIVE        The restore of a  physical  drive
{                                   in a logical unit with parity has
{                                   been initiated.
{
{       56 - DRIVE RESTORATION COMPLETE  The restore  of  a  physical
{                                   drive  in  a  logical  unit  with
{                                   parity  has   completed   without
{                                   error.
{
{       57 - FORMATTING DRIVE       The  PP  driver  has initiated an
{                                   initial format of an HDA.
{
{       58 - FORMAT COMPLETE        The  format   of   an   HDA   has
{                                   completed successfully.
{
{       59 - PARITY PROTECTION DISABLED  An error was isolated  to  a
{                                   drive.  The logical  unit  had  a
{                                   parity  drive  and  the   failing
{                                   drive was off lined.
{
{         The  following  symptom  statements  are  returned  when  a
{       diagnostic  isolated  an  error.   All  counter words, except
{       17-23, are applicable for the following symptom statements.
{
{       61 - DRIVE FAILURE          Drive diagnostics were run and an
{                                   error   occurred.    A   response
{                                   packet  with  parameter   ID   23
{                                   contains  more  information.   If
{                                   the response packet  contains  an
{                                   error  code,  it  will  be put in
{                                   counter word 10.
{
{       62 - MEDIA FAILURE          This    indicates     that     an
{                                   uncorrectable  media  defect  has
{                                   developed on the media surface or
{                                   there    is    a    less   likely
{                                   possibility  that  there  was  an
{                                   intermittent  failure  when   the
{                                   sector   was  originally  written
{                                   which was not detected until  the
{                                   subsequent  read.  The confidence
{                                   test successfully wrote, read and
{                                   verified   data   on  a  cylinder
{                                   reserved  for  maintenance.   The
{                                   storage device is not DOWNed as a
{                                   result  of   a   media   failure.
{                                   NOS/VE     will     automatically
{                                   software  flaw  this  bad   spot.
{                                   Reference  the  section on Volume
{                                   Defect   Management   for    more
{                                   information.
{
{         The  following symptom statements are most likely caused by
{       the  controller.   However, if slave reset is successful, and
{       all retries are unsuccessful, the  PP  driver  assumes  these
{       symptom  statements  are  caused  by  the drive.  All counter
{       words, except 17-23, are applicable for the following symptom
{       statements.
{
{       70 - LRC ERROR              Data was read from disk into  the
{                                   5831  controller  buffer  without
{                                   error, then either  a  transverse
{                                   parity  error  occurred,  or  the
{                                   longitudinal    redundancy   code
{                                   generated  by  the controller for
{                                   the data sent to the host did not
{                                   match  the  one  read.   This  is
{                                   reported  when  ending status has
{                                   a  code of 0B hex.  Ending status
{                                   is  right-justified   in  counter
{                                   word 19.
{
{       71 - CONTROLLER INTERVENTION REQUIRED   The   controller   is
{                                   unable  to  execute  commands and
{                                   some  intervention  is  required.
{                                   Reference parameter ID 14 in  the
{                                   response    packet    for    more
{                                   information.
{
{       72 - CONTROLLER MACHINE EXCEPTION  A  machine  exception  was
{                                   detected   in   the   controller.
{                                   Reference parameter ID 16 in  the
{                                   response    packet    for    more
{                                   information.
{
{       73 - COMMAND EXCEPTION      The command  packet  received  by
{                                   the  controller   had   incorrect
{                                   values, was too short, or did not
{                                   contain all required  parameters.
{                                   Reference  parameter ID 17 of the
{                                   response    packet    for    more
{                                   information.
{
{       74 - MICROCODE EXECUTION ERROR  The controller encountered an
{                                   error in its own microcode during
{                                   execution.   This  is bit 3, byte
{                                   1, of parameter   ID  13  in  the
{                                   response packet.
{
{       76 - UNEXPECTED RESPONSE    Either a response packet from the
{                                   controller   indicated   transfer
{                                   notification when  there  was  no
{                                   data  to transfer or the response
{                                   packet indicated command complete
{                                   when   there  was  more  data  to
{                                   transfer.
{
{       77 - DRIVE RESERVED TO OTHER CONTROLLER  PORT  The  drive  is
{                                   reserved to the redundant port of
{                                   the CM3.   This is bit 3, byte 5,
{                                   of  parameter  ID   17   in   the
{                                   response  packet.   For  the 5831
{                                   controller it is not possible  to
{                                   tell  whether the reserve is held
{                                   by another controller or  another
{                                   port,  so  symptom 89 is returned
{                                   for both.
{
{       78 - CONTROLLER OVER TEMPERATURE  This is an early warning of
{                                   a   controller  over  temperature
{                                   condition.
{
{         The following symptom statements are most likely caused  by
{       the  drive.   All counter words, except 17-23, are applicable
{       for the following symptom statements.
{
{       80 - DRIVE NOT OPERATIONAL  The drive  is  not  present,  not
{                                   powered  on,  or  not responding.
{                                   Reference parameter ID 24  in the
{                                   response    packet    for    more
{                                   information.
{
{       81 - DRIVE NOT READY        This  usually  means the drive is
{                                   not  spinning.   The  PP   driver
{                                   automatically  attempts  to power
{                                   up the spindle if this status  is
{                                   detected.  If the start switch is
{                                   not depressed, the power up  will
{                                   be    unsuccessful   and   manual
{                                   intervention  will  be  required.
{                                   Reference parameter ID 24  in the
{                                   response    packet    for    more
{                                   information.
{
{       82 - DRIVE INTERVENTION REQUIRED The drive is powered on  and
{                                   ready   but   unable  to  execute
{                                   commands.  Reference parameter ID
{                                   24  in  the  response  packet for
{                                   more information.
{
{       85 - UNCORRECTABLE DATA CHECK The controller detected a  data
{                                   error  and  all retries have been
{                                   exhausted.  This is bit  6,  byte
{                                   2,  of  parameter  ID 26  in  the
{                                   response packet.
{
{       86 - DRIVE FATAL ERROR      The drive  detected  an  internal
{                                   machine   error   that  precludes
{                                   execution or continuation of  the
{                                   current    command.     Reference
{                                   parameter ID 26  in  the response
{                                   packet for more information.
{
{       87 - HARDWARE WRITE PROTECTED An attempt was made to write on
{                                   a write protected drive.  This is
{                                   bit 4, byte 2, of parameter ID 26
{                                   in the response packet.
{
{       89 - DRIVE RESERVED TO OTHER CONTROLLER  For a CM3 controller
{                                   this  indicates that the drive is
{                                   reserved  to  another controller.
{                                   For  a  5831 controller it is not
{                                   possible  to  tell  whether   the
{                                   reserve   is   held   by  another
{                                   controller or the other  port  of
{                                   the  controller.   For  the  5831
{                                   controller it indicates the drive
{                                   is reserved through another path.
{                                   This  is  bit  1,  byte   1,   of
{                                   parameter  ID  24 in the response
{                                   packet.
{
{       91 - DRIVE ECC ERROR        Hardware detected an ECC error in
{                                   a header.  This is returned when
{                                   command   ending   status   from
{                                   parameter  ID  26 of the response
{                                   packet has a value of XX11 hex.
{
{       92 - MISSING SYNC OCTET ON DRIVE The drive failed to find the
{                                   sync  octet  for a header or data
{                                   field.   This  is  returned  when
{                                   command    ending   status   from
{                                   parameter ID 26 of  the  response
{                                   packet has a value of XX13 hex.
{
{       93 - SECTOR NOT FOUND       The correct sector for a write or
{                                   read could not be found.  This is
{                                   returned   when   command  ending
{                                   status from parameter  ID  26  of
{                                   the response packet has  a  value
{                                   of XX19 hex.
{
{       94 - DRIVE MACHINE EXCEPTION A machine exception was detected
{                                   in    the    drive.     Reference
{                                   parameter ID 26 in  the  response
{                                   packet for more information.
{
{       95 - NO UNIT OPERATIONAL RESPONSE  After  an Abort command or
{                                   after  a slave reset sequence, an
{                                   operational   response   was  not
{                                   received for the drive.
{
{       96 - DAS HEAD SHIFT WARNING A probable head  shift  condition
{                                   has   been   detected  by the DAS
{                                   microcode  while   running  drive
{                                   diagnostics.
{
{       97 - SSD BATTERY TOO LOW FOR BACKUP The battery voltage level
{                                   in the SSD is  to low  to support
{                                   backing up  the  SSD data  to the
{                                   back-up disk.
{
{       98 - SSD BATTERY TEST FAILED The SSD battery test has failed.
{                                   The battery should be replaced.

{       99 - SSD BATTERY OLD - REPLACE The SSD battery  is more  than
{                                   three years  old  or has operated
{                                   for more than 500 back-up cycles.
{                                   Replace the battery.
{
{         The  following  symptom  statements  are  returned  if  the
{       controller recovers an error without  intervention  from  the
{       PP.   Since  recovered errors are not displayed on the System
{       Console, these codes will only be found in  counter  word  8.
{       All  counter  words,  except  17-23,  are  applicable for the
{       following symptom statements.
{
{       100 - ERROR RETRY           The   controller   completed  the
{                                   command,   but  error  retry  was
{                                   required.  Error retry  does  not
{                                   include actions associated with a
{                                   data transfer.
{
{       101 - DATA RETRY            The  controller   completed  the
{                                   command,   but   data  retry  was
{                                   required.
{
{       102 - MOTION RETRY          The  controller   completed   the
{                                   command,  but  motion  retry  was
{                                   required.
{
{       103 - DATA CORRECTION       The  controller   completed   the
{                                   command,  but data correction was
{                                   required.
{
{       104 - SOFT ERROR            The   controller   detected    an
{                                   internal  machine  error that did
{                                   not   preclude    execution    or
{                                   continuation   of   the   current
{                                   command.
{
{       106 - PARITY DRIVE CORRECTION  The logical unit has a  parity
{                                   drive,  an  error occurred  on  a
{                                   read, and the  parity  drive  was
{                                   used to return correct data.
{
{         The  following  symptom  statements  are  returned  if  the
{       failure  could  not  be  isolated.   Counter  words  1-8  are
{       applicable.
{
{       110 - PP-CONTROLLER DATA INTEGRITY    Slave     reset     was
{                                   successful,  no  write  buffer or
{                                   read buffer errors were detected,
{                                   but data read from the controller
{                                   buffer   did   not   match   data
{                                   previously   written  during  the
{                                   PP/controller path test.
{
{       111 - CM-DRIVE DATA INTEGRITY All self-tests were successful,
{                                   no  write  or read command errors
{                                   were detected, but data read from
{                                   disk  to  central  memory did not
{                                   match the data previously written
{                                   during the confidence test.
{
{         The following symptom statement  is  most likely a software
{       failure, but may be caused by a hardware  error  in  the CPU.
{       Counter words 1, 2, 7 and 8 are applicable.
{
{       120 - SOFTWARE FAILURE      The  PP  found a value in a table
{                                   created  by  the  CP  in  central
{                                   memory to be incorrect.
{
{       121 - WRONG DRIVE TYPE      The  drive  type  defined  in the
{                                   physical  configuration  does not
{                                   match the actual drive type. This
{                                   is  only  returned  for  9836 and
{                                   9853 drives.
{
{         The following symptom statement code is usually caused by a
{       bad HDA.   If  counter  word  7  indicates  unrecovered,  the
{       recommended  action  is  to  try  an  initial format.  If the
{       initial format fails, the action is to replace the HDA.   All
{       counter words, except 17-23, are applicable for the following
{       symptom code.
{
{       130 - DEFECT MANAGEMENT TASK FAILED This is usually  returned
{                                   due  to  an  error  that occurred
{                                   when    formatting    the    HDA.
{                                   Reference  parameter  ID 12 or 22
{                                   in the response packet  for  more
{                                   information.
{         The following  symptom  statements  usually  occur  when  a
{       logical unit is configured the first time and it has not been
{       formatted and clusterred.  An initialize of the logical  unit
{       will usually  correct  the  problem.   Counter  words 1-9 and
{       24-40 are applicable.
{
{       140 - XXXX CONFIGURED - FOUND YYYY  The drive type defined in
{                                   the  physical  configuration does
{                                   not match the actual drive  type.
{                                   XXXX and YYYY are product numbers
{                                   for the drives.
{
{                                   Examples are as follows.
{
{        + ---------------+----------------+------------+
{        | type defined   |  actual drive  |  comment   |
{        +----------------+----------------+------------+
{        |   any 5833     |   any 5832     |   error    |
{        |   any 5833     |   any 5838     |   error    |
{        |   any 5838     |   any 5832     |   error    |
{        |   any 5838     |   any 5833     |   error    |
{        |   any 5832     |   any 5833     |   error    |
{        |   any 5832     |   any 5838     |   error    |
{        |   5833_1       | any other 5833 |   error *  |
{        |   5833_1P      | any other 5833 |   error *  |
{        |   5833_2       | any other 5833 |   error *  |
{        |   5833_3P      | any other 5833 |   error *  |
{        |   5833_4       | any other 5833 |   error *  |
{        |   5838_1       | any other 5838 |   error *  |
{        |   5838_1P      | any other 5838 |   error *  |
{        |   5838_2       | any other 5838 |   error *  |
{        |   5838_3P      | any other 5838 |   error *  |
{        |   5838_4       | any other 5838 |   error *  |
{        |   47444_1      | any other 47444|   error *  |
{        |   47444_1P     | any other 47444|   error *  |
{        |   47444_2      | any other 47444|   error *  |
{        |   47444_3P     | any other 47444|   error *  |
{        |   47444_4      | any other 47444|   error *  |
{        |   5832_1       |    5832_2      |   error ** |
{        |   5832_2       |    5832_1      |   error ** |
{        +----------------+----------------+------------+
{
{        *  If  the drive is being initialized, the operator is asked
{           to   confirm  the  need  to  change  the  logical  unit's
{           reconfiguration.     The  drive  will  be  formatted  and
{           clustered as necessary if the operator continues.
{       **  If  the drive is being initialized, the operator is asked
{           to   confirm  the  need  to  change  the  logical  unit's
{           reconfiguration.   The switch setting for the sector size
{           is  wrong.   The  configuration switch must be 17 hex for
{           the 5832_1 unit and must be hex 16 for the 5832_2 unit.
{
{       141 - DRIVE INITIALIZATION REQUIRED The drive is not properly
{                                   formatted   or   is  not properly
{                                   clustered.  The actual drive type
{                                   could  not be determined.  If the
{                                   drive is  being  initialized,  it
{                                   will automatically  be  formatted
{                                   and clustered as necessary.
{
{       142 - CONTROLLER DOES NOT SUPPORT PARALLEL      Either    the
{                                   controller  does  not  have   the
{                                   parallel option or the controller
{                                   microcode  does  not  support the
{                                   configured unit.
{
{   9. Request  retry  count  -  The  number  of  times the PP driver
{      retried the entire i/o request.
{
{  10. Diagnostic code - If this word has  a  value  of minus one, no
{      diagnostic  code  is  present.   If  counter word 8 is 61, the
{      error code was generated by the drive as  a  result of running
{      its  self-contained diagnostic.   If counter word 8 is not 61,
{      the  error  code  is  the  most  recent  one  from the drive's
{      history  log  and may have occurred prior to the current error
{      being  reported.   Bits 40-47 contain  a two-digit hexadecimal
{      access  error  code  and  bits  56-63  contain   a   two-digit
{      hexadecimal  read/write error code.   An access error code and
{      a  read/write error code will not be present at the same time.
{      If bits 40-47 are zero, a read/write error code is present.
{
{  11. Cylinder number of initial seek
{
{  12. Track number of initial seek
{
{  13. Sector number of initial seek
{
{  14. Cylinder number of failure - This will be the cylinder  number
{      in the response packet.  If there was no response  packet  for
{      this error, it will be the one the PP was attempting to access
{      at  the  time  of  the  failure.   If the error occurred while
{      executing the path test, this  will  be  the  confidence  test
{      cylinder.
{
{  15. Track number of failure - This will be the track number in the
{      response packet.  If there was no  response  packet  for  this
{      error, it will be the one the PP was attempting to  access  at
{      the  time  of  the  failure.   If  the  error  occurred  while
{      executing the path  test  and  there  is  no  response  packet
{      present, the track number will be set to zero.
{
{  16. Sector number of failure - This will be the sector  number  in
{      the response packet.  If there was no response packet for this
{      error,  it  will be the one the PP was attempting to access at
{      the  time  of  the failure.   If  the  error  occurred   while
{      executing  the  path  test  and  there  is  no response packet
{      present, the sector number will be set to zero.
{
{  17. Residual word count on incomplete channel transfer.
{
{  18. Failing  function  -  This  is  the  last function issued.  If
{      counter word 8 indicates  a  function  timeout,  this  is  the
{      failing function.
{
{  19. Status  register of IPI channel - This register is 16 bits and
{      is right justified.
{
{  20. Error register of IPI channel - This register is 16  bits  and
{      is right justified.
{
{  21. Error register of I4 IPI DMA - This register is 16 bits and is
{      right justified.  On an S0 system bit 0 will be set to one  to
{      indicate this counter word is not used.
{
{  22. Operational  status of I4 IPI adapter - This status is 16 bits
{      and is right justified.  On an S0 system bit 0 will be set  to
{      one to indicate this counter word is not used.
{
{  23. Control  register of I4 IPI adapter - This register is 16 bits
{      and is right justified.  On an S0 system bit 0 will be set  to
{      one to indicate this counter word is not used.  The right-most
{      16 bits of this word will be 4000(16) for a 25 MB channel.
{
{  24. Controller microcode revision number - The revision number  is
{      two hex digits  and is right justified for the CM3 controller.
{      For  the  5831  controller  this contains  8  hex digits right
{      justified.   From the left there are 2 for month, 2 for day, 2
{      for the year, and 2 for the revision number.
{
{  25. Response packet first word - If the upper 16 bits of this word
{      are nonzero, a response packet is present.   These  two  bytes
{      contain  the  length,  in 8-bit bytes, of the response packet.
{      The first two bytes  are  not  included  in  the  byte  count.
{      Response  packet  bytes  are packed, 8 bytes per counter word.
{      This response packet may not be applicable  for  some  errors,
{      like  function timeout, but may still contain a valid response
{      packet.  In this case it would be  the  last  response  packet
{      received  from a controller.  It could even be for a different
{      controller than the one  the  error  is  being  reported  for.
{      Reference   the   controller   product   specification  for  a
{      description of the response.
{  .
{  .
{  .
{  NN. Response  packet  last word.  The maximum value for NN will be
{      40.
{
  CONST
    cml$9836_1_failure_data = cmc$min_ecc+4106;
