DSXchange

And you are the same as the original poster? As noted, you cannot use a routine in a trigger expression. The ellipsis 'picker' thingy may let you pick one but they cannot be used there. And now you've see the error generated when you attempt to. You should be using a Routine Activity stage to call i...

Yup. A LONG, eh? Yuck.

What do you mean by 'job activity custom conditon'? A routine would be leveraged via a Routine Activity stage, not a Job Activity stage or in a Trigger expression.

Hmmm... perhaps. The 'every' or 'daily' schedules would be support by cron and thus would be able to handle multiple occurrences. One time schedules are handled by 'at' and perhaps it can only do so once per job. I don't recall ever having that problem but then I've never used DataStage on AIX and p...

Before you go too far, you've never said what kind of "queries" these sets are. Insert/Update DML? Then your sproc idea could work. Select type stuffs? Not so much.

http://www.dsxchange.com/viewtopic.php?t=119595

But the question asserted that Job2 was MI, hence the answer. And for a static four instances the solution is simple. Adding in the 'dynamic' part after the fact changes the problem. To use a Sequence job in that dynamic scenario, seems like you'd need to know the maximum number of instances and add...

Exactly, four Job Activity stages for Job2, each with a unique InvocationID.

dsdskche.pdf

The only way to not commit is ensure the job aborts, otherwise your changes will be committed. And I don't see how not committing helps you test much of anything. What I do to test the validity of a data stream when I don't want to actually affect the database is replace the DB stage with a Sequenti...

Excellent. You'll find all kinds of 'similar but different' tasks that stage variables are suited for. Me loves them.

It would help if you explained exactly what is 'not enabled' in your environment after installing RTI. If you don't get all the bits installed right, it cannot be enabled in jobs. Or you may be asking about the WSPack functionality that Ernie mentioned, which is separate from RTI.

I've never had a need for the Row Splitter stage. My preference would be the same as Ray's.

Ask IBM.

No worries, always more than one way to skin the DataStage Cat. And now you're a stage variable veteran to boot!