DSXchange

I was sure that multi-instance jobs would have at least one chapter dedicated to them in the documentation but a quick search didn't locate that chapter. DataStage initially did not have multiple job instances and the rule was that one job could only run in a single instance at one time. But for job...

In your lookup stage in the bottom left box, specify "Key Type" as "Range" in order to do a range lookup.

In the definitions of your import stage (is this a "column import" stage?) you will have incorrectly set the null_field length to 0, which is not allowed in a fixed-width timestamp field. Since this is a strictly typed field, you will have to supply a legal timestamp string value as the de...

It would seem that you don't want to use the recommended Search function before posting.
That error message, particularly the "APT_PMwaitForPlayersToStart" is found in 23 threads.

The output of your "ps -ef | grep dsrpcd" command shows that the rpcd is not running on your machine, which explains why you cannot login. Did you reboot the DataStage server? If yes, and the "dsrpcd" is not running, then attach to the DataStage home directory (usually "cd $...

zhulinqingfeng2 wrote:...I can't open the "http://myserver:9080"...

Ray has already posted that this functionality is not available at V7, just from V8 onwards. I didn't notice that you were using the previous version. Luckily, this type of problem is simpler to debug at your version 7.

I did a quick look into the Parallel Job Developers Guide and found no explicit int32 to int64 function.

I just realized that this was a IA question, not a normal DataStage job question. I should, but won't, redact my earlier post. Sorry.

"Throwing an exception" is a bit uncertain in DataStage terms. But in someething like a source stage where you are reading from an external stream then each row is rejected on error only once and only one error reason is given.

The Search functionality is quite powerful and this topic with the keyword "DSSetUserStatus" will give you lots to look at.

boppanakrishna wrote:...
ODBC_Enterprise_6,0: Fatal Error: Not bounded length.
...

What column definitions do you have in DS and what are their respective lengths?

This message comes from the database, I would suggest talking to your SQLServer DBA in order to have them fix the problem on the database end.

You have 2 basic approaches to take. a) If your job is called using a job sequence, you can pass back a user status to the calling sequence, or have the sequence check for existence of the error file, and then send a mail from the sequence. b) You can use the "After-Job Routine" capability...

What does "Period" mean? Does a "10" mean 10 days, 10 years, 10 months or something else?

None that won't give you the warning (this is a good example of where a job level message handler is very useful). You can convert an unsigned int32 to a signed int64 without a warning, but an unsigned int64 can potentially not fit into a signed int64 and thus the warning.