(C) Copyright IBM Corp. 1998 IBM eNetwork Communications Server for Windows NT Migration Utilities - README.TXT --------------------------------------------------------- This README.TXT file contains instructions on how to use both the Microsoft SNA Server to IBM eNetwork Communications Server for Windows NT Migration Utility and the IBM CS/2 or CM/2 to IBM Communications Server for Windows NT Migration Utility. Both utilities have command line and graphical versions. Once unpacked, the Microsoft SNA Server to Communications Server for Windows NT Migration Utility is placed in the \sna_server subdirectory of the user's specified base migration directory (default is c:\migrate). The IBM CS/2 or CM/2 to Communications Server for Windows NT Migration utility is placed in the \cs2_migrate subdirectory. This file is divided into the following categories: - Before you begin - Command line version - Graphical version - Limitations - Known problems - Trademarks Before you begin migration ------------------------------------------------------------------ o The graphical version of the migration utility is Java-based. To use the graphical version, you must have a copy of the Java Virtual Machine (JVM) installed on your machine. All paths and classpaths must be configured correctly. o Create a backup of your configuration files. Microsoft SNA Server to Communications Server for Windows NT ---------------------------------------------------------------- o Create an .SNA configuration file. In SNA Server choose File->Backup Configuration and enter a file name to save the configuration. SNA Server does not back up its configuration files in a readable text format. To migrate SNA Server configurations, you must create a text version of the configuration file. To create this text file, type the following command at a DOS command prompt in your SNA Server directory: snacfg #filename.sna /PRINT > filename.cfg where filename is the name of the file that you want to migrate. CS/2 or CM/2 to Communications Server for Windows NT ------------------------------------------------------------ o If the files you are migrating contain an SDLC or X.25 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. Command line version ------------------------------------------------------------------ o The command line version enables you to migrate a single configuration file to a Communications Server for Windows NT configuration file or to migrate all the configuration files in a given directory to Communications Server for Windows NT configuration files. The output from the migration is the same, but the command line parameters and placement of the output files are different. Microsoft SNA Server to IBM Communications Server for Windows NT ---------------------------------------------------------------- o To migrate a single file, type the following command at a DOS command prompt: oocmig [dest.acg] where: source.cfg - Specifies the name of the configuraton 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 .CFG file. Log files (.LOG) are placed in the directory from which you ran the utility. o To migrate all the configuration 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 .CFG 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 .ACG files; for example, MIGRATE.CFG will be migrated to MIGRATE.ACG. Output .ACG files are placed in the specified directory and .LOG files are placed in the directory from which you ran the utility. CS/2 or CM/2 to Communications Server for Windows NT ------------------------------------------------------------ o 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. o 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 ------------------------------------------------------------------ o The graphical version is a wizard that enables you to migrate single files. Click the Assistance button on any panel for detailed online help. o Before you can use the graphical version, you must 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 you close the DOS window from which you are operating is closed. After running SETUP, type MIGRATE at a DOS command prompt to begin the program. Microsoft SNA Server to Communications Server for Windows NT ---------------------------------------------------------------- o The graphical interface will prompt you for a single file to migrate and the destination file name. If you do not specify an output file name, the input filename is used; for example, MIGRATE.CFG 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. IBM CS/2 or CM/2 to Communications Server for Windows NT ------------------------------------------------------------ o The graphical interface will prompt you for a single file to migrate and the destination file name. 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. Limitations ------------------------------------------------------------------ o No password security fields are migrated. Microsoft SNA Server to Communications Server for Windows NT ---------------------------------------------------------------- o Due to differences in implementation, Microsoft SNA Server and Communications Server have different restrictions on certain values. Therefore, not everything in a valid Microsoft SNA Server configuration can migrate to Communications Server automatically; you may need to correct some values manually. For example: - SNA Server allows different Link Stations to have identical destination addresses, while Communications Server does not. - SNA Server and Communications Server have different definitions of valid pool names. A pool name of 3270POOL is valid in SNA Server, but not in Communications Server. Problems like these are listed in the migration log file. o SNA Server does not include TN3270 filter information in its configuration file, so those settings can not be migrated automatically. Known problems ------------------------------------------------------------------ o When the graphical interface is being loaded, the message - Warning: unknown JFIF revision number 2.01 - appears. Ignore this message. o 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. o 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 Microsystems. Trademarks ---------------------------------------------------------------- Java is a trademark of Sun Microsystems, Inc. Microsoft, Windows, and Windows NT(R) are registered trademarks of Microsoft Corporation.