DSXchange

It's not... the answer may depend on what exactly you mean by "define" but as I already noted that can be "any number", i.e. there is no limit that I've ever seen or recall.

Isn't technically the answer 1? While you could have any number of value files created, only one at a time can be associated with a given parameter set. That's what I recall, anywho.

Of course you do.

Yeah, it continues to confound me how many people encounter "special" or even better the so-called "junk" characters and simply want to nuke them. Far better IMHO to recognize what they are as your client's data and accommodate them properly, and which ways to do exactly that hav...

Sorry but of course it's part of validating the functionality of the routine. Would have been good to mention that you'd obfuscated your secret pathname and then I wouldn't even have mentioned it. Setting it up incorrectly could certainly cause the routine to fail, hence my question. :? Once the job...

I'll remove the quotes. Answer #1 doesn't really help, it's obvious that it is a "disk path" but what is it exactly - a parameter you pass to the routine? Now, if the directory is literally called "Basepath" making that a relative path, I would emphatically suggest you switch to ...

also found a lot of information on Dsexchange Ummm... suggest you do NOT go there while at work. :wink: On a related note, a colleague and I many moons ago did exactly this. But it was simpler time - we were generating Server jobs (as dsx files to be imported) from table metadata and the jobs were ...

I await the outcome with baited breath!

I'm curious... 1) What is "Basepath"? 2) Are the double-quotes you included actually in the routine? 3) What ends up in the job's log? Can you copy/paste it here please? Where you built the routine there should also be a 'test' button/option, I don't recall if it lets you test Before/After...

Well, there's always something like this but it isn't all that helpful IMHO. And any official Oracle documentation I could find back then like this one all discuss its use in the JDBC drivers, so not sure how valid changing it is unless you are using them. Seems like a question for support. And no, ...

To me, this is a classic case of using BYTE syntax for a column like this when you really shouldn't. IMHO it would be worth asking your architect / DBA if it can be modified to use CHAR syntax instead so it stores 4000 characters rather than 4000 bytes in the field: From BIG_FIELD VARCHAR2(4000 BYTE...

Do you have the Stored Procedure stage set to "Target"?

Since it would seem you are no longer as Premium as you used to be, I've opened up my previous message so you can see the second question I asked.

What about that processing needs two nodes, let alone a Parallel job? Either run it on a single node, or force the target stage to run sequentially or just use a dang Server job.

Help us out here, I'm curious about a couple of things. One is when you wrapped it in a script to call from DS, if you run the script from outside of DataStage does it work? Hopefully the script makes no assumptions about the environment or the CWD or any such thing. Secondly, could you elaborate a ...