DSXchange

Nope. If you've found a combination that works for you, go with it.

Make sure you understand that 'release' is a specific operation and not at all related to 'unlocking' a locked job.

I think the biggest confusion comes when it is set improperly regardless of forum. Or for people who assume based on the forum.

The problem is while running the whole process the actual jobname say "abc" changes to abc.InvocationId.Thus the script and the sequencer job fails to run the job and it fails This isn't a 'problem' per se, it is the way multi-instance jobs work. Did you take a job that was MI and turn that off wit...

Then just do it. Correct your dsenv file so that the 32bit libraries are used for the connection, you'll be fine.

That would be the Advanced guide, actually.

Confusing. Is your Sequence job multi-instance? Shouldn't the two new jobs be multi-instance as well? What Invocation ID are you expecting to pass to the four jobs, the one used for the Sequence job itself?

What is your Target? Have you confimed the lookups are the issue by replacing it with a Sequential File stage?

Since you've started a new thread for this, answers are over there. I still don't understand why you continue down this path when you've been told several times it is completely unnecessary. At least for the reason you've given.

In other words, you need to have the routine tell you what went wrong. Plus... Where is DBSCHEMA being used? What user/password is it connecting as?

As Ray noted, the behaviour you've seen is related to having the Write Cache option enabled. It goes very quickly as the records are written to memory first, then once complete (or the cache fills) they are flushed to disk as a separate step, which is why you don't see the record count change. First...

Why? Ok... SELECT * FROM #$SCHEMA_NAME#.#SrcTblNm# WHERE ATTRIBUTE_NAME = '#DSJobInvocationId#' AND Update_DT >= (select TO_DATE(max_date,'DD-MON-YYYY') from PARAM_TABLE where Tgt_Table = '#DSJobInvocationId#') I'm assuming the date mask is correct from your previous post, you'd need...

You are converting something that is already a DATE to a DATE. Simplify your SQL: SELECT * FROM #$SCHEMA_NAME#.#SrcTblNm# WHERE ATTRIBUTE_NAME = '#DSJobInvocationId#' AND Update_DT >= (select max_date from PARAM_TABLE where Tgt_Table = '#DSJobInvocationId#') And you need to use single quotes...

Thought I would revisit this and post the resolutions to all of these issues. The final piece of the puzzle was found in this thread - thanks to ttk1973 for posting that. Both of these seem to be specific to HP-UX 11.11 so keep that in mind if you think you are having a similar problem. 1) Bus Error...

For any 'abnormal abort', the first thing you need to do is Reset the aborted job from the Director and post any 'From previous run...' messages that appear in the log. Otherwise we all (yourself included) have to guess the reason behind the abort. It is always best if you cut and paste the actual e...