DSXchange

Try Convert() instead and see if that helps. If not, post the log entry that shows the Execute Command results and the returned value.

Sorry, but finding an old post and saying you have 'the same thing' is singularly unhelpful. Please start your own post and describe in detail your issue and the job design you are seeing the problem with.

Didn't mean that either one of you actually said that. It just seems to me that we're already well past the point where this should have been handed off to support or at least have them involved as well.

Probably ODBC. Or run it from your command line using whatever option you have there, such as sqlplus for Oracle.

Nothing needs editing in the 'branded' directory. Plus you need to edit the uvodbc.config file in each Project directory you want to leverage the connection from.

Then time to mark your topic as Resolved using the button at the top of the page!

In other words, be patient. The Server Sort stage is not the speediest animal on the planet.

This is indeed probably the case. Either use the <1> syntax noted or use Convert() to remove the @FM characters.

I know a stored function can be used there, not so sure about the stored procedure, though. As long as you can 'select' from the sproc in a standard sql format, then I would suppose it would work.

In other words, refer this to your official support provider.

and claim_date=trunc(sysdate)-1

If it's anything like an Oracle export, you'd need to read it with a Sequential File stage as one long varchar and then identify and parse things from there.

I know, which is why I asked why one would 'need' such a thing.

ray.wurlod wrote:Even easier is this approach. Use the Multiple Job Compile tool and check the "select only uncompiled jobs" check box.

True... except for the apparent need to schedule this so as to run unattended.

nagarjuna wrote:Use : -jobstatus in tandem with dscc .

Small correction: "-jobinfo" as there is no "-jobstatus" option.