You can define that a certain volume is 'read-only'.

This information at the moment being is used by the system only to decide if a new file should be created when updating an existing object. When a binary data content attribute of an existing object is modified the system usually writes the new data on top of the old one (except when it is generating a new version) - if the old data is in a read-only volume the system will instead generate a new file.

The volumes specified in the schema and in the partition volume maps are assumed to be read-write - the system will use them to create new files without checking their read-only status. This might change in the future.

The 'changevolume' command do check if the destination volume is read-only - and fails with an error message if this is the case.

In general, volumes should be set to 'read-only' if they contain data that has been imported 'in place' and should not be used to store new data or data that is going to be changed.

Notes

•For the description of the changevolume command, see changevolume.

•For additional information, see the discussion on Tera forum in http://forum.teradp.com/topic.asp?TOPIC_ID=737.