> I just successfully "got" a VSAM file from VSE > using the CMS FTP client.
Yes, and the VSE FTP server is the one that handled the VSAM for you. Neither the VM FTP server or client ever dealt directly with a VSAM file -- the VM FTP server wasn't involved, and the VM FTP client handled it as a CMS sequential file. There was no VSAM processing performed on CMS during that transfer, and you did not write a VSAM file on the CMS side. There is no code in the CMS FTP client or server to process VSAM files directly, thus the comment: > >You need a VSE-based FTP server which understands VSAM files > to do this. -- db
