DSXchange

a) Please don't use just uppercase - it is considered shouting
b) Using "ASAP" usually means that you get a slower answer since this is a forum staffed by volunteers.
c) Please post the exact error message

That is too bad, it sounds like you have the dubious honour of getting to open up a support call. At least you have a reproduceable test case for them.

In order for a timestamp to be compressed, it needs to be converted to a string. Likewise, the string value is decompressed and then put into a timestamp format. I would wager that the problem here is the default string formatting of the timestamp field; since the "*"s you see usually come...

Have you specified "reset if required" in the sequence where you are calling up this job? If not, please do so - if you don't have that set and try to run a job which is in an "aborted" state you would get an error message like this.

Is this the only repository error that you have seen? It would seem to indicate xmeta repository inconsistancies and/or errors. I've seen RID errors that are temporary and go away at a second attempt. Could it be that it is trying to insert a new category tree where one exists already - is this a fr...

the "Item-ID" column output is not affected by the terminal width setting. The items are listed correctly, though. The item ID you displayed is the complete record ID that is locked.

I vaguely recall that a modify can't use two functions, but am not in a position to test tht right now. I guess I always cheat and use a transform stage instead.

The SET.TERM.TYPE command isn't a UNIX command, but needs to be executed inside the TCL session, i.e. when you have the ">" prompt.

User defined stages are a way of extending DataStage functionality; if you need something specific done which cannot be handled otherwise you can write your own stage. It is much more complex and involved than just using an external routine or BuildOp. We use one here which performs a two-phase-comm...

TrimLeading only trims leading characters, Trim() by default trims leading and trailing. Both are different functions and one can't be "better" than the other. It depends upon what you are trying to achieve.

You might be lucky and be able to clear the log file from the director to get rid of this error. Or edit the job, save as another name, delete the original and rename the copy. This will get rid of the log file error.

This hashed file is internal to DataStage and is not documented anywhere.

Since both functions do different things you cannot compare them that way.

An uninstall should also involve removing the Windows registry settings.

Yes, you can have multiple instances of the same DataStage server running concurrently. They are installed using different ports and I think that this capability has gone away with version 8.x - i.e. one cannot run two or more 8.x servers on the same machine.