DSXchange

True... and thanks Ernie, didn't think to poke around in the Toolbox.

Quite the opposite, actually.

No clue, you'd have to ask IBM how known it is, 7.1 is pretty darn old now and I don't recall what all didn't work properly there. :wink: Do you really need to delete it each time? Perhaps just clearing it would help. Unfortunately, you're going to need to nail down what the failed runs have in comm...

That's not what the bit you quoted is referencing, Andy. That "URL" comment just means you don't need a landed file for the metadata, you can get it directly from the source URL. It just plain old doesn't support it.

Heck, I'm not working for that client any longer and I forget what we ended up actually doing for this.

Tell us what you mean by needing to "suppress" multi-byte characters.

It will create the DSBackup directory automatically, so it's not like you have to pre-create it or anything. Make sure that you have the permissions that you would need to create/write to that directory and to overwrite any current backup copy that might already be there.

Yes. All you need to do is add them as User Defined Environment Variables to the Project.

Yes, I'm sure lots of people could.

Never heard of it.

You need to be careful, these all look like interview questions rather than actual problems you are having and that kind of thing doesn't go over well here.

Basically it just means the job blowed up. 'Phantom' is the term for 'background process' here, which is how every job runs so it can disconnect from / not be tied to the client that starts it. That's also why the 'communication area' that it uses is named &PH& - that PH is for Phantom. :win...

Not positive but have you ensured your NLS maps in your dev jobs are set to 'None' or whatever it is that "turns that off", so to speak?

Your client should consider the 'Professional' version of 7 which includes a virtual 'XP Mode' which is specifically there for business applications rather than the XP Compatability mode like you'd use for games and such.

And this is version 7, not 8, yes? And the job status changes like it should to Running and then some form of Finished? What do you see in the Monitor while it runs?

Perhaps you're not looking at the correct log? It happens.

What happens if you run the job from Director?

Ah, OK, gotcha. Assuming a single unique occurance of the string to be removed, otherwise you'd need some kind of lather-rinse-repeat loop until it no longer found anything to do.