DSXchange

What about memory segments that are never released? Log into uv once your in $DSHOME. Type PORT.STATUS, see how many addresses come up with UNAVAILABLE next time you have a zombie dbx.

Always pay attention to your comments Ray
Thats how my journey seems to go on towards enlightenment

Your right, I need to slow down. Probably still a kid in datastage

The issue remains with the metadata, rather than data itself. Both hold different scales which is causing the problem.

No. Thats part of the data. Now you have to set quote character as 000.

Yes, then quote character needs to be set to 000.
Do that only if you see quotes as data and not surrounding any other data.

Do you have quotes surrounding your varchar and char fields when you do a cat at the unix level?
OR
with 000 as quote character, hit view data, do you see your character fields surrounded with quotes? If yes then are they single quotes(') or double quotes (")?

It aborted because it could not find its twin quote. You need to handle that or provide a different quote character.

Even though its mapped, it will understand that G:\ means xyz server ?

Do the old stype extraction, length check and concatenation. Use the Field() function to extract day, if its length is less then 2, prefix it with a zero. Do the same for month. Get them back together and then run all the previous commands.

Ask your admin to run that command. You need to run it with dsadm or root id.

paddu wrote:i do not have col1 coming from my source link . In my source link col3 is the key .i need to do a lookup on col3 and get all attributes from Hashed file

If any key changes, you cannot reuse the same hashed file. Build a different one. And make sure you name it differently as well.

I got your back on that one Craig.

It would be nice to share the solution with us

Thats a good sign. Atleast you got half of it working. The data type mismatches are very critical to databases. I was hoping it would work as varchar but apparantly it did not.