z/OS ftp vs COZBATCH todsn

Discussion of the free COZBATCH utility for z/OS
Post Reply
tsdjim
Posts: 60
Joined: Fri May 07, 2010 2:21 am

z/OS ftp vs COZBATCH todsn

Post by tsdjim » Thu Jul 21, 2011 4:44 am

When I use z/OS ftp to transfer a arabic data file from zLinux in ascii mode, the file displays fine on z/OS.

If I use COZBATCH with todsn without -s or -t or -b, the file is not readable on z/OS.

What is the difference between the two modes.

dovetail
Site Admin
Posts: 1770
Joined: Thu Jul 29, 2004 12:12 pm

Post by dovetail » Thu Jul 21, 2011 9:02 am

Please post an example of the COZBATCH job that you are using.

tsdjim
Posts: 60
Joined: Fri May 07, 2010 2:21 am

Re: z/OS ftp vs COZBATCH todsn

Post by tsdjim » Sat Jul 23, 2011 8:44 am

These are the statements I use:
todsn //DD:OUT < /home/me/infile.txt

//OUT DD SYSOUT=*

dovetail
Site Admin
Posts: 1770
Joined: Thu Jul 29, 2004 12:12 pm

Re: z/OS ftp vs COZBATCH todsn

Post by dovetail » Tue Aug 02, 2011 9:36 am

The "todsn" command that you used will break the file into records using the default rules, which are:

The source and target codepages are the default local codepage. This would typically be IBM-1047.
Any combination of newline, cr, linefeed (in the source codepage) will indicate a record delimiter.
Spaces (in the source codepage) will be trimmed.

So, without seeing the data it is difficult to understand why this isn't working. What encoding is the data in in the zFS file?

When you FTP a file from a remote system in "ascii" mode, the remote FTP client will normalize the newline characters and the z/OS FTP server will translate from ascii to ebcdic (unless you have specified different translate tables for the FTP command).

Post Reply