Administrator's Reference

RENAME FILESPACE (Rename a Client File Space on the Server)

Use this command to rename an existing client file space on the server to a new file space name or to rename imported file spaces.

You may want to rename a file space that has been imported or to cause the creation of new Unicode-enabled file spaces for Unicode-enabled clients.

Privilege Class

Any administrator with unrestricted policy authority or with restricted policy authority over the client's policy domain can issue this command.

Syntax

>>-REName FIlespace--node_name---------------------------------->
 
>--current_file_space_name--new_file_space_name----------------->
 
   .-NAMEType--=--SERVER------.
>--+--------------------------+--------------------------------->
   '-NAMEType--=--+-SERVER--+-'
                  +-UNIcode-+
                  '-FSID----'
 
   .-NEWNAMEType--=--SERVER-----------.
>--+----------------------------------+------------------------><
   |                           (1)    |
   '-NEWNAMEType--=--+-UNIcode------+-'
                     '-HEXadecimal--'
 
 

Notes:

1. This parameter is the default when you specify NAMEType=UNIcode.

Parameters

node_name (Required)

Specifies the name of the client node to which the file space to be renamed belongs.

current_file_space_name (Required)

Specifies the name of the file space to be renamed. A file space name is case-sensitive and must be specified exactly as defined to the server.

new_file_space_name (Required)

Specifies the new name for the file space. A client file space name is case-sensitive and must be specified exactly as it is to be defined to the server.

Note:

If the new name type is hexadecimal, be careful to specify valid UTF-8 hexadecimal values so the server's code page displays the file space name as intended. For example, do not specify a value that can be interpreted as a backspace.

NAMEType

Specify how you want the server to interpret the current file space name that you enter. This parameter is useful when the server has clients with support for Unicode. A backup-archive client with support for Unicode is currently available only for Windows NT, Windows 2000, Windows 2002, Windows .NET, and Windows XP operating systems.

The default value is SERVER. Possible values are:

SERVER

The server uses the server's code page to interpret the file space name.

UNIcode

The server converts the file space name entered from the server code page to the UTF-8 code page. The success of the conversion depends on the actual characters in the name and the server's code page. Conversion can fail if the string includes characters that are not available in the server code page, or if the server has a problem accessing system conversion routines.

FSID

The server interprets the file space name as the file space ID (FSID).

NEWNAMEType

Specify how you want the server to interpret the new file space name that you enter. The default is SERVER if you specified the NAMETYPE as SERVER, or if the file space to be renamed is not Unicode. The default is UNICODE if you specified the NAMETYPE as UNICODE, or if the file space to be renamed is Unicode. Possible values are:

SERVER

The server uses the server's code page to interpret the file space name.

UNIcode

The server converts the file space name entered from the server code page to the UTF-8 code page. The success of the conversion depends on the actual characters in the name and the server's code page. If the conversion is not successful, you may want to specify the HEXADECIMAL parameter.

HEXadecimal

The server interprets the file space name that you enter as the hexadecimal representation of a name in Unicode. Using hexadecimal ensures that the server is able to correctly rename the file space, regardless of the server's code page.

To view the hexadecimal representation of a file space name, you can use the QUERY FILESPACE command with FORMAT=DETAILED.

Note:

You cannot specify a new name of a type that is different from the original name. You can rename a file space that is Unicode to another name in Unicode. You can rename a file space that is not Unicode using a new name in the server's code page. You cannot mix the two types.

Examples

Task

An AIX client node named LARRY backed up file space /r033 to the TSM server. The file space was exported to tape and later reimported to the server. When this file space was imported, a system-generated name, /r031, was created for it because /r033 already existed for client node LARRY.

Client node LARRY, however, already had a file space named /r031 that was not backed up, therefore, was unknown to the server. Unless the imported file space is renamed, it will overlay file space /r031 because the file space name generated by the IMPORT function is the same as a file space on client node LARRY that is unknown to the server.

Use the following command to rename imported file space /r031:

Command:

rename filespace larry /r031 /imported-r033

The new name, /imported-r033, identifies that the new file space is an imported image of file space /r033.

Task

Client JOE is using an English Unicode-enabled TSM client. JOE has backed up several large file spaces that are not Unicode enabled in server storage. File space \\joe\c$ contains some files with Japanese file names that cannot be backed up to a file space that is not Unicode enabled. Because the file spaces are large, the administrator does not want to convert all of JOE's file spaces to Unicode-enabled file spaces at this time. The administrator wants to only rename the non-Unicode file space, \\joe\c$, so that the next backup of the file space causes the creation of a new Unicode-enabled file space. The new Unicode-enabled file space will allow the Japanese files to be successfully backed up. Use the following command to rename \\joe\c$:

Command:

rename filespace joe \\joe\c$ \\joe\c$_old

Related Commands

Table 230. Commands Related to RENAME FILESPACE