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.
z/OS ftp vs COZBATCH todsn
Re: z/OS ftp vs COZBATCH todsn
These are the statements I use:
todsn //DD:OUT < /home/me/infile.txt
//OUT DD SYSOUT=*
todsn //DD:OUT < /home/me/infile.txt
//OUT DD SYSOUT=*
Re: z/OS ftp vs COZBATCH todsn
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).
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).