HP Lto 5 Manual

							1InterfaceImplementation
HPLTOUltrium5drivesuseFibreChannelorSerialAttachedSCSI(SAS)astheinterfacetoconnect
tothehostsystem.
Thischaptergivesanoverviewofhowtheinterfaceoperates.Fulldetailsofthemessagesare
givenin“Messages”(page18),ofSASresponseframesandtaskmanagementfunctionsin
“Responseframesandtaskmanagementfunctions”(page19),andofcommandsin“Introduction
tocommands”(page22)and“Commands”(page29).
TheFibreChannelinterface
FibreChannelisanindustrystandard,approvedbytheAmericanNationalStandardsInstitute
(ANSI).YouarerecommendedtoreadtheANSIstandarddocumentsinconjunctionwiththis
manual.TheANSIspecificationsdefinetheinterfaceingeneralwhilethisdocumentdescribesthe
HPLTOUltriumimplementation.
TheFibreChannelimplementationprovidesadrivewithastandardsetoffeaturesandfunctions.
Theseincludethefollowing:
•ImplementationofallmandatoryandmostoptionalcommandsoftheSequentialAccess
commandset
•4Gbpsserialtransferswithauto-negotiationto8Gb/s,4Gb/sand2Gb/swith8Gb/s
transceiver,.4Gb/s,2Gb/sand1Gb/swith4Gb/stransceiver.
•Dualportcapability(full-heightdrivesonly)
•ConformancetothefollowingSCSIstandards:
SAM-4T10/1683-Drevision14◦
◦FCP-3ANSINCITS.416:2006
◦FC-AL-2ANSIINCITS.350:200xwithAM1:2002
◦FC-FSANSIINCITS.373-2003
◦FC-TapeANSIINCITSTR-24:1999
◦FC-FLAANSIINCITSTR-20:1998
◦SPC-4T10/1731-Drevision18
◦SSC-3T10/1611-Drevision05
Supportedtaskmanagementfunctions
Thefollowingtaskmanagementfunctionsaresupportedbythedrives:
•ABORTTASK
•ABORTTASKSET
•CLEARTASKSET
•LOGICALUNITRESET
•TARGETRESET
Forimplementationdetailsonthese,see“Responseframesandtaskmanagementfunctions”
(page19).
TheSASinterface
SerialAttachedSCSI(SAS)isanindustrystandard,approvedbytheAmericanNationalStandards
Institute(ANSI).YouarerecommendedtoreadtheANSIstandarddocumentsinconjunctionwith
TheFibreChannelinterface11 
						

							thismanual.TheANSIspecificationsdefinestheinterfaceingeneralwhilethisdocumentdescribes
theHPLTOUltriumimplementation.
TheSASimplementationprovidesadrivewithastandardsetoffeaturesandfunctions.These
includethefollowing:
•ImplementationofallmandatoryandmostoptionalcommandsoftheSequentialAccess
commandset
•SAS-2compliantinterface
•6Gbpsserialtransfers
•ConformancetothefollowingSCSIstandards:
SAM-4T10/1683-Drevision14◦
◦SAS-2(noversionclaimed)
◦SPC-4T10/1731-Drevision18
◦SSC-3T10/1611-Drevision05
Supportedtaskmanagementfunctions
Thefollowingtaskmanagementfunctionsaresupportedbythedrives:
•ABORTTASK
•ABORTTASKSET
•CLEARTASKSET
•LOGICALUNITRESET
•QUERYTASK
•QUERYASYNCHRONOUSEVENT
•QUERYTASKSET
•I_TNEXUSRESET
Forimplementationdetailsonthese,see“Responseframesandtaskmanagementfunctions”
(page19)
Supportedcommands
See“Introductiontocommands”(page22)foralistofsupportedcommands.Theyincludeall
MandatoryandExtendedcommandsandmostOptionalcommands.
Forimplementationdetailsonthesecommands,see“Commands”(page29).
SCSIfeatures
Designapproach
Thefeaturessupportedbythedrivearebasedonstandards,bothofficialanddefacto.Thedrive
isfullycompliantwiththecurrentSCSIstandards:SPC-3,SSC-2,SAM-4,andtherelevanttransport
protocol(suchasSAS-2forSASdrives).Allmandatorycommandsandfeaturesaresupported,as
wellassomethatareoptional.Inaddition,somefeaturesfromolderstandardsarestillsupported
forbackwardscompatibility.
Power-on
ThedrivewillrespondtoINQUIRY,TESTUNITREADY,REPORTLUNSandREQUESTSENSE
commandswithin250msofpoweronforSASdrives.ForstandaloneFCdrives,theresponsetime
12InterfaceImplementation 
						

							couldtakeupto3seconds.Fordrivesinlibraries,therewouldbeanadditionallibraryinitialization
