Howard Brazee wrote:
I have a job that creates a LRECL=7104 record.Most of this a
variable length comment.It gets FTPd to a Unix machine and loaded
into a database.They want the extra spaces removed.
I doubt if the optimal solution would be to make it variable length,
and wonder if
Creating the data set as RECFM=V on the z/OS side and omitting
any filtering downstream seems optimum to me.
What arguments favor a more complicated process?
The fact that the program may not support writing variable length
records?
--
Peter Hunkeler
Credit Suisse
On Tue, 18 May 2010 13:20:49 -0600, Howard Brazee
howard.bra...@cusys.edu wrote:
Creating the data set as RECFM=V on the z/OS side and omitting any
filtering downstream seems optimum to me. What arguments favor a
more complicated process?
I'll try it.
It didn't read right. I'll just clean up
Creating the data set as RECFM=V on the z/OS side and omitting
any filtering downstream seems optimum to me. What arguments
favor a more complicated process?
I'll try it.
It didn't read right. I'll just clean up the file on the Unix side.
So then the program did not write variable length
Trailing blanks disappeared with the FTP!!!
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at
On 19 May 2010 07:47:39 -0700, peter.hunke...@credit-suisse.com
(Hunkeler Peter , KIUP 4) wrote:
It didn't read right. I'll just clean up the file on the Unix side.
So then the program did not write variable length records. The record
format (RECFM) is usually declared within the program, so
-Original Message-
From: IBM Mainframe Discussion List
[mailto:ibm-m...@bama.ua.edu] On Behalf Of Howard Brazee
Sent: Wednesday, May 19, 2010 10:24 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Creating a variable length FTP to ASCII file
Trailing blanks disappeared with the FTP
On 19 May 2010 09:30:07 -0700, john.mck...@healthmarkets.com (McKown,
John) wrote:
Trailing blanks disappeared with the FTP!!!
As is normal unless you are running with LOCSITE TRAILINGBLANKS set. I thought
I mentioned that?
I've been distracted lately.
You said the following. I inferred
I have a job that creates a LRECL=7104 record.Most of this a
variable length comment.It gets FTPd to a Unix machine and loaded
into a database.They want the extra spaces removed.
I doubt if the optimal solution would be to make it variable length,
and wonder if I should create a
-Original Message-
From: IBM Mainframe Discussion List
[mailto:ibm-m...@bama.ua.edu] On Behalf Of Howard Brazee
Sent: Tuesday, May 18, 2010 1:40 PM
To: IBM-MAIN@bama.ua.edu
Subject: Creating a variable length FTP to ASCII file
I have a job that creates a LRECL=7104 record
On Tue, 18 May 2010 12:39:36 -0600, Howard Brazee wrote:
I have a job that creates a LRECL=7104 record.Most of this a
variable length comment.It gets FTPd to a Unix machine and loaded
into a database.They want the extra spaces removed.
I doubt if the optimal solution would be to make
On 18 May 2010 11:48:00 -0700, john.mck...@healthmarkets.com (McKown,
John) wrote:
Trailing blanks or embedded blanks?
quote site notrailingblanks
on the ftp to remove trailing blanks, for a UNIX client (ftp initiated by
UNIX).
locsite notrailingblanks
for a z/OS client (ftp initiated by
On 18 May 2010 11:59:54 -0700, paulgboul...@aim.com (Paul Gilmartin)
wrote:
Creating the data set as RECFM=V on the z/OS side and omitting any
filtering downstream seems optimum to me. What arguments favor a
more complicated process?
I'll try it.
13 matches
Mail list logo
