DSXchange

anandapani wrote:Then design team concluded that, this is because of server routines called from the BT of the parallel job, which are running in parallel when job run in muliple instances.

This conclusion seems highly suspect to me as well.

That all sounds correct to me. So, when Job1 aborts if you don't get a '3' passed to the second job I'm not sure why that would be. Seems to me that you should involve your official support provider.

That's what I was thinking... but you could strip the spaces for the sort key and leave the original field intact as data so there's no need to try to rebuild it.

You actually are using "Job1StageName.$JobStatus" yes? Pick it from the (...) external parameter helper, don't try to type it in by hand.

I completely and whole-heartedly agree with Mike. Just because you have the Enterprise Edition does not mean that everything must be a PX job. Both weapons in your arsenal have strengths and weaknesses, use the appropriate one for the appropriate task. And for goodness sake, don't think your first o...

Saying "I'm not able to" doesn't help us help you. Why not? What exactly are you trying? How have you implemented this? What happens?

Set up boolean stage variables, one for each check, using functions like Count() and then the constraint would reference them: svOneDot: Count(YourField,".") = 1 svNoSpace: Count(YourField," ") = 0 svLength: Len(YourField) svLengthOK: svLength >= 7 and svLength <= 70 Contraint: s...

Ah... cool, thanks.

Assuming DSND = descending, but "EXP"?

That behaviour has been reported here before, from what I recall.

That's the way it works, I'm afraid - no matter where / how you run a MI job, you can't see performance stats in the Designer as it can only display the 'base' job and not the specific invocation that is running.

Hmmm... what database? I honestly don't recall having to do anything special for Oracle but perhaps things change in other databases. Or I'm wrong. :? Also realizing that I've been thinking of the SP stage in a Server job, perhaps it being in a PX job also changes the rules. Hopefully someone can sh...

How are you 'converting it to varchar' in the transformer?

1. Not really a DataStage question 2. Documented in the Parallel guides, from what I recall From the questions, it sounds like these 'Server' routines may not need to be converted at all. Typically routines that call out to the O/S or leverage the API for job/log information are used before/after jo...

What version of DataStage? What operating system? Parallel or Server?