Filter
Top Products
API Guide
601355 Rev A API Functions 2-999
Functins
• An individual Mount request is waiting on a busy drive.
• An individual Mount request is waiting on a busy media.
Thus, for a successful MultiMount command with two Mount
requests, the client can expect at least four intermediate statuses
(two for the reserve of drives and two for the mount
notification).
VSCMD_MultiMount triggers MediaClass callbacks from
Vo lSer v.
The VSID_MOUNT_HANDLE parameter require that two
Arguments be passed instead of one.
• The first argument passed is the index of the entry in the
Mount handle table.
• The second argument is the mount handle to be stored in the
Mount handle table. The Mount handle table is created and
used internally by the API software and is not visible to the
client.
The MultiMount command does not restrict the Mount request
in its use of mount parameters. All mount parameters are valid
for each individual Mount request.
A MultiMount request is an “all-or-nothing” request. If an
entire MultiMount request cannot be satisfied because of
resource conflicts or limitations, the entire command fails.
Partial mounts can be done if one of the last Mount commands
fails and the previous Mount commands have already
completed. MultiMount does not dismount completed mounts if
one mount fails while another succeeds.
A MultiMount command reserves resources to ensure deadlock
avoidance. After all individual mounts are issued, the resources
are freed.