Download the Co:Z z/OS self-extracting installer file (download available from coztoolkit.com).

Upload cksum coz-vv.rr.mml.bin file to the z/OS zFS file system. Make sure you transfer the file with a binary mode transfer option.

Verify that the cksum command (cksum coz-vv.rr.mml.bin) results match the checksum values provided.

The installation script requires a small amount of temporary space to run successfully. Ensure that your /tmp file system is not full.

The installing userid should be either UID=0 or have BPX.SUPERUSER authority or have both BPX.FILEATTR.APF and BPX.FILEATTR.PROGCTL authority. These permissions are required in order to enable APF authorization on the ssh-socket-info utility and to mark Co:Z SFTP programs as program controlled. If these permissions are not available during installation, the product will still install but may not work properly if SMF recording is enabled. See the Enabling SMF recording section in the Co:Z SFTP User's Guide for additional information.

Make the installer file executable:

$ chmod +x coz-vv.rr.mml.bin

Run the installer:

$ ./coz-vv.rr.mml.bin

  
This software is licensed under the Co:Z Community License Agreement available
for review at https://coztoolkit.com/docs/coz/licenses.html or as part of this 
install package in file LICENSE (the "License").

Please read the License carefully.  The License sets forth the terms on which
Dovetailed Technologies, LLC, a U.S. Missouri limited liability company, makes
available the Co:Z Co-Processing Toolkit for z/OS at no charge for download,
installation and use by the community. 

THIS COMMUNITY LICENSE DOES NOT PERMIT OUTSOURCERS TO INSTALL, MANAGE, OPERATE, 
OR SUPPORT THE SOFTWARE.

By downloading, installing, or using the software, you acknowledge that you 
have read, understand and agree to be legally bound by the License.         

Are you installing, managing, operating, or supporting this software on behalf 
of an outsourcing customer or other third party? (yes or no)
no
Will an outsourcer or other third party be installing, managing, operating, or 
supporting this software on your behalf? (yes or no)
no
Do you agree to the above terms and the License? (yes or no)
yes
Enter home directory (/usr/local/coz) : 
(Enter)
/usr/local/coz is not an existing directory, create it? (y/n) : 
y
Enter new or existing target PDSE load module library name (SYS1.COZ.LOADLIB): 
(Enter)
The PDSE load module library 'SYS1.COZ.LOADLIB' does not exist, create it? (y):
y
/usr/local/coz/loadmodules/COZBATCH -> //'SYS1.COZ.LOADLIB(COZBATCH)': executable
/usr/local/coz/loadmodules/COZLNCH -> //'SYS1.COZ.LOADLIB(COZLNCH)': executable

Enter new or existing PDS for Co:Z Sample JCL and PROCs (SYS1.COZ.SAMPJCL): 
(Enter)
The PDS 'SYS1.COZ.SAMPJCL' does not exist, create it? (y):
y
/usr/local/coz/sampjcl/@@README -> //'SYS1.COZ.SAMPJCL(@@README)': text
/usr/local/coz/sampjcl/COZCFGD -> //'SYS1.COZ.SAMPJCL(COZCFGD)': text
/usr/local/coz/sampjcl/COZPROC -> //'SYS1.COZ.SAMPJCL(COZPROC)': text
...

Enter PATH directory in which to create command symlinks or 'none' (/usr/local/bin): 
(Enter)
created symlink /usr/local/bin/catsearch -> /usr/local/coz/bin/catsearch
created symlink /usr/local/bin/cozserver -> /usr/local/coz/bin/cozserver
created symlink /usr/local/bin/cozsftp -> /usr/local/coz/bin/cozsftp
created symlink /usr/local/bin/fromdsn -> /usr/local/coz/bin/fromdsn
created symlink /usr/local/bin/pdsdir -> /usr/local/coz/bin/pdsdir
created symlink /usr/local/bin/read_passwd_dsn.sh 
                   -> /usr/local/coz/bin/read_passwd_dsn.sh
created symlink /usr/local/bin/saf-ssh-agent -> /usr/local/coz/bin/saf-ssh-agent
created symlink /usr/local/bin/safauth -> /usr/local/coz/bin/safauth
created symlink /usr/local/bin/todsn -> /usr/local/coz/bin/todsn
created symlink /usr/local/bin/zsym -> /usr/local/coz/bin/zsym

FOMF0303I /usr/local/bin/ssh-socket-info: chattr() error: rv=-1, errno=8B, rsn=0924041A 
***
Unable to set extended attributes for program bin/ssh-socket-info
  - see installation guide for more informantion
***

You should update user profiles so that MANPATH contains: /usr/local/coz/doc/man

*** Co:Z Installation complete  ****
(see README and LICENSE in install root directory for more information)
      

	Enter the name of a new or existing zFS or HFS directory that will become the top-level "home" directory for the Co:Z Toolkit installation. This directory must be in a filesystem that is writable by the installing user and contains 12MB of free space. If you supply the name of an existing directory that is not empty, you will be prompted to continue, as it is not generally advisable to overlay an existing installation with a new version.
	The fully-qualified name of the PDSE library to contain the Co:Z Launcher and Co:Z Batch program objects. If this dataset exists, it must be a PDSE and existing Co:Z load modules will be replaced.
	The fully-qualified name of the PDS library to contain sample JCL for the Co:Z Toolkit. If this dataset exists, if must be RECFM=FB,LRECL=80 and existing members with the same names will be replaced.
	Several Co:Z Toolkit Unix commands, such as cozsftp, fromdsn, todsn, etc. should be made available in user's PATH. One option is to customize /etc/profile to add <COZ_HOME>/bin to the PATH, but an alternative is to create symbolic links in an existing PATH directory to the Co:Z user commands in <COZ_HOME>/bin. To have the installation script create symbolic links, enter the name of the existing directory in which to create the links, or none to skip. When creating symlinks, this script will prompt you before replacing existing symlinks or files. The <COZ_HOME>/install/create-symlinks.sh script can be used to create these links at a later time, or to replace links to one Co:Z home directory (version) with links to another. See the comments in this script for more information and example usage.
	These messages will appear if the installing userid does not have READ access to the BPX.FILEATTR.APF SAF resource. Co:Z will install properly and can be used, but the SMF socket information is not guaranteed to be accurate. A similar error will occur if BPX.FILEATTR.PROGCTL permission is not available to mark Co:Z SFTP programs as "program controlled"

z/OS OpenSSH is a prerequisite for Co:Z. Proper configuration and tuning of z/OS OpenSSH can greatly improve overall performance, specifially for z/OS ssh client startup times. See our IBM z/OS OpenSSH - Quick Install Guide for additional information.

Review the @@README member of the PDS containing Co:Z Sample JCL and PROCS. Review the following component specific members ensuring that they have been correctly tailored for your configuration by the installation process:

For additional configuration and usage information, refer to the indiviual component User's Guides: