Select language:
Entering content frame!--a11y-->

Syntax documentationGlobal Parameters 

  • alllog
  • Default:

    ALOG$(syear)$(yweek)

    Possible values: Text

    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.
    ctc

    Default:

    0

    Value range: Boolean

    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.

    Caution

    The new format of the import buffer, activated by

    ctc=1, requires at least a tp from Release 4.5A. Older tp versions destroy this new import buffer.

    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.
    • nbufform
    • Default:

      0

      Value range: Boolean

      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.

      Caution

      The new format of the import buffer, activated by

      nbufform=true, requires at least a transport control program from Release 4.5A. Older tp versions destroy this new import buffer.

      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.
      • new_sapnames
      • Default:

        0

        Value range: Boolean

        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.

        The prerequisite is that all the SAP Systems in the transport group have at least Release 3.0.

        Caution

        Once you have activated this option by setting

        new_sapnames to true, you may never again set this parameter to false (unless you also delete all the files in the sapnames subdirectory of the transport directory).
        • repeatonerror
        • Default:

          9

          Value range: Numeric

          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.
          • sli
          • 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.

            Caution

            In this case, it makes sense if the number of languages selected (language vector at export) contain all the languages of the target systems during the import. If this is not the case,

            R3trans generates a corresponding warning at import.

            Note

            The languages in the system are the ones for which language imports were already performed. Languages that were not imported are not part of the system and are not overwritten.

            This option is used as of Release 4.5B when importing Support Packages (transaction SPAM).

            • stopimmediately
            • Default:

              1

              Possible values: Boolean

              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.
              • stoponerror
              • Default:

                9

                Value range: Numeric

                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.
                • syslog
                • Default:

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

                  Possible values: Text

                  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.
                  • <sid>_log_files = true
                  • 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>).
                    • tp_version
                    • Default:

                      0

                      Value range: Version numbers

                      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.
                      • vers_at_imp
                      • 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 additional steps are:

                            • Before importing the ABAP Dictionary sources, the transport request is imported (command file Import).
                            • Then a version maker is called in the batch to store the object versions before the import into the versions database. Versions are only then created if the current version of the object is not the same as the latest version in the database, or if a version does not yet exist for the object in the versions database.
                            • The version maker is called at a point in the sequence of the import steps where the version maker was already called to set the flags on the imported objects in the versions database. If
                        vers_at_imp is configured differently from never, real versions are written to the versions database at this point.

                        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.

                        Transports of originals are:

                              • C transports: Relocation without changing development class (for a normal consolidation transport, the object must be transported back again.).
                              • O transports: Relocation with change of development class (In future, the object can be transported from the original system with a consolidation transport. The development class must also be changed during the transport.)
                              • E transports: Relocation of a complete development class (optionally you can specify a new transport layer.)

                         

                         

                        Leaving content frame