Your browser does not allow storing cookies. We recommend enabling them.

SSH

Controlling File Transfer

The current Secure Shell protocol and current clients do not transfer any information about the files to be transferred, only the file contents as a byte stream. This is sufficient for Unix-type files if the sender and receiver use the same coded character set (CCS).

Tectia Server for IBM z/OS needs more information: which transfer format to use, what coded character sets are involved, and what the file characteristics are. When Tectia is used at both ends, the information can be relayed by using the site commands of scpg3 and sftpg3, or read from environment variables. When a third-party Secure Shell client is used together with Tectia Server for IBM z/OS, the information can be either encoded in the file name (advice string), read from a file transfer profile, or read from environment variables.

For more information, see Tectia Server for IBM z/OS User Manual


 

 
What to read next:

  • Reduce Secure Shell risk. Get to know the NIST 7966.



    The NISTIR 7966 guideline from the Computer Security Division of NIST is a direct call to action for organizations regardless of industry and is a mandate for the US Federal government.
    Download now
  • ISACA Practitioner Guide for SSH



    With contributions from practitioners, specialists and SSH.COM experts, the ISACA “SSH: Practitioner Considerations” guide is vital best practice from the compliance and audit community.
    Download now