Environment Variables for Client Applications

The environment variables _BPXK_AUTOCVT, _BPX_SHAREAS, and _BPX_BATCH_UMASK must be set as shown in SSHENV and sshsetenv when running Tectia client tools for z/OS programs (see below).

The NAME=VALUE format (as in SSHENV) is used when the client or server programs are run under MVS, and the Bourne shell format (as in sshsetenv) is used when the programs are run from a USS command line.

	Note
	The environment files must not contain line numbers or reading them will fail.

SSHENV:

_BPXK_AUTOCVT=ON 
_BPX_SHAREAS=NO 
_BPX_BATCH_UMASK=0022 
SSH_DEBUG_FMT="%W(72)(2) %Dd/%Dt/%Dy %Dh:%Dm:%Ds:%Df %m/%s:%n:%f %M" 
SSH_MVS_CONSOLE=YES 
_BPXK_JOBLOG=STDERR 
_EDC_ADD_ERRNO2=1

	(Required) `_BPXK_AUTOCVT=ON` activates automatic text conversion of tagged UNIX file system files. If the variable is not set correctly, ssh-broker-g3 fails to start.
	(Required) `_BPX_SHAREAS=NO` defines that ssh-broker-g3 and the client processes are run in separate address spaces.
	(Required) `_BPX_BATCH_UMASK` defines the permissions for newly created files.
	(Optional) `SSH_DEBUG_FMT` can be used to specify the format of the debug messages.
	(Optional) Setting `SSH_MVS_CONSOLE=YES` will cause error messages to be logged to the console, in addition to `stdout`.
	(Optional) Setting `_BPXK_JOBLOG=STDERR` will cause job log messages to be written to the `STDERR` data set specified in the `BPXBATCH` job.
	(Optional) Setting `_EDC_ADD_ERRNO2=1` will cause `errno2` to be shown in debug and error messages.

sshsetenv:

export _BPXK_AUTOCVT=ON
export _BPX_BATCH_UMASK=0022
export _BPX_SHAREAS=NO
export SSH_DEBUG_FMT="%W(72)(2) %Dd/%Dt/%Dy %Dh:%Dm:%Ds:%Df %m/%s:%n:%f %M"
export _EDC_ADD_ERRNO2=1

(For a description of the variables, see SSHENV above.)