If set to YES and a normal allocation fails because a data set is not online, Tectia will allocate it and request the system to mount it. This requires that the user has read permission to the SSZ.MOUNT facility.

If set to NO, offline data sets are not mounted automatically.

If set to IMMED, Tectia will not attempt the normal allocation, it will request the system to mount the data set immediately.

Default: NO

AUTOMOUNT|AUTOM is equal to AUTOMOUNT=YES.
NOAUTOMOUNT|NOAUTOM is equal to AUTOMOUNT=NO.

Defines whether data sets migrated by a storage manager are recalled automatically.

Default: YES

AUTORECALL|AUTOR is equal to AUTORECALL=YES.
NOAUTORECALL|NOAUTOR is equal to AUTORECALL=NO.

Specifies the maximum block size.

Default: none

Specifies that the space allocation unit is blocks. Equal to SPACE_UNIT=BLKS.

Specifies the disposition of the output file when a file transfer ends prematurely (the client or server are alive but disconnected from the other end; for example, when pressing CTRL+C in the client).

	Note
	If the client (when transferring to local or client side) or the server (when transferring to remote or server side) dies, they will have no control over the disposition.

The options have the following effects, depending on the file type (MVS or HFS):

Default: CATLG

Specifies that the space allocation unit is cylinders. Equal to SPACE_UNIT=CYLS.

Specifies the data class of a data set.

Default: none

Identifies the relative position of a data set on a tape volume.

Default: System default

Specifies whether data set allocation is postponed from allocation phase to when the data set is opened.

If set to YES data set allocation is postponed until data set is opened.

If set to NO data set is allocated in allocation phase.

Default: NO

DEFER|DE is equal to DEFER=YES.
NODEFER is equal to DEFER=NO.

Specifies the number of 256-byte records in the directory.

Default: 10

Specifies the expiration date for a new data set. On and after this date, the operating system can delete or write over the data set.

Default: System default

Defines the status of a data set. If entered, the value will be used when allocating the data set. This attribute corresponds to the first value in the DISP parameter of the JCL DD statement. Possible values are:

Specifies whether to interface with the file system or with the z/OS Job Entry Subsystem (JES).

Using FILETYPE=JES enables the commands put and sput to submit transferred files to the internal reader job queue for execution, get and sget commands to retrieve spool data sets, and for file transfer advice strings, also rm to delete jobs, and ls to list jobs. To terminate interfacing with JES and return to normal file access, set the file type back to sequential (SEQ), or to an empty string (that is, FILETYPE=). Entering an empty string as file type sets the file type to default.

Default: SEQ

The data set organization is set to FB and the fixed record length is set to length.

Default: none

When in FILETYPE=JES mode, JOB_ID specifies that commands accessing the JES spool, such as get, apply only to jobs with a job ID that matches the supplied ID.

When interfacing with JES using a file transfer advice string, using ls -l in conjunction with a job ID permits listing the spool files for that job.

Commands get, sget, and so on, with a job ID can be used to retrieve the spool files for a given job.

When in FILETYPE=JES mode, JOB_OWNER specifies that commands accessing the JES spool, such as ls, and get, and so on, apply only to jobs with owner matching the supplied name.

Default: Current user

When in FILETYPE=JES mode, JOBNAME specifies that commands accessing the JES spool, such as ls, get, and so on, apply only to jobs with job name matching the supplied name.

Specifies the length in bytes of the keys used in the data set.

Default: none

Specifies the key offset; the position of the first byte of the key in records of the specified VSAM data set.

Default: none

The type of the label for the data set. This attribute corresponds to the first value in the LABEL parameter of the JCL DD statement.

	Note
	It is recommended for sites to control the use of BLP and NL tape processing by restricting access to the appropriate resource, using RACF or an equivalent security product.

Specifies the name of a model data set from which the RECFM, BLKSIZE, and LRECL attributes are to be copied. The name must be the full DSN of a cataloged data set and must be preceded with three underscores.

