SSH

Installation Settings and Defaults

Set up the settings for the installation in the Tectia SSH Assistant's Installation settings and defaults (0 SETM) panel. The settings for installation input (0.1 SETI) and output (0.2 SETO) you must define are described in more detail in the following, and you can also consult the online help.

The settings will be saved in the installation log file, as well as in the user's application profile. The facility for another user to load these settings from the log file is provided by the Load settings profile from logged definition (0.3 SETL) option.

0.1 SETI - Settings for installation input

The following table lists the settings in the Define settings for installation input (0.1 SETI) panel used for customizing the install jobs.

Table 2.1. Define settings for installation input (0.1 SETI)

SettingDescriptionExample value
HLQData set high-level qualifier for this install. The high-level qualifier will be used to name data sets, such as PARMLIB and SAMPLIB, created during installation.SSZ
Version

Version number of the SSH package to install. The version number will usually be part of the name of the original product install tar archive, which will contain a directory named ./ssh-tectia-server-zos-6.5.0.XXX.

Make sure you enter the correct version number! It must correspond with the untarred directory name.

6.5.0.123
InstallerID of the UID=0 user who will run the installation. A user with the needed authority is required to run jobs and perform other actions to complete the installation. Jobs will be generated to grant this user certain rights.BERT
TarballName of the TAR file from which to install Tectia Server for IBM z/OS. The tar archive may be a Unix file or a data set, distinguished by the presence or absence of a leading Unix path symbol. The upload of the tar archive should have been done in binary mode, and for a data set target, its attributes should be RECFM=0 BLKSIZE=32256 LRECL=0 CYLINDERS PRIMARY=120.

Unix file: /tmp/ssz-6.5.0.123.tar.Z

Data set: 'FRED.SSZ.V6500100.TARZ'

LicensesName of the TAR file containing the product licenses. The tar archive may be a Unix file or a data set, distinguished by the presence or absence of a leading Unix path symbol. If the tar archive is gzipped, gzip must be available.

Unix file: /tmp/licenses.tar.gz, /u/fred/licenses.tar

Data set: //'FRED.SSZ.LIC.TAR'

Installer tailored batch jobs output data set details
DSNameName of the tailored batch jobs output data set. If the DSN exists, it must be a partitioned data set. If it does not exist, it will be created.'FRED.SSZ.INSTALL.CNTL'
LogfileName of the installation log data set. The DSN will not be qualified and will be created as a sequential file, deleting it if it already exists. The optional volser and unit will be used if supplied.'FRED.SSZ.INSTALL.LOG'

0.2 SETO - Settings for installation output

The following table lists the settings in the Define settings for installation output (0.2 SETO) panel used for customizing the install jobs.

Table 2.2. Define settings for installation output (0.2 SETO)

SettingDescriptionExample value
Target ZFS details:
DSNameName of the data set for the installation zFS. The DSN will be used to tailor jobs to allocate and define the zFS, as well as mount commands and BPXPRM parameters.'SSZ.V6500XXX.ZFS'
MountpointMountpoint name for the installation zFS. The mountpoint name specifies the point in the Unix file system where the installation zFS will be mounted. It is used in generating jobs, commands and parameters./u/vendor/ssz-6500XXX
System libraries to receive procs and parms:
ProclibName of the system library to receive procs. The proclib name is used in generating jobs to install cataloged procedures for started tasks for the SSH server and other server tasks.USER.PROCLIB
ParmlibName of the system library to receive parms. The parmlib name is used in generating procedures for started tasks such as the SSH server.USER.PARMLIB

0.3 SETL - SSH Settings Log

Use this panel to indicate the SSH settings log to use.

SSH settings defined by another user may be loaded from the log file where they have been saved, enabling another user to continue the installation using those settings.