The product structure and the installation directory of Tectia Server for IBM z/OS has changed in version 6.0. If you have an earlier version of Tectia Server for IBM z/OS installed, it can coexist with version 6.0, as can the 5.x version.
The upgrade procedure will migrate your 5.x configuration and the keys automatically to the 6.3 version.
Before proceeding with the installation as described in Installing the Tectia Server for IBM z/OS Software, consider the following issues.
When you run
setup.sh for upgrading from version 5.x you must choose whether you want to uninstall all 5.x files or keep the old 5.x installation intact. You must run
setup.sh either with
If you choose to uninstall 5.x, please note that the directories
/usr/lpp/ssh2 will get unconditionally removed after the upgrade procedure has successfully completed. Make sure that those directories do not contain any files you want to keep for reference (ad-hoc configuration backups, notes etc.) before running
If you choose to keep the 5.x installation, nothing from the old 5.x will be uninstalled by the
setup.sh script. In case you want to have both the 5.x and the 6.3 servers running simultaneously, you must change the TCP port of either one of them, because otherwise the two installed servers will compete for default port 22.
To avoid conflicts at the next IPL please check and update:
Your started task JCL for the server
Operator instructions for running the server
sshd2init procedures (
When upgrading from 5.x to 6.3, these files/directories under
/etc/ssh2/ are copied from the 5.x installation to your new installation at
/opt/tectia/ and they continue to be used with Tectia Server 6.3 for IBM z/OS:
If you are using the SOCKS proxy functionality, you must review and update your
ssh-socks-proxy-config.xml configuration file after
setup.sh has finished.
$HOME/.ssh2/ssh2_config configuration files are not used by Tectia Server 6.3 for IBM z/OS client components. You have to create new files
opt/tectia/etc/ssh-broker-config.xml (for global configuration) and
$HOME/.ssh2/ssh-broker-config.xml (for user-specific configuration).