Copying data using TSO/E commands
You use TSO/E commands to copy data:
- Between the z/OS UNIX file system and MVS™ data sets
- Within MVS data sets.
The TSO/E commands that enable you to do this are:
- OPUT
- Puts (copies) an MVS sequential data set or partitioned data set (PDS or PDSE) member into the file system. You can specify text or binary data, and select code page conversion for single-byte data.
- OPUTX
- Puts (copies) a sequential data set, a data set member, an MVS partitioned data set, or a PDSE into a z/OS UNIX directory. You can specify text or binary data, select code page conversion for single-byte data, specify a copy to lowercase file names, and append a suffix to the member names when they become file names.
- OGET
- Gets a z/OS UNIX file and copies it into an MVS sequential data set or partitioned data set member. You can specify text or binary data, and select code page conversion for single-byte data.
- OGETX
- Gets a z/OS UNIX file or directory and copies it into an MVS partitioned data set, PDSE, or sequential data set. You can specify text or binary data, select code page conversion for single-byte data, allow a copy from lowercase file names, and delete one or all suffixes from the file names when they become PDS member names.
- OCOPY
- Copies data in either direction between an MVS data set and a z/OS UNIX file, using ddnames. OCOPY can also copy within MVS (one data set to another data set) or within the shell (one file to another file). OCOPY has a CONVERT operand for converting single-byte data from one code page to another.
For examples of using these commands, see:
- Using OPUT and OCOPY to copy a PDS member, a PDSE member, or a sequential data set
- Using OPUTX to copy a sequential data set or members of a PDS or PDSE
- Copying an MVS VSAM data set to a z/OS UNIX file
- Using OGET and OCOPY to copy a file into a sequential data set or a PDS member
- Copying z/OS UNIX files into a PDS or PDSE
- Copying an MVS data set into another MVS data set
- Using TSO/E commands and JCL to copy executables
You can also invoke BPXCOPY as a TSO/E command as described in the BPXCOPY command description in z/OS UNIX System Services Command Reference, but the OPUT interface is generally more appropriate.
For information about the TSO/E OPUT, OPUTX, OGET, OGETX, and OCOPY commands, see z/OS UNIX System Services Command Reference.
For information about the TSO/E ALLOCATE and FREE commands, see z/OS TSO/E Command Reference. These commands have z/OS UNIX keyword parameters. It is a good idea to use the TSO/E FREE command to free the allocated data set when you have finished copying to or from a data set.