...
The following figure illustrates the syntax — using the long form of command line options — of Universal Copy for Windows and UNIX.
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| Html bobswift | ucopy
[-level Html bobswift | {<b>trace</b>|<b>audit</b>|<b>info</b>|<b>warn</b>|<b>error</b>trace|audit|info|warn|error}] [ -mode Html bobswift | {<b>binary</b>|<b>text</b>binary|text}] [ -output Html bobswift | filename [ -transactional Html bobswift | {<b>yes</b>|<b>no</b>yes|no}] [ -replace Html bobswift | {<b>yes</b>|<b>no</b>yes|no}] ] [<i>file</i> file ...] ucopy { -version Html bobswift | | -help Html bobswift | }
</pre>
|
Command Operands
FILE
The file operand specifies the input files. Full or relative paths can be specified.
...
| Info | ||||
|---|---|---|---|---|
| ||||
z/OS USS permits the specification of files located in the hierarchical file system (HFS) and z/OS data sets. HFS files are specified simply as UNIX file names. z/OS data sets are specified using the IBM USS // convention, which prefixes the data set name with the characters //. The syntax is as follows:
In order for the USS shell to interpret the forward slash ( / ) characters correctly, the complete file name must be enclosed in double ( " ) quotation marks on the USS command line. The data set name adheres to TSO naming conventions; if it is not enclosed in apostrophes, your USS user name is used as the high-level qualifier. For example, "//my.data" refers to data set USERID.MY.DATA. |
...