DSXchange

In DOS it's "type".

Depends on your terminology, I guess. The routine to check and abort the job would still be part of the Server job, a part that runs 'after job' i.e. after everything on the canvas finishes. No 'batch' job or separate process needed, but yes some 'code' will be involved.

Not just "directly on" the server but "directly over" your current install on that server.

Start by posting in the correct forum (the Site forum wasn't a proper place for this but I have moved it) and by letting us know your particulars - version, O/S, etc etc. Do this by going back and editing your original post - the one right above mine - now that you're in a more correct forum that in...

Perhaps no-one else faced this issue before. I know I haven't. Ask your official support provider, you could very well be in need of a patch.

Abhi700 wrote:Actually it should be able to create dataset at run time.

Not when it is reading from it - those must already exist.

Not empty but sometimes people put their only message in the subject line of their reply and you can only see it when you reply. And people still seem to think the only way to reply in a thread is to quote another one in its entirety... sheesh.

Fixed both.

Some types are required and thus can't be left empty, the others need to be explicitly checked triggering a Terminator if needed. If there are many, a routine would be best, I would think.

CmdOutput = 'EXECUTE SH -c "':vDOSCommand:'"'

Post the FD.

What database would that be? Have you involved your DBA?

mavrick21 wrote:To separate inserts/updates into different jobs which is the recommended Stage to stage data? In parallel jobs I used DataSets to stage data. In Server jobs, is it Hashed files?

Sequential files.

You can't answer questions about logging in a sentence or two. Best to google around, grab some of the Oracle documentation and/or chat with your DBA. Advice can change depending on the Oracle version as well.One example from a quick google.

Yeah you!

Zero records = nothing for the transformer to check. Do it 'after job' with a custom routine that uses DSGetLinkInfo to see how many rows were processed.