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

OCOPY
Usage notes
TO1047 | FROM1047
TO1047
Specifies that the TO topic of the character conversion table is to be used.
This is usually used to convert from code page IBM-037 or ASCII to code
page IBM-1047.
FROM1047
Specifies that the FROM topic of the conversion table is to be used. This is
usually used to convert from code page IBM-1047 to code page IBM-037 or
ASCII.
If the CONVERT operand is specified and this operand is omitted,
v Data copied from an MVS data set to a file uses the TO1047 topic of the
table.
v Data copied from a file to an MVS data set uses the FROM1047 topic of
the table.
If the CONVERT operand is specified for a copy from a file to a file or an
MVS data set to an MVS data set, you must specify either TO1047 or
FROM1047.
1. You can use OCOPY to copy a program object from a PDSE to the file system,
and it will be executable there. If you have a load module in a partitioned data
set, however, you must first use the IEBCOPY program to copy the load module
from a partitioned data set to a PDSE and then subsequently use OCOPY to
copy the module into the file system. The IEBCOPY converts the load module to
a program object.
Note: You can use the linkage editor to put the load module directly into the file
system.
2. An executable file copied from the file system into an MVS data set is not
executable under MVS. Some required directory information is lost during the
copy. See z/OS UNIX System Services User’s Guide for a discussion of copying
executable files.
3. Data sets with spanned records are not allowed.
4. When you are copying into an existing file, data is appended to the end of the
file if OAPPEND is specified in PATHOPTS. Otherwise, the existing file is
overwritten.
5. Copying from z/OS UNIX file system text files to MVS data sets:
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.
– 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.
– For an MVS data set in variable record format: Any line longer than
the largest record size is truncated and the record length is set
accordingly. A change in the record length also occurs if the line is short.
6. Copying from z/OS UNIX file system binary files to MVS data sets:
For binary files, all data is preserved.
842 z/OS V1R9.0 UNIX System Services Command Reference