Default: ALOG$(syear)$(yweek)

Here, you specify the name of a file in which tp stores information about every transport step for each change request. The file is always stored in the transport directory log.

Default: 0

ctc stands for Client Transport Control and represents a method of configuration for transport routes. This parameter lets you set specific transport routes using various clients in your system landscape. This method requires an extension of the import buffer. This new format is not understood by old tp programs. Therefore, this new function is switched off by default and the user must explicitly turn it on.

At the same time, the profile generator of the Transport Management System is also delivered. Along with the transport route configuration in the Transport Management System, the transport profile parameter ctc is automatically switched on from the TMS if it is required for your transport landscape.

When parameter ctc is set, tp requires that you set the value for parameter tp_version to at least 264. This prevents transport control programs with lower version numbers from working with this import buffer. As a result, you can only set the new parameter ctc if all the transport control programs that work with a specific SAP System have at least version 264.

Client category definition enables new options during import, and the general handling of transport requests and target systems. There are also the command options clires and defaultclient.

If you set the parameter ctc, this changes the output of the command showbuffer, because the corresponding target client must also be part of the output.

Default: 0

Transport request names may have a length of 20 characters. However, these transport requests cannot be processed in the previous format of the import buffer. If you set the new parameter nbufform, you can switch this format so that transport requests with names between 10 and 20 characters can be processed. As with parameter ctc, you have to protect this change to the import buffer format from transport control programs that are too old.

When parameter nbufform is set, tp requires that you also set the value for parameter tp_version to at least 264. This prevents transport control programs with lower version numbers from working with this import buffer. As a result, you can only set the parameter nbufform if all the transport control programs that work with a specific SAP System have at least version 264.

Default: 0

A file is created for each user of an SAP System in the transport group in the sapnames subdirectory of the transport directory. The file is given the name of the user. However, non-valid user names in the SAP System may be used as file names in some of the operating systems. Special characters such as " ",".", etc. or the length of the file name permitted could cause problems.

tp offers a solution. The user names are modified to create file names that are valid in all operating systems. The original user name is stored in the corresponding file.

Default: 9

Parameter repeatonerror has an effect similar to parameter stoponerror, but repeatonerror specifies the return code up to which a change request is considered to be successfully processed. Return codes less than repeatonerror are still accepted. Change requests that were not completely processed successfully stay in the buffer.

Since SAP Release 4.5A, you can use the option selectivelanguageimport (sli) to control the selective language import. The default value for this option is sli=no. If sli=yes, you ensure that only the language-dependent data is imported whose languages exist in the system.

Default: 1

This parameter is connected with the parameter stoponerror.

If one of the tools (R3trans, DD Activation, etc.) called by tp outputs a return code that is equal or higher to stoponerror, tp sops immediately.

If stopimmediately = 0, tp lets the current import phase be completed. If serious problems occur, this can lead to the same error messages reoccurring (for example, database problems). If temporary problems occur, this can lead to sequence problems. Therefore, we recommend not changing the default value.

Default: 9

If stoponerror is set to 0, tp is never stopped in the middle of an import or put call. If stoponerror is set to a value greater than 0, tp stops as soon as a change request generates a return code that is equal to or greater than this value. Change requests that still have to be processed for the current step are first completed. However, a syncmark in the buffer of the relevant SAP System functions as a limit here.

If you call tp showparams <SID>, you see that two variables have been set. stoponerror itself is treated as a Boolean variable that determines if tp is stopped if the return code is too high. The numeric value of the stoponerror parameter is stored in the variable badrc.

Default: SLOG$(syear)$(yweek).$(system)

Here, you name a file in which tp stores information about the progress of import actions for a specific SAP System. The file does not store information for any particular change request. The file is always stored in the transport directory log.

The system-specific transport log flies are written to a shared log directory. However, this may become confused. If you set <sid>_log_files as true, tp does not write system-specific transport log files to the log transport directory, instead it writes them to an additional subdirectory called <sid> (.../log/<sid>).

Default: 0

If this parameter is set to a value not equal to zero, a lower version of tp is not allowed work with this transport profile. When the default value (0) is set, the parameter has no effect.

Default value: never

Possible values: never, c_only, always

If you set the parameter to either c_only or always, additional steps are started during the import that generate versions of the imported objects in the target system. This concerns the commands import and put. For more information on these additional steps, see the tp Online Help for both commands. Also call tp with either the command import or put without specifying any other options.

The difference between the values c_only and always concerns the handling of various transport methods. If the parameter vers_at_imp has the value always, all transports are made into a version according to the new method. The value c_only limits the new behavior to transports of originals.