If ssh-broker-g3 is going to be run as a started task, you need to assign a user for running it.
Assign a user to the started task by defining the procedure in the
STARTEDclass and entering the user ID in the
STDATAsegment, for example, for user
RDEFINE STARTED SSHBRKR.* STDATA(USER(SSHBRKR)GROUP(SYS1)) SETROPTS RACLIST(STARTED) REFRESH
Create the USS home directory
/u/SSHBRKRfor the user. Under it, create the
.ssh2subdirectory for storing the remote server host keys (and optionally user keys and the user-specific
ssh-broker-config.xmlconfiguration file). Make the user the owner of these directories, for example:
# mkdir /u/SSHBRKR # mkdir /u/SSHBRKR/.ssh2 # chown -R SSHBRKR /u/SSHBRKR # chmod 700 /u/SSHBRKR/.ssh2
To run the Connection Broker as a started task, you can use the JCL procedure
/opt/tectia/doc/zOS/SAMPLIB (shown below). The JCL must be installed in the procedure library.
//SSHBRKR PROC F=START,OPTS='',WTORCS='1,11' //TECTIABR EXEC PGM=BPXBATSL, // REGION=0M, // TIME=NOLIMIT, // PARM=('PGM /opt/tectia/etc/init.d/ssh-broker-g3 // &F foreground &WTORCS &OPTS') //STDENV DD DSN=&SYSUID..SSZ.SRVR63.PARMLIB(SSHENV), // DISP=SHR //STDOUT DD SYSOUT=* //*STDERR DD SYSOUT=* //STDIN DD DUMMY // PEND
Start the Connection Broker with the following operator command:
== > s sshbrkr
As an OPTS parameter, you can give parameters that the actual binary accepts, such as
-D 2. For example:
== > S SSHBRKR,OPTS='-D 2'