DSXchange

'' != null

evee1, why don't you start your own post and tell us the details of your particular issue?

Doesn't change my answer.

Reset the aborted job and let us know the contents of the "From previous run..." log message if it shows up.

Perhaps a umask issue with bchuser, if not now then at some point in the past?

I've always used "pathed" hashed files which allows you to move them out of the projects, ideally completely out of the partition where DataStage is installed. Filling your DS partition is a Very Bad Thing.

Again, if the older version jobs were imported into the current version, they were converted during that process. The "inside" directory may very well be some kind of DS6 backup, stashed there for some odd reason. Others may be able to tell you how to check their "version" via a ...

Still confusing. These "two separate directories" are two projects under the same server installation, your 7.5 version? Or do you actually still have a full copy of the 6.x engine installed?

If jobs won't run at all, involve your official support provider. Also, make sure you have all of the fix packs for 8.0 installed, that or upgrade to something more viable (like 8.5) as 8.0 was... buggy.

So, nothing to do with skipping the header and you're already doing that it seems. If you have an import error then you need to post it (copy/paste) before anyone can help.

Not quite clear what you have. If your "DS6" jobs are in a "DS7.5" project, they are 7.5 jobs now.

I would imagine that, with a little thought, you could use a UserVariables stage to build a delimited list of parameter values and then refer to it with the loop counter.

From what I recall they don't have PX licensed, hence my earlier comments.

Moved and updated.

By "easier" I assumed they meant without having to create 600 jobs.