DSXchange

Run it just like that from the cmd line.

No, nothing 'out of the box' except by hard-coding it into the derivation while you're in there.

No, but you could copy it and create your own custom version that does that.

Meaning the SCD stage supports them natively, but a Type 3 would be easy to implement.

No worries.

For the record, relative paths are relative to the 'current working directory' of the job that creates them, so that means the path starts from the job's Project directory.

Sure, with Convert() for example... but why? They're not really equivalent and a better solution would be to load them as is. What issue are you having?

OK, I'll bite... failed how?

Any idea what they changed? Would be useful information to have.

I remember what you are referring to, that was a different error however. Never seen yours mentioned here before.

Possible? Yes, I would imagine so after editing the version in the dsx. Recommended? I highly doubt it.

Ack... mea culpa... was thinking 'wildcards' when you said 'regular expressions'. Does that work from your O/S?

Where are you looking for the file?

As noted, you need to shine some light on the specifics of your error handling design, triggers etc, before we can help.

Short answer is "yes" and quickest way to test would be to try it.

can we run the ds jobs on unix from any locations/path or do I need to run from the specific location That's just 'command line 101' stuff. If that directory is in your $PATH then you can 'run it from anywhere', else you either need to specify the full path or sit where it lives to run it and (poss...