I have a records like this....
'99999','BB1','01/13/2009','08:38:16','000064529100110122500003','-38.50','-1'
I am using sequential stage to read it....
but sequentila stage is reading it as '?99999' why this is comming...?
I suppose to get only 99999 no quotes....
Make very sure that you have what you think you have, by viewing the file with something that also shows non-printing characters, such as the UNIX command od -c
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
U also can try with unix command `cat -v` to display the special characters form your input file, if there are any, you need to manually remove those characters to make it in proper format..
You need to determine how they got there... created at the source? Problems during a transfer? Then ensure they are not in the file before you have to process it.
-craig
"You can never have too many knives" -- Logan Nine Fingers
Actually i am importing file from remote location then....i am concatinating it with a available file.....
so the specila characters are comming....
not sure whether it is happening coz of transfer or coz of input sourse....
bt one thing which i observed....
when i am copy pasting the data into a new file, this character is not comming.....so it is related with file properties i guess....
As noted, you need to figure this out, we can't. Are the characters in this other 'available' file? Or in the source file after the transfer? Or only there after you cat the two together? How exactly are you "importing the file from remote location"? How exactly are you doing the concatenation? Details, man, details.
-craig
"You can never have too many knives" -- Logan Nine Fingers
well through shell script i am importing the files.....
it never happened with any other file but only with this file it is happeing....
so i want to know whether it is the sourse file problem...
by using CAT i am concatinating the files,......in shell script...
also....is there any way by which we can avoid this...??
First you need to figure out what "this" is before you'll have a clue how to fix / avoid it. Use some basic detective skills. Check the file on the remote location before the transfer, are the characters there? Check after the transfer, are they there now? Etc. Pinpoint at what stage in the process they appear.
-craig
"You can never have too many knives" -- Logan Nine Fingers
yes those special characters are available in remote file...
so is there no way to avoid it....
as that remote file will be comming from third party company
Then you need to have a chat with this third party company, see if they can provide you with a working file before you try to come up with ways to work around their... crap.
-craig
"You can never have too many knives" -- Logan Nine Fingers