DSXchange

Nageshsunkoji wrote:I am not trying to violating any datastage rules

I know... and I didn't say you were. And you've already done what is basically the right thing for this, post an Enhancement Request on the subject.

Here's a couple of suggestions. 1) DON'T SHOUT, it doesn't help and is generally considered rude. People will help when/if and as they can. 2) Spelling is good. There's no such word as 'UR'. Is it really so hard to put the 'Yo' on the front? This isn't your dang cell phone after all. Now being said,...

Nageshsunkoji wrote:If rules are rules then rules for all.

Perhaps in a perfect world. However, we have to live with the rules we're handed and deal with this as they work, not as we'd like them to work. Otherwise, we come off as a little... whiny.

Curious why you would need one in internal format? What are you planning on doing with it in that state? Typically you would convert the two portions separately using IConv with 'D' and 'MTS'...

Where do you need help - the "in parallel" part? Just put the 10 Job Activity stages in the Sequence job without linking them together.

I would guess that Avishek is not familiar with Universe from the comments and questions on this subject we've been seeing. Or at least not familiar enough to be attempting something of this nature. Nothing against the OP at all. It's just that I for one would be reticent to just hand over answers f...

XML can be discussed off in any of the 'normal' DataStage forums, I would think. Or even here if it's RTI specific. We're just about to 'Go Live' with GEAX and it actually seems to be well in hand. Even had Micheal Hester out for a stint and he checked things out and agreed that we're doing pretty d...

I have seen you activly responding for most of the topics, I appreciate it and thanks for the quick (sarcastic) response. Didn't realize this ever got replied to until I saw Ernie make his grand entrance and lay some much needed RTI wisdom on us. Sorry, it was one of those long days with no end in ...

With RTI, DataStage understands when a single "message" is complete, allowing you to utilize the Aggregator and other such stages. Interesting, not something I was really aware of. I was under the impression that stages that do their dirty work when the input stream ends could be... less than funct...

These

chulett wrote:Create a standard routine that executes shell scripts. Then a Sequence job with a series of Routine Activity stages can run them. Or code a series of DSExecute calls into the Job Control tab of a Server job and run that.

also were solutions offered to you.

What exact version of DataStage?

Was wondering the same thing...

DB2 'file'?

Are you asking if you can update a field in a table without knowing the original value of the field? Do you mean something like this using standard SQL:

All the other jobs are working well we have client oracle 8 installed on the machine. Sounds like you used to have an Oracle 7 client installed as well, and it no longer exists after you 'cleaned' the pc. Can you reinstall the 7 client? Or perhaps covert the jobs to use a different stage? I'm assum...

Odd... my understanding has always been that you either get one or the other - which makes sense as your Server is installed on one or the other.

Can you check your ExecDOC routine and see if it is 'standard' or something new someone whipped up?