×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I'm reading an IFS file, doing some processing, and writing to another NEWLY created IFS file.
The input from the read file is doing great.
For the new file, done it a hundred times. The read file has a CCSID of 819 (it was created in an FTP script, then copied to another directory. (The directory created with CRTLNK is CCSID = 37).
Okay, I opened the new file with CCSID = 37 by default and tested great. The incoming file uses a tilde as a separator for the line/segment. All I want to do is add an end-of-line marker right after that tilde. Again, it did fine.
Then show-and-tell to the one other programmer here. He says he has to view it using a Windows share folder into the IFS, because the old process this is meant to replace is a Windows-based process and it breaks a lot, so he has to fix a lot, and it's easier than green screen. This one won't break so much, I'm writing it, but it's his call... :-)
So of course CCSID 37 displays as garbage in the Windows share.
So I created it with 819, still using x'0D0A' for the CRLF. This time it shows a new line when I open it in Notepad,
where the CR is, but shows the LF line feed as a weird character at the beginning of the next line.
So back to the code. Now I've tried CCSID = 1252 for the file-CCSID on the open() API for the new file, and 37 for the open CCSID. Opening it that way still shows garbage.
What obvious thing am I forgetting here?
--Alan
--------------------------------------------------------------------------------
Confidentiality Notice: This email may contain confidential information or information covered under the Privacy Act, 5 USC 552(a), and/or the Health Insurance Portability and Accountability Act (PL 104-191) and its various implementing regulations and must be protected in accordance with those provisions. It contains information that is legally privileged, confidential or otherwise protected from use or disclosure. This e-mail message, including any attachments, is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. You, the recipient, are obligated to maintain it in a safe, secure and confidential manner. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Thank you.
--------------------------------------------------------------------------------
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.