A method of polling a ta

[Jim McGrath]

* From the SCSI Reflector, posted by:
* "Jim McGrath" <jmcgrath at qntm.com>
*
        Reply to:   RE>A method of polling a target for Informational
Exception ...

Gene,

Why is this needed?  Cann't the host just issue a TUR, and then a request
sense follow up if there is exception information pending at the target?
That would seem to be easier, and use existing commands.

Jim


--------------------------------------
Date: 3/4/96 2:59 PM
To: Jim McGrath
From: Gene Milligan
Received: by qm_smtpgw.qntm.com with SMTP;4 Mar 1996 14:54:41 U
Received: from worf.qntm.com (worf-gw.qntm.com) by mail.qntm.com with ESMTP
	(1.37.109.16/16.2) id AA223760090; Mon, 4 Mar 1996 14:54:51 -0800
Received: from mpdgw2.symbios.com by worf.qntm.com with ESMTP
	(1.37.109.16/16.2) id AA073270089; Mon, 4 Mar 1996 14:54:49 -0800
Received: (from root at localhost) by mpdgw2.symbios.com (8.6.8.1/8.6.6) id
PAA11218; Mon, 4 Mar 1996 15:47:00 -0700
Received: from aztec.ncrmicro.ncr.com(153.72.199.214) by mpdgw2.symbios.com
via smap (V1.3)
	id smab10911; Mon Mar  4 15:44:14 1996
Received: (from majordom at localhost) by Symbios.COM (8.6.8.1/8.6.6) id PAA14244
for scsi-outgoing; Mon, 4 Mar 1996 15:42:33 -0700
Received: from mpdgw2.symbios.com ([204.131.201.2]) by Symbios.COM
(8.6.8.1/8.6.6) with ESMTP id PAA14233 for <scsi at symbios.com>; Mon, 4 Mar 1996
15:42:31 -0700
Received: (from root at localhost) by mpdgw2.symbios.com (8.6.8.1/8.6.6) id
PAA10690 for <scsi at symbios.com>; Mon, 4 Mar 1996 15:42:32 -0700
Received: from ns1.seagate.com(204.160.183.10) by mpdgw2.symbios.com via smap
(V1.3)
	id sma010675; Mon Mar  4 15:42:12 1996
Received: (from smap) by ns1.seagate.com (8.6.12/cf-v5) id OAA14367 for
<@proxy.seagate.com:scsi at symbios.com>; Mon, 4 Mar 1996 14:42:31 -0800
Received: from unknown(134.204.14.86) by ns1.seagate.com via smap (V1.3)
	id sma014321; Mon Mar  4 14:41:55 1996
Received: by notes.seagate.com (IBM OS/2 SENDMAIL VERSION 1.3.2)/1.0)
	  id AA6874; Mon, 04 Mar 96 14:41:16 -0800
Message-Id: <9603042241.AA6874 at notes.seagate.com>
Received: by SEAGATE (Lotus Notes Mail Gateway for SMTP V1.1) id
  F3C8D06D271F7F8F862562E30077B7D6; Mon,  4 Mar 96 14:41:15 EDT
To: scsi <scsi at Symbios.COM>
From: Gene Milligan <Gene_Milligan at notes.seagate.com>
Date:  4 Mar 96 15:58:03 EDT
Subject: A method of polling a target for Informational Exception
  Condition status without issuing a Request Sense command
Mime-Version: 1.0
Content-Type: Text/Plain
Sender: owner-scsi at Symbios.COM
Precedence: bulk

* From the SCSI Reflector, posted by:
* Gene Milligan <Gene_Milligan at notes.seagate.com>
*
Background:

The Informational Exceptions Control Mode Page (1) describes several reporting

methods in which a target can report an informational exception condition to
an 
initiator.  These reporting methods require a host to issue a Request Sense 
command and interpret sense data to determine status.  In some environments, 
issuing an unsolicited Request Sense command is not desirable.  This proposal 
provides an initiator with a method of polling a target for Informational 
Exception Condition status without issuing a Request Sense command.


This proposal is for the inclusion of an additional log page, to be known as 
the  FAILURE PREDICTION THRESHOLD EXCEEDED Status Log Page (2Fh) in SPC.  The 
FAILURE PREDICTION THRESHOLD EXCEEDED Status Log Page will contain one log 
parameter (0000h) of the format shown below.  This will allow an initiator to 
poll the target, by issuing a Log Sense command, and check for an
informational 
exception condition regardless of the Reporting Method (MRIE) selected.

Proposal:

========================================================================+
   Bit  |   7   |   6   |   5   |   4   |   3   |   2   |   1   |   0   |
  Byte  |       |       |       |       |       |       |       |       |
========================================================================+
   0    |   (MSB)                                                       |
 -------+----             Parameter Code (0000h)                    ----+
   1    |                                                       (LSB)   |
 -------+---------------------------------------------------------------+
   2    |   X   |   X   |   X   |   0   |   0       0   |   1   |   1   |
 -------+---------------------------------------------------------------+
   3    |                   Parameter Length (2)                        |
 -------+---------------------------------------------------------------+
   4    |FAILURE PREDICTION THRESHOLD EXCEEDED ASC                      |
 -------+---------------------------------------------------------------+
   5    |FAILURE PREDICTION THRESHOLD EXCEEDED ASCQ                     |
========================================================================+

The FAILURE PREDICTION THRESHOLD EXCEEDED ASC has the same definition as the 
Additional Sense Code returned in byte 12 of Request Sense data.  

The FAILURE PREDICTION THRESHOLD EXCEEDED ASCQ has the same definition as the 
Additional Sense Code Qualifier  returned in byte 13 of Request Sense data.  
   
If either Byte 4 or Byte 5 is FFh (4) then the target is in a  test mode.  The
 
test mode may be used by an initiator for software testing.