DSXchange

Care to post the warning messages? And using Oracle, it doesn't log any warnings or logs them but doesn't abort?

True. From what I recall it generates a list of job names in the category and then exports them one job at a time, appending. The key still being one job at a time.

You can't - one job or the entire project are your two choices. You'd have to use the GUI to export a folder / category.

Then post the actual, unedited error from the log.

Then we know that's the actual row being processed. You need to keep digging, find out what is causing this, we've checked the common stuff. Could be your data is not as clean as you think.

Both topics - migrating from 7.x to 8.x and migrating from Windows to UNIX (or vice versa) - have been discussed here quite a bit, something a search would turn up. Also note they'll still be Server jobs, the way to migrate a Server job to a Parallel job is using wetware - i.e. a person needs to rew...

Sure, any valid sql can be used. Check the query outside of DataStage first, make sure it runs properly before putting it in your job.

If not already, set your Array Size to 1 and rerun, let us know if the logged "value of the row" message changes.

From what Ernie has posted, there are namespace bugs in the early 8.x releases. What exact version do you have? What patches / fixpacks have you installed?

As noted, try a search for General repository interface 'other error' and see if anything found there helps.

User-defined sql? Make sure there's no semi-colon at the end. Using job parameters? Make sure all are properly spelled and cased, if they don't resolve the # will cause that error.

Have you tried dragging the table metadata from the Repository browser to the link from your database stage?

Match your demand to what can be supplied. If your server doesn't have the resources to run those jobs in parallel, sounds like you'd be better off running serial - at least those 15 would finish in 5 hours that way. Or run fewer simultaneous instances.

Out of curiousity, which way are you trying to go? Method 1 is a basically a 'get' and Method 2 is a 'put'... or are you just trying to illustrate that neither way works? Can you manually perform these same actions from the command line of the DataStage server to/from this remote server?

That's a bus error and no-one can help without you providing more information. What's your job design? What have you tried to fix it? Also, please post the complete, unedited errors that get logged.