Your browser does not allow storing cookies. We recommend enabling them.

SSH Tectia 
PreviousNextUp[Contents] [Index]

    About This Document >>
    Installing SSH Tectia Server for IBM z/OS >>
        Preparing for Installation >>
        Upgrading Previously Installed Secure Shell Software >>
        Installing the SSH Tectia Server for IBM z/OS Software >>
            Unpacking the Installation Package
            Creating the SAMPLIB and PARMLIB Datasets
            Preparing the System
            Creating the SSHD2 User
            Creating the /opt/tectia Directory
            Running the Setup Script
            Enabling Manual Pages
        Removing the SSH Tectia Server for IBM z/OS Software
    Getting Started with SSH Tectia Server for IBM z/OS >>
    Configuring the Server >>
    Authentication >>
    System Administration >>
    File Transfer Using SFTP >>
    Secure File Transfer Using Transparent FTP Security >>
    Tunneling >>
    Troubleshooting SSH Tectia Server for IBM z/OS >>
    Man Pages and Default Configuration Files >>
    Log Messages >>

Creating the /opt/tectia Directory

SSH Tectia Server for IBM z/OS will always be installed to path /opt/tectia.

You need to create the /opt/tectia directory and mount the selected file system to it. If you do neither of the above, the product installation will be tried into the file system where /opt is.

You can have SSH Tectia Server for IBM z/OS installed into an existing HFS or zFS file system (see Option 2 below) or you can create a separate file system for it (see Option 1 below).

Option 1

When you want to create a new HFS or zFS file system for the installation, start by making an empty tectia directory under /opt:

> cd /opt
> mkdir tectia

Ensure that the /opt/tectia directory is writable and that it is owned by the SSHD2 user:

> chmod 755 /opt/tectia
> chown SSHD2:0 /opt/tectia

Next, create the file system. You can use the CREAHFS example from SAMPLIB (shown below). The sample file is for HFS, but zFS can also be used.


//* Allocate a dataset for a USS file system. The space allocated, 250
//* cylinders, corresponds to about 200 MB on a 3390 device.
//HFS      DD  DSN=SSZ.SRVR6110.HFS,
//             UNIT=SYSALLDA,
//             SPACE=(CYL,(250,1,5)),
//             DSNTYPE=HFS,
//             DCB=(DSORG=PO),
//             DISP=(NEW,CATLG,DELETE)

To mount the file system on /opt/tectia use the MOUNHFS example from SAMPLIB as shown below.


//* Mount the file system on an existing, empty directory
    MOUNTPOINT('/opt/tectia') +
    TYPE(HFS) +

Note that mounting the file system causes an operator query that must be responded to. You may want to copy the mount command into the BPXPRMxx member in PARMLIB so that the file system is mounted each time you IPL the system.

Option 2

If you want to install the product into an existing file system, for example the one where /usr/local is mounted, make an empty directory in that file system and create a link to it under /opt:

> mkdir /usr/local/tectia_6_0_0
> ln -s /usr/local/tectia_6_0_0 /opt/tectia

PreviousNextUp[Contents] [Index]

[ Contact Information | Support | Feedback | SSH Home Page | SSH Products ]

Copyright © 2011 SSH Communications Security Corp.
This software is protected by international copyright laws. All rights reserved.
Copyright Notice


What to read next:

  • Reduce Secure Shell risk. Get to know the NIST 7966.

    The NISTIR 7966 guideline from the Computer Security Division of NIST is a direct call to action for organizations regardless of industry and is a mandate for the US Federal government.
    Download now
  • ISACA Practitioner Guide for SSH

    With contributions from practitioners, specialists and SSH.COM experts, the ISACA “SSH: Practitioner Considerations” guide is vital best practice from the compliance and audit community.
    Download now