tp return code transfer (return code 14) - Free download as PDF File (.pdf), Text File (.txt) or read online for free. ">
Nothing Special   »   [go: up one dir, main page]
Scribd Logo
Upload

Welcome to Scribd!

  • 93 views

    TP196: R3trans - TP Return Code Transfer (Return Code 14)

    Uploaded by

    Marianna Müller

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    TP196: R3trans - TP Return Code Transfer (Return Code 14)

    Uploaded by

    Marianna Müller
    93 views3 pages

    Original Title

    Untitled

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    93 views3 pages

    TP196: R3trans - TP Return Code Transfer (Return Code 14)

    Uploaded by

    Marianna Müller

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    You are on page 1of 3

    2019-08-27 43552

    43552 - TP196: R3trans -> tp return code transfer (return


    code 14)
    Version 13 Type SAP Note
    Language English Master Language German
    Priority Recommendations / Additional Info Category External error
    Release Status Released for Customer Released On 20.12.2007
    Component BC-CTS ( Change and Transport System )

    Please find the original document at https://launchpad.support.sap.com/#/notes/ 43552

    Symptom

    R3trans terminates with return code 14. The following error message is displayed
    at the end of the log:
    2EETP196 returncode of "R3trans" was not transferred correctly. See Note 43552.

    Other Terms

    tp, R3trans, return code, 14, TP196

    Reason and Prerequisites

    The following problem occurs (this problem cannot be reproduced): tp calls


    R3trans. An error occurs for R3trans, which terminates too early. tp should
    receive return code 12 and therefore respond accordingly. However, tp receives
    return code 0 and responds as if the R3trans import had been carried out
    succesfully.
    To analyze the problem, an error prevention mechanism was installed in tp and
    R3trans. R3trans also writes its return code to the log and tp compares the two
    values. If tp does not find the relevant log lines, R3trans has terminated too
    early. The return code must not be lower than 12.

    Solution

    Check for any of the following known causes:

    • The system may assign return code 14 because there is no longer any disk
    space avalaible in the transport directory. As a result, the transport logs
    can no longer be written completely.

    • In TPPARAM (parameter file for tp), the parameter R3transpath is set so that
    there is no direct reference to an an executable program R3trans. Instead,
    there is a reference to a shellscript or a command file.
    The system then calls different R3trans executables according to various
    criteria in this shellscript or in these command files only.
    However, the return code of the R3trans call is not taken into account and
    is lost. This error usually occurs after a 3.0E upgrade for the first time
    and then occurs frequently. Furthermore, for this type of error, successful
    R3trans calls (not only terminated calls) are also indiacted with return
    code 14.
    Solutions:

    • In TPPARAM, directly navigate to the correct R3trans. You can use


    UNIX: r3transpath = /usr/sap/$(system)/SYS/exe/run/R3trans

    © 2019 SAP SE or an SAP affiliate company. All rights reserved 1 of 3


    2019-08-27 43552

    NT: r3transpath =
    \\<HOST>\sapmnt\<SID>\sys\exe\run\R3trans.exe
    or
    UNIX: r3transpath = R3trans

    • NT: r3transpath = R3trans.exe


    If necessary, these parameters can also be qualified with the system
    name, for example
    UNIX: XYZ/r3transpath = /usr/sap/$(system)/SYS/exe/run/R3trans
    NT: XYZ/r3transpath =
    \\<HOST>\sapmnt\<SID>\sys\exe\run\R3trans.exe

    • An additional option is available under UNIX (however, we do not


    recommend that you use this option):
    You can enhance the shellscript so that the return code is kept
    directly after each R3trans call
    (for example, set rc=$status) and is displayed at the end of the
    shellscript (for example, exit $rc).

    • In Release 3.0, tp calls R3trans with the system() command (only during an
    export). In this process, the system uses an unusual shell.
    You can use the UNIX command 'man system', to find out which shell is used.

    • For some reason, the normal signal processing does not work, for example,
    when using nohup. However, this cause has not yet been proven. If you have
    the impression that this may be the case in your system, contact SAP.

    • Under Windows NT, the problem may occur because Dr. Watson has been entered
    as a default debugger in the registry. If a dump occurs, Dr. Watson
    currently does not remember the real return code of the "trapped" program.
    Instead, it edits the dump and then returns return code 0 (no error).
    However, this only applies to the return code from Dr. Watson. As of Windows
    NT 5.0, the actual return code of the program is probably returned.
    In this case, check whether Dr. Watson was registered as the default
    debugger. To do this, open a command prompt and call regedit. Open the key:
    HKEY_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> Windows NT -> CurrentVersion
    -> AeDebug.
    If the system uses Dr. Watson as the default debugger, the call of the
    program drwtsn32.exe is written in the 'debug' field.
    If this is the case, check whether Dr. Watson wrote a dump. Change to the
    directory %WINDIR% and open the file drwtsn32.log. Navigate to the end of
    the file and check whether the last written dump belongs to the executable
    R3trans.
    Position the current excerpt from the file drwtsn32.log on SAPSERV. Open a
    CSS message and provide is with some information about the circumstances of
    this situation.

    If none of these causes apply, inform SAP of the circumstances that caused this
    situation. Create a problem message in which you refer to this note. We
    recommend that you provide us with as much information about the maintenance
    levels of all participating software components (operating system, database
    system, SAP System, tp version, R3trans version) as possible.

    Other Components

    Component Description

    © 2019 SAP SE or an SAP affiliate company. All rights reserved 2 of 3


    2019-08-27 43552
    BC-CTS-TLS Transport Tools

    This document refers to

    SAP Note/KBA Title

    374799 Correction for the parameter STOPIMMEDIATELY

    34395 tp return codes and programs used by tp

    This document is referenced by

    SAP Note/KBA Title

    374799 Correction for the parameter STOPIMMEDIATELY

    34395 tp return codes and programs used by tp

    © 2019 SAP SE or an SAP affiliate company. All rights reserved 3 of 3

    You might also like