DSXchange

Probably not, as we're talking specifically about the Execute Command stage in a Sequence job, so... ah... hmm... You may very well need quotes here because of the 'long filename' you are using, specifically the directory name with the spaces in it. So sometimes you need to put single quotes around ...

Still, it will not do that during an Initialize. There are other ways than VC to get a job set to 'Read Only', could be something/one else is the culprit here. Perhaps a check of DS_AUDIT would provide a clue.

While Index() may find it, you'll need to use Field() as noted to actually extract it. Easiest way, that is, not the only way of course.

Nope. So it's a fixed-width file? Or did you mean you used the default delimiter in the creation job? Regardless, you need to match the definitions in the stage to the actual file, nothing more or less will work.

FMT() doesn't work in a parallel job? That's too darn bad.

You will not be able to achieve this without stage variables. And yes, parallelism / partitioning could affect this.

Better if you check the documentation noted and ensure your server is setup correctly, environment variable wise. All those messages confirm is that it isn't.

From what we've seen here, best to get off of 8.0.1, fix packs or no, and on to 8.1 at your earliest convenience.

I'd start by checking with your DBA. Perhaps a permissions issue?

First off, how have you declared the DATE field in your job? As a Date, Timestamp, Varchar, what? It makes a difference. And what does your SQL look like, with regards to that particular field - a straight select or are you using a TO_CHAR() to format it? I would suggest, since the target is apparen...

I'm at a loss here with what to try next. If you are certain that it works with hard-coded values and yet doesn't work when those exact same values are parameterized, I'm stumped. Have you involved your official support provider yet? Had another set of eyes double-check everything for you? :? Can yo...

It won't do anything like that on its own, that means someone has accidentally promoted it back to the dev project. Check the history in VC, the event should be visible there.

Not that I've ever done that before or anything.

You'll need to define the output field as a string, then use something like FMT() to get what you want. There are other ways, I'm sure, but that's the first that comes to mind.

Since this seems to be a known issue, best to contact your official support provider and see about getting the patch(es) Mike is talking about.

What does your official support provider have to say about this issue?