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

SSH

File Transfer Profiles

Edit the global or local user ssh_ftadv_config file to include a named or filename-matched profile.

We provide a sample configuration file (/opt/tectia/etc/ssh_ftadv_config.example). It is a good idea to copy this file to the directory you want and edit it to match your preferences.

  • /opt/tectia/etc/ssh_ftadv_config – Global FTADV configuration file. This file is in effect for all users unless the user in question has a local FTADV configuration file.

  • $HOME/.ssh2/ssh_ftadv_config – User local FTADV configuration file. If present, this file overrides the Global FTADV configuration file.

In the FTADV configuration file of your choice you can use one of the following types of profiles:

  • Named profile: Only used when specified via /FTADV:P=<profilename>/.

    The following example profile converts text files from Unix to MVS. ASCII is converted to EBCDIC.

    %UNIX         X=text,
                  F=line,
                  C=iso8859-1,
                  D=ibm-1047

    Individual attributes can be overridden like this: /FTADV:P=UNIX,C=ibm-1047/. (The transfer code set attribute C is overridden).

  • Filename-matched profile: Any file that matches the regular expression will use the specified settings. The first match is used.

    The following example profile matches files that have one of the extensions listed in parentheses. Code set conversion from ASCII to EBCDIC is performed.

    # Match text files that end with `.' and extension.
    .*\\.(txt|TXT|c|C|h|H|log|LOG|conf|CONF)$
        X=text,
        F=line,
        C=iso8859-1,
        D=ibm-1047

Take a look at Using File Transfer Profiles for a good practical of matched profiles.

The following table describes the named transfer profiles that are defined in /opt/tectia/etc/ssh_ftadv_config.example.

Table 3.2. Named File Transfer Profiles

Profile NameIncluded FTADV AttributesUsage
UNIXX=text, F=line, C=iso8859-1, D=ibm-1047Text files from Unix to z/OS
WINX=text, F=line, C=iso8859-1, D=ibm-1047, I=dos, J=mvsText files from Windows to z/OS
ZOSX=text, F=lineText files from z/OS to another z/OS
FB80X=text, F=line, C=iso8859-1, D=ibm-1047, O=fb, R=80Text files between Unix and z/OS. Data sets created in z/OS will have fixed blocked format with 80 byte records.
RECF=record, R=1024Preserves record length information. Data sets created in z/OS will have variable blocked format with a maximum record length of 1024 bytes.
BINX=bin, F=streamBinary file transfers
%X=bin, F=streamDisables data set pattern matching


 

 
PrivX
 

 

 
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