z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

Usage notes
– BPXFX311. Specifies an ASCII-EBCDIC conversion table to convert
between code pages ISO8859-1 and IBM-1047.
YES
Specifies that the system is to perform conversion and use the default
conversion table (BPXFX000) in the standard library concatenation.
(BPXFX000 is an alias; when shipped by IBM, it points to BPXFX111.)
NO
Specifies that conversion not be done. NO is the same as omitting the
CONVERT operand.
OGET
Do not use the CONVERT parameter on files containing doublebyte data.
Doublebyte data in the file system is in code page 939. If you need to convert
to a code page other than 939, you use the iconv command.
1. For text files, all characters are stripped during the copy. Each line in
the file ending with a character is copied into a record of the MVS
data set. You cannot copy a text file to an MVS data set in an undefined record
format.
v For an MVS data set in fixed record format: Any line longer than the
record size is truncated. If the line is shorter than the record size, the record
is padded with blanks.
v For an MVS data set in variable record format: Any line longer than the
largest record size is truncated; the record length is set to the length of the
line. A change in the record length also occurs if the line is short.
For text mode transfer, if the line is longer than the record size, the line is
truncated (for DBCS, perhaps in the middle of a doublebyte character or in
“shift-in” state). If the line is shorter than the record size, the record is padded
with blanks.
2. For binary files, all data is preserved.
v For an MVS data set in fixed record format: Data is cut into chunks of size
equal to the record length. Each chunk is put into one record. The last record
is padded with spaces or blanks.
v For an MVS data set in variable record format: Data is cut into chunks of
size equal to the largest record length. Each chunk is put into one record.
The length of the last record is equal to the length of the data left.
v For an MVS data set in undefined record format: Data is cut into chunks
of size equal to the block size. Each chunk is put into one record. The length
of the last record is equal to the length of the data left.
For binary mode transfers, doublebyte characters might be split between MVS
data set records, or a “shift-out” state might span records.
3. If the MVS data set does not exist, OGET allocates a new data set, a sequential
data set of variable record format. However, OGET does not allocate a new
partitioned data set. The record length of the new data set is either 255 or the
size of the longest line in the z/OS UNIX file system file, whichever is larger.
Dynamic allocation services determine the block size and space, based on
installation-defined defaults. If the defaults are not sufficient, you should allocate
a new MVS data set and then specify it on OGET.
A simple method of allocating a sufficient size is to specify a primary extent size
and a secondary extent size equal to the number of bytes in the file being
copied.
Chapter 3. TSO/E commands 847