FTPGETFILE - Get properties of remote file(s)

Syntax:	FTPGETFILE	[ file name ] [ /options ]
Arguments:	[ file name ]	Variable or string defining a file name to look for; wildcard characters are allowed.
Options:	/ignorecase	Test for file name matches after forcing the local and site files to be lower case effectively making the match case-insensitive.
	/incldirs	Search sub-folders for files matching the [ file name ] argument.
	/newest	Return the one absolute newest file in the directory tree.
	/oldest	Return the one absolute oldest file in the directory tree.
	/skip_changing	Ignore any file if file size is not stable for one second.
	/skip_changing_seconds=nn	Ignore any file if the size is not stable for the specified number of seconds. Values between 1 and 60 are allowed.
	/timeout=nn	Time-out in seconds to wait for presence of the file, if the timeout elapses before the file is found $ERROR_WAIT_TIMED_OUT is returned. If this option is omitted Robo-FTP looks for the file and immediately returns $ERROR_NO_FILE_FOUND if no match is found.

If you need to download a file please see the Help page for the RCVFILE script command.

Robo-FTP offers numerous commands for monitoring for files and iterating over directory structures on local and remote servers. There is significant overlap in capabilities between these commands, but there are also important differences that often make one command better suited to a particular task than the others. Please see the chapter Monitoring for Files and Iterating over Directory Structures for a description of these commands and recommendations for which commands to use in a particular situation.

This script command searches the current remote directory for the file specified in the [ file name ] argument. If a matching file is found, a set of internal variables is populated which may then be used for various tasks like checking the status of a specific file, processing a group of files with names matching a wildcard pattern or executing a set of commands only when certain conditions exists. For example, a script might use the date and size variables to choose which files in a folder should be transferred, deleted or ignored.

When a match is found, the file name is saved in the %sitefile variable; the %sitepath variable contains the full remote path and filename, %sitefolder and %sitedir both contain the path as returned by the remote server (without the filename); the date and time of the file are saved in the %sitefiledate, %sitefiledatetime, and %sitefiletime variables; and the size of the file, in bytes, is saved in the %sitefilesize variable.

The /skip_changing and /skip_changing_seconds options are useful when there is a chance that a file being processed by Robo-FTP is also being modified by some other process.

This command returns $ERROR_NO_FILE_FOUND when no file matches the [ file name ] argument. The /timeout option can be used to wait for the existence of an expected file. This is accomplished by periodically polling the remote folder during the waiting period. If the file does not appear before the timeout expires $ERROR_WAIT_TIMED_OUT is returned.

Use the FTPCD command to change the current directory before calling FTPGETFILE if the file you want to find is not in the current directory or, alternatively, the /incldirs option may be use to find files in any subdirectory of the current directory.

This command is functionally equivalent to the GETSITEFILE script command except for two important differences. The first difference between FTPGETFILE and GETSITEFILE is their behavior when called repetitively with a wildcard character in the [ file name ] argument. In this situation, each subsequent call to FTPGETFILE automatically returns the next file in the list of all files matching the wildcard pattern. If there are three files matching the pattern, the first three calls to FTPGETFILE each return a different set of internal variable values and the fourth call results in a "No File Found" error.

The FTPGETREWIND command may be used to start over at the top of the list. In contrast, when GETSITEFILE is called repetitively with a wildcard character in the [file name] argument it returns the same set of values every time unless the /next option is specified.

Suppose Robo-FTP is connected to a remote site with a file named "ReadMe.txt" in the current directory. In the following example, the first line will successfully populate %sitefile and the other internal variables but the second line will cause a "No File Found" error.

The second line returns an error because subsequent calls to FTPGETFILE always return the next matching file in the list of files matching the [ file name ] argument. Since there can never be two files in the same folder with the same name, there can never be a next "ReadMe.txt" file. Because of this quirk it is safer to use GETSITEFILE if you only need to check the existence, timestamp, or size of a single file with a known filename.

