Path Names

Syntax for Renaming Files In "PUT" and "GET" Commands

The syntax for renaming files in "PUT" or "GET" commands is always:

         local_file : HPSS_file

Whitespace is required before and after the colon ":" character.

Multiple such pairs of pathnames may be freely intermixed with other files that are not being renamed, for example:

         put f1 : file1 file2 f3 : file3 f4 f5 f6

This would result in storing HPSS files file1,flle2, file3 f4 f5 and f6.


     get f1.bak : file1 file2.bak : file2 f3 : file3 f4 f5.bak : f5 f6

would result in retrieving local files f1.bak, file2.bak, f3, f4, f5.bak and f6

PUT and GET Commands With Just One Pathname

When the "local : hpss" rename syntax is not used to specify both a local path and an HPSS path, on a get or put command, such as this one:

put /glade/user/someuser/nidas/2012/2012.tar.gz

HSI assumes that the path that's given is the HPSS pathname, and it uses

the last component, in this case, "200201.tar.gz" as the local pathname,

which would be equivalent to:

put 200201.tar.gz : /glade/user/mizukami/nidas/2002/2002.tar.gz

Using Un*x PIPES 

See "Using Un*x PIPEs for Input/Output" for using PIPEs to read from or write to HPSS files.

See "FTP Compatibilities/Differences" for other differences between FTP and HSI


See "Using PIPED Input or Output" for information on using Un*x pipe commands for storing or retrieving HPSS files.

Valid characters for a path parameter are:

	ASCII characters >= 0x20 (space) and <= 0x7E (tilde)

However, HSI uses the space character as a separator, so its use is discouraged - generally, pathnames containing spaces must be quoted.  Also note that HPSS, but not HSI, supports an optional configuration setting that allows pathnames to contain non-printable characters. This option is normally disabled, so that HPSS also restricts pathnames to printable ASCII characters (0x20 - 0x7E).

Wildcard characters are

	* ? ^ [] {}

They may be used in all commands that reference either local or HPSS paths, including the "local : HPSS" form. Note that names containing wildcard characters must resolve to a single node for some commands, such as SET DIR n=pathname, or MV path path... npath, in which npath must resolve to a single directory node.

See "Tips and Tricks" for information on working with filenames that contain whitespace and wildcard characters.

UNIX-style pathname prefixes

The standard Unix pathname prefix characters 
	~ . ..

are also allowed on all file name/HPSS-path name references.