"firmware": "3DCB", "encryption": "disabled", "wwnn": "500507604419fff6", "elementAddress": "259", "beacon": "disabled", "volser": "CLN481JA" } ] Exit with code: 0 

## Modify drive use 

Modify the use of the drive to be a data access, control path, or verification drive. 

PATCH /v1/drives/<location> {"use": <”access” | “controlPath” | “verification”>} 

## Path parameters 

The following list describes the parameter: 

GLYPH<SM590000> location:  A string representing the location of the tape drive. This is also the unique identifier for the drive. The format is “drive_F<f>C<c>R<r>”  where  “f”  is the frame, “c”  is the column, and “r”  is the row the drive is installed in. 

## Request body parameters 

The following list describes the parameter: 

GLYPH<SM590000> use:  A string representing the assigned use this tape drive has been given within the logical library. Values include: 

– access: data access drive 

– controlPath: data access and control path drive 

– verification: media verification drive 

When the PATCH /v1/drives  command runs successfully, the system returns output to your display as shown in Example 6-35. 

[root@TRON ITDT]# ./itdt -f /dev/sg34 ros PATCH /v1/drives/drive_F1C2R3 {"use": "controlPath"} HTTP/1.1 200 OK Content-Type: application/json Content-Length: 0 Exit with code: 0 

The command prompt returns without comments. But if we check status of the drive_F2C3R1 before and after command execution, we see that it was changed to controlPath usage: 

