DSXchange

After you click 'Show Error' and it highlights the Transformer, click 'More'. It will tell you exactly what it thinks is wrong.

The DataStage engine uses shared memory with specific addresses, so running more than one instance on a given machine (i.e. one ip address)is not going to work. Actually, with 7.x you can! Not that I'd want to mess with that, mind you, but they have introduced the concept of a "tag" for the primary...

Never had that problem. Don't really want to derail this thread, but you shouldn't have to worry about 'numeric lookups'.

Well, there is a Java "pack" available. I don't know beans about it, only that it exists and may let you do what you want. You'd need to contact Ascential about getting your hands on it. That and to find out the additional price tag, if any.

Export them via the DataStage Manager via the Export / DataStage Components menu item. You shouldn't need a network connection per se to move your jobs to another project, simply connect to the new project via the Manager and then Import your .dsx file.

DISABLE the constraints, don't drop them. Use the update actions I mentioned and then, as Ogmios points out, reenable them when the job is done.

And as noted have a good plan in place in case they can't be reenabled.

And, of course and as mentioned by trokosz, the discussion ranges well beyond just database passwords. The Rule of Thumb should be that anything that can change from environment to environment, day to day, release to release should be parameterized. For databases that can be DSN, Host, Userid, Passw...

The scheduler isn't part of this equation. What matters is how the jobs are run - via a Sequencer, via hand-coding / Job Control or directly via a script and 'dsjob' from the command line.

Each have different mechanisms and APIs for controlling resetting of aborted jobs.

Depending on your database and therefore the plugin you are using, there should be two Update Action options built into your target stage: * Clear table - transactional delete of all records * Truncate table - non-transactional clear of all records You can also do something before-job via a script i...

You can create a routine of the Transform Function type and then run it outside of your DataStage jobs via a Sequencer and the Routine Activity stage. It's a little more generic of a routine, would allow multiple input arguments and would look something like this: $INCLUDE DSINCLUDE JOBCONTROL.H rJo...

I've done something similar by passing in the Job Name, Stage Name and Link Name as parameters to the routine and then passing the row count out as the Answer. You would need to attach to the job, use that handle to get the link information and then detach from the job. This lets you use it in a Rou...

So... if you "don't want" the time portion, set it to zeroes (midnight) by appending " 00:00:00" to the end of your properly formatted date string.

FYI - The output for an OCI Timestamp field needs to be in "YYYY-MM-DD HH24:MI:SS" format. Dashes not slashes.

There is no ".exe" in the strictest sense for Server jobs.

What are you trying to accomplish?

'What is the most efficient way to abort a running job, close the Window? stop it via Director? or ?" Kim has already addressed the Director issue and the proper way to stop a job. I just wanted to address the 'close the Window' comment. I'm assuming 'the window' refers to having a job open in Desi...

Is there any way my entire code can be disclosed i.e where others cannot do a copy and paste of my routine code. If you really don't want people 'borrowing' your routines, the only way to do that here would be to not disclose them. Share them offline with someone you trust, but putting them here pu...