Example for Unix systems
openFT V12.1 is installed on the computer uxpartn. Using -sif=l you want to check whether there are files with non-mappable file names in the task directory.
ftshw -d uxpartn!task transunx -fnc=t -sif=l dr-pxeacd--- user1 Okt 21 17:10 dtransfer dr-pxeacd--- user1 Feb 16 2016 pcmx32 dr-pxeacd--- user1 Feb 16 2016 pcmx_64 dr-pxeacd--- user1 Feb 10 2016 unicode dr-pxeacd--- user1 Jul 25 12:50 utf16
Example for Windows systems
openFT V12.1 is installed on the computer mt001. Using -sif=l you want to check whether there are files with non-mappable file names in the Test directory.
|
The last line means that there are files with a non-mappable file name which are therefore not output. Instead of attributes, this line contains a string with the following format:
|*IMPROPER FILE NAMES (x): nnn
This string is also output on stderr with -sif=m.
Explanation:
nnn
is the number of suppressed file names (2 in this example).
(x)
refers to the position that suppresses the file names, possible values:
D
the file access routines in the responder (as in the example). These include file names in Windows, which cannot be presented in the locally set ANSI character set for calls in transparent mode, as well as symbolic links on Unix systems, which refer to a file that does not exist.
R
the encoding of the file names in the responder. These include for example file names on Unix systems for calls in character mode, which do not have a valid UTF-8 byte sequence if UTF-8 is set as the character code for file names
I
the decoding of file names in the initiator. These include for example file names for calls from a Unix initiator in character mode, which cannot be mapped to the appropriate character set of the Locale or LANG variables
Up to three of these list entries and messages can be output - one for each of the above "categories".