A Tag for ASCII_EBCDIC Conversion
You would want to use TAG support if you have file systems that do not support storing file tags,
such as an NFS remote file system. It is also useful for any file systems that don't have
tags, for other reasons; for example, an HFS of old ASCII files that pre-date ASCII tagging
support. It also could be used by a process that doesn't tag new files, one that may be
storing ASCII files in your HFSes but isn't setting their tags.
The default is to have the box unchecked, meaning that the system does not provide a tag for
ASCII-EBCDIC data conversion for untagged files. Only those files that are individually tagged will be converted.
If you check the box indicating that you want the system to provide a tag for ASCII-EBCDIC
data conversion, you have two additional questions to answer:
- For the files that are not individually tagged, what coded character set identifier (CCSID)
do you want the system to use for that file? Select 1047 (for EBCDIC) or 819 (ASCII).
The default is 1047.
- Are the files that are not individually tagged pure text? In other words, are they
free from non-text characters, such as binaries or executables?
- If so, check "Yes". The warning on the page applies to the case where you check "Yes".
It warns that if you have untagged binary or executables in your file system, they also
might be automatically converted, sometimes causing corruption of data.
The wizard uses the keyword TEXT as default, meaning that the "Yes" box is checked.
- If not, check "No" meaning none of the untagged files in the file system are
automatically converted during reading and writing.