Creating a program object in a z/OS UNIX file

To place a program object in a z/OS UNIX file, specify the PATH parameter on the SYSLMOD DD statement in a batch bind job. You can also use the binder application programming interface or the z/OS® UNIX c89 or ld command. You can use the following TSO commands to copy a program object between a PDSE to and a z/OS UNIX file:
  • OGET
  • OGETX
  • OPUT
  • OPUTX
The following z/OS UNIX System Services commands will also allow you to copy and move executables between a PDSE and z/OS UNIX files:
  • cp
  • mv
Additional information on this topic can be found in the following documents:

When specifying PATH in a batch bind job, you can provide either the complete path name or a directory. If the PATH parameter designates a directory, you must provide the file name on a NAME statement. The name on the NAME statement must be no longer than 255 bytes.

You can also specify the PATHOPTS and PATHMODE parameters in the JCL. If you do not, and the JCL designates a directory, the binder assigns attributes for the created file that allow only the file owner to have read, write, and execute authority.

If you specify the PATH parameter for SYSLMOD, the save operation is always processed as though you had specified REPLACE. Also, if you attempt to save a program object to a z/OS UNIX file and do not provide a name through the NAME control statement, the binder does not create a temporary name as it does when you save to a partitioned data set or PDSE under the same circumstance. Refer to the NAME statement in Binder control statement reference for a description of said condition.

You can provide an ALIAS control statement to designate the pathname to be used for an alias. The binder appends the path information on the SYSLMOD DD statement to each operand on the ALIAS control statement in order to form each complete alias pathname.