The directory structure under Unix System Services (USS) is shown below. The space requirements are approximate upper limits.
Contains executable binaries, setup scripts, configuration files, server key files, manual pages, documentation, license agreement, example JCL scripts.
Space: 200 MB, 250 Cyls, read/write
After running the setup script, Tectia Server for IBM z/OS consists of a directory
/opt/tectia. You may create a symbolic
'tectia' link to the place where the directory structure resides under
/opt or you may want to create a separate HFS or zFS file
system for it.
Each z/OS user account that is accessed via Tectia Server or that runs SSH
client programs normally has a USS home directory
$HOME, for example,
/u/home1/username) and under it a
.ssh2 subdirectory. The
directory contains the user's configuration files and keys. The home
directory is required if public key user authentication is used and if
user-specific configuration is needed.
Space: 128 kB, read/write
The runtime programs of Tectia Server for IBM z/OS create the
$HOME/.ssh2 directories as needed. If you want these
directories to be a link to some other spot in your directory hierarchy,
create the link before running the program.
Contains server process ID files and the default STDOUT and STDERR. Used also temporarily during installation.
Space: 256 kB (300 MB during installation), read/write/sticky.
/tmp directory must exist in advance and it
must be user-writable and have the sticky bit on.
The sticky attribute for
/tmp can be checked by
observing the output of
ls(1) and verifying that the letter
t is present in the permissions field:
:> ls -ld /tmp/. drwxrwxrwt 89 WEBSRV SYS1 49152 Apr 11 14:43 /tmp/.
If the permissions differ from
rwxrwxrwxt, they must be
:> chmod 1777 /tmp/.
Contains users' temporary files used in Secure Shell agent forwarding.
The agent forwarding status files are temporary and valid only while the actual user process is running.
Space: 12 kB for each user, read/write