16.12.2012 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

OCOPY<br />

Parameters<br />

v A file to an MVS sequential data set<br />

v A file to a file<br />

v A member of an MVS PDS or PDSE to another member of an MVS PDS or<br />

PDSE<br />

v A member of an MVS PDS or PDSE to an MVS sequential data set<br />

v An MVS sequential data set to another MVS sequential data set<br />

v An MVS sequential data set to a member of an MVS PDS or PDSE<br />

Both INDD and OUTDD can represent an MVS data set or a file. If the source<br />

(INDD) is an MVS data set and the target (OUTDD) is an z/<strong>OS</strong> <strong>UNIX</strong> file system<br />

file, then OCOPY copies an MVS data set to a file; the operation is the same as the<br />

OPUT command. If the source (INDD) is an z/<strong>OS</strong> <strong>UNIX</strong> file system file and the<br />

target (OUTDD) is an MVS data set, then OCOPY copies a file to an MVS data set;<br />

the operation is the same as the OGET command.<br />

Both the target and source can be an MVS data set or member of a partitioned<br />

data set, or both can be a file. This function is typically used for code page<br />

conversion.<br />

If PATHMODE, which sets the permission bits for a new file, is specified during<br />

allocation, it is used when creating a new file. If PATHMODE is not specified during<br />

the allocation of a new file, the allocation creates a file with the default permission<br />

of 000, which means the user has no access to it.<br />

INDD(ddname1)<br />

Specifies the ddname of the source. The ddname is up to 8 characters long.<br />

OUTDD(ddname2)<br />

Specifies the ddname of the target. The ddname is up to 8 characters long.<br />

BINARY | TEXT<br />

Specifies that the data to be copied is a binary file or text file.<br />

BINARY<br />

Specifies that the data to be copied is a binary file. The default is binary<br />

when copying a data set of undefined record format to a file.<br />

When you specify BINARY, OCOPY operates without any consideration for<br />

characters or the special characteristics of DBCS data. For<br />

example, doublebyte characters might be split between MVS data set<br />

records, or a “shift-out” state might span records.<br />

TEXT<br />

Specifies that the data to be copied is a text file. The default is text except<br />

when copying a data set of undefined record format to a file.<br />

If you are using a DBCS-supported terminal, you should use TEXT. It is<br />

assumed that doublebyte data in the file system includes the <br />

character in order to delineate line boundaries. Data within these lines that<br />

are delineated by characters must begin and end in the “shift-in”<br />

state.<br />

CONVERT(character_conversion_table | YES | NO)<br />

Specifies the character conversion table used to convert between the following:<br />

v Code pages IBM-037 and IBM-1047<br />

v The ASCII code page and IBM-1047<br />

840 z/<strong>OS</strong> <strong>V1R9.0</strong> <strong>UNIX</strong> <strong>System</strong> <strong>Services</strong> <strong>Command</strong> Reference

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!