DSXchange

Second question first - no, they don't need to be compiled. Now, for the first - by 'folders' do you mean Categories or do you mean literally folders/directories you created at the operating system level inside the project directory? If you mean categories, then yes an export always includes that in...

There is no such thing as a Project level warning limit. You can set it as a default for your Director client but that just affects jobs you run manually. Otherwise, unless specifically overridden, the default is 50.

Never heard of such a bug or the need to "use environment variables always". :? Rather than cluttering up someone's lovely migration thread, why don't you start a new post on the topic of this issue and we'll talk about it. Please include lots of gory details when you do. In the new post. ...

No, not true. While it is easiest to create a message handler from an existing message, I don't believe that you actually need one to do it. I also wasn't aware you could demote a Fatal error like that but then I've never really tried to either, preferring instead to not causing the fatal error in t...

If you create a new job from scratch with a BASIC Transformer stage in it, does it work correctly or abort as well?

So... you have to specifically tell it to use a particular values file at run time each time? There's no concept of a default 'always use this file' file here?

Server job, so if you really want a 'multi-row result set' you'll need to use an ODBC or UV stage.

OK, my information seems to be specific to Server jobs... and your list of types in your project don't seem to include any PX types. Are you sure there are Parallel jobs in the project you queried? :? Edited to add: I've just queried one of my projects for a list and it too does not list the PX OLET...

Where are you getting these OLETYPE values like "PxOdbc" that you are looking for? :? From what I recall, database stages will have an OLETYPE of either "CCustomOutput" or "CCustomInput" depending on it being on the end of an output or input link and you need to check a...

But in the end they're all just different releases of the same thing.

Parameter sets in each project have a default value file associated with them, do they not, assuming you've set that up? If that's the case there's no reason to pass anything from the command line unless you need to override the job to use a different value file for the run, I would assume.

Windows has scripts, they're called batches, you just have to learn that DOS style of scripting with ERRORLEVELs and all that jazz. So, you aren't using sequences or you can't use sequences, it would be pretty simple to get a timestamp there (in a routine or execute command stage) and then to pass i...

[crosses fingers]

That's a good next step but you MUST ensure that there are no other processes of any kind in the project.

No, it has been talked about ALOT and that 'timeout' limit is hard-coded in the engine, which a search here for that message would reveal.