PK #.ze ) tivoli/tsm/swap/51/eng/html/ashgs007.html
PK #.l14 4 ) tivoli/tsm/swap/51/eng/html/ashgs999.htmlTo register a new license with the Tivoli Storage Manager server, first complete the following field and then click Finish, or click Cancel to end the task. Licenses are stored in files called enrollment certificate files. When registered, the licenses are stored in a file named NODELOCK in the current directory from which the server was started. The nodelock file contains an entry for each license file you register.
You can specify the number of license files you would like to register by entering the number just before the license authorization code. For example, you may enter 10mgsyslan.lic. You should always specify the total of number of registered licenses, as this may also be used to change the quantity of registered licenses. For example, you may have 10 registered licenses and you need to register 20, enter 20mgsyslan.lic
Enter the name of the enrollment certificate file containing the license to be registered. The specification can contain a filename wildcard (*). Note: The names of the files are case-sensitive.
Example: To register all files, enter: *.lic
You can obtain the licensed features and register those licenses by entering the following enrollment certificate files.
mgsyslan.lic | License for a managed system (client) that moves data to and from storage over a LAN. |
mgsyssan.lic | License for each system that uses Tivoli Space Manager. A Managed System for LAN license is required if you use a communication protocol other than shared memory. |
spacemgr.lic | License for each system that uses Tivoli Space Manager. A Managed System for LAN license is required if you use a communication protocol other than shared memory. |
domino.lic | Tivoli Data Protection for Lotus Domino. A Managed System for LAN license is required if you use a communication protocol other than shared memory. |
drm.lic | Tivoli Disaster Recovery Manager (this includes server-to-server virtual volumes for database and storage pool backup).
This is required on a source server and not on a target server.
Note: |
ess.lic | Tivoli Data Protection for ESS. A Managed System for LAN license is required if you use a communication protocol other than shared memory. |
essr3.lic | Tivoli Data Protection for ESS R/3. A Managed System for LAN license is required if you use a communication protocol other than shared memory. |
emcsymm.lic | Tivoli Data Protection for EMC Symmetrix. A Managed System for LAN license is required if you use a communication protocol other than shared memory. |
emcsymr3.lic | Tivoli Data Protection for EMC Symmetrix R/3. A Managed System for LAN license is required if you use a communication protocol other than shared memory. |
informix.lic | Tivoli Data Protection for Informix. A Managed System for LAN license is required if you use a communication protocol other than shared memory. |
lnotes.lic | Tivoli Data Protection for Lotus Notes. A Managed System for LAN license is required if you use a communication protocol other than shared memory. |
mssql.lic | Tivoli Data Protection for MS SQL. A Managed System for LAN license is required if you use a communication protocol other than shared memory. |
msexch.lic | Tivoli Data Protection for MS Exchange. A Managed System for LAN license is required if you use a communication protocol other than shared memory. |
oracle.lic | Tivoli Data Protection for Oracle. A Managed System for LAN license is required if you use a communication protocol other than shared memory. |
r3.lic | Tivoli Data Protection for R/3. A Managed System for LAN license is required if you use a communication protocol other than shared memory. |
libshare.lic | License for the Tape Library Sharing feature. This is required on a Tivoli Storage Manager server that can access a shared library, including the library manager. |
library.lic | License for Managed Library. Tivoli Storage Manager requires this license for each library in the Extended Device Category that is managed by a Tivoli Storage Manager server. |
To assign a sequential access volume to a storage pool, first complete the following fields and then click Finish, or click Cancel to end the task.
Select the name of the storage pool to which the volume is assigned.
Enter the name of the storage pool volume. The volume name cannot contain any embedded blanks or equal signs. Use the following naming conventions when specifying volumes for each device type:
Device Type | Name Requirements |
File | Specify any fully qualified name string for your platform, for example: /data/fpool01.dsm |
Removablefile | Specify 1-6 alphanumeric characters. |
Server | Specify 1-250 alphanumeric characters. |
3590, 4mm, 8mm, DLT, DTF, QIC, LTO, NAS | Specify 1-6 alphanumeric characters. |
Select how client nodes and server processes (such as migration) can access files in the storage pool volume. The default is Readwrite.
Readwrite | Specifies that client nodes and server processes can read from and write to files stored on the volume. |
Readonly | Specifies that client nodes and server processes can only read files stored on the volume. |
Unavailable | Specifies that neither client nodes nor server processes can access files stored on the volume. The server does not attempt to access the volume. |
Offsite | Specifies that the volume is at an offsite location from which it cannot be mounted. This value is valid only for a volume in a copy storage pool. |
Enter the location of the volume. This field is optional. The maximum length is 255 characters.
PK #.9 ) tivoli/tsm/swap/51/eng/html/ashps057.htmlTo register a new license with the Tivoli Storage Manager server, first complete the following field and then click Finish, or click Cancel to end the task. Licenses are stored in files called enrollment certificate files. When registered, the licenses are stored in a file named NODELOCK in the current directory from which the server was started. The nodelock file contains an entry for each license file you register.
With the exception of the drm.lic and libshare.lic, you can specify the number of license files you would like to register by entering the number just before the license authorization code. For example, you may enter 10mgsyslan.lic. You should always specify the total of number of registered licenses, as this may also be used to change the quantity of registered licenses. For example, you may have 10 registered licenses and you need to register 20, enter 20mgsyslan.lic
Enter the name of the enrollment certificate file containing the license to be registered. The specification can contain a filename wildcard (*). Note: The names of the files are case-sensitive.
Example: To register all files, enter: *.lic
You can obtain the licensed features and register those licenses by entering the following enrollment certificate files.
Note: Each Tivoli Data Protection client also requires a Managed System for LAN license if you use a communication protocol other than shared memory.
mgsyslan.lic | License for a managed system (client) that moves data to and from storage over a LAN. |
mgsyssan.lic | License for each storage agent. The Tape Library Sharing feature is required on the server. This license is required for server-free data movement. |
spacemgr.lic | License for each system that uses Tivoli Space Manager. A Managed System for LAN license is required if you use a communication protocol other than shared memory. |
domino.lic | Tivoli Data Protection for Lotus Domino. A Managed System for LAN license is required if you use a communication protocol other than shared memory. |
ess.lic | Tivoli Data Protection for ESS. A Managed System for LAN license is required if you use a communication protocol other than shared memory. |
essr3.lic | Tivoli Data Protection for ESS R/3. A Managed System for LAN license is required if you use a communication protocol other than shared memory. |
emcsymm.lic | Tivoli Data Protection for EMC Symmetrix. A Managed System for LAN license is required if you use a communication protocol other than shared memory. |
emcsymr3.lic | Tivoli Data Protection for EMC Symmetrix R/3. A Managed System for LAN license is required if you use a communication protocol other than shared memory. |
informix.lic | Tivoli Data Protection for Informix. A Managed System for LAN license is required if you use a communication protocol other than shared memory. |
lnotes.lic | Tivoli Data Protection for Lotus Notes. A Managed System for LAN license is required if you use a communication protocol other than shared memory. |
mssql.lic | Tivoli Data Protection for MS SQL. A Managed System for LAN license is required if you use a communication protocol other than shared memory. |
msexch.lic | Tivoli Data Protection for MS Exchange. A Managed System for LAN license is required if you use a communication protocol other than shared memory. |
oracle.lic | Tivoli Data Protection for Oracle. A Managed System for LAN license is required if you use a communication protocol other than shared memory. |
r3.lic | Tivoli Data Protection for R/3. A Managed System for LAN license is required if you use a communication protocol other than shared memory. |
drm.lic | Tivoli Disaster Recovery Manager (this includes server-to-server virtual volumes for database and storage pool backup). This is required on a source server and not on a target server. |
libshare.lic | License for the Tape Library Sharing feature. This is required on a Tivoli Storage Manager server that can access a shared library, including the library manager. |
library.lic | License for Managed Library. Tivoli Storage Manager requires this license for each library in the Extended Device Category that is managed by a Tivoli Storage Manager server. |
To define a drive to a library, complete the following fields and then click Finish, or click Cancel to end this task.
Enter the name of the library to which the drive is to be assigned. This parameter is required for all drives including stand-alone drives. The specified library must have been previously defined.
Enter the name assigned to the drive. This parameter is required. The maximum length of this name is 30 characters.
Enter the element address of the drive within a SCSI library. This field is valid only for drives in SCSI libraries when the operation is performed from a server that is a library manager.
The following options are available for the element parameter:
The server needs the element address to connect the physical location of the drive to the drive's SCSI address. To find the element address for your library configuration, consult the manufacturer's information.
Select an option. This parameter is optional. The default is Yes.
Yes | The drive is online. |
No | The drive is not online. |
Enter the value for the cleaning frequency you would like to establish for the selected drive. The default is None.
The following are possible values:
None | Specifies that the server does not track the need for device cleaning. Some libraries have their own automatic cleaning. |
Asneeded | Specifies that the server loads the drive with a checked-in cleaner cartridge only when a drive reports to the device driver that it needs cleaning. |
Gigabytes | Specifies a value in gigabytes, from 1 to 9999. This indicates how much data processing will occur before the server loads the drive with a cleaner cartridge. Drive cleaning will still take place when a drive indicates that cleaning is required. |
Consult the drive manufacturer's information for cleaning recommendations. If the information gives recommendations for
cleaning frequency in terms of hours of use, convert to a gigabytes value by doing the following:
To update a drive, complete the following fields and then click Finish, or click Cancel to end this task.
Enter the element address of the drive within a SCSI library. This field is valid only for drives in SCSI libraries when the operation is performed from a server that is a library manager.
The server needs the element address to connect the physical location of the drive to the drive's SCSI address. To find the element address for your library configuration, consult the manufacturer's information.
Select the value of the drive's online state. This parameter is optional.
Do not specify other optional parameters along with ONLINE=YES or ONLINE=NO, because the drive will not be updated and the command will fail when the drive is in use.
Available options are the following:
Yes | Specifies that the drive is to be available for use. |
No | Specifies that the drive will not be online. |
This command can be issued when the drive is involved in an active process or session, but it is not recommended. This command allows drives to be taken offline and used for another activity, such as maintenance.
If you make the drive offline while it is in use, the drive will be marked offline. However, the mounted volume will complete its current process. If this volume was part of a series of volumes for a given transaction, the drive will no longer be available to complete mounting the series. If no other drives are available, the active process may fail.
The updated state will be retained even when the server is halted and brought up again. If a drive is marked offline when the server is brought up, a warning is issued noting that the drive must be manually brought online. If all the drives in a library are updated to be offline, processes that need a library mount point will fail, rather than queue up for one.
Enter the value for the cleaning frequency you would like to establish for the selected drive.
The following are possible values:
None | Specifies that the server does not track the need for device cleaning. Some libraries have their own automatic cleaning. |
Asneeded | Specifies that the server loads the drive with a checked-in cleaner cartridge only when a drive reports to the device driver that it needs cleaning. |
Gigabytes | Specifies a value in gigabytes, from 1 to 9999. This indicates how much data processing will occur before the server loads the drive with a cleaner cartridge. Drive cleaning will still take place when a drive indicates that cleaning is required. |
To add a volume to the server inventory for an automated library, complete the following fields and then click Finish, or click Cancel to end this task.
Select the name of the library. This field is required.
Enter the name of the volume being checked in. This field is required except when the Search Library field has a value of Yes.
Select the volume status. This field is required. The default is Private.
Private | Specifies that the volume is not part of the library's pool of scratch volumes. A private volume is mounted only when its volume name is requested by name. |
Scratch | Specifies that the volume is a scratch volume. This volume can be mounted to satisfy scratch mount requests during data storage operations or export operations. |
Cleaner | Specifies the volume is a cleaner cartridge and not a data cartridge. This option applies only to SCSI libraries. The Cleanings parameter is required. |
Select an option. This field is optional.
Yes | Specifies that during check-in an attempt is made to read the media label. Yes is not valid for cleaner cartridges. The default is Yes. |
No | Specifies that during check-in the media label is not read. Selecting this value can result in future errors that must be resolved through library audit processing. |
Barcode | Specifies that the barcode label is used during check-in. This option is valid for SCSI libraries only. |
Select whether the server performs a swap operation when an empty library slot is not available during check-in. This field is optional. The default is No.
Yes | Specifies that if an empty slot is not available, the server initiates a swap operation. The volume selected (target swap volume) for the swap operation is ejected from the library and replaced with the volume being checked in. |
No | Specifies that if an empty slot is not available, this request is rejected. |
Enter the maximum number of minutes that the server waits for a storage volume to be mounted. This field is optional.
Select whether the server searches the library to find volumes that have not been checked in. This field is optional. The default is No.
Yes | Specifies that the server should search the library for volumes to be checked in. |
No | Specifies that the server does not search the library for volumes to be checked in. A name must be specified in the Volume Name field. |
Bulk | Specifies that the server searches the library's Entry/Exit ports for volumes to be checked in. Bulk applies only to SCSI libraries. Do not specify both Check Label as No and Search as Bulk. |
Specify the device type for the volume being checked in. This parameter only applies to 349X libraries containing 3490 and 3590 devices. This field is optional.
Cartridge | Specifies that the volume being checked in is for a 3490 device type. The default is Cartridge. |
3590 | Specifies that the volume being checked in is for a 3590 device type. |
Enter the first and last volumes in a range of volume names. Separate the names by a comma with no intervening spaces. Use this parameter to limit the search when the Search Library parameter has a value of Yes. This parameter is optional.
bar110,bar130 | The range includes 21 volumes: bar110, bar111, ...bar130 |
bar11a,bar13a | The range includes 3 volumes: bar11a, bar12a, bar13a |
123400,123410 | The range includes 11 volumes: 123400, 123401, ...123410 |
bar100,bar100 | The range includes 1 volume: bar100 |
Enter the list of volumes to be processed for the command. The volume list is designed to filter only the volumes to be checked in or labeled, and it requires that Check Label is set to Barcode. This parameter is optional.
Choose one of the following options:
Enter the recommended value for the individual cleaner cartridge (usually indicated on the cartridge). Cleanings applies only to SCSI libraries. This parameter is required if Status is set to Cleaner.
To remove a volume from an automated library, first complete the following fields and then click Finish, or click Cancel to end this task.
Select how or whether the server should read sequential media labels of volumes. This parameter is optional and does not apply to 349X libraries. The default is Yes.
Yes | Specifies that during checkout an attempt is made to read the media label. Reading the media label verifies that the correct volume is being checked out. |
No | Specifies that during checkout the media label is not read. This increases performance since the read process does not occur. |
Select an option. This parameter is optional and does not apply to 349X libraries. The default is No.
Yes | Specifies that the server checks out the volume even when an I/O error occurs while reading the label. |
No | Specifies that the server does not check out a volume when an I/O error occurs while reading the label. |
Select whether the server ejects a volume during command processing from a library. The default is Yes.
Yes | Specifies that a volume is ejected during command processing. The volume entry is deleted from the the server library inventory. |
No | Specifies that a volume is not ejected during command processing. |
Bulk | Specifies that the volume is ejected to a predefined high capacity area, instead of an I/O station, in the library. This parameter only applies to libraries with a defined bulk eject area. |
Enter the first and last volumes in a range of volume names. Separate the names by a comma with no intervening spaces. This parameter is optional.
bar110,bar130 | The range includes 21 volumes: bar110, bar111, ...bar130 |
bar11a,bar13a | The range includes 3 volumes: bar11a, bar12a, bar13a |
123400,123410 | The range includes 11 volumes: 123400, 123401, ...123410 |
bar100,bar100 | The range includes 1 volume: bar100 |