DMC_IU - DMC: Nachrichten f�r den Integrierten Upgrade
The following messages are stored in message class DMC_IU: DMC: Nachrichten f�r den Integrierten Upgrade.
It is part of development package CNV_DMCU in software component CA-LT. This development package consists of objects that can be grouped under "MWB: Management of Upgrade Actions".
It is part of development package CNV_DMCU in software component CA-LT. This development package consists of objects that can be grouped under "MWB: Management of Upgrade Actions".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Function &1 started on &2 at &3 |
| 001 | Function &1 finished on &2 at &3 |
| 002 | Older object lists for specified release passage are deactivated |
| 003 | Object list &1 for the specified release passage was created |
| 004 | &1 entries read from buffer &2 |
| 005 | Error while reading buffer file &1 |
| 006 | Transfer content of the transport requests in the buffers |
| 007 | Error while transferring the content of transport request &1 |
| 008 | Transport &1 (&2) was created for &3 by buffer analysis |
| 009 | Error in buffer analysis: Transport to &1 could not be created |
| 010 | Action canceled by user |
| 011 | No content found for the specified object list |
| 012 | Task &1 does not contain any objects |
| 013 | Lock error while creating the upgrade transport for &1 |
| 014 | You are not authorized to create the upgrade transports for &1 |
| 015 | &1 canceled because of COMMUNICATION ERROR on &2 at &3 |
| 016 | &1 was canceled because of SYSTEM FAILURE on &2 at &3 |
| 017 | &1: &2&3 |
| 018 | Object list &1 does not exist |
| 019 | This step requires manual activities |
| 020 | The TP parameter file could not be read |
| 021 | For parameter &1, the necessary value has not been maintained |
| 022 | Parameter &1: target value: '&2', actual value: '&3' |
| 023 | Parameter &1 is not maintained in the parameter file |
| 024 | Error while creating the upgrade transports for &1 |
| 025 | Error while reading the entries for request &1 |
| 026 | For more information, see the spool |
| 027 | Error while filling the upgrade transports for block &1 |
| 028 | Object list &1 is not active |
| 029 | Upgrade transport &1 has already been exported |
| 030 | Transport dispatcher is not scheduled in client &1 |
| 031 | Upgrade transport &1 does not exist |
| 032 | Error while exporting upgrade transport &1 |
| 033 | Import is not possible as upgrade transport &1 has not been exported yet |
| 034 | Transport buffer of target system could not be read |
| 035 | Error while adding upgrade transports to the transport buffer |
| 036 | Error while importing upgrade transport &1 |
| 037 | No TP parameter file has been specified |
| 038 | No client has been specified |
| 039 | Error while maintaining TP parameter file for client &1 |
| 040 | Error while maintaining TP parameter file in all clients |
| 041 | Standard TP parameter file could not be determined |
| 042 | TP parameter file &1 for client &2 has been maintained |
| 043 | TP parameter file &1 has been maintained in all clients |
| 044 | Function &1 has already been processed |
| 045 | The preceding steps are not yet completed |
| 046 | No TP parameter file has been maintained for the target client |
| 047 | Specified client &1 does not exist |
| 048 | Export of template client &1 is not yet completed |
| 049 | Error while writing the data for client &1 |
| 050 | An import has already been started in client &1 |
| 051 | Data for export is already maintained in client &1 |
| 052 | Transfer object entries of request &1 |
| 053 | Buffer analysis started on &1 at &2 |
| 054 | Buffer analysis completed on &1 at &2 |
| 055 | Namespace for the creation of upgrade transports is exhausted |
| 056 | Error while changing status of upgrade transport &1 |
| 057 | Upgrade transport &1 for &2 - block &3 created in target system |
| 058 | Error while saving the upgrade transports for &1 in control table |
| 059 | Upgrade transport &1 has been exported |
| 060 | Upgrade transport &1 has been imported into client &2 |
| 061 | Error while inserting data in target system |
| 062 | Export of client &1 has been accepted for client &2 |
| 063 | XPRA list for client &1 was loaded successfully |
| 064 | Release passage of client &1 was maintained |
| 065 | No XPRA list for client &1 has been loaded yet |
| 066 | No release passage has been defined for client &1 yet |
| 067 | For client '&1' / component '&2', upgrade info has already been defined |
| 068 | Error while deactivating older object lists for the same release passage |
| 069 | Error while creating object list &1 for specified release passage |
| 070 | Error while saving data that was extracted from buffers |
| 071 | Error while saving analyzed data (transport &1, block &2) |
| 072 | No analysis is executed as &1 does not contain any objects |
| 073 | No analysis is executed as &1 contains only object lists |
| 074 | Start of 'Creation of Upgrade Transports' for &1 - block &2 |
| 075 | End of 'Creation of Upgrade Transports' for &1 - block &2 |
| 076 | Tests before creation of exports are completed |
| 077 | Parallel import is possible; &1 upgrade transports are created |
| 078 | Pparallel import is not possible |
| 079 | &1 contains only comment entries; no transports are created |
| 080 | Client of the RFC destination is not equal to the selected client |
| 081 | Upgrade transport &1 has already been imported into client &2 |
| 082 | Status '&1' was set for client &2 |
| 083 | Error while setting status '&1' for client &2 |
| 084 | Error while creating export; status '&1' cannot be set |
| 085 | Not all transports have been exported; status '&1' cannot be set |
| 086 | Not all transports were imported; status '&1' cannot be set |
| 087 | An upgrade transport has already been created for block &1 |
| 088 | An export with a different object list has already been created |
| 089 | No differences in support package level found |
| 090 | Not all relevant support packages for component &1 found |
| 091 | Error while reading the support packages in the receiver system |
| 092 | &1 support packages for the specified support package difference found |
| 093 | Upgrade necessary because of different release level in component &1 |
| 094 | Differences found in support package level of component &1 |
| 095 | Support package level of component &1 is identical |
| 096 | No relevant data found in support package difference |
| 097 | Upgrade ID &1 does not exist |
| 098 | No active object list for upgrade &1 found |
| 099 | Buffer names are not maintained completely |
| 100 | Transport request &1 does not exist |
| 101 | You are not authorized to read transport request &1 |
| 102 | Namespace for creation of analysis transports is exhausted |
| 103 | Error while reading system information via RFC connection &1 |
| 104 | Object list &1 could not be activated |
| 105 | Object list &1 could not be deactivated |
| 106 | Error while scheduling transport dispatcher in client &1 |
| 107 | You are not authorized to schedule transport dispatcher in client &1 |
| 108 | Error while creating command &1 |
| 109 | Errow while executing command &2 |
| 110 | Error while executing XPRAs (see XPRA log) |
| 111 | Error while writing the log |
| 112 | Error while reading system data via RFC connection &1 |
| 113 | System data of sender system has not been specified |
| 114 | System data of receiver system has not been specified |
| 115 | Error while creating upgrade ID &1 |
| 116 | Upgrade ID &1 has already been created with different data |
| 117 | XPRAs have already been executed; list cannot be loaded |
| 118 | Start of language replenishment cannot be started for client 000 |
| 119 | Language replenishment in job &1; ident number &2 started at &3 on &4 |
| 120 | Not all XPRAS have been executed; status '&1' cannot be set |
| 121 | Component &1 (from upgrade buffer) does not exist in receiver system |
| 122 | Component &1 has not been part of the upgrade buffer |
| 123 | Different Release for comp. &1; upgrade buffer: &2, receiver system: &3 |
| 124 | Different SP level for comp. &1; upgrade buffer: &2, receiver system: &3 |
| 125 | Compatibility of upgrade buffer could not be checked |
| 126 | &1 relevant BC Sets found |
| 127 | BC Sets in client &1 activated |
| 128 | Cross-check (counting) for client &1 not completed successfully |
| 129 | Language supplementation started for language &1 |
| 130 | Error during language supplementation for language &1 |