Dovetailed Technologies

2. Installation

This chapter explains how to install the Co:Z Toolkit on z/OS. Once the toolkit is installed, individual components can be configured for use. For component configuration details, consult the user's guides (referenced in Chapter 1, Introduction).

For questions, please visit the Dovetailed Technologies Co:Z Forum

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

  2. Upload file to the z/OS HFS or zFS file system. Make sure you transfer the file with a binary mode transfer option.

  3. Verify that the cksum command (cksum results match the checksum values published on the website download page.

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

  5. The installing userid should have READ access to the BPX.FILEATTR.APF SAF resource. If not, Co:Z will install without APF authorization on the ssh-socket-info utility, but will otherwise operate properly. See the Enabling SMF recording section in the Co:Z SFTP User's Guide for additional information.

  6. Make the installer file executable:

    $ chmod +x
  7. Run the installer:

    $ ./
    This software is licensed under the Co:Z Community License Agreement available
    for review at or as part of this 
    install package in file LICENSE (the "License").  
    Do you agree to the above license terms? [yes or no]
    Enter home directory [/usr/local/coz] : 1
    /usr/local/coz is not an existing directory, create it? [y/n] : 
    Enter new or existing target PDSE load module library name [SYS1.COZ.LOADLIB]: 2
    The PDSE load module library 'SYS1.COZ.LOADLIB' does not exist, create it? [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]: 3
    The PDS 'SYS1.COZ.SAMPJCL' does not exist, create it? [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]: 4
    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/ 
                       -> /usr/local/coz/bin/
    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 5
    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/ 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.

  8. z/OS OpenSSH must be available either as a component of z/OS (V2R2 or higher) or by installing IBM Ported Tools OpenSSH on older z/OS versions.

    Proper configuration and tuning of z/OS OpenSSH can greatly improve overall performance, specifially for z/OS ssh client startup times. See the version of our Quick Install Guides matching your z/OS OpenSSH version for additional information.

  9. Review the @@README member of the PDS containing Co:Z Sample JCL and PROCS. Tailor the following component specific members:

    • Co:Z Launcher and Dataset Pipes: COZPROC and COZCFGD

      • The RUNLNCH, RUNLNCHK, and RUNLNCHP are basic Co:Z Launcher samples using different authentication methods. Additional examples can be found in the User's Guide.


      • While other samples are provided, the SFTPSAMP member contains sample JCL for the perferred method of using the Co:Z SFTP client in batch. These samples use the Co:Z SFTP batch scripts installed in <COZ_HOME>/samples/sftp_batch. See Using the Co:Z SFTP client in batch in the User's Guide for additional information.

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

Copyright© 2009-2017 Dovetailed Technologies, LLC. All rights reserved.
Co:Z® is a registered trademark of Dovetailed Technologies, LLC.