DSXchange

No.

The best you can do is to identify every row loaded so that you can unwind the load.

You need to keep diagnosing. Check that job parameters are being passed correctly. Find out where the errors are occurring. Every time there is any return status that is not SQL.SUCCESS (including SQL.SUCCESS.WITH.INFO), use SQLError() repeatedly to remove all associated information from the handle ...

Proof?

SQL.BADHANDLE (-1) suggests that your first argument is invalid.

Is hdbc a valid handle; that is, did SQLAllocConnect() return SQL.SUCCESS?

Remember that variable names are case sensitive; hdbc and hDBC are two different variable names.

What are the scores doing in all of this? Is it the Qty values or the Score values being compared? Can you provide a couple of examples with numbers and a description of the expected outcomes, one where there is a match and one where there isn't? Are you prepared to countenance a solution that does ...

The "file name column" property must refer to a column (type VarChar probably) that is defined on the output link. Is this the case with your design?

The same is true for the file row number property, if you use that.

Please prove your assertion that "the routine didn't return the correct number". The maximum value in a column is a dynamic kind of thing - it can change frequently. So you must be able to show that, at the time when the routine was invoked, there was no way that the value could be changed, that a s...

In version 7.? they added a 33rd field to the dynamic array returned by the STATUS statement. It contains the maximum key size allowed for the open file, picked up from the MAXKEYSIZE configuration parameter in the uvconfig file, but possibly reduced if the separation (group size) is not large enough.

Stored procedure called from ODBC stage MUST produce (or consume) a data set. For this to have any chance at all of working, your SP must generate one or more rows, even if they contain only one column. And the ODBC stage must have precisely the same number of columns (and data types) on its Columns...

The problem with the Modify stage is that typos matter!

The Sequential File stage can generate two additional columns, one containing the file name of the file currently being read, the other containing the line number within that file of the record currently being read. But, as noted, it may be wise to set APT_IMPORT_PATTERN_USES_FILESET to False. Or at...

"Unicode" and "tab delimited" are totally unrelated. "Unicode" is one way of encoding characters. "ASCII" is another, "EBCDIC" is another, "ISO8859-1" is another. And there are gazillions more. How the characters are encoded is irrelevant to the selection of a delimiter character. You should be able...

Multiple defintion of the same output column is not permitted. In particular the following pair of specifications is illegal.

DS_MJ wrote:CD_COL_2:String[2] =Handle_null(string_trim(CD_COL_2),"xx")
;
CD_COL_2:int16 = int16_from_string (CD_COL_3)
;

Tell us what you're trying to do. At a guess you are performing "normal" (not sparse) lookups into a Lookup stage, and there is insufficient memory to load those rows from the reference table into a virtual Data Set on the nodes indicated. The best fix, if this is the problem, is a hardware solution...

Make sure that the 32-bit library directory precedes the 64-bit library directory or that the 64-bit library directory does not appear at all, for DataStage processes.