On 28-Mar-2014 09:26 -0700, Srinivas Boggula wrote:
We have converted some data from text file to PF file. The text file
has lines separated by CRLF. This PF file when read in V5R4M0
doesn't create any problem.
But when being read in V7R1M0 this CRLF is being consider as
The two characters representing both a <CR> and a <LF> are indeed
"characters"; albeit control characters. Every release will have the
database /read/ method including all control characters, converted
according to character translation requirements.
If the v5r4 database read had no issue, and presumably never passed
those characters in the buffer, then the characters were probably not
there. Thus, very likely, the means chosen to have "converted some data
from text file to PF file" is not operating the same as in the past.
Can you please let us know how to avoid this?
Strip the CRLF before placing the [other] data in the PF, or ignore
the CRLF that is being read from the PF. That is the same as always;
i.e. the OS database has never operated differently in that regard,
across every release.
Attaching sample data where we face issue.
Attachments [at least non-text and non-".txt" extension] are stripped
from the email list and via NNTP. The scenario must be described wholly
within the text of the email, or with redirection to a public area for
viewing; e.g. with a URL to some HTML.