DSXchange

Or - I assume - use a BASIC Transformer in the PX job, with all the caveats that brings to the table. It's not that Parallel jobs "don't have a user status area" - they do. It's just that it is not quite as simple to get to in a Parallel job as it is in Server.

can u please help in the issue now am in. No, not really. My only goal was to try and set some expectations. And (unfortunately) I still think you are ultimately wasting your time. Hope I'm wrong on that. My C coding days are long behind me and I don't have access to PX here. Others will have to fi...

I don't see how building a C version will change anything about the behaviour of the API as it relates to specific stages. If you are doing this in the sole belief that it will magically start working with the 'dataset stage', I'd be afraid you are going to be disappointed. Contact your Support prov...

Don't you just need to add an XML Input stage into the mix? Have it flatten the returned XML before you write it out to your sequential file.

Have you done much C programming? If this is all new for you I'm not sure this path would be recommended.

Why not continue to use your existing routine? Simple enough to use it as is from a Sequence job or some form of job control. I don't really see any burning need to rewrite it in C.

Sounds like it's time to mark your post as Resolved.

Welcome. Technically you'd need to get the patch from IBM nowadays. This is the official eService website and is where you'd need to have a logon for patches and other goodies. Is this the 'Ascential' you are having trouble with? m If you *are* having problems with that site, as noted on it you shou...

Google, or use your favoritve search engine. All kinds of discussions out there in the wild for the reading, not sure why someone should bang in all that information here. Our friend Vincent has a blog entry on the subject from a DataStage perspective. Give that a read. And I don't really see any ne...

I have substituted the generated query with a user defined query. There's your problem right there. Does it need to be user defined? As noted, you've got a mismatch between the columns defined in the stage and the parameter markers in your SQL - something that cannot happen when the SQL is generate...

Your job sounds a little... destroyed. Did you have space problems? Have you tried recompiling it? Or export/import the source for it and see if that helps.

When you searched the forums here for the phrase 'broken pipe', didn't anything already posted help you?

Sorry, looked up the wrong one. There is a tdatabl.pdf manual in your Docs directory for the Teradata load stage.

Parallel Job Developer's Guide of all places. There's a separate section for pretty much every stage, that one included.

Yes, via the Write Mode options. It's in the documentation.

http://www.duke-consulting.com/Download ... ctices.zip

Learn it. Live it. Love it.