"elementAddress": "259", "beacon": "disabled", "volser": null } ] Exit with code: 0 

## Turn drive beacon on/off 

Switches on/off the drive beacon LED at the back of the drive. 

PATCH /v1/drives/<location> {“beacon”: <”enabled” | “disabled”>} 

## 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> beacon : A string indicating the current state of the drive beacon LED. This beacon can be seen from the rear of the drive. Values include: “enabled”  (LED is flashing) and “disabled”  (LED is off). 

Note: if the drive is replaced while the beacon is enabled, the state of the physical LED may not match this attribute. In this case, the beacon should be disabled. 

When the PATCH /v1/drives/drive_F1C2R3 {"beacon": "enabled"}  command runs successfully, the system returns output to your display as shown in Example 6-38. 

[root@TRON ITDT]# ./itdt -f /dev/sg34 ros PATCH /v1/drives/drive_F1C2R3 {"beacon": "enabled"} 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_F1C2R3 before and after command execution, we see that the beacon changed from “disabled”  to “enabled” : 

Before command execution: Example 6-39. 

[root@TRON ITDT]# ./itdt -f /dev/sg34 ros GET /v1/drives/drive_F1C2R3 HTTP/1.1 200 OK Content-Type: application/json Content-Length: 395 [ 

