In this example we have two started tasks for two sshd2 servers: SSHD2 and SSHD2B.
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.
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:
For SSHD2B in /opt/tectia/etc/sshd2b_config we specify the PID file sshd2b_22.pid:
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:
The sshd2 configuration file is specified with the -f option.
The _BPXK_SETIBMOPT_TRANSPORT environment variable is set in <HLQ>.V650.PARMLIB(TCPIPB):
(Replace TCPIPB with the name of your TCP/IP stack.)
Copyright 2015 SSH Communications Security Corporation This software is protected by international copyright laws. All rights reserved. Contact Information
Highlights from the SSH.COM blog:
Cryptomining with the SSH protocol: what big enterprises need to know about it
Cryptomining malware is primarily thought of as targeting desktops and laptops and is used to hijack system resources to mine cryptocurrency. Read more
SLAM the door shut on traditional privileged access management
Did you know that something as trivial-sounding as granting access for your developers or third parties to a product development environment can throw a gorilla-sized monkey wrench into your operations and productivity? Read more
We broke the IT security perimeter
Everyone understands the concept of a security perimeter. You only gain access if you are identified and authorized to do so. Read more