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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

pathname may be an absolute pathname (beginning with a slash) or a relative<br />

pathname (not beginning with a slash). When an absolute pathname is used,<br />

the symbolic link will be resolved starting at the root directory. When a relative<br />

pathname is used, the symbolic link will be resolved starting at the parent<br />

directory of the symbolic link.<br />

For JCL, the maximum length for a pathname is limited by the 100 character<br />

limit on the entire PARM string (including other parameters) on the EXEC<br />

statement. Pathnames with a length of up to 1023 characters can be specified if<br />

BPXCOPY is invoked from LINK, XCTL, or ATTACH, a TSO/E CALL command,<br />

or by a CALL after a LOAD.<br />

Specifying SYMPATH is optional, but if you specify SYMPATH, you must also<br />

specify SYMLINK. Each SYMLINK linkname must be matched with a<br />

corresponding SYMPATH pathname. The first linkname will define a symbolic<br />

link to the first pathname, the second linkname will define a symbolic link to the<br />

second pathname, etc. If there are fewer pathnames than linknames, the last<br />

pathname will be used for the remaining linknames.<br />

PATHMODE (mode_bits)<br />

Changes the access permissions, or modes, of the specified file or directory.<br />

Modes determine who can read, write, or search a directory. The bits are used<br />

to set execution and permission access of the output file. On BPXCOPY, you<br />

can specify PATHMODE as an absolute mode; it must consist of four octal<br />

numbers separated by commas or blanks.<br />

Absolute modes are four octal numbers specifying the complete list of attributes<br />

for the files; you specify attributes by ORing together the bits for each octal<br />

number.<br />

4,0,0,0 Set-user-ID bit<br />

2,0,0,0 Set-group-ID bit<br />

1,0,0,0 Sticky bit<br />

0,4,0,0 Individual read<br />

0,2,0,0 Individual write<br />

0,1,0,0 Individual execute (or list directory)<br />

0,0,4,0 Group read<br />

0,0,2,0 Group write<br />

0,0,1,0 Group execute<br />

0,0,0,4 Other read<br />

0,0,0,2 Other write<br />

0,0,0,1 Other execute<br />

Specifying PATHMODE is optional.<br />

For more information on permission bits, see the chmod command.<br />

BPXCOPY<br />

TYPE (TEXT|BINARY)<br />

The format for the HFS file. The default is BINARY for U-format data sets and<br />

TEXT for all others. (U-format means undefined-length records.) Specifying<br />

TYPE is optional.<br />

APF|NOAPF<br />

Specifies whether the APF extended attribute is set or unset. When this<br />

attribute is set (APF) on an executable program file (load module), it behaves<br />

as if loaded from an APF-authorized library. For example, if this program is<br />

exec()ed at the job step level and the program is linked with the AC = 1<br />

attribute, the program will be executed as APF-authorized.<br />

To be able to set APF, you must have at least READ access to the<br />

BPX.FILEATTR.APF resource in the FACILITY class. For more information, see<br />

z/<strong>OS</strong> <strong>UNIX</strong> <strong>System</strong> <strong>Services</strong> Planning.<br />

Appendix E. BPXCOPY: Copying a sequential or partitioned data set or PDSE member into an HFS file 903

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

Saved successfully!

Ooh no, something went wrong!