You use autoDataSpec to define the transfer mode for the file in which the element was specified.
If the file's data type is unknown then it is determined on the basis of the file name using pattern recognition.
The only pattern currently permitted is *.xxx since only the file name suffix is checked. The file name specified for the actual transfer is used.
The file types are described in the openFT manual "Concepts and Functions".
Data type | Format | Example |
| Text format | *.xml |
| Binary format | *.doc in a Windows system |
| User format |
autoDataSpec describes which pattern is assigned to which data type.
If multiple patterns for different file formats match a file name then the file type is determined in the sequence bin, char, user.
If an explicit data type is specified for the file after de-referencing then autoDataSpec is not evaluated.
Restrictions
The only useful pattern is *.xxx where xxx may be of any length. However, the overall length of 512 characters for the entire expression may not be exceeded.
Only the file name suffix is checked.
Format
|
Attributes
Name | Value | Meaning |
| string | Reference to an autoDataSpec context object. |
| patternlist1 | Wildcard pattern. |
| patternlist1 | Wildcard pattern. |
| patternlist1 | Wildcard pattern. |
| | The default value is char. |
Example
|
|
In the example, the file list FileList of local files is transferred to all the computers in the HostList. The file transfer modes are activated in accordance with the autoDataSpec specification. *.txt files are converted in accordance with the target system type. All unknown file types are transferred in binary form. *.tab and *.dat are defined for user transfers.