Your browser does not allow storing cookies. We recommend enabling them.

SSH

Starting the Server

Console

To run sshd2 as a started task, use a JCL procedure such as SSHD2 (shown below), by default USER.PROCLIB(SSHD2) (defined in 0.2 SETO).

SSHD2:

//SSHD2   PROC OPTS='',PORT=
//TECTIA  EXEC PGM=BPXBATSL,
//             REGION=0M,
//             TIME=NOLIMIT,
//             PARM=('PGM /opt/tectia/sbin/sshd2 -F &PORT   1 
//              &OPTS')
//STDENV   DD  DSN=<HLQ>.V663.PARMLIB(SSHENV),DISP=SHR
//STDOUT   DD  SYSOUT=*
//*STDERR   DD  SYSOUT=*
//STDIN    DD  DUMMY
//         PEND
1

Note that when sshd2 is run as a started task, the -F (foreground) option is required to prevent sshd2 from detaching itself as a daemon. If sshd2 is run as a started task without the -F option, it cannot be modified.

Start the server with the following operator command:

===> s sshd2 

The sshd2 job starts.

ISPF

In the Tectia SSH Assistant ISPF application you can manage SSH tasks via submenu 4 TASK. Started tasks may be started, stopped and modified here, provided that the user is properly authorized and that the started task procedure has been generated and installed.

You can control the SSH server (sshd2) via submenu 4.1 TSRV.

Tectia SSH Assistant ISPF application - Tasks: SSH Server (4.1 TSRV)

Figure 3.1. Tectia SSH Assistant ISPF application - Tasks: SSH Server (4.1 TSRV)

To start the server, enter option 4.1.1 TSRVS (Start the SSH server).

You should see the following console message:

 ISF031I CONSOLE <USERID> ACTIVATED
-S SSHD2
 +SSZ0006I Task sshd2 started

USS

[Note]Note

If you want to run the server manually from USS, the SSHD2 user needs to have a login shell defined. Modify the ADDSSHD2 script accordingly.

To start the server manually, log on to Unix System Services (USS) as the SSHD2 user and execute the command:

> /opt/tectia/etc/init.d/sshd2 start

When the version string message appears, you may exit from the shell. The server will continue to run as a process without a controlling terminal. During the startup the server might report warnings that the server daemon cannot access the cryptographic hardware. Those are only warnings and the server starts without the cryptographic hardware mentioned in the warning messages.