.get

.get server:[[<relative_path>/]file/]file [[[<relative_path>/]file/]file]

Use the .get command to transfer a file from one logical server to another. The .get operation runs from the current server path and retrieves the file from the specified server path. The destination path name is relative to the step's current working directory. The source path name is relative to the specified server base path. The server must specify a logical server that allows the .get operation for files. For information, see Enabling file copying on a server resource. Only single files can be transferred.

The path specification can include environment variables. This capability allows you to specify files relative to the path used by a specific job. See the description of paths used by jobs in Working directories for jobs.

If the server name you are using has spaces in it, put the server name and the path to the file in quotes. For example: .get [<relative_path>/]"file server:[[<relative_path>/]file]"

Note: Be sure that the path you use exists before doing the file transfer.

The transfer is not fast, so you might want to choose a different method to transfer large files. Expect speeds of no more than 40 KB per second; a 70 MB file can take 45 minutes to an hour to transfer.

Note: If the destination file already exists, it is overwritten without warning.
Because the Windows file path separator, the backslash (\), is the same as the escape character used in Rational® Build Forge®, when parsing dotcommands, it is difficult to determine when the command means "escape." Use the following characters to distinguish between a Windows file path separator and escape: This example shows the .put command:

.put[/E|/e] [<relative_path>/]file server:[[<relative_path>/]file]

If neither /E nor /e is specified, the system uses the heuristics method to see if the dotcommand contains something that looks like a Windows file path. If it detects a file path, escape is disabled; otherwise, escape is enabled.


Feedback