<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi Folks,<div class=""><br class=""></div><div class="">In dealing with modern LTO-6 and LTO-7 drives, we’ve noted (specifically for IBM devices) that commands set with the IMMED bit unset have started to act as if the bit is set with what should be long running tape motion (SPACE, LOCATE, etc.) commands returning from the device server immediately.</div><div class=""><br class=""></div><div class="">After digging through execution logs and discussing this with our HPE tech team members, we have finally uncovered the new D_BOPC bit that can affect the expected results of such commands. &nbsp;This is not mentioned in the current SSC-5 draft rev 02b, dated Jul 1, 2016.</div><div class=""><br class=""></div><div class="">I recommend that the D_BOPC information be added and that all commands utilizing the IMMED bit be updated to include a reference to the affect of the D_BOPC bit on those commands.</div><div class=""><br class=""></div><div class="">Thanks for your consideration,</div><div class="">Tim</div><div class="">--<br class="">Tim Jones<span class="Apple-tab-span" style="white-space:pre">                                </span><a href="mailto:tjmac@tolisgroup.com" class="">tjmac@tolisgroup.com</a><br class="">President/CTO<span class="Apple-tab-span" style="white-space:pre">                        </span>http://www.tolisgroup.com<br class="">TOLIS Group, Inc.<br class="">480-505-0488 x227<span class="Apple-tab-span" style="white-space:pre">                        </span>480-505-0492 (fax)<br class=""><span><img height="53" width="100" apple-inline="yes" id="1D4840C4-A848-486F-898D-FB28858FE595" apple-width="yes" apple-height="yes" src="cid:ACCF3A9E-C4C7-4AF2-808B-7A2C5E0733D1" class=""></span><br class="">BRU ... Because it's the RESTORE that matters</div><br class=""></body></html>