DSXchange

Could it be that you have reached the MAXUPROC value for that user-id?

When you use user-defined insert & update you must manually change the order so the update gets done first - this would be in the "insert" code section. The "update" code section then has the insert statement.

I disagree with Ray in this case, it is an easy question to answer: The answer is a 386SX processor and 16Mb of memory. According to the accounting department, this is an optimal hardware configuration. The IBM Sales department has a different opinion, they recommend a P595 frame, fully equipped wit...

Pass just the variable components to the job as parameters, the YYYYMMDD and YYYYMMDDHHMMSS. The rest is constant in your case.

Without looking into the rest

main_program: Fatal Error: Added field has duplicate identifier():

is indicative of a runtime column propagation issue. Do you have RCP enabled for this stage?

Outlink will only be NULL if the input is NULL

StageVar: InternalDate = ICONV(Inlink.field2,'D MY[A3,2]')
Derivation: OCONV(InternalDate,'D4Y'):'Q':OCONV(InternalDate,'DQ')

Are there any non-standard ASCII characters in the table or column names?

Since your date is in the form YYYY/MM/DD there is no need to convert to internal format. The nulls or empties are a separate issue.

What did you try? I use "VarBinary" or "LongVarBinary" with some success.

If you set APT_DATE_CENTURY_BREAK_YEAR to 2000 then Year 96 correctly gets computed as 2096. If you set the break year to "1970" then 71 or 96 will get converted to 1971 and 1996 respectively.

I don't quite understand what you are asking. The PX "APT_DATE_CENTURY_BREAK_YEAR" and the Server equivalent setting of the CENTURYPIVOT uvconfig parameter both work perfectly well.

No, the DataStage MVS is a separately priced product.

1. use "od"
2. Ok, "MS1253" is Greek. Is that what the CFF was originally created in? And what is your DataStage output file NLS character set?

Luckily you are on Windows, so it is easy to check. You should have a system DSN for the ODBC connection. Try connecting using another utility, preferably the (free) MSQUERY that comes with Office. If you cannot connect from there either then the problem does not lie within DataStage.