Notes on migrating management information between Windows and UNIX
DataMagic allows you to transfer the management information set in the Windows version to the equivalent in the UNIX/Linux version. Likewise, you can transfer the management information set in the UNIX/Linux version to the equivalent in the Windows version.
Note, however, that due to the difference between the environments, restrictions of each OS, etc., you might not be able to use the management information as it is. The following are some points to note:
(1) Path name
The path names of the following files and directories must be replaced before transferring the management information.
- Data processing information
-
Input file, matching file, merge file, user exit program, output file, storage path of the external character conversion table, storage path of the EBCDIC user table, virtual table file, and error file
- Excel information
-
Management Excel file, template file name
- Database connection information
-
Database name (when Product type is SQLite3)
The path name of the data processing information can be replaced in a batch. To replace the path name in a batch, open the Replace screen by clicking the Replace button in the Data Processing Settings screen, and then specify the replacing path name.
To change the path name set in the Excel information or the database connection information, use the settings screen for each type of information.
(2) Output location (use of field values)
Halfwidth spaces and 2-byte characters can be used in the file name in the Windows version, but not in the UNIX/Linux version. As a result, in the specification of the output file name, if a halfwidth space or 2-byte character is included as part of input field or fixed character string, the conversion terminates abnormally in the UNIX/Linux version.
When transferring data from the Windows version to the UNIX/Linux version, be sure to review and modify the settings by, for example, changing to a file name that does not contain a halfwidth space or 2-byte character.
(3) Migration between operating systems with different encodings on local devices
If any double-byte code is used for settings on management information such as data processing information, and the local device on the migration destination uses a character encoding that cannot be converted, conversion to the default code occurs. (Note that the default code is a white-box symbol .)