DSXchange

I don't know of an official API to get this. Perhaps a workaround solution could be used, add the version to the short or long description of each job, then DSGetJobInfo(DSJ.FULLDESC) could be used.

Compute the timestamp in a job sequence, then pass that value as a parameter to the job for use in the database and as part of the filename.

Since numeric columns cannot contain those special characters, ensure that they aren't put in there - several DataStage methods exist including string replacement and numeric conversion functions. For error number (2) please post line 11048 to see exactly what error is in the data.

Please explain how you setup your external source stage to read xml (from where?) and what your error is.

If you look at page 283 (V8 documentation) of the Parallel Job Developer guide the output schema is described.

The first message that looks suspicious that I saw in the log was Caused by: com.ascential.xmeta.exception.usage.InvalidQueryException: Error when parsing query (select rid(x) from x in ASCLModel::Principal where x.principalId = "PNB-EDWDS8\isadmin"): unexpected char: 'i' and I don't reall...

srinivas.g has the approach I would take, although I would do a straight constraint of In.Col1+In.Col2+In.Col3+...+In.Col104 >0 In any case using OR instead of AND is much better, since after the first FALSE with a linked list of OR s the matching would break off and not evaluate the rest.

Although I would not recommend it, it is not necessarily slow and certain functions such as some ICONV/OCONV conversions don't exist in PX and are quickly solved in a BASIC transform stage. Be that as it may, the problem here is not whether or not to use the stage, but that it is being used incorrec...

What sort of Delimiters? I suppose, with NLS, you can use the whole UTF-8 range of characters as delimiters.

If you mean characters with special meanings (e.g. @FM, @VM, @TM, @IM and @SM) the BASIC handbook lists them all.

Ahh, I see that now as well. Unfortunately, the DSG_BP file doesn't exist, so a simple VLIST command won't work. At version 8.0.1 the LOADSTRING program only has 294 source lines. What version are you on? How fit are you with the UniVerse command line editor?

My first guess is that you have a limit on the number of concurrent connections on your target machine. Once the limit is reached it counts as a "bad login" and after n-attempts the userid is disabled.

Do you drop it if one column is zero or if all columns are zero? Is the column a numeric one?

When you do a reset of your job, what does the log entry "from previous run..." show?

DataStage is written to be backwards compatible, so any (supported & documented) functionality you have now will work at 8.1

No issues, and it returns the correct values.