TH - Nachrichten fuer das Austauschverfahren
The following messages are stored in message class TH: Nachrichten fuer das Austauschverfahren.
It is part of development package SAUS in software component BC-UPG-TLS-TLA. This development package consists of objects that can be grouped under "Transport Control (Repository Switch)".
It is part of development package SAUS in software component BC-UPG-TLS-TLA. This development package consists of objects that can be grouped under "Transport Control (Repository Switch)".
Message Nr ▲ | Message Text |
---|---|
000 | RSPUSCA4: Calculation of documentation to be exported |
001 | Documentation &1 &2 &3 with type 'M' is being saved |
002 | Documentation of object &1 &2 &3 is being saved |
003 | Documentation &1 &2 &3 is being saved |
004 | Documentation &1 &2 &3 already exists in request &4 |
005 | Request &1 created |
006 | Documentation objects entered in request &1 |
007 | Target release could not be determined: RC &1 |
008 | Documentation &1 &2 &3 is in a different namespace and is not saved |
009 | &3 objects from request &1 were inserted in request &2 |
010 | RSVBCHCK: Checking for open update requests |
011 | Start: Selecting patch integration file and integrating requests |
012 | Patch integration file &1 was selected |
013 | User wants to repeat PREPARE module |
014 | User wants to reset PREPARE |
015 | Serious error when selecting the patch integration file |
016 | No patch integration file was found |
017 | Unable to find NCVERS entries with key &1 (RC = &2) |
018 | Unable to write NCVERS entry &1 (RC = &2) |
019 | Inconsistent input parameter in SPDA_GET_PATCH_QUEUE call |
020 | Error when reading the Support Package file |
021 | No patches found or prerequisites were not met |
022 | An internal error occurred in SPDA_GET_PATCH_QUEUE |
023 | This release is not supported (Release >= 4.0B) |
024 | A miscellaneous error occurred in SPDA_GET_PATCH_QUEUE |
025 | This release is not supported |
026 | An error occurred in the patch file / unable to find patch |
027 | An internal error occurred in SPDA_DISASSEMBLE_QUEUE |
028 | A miscellaneous error occurred in SPDA_DISASSEMBLE_QUEUE |
029 | -> & objects from Support Packages pending export |
030 | Error while determining Support Packages for component & |
031 | Collecting objects from Support Packages pending export in &, & |
032 | Objects from Support Package & are being checked |
033 | No add-on component has been installed |
034 | No mapping exists between software component and business function set |
035 | No mapping exists between software component and IO functions |
036 | In exit module &1 the following error occurred: &2 |
037 | Error occurred while writing to SFW upgrade table &1 |
038 | Exit module &1 is not remote-enabled |
039 | No exit module defined for business function set &1 |
040 | Unable to delete table entries in database table &1 |
041 | Exit module &1 does not exist in the system |
042 | Interfaces of exit module &1 are not consistent |
043 | Business function set &1 is being activated |
044 | Enterprise add-on function &1 is being activated |
045 | Business function &1 (of BFS &2) remains inactive |
046 | No business function set is activated |
047 | No business function set could be determined |
048 | View & exists on the database and will be deleted |
049 | Delete view & manually (SOL) |
050 | RADNTABCOR: Correcting DBTABPOS in runtime object from & |
051 | Active runtime object table & could not be read |
052 | Database items set from & to 0000 |
053 | Database items set successfully |
054 | Database items not set |
055 | Active runtime object in table & could not be written |
057 | Start stress_maker -> init_stress( ) |
058 | End stress_maker -> init_stress( ) |
059 | Start stress_maker -> start_stress_upg( ) |
060 | End stress_maker -> start_stress_upg( ) |
061 | Start stress_maker -> stop_run( ) |
062 | End stress_maker -> stop_run( ) |
063 | Start stress_maker -> DELETE_ENVIRONMENT_UPG( ) |
064 | End stress_maker -> DELETE_ENVIRONMENT_UPG( ) |
065 | Starting conflicht handling test |
066 | Ending conflict handling test |
067 | Conflict handling test ended with errors |
068 | Conflict handling test ended without errors |