DSXchange

It would be best (and help future searchers) if you actually posted the resolution rather than just the fact that you resolved it.

It doesn't "work fine" with both -wait & -jobstatus as they are mutually exclusive. Read about the difference and use one or the other. Not saying that's your issue but it is an issue.

I would first ensure that the dsjob command you are running in the script actually works. Have you done that? Run it directly from the command line?

No, they just need the scheduling user added to cron/at.allow, something that doesn't typically happen 'out of the box'.

How many nodes does the job run on in QA?

Get authorized. Talk to your SysAdmin. Make sure you have cron access as well while you're at it.

No, just one XML Output stage is needed. Combine the two fields and send it in just like any of the true source fields and declare it to be the Trigger.

That sounds like a good start. Now that we know you want to store rather than parse it, can you tell us what 'store' means here? Where / how does it need to be stored?

Create a new column which concatenates those two fields and use it as the Trigger Column, don't include it in the outgoing XML by leaving the XPath Expression empty.

Rather than run around and ask the same question over and over in other people's posts, best to come back here where you've already asked it and bump this one. However, I believe the answer is that it can't be done from the command line, that it is as you've found for jobs only. Could be wrong, of c...

Just Ray being Ray, I believe... you should be able to relate.

ray.wurlod wrote:Google will help with the first part of the question.

As will whomever gave you the requirement - Data Modeler, Architect, ETL Lead, etc. Actually they should be able to answer both questions... except for perhaps the "in DataStage" part.

For the record, we were using it for the 7.x release and didn't have any issues with it.

The "bitness" of the underlying operating system plays a role as well. I've had to help people who learned the hard way that just because it runs fine in your 64bit development environment doesn't mean it will continue to work in your 32bit production environment. Don't ask me why they set...

If everything works other than the 'test connection' option, that smacks of a bug to me and something you should report to your official support provider.