In this example we have two started tasks for two sshd2 servers:
SSHD2
and SSHD2B
.
Configuration Files
Create two separate configuration files for the two servers to maintain their PID files
distinct. In this example we have files /opt/tectia/etc/sshd2_config
and /opt/tectia/etc/sshd2b_config
.
PID Files
The only difference between the two configuration files is the value of the PidFile
keyword. It specifies the file where the process
ID of the Server is written. For example, for SSHD2
in
/opt/tectia/etc/sshd2_config
the PidFile
keyword has
the default value:
PidFile /opt/tectia/var/run/sshd2_22.pid
For SSHD2B
in /opt/tectia/etc/sshd2b_config
we specify
the PID file sshd2b_22.pid
:
PidFile /opt/tectia/var/run/sshd2b_22.pid
TCP/IP Stacks
In this example started tasks SSHD2
and SSHD2B
use
TCP/IP stacks TCPIP
and TCPIPB
, respectively.
You can specify the TCP/IP stack using the environment variable
_BPXK_SETIBMOPT_TRANSPORT
. You can set it in the STDENV DD
for
BPXBATxx
jobs, for example for SSHD2B
:
//SSHD2B PROC OPTS='-f /opt/tectia/etc/sshd2b_config' //TECTIA EXEC PGM=BPXBATSL,REGION=0M,TIME=NOLIMIT, // PARM=('PGM /opt/tectia/sbin/sshd2 -F &OPTS') //STDENV DD DSN=<HLQ>
.V650.PARMLIB(SSHENV),DISP=SHR // DD DSN=<HLQ>
.V650.PARMLIB(TCPIPB
),DISP=SHR //STDOUT DD SYSOUT=* //*STDERR DD SYSOUT=* //STDIN DD DUMMY // PEND