DSXchange

Isn't that exactly where I said?

This suggests that the jobs were exported without design time information. Make a new export, ensuring that you include both job designs, job executables and source code. The last is a check box alongside the job executables list.

Search the forum. You might beneficially include BTEQ as a search term.

Adjust the CREATE INDEX command?

That's not a good example of a default configuration file, since not all nodes are in the default node pool. Also, in the default configuration file, the disk and scratch disk resources are subdirectories in the DS Engine directory. (And it is undocumented.) Based on that, however: { node "...

Possibly.

But also investigate the warning The number of reject datasets "0"is less than the number of input datasets "1".

You could build a server shared container containing a UV stage. Read the end of Chapter 2 of Parallel Job Developer's Guide for the restrictions on what you can do using this approach.

You could use an External Source (or External Target) stage, as noted above.

Basically it is telling you that IsValid("date", Ln_pour_controle.date_creation) is legal but IsValid("date [%yyyy%mm%dd]", Ln_pour_controle.date_creation) is not.

That is, in the IsValid() function, the first argument must be a literal string that does not contain a formatting parameter.

You can remove the uncertainty by using the Expression Editor to build your expressions

Usually "try it". Sometimes called "suck it and see".

Does it work if you replace DRS with Oracle Enterprise stage? If so you've identified the culprit. Otherwise the next thing to explore is the for-Oracle environment variable settings. These can be set via Windows Control Panel (System applet), or as user-defined in the DataStage Administrator. There...

The answer is QS Server, because ultimately you need the server to process the data. However, it's common practice to configure both, so that you can inspect the data (outside of QS) before/during processing.

No it won't - that's why I qualified the query with a following comment. I knew that the field was field number 3, but was unable to remember its name in the dictionary. Arnd has since confirmed that the appropriate column name is NAME. Replace F3 in the UPDATE statement with NAME.

Can you create a new job in the Test project?
How did the jobs that you can not open arrive in the Test project?

What do you see when you View Data on the Sequential File stage? Are there any NULLs being delivered?

Etiquette note: we are an all volunteer site, we reply as and when we can. Requesting ASAP causes offence. If you want urgent support, arrange a premium contract with your support provider.