DSXchange

Can you use a Server job for this, that would be fairly simple to build. Or are you one of those shops where only PX jobs are allowed because Server jobs are some kind of evil?

Rather than hijack / sidetrack someone else's slightly related post, please start your own.

Sure but it really depends on when you need to do this. A custom routine in BASIC using DSExecute() would be fairly simple to build and could be called 'after job' but you'd have to let us know how that would work for you, timing and/or process flow wise. How were you planning on implementing your d...

:idea: If this is all too much, how about at least addressing where LOCATION comes from? Is this a singleton value, such that once you somehow know what it is "for this run" you can compute the VARIABLE value and then use it in a select statement in a job to grab and process a bunch of dat...

What you posted is *still* confusing and shows a lack of understand of how the tool works. Still... let's keep trying... 1. It doesn't need to be an environment variable, just a simple job parameter could work. 2. In my example, "p_VARIABLE" was not a stage variable but yet again a simple ...

I do not know why there is so much confusion on these Topic. Simple. Because, in all honesty, you've done a terrible job of helping us help you and explaining clearly what the heck you were/are trying to do. Maybe it's all me and I'm being especially dense or something but I honestly don't think so...

Yes. Clarify your issue, especially your Write Method setting.

dr.murthy wrote:... it takes 10 sec in data stage with auto partitioning where as ...

Guessing that the Job Type is mis-marked. And that you know that and are making a point.

Yes, and you have all kinds of options to accomplish that. Bottom line, you just need to run "DEL <filename>" from the O/S. This can be done in a custom routine, before/after job directly or with a script, in a Sequence job with the Execute Command stage... etc etc...

Exactly. So... you need to build this SQL string. Check, fine, simple. The question still stands - then what? How are you planning on executing it? :? This is a 'select' as in source query, so running it once for every row passing through your job doesn't make much sense unless you're only processin...

Not just from that message... how exactly are you 'calling one job inside another job'? Are there any other messages logged, parent or child?

When you attach to the multi-instance job, are you specifying the invocation id and a dot along with the job name?

handleJob = DSAttachJob(JobName.InvID, DSJ.ERRFATAL)

Why not ask whomever wrote that? Get their reason for saying that. Where did you see it here?

I'm assuming the 'question' was here rather than in an interview, so... I would think by "stage" they meant "land", to me that would be a more appropriate word.

Why were you using the DIGITS transform for that kind of data? Do you sometimes have something other than digits in there? It really was meant to do something like this: DIGITS("(303) 555-2201") = 3035552201 I don't see the need with the data you posted. Just set the data type appropriatel...