Library Importer Tool
It is often useful to be able to import maps from one development library into another, particularly when migrating from VisualAge Smalltalk to VA Smalltalk or from one version of VA Smalltalk to another. The importer program is the tool that provides this function. Both the client and the manager product installation processes install the importer program in the <vast>\importer directory.
Windows: The importer program is called importer.exe.
Linux: The the importer program is called importer.
The importer is most useful when installing a new version of VA Smalltalk where it can be used to update your working development manager with the content of the new version’s manager. You typically would not use the importer to merge a working development library into the new version’s library since the importer does not copy everything from the source library; it copies only the versioned configuration maps (unless allVersions=false is specified, in which case only the newest versioned configuration mapswill be copied).
The importer accepts the following parameters:
-z.target= accepts the location of the target library – the development library that will contain the imported code. The library can be specified in one of two ways:
libraryPath This will use fileIO to access the library
server::libraryPath This will use EMSRV to access the library
-z.source= accepts the location of the source library – the development library containing the code to be copied. The format is the same as for the target.
-z.sourcedir= accepts a directory path. Code will be copied from of each library (i.e. each file with a DAT extnsion) in the directory.
-z.allVersions= accepts 'true' to import all map versions from the source library or libraries, or 'false' to import only the most recent version of each map in the source library or libraries. Default is 'true'.
-z.silent runs with no user interface (no longer used, it will be ignored).
Notes:
1. Either -z.source or -z.sourcedir must be specified, but never both.
2. With File I/O only one person may be using the development library at any one time or you will get the following error message:
Error 65: Open Failed.
3. The z. prefix on parameters is optional as of V8.6.3.
After the tool runs, check for non-zero exit codes. The tool will end with a 0 (zero) exit code if the import was successful. If the import was not successful, the tool will end with a non-zero exit code.
The following are some examples of how to run the tool. All examples copy from a working development library into the new development library, mgr1000.dat.
•importer.exe -source=e:\tmp\myfeat.dat -target=localhost::d:\vamgr\manager\mgr1000.dat
•importer.exe "-source=c:\Program Files\Instantiations\VA Smalltalk\10.0\manager\mgr-working.dat" "-target =c:\Program Files\Instantiations\VA Smalltalk\10.0\manager\mgr1000.dat"
•importer.exe -z.target=zot::d:\vamgr\manager\mgr1000.dat -z.sourcedir=e:\tmp\featureDir –z.allVersions=true
The following examples copies from the new development library, mgr1000.dat, into a working development library.
•importer.exe "-target=c:\Program Files\Instantiations\VA Smalltalk\10.0\manager\mgr-working.dat" "-source=c:\Program Files\Instantiations\VA Smalltalk\10.0\manager\mgr1000.dat"
Logging
An importer.ini file is provided in the <vast>\importer directory. It contains an [EmLibraryImporter] stanza controlling the logging done by the importer. You can set the value of logFilename= to empty (blank) to disable logging or to the fully-qualified name of the desired log file to enable logging. The default value is
Linux: logFilename=temp/importer.log or
Windows: logFilename=%tmp%\importer.log
Last modified date: 06/26/2020