timeontopofthesefigures.
Thefirstcommandreceivedfromaninitiator(otherthanINQUIRY,REQUESTSENSEandREPORT
LUNS)willresultinCHECKCONDITIONstatus,withUNITATTENTIONsensedatareportedfor
thepoweron.Oncethedrivehascompleteditsself-testandset-upprocedures,itwillattemptto
reloadanytapethatisalreadypresentinthedrive.Itmaytakesometimetorecoverthetape,
especiallyifitwaspositionednearEOMwhenpowerwascycled.Duringtaperecovery,medium
accesscommandswillresultinasensekeyofNOTREADY,withadditionalsenseof0401h(drive
inprocessofbecomingready).
Resetstrategy
FollowingonthereceiptofaLogicalUnitResetTaskManagementFunction,thefollowingactions
willbecarriedoutbythedrive:
•AlltasksqueuedforthatLogicalUnitwillbeaborted.
•Modeparametersareclearedtotheirdefaultvalues.
•Thedrive'sreservationisreleased,butnotthepersistentreservation.
•Anybufferedwritesareflushedtotape.
•IfRewind-On-Resethasbeenconfigured,thetapewillberewound(LogicalPositionisBOM).
•AUNITATTENTIONconditionisset,basedonthetypeofreset.
Thefirstcommandfromanyinitiator(otherthanINQUIRY,REQUESTSENSEandREPORTLUNS)
tothatparticularLogicalUnitwillresultinCHECKCONDITIONstatuswithUNITATTENTION
sensedataforthereset.
Itispossibletoforceahardresetinthedrive,whichisequivalenttoasoftpower-cycle.
TheResetbuttononthefrontpanelisconnectedtotheresetcircuitryofthedrive.Theeffectof
depressingtheResetbuttonisequivalenttopower-cyclingthedrive.
TheACI_RST_LlineontheACIconnectorwillalsoactivatetheresetcircuitrywhenpulledlowin
anACIautomationenvironment.ActivatingtheACI_RST_LlineinanADIautomationenvironment
willresultinanADTportlogoutandwillnotactivatetheresetcircuitry.
Thecontentsofthetapeandcartridgememorymaynotbeconsistentafteraresetandanydata
inthedrivebufferwillbelost.
Aborthandling
Linkerrorhandling(SASdrives)
Innormaloperation,randomerrorswilloccasionallybeencounteredonthelinkbetweenthe
initiatorandthetapedrive.AsinglebiterrormayresultinaframewithabadCRCvalue,orin
acommunicationfailureiftheerrorcorruptsoneofthespecial“primitive”messagesusedtomanage
thelink.TheSASstandardprovidesanoptionalmechanismtoretrymostlinkerrors;thismechanism
isknownasTransportLayerRetries.See“Protocol-SpecificLogicalUnitmodepage(SASdrives)”
(page102).Bydefaultthetapedrivehasretriesdisabled;aninitiatorwhichisalsocapableof
handlingretriesmustenabletheminthetapedrivetypicallyduringthediscoveryphase.Thetape
drivewillalsosupporttheTLRControlfieldinSSPcommandframes.
SCSIfeatures13 
						

							Thefollowingtableindicatesthedrivebehaviorbothwithandwithouttransportlayerretries
