Table 34 Message Body JSON Objects for Volume Modification Request (continued)
Member
rmUsrSpcAllocLimit
The volume policies object is described in
set to the staleSS, oneHost, or zeroDetect policies.
Volume Modification Success
Upon a successful request to modify a VV, the HTTP code 200 OK is returned. The location portion
of the response header will contain the new URI for updated VV:
/api/v1/volumes/<volume name>
Volume Modification Errors
Possible error codes following a VV modification request are shown in
generic API error codes, see
Table 35 Volume Modification Request Error Codes
API Error
INV_INPUT_WARN_GT_LIMIT
INV_INPUT_USR_ALRT_NON_TPVV
INV_INPUT_RETAIN_GT_EXPIRE
INV_INPUT_VV_POLICY
INV_INPUT_EXCEEDS_LENGTH
INV_INPUT_TIME
INV_OPERATION_VV_MODIFY_USR_CPG_TPVV
UNLICENSED_FEATURE
46
Working with Storage Volumes
JSON Type
API Type
Boolean
Table 29 (page
Table 5 (page
17).
Ignored Values
None
40). The policies object may be
Table 35 (page
HTTP Code
400 Bad Request
400 Bad Request
400 Bad Request
400 Bad Request
400 Bad Request
400 Bad Request
403 Forbidden
400 Bad Request
Description
(Since WSAPI 1.2)
If true, remove User
Space allocation limit.
If False, and limit
value is 0, then
ignore.
If False, and limit
value is positive, then
set.
(Since WSAPI 1.2)
46). For
Description
Allocation warning level
is higher than the limit.
(Since WSAPI 1.2)
User space allocation
alerts are valid only with
a TPVV.
Retention time is greater
than expiration time.
Invalid policy
specification (for
example, caching or
system is set to true).
(Since WSAPI 1.2)
Invalid input: string
length exceeds limit.
(Since WSAPI 1.2)
Invalid time specified.
usr_cpg cannot be
modified on a TPVV.
(Since WSAPI 1.2)
Retention time cannot be
modified on a system