DSXchange

First off, customizing the stylesheet has nothing to do with having (or not having) an xsd. Did you read the appendix I mentioned? There is a section there called Accessing the Generated XSLT Stylesheet which explain the rather simple steps required. I'm not positive but tend to agree with you that ...

Right... they are called 'soft returns' from what I recall and you'd need to use a hex editor to verify their actual ascii value.

Absent, missing... picky, picky.

Wow... a Quadruple Hijack! Haven't seen that before - that gets you a 10.0 from this judge! :D

Assign $ReturnValue<1> to the job parameter. Use the ellipsis (...) to start it off rather than attempt to hand type the whole thing.

There's another version of this thread here (somewhere) where this was mysteriously resolved.

I was guessing that, when you were doing all of the work in one job, that your two links - the one for deletes and the one for inserts - were going to two separate Oracle stages. If so, this creates two separate sessions / transactions that have no knowledge of each other and is the typical reason f...

Welcome aboard. :D Can't help on the 'runLocally' issue, have you tried searching the forums for that error? If that doesn't help then perhaps a call to your official Support provider is in order. On the subject of 'decent documentation', I'm assuming you've read the XML PACK Designer Guide pdf in y...

Well... thought you were going to go off and whip up a custom stylesheet, what happened to that effort? Recognize the fact that you haven't said what your issue is, exactly - all you've said is what you have to do. What have you tried? What didn't work? Examples are always good. You'll need either t...

Arise, sleeping thread! Arise!

My 'fix' was to supply the missing .developer.adm file in the Project from what I recall.

It's easy enough to get the version of the JRE that's embedded in DataStage but the parser itself? No clue. Both questions will probably need to be answered by IBM Support.

The answer depends on the datatype of the field in your job and if you are generating sql or have rolled your own.

You do realize that your 'Option to use both parallel and server jobs' comes at a price? If all you have licensed at the moment is the Server component, then an upgrade to the Enterprise Edition (which is what gets you PX) is neither free nor cheap. The upgrade to 8.x (with again just Server license...

I myself dont like the job design but I am comparing dates in my job and doing a (internal date - 1) in the job to get the previous day date, And I am "SUPPOSED" to stick to this job design. All the jobs are designed like this so ppl dont like me changing the structure for 1 job. That's all well an...

Erk. Not an approach I would take. We have a couple thousand jobs and I can count on one mutated hand how many have IPC stages in them.

You shouldn't use internal dates with the OCI stage. It may 'seem' to work but I seriously doubt it is. Stick with your external representation and let the normal TO_DATE() function handle the coversion for you in the generated SQL.