DSXchange

Not really sure. Where does it occur? I'm guessing that it's the next number to be used when adding objects to the job design.

Does it matter? It's actually done on the link itself, and the link is visible from either stage.

The numeric portion is the order in which they're added to the job design. The non-numeric portion indicates the stage type. For example SequentialFile_0 indicates that the Sequential File stage thus named was the first object added to the job design.

INTEGER(4) in DB2 means four bytes, or 32 bits, or int32. It's not the number of digits. DataStage always adds nonsignificant leading and trailing zeroes to decimal data to prove that precision and scale are being honoured. You don't get a choice on this. To remove them you can convert to string dat...

0 is enough.

0.0 is better if you want to be pedantic about the structure of a decimal data type.

But it makes no difference to DataStage.

Precision will be ignored for Integer, SmallInt and TinyInt data types. Integer (int32) can be up to 2**31-1 so can have at most ten digits plus a sign. SmallInt (int16) can be up to 2**15-1 so can have at most five digits plus a sign. TinyInt (int8) can be up to 2**7-1, or 127, so can have at most ...

That looks suspiciously like the limit on VARCHAR2. Have you tried LONG VARCHAR2 as the data type?

Read the manual (not sure if it is Parallel Job Developer's Guide or Parallel Job Advanced Developer's Guide) about Decimal data types. All zeroes is not permitted by default but can be enabled. Under what circumstances do you wish to use the default value? Is it only if the input is null (consider ...

It will work, but under the covers the system has to position to the end of the physical structure in which data rows are stored. This will take some time, but 55 minutes does seem a lot.

Nice to have that vote of confidence, but we're far from being the only helpful posters on this site. Getting this kind of error occasionally suggests that you're working your server close to its limits, and very occasionally exceeding them. It's simple supply and demand: you need to increase the su...

Which timeout are you setting, and how are you setting it?

That's a huge oversimplification but it will do for now.

Not only is this findable on DSXchange by searching, it's also in the manuals and the IBM Information Center.

Before/after subroutines are written in DataStage BASIC programming language and stored in the DS_ROUTINES table. They are not readily viewed using operating system utilities.

What do you mean by "activate"? Was it blocked in a firewall? There are lots of other ports that may need to be activated too, if this was the problem.