No they are not terminated with CR or LF or anything.  They are just different 
length records with no length prefix or any suffix at all in a RECFM=U file.

I was the one who suspected that the original source file from the vendor was 
from Unix somewhere due to the content.  Goal here was to get this weird format 
file loaded on our system by the vendor into something normal for z/OS, like 
RECFM=VB.

But in any case the other application team has it under their control now, so 
it is out of my hands.

Peter

-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of 
scott Ford
Sent: Tuesday, June 18, 2019 10:48 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Is there any way to convert RECFM=U to RECFM=V with a utility or 
script?

Peter,

I was scanning through this thread. It sounds like the records are terminated 
with a 'CR' or 'CRLF' , i.e.;  x'0d' or x'0d0a' , is this correct

Scott

On Tue, Jun 18, 2019 at 10:14 AM Paul Gilmartin < 
0000000433f07816-dmarc-requ...@listserv.ua.edu> wrote:

> On Tue, 18 Jun 2019 03:43:18 +0000, Farley, Peter x23353 wrote:
>
> >Very interesting.  Collapsing the two steps and eliminating the
> intermediate Unix file also works, but I do have explicit DCB 
> information in the JCL for both SYSUT1 and SYSUT2, so maybe that's 
> what makes the IEBGENER process work here.
> >
> An early ply in this thread mentioned that the source of the data 
> appeared to be UNIX.
> Many followups assumed you wanted to reload to UNIX.
>
> >I had been told by the coworker who solicited my help that they had
> already tried IEBGENER to copy the file and that it failed, but I 
> should have asked to see the job.  I'll remember that.
> >
> It has been my experience that if no DCB information is available for
> SYSUT2 it will
> all be copied from SYSUT1.  If partial DCB information is available 
> for SYSUT2, IEBGENER reports an error.
>
--

This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to