—> ... | deblock linend 0a | split 0d | ...
Could that cause extra lines?
If you know the data has crlf or lfcr or just lf but never just cr then
… deblock 0a | strip both 0d | …
I suspect strip is more efficient than split because split has to scan
entire record, where as strip starts at each
On 3/13/23 16:41:47, Glenn Knickerbocker wrote:
Anyone have an idiom for deblocking and translating a file in ASCII that
may have either or both of CR and LF (*), ...
The problem is not well-posed. Consider
Foo
Bar
Is that two records, or three with a null record between the
I've got a bunch of lists where each list *precedes* the container I
want to match it up with--similar to link-edit steps in JCLIN, where the
name of the load module comes last. The lists are actually already
joined up into a single record, so I can join the container to the list,
move it to the s
(Copied here from an IBM internal discussion because I should have come
here first anyway:)
Anyone have an idiom for deblocking and translating a file in ASCII that
may have either or both of CR and LF (*), and may be split into records,
without unnecessarily buffering the whole file? The possibi
