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

Tectia

Alternate Methods for 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 CCS.

Tectia Server for IBM z/OS needs more information: which transfer format to use, what code 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 filename (advice string), read from a file transfer profile, or read from environment variables.

Using the Site command is described in Site Command. Using the environment variables is described in File Transfer Environment Variables for the Clients and File Transfer Environment Variables for the Server. For information on using third-party clients, see Advice String and File Transfer Profiles.


 

 
Highlights from the SSH.COM blog:

  • Cryptomining with the SSH protocol: what big enterprises need to know about it

    Cryptomining malware is primarily thought of as targeting desktops and laptops and is used to hijack system resources to mine cryptocurrency.
    Read more
  • SLAM the door shut on traditional privileged access management

    Did you know that something as trivial-sounding as granting access for your developers or third parties to a product development environment can throw a gorilla-sized monkey wrench into your operations and productivity?
    Read more
  • We broke the IT security perimeter

    Everyone understands the concept of a security perimeter. You only gain access if you are identified and authorized to do so.
    Read more