DSXchange

You will find that the UNIX environment variable TEMP is also a project environment variable - you might try changing that value.

Welcome aboard. We don't do "urgent" or "ASAP", particularly not on weekends. DSXchange is an all volunteer site whose members post when they can. If you need an answer ASAP sign up with your official support provider for priority service and learn just how much "urgent"...

You probably got the wrong answers using Auto partitioning.

Sorry, it's New (not Add). This gives you a new dialog in which you define the user's contact characteristics, and in the middle of which you assign Information Server suite roles and product roles. You need to create your users as suite users (rather than administrators) and DataStage users (rather...

Not true. It's going to be the port set up in the database client's connectivity utility.

I still don't understand your meaning of "taking". Can you try to express this in different words?

They will work regardless.

Unless, of course, you've selected that reference link as "allow duplicates".

Creating a UNIX id is optional. On the Users page there is a menu on the right hand edge, one option there is Add.

How would you do it in SQL ? Play with the properties or SQL in the DB2 API stage until you match that SQL. You may need user-defined SQL here, because you need to pass the old key value as a Key column and the new key value as a non-key column.

Map the output argument to a column on the output link from your stage that invokes the Stored Procedure.

In short because your data do not match your metadata in the first case. Without seeing examples of your data and your record schema(s) it is not possible to comment further.

Enterprise Edition comes with both server and parallel licenses; it is possible to choose to license either or both. In my opinion you'd be crazy not to license both, because server jobs still have a place for small tasks (especially single-row jobs). My rule of thumb is to be empirical - up to, say...

Truncate issues a TRUNCATE TABLE statement, which is non-transactional. Clear (probably) issues a DELETE command, which will be logged in the transaction log. As a general rule truncate is faster.

The answer initially is zero. The Stored Procedure is not returning (producing) any rows; it is consuming them.

You could always amend the Stored Procedure so that it returns the number of rows it received, or processed, or whatever other value interests you, via an output argument.