iiimport Command--Import Application Components
The iiimport command copies application components from an intermediate file into an existing application. The intermediate file, created by iiexport, contains the definitions for the components you specified when you ran iiexport. See the The iiexport Command section for the types of components you can copy.
When you import a component, the iiimport command assumes that the component exists in the application, and revises the existing version of the component. When you import a frame, the existing frame definition, including local components, is replaced with the new definition. The iiimport command does not change menu items for a frame, except for user-defined menu items included with Escape code. See
How Dependencies Are Handled for information on how iiimport handles menu items and other dependent components.
You can check whether a component exists in the target application by using the -check option. Running iiimport with the -check flag does not actually copy or replace any components, but reports on the status of the components in the target application.
You can import a component that does not exist in the target application, but the target application itself must exist. To copy an entire application into a database, use the copyapp utility.
All components copied in are assigned to the owner of the target application.
This command has the following syntax:
iiimport dbname appname [-intfile=filename] [-listing=filename]
[-user=username] [-check | -copysrc] [-dropfile]
dbname
Specifies the database to which the component is being copied
appname
Specifies the application to which the component is being copied
-intfile=filename
Specifies the intermediate file to be imported. The filename must specify a file created by iiexport. The filename can be the full pathname of the file. If you specify the -intfile flag, you must indicate a file name. If you do not specify the -intfile flag, iiimport assumes the name of the intermediate file is iiexport.tmp.
-listing=filename
Specifies a file that contains a list of source code files for the copied frames or procedures
If you specify the -copysrc flag, the source files listed in this file are the files iiexport/iiimport copies.
If you do not specify the -copysrc flag, you can refer to the listing file to find out which files must be copied manually.
If you specify the -listing flag, you must indicate a file name. If -listing is not specified, ABF does not create a listing file.
-user=username
Runs the command as the user specified by the username.
To use this option, you must be a privileged user.
If you are using Enterprise Access products (formerly Gateways), see your Enterprise Access documentation before using this parameter.
-check
Reports the status of the components before actually replacing or importing any components. Use the -check option to report whether the components in the iiexport file exist in the target application. The status is 0 if all components were found. If not all components were found, the status is a non-zero integer.
-copysrc
Specifies that application's source code files are copied to the target application's source code directory. These are the files named in the
-listing file, if one was specified. You cannot use the -copysrc flag if the applications are on different machines.
-dropfile
Deletes the intermediate file when the import operation is completed