You must include the TYPE attribute when using LIKE unless you are creating a PS data set and the model is a PS data set.

Default: none

Maximum record length or fixed record length.

Default: 4096 for VSAM, 80 if data set organization is F or FB, otherwise 1024

Specifies the management class of a data set.

Default: none

Specifies the data set disposition to be used after a file transfer that ends normally. This attribute corresponds to the second value in the DISP parameter of the JCL DD statement.

Default: CATLG

Primary space allocation for a data set.

Default: none

The file transfer profile specifies the named profile used for the file transfer. The profile name is case-sensitive. With special profile name P=% no profiles are used. This also prevents profile matching based on file name.

Default: none

RECFM specifies the data set organization. The possible values are all valid combinations of the following letters:

    F       Fixed
    V       Variable
    U       Undefined
    B       Blocked
    S       Spanned or standard
    M       Machine line printer codes
    A       ASA line printer codes

Default: VB

When a record truncation occurs while writing an MVS data set, the system will continue writing the data set if RECORD_TRUNCATE is set to YES; and the system will abort the transfer if RECORD_TRUNCATE is set to NO or omitted.

Record truncation will occur if the length of a transferred record (after code set and line delimiter conversion) is larger than the maximum record length of the data set. Truncation can occur only when TRANSFER_FORMAT is set to LINE or RECORD. Note that the STREAM format does not have any concept of records in transferred data and it will fill out all records to their maximum length.

In the LINE transfer format, the length of a transferred record is the number of characters up to a newline character.

In the RECORD format, the length of a transferred record is given by the 4 byte binary length field which precedes the record.

The maximum length of a data set record depends on the data set organization:

  F and FB - LRECL
  V and VB - LRECL-4
  U        - BLKSIZE
  VSAM     - MAXRECLEN

When Tectia client tools for z/OS aborts writing a data set because of record truncation, it will complete the write operation during which the system observed the truncation. It will write to disk one or more records, at least one of which is truncated. The data set is left on the system.

Tectia client tools for z/OS may write a large amount of data in one write operation, typically 32kB. Several records may be written in the last operation, some of them truncated. Small files may be written to the end of the file, and thus the resulting data set will be equivalent to one written with setting RECORD_TRUNCATE=YES.

Note that some file transfer client programs do not always show the error or warning messages from the server. Using the verbose mode (--verbose, -v) may show more messages from the server.

	Note
	When Tectia client tools for z/OS writes a data set with RECORD_TRUNCATE=YES, data loss may occur.

TRUNCATE|TRU|TRUN is equal to RECORD_TRUNCATE=YES.
[NO]TRUNCATE|[NO]TRU|[NO]TRUN is equal to RECORD_TRUNCATE=NO.

The retention period in days. After the retention period, the data set expires and the operating system can delete or overwrite the data set.

Default: System default

Secondary space allocation for a data set.

Default: none

Size estimate (in bytes) for data set allocation.

Default: 1000000

When a new data set it allocated, SPACE_RELEASE specifies whether unused disk space will be released. If set to YES, unused disk space of a new data set is released. If set to NO, allocated disk space of a new data set is retained.

Default: YES

Unit of space allocation for a data set.

Possible values for the space allocation unit are:

Default: none

When SPACE_UNIT=BLKS or SPACE_UNIT=AVGRECLEN, specifies the size of the space allocation unit.

Default: 100 with SPACE_UNIT=AVGRECLEN, none with SPACE_UNIT=BLKS

Specifies whether staging is to be used in the SFTP server when accessing a file or data set.

If set to NO, staging is not used.

If set to YES, staging is used, when needed.

Default: NO

	Note
	When staging is used, do not set the _CEE_RUNOPTS environment variable's TRAP option to OFF. If you do, sftpg3 fails to start. The TRAP option is ON by default.

Specifies the storage class of system managed storage.

