It's for import of DSX files only.
You might want to check out the new Asset Import/Export capabilities of Information Server 8.1. And the ISManager tool. These use a new format, not DSX though, as they apply to more than just DataStage artifacts. So can't handle stuff from before 8.1.
Search found 36 matches
- Wed Apr 15, 2009 9:44 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Cannot import server routine DS 8.0 in DS 8.1
- Replies: 25
- Views: 13455
- Wed Mar 18, 2009 3:47 am
- Forum: General
- Topic: Error while saving Parallel jobs & Compiling
- Replies: 4
- Views: 3192
A number of errors appear on the client for which you really need to see a Java stack trace to find the root cause. If you look in the C:\Documents and Settings\ Windows_Username \ds_logs directory you should find files named like dstage_wrapper_trace_NN.log (where N cycles from 1 to 20, to give you...
- Wed Mar 18, 2009 2:58 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Cannot import server routine DS 8.0 in DS 8.1
- Replies: 25
- Views: 13455
- Fri Jan 23, 2009 3:48 am
- Forum: General
- Topic: DatStage showing DSCAPIOP_OraDB Error
- Replies: 5
- Views: 3191
- Thu Jan 22, 2009 7:46 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Warning: Configuration file not set
- Replies: 1
- Views: 1323
- Thu Jan 22, 2009 7:23 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: .dsx file
- Replies: 2
- Views: 2005
DSX files are created on the client (that is the same machine you are running the Designer on) in any location you choose to give to the export dialog. If you create a DSX file by running the dsexport.exe command, again you specify where you want to create the file on the local (must be Windows) sys...
- Thu Jan 22, 2009 7:00 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Importing Universe table definitions
- Replies: 4
- Views: 2583
- Fri Jan 16, 2009 2:38 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Audit routines
- Replies: 5
- Views: 3258
- Wed Jan 14, 2009 6:03 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Audit routines
- Replies: 5
- Views: 3258
- Wed Jan 14, 2009 4:23 am
- Forum: General
- Topic: Routine Argument maximum size
- Replies: 8
- Views: 3703
- Tue Jan 13, 2009 10:17 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Sequence - Possibility of Shell Script
- Replies: 20
- Views: 9925
- Tue Jan 13, 2009 4:33 am
- Forum: General
- Topic: Job Report Folder
- Replies: 3
- Views: 3137
- Fri Jan 09, 2009 4:51 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Sequence - Possibility of Shell Script
- Replies: 20
- Views: 9925
- Thu Jan 08, 2009 6:18 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Sequence - Possibility of Shell Script
- Replies: 20
- Views: 9925
The trigger tab of a job activity stage is an expression that fires after the job has run. Sounds like your expressions need to be on the triggers of the Execute Command stage, not the job activity. Those fire after the command is executed, to decide whether execution proceeds to the next stage (the...
- Thu Jan 08, 2009 4:20 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Chinese Characters
- Replies: 21
- Views: 18863
From your original mail, it sounded like the character set of the data you are reading in the job was UTF-8. You should not change the project or job maps to say MS-936-CS, in that case. If you do, you are telling DataStage that the *data* is in code page 936, when it is not - it is in UTF-8. (The r...