The system assumes that all environment variables needed for setting up the database connection are set correctly before tp is called. For this reason, only user <sid>adm should use tp at operating system level.
This applies in release 6.10 and higher. Unlike in earlier releases, tp now no longer modifies the environment variables.
To set individual environment variables to a specific value other than the default value of the user <sid>adm, you can use the parameter mod_env. You can also use this parameter if you want to use operating system users other than <sid>adm.
For information on the environment variables and their recommended values, see Environment Variables for Setting Up the Database Connection.
The value of this parameter can have the following syntax:
<conditional_statement> can have the following syntax:
<condition> can have the following syntax:
Two special variables can be used for the <condition>:
This variable is replaced by the name of the host where tp is running.
This variable is replaced by the name of the operating system user who called tp.
<statement> can have the following syntax:
set <variable> = <value>
unset <variable>
The syntax of <statement> is independent of the operating system (and of the UNIX shell).
tp automatically converts <statement> to suitable commands to change its environment (together with the environment of any programs that it has started, such as R3trans).
Examples of setting the environment variable MSSQL_USEINTEGRATEDSECURITY to a particular host:
This parameter is usually set automatically during configuration of the transport system. It is set to 1 for all non-SAP systems.
Default: 0
Value range: Boolean
You can use this parameter to make a dummy system known in the global parameter file. No imports are performed for SAP systems with dummy=1.
D11/dummy = 1