SSC-3: Cleaning Behavior

Kevin D Butt kdbutt at us.ibm.com
Wed May 12 10:27:19 PDT 2004


* From the T10 Reflector (t10 at t10.org), posted by:
* Kevin D Butt <kdbutt at us.ibm.com>
*
This is a multipart message in MIME format.
--=_alternative 005F64E207256E92_=
Content-Type: text/plain; charset="US-ASCII"


All, 

I have been searching SSC-x, SPC-x and whatever else I can think of to
find a standards described behavior for Cleaning.  The only behavior(s)
that the standards describe are what TapeAlerts are returned when as
well as listing some ASC/ASCQs but not describing how/when they are to
be used. 

I would like to have the behavior (as seen from a host) during cleaning
to be standardized. 

The ASC/ASCQs listed are: 
          30h/03h  CLEANING CARTRIDGE INSTALLED 
          30h/07h  CLEANING FAILURE 
          00h/17h  CLEANING REQUESTED 

Other interesting ASC/ASCQs listed for are: 
         04h/10h  LOGICAL UNIT NOT READY, AUXILIARY MEMORY NOT
ACCESSIBLE 
         04h/00h  LOGICAL UNIT NOT READY, CAUSE NOT REPORTABLE 
         04h/02h  LOGICAL UNIT NOT READY, INITIALIZING CMD. REQUIRED 
         04h/03h  LOGICAL UNIT NOT READY, MANUAL INTERVENTION REQUIRED 
         04h/07h  LOGICAL UNIT NOT READY, OPERATION IN PROGRESS 
         3Fh/11h MEDIUM AUXILIARY MEMORY ACCESSIBLE 
         3Fh/10h MEDIUM LOADABLE 
         3Ah/00h MEDIUM NOT PRESENT 
         3Ah/03h MEDIUM NOT PRESENT - LOADABLE 
         3Ah/04h MEDIUM NOT PRESENT - MEDIUM AUXILIARY MEMORY ACCESSIBLE

         3Ah/01h MEDIUM NOT PRESENT - TRAY CLOSED 
         3Ah/02h MEDIUM NOT PRESENT - TRAY OPEN 


I have had suggestions ranging from: 
1) Report 30h/03h  CLEANING CARTRIDGE INSTALLED from the time the
cleaning cartridge is detected to the time the cleaning cartridge is
removed (i.e. no longer detectyed by the drive) 
2) Report 30h/03h  CLEANING CARTRIDGE INSTALLED from detection of
cleaning cartridge to completion of clean, then report 3Ah/00h MEDIUM
NOT PRESENT even if the tape is still in the drive. 
3) etc. etc. 

I have also had some ISV/OS people request that we behave the same as
drives of a different technology in areas where that behavior does not
make sense in my drives technology. 

Can we add this as an item to the SSC-3 Agenda? 

I would propose the following as a starting point: 
1) On detection of cleaning cartridge, if can detect but medium not
threaded, report 3Ah/04h MEDIUM NOT PRESENT - MEDIUM AUXILIARY MEMORY
ACCESSIBLE 
2) On medium threaded through the unthreading process, report 30h/03h
CLEANING CARTRIDGE INSTALLED. 
3) On medium unthreaded but cartridge still detected and MAM accessible,
report 3Ah/04h MEDIUM NOT PRESENT - MEDIUM AUXILIARY MEMORY ACCESSIBLE 
4) On cartridge ejected and no longer detected, report 3Ah/00h MEDIUM
NOT PRESENT         

Some technologies will not be able to report 1) or 3) because this state
will not exist.  Others may be configured such that 3) will not be a
settling state but only a transitory state.  And there may be others I
am unaware of. 

What are your initial thoughts?  If I get enough feedback prior to the
next WG meeting I will compile the feedback into an official proposal. 

Thanks, 

Kevin D. Butt
Fibre Channel & SCSI Architect, IBM Tape Microcode, 
6TYA, 9000 S. Rita Rd., Tucson, AZ  85744
Tie-line 321; Office: 520-799-5280, Lab: 799-5751, Fax: 799-4138, Email:
kdbutt at us.ibm.com

