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 >>
            System Requirements
            Permission Requirements
            System Limit Requirements
            Directories and Datasets
        Upgrading Previously Installed Secure Shell Software >>
        Installing the SSH Tectia Server for IBM z/OS Software >>
    Getting Started with SSH Tectia Server for IBM z/OS >>
    Setting up Non-Interactive Server and User Authentication >>
    Setting up Non-Interactive Secure File Transfer >>

System Limit Requirements

Check the definitions in BPXPRMxx. The following guidelines are approximate and apply to both the server and the clients.

Tectia requires an address space size of at least 200 MB (MAXASSIZE).

Each concurrent connection typically needs 2 to 3 processes (MAXPROCSYS, MAXPROCUSER). The user limit may require adjusting if many concurrent connections are run under one user ID.

For each concurrent connection Tectia requires:

  • file descriptors (MAXFILEPROC)
  • TCP/IP sockets (MAXSOCKET for file system type INET)
  • AF_UNIX sockets (MAXSOCKET for file system type UDS)

The limits suggested in the z/OS UNIX System Services Planning book are typically adequate except maybe for AF_UNIX. Tectia uses 3 to 4 AF_UNIX sockets for each concurrent connection.

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


 

 
Highlights from the SSH.COM blog:

  • Cryptomining with the SSH protocol: what big enterprises need to know about it

    Cryptomining malware is primarily thought of as targeting desktops and laptops and is used to hijack system resources to mine cryptocurrency.
    Read more
  • SLAM the door shut on traditional privileged access management

    Did you know that something as trivial-sounding as granting access for your developers or third parties to a product development environment can throw a gorilla-sized monkey wrench into your operations and productivity?
    Read more
  • We broke the IT security perimeter

    Everyone understands the concept of a security perimeter. You only gain access if you are identified and authorized to do so.
    Read more