DSXchange

The best source of information is the vendor from whom the product was purchased, and who should be providing first-line support.

It then becomes their problem who to approach - in their place I'd first be asking IBM, not Microsoft.

Welcome aboard.

All projects, or just one? Have you checked the local repository locks (the LIST.READU command)?

What tool did you use for the query? What do you see when you use TO_HEX() in the query?

That is the limitation of which I spoke. To avoid it you need to prefix each substring with some other character, such as tilde in the following example. FUNCTION ReturnSecondOfPair(aString, aSearchString) * Convert string into dynamic array and prefix each substring with tilde. String = Convert(&qu...

It's not a change. Read my previous post carefully. It has always been thus - Oracle has its own standards, and tends to ignore industry standards. Despite having been authored by Microsoft, ODBC is an industry standard, and the CAE SQL Access Group standards certainly are.

The first thing I'd advise is to use WRITE, not WRITEU. You do want to release the lock on the record that you're writing. Second, instead of losing the diagnostic information (when you overwrite the Ans variable), use a call to DSLogInfo() to see what's happening. Use $DEFINE, $IFDEF and $ENDIF to ...

Here is the routine: FUNCTION ReturnSecondOfPair(aString, aSearchString) * Convert string into dynamic array. String = Convert(";", @FM, aString) SearchString = aSearchString : "+" * Find search string within string FindStr SearchString In String Setting FMC,VMC,SMC Then Ans = Fi...

Please look as your destination with something other than View Data. Tell us what's actually loaded. The question mark is simply a mechanism for representing "unmappable character".

Only Oracle uses the :1 and :2 syntax.

Everything else, including ODBC (even though it's to Oracle), uses ? for parameter markers, in accordance with the SQL CAE Access Group standards.

In this case it does not matter. The only way to reinstate JOBPARAMINSTS is to re-schedule the job.

Or you can have a unique sort on the input link of the Transformer stage.

That's still "in the Transformer stage".

Where they are developed is irrelevant. On a version 8.1 or higher system you can run any kind of job, any mix of kinds of job, developed in version 8.1 or earlier. As for performance, please define what you mean by "performance" in this context. Then we may be able to provide a more cogen...

It's my understanding that version 8.0 must be installed with "ade" itag. This may have been relaxed for version 8.1. I can't check at the moment - why not ask your official support provider?

For XMETA 10g is the only Oracle version currently supported.

This can only happen if those jobs are using a non-default configuration file.