Default: none

Dynamic allocation arguments that override or are added to arguments from other file transfer attributes. For detailed information on this attribute, see Low-Level Access.

Default: none

Specifies that the space allocation unit is tracks. Equal to SPACE_UNIT=TRKS.

Specifies whether to preserve trailing blanks in a transferred data set.

If set to YES, trailing blanks will be transferred. This can be used, for example, to preserve the structure of fixed format data sets when transferring to a Unix-type file system.

If set to NO, trailing blanks will be stripped.

Default: NO

	Note
	This option only applies to line-delimited target files (TRANSFER_FORMAT=LINE), not to target unit-record data sets.

TRAILINGBLANKS|TRAI|TRAIL is equal to TRAILING_BLANKS=YES.
NOTRAILINGBLANKS|NOTRAI|NOTRAIL is equal to TRAILING_BLANKS=NO.

During the transfer the data has the specified code set. codeset is the code set name that is known to the iconv function of the system performing the conversion. The available code sets can be listed by invoking the iconv command at a USS prompt with the -l option:

> iconv -l

Default: none

Example 1: A Windows SFTP client puts a file to a z/OS data set and gets a data set from z/OS

Using file transfer advice strings:

sftp> sput file.txt /ftadv:C=ISO8859-1,D=IBM-1047/__DATASET.TXT 
sftp> sget /ftadv:D=IBM-1047,C=ISO8859-1/__DATASET.TXT file.txt 

	The Windows client tells the z/OS server that the code set during the transfer is ISO8859-1 and that the server should store the data set with the IBM-1047 code set.
	The Windows client tells the z/OS server that the code set in the data set is IBM-1047 and it should be converted to ISO8859-1 before transferring the data to the Windows client.

Using the site command:

sftp> site C=ISO8859-1 D=IBM-1047 
sftp> sput file.txt //DATASET.TXT 
sftp> sget //DATASET.TXT file.txt 

Example 2: A z/OS SFTP client puts a data set to a Windows file and gets a file from Windows

Using file transfer advice strings:

sftp> sput /ftadv:C=ISO8859-1,D=IBM-1047/__DATASET.TXT file.txt  
sftp> sget file.txt /ftadv:C=ISO8859-1,D=IBM-1047/__DATASET.TXT  

	The z/OS client is told that code set in the data set is IBM-1047 and it should be converted to ISO8859-1 before transferring the data to the Windows server.
	The z/OS client is told that the file has the ISO8859-1 code set during the transfer and the data set should be stored with the IBM-1047 code set.

Using the lsite command:

sftp> lsite C=ISO8859-1 D=IBM-1047
sftp> sput //DATASET.TXT file.txt
sftp> sget file.txt //DATASET.TXT

	Note
	The line delimiter information is always given to the host that is capable of performing the conversion, in these cases the z/OS host.

The data in the data set has the specified code set. codeset is the code set name that is known to the iconv function of the system performing the conversion. The available code sets can be listed by invoking the iconv command at a USS prompt with the -l option:

> iconv -l 

Default: none

The transfer file line delimiter specifies the newline convention used in the (source or destination) file. Possible values are:

Default: none

	Note
	The line delimiter information should be given to the host that is capable of performing the conversion, such as a host with a Tectia. Line delimiter conversion is implemented for single byte code sets only. For the line delimiter conversion to happen, both TRANSFER_LINE_DELIMITER|I and TRANSFER_FILE_LINE_DELIMITER|J must be specified.

Example: a z/OS Tectia SFTP client sends a data set to a Windows host and copies the file back from Windows

In this example, the code set is also converted.

Using file transfer advice strings:

sftp> sput /ftadv:I=DOS,J=MVS,C=ISO8859-1,D=IBM-1047/__DATASET.TXT file.txt 
sftp> sget file.txt /ftadv:I=DOS,J=MVS,C=ISO8859-1,D=IBM-1047/__DATASET.TXT \ 
        file.txt 

