Thanks.
Good point re: concurrency.
I'll play with the surrogate key generator some more.
Search found 64 matches
- Tue Dec 15, 2009 12:12 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Retrieving multiple values from a sequence
- Replies: 9
- Views: 2306
- Tue Dec 15, 2009 11:22 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Retrieving multiple values from a sequence
- Replies: 9
- Views: 2306
- Tue Dec 15, 2009 11:08 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Retrieving multiple values from a sequence
- Replies: 9
- Views: 2306
- Wed Dec 09, 2009 9:04 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: xsi:nil+"true" in XML Output stage
- Replies: 6
- Views: 3724
1. No chance yet to explore pure xslt, but that sounds interesting. 2. Datastage is smart enough that when I'm populating an element AND its attributes, it doesn't create 2 sets of tags. I'm sure everyone else knew that, but I didn't :oops: 3. So I can put the 2 rows in the input columns for the xml...
- Fri Dec 04, 2009 2:25 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: xsi:nil+"true" in XML Output stage
- Replies: 6
- Views: 3724
- Fri Dec 04, 2009 1:34 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: xsi:nil+"true" in XML Output stage
- Replies: 6
- Views: 3724
Found an alternative to hand coding the xml (option 2 above). Not sure its any BETTER, just an alternative. For upstream transformer, lets suppose target column name is Colour. create a 2nd column ColourNil immediately before or after this column. make both target columns NULLABLE. In the derivation...
- Fri Dec 04, 2009 12:11 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: xsi:nil+"true" in XML Output stage
- Replies: 6
- Views: 3724
Thanks Ernie. That's actually my option 2 above. And since there are ampersands in some of the data, I have to make the element XML when passing it to the XML output stage. The problem is that I have to do this for several jobs and many elements per job. I was hoping that, since I had imported the o...
- Fri Dec 04, 2009 10:56 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: xsi:nil+"true" in XML Output stage
- Replies: 6
- Views: 3724
xsi:nil+"true" in XML Output stage
http://www.dsxchange.com/viewtopic.php?t=130297 http://www.dsxchange.com/viewtopic.php?t=117035 http://www.dsxchange.com/viewtopic.php?t=116064 http://www.dsxchange.com/viewtopic.php?t=10187 http://www.dsxchange.com/viewtopic.php?t=109788 I have read through the above and I am still not sure. If I w...
- Mon Nov 30, 2009 1:40 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: the record is too big to fit in a block
- Replies: 12
- Views: 15349
- Mon Nov 30, 2009 12:49 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: the record is too big to fit in a block
- Replies: 12
- Views: 15349
The problem returns when I try to send the output to another stage or to a Dataset Stage. Sending the output to a Sequential File Stage is what solved the problem. What APPEARED to be the solution from the previous post was coincidental as that output was written to a sequential file. As soon as I c...
- Fri Nov 27, 2009 4:13 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: the record is too big to fit in a block
- Replies: 12
- Views: 15349
No parameter setting seemed to work. I was building detail xml chunks in one xml output stage and aggregating in the next (copy stage in between). I've done this before to control the way the xml is formed and haven't encountered this problem before. I'm still verifying that the generated xml confor...
- Fri Nov 27, 2009 9:17 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: the record is too big to fit in a block
- Replies: 12
- Views: 15349
Ran into the low watermark message as per viewtopic.php?t=128506.
Is there any way for me to see what values DS is actually using at run time?
Is there any way for me to see what values DS is actually using at run time?
- Thu Nov 26, 2009 4:11 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: the record is too big to fit in a block
- Replies: 12
- Views: 15349
Thanks Ray. In the xml output stage, Output tab, advanced, cahnged buffering from automatic. Increase max buffer by adding 0 on the end (10 x) to from 3145728 to 31457280. Did the same for disk write increment. Changed from 1048576 to 10485760. Dies in exactly the same place. Same message. Will try ...
- Thu Nov 26, 2009 3:20 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: the record is too big to fit in a block
- Replies: 12
- Views: 15349
I've reviewed the following posts : http://dsxchange.com/viewtopic.php?p=23680046 http://www.dsxchange.com/viewtopic.php?t=109868 http://www.dsxchange.com/viewtopic.php?t=109896 http://www.dsxchange.com/viewtopic.php?t=126730 The job is creating XML using parallel xml output stages. The first stage ...
- Mon Nov 09, 2009 4:44 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: remove string
- Replies: 15
- Views: 5641
Thanks rcanaran, ContractRoleIdPK string repeatable in line with value. I need to delete all <ContractRoleIdPK> values </ContractRoleIdPK> values. Please give me command in unx See option 3 above. Use an external filter stage. with filter command and arguments set as above. If you want to process s...