Modify VOLSER range

Edit online

Modifies an existing VOLSER range and its import and export policies. The VOLSER range is identified by its start and end values.

Request Syntax

PUT /v1/volserRanges {"mediaType": <"LTO"|"3592">, "start": <starting VOLSER<, "end": <ending VOLSER>, "assignOnImportTo": <null|<LL name>>, "reassignOnExportTo": <null | <LL name>>}

Request Body Parameters

mediaType (string, required): Cartridge media type supported by the VOLSER range. One of "LTO" or "3592". This value is used along with start and end to identify the existing VOLSER range to modify.
start (string, required): The starting VOLSER, inclusive, of the VOLSER range to modify. This value is used to identify the existing VOLSER range.
end (string, required): The ending VOLSER, inclusive, of the VOLSER range to modify. This value is used to identify the existing VOLSER range.
assignOnImportTo (string, optional): This is either null (default) if no assignment should be done when a cartridge in this range is inserted into the library, or the name of the logical library to assign newly imported cartridges to in this range. Both assignOnImportTo and reassignOnExportTo cannot be null. At least one must be specified.
reassignOnExportTo (string, optional): This is either null (default) if no reassignment should be done when a cartridge in this range is exported to an I/O station by a host, or the name of the logical library to reassign cartridges exported by a host to in this range instead of exporting them. Both assignOnImportTo and reassignOnExportTo cannot be null. At least one must be specified.

Safeguarded Logical Library Considerations

Important: When modifying a VOLSER range that targets a safeguarded logical library (either through assignOnImportTo or reassignOnExportTo), the following restrictions apply:

A local session is required to modify VOLSER ranges that assign or reassign cartridges to safeguarded logical libraries. Remote sessions will be rejected.
Safeguarded logical libraries enforce on-site cartridge management to ensure data protection and compliance requirements are met.
If the operation fails due to remote session restrictions, ensure you are connected through a local network interface before retrying.

Example

> PUT /v1/volserRanges {"mediaType": "LTO", "start": "000000", "end": "000ZZZ", "assignOnImportTo": "myLL2", "reassignOnExportTo": null}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 10