DSXchange

In other words, unless you have an 8.x version you need to purchase RTI/SOA in order to expose jobs as services.

Oh my, not even close to what you needed to do. Drop the test project, recreate it empty and then populate it from a production export.

47shailesh wrote:I have recently refreshed Project from Production in Testing env.

Explain to us exactly how you did this 'refresh'.

What happened to the %s?

Not sure why people seem loath to do this, but go have a chat with your DBA. They LOVE helping with stuff like this.

Patience, GrassHopper.

So... no questions, just a post to let us know things you're trying?

ps. A 'reference lookup' doesn't count as an 'input link', hence your need for a second transformer.

Exactly. If/when that fixes your problem, please mark the topic as Resolved.

'Real time' would imply the need for whatever they call SOA/RTI nowadays in 8 - I don't recall the new acronym.

Seems like you would be able to build an RTI enabled job, which could run continuously and process those messages in real time.

I'd be careful there. Anything that resolves to 'true' is the same as not having a constraint and - in a Server job at least - will result in an 'infinite' number of records generated. I would suggest something specific, like:

I can read. Still unclear as there's no specific mention of any script. Sounded to me that all they put in the 'Input Value' field after setting the 'After-job subroutine' to ExecSH was 'parameter+1'. Hence the rather generic answer I gave in the hopes of garnering something more specific when that...

They'll know this, but specifically your scheduling user needs to be added to 'cron.allow' and 'at.allow'.

Even though the job is in aborted state and if we try to reset it knowing that we dont have c++ compilers not installed,will it get reset and will execute properly ? Asked and Answered. More than once. Yes. But in this regard, When i try to reset the aborted job ,I am facing the Error Messsage as :...

Director log (OSH script) doesn't show the final SQL, it shows the SQL with parameter. If we were discussing a Server job here, that - the 'non translation' of a job parameter in the logs - would imply the parameter name didn't exist in the job. Is the same not true here? How, in a PX job, does one...

As noted, on the surface that should work just fine. We'd need specifics of the problem/abort to be able to help.