DSXchange

It's a placeholder for the sign, space means a positive value. Does it actually hurt, cause an issue? My understanding is if you need to get rid of the space, you'd need to make the flat file target field a string. Or there may be an extended property to tell it that it is not signed. Not positive. ...

An internal error would typically indicate a bug, requiring help from support and probably a patch as well. Hence the suggestion. But perhaps someone has faced this issue and has a different solution...

Suggest you start by reading the documentation.

Meaning, perhaps it behaves differently. As Ray noted, sounds like one includes executables / binaries (etc) and one does not. Which is also why the /EXEC question came up.

So why not simply "report to IBM with log files"?

Methinks he is saying it is not 'the same command'.

So... bug. Really, really persistent prehistoric bug.

I changed your initial post's subject to something more problem specific, not sure why you felt the need to edit it and change it back to something so... generic.

Actually:

No, there's nothing special you need to do. DataStage is a client just like your Developer tool - both send the SQL to the database and it sends back the results. If you are certain the SQL is the same then perhaps they are not connecting to the same instance. Been there, done that, got the t-shirt.

Best to start by posting in the Server forum. I've moved you there. Also known as 'here'.

Secondly, no. What's different about the SQL in the job versus the tool - parameters? Look at the detail in the job's log to see what was actually executed.

Just for grins, can you confirm for us what your understanding of "sourcing dsenv" means?

Right. Posted it in all caps for a reason. :wink: At least this confirms they are still dynamic type 30 hashed files and haven't mysteriously been converted to something else. As noted, suggested a long listing so you could see the sizes of each and also how much has possibly skewed into the OVER po...

These tables are not things you just want to start deleting. If you're not sure which job is #582 (to use your example) run a query against DS_JOBS. Off the top of my head, something like: SELECT NAME FROM DS_JOBS WHERE ID = 584 I'd also be curious what files are in the directory when you do a "...

So are you saying that you think these function calls "should be able to complete in fraction of seconds" because they do in other environments? But in this one, whichever one this is, they take much longer? If that's the case, you really need to dig into discovering what exactly is differ...