This approach assumes the data blocks are already split at record boundaries. The last record of a block could span to the first record of the next block.
DEBLOCK operates on an input byte stream instead of data blocks. I could replace the split with the deblock linend 0a. I'll test it a see what happens. ____________________________ Jim Hughes 603-271-5586 "Its kind of fun to do the impossible." (Walt Disney) =>-----Original Message----- =>From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On =>Behalf Of Phil Smith III =>Sent: Wednesday, July 09, 2008 10:19 AM =>To: [email protected] =>Subject: PIPELINES and Deblocking(Cross posted in CMSPIPELINES Listserve) => =>Jim Hughes wrote: =>>I download files to our Z/VM system in binary. The files on the windows =>>ftp server are in ascii. => =><snip> =>>This works fine when the records are delimited by '0d0a' or '0a'. => =>>Last night I received a file whose records are delimited by '0d'. Things =>>broke because the file wasn't deblocked properly. => =>>I am having a hard time visualizing how to cope with records delimited =>>by '0d' and not mess up what I already have. => =>Normalize, normalize normalize! (Yeah, a strange concept for THIS crowd!) => =>Since they're ASCII, how about: => '| change x0d0a x0a *' , => '| xlate 0d 0a' , => '| split at x0a' , => => =>? => =>...phsiii
