Search found 198 matches
- Fri Aug 01, 2008 3:37 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Database comparison
- Replies: 8
- Views: 2410
I would go with a script (Unless its a different database and you don't have a dblink) select t1.*, t2.* from $TableA t1 left join $TableB t2 on t1.$PK1=t2.$PK2 where t2.$PK2 is null you can use full outer join if required. If Keys vary then select t1.*, t2.* from $TableA t1 left join $TableB t2 on ...
- Fri Aug 01, 2008 11:34 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: output from hashed file
- Replies: 47
- Views: 15439
This is the output resulting from the sql query. Field1...... Field2......... Field3.............. Field4.... Field5.... -4927275313 Not Applicable 2008-05-06 09:06:40 Test1 0 -4829300379 Not Applicable 2008-03-25 07:38:49 Test2 0 -4813747248 Not Applicable 2008-03-17 10:51:17 Test3 0 -4702305701 No...
- Thu Jul 31, 2008 10:06 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: output from hashed file
- Replies: 47
- Views: 15439
- Thu Jul 31, 2008 12:08 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: output from hashed file
- Replies: 47
- Views: 15439
- Thu Jul 31, 2008 9:55 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: output from hashed file
- Replies: 47
- Views: 15439
I made some study and found that we can change the width of all fields to a predetermined value by using CONNECT localuv .w *,<width> But even when I do that still the truncation/folding occurs [There is no other option allowed ie. to allow for continous display of the row] Right now I see that the ...
- Thu Jul 31, 2008 5:36 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Extremely long time loading and extracting records
- Replies: 2
- Views: 1576
- Thu Jul 31, 2008 5:31 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: date Format YYYYMMDD check
- Replies: 10
- Views: 3792
I guess that would be a valid date, so you would need to have a special condition (ie. ignore 0000-00-00) apart from checking whether its a date. As to know whether it is a date or not, there are date functions available, you could apply your own logic on them to know whether its a valid date or not.
- Thu Jul 31, 2008 5:28 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Remove "," from a file to read each field
- Replies: 4
- Views: 1794
- Wed Jul 30, 2008 1:41 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Routine to delete a table
- Replies: 7
- Views: 2282
- Wed Jul 30, 2008 1:05 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Routine to delete a table
- Replies: 7
- Views: 2282
- Wed Jul 30, 2008 8:44 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: output from hashed file
- Replies: 47
- Views: 15439
- Tue Jul 29, 2008 7:38 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: output from hashed file
- Replies: 47
- Views: 15439
Code: Select all
No, not really. Why not just do this in a Server job and be done with it?
- Tue Jul 29, 2008 6:40 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: output from hashed file
- Replies: 47
- Views: 15439
- Tue Jul 29, 2008 12:45 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: output from hashed file
- Replies: 47
- Views: 15439
LIST DICT yourhashedfile when I do the list.. even the column names (not all) are split (comes half in one line half in other ) GET.TERM.TYPE I have used GET.TERM.TYPE and saw that the width is changing from 80 to 132. But the following are still occuring a) HashFile1 : split of fields - fields com...
- Tue Jul 29, 2008 12:22 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: output from hashed file
- Replies: 47
- Views: 15439
Yes I do have it in seperate line as below. LOGTO <ProjectName> SET.TERM.TYPE WIDTH 132 SELECT * FROM <HashedFile>; Is there any max limit to it, as I want this to be generic and wouldn't like my process causing a limitations. Will this as well solve the splitting of the fields? I will try to look a...