In this chapter, you will learn how to use the ACSLS commands, including general command syntax and reference information.
Creates or updates the database inventory of the volumes in a library component.
Cancels a current or pending request.
Removes all active and pending locks on drives or cartridges.
Creates or modifies scratch pools.
Deletes empty scratch pools.
Dismounts a cartridge.
Ejects one or more cartridges from the ACS.
Sets a CAP to enter mode.
Stops ACSLS from processing new requests.
Locks (dedicates) a cartridge or drive to a user.
Exits from cmd_proc.
moves a specified cartridge to an available storage cell in a specified LSM.
Mounts a data or scratch cartridge.
Displays the status of a library component.
Sets various attributes of different library components.
Displays your lock ID or user ID.
Starts ACSLS request processing.
Manually switches ACS management from the ACS's active LMU to the standby LMU.
Removes active locks on cartridges or drives.
Indicates the amount of elapsed time ACSLS has been enabled and/or the last restart of the ACSLS library manager.
Changes the state of an ACS, LSM, CAP, drive, or port.
This section describes the general syntax of the ACSLS commands. The following sections fully describe each command, including its syntax.
ACSLS commands use the following general syntax:
command type identifier state options
Where:
type identifier
is the ACS component and its identifier; see "Component Types and Identifiers" for more information.
state
is a device state for the vary command only.
options
are command options; see the description of the command you want to run.
Note the following syntax rules:
Enter commands in the order shown above (command name, followed by the component and its identifier, the state and any options).
This chapter shows commands in lowercase, but you can enter commands in any combination of lowercase and uppercase letters.
Underlines show minimum abbreviations for commands and keywords. For example, query server and q ser are both valid forms of the query server command.
Ellipses (...) indicate that you can repeat an identifier.
Brackets [ ] enclose optional options.
The following table describes the valid ranges of values for each of the ACS component identifiers. You can specify a maximum of 42 identifiers for each type. See specific command descriptions for the valid component types of each command.
Note:
The identifiers specified in the following table represent valid ranges of values supported by the software. Your LSM type and library configuration determine what identifier values are valid for your particular site.Table 12-1 ACSLS Component Types and Identifiers
| Component | Type | Identifier | Valid Values |
|---|---|---|---|
|
entire library |
serve |
none |
none |
|
ACS |
ac |
|
acs( lsm( |
|
LSM |
ls |
|
acs( lsm( |
|
LSM panel |
pane |
|
acs( lsm( panel( |
|
LSM subpanelFoot 1 |
subpane |
|
acs( lsm( panel( startrow( startcolumn( endrow( endcolumn( |
|
LSM storage cell |
subpane |
|
acs( lsm( panel( row( column( |
|
CAP |
cap |
|
acs( lsm( cap( An asterisk (*) in the cap_id does the following: acs,lsm,* - causes ACSLS to select the highest priority available CAP in the LSM. acs,* - causes ACSLS to select the highest priority available CAP in the ACS. * - for an enter request causes ACSLS to select the CAP in the LSM with the most free cells. * - for an eject request causes ACSLS to select the highest priority CAP in each ACS with a cartridge designated for ejection. |
|
drive |
driv |
drive_id |
acs( lsm( panel( drive( |
|
drive type |
driv |
|
Up to a 10-character drive type identifier; can be any combination of numbers ( |
|
port |
por |
|
acs( port( |
|
volume serial number of a data or scratch cartridge or a cleaning cartridge |
volume, |
|
Six-character identifier consisting of any combination of numbers ( Use single or double quotes to enclose volsers with leading or trailing spaces. Do not specify volsers with embedded spaces. |
|
range of volume serial numbers |
volume |
|
Specifies an ascending range of volumes separated by a dash ( If the ALPHANUM_VOL_RANGES dynamic variable is set to FALSE (default): ACSLS supports the starting and ending vol_ids of the range that are specified as complete vol_ids (Ex: AAA000-AAA999). Specify only the right-most numeric portions of the volsers as the range. All preceding characters must be identical. *** If the ALPHANUM_VOL_RANGES dynamic variable is set to TRUE: *** Use single or double quotes to enclose volsers in a range with leading or trailing spaces. The range must be in ascending sequence per the ACSII collating sequence. |
|
volume media type |
medi |
|
Up to a 10-character media type identifier; can be any combination of numbers ( |
|
volume owner |
owne |
|
|
|
scratch pool |
poo |
|
Decimal number ( |
|
ACSLS request |
reques |
|
Unique decimal number ( |
|
drive or volume lock |
loc |
|
Decimal number ( |
|
ACSLS request |
reques |
|
unique numeric ( |
Footnote 1 The ending row (and column) must be greater than or equal to the beginning row (and column).Only cells within the beginning and ending matrix are audited: the matrix starts with the beginning row and beginning column and extends to the ending row and ending column.
A common error message appears if ACSLS rejects a command because of a syntax error, invalid identifier, type, option, process failure, database error, and so forth. For more information on common error messages, see ACSLS Messages.
If you enter a command that you cannot use, the following message appears:
Command access denied.
If you specify a volume that you cannot access, the following message appears:
Volume access denied.
The following section describes the ACSLS commands.
The audit command updates the ACSLS database to match the actual inventory of library cartridges.
You must always perform an audit, if:
This is a new library.
To re-synchronize the ACSLS database with the contents of the library.
One or more modules have been added, removed or swapped.
Cartridges have been manually added or removed through the door.
After library configuration settings have changed.
If ACSLS does not know the location of one or more cartridges in the library.
If a library has been expanded and you are auditing it for the first time.
When a SL8500 has been expanded, see the procedures described in "Understanding SL8500 Internal Addresses and ACSLS Addresses", to audit it for the first time.
audit cap_id type identifier...
cap_id
specifies the CAP that ACSLS uses to eject any errant volumes. You can specify a particular cap or enter an asterisk (*), which causes ACSLS to select the highest priority CAP.
You can specify the server or multiple ACSs only if CAP priority has been set in each ACS. You must specify an asterisk for the cap_id to allow automatic selection of a CAP in each ACS.
A single LSM audit waits until ACSLS updates the database, then reserves the CAP if required to eject errant volumes.
type identifier
specifies a library component. The following table lists the components you can audit.
Table 12-2 Valid Components for Audit
| Library Component | type | identifier |
|---|---|---|
|
all libraries |
|
none |
|
ACS |
|
acs_id |
|
LSM |
|
lsm_id |
|
LSM panel |
|
panel_id |
|
LSM subpanel |
|
subpanel_id |
You can specify multiple ACSs, LSMs, panels, or subpanels in a single audit request. You cannot specify overlapping subpanels.
You can specify the server or multiple ACSs only if CAP priority has been set in each ACS. You must specify an asterisk for the cap_id to allow automatic selection of a CAP in each ACS. If this is not done, audit cannot eject any invalid cartridges found.
When you audit the server or an ACS, the parent audit process creates a separate audit process for each LSM. These LSM audits run in parallel and process panel-by-panel in ascending panel_id sequence. To audit all LSMs in all libraries or an ACS, just audit the server or ACS. There is no need to run multiple, separate LSM audits.
However, within an LSM, regardless of the order in which you specify multiple components the audit processes these components in ascending order by acs_id, lsm_id panel_id, subpanel_id. For example, the audit will process panel 0,0,9 before subpanel 0,0,10,1,7 even if you specify the subpanel first.
An audit updates the ACSLS database to match the actual inventory of library cartridges. You run an audit to:
Create volume information in the database if you do not enter cartridges through the CAP. For example, run an audit if you add an LSM to your library, open the LSM door and manually add cartridges to the LSM.
Resolve discrepancies between the library and the database. For example, run an audit if you open an LSM door and manually remove cartridges instead of ejecting them through the CAP. The audit deletes information for the removed cartridges from the database.
View the contents of cells specified by the audit (you must have a display monitor connected to the LSM robots' vision system).
Note:
Audit recognizes particular models of cleaning cartridges and will record them in the database as cleaning cartridges. Theaudit command also sets the max_uses for new cleaning cartridges it encounters appropriately for each type of cleaning cartridge.Note:
Whenaudit cannot find a cartridge in any recorded location (cell and possibly drive), audit either marks the cartridge as absent (if absent volume retention is enabled) or deletes the volume. When audit deletes the volume, it removes all information about the volume from the database, including volume information and customer-supplied information about access control, scratch status, lock IDs, and pool IDs. If audit later finds the cartridge in another location, it re-adds the volume information, but the customer-supplied information is lost.An audit ejects errant volumes and deletes their information from the database. An errant volume has:
An external label that duplicates one already scanned.
A missing or unreadable external label and no virtual label.
An invalid media type.
Audits only apply to LSM storage cells, not to drives or CAPs. ACSLS displays cmd_proc messages during the audit and records any database changes from the audit in the Event Log. If volume statistics logging is enabled, ACSLS records additional volume found and volume not found messages in the acsss_stats.log. See "Creating a Logging Volume Statistics Report" for more information.
HINT: Use the following guidelines for running an audit:
The ACS or LSM being audited must be either online or in diagnostic state. Normal library processing (including mounts and dismounts) can occur during an audit, although library processing slows down the audit.
The difference between online and diagnostic states, is: an audit in diagnostic state can only be performed through the cmd_proc. Client requests are rejected while the LSM is in the diagnostic state. This state is faster because the audit now has exclusive run of the library without competing mount/dismount requests that could otherwise be submitted from the client.
After you start an audit on an entire LSM, you cannot start another audit on the same LSM. You must cancel and rerun the audit.
You can cancel any audit request, but ACSLS will always finish auditing the current panel or subpanel. When you cancel an audit, some or all of the cartridges marked for ejection may not be ejected. When you cancel an audit, cartridges already ejected are not re-entered.
Caution:
If youcancel an audit, or if there is a library or ACSLS hardware or software failure during the audit, you must rerun the same audit. Cartridges marked for ejection but not actually ejected during the first audit are no longer in the database and are not under ACSLS control.To audit the entire library and specify the highest priority CAP in each ACS for ejections:
audit * server
To audit LSM 0,1 and specify CAP 0,1,1 for ejections:
audit 0,1,1 lsm 0,x
To audit panel 10 of LSM 0,1 and specify the highest priority CAP in LSM 0,1 for ejections:
audit 0,1,* panel 0,1,10
Note:
A cell cannot be audited if it is reserved by another process. If a cell is reserved, ACSLS rechecks the database until the cell becomes available up to a maximum of 60 retries. If the cell is still unavailable, theaudit skips the cell and logs a message to the Event Log.See also:
| For information about... | See... |
|---|---|
| Guidelines for auditing the library | "Specifying ACS Numbers" |
| Cancelling a command | "cancel" |
| Displaying CAP status | "query cap" |
| Displaying ACSLS and library status | "query server" |
| Displaying ACS status | "query acs" |
| Displaying LSM status | "query lsm" |
| Setting CAP selection priority | "set cap priority" |
| Setting CAP mode (manual or automatic) | "set cap mode" |
| Changing the state of a library component | "vary" |
The following section discusses audit messages.
The following message appears when the audit completes successfully.
Audit: Audit completed, Success.
In addition, one of the following messages appears to confirm which component was audited:
Audit: Audit of storage server, valid
Audit: Audit of ACS, acs_id, status valid
Audit: Audit of LSM, lsm_id, panel_id, valid
Audit: Audit of panel, panel_id, valid
Audit: Audit of subpanel, subpanel_id, valid
HINT: If you audit an invalid cell location (that is just above or below a drive or on an extra column), ACSLS returns a success message to allow audits to work with PTPs.
Intermediate messages consist of a two-line display with the following first line:
Audit: Intermediate response: Audit activity.
One of the following messages appears on the second line:
Audit: Volume ejected, unreadable label.
Explanation: ACSLS ejected a cartridge that had:
No external label
No virtual label, or
An unreadable label
Audit: Volume vol_id will be ejected, duplicate label.
Explanation: ACSLS ejected with a duplicate external label within the range of cells being audited.
Variable: vol_id is the volume with the duplicate label.
Audit: Volume vol_id found.
Explanation: The audit found a volume in the ACS that is not in the ACSLS database. The audit added the volume to the database.
Variable: vol_id is the volume added to the database.
Audit: Volume vol_id not found.
Explanation: A volume listed in the ACSLS database is not in the ACS. The volume is deleted from the database.
Variable: vol_id is the volume deleted from the database.
Audit: Volume will be ejected, invalid media type
Explanation: ACSLS ejected a volume with an invalid media type.
Audit in progress.
Explanation: ACSLS did not start the audit because another audit for the same LSM is in progress.
CAP cap_id in use.
Explanation: The CAP specified for the audit is in use.
Variable: cap_id is the CAP in use.
Multiple ACS audit.
Explanation: The audit failed because the audit command specified multiple ACSs without specifying an * for the cap_id.
Not in same ACS.
Explanation: The audit failed because the cap_id and the identifier specified are not in the same ACS.
Variable:
cap_id is the CAP specified for the audit.
identifier is the library component specified for the audit.
cap_id Remove cartridges from CAP.
Explanation: The audit filled the CAP with ejected cartridges. Empty the CAP, then close it to continue the audit.
Variable: cap_id is the CAP that contains the ejected cartridges.
CAP cap_id: Place magazines in CAP.
Explanation: The CAP requires magazines for the audit. Open the CAP, place magazines inside, then close the CAP.
Variable: cap_id is the CAP that requires magazines.
CAP cap_id: No CAP available, waiting...
Explanation: No CAP is available to eject cartridges.
Variable: The cap_id appears as it was specified in the audit command:
acs, lsm, cap if the audit command explicitly specified the CAP.
acs, lsm, * if the audit command specified the CAP as acs, lsm, *.
acs, *, * if the audit command specified the CAP as acs, * or *.
The cancel command cancels a current or pending request.
request_id
specifies the identifier of the request to cancel.
Use the cancel command to cancel current or pending request issued by an audit, define pool, delete pool, eject, enter, lock, query, set, or venter command or client application. Use the query request command to display the ID of the request you want to cancel.
You can cancel an audit of a server, ACS, or LSM. Because ACSLS internally translates server, ACS, or LSM audits into a series of panel audits, ACSLS completes the audit of the current panel before cancelling the remainder of the audit. You cannot cancel an audit of a panel or subpanel. When you cancel an audit, cartridges already ejected are not re-entered.
Caution:
If you cancel an audit or if there is a library or ACSLS hardware or software failure during the audit, you must rerun the same audit. Cartridges marked for ejection but not actually ejected during the first audit are no longer in the database and are not under ACSLS control.HINT: Enter a cancel command from a different cmd_proc than the cmd_proc that issued the request you want to cancel.
The cancel command immediately cancels any pending requests and handles current requests as follows:
audit
Because ACSLS internally translates server, ACS, or LSM audits into a series of panel audits, ACSLS completes the audit of the current panel before cancelling the remainder of the audit.
Note:
If youcancel an audit or if there is a library or ACSLS hardware or software failure during the audit, you must re-run the same audit. Cartridges marked for ejection but not actually ejected during the first audit are no longer in the database and are not under ACSLS control.define pool
ACSLS stops defining scratch pools but does not delete any scratch pools already defined.
delete pool
ACSLS stops deleting scratch pools but does not redefine any scratch pools already deleted.
eject
ACSLS stops the ejection and the cmd_proc displays a message to remove any cartridges already ejected, which are not re-entered.
The eject does not terminate until the cartridges are removed, the CAP is closed, and ACSLS verifies that the CAP is empty.
enter
ACSLS stops the enter and, if any cartridges remain in the CAP, cmd_proc displays a message to remove these cartridges. Any cartridges already entered into the LSM are not ejected.
The enter does not terminate until the cartridges are removed, the CAP is closed, and ACSLS verifies that the CAP is empty.
Note:
Automatic enter. You cannot cancel an automatic enter operation that is in progress using the cancel command. To terminate an automatic enter in progress:If the CAP door is open, remove all of the cartridges and close the door.
If the CAP door is closed and the cartridges are being moved into the library, allow the remaining cartridges to be entered into the library. The enter then terminates.
lock
Resource locking by the specified request is stopped. If the request has not yet acquired all specified resources, none of the resources are locked.
query
ACSLS cancels the query.
set
For set cap, ACSLS stops setting CAP attributes, but does not change any attributes already set.
For set scratch or set clean requests, ACSLS stops setting scratch cartridge or cleaning cartridge attributes, but does not change any attributes already set.
venter
ACSLS stops the enter, and, if any cartridges remain in the CAP, cmd_proc displays a message to remove these cartridges. Any cartridges already entered into the LSM are not ejected.
To display request IDs for all current and pending requests:
query request all
Example output of query request all:
Identifier Command Status
13 enter Current
15 query Pending
To cancel request 13 (current enter request) in the example above:
cancel 13
See also:
| For information about... | See... |
|---|---|
| Updating the ACSLS database to match the actual inventory of library cartridges | "audit" |
| Creating or modifying scratch pools | "define pool" |
| Deleting empty scratch pools | "delete pool" |
| Ejecting cartridges from the library | "eject" |
| Making a CAP (manual mode) ready to enter labelled cartridges into the library | "enter" |
| Locking (dedicating) drives and cartridges to your current lock ID | "lock" |
| Displaying the status of a library component | "query commands" |
| Setting various attributes of different library components | "set commands" |
This section discusses the command area messages.
Request request_id canceled.
Explanation: ACSLS canceled the requested command.
Variable: request_id is the request identifier of the canceled command.
None.
Request request_id can not be canceled: status.
Explanation: ACSLS cannot cancel the specified command.
Variable:
request_id is the request identifier of the command that ACSLS cannot cancel.
status is one of the following:
Request identifier request_id invalid.
The cancel command specified an invalid request identifier.
Request identifier request_id not found.
The cancel command specified an request identifier for a request that is not current or pending.
The clear lock command removes all active and pending locks on a specified drive or cartridge.
type identifier
specifies a library component. The following table lists the components whose resource locks you can clear.
Use the clear lock command to remove all active and pending locks on a specified drive or cartridge. Your current lock ID must either be 0 or it must match the lock ID of the driver or cartridge.
The unlock command removes only active locks on drives or cartridges. You can, however, use the unlock command to remove active locks on all drives or all cartridges.
Note:
Theclear lock command always resets your lock ID to 0.To clear all locks for drive 1,1,5,2:
clear lock drive 1,1,5,2
To clear all locks for volume NN0108:
clear lock volume NN0108
Note:
You cannotcancel a clear lock command.See also:
| For information about... | See... |
|---|---|
| Locking drives and cartridges | "lock" |
| Displaying the lock status of a drive or cartridge | "query lock" |
| Setting your lock ID | "set lock" |
| Displaying your lock or user ID | "show" |
| Removing active locks for drives or cartridges | "unlock" |
This section discusses the command area messages.
The following message appears when a clear request succeeds:
Clear: Completed, Success.
In addition, for each identifier in the request, one of the following messages appears depending on the library component (type):
Clear: Drive drive_id all locks cleared.
Clear: Volume vol_id all locks cleared.
None.
Clear: Clear lock of drive drive_id failed,
Drive identifier drive_id available.
Explanation: ACSLS cannot clear locks because the specified drive is not locked.
Variable: drive_id is the identifier of the specified drive.
Clear: Clear lock of volume vol_id failed,
Volume identifier vol_id available.
Explanation: ACSLS cannot clear locks because the specified volume is not locked.
Variable: vol_id is the identifier of the specified volume.
The define pool command creates or modifies scratch pools.
low_water_mark
is the low volume warning threshold. If the scratch cartridge count falls below this threshold, ACSLS logs a warning message in the Event Log. Valid values are 0 to 231-1. The default is 0.
high_water_mark
is the high volume warning threshold. If the scratch cartridge count reaches or exceeds this threshold, ACSLS logs a warning message in the Event Log. This value must be greater than the value for low_water_mark.
pool_id
specifies the pool identifier. Pool 0 is the common scratch pool, which always exists. You can modify the common scratch pool attributes.
overflow
specifies that if this pool cannot satisfy mount scratch requests, ACSLS will select cartridges from the common pool (Pool 0).
To define a low threshold of 0, a high threshold of 600, and overflow for new pool 1:
define pool 0 600 1 overflow
To define a low threshold of 0, a high threshold of 600, and no overflow for existing pool 5:
define pool 0 600 5
Note:
Scratch pools are not owned by one client application or user ID. You can, however, use volume access control to restrict access for specific scratch cartridges.See also:
| For information about... | See... |
|---|---|
| Cancelling a command | "cancel" |
| Deleting empty scratch pools | "delete pool" |
| Guidelines and procedures for managing scratch cartridges | "Populating the LSM" |
| Mounting a scratch cartridge on a drive | "mount *" |
| Displaying scratch pool attributes | "query pool" |
| Setting or clearing cartridge scratch attributes | "set scratch" |
This section discusses the command area messages.
The following message appears when a define pool command succeeds:
Define: Define completed, Success.
The following message appears for each created or modified pool:
Define: Pool pool_id created.
None.
None.
Pool pool_id: low water mark warning.
Explanation: The number of volumes in the specified scratch pool is less than or equal to the low volume threshold.
Variable: low_water_mark is the low volume threshold of the specified scratch pool.
Pool pool_id: high water mark warning.
Explanation: The number of cartridges in the specified scratch pool is greater than or equal to the high volume threshold.
Variable: high_water_mark is the high volume threshold of the specified scratch pool.
The delete pool command deletes empty scratch pools.
pool_id
specifies the pool ID.
Pool 0 is the common pool, which you cannot delete.
all
specifies all empty scratch pools.
Use the delete pool command to delete empty scratch pools. If a pool contains scratch cartridges, you must reassign these cartridges to another pool before deleting the first pool. If a scratch cartridge is mounted, it becomes a data cartridge but remains in its scratch pool. Use the set scratch off command to reassign the data cartridge to the common pool.
To delete all empty scratch pools:
delete pool all
Only the empty pools will be deleted; pools with cartridges assigned are not affected.
To delete scratch pool 1, follow the procedure below:
Query scratch pool 1:
query scratch 1
1998-0630>09:35:30>Scratch Status Scratch Pool> Identifier> Homer location> Status> Type 1) 34813> 0,0,1,8,8> home> 3480 3480 1) 34815> 0,0,1,8,1> home> 3480 3480
Pool 1 has two cartridges, 34813 and 34815.
Empty pool 1 by reassigning its cartridges to pool 5:
set scratch 5 348013 348015
Delete pool 1:
delete pool 1
See also:
| For information about... | See... |
|---|---|
| Cancelling a command | "cancel" |
| Creating or modifying scratch pools | "define pool" |
| Guidelines and procedures for managing scratch cartridges | "Populating the LSM" |
| Displaying scratch pool attributes | "query pool" |
| Displaying the location and media type of a cartridge | "query volume" |
| Setting or clearing cartridge scratch attributes | "set scratch" |
This section discusses the command area messages.
The following message appears when a delete pool command completes successfully:
Delete: Delete completed, Success.
The following message appears for each deleted pool:
Delete: Pool pool_id deleted.
None.
Delete: Pool pool_id failed, Pool not empty.
Explanation: ACSLS cannot delete the scratch pool because it is not empty.
Variable: pool_id is the identifier of the requested pool.
The dismount command dismounts a cartridge from a drive.
vol_id
specifies the cartridge.
drive_id
specifies the drive.
force
forces a dismount of the actual volume in the specified drive, even if the vol_id of the cartridge in the drive does not match the specified vol_id (provided that drive is not in STATUS_DRIVE_RESERVED state, in which case, the vol_ids must match; this prevents client conflicts while a mount or dismount operation is in progress).
This option also forces a dismount, even if the drive is not unloaded.
Use the dismount command to dismount a volume from a drive, and place the cartridge in an available storage cell.
Use the dismount command without the force option to dismount a specified cartridge from a specified drive. A successful unforced dismount requires the following:
The drive must be online
The vol_id of the cartridge in the drive must match the vol_id you specify on the dismount command
The drive must be unloaded
Caution:
On a normal dismount, SL500 and SL150 libraries automatically rewind and unload a cartridge that is found loaded in a drive. They do not require a dismount force to rewind and unload a cartridge. Make sure that an ACSLS client application is not reading from, or writing to a tape drive before issuing a dismount on these libraries.Use the dismount command with the force option to force a dismount of the actual cartridge mounted in a specified drive. The vol_id of the cartridge in the drive does not have to match the vol_id you specify on the dismount command (unless the drive is in STATUS_DRIVE_RESERVED state; this prevents client conflicts while a mount or dismount operation is in progress). In addition, if the cartridge is not ready for dismounting, ACSLS forces the drive to automatically rewind, unload, and dismount the cartridge. The drive must be online.
A dismount force must include the correct vol_id if a drive was left marked as reserved by a mount or dismount operation that never received a response. If the drive has no vol_id (as seen in the results of a query drive command), then any vol_id may be used. Match is not required, since there is nothing to match. A reserved drive is reported as in use to the cmd_proc or an ACSAPI client.
You can use the force option to dismount a cartridge with an unreadable or unknown label or a cartridge that a client application did not dismount. Notice that ACSLS returns the cartridge to an available storage cell, even if the label is unreadable or missing.
Note:
Any read/write activity between the drive and any application that is currently using the drive must stop or pause before the library rewinds and uploads the cartridge. If the read/write activity continue uninterruptedly, the dismount force fails after the library wait timeout is exceeded.This consideration also applies to media validation that was requested from the host to the drive, by way of the data path. Until the media validation completes or the host stops it through the data path, a dismount force from ACSLS fails.
To dismount cartridge EDU200 from drive 0,1,10,2:
dismount EDU200 0,1,10,2
See also:
For information about... |
See... |
|---|---|
| Cancelling a command | "cancel" |
| Ejecting cartridges from the library | "eject" |
| Making a CAP (manual mode) ready to enter labelled cartridges into the library | "enter" |
| Mounting a scratch cartridge on a drive | "mount *" |
| Mounting a data cartridge on a drive | "mount" |
| Displaying CAP status | "query cap" |
| Displaying drive status | "query drive" |
| Setting CAP mode (manual or automatic) | "set cap mode" |
| Setting CAP selection priority | "set cap priority" |
This section discusses the command area messages.
Dismount: vol_id dismounted from drive_id.
Explanation: A forced dismount succeeded.
Variable:
vol_id is the identifier of the dismounted cartridge.
The vol_id displayed is the volume that was actually dismounted, not necessarily the volume that was specified in the dismount force command.
drive_id is the identifier of the specified drive.
Dismount: Forced dismount of vol_id from drive_id.
Explanation: A forced dismount succeeded.
Variable:
vol_id is the identifier of the dismounted cartridge.
The vol_id displayed is the volume that was actually dismounted, not necessarily the volume that was specified in the dismount force command.
drive_id is the identifier of the specified drive.
None.
Dismount: Dismount failed, ACS acs_id full.
Explanation: ACSLS cannot dismount the cartridge because the ACS has no free storage cells. Eject at least one other cartridge from the ACS so that ACSLS can dismount the cartridge from the drive.
Variable: acs_id is the identifier of the ACS that contains the cartridge.
Note:
Only online LSMs are used in locating free cells; therefore, this message can occur even when there is an LSM with free storage cells if that LSM is offline. Additionally, if an LSM or ACS has not been audited, the recorded number of free cells may not be accurate, resulting in this error. Audit the library to remedy this condition.Dismount: Dismount failed, Audit in progress.
Explanation: ACSLS cannot dismount the cartridge because an audit in progress has locked out access to the last unoccupied cell location in the ACS.
Dismount: Dismount failed, Cartridge in drive drive_id, unreadable label
Explanation: ACSLS cannot dismount the cartridge because the cartridge either has no external label, an unreadable external label, or no virtual label. Use a forced dismount to dismount the cartridge.
Variable: drive_id is the identifier of the specified drive.
Dismount: Dismount failed, Drive identifier drive_id available.
Explanation: No cartridge is mounted in the specified drive.
Variable: drive_id is the identifier of the specified drive.
Dismount: Dismount failed, Drive identifier drive_id in use.
Explanation: ACSLS cannot dismount the cartridge because the cartridge is not rewound and unloaded. Either wait for the client application to either rewind and unload the cartridge, then enter a dismount command, or use a forced dismount to dismount the cartridge.
Variable: drive_id is the identifier of the specified drive.
Dismount: Dismount failed, Misplaced tape.
Explanation: ACSLS cannot dismount the cartridge because the external label of the cartridge does not match the cartridge identifier in the ACSLS database. The cartridge identifier in the ACSLS database is updated to match the external label of the cartridge. Retry the dismount.
Dismount: Dismount failed, Cartridge not in drive.
Explanation: ACSLS cannot dismount the cartridge because the external label of the cartridge does not match the cartridge identifier specified in the dismount. Re-enter the dismount command with the correct cartridge identifier.
The eject command directs the robot to take cartridges from the inside of an LSM, and place them into a CAP where they can be removed by the operator.
If you select the lsm_id option, you can use multiple CAPs in a single LSM to eject cartridges.
cap_id
specifies the CAP used to eject the cartridges.
lsm_id
If you select the lsm_id option, you can use multiple CAPs that are available in a single LSM to eject cartridges. All CAPs that satisfy the requirements (such as manual, nonzero priority available) are unlocked for ejecting cartridges. You can eject cartridges through any or all of the CAPs selected, and in any order. The eject initially fills the CAPs with cartridges in order of highest priority.
Example: You have two CAPs - one with priority 2 and one with priority 5; eject fills the CAP with priority 5 status first, then the CAP with priority 2 status. If there are only enough cartridges to be ejected for one CAP, then the CAP with priority 5 is filled.
opmsg opmsg_nbr
Custom operator panel message numbers can be specified for the SL8500 Bulk CAP eject commands that are entered using cmd_proc. The message is displayed when a Bulk CAP is unlocked so cartridges being ejected can be removed.
Valid message numbers are from 4 and 99.
Currently a custom opmsg is only displayed for the Bulk CAP on SL8500 libraries.
The opmsg parameter is optional. If it is not specified, a default message to remove cartridges is sent.
Custom opmsg numbers cannot be specified for ejects from ACSAPI clients, the ACSLS GUI, or lib_cmd eject. In these cases the default messages are displayed.
To create the message to be displayed for an opmsg number use the SL Console and select the following:
Tools
Configuration
CAP Usage Message
To view the SL Console CAP Status display showing the opmsg, select:
Tools
System Detail
CAP Folder
Status
The SL Console displays a Bulk CAP message based on the message number sent from ACSLS during an eject. The message displays on the System Details CAP Status page after a CAP is unlocked for cartridges being ejected to be removed.
Example: To specify custom operator panel message number 55 for ejecting cartridges through Bulk CAP 1,2,1:
eject 1,2,1 opmsg 55 T10001 T10033-T10067
vol_id | volrange
specifies the external or virtual label types of the cartridge or range of cartridges to eject.
Use the eject command to eject cartridges from the library, which removes them from ACSLS control. The robot places the specified cartridge in the designated CAP, then ACSLS frees the cell locations where the cartridges were stored. Cartridge information is either retained if the ABSENT_VOLUME_RETENTION_PERIOD variable has a nonzero value, or deleted if the ABSENT_VOLUME_RETENTION_PERIOD is set to zero. If you specify more than a CAP full of cartridges on the eject command, empty the CAP when it fills, close the CAP, and continue the ejection until all cartridges are ejected.
You can use a single eject command to eject multiple cartridges not in a range by specifying multiple cartridge IDs separated by a space.
If your library has two connected LSMs and the PTP is down, to successfully eject cartridges, either:
Specify a CAP in the LSM where the cartridge is stored. For example, if cartridge NN0100 is stored in LSM 0,0, to eject this cartridge through CAP 0,0,0:
eject 0,0,0 NN0101
For the cap_id, specify the LSM where the cartridge is stored but use a wildcard (*) for the CAP number; ACSLS will select the highest priority CAP in the LSM. For example, if cartridge NN0114 is stored in LSM 0,0, to eject this cartridge through LSM 0,0's highest priority CAP:
eject 0,0,* NN0114
To eject cartridge NN0101 through CAP 0,0,0:
eject 0,0,0 NN0101
To eject cartridge range NN0101-NN0109 through the highest priority CAP on ACS 0:
eject 0,* NN0101-NN0109
To eject cartridges NN0101, NN0103, NN0105, and NN0107 through the highest priority CAP on ACS 0:
eject 0,* NN0101 NN0103 NN0105 NN0107
To use multiple non-zero priority CAPs for ejecting cartridges in LSM 1,2:
eject 1,2 RB1000-RB2000
Note:
Make sure you remove all ejected cartridges from the CAP. You must complete the ejection by unloading all ejected cartridges and closing the CAP door before you can use the CAP for another operation (such as an enter or audit).See also:
| For information about... | See... |
|---|---|
| Cancelling a command | "cancel" |
| Dismounting a cartridge from a drive | "dismount" |
| Guidelines and procedures for ejecting cartridges | "Populating the LSM" |
| Making a CAP (manual mode) ready to enter labelled cartridges into the library | "enter" |
| Displaying CAP status | "query cap" |
| Displaying drive status | "query drive" |
| Displaying the location and media type of a cartridge | "query volume" |
| Setting CAP mode (manual or automatic) | "set cap mode" |
| Setting CAP selection priority | "set cap priority" |
This section discusses command area messages.
Eject: Eject complete, a cartridges ejected
Eject: vol_id ejected from cap_id
Explanation: ACSLS ejected the specified cartridges.
Variable:
nn is the number of cartridges ejected.
vol_id is the cartridge identifier of the ejected cartridge.
cap_id is the CAP that contains the ejected cartridge.
None
Eject: vol_id Eject failed, CAP cap_id full.
Explanation: A cartridge was not ejected because the CAP is full.
Variable:
vol_id is the cartridge identifier of the cartridge that was not ejected.
cap_id is the CAP specified for the ejection.
Eject: vol_id Eject failed, CAP cap_id in use.
Explanation: A cartridge was not ejected because the CAP is in use.
Variable:
vol_id is the cartridge identifier of the cartridge that was not ejected.
cap_id is the CAP specified for the ejection.
Eject: vol_id Eject failed, Misplaced tape.
Explanation: ACSLS cannot eject the cartridge because the external label of the cartridge does not match the database's cartridge identifier for the storage cell. The database updates the cartridge identifier, media type, and cleaning cartridge attribute for the cartridge in the storage cell.
Variable: vol_id is the cartridge identifier of the cartridge that was not ejected.
Eject: vol_id Eject failed, Not in same ACS.
Explanation: A cartridge was not ejected because it is not in the ACS specified in the cap_id.
Variable: vol_id is the cartridge identifier of the cartridge that was not ejected.
Eject: vol_id Eject failed, Volume identifier vol_id not found.
Explanation: A cartridge was not ejected because it is not:
In the storage cell specified in the database,
In-transit, or
In a drive.
ACSLS deletes the volume entry from the database.
Variable: vol_id is the cartridge identifier that was deleted from the database.
Eject: vol_id Eject failed, Cartridge in drive.
Explanation: A cartridge was not ejected because it is mounted in a drive.
Variable: vol_id is the cartridge identifier of the cartridge that was not ejected.
Eject: vol_id Eject failed, Volume vol_id in use.
Explanation: A cartridge was not ejected because it is reserved for use by another request.
Variable: vol_id is the cartridge identifier of the cartridge that was not ejected.
CAP cap_id Remove cartridges from CAP.
Explanation: Either the CAP is full, or all requested cartridges are in the CAP. Empty the CAP.
Variable: cap_id is the CAP that contains the ejected cartridges.
CAP cap_id Place magazines in CAP.
Explanation: The CAP requires magazines for the ejection. Open the CAP, place magazines inside, then close the CAP.
Variable: cap_id is the CAP that requires magazines.
This command allows you to set the CAP to operate in either manual or automatic mode. For procedures for setting the CAP to automatic mode or manual mode, refer to the section "Entering Cartridges".
Automatic mode
When a CAP is in automatic mode, you can initiate an enter operation without issuing an enter command. You do this by opening the CAP door, placing one or more cartridges inside, and closing the CAP. The CAP is locked while the enter is being processed; when the enter operation is compete, the CAP is unlocked.
Manual mode
When in manual mode, the CAP is locked and can only be used by issuing the following command before opening the CAP and entering the cartridges.
enter cap_id [opmsg opmsg_nbr]
cap_id
specifies the CAP. This can be wild-carded with an asterisk (*) to select the CAP with the highest non-zero priority in an LSM, such as 1,1,* or an ACS, such as 0,*,*.
opmsg opmsg_nbr
Custom operator panel message numbers can be specified for the SL8500 Bulk CAP enter commands that are entered using cmd_proc. The message is displayed when a Bulk CAP is unlocked for cartridges being entered.
Valid message numbers are from 4 and 99.
Currently a custom opmsg is only displayed for the Bulk CAP on SL8500 libraries.
The opmsg parameter is optional. If it is not specified, a default message to enter cartridges is sent.
When cartridges were left in the CAP before the enter started or unreadable or duplicate cartridges cannot be entered, a message to remove these cartridges is displayed. This can also happen when an opmsg parameter was specified for the enter.
Custom opmsg numbers cannot be specified for enters from ACSAPI clients or the ACSLS GUI. In these cases the default messages are displayed.
To create the message to be displayed for an opmsg number use the SL Console and select the following:
Tools
Configuration
CAP Usage Message
To view the SL Console CAP Status display showing the opmsg, select:
Tools
System Detail
CAP Folder
Status
The SL Console displays a Bulk CAP message based on the message number sent from ACSLS during an enter. The message displays on the System Details CAP Status page after a CAP is unlocked for cartridges being entered.
Example: To specify custom operator panel message number 66 for entering cartridges through Bulk CAP 1,3.0:
enter 1,3,0 opmsg 66
lsm_id
If you select the lsm_id option, you can use multiple CAPs that are available in a single LSM to enter cartridges. All CAPs that satisfy the requirements (such as manual, non zero priority, available) are unlocked for entering cartridges. You can enter cartridges through any or all the CAPs selected, and in any order. venter is not valid and returns a CAP invalid error.
To make CAP 0,0,2 ready to enter cartridges:
enter 0,0,2
To make the highest non-zero priority CAP in LSM 0,0 ready to enter cartridges:
enter 0,0,*
To use multiple CAPs for entering cartridges in an LSM 1,2:
enter 1,2
Note:
Cartridges being entered into an LSM must be compatible with that LSM. For example, only T9840, T9940, and LTO cartridges can be entered into an L5500 LSM.See also:
| For information about... | See... |
|---|---|
| Cancelling a command | "cancel" |
| Creating or modifying scratch pools | "define pool" |
| Ejecting cartridges from the library | "eject" |
| Guidelines and procedures for entering cartridges | "Entering Cartridges" |
| Mounting a scratch cartridge on a drive | "mount *" |
| Mounting a data cartridge on a drive | "mount" |
| Displaying CAP status | "query cap" |
| Setting CAP mode (manual or automatic) | "set cap mode" |
| Setting CAP selection priority | "set cap priority" |
This section discusses the command are messages.
After all labelled cartridges have been entered, the following message appears, with the second line of the message repeated for each cartridge successfully entered:
Enter: Enter complete, nn volumes entered
Enter: vol_id Entered through cap_id
nn is the total number of cartridges entered
vol_id is the cartridge identifier of the entered cartridge
cap_id is the CAP used to enter the cartridges
None.
Enter: vol_id Enter failed, ACS acs_id full.
Explanation: A cartridge was not entered because the ACS has no free storage cells. You must eject at least one cartridge from the ACS so that ACSLS can enter the cartridge.
Variable:
vol_id is the external label of the cartridge that was not entered.
acs_id is the identifier of the ACS that has no free storage cells.
Note:
ACSLS only searches online LSMs for free cells; this message can occur even if offline LSMS have free cells.Enter: vol_id Enter failed, Audit in progress.
Explanation: A cartridge was not entered because an audit has locked out access to a cell location required for the enter.
Variable: vol_id is the external label of the cartridge that was not entered.
Enter: vol_id Enter failed, CAP cap_id in use.
Explanation: A cartridge was not entered because the specified CAP is in use for auditing, ejecting cartridges, or another enter process.
Variable:
vol_id is the external label of the cartridge that was not entered.
cap_id is the in-use CAP.
Enter: vol_id Enter failed, Duplicate label.
Explanation: A cartridge was not entered because the cartridge identifier of a cartridge in the CAP already exists in the ACSLS database.
Variable: vol_id is the external label of the cartridge that was not entered.
Enter: Enter failed, Unreadable label.
Explanation: A cartridge was not entered because the cartridge either has no external label or an unreadable external label.
Enter: vol_id Enter failed, Unknown media type label.
Explanation: A cartridge was not entered because the cartridge does not have a media identifier on its externals label.
Variable: vol_id is the external label of the cartridge that was not entered.
CAP cap_id: Place cartridges in CAP.
Explanation: The CAP is ready for cartridge entry. Open the CAP and enter cartridges.
Variable: cap_id is the CAP used to enter cartridges.
CAP cap_id: Remove cartridges from CAP.
Explanation: One or more cartridges cannot be entered.
Variable: cap_id s the CAP used to enter cartridges. Open the CAP and remove the cartridges.
CAP cap_id: CAP cap_id Place magazines in CAP.
Explanation: The CAP uses magazines for cartridge entry. Load cartridges in the correct magazine, open the CAP, and insert the magazines.
Variable: cap_id s the CAP used to enter cartridges.
The idle command stops ACSLS from processing new requests.
idle [force]
Enter the full command name for the idle command. ACSLS will reject all other forms of the command, such as i, id, or idl.
Use the idle command to stop ACSLS from processing new requests. For example, you idle ACSLS before doing maintenance or before terminating ACSLS.
Note:
Use thestart command to restart the request processing.idle
Entering an idle command without the force option puts ACSLS in the idle-pending state. ACSLS completes current and pending requests (except pending lock requests, which are canceled) and rejects new requests except those listed in ”Notes.” ACSLS then goes to idle state and does not process subsequent requests until request processing is restarted.
Idle force
Entering an idle command with the force option puts ACSLS in the idle state. ACSLS cancels all current and pending requests and rejects new requests except those listed in the Note under ”Examples”. ACSLS does not process subsequent requests until restarted. Because ACSLS does not complete current requests, forcing ACSLS to idle state may leave the database in an inconsistent state with the hardware, which requires an audit to correct.
HINT: Depending on the current requests processing when you enter an idle force, the Event Log may report process failures. If so, vary the affected LSMs offline and back online. See "vary" for information about the vary command.
To put ACSLS in idle-pending state:
idle
To force ACSLS to idle state:
idle force
Note:
In eitheridle or idle-pending state, ACSLS accepts new requests for the cancel, idle, query, start, and vary requests.See also:
| For information about... | See... |
|---|---|
| Displaying the status of a library component | "query commands" |
| Starting ACSLS request processing | "start" |
| Changing the state of a library component | "vary" |
This section discusses the area command messages.
The following message appears when ACSLS request processing stops:
ACSLM Request Processing Stopped: Success.
None.
ACSLM Request Processing Stopped: status
Explanation: ACSLS did not stop processing requests.
Variable: status is the reason for the failure. For more information on common status messages, see ACSLS Messages.
The lock command locks a cartridge or drive to a lock ID that ACSLS assigns.
type identifier
specifies a library component. The following table lists the components that you can lock. You can specify either a drive or a volume but not both in a single lock command. You can, however, use the same lock ID for both drives and volumes..
Table 12-4 Valid Components for Lock
| Library Component | type | identifier |
|---|---|---|
|
drive |
|
drive_id |
|
volume |
|
vol_id |
wait
specifies that the lock is pending if the component is unavailable (locked or in use). ACSLS then locks the component when it is available. You can clear or cancel a pending lock request. Idling ACSLS also cancels a pending lock request.
Use the lock command to lock a volume or drive to a lock ID that ACSLS assigns. You can only lock available (not locked or in use) volumes or drives.
Note:
When you enter alock command to lock a cartridge or drive, ACSLS assigns a lock ID to the volume or drive and then changes your lock ID to the lock ID of the volume or drive. You cannot use the set lock command to set your lock ID and then use the lock command to lock a volume or drive with the lock ID that you set with set lock.To lock drive 0,1,10,2:
lock drive 0,1,10,2
To lock volume EDU445:
lock volume EDU445
See also:
| For information about... | See... |
|---|---|
| Removing all active or pending locks on a specified drive or cartridge | "clear lock" |
| Displaying the lock status of a drive or cartridge | "query lock" |
| Setting your lock ID | "set lock" |
| Displaying your lock or user ID | "show" |
| Removing active locks on drives or cartridges | "unlock" |
This section discusses the command area messages.
The following message appears when a lock request succeeds:
Lock: Lock completed, Success.
For each identifier in the request, one of the following messages appears:
Lock: Drive drive_id locked under lock_id lock_id.
Lock: Volume vol_id locked under lock_id lock_id.
Where:
drive_id is the locked drive.
The vol_id is the cartridge identifier of the locked cartridge.
lock_id is the lock ID.
None.
One of the following messages appears if the lock request fails:
Lock: Lock of drive drive_id failed, Drive in use.
Explanation: ACSLS cannot lock the specified drive because the drive is already locked or in use.
Variable: drive_id is the drive that ACSLS cannot lock.
Lock: Lock of drive drive_id failed, Lock failed.
Explanation: ACSLS cannot lock the specified drive. Re-enter the lock command with the correct syntax and drive identifier.
Variable: drive_id is the drive that ACSLS cannot lock.
Lock: Lock of volume vol_id failed, Volume in use.
Explanation: ACSLS cannot lock the specified cartridge because the cartridge is already locked or in use.
Variable: vol_id is the cartridge that ACSLS cannot lock.
Lock: Lock of volume vol_id failed, Lock failed.
Explanation: ACSLS cannot lock the specified cartridge. Re-enter the lock command with the correct syntax and cartridge identifier.
Variable: vol_id is the cartridge that ACSLS cannot lock.
The logoff command exits from a cmd_proc.
Use the logoff command to exit from cmd_proc. If you run an interactive (window), cmd_proc, logoff also quits the cmd_proc window.
To exit a cmd_proc:
logoff
Note:
logoff exits from cmd_proc only, is valid in any ACSLS state, and does not affect ACSLS operations.See also:
| For information about... | See... |
|---|---|
| Starting a cmd_proc | "Starting cmd_proc" |
| Using a cmd_proc | "Starting cmd_proc" |
The mount command mounts a data cartridge.
vol_id
specifies the cartridge.
drive_id
specifies the drive.
bypass
The bypass option overrides the checks that ACSLS does before trying to mount a cartridge as follows:
The bypass option always overrides the ACSLS verification of the cartridge ID on the external label.
It may override ACSLS verification of the compatibility between the tape drive and the cartridge's media type.
When the library receives the mount request, it verifies that the cartridges' media is compatible with the tape drive; the library fails the mount if the media type is incompatible or is an unknown type.
readonly
specifies that the cartridge is mounted write-protected.
Caution:
LTO drives do not support mounts with write protect. If a "mount read-only" is attempted to an LTO drive, it will fail with a "Drive cannot honor write protect" message in the Event Log.Use the mount command to mount a data cartridge. You can only mount one cartridge on one drive each time you enter a mount command.
A successful mount requires the following:
The cartridge and drive must be in the same ACS.
The cartridge must be available, and the drive must be online and available.
To mount volume EDU010 on drive 0,0,10,2:
mount EDU010 0,0,10,2
In the following example, YUMA15 is a DD3C volume whose cartridge label is missing the seventh character. The bypass option bypasses the media compatibility checks and forces a mount of the cartridge on drive 0,0,4,0, an SD3 drive.
To mount YUMA15 on drive 0,0,4,0 using the bypass option:
See also:
| For information about... | See... |
|---|---|
| Dismounting a cartridge from a drive | "dismount" |
| Making a CAP (manual mode) ready to enter labelled cartridges into the library | "enter" |
| Displaying CAP status | "query cap" |
| Displaying drive status | "query drive" |
| Displaying the lock status of a drive or cartridge | "query lock" |
| Displaying the status of media-compatible drives for a specified data cartridge | "query mount" |
| Displaying the location and media type of a cartridge | "query volume" |
| Setting CAP mode (manual or automatic) | "set cap mode" |
| Setting CAP selection priority | "set cap priority" |
This section discusses the command area messages.
Mount: vol_id mounted on drive_id
Explanation: ACSLS mounted the specified cartridge.
Variable:
vol_id is the cartridge identifier of the cartridge that ACSLS mounted.
drive_id is the drive that mounted the cartridge.
None.
Mount: Mount failed, Audit in progress.
Explanation: ACSLS cannot mount the cartridge because an audit has locked out access to the cell location of the specified cartridge.
Mount: Mount failed, In use.
Explanation: ACSLS cannot mount the cartridge because either the drive is in use or the requested cartridge is reserved for another command.
Mount: Mount failed, Misplaced tape.
Explanation: ACSLS cannot mount the cartridge because the external label of the cartridge does not match the databases' cartridge identifier for the storage cell. The database updates the cartridge identifier, media type, and cleaning cartridge attribute for the cartridge in the storage cell.
Mount: Mount failed, Not in same ACS.
Explanation: ACSLS cannot mount the cartridge because the specified cartridge and drive are not in the same ACS.
Mount: Mount failed, Cartridge in drive.
Explanation: ACSLS cannot mount the cartridge because the specified cartridge is already mounted in a drive.
Mount: Mount failed, Unreadable label.
Explanation: ACSLS cannot mount the cartridge because the cartridge has no label, an unreadable label, or no virtual label.
Mount: Mount failed, Invalid media type.
Explanation: ACSLS cannot mount the cartridge because the specified cartridges' media type is invalid.
Mount: Mount failed, Invalid drive type.
Explanation: ACSLS cannot mount the cartridge because the specified drive type is invalid.
Mount: Mount failed, Incompatible media type.
Explanation: ACSLS cannot mount the cartridge because the cartridges' media type is incompatible with the specified drive.
The mount * command selects a scratch cartridge and mounts it.
drive_id
specifies the drive.
pool_id
specifies the pool from which ACSLS selects the scratch cartridge. pool_id is optional; if you do not specify a pool_id, ACSLS tries to find a scratch cartridge in the common pool (pool 0).
If you specify a pool_id and the pool does not contain a scratch cartridge (or one of the correct media for mixed-media libraries), or if the pool is set for overflow; ACSLS tries to find a scratch cartridge in the common pool (pool 0).
media media_type | media *
specifies the cartridge media type. Specifying the media type is optional.
Use the mount * command to select a scratch cartridge and mount it. The following sections describe how ACSLS selects the scratch cartridge to be mounted and how to specify the cartridge media type for a scratch cartridge.
How ACSLS Selects Scratch Cartridges
The mount * command selects a scratch cartridge by:
Creating a list of LSMs in the ACS, based on proximity to the LSM containing the specified drive.
Examining each LSM in the list, until it finds scratch cartridges that meet the pool and media type criteria.
Choosing the scratch cartridge with the least recent access date in that LSM.
The selected scratch cartridge is then mounted on the drive.
Specifying the Media Type
You can specify cartridge media type in any of the following ways:
Explicitly specify the media type in this form of the mount * command:
mount * drive_id [pool_id] media media_type
Example: To mount a T10000 scratch cartridge from the common pool (pool 0):
mount * 0,0,10,2 media T10000T1
Use a wildcard (*) for the media type so that ACSLS selects the media by scratch preferences; for more information see"Using the Extended Store Feature" . To use scratch preferences, enter this form of the mount * command:
mount * drive_id [pool_id] media *
Example: To use scratch preferences to mount a scratch cartridge from the common pool (pool 0):
mount * 0,0,10,2 media *
Omit the media option in this form of the mount * command. This instructs ACSLS to pick a media type compatible with the drive:
mount * drive_id [pool_id]
Example: To mount a scratch cartridge compatible with the drive from the common pool (pool 0):
mount * 0,0,10,2
The following sections show mount scratch examples for single-media and mixed-media libraries.
Single-Media Libraries
To mount a scratch cartridge from pool 5 on drive 0,0,10,2:
mount * 0,0,10,2 5
HINT: If no cartridge is available from pool 5 and it has been set for overflow, ACSLS will select a cartridge from the common pool (pool 0).
To mount a scratch cartridge from the common pool (pool 0) on drive 0,0,10,0:
mount * 0,0,10,0
To mount a scratch cartridge from pool 5 with a media type of T10000T2 on drive 0,0,10,2:
mount * 0,0,10,2 5 media T10000T2
If no cartridge is available from pool 5 and it has been set for overflow, ACSLS will select a cartridge with the specified media type from the common pool (pool 0).
To mount a scratch cartridge from pool 10 with media type determined by scratch preferences on drive 0,0,2,3:
mount * 0,0,2,3 10 media *
HINT: If no cartridge is available from pool 10 and it has been set for overflow, ACSLS will select a cartridge with the specified media type from the common pool (pool 0).
To mount a scratch cartridge from the common pool (pool 0) with media type of T10000T2 on drive 0,0,10,2:
mount * 0,0,10,2 media T10000T2
To mount a scratch cartridge from the common pool (pool 0) with media type determined by scratch preferences on drive 0,0,2,3:
mount * 0,0,2,3 media *
To mount a scratch cartridge from the common pool (pool 0) with media compatible with drive 0,0,2,3:
mount * 0,0,2,3
See also:
| For information about... | See... |
|---|---|
| Creating or modifying scratch pools | "define pool" |
| Deleting empty scratch pools | "delete pool" |
| Dismounting a cartridge from a drive | "dismount" |
| Managing scratch cartridges | "Populating the LSM" |
| Displaying drive status | "query drive" |
| Displaying the lock status of a drive or cartridge | "query lock" |
| Displaying the status of media-compatible drives for a specified scratch pool | "query mount *" |
| Displaying scratch pool attributes | "query pool" |
| Displaying scratch cartridge status | "query scratch" |
| Displaying the location and media type of a cartridge | "query volume" |
| Setting or clearing cartridge scratch attributes | "set scratch" |
| Setting scratch preferences | "Using the Extended Store Feature" |
This section discusses the command area messages.
Mount: vol_id mounted on drive_id
Explanation: ACSLS mounted the specified cartridge.
Variable:
vol_id is the cartridge identifier of the cartridge that ACSLS mounted.
drive_id is the drive that mounted the cartridge.
None.
Mount: Mount failed, Audit in progress.
Explanation: ACSLS cannot mount the cartridge because an audit has locked out access to the cell location of the specified cartridge.
Mount: Mount failed, In use.
Explanation: ACSLS cannot mount the cartridge because either the drive is in use or the requested cartridge is reserved for another command.
Mount: Mount failed, Misplaced tape.
Explanation: ACSLS cannot mount the cartridge because the external label of the cartridge does not match the database cartridge identifier for the storage cell. The database updates the cartridge identifier, media type, and cleaning cartridge attribute for the cartridge in the storage cell.
Mount: Mount failed, Not in same ACS.
Explanation: ACSLS cannot mount the cartridge because the specified cartridge and drive are not in the same ACS.
Mount: Mount failed, Cartridge in drive.
Explanation: ACSLS cannot mount the cartridge because the specified cartridge is already mounted in a drive.
Mount: Mount failed, Unreadable label.
Explanation: ACSLS cannot mount the cartridge because the cartridge has no label, an unreadable label, or no virtual label.
Mount: Mount failed, Invalid media type.
Explanation: ACSLS cannot mount the cartridge because the specified cartridges' media type is invalid.
Mount: Mount failed, Invalid drive type.
Explanation: ACSLS cannot mount the cartridge because the specified drive type is invalid.
Mount: Mount failed, Incompatible media type.
Explanation: ACSLS cannot mount the cartridge because the cartridges' media type is incompatible with the specified drive.
Mount: Mount failed, No compatible scratch cartridges in pool.
Explanation: ACSLS cannot mount the cartridge because there are no scratch cartridges in the ACS of the specified drive that match the scratch cartridges' media type. In addition, if the overflow attribute is set for the pool, there are no scratch cartridges with valid media types.
Pool pool_id: low water mark warning.
Explanation: The number of cartridges in the specified scratch pool is less than or equal to the low cartridge threshold.
Variable: low_water_mark is the low threshold of the specified scratch pool.
Pool pool_id: high water mark warning.
Explanation: The number of cartridges in the specified scratch pool is greater than or equal to the high cartridge threshold.
Variable: high_water_mark is the high water cartridge threshold of the specified scratch pool.
The move command moves a specified cartridge to an available storage cell in a specified LSM or to a specific storage cell.
Note:
SL3000 allows for cartridges to be moved to a specific cell. For more information, see "Partitioning a Library or Changing Partition IDs".vol_id
specifies the cartridge.
lsm_id
specifies the LSM that will contain the moved cartridge.
cell_id
specifies the cell to which the cartridge will be moved.
Use the move command to move a specified cartridge to an available storage cell in either:
A different panel in the same LSM. For example, if you want to empty an entire panel in an LSM, move all of the cartridges in that panel to a different location in the same LSM.
A different LSM.
You can move only one cartridge each time you enter the move command. If you specify the LSM where the cartridge currently resides, ACSLS will move the cartridge to another panel within that LSM. Otherwise, ACSLS will move it to the LSM you specify. You cannot cancel a move command.
A successful move requires the following:
The cartridge must be available and in the same ACS as the specified LSM.
The LSM where the cartridge currently resides, and the specified LSM, must both be online. The specified LSM must have at least one available storage cell. If the move is within the same LSM, there must be at least one available cell in a different panel in that LSM. If the move requires a pass-thru, any LSMs used must also be online.
To move cartridge EDU010 (which resides in LSM 0,1) to a different panel in this LSM:
move EDU010 0,1
To move cartridge EDU010 (which resides in LSM 0,1) to LSM 0,2:
move EDU010 0,2
See also:
| For information about... | See... |
|---|---|
| Displaying the lock status of a drive or cartridge | "query lock" |
| Displaying the status of an LSM | "query lsm" |
| Displaying the location and media type of a cartridge | "query volume" |
This section discusses the command area messages.
Move: vol_id moved to location cell_id
Explanation: ACSLS moved the specified cartridge to the specified cell location.
Variable:
vol_id is the cartridge identifier of the cartridge that ACSLS moved.
cell_id is the new cell location of the specified cartridge.
None.
Move: Move failed
The query commands display the status of a library component. See the following sections for more information about each query command, including format, options, and usage.
The following shows the general format of the query commands:
query type [subtype | *] identifier... | all
Note:
If acancel request is issued against a pending or current query request, the display of information is halted.See also:
| For information about... | See... |
|---|---|
| Cancelling a command | "cancel" |
| Display Command | "Using display Command Options" |
This section discusses the command area messages.
None.
Note:
If thequery succeeds, the requested status appears.None.
Library not available.
Explanation: The query failed because ACSLS is recovering (all queries except query server).
Cartridge identifier vol_id not found.
Explanation: The query mount * command cannot display status for the specified cartridge because it is not in the library.
Variable: vol_id is the specified cartridge.
Invalid media type
Explanation: The query mount * command cannot display status for the specified cartridge because it either has an invalid media type or you specified an invalid media type on the command.
Variable: vol_id is the specified cartridge.
The query acs command displays ACS status.
Use the query acs command to display the status of an ACS in the following format:
yyy-mm-dd hh:mm:ss ACS Status
Identifier State Free Cell Audit Mount Dismount Enter Eject
Count C/P C/P C/P C/P C/P
acs_id state count n/n n/n n/n n/n n/n
Where:
acs_id
is the ACS identifier.
state is one of the following ACS states:
online
The ACS is online.
offline
The ACS is offline.
offline pending
The ACS will process current and pending requests, then go offline. The ACS will reject any new requests.
diagnostic
The ACS will process only current and pending requests and will reject any new requests. The ACS is unavailable to client applications and can only be controlled using cmd_proc. Use the vary command to vary the ACS online.
recovery
The ACS is initializing or recovering from errors. Wait for the ACS to go online.
count
is the number of free cells in the ACS.
n
is the number of current (C) and pending (P) requests for the ACS for each command that requires library resources (audit, mount, dismount, enter, and eject).
To query ACS 1:
query acs 1
To query all ACSs in the library:
query acs all
See also:
| For information about... | See... |
|---|---|
| Changing the state of a library component | "vary" |
| Displaying request status | "query request" |
The query cap command displays CAP status.
cap_id | all
specifies the CAP to query or all for all CAPs.
Note:
You cannot specify acap_id that contains asterisks.Use the query cap command to display the status of a CAP.
The query cap command displays CAP status in the following format:
yyy-mm-dd hh:mm:ss CAP Status Identifier Priority Size State Mode Status cap_id cap_priority cap_size cap_state cap_mode status
cap_id
is the CAP identifier.
cap_priority
is the CAP priority.
cap_size
is the number of cells in the CAP.
is one of the following CAP states:
online
The CAP is online.
offline
The CAP is offline.
offline-pending
The CAP will process current and pending requests, then go offline. The CAP will reject any new requests.
diagnostic
The CAP will process only current and pending requests, and will reject any new requests. The CAP is unavailable to client applications, and can only be controlled using cmd_proc. Use the vary command to vary the CAP online.
recovery
The CAP is initializing or recovering from errors. Wait for the CAP to go online.
cap_mode
is one of the following CAP entry modes:
manual
You must unlock the CAP before entering cartridges.
automatic
The CAP is ready for cartridge entry.
status
is one of the following CAP statuses:
available
The CAP is available.
enter
The CAP is unavailable (reserved for entering cartridges).
eject
The CAP is unavailable (reserved for ejecting cartridges).
audit
The CAP is unavailable (reserved for audit processing).
To query CAP 0,1,0:
query cap 0,1,0
To query all CAPs in the library:
query cap all
See also:
| For information about... | See... |
|---|---|
| Displaying request status | "query request" |
| Setting CAP mode (manual or automatic) | "set cap mode" |
| Setting CAP selection priority | "set cap priority" |
| Changing the state of a library component | "vary" |
The query clean command displays cleaning cartridge status. Absent or ejected cartridges are not displayed. Cleaning cartridges that were reported as spent (used-up) by tape drives are not reported.
Use the query clean command to display the status of a cleaning cartridge in the following format:
yyy-mm-ddhh:mm:ssDrive Status Identifier State Status volumeType drive_id state status vol_idtype
Where:
vol_id
is the cartridge identifier of the cleaning cartridge.
cell_id
is the location of the cleaning cartridge.
max_usage
is the number of times the cleaning cartridge can be used.
current_usage
is the number of times the cleaning cartridge has been used.
status
is the location of the cleaning cartridge:
home
The cartridge is in a storage cell.
in drive
The cartridge is in a drive.
in transit
The cartridge is being moved.
type
is the cartridge media type (for example, 3480, DD3D, DLTIII, or STK1R).
To display status information for cleaning cartridge J35992:
query clean J35992
To query all cleaning cartridges:
query clean all
See also:
| For information about... | See... |
|---|---|
| Guidelines and procedures for cleaning drives | "Populating the LSM" |
| Setting cleaning cartridge attributes | "set clean" |
| Displaying cleaning cartridges and spent cleaning cartridges | "Using display Command Options" |
The query drive command displays drive status.
Use the query drive command to display the status of a drive in the following format:
Where:
drive_id
is the drive identifier.
state
is one of the following:
online
The drive is online.
offline
The drive is offline.
diagnostic
The drive will process only current and pending requests and will reject any new requests. The drive is unavailable to client applications, and can only be controlled using cmd_proc. Use the vary command to vary the drive online.
recovery
The drive is initializing or recovering from errors. Wait for the drive to go online.
status
is one of the following drive statuses:
In use
The drive has a cartridge mounted or is reserved for a mount.
Possible Scenario: You perform a query drive all and get a message saying the drive is in use. You then perform a display drive * and get a message saying the drive is reserved. This means: the reserved status for the drive implies that a mount request is in progress, and that a cartridge is on its way to the drive. At the same time, the drive is considered to be in use.
Available
The drive is available for a mount.
vol_id
is the identifier of the cartridge in the drive. This field is blank if there is no cartridge in the drive or if the cartridge's external label is unreadable or unknown.
drive_type
is the drive type.
To query drive 0,3,1,0:
query drive 0,3,1,0
To query all drives:
query drive all
See also:
| For information about... | See... |
|---|---|
| Changing the state of a library component | "vary" |
| Dismounting a cartridge from a drive | "dismount" |
| Drive serial numbers | "Using display Command Options" and "Using display Command Options" |
The query lmu command displays LMU and port status for both single-LMU and Dual-LMU ACS configurations and the desired state for ACSs and ports. If a library is partitioned, it also displays the partition ID.
The query lmu command is the best way to monitor ACSLS communication with the libraries it manages. query lmu:
Shows the status of ACSLS connections to the library.
Shows Redundant Electronics (RE) if any library in a string reports RE.
Shows single or Dual-LMU for non- RE libraries or a non- SL8500.
Displays the desired state for ACSs, port connections, LSMs, and tape drives.
Displays the partition ID of a partitioned library.
acs_id | all
specifies the ACS whose LMUs you want to query or select all to query LMUs for all ACSs.
Use the query lmu command to display LMU and port status and desired state for both single-LMU and Dual-LMU ACS configurations. The following examples show output for a library without Redundant Electronics and a library with Redundant Electronics.
Output Example without Redundant Electronics
ACSSA> q lmu all
2010-04-02 14:43:54 LMU Status
ACS: 0 Mode: Single LMU Active Status: Communicating
Not Partitioned Standby Status: -
ACS State Desired State
online online
Port Port State Desired State Role CL
0,0 online online - 21 springtime:9997
ACS: 1 Mode: Dual LMU Active Status: Communicating
Not Partitioned standby Status: Communicating
ACS State Desired State
online online
Port Port State Desired State Role CL
1,0 online online Active(A) 13 springtime:51100
1,1 online online standby(B) 13 springtime:51101
ACSSA>
Output Example of library with Redundant Electronics
ACSSA> q lmu all
2010-05-03 11:03:11 LMU Status
ACS: 0 Mode: Redundant Active Status: Communicating
Not Partitioned Standby Status: Communicating
ACS State Desired State
Online Online
Port Port State Desired State Role CL
0,0 online online Standby(A) 21 10.80.92.43
0,1 online online Standby(A) 21 10.80.93.33
0,2 online online Active(B) 21 10.80.92.52
0,3 online online Active(B) 21 10.80.93.47
0,4 online online Standy(B) 21 10.80.92.44
0,5 online online Active(A) 21 10.80.92.53
Where:
acs_id
is the ACS identifier.
mode
is the LMU mode (Dual LMU, Single LMU, or SCSI LMU).
status
is the active or standby LMU status (Communicating, Not Communicating, or Offline).
partition_status
shows if the library is partitioned. If it is partitioned, the library shows the partition to which you are connected. The partition status is:
Not Partitioned
Partition 1-n
The partition number.
acs_state
is the actual ACS state. States are:
online
The ACS is online.
diagnostic
The ACS will process only current and pending requests, and will reject any new requests. The ACS is unavailable to client applications, and can only be controlled using cmd_proc. Use the vary command to vary the ACS online.
offline
The ACS is offline.
offline pending
The ACS will process current and pending requests, then go offline. The ACS will reject any new requests.
acs_desired_state
you want the ACS to be in this state. The desired states are:
online
diagnostic
offline
port_id
is the port identifier.
port_state
is one of the following actual port states:
online
The port is online.
offline
The port is offline.
port_desired_state
you want to port to be in this state. The desired states are:
online
offline
role (des)
is the LMUs' role and designation (A or B), where roles are:
Active
LMU is in active role (the LMU is managing the ACS).
Standby
LMU is in standby role (not managing the ACS, communicating with the active LMU and available for switch over).
Note:
During switch over, therole field information is not current, and may display as a single dash (-). As the information becomes current, ACSLS refreshes the role field with the actual role of each LMU.compat_level
is the host/LMU microcode compatibility level. Level 11 or above is required for Dual-LMU configurations.
dev_name
is the port device name.
To display LMU and port status for all LMUs managing all ACSs:
query lmu all
To display LMU and port status for all LMUs managing ACSs 0 and 1:
query lmu 0 1
See also:
| For information about... | See... |
| Manually switching ACS management from the ACS's active LMU to the standby LMU | "switch lmu" |
The query lock command displays the lock status of a drive or cartridge.
type identifier | all
specifies the drive or cartridge to query or all for all drives or cartridges as shown in the following table.
Use the query lock command to display the lock status of a drive or cartridge in the following format:
yyy-mm-ddhh:mm:ssLock Status Identifier Lock-id Duration Pending StatusUser Identifier vol_id lock_id duration pending status user_id or drive_id lock_id duration pending status user_id
Where:
vol_id
is the identifier of the specified cartridge.
drive_id
is the identifier of the specified drive.
lock_id
is the lock ID.
duration
is the amount of time, in seconds, that the lock has been active.
pending
is the number of lock requests that are waiting for cartridge or drive.
status is one of the following statuses:
available
The cartridge or drive is available.
in use
The cartridge or drive is in use, or is reserved for a mount.
user_id
is the user ID that has locked the cartridge or drive. The user_id wraps after 80 characters.
To display lock status information for drive 1,0,4,0:
q loc dr 1,0,4,0
To display lock status information for all drives:
query lock drive all
To display lock status information for cartridge SL4493:
query lock cartridge SL4493
To display lock status information for all cartridges:
query lock cartridge all
See also:
| For information about... | See... |
| Removing all active or pending locks on a specified drive or cartridge | "clear lock" |
| Locking drives and cartridges | "lock" |
| Setting your lock ID | "set lock" |
| Displaying your lock or user ID | "show" |
| Removing active locks | "unlock" |
The query lsm command displays LSM status.
lsm_id | all
specifies the LSM to query or all, for all locks.
Use the query lsm command to display the status of an LSM in the following format:
yyy-mm-ddhh:mm:ssLSM Status
Identifier State Free Cell Audit Mount Dismount Enter Eject
Count C/P C/P C/P C/P C/P
Where:
lsm_id
is the LSM identifier.
state is one of the following LSM states:
diagnostic
The LSM will process only current and pending requests and will reject any new requests. The LSM is unavailable to client applications and can only be controlled using cmd_proc. Use the vary command to vary the LSM online.
offline
The LSM is offline.
offline pending
The LSM will process current and pending requests, then go offline. The LSM will reject any new requests.
online
The LSM is online.
recovery
The LSM is initializing or recovering from errors. Wait for the LSM to go online.
count
is the number of free storage cells in the LSM.
n
is the number of current (C) and pending (P) requests for the LSM for each command that requires library resources (audit, mount, dismount, enter, and eject).
To display status information for LSM 1 of ACS 0:
query lsm 0,1
To display status information for all LSMs:
query lsm all
See also:
| For information about... | See... |
|---|---|
| Displaying request status | "query request" |
| Changing the state of a library component | "vary" |
Use the query mount command to optimize the performance of a library with multiple LSMs, such as an SL8500 or a string of connected SL8500s. It displays the status of media-compatible drives for a specified data cartridge. These drives are not displayed if a cartridge(s) is absent or rejected. In addition:
When selecting the list of drives to be returned to a query mount request, the drives must be compatible with the volume specified.
Drives are ordered primarily by pass-thru distance. The drives in LSMs closest to the cartridge are listed first.
With ACSLS 7.3 and later releases, drives that are the same pass-thru distance from the cartridge are in least-recently-used order.
Example: The compatible drive with the longest time since a cartridge was dismounted, is first; the drive with the next longest time, is second, and so on.
Use the query mount command to display the status of all library drives attached to the same ACS as the cartridge, and compatible with the media type of the specified cartridge. query mount displays drive status for LSMs in any state (online, offline, offline pending, or diagnostic).
The compatible drives are ordered by proximity to the specified cartridge in the following format:
yyy-mm-dd hh:mm:ss Mount Status Identifier Status Drive State Status Volume Drive Type vol_id vol_stat drive_id state drive_stat inu_id drive_type
Where:
vol_id
is the identifier of the specified cartridge.
vol_stat
is the location of the cartridge:
home
The cartridge is in a storage cell.
in drive
The cartridge is in a drive.
in transit
The cartridge is being moved or is missing.
drive_id
is a list of all library drives compatible with the media type of the specified cartridge.
drive_id
is the drive identifier.
state
is one of the following drive states:
online
The drive is online.
offline
The drive is offline.
diagnostic
The drive will process only current and pending requests, and will reject any new requests. The drive is unavailable to client applications, and can only be controlled using cmd_proc. Use the vary command to vary the drive online.
recovery
The drive is initializing or recovering from errors. Wait for the drive to go online.
status
is one of the following drive statuses:
In use
The drive has a cartridge mounted or is reserved for a mount.
Available
The drive is available for a mount.
inu_id
is the identifier of the cartridge in the drive. The cartridge id appears only if the drive_stat is In use.
drive_type
is the drive type.
To display status information of drives ordered by proximity to cartridge ZUNI14:
query mount ZUNI14
See also:
| For information about... | See... |
|---|---|
| Mounting a data cartridge on a drive | "mount" |
| Displaying the lock status of a drive or cartridge | "query lock" |
| Displaying the location and media type of a cartridge | "query volume" |
| Changing the state of a library component | "vary" |
The query mount * command displays the status of drives that are compatible with the media in one or more specified scratch pools (and, optionally, only the drives compatible with a specific cartridge media type within the pool).
pool_id
specifies the scratch pool or pools to query.
media media_type | media *
specifies the media type.
Use the query mount * command to display the status of all library drives compatible with all cartridge media types in a specified scratch pool(s), and in the same ACS as the cartridges. Pool 0 is the common scratch pool. Specify the media_type option to restrict the display, to drives compatible with a specific cartridge media type within the pool. The displayed drives are ordered by proximity to the densest scratch pools. query mount * displays drive status for drives in LSMs in any state (online, offline, offline-pending, or diagnostic).
The query mount * command displays drive status in the following format:
yyy-mm-dd hh:mm:ss Mount Scratch Status Identifier Drive State Volume Status Drive Type pool_id drive_id state vol_id drive_stat drive_type
Where:
pool_id
is the specified scratch pool(s).
drive_id
is a list of all library drives compatible with all media types of the specified pool(s), or a specific media type within the pool if a media type was specified.
state
is one of the following drive states:
online
The drive is online.
offline
The drive is offline.
diagnostic
The drive will process only current and pending requests, and will reject any new requests. The drive is unavailable to client applications, and can only be controlled using cmd_proc. Use the vary command to vary the drive online.
recovery
The drive is initializing or recovering from errors. Wait for the drive to go online.
vol_id
is the identifier of the cartridge in the drive. The cartridge id appears only if the drive_stat is in use.
drive_stat
is one of the following drive statuses:
In use
The drive has a cartridge mounted or is reserved for a mount.
Available
The drive is available for a mount.
drive_type
is the drive type.
To display the status of compatible drives listed by proximity, to the largest concentration of scratch tapes in pool 5:
query mount * 5
See also:
| For information about... | See... |
|---|---|
| Creating or modifying scratch pools | "define pool" |
| Deleting empty scratch pools | "delete pool" |
| Mounting a scratch cartridge on a drive | "mount *" |
| Displaying the lock status of a drive or cartridge | "query lock" |
| Displaying scratch pool attributes | "query pool" |
| Displaying scratch cartridge status | "query scratch" |
| Setting or clearing cartridge scratch attributes | "set scratch" |
| Changing the state of a library component | "vary" |
The query pool command displays scratch pool attributes.
pool_id | all
specifies the scratch pool to query or all, for all pools. Pool 0 is the common pool.
Use the query pool command to display scratch pool attributes in the following format:
yyy-mm-dd hh:mm:ss Pool Status Identifier Volume Count Low Water Mark High Water Mark Attributes pool_id vol_count low_water_mark high_water_mark attribute
Where:
pool_id
is the specified scratch pool.
vol_count
is the number of scratch cartridges in the pool.
Cartridges not counted are absent and ejected scratch cartridges and data cartridges in a pool.
low_water_mark
is the low cartridge warning threshold. If the scratch cartridge count falls below this threshold, ACSLS logs a warning message in the Event Log.
A ”-” after the value means that the scratch cartridge count is below the low cartridge threshold.
high_water_mark
is the high cartridge warning threshold. If the scratch cartridge count reaches or exceeds this threshold, ACSLS logs a warning message in the Event Log. A ”+” after the value means that the scratch cartridge count is at or above the high cartridge threshold.
attribute
is displayed if overflow is set (using the set scratch command) for the specified scratch pool. Overflow specifies that scratch cartridges are selected from the common scratch pool (Pool 0) if mount scratch * requests cannot be satisfied with a cartridge from the specified scratch pool.
To display status information for scratch pool 5:
query pool 5
To display status information for all scratch pools:
query pool all
See also:
| For information about... | See... |
|---|---|
| Creating or modifying scratch pools | "define pool" |
| Deleting empty scratch pools | "delete pool" |
| Displaying scratch cartridge status | "query scratch" |
| Setting or clearing cartridge scratch attributes | "set scratch" |
The query port command displays port status.
Use the query port command to display the status of a port in the following format:
yyy-mm-dd hh:mm:ss Port Status State Identifier state port_id
Where:
state
is one of the following port states:
online
The port is online.
offline
The port is offline.
port_id
is the port identifier.
To display status information for port 0,0:
query port 0,0
To query all ports:
query port all
See also:
| For information about... | See... |
|---|---|
| Changing the state of a library component | "vary" |
The query request command displays request status.
Use the query request command to display the status of a request in the following format:
Where:
request_id
is the ACSLS request identifier.
command
is the ACSLS command that corresponds to the request identifier.
status
is one of the following request statuses:
Current
ACSLS is processing the request.
Pending
The request is waiting to be processed.
Not found
The specified request is not a valid ACSLS request.
To display status information for request 33179:
query request 33179
To display all current and pending requests:
query request all
See also:
| For information about... | See... |
|---|---|
| Cancelling a command | "cancel" |
The query scratch command displays the status of scratch cartridges in a pool sorted by ascending order of access date. The cartridges with the earliest access date are at the top of the list, with the most recently used cartridges at the bottom of the list. Pool IDs in the first column do not appear in any particular order. Only those cartridges permitted through Access Control are displayed.
pool_id | all
specifies the scratch pool to query or all, for all pools. Pool 0 is the common pool.
Use the query scratch command to display the status of scratch cartridges in a pool in the following format:
Where:
pool_id
is the specified scratch pool.
vol_id
is the identifier of the scratch cartridge.
cell_id
is the storage cell that contains the cartridge.
status
is the location of the cartridge:
home
The cartridge is in a storage cell.
in drive
The cartridge is in a drive.
in transit
The cartridge is being moved.
media_type
is the cartridges' media type.
Note:
Scratch cartridges with a cartridge status of absent, ejected, or missing are not included in thequery scratch output.To see cartridges sorted by pool, you issue successive query scratch commands for each pool. Alternately, you can issue the display volume command to see the information and sort it by pool, but you will not be guaranteed of getting the least recently used scratch cartridge.
To display status information for scratch cartridges in scratch pool 29015:
query scratch 29015
To display status information for scratch cartridges in all scratch pools:
query scratch all
See also:
| For information about... | See... |
|---|---|
| Creating or modifying scratch pools | "define pool" |
| Deleting empty scratch pools | "delete pool" |
| Setting or clearing cartridge scratch attributes | "set scratch" |
The query server command displays ACSLS and library status.
Use the query server command to display the status of ACSLS and the library in the following format:
Where:
Identifier
is blank
state
is one of the following ACSLS states:
idle
ACSLS is idle (not processing requests).
idle pending
ACSLS will process current and pending requests, reject new requests, then go idle.
recovery
ACSLS is initializing (going to run state), or recovering from errors; ACSLS is not processing requests.
run
ACSLS is running (processing requests).
count
is the number of free storage cells in the library.
n
is the number of current (C) and pending (P) ACSLS requests for each command that requires library resources (audit, mount, dismount, enter, and eject).
HINT: You cannot cancel a query server request.
To display status information on the server:
query server
See also:
| For information about... | See... |
|---|---|
| Changing the state of a library component | "vary" |
| Displaying request status | "query request" |
The query volume command displays the location of a cartridge.
Use the query volume command to display the location of a volume in the following format:
Where:
vol_id
is the volume identifier.
status
is the location of the cartridge.
home
The cartridge is in a storage cell.
in drive
The cartridge is in a drive.
in transit
The cartridge is being moved or is missing.
absent
The cartridge cannot be found.
ejected
The cartridge has been ejected from the library.
location
specifies the location as one of the following:
If the status is home, the location is a storage cell identifier.
If the status is in transit, the location is either a cell identifier or a drive identifier.
If the status is in drive, the location is a drive identifier.
media_type
is the volume's media type.
To display status information for volume 2903B:
query volume 2903B
To display all volumes in the library:
q volume all
See also:
| For information about... | See... |
|---|---|
| Other volume information | "Creating a Logging Volume Statistics Report" |
| Display Command | "Using display Command Options" and "Using display Command Options" |
| Mounting a data volume on a drive | "mount" |
| Displaying the lock status of a drive or volume | "query lock" |
| Displaying the status of media-compatible drives for a specified data volume | "query mount" |
| Displaying scratch pool attributes | "query pool" |
| Setting or clearing volume scratch attributes | "set scratch" |
| Changing the state of a library component | "vary" |
The set commands set various attributes of different library components. See the following sections for more information about each set command, including format, options, usage, and messages.
The following shows the general format of the set commands:
set type [off | subtype] [*] identifier...
See also:
| For information about... | See... |
|---|---|
| Cancelling a command | "cancel" |
The set cap mode command sets a CAPs' entry mode.
cap_mode
specifies manual or automatic CAP mode.
cap_id
specifies the CAP identifier.
You cannot specify a CAP identifier that contains an asterisk (*) unless the priority is set.
Use the set cap mode command to set a CAP's entry mode to one of the following modes:
manual
You must enter an enter command before entering cartridges.
automatic
You can enter cartridges without first entering an enter command.
Note:
You cannot set the CAP mode to automatic in a partitioned library.HINT: You cannot change a CAP's mode while the CAP is in use. That is, if the door is open during either manual or automatic enter operations, you cannot change its mode until you complete the enter operation.
To set CAP 0,3,1 in manual mode:
set cap mode manual 0,3,1
To set CAP 0,3,1 in automatic mode:
set cap mode automatic 0,3,1
See also:
| For information about... | See... |
|---|---|
| Making a CAP (manual mode) ready to enter labelled cartridges into the library | "enter" |
| Displaying CAP status | "query cap" |
| Changing the state of a library component | "vary" |
This section discusses the command messages.
Set: CAP cap_id, mode changed to cap_mode.
Explanation: ACSLS changed the mode of the specified CAP.
Variable:
cap_id is the CAP whose mode is changed.
cap_mode is the new enter mode of the CAP.
None.
Set: CAP cap_id Set failed, Incorrect attribute.
Explanation: ACSLS cannot change the mode of the specified CAP because you specified an invalid CAP mode.
Variable: cap_id is the CAP whose mode is not changed.
CAP cap_id: Automatic mode.
Explanation: ACSLS changed the specified CAP's mode to automatic.
Variable: cap_id is the CAP whose mode is changed.
CAP cap_id: Manual mode.
Explanation: ACSLS changed the specified CAP's mode to manual.
Variable: cap_id is the CAP whose mode is changed.
The set cap priority command sets a CAP's automatic selection priority.
cap_priority
specifies the CAP priority. Valid values are 0 to 16, where 16 is the highest priority. All CAPs initially have a 0 priority, which means that ACSLS does not automatically select the CAP.
Note:
If you are using the AEM option. Since the AEM should not be used for small enters and ejects, the maximum CAP priority is 1. This aids in preventing the AEM from being selected when the CAP ID is wild-carded with an asterisk on anaudit, enter, or eject. For more information on the AEM, refer to "Using the AEM".cap_id
specifies the CAP identifier. You must specify a particular CAP; you cannot specify an asterisk (*) to set the same priority for all CAPs.
Use the set cap priority command to set a CAP's automatic selection priority.
If a CAP request specifies an asterisk (*) for the CAP ID, ACSLS automatically selects an available CAP with the highest nonzero priority for each ACS specified in the request.
To assign priority 16 to CAP 0,3,1:
set cap priority 16 0,3,1
See also:
| For information about... | See... |
|---|---|
| Updating the ACSLS database to match the actual inventory of library cartridges | "audit" |
| Ejecting cartridges from the library | "eject" |
| Making a CAP (manual mode) ready to enter labelled cartridges into the library | "enter" |
| Displaying CAP status | "query cap" |
| Changing the state of a library component | "vary" |
Updates the ACSLS database to match the actual inventory of library cartridges.
Set: CAP cap_id, priority changed to cap_priority.
Explanation: ACSLS changed the priority of the specified CAP.
Variable:
cap_id is the CAP whose priority is changed.
cap_priority is the new CAP priority.
None.
Set: CAP cap_id Set failed, Incorrect attribute.
Explanation: ACSLS cannot change the mode of the specified CAP because you specified an invalid CAP priority.
Variable: cap_id is the CAP whose priority is not changed.
The set clean command sets cleaning cartridge attributes.
For all modern cleaning cartridges, cleaning cartridge attributes are automatically set when the cleaning cartridges are added by audit, enter, or Cartridge Recovery. This includes setting the cleaning cartridges max_usage.
max_usage | off
specifies the number of times a cleaning cartridge is used before ACSLS stops selecting the cartridge to clean drives. off specifies that ACSLS will not select the cartridge and redefines the cartridge as a data cartridge.
Note:
You cannot: specify a maximum cleaning usage for a media type that is reserved for only data cartridges; set cleaningoff for a media type that is only a cleaning cartridgevol_id | volrange
specifies the cleaning cartridge or range of cartridges.
Use the set clean command to set the number of times ACSLS will select a cleaning cartridge. You also use set clean to set a cartridge's cleaning cartridge attribute off, which you do if you have incorrectly defined a data cartridge as a cleaning cartridge.
To set the maximum use to 10 for cleaning cartridges CLN108 - CLN112:
set clean 10 CLN108-CLN112
To set the cleaning cartridge attribute off and redefine cartridges HRR234 - HRR244 as data cartridges:
set clean off HRR234-HRR244
See also:
| For information about... | See... |
|---|---|
| Guidelines and procedures for cleaning drives | "Populating the LSM" |
| Displaying cleaning cartridge status | "query clean" |
This section discusses the command area messages.
Set: volume vol_id is a cleaning cartridge.
Explanation: ACSLS specified that the cleaning cartridge is valid for drive cleaning.
Variable: The vol_id is the valid cleaning cartridge.
Set: volume vol_id is not a cleaning cartridge.
Explanation: ACSLS specified that the cleaning cartridge is not valid for drive cleaning.
Variable: The vol_id is the invalid cleaning cartridge.
None.
Set: Clean vol_id Set failed, Incorrect attribute.
Explanation: ACSLS cannot change the cleaning attribute because the specified cartridge is not a cleaning cartridge.
Variable: The vol_id is the data or scratch cartridge.
The set lock command sets your lock ID.
Use the set lock command to set or change your lock ID. Change your current lock ID when you want to remove locks on a drive or cartridge whose lock ID does not match your current lock ID, as follows:
To clear all locks on a specified drive or cartridge, set your lock ID to 0, then enter a clear lock command.
To remove active locks on drives or cartridges, set your lock ID to the lock ID of the locked components, then enter an unlock command.
Note:
When you enter alock command to lock a cartridge or drive and your lock ID is zero (0), ACSLS assigns a lock ID to the cartridge or drive, and then changes your lock ID to the lock ID of the cartridge or drive. You cannot use the set lock command to set your lock ID and then use the lock command to lock a cartridge or drive with the lock ID that you set with set lock.To change your current lock ID lock to new lock ID 354:
set lock 354
See also:
| For information about... | See... |
|---|---|
| Removing all active or pending locks on a specified drive or cartridge | "clear lock" |
| Locking drives and cartridges | "lock" |
| Displaying the lock status of a drive or cartridge | "query lock" |
| Displaying your lock or user ID | "show" |
| Removing active locks | "unlock" |
The set owner command sets volume ownership.
owner_id
specifies the owner identifier. You must enclose this value in quotes (" ").
volume vol_id | volrange
specifies the volume or range of volumes.
Use the set owner command to set volume ownership. Enter set owner from cmd_proc; you cannot set volume ownership from a client application.
The set scratch command sets or clears a volumes' scratch attribute and assigns the volume to a pool.
You can also use the watch_vols utility to automatically set scratch cartridge attributes automatically when scratch cartridges are added or re-activated by audit, enter, or Cartridge Recovery.
off
specifies that the volume is a data cartridge.
pool_id
specifies the cartridges' scratch pool. Specify an asterisk (*) to reassign a data cartridge to its current pool.
vol_id | volrange
specifies the volume or range of volumes.
Use the set scratch command to set or clear a volumes' scratch attribute, and assign the volume to a pool.
To define volumes YUMA10-YUMA20 as scratch volumes, and assign them to scratch pool 5:
set scratch 5 YUMA10-YUMA20
To move scratch volumes YUMA10-YUMA15 to pool 10:
set scratch 10 YUMA10-YUMA15
To ”unscratch” (change from scratch to data) volumes YUMA16-YUMA20, and move them to the common pool (pool 0):
set scratch off 0 YUMA16-YUMA20
To scratch to data volumes YUMA16-YUMA20 and keep them in their current pool:
set scratch * YUMA16-YUMA20
See also:
| For information about... | See... |
|---|---|
| Displaying scratch cartridge status | "query scratch" |
| Displaying scratch pool attributes | "query pool" |
| Creating or modifying scratch pools | "define pool" |
| Deleting empty scratch pools | "delete pool" |
This section discusses the command area messages.
Set: volume vol_id in tape pool pool_id is a scratch cartridge.
Explanation: ACSLS changed the specified data cartridge to a scratch cartridge and assigned it to a pool.
Variable:
The vol_id is the specified volume.
The pool_id is the pool to which the volume is assigned.
Set: volume vol_id in tape pool pool_id is a data volume.
Explanation: ACSLS changed the specified scratch cartridge to a data cartridge.
Variable: The vol_id is the specified volume.
None.
Set: Scratch vol_id Set failed, Incorrect attribute.
Explanation: ACSLS cannot change the scratch attribute because the specified cartridge is a cleaning cartridge.
Variable: The vol_id is the cleaning cartridge.
Pool pool_id: low water mark warning.
Explanation: The number of cartridges in the specified scratch pool is less than or equal to the low threshold.
Variable: The low_water_mark is the low threshold of the specified scratch pool.
Pool pool_id: high water mark warning.
Explanation: The number of cartridges in the specified scratch pool is greater than or equal to the high threshold.
Variable: The high_water_mark is the high threshold of the specified scratch pool.
The show command displays your lock ID or user ID.
To display requestor's user_id:
show user
To display current lock_id:
show lock
See also:
| For information about... | See... |
|---|---|
| Removing all active or pending locks on a specified drive or cartridge | "clear lock" |
| Locking drives and cartridges | "lock" |
| Displaying the lock status of a drive or cartridge | "query lock" |
| Setting your lock ID | "set lock" |
| Removing active locks | "unlock" |
The start command starts ACSLS request processing.
Use the start command to put ACSLS in run state and start ACSLS request processing. You typically use the start command to restart request processing if ACSLS is idled.
To restart ACSLS request processing:
start
If ACSLS is in run state, entering the start command has no effect.
See also:
| For information about... | See... |
|---|---|
| Stopping ACSLS from processing new requests | "idle" |
| Displaying the status of a library component | "query commands" |
| Changing the state of a library component | "vary" |
This section discusses the command area messages.
ACSLM Request Processing Started: Success.
Explanation: ACSLS started processing requests.
None.
ACSLM Request Processing Not Started: status
Explanation: ACSLS did not start processing requests.
Variable: status is the reason for the failure. For more information on common status messages, see ACSLS Messages.
In Redundant Electronics (RE) or Dual-LMU configurations, the switch lmu command manually switches ACS management from the active library controller (LC) to the standby LC.
switch lmu only supports ACSs with a single RE library, either an SL3000 or a standalone SL8500.
switch lmu does not support partitioned SL8500s or SL3000s.
acs_id
specifies the ACS to switch library management from the active to the standby LC or LMU.
Use the switch lmu command to manually switch library management from the library's active LC or LMU to the standby LC or LMU. Before you enter a switch lmu command, make sure that:
ACSLS is in run state
The ACS you specify is in the online or diagnostic state
At least one port is online to each LC or LMU
In RE or Dual-LMU configurations, use the switch lmu command to switch ACS management from the library's active LC or LMU to the standby LC or LMU. Assume the following RE configuration:
In a library, LC A is in the active role and LC B is in the standby role.
If ACSLS loses communication to LC A, but can still communicate with LC B, use switch lmu to make LC B the active LC.
See also:
| For information about... | See... |
|---|---|
| Displaying ACS status | "query acs" |
| Displaying ACS and port status with details | "query lmu" |
| Displaying port status | "query port" |
| Displaying ACSLS and library status | "query server" |
| Starting ACSLS request processing | "start" |
| Changing the state of a library component | "vary" |
| Redundant Electronics | "Overview" |
This section discusses the command area messages.
Switch: Switch lmu completed for acs_id, Success.
Explanation: ACSLS switched library management from the active to the standby LMU.
Variable: The acs_id is the ACS whose LC or LMUs switched roles.
Switch: Switch lmu initiated for acs_id, Success.
Explanation: ACSLS started switching library management from the active to the standby LC or LMU.
Variable: The acs_id is the ACS whose LC or LMUs are switching roles.
Switch: Switch lmu failed, acs_id not found.
Explanation: You specified an invalid ACS.
Variable: The acs_id is the ACS identifier you specified on the switch lmu command.
Switch: Switch lmu failed, acs_id is offline.
Explanation: You specified an ACS that is offline. Use the vary command to vary the ACS to online or diagnostic mode.
Variable: The acs_id is the ACS identifier you specified on the switch lmu command.
Switch: Switch lmu failed, acs_id not configured for dual lmu.
Explanation: You specified an ACS that is not configured with active and standby LC or LMUs. Either:
Reconfigure the specified ACS, then re-enter the switch lmu command
Enter a switch lmu command that specifies a library that is configured with active and standby LCs or LMUs.
Variable: The acs_id is the ACS identifier you specified on the switch lmu command.
Switch: Switch lmu failed, not communicating.
Explanation: switch lmu switch failed because the standby LC or LMU is not communicating. Check the standby LC or LMU for communications problems.
Switch: Switch lmu failed, switch already active.
Explanation: switch lmu is in progress for the ACS you specified. Wait until the switch completes, then, re-enter the switch lmu command.
Switch: Switch lmu failed, port is offline.
Explanation: You specified an ACS with no ports online. Vary at least one port online to each LC or LMU.
The unlock command removes active locks (associated with your current lock ID) on a specified drive or cartridge or removes all active locks.
type identifier
specifies a library component. The following table lists the components that you can unlock.
Table 12-6 Valid Components for Unlock
| Library Component | type | identifier |
|---|---|---|
|
drive |
|
drive_id |
|
volume |
|
vol_id |
all
specifies all active locks.
Use the unlock command to remove active locks on specified cartridges and drives or remove all active locks. The lock ID of the component must match your current lock ID.
When you unlock a component that is not in use, ACSLS checks for pending locks on the component. If there is a pending lock, ACSLS locks the component with the lock ID of the pending lock.
Note:
Theunlock command always resets your lock ID to 0.To remove active locks on drive 0,0,2,0:
unlock drive 0,0,2,0
To remove active locks on all locked cartridges:
unlock volume all
See also:
| For information about... | See... |
|---|---|
| Removing all active or pending locks on a specified drive or volume | "clear lock" |
| Locking drives and volumes | "lock" |
| Displaying the lock status of a drive or cartridge | "query lock" |
| Setting your lock ID | "set lock" |
| Displaying your lock or user ID | "show" |
This section discusses the command area messages.
Unlock: Unlock completed, Success.
Unlock: drive drive_id unlocked.
Explanation: ACSLS unlocked the specified drive.
Variable: The drive_id is the unlocked drive.
Unlock: Unlock completed, Success.
Unlock: volume vol_id unlocked.
Explanation: ACSLS unlocked the specified volume.
Variable: The vol_id is the unlocked volume.
None.
Unlock: Unlock of drive drive_id failed, status.
Explanation: ACSLS cannot unlock the drive.
Variable: The status is the reason for the failure. For more information on common status messages, see ACSLS Messages.
Unlock: Unlock of volume vol_id failed, status.
Explanation: ACSLS cannot unlock the volume.
Variable: The status is the reason for the failure. For more information on common status messages, see ACSLS Messages.
The uptime command indicates the amount of elapsed time ACSLS has been enabled and/or the last restart of the ACSLS library manager.
Use the uptime command to display the amount of elapsed time ACSLS has been enabled and/or the last restart of the ACSLS library manager, in the following format:
ACSLS uptime=<days-hrs:min:sec>
Where:
days
is the number of days.
hrs
is the number of hours.
min
is the number of minutes.
sec
is the number of seconds:
The vary command changes the state of a library component.
type [identifier]
specifies a library component. The following table lists the components you can vary.
Table 12-7 Valid Components for Vary
| ACS Component | type | identifier |
|---|---|---|
|
ACS |
|
acs_id |
|
LSM |
|
acs_id,lsm_id |
|
CAP |
|
cap_id |
|
drive |
|
drive_id |
|
port |
|
port_id |
state
specifies one of the following device states: online (online to clients and cmd_proc), offline, or diagnostic (online to cmd_proc only).
You can vary an ACS, LSM, CAP, or drive online, offline, or diagnostic. You can vary a port either online or offline. See "Usage" for more information about device states.
force
varies an ACS, LSM, CAP, or drive offline after processing only the current robotic request.
Use the vary command to change the state of an ACS, LSM, CAP, drive, or port. The following sections tell how each of the device states affects library components.
vary offline
The following table shows the results of vary offline for each ACS component. When you vary a component offline and it first goes to offline-pending state, ACSLS processes all active and pending requests for the component, rejects new requests, then varies the component offline.
Table 12-8 Vary Offline Results
| ACS Component | Results |
|---|---|
|
ACS |
ACS and subcomponents go offline-pending, then offline. LSMs must go offline before the ACS goes offline. |
|
LSM |
LSM goes offline-pending, then offline. |
|
CAP |
CAP goes offline-pending, then offline. |
|
drive |
If available, drive goes offline immediately. If in use, drive stays online. |
|
port |
Port goes offline immediately if:
Otherwise, the port stays online. |
vary offline force
The following table shows the results of vary offline force for each ACS component. This option is useful if the device must be taken to the offline state while it is involved in extended activity (for example, during an audit).
Table 12-9 Vary Offline Force Results
| ACS Component | Results |
|---|---|
|
ACS |
Only the current robotic request completes, then the ACS and subcomponents go offline immediately. Pending requests are discarded and new requests are rejected. LSMs must go offline before the ACS goes offline. |
|
LSM |
Only the current robotic request completes, then the LSM goes offline immediately. Pending requests are discarded and new requests are rejected. |
|
CAP |
Only the current robotic request completes, then the CAP goes offline immediately. Pending requests are discarded and new requests are rejected. |
|
drive |
Only the current robotic request completes, then the drive goes offline immediately. Pending requests are discarded and new requests are rejected. |
|
port |
Not valid. |
vary diagnostic
The vary diagnostic request places the specified component in the diagnostic state (online to cmd_proc only). ACSLS processes all active and pending requests for the component, rejects new client application requests, then varies the component to diagnostic state. For an ACS, all of its subordinate LSMs are also varied to diagnostic.
vary online
The following table shows the results of vary online for each ACS component. When you vary a component online and it first goes to recovery state, ACSLS processes all active and pending requests for the component, rejects new requests, then varies the component online. When the component goes to online, ACSLS processes all requests for the component.
Table 12-10 Vary Online Results
| ACS Component | Results |
|---|---|
|
ACS |
If ACS is offline, ACS and its LSM go to recovery, then online. If ACS is in diagnostic state, ACS and its LSM go to online immediately. |
|
LSM |
LSM goes to recovery, then online. You cannot vary an LSM online if it is attached to an offline ACS. |
|
CAP |
CAP goes to recovery, then online. |
|
drive |
drive goes to recovery, then online. |
|
port |
Port goes online immediately. |
To vary drive 0,0,9,3 offline:
vary drive 0,0,9,3 offline
To vary CAP 0,0,0 diagnostic:
vary cap 0,0,0 diagnostic
To force lsm 0,1 offline:
vary lsm 0,1 offline force
Note:
IPLing the system does not change the state of these components. Installing or reconfiguring ACSLS places all components in the online state wherever possible.When two or more partitions of the same library are managed by ACSLS, use separate vary commands to vary the same CAP (identified as being in different ACSs).
Example: If ACS 0 and ACS 1 are two partitions of the same library, vary the CAP online or offline independently for each partition (and each ACS). The same CAP can be varied online to one partition (ACS) and offline to another partition (ACS).
See also:
| For information about... | See... |
|---|---|
| Displaying the status of a library component | "query commands" |
This section discusses the command area messages.
Vary: type identifier Varied state
Explanation: ACSLS changed the state of the specified library component.
Variable:
The type is the library component type.
The identifier is the library component identifier.
The state is the new state of the library component.
None.
In-transit volume recovery incomplete.
Explanation: The LSM robot cannot dispose of in-transit volumes while the LSM or its ACS is varied online. If you are varying an ACS online, the ACS state is changed to online immediately, but any LSMs that are unable to complete in-transit volume recovery remain offline.
Vary: Vary type identifier failed, Drive in use.
Explanation: ACSLS cannot change the state of the specified library component because the command involved an in-use drive.
Variable:
The type is the library component type.
The identifier is the library component identifier.
Vary: Vary type identifier failed, Incorrect lockid
Explanation: ACSLS cannot change the state of the specified library component because the drive lock_id does not match your lock_id.
Variable:
The type is the library component type.
The identifier is the library component identifier.
Vary: Vary type identifier failed, State unchanged.
Explanation: ACSLS cannot change the state of the specified library component because the component is already in the requested state.
Variable:
The type is the library component type.
The identifier is the library component identifier.
Vary: Vary type identifier failed, Vary disallowed.
Explanation: ACSLS cannot change the state of the specified library component because a vary diagnostic request was issued from a client application.
Variable:
The type is the library component type.
The identifier is the library component identifier.
Vary: Vary type identifier failed, Incorrect state.
Explanation: ACSLS cannot change the state of the specified library component because you tried to vary:
A CAP online when the LSM or ACS is in the diagnostic or offline state.
A CAP diagnostic when the LSM or ACS is offline.
An LSM online when the ACS is in the diagnostic or offline state.
An LSM diagnostic if the ACS is offline.
Variable:
The type is the library component type.
The identifier is the library component identifier.
Vary: Vary type identifier failed, Vary in progress.
Explanation: ACSLS cannot change the state of the specified library component because:
A CAP, its LSM, or its ACS is in a transitory (recovery or offline-pending) state.
An LSM, its ACS, or a subordinate CAP is in a transitory state.
An ACS, a subordinate LSM, or a subordinate CAP is in a transitory state.
A vary offline/force request overrode the attempt to change an ACS, LSM, or CAP to the diagnostic or online state.
A drive is in a transitory state of recovery.
Variable:
The type is the library component type.
The identifier is the library component identifier.
Vary: Vary type identifier failed, State unchanged.
Explanation: ACSLS cannot change the state of the specified library component because you tried to vary an ACS, LSM, or CAP offline and a vary offline/force request overrode the attempt.
Variable:
type is the library component type.
identifier is the library component identifier.
Vary: Vary type identifier failed, ACS online.
Explanation: ACSLS cannot change the state of the specified library component because you tried to vary the last port offline in an online ACS.
Variable:
The type is the library component type.
The identifier is the library component identifier.
Vary: Vary type identifier failed, No ports online.
Explanation: ACSLS cannot change the state of the specified library component because there are no ports online for an ACS.
Variable:
The type is the library component type.
The identifier is the library component identifier.
One of the following messages appears when an ACS, LSM, drive, or port changes state.
ACS acs_id: state
LSM lsm_id: state
Drive drive_id: state
Port port_id: state
The following message appears if, during recovery of in-transit volumes, a cartridge label is unreadable or a duplicate. The cartridge is moved to the CAP.
CAP cap_id. Remove volumes from CAP.
cap_id
is the CAP containing the cartridges.