DSXchange

You can actually 'Add to Schedule' as many times as you like. So you could, if you wanted to and the job runtimes don't overlap, have it run every hour by adding it to the schedule for each hour it should run.

I don't believe the Row Splitter stage has anything to do with performance improvement. At least not directly.

netland wrote:Might go the official way instead, and see if they have a solution for the problem.

That's going to depend on if 'they' consider it a problem or not.

Hard to say - what other kinds of things is your job doing? What other stages are in it? Do you have some form of Buffering enabled?

For all we know it may just stop working again.

As already noted, the problem was their T30FILE setting in uvconfig.

As noted, it would be nice to know what database and stage you are asking about. Oracle (and others for all I know) have the ability to handle pound and dollar signs in table names by using the following substitutes: # = __035__ $ = __036__ Note that there are two underscores on either side of the n...

The Server version of the DB2 stage wants dates in internal format. I wonder if the same if true for the EE version?

i want starting value with 1 to n(no of rows in the sorce file).when ever i run this job the no should get 1 to n. which is best way to do it? Not sure why you'd want it to always start over at 1 each time, but if you do there's an easy way to do that: the @INROWNUM System Variable. This tracks the...

Depends, somewhat, on what happens next with the new file. Going back to one of the original suggestions - use the copy command: copy file1+file2 file3 The file noted as 'file3' becomes the product of the first two files concatenated together. Do this 'before job' to a fixed filename for processing ...

Ray, I think Lance was looking for something a little more... generic... than that.

A good reference book about Web Services - the concept, not the specific DataStage implementation - even as a 'Dummies' book, would be good to get one's mitts on. Anybody have one they could recommend?

ray.wurlod wrote:It must be correctly cased on Windows, too.

Ah, thanks for that. I wasn't sure since the O/S doesn't care, didn't know if DataStage enforced that or not.

Wasn't gonna open that can of worms, Arnd.

More than a million warnings? And that's ok? Yikes.

Set the limit to zero for unlimited.

I think it may depend on your exact version. I seem to recall reading somewhere that server side import/export would be included in the 'latest' version but can't seem to find anything about it again.

To expand a bit on the previous post, I agree it is best to leave it blank. A blank Account Name means the current account - i.e. the Project the job is currently running in. If you leave it blank then it will still work as expected when you promote the job from your development to test to productio...