(C) Copyright IBM Corp. 1997 CS/2 to CS/NT Migration Utility - README.TXT ------------------------------------------------------- This README.TXT file contains instructions on how to use both the command line and graphical versions of the migration utility. This file is divided into the following categories: - Before you begin - Command line version - Graphical version - Limitations - Known problems Before you begin migration ------------------------------------------------------------------ 1) If the files you are migrating contain an SDLC or X25 DLC, make sure that the corresponding PROTOCOL.INI file is included in the same directory as the .RSP file. Use the same file name as the .RSP; for example, MIGRATE.RSP and MIGRATE.INI. If no file of the same name is found, the migration utility defaults to PROTOCOL.INI. This file is usually located in the C:\IBMCOM directory. You should change the name only when you want to migrate multiple files. 2) The graphical version of the migration utility is JAVA based. In order to use the graphical version, a copy of the Java Virtual Machine (JVM) must be installed on your machine and all paths and classpaths must be configured correctly. 3) Create a backup of your response (.RSP) files. Command line version ------------------------------------------------------------------ 1) The command line version enables you to migrate a single CS/2 response file to a CS/NT configuration file or to migrate all the response files in a given directory to CS/NT configuration files. The output from the migration is the same, but the command line parameters and placement of the output files are different. 2) To migrate a single file, type the following command at a DOS command prompt: oocmigcm [dest.acg] where: source.rsp - Specifies the name of the response file to migrate dest.acg - Specifies the name of the output file to create. You can use a fully-qualified name to put the new file in another directory. If you do not specify a name, the output is placed in MIGRATE.ACG. If you do not specify a directory, the output .ACG file is placed in the same directory as the source .RSP file. Log files (.LOG) are placed in the directory from which you ran the utility. 3) To migrate all the response files in a directory, type the following command at a DOS command prompt: oocmigcm <-d> where: -d - Specifies that you want to migrate a directory. dirname - Specifies the name of the directory to migrate. All .RSP files in the given directory will be migrated. Other files in the directory will be ignored. Output .ACG files have the same name as their corresponding source .RSP files; for example, MIGRATE.RSP will be migrated to MIGRATE.RSP. Output .ACG files are placed in the specified directory and .LOG files are placed in the directory from which you ran the utility. Graphical version ------------------------------------------------------------------ 1) The graphical interface is a TaskGuide (wizard) that enables you to migrate single files or entire directories. Click the Assistance button on any panel for detailed online help. 2) Before you can use the graphical interface, run the SETUP.BAT file by changing to the directory where the file is located and typing SETUP. This will add several lines to your CLASSPATH. These lines will be removed when the DOS window from which you are operating is closed. After running SETUP, type MIGRATE at a DOS command prompt to begin the program. 3) You have a choice of two modes in which to run the utility: Interactive and Batch. Interactive enables you to specify individual input and output file names for migration. Batch mode enables you to specify a directory of files for migration. To specify more than one file or directory name in either mode, click Enter Files on the File Entry panel and click Next. This returns you to the Enter Files panel, where you can specify another file or directory to migrate. 4) In Interactive mode, each file is verified when you enter it. If the given file is not a valid response file, you will receive an error message. If you do not specify an output file name, the input filename is used; for example, MIGRATE.RSP will be migrated as MIGRATE.ACG. The output file is placed in the same directory as the input file unless you specify another directory name. LOG files (.LOG) are placed in the directory from which you ran the utility. 5) In Batch mode, only the directory is verified before proceeding with migration. If a file fails to migrate, the file name is noted in the log, but is otherwise ignored, and migration of the remaining files continues. You will be notified when the migration is completed. If any files failed to migrate, you will be instructed to check the log file. Limitations ------------------------------------------------------------------ 1) No password security fields are migrated. Known problems ------------------------------------------------------------------ 1) When the graphical interface is being loaded, the message - Warning: unknown JFIF revision number 2.01 - appears. Ignore this message. 2) In some instances, after migration is completed, a Java error will be registered and several error messages will be printed to the screen. These errors do not affect the operation of the migration utility and can be ignored. 3) Error: Can't find class SmartGuide. If the above error occurs, make sure you have run SETUP.BAT. If you still get this error, you should download and install the standard Java Development Kit from Sun.