enabled,foravarietyofpossibleerrorscenarios:
BehaviorErrorType
TransportLayerRetriesEnabledTransportLayerRetriesDisabled
ThedrivesendsNAK.
Theinitiatorrestartsdatatransferwiththe
ChangingDataPtrbitsetforthefirst
resentframe.
ThedrivesendsNAK.
Theinitiatorabortsthecommandusing
theABORTtaskmanagementfunctions.
DataframeCRCerroronwrites
TheinitiatorsendsNAK,driverestarts
transferfromstartofburstwithChanging
DataPtrbitsetfor1stresentframe
TheinitiatorsendsNAK.
Thedriveabortsthecommandwitha
sensekeyofABORTEDCOMMANDand
additionalsenseof4B04h(NAK
received).
DataframeCRCerroronreads
TheinitiatorsendsNAK.
Thedrivere-issuesXFER_RDYwiththe
RetransmitbitsetandafreshTPTTvalue.
TheinitiatorsendsNAK.
Thedriveabortsthecommandwitha
sensekeyofABORTEDCOMMANDand
additionalsenseof4B04h(NAKreceived)
XFER_RDYframeCRCerror
TheinitiatorsendsNAK.
Thedrivere-sendstheresponseframewith
theRetransmitbitset.
TheinitiatorsendsNAK.
Thedrivere-sendstheresponseframewith
theRetransmitbitset.
ResponseframeCRCerror
Thedrivecompletestheoperation(since
alldatawasreceivedsuccessfully)and
sendsGOODstatus.
Theinitiatortimesouttheoperationand
sendsanABORTtaskmanagement
function.
LossofACKforawritedata
frame
Thedrivetimesouttheoperation,then
restartsthetransferfromthestartofthe
burstwiththeChangingDataPtrbitset
forthefirstresentframe.
Thedrivetimesouttheoperationand
abortsthecommandwithasensekeyof
ABORTEDCOMMANDandadditional
senseof4B03(ACK/NAKTimeout).
LossofACKforreaddataframe
Thedrivetimesouttheoperation,then
re-issuesXFER_RDYwiththeRetransmitbit
setandafreshTPTTvalue.
Thedrivetimesouttheoperationand
abortsthecommandwithasensekeyof
ABORTEDCOMMANDandadditional
senseof4B03(ACK/NAKTimeout).
LossofACKforaXFER_RDY
frame
Thedrivetimesouttheoperation,then
re-sendstheresponseframewiththe
Retransmitbitset.
Thedrivetimesouttheoperation,then
re-sendstheresponseframewiththe
Retransmitbitset.
LossofACKforaresponse
frame
Multi-initiatorsupport
Alldrivesaredesignedtooperatewithinamulti-initiatorenvironment.Themaximumnumberof
concurrentlyconnectedinitiatorsis:
•FCdrives:511(forfull-heightdrives,sharedacrossbothports)
•SASdrives:32(forfull-heightdrives,sharedacrossbothports)
SenseData,UnitAttentionandDeferredErrorsaremaintainedforeachinitiator.ModeParameters
arecommontoallinitiators.
Theuntaggedqueuingmodelimplementedbythedrivesguaranteesthatallcommandsareexecuted
instrictorderofreceipt.Certainnon-mediaaccesstypecommands,suchasTESTUNITREADY,
INQUIRY,REQUESTSENSEandREPORTLUNS,areimplicitlyallowedtoqueue-jumpothermedia
accesstypecommands,suchasREWIND.
FCdrivessupportthefullcommandqueuingmodelwithaqueuedepthof4.See“StandardInquiry
Dataformat(LUN0)”(page37)fordetailsoftheBQueandCmdQuebitswhichdefinethissupport.
14InterfaceImplementation 
						

							FibreChanneloperation
ThefollowingsectionshaveinformationspecifictoFibreChanneloperation:
•“Protocol-SpecificLogicalUnitmodepage(FCdrives)”(page102)
•“Protocol-SpecificPortmodepage(FCdrives)”(page102)
•“VitalProductDatapages”(page40)
FibreChanneladdressing
BeforedescribingHP'simplementationofFibreChanneladdressing,theconceptsofNamesand
Addressesneedtobeclarified.
Names
Namesare64-bitidentifiersassignedpermanentlytothetapedriveduringmanufacture.Theyare
commonlyreferredtoasWorldWideNamessincetheymustbeguaranteedunique.Thenames
aretypicallyusedforidentifyingthedevicetooperatingsystems,sinceaddressesareassigned
dynamically.OneoftheprincipalusesforWWNsinStorageAreaNetworksistoenablethe
divisionoffabricsintoseparatezonesforsecurity,loadbalancing,redundancyormanageability
purposes.
ThereatleasteightdifferentnameformatsdistinguishedbytheNetworkAddressAuthority(NAA).
OnlyoneisusedonHPLTOUltriumdrives.ThisistheIEEERegisteredName(NNA=5)andhas
thefollowingformat:
Thisnameismadeupofthreefields:
•NAAIdentifier(4bits).“5”indicatesaIEEERegisteredName.
•IEEECompanyID(24bits).AssignedbyIEEEtothecompany.
•VendorSpecifiedID(36bits).Assignedbythecompany.
Addresses
EachFibreChannelportalsohasaPortAddresswhichisassignedduringloopinitializationand/or
FabricLogin.Thisisa24-bitvalueinthefollowingformat:
TheAL_PAistheArbitratedLoopPhysicalAddress.Thisisnormallyassigneddynamicallyduring
loopinitialization.
Ifthedriveisonaloopthatisnotattachedtoafabric(inotherwords,whenitisonaprivatelink),
thetoptwobyteswillbezero.Iftheloopisattachedtoafabric,thetoptwobytesareassigned
whenitlogsintothefabric.
Together,thethreebytesprovideauniqueaddressontheFibreChannelfabricthatisusedfor
frameaddressing.ItformstheequivalentoftheTargetIDorInitiatorIDinSCSI.
FibreChanneloperation15 
						

							HP'simplementationofnamesandaddresses
