Gil, The OP showed a sample pipe in which he created a string of text under 80 characters long, blocked it as F 80, and then used the PUNCH stage to send it out the virtual punch. Thus, it was not in NETDATA format because it was not processed by either the NETDATA stage, nor SENDFILE command.
But alerting the OP the existence of the NETDATA stage may open new avenues for him. OTOH, he also reported that there are many files being processed, and NETDATA adds overhead on the sending and receiving ends. That said, if the files are longer than LRECL 80, or are variable length and the variable format must be retained, then NETDATA/SENDFILE is the proper method. Mike Walter -Retired- -----Original Message----- From: CMSTSO Pipelines Discussion List <[email protected]> On Behalf Of Paul Gilmartin Sent: Friday, January 25, 2019 2:57 PM To: [email protected] Subject: Re: Punch and deblock On 2019-01-25, at 13:40:12, Alain Benvéniste wrote: > Rob > I thought to use a pipe reader file to read it back but if it is not long to > show me I would be glad to know how to do that for a receive. > Many files are in transit so performance is a plus. > Have you looked at: https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ibm.com%2Fsupport%2Flibraryserver_os390%2FBOOKS%2FHCSH1C00%2F9.5%3FDT%3D20090727132928&data=02%7C01%7C%7Ca6b80f3a949f4694c41d08d68307c074%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636840466642199203&sdata=yVDmpEdVILc8ohPNW1bVdsHV5p2qaAIb9OCYYpHqN6A%3D&reserved=0 9.5 NETDATA Format /* DEBNET REXX -- Deblock a reader file in NETDATA format. */ 'callpipe', 'reader', /* From reader */ '| find' '41'x||, /* Only data records */ '| specs 2-* 1.80', /* Discard channel command and pad to 80 */ '| deblock netdata', /* Deblock */ '| find' 'c0'x||, /* Only data records */ '| specs 2-* 1', /* Remove control character */ '| *:' -- gil
