Name conversion considerations

Here are several things to consider during the automatic name conversion process.

Conversion status determination
General messages indicating which file systems have been converted and various progress messages are sent to the job log of the job performing the conversion.
Objects renamed
In a file system that is not case sensitive, the system does not distinguish between uppercase and lowercase characters during searches for names. Any change in the casing rules will affect the characters that are considered the same when not distinguishing between uppercase and lowercase.
User profile considerations
While the conversion is running, the system needs additional storage, which impacts the amount of storage owned by the user profile.
Tips: Symbolic link
Symbolic links are objects within the integrated file system that contain path names pointing to other objects. If one of the elements of the path name within a symbolic link is renamed during the conversion, the contents of the symbolic link no longer point to the other object.
Tips: Independent ASP
If the user-defined file systems in an independent ASP have not yet been converted to use the Unicode Standard version for the current release, a job is started to do that conversion when the independent ASP is varied on.
Tips: Saving and restoring
Directories that are using Unicode Standard 2.0 can be saved and restored to a file system that is using the Unicode Standard 4.0, and vice versa.
Tips: Reclaiming integrated file system objects
If there are any errors during the automatic name conversion, the Reclaim Storage (RCLSTG) and Reclaim Object Links (RCLLNK) commands can complete the conversion of the directory and its subdirectories. This only happens after the automatic name conversion processing has completed for the file system.

Parent topic: Converting names to support additional characters