TheHPimplementationusesthreeadjacentIEEERegisteredNames:
•Thefirst(lastbits=00)isusedasthePort0WorldWideName.
•Thesecond(lastbits=01)isusedasthePort1WorldWideName(full-heightdrivesonly).
•Thethirdname(lastbits=10)isusedfortheDeviceWorldWideName.
(TheseareassignedduringmanufacturefromHP'spoolofnames,althoughonlythefirstwill
actuallybestoredinthedriveNV-RAM).
Theportaddresseswillbeassignedusingthe‘standard’AL_PAinitializationmechanisms.The
‘FibreChannelPortControlmodepage’controlsthis.Thedrivehastheabilitytosupporthard
addressesaspartofthisscheme.
TherearetwofurtherWWNs,theSCSIDeviceWWN(typicallysetequaltotheNodeWWN)
andtheADCDeviceWWN(lastbits=11)
ThevaluesofthenamescanbeobtainedusingtheDeviceIdentificationVitalProductInformation
Page(partoftheINQUIRYcommand).
Implicationsforlibraries
•Normallyastandalonedrivewilloperateusingitsownfactory-programmed‘hard’names.
•Thedriveknowsitisinalibraryorother‘managed’environmentsinceoneofthesignallines
ontheAutomationInterfacewillbetieddown.Inthisguide,theterm“AutomationInterface”
coversbothACI(AutomationControlInterface)andADI(Automation/DriveInterface).
Inthiscase,thedrivewillnotgoontheFClooporconnecttothefabricuntilitistoldto.The
librarycanoptionallyconfigurenewsoftnames(Port0,Port1forfull-heightdrivesonly,and
NodeName)intothedriveatthispoint.Thedrivewillthenusethisastheoriginofitsnames.
ThelibrarymanufacturerwouldberesponsibleforobtainingthisIEEERegisteredName.It
wouldbeapropertyofthelibrary,notthedrive.
•Ifthelibrarywantsto‘warmswap’drives,itcan.Itjust‘turnsoff’thedrivewiththesoftname
usingtheACIandthenturnsonthesparedrive,downloadingthesamenametoit.
•Ifadriveisremovedfromthelibrary,itwillnothavetheACIsignaltiedlowandsowillrevert
toitsoriginalhardname.Itshouldforgetthesoftnameinthiscase.
•Afterapower-cycleorhardresetsoftnameswillreverttotheoriginalhardnamesassigned
duringmanufacture.
•Ifthelibrarycontrollerbreaks,thedrivewillcontinuetousethesoftnamelastdownloaded.
Thiswillallowdriveaccesswithoutconfusingthehost.
16InterfaceImplementation 
						

							Fieldreplaceableunits
