{
{ CML$FA7B4_D_FAILURE_DATA
{
{
{ PURPOSE:
{    The purpose of this statistic is to record the failure data
{ captured by the system when accessing a FA7B4_D disk controller.
{
{ 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 'PPn' where n is the PP number (in
{        decimal) of the PP which performed the i/o operation  which
{        is being reported.
{
{      where  <ch>  is  the string 'CHn' where n is the channel
{        number  (in  decimal)  over  which  the  i/o  request   was
{        processed.
{
{      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 failure log-entry, and 'IM'
{        for an 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.
{
{        For  failures  corrected  during  sector-oriented  (media)
{        recovery, the counter values contain the first-failure data
{        captured by  the  PP.   This  log-entry  is  only  made  to
{        document successful sector-oriented recovery.
{
{      where  <message> is a statement of failure isolation based on
{        either diagnostic execution or status reported by subsystem:
{
{        ADAPTER FAILURE <code>
{        CONTROL MODULE FAILURE <code>
{        DRIVE FAILURE <code>
{          The <code> clause, a hex value which is optionally
{          appended to the messages documented above, is the
{          diagnostic code reported by the subsystem when an inline
{          diagnostic has isolated a failure to the indicated
{          subsystem element.  The diagnostic code is also reported
{          in counter-value 10.  Absence  of  the  <code> clause
{          indicates that the Adapter suspects the failure to be in
{          the indicated box; however, the failure could not be
{          isolated by diagnostics.
{
{       MEDIA FAILURE - Cccc Ttt Sss
{          The cylinder (ccc), track (tt) and sector (ss) are
{          expressed in decimal.  The location of the media failure
{          is also reported in counter-values 14, 15 and 16.
{
{       <symptom statement>
{          The symptom  statement  is  provided  for  those failures
{          which could not be isolated to a particular element.
{          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).
{        Bits 46 - 51 contain the IOU number.
{
{    2.  Channel Number (bits 58 - 63).
{        Bits 46 - 51 contain the IOU number.
{
{    3.  Address of Control Module
{    4.  Physical Unit Number
{    5.  Unit-type
{        4 - 836-12
{    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.  The
{        failure data is analyzed in the order in which the following
{        symptom statements are presented in this paper.  Therefore,
{        should multiple failures occur and be implied in the failure
{        data, only one symptom statement will be provided;  the one
{        provided will be the one appearing first in the following
{        list of symptoms.
{
{    0 - INDETERMINATE        The   failure  did  not  manifest
{                             itself as one  of  the  following
{                             symptoms.    Refer  to  the  Poll
{                             Status and  Detailed  Status  for
{                             additional information.
{
{    Failures reported to be in the Adapter, Control Module,
{    Drive or Media are confirmed either by subsystem
{    diagnostics or by attempting to reload the controlware
{    for a subsystem element.
{
{    1 - PP TIMED OUT A COMMAND    A command sent to the Adapter and
{                                  or Control Module was not
{                                  responded to in the allotted time.
{
{    2 - CONTROL MODULE RESERVED   The Control Module was reserved to
{                                  another host adapter.
{
{    3 - SOFTWARE FAILURE          A software failure was detected by
{                                  the PP driver.
{
{    4 - DRIVE NOT READY           The  Control  Module  reported  a
{                                  manual   intervention   code   of
{                                  C1(16)  but  there  was  no drive
{                                  fault; the Adapter  reports  this
{                                  as  a  Poll  Status  of  440xx(8).
{                                  This failure indicates  that  the
{                                  drive  is  not  spinning.  The PP
{                                  driver automatically  spins-up  a
{                                  drive   if   this   condition  is
{                                  detected; therefore if this is an
{                                  unrecovered  failure,  the  CE or
{                                  Operator  may  have  placed   the
{                                  LOC/REM  switch of the FSD in the
{                                  LOC position.  Placing the switch
{                                  in  the LOC position prevents the
{                                  PP from spinning  up  the  drive.
{                                  The PP cannot determine the state
{                                  of    the     LOC/REM     switch.
{                                  Therefore,  if  the  switch is in
{                                  the LOC position  either  depress
{                                  the   START  button  or  set  the
{                                  LOC/REM switch to the REM  state.
{
{    5 - RELOADING CONTROL MODULE  A Control Module microcode reload
{                                  was initiated.
{
{    6 - CONTROL MODULE RELOADED   The Control Module microcode was
{                                  successfully reloaded.
{
{    7 - EXECUTING LEVEL II DIAGNOSTICS   Execution of LEVEL II
{                                  inline diagnostics was initiated.
{
{    8 - LEVEL II DIAGNOSTICS PASSED      Level II diagnostics ran
{                                  successfully.
{
{    9 - DRIVE NOT PRESENT         The  Control  Module  reported  a
{                                  manual   intervention   code   of
{                                  C3(16) indicating  there  was  no
{                                  response from the drive.
{
{    10 -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.
{
{    11 -FUNCTION FAILURE CLASS 2  The  channel-error-flag  was  set
{                                  and the Adapter failed to respond
{                                  to a function attempt.
{
{    12 -FUNCTION FAILURE CLASS 3  The channel-error-flag was  not
{                                  set  and  the  Adapter  failed to
{                                  respond to a function attempt.
{
{    13 -INPUT ICI PARITY          On an input from the  Adapter  to
{                                  the PP the channel-error-flag was
{                                  set.
{
{    14 -OUTPUT ICI PARITY CLASS 1 On an output from the PP  to  the
{                                  Adapter   the  channel-error-flag
{                                  was set and the Adapter  reported
{                                  the parity error.  The IOU is the
{                                  likely cause of the  problem  but
{                                  this is not a certainty.
{
{    15 -OUTPUT ICI PARITY CLASS 2 On  an  output from the PP to the
{                                  Adapter  the   channel-error-flag
{                                  was set but the Adapter did not
{                                  report a parity error.
{
{    16 -OUTPUT ICI PARITY CLASS 3 On an output from the PP  to  the
{                                  Adapter  the  Adapter  reported a
{                                  parity     error     but      the
{                                  channel-error-flag was not set.
{
{    17 -ADAPTER RAM PARITY        The  Adapter  reported  a  parity
{                                  error in its RAM memory.
{
{    18 -ADAPTER BUFFER PARITY     A  parity  error  was detected in
{                                  the Adapter's buffer memory.
{
{    19 -ADAPTER ROM PARITY        A parity error  was  detected  in
{                                  the  Adapter's  ROM  (poll status
{                                  5014).
{
{    20 -START SWITCH NOT DEPRESSED   Spin-up of the storage device
{                                  failed because the start switch
{                                  was not depressed.
{
{    21 -ISI PARITY                On  an  input or an output between
{                                  the Control Module and the Adapter
{                                  the Adapter reported a parity
{                                  error but the Control Module did
{                                  not.
{
{    22 -OUTPUT ISI PARITY CLASS 1 On  an output from the Adapter to
{                                  the  Control  Module   both   the
{                                  Adapter  and  the  Control Module
{                                  reported a parity  error  on  the
{                                  ISI channel.
{
{    23 -OUTPUT ISI PARITY CLASS 3 On  an output from the Adapter to
{                                  the Control  Module  the  Control
{                                  Module reported a parity error on
{                                  the ISI channel and  the  Adapter
{                                  did not.
{
{    24 -SEEK ERROR                The  Control  Module  reported  a
{                                  system   intervention   code   of
{                                  21(16) indicating a seek fault or
{                                  a    sector    header     address
{                                  miscompare.
{
{    25 -UNABLE TO READ HEADER     The  Control  Module  reported  a
{                                  system   intervention   code   of
{                                  41(16)  indicating  it was unable
{                                  to read the header portion of the
{                                  sector.
{
{    26 -UNABLE TO READ DATA       The   Control   Module   reported
{                                  system   intervention   code   of
{                                  43(16)  indicating  either a Sync
{                                  Byte  detection  problem   or   a
{                                  header ECC mismatch.
{
{    27 -ISI DEADMAN TIME-OUT      The    Adapter    detected     an
{                                  expiration  of  the deadman timer
{                                  on a data transfer between itself
{                                  and the Control Module.
{
{    28 -CM SCHEDULER PARITY       The  Control  Module  reported  a
{                                  manual   intervention   code   of
{                                  64(16) indicating a R/W Scheduler
{                                  memory parity error.
{
{    29 -CM MPU PARITY             The  Control  Module  reported  a
{                                  manual   intervention   code   of
{                                  65(16)  indicating  an MPU memory
{                                  parity error.
{
{    30 -CM R/W HARDWARE FAULT     The  Control  Module  reported  a
{                                  manual   intervention   code   of
{                                  66(16).
{
{    31 -DRIVE VOLTAGE FAULT       The  Control  Module  reported  a
{                                  manual   intervention   code   of
{                                  67(16).
{
{    32 -OVER TEMPERATURE FAULT    The  Control  Module  reported  a
{                                  manual   intervention   code   of
{                                  6B(16).
{
{    33 -INVALID BOOTSTRAP ERROR   Manual Intervention Status 69(16)
{                                  was reported by the Control
{                                  Module.
{
{    34 -DRIVE WRITE PROTECTED     The  Control  Module  reported  a
{                                  manual   intervention   code   of
{                                  C2(16) indicating that the system
{                                  attempted  to  write on the drive
{                                  but  the  drive's  WRITE  PROTECT
{                                  switch was set.
{
{    35 -INCOMPLETE ICI TRANSFER   The  PP's A-register was non-zero
{                                  after   the   ICI   channel   was
{                                  inactivated    during    a   data
{                                  transfer  and  Poll  Status   was
{                                  normal.   Refer  to  the Residual
{                                  Byte Count below to see how  many
{                                  16-bit bytes were lost.
{
{    36 -LOOPBACK COMPARE ERROR    A  compare  error was detected by
{                                  the  Adapter  when  looping  data
{                                  between   the   Adapter  and  the
{                                  Control Module.
{
{    37 -LOOPBACK SELECT ACTIVE    The select active state  did  not
{                                  drop  when  a  word  sent  to the
{                                  Control Module from  the  Adapter
{                                  had a parity error.
{
{    38 -LOOPBACK ATTENTION        The attention status was not sent
{                                  by the Control Module  after  the
{                                  Adapter sent a word with a parity
{                                  error.
{
{    39 -LOOPBACK CHECK FAILURE    The  Control  Module  failed   to
{                                  report   an  ISI  channel  parity
{                                  error when  the  Adapter  sent  a
{                                  word   with  bad  parity  to  the
{                                  Control Module.
{
{    40 -CONTROL MODULE FAILURE   The failure was isolated to the
{                                 Control Module.
{
{    41 -ADAPTER FAILURE          The failure was isolated to the
{                                 7255-1 adapter.
{
{    42 -DRIVE FAILURE            The failure was isolated to the
{                                 storage device (drive).
{
{    43 -ADAPTER CONTROLWARE ERROR  An error most likely caused by
{                                 the adapter.  Some of the possible
{                                 causes are: wrong status after load
{                                 attention delay, wrong status after
{                                 sending controlware, status asking
{                                 for more data when there is none,
{                                 and status saying the read or write
{                                 command is complete when there is
{                                 more data to transfer.
{
{    44 -PP - ADAPTER DATA INTEGRITY  An interface test transferred
{                                 data between the PP and the adapter.
{                                 No error was detected, but the data
{                                 miscompared.
{
{    45 -PP - DRIVE DATA INTEGRITY  A confidence test wrote data to a
{                                 drive, then read it back.  No error
{                                 was detected, but the data miscompared.
{
{    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 - This is normally the cylinder
{        number in the disk request.  However, if the failure occurred
{        while running the confidence test, the cylinder number will be
{        815 for an 834 drive and 699 for an 836 drive (the confidence
{        test cylinder).
{
{    15. Track number of failure
{
{    16. Sector number of failure
{
{    17. Residual byte count on incomplete channel transfer
{
{
{    18. Failing Function         The   function  that  caused  the
{                                 initial  recovery  attempt.   The
{                                 value   is   extracted  from  the
{                                 initial detailed  status  if  the
{                                 Adapter provides status after the
{                                 failure.  On a function  timeout,
{                                 the  function reported is the one
{                                 which was  outstanding  when  the
{                                 Adapter hung.
{
{   First-failure Data:
{    19.       Poll Status
{                    (right justified)
{    20 .. 39. Words 1..20 of Detailed Status
{                    (right justified)
{
{    The following failure data is only provided in the
{    cases where the Log-entry Class is unrecovered or
{    intermediate.  The data represents the subsystem
{    status at the end of the intermediate or final
{    request retry.
{
{   Last-failure Data:
{    40.       Poll Status
{                    (right justified)
{    41 .. 60. Words 1..20 of Detailed Status
{                    (right justified)
{

  CONST
    cml$fa7b4_d_failure_data = cmc$min_ecc + 4103;

*copyc cmc$condition_limits
