{
{ CML$887_FAILURE_DATA
{
{
{ PURPOSE:
{    The purpose of this statistic is to record the failure data
{ captured by the system when accessing a 887 disk subsystem.
{
{ FREQUENCY: At each failure occurrence.
{
{ CONTENT:
{    The  descriptive-data portion of this statistic contains:
{
{    '<mf>.<iou>.<pp>.<ch>.<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' and n is the decimal
{        representation of the logical PP number used to process
{        the failing request.  Note that 'CPP' is the
{        designation given to the concurrent PPs in an I4 IOU.
{
{      where <channel> is the string 'CCHnp', where 'n' is the
{        decimal representation of the channel and 'p' is the
{        channel port (A or B) through which the disk device
{        was accessed.  Note that 'CCH' is the designation given
{        to the concurrent channels in an I4 IOU.
{
{      where  <unit> is the element name of the 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 failure log-entry, and
{        'IM' for informative message.
{
{        The PP reports failure data and diagnostic results  as  an
{        intermediate  failure  log-entry  prior  to retrying an i/o
{        request.  This is due to  PP-memory-size  limitations.   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.  This  log-entry  provides  the  initial  and  final
{        failure data for an intermediate, unsuccessful i/o request
{        retry.  At least  one  additional  request  retry  will  be
{        performed after this log-entry is made.
{
{        For  unrecovered  disk failures the counter values contain
{        the failure data corresponding  to  the  last  unsuccessful
{        retry of the i/o request.  This log-entry provides
{        the   initial   and  final  failure  data  for  the  final,
{        unsuccessful i/o request retry.
{
{      where  <message> is a statement of failure isolation based on
{        either diagnostic execution or status reported by the HYDRA
{        subsystem:
{
{       <symptom statement>
{          The text of the possible symptom statements is
{          identical in content to the uppercase text discussed
{          under counter-value 8 below.
{
{    The  counter-value portion of this statistic contains:
{
{    1.  Logical PP number (bits 58 - 63).
{        Bit 57 is set to 1 implying that the PP is an I4
{        concurrent PP.
{        Bits 46 - 51 contain the IOU number.
{
{    2.  Channel Number (bits 58 - 63).
{        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 Address - (0 .. 7)
{    4.  Physical Unit Number - always zero
{    5.  Unit-type
{        6 - 887
{    6.  Logical Operation Code
{        1 - read
{        2 - write
{    7.  Log-entry Class
{        0 - Recovered Failure Report
{        1 - Unrecovered Failure Report
{        2 - Intermediate Failure Report
{        3 - Informative Message
{    8.  Failure Analysis
{        Indicates the extent to which the subsystem and the PP were
{        able to isolate  the  failure when it was detected.
{
{    0 - INDETERMINATE        The   failure  did  not  manifest
{                             itself as one  of  the  following
{                             symptoms.    Refer  to  the
{                             Controller Status for additional
{                             information.
{
{    1 - EXECUTING LEVEL I DIAGNOSTICS   Execution of LEVEL I
{                                  inline diagnostics was initiated.
{
{    2 - LEVEL I DIAGNOSTICS PASSED      Level I diagnostics ran
{                                  successfully.
{
{    3 - EXECUTING LEVEL II DIAGNOSTICS   Execution of LEVEL II
{                                  inline diagnostics was initiated.
{
{    4 - LEVEL II DIAGNOSTICS PASSED      Level II diagnostics ran
{                                  successfully.
{
{    5 - SPINDLE POWERED UP        The spindle was successfully
{                                  powered up.
{
{    6 - FUNCTION TIMEOUT          The I4 channel adapter failed to
{                                  respond to a function.
{
{    7 - CHANNEL DOESNT GO EMPTY   The I4 channel doesn't go
{                                  empty after the PP sends a
{                                  function or parameter word.
{
{    8 - INCOMPLETE I4 TRANSFER    The PP's A register was non-zero
{                                  after the channel was inactivated
{                                  during a data transfer.
{
{    9 - CHANNEL INITIALIZATION ERROR    The PP could not read and
{                                  verify the control or mask
{                                  registers.
{
{    10 - CANNOT SELECT THE CONTROLER     The 887 controller did not
{                                  set 'Select Active' in the
{                                  allotted time.
{
{    11 - INCORRECT CONTROLLER WAS   The wrong controller replied to
{         SELECTED                 a PP-initiated selection
{                                  sequence.
{
{    12 - PP TIMED OUT A COMMAND    The 887 controller did not
{                                  respond to a command block by
{                                  sending an attention within the
{                                  allotted time.
{
{    13 - CONTROLLER RESERVED      The 887 controller was reserved
{                                  to another host channel.
{
{    14 - SOFTWARE FAILURE         A software failure was detected by
{                                  the PP driver.
{
{    15 - DRIVE NOT READY - MIC1   The 887 controller reported  a
{                                  manual   intervention   code   of
{                                  C1(16).
{
{    16 -UNCORRECTED CM ERROR      An uncorrected error response was
{                                  received from Central Memory on a
{                                  read or write request.
{                                  Bit 50 of the I4 error status
{                                  register was set.
{
{    17 -CM REJECT                 A reject response was received
{                                  from Central Memory on a read
{                                  or write request.
{                                  Bit 51 of the I4 error status
{                                  register was set.
{
{    18 -INVALID CM RESPONSE CODE   The response code from Central
{                                  Memory decoded into an illegal
{                                  value.
{                                  Bit 52 of the I4 error status
{                                  register was set.
{
{    19 -CM RESPONSE CODE PARITY ERROR   The response code from
{                                  Central Memory had a parity
{                                  error.   Bit 53 of the I4 error
{                                  status register was set.
{
{    20 -CMI READ DATA PARITY ERROR   The I4 Central Memory Interface
{                                  (CMI) logic detected a read data
{                                  parity error.
{                                  Bit 54 of the I4 error status
{                                  register was set.
{
{    21 -INPUT BUFFER OVERFLOW     A sync-in was received after the
{                                  I4 DMA channel's input buffer had
{                                  filled.
{                                  Bit 56 of the I4 error status
{                                  register was set.
{
{    22 -JP/JY DATA PARITY ERROR   The JP/JY board detected an error.
{                                  Bit 59 of the I4 error status
{                                  Bit 59 of the I4 error status
{                                  register was set.
{
{    23 -BAS PARITY ERROR          The JN/JX board detected a parity
{                                  error on the data received from a
{                                  PP.
{                                  Bit 60 of the I4 error status
{                                  register was set.
{
{    24 -OUTPUT ISI PARITY ERROR   On  an output from the IOU to the
{                                  887 controller, the IOU reported
{                                  an ISI parity error (bit 61 of the
{                                  I4 error status register was set).
{
{    25 -JZ ERROR                  The JZ board detected an error.
{                                  Bit 61 of the I4 error status
{                                  register was set (and the 887
{                                  controller did not report an ISI
{                                  parity error).
{
{    26 - JP/JY ERROR              The JP/JY board detected an error.
{                                  Bit 62 of the I4 error status
{                                  register was set and bit 59 is
{                                  clear.  The error is either a
{                                  byte count parity, an RMA parity
{                                  error or a constant CM request
{                                  error.
{
{    27 - JN/JX ERROR              The JN/JX board detected an error.
{                                  Bit 63 of the I4 error status
{                                  register was set.
{
{    28 - INCOMPLETE DMA TRANSFER  The DMA transfer did not complete.
{                                  The PP timed out when either the
{                                  T' register was non-empty or the
{                                  Transfer-in-Progress status was
{                                  present and Select Active was set
{                                  and the the Channel Error Flag was
{                                  not set.
{
{    29 - T REGISTER BYTE COUNT NONZERO  The PP timed out when the
{                                  T register byte count was nonzero.
{
{    30 - INVALID CONTROLLER STATUS  The 887 controller has reported
{                                  one of the following:
{                                  1) 'Buffer Space Available' or
{                                  'Read Data Available' when not
{                                  appropriate.
{                                  2) Invalid Execution Status.
{                                  3) Status reported an invalid
{                                  device number or an invalid
{                                  command block number.
{
{    31 - CONTROLLER INTERFACE ERROR   1) Attention was received but
{                                  there was no outstanding command.
{                                  2) Attention was received to
{                                  transfer data when the PP was
{                                  waiting for final completion
{                                  status.
{                                  3) 'Command Complete' status was
{                                  received when there was more data
{                                  to transfer.
{
{    32 -SEEK ERROR - SI21         The 887 controller reported  a
{                                  system   intervention   code   of
{                                  21(16) indicating a seek fault or
{                                  a    sector    header     address
{                                  miscompare.
{
{    33 -UNABLE TO READ HEADER - SI41   The  887 controller reported
{                                  a system intervention   code   of
{                                  41(16)  indicating  it was unable
{                                  to read the header portion of the
{                                  sector.
{
{    34 -HEADER MISCOMPARE - SI42  The  887 controller reported  a
{                                  system   intervention   code   of
{                                  42(16)  indicating  the header
{                                  read from the disk does not match
{                                  the expected cylinder address.
{
{    35 - UNABLE TO READ DATA - SI43   The   887 controller reported
{                                  system   intervention   code   of
{                                  43(16)  indicating  either a Sync
{                                  Byte  detection  problem   or   a
{                                  header ECC mismatch.
{
{    36 - DISK NOT FORMATTED - SI82   During a Power Up Spindle
{                                  command, the 887 controller
{                                  detected that the media is not in
{                                  the format indicated by the format
{                                  select switch (System Intervention
{                                  code was 82(16).
{
{    37 - DIAGNOSTIC FAULT DETECTED    Level I or II diagnostic tests
{                                  detected a fault.
{
{    38 - COMMAND BLOCK NEGATED - SIC1   The 887 controller negated a
{                                  Command Block that it had already
{                                  recognized
{
{    39 - COMMAND BLOCK OVERWRITE - MI21   The PP has altered a
{                                  command block.
{
{    40 - ILLEGAL COMMAND BYTE - MI22   The 887 controller received a
{                                  Command Block with a Command Code
{                                  that is not defined.
{
{    41 - ILLEGAL SECONDARY SEEK ADDRESS - MI23   The 887 controller
{                                  received a Command Block with an
{                                  illegal secondary seek address.
{
{    42 - ILLEGAL PRIMARY SEEK ADDRESS - MI24   The 887 controller
{                                  received a Command Block with an
{                                  illegal primary seek address.
{
{    43 - ILLEGAL COMMAND PARAMETER - MI25   The 887 controller
{                                  received a Command Block with an
{                                  undefined command parameter.
{
{    44 - I/O ILLEGAL WRITE ERROR - MI27   The PP attempted to write
{                                  into one of the status areas in
{                                  the controller's buffer.
{
{    45 - END OF DISK REACHED - MI28   The seek address has been
{                                  incremented to its maximum value.
{
{    46 - ILLEGAL DEVICE NUMBER - MI29   The controller received a
{                                  Command Block with a nonzero
{                                  Device Number.
{
{    47 - ILLEGAL CONTROL FIELD - MI2A   The controller received a
{                                  Command Block with an invalid
{                                  Control Field.
{
{    48 - I/O ILLEGAL DISCONNECT - MI41   The controller detected
{                                  an illegal disconnect at the ISI
{                                  interface.
{
{    49 - ISI I/O PARITY ERROR - MI63   The controller received a
{                                  word across the ISI interface with
{                                  an invalid parity bit.
{
{    50 - R/W SEQUENCER RAM        The  887 controller reported  a
{         PARITY ERROR - MI64      manual   intervention   code   of
{                                  64(16) indicating a read/write
{                                  sequencer memory parity error.
{
{    51 - MPU PARITY ERROR - MI65  The 887 controller reported  a
{                                  manual   intervention   code   of
{                                  65(16)  indicating  an MPU memory
{                                  parity error.
{
{    52 - ECC FAULT - MI66         The  887 controller reported  a
{                                  manual   intervention   code   of
{                                  66(16) indicating a malfunction in
{                                  its error correction circuitry.
{
{    53 - VOLTAGE FAULT - MI67     The  887 controller reported  a
{                                  manual   intervention   code   of
{                                  67(16) indicating its DC voltage
{                                  supply is out of tolerance.
{
{    54 - WRITE TRANSFER COUNT ERROR - MI68   The PP sent more data
{                                  than the controller expected.
{
{    55 - OVER TEMPERATURE FAULT - MI6B   The 887 controller reported
{                                  a manual intervention   code   of
{                                  6B(16) indicating temperatures in
{                                  storage device are above the
{                                  desired range.
{
{    56 - NO READ/WRITE SEQUENCER RESPONSE - MI6C   The Read/Write
{                                  Sequencer failed to respond to a
{                                  request for headers and/or data
{                                  to be written or read within the
{                                  time limits.
{
{    57 - INVALID READ/WRITE SEQUENCER RESPONSE - MI6D   The 887 MPU
{                                  in unable to interpret the
{                                  response given by the Read/Write
{                                  Sequencer to a read or write
{                                  command.
{
{    58 - READ/WRITE SEQUENCER STATUS OVERWRITE - MI6E   The Read/
{                                  Write Sequencer indicated that
{                                  valid status which it was
{                                  attempting to present to the
{                                  887 MPU had been overwritten
{                                  before it was read by the MPU.
{
{    59 - HYDRA HARDWARE FAULT - MI6F   The 887 controller
{                                  reported a failure other than
{                                  those which are assigned a manual
{                                  intervention code. The failure
{                                  data is recorded in the ERROR
{                                  REGISTER IMAGE. Refer to the
{                                  contents of counter-values
{                                  36 .. 47.
{
{    60 - READ/WRITE SEQUENCER FAULT - MI70   The 887 controller
{                                  reported a failure detected by
{                                  its read/write sequencer.  A
{                                  manual intervention status of
{                                  70(16) was returned.
{
{    61 - ZEROFILL TIMEOUT - MI71   The 887 controller reported a
{                                  zerofill timeout.
{
{    62 - FUNCTION BUFFER PARITY ERROR - MI72
{                                  The 887 controller reported a
{                                  function buffer parity error.
{
{    63 - PARTIAL SECTOR ERROR - MI73    The 887 controller
{                                  ended a read/write data
{                                  transfer with a partial sector.
{
{    64 - DISK FAULT - MI81        The 887 controller reported a
{                                  manual intervention code of 81(16)
{                                  indicating the storage device
{                                  detected a fault condition. The
{                                  failure data is recorded in the
{                                  DEVICE STATUS BLOCK.  Refer to
{                                  the contents of counter-values
{                                  32 and 35.
{
{    65 - NO SECTOR PULSE - MI90   The Read/Write Sequencer is
{                                  unable to detect a sector pulse
{                                  from the disk.
{
{    66 - NO INDEX PULSE - MI91    The Read/Write Sequencer is
{                                  unable to detect the index
{                                  pulse from the disk.
{
{    67 - CYLINDER/HEAD/SECTOR WRAP ERROR - MI92   The 887 controller
{                                  detected a mismatch between a
{                                  cylinder, head or sector
{                                  address which was sent to the
{                                  disk and the value which the
{                                  disk returned for verification.
{
{    68 - NO DISK RESPONSE - MIC3   The disk does not respond to
{                                  commands from the control
{                                  portion of the 887.
{
{    69 - PAUSE TIME OUT           The controller Pause status
{                                  did not clear in the alloted
{                                  time.
{
{    70 - TRANSFER IN PROGRESS DID NOT CLEAR
{                                  The transfer-in-progress
{                                  bit in the operational
{                                  status did not clear in the
{                                  alloted time.
{
{    71 - INCOMPLETE COMMAND BLOCK TRANSFER   The channel
{                                  disconnected when the PP
{                                  was writing a command block
{                                  to the controller.
{
{    72 - INCOMPLETE STATUS TRANSFER   The channel disconnected when
{                                  the PP was reading the controller
{                                  status.
{
{    73 - SELECT ACTIVE DROPPED WHEN READING CONTROLLER STATUS
{                                  The controller dropped Select
{                                  Active when the PP was reading the
{                                  controller status.
{
{    74 - INCOMPLETE DEVICE STATUS TRANSFER   The channel
{                                  disconnected when the PP was
{                                  reading the device status.
{
{    75 - SELECT ACTIVE DROPPED WHEN READING DEVICE STATUS
{                                  The controller dropped Select
{                                  Active when the PP was reading
{                                  device status.
{
{    76 - INCOMPLETE ERROR REGISTER IMAGE TRANSFER
{                                  The channel disconnected when
{                                  the PP was reading the error
{                                  register image.
{
{    77 - SELECT ACTIVE DROPPED WHEN READING ERROR REGISTER IMAGE
{                                  The controller dropped Select
{                                  Active when the PP was reading
{                                  the error register image.
{
{    78 - INCOMPLETE ERROR LOG TRANSFER   The channel disconnected
{                                  when the PP was reading the
{                                  error log.
{
{    79 - SELECT ACTIVE DROPPED WHEN READING ERROR LOG
{                                  The controller dropped Select
{                                  Active when the PP was reading
{                                  the error log.
{
{    80 - SELECT ACTIVE DROPPED WHEN TRANSFERRING DATA
{                                  The controller dropped select
{                                  active when the PP was
{                                  transferring data.
{
{    81 - HOST I/F INTEGRITY ERROR   The NOS/VE PP writes data into
{                                  the controller's buffer, rereads
{                                  it and verifies it during the
{                                  PP's initialization sequence.
{                                  The PP detected an error when
{                                  verifying the data.
{
{    82 - DRIVE I/F INTEGRITY ERROR  After the PP verifies the host
{                                  to controller buffer data path
{                                  (see preceding symptom), the PP
{                                  writes data to a reserved
{                                  cylinder, rereads it and
{                                  verifies it during the PP's
{                                  initialization sequence.  The PP
{                                  detected an error when verifying
{                                  the data.
{
{    83 - ISI INPUT ERROR          A parity error was detected by
{                                  the I4 DMA logic on data read
{                                  from the 887 controller.
{                                  Bit 57 of the I4 error status
{                                  register was set.
{
{    84 - ISI TIMEOUT              A channel time out occurred.
{                                  The I4 channel adapter sent a
{                                  sync out and did not receive
{                                  a sync in within one second.
{                                  Bit 58 of the I4 error status
{                                  register was set.
{
{    85 - MEDIA FAILURE            This  indicates that a 'bad-spot'
{                                  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.
{
{    86 - SEEK ERROR - DS22        The 887 controller has attempted
{                                  to recover from a seek error or
{                                  header miscompare error.
{
{    87 - POWER-UP INITIALIZATION COMPLETE - DS81
{                                  The 887 controller completed a
{                                  successful initialization
{                                  operation after application
{                                  of dc power to a unit.
{
{    88 - HOST GENERATED RESET COMPLETE - DS83    The controller
{                                  has successfully completed a
{                                  Broadcast Master Reset or
{                                  Selective Reset operation.
{
{    89 - PRIORITY OVERRIDE COMPLETE - DS84    The controller has
{                                  successfully completed a
{                                  Priority Override operation.
{
{    90 - HYDRA ON LINE - DS85     The PORT Enable Switch for the
{                                  PORT sending Attention has been
{                                  moved from the offline position
{                                  to on line.
{
{    91 - SECTOR SIZE IS NOT 4096  The sector size is not 4096
{                                  bytes.
{
{    92 - HOST IDS ARE DIFFERENT   When running dual access
{                                  the host ids must be the same.
{                                  Single access will work either
{                                  way.
{
{    9.  Request Retry Count      The number of times the PP driver
{                                 retried the  entire  i/o  request
{                                 from the beginning.
{
{    10. Diagnostic Code          Provides  the result of a failing
{                                 diagnostic.
{
{    11. Cylinder number of initial seek
{
{    12. Track number of initial seek
{
{    13. Sector number of initial seek
{
{    14. Cylinder number of failure
{
{    15. Track number of failure
{
{    16. Sector number of failure
{
{    17. Residual byte count on incomplete channel transfer
{
{
{    18. Failing Function         On a function  timeout, the
{                                 function reported is the one
{                                 which was  outstanding  when  the
{                                 I4 channel adapter hung.
{
{    19. PP Status
{        bit    48          The sector size is not 4096.
{        bit    49          The controller does not have the
{                           same host id on both of its ports.
{        bit    51          Set whenever the PP is running the
{                           confidence test.
{        bit    52          Channel master clear did not work.
{        bit    53          After the PP verifies the host to
{                           controller buffer data path, the PP
{                           writes data to a reserved cylinder,
{                           rereads it and verifies it during the
{                           PP's initialization sequence.  The PP
{                           detected an error when verifying the
{                           data.
{        bit    54          The NOS/VE PP writes data into the
{                           controller's buffer, rereads it and
{                           verifies it during the PP's
{                           initialization sequence.  The PP
{                           detected an error when verifying
{                           the data.
{        bit    55          The PP could not read and verify
{                           the control or mask registers.
{        bit    56          The PP timed out waiting for Pause
{                           to clear.
{        bit    57          The PP timed out waiting for Transfer
{                           In Progress to clear.
{        bit    58          The 887 controller did not set
{                           'Select Active' in the alloted time.
{        bit    59          The wrong controller replied to a
{                           PP-initiated selection sequence.
{        bit    60          The error log is present.
{        bit    61          The error register image is present.
{        bit    62          The device status is present.
{        bit    63          The Hydra status is present.
{
{    20. PP Status
{        bit    48          The channel has been downed.
{        bit    49          The controller has been downed.
{        bit    50          not used
{        bit    51          Level I diagnostics ran successfully.
{        bit    52          Execution of LEVEL I inline diagnostics
{                           was initiated.
{        bit    53          Selective Reset was successful.
{        bit    54          Selective Reset was attempted.
{        bit    55          not used
{        bit    56          not used
{        bit    57          The 887 controller did not response to a
{                           command block by sending an attention
{                           within the allotted time.
{        bit    58          The spindle was successfully powered up.
{        bit    59          The PP issued a Power Up Spindle command.
{        bit    60          Level II diagnostics ran successfully.
{        bit    61          Execution of LEVEL II inline diagnostics
{                           was initiated.
{        bit    62          not used
{        bit    63          not used
{
{    21. PP Status
{        bit    48          The PP timed out trying to clear Select
{                           Active by clearing Select Hold.
{        bit    49          The PP timed out when the T register
{                           byte count was nonzero.
{        bit    50          The DMA transfer did not complete.
{                           The PP timed out when either the T'
{                           register was non-empty or the Transfer-
{                           in-Progress status was present and
{                           Select Active was set and the Channel
{                           Error Flag was not set.
{        bit    51          The I4 detected an error during the data
{                           transfer.
{        bit    52          The 887 controller has reported
{                           one of the following:
{                           1) 'Buffer Space Available' or
{                              'Read Data Available' when not
{                              appropriate.
{                           2) Invalid Execution Status.
{                           3) Status reported an invalid
{                              device number or an invalid
{                              command block number.
{        bit    53          The controller dropped select active when
{                           the PP was transferring data.
{        bit    54          The controller dropped Select Active when
{                           the PP was reading the error log.
{        bit    55          The channel disconnected when the PP was
{                           reading the error log.
{        bit    56          The controller dropped Select Active when
{                           the PP was reading the error register
{                           image.
{        bit    57          The channel disconnected when the PP was
{                           was reading the error register image.
{        bit    58          The controller dropped Select Active when
{                           the PP was reading device status.
{        bit    59          The channel disconnected when the PP was
{                           reading the device status.
{        bit    60          The controller dropped Select Active
{                           when the PP was reading the controller
{                           status.
{        bit    61          The channel disconnect when the PP was
{                           reading the controller status.
{        bit    62          not used
{        bit    63          The channel disconnected when the PP
{                           was writing a command block to the
{                           controller.
{
{    22. PP Status
{        bit    48          1) Attention was received but
{                              there was no outstanding command.
{                           2) Attention was received to
{                              transfer data when the PP was
{                              waiting for final completion status.
{                           3) 'Command Complete' status was
{                               received when there was more data
{                               to transfer.
{        bit    49          The 887 controller was reserved
{                           to another host channel.
{        bit    50          not used
{        bit    51          not used
{        bit    52          not used
{        bit    53          not used
{        bit    54          not used
{        bit    55          This  indicates that a 'bad-spot'
{                           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.
{        bit    56          not used
{        bit    57          not used
{        bit    58          The I4 channel doesn't go empty after
{                           the PP sends a function or parameter
{                           word.
{        bit    59          not used
{        bit    60          not used
{        bit    61          not used
{        bit    62          not used
{        bit    63          The PP's A register was non-zero after
{                           the channel was inactivated during a
{                           data transfer.
{
{    23. I4 Error Status Register
{                    (bits 48 .. 63)
{    24. I4 Operational Status Register
{                    (bits 48 .. 63)
{    25. I4 T Register Content
{                    (bits 16 .. 63)
{    26. I4 Control Register
{                    (bits 48 .. 63)
{    27. I4 Flag Mask Register
{                    (bits 48 .. 63)
{    28. ISI Idle Status  (bits 48 .. 63)
{        Bits 48 .. 55 of this word correspond to the reserve
{        status of the ISI bus addresses 7 .. 0, respectively.
{        Bits 56 .. 63 of this word correspond to the attention
{        status of the ISI bus addresses 7 .. 0, respectively.
{    29. Bus Unit Select Word   (bits 48 .. 63)
{        Bits 56 .. 63 (the least significant bits) of this word
{        correspond to ISI bus addresses 7 .. 0, respectively.
{        The PP selected a controller and either no controller
{        responded or the wrong controller responded.  This word
{        contains the Bit Significant Response (BSR) the PP
{        received.
{
{   First-failure Data:
{    30. Words 0..3 of 887 HYDRA Status Block (left to right)
{    31. Words 4..5 of 887 HYDRA Status Block (left justified)
{    32. Words 0..3 of 887 Device Status Block (left to right)
{

{   Last-failure Data:
{    33. Words 0..3 of 887 HYDRA Status Block (left to right)
{    34. Words 4..5 of 887 HYDRA Status Block (left justified)
{    35. Words 0..3 of 887 Device Status Block (left to right)

{
{    36 .. 47. Words 0..47 of 887 Error Register Image (left to right)
{    48 .. 59. Words 0..47 of 887 Error Log (left to right)
{
  CONST
    cml$887_failure_data = cmc$min_ecc + 4105;

*copyc cmc$condition_limits