AnFRUcodeidentifieswhichpartofthehardwareisconsideredtohavefailed.Thesecodesturn
upinsensedatabyte14andasthesensecodequalifierforsensecodes4400h(internaltarget
failure)and40XX(diagnosticfailure).
AlthoughtherearenoactualFieldReplaceableUnitsonHPLTOUltriumdrives,thefollowing
sub-assembliescanbereplacedatRepairCentres:
•HeadAssembly
•FrontPanel
•DrivePCA
•Mechanism
CD-ROMemulation(SASdrivesonly)
TheOneButtonDisasterRecovery(OBDR)functionalityinHPLTOUltriumdrivesenablesthemto
emulateCD-ROMdevicesinspecificcircumstances(alsoknownasbeingin“DisasterRecovery”
mode).ThedrivecanthenactasabootdeviceforPCsthatsupportbootingoffCD-ROM.
ACD-ROMcapabledrivecanbeswitchedintoCD-ROMmodebypoweringonwiththeeject
buttonhelddown.Thedrivethenaltersitsbehaviorasfollows:
•Thefrontpanellightsflasha“warbling”sequence.
•CD-ROMcommandsareexecuted(asopposedtotapedrivemodewhentheywouldbe
rejected).CommandsspecifictoCD-ROMmodeareREAD10,READTOCandREAD
CAPACITY.InthecaseofSCSIcommands08h(READ),1Bh(LOAD/UNLOAD)and2Bh
(LOCATE),theseareinterpretedasCD-ROMcommands08h(READ6),1Bh(START/STOP)
and2Bh(SEEK)respectively.
•Writingisdisabled.
•NormalINQUIRYdataismodifiedtoaddafieldindicatingthatthedrivesupportsCDemulation
andtoswitchtheperipheraldevicetypefieldtoindicateaCD-ROMdrive.
•Themodeheaderandmodeblockdescriptoraremodified.
•ACD-Emulationmodepageisadded.
•ModedatachangestoreflectCD-ROMmediumtypeandblocksize.
•Statusreportingbythemediaaccesscheckisaltered.
•Thedrive’ssensedatawhenthemediaisnotreadyforaccessalwaysindicates“loading”.
IfatapeisinsertedwhilethedriveisinCD-ROMmode,thedriveassumesthatitwillcontainan
imageofaCDoffset20blocksintothetape.Itreadsthefirst250kilobytesofthisimageinto
bufferspacereservedforCD-caching.Itthenlooksforaspecialmessage(“EL TORITO
SPECIFICATION”)atthe8thbyteofthe18threcordoftheimage.Ifthedrivefailstofindthis
message,itejectsthetapeandwaitsinCD-ROMmodeforaproperly-writtenCD-imagetapeto
beinserted.
ThedrivewillremaininCD-emulationmodeuntiloneofthefollowingoccurs:
•AMODESELECTcommandswitchesitbacktotapedrivemodeusingtheCD-emulationmode
page.
•ALogicalUnitResettaskmanagementfunctionoraHARD_RESETprimitivesequenceis
received,followingthereadingofatleast100blocksofCD-ROMdatabyahost.
•Theuserpower-cyclesthedriveorresetsitusingtheforced-ejectmechanism.
NOTE:IfthedriveexitsCD-ROMmodethrougheitherofthefirsttwoofthese,thetapewill
remainatthelastlogicalpositionwheninCD-ROMmode.
Fieldreplaceableunits17 
						

							2Messages
Status
AStatusbyteissentfromthedrivetothehostduringtheStatusphaseattheendofeachcommand
asspecifiedintheSCSIspecification,unlessthecommandhasbeenclearedbyanABORTmessage,
byaBUSDEVICERESETmessage,orbyahardreset.
TheStatusbytesthatthedrivereturnsareasfollows:
GOOD:Thisstatusindicatesthatthedrivehassuccessfullycompletedthecommand.00h
CHECKCONDITION:Anyerror,exception,orabnormalconditionthatcausessensedatatobeset
returnsCHECKCONDITION.TheREQUESTSENSEcommandshouldbesentfollowingthisstatusto
determinethenatureoftheerror.
02h
CONDITIONMET:ThisstatuswillneverbereturnedbyanHPLTOUltriumtapedrive.04h
BUSY:Thedriveisunabletoexecutethecommandatthistime.Tryagainlater.Thedrivetriestoavoid
usingthisstatuscodeduringnormaloperation.Itcansometimesbeusedaftercommandshavebeen
aborted,duringpower-onandiftherearemultipleselectinginitiators.
08h
INTERMEDIATE:ThisstatuswillneverbereturnedbyanHPLTOUltriumtapedrive.10h
INTERMEDIATECND:ThisstatuswillneverbereturnedbyanHPLTOUltriumtapedrive.14h
RESERVATIONCONFLICT:Returnedifthedriveisreservedbyanotherparty.SeetheReservationcheck.18h
COMANDTERMINATED:ThisstatuswillneverbereturnedbyanHPLTOUltriumtapedrive.22h
QUEUEFULL28h
ABORTEDCOMMAND40h
18Messages 
						

							3Responseframesandtaskmanagementfunctions
