DSXchange

I wouldn't bother with the explain plan if the table mentioned is the target of your job. If so, it simply needed to grow and ran out of space in the tablespace it lives in.

Tell your DBA. If you've got a good one, you shouldn't even have to tell them, they should know already.

Do you want literally USERSTATUS to be "Ok" or "Warning" because your first job does something to explicitly set it, or do you mean just the normal job status of ok or warning? How are you setting the User Status? If that's really what you are using, then I'd suggest first thing in the job setting i...

As already noted - via a Reject link. Re-read Ray's post, it's all in there.

6. Adjust job tunable properties Looking for an explanation of the Aggregator stage properties I can change with this option. Defaults: 1 = ReportAfterRows 100 2 = ReportAfterTime 15 3 = TableSize 8192 4 = ResizeAt 2 5 = ResizeBy 8 6 = Resize2Threshold 524288 Is there a DataStage / Universe pdf tha...

First re-install the DB2 client on the server. Then re-install Datastage on the server. This will set the dsenv file and any other variables needed. Unless something has changed recently, installing (or re-installing) DataStage on a UNIX server does nothing to your dsenv file. You've always had to ...

That and you should clear the hash before you start.

Why not just have your four jobs all write to the same hash file? Save you the 'concatenate' step. I don't believe there will be a problem with them all doing this at the same time.

Interesting. Have to file this one away.

You can use a UV stage to access the hash file and then use 'normal' SQL commands to extract the data from it - including the ORDER BY clause. However, it can't be stored sorted... it's a hashed file after all. Where is your hash file located? If it's in your project (i.e. account) then it will be f...

Dang, Ken, will you stop following me around and typing faster than me! Sheesh...

What I generally do is create all three in the same job... or seperate jobs, if that is not possible. An after job then creates the final product by 'catting' the three files together: cat header detail trailer > final_file You could do something similar. Either that or create your header record fir...

Not sure what you mean by 'unknown system related problem', could you provide an example? What is the target of your job?

In general, any kind of error should be capturable via a Reject link... unless there is some sort of job ending, catastrophic error of course.

Well, let's see... The system variables are local to each transformer, so there's no guarentee that they will match. Constraints are what can cause an out row number to not match an in row number, and the next transformer could care less what number the row was in the previous transformer. However, ...

Well, I had a nice little answer all penned out but then noticed the 'never mind' message when I did a Preview, so I changed what I was going to post. Seemed appropriate.

Consider it ignored.