[Contents] [Index]

About This Document >>     Installing SSH Tectia Server for IBM z/OS >>         Preparing for Installation >>         Installing the SSH Tectia Server for IBM z/OS Software >>             Unpacking the Installation Package             Creating the SAMPLIB and PARMLIB Directories             Preparing the System             Creating the SSHD2 User             Creating the /usr/lpp/ssh2 Directory             Running the Setup Script             Enabling Manual Pages         Upgrading the SSH Tectia Server for IBM z/OS Software         Removing the SSH Tectia Server for IBM z/OS Software     Getting Started with SSH Tectia Server for IBM z/OS >>     Configuring the Server >>     Configuring the Client >>     Authentication >>     File Transfer Using SFTP >>     File Transfer Using Transparent FTP Tunneling >>     Tunneling on the Command Line >>     Troubleshooting SSH Tectia Server for IBM z/OS >>     Advanced Information >>     Man Pages >>     Log Messages >>

Running the Setup Script

Note: Before continuing the installation, make sure that all the required permissions, SSHD2 user account and /usr/lpp/ssh2/ directory are set. The user account used for running the setup script must have read access to the BPX.FILEATTR.PROGCTL FACILITY.

Go to the directory into which the installation package was unpacked and run the setup script, for example:

> cd /tmp/ssh2-5.5.1.<build>
> ./setup.sh

If you run the script in the TSO OMVS shell you may need to press the PF10 key from time to time to keep the shell in the RUNNING state.

The setup script does the following:

• It copies the binaries and manual pages under /usr/lpp/ssh2 and configuration files under /etc/ssh2.
• It makes the server program-controlled.
• It creates a host key pair (1536-bit RSA) if none is previously available at /etc/ssh2/hostkey and /etc/ssh2/hostkey.pub. For example, if the software is upgraded from an earlier version, a new key pair is not created but the existing key pair is used. For more information on the server host key, see Section Server Authentication with Public Keys.