Your browser does not support HTML5 local storage or you have disabled it. Some functionality on this site, including saving your privacy settings and offering you special discounts, uses local storage and may not work with local storage disabled. We recommend allowing the use of local storage in your browser. In some browsers, it is the same setting used for disabling cookies.
Space: 200 MB, 250 Cyls, read-only after installation
Contains configuration files and keys for the server.
Space: 1 MB, read/write
Each z/OS user account that runs SSH client programs or accesses the server must have a USS home directory ($HOME, for example, /u/home1/username). The system will create the .ssh2 directory under the home directory. It contains the user's configuration files and keys.
Space: 128 kB, read/write
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
Contains users' temporary files used in SSH agent forwarding.
Space: 8 kB, read/write
SSH Tectia Server for IBM z/OS, when installed, mainly consists of a directory structure under /usr/lpp/ssh2. You may create a symbolic 'ssh2' link to the place where the directory structure resides under /usr/lpp or you may want to create a separate HFS or zFS file system for it.
The setup script and runtime programs of SSH Tectia Server for IBM z/OS create the /etc/ssh2 and $HOME/.ssh2 directories as needed. If you want any of these 'ssh2' directory levels to be a link to some other spot in your directory hierarchy, create the link before running the setup script or program.
The /tmp directory must exist in advance and it must be user-writable.
The SSH agent forwarding status files under /tmp are temporary and valid only while the actual user process is running.
Although this version of SSH Tectia Server for IBM z/OS must be installed in a USS file system and use the directory structure shown above, the server supports the transfer of MVS files and all the programs can be executed in JCL by BPXBATCH, BPXBATSL, and oshell.