×
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.
GKern@xxxxxxxxxxxxxxxx wrote:
Within the string there are multiple x'0D' where the data segments end
within the string. I thought those would serve to enable displaying each
segment as a separate line in the wrklnk view.
They would... on an Apple //e, and other older Apple computers! You
see, x'0d' is CR (carriage return) which is what Apple used to use for a
line terminator.
On Windows, you want to include CRLF which in x'0d25' in EBCDIC or
x'0D0A' in ASCII.
On Unix systems, you only want LF, which is x'25' in EBCDIC or x'0A' in
ASCII.
i5/OS tries to detect which convention you're using, and handle it
appropriately. The problem with this method is that it can be confused
if there's any other non-text data in the file.
I'm guessing you've (accidentally, I'm sure) written a lot of garbage
characters into the file, and it therefore can't determine the correct
end of line sequence. This would explain both problems (Both the
records exceeding 4k and the lack of line wrapping)
Start with WRKLNK option 8 to see how big the file is. Is it less than
2k as you say?
Then try running the following command from QShell (but use your
filename instead of the example, below)
od -vx /path/to/myfile.txt
This will provide a "hex dump" of the file so you can see what
characters are in it.
midrange.com
