Import command for InfoSphere DataStage and QualityStage assets

Purpose

Use the InfoSphere® DataStage® command option with the istool import command to import IBM® InfoSphere DataStage and QualityStage® assets from an archive file to the metadata repository of IBM InfoSphere Information Server. This command is the reverse of the export command.

Prerequisites

To import InfoSphere DataStage and QualityStage assets you must have a role that grants you permission to edit assets in the target project. To include related common metadata assets in the import, you must have the Common Metadata Administrator role.

The preferred way to run this command is in the istool command-line window. If you run this command in your operating system command-line window or in scripts, you must add istool before the command name.

Command syntax

Command options

authentication parameters

All asset interchange commands use authentication options to connect to a specific installation of InfoSphere Information Server.

generic parameters

The generic parameters are available by all asset interchange commands. Use the generic options to request help on command syntax, or to specify silent or verbose operation.

-archive |-ar "asset_pathname"

Required. Specifies the .isx file to import assets from.

-preview |-pre

Specify this option to preview the action of the command without changing the repository.

-replace

Specify this option to replace existing assets with imported assets of the same identity.

-responseFile | -rf "file_name_and_path"

Specifies the name and path of a response file that contains assets that failed to import during a run of a previous istool import -ds command. Not supported with the -preview parameter. For more information, see Using a response file with istool export and istool import commands.

-abortAfter | -abort number_of_errors

Stops the import stops after the specified number of errors.

-datastage | -ds ' "server/project" '

Specifies that InfoSphere DataStage and QualityStage assets are to be imported to the target server and project. You can use the following option within the single quotation marks (' ') that follow the -datastage parameter:

-nodesign

Specifies that only job executables are imported, not job designs.

Importing multiple types of assets

If the archive file includes multiple types of assets, you must specify each type of included metadata on the command line when you import the archive file. Otherwise, only InfoSphere DataStage and QualityStage assets are imported. For example, if the archive was exported with the -includedependent option, it could include common metadata assets.

import –domain sliver.svl.ibm.com:9443
-username user1 -password pass1
-archive "c:\arc.isx" 	-cm '' 

import –domain sliver.svl.ibm.com:9443
-username user1 -password pass1 
-archive "c:\arc.isx" 	-datastage ' "slice/aProj" '  

Importing standardization rule sets into multiple projects

If an archive file contains only standardization rule sets from InfoSphere QualityStage, you can import the rule sets into more than one project at the same time.

You can use an asterisk (*) as a wildcard character to indicate the projects that you want to import the rule sets into. For example, the following command imports the rule sets into all projects on the server:

import –domain test.sample.com:9443
-username isadmin -password isadmin
-archive "c:\arc.isx" 	-datastage ' " test.sample.com/*" '

The following command imports the rule sets into the projects on the server that begin with the letter X:

import –domain test.sample.com:9443
-username isadmin -password isadmin
-archive "c:\arc.isx" 	-datastage ' " test.sample.com/X*" '

Exit status

A return value of 0 indicates successful completion, any other value indicates failure. The list of exit codes is shown in the command help. Enter istool import -help to see the list of possible exit codes for the import command.

Error handling