...
The default behavior of JADE is to throw an error if a file transfer is attempted and no files are found. . The DisableErrorOnNoFilesFound element is used to allow JADE to attempt a file transfer without an error being generated of if no files are found. This behavior can be useful when, for example, when polling for files.
The DisableErrorOnNoFilesFound element is specified as a Directives child element, and is specified as shown in the next screenshot shows how this element is integrated in a configuration:
The effect of setting the DisableErrorOnNoFilesFound element can be demonstrated if, for example, the FileSpec regular expression in the Profile element to, for example ^text\.txt$ and recalling the operation.
...
If, however, the DisableErrorOnNoFilesFound element is set to true, JADE will not throw an error.
Note:
- The meaning of the values true and false for the DisableErrorOnNoFilesFound element are the opposite to the meaning for the element's
settings.inifile predecessor, force_files.
Zero-Byte Files
The JADE Client can handle files with zero bytes in a number of ways, depending on the setting used for the TransferZeroByteFiles parameter, which is also specified as a child of the Directives element.
Test Example
...
The default TransferZeroByteFiles setting is true. The screenshot below shows how this element is integrated in a duplicate of the ftp_server_2_local file transfer profile described in the first tutorial in this series.
In its original configuration, the ftp_server_2_local profile transfers six files from the SOS test server to the local file system. One of these files - ./test_4.txt - has zero bytes and can be used to demonstrate the use of the TransferZeroByteFiles parameter.
The screenshot also shows the relevant extract from the parameter reference for the TransferZeroByteFiles and element with a description of the meaning of the different values it the TransferZeroByteFiles element can have.
This profile is called on Windows systems using the following command:
...