DSXchange

Well... I've done this in the past, but not recently so bear with me. An aggregator will get you the pieces that you need for the header and trailer records per grouping. Your example of the extract output seems a little odd to me, shouldn't it more properly be: HDR 111 DTL 111 PAT 100 DTL 111 ABC 1...

Which ones can you see but are grayed out? Perhaps those are the Server Only plug-ins, as not all are valid for PX from what I recall.

Upon further review, there could be an issue with the concatenation in addition to my previous post. Do you know if each record is delimited, meaning there are EOR characters at the end of each record? If you do a 'wc -l' on the file, does it show a 1 or something else? I'm wondering if there will b...

can any one suggest me how to tackle a file with no delimiter. something to do with the properties of before job subroutine i guess or whatever, please help me. i am stuck in my project. It should have nothing to do with your concatenation or before job subroutine. It's all about properly defining ...

Odd that you would have to get a patch to enable something like that. Seems like pretty basic funtionality to me...

Excellent! Just as an FYI - there's no reason to use User Defined SQL just to add the DISTINCT keyword. I know I sound like the proverbial broken record here, but I champion (and enforce) the use of User Defined or Custom SQL only when it is absolutely needed. In other words, only if you've got no o...

Your SQL isn't correct - in order to get distinct values of two fields, you need to group by both fields. Which is basically what the error is telling you.

Same here. And in the meantime, perhaps I'll hold off on any upgrade to 7.5.2 I was contemplating...

:D No 'Kung Fu' fans over there, eh? Too bad...

Then I'd say it's time to open an official Support case.

The literal answer to "can we use the parallel jobs in server edition" is no. If the question is "can we only create the parallel job in enterprise edition only", the answer is yes.

But keep in mind the fact that in the Enterprise Edition you can also create Server jobs.

It's not about compiling or the fact that it's Read Only. There is a Transform sitting over those routines so that overrides the ability to pick the Routine directly.

Seek it under DS Transforms, Grasshopper...

Nobody uses VARCHAR in Oracle.

No, that's not what I meant... I meant exactly what I said. If you have the ability to create PX jobs, then you have the Enterprise Edition of DataStage. The Enterprise Edition supports both Server and PX jobs, created using the same client tools - Designer, Director, etc - all work for both Server ...

DataStage 7 dot 5 dot nothing? From what I recall, the original 7.5 release was a little... wonky... and it would behoove you to get the 'latest' point release - at least 7.5.1A unless 7.5.2 is available for your platform.

Not saying that is the cause of this rather odd problem, but... ??