DSXchange

That would be Account[5,5]

So it looks like the SEQ and SEQ1 calls are working (but shouldn't they be exactly the same?) - now what is your derivation where you use them?

Woth - that's the first time I heard about that. Are you sure you heard that from a credible source?

Yen,

how would you determine whether or not a job is "hung"? Once you have that definition - which isn't easy or possible, in my opinion - the send mail part is easy as it already is part of DataStage.

Oracle does have sequences - is that restriction due to policy at your site? Search this forum for "KeyMgt" and you'll find lots of posts on the subject. The KeyMgt routines are part of the SDK and I don't know where that is documented.

You would need to create a hashed file secondary lookup table to do this. There are many posts and several examples to be found here on DSXchange on how to do this as it is a problem that many have had before.

Try "LIST SDKSequences F1" to see what the values are.

Most databases have sequences that you can use to do this in simpler manner; you could also manage your keys from within datastage. What database are you using? Can you implement sequences? If DataStage is the only application that is creating new keys for this table then the most efficient and fast...

I just took a gander at the source and there should be no problem with those two names. Did you also check in the derivation that you used both names as well and didn't inadvertantly re-use the same stage variable? You should have a hashed file called "SDKSequences" with two records in it (SEQ,SEQ1)...

Could you post your exact syntax for calling the routines? I suspect that the problem lies there.

You can use the scheduler in the Director to do this. It will use the underlying OS system (cron on UNIX, at on Windows) to do this so that subsystem must be enabled.

The jobs will start at 9am, whether you run sequentially or in parallel.

What else are you asking about this or what sort of information are you looking for? If you ask the question again with a bit more precision someone might be able to help.

Try writing your own routine as follows: Command = "d:\progra~1\winzip\winzip32.exe -min -e c:\File_Name.zip c:\" EXECUTE 'SH -c "':Command:'"' CAPTURING Ans RETURNING ErrorCode Ans = 'Error Code "':ErrorCode:'", Output "':Ans:'".' Compile and run - if the rou...

Ocean - if you address a post to Ray, does that mean you don't want to hear from anyone else? The performance change is expected when you have a multi cpu system. What is your question? Oops, I'll take that back since I'm not Ray.

Lucky, in your case note that the DS job is not hanging, it is just waiting for your WinZip to return control to it; so actually WinZip is hanging. In 99 out of a 100 cases this is because it has issued some command and is waiting for input, as Craig has already suggested. Could it be that the outpu...