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

mv
3. If you specify a UNIX file as source and the MVS data set (target) does not
exist, a sequential data set will be created. If the partitioned data set exists, the
UNIX file will be moved to the partitioned data set member.
4. If source is an MVS data set and target is a UNIX directory, the UNIX directory
must exist.
5. You cannot have a UNIX directory, partitioned data set, or sequential data set
as source if the target is a partitioned data set.
6. To move all members from a partitioned data set, you may specify the
partitioned data set as source and a UNIX directory as target.
MVS data set naming limitations
v Data set names may only contain uppercase alphabetic characters (A-Z).
Lowercase characters will be converted to uppercase during any moves to MVS
data sets.
v Data set names can contain numeric characters 0–9 and special characters @,
#, and $.
v Data set names cannot begin with a numeric character.
v A data set member name cannot be more than 8 characters. If a filename is
longer than 8 characters or uses characters that are not allowed in an MVS data
set name, the file is not moved. You may use the –C option to truncate names to
8 characters.
Limitations: UNIX to MVS data set
1. If you specify a sequential MVS data set that is in undefined record format, the
file is moved as binary.
2. If you specify a PDSE that is in undefined record format, the first file
successfully moved determines in what format files will be moved. Note that
PDSE does not allow mixture. So if the first successfully moved file is an
executable, the PDSE will have program objects only and all other files will fail.
On the other hand, if the first file is data, then all files are moved as binary.
3. If you specify a PDS that is in undefined record format, UNIX executables are
saved as PDS load modules. All other files are moved as binary.
4. If you specify an MVS data set that is either in variable length or fixed record
length and you have not set the file format, text files are moved as text, binaries
as binary, and executables as binary. (IBM-1047 end-of-line delimiters are
detected in the data)
5. If you set the file format, the set value is used to determine if data is binary or
text.
Limitations: MVS data set to UNIX
1. If an UNIX file does not exist, one is created using 666 mode value, whether the
data to be copied is binary or text:
666 mode value: owner(rw-) group(rw-) other(rw-)
If the data to be copied is a shell script or executable residing in a PDS or
PDSE with undefined record format, the UNIX file is created using 777 mode
value:
777 mode value: owner(rwx) group(rwx) other(rwx)
2. If a UNIX file exists and the file format is set, mv moves the file as that format.
Otherwise,
v load modules (PDS) are stored as UNIX executables and program objects
(PDSE) are moved since they are the same as executables;
444 z/OS V1R9.0 UNIX System Services Command Reference