Open the transformer stage, go to the top menu bar, on the right side is a button for output link order. Set the order you need.
Be careful if you're attempting to group rows in a single commit. Read the manual for the conditions to make this work.
Search found 4992 matches
- Thu Feb 10, 2005 9:45 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Out execution order
- Replies: 1
- Views: 343
- Thu Feb 10, 2005 9:44 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: How To Learn more about DS.Tools
- Replies: 2
- Views: 1066
- Thu Feb 10, 2005 9:42 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Hash files and equijoin
- Replies: 3
- Views: 659
For a hash file, the order of the columns (hash files are really delimited strings of data, therefore "positional") and the key designations are what matters. The data types and widths currently don't matter to hash files. Make sure you compare apples to apples. When referencing a hash file, you mus...
- Thu Feb 10, 2005 9:07 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Hash files and equijoin
- Replies: 3
- Views: 659
The metadata used to write a hash file has to be the metadata used to reference the hash. The values defined as the keys are written to a different area in a hash file, therefore, using a different metadata definition does not correctly find rows in the hash file. If you used 3 columns as a multi-pa...
- Thu Feb 10, 2005 8:43 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Extract Column name in Trx through a function call
- Replies: 10
- Views: 3286
Only using proprietary, undocumented, and unsupported library information will allow you to do what you want, and word is that the internal repository design is about to change (again) rendering these hacks useless in future releases. In order to get the column name, you must resolve the internal st...
- Wed Feb 09, 2005 2:34 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Reading hash file
- Replies: 9
- Views: 2191
You have to have the values in your source data that can successfully match to the key values in your hash file. If your hash file key should just be error_cd, then build your hash file that way. You must change the job that creates that hash file and reprocess the data into the hash file. Now, go b...
- Wed Feb 09, 2005 11:26 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Call Stored Procedure from OCI Stage - DS v7.0 (server jobs)
- Replies: 11
- Views: 6141
If your stored procedure is a "do something" procedure, as opposed to a "process with streaming data" procedure, then you're better off using a shell command to execute sqlplus. If you don't want that route, you will have to create a job like OCI --> XFM --> SEQ that will return at least a single ro...
- Tue Feb 08, 2005 10:13 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Random abnormal termination of jobs
- Replies: 11
- Views: 4059
Release 5.x running on Sun 2.8 had issues that required a Sun patch and a DS patch that was characterized by random abnormal terminations under heavy system load. Release 6+ incorporated the DS side fixes, but the Sun patch I believe is still required. You may consider contacting tech support and ve...
- Tue Feb 08, 2005 9:18 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Changing database schema name across all jobs
- Replies: 6
- Views: 1507
Make sure you NEVER use fully qualified embedded schema names. When you import metadata, NEVER use fully qualified names because when you load the table definition it shows up in the DERIVATION column. If you are not going to work thru public synonyms, then you need to parameterize the schema name a...
- Tue Feb 08, 2005 9:09 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Random abnormal termination of jobs
- Replies: 11
- Views: 4059
Make sure your T30FILES setting is high enough to support the number of jobs executing simultaneously. Your problem is a common one. Search the forum for discussions about the UVCONFIG file and recommended settings. The abnormal terminations can be related to not enough internal pointers available t...
- Tue Feb 08, 2005 9:06 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Lookup problem with a multi-instance job - Strange !
- Replies: 30
- Views: 4714
Seems like I will have to take it as one of those datastage 'don't-know-why-it-happens' "features"... NO. I have trained, taught, and used this product since 1998. I am certified in deploying this product (got the paper to prove it) and served over 4 years with Ascential as a consultant. I have nev...
- Tue Feb 08, 2005 3:12 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: instr function
- Replies: 2
- Views: 2617
Code: Select all
INDEX(yourstring, findthis, occurence)To find the first occurence of "test" in "thislongteststring", use
Code: Select all
INDEX("thislongteststring", "test", 1)and it returns the character location of the beginning letter, otherwise 0 if not found.
- Tue Feb 08, 2005 12:00 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Loading Date Values
- Replies: 15
- Views: 5373
- Tue Feb 08, 2005 8:45 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Loading Date Values
- Replies: 15
- Views: 5373
- Mon Feb 07, 2005 9:13 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Lookup problem with a multi-instance job - Strange !
- Replies: 30
- Views: 4714
Verify the path to the hash file. If you're using the project as the default, do a sanity check and View data. Sometimes the hash file being written to is not the same one being referenced. Also double-check the filename is still the same. DataStage Server has this "feature" of updating the hash fil...