Welcome to uniBasic (tm) Iris Migration Toolkit (IMT) ----------------------------------------------------- uniBasic-IMT Release 2.1 All Rights Reserved. Copyright (c) 1995 by: Dynamic Concepts, Inc. Aliso Viejo, CA 92656 USA Table of Contents ----------------- 1. Introduction 2. Changes for IMT 2.1 1. Introduction --------------- The manual you received with IMT is current through IMT version 1.4. This file contains new information for uniBasic-IMT that was not included in the manual. You should read this before loading or running IMT. If you have any questions and/or comments, please contact DCI at 714-448-8600 or 1-800-UB-BASIC. 2. Changes for IMT 2.1 ---------------------- New option to specify Tape Block size in bytes: 1. A new menu option has been added to "IMT Initialize" to specify tape block size in decimal bytes. By default, IMT requests a maximum of 64K (65536 bytes) from the tape driver. The driver in turn returns a tape record no larger than the requested tape block size. It is possible that the tape driver will actually return a smaller tape record. ***** CAUTION CAUTION CAUTION ***** DATA LOSS will occur if you specify a tape block size that is too small. Your Unix tape driver must be able to handle specified tape block size. Motorola SVR4 tape drivers cannot handle a tape block size larger than 65536 bytes. New IMT Initialize menu screen: 1. Option #3 has been changed from "Tape utility used" to "Tape Block size in bytes". 2. Options 3 - 10 have been renumbered to options 4 - 11 respectively. More Robust DMAP verification: 1. Improved algorithm has been added to compute source disk's tracks per cylinder and sectors per track (NPTC value as found in IRIS R8 and R9 Peripherals Manual). 2. Improved algorithm has been added to verify DMAP integrity. ***** CAUTION CAUTION CAUTION ***** 3. In the event that IMT detects a corrupted DMAP, it is important to do a full INSTALL (not Install Fast) on a proper IRIS system. Failure to do a normal INSTALL in such an event may cause improper conversions, such as missing records. 4. Specifying phantom LUs may lead to partial coping of a prior LU. 5. IMT SCAN a tape option (option # 2 from IMT main menu) should be run for proper conversions. uniBasic Release Number: 1. set MAXPORT environment variable to 511 or less to run this version of IMT with uniBasic prior to 5.2.8.2. Failure to set MAXPORT with uniBasic 5.2.8.2 or earlier versions will result in a security failure. 3. Changes for IMT 1.5 and greater ---------------------------------- Polyfiles and environment variable PFCHAR: 1. uniBasic 5.3 includes a new environment variable, PFCHAR, specifying a character to use for replacing the '@' in polyfile filenames. uniBasic IMT uses this feature now. (IMT must manually replace the '@' character since it uses absolute paths and uniBasic does not alter absolute paths.) 2. If you specify PFCHAR in an earlier version of uniBasic, IMT will still replace the '@' with the value of PFCHAR. However, you must either change the converted filenames to remove the replacement character or change your programs since the '@' will still terminate a filename on BUILD, OPEN, etc. This does not need to be done with uniBasic 5.3 and later. 3. The reason for this enhancement is to help in processing files with the same filename except for the '@', such as ABC and ABC@. Under current versions of IMT (and uniBasic), these are treated the same (the '@' is discarded) so they appear to be the same file to uniBasic. This results in some polyfiles not converting since ABC sorts before ABC@. 4. These problems only happen on logical units where volume 0 of ABC@ exists along with ABC. If your systems do not have this arrangement of files, you do not need to set PFCHAR. 5. If you decide to use PFCHAR, DCI recommends that you use the character '-' since it is used by Unix in fewer places than '@' and generally doesn't need to be escaped. 6. The PFCHAR setting is saved to the general log file when starting to convert files and when entering IMT regardless of the version of uniBasic that you are using. 7. If you overlay existing files and PFCHAR is not defined, whichever file is created last will replace any existing file of the same name. This means that even if both ABC and ABC@ are converted, only the last one converted will be kept. No mention of this will be saved to the log files. 8. If you overlay existing files and PFCHAR is not defined, you may get some file errors when running in unattended mode. This happens because of timing considerations when trying to convert files like ABC and ABC@ at the same time. If this happens to you, re-convert the affected files separately. Additional polyfile changes: In earlier versions of IMT, when you tried to convert a polyfile terminated with '@' and another non-polyfile already existed with the same name, IMT would sometimes return error 70. This has been corrected to return the message "File already exists under a different file type." This also replaces the "File already converted" message for polyfiles. Choosing data on the screen: Certain programs had a problem where not all columns of available choices would be displayed, such as when choosing which logical units to load from tape. This has been fixed so that all available choices fill as much of the page as possible. Saint backup format. Blocking and restoring problems are fixed. Note that one block is added to the LU size in order to handle repeat blocks at the end of a LU. This does not affect processing the next LU on the tape. Two utilities are new in this release of IMT. They are used to help diagnose tape backup problems: Utility: hxd -- Dump a file Syntax: hxd [-d] [-bSTARTBLOCK[.]] [-oSTARTOFFSET[.]] [-0] [-s] [file] Description: Display a file in hex or octal format. The display includes the ascii text that the data represents. This is similar to existing hex dump utilities except that an octal dump (with ascii text) option has been added. Also, the ascii text is displayed with the left bit stripped so that IRIS text can be viewed. Options: -d include duplicate lines -b starting block number to display in hex (end with '.' if specifying a decimal number) -o starting byte offset to display in hex (end with '.' if specifying a decimal number) -0 display in octal words (with ascii text)(similar to DSP) -s swap bytes. useful with -0. Utility: gl -- Verbose copy Syntax: gl source dest Description: This is similar to cp but displays the block number and block length in bytes. This utility is used to help diagnose tape problems. Parameters: source source file or device dest destination file or device Converting IRIS data from a DAT or Exabyte tape: If converting on a system with SCO UNIX release 3.2.4.2 or later, the tape device driver must be configured with 'setblk' equal to 16384. Without this change it is possible for data to be lost during the conversion. This parameter can be configured with the following command: tape -a 65536 setblk /dev/{SCSI tape device name} This is only a temporary change and the default setting is restored if the system is rebooted or powered down. At this time, there has been no reports of any problems with the DAT or Exabyte tape drives on earlier releases of SCO UNIX or any other UNIX operating systems. (end of file)