Search found 53125 matches
- Tue Oct 23, 2007 4:35 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Warning in Datastage 8x Remove duplicate stage
- Replies: 6
- Views: 6774
- Tue Oct 23, 2007 4:33 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: The NLS character map <ASCL_ISO8859-1>
- Replies: 1
- Views: 2083
And? You did not tell us the value you have set for the NLS_LANG environment variable. The message suggests that it is not compatible with the NLS code page setting (ISO8859-1) you have specified for DataStage. NLS_LANG is mainly used by database client software when communicating with database serv...
- Tue Oct 23, 2007 4:31 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Exporting the Project: read only items were ignored problem
- Replies: 7
- Views: 1500
- Tue Oct 23, 2007 1:33 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Can any one look into this????
- Replies: 13
- Views: 3388
What's the basis of the join - the Cartesian product across all tables? If not, what is the basis for selecting corresponding rows from the three tables? For example, you could generate a key from/in each SELECT, and use that as a join key. But what's the right order from each table? More informatio...
- Tue Oct 23, 2007 1:12 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Where can I enable the NLS setting???
- Replies: 14
- Views: 6096
You will need to reinstall the production server if NLS is not installed and you want to use NLS. You would do well to read the DataStage NLS manual first since you appear to be unacquainted with it. As Arnd points out, you do not need to uninstall to re-install DataStage server at the same version.
- Mon Oct 22, 2007 10:17 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: DB2 stage performance issue
- Replies: 13
- Views: 5341
- Mon Oct 22, 2007 10:15 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Where can I enable the NLS setting???
- Replies: 14
- Views: 6096
- Mon Oct 22, 2007 6:50 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: How many files can File Pattern Handle
- Replies: 5
- Views: 1395
- Mon Oct 22, 2007 6:49 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Routine is not cataloged
- Replies: 13
- Views: 8469
- Mon Oct 22, 2007 6:37 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: problem with date format
- Replies: 8
- Views: 2179
- Mon Oct 22, 2007 6:36 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: dsjob server name
- Replies: 4
- Views: 1580
- Mon Oct 22, 2007 6:35 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: dsjob server name
- Replies: 4
- Views: 1580
- Mon Oct 22, 2007 6:33 pm
- Forum: General
- Topic: How do I write out records when input has no eol char?
- Replies: 7
- Views: 1536
Server job CFF stage does not support OCCURS DEPENDING ON. Your only choice, without an EOL character, is to read the file byte by byte. While you can do this in a routine, you probably don't want to. If there are EOL markers, you can at least read each record as a single VarChar, and parse it withi...
- Mon Oct 22, 2007 2:34 pm
- Forum: General
- Topic: Best Practices for IDOC Load
- Replies: 3
- Views: 1616
You could call a BAPI, but performance would be woeful. A better approach is to build the lookup table locally to your job, in a hashed file. This will offer best performance. Only populate the hashed file with those columns that you actually need in the job, and only extract current rows from R/3 (...
- Mon Oct 22, 2007 2:32 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Routine is not cataloged
- Replies: 13
- Views: 8469
It apears that, in Project B, either someone has written their own ExecSH and compiled it, or that Project B has been around for a very long time (since at least version 5.2). Check whether there is a DEFFUN declaring ExecSH as calling "DSU.ExecSH". If there is, this is at the heart of your problem;...