Do not use the FTPGETFILE command to construct a loop that moves or deletes files; such loops may be built using GETSITEFILE without the /next option. Use the FTPDIFF command instead of either FTPGETFILE or GETSITEFILE if your project requirements include processing dynamic folders where files may be added, renamed, moved or deleted during processing.

Use of the /newest or /oldest options negates the auto-incrementing next behavior of the FTPGETFILE command. When either of these options is used, Robo-FTP always returns the newest or oldest file respectively. This behavior requires checking the date of every file in the folder so combining either option with the /skip_changing or /skip_changing_seconds option will result in longer script execution times.

The FTPGETREWIND command may be used to start over at the top of the list of files that match the wildcard pattern.

The second difference between FTPGETFILE and GETSITEFILE involves the /incldirs option. If FTPGETFILE is used with the /incldirs option it searches the current remote directory and any subdirectories. If a file matching the [ file name ] argument is found then %sitefile, %sitefolder and all the other internal variable values are populated as discussed above. If GETSITEFILE is used with the /incldirs option it searches only the current remote directory. If a matching file name is found then the %sitefile variable is populated and the %sitefolder variable is empty; but if a sub-folder name matches the [ file name ] argument then the %sitefolder variable is populated and the %sitefile variable is empty.

To understand this second difference, suppose Robo-FTP is connected to a remote site and the root directory contains a file named one.txt and a sub-folder named /sub and further suppose that sub-folder contains a file named two.txt and its own sub-folder named /deep which contains a file named three.txt as follows:

The chart below shows the results of calling FTPGETFILE in the root folder with various arguments and options. (Assuming FTPGETREWIND is executed between calls to FTPGETFILE.)

Command syntax	Error	%sitefile	%sitefolder
FTPGETFILE "one.txt"	No	one.txt	/
FTPGETFILE "sub" /incldirs	Yes	empty	empty
FTPGETFILE "two.txt" /incldirs	No	two.txt	/sub/
FTPGETFILE "deep" /incldirs	Yes	empty	empty
FTPGETFILE "three.txt" /incldirs	No	three.txt	/sub/deep/

Command syntax	Error	%sitefile	%sitefolder
GETSITEFILE "one.txt"	No	one.txt	empty
GETSITEFILE "sub" /incldirs	No	empty	sub
GETSITEFILE "two.txt" /incldirs	Yes	empty	empty
GETSITEFILE "deep" /incldirs	Yes	empty	empty
GETSITEFILE "three.txt" /incldirs	Yes	empty	empty

Note: The platform of the remote server controls which path-separator character appears in the %sitefolder internal variable.

Consider the following example where FTPGETFILE uses the "*" wildcard to match all the files in the current remote directory and then download each of them.

The date and time of files found with FTPGETFILE are saved to three internal variables named %sitefiledate, %sitefiledatetime, and %sitefiletime. Consider the following example that cycles through all files on the remote site until it finds one created after a specified date.

MESSAGEBOX "Found a file named " & %sitefile & " created on or after July 31, 2010!"

The following example causes Robo-FTP to wait indefinitely, polling the remote site periodically until the network connection is disrupted or a file with a name matching *.rdy is found. Script execution resumes on the next line when either of these events occurs.

The success of this command depends on Robo-FTP's ability to automatically read and understand the directory listings returned by the remote site. Most HTTP/HTTPS sites do not return listings in a supported format and many return no raw directory listings in response to HTTP GET requests based on slash-terminated URLs. Some servers respond to HEAD requests and are partially compatible. Some supported HTTP listing types like APACHE_DEFAULT include file sizes rounded to the nearest megabyte or kilobyte and are therefore not fully compatible with this command. Contact technical support if you have an urgent need related to a directory listing format that is currently unsupported.

This command returns $ERROR_NO_FILE_FOUND when no file matches the [ file name ] argument. This is not the same error as $ERROR_NO_FILES_FOUND. Please be sure to test for the correct error code.