Responseframes
ThissectiondescribestheformatofSASresponseframesreturnedbyHPLTOUltriumtapedrives.
ResponseframesprovideawayforthedrivetoreporttheoutcomeofallSCSIcommandsandtask
managementfunctions:
01234567
Reserved(0)0–7
StatusQualifier(0000h)7
8
DATAPRESReserved(0)10
Status11
Reserved(0)12–15
SenseDataLength(nbytes)(MSB)16
(LSB)19
ResponseDataLength(mbytes)(MSB)20
(LSB)23
ResponseData(ifany)24
23+m
SenseData(ifany)24+m
23+m+n
SpecifiestheformatandcontentoftheStatus,SenseDataLength,ResponseDataLength,
ResponseData,andSenseDatafields:
DATAPRES
DescriptionNameCode
NeitherresponsedatanorsensedataarepresentNO_DATA00b
ResponsedataispresentRESPONSE_DATA01b
SensedataispresentSENSE_DATA10b
Reserved11b
TheStatusbyteisvalidforallresponseframes,unlesstheDATAPRESfieldissetto
RESPONSE_DATA.ItindicatestheoutcomeoftheSCSIcommand:
Status
Thedrivehassuccessfullycompletedthecommand.GOOD00h
Anerror,exception,orabnormalconditionhasoccurred
thatcausessensedatatobeset.Checkthesensedatain
theRESPONSEframetodeterminethenatureoftheerror.
CHECKCONDITION02h
NeverreturnedbyanHPLTOUltriumtapedrive.CONDITIONMET04h
Thedriveisunabletoexecutethecommandatthistime.
Tryagainlater.Thedrivetriestoavoidusingthisstatus
codeduringnormaloperation.
BUSY08h
NeverreturnedbyanHPLTOUltriumtapedrive.INTERMEDIATE10h
Responseframes19 
						

							NeverreturnedbyanHPLTOUltriumtapedrive.INTERMEDIATECND14h
Thedriveisreservedbyanotherparty.SeetheReservation
check.
RESERVATION
CONFLICT
18h
NeverreturnedbyanHPLTOUltriumtapedrive.COMMAND
TERMINATED
22h
Thedrivecannotacceptanothertaskatthemoment
becausetheinternallimithasbeenreached.Tryagain
later.
TASKSETFULL28h
TypicallynotreturnedbyanHPLTOUltriumdrivebutmay
beinsomecircumstances;forexample,onaFibreChannel
drive,ifHostAsendsLogicalUnitResetthenTaskAborted
wouldbesenttoanoutstandingRewindonHostB.
ACAACTIVE30h
FCandSASdrivesonly:CausedbyaThirdPartyHost
Interfacereset.
TASKABORTED40h
IftheDATAPRESfieldissettoRESPONSE_DATA,theStatusandSenseDatafieldsarenot
valid;thedriveisreportingaresponsetoataskmanagementfunctionortoaninvalidrequest
asindicatedbytheresponsecode:
ResponseData
DescriptionCode
Taskmanagementfunctioncompletea00h
Invalidframe02h
Taskmanagementsfunctionnotsupporteda04h
Taskmanagementfunctionfaileda05h
Taskmanagementfunctionsucceededa08h
IncorrectLogicalUnitNumbera09h
Overlappedtagattemptedb0Ah
Allothercodesarereserved.
aOnlyvalidwhenrespondingtoaTASKframe.
bReturnedwhenacommand/taskmanagementfunctionortaskmanagementfunction/task
managementfunctiontagconflicts.
Taskmanagementfunctions
ThissectionincludesallSCSItaskmanagementfunctions,bothsupportedandunsupported.
TaskManagementfunctionsprovideaninitiatorandatargetintheSASdomainwithameansof
managingspecificoperationsortasks.Thesupportedfunctionsarelistedinthischapter.
Inthefollowingtable,allthesupportedtaskmanagementfunctionsusetheLogicalUnitNumber
field,andABORTTASK(01h)andQUERYTASK(80h)alsousetheTagofTasktoBeManaged
field.
DescriptionTaskManagementFunctionCode
PerformstheABORTTASKtaskmanagementfunctionwith:
L=LogicalUnitNumberfield
Q=TagofTasktoBeManagedfield
ABORTTASK01h
PerformstheABORTTASKSETtaskmanagementfunctionwith:
L=LogicalUnitNumberfield
ABORTTASKSET(SASonly)02h
20Responseframesandtaskmanagementfunctions