Search found 189 matches
- Wed Mar 28, 2007 1:12 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Special character !! ... ascii value "20" ?
- Replies: 15
- Views: 4442
- Mon Mar 26, 2007 9:44 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Special character !! ... ascii value "20" ?
- Replies: 15
- Views: 4442
- Mon Mar 26, 2007 9:35 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Special character !! ... ascii value "20" ?
- Replies: 15
- Views: 4442
- Fri Mar 23, 2007 2:31 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Special character !! ... ascii value "20" ?
- Replies: 15
- Views: 4442
0506110000 0000905413TN200605120620000000 0000905413TN200605140356380000 0000905413TN200605150568250000 0000905413TN200605210306880000 0000915113 ZP200608130546660000 0000915113ZP200608140291640000 0000915113ZP2006081806 04450000 0000915113ZP200608210647340000 0000905413TN200605120241960000 00009054...
- Fri Mar 23, 2007 2:29 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Special character !! ... ascii value "20" ?
- Replies: 15
- Views: 4442
- Fri Mar 23, 2007 2:26 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Special character !! ... ascii value "20" ?
- Replies: 15
- Views: 4442
Special character !! ... ascii value "20" ?
HI, I am creating a fixed width file as a final target to my job. DS fills the empty space with blank values which are not spaces. This file when we try to load to SAP those blanks show as ###. I have tried viewing the file in HEX EDITOR and found that "20" is filling in the spaces( THE VA...
- Wed Mar 21, 2007 8:32 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Blank "Timestamp" field shows *****
- Replies: 9
- Views: 2400
- Tue Mar 20, 2007 1:53 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Blank "Timestamp" field shows *****
- Replies: 9
- Views: 2400
- Tue Mar 20, 2007 12:14 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Blank "Timestamp" field shows *****
- Replies: 9
- Views: 2400
- Tue Mar 20, 2007 11:41 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Blank "Timestamp" field shows *****
- Replies: 9
- Views: 2400
- Tue Mar 20, 2007 11:18 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Blank "Timestamp" field shows *****
- Replies: 9
- Views: 2400
Blank "Timestamp" field shows *****
Hi, I have a job where I get blank data from the source for a column with "Timestamp" datatype in a seq file. The source is from a server job. When i view the data in parallel it shows blank columns but when I write the data in a seq file or a dataset.... The data shows as "*******&qu...
- Tue Mar 13, 2007 12:09 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Is this the right way to execute a script in a sequence
- Replies: 2
- Views: 1381
Is this the right way to execute a script in a sequence
The script name is "PMCSExtractEPBWhlseOrders", its a sql script. I am specifying the script in a execute command stage in a sequence. Is this the way I am supposed to do it?? I get a error saying SP2-0640: Not connected , when i do it ... does this mean i dont have the permission to execu...
- Tue Mar 13, 2007 7:51 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: reading a delimited file
- Replies: 19
- Views: 4209
- Mon Mar 12, 2007 3:07 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: reading a delimited file
- Replies: 19
- Views: 4209
- Mon Mar 12, 2007 9:48 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Constraint to abort job
- Replies: 19
- Views: 6220
Thanks for the response guys... In my case i'm comparing the counts in a job , ... INPUTROW COUNT = OUTPUT ROWCOUNT (this is the constraint), if they are equal then the job should run. If not it should fail. This job will be in a sequence, so even if the job fails after processing all the rows ... a...