DSXchange

unfortunately, you dont have luxory of some of the function of server job in Datastage EE... the best option you have in PX job is use "convert"

Yep, I agree as I said before after doing all renaming and dropping stuff; if you are still getting the error(warn) message only possible reason for that is RCP enabled.

In the new server, what is the default date format specified ? "YYYY-MM-DD" or "YYYY/MM/DD" or something else...if both the server has same default format set at "project" level..then ideally you shouldn't be having problem...

kumar_s wrote:Data might be valid, but how about join?

I dont concur with you. He is saying date looks good on the table, but after join its defaulted. A db2 table cannot store a invalid value in a date column.

assuming you have design, like below db2----| seq----|join stage----seq file 1. now you have left outer join, with seq file on left and db2 on the right. 2. assuming db2 has two columns, 1st is a key column and 2nd is the date column. 3. now in db2 stage or join stage or o/p seq file stage you didnt...

a question before suggesting anything; are you using the same file in pre-production run ?

I am not aware of your other design detail, so my suggestion would be based on some assumptions. If ActNo is one of the key columns and is at the higher level, then it would be an additional benefit. Assuming it is; I would sort the data on ActNo and hash partition on ActNo and enable "Create C...

please read below message

Please write in English, otherwise we will send Borat to your site. There is no word in English called "Borat" :shock: If it's a slang, then please correct your english. Secondly, we are here not to correct anybody's english but to correct Datastage understanding. If language used by some...

Historical Notes Ur was a city in ancient Babylon. It has no place in DataStage documentation, which includes posts on this forum. U was the first name of a UN Secretary General (U Thant, since deceased, so unlikely to be doing anything at all with DataStage). Grammatical Note "wont" is a...

ur job Dataset as Input, passed thru Transformer, Filter, SORT and Aggregator Few assumption: 1. its a linear flow, just one stream, as u have given. 2. In transformer u have some derivations and in next stage ur are dropping/selecting some records. 3. SOrt is used to just group the rows before aggr...

if ur coversion is about just change in length...u dont have to use modify stage...just in any of the transformer stage you may be having in ur job...simply map Decimal[31,11] column to Decimal[15,2] column..u wont get any error or warning.. word of caution, if ur input value is really occupying all...

yep, thatz the concept of RCP ..propagation.. words of caution...if you are using below stages and logic, i wd suggest not to use RCP..you may not get desired value, in ur o/p 1. Join stage (depend on type of join ur using) 2. remove duplicate 3. aggregator or aggragation logic in transformer stage ...

Ideally u shdnt be getting the problem if u have renamed the common columns...worth giving it a try..are the columns renamed in the input stage itself or intermediate stage? if its renamed in a intermediate stage, try disabling RCP

looking at the msg i wd make three guesses
1. permission on the file
2. space problem
3. u are trying to write a file twice in same job or ur trying to read a file and write to the same file, in the job