Mainframe low values
Moderators: chulett, rschirm, roy
Mainframe low values
I have a text file in which we have some special/junk characters. the special charater is something like box whose ascii value is 255. When i checked, i came to know that the file is from mainframe and during coversion they have some mainframe low values left as is.
Now my problem is i want convert them to blanks.
I am not able to do that. i have searched the db and tried all the options told but they are not working.
I request you to help me in this regard. Thanks in advance
Now my problem is i want convert them to blanks.
I am not able to do that. i have searched the db and tried all the options told but they are not working.
I request you to help me in this regard. Thanks in advance
Did you try convert?
Code: Select all
Convert(CHAR(255)," ",YourField)
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Yes i tried that. I got that from one of the previous post. But it did not work.chulett wrote:Did you try convert?
Code: Select all
Convert(CHAR(255)," ",YourField)
There is an open question here: How is the text file from the mainframe being created?
If there is a separate download job/process that creates the file, then the easiest and most effective way to handle this is to make sure that process is doing the proper EBCDIC to ASCII conversions. It's possible you can configure it to convert extended-charset values to space during the download.
An alternative is to read the mainframe data from the mainframe with FTP Enterprise, if your environment supports it. This stage lets you define the input format for "COBOL" which provides the necessary defaults and lets DataStage handle the characterset incoming and for conversion to ASCII. I use that in jobs I'm developing right now.
If there is a separate download job/process that creates the file, then the easiest and most effective way to handle this is to make sure that process is doing the proper EBCDIC to ASCII conversions. It's possible you can configure it to convert extended-charset values to space during the download.
An alternative is to read the mainframe data from the mainframe with FTP Enterprise, if your environment supports it. This stage lets you define the input format for "COBOL" which provides the necessary defaults and lets DataStage handle the characterset incoming and for conversion to ASCII. I use that in jobs I'm developing right now.
Franklin Evans
"Shared pain is lessened, shared joy increased. Thus do we refute entropy." -- Spider Robinson
Using mainframe data FAQ: viewtopic.php?t=143596 Using CFF FAQ: viewtopic.php?t=157872
"Shared pain is lessened, shared joy increased. Thus do we refute entropy." -- Spider Robinson
Using mainframe data FAQ: viewtopic.php?t=143596 Using CFF FAQ: viewtopic.php?t=157872
-
- Participant
- Posts: 135
- Joined: Tue Aug 14, 2007 4:27 am
- Location: Mumbai
I assumed no problem with low-values because they are ASCII null.
I also wonder, from his replies so far, if his clients are tying his hands and expecting him to do handstands.
I also wonder, from his replies so far, if his clients are tying his hands and expecting him to do handstands.
Franklin Evans
"Shared pain is lessened, shared joy increased. Thus do we refute entropy." -- Spider Robinson
Using mainframe data FAQ: viewtopic.php?t=143596 Using CFF FAQ: viewtopic.php?t=157872
"Shared pain is lessened, shared joy increased. Thus do we refute entropy." -- Spider Robinson
Using mainframe data FAQ: viewtopic.php?t=143596 Using CFF FAQ: viewtopic.php?t=157872