DSXchange

Or you could just delete and recreate it, I would think.

Well, 'better' is a pretty subjective (and relative) term. Some organizations may feel it's better to use other existing tools, but Version Control is bundled with DataStage and is well integrated into the suite. It sure beats the heck out of the original process of 'releasing' and 'packaging' jobs....

Good eye! I didn't notice the JonHandles.

Ok. I get those at times using 7.0.1, typically when I've use a connection for multiple things before trying to debug a job. Usually can be 'worked around' by opening a new Designer session and doing the debugging of the job in isolation.

Post your code.

The best way to resolve the problem is to ensure your jobs do not log any errors. Seriously, this should be your goal with any job and running with all of your jobs set to unlimited warnings is asking for trouble. I hope you have plenty of disk space whereever DataStage is installed. That being said...

Are you saying it's broken, Ray? In what version?

It looks like it was caused by the next error logged:

ORA-24329: invalid character set identifier

What? You don't sound too! excited! about! all! this! Vince!

At least there was a plus side.

Welcome. :D You can't stop the stage from creating the file, it does so when the stage cranks up or 'opens'. If you don't write to it, what you are left with is a zero byte file. As you've found. Given the path you've been taking with this, I'd suggest you write your output file to a different name,...

Chapter 2 of the help (either online or pdf) is the Methodology chapter and gives you a good grounding in how the tool is meant to be used. The rest of it gets into the details of Initializing objects into the Version Control project from Dev and then Promoting them from there into Test and Producti...

Convert and Ereplace are two of the weapons of choice here. Searching the forum would turn up several examples like this one.

So, is the target an Oracle DATE field? If you treat this as a Timestamp in the job and make sure it looks like YYYY-MM-DD HH24:MI:SS when it gets to Oracle, you should be fine. This also assumes you are using an OCI stage to write to the database, that or the DRS stage set to Oracle.

More information needed. * What format is the date stored in in the hashed file? * What format is it in when you send it to Oracle? * How is it defined in your target - DATE? TIMESTAMP? * What datatype did you define it as in your job - Date? Timestamp? Varchar? What size? * What kind of transformat...

Well, your first issue is going to be the fact that XP of any flavor is not a supported Server platform. Client, yes - but not for the server. Didn't say it can't be made to work (have no clue, actually) but you'll have to face that hurdle when attempting to get any 'official' support for it if you ...