DSXchange

Un-hijacked. your are correct craig, sorry about that for not making it a new post i though that would be more clearer. Sorry, but it never is. All it does is distract people and confuse things when two problems are being discussed in the same thread. That and you have no mechanism to mark things a...

Suggest you talk to jeet_81.

viewtopic.php?t=142953

"doesn't work"?

It sounds like the first Sequence you ran inside the loop did not run gracefully. What is in its log? What is your trigger expression from there to the End Loop stage?

That's what I was thinking you might mean.

You must have a lot of free time on your hands.

Un-hijacked.

g_rkrish: I was forced to enter a Release & OS for your post, please go back and edit it if what I set them to (8.x, Unix) are not correct.

But if we know the number and types of stages in sequence , Then we can implement job sequence specific script in our own way. The above is not clear. Can you please explain? OK, a little good natured tease but honestly - I have no idea what a "job sequence specific script" could possibly...

That is a "best practice" but I'm a little surprised to see it as a compile time error rather than a run time error. Interesting.

i want to start from where it aborts in the last run. At the same time, there should not be any checkpoints in sequence. Those are mutually exclusive requirements, unless for some reason you want to play the "roll your own" game. As noted, why bother? Enable checkpoints. Be curious to hea...

I'm assuming it is a part of the larger ETLStats package...

pandeesh wrote:I am not using checkpoints in sequence.

What happened to this part? (emphasis mine)

There is no option for Enterprise Edition Don't need one. Your questions are either for a specific job type (Server, Parallel or TX) and there are forums for each or a "general" question goes in the General forum. I sincerely doubt your questions are related in any way to the TX product, ...

No. Since you've said there are no checkpoints involved, you will need to RESET the job if it aborted on the previous run.

Hopefully that means you realized that you can indeed go straight to the "parameter file" since it indeed is just a sequential file.

Moved.

Cherukuri - please go back and edit your post to include the details we're missing right now: Version, Job Type & O/S .