DSXchange

You had it in your original post, the Transform stage will let you do mathematical operations.

COMP-3 is also known as BCD where each position is encoded in 4bits. Another 4 bits are used for the sign and the result is padded to an even byte boundary. If you declare it as binary integer, then the 16 bits are used as an excess-128 representation and you get the negative number.

ag_ram, your list command is incorrect. The syntax of the list command is | SYNTAX | | | | LIST [DICT | USING [DICT] dictname] filename [records | | | FROM n] [selection] [output.limiter] [sort] [output] | | [report.qualifiers] note, the first mandatory parameter is the filename. It just so happens ...

127.0.0.1?

What is the data type and lengths of both the source and the target columns?

That is not the COBOL definition, but is close and might be enough. I don't like the "0c" hex at the beginning which would indicate a leading sign which is nonstandard. If your COBOL doesn't have a leading sign specificed then you probably already have a wrong position. Also, the data type is 2 digi...

If you go to your director, double click on the job name and then paste the output to this thread we might see something, that will contain the parameters used by the job.

What is the COBOL field definition for this column? It looks like a non-standard COMP-3 with leading sign from the binary.

That is a function of many databases. With hashed files the key is "hashed" into a number which corresponds to a hashed file group (or bucket). When the file is read in unsorted order it will read keys from each group and this will give you the "shuffled" order you see.

The LIST command is incorrect, ag_ram

Can you explain what didn't work? DataStage server internal time is an integer (number of seconds since midnight) so it will sort correctly. If you somehow declare this as a character then it will not sort appropriately, so part of the question back is to ask how you are sorting.

Looks like you entered an empty hostname.

I've changed the post to be non-premium.

No $ sign should be used. Are those "0" or "O" in your parameter name?

I just realized that this thread is in the Server forum and the solution with the job number that I posted was for Parallel jobs; so you are quite correct that it was the wrong answer. You can get the job number by going into TCL or using the Admin command line and issuing a "LIST" or "SELECT" state...