The file line delimiter conversion (J=MVS) makes the z/OS client insert an NL (0x15) character after each record. The line delimiter conversion (I=DOS) converts all NL:s to CRLF (0x0D 0x0A) characters, which remain unchanged in the code set conversion. The z/OS client is told that the code set in the data set is IBM-1047 and it should be converted to ISO8859-1 before transferring the data to the Windows server.

The CRLF line delimiters (set by I=DOS) are converted to LF characters (J=MVS), which are converted to NL characters in the code set conversion. The conversion from line-delimited stream format to record-oriented format occurs automatically. In the code set conversion, the z/OS client is told that the file has the ISO8859-1 code set during the transfer and the data set should be stored with the IBM-1047 code set.

Using lsite commands:

sftp> lsite I=dos J=mvs                
sftp> lsite C=IBM-437 D=IBM-1047       
sftp> sput //DATASET.TXT file.txt      
sftp> sget file.txt //DATASET.COPY.TXT 

The byte stream consists of the bytes that are transferred as payload in the SFTP protocol packets. The byte stream has one of the following formats: LINE, STREAM or RECORD. All three formats may have data consisting of text, non-text data, or a mixture of these.

When writing an MVS data set, a record that is longer than the maximum or fixed record length will cause an error unless RECORD_TRUNCATE is set to YES, in which case the record will be truncated. When writing to data sets with fixed record lengths, short records will be filled with binary zeroes if you use the record transfer format and with blanks if you use the line transfer format.

Default: LINE.

The transfer line delimiter specifies the newline convention used in the data that is transferred over the connection. Possible values are:

Default: none

	Note
	The line delimiter information should be given to the host that is capable of performing the conversion, such as a host with a Tectia.

The transfer mode specifies whether code set and line delimiter conversions are performed. The available values are:

Default: none

	Note
	If TRANSFER_MODE is not given but both TRANSFER_CODESET and TRANSFER_FILE_CODESET or TRANSFER_TRANSLATE_TABLE are present conversions are performed.

templates specifies the search templates for the translate table. Write '%T' to show the point where the translate table name (see above) is to be inserted. Delimit the templates with a plus character. The data set name templates must not contain slashes, instead they must be preceded by two or three underscores. For more information, see Data Set and HFS File System Access.

The first translate table data set that is found is used to perform the code conversion.

	Note
	The translate table must translate line delimiters into EBCDIC NL characters. See TRANSFER_FORMAT.

Default: none

TABLE is the name of the table that specifies the code set conversion. If set, this attribute overrides the transfer code set and file code set attributes. The table is always applied in the normal direction, that is, the first character array is used for incoming (from the line to the data set) data and the second array for outgoing data. If the opposite translation is needed, e.g. the data set contains ASCII and should be transferred as EBCDIC, you (or your system programmer) can prepare a table data set with the character arrays in reversed order (e.g. with the system utility CONVXLAT or by editing an existing translate data set).

Specifies the type of a data set when the data set is created. The available values are:

Default: PO, if data set name includes member, otherwise PS

The name of the device or group of devices that the data set will reside on (or does reside on, if it already exists). The maximum length of unit is 8 characters. If the value exceeds the maximum length, it is truncated to 8 characters.

It is also possible to specify a device address. Precede a four digit address with an underscore.

Default: none

Specifies the number of devices for the data set. This attribute corresponds to the second value in the UNIT parameter of the JCL DD statement.

Default: System default

Asks the system to mount all the volumes for the data set in parallel. This attribute corresponds to the character 'P' in the second value in the UNIT parameter of the JCL DD statement.

Default: System default

Specifies the maximum number of volumes that an output data set requires. This attribute corresponds to the volume count value in the VOLUME parameter of the JCL DD statement.

Default: System default

A plus sign (+) separated list of volumes a data set will reside on (or does reside on, if it already exists).

Default: none