The directory structure under Unix System Services (USS) is shown below. The space requirements are approximate upper limits.
/opt/tectia
symlinkSymbolic link to the zFS (Space: 200 MB, 200 Cyls, read/write) that contains executable binaries, setup scripts, configuration files, server key files, manual pages, documentation, license agreement, example JCL scripts.
After installation, Tectia Server for IBM z/OS consists of a directory structure under the
zFS file system defined for it. The zFS is mounted onto a mount point defined at
installation, and pointed to by the /opt/tectia
symlink.
$HOME/.ssh2
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 .ssh2
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.
/tmp
Contains server process ID files and the default STDOUT
and
STDERR
.
Space: 256 kB (300 MB during installation), read/write/sticky.
The /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 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
adjusted with chmod:
:> chmod 1777 /tmp/.
/tmp/ssh-username
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