Re: [netrexx-pipelines] Migrate OS/2 pipelines to NetRexx Pipes

[René J. <rvj...@xs...>]

Well, let me strike that remark from the proceedings. It was a rather loose comment, based in the fact that on CMS and TSO you know there are records (F/V) because these are a part of data set organisation and access methods. With stream oriented file I/O there is a change that you mistake delimited strings for records. This most of the time is my own mistake (cr/cr/lf, tabs etc) and requires me to delimit and split.

I think restraint is always a good thing, except in fighting evil. In this case, I think your scepticism should not be based on imprecise statements from my side.
Probably Jeff already has pointed to the real cause of your problem. Keep sending them in!

René 

> On 23 Jun 2022, at 09:20, hp...@we... wrote:
> 
>> 
>> a general problem is that sometimes you must inset a ’split’ into the pipeline because on other platforms than CMS a ‘record’ is less strictly defined.
> 
> Could you please be so kind an define 'sometimes' in this respect.
> Are there well-defined indicators when or where a 'split' is
> required? What are the reasons records get concatenated (two or
> more?) or not discerned as single records? Your 'insert a split
> sometimes' makes me very sceptical, if on platforms other than CMS
> we better restrain using Pipelines at all.