QUERY Name
START Name
start - Initiates ACSLM request processing.
Description
The start request places the ACSLM in STATE_RUN, enabling processing of Storage Server requests. The start command has no options.
If the start is successful, the Storage Server becomes ready to receive requests. If the start is unsuccessful, the Storage Server does not become ready to receive requests.
See the Library Request Processing section in Chapter 2 for details on the possible Storage Server states.
Requests
Request Format
struct start_request { .
} ;
IPC HEADER MESSAGE HEADER
Request Values
ipc _header;
message_header;
Within MESSAGE_HEADER, command is COMMAND START.
Responses
Intermediate Response Format Not applicable.
Final Response Format
struct start_response IPC HEADER
MESSAGE HEADER RESPONSE STATUS } ;
ipc _header;
message_header;
message_status ;
start
Notes
ACSLM Command Structures
Final Response Values
Within MESSAGE_HEADER, command is COMMAND_START.
Within RESPONSE_STATUS, status is the disposition of the request.
Following are status values specific to this command.
• STATUS_SUCCESS if the Storage Server was successfully put in STATE RUN.
Following are common RESPONSE_STATUS status values. See the Common Statuses section in Chapter 3 for their descriptions.
•
•
•
•
•
STATUS INVALID OPTION
-
-STATUS LIBRARY NOT AVAILABLE
-
-STATUS_MESSAGE_TOO_LARGE STATUS_MESSAGE_TOO_SMALL STATUS UNSUPPORTED OPTION
-
-Final Response Values - Cancelled RequestNot applicable.
None.
See Also
• The idle command for infonnation on placing the Storage Server in STATE IDLE.
• The query command for details on displaying the current state of the Storage Server.
• Appendix A for entries that may be written to the Event Log.
ACSLM Command Structures vary VARY
Name
Description
vary - Changes the state of an ACS, LSM, library drive or port.
The vary request changes the state of an ACS, LSM, library drive, or port. Only one device type at a time can be varied. Within that type, from one to MAX _ ID different devices can be specified in each request.
The message_option FORCE changes the state of the device abruptly.
FORCE is valid only when the device is an ACS or an LSM and it device varied offline.
An ACS, LSM, or library drive can be changed to online, offline, or diagnostic. A port can be changed to online or offline.
Device States
A device can be in one of five states, as described below:
~ STATE_ONLINE. The nonnal operating state. The device is available for library processing.
• STATE_OFFLINE. A state in which the device is'logically disabled.
Requests involving offline devices are rejected.
• STATE OFFLINE PENDING.
- -
A transition state that occurs when an ACS or LSM is taken from online or diagnostic to offline. All new requests for the device are rejected, but current and pendingrequests are processed to completion. This state is not valid for cartridge drives or ports.
• STATE RECOVERY. A transition state that occurs when an ACS or LSM is taken from omine to diagnostic or online. A recovery process is perfonned. New requests are rejected while the device is in this state. This state is not valid for cartridge drives or ports.
• STATE DIAGNOSTIC. A state in which the device is not available to client application requests, but is available to operator requests from the Command Processor. This state allows for diagnostic activity to be perfonned on the device without interference from client applications. This state is not valid for ports.
vary ACSLM Command Structures Table 4-1 identifies which states are valid for each device.
Table 4-1. Valid Device States
Devic~ Online Qmin~ Omine-Pend. Recover!
ACS x x x x
LSM x x x x
Drive x x
Port x x
Device State Transitions
The vary request moves a device between these states. The transitions occur as follows:
Diag. the STATE_RECOVERY state while it attempts to recover in-transit cartridges. When this recovery process has been completed successfully, the device is placed in the STATE_ONLINE state.
• A vary offline request with the force message_option puts the device in the STATE_OFFLINE state immediately, causing any current or pending requests for the device to be aborted.
• An unqualified vary offline request (that is, without the force message_option) is processed according to the type of device:
- For an ACS or an LSM, the request causes the device to go into the STATE_OFFLINE_PENDING state initially. The ACSLM processes all current and pending requests for the device to completion before placing it in the STATE_OFFLINE state.
- For a cartridge drive, the request is rejected if the drive is in use. If the drive is available, it is placed in the STATE_OFFLINE
state immediately.
- For a port, the request is rejected if the ACS it is connected to is online and it is the only online port for that ACS. If the ACS is in the STATE_OFFLINE state, or if there are other ports in the
STATE_ONLINE state for that ACS, the port is placed in the
STATE_OFFLINE state immediately.
• A vary diagnostic request places the device in
STATE_DIAGNOSTIC. The ACSLM processes all current and pending requests for the device to completion. It accepts new requests from the ACSSA, but rejects new requests from a CSI. A port cannot be
·ACSLM Command Structures vary
Within MESSAGE_HEADER, command is COMMAND_VARY.
Within MESSAGE_HEADER, message_options can be FORCE if the state is
STATE_OFFLINE. This causes request processing for the requested
ACS or LSM to be stopped immediately. The specified component's state is marked STATE OFFLINE in the data base.
state is one of the following:
STATE ONLINE STATE OFFLINE STATE DIAGNOSTIC
state STATE_DIAGNOSTIC cannot be used when type is TYPE_PORT.
type is one of the following:
TYPE ACS TYPE LSM TYPE PORT TYPE DRIVE
Only one type is allowed in a single request.
count is the number of identifier entries that follow. count must be 1
to MAX ID.
Within identifier, the device ID is one of the following, based on type:
vary ACSLM Command Structures
Responses
Intermediate Response Format Not applicable.
Final Response Format
struct vary_response
Final Response Values
ipc _header;
Within MESSAGE_HEADER, command is COMMAND_VARY.
Within RESPONSE_STATUS, status is the disposition of the request.
Following are status values specific to this command.
• STATUS_SUCCESS if the fixed portion of the request was correct.
Following are common RESPONSE_STATUS status values. See the Common Statuses section in Chapter 3 for their descriptions.
• STATUS CONFIGURATION ERROR -
-• STATUS COUNT TOO LARGE -
-• STATUS COUNT TOO SMALL -
-• STATUS DATABASE ERROR
-
-ACSLM Command Structures
• S TATUS_INVALID_OPTI ON
• STATUS INVALID STATE
-
-• STATUS_INVALID_TYPE
• STATUS_LIBRARY_BUSY
• STATUS_LIBRARY_FAILURE
• STATUS_LIBRARY_NOT_AVAILABLE
• STATUS_MESSAGE_TOO_LARGE
• STATUS_MESSAGE_TOO_SMALL
• STATUS_PROCES S_FAI LURE
• STATUS UNSUPPORTED OPTION
-
-• S TATUS_UNSUPPORTED_S TATE
• STATUS UNSUPPORTED TYPE - -state is one of the following:
STATE ONLINE STATE OFFLINE STATE DIAGNOSTIC type is one of the following:
TYPE ACS TYPE LSM' TYPE PORT TYPE DRIVE
vary
count is the number of device status entries that follow. count must be
1 to MAX ID.
Within device_status, the device identifier is one of the following, based on type:
acs Ism id port id drive id
Within device_status, status is the disposition of the particular device.
Following are status values specific to this command:
• STATUS_RECOVERY_INCOMPLETE if recovery of in-transit cartridges is unsuccessful while varying an LSM or ACS online. The LSM is marked STATE_ONLINE in the data base, but the unrecorded in-transit cartridges may restrict use of PTPs or the robot's hands.
An unsolicited message is sent to the ACSSA.
vary ACSLM Command Structures
Notes
• STATUS_SUCCESS if the device was successfully varied to the specified state.
• STATUS_VARY_DISALLOWED for any of the following conditions:
- The request specifies an ACS or LSM that is currently in the STATE_OFFLINE_PENDING or STATE_RECOVERY state. These are transition states which are one-way only and indicate a vary request in progress.
The request specifies. an ACS, LSM, or library drive be varied to or from STATE_DIAGNOSTIC and the originator is not the ACSSA.
- The request is to vary an LSM online, but the ACS to which the LSM is attached is offline.
- IT the request is to vary an ACS, but not all LSMs within the ACS can be varied accordingly. The entire request fails, and all LSMs are left in their original state.
Following are common device_status status values. See the Common
Statuses section in Chapter 3 for their descriptions.
• STATUS_ACS_NOT_IN_LIBRARY
• STATUS_DRIVE_NOT_IN_LIBRARY
• STATUS_LSM_NOT_IN_LIBRARY
• STATUS_PORT_NOT_IN_LIBRARY
• STATUS INVALID ACS·
-• STATUS INVALID DRIVE
-• STATUS INVALID LSM
-• STATUS_INVALID_PORT
• STATUS_LIBRARY_BUSY
• STATUS LIBRARY FAILURE
-
-Final Response Values - Cancelled Request Not applicable.
• A vary request for an ACS is applied to all LSMs belonging to that ACS. IT an LSM is not available, an error status value will be returned in the Ism_status status.
• When a device changes state, a STATUS_DIAGNOSTIC,
STATUS_ONLINE, or STATUS_OFFLINE unsolicited message is sent to the ACSSA.
• If during recovery of in-transit cartridges either no available storage cells can be found or a cartridge label fails to validate, the cartridge
is moved to the CAP. A unsolicited
ACSLM Command Structures vary
See Also
message is sent to the ACSSA to notify the operator to empty the CAP. IT the CAP is full or cannot accept all in-transit cartridges, recovery of in-transit cartridges is unsuccessful.
• The query command for details or displaying the current state of a library device.
• Appendix A for entries that may be written to the Event Log.
vary ACSLM Command Structures
(INTENTIONALL Y LEFf BLANK)
OVERVIEW
CHAPTER 5:
CSIPROCESSES
This chapter describes the basic functions perfonned by the CSI. It also identifies function calls and common data structures used by the CSI. See Appendix C: XDR Translation Functions for listings of StorageTek-supplied functions. See Chapter 7: CSI Data Structures for the fonnats and contents of the data structures.
Note: Since the functions of the SSI are essentially reciprocal to those of the CSI, an understanding of CSI functionality is required in order to derive SSI requirements. See Chapter 6: SSI Requirements for specific details on SSI requirements and programming.
This chapter covers the following topics: