junk character - how to identify
Moderators: chulett, rschirm, roy
junk character - how to identify
How to identify the junk (non-reable or non-printable) characters in a record, I need to find it out in process of loading the records from source to target. is there any function for that.
tks.
tks.
with regards,
tsn
tsn
Yes, you can use OCONV(In.MessyString,'MCP') to turn all those nasty characters into "."
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
I hope that is not a jung characters, as i said earlier, it is not readable characters. example, if the thai characters coming in the name attribute, without using NLS, you can read those characters, so how we can identify those characters which are not undertandable by english one.
with regards,
tsn
tsn
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
It will be displayed as 2 bytes per character unless you are using NLS
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
As i said earlier, we are not using NLS. in the name attribute if those characters are coming then it is a problem.
example - NAME - VARCHAR(50).
If this non readable character is coming in the name attribute then the requirement here is to read and count how many characters are coming as non-readable character in a string(NAME), so that the warning or job abort can be avoided. so how to handle this one
example - NAME - VARCHAR(50).
If this non readable character is coming in the name attribute then the requirement here is to read and count how many characters are coming as non-readable character in a string(NAME), so that the warning or job abort can be avoided. so how to handle this one
with regards,
tsn
tsn
Why not just use LEN({string}) before doing the conversion to hex?
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
here is the situation, take is as an example.
the NAME is an attribute and its datatype is VARCHAR(50).
from the source file for few records under the name attribute thai characters are coming, since we are not using NLS, it will be consider as two byte which will try to get instered into table under NAME attribute.
If the thai characters are coming 10 then it will store into table with 20 character size. instead of 10 if it comes with 30 thai characters, then it will try to get stored as 60 character size. It will give warning in datastage. project has 0 warning settings. so the job will get aborted.
the NAME is an attribute and its datatype is VARCHAR(50).
from the source file for few records under the name attribute thai characters are coming, since we are not using NLS, it will be consider as two byte which will try to get instered into table under NAME attribute.
If the thai characters are coming 10 then it will store into table with 20 character size. instead of 10 if it comes with 30 thai characters, then it will try to get stored as 60 character size. It will give warning in datastage. project has 0 warning settings. so the job will get aborted.
with regards,
tsn
tsn
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Not necessarily. In many cases Thai characters can be encoded in a single-byte character set. TIS620 (the "standard" Thai character set encoding on UNIX) is one example.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.