The following table describes the general transfer options. The usage columns describe when the option (if active) will apply during transfer. Usage Read means using Co:Z SFTP (server or client) to read a z/OS file. Usage Write means using Co:Z SFTP (server or client) to write a z/OS file.
Note | |
---|---|
Options that have a blank value column are
on/off options. They are activated by supplying the option name by itself (no values
allowed) and deactivated by prefixing the option name with the prefix |
clientcp
Specifies the name of the client codepage used when performing text mode transfers. Data will be converted between the server codepage (servercp) and this code page. The codepage must either be a single byte codepage or any multi-byte codepage that has single-byte line terminators (e.g. UTF-8). The z/OS Unix command iconv -l lists the available codepages. For the Co:Z SFTP server the default is
ISO8859-1
. For the Co:Z SFTP client, the default is the default locale codeset of the client's process (some variant of EBCDIC).A TranslationException is logged when the transferred file is malformed. When possible, the offset of the last successfully translated byte is captured in the error log message.
estsize
When estsize (the default) is enabled, Co:Z SFTP returns the actual size for Unix files and an estimated size for MVS data sets. When estsize is disabled (NOestsize), the size returned is zero and
SSH_FILEXFER_ATTR_SIZE
is off indicating that the attribute size is not present. This has the effect of telling the client on a file read that there is no estimated size.filetag
(new in 8.0.0) The values use and create may be specfied, and both values may be specified separated by a period. Alternatively u and c may be used, either alone or together as filetag=uc. The default is NOfiletag.
When use is specified, existing UNIX file tags will be respected when converting files, and these transfer options will be displayed. This option affects both reading and writing of existing UNIX files that have file tags.
When create is specified, UNIX files that are written will be tagged according to the mode and codepage settings in effect, replacing any existing file tags.
When both use and create are specified, existing file tags will be respected. New or untagged UNIX files that are written will be tagged according to the mode and codepage settings in effect. Existing file tags will not be replaced when writing.
Note: If NOfiletag is in effect (the default and prior to 8.0.0), then existing file tags will result in filesystem autoconversion IF _BPXK_AUTOCVT=ON/ALL or equivalent are set in the current execution environment. Any such autoconversion will not be made visible by Co:Z SFTP in "Transfer options" messages, and may occur in addition to translations made by CO:Z SFTP based on mode and codepage settings, possibly with unexpected results. If filetag is specified with either or both values, then file system autoconversion will not occur. Refer to IBM documention for more information on z/OS UNIX autoconversion.
jesincsysin
When option
jesincsysin
is enabled, concatenated spool file downloads will include SYSIN spool files. In addition, the separator between spool files will be annotated with the [step.[procstep.]]ddname. This option is a convenient way to download all job input and output.linerule
The values
cr
,crlf
,crnl
,lf
,nl
specify that, for text mode transfers, lines will be terminated with the given characters in the client codepage.flexible
may be used when writing to files or datasets to indicate that any combination of cr, lf, or newline will be recognized as a line terminator.rdw
specifies that IBM-style RDWs are used as prefixes.l4
specifies that each record is delimited (preceded) by a four byte length of the record that follows. Note: Unlike therdw
option, this length value does not include the size of the length field.mfrdw
indicates that Micro-focus file and records headers are used. This only supportsVariable Format Record Sequential File
s containing normal data records.0xbb[bb..]
may be used to specify a sequence of one or more bytes in the source codepage.none
should be used when no line terminators are to be recognized/used.The default is
flexible
for writing and lf for reading.mode
Specifies whether transfers are as-is (binary) or subject to codepage/linerule/overflow/pad processing (text). The default is
binary
.notify
Specifies whether a message should be written to the console on completion of a put or get command by the Co:Z SFTP server and client. Notifications are also written on completion of a remove or rename command on the server. The default is
NOnotify
. In order to enable this option, a valid message template must be defined in the site-wide server or client configuration. For addition information, see Section C.1, “Specifying notification (immutable) options”. Notifications are disabled if the Co:Z SFTP server log file has been redirected to/dev/console
due to the potential for recursive logging.overflow
For text-mode dataset write processing, controls the treatment of lines longer than the maximum dataset record length. The default is
wrap
. When set toerror
, an error is returned if the source line is longer than the maximum record length. When set toflow
, source lines longer than the maximum record length are flowed across subsequent records. For fixed record formats, the pad character is used to complete the final record resulting from the source line. When set totrunc
, source lines longer than the maximum record length are truncated. When set towrap
, source lines longer than the maximum record length are broken into multiple records.pad
For text-mode dataset write processing, specifies the character to use when padding lines into fixed-length dataset records. For text-mode dataset read processing, this character also identifies the character to be trimmed if the
trim
is enabled. If given as0xbb
, it specifies (in hex) a single-byte character in the source codepage. If not specified, the default is a space character in the local z/OS codepage.replace
This setting allows for existing data sets or files to be replaced. The default, if not specified, is
replace=reuse
, which allows for replacement. If the target is a data set, the existing data set will be cleared but the original allocation options will be preserved.replace=realloc
can be set to cause the existing data set to be deleted and reallocated using the allocation option settings currently in force.NOreplace
can be set to prevent an existing dataset or file from being replaced.When using cozsftp, setting
NOreplace
andreplace=realloc
withlzopts
only applies to get commands.NOreplace
andreplace=realloc
for a put command requires that the server be running Co:Z SFTP Server. For other SFTP servers, these options are not supported.Note 1: If
NOreplace
orreplace=realloc
is set, you may not create PDS members, regardless of whether the member exists, and you may only write to GDG datasets using a positive (+n) relative reference.Note 2: The
mkdir
command cannot be used to replace an existing PDS, even ifreplace=realloc
.servercp
Specifies the name of the server codepage used when performing text mode transfers. Data will be converted between the client codepage (clientcp) and this code page. For the Co:Z SFTP server the default is default locale codeset of the server's process (some variant of EBCDIC). For the Co:Z SFTP client the default is
ISO8859-1
.A TranslationException is logged when the transferred file is malformed. When possible, the offset of the last successfully translated byte is captured in the error log message.
technique
Specifies the Codepage conversion technique string. Used to override the default Unicode Services value of
LMREC
. For more information, see IBM's Unicode Services User's Guide and Reference (SA22-7649).trtab
Specifies the translate table to use for text mode transfers. This option overrides the
clientcp/servercp/technique
options if also given. IfSTANDARD
, the translate table TCPIP.STANDARD.TCPXLBIN is used. If a dataset name is supplied, it is expected to be in the format produced by the TSO CONVXLAT command. Only single byte translations are supported. Specifically, the dataset DCB must be LRECL=256,RECFM=F and contain two translation table records. The first record is an ASCII-to-EBCDIC mapping; the second record is an EBCDIC-to-ASCII mapping. Additional comment records (starting with * in the first column) are allowed.trim
For text-mode dataset read transfers, enabling this options will cause pad characters to be trimmed from the dataset records as they are read. The default, if not specified, is
trim
.utfbom
For text-mode data set and POSIX file transfers, setting this option to
remove
will cause Co:Z to remove the Byte Order Mark (BOM) from the incoming data stream if it is present. In order for this option to take effect, the source code page must be UTF-8. The default, if not specified, iskeep
.
The following table describes the miscellaneous options. These options do not apply to transfer operations, but affect the behavior of Co:Z SFTP.
Table B.2. Miscellaneous options
|
The following table describes options that apply when transferring MVS datasets. The z/OS BPXWDYN service is used for dataset allocation and these options correspond to keywords available with BPXWDYN with similar syntax except that:
keyword=value
is used rather thankeyword(value)
periods are used in place of commas
other minor differences as described below
Note: If a local data set is referenced in a Co:Z SFTP batch job by
//DD:MYDD
, then dynamic allocation options do not apply.
In this case, options may be specified on the JCL DD statement.
The usage columns below describe when the option (if active) will apply during dataset transfer, as indicated by an X. A T is indicated for options that apply only to reading cataloged tape data sets. These options will only be used when allocating the tape data set if the "label" option is set. This can be useful for overriding DCB information or specifying DCB information for non-labeled tapes.
None of these options, with the exception of conddisp
, apply during POSIX file transfers.
For more information on BPXWDYN, see Using REXX and z/OS UNIX System Services - SA22-7806
Note | |
---|---|
|
Table B.3. BPXWDYN options
|