Datastage jobs Import/Export

Difference between Jobs with and without executable:

1. Export job designs with executable:Both the ‘design time’ information (what you see in the Designer) and the ‘runtime code’ are exported. This way it can be imported into another environment and (ideally) be ready to run without any further steps. Of course, this assumes the new environment is equivalent to the old one, especially if true C++ compiled code is involved. You might use this if you only have a C++ compiler in the Dev environment, for instance, but don’t want to pay for licenses to run it on all boxes.

2. Export job designs without executable: Design time without run time. First thing you would need to do post-import would be a compile. Mostly for heterogeneous environments, I would imagine. Note that this is the only option available for exports in XML format.

ISX vs DSX

.isx archived file of .dsx
DataStage export generates “.dsx”. Information Server Manager export generates “.isx”
Isx is in binary form and dsx is not, so isx is more secured.
Less in size and can automate easily compared to dsx.

How to use ISTOOL for EXPORT IMPORT Information Server Components

http://www-01.ibm.com/support/docview.wss?uid=swg21437906

Location of command:
Windows: IBM\InformationServer\Clients\istools\cli

Export command sample:

Example
domain name: SERVER.us.ibm.com
port no: 9080
DS Server name: SERVER
DS Project name: Test
and we want to export parallel job PxCustom.pjb which is in folder “Jobs/PX Jobs/”.
then command would be
istool export -dom SERVER.us.ibm.com:9080 -u admin -p admin -ar /test1.isx -ds ‘ “SERVER/Test/Jobs/PX Jobs/PxCustom.pjb” ‘

We export with executable using incexec because we don’t have compiler in production env.

Possible values for: Options
Long Name: Short Name: Description:
-help , -h : print command usage
-domain , -dom : Name of Information Server domain
-username , -u : Name of user account on Information Server domain
-password , -p : Password for Information Server account
-updatearchive , -up : Update any existing Package file
-datastage , -ds : DataStage Assets

Options for: -datastage
-includedependent , -incdep : Include dependent items
-nodesign , -nodes : Exclude design items
-includeexecutable , -incexec : Include executable items
-base , -base : Prefix for Paths

How to use dsexport/dsimport for EXPORT IMPORT Information Server Components

http://www-01.ibm.com/support/knowledgecenter/SSZJPZ_9.1.0/com.ibm.swg.im.iis.ds.design.doc/topics/dsexportcommand.html

dsexport.exe /AF=authfile |
/D=domain /H=hostname [/U=username [/P=password]]
/JOB=jobname
/XML /EXT /EXEC /APPEND
project pathname1

How can I improve performance during an import into Datastage?

• Exclude the executables from the export.
  In DataStage Designer export using the option export Jobs without executables.
• Create an xml file instead of a dsx file.
  Executables are not included in xml files.
  (The xml option is available with dscmdexport but only with /JOB option)
• Use the IS Manager or istool command.

You can use the istool command line interface (CLI) to export assets to an archive file. The default extension of the archivefile is .isx.
When using the istool command, if you do not use the parameter -incexe, it will not include executables.