Hi, Jim. Looks like you have been bitten by the different ways Windows and Unix terminate records in ASCII files.....Windows uses the convention of 'cr-lf' (x'0d0a') while Unix uses a single 'cr'.
You could simply edit the ASCII file on your PC, using and editor that can saveASCII files in either Windows or Unix format. On Windows, I use notepad++, an open source editor (http://notepad-plus.sourceforge.net) to fix these sorts of things. Godd luck. DJ Original Message: ----------------- From: Hughes, Jim [EMAIL PROTECTED] Date: Wed, 9 Jul 2008 09:32:10 -0400 To: [email protected] Subject: PIPELINES and Deblocking(Cross posted in CMSPIPELINES Listserve) I download files to our Z/VM system in binary. The files on the windows ftp server are in ascii. Then I run a PIPE to deblock the file and convert to ebcidic. Here is a snippet: address command "PIPE ( endchar ? ) " , "<" !workfile " | " , " deblock linend 0a | " , " strip both 0d 1 | " , " xlate from 819 to 1047 | " , " change x00 / / | " , " strip trailing | " , 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. Advice?? ____________________________ Jim Hughes 603-271-5586 "Its kind of fun to do the impossible." (Walt Disney) -------------------------------------------------------------------- mail2web LIVE – Free email based on Microsoft® Exchange technology - http://link.mail2web.com/LIVE
