DSXchange

Not a DB2 person but taking a stab at this:

1. I would think so, it is perfectly feasible in the Oracle world.

2. Forget the 'different dsenv' approach, accomplish this via environment variables in your job which override the ones you need to be different.

3. No, not here, they're only for ODBC.

So... the existing job runs fine but the copy doesn't? What's different between the two?

So... you get this with all datasets or just one particular one? And the 'other projects' comment - you can view this dataset from other projects?

Actually, please refrain from posting at all in ALL CAPS in any capacity, on the Internet (not just here) it is considered SHOUTING and we like it when people use their inside voices. Unless, of course, you are really really mad and feel the need to shout at someone.

Edited to make that point a little... clearer.

Simple enough, what have you tried? Read up on the Start Loop and User Variables Activity stages in the Designer Guide, they are what you will need for this.

Why not post what it is you are trying to accomplish, instead? For example, what is this routine meant to do?

Oh, and there's always this but you'll need a Premium Account to see all of it.

What was 'text' supposed to accomplish? Did you perhaps mean 'ascii' instead?

Please mark your post as Resolved using the button at the top of the page. Thanks.

You do it the same way you would do it anywhere else, with the help of a properly configured TO_DATE() function. The stage can automatically generate that for you.

naveen19 wrote:Siva,

This not possible...

whether this interview question ?
:D

If it had been, you would have gotten it wrong.

I am on a Server Edition... Yet another reason that you don't have the "same" error. It may be similar but it cetainly isn't the same. And the proper thing to do here, as I noted earlier, is to not hijack someone else's post but instead start your own in the proper forum (which is not thi...

I've never tried but would be reluctant to rely on DSJ.ME for anything other than the job handle. So, in my mind, when you do either of the following: DSGetJobInfo(DSJ.ME, 'dupCheck', 'insert', DSJ.LINKSQLSTATE) DSGetJobInfo(DSJ.ME, 'dupCheck', 'insert', DSJ.LINKDBMSCODE) Your call is syntactically ...

I do a "dsjob -jobinfo" first and grep out the "Job Status" line. Then you can check for does not exist, running, or aborted. Fail on the first two, reset on the third then run, else just run.

SQL*Loader-937: parallel load requested and name has enabled triggers or constraints Cause: A request was made for a parallel direct load, but the object to be loaded has an enabled constraint (check, referential) and/or enabled triggers. Action: Disable the offending enabled constraints and/or tri...

Perhaps when you reset a job that doesn't need it? Our scripts check first and only issue the reset when appropriate, haven't seen that issue that I recall.