Assign or Unassign Data Cartridges Directly to or from Logical Library

Edit online

Data cartridges can be assigns directly to logical libraries outside the normal VOLSER ranges.

These cartridges would show as assigned to this logical library when queried, but the VOLSER range would not be updated to reflect their assignment.

If a cartridge currently assigned to a logical library and a request is sent to assign it to a new library, it will be unassigned from the original library first.

Request syntax

POST /v1/logicalLibraries/{name}/assignDataCartridges {"cartridges": [<VOLSER1|internalAddress1>, <VOLSER2|internalAddress2> ...]}
Assign Data Cartridges directly to Logical Library

POST /v1/logicalLibraries/{name}/unassignDataCartridges {"cartridges": [<VOLSER1|internalAddress1>, <VOLSER2|internalAddress2> ...]}
Unassign Data Cartridges from Logical Library

Path parameters

cartridge (array of strings)

A set of volume serial numbers (VOLSERs) or bar codes that identifies the cartridge to the host. This can also a 6-character hex strings that represent the internal address which is a unique identifier of the cartridge within the library that is used when duplicate VOLSERs exists.

Example

> POST /v1/logicalLibraries/myLL1/assignDataCartridges {"cartridges": ["000000", "000001", 
"000002", "000003", "000004", "000006", "000007"]}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 0

> POST /v1/logicalLibraries/myLL1/unassignDataCartridges {"cartridges": "000000"}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: 0

Error handling

  • Returns 404 Not Found if the cartridge does not exist for the given VOLSER or internal address.
  • Returns 422 Unprocessable Entry if the logical library mediaType does not match that of the cartridge.