NOTRAILINGBLANKS with VB File

George Hayes · New User Joined: 29 Oct 2007 Posts: 7 Location: Tennessee

We are able to get the NOTRAILINGBLANKS FTP parameter to work with an FB file, but it does not seem to work with VB. Is there do do this with a variable lenght file?

Thanks.

dick scherrer · Posted: Tue May 24, 2011 11:43 pm

Hello,

How does it "not seem to work"?

Posting "It didn't work" provides nothing for us to use to help you. . .

Was there an abend, a syntax error, unexpected/undesired output, etc?

George Hayes · New User Joined: 29 Oct 2007 Posts: 7 Location: Tennessee

Sorry for being vague. No error or abend is produced. The job finishes successfully and ignores the command. Hence, the transferred file still contains the unwanted blanks.

dick scherrer · Posted: Wed May 25, 2011 1:13 am

Hello,

Does this process "push" the file from the mainframe or "pull" runnig on the target system?

Maybe it will help if you post the informational messages from the ftp process.

superk · Posted: Wed May 25, 2011 2:29 am

I'm confused. NOTRAILINGBLANKS is only for fixed-length data files. Why would a variable-length file have trailing blanks?

Robert Sample · Posted: Wed May 25, 2011 3:06 am

And since the length is explicitly given in the RDW, why would FTP -- or anything else -- be changing it? I could see a Unix system receiving the data and getting rid of excess spaces, but that's a Unix thing not an FTP issue.

George Hayes · New User Joined: 29 Oct 2007 Posts: 7 Location: Tennessee

Thanks to all your patience and help. I'm trying to help a co-worker,since we're working on the same project. He has sent the log info for what he is trying to do. See below:

George,
Here is my jcl and output for the variable file and fixed file. In both cases, we are going from the mainframe to windows. The files are exact copies but the NOTRAILINGBLANKS command seems to only work on the FB version of the file. There are no errors/messages.

In-Stream JCL for Variable File
LOCSITE NOTRAILINGBLANKS
PUT 'ZZ.FCTS.ZB512B(0)' ZZ.TEST.ZB512B.TXT

Log
230 Login OK. Proceed.
EZA1460I Command:
EZA1736I LOCSITE NOTRAILINGBLANKS
EZA1460I Command:
EZA1736I PUT 'ZZ.FCTS.ZB512B(0)' ZZ.TEST.ZB512B.TXT
EZA1701I >>> SITE VARrecfm LRECL=49 RECFM=VB BLKSIZE=32760
EZA1701I >>> STOR ZZ.TEST.ZB512B.TXT
150 Opening ASCII mode data connection for ZZ.TEST.ZB512B.TXT.
226 Transfer complete. 162667 bytes transferred. 162667 Bps.

In-Stream JCL for Fixed File
LOCSITE NOTRAILINGBLANKS
PUT 'ZZ.TEST.ZB512B.TC1' ZZ.TEST.ZB512B1.TXT

Log
230 Login OK. Proceed.
EZA1460I Command:
EZA1736I LOCSITE NOTRAILINGBLANKS
EZA1460I Command:
EZA1736I PUT 'ZZ.TEST.ZB512B.TC1' ZZ.TEST.ZB512B1.TXT
EZA1701I >>> SITE FIXrecfm 49 LRECL=49 RECFM=FB BLKSIZE=27930
EZA1701I >>> STOR ZZ.TEST.ZB512B1.TXT
150 Opening ASCII mode data connection for ZZ.TEST.ZB512B1.TXT.
226 Transfer complete. 90568 bytes transferred. 90568 Bps.

Again, thank for the help.

dbzTHEdinosauer · Posted: Wed May 25, 2011 6:43 pm

George,

you keep ignoring the obvious.

FTP insures the integrity of Variable Length Files,
that would mean 180 bytes on mainframe, 180 bytes on windows platform.

if you want to remove the trailing blanks on a VB file, you will have to use sort or some other utility to 'effectively (reduce) change the record length indicator' for the file.

FTP insures the integrity of Fixed Length Files,
but since there actually is no such thing as a fixed length record txt file.
the end of the record is the end-of-record marker.
FTP does not transfer trailing spaces (when the option is requested),
and writes the end-of-record marker at the end of an FTP identified end-of-record position. (thus dropping and not transfering the spaces)

for variable length files, there is no function in ftp to reduce the record length indicator.

George Hayes · New User Joined: 29 Oct 2007 Posts: 7 Location: Tennessee

I agree. But, he wanted to be sure that no one else had another answer.

Thanks for all the help.