DSXchange

bobyon wrote:I suppose technically I should mark this thread resolved and start another.

Yup. Technically.

Dammit, Arnd... beat me to it.

Is that coming from DataStage or your Scheduler?

Do you actually have data like "19556,3,18," in the source? What kind of field are you loading it into?

"where" clause is ideally not required for input table or reference table. So it should not make a difference. Try it with alias name for the 1st field in the query, Oracle stage will expect a alias name same as the name that you mention in the columns field. Unfortunately, a couple of pr...

Hmmm... is this question related at all to the subject?

Ernie, any idea on when Part 2 will be available?

Right, search here for USERSTATUS and DSSetUserStatus for examples.

Ah, true... you'd need to constrain it to the rightmost two digits but that's simple enough.

NadrOutboundTempTable,0: Warning: Value "9297104 " truncated to "9297104 " NadrOutboundTempTable,0: Warning: At row 1, link "MatchedRecs", while processing column "SRC_ID" Value "9297104 " truncated to "9297104 " From 40 to 39 in length. W...

So, are you really dealing with NCHAR / NVARCHAR2 data? What is your source?

Hmmm... then that sounds like just a little substring work and adding 2 to the YY portion before you glue them together.

Depends on how picky you are about "two years". If you go with the definition that says a year is 365 days, then use DateFromDaysSince() to add 730 days to the system date.

On the way, my friend, on the way.

From what I recall, yes - the Terdata client (or "tools"??) needs to be installed on the DataStage server.

Right(ColumnName,7)