In Tivoli Storage Manager server access to a volume in a storage pool is determined by the access mode

assigned to that volume. You can manually change the access mode of a volume, or the server can change
the access mode based on what happens when it tries to access a volume.
For example, if the server cannot write to a volume having read/write access mode, the server
automatically changes the access mode to read-only.

Access Modes of STGPool Volumes:

The following access modes apply to storage pool volumes:
Read/write
Allows files to be read from or written to a volume in the storage pool. If the server cannot write
to a read/write access volume, the server automatically changes the access mode to read-only. If
a scratch volume that is empty and has an access mode of off-site is updated so that the access
mode is read/write, the volume is deleted from the database.
Read-only
Allows files to be read from but not written to a disk or tape volume. If a scratch volume that is
empty and has an access mode of off-site is updated so that the access mode is read-only, the
volume is deleted from the database.
Unavailable
Specifies that the volume is not available for any type of access by the server. You must vary
offline a random-access volume before you can change its access mode to unavailable. To vary a
volume offline, use the VARY command. If a scratch volume that is empty and has an access
mode of off-site is updated so that the access mode is unavailable, the volume is deleted from
the database.
Destroyed
Specifies that a primary storage pool volume has been permanently damaged. Neither users nor
system processes (like migration) can access files stored on the volume.
This access mode is used to indicate an entire volume that should be restored using
the RESTORE STGPOOL or RESTORE VOLUME command. After all files on a destroyed volume
are restored to other volumes, the destroyed volume is automatically deleted from the
database.
Only volumes in primary storage pools can be updated to an access mode of destroyed. You
must vary offline a random-access volume before you can change its access mode to destroyed.
To vary a volume offline, use the VARY command. Once you update a random-access storage
pool volume to destroyed, you cannot vary the volume online without first changing the access
mode.
If you update a sequential-access storage pool volume to destroyed, the server does not attempt
to mount the volume. If a volume contains no files and the UPDATE VOLUME command is used
to change the access mode to destroyed, the volume is deleted from the database.
Offsite

Specifies that a copy storage pool volume or active-data pool volume is at an off-site location and
therefore cannot be mounted. Use this mode to help you track volumes that are off-site. The
server treats off-site volumes differently, as follows:

Mount requests are not generated for off-site volumes.

Data can be reclaimed or moved from off-site volumes by retrieving files from other
storage pools.
Empty, off-site scratch volumes are not deleted from the copy storage pool or from the
active-data pool.

You can only update volumes in a copy storage pool or an active-data pool to off-site access
mode. Volumes that have the device type of SERVER (volumes that are actually archived objects
stored on another Tivoli Storage Manager server) cannot have an access mode of off-site.

STATUS modes of STGPool Volumes

Specifies that output is restricted by volume status. This parameter is optional. You can specify multiple
status values by separating values with commas and no intervening spaces. If you do not specify a value
for this parameter, output is not restricted by volume status. Possible values are:
ONline
Display random access volumes that are available to the server.
OFfline
Display random access volumes that are not available to the server.
EMPty
Display sequential access volumes that have no data.
PENding
Display volumes with a status of PENDING. These could be sequential-access volumes from which all
files have been deleted, but for which the time specified by the REUSEDELAY parameter on the DEFINE
STGPOOL command has not elapsed. These volumes could also be random-access disk volumes that
were deleted, but that still contain discarded data that is waiting to be shredded. After the data is
shredded, the volume will be physically deleted.
FILling
Display sequential access volumes that the server has written to but has not yet filled to capacity.
FULl
Display sequential access volumes that the server has filled.

Examples
To check the Access mode and Status of a particular volume, run this below command
query volume <volumename> f=d
To update the Access mode and Status of a particular volume, run this below command

>>-UPDate Volume-------volume_name------------------------------>

>--+-------------------------------+---------------------------->
'-ACCess--=--+-READWrite------+-'
+-READOnly-------+
+-UNAVailable----+
|
(2) |
+-DEStroyed------+
|
(3) |
'-OFfsite--------'
>--+----------------------------+------------------------------->
|
(4)
|
'-LOcation-------=--location-'
.-WHERESTGpool--=--*---------.
>--+----------------------------+------------------------------->
'-WHERESTGpool--=--pool_name-'
.-WHEREDEVclass--=--*-----------------.
>--+-------------------------------------+---------------------->
'-WHEREDEVclass--=--device_class_name-'
>--+-------------------------------------+---------------------->
|
.-,---------------. |
|
V
||
'-WHEREACCess--=----+-READWrite---+-+-'
+-READOnly----+
+-UNAVailable-+
+-OFfsite-----+
'-DEStroyed---'
>--+---------------------------------+-------------------------->
|
.-,-----------. |
|
V
||
'-WHERESTatus--=----+-ONline--+-+-'
+-OFfline-+
+-EMPty---+
+-PENding-+
+-FILling-+
'-FULl----'
.-Preview--=--No------.
>--+---------------------+-------------------------------------><
'-Preview--=--+-No--+-'
'-Yes-'

For example to update a volume volume007 access mode to readwrite

update volume <volume007 access=readwrite