ACL OUT command coordination with other commands

[Ralph Weber]

* From the T10 Reflector (t10 at t10.org), posted by:
* Ralph Weber <ralphoweber at compuserve.com>
*
One of the topics left open by last week's Access Controls
conference call was specific wording on how the processing
of an ACL OUT command with MANAGE ACL or DISABLE ACCESS
CONTROLS service action affects other commands concurrently
in the queue.  I am proposing the wording below to cover
that issue.  If you have any enhancements or corrections
for this wording, please reply to the reflector (so that
Jim Hafner can see the changes).

Upon successful completion of an ACL OUT command with the MANAGE ACL
or DISABLE ACCESS CONTROLS service action, the new access control
state defined by that command shall apply to all tasks that
subsequently enter the enabled task state.  Tasks that have modified
the media, mode pages, or equivalent target elements shall not be
affected by an ACL OUT command that subsequently enters the task
enabled state.  Tasks in the enabled task state that have not
modified the media, mode pages, or equivalent target elements may or
may not be affected by an ACL OUT command that subsequently enters
the task enabled state.  The access control state in effect prior to
when the ACL OUT command (with the MANAGE ACL or DISABLE ACCESS
CONTROLS service action) entered the enabled task state shall apply
to all tasks that are not affected by the ACL OUT command.

Note: A task completes all its media modifications etc. under the
control of a single access control state, either the state in effect
prior to processing of the ACL OUT command or the state in effect
following the processing of the ACL OUT command.  Once a task has
begun its media modifications etc., changes in the access control
state have no effect on the task.

Thanks.

Ralph...




*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org