--=_alternative 005F64E207256E92_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">All,</font>
<br>
<br><font size=2 face="sans-serif">I have been searching SSC-x, SPC-x and
whatever else I can think of to find a standards described behavior for
Cleaning. &nbsp;The only behavior(s) that the standards describe are what
TapeAlerts are returned when as well as listing some ASC/ASCQs but not
describing how/when they are to be used.</font>
<br>
<br><font size=2 face="sans-serif">I would like to have the behavior (as
seen from a host) during cleaning to be standardized.</font>
<br>
<br><font size=2 face="sans-serif">The ASC/ASCQs listed are:</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 30h/03h
&nbsp;CLEANING CARTRIDGE INSTALLED</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 30h/07h
&nbsp;CLEANING FAILURE</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 00h/17h
&nbsp;CLEANING REQUESTED</font>
<br>
<br><font size=2 face="sans-serif">Other interesting ASC/ASCQs listed for
are:</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;04h/10h
&nbsp;LOGICAL UNIT NOT READY, AUXILIARY MEMORY NOT ACCESSIBLE</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;04h/00h
&nbsp;LOGICAL UNIT NOT READY, CAUSE NOT REPORTABLE</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;04h/02h
&nbsp;LOGICAL UNIT NOT READY, INITIALIZING CMD. REQUIRED</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;04h/03h
&nbsp;LOGICAL UNIT NOT READY, MANUAL INTERVENTION REQUIRED</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;04h/07h
&nbsp;LOGICAL UNIT NOT READY, OPERATION IN PROGRESS</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3Fh/11h
MEDIUM AUXILIARY MEMORY ACCESSIBLE</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3Fh/10h
MEDIUM LOADABLE</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3Ah/00h
MEDIUM NOT PRESENT</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3Ah/03h
MEDIUM NOT PRESENT - LOADABLE</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3Ah/04h
MEDIUM NOT PRESENT - MEDIUM AUXILIARY MEMORY ACCESSIBLE</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3Ah/01h
MEDIUM NOT PRESENT - TRAY CLOSED</font>
<br><font size=2 face="sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3Ah/02h
MEDIUM NOT PRESENT - TRAY OPEN</font>
<br>
<br>
<br><font size=2 face="sans-serif">I have had suggestions ranging from:</font>
<br><font size=2 face="sans-serif">1) Report 30h/03h &nbsp;CLEANING CARTRIDGE
INSTALLED from the time the cleaning cartridge is detected to the time
the cleaning cartridge is removed (i.e. no longer detectyed by the drive)</font>
<br><font size=2 face="sans-serif">2) Report 30h/03h &nbsp;CLEANING CARTRIDGE
INSTALLED from detection of cleaning cartridge to completion of clean,
then report 3Ah/00h MEDIUM NOT PRESENT even if the tape is still in the
drive.</font>
<br><font size=2 face="sans-serif">3) etc. etc.</font>
<br>
<br><font size=2 face="sans-serif">I have also had some ISV/OS people request
that we behave the same as drives of a different technology in areas where
that behavior does not make sense in my drives technology.</font>
<br>
<br><font size=2 face="sans-serif">Can we add this as an item to the SSC-3
Agenda?</font>
<br>
<br><font size=2 face="sans-serif">I would propose the following as a starting
point:</font>
<br><font size=2 face="sans-serif">1) On detection of cleaning cartridge,
if can detect but medium not threaded, report 3Ah/04h MEDIUM NOT PRESENT
- MEDIUM AUXILIARY MEMORY ACCESSIBLE</font>
<br><font size=2 face="sans-serif">2) On medium threaded through the unthreading
process, report 30h/03h &nbsp;CLEANING CARTRIDGE INSTALLED.</font>
<br><font size=2 face="sans-serif">3) On medium unthreaded but cartridge
still detected and MAM accessible, report 3Ah/04h MEDIUM NOT PRESENT -
MEDIUM AUXILIARY MEMORY ACCESSIBLE</font>
<br><font size=2 face="sans-serif">4) On cartridge ejected and no longer
detected, report 3Ah/00h MEDIUM NOT PRESENT &nbsp; &nbsp; &nbsp; &nbsp;
</font>
<br>
<br><font size=2 face="sans-serif">Some technologies will not be able to
report 1) or 3) because this state will not exist. &nbsp;Others may be
configured such that 3) will not be a settling state but only a transitory
state. &nbsp;And there may be others I am unaware of.</font>
<br>
<br><font size=2 face="sans-serif">What are your initial thoughts? &nbsp;If
I get enough feedback prior to the next WG meeting I will compile the feedback
into an official proposal.</font>
<br>
<br><font size=2 face="sans-serif">Thanks,</font>
<br><font size=2 face="sans-serif"><br>
Kevin D. Butt<br>
Fibre Channel &amp; SCSI Architect, IBM Tape Microcode, <br>
6TYA, 9000 S. Rita Rd., Tucson, AZ &nbsp;85744<br>
Tie-line 321; Office: 520-799-5280, Lab: 799-5751, Fax: 799-4138, Email:
kdbutt at us.ibm.com</font>
--=_alternative 005F64E207256E92_=--




More information about the T10 mailing list