For command descriptions, see the site and
lsite command in sftpg3(1) and the
--dst-site
and --src-site
options in scpg3(1).
When giving the command, either the full parameter name or its abbreviation can be used. For example, the following two commands accomplish the same thing:
sftp> site x=bin sftp> site transfer_mode=bin
The available site parameters are listed and described in the following.
Table 5.1. site parameters
Parameter | Abbreviations | Possible values |
---|---|---|
AUTOMOUNT
|
-
|
YES|NO|IMMED
|
[NO]AUTOMOUNT
|
[NO]AUTOM
|
-
|
AUTORECALL
|
-
|
YES|NO
|
[NO]AUTORECALL
|
[NO]AUTOR
|
-
|
BLKSIZE
|
B, BLOCKSI
|
size
|
BLOCKS
|
BL
|
-
|
CONDDISP
|
CO
|
CATLG|UNCATLG|KEEP|DELETE
|
CYLINDERS
|
CY
|
-
|
DATACLAS
|
DA
|
class
|
DATASET_SEQUENCE_NUMBER
|
SEQNUM
|
number
|
DEFER
|
DE
|
YES|NO
|
[NO]DEFER
|
-
|
-
|
DIRECTORY_SIZE
|
M, DI, DIRSZ
|
size
|
EXPIRY_DATE
|
EXPDT
|
yyddd
|
yyyyddd
|
FILE_STATUS
|
STATUS
|
NEW|MOD|SHR|OLD
|
FILETYPE
|
FILET
|
SEQ|JES
|
FIXRECFM
|
FI
|
length
|
JOB_ID
|
JESID
|
ID
|
JOB_OWNER
|
JESO
|
name
|
JOBNAME
|
JESJOB
|
name
|
KEYLEN
|
KEYL
|
length
|
KEYOFF
|
KEYO
|
offset
|
LABEL_TYPE
|
LABEL
|
NL|SL|NSL|SUL|BLP|LTM|AL|AUL
|
LIKE
|
-
|
like
|
LRECL
|
R, LR
|
length
|
MGMTCLAS
|
MG
|
class
|
NORMDISP
|
NOR
|
CATLG|UNCATLG|KEEP|DELETE
|
PRIMARY_SPACE
|
PRI
|
space
|
PROFILE
|
P, PROF
|
profile
|
RECFM
|
O, REC
|
recfm
|
RECORD_TRUNCATE
|
U, TRUN
|
YES|NO
|
[NO]TRUNCATE
|
[NO]TRU, [NO]TRUN
|
-
|
RETENTION_PERIOD
|
RET
|
days
|
SECONDARY_SPACE
|
SE, SEC
|
space
|
SIZE
|
L
|
size
|
SPACE_RELEASE
|
RLSE
|
YES|NO
|
SPACE_UNIT
|
SU
|
BLKS|TRKS|CYLS|AVGRECLEN
|
SPACE_UNIT_LENGTH
|
SUL
|
length
|
STAGING
|
S, STAGE
|
YES|NO
|
STORCLAS
|
ST
|
class
|
SVC99_TEXT_UNITS
|
SVC99
|
string
|
TRACKS
|
TR
|
-
|
TRAILING_BLANKS
|
TRAIL
|
YES|NO
|
[NO]TRAILINGBLANKS
|
[NO]TRAI, [NO]TRAIL
|
-
|
TRANSFER_CODESET
|
C, CODESET
|
codeset
|
TRANSFER_FILE_CODESET
|
D, FCODESET
|
codeset
|
TRANSFER_FILE_LINE_DELIMITER
|
J, FLDELIM
|
UNIX|MVS|MVS-FTP|DOS|MAC|NEL
|
TRANSFER_FORMAT
|
F, FORMAT
|
LINE|STREAM|RECORD
|
TRANSFER_LINE_DELIMITER
|
I, LDELIM
|
UNIX|MVS|MVS-FTP|DOS|MAC|NEL
|
TRANSFER_MODE
|
X, MODE
|
BIN|TEXT
|
TRANSFER_TRANSLATE_DSN_TEMPLATES
|
A, XDSNT
|
templates
|
TRANSFER_TRANSLATE_TABLE
|
E, XTBL
|
table
|
TYPE
|
T
|
PS|PO|PDS|POE|PDSE|GDG|HFS|VSAM|ESDS|KSDS|RRN
|
UNIT
|
UN
|
unit
|
UNIT_COUNT
|
UC, UNC
|
number
|
UNIT_PARALLEL
|
UNP
|
YES|NO
|
VOLUME_COUNT
|
VC, VOLCNT
|
number
|
VOLUMES
|
VO, VOL
|
vol1+vol2+...
|
AUTOMOUNT=YES|NO|IMMED
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
[NO]AUTOMOUNT|[NO]AUTOM
AUTOMOUNT|AUTOM
is equal to AUTOMOUNT=YES
.
NOAUTOMOUNT|NOAUTOM
is equal to AUTOMOUNT=NO
.
AUTORECALL=YES|NO
Defines whether data sets migrated by a storage manager are recalled automatically.
Default: YES
[NO]AUTORECALL|[NO]AUTOR
AUTORECALL|AUTOR
is equal to AUTORECALL=YES
.
NOAUTORECALL|NOAUTOR
is equal to AUTORECALL=NO
.
BLKSIZE|B|BLOCKSI=
size
Specifies the maximum block size.
Default: none
BLOCKS|BL
Specifies that the space allocation unit is blocks. Equal to
SPACE_UNIT=BLKS
.
CONDDISP|CO=CATLG|UNCATLG|KEEP|DELETE
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):
CATLG
: an MVS data set is retained and its name is cataloged. An
HFS file is retained.
UNCATLG
: the name of an MVS data set is removed from the catalog
but the data set is retained. An HFS file is retained.
KEEP
: an MVS data set is retained (if cataloged it will be still
cataloged, if uncataloged it will be still uncataloged). An HFS file is retained.
DELETE
: the name of an MVS data set is removed from the catalog and
the space allocated for the data set is released. An HFS file is deleted.
Default: CATLG
CYLINDERS|CY
Specifies that the space allocation unit is cylinders. Equal to
SPACE_UNIT=CYLS
.
DATACLAS|DA=
class
Specifies the data class of a data set.
Default: none
DATASET_SEQUENCE_NUMBER|SEQNUM=
number
Identifies the relative position of a data set on a tape volume.
Default: System default
DEFER|DE=YES|NO
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
[NO]DEFER|DE
DEFER|DE
is equal to DEFER=YES
.
NODEFER
is equal to DEFER=NO
.
DIRECTORY_SIZE|M|DI|DIRSZ=
size
Specifies the number of 256-byte records in the directory.
Default: 10
EXPIRY_DATE|EXPDT=
yyddd|yyyyddd
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
FILE_STATUS|STATUS=NEW|MOD|SHR|OLD
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:
NEW
: Create a data set.
MOD
: Append to an existing data set. If the data set does not
exist, a new data set is created.
SHR
: Create a read-only data set.
OLD
: Designate an existing data set.
FILETYPE|FILET=SEQ|JES
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, and get and sget
commands to retrieve spool data sets. 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
FIXRECFM|FI=
length
The data set organization is set to FB
and the fixed record length is
set to length
.
Default: none
JOB_ID|JESID=
ID
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
.
Commands get, sget, and so on, with a job ID can be used to retrieve the spool files for a given job.
JOB_OWNER|JESO=
name
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
JOBNAME|JESJOB=
name
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
.
KEYLEN|KEYL=
length
Specifies the length in bytes of the keys used in the data set.
Default: none
KEYOFF|KEYO=
offset
Specifies the key offset; the position of the first byte of the key in records of the specified VSAM data set.
Default: none
LABEL_TYPE|LABEL=NL|SL|NSL|SUL|BLP|LTM|AL|AUL
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 |
LIKE=
like
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
LRECL|R|LR=
length
Maximum record length or fixed record length.
Default: 4096
for VSAM, 80
if data set organization is
F
or FB
, otherwise 1024
MGMTCLAS|MG=
class
Specifies the management class of a data set.
Default: none
NORMDISP|NOR=CATLG|UNCATLG|KEEP|DELETE
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|PRI=
space
Primary space allocation for a data set.
Default: none
PROFILE|P|PROF=
profile
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|O|REC=
recfm
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
RECORD_TRUNCATE|U|TRUN=YES|NO
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 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 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 writes a data set with |
[NO]TRUNCATE|[NO]TRU|[NO]TRUN
TRUNCATE|TRU|TRUN
is equal to RECORD_TRUNCATE=YES
.
[NO]TRUNCATE|[NO]TRU|[NO]TRUN
is equal to
RECORD_TRUNCATE=NO
.
RETENTION_PERIOD|RET=
days
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|SE|SEC=
space
Secondary space allocation for a data set.
Default: none
SIZE|L=
size
Size estimate (in bytes) for data set allocation.
Default: 1000000
SPACE_RELEASE|RLSE=YES|NO
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
SPACE_UNIT|SU=BLKS|TRKS|CYLS|AVGRECLEN
Unit of space allocation for a data set.
Possible values for the space allocation unit are:
BLKS
: Blocks
CYLS
: Cylinders
TRKS
: Tracks
AVGRECLEN
: Average record length
Default: none
SPACE_UNIT_LENGTH|SUL=
length
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
STAGING|S|STAGE=YES|NO
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 |
STORCLAS|ST=
class
Specifies the storage class of system managed storage.
Default: none
SVC99_TEXT_UNITS|SVC99=
string
Dynamic allocation arguments that override or are added to arguments from other file transfer attributes.
Default: none
TRACKS|TR
Specifies that the space allocation unit is tracks. Equal to
SPACE_UNIT=TRKS
.
TRAILING_BLANKS|TRAIL=YES|NO
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
( |
[NO]TRAILINGBLANKS|[NO]TRAI|[NO]TRAIL
TRAILINGBLANKS|TRAI|TRAIL
is equal to TRAILING_BLANKS=YES
.
NOTRAILINGBLANKS|NOTRAI|NOTRAIL
is equal to
TRAILING_BLANKS=NO
.
TRANSFER_CODESET|C|CODESET=
codeset
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: A Windows SFTP client puts a file to a z/OS data set and gets a data set from z/OS
sftp> site C=ISO8859-1 D=IBM-1047 sftp> sput file.txt //DATASET.TXT sftp> sget //DATASET.TXT file.txt
The z/OS server is told that the code set during transfer is ISO8859-1 and that the data set is stored on the server with the IBM-1047 code set. | |
The server converts the code set from ISO8859-1 to IBM-1047 upon receiving the data. | |
The server converts the code set from IBM-1047 to ISO8859-1 before sending the data. |
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. |
TRANSFER_FILE_CODESET|D|FCODESET=
codeset
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
TRANSFER_FILE_LINE_DELIMITER|J|FLDELIM=UNIX|MVS|MVS-FTP|DOS|MAC|NEL
The transfer file line delimiter specifies the newline convention used in the (source or destination) file. Possible values are:
UNIX
: The line delimiter used in the file is LF
(\n
, 0x0A
).
MVS
: The line delimiter used in the file is NL
(\n
, 0x15
). When writing to a data set, also
the CR (\r
, 0x0D
) code is considered as the End
of Line.
MVS-FTP
: When reading MVS data sets, each record in the data set is
treated as a line. The transfer line delimiter is appended to the record. Any control
characters in the record data are preserved.
When reading data sets with printer control characters, the control characters are preserved in the output.
If the code set conversion is specified either by
TRANSFER_TRANSLATE_TABLE|E
, or by TRANSFER_CODESET|C
and TRANSFER_FILE_CODESET|D
, the appended delimiter is the delimiter
specified by TRANSFER_LINE_DELIMITER|I
,
TRANSFER_CODESET|C
, or TRANSFER_TRANSLATE_TABLE|E
.
If no code set conversion is requested, the delimiter is defined by the code set of the
data set. By default it is EBCDIC.
You can specify code sets by defining TRANSFER_FILE_CODESET
without
TRANSFER_CODESET
. For example, to have a DOS delimiter in Unicode
(x'000D000A'
) appended to the records, set
"I=DOS,J=MVS-FTP,D=UCS-2
", and to have a Unix delimiter in ISO Latin
1 (x'0A'
), set "I=UNIX,J=MVS-FTP,D=ISO8859-1
".
Do not use this when writing data sets.
DOS
: The line delimiter used in the file is CRLF
(\r\n
, 0x0D 0x0A
).
MAC
: The line delimiter used in the file is CR
(\r
, 0x0D
).
NEL
: The line delimiter used in the file is Unicode New Line
(0x85
).
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
|
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.
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
Transfer line delimiter is set to | |
Transfer code set is set to IBM-437 and transfer file code set to IBM-1047. | |
The z/OS client inserts a NL ( | |
The CRLF line delimiters are converted to LF characters, which are converted to NL characters in the code set conversion. Each NL character (and CR character, if there are any in the data) causes the current record to be written out and a new record started. |
TRANSFER_FORMAT|F|FORMAT=LINE|STREAM|RECORD
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.
LINE
: The line transfer format is record-based. It uses delimiter
characters to mark the end of a record. The delimiter character may be a Carriage Return
(CR) or a Newline (NL). When writing to or reading from data sets with ASA control
characters, a Form Feed (FF) is also treated as a delimiter. The table below shows the
values of these characters in EBCDIC and ASCII. Data sent to Tectia Client in the line
transfer format must be in EBCDIC or must be converted to EBCDIC during the
transfer.
Delimiter EBCDIC ASCII Name Dec Oct Hex Name Dec Oct Hex \r Carriage Return CR 13 015 0x0D CR 13 015 0x0D \n Newline NL 21 025 0x15 LF 10 012 0x0A \f Form Feed FF 12 014 0x0C FF 12 014 0x0C
Note that ASCII does not have a NL character, instead Line Feed (LF) is used to delimit lines.
Avoid conversions that transform an ASCII Line Feed
(LF/10/012/0x0A
) into an EBCDIC Line Feed
(LF/37/045/0x25
) or an EBCDIC Newline
(NL/21/025/0x15
) into an ASCII Next Line
(NEL/133/0205/0x85
).
Be aware that sending a double delimiter, e.g. \r\n
or
\n\r
, to Tectia Client will result in two records. The
TRANSFER_LINE_DELIMITER
and
TRANSFER_FILE_LINE_DELIMITER
attributes can be used to cause the
Tectia Client server or client program to convert between the line delimiter
conventions.
Tectia Client sends \n
as the Server Newline Convention in the
server initialization SFTP protocol message.
When transferring line format data to and from MVS files with ASA line printer control characters, Tectia Client will convert between the control characters and line delimiter characters, as described in the IBM z/OS XL C/C++ Programming Guide, Chapter "Using ASA Text Files".
To transfer records without changing the ASA code, use the STREAM
or RECORD
transfer format, or define the data set using a DD card and
specify RECFM=FB
or RECFM=VB
.
Data sets transferred in the line transfer format and recreated on a mainframe will not necessarily be identical.
STREAM
: The stream transfer format contains the data bytes of the
data set but no structural information. If a data set with a fixed record length is
transferred with the stream format and recreated with the same record length, the record
structure will be preserved. Variable length records will not be recreated properly if
transferred with the stream format.
RECORD
: The record transfer format is record-based. Each record is
preceded by a length field consisting of a 4- byte big-endian binary integer, which
indicates the number of data bytes in the record. Note that the format is not the same
as the record descriptor word in data sets with RECFM=V
or
RECFM=VB
.
A data set that is transferred with the record transfer format can be recreated as any data set type.
Default: LINE
.
TRANSFER_LINE_DELIMITER|I|LDELIM=UNIX|MVS|MVS-FTP|DOS|MAC|NEL
The transfer line delimiter specifies the newline convention used in the data that is transferred over the connection. Possible values are:
UNIX
: The line delimiter on the connection is LF
(\n
, 0x0A
).
MVS
: The line delimiter on the connection is NL
(\n
, 0x15
). If the data is converted from
EBCDIC to ASCII, the NL becomes a LF (\n
,
0x0A
).
MVS-FTP
: When writing to a data set, only the LF
(\n
, 0x0A
) control codes are considered as an
End Of Line. Any CR (\r
, 0x0D
) codes are
preserved as data in the record.
When writing data sets with ASA printer control characters, the first character on each line is used as the ASA character.
Do not use this when reading data sets.
DOS
: The line delimiter on the connection is CRLF
(\r\n
, 0x0D 0x0A
).
MAC
: The line delimiter on the connection is CR
(\r
, 0x0D
).
NEL
: The line delimiter used in the file is Unicode New Line
(0x85
).
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. |
TRANSFER_MODE|X|MODE=BIN|TEXT
The transfer mode specifies whether code set and line delimiter conversions are performed. The available values are:
BIN
: Code set and line delimiter conversions are not
performed.
TEXT
: Code set and line delimiter conversions are performed.
Default: none
Note | |
---|---|
If |
TRANSFER_TRANSLATE_DSN_TEMPLATES|A|XDSNT=
templates
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.
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
|
Default: none
TRANSFER_TRANSLATE_TABLE|E|XTBL=
table
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).
TYPE|T=PS|PO|PDS|POE|PDSE|GDG|HFS|VSAM|ESDS|KSDS|RRN
Specifies the type of a data set when the data set is created. The available values are:
PS
: The type of the created data set is PS.
PO|PDS
: The type of the created data set should be PDS. Note that
in order to create a PDS, you need to specify the DIRECTORY_SIZE
parameter. If you do not specify
the directory size, a sequential data set - not a partitioned data set - is
created.
POE|PDSE
: The type of the created data set is PDSE.
GDG
: The type of the created data set is GDG.
HFS
: The type of the created data set is HFS.
VSAM
: The type of the created data set is VSAM.
ESDS
: The type of the created data set is VSAM ESDS.
KSDS
: The type of the created data set is VSAM KSDS.
RRN
: The type of the created data set is VSAM RRN.
Default: PO
, if data set name includes member, otherwise
PS
UNIT|UN=
unit
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
UNIT_COUNT|UC|UNC=
number
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
UNIT_PARALLEL|UNP=YES|NO
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
VOLUME_COUNT|VC|VOLCNT=
number
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
VOLUMES|VO|VOL=
vol1+vol2+...
A plus sign (+) separated list of volumes a data set will reside on (or does reside on, if it already exists).
Default: none